Hierarchy
EA-RETAIL (Software Component) SAP Enterprise Extension Retail⤷
CA (Application Component) Cross-Application Components⤷
WLC_PARALLEL (Package) Retail: Load Control and External Parallel Processing
Basic Data
| Data Element | WLC_RFC_MSG |
| Short Description | Load Control/Ext. Par. Proc.: RFC Message |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 80 | |
| Decimal Places | 0 | |
| Output Length | 80 | |
| 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 | RFC Mess. |
| Medium | 15 | RFC Message |
| Long | 20 | RFC Message |
| Heading | 80 | RFC Message |
Documentation
Definition
The report that is to be parallel processed is started separately in sub-jobs in the background. When starting a program in this way, you cannot transfer any detailed information on the final status of the job (whether it was successful or errors occurred) to the calling process.
The only information that the calling process may obtain is the message in plaintext, while the message number and category are unknown.
You can use this selection option to enter search strings that are compared with the plaintext message. If they match up, the message is interpreted as an error message.
Example
A report always issues an information message when it finishes (message category 'I')
<Number> documents were processed successfully.
If you enter the single value '*successfully*' in the selection option and 'different' as a comparison option, then all messages containing the character string 'sucessfully' not are valuated as errors.
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in | 46C |
