Ansicht
Dokumentation

SIMG_RECPT_AMOUNT_BP - BAdI: Check If Maximum Amount Exceeded for Business Partner

SIMG_RECPT_AMOUNT_BP - BAdI: Check If Maximum Amount Exceeded for Business Partner

Vendor Master (General Section)   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the SAP Travel Management (FI-TV) component.

You can use this BAdI to check if the maximum amount for entertainment expenses has been exceeded for a business partner who is listed in the additional receipt information of an expense receipt.

The BAdI ensures compliance with statutory rules, such as those prescribed for expense reporting in the United States by the Sarbanes-Oxley Act. One application of these rules is the limitation of entertainment expenses of a pharmaceutical company for business partners that are health care providers.

The BAdI contains the following methods:

  • TRIP_RECEIPT_AMOUNT
The system executes this method when a user enters a business partner in the additional receipt information on the Participants tab page.
You can use this method to check whether the sum of entertainment expenses for the specified business partner exceeds a maximum value.
We recommend that you copy the example class implementation TRIP_AMOUNT_BU_PARTNER_EXAMPLE and tailor your copy to meet your requirements (see below).

The BAdI is valid for (a) the transactions of the Travel Expense Report in SAP GUI (PR01, PR02, PR04, PR05, but not TRIP or TP01) and (b) the Expense Report and the Express Expense Sheet in the Web Dynpro ABAP-based user interface.

You have made your settings for business partners in Customizing for Cross-Application Components under SAP Business Partners, and you have defined a business partner role, for example, for health care providers. You have assigned this role to the appropriate business partners (for example, using transaction BUP1 or BUP2).

We recommend users (such as your field sales representatives) assign this business partner role to the BPO parameter in the SAP system under System-> User Profile-> Own Data on the Parameters tab. This setting simplifies the searching of business partners when entering the participants in the additional receipt information of expense receipts.

You have made the following settings in the activity Field Control for Additional Receipt Information:

  • For the Participants field you selected Requiredor Optional.
This enables users to enter the participants in the additional receipt information.
  • For the Options for Entering Business Partners you enabled the entry of business partners.
This enables users to enter business partners as participants in the additional receipt information.

In the standard system, there is no activated BAdI implementation.

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

This BAdI uses the interface IF_TRIP_RECEIPT_AMOUNT. For more information, display the interface in the Class Builder.

In the example class implementation TRIP_AMOUNT_BU_PARTNER_EXAMPLE, the BAdI reads a table with the maximum amounts for entertainment expenses for business partners. You need to define these amounts. Alternatively, you can define the maximum amounts in the BAdI implementation itself.

In all expense reports of the current fiscal year, the BAdI searches for receipts that contain the business partner that a user has entered as a participant and checks if the business partner is declared as a participant in that receipt. If this is the case, the system calculates the business partner's share of the entertainment expenses and adds this to the proportionate entertainment expenses of the current receipt.

The BAdI compares the accumulated sum of entertainment expenses for the business partner with the maximum amount and issues a message as per the result of the comparison.






ABAP Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 5221 Date: 20240523 Time: 170542     sap01-206 ( 140 ms )