Issue

The purpose of this document is to describe the Delegation of Authority (DOA) feature as it exists across the following platforms: SAP SuccessFactors, SAP Ariba, Salesforce, and Icertis. It outlines how each system implements DOA, including its core functionality, configuration options, limitations, and use cases.

Recommendation

Recommended approach is option A, i.e., DOA matrix and Framework in S4 HANA. 

Background & Context

Assumptions

Constraints

Impacts

Business Rules

Approval Process Principles

1. Approval Basis

   • Approval decisions are determined by the Master data object, like cost centre, WBS, and Business Partner, in the document requiring approval.

2. Final Approver

   • Each approval workflow task is routed directly to the Final approver identified in the Delegation of Authority (DOA) matrix.

   • The ultimate approver must be authorized to approve the entire transactional value within the relevant organizational boundary.

3. Single-Step Approval

   • The process will follow a single-step approval approach.

   • No multi-step approvals will be implemented to minimize potential delays.

4. Vacant Position Escalation

   • If the designated approver position is vacant, the system will automatically escalate the task to the next higher filled position in the organizational hierarchy.

5. Eligible Approvers

   • The approver may be:

     • A permanent Syensqo employee, or

     • A contingent worker, provided they are officially appointed to the relevant position in SAP SuccessFactors.

6. Task Centre
   • BTP Task Centre will be the central Inbox for all approvals from S4 Hana, Ariba, and iCertis.

Options considered

Option A: DOA matrix and Framework in S4 HANA

Option B: DOA matrix and Framework in BTP

Option C: DOA matrix and Framework in respective cloud applications 

Evaluation

	Option A	Option B	Option C
DOA Maintainance	Pro Con	Pro Pro	Pro Con
Intgeration	Pro Con	Con	Pro Pro
Employe Replication	Pro	Con	Con

See also

Change log