User Transaction Guide Stahl Sap 4.7: Trigger
User Transaction Guide Stahl Sap 4.7: Trigger
7
Function Module : Process Planning
Transaction : CO09
Trigger:
Prior to initiating production, the SAP R/3 system enables the production planner to verify the
availability of material required to satisfy requirements.
The availability is determined according to the ATP (available to promise) method. Using
this method, the system checks :
whether the material requirements can be covered on the requirements date, and
at what point in time the requirements can be covered, if a full coverage of the
requirements is not possible on the requirements date.
Procedural Steps
/conversion/tmp/activity_task_scratch/579613756.doc Page 1 of 4
Requirements Production Order Control Availability Overview, OR
/conversion/tmp/activity_task_scratch/579613756.doc Page 2 of 4
1.3 Use the ENTER icon to perform the check.
GENERAL NOTES:
According to ATP logic, the system checks whether the dependent requirements of each
component are covered by specific receipt and issue elements or by stock. This check is
carried out dynamically; that is, each time you carry out the check, the system
recalculates the current situation. If a quantity can be committed for the requirement date,
the system commits precisely this quantity in the dependent requirements. The ATP
quantity for the components is reduced by this committed quantity. Therefore, in the next
availability check, dependent requirements can only be committed for the amount of the
remaining ATP quantity.
In planned independent requirements, the system only checks the open planned
independent requirement quantities created for the components. This means that the
ATP quantity is not included in this availability check, and neither are receipts or stocks.
The system uses the open planned independent requirements quantity at the component
level to determine a committed quantity, and this quantity is copied to the planned order
header in the Committed Quantity field. In contrast to the availability check according to
ATP logic, however, the committed quantity is not recorded in the dependent
requirements. The planned independent requirements of the components are not
consumed by the committed quantity but by the complete dependent requirements
/conversion/tmp/activity_task_scratch/579613756.doc Page 3 of 4
quantity. In subsequent availability checks, the system can only commit quantities for the
amount of planned independent requirements that have not yet been consumed.
/conversion/tmp/activity_task_scratch/579613756.doc Page 4 of 4