Question:
Hello,
we are currently running the collective ATP check using t_code CO28 on planned orders in order to commit receipts and stock against them, this is working fine except that the problem we have is that if the planned order for assembly X requires two components A and B and if the planned order needs i.e. 100 of component A and there is 100 available but also needs 100 of component B of which there are only 50 available, the ATP logic will only commit 50 of component A as there was only 50 of component B, we would like the ATP logic to commit all 100 of component A and the 50 available of component B.
Does anyone know how to achieve this?
Regards,
johnga.
Answer:
Hey Johnga,
In IMG, transaction OPPR, Maintain MRP Groups, there is a setting that affects this.
It's under the area called "Availability Check" then "Check.rule dep.reqt". You have to check "on" the box called " Activate full confirmation logic". This will then commit the all available stock if it can and partials if it can't.
The only caviat to this is that you must assign an MRP Group to all materials in order for this functionality to work. I have not found this as a global setting anywhere else.
Read the help on the box for a better explantion.
Regards,
Greg_S
Answer:
Hello Greg_S,
unfortunately this indicator doesn't appear in that transaction, presumably because we are on version 31I.
Any ideas?
Regards,
johnga.
Answer:
Sorry, I'm not familiar with 3.1
This flag was part of release 4.6A because of the exact req't you have. It releates to transaction MDVP. I don't know if MDVP is part of 3.1
You could try checking a few OSS notes to see if there is a note you could install in 3.1
Check note 111810. You may be able to patch your system.
Try searching on "Full confirmation logic" as a key phrase.
Note 423528 addresses this issue. I'll attempt to paste it here:
--------------------------------------------------------------------------
Symptom
In the missing parts view, the collective availability check for planned orders (Transaction MDVP) displays all planned order components as missing parts although an individual check of corresponding planned orders only flags individual components as missing parts.
Other terms
MDVP, collective availability check, missing parts list,
Missing parts view, partial confirmation logic, full confirmation logic, ...
Reason and Prerequisites
This problem is caused by the system design: For dependent requirements of a planned order, the system generally updates no missing part indicators using the availability check in the corresponding dependent requirements record of table RESB. SAP does not plan to implement changes in the system design of the R/3 standard system that allow processing the missing part indicator from the availability check.
As this indicator is missing, in the missing part view of the collective availability check for planned orders (Transaction MDVP), the system displays all components as a missing part when the quantity of the affected components from the availability check is less than the requirements quantity of the component.
The confirmed quantities of the planned order components depend considerably on the confirmation logic of the availability check for planned orders. For planned orders in the R/3 standard system, a difference is made between the following confirmation logics:
* ATP check according to partial confirmation logic
* ATP check according to full confirmation logic
* Availability check against planned independent requirements
ATP check according to partial confirmation logic
In case of an ATP check, up to and including Release 4.5B, the check according to partial confirmation logic was the only confirmation logic for planned orders supported by the R/3 standard system. As of Release 4.6A, this check logic is preset in Customizing.
For the partial confirmation logic, the system confirms the planned order header and all planned order components proportionally for the same proportion. For calculating a proportion, the component with the least availability is relevant.
Example:
Planned order header - Total quantity : 100 pcs
Planned order header - Confirmed quantity: 30 pcs
Requirements qty Available confirmed
Component A: 200 pcs 300 pcs 60 pcs
Component B: 100 pcs 80 pcs 30 pcs
Component C: 100 pcs 30 pcs 30 pcs
As only 30 % can be confirmed in component C, only 30 % are confirmed in components A and B, using the partial confirmation logic. In the same way, the confirmed quantity of the order is also 30 % of the total quantity of the order.
In the displayed scenario, the system displays all components as missing parts in the collective availability check because their confirmed quantities are less than the corresponding requirements quantities. However, only components B and C are actual missing parts.
ATP check according to full confirmation logic
As of Release 4.6A, the ATP check according to full confirmation logic can be activated in Customizing of the MRP group of the order header. Previously, you could only check according to full confirmation logic after implementing Note 111810.
With the full confirmation logic all components are confirmed in the same way as the production order according to their availability. However, the confirmed quantity of the planned order header is still calculated in proprotion to the component with the lowest availability.
Example:
Planned order header - Total quantity: 100 pcs
Planned order header - Confirmed qty : 30 pcs
Requirements qty Available confirmed
Component A: 200 pcs 300 pcs 200 pcs
Component B: 100 pcs 80 pcs 80 pcs
Component C: 100 pcs 30 pcs 30 pcs
For all components, the system confirms the entire available quantity.
In the scenario described, components B and C are displayed as missing parts in the collective availability check as their confirmed quantities are less than the corresponding requirements quantities.
Availability check against planned independent requirements
The availability check against planned independent requirements can be used for planned orders the components of which were planned by a subassembly planning.
In this case, the confirmation of the components and of the planned order header is not issued based on available stock or fixed receipts for the components. Instead, the planned order is confirmed based on the subassembly planning for the components and on the assignment of the component requirements to be checked to free planning quantities that have not been cleared yet.
In general, this kind of check just leads to a confirmation on the planning order header. Confirmed quantities are not written for the components since there is no assignment of the component requirement quantities to corresponding planned independent rquirements. Assignment and clearing of component requirement quantities is effected in a dynamic way and based on the full requirement quantity of the components.
Since confirmed quantities (RESB-VMENG) are not written for the components, it is not required here to differentiate between a partial confirmation logic and a full confirmation logic. Like with the ATP check, the confirmed quantity of the planned order header is calculated proportionally with regard to the component with the lowest availability.
With this kind of check, all components are indicated as missing parts in the collective availability check because confirmed component quantities are missing. This even applies if the planned order could be fully confirmed in the actual check.
Solution
The system response described corresponds to the current design of the availability check for planned orders and the missing parts list in the R/3 standard system. Changes to the system design of the availability check and the missing parts list are not planned.