Hierarchy
WEBCUIF (Software Component) SAP Web UI Framework⤷
CA-WUI (Application Component) WebClient UI⤷
WCF_IMG_STRUCTURE (Package) Structure and Activities for WEBCUIF IMG
IMG Activity
| ID | WCF_GENIL_010 | Basic Settings |
| Transaction Code | S_A0F_96000034 | (empty) |
| Created on | 20090423 | |
| Customizing Attributes | WCF_ATT_GENIL_010 | Attributes: Basic Settings |
| Customizing Activity | WCF_OBJ_GENIL_010 | Objects: Basic Settings |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | WCF_GENIL_010 |
Use
In this Implementation Guide (IMG) activity, you define the components and component sets used by the generic interaction layer for various SAP applications.
By assigning components to a component set, you define the functional scope of the application. If your application uses the generic interaction layer, you must use this IMG activity to define your application as components and then assign all the applications and functions that should access your application.
You can also use this IMG activity to delete assignments of faulty components from your application. You can do so by deleting these components from the assignment to the component set. This way, you can temporarily stabilize your application during malfunctions. In the long term, however, it is necessary to correct and reassign the desired components.
You should only use this IMG activity if you have your own applications and functions that you want to link to your applications, which use the generic interaction layer.
Requirements
Standard settings
The standard version of this IMG activity contains all required entries for all SAP applications that use the generic interaction layer.
The existing entries should neither be changed nor deleted since these actions could affect other applications that are based on the generic interaction layer.
Activities
- Define your own components, if necessary. For each one, enter a technical name, a description, and the corresponding implementation class.
Self-defined implementation classes must implement interfaces IF_GENIL_APPL_MODEL and IF_GENIL_APPL_INTLAY. We recommend that the class inherits from the abstract Basis class CL_CRM_GENIL_ABSTR_COMPONENT, because this class already implements the interfaces named above. Self-defined implementation classes should be created in namespace Z or another customer namespace. - Define new component sets, if necessary. For each one, enter a technical name and a description.
- Assign the corresponding components to the component sets.
Example
Business Attributes
| ASAP Roadmap ID | 201 | Make global settings |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| CRMVC_GIL_APPDEF | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20090423 |
| SAP Release Created in | 701 |
