Ansicht
Dokumentation

CPRO_CUSTERW_CHNGEUI - Make Customer-Specific Interface Changes

CPRO_CUSTERW_CHNGEUI - Make Customer-Specific Interface Changes

BAL Application Log Documentation   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Use

In this activity you make changes to the interface. In this way you can adapt the application to your needs.

There is no connection to the modification assistant for BSP views. Therefore it is possible to overwrite changes to views modifications that are made in an upgrade or in some cases, when implementing a Support Package or an SAP Note.

The concept for changing the layout of the user interface introduced here is a preliminary, modification-free solution. Instead of calling a view from the original BSP application, it calls a view from a customer application. The indirection is saved in a Customizing table you maintain using the report BSP_CUSTOMIZE. The runtime environment recognizes which view in the SAP BSP application has a customer-specific view, and then calls this instead of the original view.

The report also allows you to deactivate and then reactivate the call of the views in your own application. To do so use the radio button Deactivate Customizing or Activate Customizing accordingly. Furthermore you can delete the Customizing entry for your own application.

Note the following if you upgrade or implement a Support Package:

  • The modification adjustment transaction (transaction SPAU) does not inform you of changes.
  • After you upgrade you must make the required changes by comparing the original view with the modified view yourself. The system does not offer support in this matter.
  • It is not impossible to make incompatible changes in the SAP application. This can lead to the fact that errors occur when you call the customer view.

Requirements

So that the additional fields are visible on the interface, you must complete the following IMG activity: Enhance Database Tables.

Standard settings

Activities

  1. Call the report BSP_CUSTOMIZE in transaction SE38.
  2. Using the report for the BSP application cProjects, create a new BSP application in the customer namespace:
    1. Decide where you want to make the changes, and enter cprojects, cprojects_cp, or prp (see the table below) under Name of Application and a name in the customer namespace as the new name.
    2. Select Copy Application from the selection screen.
    3. In the screen that follows, select the views you want to change.
We recommend that you make the changes in the structure view on the Basic Data or Additional Data tab strip, because you do not need to make changes to the controller class there. The data in the customer field enhancement is contained in a page attribute. The corresponding views are:
Project Element   View   Description   BSP Application
Project   prjDetailData.bsp   View Project Details Basic Data   CPROJECTS
  prjDetailData2.bsp   View Project Details Basic Data 2   CPROJECTS
  prjDetailDataT.bsp   View Project Template Details Basic Data   CPROJECTS
  prjDetailData2T.bsp   View Project Template Details Basic Data2   CPROJECTS
Phase   phaDetailData.bsp   View Phase Details Basic Data   CPROJECTS
  phaDetailData2.bsp   View Phase Details Basic Data 2   CPROJECTS
  phaDetailDataT.bsp   View Phase (Template) Details Basic Data   CPROJECTS
  phaDetailData2T.bsp   View Phase (Template) Details Basic Data2   CPROJECTS
Task   tskDetailData.bsp   View Task Details Basic Data   CPROJECTS
  tskDetailData2.bsp   View Task Details Basic Data 2   CPROJECTS
  tskDetailDataT.bsp   View Task (Template) Details Basic Data   CPROJECTS
  tskDetailData2T.bsp   View Task (Template) Details Basic Data2   CPROJECTS
Checklist   cliDetailData.bsp   View Checklist Detaila Basic Data   CPROJECTS
  cliDetailData2.bsp   View Checklist Details Basic Data 2   CPROJECTS
  cliDetailDataT.bsp   View Checklist Template Details Basic Data   CPROJECTS
  cliDetailData2T.bsp   View Checklist Template Details Basic Data2   CPROJECTS
Checklist Reference   clrDetailData.bsp   View Checklist Reference Details Basic Data   CPROJECTS
  clrDetailDataT.bsp   View Checklist Reference (Template) Details Basic Data   CPROJECTS
Checklist Item   citDetailData.bsp   View Checklist Item Detail Basic Data   CPROJECTS
  citDetailData2.bsp   View Checklist Item Details Basic Data 2   CPROJECTS
  citDetailDataT.bsp   View Checklist Item (Template) Details Basic Data   CPROJECTS
  citDetailData2T.bsp   View Checklist Item (Template) Details Basic Data2   CPROJECTS
Control Plan   cpheader.bsp   Control Plan Header Data   CPROJECTS_CP
  cpitems.bsp   Control Plan Items   CPROJECTS_CP
  cpitem_detail.bsp   Details Control Plan Items   CPROJECTS_CP
Role   roleGeneral.bsp   View Role DetailsBasic Data   PRP

  1. Execute the report.
  • From the BSP application cProjects copy the controller error.do to your own BSP application.
  • Make changes to the layout of the copied views.
  • Note:
    • Do not change the characteristics or page attributes of the views.

    • In general you do not need to make changes to the controller class since the fields in the customer enhancement are contained in the page attribute PS_ATTRIBUTES.

    1. If you want to change other views at a later point in time, copy these views from the cProjects BSP application to your own application und change them here.

    Example

    Add the following coding to the corresponding BSP pages if you added the field CUSTOMER01 to a table, for example, and if you want to display it on the interface:


    <tr>
    <%-- CUSTOMER01  --%>
    <%
      lr_fieldutil->set_field( iv_name = 'extended_attributes-customer01'
      iv_data = ps_attributes-extended_attributes-customer01 ).
    %>
    &lt;td>

                 id   = "customer01_lb"
                 text = "<%= lr_fieldutil->get_label( ) %>" />

    &lt;td>

                      value     = "<%= lr_fieldutil->get_value( ) %>"
                      maxlength = "<%= lr_fieldutil->get_maxlength( ) %>"
                      disabled  = "<%= pv_not_change %>" />






    SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ROGBILLS - Synchronize billing plans  
    This documentation is copyright by SAP AG.

    Length: 13961 Date: 20240523 Time: 163715     sap01-206 ( 110 ms )