Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-WHM-DST (Application Component) Data Staging⤷
RSSM (Package) BW: General monitoring and scheduling
Basic Data
| Data Element | RSNOSISICO |
| Short Description | No single SID commit with master data update |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RSNOSISICO | |
| 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 | No sinComm |
| Medium | 20 | No single SID commit |
| Long | 40 | No single SID commit with masData update |
| Heading | 50 | No single SID commit with master data update |
Documentation
Definition
When you update master data, a new SID is carried out, usually a database commit. This commit is seen as relatively time-sensitive. For example, if you load the master data intially when the Warehouse is installed, you have to create a large number of SIDs.
For this reason, you can use this setting to choose whether you want to run a SID after every creation process, or only when all SIDs have been created for the values of a characteristic and data packet. (With a master data update, SIDs are created for the values of a characteristic to be loaded and its navigation attributes, if they do not exist in the system yet)
Dependencies
If there are no more SIDs to be created, the internal program logic is quite time-consuming if you choose the setting for the blocked commit.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 20B |
