Oracle ERP Testing Tool > Test Library > Financials > Intercompany

Syntra Standard Oracle Test Library

Oracle Fusion Intercompany Approval Test Cases

Validate approval, acceptance and workflow routing of intercompany transactions according to configured approval rules, using parameterised approval thresholds rather than fixed dollar amounts.

Test ID	ORCL.R2R.IC.APPROVAL
Application	Oracle Fusion Cloud
Product	Financials
Module	Intercompany
Process	Intercompany Transactions
Business Flow	Record-to-Report
Scenario Type	Positive / Functional
Test Usage	Functional Testing / Regression Testing / UAT
Priority	High
Automation	SyntraFlow Ready
Library	Syntra Standard

Note on test design: SyntraFlow executes the detailed Oracle Fusion UI interactions automatically while presenting the scenario as business-readable test steps for documentation, review and reporting. This scenario is presented as 10 business-readable test steps; SyntraFlow's automation executes approximately 33 underlying Oracle Fusion UI actions to complete it.

Test Objective

Validate approval, acceptance and workflow routing of intercompany transactions according to configured rules — including how transactions are routed to the correct approver, how approve, reject and reassign actions update transaction status, and how rejected transactions can be corrected and resubmitted.

The scenario should confirm that:

a transaction awaiting approval is correctly identified and can be submitted into the approval workflow
the transaction routes to the correct approver based on the applicable rule (amount, entity, or provider/receiver context)
single-level and multi-level approval hierarchies are enforced as configured
provider approval and receiver acceptance are enforced where configured
approve, reject and reassign actions are correctly processed
transaction status updates accurately reflect the approval outcome
rejection reasons are captured and available to the transaction owner
rejected transactions can be corrected and resubmitted into the approval workflow
transactions requiring approval do not proceed to downstream accounting before approval is complete

This scenario does not claim that intercompany transaction creation, exception handling or accounting are covered — those are addressed by separate test scenarios in the Intercompany lifecycle.

When to Use This Test

Functional testing of a new Oracle Fusion Intercompany approval workflow implementation
Regression testing after an Oracle quarterly update
UAT sign-off for intercompany approval routing and provider/receiver acceptance
Baseline case referenced by intercompany create, exception and accounting scenarios within the same lifecycle

Where This Test Fits in the Intercompany Lifecycle

Create

→

Approval

→

Exceptions

→

Accounting

This test covers approval, acceptance and workflow routing of an intercompany transaction that has already been created, and is a prerequisite for downstream exception handling and accounting scenarios.

← Previous Stage

Create Intercompany Transaction

Next Stage →

Intercompany Exceptions

Preconditions

Oracle Fusion Intercompany access is configured and available for the test user.
An intercompany transaction has been created and is awaiting approval or acceptance.
Approval workflow and routing rules are configured for intercompany transactions.
Valid approvers are assigned for both the provider and receiver sides of the transaction.
The test user (or approver context) has permission to action Intercompany approvals.

Exact approval workflow configuration, routing rules, approval levels and approver assignments vary by Oracle Fusion implementation and security setup.

Sample Test Data

Transaction	Created intercompany transaction, status Awaiting Approval
Approval Rule Context	Amount-based, entity-based, or provider/receiver-based — scenario-defined
Approval Threshold	${APPROVAL_THRESHOLD} — customer-configured value, not a fixed amount
Approver	Valid approver assigned to the applicable rule and level
Approval Action	Approve / Reject / Reassign / Resubmit

Approval rules, routing hierarchies and approval thresholds are defined per Oracle Fusion customer implementation. This test intentionally uses ${APPROVAL_THRESHOLD} as a placeholder rather than a fixed dollar amount — actual threshold values should be sourced from DataVault or the customer's approval configuration, not hard-coded into the test.

Test Steps

10 business-readable steps. SyntraFlow's automation executes ~33 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.

#	User Action	Expected Result
1	Navigate to Intercompany Navigate to the Intercompany work area in Oracle Fusion.	The Intercompany work area opens successfully.
2	Locate the Transaction Awaiting Approval Search for and open the transaction that requires approval or acceptance. ${TRANSACTION} This single business step replaces multiple technical actions such as opening search, entering the transaction reference, clicking Search and selecting the result.	The correct transaction is located and its status confirms it is awaiting approval.
3	Submit for Approval Submit the transaction into the approval workflow where it is not already in the approval queue.	The transaction is accepted into the approval workflow.
4	Verify Routing to Expected Approver Confirm the transaction routes to the approver determined by the applicable approval rule. ${APPROVAL_RULE_CONTEXT}	The transaction routes to the correct approver based on the amount, entity, or provider/receiver rule in effect.
5	Sign In as Approver Sign in as the assigned approver, or switch approver context where testing a multi-level approval hierarchy. ${APPROVER}	The approver can access the transaction in their approval queue.
6	Review the Submitted Transaction Review the transaction details, amount and supporting information presented to the approver.	Transaction details are complete and available for review before an approval decision is made.
7	Take the Approval Action Approve, reject or reassign the transaction according to the scenario. ${APPROVAL_ACTION}	The selected action is accepted by Oracle Fusion without unexpected errors.
8	Verify Transaction Status UpdateBusiness assertion Confirm the transaction status updates to reflect the approval action taken. This is the main business assertion for the scenario — the test does not stop merely because the approval action was accepted successfully.	Transaction status accurately reflects the approval outcome — for example Approved, Rejected, or Pending Next-Level Approval — consistent with the configured routing rule.
9	Review Rejection Reason Where the transaction was rejected, review the rejection reason recorded against the transaction. Applicable to reject scenarios only — skipped for approve, reassign and auto-approved variations.	The rejection reason is captured and available to the transaction owner.
10	Resubmit Corrected Transaction Where applicable, correct the transaction and resubmit it into the approval workflow. Applicable only when correction and resubmission are required by the scenario.	The corrected transaction is successfully resubmitted and re-enters the approval workflow at the appropriate level.

Expected Results

Transactions requiring approval route correctly to the configured approver(s) based on the applicable rule (amount, entity, or provider/receiver context).
Single-level and multi-level approval hierarchies are enforced as configured.
Provider approval and receiver acceptance are enforced where configured.
Approve, reject and reassign actions correctly update transaction status.
Rejection reasons are captured and available to the transaction owner.
Rejected transactions can be corrected and resubmitted into the approval workflow.
Resubmitted transactions correctly re-enter the approval workflow at the appropriate level.
Transactions requiring approval do not proceed to downstream accounting before approval is complete.

Key Validation Checkpoints

Transaction status before approval matches Awaiting Approval.
Routing matches the configured approval rule (amount, entity, provider/receiver).
Assigned approver matches the expected approver for the rule and level.
Approval action (approve/reject/reassign) is correctly recorded.
Transaction status after the action matches the expected outcome.
Multi-level transactions correctly progress to the next approval level.
Rejection reason is captured when the transaction is rejected.
Downstream accounting is blocked until approval is complete.
Resubmitted transactions re-enter the approval workflow correctly.
Unauthorized approvers cannot action the transaction.

Core Business Scenario

Intercompany Approval

Business Steps

Test Variations

AI-Generated

Test Data

DataVault-Driven

Execution

On-Demand / Scheduled / Batch

Automation

SyntraFlow Ready

Jarvis AI

Go Beyond the Standard Test with Jarvis AI

The Syntra Standard Test Library defines the core intercompany approval business scenario. Jarvis AI can extend this scenario by generating additional positive and negative test variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually duplicate the same approval test dozens of times simply to cover different combinations of approval rule, approval level, provider/receiver context, and approve/reject/reassign outcomes. Jarvis uses the standard business scenario as the foundation and generates relevant variations for the customer's configured approval rules — including threshold-relative amounts, without assuming a fixed dollar value.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Approval Rules, Approval Thresholds, Approvers, Entities, Provider/Receiver relationships and other relevant test attributes.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant scenario variations.

Positive + Negative Test Variations

Positive, negative, boundary and configuration-specific scenarios.

Regression Pack

Selected variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

Execute immediately or schedule the regression pack for unattended batch execution.

Results + Evidence + Exceptions

Capture execution results, business assertions, screenshots/evidence and exceptions.

Rather than maintaining dozens of near-duplicate copies of the same approval test, SyntraFlow maintains the core business scenario and allows Jarvis AI to generate relevant variations using the customer's available approval configuration — including threshold-relative amounts sourced from DataVault or customer configuration, never a hard-coded dollar value.

AI-Generated Test Variations

The same Intercompany Approval business scenario can produce many test variations without creating separate public library pages. Below is a real slice of SyntraFlow's Build Scripts library, filtered to Intercompany.

Positive Scenarios

Auto-approved transaction
Single-level approval
Multi-level approval
Provider approval
Receiver acceptance
Amount-based routing
Entity-based routing
Approve transaction
Resubmit corrected transaction

Negative Scenarios

Reject transaction
Missing approver
Invalid routing
Unauthorized approver
Approval configuration issue
Approval-required transaction not approved
Attempt downstream processing before approval

These are representative examples only. Approval rules, approval thresholds and expected behavior depend on the customer's Oracle Fusion configuration — not every Oracle configuration behaves identically, and approval thresholds are never hard-coded; they are sourced from DataVault or the customer's configuration where available.

Generated Using Your DataVault Test Data

Generic test data cannot represent a real Oracle Fusion approval configuration. Where connected, Jarvis can use approved test data available through Syntra DataVault — approval rule context, approver, and amount relative to ${APPROVAL_THRESHOLD} — to create variations relevant to the customer's actual implementation, rather than assuming a fixed threshold value.

Standard Library Definition

Transaction              ${TRANSACTION}
Approval Rule Context    ${APPROVAL_RULE_CONTEXT}
Approval Threshold       ${APPROVAL_THRESHOLD}
Approver                 ${APPROVER}
Approval Action          ${APPROVAL_ACTION}

DataVault

Approval Rules
  Amount-Based
  Entity-Based
  Provider/Receiver-Based
Approval Thresholds
  Per customer configuration (not published)
Approvers
  Approver A (Level 1)
  Approver B (Level 2)
  Approver C (Provider)
  Approver D (Receiver)
Entities
  Entity A
  Entity B

Jarvis AI Generates

Scenario 01 — Amount Below Threshold + Single-Level + Approve
Scenario 02 — Amount Above Threshold + Multi-Level + Approve
Scenario 03 — Entity A + Provider Approval
Scenario 04 — Entity B + Receiver Acceptance
Scenario 05 — Reject at Level 1
Scenario 06 — Missing Approver Configuration
...

Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Approval configuration — including approval rules, routing hierarchies and approval thresholds — is customer-specific and, where DataVault is connected, is sourced from DataVault or the customer's own configuration rather than assumed by SyntraFlow.

Example Test Variations

Representative examples of scenarios Jarvis can generate from this business scenario. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.

ID	Variation	Type	Key Difference	Execution
VAR-001	Auto-Approved Transaction	Single-Level/Approve	Transaction meets auto-approval criteria; no manual approver action required	Syntra Ready
VAR-002	Single-Level Approval — Approve	Single-Level/Approve	One approval level required; approver approves the transaction	Syntra Ready
VAR-003	Single-Level Approval — Reject	Single-Level/Reject	One approval level required; approver rejects the transaction	Syntra Ready
VAR-004	Multi-Level Approval — Second Level Approve	Multi-Level/Approve	Transaction routes to a second-level approver per configured rule	Syntra Ready
VAR-005	Multi-Level Approval — Rejected at Second Level	Multi-Level/Reject	Second-level approver rejects an otherwise first-level-approved transaction	Syntra Ready
VAR-006	Provider Approval	Routing/Approve	Provider-side approval required before the transaction can proceed	Syntra Ready
VAR-007	Receiver Acceptance	Routing/Approve	Receiver-side acceptance required after provider approval	Syntra Ready
VAR-008	Amount-Based Routing — Below Threshold	Routing/Single-Level	Transaction amount below ${APPROVAL_THRESHOLD}; single-level approval applies	Syntra Ready
VAR-009	Amount-Based Routing — Above Threshold	Routing/Multi-Level	Transaction amount above ${APPROVAL_THRESHOLD}; routes to next approval level	Syntra Ready
VAR-010	Entity-Based Routing — Entity A	Routing/Approve	Routing determined by the entity-based rule configured for Entity A	Syntra Ready
VAR-011	Entity-Based Routing — Entity B	Routing/Approve	Routing determined by the entity-based rule configured for Entity B	Syntra Ready
VAR-012	Approve Transaction — Standard	Approve	Standard approve action on a transaction awaiting approval	Syntra Ready
VAR-013	Reassign Transaction	Routing/Approve	Approver reassigns the transaction to an alternate approver	Syntra Ready
VAR-014	Resubmit Corrected Transaction	Approve	Rejected transaction is corrected and resubmitted into the approval workflow	Syntra Ready
VAR-015	Reject Transaction — Incorrect Amount	Reject	Approver rejects the transaction due to an incorrect amount	Syntra Ready
VAR-016	Reject Transaction — Missing Supporting Detail	Reject	Approver rejects the transaction due to missing supporting information	Syntra Ready
VAR-017	Missing Approver	Exception	No approver is configured or assigned for the applicable approval rule	Syntra Ready
VAR-018	Invalid Routing Configuration	Exception/Routing	Approval rule configuration produces no valid routing path for the transaction	Syntra Ready
VAR-019	Unauthorized Approver Attempt	Exception	A user without approval authority attempts to action the transaction	Syntra Ready
VAR-020	Approval Configuration Issue	Exception	Approval workflow configuration is incomplete or internally inconsistent	Syntra Ready
VAR-021	Approval-Required Transaction Not Approved	Exception	Transaction remains pending; required approval is never completed	Syntra Ready
VAR-022	Attempt Downstream Processing Before Approval	Exception	An attempt to process or account the transaction before approval is complete	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

Jarvis generates scenarios using combinations expected to successfully complete the intercompany approval business process.

Transaction Within ${APPROVAL_THRESHOLD} + Single Approver → Approved Correctly

Negative Testing

Jarvis can generate scenarios designed to exercise Oracle's approval validations, routing rules and access controls around intercompany approval.

Unauthorized Approver Attempt → Expected Access Validation
Missing Approver Configuration → Expected Routing Failure
Attempt Downstream Processing Before Approval → Expected Block

A negative or exception test should not be marked as failed simply because Oracle blocks the action. If Oracle correctly enforces the approval rule — for example blocking downstream processing before approval is complete — the negative test has passed.

Scenario	Oracle Outcome	Test Result
Transaction within threshold, single approver	Approved correctly	PASS
Transaction exceeding threshold	Routes to next-level approver as expected	PASS
Attempt downstream processing before approval	Correctly blocked	PASS
Unexpected routing or processor error	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated scenarios and group them into reusable execution packs.

Intercompany Approval Regression Pack

Auto-Approved Transaction
Single-Level Approval — Approve
Multi-Level Approval — Second Level Approve
Provider Approval
Receiver Acceptance
Amount-Based Routing — Above Threshold
Entity-Based Routing — Entity A
Resubmit Corrected Transaction
Missing Approver
Attempt Downstream Processing Before Approval

Add Selected to Regression Pack(coming soon)Run Now(coming soon)Schedule(coming soon)

Run On-Demand or Schedule Automated Batch Execution

SyntraFlow can execute selected scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected scenarios unattended and records the outcome of each test and business assertion.

Run immediatelyNightly regressionWeekly regressionBefore releaseAfter configuration changesAfter environment refreshQuarterly Oracle update testingPre-UAT validation

Pack	Intercompany Approval Regression Pack
Schedule	Quarterly Update Regression
Tests	22 scenarios
Execution	Batch Mode
Start	10:00 PM
Environment	Oracle Fusion TEST
Status	Scheduled

Illustrative example — not a live schedule.

Review Results Across the Entire Test Pack

Users can drill from the regression pack into a scenario, its business steps, the underlying automation actions, and the evidence captured for each.

Illustrative example data — not actual production metrics.

Total Scenarios

Passed

Failed

Exceptions

Positive Tests

Negative Tests

Business Assertions

Regression Pack → Scenario → Business Step → Automation Action → Evidence

Intercompany Lifecycle

Actual workflow depends on customer intercompany configuration. Stages link to the corresponding test scenario family.

Create→

Approval

→Exceptions→Accounting

Understand Why a Test Failed

SyntraFlow execution evidence can help distinguish business-data failures, configuration issues, automation problems and potential application defects.

DataConfigurationSecurityAutomationApplicationEnvironmentExpected Validation

Jarvis Failure Intelligence — Coming Soon

From Business Scenario to Execution Evidence

Business teams get readable test documentation; automation teams retain detailed execution traceability.

Standard Business Scenario

AI-Generated Variation

Regression Pack

Business Test Step

Automation Actions

Business Assertion

Screenshot / Evidence

Execution Result

Meet Jarvis — SyntraFlow's AI Testing Engine

Jarvis extends the Syntra Standard Test Library by analysing the business scenario, available DataVault test data and expected business outcomes to generate additional test coverage for the customer's environment.

Generate

Positive and negative variations.

Parameterize

Use relevant test data from DataVault.

Assemble

Build reusable regression packs.

Execute

Run scenarios autonomously.

Schedule

Execute unattended test batches.

Validate

Evaluate expected business outcomes.

How SyntraFlow Automates This Test

The Standard Test defines the scenario; DataVault, Jarvis AI and SyntraFlow's execution engine take it from a single reusable business definition to executed, evidenced regression coverage.

Standard Library — Intercompany Approval, 10 Business Steps

↓

DataVault — Customer-Specific Approval Configuration

↓

Jarvis AI — Generate Positive + Negative Variations

↓

Regression Pack — Select Relevant Coverage

↓

SyntraFlow Execution — Each Variation

↓

Detailed UI Actions

↓

Business Assertions

↓

Evidence

↓

PASS / FAIL

Business Step → Underlying UI Actions

Business Step

Locate the Transaction Awaiting Approval

May internally include

Open Transaction Search → Focus Transaction Reference → Enter Reference → Search → Select Transaction → Confirm

Business Step

Take the Approval Action

May internally include

Open Approval Action Menu → Select Approve/Reject/Reassign → Enter Comments/Reason → Confirm Action

What SyntraFlow Captures Per Run

Parameterised input valuesReusable navigationAutomation action traceScreenshots / evidence captureExecution timingPass / fail statusBusiness assertionsEnvironment-independent test data

Action Status vs. Business Validation

A successful UI interaction does not automatically prove the business outcome — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution.

Step	Action Status	Business Validation
Take the Approval Action	Pass	—
Confirm Action Accepted	Pass	—
Verify Transaction Status Update	Pass	Pass

Related Intercompany Tests

Approval is one stage of the same Intercompany transaction lifecycle — explore the related creation, exception handling and accounting scenarios below.

Create Intercompany Transaction Intercompany Exceptions Intercompany Accounting

Turn This Standard Test into Your Oracle Intercompany Regression Suite

Start with the Syntra Standard intercompany approval test, use DataVault to provide environment-specific approval configuration, let Jarvis generate additional positive and negative variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore Intercompany Test Library

Use This Oracle Fusion Test Case

Download Test Case

Excel, CSV or JSON export.

Coming soon

Automate with SyntraFlow

Run this script against your own tenant today.

Related Oracle Testing Resources

Intercompany Test Library Oracle R2R Testing Tool Syntra DataVault DataVault Data Masking

Frequently Asked Questions

What does the Intercompany Approval test validate in Oracle Fusion?

It validates that transactions requiring approval route to the correct approver, that approve, reject and reassign actions correctly update transaction status, and that rejected transactions can be corrected and resubmitted into the approval workflow.

How are approval rules determined for intercompany transactions?

Approval rules are configured per Oracle Fusion customer implementation and can route transactions based on amount, entity, or provider/receiver context. This test scenario is designed against configured rules rather than assuming a single fixed routing behavior.

Does this test cover multi-level approval routing?

Yes. Both single-level approval and multi-level approval hierarchies are covered as variations of this scenario, including transactions that route to a next-level approver based on the applicable rule.

Can a transaction proceed to accounting before it is approved?

No — Oracle Fusion is expected to block downstream processing until required approval is complete. This test includes a negative scenario that confirms an attempt to process a transaction before approval is correctly blocked.

Does this test use a specific dollar-amount approval threshold?

No. Approval thresholds vary by Oracle Fusion implementation and customer configuration, so this test uses a parameterised placeholder (${APPROVAL_THRESHOLD}) rather than a hard-coded dollar amount. Actual threshold values are sourced from DataVault or the customer's approval configuration.

How are the many approval test variations generated, and can this be scheduled?

Jarvis AI uses this standard approval scenario together with available DataVault test data and configuration to generate relevant positive and negative variations. Selected variations can be grouped into a regression pack and scheduled for on-demand or unattended batch execution.