Kontakt

Ansicht
Dokumentation

EPIC_APPROVAL_CONTRO - BAdI: Approval Process Setup

EPIC_APPROVAL_CONTRO - BAdI: Approval Process Setup

General Material Data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Accounts Payable component. You can use this BAdI to set up an approval process for payment proposal items before the corresponding payment orders are created and the payments are sent to a bank for further processing.

This BAdI is called throughout such an approval process, which usually begins when a processor uses the Electronic Payment Integration functions to send an item from a payment proposal run for approval. This BAdI determines if the item can be released direct for payment (because the item amount is less than a threshold amount) or sent to another user for approval. If the item needs approval, the BAdI determines which users are possible approvers and which users are valid approvers for a certain approval level.

You have activated the Payment Release List (PRL) and the Electronic Payment Integration for China (EPIC) application for the PRL in Customizing. For more information, see Related Customizing for Electronic Payment Integration.

For more information about the standard settings (filters, single or multiple users) see the Enhancement Spot Element Definitionstab in the BAdI Builder (transaction SE18).

Electronic Payment Integration (China) allows you to implement a flexible approval process using this BAdI. Note that, to prevent inconsistencies, you can only activate one implementation of this BAdI in your system at one time.

If you use an approval process and then want to switch to a new implementation, ensure that all items that are currently in the approval process, that is, items with the Approval Pending status, have been approved (status is now Released for Payment) or rejected (status is Rejected) before you make the switch.

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.

You can find example implementations in the BAdI Builder on the Enhancement Spot Element Definitionstab in the Implementation Example Classessection.

The following example implementations are available:

  • CL_EPIC_APPR_CTRL_EXAMPLE_01,,Four-Eye Principle
In this implementation, an item must be approved twice, that is, it must pass through two approval levels, and the two approvers must be different users. There is no set sequence to the order in which the valid approvers approve the items. Note that items under a threshold amount (you determine the amount) can be released direct for payment; they require no approval.
  • CL_EPIC_APPR_CTRL_EXAMPLE_02,,Three-Tier Approach
In this implementation, the final approval level of an item that needs approval must be "3". The approval process has three tiers. Each tier has its own valid approvers (determined by the GET_TIER_ASSIGNMENTS method). In this method, approvers with different authorizations could be assigned to different tiers, that is, users that can only approve smaller amounts (you determine the amount) are assigned to Tier 1, users with the authorization to approve larger amounts are assigned to Tier 2, and users that can approve the largest amounts are assigned to Tier 3.
The amount of the item then determines which tiers it must pass through for approval, that is, which approvers can approve the item:
  • Items under a small threshold amount can be released direct for payment, they require no approval.

  • Items with an amount larger than the smallest threshold but under the next threshold amount must be approved by two approvers on Tier 1 and one approver on Tier 2.

  • Items larger than the second threshold amount must be approved by two approvers on Tier 2 and one approver on Tier 3.

When the approval level is "3", that is, three approvers (regardless of their tier) have approved the item, the BAdI sets the status of the item to "Released for Payment".

For more information about how these example implementations can be used, see the documentation in the SAP Library for SAP ERP under https://help.sap.com -> SAP ERP Central Component -> SAP ERP Central Component -> Financials -> Local Versions -> Asia-Pacific -> China -> Financial Accounting (FI) -> Accounts Payable (FI-AP) -> Electronic Payment Integration -> Examples: Approval Process Setup.

BAdI method documentation:






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 6178 Date: 20240523 Time: 215332     sap01-206 ( 208 ms )