bom component in sub contracting purchase requisition

[Former Member]

Hello All,

I have a situation.

I have a material (sub-contratced) which I buy from two vendors. Also,this Material has two BOMs.

Requirement :

Post MRP the system should propose procurement proposal where the material is

procured from both vendors with  different BOMs.

So we have created Production versions. also quota arrangement has been

implemented.

Issue :

MRP is proposing subcontracting purchase requisitions from both of the vendors with different production versions and quantities. The subcontracting purchase requisitions are not having BOM components assigned

in one of the purchase requisitions. But if we go in change mode ME52n, and press the explode BOM icon in the material data TAB BOM components reappear..

Please help understanding why this behavior and how we can fix this if possible.

-Vivek

[Former Member]

Experts, Please advise on this issue.

Vivek

[Caetano]

Hi Vivek

Did you implement the suggested notes?

What is the result after a new MRP run with planning mode 2?

BR

Caetano

[Former Member]

Hi Caetano,

Yes I did , but it did not had any improvement. Although I have one observation that , as I earlier mentioned that quota arrangement is also being used. Now I deleted the Quota arrangement ofr this material and the system stared picking the first valid production version from the material master and the issue is no more there.

But the whole idea of using quota arrangement is now missing as I want to procure from two different vendors using two different BOMs.

Vivek

[Caetano]

Hi Vivek

It should be possible to use a quota arrangement.

The mentioned notes correct a program error that may cause the second alternative of a BOM to never be selected. If they are both implemented, you should be able to use the quota arrangement and select the second BOM alternative.

BR

Caetano

[Former Member]

Hi Cateano,

I referred the two notes you referred in the SAP ticket which I had created in the Market place.

One of the note explaned of buffering issue for BOM. Transaction OPPQ

And other was OMI4 for qouta split for the lot sizing procedure.

Post these changes the system started working as exepcted and both of the BOM for the respective production version started reflecting.

Thanks Caetano. I will be keeping this ticket open for some time as I am further doing testing.

Vivek

[Caetano]

Hi Vivek

Thanks for the update.

Please close the thread once you finish your tests.

BR

Caetano

[former_member188931]

Hi Vivek,

Could you please check your Production Version or BOM validity period? or

You can also check the BOM status, whether In-active?

Message was edited by: Hrishi J One more thing, as you have stated that you are using the Production version you can maintain the Production version number in sub-contract info record and then process the MRP again.

[Former Member]

Hrishi,

The objects identified are good in this context. The status is also 1 i.e.active.

VIvek

[former_member188931]

Have you tried to assign the production version in sub-contract info-record and re-run the MRP?

[Former Member]

Yes more than couple of times.

[Caetano]

Hello Vivek

Please make sure that the notes listed on the following document are implemented on your system:

These notes are corrections for program errors that may affect the BOM explosion on MRP on a scenario where production versions are used, therefore, you should implement them and test your scenario again.

BR

Caetano

[Former Member]

Thanks Caetano,

I dont thnk the notes suggested have anything to do with this issue  I am currently facing.

VIvek

[Caetano]

Hi Vivek

I strongly recomment the implementation of such notes.

I know that the description may not fit exactly to your scenario, however, they are corrections on the main program where the BOM explosion is executed during MRP and they are effective on may different scenarios.

If you open an OSS to SAP, you will be requested to implement such corrections before anything.

BR

Caetano

[Former Member]

Okay.

Let me speak with my ABAP person.

These are the screen shots.

In the last screen, the Purchase requsition is in displau mode and on pressing the component push button, the components are not visible.

Even the EBAN table does not have a RSNUM record for this purchase requisition as shown.

-Vivek

[Caetano]

Hello Vivek

After the implementation of the notes, you must run MRP again for this material, in order to force a new BOM explosion.

BR

Caetano