SAP ABAP IMG Activity CM_XX_STAT15 (BAdI: Status Indicator Derivation)
Hierarchy
☛ IS-PS-CA (Software Component) IS-PUBLIC SECTOR CONTRACT ACCOUNTING
   ⤷ IS-HER-CM-AD (Application Component) Administration
     ⤷ PMIQ (Package) Campus Management
IMG Activity
ID CM_XX_STAT15 BAdI: Status Indicator Derivation  
Transaction Code S_KK4_82000844   (empty) 
Created on 20011123    
Customizing Attributes CM_XX_257_2_1   Multiple Use: Critical Optional Activity, IS-HER-CM-AD, ASAP 257 
Customizing Activity CM_XX_STAT15   BAdI for Derivation of Status Indicators 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRPIQ00_SET_STATIND    

Use

You can use this customer enhancement to implement the method which sets holds and customer statuses, (but not system statuses), in the business add-in HRPIQ00_SET_STATIND. This method is:

SET_STATIND (Set Status Indicators)

The system uses the method SET_STATIND and specific source information to determine status indicators and set the relevant specification. Status indicators can have the status active (activate status indicator) or inactive (deactivate status indicator). The business add-in HRPIQ00_SET_STATIND can be used in every Campus Management activity that sets status indicators. The system can only set status indicators if the business add-in has an active implementation. Manual maintenance of status indicators in the Student File is not affected by this restriction.

Requirements

Before you can implement this method, you must create the required hold types and customer status types in Customizing. You create these entries in the following IMG activities:

The SET_STATIND method uses the following parameters:

  • Import parameters
    • FLT_VAL: Filter value for which the active implementation is selected
      Possible filter values are the Campus Management activities in table T7PIQPROCESS which allow the setting of status indicators. You can use an implementation for several filter values (in this case: activities).
    • IS_PROCESSDATA: Structure containing activity data for status indicators including the:
      - Activity
      - Callup point (optional)
      - Booking date
      - Booking time
      - Student object ID
      - Study ID (optional)
    • IT_DERIV_DATA: Table containing the additional data (optional) which is transferred to the business add-in by certain activities, and which may be relevant for setting status indicators
  • Export parameters
    • ET_STATIND_LIST: Table containing the status indicators transferred by the implementation
      This list can retain its initial values if the system determines, on the basis of imported data, that status indicators do not need to be set for the student. The table can contain one or more status indicators if the system determines, on the basis of imported data, that specific holds and/or customer statuses must be activated and/or deactivated. The fields HS_STATUS and HS_STATE must contain values for each status indicator to be set. The other fields are optional. They contain values which are set by the system:

      - Plan version (PLVAR): Current plan version
      - Object type (OTYPE) and object ID (OBJID): Values of the student in question
      - Validity start date (BEGDA) and end date (ENDDA) of the status indicator with the relevant specification: Current system date or 31.12.9999.
      • If your implementation transfers other values, these values are written in the fields. If the table contains program-related status indicators, that is, status indicators which are stored in the object type study of infotype 1728 (Status Indicators), you can leave the initial values in the fields object type and object ID only if the import structure IS_PROCESSDATA contains the ID of a study object. If not, you have to determine the ID and object type of the relevant study object in your implementation of the business add-in, and insert it in the table for the relevant status indicator.

Note

You only need to perform this activity if your system configuration requires Campus Management activities to automatically set status indicators. If you want to set status indicators manually, you can skip this activity.

Further notes

You should perform this activity only if both of the following conditions are satisfied:

  • The SAP standard processes do not cover your requirements.
  • You have an in-depth knowledge of the ABAP programming language.

Business add-in implementations are code extensions and therefore apply across clients. If you have a multiclient system, you have to define how the customer enhancement is to be used within the implementation for each client using the system variable SY-MANDT.

Business add-ins without multiple usages can have several implementations. However, only one of these implementations may be active at any one time.

You must also make sure that instance creation for the implementing class (Properties tab page) is declared as public and not as private, protected, or abstract. Otherwise unwanted short dumps may occur during runtime.

General information and implementation instructions for business add-ins are found in the SAP library under Basis Components -> ABAP Workbench (BC DWB) -> Changes to the SAP Standard (BC) -> Business Add-Ins. You can also access this documentation from the initial BAdI builder screen via Help -> Application help.

Activities

After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:

  1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

    The screen for creating BAdI implementations is now displayed.

  2. Enter a short text for the implementation in the Short text for implementation field.
  3. From the tab index, choose Interface.

    The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.

  4. Save your entries, and assign the implementation to a development class.
  5. Place the cursor on the method, and double-click to enter method processing.
  6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. Return to the Edit Implementation screen.
  8. Save the entries on the Edit Implementation screen.

    Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.

  9. Choose Activate

    The code you stored in the method will be run when the application program is executed.

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20030113 
SAP Release Created in 464