SAP table CKMLCOCKPITSTATE (User Data for Actual Costing Costing Run)
SAP table CKMLCOCKPITSTATE has 3 primary key fields being MANDT,APPLICATION,KALUSER.
If you're only analyzing data from a single SAP instance you may omit field MANT in your relationships as it will we the same across the entire dataset. On the other hand, if you're combining data from multiple SAP instances you need to take MANDT into account.
| Field | Description | Data Type | Length | Decimals | Checktable | Data Element | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| MANDT | Client | CLNT | 3 | 0 | T000 | MANDT | |||||||||||||||
| APPLICATION | Material Ledger Costing Run Application | CHAR | 4 | 0 | CKML_RUN_APPL |
|
|||||||||||||||
| KALUSER | User Name | CHAR | 12 | 0 | SYUNAME | ||||||||||||||||
| RUN_ID | Number of Costing Runs for Material Ledger | NUMC | 12 | 0 | * | CKML_RUN_ID | |||||||||||||||
| DISPLAY | Status of Transaction | CHAR | 1 | 0 | CK_DISPLAY | ||||||||||||||||
| COMSTATE | Subscreen Status | CHAR | 1 | 0 | CK_VISIBLE | ||||||||||||||||
| PROCSTATE | Subscreen Status | CHAR | 1 | 0 | CK_VISIBLE | ||||||||||||||||
| RESSTATE | Subscreen Status | CHAR | 1 | 0 | CK_VISIBLE | ||||||||||||||||
| RESSIZE | Size of Costing Results Report | CHAR | 1 | 0 | CK_SIZE | ||||||||||||||||
| DISP_MODE | CHAR | 1 | 0 | ||||||||||||||||||
| MAT_FILTER | Filter for Restriction on Materials List | NUMC | 2 | 0 | CKML_MATSELID |
|
|||||||||||||||
| HIERARCHY_TYPE | Hierarchy for Displaying Costing Run Results | NUMC | 4 | 0 | CKML_FILTER_ID |
|
|||||||||||||||
| SASH_POS | INT1 | 3 | 0 | ||||||||||||||||||
| MAX_NR_MATERIALS | INT4 | 10 | 0 | ||||||||||||||||||
| RES_VIEW | View for the Display of Costing Results | CHAR | 1 | 0 | CKML_SICHT_ID |
CKMLCOCKPITSTATE foreign key relationships
| Table | Field | Check Table | Check Field | |
|---|---|---|---|---|
| 0 CKMLCOCKPITSTATE | MANDT | T000 | Clients | MANDT |