Kontakt

Ansicht
Dokumentation

WRF_PREPAY_INVOICE - BAdI for Prepayment

WRF_PREPAY_INVOICE - BAdI for Prepayment

General Data in Customer Master   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Application component: MM-IV-LIV (Logistics Invoice Verification)
Package: WRF_INVOICEVERIFICATION_PREPAY

How does the standard system respond?

The relevance for prepayment of a logistics invoice is determined from the prepayment-specific Customizing. If necessary, a prepayment document is posted with the posting date of the logistics invoice.

What does the Business Add-In do?

Business Add-In WRF_PREPAY_INVOICE provides two methods:

  • Method SET_POSTING_DATE lets you change the posting date of the prepayment document. The posting and document date from the logistics invoice verification are passed on.
  • Until a prepayment document is posted, you can use method PREPAYMENT_RELEVANCE_CHANGE to override the Prepayment Relevance field from the header of the current logistics invoice, and thus prevent (or trigger) prepayment.

What is the business and technical context of the Business Add-In?

Method SET_POSTING_DATE lets you select a posting date other than the system date for the prepayment document.

Method PREPAYMENT_RELEVANCE_CHANGE lets you implement extended logic to control the prepayment relevance (request or reject). To do so, the Business Add-In provides the invoice document header (RBKP) at runtime.

When are the Business Add-Ins called?

Both BAdI methods are called before saving the logistics invoice, in method INVOICE_SAVE_PREPARE of class CL_WRF_PREPAYMENT.

What impact do the Business Add-Ins have on the application?

Please note that the posting date (in method SET_POSTING_DATE) and the prepayment relevance (in method PREPAYMENT_RELEVANCE_CHANGE) can only be changed as long as no prepayment document has been created.

The Business Add-In is not active in the standard system.

The Business Add-In does not support multiple use.

The Business Add-In is not filter-dependent.

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.






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

Length: 4326 Date: 20240523 Time: 201726     sap01-206 ( 54 ms )