on 08-26-2011 4:46 PM
Hi,
I would like to know how ATP check takes place at component level during multileve ATP check for finished product.
The requirement is that, system should consider component availability and then only promise date for Finished goods.
Further, if BOM contains many components then system should calculate FG availabilty considering the component quantity which is least available in quantity.
Let me know if this is possible in MATP and if yes how? and if ECC planning strategy, planning without final assembly is required for this ?
Regards,
YR
YR,
The requirement is that, system should consider component availability and then only promise date for Finished goods.
This is standard in MLATP
Further, if BOM contains many components then system should calculate FG availability considering the component quantity which is least available in quantity.
This can be configured. Alternatively, you can leave sales orders unconfirmed if it is impossible to determine availability of a component.
if ECC planning strategy, planning without final assembly is required for this ?
Planning without final assembly is not required.
Read online help at
http://help.sap.com/saphelp_scm70/helpdata/EN/05/7e1f3bc779144ae10000000a114084/frameset.htm
for more info.
Best Regards,
DB49
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi DB49,
thanks for clarification. I have further query related to same. I have gone through the literature. It says that MATP does not consider capacity when creating planned orders and it can be done in CTP.
So if infinite capacity is considered, what (in which cases) is the use of promising dates of finished goods using such a feature.
Because anyways capacity leveling will take place later which would again change the promise dates.
Regards,
YR
YR,
It says that MATP does not consider capacity when creating planned orders and it can be done in CTP.
Well, MultiLevel ATP only creates planned orders during the "ATP Tree" conversion process. The conversion itself indeed has no link to capacity consumption. That doesn't mean that capacity was ignored during the ATP tree creation, and during the FGs Sales order confirmation..
what (in which cases) is the use of promising dates of finished goods using such a feature.
The functionality is explained fully in the link, and the answer to your question is contained there. If you don't see any 'use' to using MultiLevel ATP, then there is nothing that I will add, your concept of 'useful' is substantially different from mine, and I have no interest in restating information that is clearly presented in SAP documentation. If you don't see any advantage for your company, then don't use it.
Because anyway capacity leveling will take place later which would again change the promise dates
Well, BOP changes promise dates, not capacity leveling. To your point, cap leveling will not necessarily change your planned order dates, if the dates were originally created so as to fit within capacity limits.
Best Regards,
DB49.
User | Count |
---|---|
8 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.