Divisions

In the tab “divisions” the scheduling agreement from the archive is converted to a scheduling agreement with precise dates.
The week indication is terminated to the first day of the week.
There are two conversion methods for the indications from-week / to-week:

1. For every week in the time period from-week / to-week an allocation is created with the appointment of the week’s monday with the same quantity.
2. For the time period from-week / to-week the quantity is put to the monday of the first week.

The setting of which conversion routine is active, can be adjusted in the business partner master data among the tab ATM Info with the button “LAB Wo von-bis einmalig”

The monthly divisions out of the archive are saved as a allocation to the first of the month.

In addition the weekly / monthly requirements can be divided as follows:

• per day
• per week

In which way the requirements are divided, can be defined in the business partner master data among the tab ATM Info with the button “Teilung Bedarfe”.

The scheduling agreement with precise date indications is saved in the tab “divisions”. The thus saved scheduling agreement is saved as a scheduling agreement to the partner sales order with the feature processing

Call date (@IAG_HSV5.U_Etldat):
Contains the calculated division date (as mentioned above).

Call time (@IAG_HSV5.U_Etlzet):
Contains the time of the division. The indication of time is generally transmitted via the business processes JIS or JIT delivery schedule. If no time is transmitted, the default value (4 p.m.) is entered. If there are more than one allocations transmitted for a single date, the time indication is increased by one second.

Call quantity (@IAG_HSV5.U_Etlmng):
Contains the requirement of the allocation.

Total demand (@IAG_HSV5.U_Wgfefz):
Contains the total demand from the “date of zero position” until the division date.

Date flag (@IAG_HSV5.U_Datkz):
Contains a mark (flag) which highlights the origin of the allocation. The following characteristics are possible:

Production No. (@IAG_HSV5.U_Prodnr):
Contains the production number. This information is generally transmitted via the business process JIS delivery schedule.

Customer reference No. (@IAG_HSV5.U_Refnrk):
Contains the customer’s reference number. This information is generally transmitted via the business process JIS delivery schedule.

Chassis No. (@IAG_HSV5.U_Frgnr):
Contains the chassis number. This information is generally transmitted via the business process JIS delivery schedule.

Material handling code (@IAG_HSV5):
Contains the “material handling code” which the customer transmitts. This information is mainly transmitted by the GM corporation.

Kanban (@IAG_HSV5.U_Kanban):
Contains the KANBAN number or a supplementary item code number which the customer transmitts. This information is mainly transmitted by the GM corporation.

Change index (@IAG_HSV5.U_Aix):
Contains the change index at the allocation level. The change index at the allocation level is generally not used.

Change flag (@IAG_HSV5.U_Aenkz):

Special specification (@IAG_HSV5.U_Sspkt):
Contains a specification of the customer. This information is generally transmitted via the business process JIS delivery schedule.

Type/Design (@IAG_HSV5.U_Typbm):
Contains type or design information. This information is generally transmitted via the business process JIS delivery schedule.

Creation user (@IAG_HSV5.U_Anlusr):
Contains the user who processed the transmission.

Creation date (@IAG_HSV5.U_Anldat):
Contains the creation date of the allocation.

Creation time (@IAG_HSV5.U_Anlzet):
Contains the creation time of the allocation.

Update user (@IAG_HSV5.U_Updusr):
Contains the user who was the last to process the allocation.

Update date (@IAG_HSV5.U_Upddat):
Contains the date when the allocation was last processed.

Update time (@IAG_HSV5.U_Updzet):
Contains the time when the allocation was last processed.