Hierarchy

⤷

⤷

Basic Data
Data Element | MEREP_CASCADE_ALLOWED |
Short Description | Cascade Allowed |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | MEREP_FLAG | |
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 | Cascade |
Medium | 15 | Cascade |
Long | 40 | Trigger Download of Reference SyncBO |
Heading | 2 | CA |
Documentation
Definition
Controls the cascade download relations between SyncBOs. The flag defines which SyncBO drives the records being downloaded from another SyncBO.
Procedure
Define whether a particular SyncBO is a trigger for downloading the reference target SyncBO.
Examples
A sales order SyncBO refers to a customer SyncBO.
- You must filter the sales order SyncBO to a client with some criteria
- All customers that are referenced from the downloaded sales orders need to be downloaded to the client
In the above example, set the synchronizer control record of the customer SyncBO so that the sales order SyncBO triggers the download of the customer SyncBO with cascading.
You can define further cascading downloads. For example, the above customer SyncBO can refer to another SyncBO, such as the sales area.
Dependencies
If you set the cascading flag from SyncBO A to SyncBO B, the definition for SyncBO A must include a foreign key relationship from at least one of its fields to SyncBO B.
Definition
History
Last changed by/on | SAP | 20070216 |
SAP Release Created in | 630 |