Hierarchy
⤷ SCM-BAS (Application Component) SCM Basis
⤷ CIF (Package) Core Interface
Basic Data
Data Element | CIFERRSTAT |
Short Description | Error Status of a Postprocessing Record |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CIFERRSTAT | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | Err. Stat. |
Medium | 15 | Error Status |
Long | 34 | Error Status |
Heading | 41 | Error Status of a Postprocessing Record |
Documentation
Definition
In CIF error handling, the system marks all generated postprocessing records with an error status.
Use
If CIF error handling is active, no data is posted to the target system when there are errors in the data transfer using the APO Core Interface (CIF). To retransfer the data that was not posted from the source system, postprocessing records are created in the target system. The error status in the postprocessing record details whether the object that was not posted to the target system was processed at all:
- 1 No Errors
The object was processed and errors did not occur. It is expected that this object can be retransferred without errors.
- 2 Errors
The object was processed and an error occurred. It is expected that a retransfer of this object will again lead to an error if the cause of error has not since been removed.
- 3 Object Not Processed (Ignored)
An error occurred for an object that was processed earlier in the same qRFC LUW. The subsequent objects are not processed (ignored). The associated postprocessing records are marked with the error status Ignored. For ignored objects, it is not possible to say whether a retransfer will be successful.
Dependencies
Dependencies
Example
You create three planned orders in SAP APO. These planned orders are sent to SAP R/3 in a qRFC LUW. The first planned order A is processed without errors in SAP R/3. However, an error occurs in SAP R/3 during the processing of the data for the second planned order B. The data for the third planned order C is not processed by the system (ignored) because an error already occurred in the same qRFC LUW (for planned order B).
The postprocessing records of the planned orders have the following error statuses:
Planned order Error status
A 1 - No errors
B 2 - Errors
C 3 - Object was not processed (ignored)
History
Last changed by/on | SAP | 20030602 |
SAP Release Created in |