SAP ABAP Data Element OIG_LDDATE (Loading Date)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ OIG (Package) TD Transport and Distribution
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
OIG (Package) TD Transport and Distribution
Basic Data
| Data Element | OIG_LDDATE |
| Short Description | Loading Date |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DATUM | |
| Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | Load. Date |
| Medium | 15 | Loading Date |
| Long | 20 | Loading Date |
| Heading | 8 | LoadDate |
Documentation
Definition
Date at which the actual loading takes place and which is used when entering the document in Financial Accounting or Controlling.
Use
The fiscal year and the period for which an update of the accounts specified in the document or cost elements is made, are derived from theposting date.
When entering documents, the system checks whether the posting date entered is allowed by means of the posting period permitted.
Note
The posting date can differ from both the entry date (day of entry into the system) and the document date (day of creation of the original document).
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
