cancel
Showing results for 
Search instead for 
Did you mean: 

Container resource stock not visible in APO detailed scheduling board

former_member276618
Discoverer
0 Kudos
613

Hi,

I've setup resource with storage characteristics, container resources, in ECC/APO and I've set them up in APO as product storage definition (PSD). I've assigned stock (in ECC) on the storage locations linked to these container resources. I've created a fill chart (in APO) and added it to the detailed scheduling board to be able to follow up the stock on these container resources but I'm not able to get this stock in the detailed scheduling board in APO but the planned receipt and issues via planned orders on the product storage definition works well.

Can anybody help me out and let me know how I can get my current stock in the detailed scheduling board as well?

Thanks

Valeska

View Entire Topic
rupesh_brahmankar
Active Contributor

Hello,

Do you have stock is visible at the product view?

Does resource flag 'Storage Character.' is set at General Data tab?

Storage location assigned to the resource is assigned to a MRP area location or plant level?

Please refer SAP note 2434473 - Blank Resource Utilization and Product Stock Chart in /SAPAPO/CDPS0 and

2129054 - DSPB: Material Information is not displayed correctly in Product Stock Chart

Best Regards,

R.Brahmankar

former_member276618
Discoverer
0 Kudos

Hello R,

Thank you for your answer. We found out the root cause ourselves, your answer guide us there.

The 'Storage Character.' was on the resource in question. However, a few weeks ago we made different container resources for the same storage locations. We changed the link between resource and storage location in CRC2 in ECC but apparently this does not change the sublocation in the resources in APO. As such, there were two separate container resources in APO with the same sublocation. We could not find the stock on one resource because the stock was linked with an "old" container resource not in our detailed scheduling profile. This problem was completely after we completely deleted the old resources from APO and ECC.