Issue in Storage Location Determination in SAP ECC PP Discrete Manufacturing from Production Version

[dineshudl]

Hi Team,

I am facing an issue related to the storage location determination in SAP PP Discrete Manufacturing when multiple production versions are maintained for a finished good (FG) material.

Scenario:

I have two active production versions for the same FG material, with different issue storage locations assigned to each:

Production Version 1: Issue Storage Location = "SLOC_1"

Production Version 2: Issue Storage Location = "SLOC_2"

In the MRP configuration, I have maintained a setting for the combination of Plant and MRP Group as "2" for storage location determination.

I have not maintained any default issue storage location in the material master or BOM component details.

Transaction & Observed Behavior:

I created a production order manually using transaction CO01. The system automatically determined Production Version 2 based on the lot size.

In the Production Order header (under the Master Data tab), I could see that Production Version 2 was selected, but in the Component Overview of the production order, the Issue Storage Location was still showing SLOC_1 instead of SLOC_2, which should be the expected behavior based on the determined production version.

If I delete Production Version 1, the system updates the issue storage location correctly to SLOC_2.

In summary, when multiple production versions are available, the system appears to default to the issue storage location of the first production version.

Analysis & Gap: This behavior seems to be a gap in the system, as the issue storage location should be updated to reflect the storage location associated with the production version that is automatically determined (in this case, SLOC_2 for Production Version 2).

Request: Could you please advise on how to address this issue so that the system correctly updates the issue storage location based on the determined production version? Any insights on how to resolve this gap would be greatly appreciated.

Thank you.

Best regards,
Dinesh Kumar V

[Prasath]

Hello @dineshudl , I am usure about system version, However could you please try refer this note 616987 - Issue storage location not taken from production version.

Regards

Prasath 

[Jens_Koyen]

Hi @dineshudl 

Do you work with (e)WM? Your components are assigned to an operation of the routing. The operation has a work center. The work center has a supply area. The supply area is linked to a storage location.

If you have this setup, the supply area storage location can be determined and used as well.

The determination happens in a logical predefined order of course. More information on it via SAP note 137225. If your behaviour is different, please check user exits, badi's or check with SAP.

https://me.sap.com/notes/137225/E

Hope this helps.

Kind regards,
Jens Koyen

[dineshudl]

Hi Jens, I don't use any of the setup you mentioned above. If I delete the first Production Version, system determine storage location from second PV. Only if I have multiple PV's, it always goes for first PV Storage Location but other parameter like BOM and routing operation are determined from second PV. Regards, Dinesh Kumar V.

[DerekDing]

1. Pls check the BOM, whether maintain the storage location.

2. If the Storage Location in BOM is Blank.

You should check whether maintained the MRP Group for the material,

Then check the MRP Group configuration in background.

IMG Menu

Production-> Material Requirements Planning-> MRP Group-> Carry Out Overall Maintenance of MRP Groups

If you want to use the storage location in the production version, you can create a new MRP Group and set "Issue storage Location Selection" = "2". Then you can maintain the Finished material with this MRP Group, thank you.

Reference Link: Storage Location Determination in BOM Explosion | SAP Help Portal

[dineshudl]

Hi DerekDing,

I have already checked these settings all looks good but still not functioning as expected.

Do we need to implement any SAP notes ?

Regards,

Dinesh Kumar V.