Generally there are scheduling agreements in the position data. You can reach the “position data” via right click on a position in the “history” and select ‘Position data’):
All the data in the “position” is grouped as follows:
- Head data
- Tabs
Head data
Foreign item code (@IAG_HSV3.U_Fsn):
Contains the customer’s item code which is also called foreign item code (FIC). Since leading whitespaces are not saved in B1, a “~” is automatically put in front of the number as soon as it begins with a whitespace. Item codes with whitespaces are mainly used by the VW group.
Customer factory (@IAG_HSV3.U_Wrk):
Contains the customer’s factory.
Unloading point (@IAG_HSV3.U_Abl):
Contains the customer’s unloading point.
Order No. (@IAG_HSV3.U_ABS):
Contains the contract number which underlies the partner sales order. This number is usually assigned by the customer.
Change index (@IAG_HSV3.U_Aix):
Contains the customer’s change index.
Status (@IAG_HSV3.U_Hsvsts):
Contains the processing status of a position. These characteristics are possible:
| Value | Meaning | Description |
|---|---|---|
| 1 | created | The position was not processed any further. |
| 2 | Transfer failed | The position was not inherited properly. This status is only assigned to the business processes LSR (delivery note transport data received) and GUT (credit note). |
| 9 | done | The position was processed successfully. |
Cumulative received quantity (@IAG_HSV3.U_EFZ):
Contains the customer’s cumulative quantity received (CQR). This is the sum of all the customer’s engrossed deliveries in the period between the date of zero position and the boundary date.
Residue (@IAG_HSV3.U_Rst):
Contains the customer’s residue quantity. In theorie, the residue quantity should have been transmitted to the supplier once before. Not being assigned to any date (like an allocation), it should be satisfied as fast as possible.
Instant stock (@IAG_HSV3.U_Sst):
Contains the customer’s instant stock (immediate requirement). In theorie, the instant stock is a new requirement of the customer. Not being assigned to any date (like an allocation), it should be satisfied as fast as possible.
Limiting date (@IAG_HSV3.U_Agrdat):
Contains the “date of the last delivery”. It is also called “boundary date”, because this date separates past and present in this scheduling agreement. Basically the allocations of the scheduling agreement lie in the future. The past is represented via the residue quantity.
Post your comment on this topic.