SAP ABAP IMG Activity IHC_BADI_BANSTA_PUSH (BAdI: Convert Bank Statement into Bank Statement IDoc Format)
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ FIN-FSCM-IHC (Application Component) FSCM In-House Cash
     ⤷ FIN_IHC (Package) Payment Order In-House Cash
IMG Activity
ID IHC_BADI_BANSTA_PUSH BAdI: Convert Bank Statement into Bank Statement IDoc Format  
Transaction Code S_P7F_76000012   (empty) 
Created on 20060512    
Customizing Attributes IHC_257KUA   BAdI: Change Payment Orders During Background Processing 
Customizing Activity IHC_BADI_BANSTA_OB   BAdI: Convert Bank Statement into Bank Statement IDoc Format 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name IHC_BADI_BANSTA_PUSH    

Use

This business add-in (BAdI) is used in the SAP In-House Cash (FIN-FSCM-IHC) component.

You use this BAdI to change the outbound Bank Statement Notification XI message.

Requirements

Standard settings

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.

    The system displays the initial screen for creating Business Add-In implementations.

  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Classfield automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.

    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:

  8. Choose Activate.

When the application program is executed, the code you created is run through.

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  20060512 
SAP Release Created in