Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-MOB (Application Component) SAP NetWeaver Mobile - Use subcomponents⤷
S_ME_DATA (Package) Mobile: data replication
Basic Data
| Data Element | MEREP_STOPONERR |
| Short Description | Stop Processing If Errors Occur |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AS4FLAG | |
| 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 | Stop |
| Medium | 15 | Stop Processing |
| Long | 25 | Stop Processing on Error |
| Heading | 4 | Stop |
Documentation
Definition
If this flag is set and an error occurs when processing a message, no subsequent messages from the same client are processed.
This restriction ensures that messages are processed as intended by the user.
Procedure
The application defines whether or not this flag should be set. Set this flag if you expect that processing a message whose related object upload has already failed could cause unintended data updates in the backend system.
Examples
In the following case you do not need to set the flag:
On a client, you first create a customer master record A and then create a sales order record B for customer A. If the customer upload fails, the order upload via the BAPI will also fail. The consequences will be the same whether the MI server stops the sales order upload or the backend returns an error for the executed sales order upload.
In the following case you are recommended to set the flag:
On a client, you first modify a customer master record C and then create a sales order record B for customer B. If the customer upload fails, the order might be uploaded or executed successfully, but with unintended update results in the backend. Neither of the cases are treated as an error from the middleware perspective if the function call is successful. It is therefore preferable if the middleware does not issue a second update BAPI call.
Dependencies
History
| Last changed by/on | SAP | 20070216 |
| SAP Release Created in | 620 |
