SAP ABAP IMG Activity FDM_BADI_P2P_JUDGE (BAdI: Valuation of Promise to Pay)
Hierarchy
☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ FIN-FSCM-COL-AR (Application Component) Accounts Receivable Accounting Process Integration
     ⤷ FDM_AR_COLLECTION (Package) FSCM Collections Management FI-AR
IMG Activity
ID FDM_BADI_P2P_JUDGE BAdI: Valuation of Promise to Pay  
Transaction Code S_AXA_22000092   (empty) 
Created on 20040212    
Customizing Attributes FDM_257NKA_COL   Attribute: Critical User Exits (Non-Required) 
Customizing Activity FDM_BADI_P2P_JUDGE   BAdI: Valuation of Promise to Pay 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FDM_P2P_JUDGE    

Use

You use this Business Add-In (BAdI) in the SAP Collections Management (FIN-FSCM-COL) component.

You can use it to valuate promises to pay.

It is accessed for the following events:

  • In the program for valuating open promises to pay (FDM_P2P_JUDGE)
  • During the assignment of a payment to a promise to pay
  • During reset of the assignment of a payment to a promise to pay
  • In the dunning program, if you have defined a dunning lock in Customizing

The import parameter IS_PROMISE_DATA contains the current attributes of the promise to pay. You can use these during the implementation of the BAdI to decide which new state the promise to pay is to receive. You forward the new state to the calling program via the parameter E_PROMISE_STATE.

If no state is transferred, that is, the parameter E_PROMISE_STATE remains initial, the system valuates the promise to pay according to the standard logic. In this situation you can override the tolerance days you have defined in Customizing using the parameter E_TOLERANCE_DAYS.

Requirements

Standard settings

The BAdI is not active in the standard system.

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 Class field 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

See also

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 3   Nonrequired 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  20040212 
SAP Release Created in 2004_1_470