SAP ABAP IMG Activity CPRO_CUSTERW_EXTRTAB (Show Additional Tab Pages in Project Management)
Hierarchy
☛ CPRXRPM (Software Component) SAP Portfolio and Project Management 6.0
   ⤷ PPM-PRO (Application Component) Project Management
     ⤷ DEVELOPMENT_PROJECTS_CUSTOMIZE (Package) General Customizing for Project Management
IMG Activity
ID CPRO_CUSTERW_EXTRTAB Show Additional Tab Pages in Project Management  
Transaction Code S_PPD_96000040   (empty) 
Created on 20050428    
Customizing Attributes CPRO_CUSTERW_EXTRTAB   Show Additional Tab Page in Project Management 
Customizing Activity CPRO_CUSTERW_EXTRTAB   Show Additional Tab Page in Project Management 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name CPRO_CUSTERW_EXTRTAB    

Use

In this Customizing activity, you can display your own tab pages for project elements or show them as an additional initial view. You can restrict the new tab page to a single project type or make it available for all project types.

Extension Framework

In addition to the current function, you can add up to ten further customer Web Dynpro components by implementing the BAdI: Definition of Customer-Specific Tabs (DPR_EXTENSIONS). This extension framework can only be established by implementing the BAdI DPR_EXTENSIONS and not by performing the activities in this Customizing activity.

Requirements

You have created your own WebDynpro components in which you specified the content of the tab pages. SAP supplies the DPR_CUST_EXT_INTF_DEMO component as a demo implementation.

You have implemented the WebDynpro interface DPR_CUST_EXT_INTF that supplies your WebDynpro component with events to which the component can react. The interface defines the startup plug, the methods for data input, and the WebDynpro events for information output:

Startup Plug

The WebDynpro window of your component is called WI_CUSTOMER_VIEW and it defines an inbound plug of the type Startup. It has an input parameter called CUST_INPUT_VALUES of the type DPR_TS_CUST_EXT_TABC_INPUT. It transfers the following values:

  • OBJECT_TYPE: CGPL object type, for example, DPO for project definition, PPO for phase, and so on.
  • GUID: Internal ID of the project element
  • ROOT_GUID: Internal ID of the corresponding main object (usually the project definition)
  • ROOT_OBJECT_TYPE: CGPL object type of the corresponding main object (usually the project definition, DPO)
  • ELEM_LEVEL: Information about where your WebDynpro component is assembled (STR=structure level, DET=detail level)
  • CHANGE_MODE: 0=display, 1=change
  • LANGUAGE: Language of the current data in SAP-1-char format
  • LANGUAGE_ISO: Language of the current data in ISO format
  • DATA1: Customer-defined data field that does not map via the relevant CI structure but is managed by means of a demo subsystem (see class CL_DPR_DEMO_SUBSYSTEM). We recommend that you only use this type of customer-defined data management if, by way of an exception, it is not possible to use the CI structures.

Use these values to set up the display for your components.

Important Component Controller Methods

  • ON_AFTER_SAVE

    Time of call: The user selected Save in the application and the data has been updated.

    Use this method to discard buffered UI data from your component where necessary if it is no longer valid after the Save action.

    In this demo implementation, the UI does not buffer any of its own data, so no action is required here.

    This method is also called if the changed data was saved before the switch from 'Change' to 'Display'.

    If you want to update the customer-defined data in your component, the following rules apply:

    • If the customer-defined data is stored as fields in the relevant CI structure of the object, the data is updated automatically. SAP recommends this procedure.
    • If you do not use the CI structures and the customer-defined data is totally independent of the object model in Project Management and the update can also take place independently of Project Management , you can enter the data straight in the customer-defined table or change or delete it. Do not use a COMMIT WORK in the current LUW. If you have to use one, you have to set up your own application LUW (for example, via 'Submit Report xy and Return'), which can be used to transfer the data via the memory and in which a COMMIT WORK can take place afterwards.
    • If you do not use the CI structures and the customer-defined data has to be updated in the project management context, you should use a customer-specific subsystem: see class CL_DPR_DEMO_SUBSYSTEM. The subsystem takes control when you save the current view. However, you have to manage the data transfer between the UI and the subsystem yourself, see the methods START and ON_REPORT_CHANGES for the field DATA1.
      • SAP recommends that you only use this alternative if, by way of an exception, it is not possible to use the CI structures.
      For details about the system response when saving the current view, see Notes below.
  • ON_CLEANUP

    Time of call: The user exited the current view or chose Start Page.

    Use this method to discard buffered UI data from your component where necessary if it is no longer valid after the Exit current view or Start Page action.

    In this demo implementation, the UI does not buffer any of its own data so no action is required here.

    If you want to invalidate the customer-defined data in your component, the following rules apply:

    • If the customer-defined data is stored as fields in the relevant CI structure of the object, the data is discarded automatically. SAP recommends this procedure.
    • If you do not use the CI structures and the customer-defined data is totally independent of the object model in Project Management and the update can also take place independently of Project Management, you can invalidate the customer-defined data here.
    • If you do not use the CI structures and the customer-defined data has to be discarded in the project management context, you should use a customer-specific subsystem, see class CL_DPR_DEMO_SUBSYSTEM. The subsystem takes control when you exit the current view.
      • SAP recommends that you use this alternative only if, by way of an exception, it is not possible to use CI structures.
      For details about the system response when exiting the current view, see Notes below.
  • ON_REPORT_CHANGES

    Time of call: The UI triggered an event somewhere in the application. This may also involve your own component.

    You use this method to determine and process changes made to your own (or a third-party) component. If the customer-defined data is updated via the subsystem, you can transfer the determined data of your component to the buffer of the subsystem here. See the implementation of DPR_CUST_EXT_INTF_DEMO.

    Notes:

    • This method is called each time the user carries out a UI event, for example, when the user exits the current view, although it is not called automatically after an action such as Save. However, since the context change service is activated for the component using the method WDDOINIT (see below), ON_REPORT_CHANGES is also called for all other UI events that follow, outside your own component.
    • In the existing demo implementation, the data transfer is also explicitly triggered (for demonstration purposes) if the Mark As Changed button is chosen (see the event onAction = CHANGE of button, method ONACTIONCHANGE in the view VI_MAIN for more details).
    • Alternatively, you can use the onEnter event in the VI_MAIN view for each customer-defined field to process the customer-defined data in the same way as for ONACTIONCHANGE. This option is not used in this demo implementation.
    • You can use the singleton of the class CL_DPR_SESSION_STATE to obtain information about the current UI status. This enables you, for example, to use the method GET_DETAILVIEW to check whether your own component is currently active. Note that internally, the system only uses the first three characters to identify the tab, in this case 'CUS' and not 'CUSTOMER'.
    • Take the ON_UPDATE method, which always occurs together with ON_REPORT_CHANGES, into account too.
  • ON_SET_CHANGE_MODE (importing new_mode type i)

    Time of call: The user triggered the switch between display and change mode. The event is only used if the switch was successful.

    If new_mode = 0, the system switches to display mode. If new_mode = 1, the system switches to change mode.

    In this demo implementation, the context element READONLY is set accordingly in the node UI.

  • ON_SET_DATA_LANGUAGE (importing new_language type sylangu, new_language_iso type laiso)

    Time of call: The user changed the text language.

    The new text language is made available both in SAP's own single-figure format as well as in ISO format.

    Use this method if you have to manage language-dependent data.

    No actions of this kind are required on the UI in this demo implementation.

  • ON_UPDATE

    Time of call: The UI triggered an event somewhere in the application. This could be for your own component. First of all, the ON_REPORT_CHANGES event was sent (see above).

    You use this method to update the format in your component so that changes to project management data appear straight away or to update dependent values (for example, headings or inspection texts) for changed, customer-defined data.

    No actions of this kind are necessary on the UI in this demo implementation.

  • SET_CHANGED

    Time of call: Handles the action CHANGE (ONACTIONCHANGE method) from the

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
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 CPRO_CUSTERW_EXTRTAB 0 APL0000008 Project Management 
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
DPR_CUST_TABC S - Table (with text table) SM30  
History
Last changed by/on SAP  20101028 
SAP Release Created in 400