Archive

The scheduling agreements are saved in the tab “archive” exactly as they were transmitted. The week and month appointments are not converted to calendar days.

Call date from (@IAG_HSV4.U_Etldtv):
Contains the date from which the requirements are valid.

Call time (@IAG_HSV4.U_Etlzet):
Contains the time to which the requirement is needed. Is generally transmitted via JIT – or JIS delivery schedule. If no time is transmitted, “4 p.m.” is entered by default.

Call to (@IAG_HSV4.U_Etldtb):
Contains the end date for the valid time period of the requirement. Is generally transmitted via EDIFACT standards.

Call quantity (@IAG_HSV4.U_Etlmng):
Contains the requirement for the stated time period.

Date flag (@IAG_HSV4.U_Datkz):
Contains a mark (flag) which defines the requirement period. The following characteristics are possible:

Customer reference No. (@IAG_HSV4.U_Refnrk):
Contains the customer’s reference number at requirement level.

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

Material handling code (@IAG_HSV4.U_Mhdcod):
Contains the “material handling code” at requirement level. This information is usually used by the GM corporation.

Kanban (@IAG_HSV4.U_Kanban):
Contains the KANBAN number at requirement level. This information is usually used by the GM corporation.

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

Creation date (@IAG_HSV4.U_Anldat):
Contains the creation date of the requirement.

Creation time (@IAG_HSV4.U_Anlzet):
Contains the creation time of the requirement.

Update user (@IAG_HSV4.U_Updusr):
Contains the user who was the last to process the requirement.

Update date (@IAG_HSV4.U_Upddat):
Contains the date when the requirement was last processed.

Update time (@IAG_HSV4.U_Updzet):
Contains the time when the requirement was last processed.