logo

Are you need IT Support Engineer? Free Consultant

Review and Approval: Authorization Checks

  • By Sanjay
  • 18/11/2026
  • 15 Views



Challenge with Authorization Checks

  • The object being processed is the purchase order item; however, reviewers and/or approvers are generally not purchasers and will not have authorization to display the purchase order itself
  • Different types of users perform review/approval (Purchase Order Owner, Controller, or G/L Accountant), each requiring specific authorization checks fitting their role

Implementation of Authorization Checks

  • Role-specific authorization checks are implemented in the review and approval transactions
  • Authorization checks are implemented as the default implementation of BAdI BADI_FACRA_AUTH_CHECK in ABAP class CL_BADI_FACRA_AUTH_CHECK
  • The default implementation can be replaced by a customer-defined implementation

Authorization Checks by User Role

  1. For Purchase Order Owners:
  • In review transaction FACRARVWBU, the purchase order owner is only allowed to review purchase order items where their UserID is entered as:
    • Goods recipient, OR
    • Requisitioner, OR
    • Creator
  • If defined as a substitute for another user in the workflow, they are also allowed to review the corresponding purchase order items of that user
  • Substitutes are defined in transaction SBWP menu: Settings → Workflow Settings → Edit Substitute (any substitution profile can be used)
  • Note: Workflow transaction SBWP is used for defining substitutes despite the workflow itself not being used for review by transactions FACRARVW*
  1. For Controllers:
  • The Controller must have CO reporting authorization for the cost object for which they started review transaction FACRARVWCO
  1. For G/L Accountants:
  • The G/L Accountant must have display authorization for the company code and/or business area for which they started approval transaction FACRAAPPRVGL

Balazs_Szauder_0-1794995831272.Png

Users processing data with the Accrual Engine must possess specific authorizations for three authorization objects (viewable in transaction SU21):

  1. F_ACES_DST – Accrual Engine in S4: Accrual Objects
  2. F_ACES_PST – Accrual Engine in S4: Accrual Postings
  3. F_ACES_PER – Accrual Engine in S4: Periodic Accrual Amounts

Additional Requirements for Reviewers and Approvers:

Reviewers and approvers must have these Accrual Engine-specific authorizations in addition to their user-role specific authorizations.

Authorization Checking Mechanism:

In review and approval transactions, authorizations for the F_ACES_PER authorization object are verified directly at the database level through the corresponding CDS view (DDL source), rather than at the ABAP runtime level.

Critical Troubleshooting Information:

If review/approval transactions fail to display records for a company code, the root cause is likely missing authorization for the F_ACES_PER authorization object. This missing authorization cannot be detected through transaction SU53 because the check occurs at the database level rather than during ABAP runtime execution.





Source link

Leave a Reply

Your email address will not be published. Required fields are marked *

Chat with us on WhatsApp!