Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-BW (Application Component) BW Service API⤷
SBIG (Package) Business Information Warehouse: Generation Tool
Basic Data
| Data Element | RSSG_CLID |
| Short Description | BW Generation Tool: Client-dependent object ID |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RSBOOL | |
| 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 | Cl.-spec. |
| Medium | 15 | Cl-spec. obj. |
| Long | 20 | Client-spec.meta ob. |
| Heading | 3 | ClD |
Documentation
Definition
This indicator determines that the application object type belonging to the program class is client-specific. This means that when a client copy is made, the 25-digit GUID, that acts as a reference to the generated program for the application object, is also copied over. The generation tool then ensures that separate programs are generated for the object in both clients. It does this by attaching a three character suffix to the program name. If a program class is indicated from which executable programs are generated, (also see documentation on program type), variants for the programs should be transported with transport object GPVD. In all other cases, use transport object GPVI. Both transport objects expect the 25-digit GUID as the object name. In particular, they allow variants to be transported to local private programs. However it is not possible to selectively transport variants for a program: All variants for a program are always transported.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in |
