SAP ABAP IMG Activity APB_ISR_FORM_PR_BADI (BAdI: Form Processing)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-MUS-LP (Application Component) Launchpad
     ⤷ APB_ISR (Package) Internal Service Request on ABA
IMG Activity
ID APB_ISR_FORM_PR_BADI BAdI: Form Processing  
Transaction Code S_ABA_72000406   (empty) 
Created on 20090406    
Customizing Attributes APB_ISR_FORM_PR_BADI   BAdI: Form Processing 
Customizing Activity APB_ISR_FORM_PR_BADI   BAdI: Form Processing 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name APB_ISR_FORM_PROCESSING    

Use

This Business Add-In (BAdI) is used in the General Application Functions (CA-GTF) component. It can be used to control the flow logic details of the request form for a Basic Internal Service Request (Basic ISR) in the back-end system.

Requirements

Standard settings

In the standard system, the scenario filter implementation is activated.

The BAdI is designed for single use and is filter dependent.

BAdI Implementations

  • Scenario filter

Activities

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

Methods

The following BAdI methods are available:

  • INIT: Initialize

    This is the first method that is used when you call a new request form (mode CREATE). The following parameters are defined:

    • IV_MODE = "CREATE"
    • IV_EVENT is blank.
    • CT_SPECIAL_DATA can be used to initalize the form fields provided.
  • SET_ADDITIONAL_VALUES (corresponds with screen PBO): Set additional values for value help

    This method is used for calling a request form (create, display, change) before the form is output. The standard values for the MODE parameter are described below.

    Note: In this BAdI, provide internal table CT_ADDITIONAL_DATA with values that are required only at the runtime of the form, but are not to be saved in the request. This means you set input helps for dropdown list boxes and control parameters. Internal table CT_ADDITIONAL_DATA is not automatically deleted so that the system retains data that was set until the form is sent. You can use parameter MODE to modify your logic depending on the current mode (CREATE, CHANGE, DISPLAY).

    Note: The CT_ADDITIONAL_DATA table has to be sorted alphabetically according to the technical characteristic name.

  • PROCESS_EVENT (corresponds with screen PAI): Process own user commands

    This method is the first method that is used when an event in the request form is triggered (check, send, user command).

  • CHECK: Check

    This method is the second method that is used when a standard event is triggered in the request form (check, send). Therefore, the check is always carried out before creating or changing a notification. In case you encounter an error you can return a corresponding error message via exporting parameter ES_RETURN. In case you would like to present more than one message on the form you can use parameter CT_MESSAGE_LIST.

  • FINALIZE: Finalize after data storage

    This method will be used after the form data are stored in the data base, and the request number was created but before the request number will be provided on the screen. You can use that method to carry out follow-up action. In case you would like to rollback the creation of the request on the data base you can return a corresponding error message via exporting parameter ES_RETURN. This leads to a rollback of the data base entry of the request.

Parameters

The standard values of parameters IV_MODE and IV_EVENT are as follows:

  • IV_MODE: Current processing mode (CREATE, CHANGE, DISPLAY); corresponds with URL parameter MODE. The following values are possible:
    • MODE = "CREATE" if the initial call of the Basic ISR form was carried out without a notification number (URL/iView parameter NOTIF_NO blank)
    • MODE = "CHANGE" if the call of the Basic ISR form was carried out with a notification number (URL/iView parameter NOTIF_NO filled)
    • MODE = "DISPLAY" if the call of the Basic ISR form was carried out with a notification number (URL/iView parameter NOTIF_NO filled) in display mode

  • IV_EVENT: Standard Basic ISR events are defined as follows:
    • "SEND" if the Basic ISR form (Web Dynpro application APB_ISR_UI_FORM) is sent
    • "SAVE" if the Basic ISR form (Web Dynpro application APB_ISR_UI_FORM) is saved
    • "CHECK" if you choose "Review" in the Basic ISR form

In the customer-specific form, you can define individual additional events that can be queried at runtime in the methods of this BAdI using parameter IV_EVENT.

Example

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 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20090406 
SAP Release Created in 730