SAP ABAP IMG Activity ISHMED_PRG_BADI_SUBS (BAdI for Including Customer-Specific Subscreen)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ NORD (Package) R/3MED: Services processing EDV-G
IMG Activity
ID ISHMED_PRG_BADI_SUBS BAdI for Including Customer-Specific Subscreen  
Transaction Code S_KK4_96000635   IMG Activity: ISHMED_PRG_BADI_SUBS 
Created on 20020521    
Customizing Attributes ISHMED_PRG_BADI_SUBS   BAdI for Including Customer-Specific Subscreen 
Customizing Activity ISHMED_PRG_BADI_SUBS   BAdI for Including Customer-Specific Subscreen 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISHMED_PRG_BADI_SUBS    

With the BAdI N1_PREREG_SUBSCREEN, you can add your own processing in the form of a subscreen, in the processing (display, change, enter, etc.) of preregistrations.

Use

For certain applications you will need to add application-specific information in the preregistration. As standard, the preregistration has the following fields which you can use as required:

  • Two alphanumeric fields of 20 characters each
  • Two date fields
  • Two checkboxes
  • One alphanumeric field of 50 characters.

If these fields are insufficient, you can also display or enter information from other tables in a customer-specific subscreen. In this case you procure and save the data to be displayed and save any changes.

Requirements

In order to add a subscreen, you must configure the system so that you can enter and save a preregistration.

Standard settings

In this Business Add-In you will find a sample which displays the fields available as standard in a subscreen and also allows changes.

Activities

To implement a subscreen you create a screen of the subscreen type in a function group in the customer namespace.

In this function group you then define the data structures which you require for the subscreen.

You also create an implementation of BAdI N1_PREREG_SUBSCREEN and activate this. The following BAdI methods are called as standard at PBO and/or PAI times:

  • INITIALIZE: This announces the name of your subscreen and the function group where it is situated.
    In this method you should note the current preregistration instance and the processing code, in order to be able to access these later.
    This method is called at the program start as standard.
  • BEFORE_PBO: This method is called before each PBO process as standard.
    You can dynamically set the subscreen (independent of the data).
    If, for example, the customer-specific subscreen should appear differently in a specific organizational unit, you can create two screens in your function group and set the screen number in the BEFORE_PBO method depending on the organizational unit.
  • SET_DATA: With this method, the standard supplies the BAdI with the preregistration data and the OK code. It is not absolutely necessary to implement this method. It is sufficient to note the reference to the preregistration object in the INITIALZE method. Using this reference you can access the current preregistration data at any time.
  • GET_DATA: Used to transfer an OK code to the standard
  • CHECK_DATA: In this method you should implement checks for the fields of your subscreen. Using the error handler and a return code, you can return any error messages to the standard.
    This method is called by the standard when checking or saving.
  • SAVE: In this method you can maintain any customer-specific tables. If, for example, you wish to save a history in a separate table each time a preregistration is saved, you should do this here.
    You do no need to save the preregistration itself. This is done automatically by the standard.
    Der Standard ruft die SAVE-Methode, wenn der Anwender speichern will.
  • CHECK_FOR_CHANGES: You can use this method to inform the standard of whether data in your subscreen has changed.
  • SET_CURSOR: You can use this method to position the cursor on a specific field of your subscreen.
    The standard calls the SET_CURSOR method if, for example, you double-click on a error message.
    As the IMPORTING parameter you receive an error message and the name of the field concerned. If the field concerned is on your subscreen, you position the cursor on it and inform the standard that you have already set the cursor.

You implement the methods which you require for your subscreen.

Example

See sample coding CL_EXM_IM_N1_PREREG_SUBSCREEN.

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 ISHMED_PRG_BADI_SUBS 0 I041002042 O  
SIMG ISHMED_PRG_BADI_SUBS 1 I041002042 Preregistration 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20020521 
SAP Release Created in 463B