Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-ESI-SIW (Application Component) Service Implementation Workbench⤷
S_SIW_TYPES (Package) SIW: Global Type definitions
Basic Data
| Data Element | SIW_DTE_PIECE_SHARE_ATTRIBUTE |
| Short Description | Shared Object |
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 | Shared Obj |
| Medium | 15 | Shared Object |
| Long | 20 | Shared Object |
| Heading | 30 | Shared Object |
Documentation
Definition
A non initial shared attribute indicates that different SIW projects can use this object. Consider that the backend object can be modified by different SIW projects that shares that object since SIW creates the object only once in the backend.
Use
Use this shared attribute consciously. SIW checks the shared attribute only when a project creates a new object or renames an object. The sharing of an object can't be reverted, after the project has been saved.
Dependencies
The architect defines whether the object can be shared and defines the value of this attribute in the construction plan by specifying a shared class.
Example
If SIW project A specifies an interface which has to be enhanced by SIW project B, the object description for interface is used in both projects. Is no shared attribute specified or does the shared attributes not match SIW aborts the generation of that object.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 100 |
