Kontakt

Ansicht
Dokumentation

CRM_FINANCE_STEPSTR - BAdI: Check Flexible Payment Structure Flag

CRM_FINANCE_STEPSTR - BAdI: Check Flexible Payment Structure Flag

rdisp/max_wprun_time - Maximum work process run time   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

With this Business Add-In (BAdI), you implement the check as to whether or not the Step Payments flag is set in the product master.
You can set the Step Payments flag in the financing structure. This flag indicates whether the payment structure can have an irregular structure, and is transferred automatically to the lease and/or lease quotation.
If the payment structure in the lease/lease quotation has an irregular payment structure, but the Step Payments flag is not set in the product master, an error message appears.

The standard implementation checks the relevant items as described below, and assumes that an irregular payment schedule is present in the following cases:

  • Payment steps with different flow categories (aside from the interim period)
  • Special offer payments
  • Non-annuity payments steps exist, such as pure interest payment steps or zero payments
  • Fees within the payment structure
  • Different periodicities
  • A default amount or default percentage is specified in more than one payment step - that is, installments are prespecified
  • A broken, or incomplete period exists

If you want to generally allow irregular payment schedules, you always have to set the Step Payments flag in the affected financing products.

If you want to have different error handling or specify different check logic, you will have to create your own implementation.

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.






Fill RESBD Structure from EBP Component Structure   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 3967 Date: 20240523 Time: 152842     sap01-206 ( 55 ms )