SAP ABAP IMG Activity _WCMMD_000088 (Define View Profiles)
Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   PM-WCM (Application Component) Work Clearance Management
     WCM (Package) WCM: Work Clearance Management
IMG Activity
ID _WCMMD_000088 Define View Profiles  
Transaction Code S_EE5_50000264   (empty) 
Created on 20091020    
Customizing Attributes _WCMMD_000088   Define View Profiles 
Customizing Activity _WCMMD_000088   Define View Profiles 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name _WCMMD_000088    

Use

In this IMG activity you define the view profiles for WCM objects. You can use a view profile to set up the entire header data screen of a WCM object according to individual criteria.

A range of subscreens are available for this purpose:

  • Numerous data screens with related fields
  • Six tabstrips with freely definable tabs.

You can define a view profile with either two or four levels:

  • You need a two-level view profile if you do not want to use tab pages on the header data screen (see level 1-2 below).
  • You need a four-level view profile if want to use only tab pages or mainly tab pages on the header data screen (see level 1-4 below).

You define view profiles as follows:

  • On the first level, you define the basic definition of the view profile (for example, name and description). The maximum width of the header data screen is predefined by the system and cannot be changed.
  • On the second level, you assign each of the desired areas (up to six) of the header data screen to a subscreen - either a data screen or a tabstrip. For each assigned subscreen of the header screen, you have the following options:
    • Assignment of a sequence number, to define the vertical sequence of the assigned subscreens (mandatory entry)
    • Display of a closing blank line below the assigned subscreen (optional entry)
    • Display of a border with a heading around the assigned subscreen (optional entry)
    • Note that this option is only used for data screens (not for tabstrips).
    • Positioning of the subscreen on the right-hand side of the screen area (optional entry)
    • Note that this option is only used for data screens (not for tabstrips). In addition, the following conditions must be fulfilled:
      - The width of the subscreen (including any border) does not exceed half of the maximum screen width of the header data.
      - The subscreen with the next lowest sequence number is positioned on the left-hand side of the screen and also has a width that does not exceed half of the maximum screen width.
  • On the third level (only relevant for screen areas to which a tabstrip is assigned), enter the desired tab pages and their sequence. For each specified tab page, you have the following options:
    • Definition of a tab page title (mandatory entry)
    • Definition of an icon for the tab page (optional entry)
    • Deactivation of the tab page as a (temporary) alternative to final deletion (optional entry)
  • On the fourth level, you assign each of the desired areas (up to six) for a tab page to one data screen. For each data screen assigned to a tab page, you have the following options:
    • Assignment of a sequence number, to define the vertical sequence of the assigned data screens (mandatory entry)
    • Display of a closing blank line below the assigned data screen (optional entry)
    • Display of a border with a title around the assigned data screen (optional entry)
    • Positioning of the data screen on the right-hand side of the screen area (optional entry)
    • Note that the following conditions must be fulfilled:
      - The width of the data screen (including any border) does not exceed half of the maximum screen width of a tab.
      - The data screen with the next lowest sequence number is positioned on the left-hand side of the screen and also has a width that does not exceed half of the maximum screen width.

For the (optional) titles of individual data screens, the internal description is used. However, you can also define individual titles at plant level.

Furthermore, internal standard lengths are defined for the individual data screens, in order to calculate the lengths necessary for tabstrips. However, since these data screens may be customer specific, you have the option of specifying the actual length of a data screen (at plant level). However, you only need to consider this if you are using tabstrips in the application and notice that the tabstrip is much longer than necessary, in that it is longer than required by the longest tab page.

Requirements

Note that the use of individual data screens can be coupled to the following prerequisites:

  • The use can be restricted to specific WCM objects. This kind of restriction is visible in the input help for the subscreens. For example, data screens for work and requirements can only be used for applications.
  • The processing of further IMG activities can be a prerequisite for use. Examples:
    • Data screens for work and requirements can only be used if you have defined the corresponding work and requirements.
    • Data screens for customer-specific data can only be used if you have implemented the corresponding screen extensions using:
    • - BADI_WCM_WAP_001 for work approvals (screens 8300 and 8400)
      - BADI_WCM_WCA_001 for work clearance applications (screens 8300 and 8400)
      - BADI_WCM_WAPI_001 for other applications (screens 8300 and 8400)
      - BADI_WCM_WCD_001 for work clearance documents (screens 8300 and 8400)

If you assign a data screen that cannot be used for a WCM object, the assignment is ignored at runtime, so that the data screen is not displayed for the WCM object.

Standard settings

Activities

Maintain the view profiles and assign them to the WCM objects.

Note that the standard Customizing settings for work clearance management contain sample profiles. If you require customer-specific view profiles, we recommend that you copy the sample profiles, rather than change them.

Example

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
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 _WCMMD_000088 0 PK40000012 Master Data 
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
WCV01 C - View cluster SM34  
History
Last changed by/on SAP  20091020 
SAP Release Created in 605