Kontakt

Ansicht
Dokumentation

SAPAPO_SPP_PWL - Maintain Detail Component

SAPAPO_SPP_PWL - Maintain Detail Component

General Data in Customer Master   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you can define settings that allow the detail component to be displayed in the following Planner's Worklist queries:

  • SPP_PLANNER_ALERTS_1
  • SPP_PLANNER_ALERTS_2
  • SPP_PLANNER_ALERTS_3
  • SPP_PLANNER_CRITICAL_PROD
  • SPP_PLANNER_CRITICAL_SO
  • SPP_PLANNER_FCST_APPR
  • SPP_PLANNER_FEEDER_STO
  • SPP_PLANNER_FEEDER_SURPLUS
  • SPP_PLANNER_PROCURE
  • SPP_PLANNER_PROCURE_APPR
  • SPP_PLANNER_STOCK
  • SPP_PLANNER_STOCK_APPR
  • SPP_PLANNER_STO_APPR

The worklist detail component enables you to display content that you defined within one or several form views for most of the standard worklist queries, as well as for queries defined by you.

SAP provides two example implementations which you can activate by setting up Customizing in the following way:

Product-dependent master data information:

Detail ID,,,,001
Group ID,,,,G01
Sequence,,,,1
No. Fields per Row,,3
Structure,,,,/SAPAPO/SPP_PWDET_PROD_STR
Class,,,,,,/SAPAPO/CL_POWL_DETAIL_READ
Method,,,,GET_PRODUCT_DATA

Location product-dependent master data information:

Detail ID,,,,001
Group ID,,,,G02
Sequence,,,,2
No. Fields per Row,,3
Structure,,,,/SAPAPO/SPP_PWDET_LOC_PROD_STR
Class,,,,,,/SAPAPO/CL_POWL_DETAIL_READ
Method,,,,GET_LOCPROD_DATA
  1. Assign detail component to worklist
You assign a Detail ID(Detail Component ID) to your worklist.
  1. Maintain POWL detail component
    1. You define the Detail ID (Detail Component ID). One Detail ID can include multiple Group IDs.
    2. You define the Group ID as follows:

  1. Set up your own DDIC structure
You can enter your own DDIC structure that you want the system to use to display the detail component. To do so, in the Structure (POWL Detail Component: Structure) field, enter your DDIC structure you want to use.
You must make sure that your DDIC structures only contain components with elementary component types. Nested component types, like structures or tables are not supported.
The system generates the forms dynamically, following a simple pattern:
  • Each DDIC structure is rendered in a group container as a form view.

  • The number of fields per row shown in a group is taken from the setting you make in the No. Fields per Row (Number of Fields per Row) field.

  • The order of the form fields follows the sequence of the components in the DDIC structure.

  • In case you have specified three fields per row for a group, the first three DDIC structure components are shown as fields in the first form view row, then the system renders the next row.

  • In most cases, the system renders a form field as display only input field. In case the data element's domain is of type XFELD (data type character with length 1), the system renders a checkbox.

  • The system derives the label and tooltip of the form fields from the data element field label heading and its short description. The caption of the group is derived from the DDIC structure's short description.

  1. You set up your own reading routines
You can set up your own reading routines that you want the system to use to read the data that it displays in the detail component.
The reading routines must be public class methods. The naming convention of the method parameters is the following:
Parameter Type Typing Method Associated Type
IS_SELECTION Importing Type /SAPAPO/PUIA_POWL_DETAIL_PARAM
ES_RESULT Exporting Type Name of the result type DDIC structure
ET_RETURN Exporting Type BAPIRETTAB

Warning: You must follow the naming convention when creating own reading routines, otherwise the dynamic method call fails.
You can use exporting parameter ET_RETURN for message handling.
The importing structure /SAPAPO/PUIA_POWL_DETAIL_PARAM contains the following components:
  • Application ID

  • POWL Type ID

  • Action identifier

Contains the ID of the hyperlink-enabled key field that you can select in the worklist result table.
  • Key fields that contain product, ship-from location and ship-to location for selection purposes. The available key fields are automatically filled in the corresponding worklist feeder class.

  • A generic data reference of type DATA that contains all values of the selected line in the worklists result table. It can be used for further parameterization of the selection in own reading routines.

As an example implementation, we provide class /SAPAPO/CL_POWL_DETAIL_READ with methods GET_PRODUCT_DATA and GET_LOCPROD_DATA that you can use as a template for your own implementations.
Type

For more information about the details of setting up the detail component, see Product Assistance for SAP S/4HANA on SAP Help Portal at https://help.sap.com/viewer/product/SAP_S4HANA_ON-PREMISE under Enterprise Business Applications -> Supply Chain -> Extended Service Parts Planning (eSPP) -> Master Data and General Functions for eSPP -> Worklists for Extended Service Parts Planning -> Detail Component for the Planner's Worklists.

Type






rdisp/max_wprun_time - Maximum work process run time   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 9419 Date: 20240523 Time: 213737     sap01-206 ( 89 ms )