SAP ABAP Data Element REAJXADJMDRECORDSTAT (Name of Status of an Adjustment Record)
Hierarchy
EA-FIN (Software Component) EA-FIN
   RE-FX-AJ (Application Component) Rent Adjustment
     RE_AJ_PR (Package) RE: Adjustment Process
Basic Data
Data Element REAJXADJMDRECORDSTAT
Short Description Name of Status of an Adjustment Record  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type REAJXADJMDRECORDSTAT    
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 Stat.Name 
Medium 15 Status Name 
Long 20 Status Name 
Heading StNm 
Documentation

Definition

Shows the status of an adjustment record:

@5B@ No Errors in Calculation (0)
The adjustment run for determining the adjustment was executed without errors. You can activate the adjustment.

@5C@ 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.

@5D@ Warnings Exist for Calculation (2)
During the adjustment run for determining the adjustment, problems occurred that do not prevent the adjustment from being activated.

@DF@ Adjustment Complete (3)
This status is set when an adjustment without errors (@5B@) or an adjustment with warnings (@5D@) is activated.

@B6@ Adjustment Reversed (4)
The adjustment was reversed.

@AG@ 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.

@F1@ 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.

@BZ@ No Adjustment Exists (7)
There is no adjustment.

@8Q@ 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.

Use

Dependencies

Example

History
Last changed by/on SAP  20100310 
SAP Release Created in 200