Hierarchy
⤷ MM-IV-LIV (Application Component) Logistics Invoice Verification
⤷ WRF_INVOICEVERIFICATION_PREPAY (Package) Invoice Verification Prepayment
IMG Activity
ID | WRF_PREPAY_INVOICE | BAdI for Prepayment |
Transaction Code | S_XC0_18000015 | (empty) |
Created on | 20050718 | |
Customizing Attributes | WRF_PREPAY_INVOICE | BAdI for Prepayment |
Customizing Activity | WRF_PREPAY_INVOICE | BAdI for Prepayment |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | WRF_PREPAY_INVOICE |
Use
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.
Requirements
Standard settings
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.
Activities
To activate the Business Add-In, you must create an active implementation. To do this, choose the following path in the SAP Menu: Tools -> ABAP Workbench -> Utilities -> Business Add-Ins -> Implementation
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:
- 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. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- 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.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - 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: - Choose Activate.
When the application program is executed, the code you created is run through.
For more information about this procedure, see the SAP Library under
- Basis Components -> ABAP Workbench -> Changing the SAP Standard -> Business Add-Ins -> Implementing Business Add-Ins.
Example
Business Attributes
ASAP Roadmap ID | 153 | Design enhancements |
Mandatory / Optional | 3 | Nonrequired activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | WRF_PREPAY_INVOICE | 0 | HLA0001544 | Logistics Invoice Verification |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20050718 |
SAP Release Created in | 600 |