Hierarchy

⤷

⤷

IMG Activity
ID | WCF_CRMVC_DESIGN | Define Design Objects |
Transaction Code | S_A0F_96000052 | (empty) |
Created on | 20090424 | |
Customizing Attributes | WCF_CRMVC_DESIGN | Define Design Objects |
Customizing Activity | WCF_CRMVC_DESIGN | Define Design Objects |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | WCF_CRMVC_DESIGN |
Use
In this Customizing activity, you can adapt copied design objects to your requirements, after you have copied them from SAP design objects in the Customizing activity Copy of SAP Design Objects.
You can also create your own design objects and add attributes that belong to other BOL objects, in one design object. This means that you can group similar attributes in one design object, even if these attributes belong to different BOL objects.
In this Customizing activity, you can see copied SAP design objects, and maintain the design settings of these copies.
Once you have changed the design object, you assign it to a context node, in the UI Component Workbench.
Note
If the copied design object has the same name as the SAP design object, it is automatically assigned to the same context nodes and attributes as the SAP design object, in the UI Component Workbench. The assignment is only necessary for design objects that you have created on your own.
Design Settings
Every design object is defined by the following design settings:
- Attribute name
This identifies the design settings - The attribute name usually corresponds to the attribute in a context node; it determines which design setting is to be used at runtime.
- The attribute <DEFAULT> is used for all attributes that cannot be identified among the design object attributes. It is used to handle these non-identified attributes and hide them.
- Link to the business object (BOL) layer
This provides a BOL object and a BOL attribute, for example, if you want to refer to another BOL object and another BOL attribute in the design object. - Field label
This defines the field label that is centrally provided. If the field label is empty at runtime, it is provided by the ABAP Dictionary. - Field visibility options
- Standard
The field is displayed and provided as an available field in the UI configuration; it is displayed at runtime on the UI. - Hidden
The field is not displayed and not provided as an available field in the UI configuration; it is not displayed at runtime on the UI. - Field excluded from field set
The field is hidden and excluded from the field set. - Value help from ABAP Dictionary
The generic V-getter method is used to determine the value help. - Value help from the ABAP Dictionary: Generic V- and P-getter methods that define the value help (from the ABAP Dictionary: search help, value table, domain values) and field type (input field, checkbox, and dropdown box) have been implemented. Generic V- and P-getter logic is used only if this checkbox is selected. Search help with dialog type Dialog depends on set of values is not supported.
- Field type
The generic P-getter method is used to determine the field type. - Action provider
You can assign an action provider to one attribute of a design object. Then, in all views where that field is used, the action menu is assigned.
- Action Provider ID
- This defines the action provider ID from the action providers that are available for the BOL object for which you define a design object or for its child objects.
- You define action providers for BOL objects under Define Action Providers.
- Action BOL Relation
- This defines the BOL relation between the current BOL object of the design object and the BOL object of the action provider.
Reference Design Object
When a reference design object is used, the design objects that are based on this reference design objects inherit this design at runtime. If you click Resulting Design on the Design overview screen, you can see a list of the design settings of the current design object and its reference design object. Hidden and excluded fields are not displayed, but can be made visible if you manually remove the predefined filter of the Hidden and Excluded columns.
Requirements
Standard settings
Activities
Adapting Copied Design Objects
- Select the copied design object that you want to adapt.
- Adapt the design settings for each design object:
- You can affect all attributes of the BOL object using <BOL attribute name> = <Default>. You can also use specific BOL attribute names.
- You can enter an additional BOL object and BOL attribute.
- You can enter a field label and select whether the design object is standard or hidden.
- Save your entries.
Example
Business Attributes
ASAP Roadmap ID | 201 | Make global settings |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | WCF_CRMVC_DESIGN | 0 | PNF0000014 | UI Configuration & Design Layer |
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 |
IMGDUMMY | D - Dummy object | BSP_DLC_DESIGN |
History
Last changed by/on | SAP | 20100601 |
SAP Release Created in | 701 |