cancel
Showing results for 
Search instead for 
Did you mean: 

Special Procurement Type function specific to number range

former_member437413
Discoverer
0 Kudos

Hi all,

Please can I ask a question about the functionality behind the special procurement keys. We have maintained entries in OMD9 for stock transfer (direct delivery to customer), as material can be produced or supplied from multiple plants, each plant is assigned its own key and we have used special procurement types 40-49, 'F' external procurement, 'U' stock transfer and then maintained the supplying plant. As the business has grown, we have outgrown the number range and the next two plants have been assigned SPK '52' and '53'.

When we create an STO for materials assigned keys 52 and 53 the total replenishment lead time on MRP 3 in material master is ignored and the planned delivery time is used. However all materials assigned a key between 40 and 49 look at the total replenishment lead time. If I create new keys '4A', '4B' etc the replenishment lead time is used.

Now for my question........From my testing it appears that as long as the key begins with a '4' then the total replenishment lead time is used, if I use any other value such as 'Z1', 'Y1','21','35', etc then only the planned delivery time is used by ATP. Is this normal behavior or do we have some bespoke code hidden in MV45A somewhere influencing this?

Many thanks

Mark

Accepted Solutions (1)

Accepted Solutions (1)

Caetano
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Mark

I have never seen any influence on the special procurement type number range on the ATP results and this is not the kind of logic that you should expect in SAP standard. My guess is that there is some kind of custom code changing the standard system behavior.

Regards,
Caetano

Answers (1)

Answers (1)

former_member437413
Discoverer
0 Kudos

Many thanks Caetano,

Purchasing is not my area of expertise, and I thought this was odd behavior. Now I know this is not standard SAP I'll start digging through the user exit enhancements to see if I can find the offending code.

Many thanks

Mark