SAP ABAP IMG Activity SIMG_BADI_SESPROCESS (BAdI for POWL-Feeder Service Entry Sheet)
Hierarchy
SAP_APPL (Software Component) Logistics and Accounting
   MM-PUR (Application Component) Purchasing
     MMPUR_UI_MODEL (Package) Model Components for Web Dynpro Applications, Purchasing
IMG Activity
ID SIMG_BADI_SESPROCESS BAdI for POWL-Feeder Service Entry Sheet  
Transaction Code S_E38_98000154   (empty) 
Created on 20071011    
Customizing Attributes SIMG_BADI_SESPROCESS   BAdI for POWL-Feeder Service Entry Sheet 
Customizing Activity SIMG_BADI_SESPROCESS   BAdI for POWL-Feeder Service Entry Sheet 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_BADI_SESPROCESS    

Use

This Business Add-In (BAdI) is used in the MM-PUR component.

Enhancement spot: ES_BADI_MMPUR_UI_MODEL_FEEDER

The BADI_FEEDER_SESPROCESS BAdI implements the IF_BADI_FEEDER_POWL interface, and allows you to change the selection criteria, detail information, and actions to be carried out in the "Personalizable Object Worklist" (POWL) for material documents.

The following methods are made available via the interface:

  • GET_ACTIONS
    Here you can define pushbuttons for your own additional actions.
  • GET_ACTION_CONF
    If necessary, you can define confirmation messages for actions here. The action is then only performed if you have acknowledged the message with "YES".
  • GET_DETAIL_COMP
    Here you can specify a Web DynPro detail component that is to be branched to when a POWL line is selected.
  • GET_FIELD_CATALOG
    This method enables you to change the attributes of the fields of the standard field catalog.
  • GET_MAX_RESULTS
    This method enables you to define the number of hits after which the search ends. This prevents the system from, for example, selecting all existing data records for an object and displaying them in the POWL.
  • GET_OBJECTS
    This method makes available the objects that have already been selected as standard. If you have defined additional selection criteria, you can reselect the purchase orders here on the basis of these criteria.
  • GET_SELECTION_CRITERIA
    Here you can define additional selection criteria or default values for the standard selection criteria.
  • HANDLE_ACTION
    In this method, you define the portal follow-on operations for your additionally defined actions.

Requirements

If you define an action of your own, you must set up the business object that is to be navigated to and the operation that is to be performed on it in the portal.

If you specify a detail component, it must implement the interface POWL_DETAIL_COMP_IF.

Standard settings

The BAdI cannot be used multiple times.

This BAdI is not filter dependent.

There is no default implementation.

Activities

To activate the Business Add-In, you must create an active implementation. To do this, choose the following path in the SAP Menu: Tools -> ABAP Workbench -> Utilities -> Business Add-Ins -> Implementation

For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

Example

In the example implementation supplied, CL_EXM_IM_BADI_SES_PROCESS, the system behaves as follows:

  • An additional selection criteria is defined XMWST, Evaluate Receipt Settlement.
  • An additional action, PURREQ is defined, which is used to display the purchase requisitions using object-based navigation. The system sends a confirmation message for this action.
  • The XERSY field is added to the field catalog.

Business Attributes
ASAP Roadmap ID 153   Design enhancements 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   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 SIMG_BADI_SESPROCESS 0 HLA0009512 Purchasing 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20071011 
SAP Release Created in 603