Kontakt

Ansicht
Dokumentation

FDM_BADI_P2P_JUDGE - BAdI: Valuation of Promise to Pay

FDM_BADI_P2P_JUDGE - BAdI: Valuation of Promise to Pay

CL_GUI_FRONTEND_SERVICES - Frontend Services   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

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

With this BAdI you have two options for how you valuate promises to pay:

  • You can valuate a promise to pay without installment plan and specify whether is was kept, partially kept or broken.
  • You specify Tolerance Days for the valuation, and so override the entries that you have made in Customizing. This is possible for both promises to pay with or without installment plan.

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
  • When displaying the installment plan in the 'Process Receivables' view (the system distributes all of the payments assigned to the promise to pay with installments to the installments, and determines whether these have been paid on schedule or not).
  • When checking in 'Process Receivables' whether that state has been changed manually or not for the promise to pay with installments. The state may only be changed manually if the due date of the last installment including the tolerance days is in the past.

Import parameter IS_PROMISE_DATA contains the current attributes of the promise to pay.
You use parameter E_PROMISE_STATE to determine the new state for promises to pay without installment plan.
Use parameter E_TOLERANCE_DAYS to override the Tolerance Days you have defined in Customizing. However, the prerequisite for this is that a value > 0 is transferred. You should also note that for promises to pay without installment plan, E_TOLERANCE_DAYS is only taken into account provided E_PROMISE_STATE remains empty.

The BAdI is not active in the standard system.

After you have called the IMG activity, proceed as follows:

  1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.
If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.
  1. In the corresponding field, enter a short text for implementation .
  2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
  3. Choose the tab Interface.
The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.
If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.
  1. Save your entries and assign a package.
  2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
  3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
  4. Save and activate your coding, and navigate back to the screen Change Implementation.
  5. Save on the screen Change Implementation.
Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.
  1. Choose Activate.
When the application program is executed, the coding you have created will be run.






RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4668 Date: 20240523 Time: 192016     sap01-206 ( 65 ms )