Overview of COA in OpenText Maintenance of Chart of Authority In VIM we use COA for the level based approval. It is used in NON-PO based document type and for PO based invoices baseline implementation identifies the requester of the PO as the first and only approver. Basically COA provides a single interface where the combination of approvers, approval limits and coder are maintained for the Invoice approval process. Use TCODE -/OPT/AR_COA We have 4 Tabs within COA. User details Approval Limits/Level COA Details Coder Settings User Details We use substitutes management utility for adding substitute to USER so that in absence of present user it can be approved by its substitute. Approval Limits/Level Parameters 1.Company code 2.Approval Level 3.Expense type of invoices 4.Description 5.Amount Limit 6.Approval Category 7.Additional Amount COA Details: It Enables to assign cost center to the user. Coder Settings : It helps to maintain the code for the subsequent AFS ID.
BADI is Business Add-Ins which is a new enhancement approach. BADI completely follows Object oriented methodology of class and methods which makes it faster. The main advantage of having BADI over USER-EXIT is we can have multiple implementation and each implementation is restricted with filters criteria. What are the different types of BADI in SAP? 1.Single use BADI The badi which is having one active implementation is called single use badi. 2.Multi use BADI The badi which is having multiple implementation is called multi used badi. For multi used badi there is no sequence in which the implementation is called. 3.Filter BADI The BADI which is having multiple implemented can be restricted with filter criteria. We can define filter values for each implementation. For example we have a requirement to develop an application which used multiple plant. So in our exit we will define CASE for each and every plant and if some changes needed to be done for any plant we need to do intensive tes