Hierarchy
⤷ FI-LOC (Application Component) Localization
⤷ GLO_REFX_NL_DDIC (Package) Localization Flexible Real Estate Netherlands
Basic Data
Data Element | REXCNLAJSTATUS |
Short Description | Status |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DDTEXT | |
Data Type | CHAR | Character String |
Length | 60 | |
Decimal Places | 0 | |
Output Length | 60 | |
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 | Status |
Medium | 15 | Status |
Long | 20 | Status |
Heading | 10 | Status |
Documentation
Definition
Shows the status of an adjustment record.
Use
The adjustment record can have any of the following statuses:
- No Errors in Calculation (0)
The adjustment run for determining the adjustment was executed without errors. You can activate the adjustment. - Errors in Calculation (1)
This status can only occur when the system is determining the adjustment during the adjustment run. Adjustments with this status are not saved.
- Warnings Exist for Calculation (2)
During the adjustment run for determining the adjustment, problems occurred that do not prevent the adjustment from being activated.
- Adjustment Complete (3)
This status is set when an adjustment without errors or an adjustment with warnings is activated.
- Adjustment Reversed (4)
The adjustment was reversed.
- Adjustment Locked (5)
This status can only occur for adjustments during the simulation. Adjustments that are locked are excluded from further processing. This status occurs due to one of the following: A manual change was made to the condition being adjusted ( valid from, unit price); The condition being adjusted was deleted; There is a more recent adjustment.
- Adjustment Invalid (6)
The adjustment is declared invalid because the context for the adjustment has changed. This can occur, for example, if the definition of costs for an adjustment measure changes. The system performs an update the next time the adjustment is processed.
- No Adjustment Exists (7)
There is no adjustment.
- Status Cannot Be Determined (not defined)
The system sets this status if the adjustment history is displayed and the adjustment it belongs to is still in simulation mode. To improve performance, the system does not determine the actual status. If you want to determine the correct status, then change to the adjustment view.
Dependencies
Example
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 605 |