Record Types 
The following record types are used:
Record type |
Function |
Remark |
K10 |
Kanban impulse |
Status change of kanban container |
K20 |
Quantity impulse |
Debit quantity from kanban container |
The following fields must be filled, when confirmations are transferred to structure conf51 :
Record type |
Fields to be filled (see "Data structures in CC5") |
Required fields |
Optionalfields |
K10 |
SATZA, TERID, LDATE, LTIME, ERDAT, ERTIM, PKKEY, PKBST, PKNUM, PKPOS, PKIMG |
X X |
X |
K20 |
SATZA, TERID, LDATE, LTIME, ERDAT, ERTIM, PKNUM, ABMNG |
X X |
The record type is filled through the selection of an entry transaction or through the entry of an identifier.
The kanban impulse (K10) can be encrypted in 11-digit bar code that features the following structure:
Position 1-7 |
= PKKEY |
Position 11 |
= PKBST |
The quantity impulse (K20) can be encrypted in an 8-digit bar code that features the following structure:
Position 1-7 |
= PKNUM |
Position 8 |
= ABMNG |
Fields in CC5
Field name |
Description |
Content is checked for |
SATZA |
Record type of confirmation |
Valid record type |
TERID |
Terminal ID |
Valid terminal ID |
LDATE |
Actual date of confirmation |
Valid date |
LTIME |
Actual time of confirmation |
Valid time |
ERDAT |
Entry date of confirmation |
Valid date |
ERTIM |
Entry time of confirmation |
Valid time |
PKKEY* |
Kanban ident. number |
Against pkps5 |
PKNUM** |
Control cycle number |
Against pkhd5 |
PKPOS |
Container number |
PKNUM, PKPOS against pkps5 |
PKBST |
Target status |
PKSFG***, PKBST against pkst5 |
PKIMG |
Actual quality |
Numeric value |
ABMNG |
Debited quantity |
Numeric value |
* If you make manual entries, you should use the PKNUM field (or the MATNR field, the WERKS field, and the PRVBE field, see also definition of the PKNUM field) and the PKPOS field (secondary key), rather than the PKKEY field (primary key). The pkPS5 data structure is then used to determine the value with which the PKKEY field is filled.
** If you want to make manual entries in the PKNUM field (primary key), it is advisable to fill the MATNR field, the WERKS field, and the PRVBE field (secondary key) instead. You can then use pkhd5 data structure to determine the value for the PKNUM field.
*** As a rule, the value of the PSKFG field is a blank when checking the value of the PKBST field in the pkst5 table. In this case, the system checks for existence of the entry pkst5-pksfg= blank, pkst5-pkbst=pkbst .
The system fills the TERID field, the LDATE field, the LTIME field, the ERDAT field, and the ERTIM field in the background.