The last active scheduling agreement ist displayed in the tab “Demands”. The scheduling agreement is taken from the MRP or entered manually.
Each row is an allocation in the scheduling agreement (call date, call time, call quantity).
The graphical display of a scheduling agreement:
Three scheduling agreements are displayed in the tab “Demands”:
- MRP plan. A scheduling agreement taken one-to-one out of the MRP.
- ATM plan. This is an altered MRP plan. The MRP date is altered by the value of “Plus/Minus days production” and the MRP quantity is rounded to a “Multiple”.
- Delivery plan. This is the ATM plan at the time when the feature Create history is executed.
The MRP plan is represented by the following four colums:
MRP date (@IAG_PBS3.U_Mrpdat):
Contains the requirement date from the MRP.
MRP time (@IAG_PBS3.U_Mrpzet):
Contains the requirement time from the MRP.
MRP quantity (@IAG_PBS3.U_Mrpmng):
Contains the requirement from the MRP.
MRP-RCQ (@IAG_PBS3.U_Mrpefz):
Contains the total requirement from the date of zero position to the MRP date. The total requirement is calculated as follows:
Total requirement (of the allocation)(PBS3.U_Mrpefz) = “Cumulated Received Quantity(PBS0.U_Efz)” + “MRP residue(PBS0.U_Mrprst)” + “MRP instant stock(PBS0.U_Mrpsst)” + “MRP quantity(of the allocation)(PBS3.U_Mrpmng)”.
The ATM plan is represented by the following five colums:
ATM date (@IAG_PBS3.U_Atmdat):
Contains the “MRP date” altered by the value of “Plus/Minus days production”(PBS0.U_Pmtprd).
Here an example with the "Plus/Minus days production" = 5.
ATM time (@IAG_PBS3.U_Atmzet):
Inherits the value of “MRP time”.
ATM quantity (@IAG_PBS3.U_Atmmng):
Contains the “MRP quantity” which is rounded up to a “Delivery multiples”(PBS0.U_Lifvlf).
Here an example with the "Delivery multiples" = 30.
ATM-RCQ (@IAG_PBS3.U_Atmefz):
Contains the total requirement from the date of zero position to the boundary date. It is calculated through the feature “Calculate Cumulative Quantities” as follows:
ATM-RCQ (PBS3.U_Atmefz) = “Cumulated Received Quantity(PBS0.U_Efz)” + “ATM residue(PBS0.U_Atmrst)” + “ATM instant stock(PBS0.U_Atmsst)” + “ATM requirement(PBS3.U_Atmmng)”.
Quantity to be delivered (@IAG_PBS3.U_Etldis):
Contains the total quantity still to be delivered from the date of zero position until the “ATM date”. It is determined through the feature Calculate Cumulative Quantities as follows:
Quantity to be delivered(PBS3.U_Etldis) = “ATM-RCQ (PBS3.U_Atmefz)” – “Cumulated Goods Receipt Quantity(PBS0.U_Vfz)” – “open goods received(PBS0.U_Ofnwe)”.
The scheduling agreement at the supplier's is represented by the following five colums:
Supplier date (@IAG_PBS3.U_Lifdat):
Contains the “ATM date” at the time of executing the feature Create history.
Supplier time (@IAG_PBS3.U_Lifzet):
Contains the “ATM time” at the time of executing the feature Create history.
Supplier quantity (@IAG_PBS3.U_Lifmng):
Contains the “ATM quantity” at the time of executing the feature Create history.
Supplier RCQ (@IAG_PBS3.U_Lifefz):
Contains the total requirement from the date of zero position to the point when executing the feature Create history. This value is calculated through the feature Create history as follows:
Supplier RCQ (PBS3.U_Lifefz) = “Cumulated Supplier Quantity(PBS0.U_Lfz)” + “Delivery residue(PBS0.U_Lifrst)” + “Delivery instant stock(PBS0.U_Lifsst)” + “Supplier quantity(PBS3.U_Lifmng)”.
Supplier for quantity to be delivered (@IAG_PBS3.U_Lidis):
Contains the still to be delivered total quantity from the date of zero position to the “Supplier date”. Is determined through the feature “Calculate Cumulative Quantities” as follows:
Supplier for quantity to be delivered(PBS3.U_Lidis) = “Supplier RCQ (PBS3.U_Lifefz)” – “Cumulated Goods Receipt Quantity(PBS0.U_Vfz)” – “open goods received(PBS0.U_Ofnwe)”.
Change RCQ (@IAG_PBS3.U_Wgfefzd):
Contains the total change between the current “ATM plan” and the scheduling agreement transmitted lasty to the supplier. Is determined through the feature “Calculate Cumulative Quantities” as follows:
Change RCQ (PBS3.U_Wgfefzd) = “ATM-RCQ (PBS3.U-Atmefz) – “Supplier RCQ (PBS3.U_Lifefz)”.
Update (@IAG_PBS3.U_Vraend):
Contains the changes/updates between two allocations. Is determined through the feature “Calculate Cumulative Quantities” as follows:
Update(PBS3.U_Vraend)(n) = “Change RCQ (PBS3.U_Wgfefzd)(n-1)” – “Change RCQ (PBS3.U_Wgfefzd)(n)”
Here an example of the mechanics
Schedule line flag (@IAG_PBS3.U_Etlkz):
Marks the allocation and the following characteristics are possible:
| Value | Meaning | Description |
|---|---|---|
| E | normal | A normal allocation, no specialities |
| F | Production release | for future use |
| M | Material release | for future use |
| V | Preview | for future use |
| R | Backlog | Is created automatically when reading a forecast delivery schedule if backlog is available and no allocation is present at the time of the boundary date |
| D | Difference | for future use |
| B | Order confirmation printed | If a partner order is used as an individual order, the allocation is locked when an order confirmation is printed |
Manipulation flag (@IAG_PBS3.U_Mankz):
This button can freeze an allocation. This implies that in case of another EDI, this particular allocation will not be overwritten.
| Value | Meaning |
|---|---|
| N | not fixed |
| J | fixed |
Origin flag (@IAG_PBS3.U_Hrkkz):
This indicator (flag) describes the origin of the allocation. The following characteristics are possible:
| Value | Meaning | Description |
|---|---|---|
| L | LAB – Forecast | The allocation originates in an EDI with the business process “Forecast delivery schedule” |
| F | FAB – Just-In-Time | The allocation originates in an EDI with the business process “JIT delivery schedule |
| P | PAB – Just-In-Sequence | The allocation originates in an EDI with the business process “JIS delivery schedule” |
| O | online | The allocation was edited manually via keyboard |
| M | MRP | Is created automatically when reading a forecast delivery schedule if backlog is available and no allocation is present at the time of the boundary date |
| V | Packaging | for future use |
Supplier reference No. (@IAG_PBS3.U_Refnrk):
Contains a supplier’s reference number.
Chassis No. (@IAG_PBS3.U_Frgnr):
The chassis number is a characteristic from the JIS delivery schedule.
Material handlings code (@IAG_PBS3.U_Mhdcod):
Contains the “Material handlings code” which is inherently used by GM’s “MAIS PUS” procedure.
Kanban (@IAG_PBS3.U_Kanban):
Contains the Kanban number.
PUS-Number (@IAG_PBS3.U_Pusnr):
Contains the PUS (pick up sheet) number. This information is inherently used by GM’s “MAIS PUS” procedure.
Updating index (@IAG_PBS3.U_Aix):
Is the updating index on the allocation level.
GR (@IAG_PBS3.U_Lsnr):
If the allocation is used in a goods receipt (GR), the goods receipt number is then saved.
GR date (@IAG_PBS3.U_Lsdat):
If the allocation is used in a goods receipt (GR), the goods receipt date is then saved.
GR quantity (@IAG_PBS3.U_Lsmng):
If the allocation is used in a goods receipt (GR), the goods receipt quantity is then saved.
Business process (@IAG_PBS3.U_Dfugpr):
Contains the business process of the EDI transmission.
EDI number int. (@IAG_PBS3.U_Dfunri):
Contains the internal EDI number of the last EDI.
EDI sequence (@IAG_PBS3.U_Dfuseq):
Contains the EDI sequence number of the last EDI.
Item ID (@IAG_PBS3.U_Itemcode):
Contains the item ID from the allocation.
Creation User (@IAG_PBS3.U_Anlusr):
Contains the user who created the allocation.
Creation Date (@IAG_PBS3.U_Anldat):
Contains the creation date of the allocation.
Creation Time (@IAG_PBS3.U_Anlzet):
Contains the creation time of the allocation.
Update User (@IAG_PBS3.U_Updusr):
Contains the user who was the last to edit the allocation.
Update Date (@IAG_PBS3.U_Upddat):
Contains the date at which the allocation was last edited.
Update Time (@IAG_PBS3.U_Updzet):
Contains the time when the allocation was last edited.
Post your comment on this topic.