Phantom Assembly Planning for Project (PIR)

[shinjiin]

Hi All

I am trying to run phantom assembly planning (by WBS) through PIR. What I'm hoping to achieve is - the planned orders for the phantom assembly components will be account assigned to the WBS.

I've maintained PIR for the Phantom Assembly through MD61 with account assignment of Q, to my WBS.

When I run MRP - the components of the Phantom Assembly are exploded, but the Planned Order for the components are non-account assigned.

Is there any possibility for the Planned Orders to be account assigned to the WBS?

Thanks

Jiin

[Caetano]

Hello

Please observe that when you define strategy 59 system generated planned orders with the special type VP.

Note 1595312 provides the following information about these planed orders:

"VP planned orders should be listed on a separate segment on the MRP
List (MD05) or the Stock / Requirements List (MD04). They are used to
trigger the procurement of the components and they are not yet "real".
They should be only relevant for production once a sales order for the
finished product exists, in case of planning without final assembly, or
when the production of the final assembly is executed, in case of
planning at phantom assembly."

Therefore, an account assignment is not expected for this kind of planned orders.

BR

Caetano

[shinjiin]

Hi Caetano

Thanks alot for the advice. In that case, is there any strategy I can use to achieve the results I want to?

i.e. Phantom Level Planned Order (not real) that cannot be converted

Component Level Planned Order that can be converted and are account assigned.

Thanks

Jiin

[shinjiin]

Hi Caetano

I'm rereading your reply again and I'm a little confused by it.

I do absolutely agree that the Planned Order at the Phantom Assembly level should be of type VP and should not be converted.

My question is - at the component level, the Planned Orders generated are of type NB, and can be converted to external procurements. Why should they not have WBS as an account assignment?

Thanks

Jiin

[Caetano]

Hello

This is standard for this strategy type. The account assignment for the

material master can only be inherited from the parent material.

In this case, dependent requirements can either have the same behavior

of the parent material (planned order VP) or they can be managed as

colleactive requirements, without account assignment.

This is defined by the already refered Individual/Collective

Indicator on the Material master.

BR

Caetano

[former_member208398]

Dear,

What is the strategy that you are using for the components?

Check in OPPS configuration, you will find the account assignment category there.

Best Regards,

Rajen

[shinjiin]

Hi Rajen

I'm using a combination of Strategy 11 (Main) and Strategy 51 as the strategy for the components.

Thanks

[Caetano]

Hi Rajen

Try to set the field "individual/collective" of the components to 1. Also, if you are not creating PIRs for the component, it is not necessary to define a strategy.

BR

Caetano

[former_member208398]

Dear,

I hope your components do not have individual/collective indicator = 2 in MRP4 view. If it is '2', then MRP will plan for collective planned orders as receipts for the components not assigned to any WBS.

Once test with individual/collective indicator = 'blank' or '1'.

If you maintain this as 'blank' or '1', the components will follow the account assignment maintained in MD61 for the phantom.

Best Regards,

Rajen

[former_member208398]

Caetano,

Just replied the same.

It is not necessary, but I wanted to be sure whether the components were having any strategy group setting.

BR,

Rajen

[shinjiin]

Hi Almeida

Tried changing the "individual/collective" indicator to 1, but didn't work too.

On the second bit - yes PIR will be created for the components too.

Thanks

Jiin

[shinjiin]

Hi Rajen & Almeida

Many thanks for your response - truly appreciate it !

I've tried the below, but no luck so far

- removed planning strategy from component and set individual/collective indicator = 'blank'

- removed planning strategy from component and set individual/collective indicator = '1

Any other areas i should be watching out for?

Thanks

Jiin

[former_member208398]

Dear Shin,

I tested and worked for me though.

You can further check in CJ20N, check for the Account Assignment Element indicator in the Basic Data tab.

Best Regards,

Rajen

[shinjiin]

Hmm.. that's odd.. not sure what I'm missing

Yeap - my wbs has the account assignment field checked in cj20n

[former_member208398]

Dear Jiin,

Please check one more data.

In CJ20N, go to the project where the WBS belongs. In project header, check the control tab. In the project stock section, check whether the radio button valuated stock is selected.

It is copied from the project profile setting in OPSA.

Best Regards,

Rajen

[shinjiin]

Hi Rajen

My WBS is non-valuated. However, don't think this is the cause - I retried with another WBS that has valuated stock - still doesn't work. The planned orders generated are without account assignments in both scenario.

Thanks

[former_member208398]

Hi Jiin,

There is one more indicator that can drive this effect. Are you using any explosion type in the BOM component level?

To check this, go to the BOM of the phantom assembly, in the component details Basic Data tab, you will find explosion type. If this is blank, system follows the individual/collective indicator of the material master for the components MRP4 view.

If you are having any explosion type maintained, check in SPRO -> Production -> Basic Data -> Bill of Material -> Item Data -> Define Explosion Type

The individual/ collective maintained here is more prior than the material master setting.

Best Regards,

Rajen

[shinjiin]

Hi Rajen

Nothing is maintained for that field at the BOM level. Should I be maintaining it?

Thanks

Jiin

[former_member208398]

Hi Jiin,

Then it should have followed the material master setting. Test with the following set of data:

1. Define an explosion type (in my example 04):

2. Assign this in the component basic data tab in the BOM of the phantom assembly.

3. Run MRP for the phantom assembly in MD02.

Best Regards,

Rajen

[shinjiin]

Hi Rajen

Did that.. not working still

Thanks for the help so far

Jiin

[shinjiin]

Hi Rajen

Any further ideas on this? Perhaps you could share screenshots from your system on how you managed to get them to work?

Thanks

Jiin

[former_member208398]

Hi Jiin,

First of all, I have taken a very very simple example. Please find the attachment and try to replicate the same data and test the results.

I have done this exercise in IDES EhP 4.

The problem is each time I am getting planned orders assigned to the WBS and am unable to recreate your problem, because I do not know what exactly are there in your system. Perhaps you could send a note to SAP in SAP service marketplace so that the SAP people get access to your system and resolve the same.

I was able to get planned orders not assigned to any WBS in the below two situations:

1. When the individual/collective indicator for the components were '2'

2. I used explosion type that forces individual/collective indicator for the components as '2'.

Kindly raise a note to SAP and get this issue resolved. I will sincerely request you to update this thread once you get it done.

Best Regards,

Rajen

[shinjiin]

Hi Rajen

Thanks alot for the reply - will definitely check out SAP marketplace and see if I can find anything to help me there.

If it's not too much of a trouble, may I request that you resend your file over? I can't seem to open it .. another format, maybe?

Thanks alot

Jiin

[former_member208398]

Hi Jiin,

You should be able to open it in office 2010 xml editor. I have just saved my .doc file to .xml.

However, please find another version compatible with 2003 office version.

Attachments allowed are .asc, .txt, .text, .xml, .xsl, .gif, .png, .jpeg, .jpg, .jpe, .ics in scn.

Best Regards,

Rajen

[shinjiin]

Hi Rajen

Thanks - am able to open it now.

I just noticed slight difference in the way you've set up your phantom material as opposed to mine.

My phantom material is running with strategy 59 while yours run with strategy 10.

I agree that when I set strategy 10 to my phantom, the components will have Account Assigned Planned Orders - but I don't want planned orders at the Phantom Level that can be converted to ProdOrd/PR, as they are phantom materials and I do not expect to stock them in my warehouse.

So, what I'm looking for is - planned orders at phantom level that cannot be converted and planned orders at component level that are account assigned.

Thoughts?

Thanks

Jiin

[former_member208398]

Hi Jiin,

Glad I could help you. Well, I can think of a very simple but not so good solution. The suggestion is, you do not maintain any work scheduling view for the phantom material. Without a work scheduling view, system will not allow you to create Production Order.

Also do not maintain purchasing view for the phantom header, so that no conversion to PR takes place.

Please check.

Best Regards,

Rajen

Message was edited by: Rajen Madan