SAP ABAP Data Element MILL_MM_OB_AJAHR (Year in Which Original Batch was Created)
Hierarchy
☛
ECC-DIMP (Software Component) DIMP
⤷
IS-MP-MM (Application Component) Materials Management (MM) enhancements
⤷
MILL_MM (Package) IS: Mill Products - Materials Management
ECC-DIMP (Software Component) DIMP⤷
IS-MP-MM (Application Component) Materials Management (MM) enhancements⤷
MILL_MM (Package) IS: Mill Products - Materials Management
Basic Data
| Data Element | MILL_MM_OB_AJAHR |
| Short Description | Year in Which Original Batch was Created |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | GJAHR | |
| Data Type | NUMC | Character string with only digits |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Year |
| Medium | 15 | Year |
| Long | 20 | Year |
| Heading | 4 | Year |
Documentation
Definition
The year is filled as follows when you create an original batch:
- Original batch for production or process order item: AUFK-ERDAT
- Original batch for purchase order item: EKKO-BEDAT
The creation year is in the key for these tables, so that a number of orders or purchase orders can be stored with the same number.
Scenario: An original batch is being created for the production order. The system updates the batch where-used list. The production order is then reorganized and a new order is created with the same number. However, a batch where-used list is still possible for the original batch, because the entries in tables CHVW and PROOB remain in place.
History
| Last changed by/on | SAP | 20050301 |
| SAP Release Created in |
