SAP ABAP Data Element OB_AJAHR (Year in Which Original Batch was Created)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷
PP-SFC (Application Component) Production Orders
⤷
COWIPB (Package) WIP Batch
SAP_APPL (Software Component) Logistics and Accounting⤷
PP-SFC (Application Component) Production Orders⤷
COWIPB (Package) WIP Batch
Basic Data
| Data Element | 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 of creation field is populated as follows when an original batch is created:
- Original batch for production or process order item: AUFK-ERDAT
- Original batch for PO item: EKKO-BEDAT
The year of creation is kept in the key of these tables so that several orders or POs can be stored there with the same number.
Scenario: An original batch is created for a production order. In the system, the batch where-used list is updated. The production order is then reorganized and then a new one created with the same number. A batch where-used list is still possible for the original batch because the entries in the tables CHVW and PROOB are retained.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 604 |
