Batch managed stock not pegging in APO

[Former Member]

Hi All,

We have a few thousand materials that are batch managed. it appears that the batch managed stock is not being pegged. It is being brought over in APO from R3 and is visible in the product view... just not being pegged/netted against requirements.

Are there any setting in APO that need to be made for this? We have no issues in R/3.

thanks

[hubert_spohn · Accepted solution]

If the 'total shelf life' is maintained in R3, this triggers APO to consider shelf life data.

You even have to transfer shelf life data for the batches as well (otherwise they are expired and can not be pegged) or you have to clear the planning with shelf life flag in the product master.

Hubert

[Former Member]

Thanks all for the helpful info.

The stock was about to expire that is why it wasn't pegging.

[srinivas_krishnamoorthy]

We have a similar requirement.

We did go through the link below

http://help.sap.com/saphelp_scm50/helpdata/en/3c/0def2c44afb547bf5b98b64d67edfa/frameset.htm

Our requirement was to give planners ability to peg a demand element like purchase req release or dependent demand with batch stocks in a given product location. Honestly could not find any way of doing this at all in APO. Will be useful to know how you go about this.

We are exploring the option of creating a Z table containing list of product locations and batch numbers and quantity available through some RFC call to r3 tables. There will be one more Z table that will be created after a SNP run or after SNP runs are managed by planners. This Z table will have the product location and demand elements created/managed through SNP. Planners will be given a view to match and map the Z tables - they would manage how demand elements peg to batch numbers. This information will go into R3 through CIF(user exit) to keep the relationship between demand elements and batch numbers. We are in the process of designing this, but not very sure if it will work. Its good you have this query out in the forum, and I am curious for any elegant solutions on this.