SAP ABAP Data Element CIFERRHAND (Error Handling in Target System)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ SCM-BAS (Application Component) SCM Basis
     ⤷ CIF (Package) Core Interface
Basic Data
Data Element CIFERRHAND
Short Description Error Handling in Target System  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type CIFERRHAND    
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. Hndlg 
Medium 16 Error Handling 
Long 24 Type of Error Handling 
Heading 24 Type of Error Handling 
Documentation

Definition

Determines how the system reacts to errors in the transfer to and from the current target system using the APO Core Interface (CIF). Note that the setting you make here applies to the transfer to SAP APO and vice versa.

Use

The following settings are available:

  • <INITIAL>:    Strict (termination at error)
  • S:    Strict (termination at error)

    This setting is identical to the setting <INITIAL>. If an error occurs in the target system during the processing of a CIF queue, the queue hangs with the status SYSFAIL.

  • 1:    Postprocessing at error, no splitting of LUWs

    If an error occurs during the processing of a CIF queue, the queue does not hang with the status SYSFAIL. It is also no longer displayed in the SCM Queue Manager, as if it had been processed successfully. However, data is not changed in the target system, which means that the transfer has not taken place. In this case, postprocessing has to be carried out using CIF postprocessing.

    Transfers through CIF that use queued Remote Function Calls (qRFC) sometimes group multiple objects (such as orders) in one Logical Unit of Work (LUW). The No Splitting of LUWs setting means that none of the transferred objects are posted in the target system if an error occurs during the processing of one object in the same LUW. For more information, see qRFC LUW.

Dependencies

Example

History
Last changed by/on SAP  20030602 
SAP Release Created in