The tab “Demands” always displays the last active scheduling agreement. The scheduling agreement can be transmitted via EDI or created manually,
Each row is an allocation in the scheduling agreement (call date, call time, call quantity).
The graphical depiction of a scheduling agreement:
The forecast delivery schedule (scheduling agreement) is displayed through the following columns:
Call date (@IAG_RAT3.U_Etldat):
Is the delivery date at the customer’s.
Call time (@IAG_RAT3.U_Etlzet):
Is the time of delivery at the customer’s. Transmitted only through JIT delivery or JIS delivery.
Call quantity (@IAG_RAT3.U_Etlmng):
Is the demand quantity at the call date.
The graphical display of a scheduling agreement with two cumulative quantities (cumulative quantities received, cumulative quantities delivered):
The cumulative quantity received (CQR) is the sum of the engrossed deliveries since the date of zero position until the boundary date (date of the last delivery). The cumulative quantity delivered (CQD) is the sum of the deliveries since the date of zero position until today’s date. If you add the respective call quantities to the CQR, the result is the “total demand” since the date of zero position until the call date of the allocation. If you subtract the CQD from the “total demand”, the result is the quantity to be delivered (“planned” quantity) for the respective allocation.
Quantity to be delivered (@IAG_RAT3.U_Etldis):
Contains the quantity yet to be delivered (overdraft quantity). The quantity to be delivered is calculated as follows: quantity to be delivered (allocation’s overdraft quantity) = Total demands (of the allocation) – CQD – open goods issue.
Display quantity to be delivered (@IAG_RAT3.U_Etldisa):
Contains the quantity to be delivered (display).
Total demands (@IAG_RAT3.U_Wgfefz):
Contains the total demand (continued CQR) from the date of zero position to the allocation’s date. The total demand is calculated as follows: Total demand (of the allocation) = CQR + backorder + immediate requirement + call quantity (of the allocation).
This field not only shows the current scheduling agreement, but also the last one.
Old delivery date (@IAG_RAT3.U_Etldata):
Is the call date of the last scheduling agreement (by comparison with the current scheduling agreement).
Old delivery quantity (@IAG_RAT3.U_Etlmnga):
Contains the call quantity of the last scheduling agreement.
Old delivery demands (@IAG_RAT3.U-Wgfefza):
Contains the total demand of the last scheduling agreement.
Change total demand (@IAG_RAT3.U_Wgfefzd):
Displays the total change until the allocation’s point in time between the old forecast delivery schedule and the current one.
Change (@IAG_RAT3.U_Vraend):
Contains the change at the allocation’s point in time.
Schedule line flag (@IAG_RAT3.U_Etlkz):
Marks the allocation and can have the following characteristics:
| Value | Meaning | Description |
|---|---|---|
| E | normal | A normal alllocation, no specialities |
| F | Production release | for future use |
| M | Material release | for future use |
| V | Preview | for future use |
| R | Backlog | Is created automatically on reading in a forecast deliver schedule if backlog is available and no allocation is set at the boundary date. |
| D | Difference | for future use |
| B | Order confirmation printed | If a partner sales order is employed like an individual order, the allocation is locked once an order confirmation was printed. |
Manipulation flag (@IAG_RAT3.U_Mankz):
This button can freeze an allocation. That means the allocation will not be overwritten by a new EDI. The following characteristics are possible:
| Value | Meaning |
|---|---|
| N | not fixed |
| J | fixed |
Origin flag (@IAG_RAT3.U_hrkkz):
This flag describes the allocation’s origin. The following characteristics are possible:
| Value | Meaning | Description |
|---|---|---|
| O | online | The allocation was edited manually via keyboard entry |
| L | FOR | The allocation hails from an EDI with the business process “forecast delivery schedule”. |
| F | JIT | The allocation hails from an EDI with the business process “JIT delivery schedule”. |
| P | JIS | The allocation hails from an EDI with the business process “JIS delivery schedule”. |
| M | MRP | The allocation hails from the MRP (MRP run, proposal list) |
| V | Packaging | The allocation hails from the PM-creation. |
Planning date (@IAG_RAT3.U_Plndat):
The planning date is the requirement date for the MRP. The planning date is determined through the call date. Planning date (of the allocation) = Call date (of the allocation) + Plus/Minus days production.
Planning quantity (@IAG_RT3.U_Plnmng):
The planning quantity is the requirement quantity for the MRP. The planning quantity equals the call quantity. The planning quantity is calculated as follows: planning quantity (of the allocation) = quantity to be delivered (of the allocation) + open goods issue.
Customer reference number (@IAG_RAT3.U_Refnrk):
Contains a reference number of the customer. If one wants to manage individual purchase orders through the partner sales order, the purchase order number is entered here.
Chassis No. (@IAG_RAT3.U_Frgnr):
The chassis number is an attribute out of a JIS delivery schedule.
Material handlings code (@IAG_RAT3.U_Mhdcod):
Contains the material handlings code, which is usually used by GM’s “MAIS PUS” procedure.
PUS-No (@IAG_RAT3.U_Pusnr):
Contains the “pick up sheet” (PUS) number. This information is usually used by GM’s “MAIS PUS” procedure.
Production No. (@IAG_RAT3.U_Prodnr):
Contains the production number. It is usually transmitted through JIS delivery schedule.
Special specification (@IAG_RAT3.U_Sspfkt):
This field can contain a feature.
Type/Model (@IAG_RAT3.U_Typbm):
The data in this field is usually transmitted through JIS delivery schedule.
Kanban (@IAG_RAT3.U_Kanban):
Contains the Kanban number.
Updating index (IAG_RAT3.U_Aix):
Is the updating index on the allocation layer.
Delivery note (@IAG_RAT3.U_Lsnr):
If the allocation is adduced in a goods issue, the delivery note number is saved.
Delivery note date (@IAG_RAT3.U_Lsdat):
If the allocation is adduced in a goods issue, the delivery note date is saved.
Delivery note quantity (@IAG_RAT3.U_Lsmng):
If the allocation is adduced in a goods issue, the delivery note quantity is saved.
Business prcs. (@IAG_RAT3.U_Dfugpr):
Contains the business partner process of the EDI transmission.
EDI No. int. (@IAG_RAT3.U_Dfunri):
Contains the internal EDI number of the last EDI.
EDI sequence (@IAG_RAT3.U_Dfuseq):
Contains the EDI sequence number of the last EDI.
Item code (@IAG_RAR3.U_Itemcode):
Contains the item ID of the allocation.
Creation user (@IAG_RAT3.U_Anlusr):
Contains the user who created the allocation.
Creation date (@IAG_RAT3.U_Anldat):
Contains the creation date of the allocation.
Creation time (@IAG_RAT3.U_Anlzet):
Contains the creation time of the allocation.
Update user (@IAG_RAT3.U_Updusr):
Contains the user who was the last to edit the allocation.
Update date (@IAG_RAT3.U_Upddat):
Contains the date at which the allocation was last edited.
Update time (@IAG_RAT3.U_Updzet):
Contains the time when the allocation was last edited.
Post your comment on this topic.