|
Functionality
In this method a kanban status change is carried out. With such astatus change replenishment is triggered for a kanban or goods receiptis posted for a kanban.
The main entry parameter is the kanban identification number. Thestatus to which the kanban is to be set, can be provided or determinedby the system. The kanban ID number and status can be encoded in abarcode and determined this way.
COMMIT and ROLLBACK WORK: the function module does not carry out anyCOMMIT work. Command off. The initiator must make sure of this afterending the function module. Each time after the FM is called up, aCOMMIT WORK must take place. It is not permissible to call up this FMseveral times and to post the result with a COMMIT WORK. If the FMfinds an error during processing, then in some cases the commandROLLBACK WORK is executed. In these cases the kanban is either set tostatus ERROR or an error message is issued in the parameter RETURN. Description
Error message, if the status change could not be posted. Depending onwhich functions are being used during the kanban status change, avariety of errors could occur:
Possible error messages are, for example: Value range
Please enter the kanban ID number
Kanban data locked by user <(>&<)>
Data could not be locked (system error)
Unit of measure transferred does not match unit of measure in controlcycle
No authorization for triggering kanban signals in plant
Kanban has an error! Signal not possible.
Status <(>&<)> is not allowed in status sequence <(>&<)>
Obligatory status <(>&<)> from status sequence <(>&<)> cannot beskipped
Status IN USE cannot be skipped
Status IN USE cannot be skipped
With GI to cost center, GR must be posted to the kanban first.
Kanban is locked. Replenishment is not triggered.
Kanban cannot be set from status <(>&<)> to WAIT
Kanban cannot be set from status <(>&<)> to EMPTY
Kanban cannot be set from status <(>&<)> to IN PROCESS
Kanban cannot be set from status <(>&<)> to IN TRANSIT
Kanban cannot be set from status <(>&<)> to FULL
Kanban cannot be set from status <(>&<)> to IN USE
Status can only be changed after the <(>&<)> <(>&<)>
GR for full kanban has not yet occurred Description
This quantity only has to be specified if a goods recipt also takesplace with the kanban status change. Goods receipt then takes placewith the quantity specified instead of the target quantity of thekanban.
The unit of measure does not have to be specified. It is automaticallytransferred from the control cycle. If it is specified anyway, then itmust match the unit of measure in the control cycle. Description
If good receipt takes place with the kanban status change, if thematerial requires batch management and if the batch number is notdetermined internally by the system, then the batch must be specified. Description
With this key the kanban is created in the system. Description
Most of the functions in KANBAN take place with the status change of akanban. The next status, to which a kanban is to be set, can beprovided from outside or can also be determined from the system. Description
If the status change for the kanban is not posted straight away butlater, then here you can enter the actual time at which the statuschange took place. The times in the kanban and in the KANBAN LogisticsInformation System are then updated as if the status change had beenposted synchronously. Description
For every kanban whose status can be changed, a record is made in thislist. This contains the following data: kanban and control cycle, thenew status, the replenishment element, if one has been created, thematerial document, if one has been created, the error message, if thekanban has been set to ERROR.
Ususally only one record is made here. With special settings in thecontrol cycle it is possible, however, that a second kanban in thestatus is changed. |