y y y
Attachments:23 Added by Manu Bhatia, last edited by Manu Bhatia on Mar 08, 2009 (view change) What do we need to know?
Dates:Order Date
Date on which the sales order is entered. System proposes the current date by default.
Loading Date
Picking and packing must be completed by this date so that the goods are ready for loading.
Delivery Date
Customer should receive delivery of the goods by this date. The date on which goods are to arrive at the customer's premises. Example: The delivery date can be the delivery date requested by the customer (desired delivery date) or the date confirmed in the vendor's order acknowledgment or shipping confirmation (confirmed or acknowledged delivery date).
Times:Pick/Pack Time
Difference between the material availability date and loading date.
Loading Time
Difference between loading date and goods issue date.
Transit Time
Number of days required for delivering an item from your company to the customer via a certain route.
Enter Plant & Checking Rule, against which the Availability is to be checked. For Sales Order Checking Rule = A, Delivery = B, Back Order = BO
y y y y
Availability Checking Group (Avail Check): 02 Check Rule : A End Lead Time Refers to the end of Replenishment Lead Time. If that is not included in the Configuration, then this field is not visible. Totals Display:** Receipts = Sum of all +ve Quantities in Rec./Reqd qty Column (Leave out the last row, MRP Element 001, since it is a total) These are all the Planned Incoming Movements
o o
Issues = Sum of all -ve Quantities in Rec./Reqd qty Column These are all the Planned Outgoing Movements Confirmed issues = Sum of all (+ve) Quantities in Confirmed Column These are the confirmations against ATP.
requested delivery date, the system goes to Availability screen automatically. (Discussed later) Run Transaction: VA01
Backwards Scheduling
Forward Scheduling
Above is the Availability Screen as seen in Sales Order. It has following Buttons: One-time delivery In the results of Availability, we have 3 options to choose from. This is Case 1, when we can confirm the Customer's Requested delivery Date. The details of this are visible in the first sub screen below. Complete dlv. This is Case 2, when we can confirm the Customer's Requested complete delivery at a future Date. The details of this are visible in the second sub screen below. Delivery proposal
This is Case 3, when we can confirm the Customer's Requested delivery in partial quantities at future dates. The details of this are visible in the third sub screen below. Continue If we select one of the above options, the same gets saved in the ATP results. Otherwise, we can sele ct this button. In that case, system leaves the ATP screen without saving the ATP results.
We have created a SO ( VA01) on 09 Feb, with requested Delivery date for 09 Feb.
Now we change the Availability situation, by changing the PO Date to 12 Feb. See the screens below corresponding to this situation.
The first screen shows the Availability (CO09) Overview. We have an incoming PO on 12 Feb. See the new Cum ATP qty. date wise accordingly.
!image038.jpg!In the second screen We have created a SO on 09 Feb, with requested Delivery date for 09 Feb. See that the Delivery got staggered according to the new Availability situation.
In the screens below, we have simulated the RLT. In the first scenario RLT is not activated, see below: 'Check without RLT'. The system considers only the confirmed inward movements. So out of 500 only 21 is confirmed. See IMG Guide > SD > BF > AC & TOR > AC > AC with ATP > Control of Availability Check
See VA01
In the second scenario RLT is activated, but corresponding data in material master is not maintained. Material is procured In-House (E), but In-house Production time (1st screenshot) & RLT (2 ndscreenshot) are not maintained. The system assumes both these times as Zero. So, complete 500 are confirmed immediately. See MM01
In the third scenario RLT is activated, corresponding data in material master is maintained. Material is procured InHouse (E), In-house Production time (10 days) & RLT (not maintained). The system confirms 21 on basis of incoming material. Rest 479 is confirmed after 14 days. This is because 10 working days for in-house production + 4 holidays (Sat-Sun).
In the fourth scenario RLT is activated, corresponding data in material master is maintained. Material is procured InHouse (E), In-house Production time (10 days) & RLT (20 days). The system confirms 21 on basis of incoming material. Rest 479 is confirmed after 14 days. This is because 20 working days for in-house production + 8 holidays (Sat-Sun).
Material Master Data:MRP 1 > MRP Group MRP 2 > Planned Delivery Time MRP 2 > GR Processing Time MRP 3 > Checking Group for Availability Check MRP 3 > Strategy Group MRP 3 > Total Replenishment Lead Time
Scheduling Data:Transit Time Loading Time Pick/Pack Time Transportation Planning Lead Time