The tab “Demands” of the superior partner sales order always represents the latest, active scheduling agreement. The scheduling agreement can be transmitted via EDI or entered manually.
Every row is an entry in the scheduling agreement (Call date, call time, call quantity).
A graphic display of a scheduling agreement:
The forecast delivery schedule (scheduling agreement) is represented by the following columns:
Call date (@IAG_RAT3.U_Etldat):
Date of delivery at customer
Call time (@IAG_RAT3.U_Etlzet):
Delivery time at customer. Tranmitted only through JIT delivery schedule (FAB) or JIS calls (PAB).
Call quantity (@IAG_RAT3.U_Etlmng):
The requirement quantity by the call date.
A graphic display of a scheduling agreement with two cumulative quantitys (CQ-recieved, CQ-delivery):
The cumulated quantity recieved by the customer (CQR) is the sum of the engrossed delivery 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 the current date. The addition of the CQR to the respective call quantity results in the “total demand” from the point of zero position and the allocation’s call date. If you subtract the CQD from the “total demand”, the result will be the yet to be delivered quantity (plannable quantity) for the respective allocation.
Quantity to be delivered (@IAG_RAT3.U_Etldis):
The yet to be delivered quantity (dispo-quantity). The quantity to be delivered is calculated like this: Quantity to be delivered (dispo-quantity) = Total demand (of the allocation) – CQD – open goods issue.
Display quantity to be delivered (@IAG_RAT3.U_Etldisa):
The yet to be delivered quantity (display).
Total demands (@IAG_RAT3.U_Wgfefz):
The total demand (continued CRQ) since date of zero position until date of allocation. The total demands is calculated as follows: Total demands (of allocation) = CRQ + backlog + immediate requirements + call quantity (of allocation).
Not only the current, but also the last scheduling agreement is shown.
Old delivery date (@IAG_RAT3.U_Etldata):
The delivery date of the last scheduling agreement (in comparison to the current scheduling agreement).
Old delivery quantity (@IAG_RAT3.U_Etlmnga):
The delivery quantity of the last scheduling agreement.
Old total demands (@IAG_RAT3.U-Wgfefza):
The total demands of the last scheduling agreement.
Update total demands (@IAG_RAT3.U_Wgefzd):
Contains the overall change in demand until the point of classification between the last and current scheduling agreement.
Update (@IAG_RAT3.U_Vraend):
The change at the time of the classification.
Schedule line flag (@IAG_RAT3.U_Etlkz):
Marks the classification und can have the following characteristics:
| Wert | Bedeutung | Beschreibung |
|---|---|---|
| E | normale Einteilung | A normal allocation, no features |
| F | Fertigungsfreigabe | for future use |
| M | Materialfreigabe | for future use |
| V | Vorschau | for future use |
| R | Rückstandseinteilung | Will automatically be created while importing a LAB, if backorder is available and no allocation is availabe at the boundary date |
| D | Differenzeinteilung | for future use |
| A | Auftragsbestätigung gedruckt | If a partner sales order is used as a induvidual purchase order, the allocation will be locked, if at the same time a order confirmation was printed |
Manipulation flag (@IAG_RAT3.U_Mankz):
This button can freeze an allocation. If a new EDI is transmitted, this allocation will hence not be overwritten. The following characteristics are possible:
| Value | Meaning |
|---|---|
| N | no freezing |
| J | freezing |
Origin flag (@IAG_RAT3.U_hrkkz):
This flag describes the allocation’s origin. The following characteristics are possible:
| Wert | Bedeutung | Beschreibung |
|---|---|---|
| L | LAB | The allocation comes from an EDI with the business process “forecast delivery schedule” |
| F | FAB | The allocation comes from an EDI with the business process “JIT delivery schedule” |
| P | PAB | The allocation comes from an EDI with the business process “JIS delivery schedule” |
| O | online | The allocation was manipulated manually via keyboard entry |
| M | MRP | The allocation comes from MRP |
| V | Verpackung | The allocation comes from Packaging-generation |
Planning date (@IAG_RAT3.U_Plndat):
The planning date is the requirement date for the MRP. The planning date is calculated via the call date: Planning date (of allocation) = call date (of allocation) + plus-minus-days production
Planning quantity (@IAG_RT3.U_Plnmng):
The planning quantity is the requirement quantity. The planning quantity equals the call quantity. The planning quantity is calculated as follows: Planning quantity (of allocation) = quantity to be delivered (of allocation) + open goods issue.
Customer reference number (@IAG_RAT3.U_Refnrk):
The reference number of the customer. If you want to administrate the individual purchase order via the partner sales order, insert the customer’s order number here.
Chassis No. (@IAG_RAT3.U_Frgnr):
The chassis number is a characteristic out of the PAB.
Material handlings code (@IAG_RAT3.U_Mhdcod):
Contains the material handlings code, which is generally used by the “MAIS PUS” procedure by GM.
PUS-No (@IAG_RAT3.U_Pusnr):
Contains the “pick up shit” (PUS)-number. This information is generally used by the “MAIS PUS” procedure by GM.
p(bannner tip). If this field is filled, a distinct goods issue has to be created for every PUS-No.
Production No. (@IAG_RAT3.U_Prodnr):
Contains the production number. Generally transmitted with the PAB.
Special specification (@IAG_RAT3.U_Sspfkt):
Can contain a special feature.
Type/Model (@IAG_RAT3.U_Typbm):
Generally transmitted by PAB.
Kanban (@IAG_RAT3.U_Kanban):
Contains the kanban number.
Updating index (IAG_RAT3.U_Aix):
The updating index on the level of the allocation.
Delivery note (@IAG_RAT3.U_Lsnr):
If the allocation is used in a goods issue, the delivery note number is saved.
Delivery note date (@IAG_RAT3.U_Lsdat):
If the allocation is used in a goods issue, the delivery note date is saved.
Delivery note quantity (@IAG_RAT3.U_Lsmng):
If the allocation is used 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 of the last EDI.
Item code (@IAG_RAR3.U_Itemcode):
Contains the allocation’s article-ID.
Creation User (@IAG_RAT3.U_Anlusr):
Contains the user who created the allocation.
Creation date (@IAG_RAT3.U_Anldat):
Contains the allocation’s creation date.
Creation time (@IAG_RAT3.U_Anlzet):
Contains the allocation’s creation time.
Update user (@IAG_RAT3.U_Updusr):
Contains the user who was the last to manipulate the allocation.
Update date (@IAG_RAT3.U_Upddat):
Contains the date at which the allocation was last manipulated.
Update time (@IAG_RAT3.U_Updzet):
Contains the time at which the allocation was last manipulated.
VisOrder
Post your comment on this topic.