Skip to content

Blog

Cross-Application SoD: Finding Risk Across Oracle ERP Cloud and Connected Systems

An employee has purchasing access in Oracle Fusion Cloud ERP and invoice-verification access in SAP. The Oracle owner approves one assignment; the SAP owner approves the other. Neither review establishes whether the employee’s combined authority violates the organization’s segregation-of-duties policy.

The gap sits between the applications. Each owner may understand the local access without seeing the responsibilities it creates across the business process.

Cross-application segregation of duties (SoD) assesses that combination. It links accounts to an identity, identifies the capabilities held in each system, and tests whether their relationship meets a defined conflict.

The worked example below follows one purchasing and invoice-verification conflict through identity matching, capability mapping, and scope. The analysis needs to explain more than where the person has accounts.

Within the wider Oracle Cloud ERP risk and control structure, this extends access assessment beyond Oracle while keeping decisions and corrective actions connected to the underlying systems.

Where application-by-application reviews leave a gap

Business processes often span several applications. Purchasing may begin in one system, invoice processing may occur in another, and payment activity may involve a treasury platform.

Access approvals usually follow application ownership. A reviewer can confirm a legitimate local requirement without knowing that another assignment gives the same person an incompatible responsibility elsewhere.

Job changes can widen that gap. An employee receives access for a new responsibility but retains an assignment in an application owned by a different team. Each assignment remains familiar to its local owner, even though the combination no longer fits the employee’s job.

Cross-application review brings those capabilities into one policy assessment. It still needs the application-specific detail: account relationships, permissions, restrictions, and relevant data scope.

What does a cross-application control need?

An integration establishes that data or instructions can move between systems. It does not establish that a particular conflict is being tested.

Capability What it establishes
Data collection Relevant accounts, assignments, privileges, or business records are available for analysis.
Identity correlation Accounts in different systems are linked to the identity being assessed.
Cross-application policy analysis Capabilities from different systems are evaluated against a defined conflict and its scope conditions.
Review and action routing A finding reaches an accountable owner, and an approved task reaches the appropriate executor.
Verification The resulting access is checked to establish whether the intended correction took effect.

A connector list helps identify potential coverage. A working control also needs validated mappings, sufficient source data, tested logic, and an accountable review process.

Inside the SafePaaS + Oracle ERP Architecture: Security Context and Data Flows explains the collection, analysis, and execution responsibilities behind that distinction.

Define the incompatible activities before mapping roles

“Oracle buyer plus SAP user” does not explain a conflict. The policy needs to identify the activities the organization separates and why their combination creates exposure.

It must also define any relevant conditions. These may concern purchasing organizations, business units, transaction populations, or another relationship within the process.

The technical mapping then identifies the permissions that enable each activity. A role may contain the capability, but its name is not sufficient evidence. The analysis should show how the account receives the permission, including inherited access and relevant restrictions.

This avoids treating every user with accounts in both systems as risky—or assuming that activities cannot conflict because they occur in different applications.

Purchasing in Oracle and invoice verification in SAP

Consider a hypothetical organization that uses Oracle Fusion Cloud ERP for purchasing and SAP ECC for part of its invoice processing.

Its policy prohibits the same person from creating purchase orders and performing the corresponding invoice-verification activity for the purchasing population in scope. An employee holds access associated with both activities.

That combination warrants analysis. To establish a finding, the team must confirm the identity, capabilities, and process relationship.

Confirm that the accounts belong to the same person

Use an authoritative identity record or validated account mapping to connect the Oracle and SAP accounts. A similar display name is not sufficient.

Retain the source identifiers and basis for the match. Investigate ambiguous relationships rather than silently merging accounts or excluding them from review.

Shared accounts need separate treatment because attributing their capabilities to one person may misrepresent who can use them.

Resolve the capability in each application

For the Oracle account, trace the relevant assignment and role hierarchy to the privilege permitting purchase-order creation.

For the SAP account, establish the authorizations permitting invoice verification, including relevant restrictions. Preserve SAP’s security structures rather than describing them in Oracle role terminology.

Retain both access paths and their evidence dates. Incomplete information on either side limits the conclusion.

Establish whether the scopes overlap

Determine whether the capabilities apply to the purchasing population covered by the policy.

Identical organizational labels do not prove overlap if they represent different populations. Different labels do not prove separation if they refer to the same business process.

Where the capabilities apply within the defined overlapping scope, the evidence supports inclusion. Where separation is demonstrated and overlap is a required condition, exclusion may be appropriate.

Check other accounts and assignments that could supply the missing overlap. If the relationship cannot be established, record the unresolved question rather than treat uncertainty as proof that no conflict exists.

Keep authorization separate from activity

The access finding concerns what the employee can do.

Transaction records may help establish whether both activities were performed or identify affected business records. They can support investigation and prioritization, but a lack of observed activity does not remove the underlying authorization.

Likewise, a conflict does not prove fraud or an improper transaction. It establishes that the defined separation of responsibilities is not maintained for the access and scope assessed.

Assign one owner for the combined finding

A cross-application finding can stall when each application team considers only its own assignment.

Assign an accountable business or control owner who can assess the combined responsibility, with input from both teams. The response may be to remove an unnecessary assignment, narrow its scope, allocate work differently, or retain a documented exception.

Choose the correction at the source of the problem. Redesigning a shared Oracle role may be unnecessary if one employee no longer needs an SAP assignment. Removing one account’s permission may also be insufficient if another account provides the same capability.

Oracle ERP Cloud role design and management explains the distinction between role redesign, assignment correction, and data-scope changes.

Keep exceptions distinguishable from corrections

Business need may explain why conflicting access exists; it does not make the finding false. An approved exception still needs an owner, conditions, and appropriate review, and should not be reported as removed access. Risk Signals vs Noise in Oracle Cloud ERP explains how false positives, mitigation, acceptance, and correction differ.

Verify the combined access after a correction

An administrator may confirm that an assignment was removed in one system. The review still needs to establish whether the conflicting combination remains.

Use updated evidence to examine the identity’s relevant accounts, access paths, and scope. Check whether another assignment or account continues to provide the capability.

Collection dates matter. A current Oracle extract combined with outdated SAP data may not support a conclusion about the corrected state.

If verification cannot confirm the intended result, keep the finding pending verification or return it for further action. Where an exception remains, retain the exposure and review conditions.

Oracle Cloud ERP risk-to-resolution explains the connection between implementation, verification, and closure.

Preserve the evidence behind the result

Another reviewer should be able to follow the finding without reconstructing its logic from separate exports.

Evidence What it explains
Policy definition and version Which activities conflict and under what conditions.
Identity and account mapping Why the accounts are assessed together.
Source-system access paths How each capability is granted.
Scope mapping Why the capabilities overlap—or why an exclusion applies.
Extraction dates and coverage Which state the analysis represents and its limitations.
Review decision What the owner concluded and why.
Action and verification records What changed and whether the combined exposure remains.

Changes to identity matching or scope exclusions also need validation. Test known applicable and inapplicable cases to confirm that the revised logic preserves genuine findings.

How SafePaaS supports cross-application SoD analysis

In the purchasing and invoice-verification example, SafePaaS cross-application rules management lets one rule select purchase-order creation from Oracle and invoice verification from SAP. The violation engine evaluates the rule across both data sources, even though Oracle roles and SAP authorizations have different structures, and produces a single cross-application finding for the employee.

The rule defines the two activities. Application-specific mappings define which Oracle privileges and SAP authorizations provide them, and the identity mapping connects both accounts to one person. A demonstration should show those three things, not only that both applications are connected.

The approved correction is made by an Oracle administrator, an SAP administrator, or an authorized connected workflow. The finding keeps the decision and action references, and the next analysis across both systems shows whether the combination remains.

See a cross-application conflict explained

Bring an Oracle ERP Cloud access scenario involving another business application.

Request a SafePaaS demo to examine how activities from different systems are evaluated in a cross-application rule, and discuss the identity, scope, data coverage, and verification required for your environment.

See governance applied to the access you have today

A working session with a governance specialist — not a slide presentation.

Book your tailored demo

Read next