The selection and aggregation of the quantities requested and delivered shall be carried out dynamically; each field in a planning agreement and the referenced master data can be considered characters. This can be agreed by the user, the user group or globally through entries in the respective tables. A new planning agreement is used to convey a customer`s current requirements. Often, it is agreed that the quantities requested in the short term (frozen area) cannot be changed by a new delivery schedule. In the case of a high planning agreement sequence and the transmission of a high number of delivery dates, this cannot be controlled. Delivery dates are often adopted in planning agreements without prior availability checks. This can lead to the problem that by submitting a new delivery date, the customer immediately creates a backlog at the supplier (request sent today to be delivered yesterday). The date requested by the customer is used in a similar way to the date indicator day, week and month used and assigned accordingly in the ratings. This assignment is analogous to the SAP standard when processing planning agreements and orders. Previously, the display of deliveries from the past was enabled when selecting the requirement of the planning agreement, the delivered quantities are also displayed for the requirements of the purchase order.
Depending on the time windows, the result of the current analysis is displayed as traffic lights in the first result screen. This clearly indicates at first glance how many times the customer has not complied with the agreements. In the detail screen, deviations are displayed in pieces or percentage by selected period, colored information indicates violations. The environmental analysis of the requirements for the ESA, TAM and JIT processes checks whether the forecast data in the planning agreements correspond to the subsequent process in terms of time and quantity. It represents quantities in relation to deliveries. All relevant data related to the planning agreement is stored in the QC tab (cumulative quantity). The agreed cumulative quantity is deducted from the cumulative quantity of receipt of the goods, so that the purchasing department and the supplier work on the basis of the same GR quantity at the time of the beginning of the year. The agreed cumulative quantity shall be calculated on the basis of the reconciliation date. Cumulative amount of receipt (@IAG_RAT0. U_Efz): Contains the cumulative quantity received (CQR) that is normally transmitted via EDI using the Forecast Planning Agreement.
The CQR is the sum of all interrupted deliveries to the customer from the date of the zero position until the deadline (date of the last delivery). In the standard, the basis of calculation is the “open quantity” expected for the date of availability of the material, but any quantity considered open or the planning agreement and order requirements may be designated as the basis. The planning agreement requirements analysis displays the current demand quantities of the types of planning agreements available in a results matrix. Capacity analysis extends the screen of the results of the planning agreement requirement by displaying the available capacity of a period and the possible mismatch or overlap. You can transfer this additional data to SAP APO in the planning agreement line using IDoc DELFOR02 – Scheduling Agreement/JIT Date. The cumulative quantities on the left side of the planned planning agreement are based on all delivery orders for the planning agreement. These are: In the JIT planning agreement, customers specify the “approximate” request transmitted (forward planning agreement) for the short-term period (horizon of the JIT planning agreement). While the forecast planning agreement primarily reflects monthly requirements, the JIT planning agreement is specified on a daily basis. The SAP standard system does not allow verification of whether the JIT planning agreement corresponds to the forward planning agreement, especially with regard to quantity deviations. – Transit quantity and problem-free delivery quantity of goods You use this function to adjust the cumulative quantities in planning agreements for delivery orders. This is possible: Along with the actual requirement, other information can be displayed on several lines: – Value in the target currency, selectable price base – type of additional planning agreement, e.B. Scheduling of scheduling agreements – Quantity and/or percentage deviations The following variants are proposed for the calculation of the open quantity, which can be activated individually but also in parallel: – Open quantities for the date of the planning line, Non-emission delivery quantities of goods are open – Open quantities without issuing goods are not opened – Quantities opened on the day of arrival, Non-emission quantities of goods are open on the day of arrival, Non-emission quantities of goods are not open The Bensberg component “Quality/Demand Analysis of the Planning Agreement” is the central analysis of the requirements of the SD customers and its environment.
Keywords: cumulative quantities, planning agreement, cumulative quantity, quantity received, current fiscal, cumulative quantity delivered, quantity delivered, system determined, specified delivery, customer shipments, system checks, difference between, planning agreement, cumulative delivery, master customer, delivery quantity The Bensberg component verifies each planning agreement and determines the complete MRP based on the date of the planning line: date of physical supply, date of planning line, date of issue of goods, etc. . .
