SAP table RMUSER (User Settings for REM Backflush Transactions)
SAP table RMUSER has 3 primary key fields being MANDT,UNAME,TCODE.
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 | MANDT | ||
| UNAME | User Name | CHAR | 12 | 0 | SYUNAME | ||
| TCODE | Transaction Code | CHAR | 20 | 0 | SYTCODE | ||
| WERKS | Plant | CHAR | 4 | 0 | WERKS_D | ||
| ALORT | Receiving storage location for repetitive manufacturing | CHAR | 4 | 0 | ALORT | ||
| VERID | Production Version | CHAR | 4 | 0 | VERID | ||
| KDAUF | Sales Order Number | CHAR | 10 | 0 | KDAUF | ||
| KDPOS | Item number in Sales Order | NUMC | 6 | 0 | KDPOS | ||
| FTYPS | Selection of production type: make-to-stock production | CHAR | 1 | 0 | SA_FTYPS | ||
| FTYPM | Selection of production type: make-to-order production | CHAR | 1 | 0 | SA_FTYPM | ||
| PLNUM | Planned Order | CHAR | 10 | 0 | PLNUM | ||
| RADIOKDE | Radio button: 'Process: make-to-order production' | CHAR | 1 | 0 | VHURM_RBKDE | ||
| RADIOLAG | Radio button 'Process: make-to-stock production' | CHAR | 1 | 0 | VHURM_RBLAG | ||
| AGGRE | Aggregate the HUs as far as possible before GR | CHAR | 1 | 0 | VHURM_AGGRE | ||
| MDV01 | Production line | CHAR | 8 | 0 | MDV01 | ||
| MDV02 | Planning identification 2 | CHAR | 8 | 0 | MDV02 |