SAP ABAP Data Element CO_CHARRFCCHK (Remote Input Validation: Behavior in the Case of an Error)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ COCB (Package) R/3 Application Development: PP Orders Batch Management
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ COCB (Package) R/3 Application Development: PP Orders Batch Management
Basic Data
Data Element | CO_CHARRFCCHK |
Short Description | Remote Input Validation: Behavior in the Case of an Error |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CO_CHARRFCCHK | |
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 | Validation |
Medium | 25 | Input validation |
Long | 40 | Input Validation Behavior |
Heading | 15 | Input Validatn |
Documentation
Definition
This indicator determines how the system behaves if there is an error in the communication with the remote system during the input check. In RFC connections without errors, this indicator does not take effect.
The following situations can lead to a communication error:
- The RFC destination has not been maintained correctly.
- The remote system is not available.
- The relevant characteristic does not exist in the remote system or is not consistent. Note that the characteristic must exist both in the local and the remote system and must have the same technical qualities (format, length, decimal places, and so on).
You have the following options to specify how the system reacts to a communication error:
- Accept all entries with warning (default setting): The system issues a warning (message CB 620: "Input check is not possible at present. Value is taken over unchecked") and accepts the value entered without checking it. The reason for the error is explained in the message long text.
- Accept all entries: The system accepts the value entered without issuing a warning and without checking it. Note that if you choose this setting, the user does not know whether the value he/or she entered was correct or taken over without first checking it.
- Reject all entries with error message: The system rejects all entries and issues an error message (message CB 621: "Input check is not possible at the moment. Value must be rejected). Note that this setting leads to a high dependency on the remote system. If it is not available, you may not be able to continue working in the local system either.
- Perform local check without warning:The system checks the entry in the local system. This setting only makes sense if the same data is available in the local system and in the remote system (for example, when the data is distributed via ALE).
- Local check with warning: The same as above but a warning is issued (message CB 622: "Input check is restricted at present. Check entry carefully"). The reason for the error is explained in the message long text.
Which setting you choose, depends largely on the relevant characteristic and when it is used.
History
Last changed by/on | SAP | 20011120 |
SAP Release Created in | 46C |