Oracle ERP Testing Tool > Test Library > Financials > Intercompany

Syntra Standard Oracle Test Library

Oracle Fusion Intercompany Exception Test Cases

Validate expected Oracle Fusion behavior when intercompany transactions, approvals or accounting fail to satisfy entity, accounting, period/currency, workflow or data requirements, and confirm each exception is correctly detected and classified rather than silently accepted.

Test ID	ORCL.R2R.IC.EXCEPTION
Application	Oracle Fusion Cloud
Product	Financials
Module	Intercompany
Process	Intercompany Transactions
Business Flow	Record-to-Report
Scenario Type	Negative / Exception Handling
Test Usage	Functional Testing / Regression Testing / Exception Classification
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 30 underlying Oracle Fusion UI actions to complete it.

Test Objective

Validate expected Oracle behavior when intercompany data, balancing, configuration or workflow requirements are not satisfied.

The scenario should confirm that:

the deliberately invalid entity, accounting, period/currency, workflow or data condition is correctly rejected rather than silently accepted
the resulting exception, error or validation message matches the expected classification for the condition triggered
the exception occurs at the correct lifecycle stage — creation, approval or accounting
the resulting transaction status correctly reflects the unresolved exception
evidence is captured to support the exception classification
a likely root-cause category and recommended corrective action can be recorded

This scenario does not attempt to certify a specific Oracle application defect. Where an exception appears unexpected or its cause is unclear, it is treated as requiring further investigation and supporting evidence rather than a confirmed conclusion.

When to Use This Test

Functional testing of intercompany exception handling for a new Oracle Fusion implementation
Regression testing of entity, accounting, period/currency, workflow and data validations after an Oracle quarterly update
UAT sign-off for intercompany controls that must correctly reject invalid conditions
Baseline case referenced by the create, approval and accounting scenarios within the same intercompany lifecycle

Where This Test Fits in the Intercompany Lifecycle

Create

→

Approval

→

Exceptions

→

Accounting

This test covers exception conditions that can arise while an intercompany transaction is created, approved or accounted for — it does not create or approve a transaction under normal conditions, and it does not perform the accounting itself. Actual exception triggers and messages depend on the customer's intercompany configuration.

← Previous Stage

Intercompany Approval

Next Stage →

Intercompany Accounting

Preconditions

Oracle Fusion Intercompany access is available to the test user.
Intercompany provider and receiver organizations are configured for the test tenant.
The test user, or Syntra DataVault, can reproduce or observe exception conditions across entity, accounting, period/currency, workflow and data dimensions.
A representative intercompany transaction, approval or accounting event exists that can be placed into an exception condition.
Test data required to trigger each exception category — invalid entity, invalid account, closed period, missing approver, unbalanced amount and similar conditions — is available or can be constructed.

Exact exception triggers, messages and classifications may vary by Oracle Fusion implementation, security configuration and intercompany setup.

Sample Test Data

Exception Category	Entity / Accounting / Period-Currency / Workflow / Data
Provider Organization	${PROVIDER_ORG}
Receiver Organization	${RECEIVER_ORG}
Expected Exception Type	${EXPECTED_EXCEPTION_TYPE}

Sample values are illustrative. Actual exception triggers, messages and codes depend on the target Oracle Fusion environment and its intercompany configuration.

Test Steps

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

#	User Action	Expected Result
1	Navigate to Intercompany Navigate to the Oracle Fusion Intercompany work area.	The Intercompany work area opens successfully.
2	Trigger the Exception Condition Create, approve or account for an intercompany transaction that deliberately carries the exception condition under test. ${EXCEPTION_CATEGORY} / ${PROVIDER_ORG} / ${RECEIVER_ORG} This single business step replaces multiple technical actions such as opening the create, approval or accounting screen, entering the deliberately invalid value and submitting.	Oracle Fusion processes the transaction against the exception condition rather than silently accepting it.
3	Observe the Resulting Exception Observe the exception, error or validation message returned by Oracle Fusion at the point the condition is triggered.	An exception, error or validation message is displayed or logged at the correct lifecycle stage — create, approval or accounting.
4	Review the Exception Category and Message Review the exact exception message text and the category it falls under. ${EXPECTED_EXCEPTION_TYPE}	The exception message text and category are captured for comparison against the expected classification.
5	Verify the Exception Maps to the Expected Classification Compare the observed exception against the expected classification for this scenario — Entity, Accounting, Period/Currency, Workflow or Data.	The observed exception matches the expected classification for the triggered condition.
6	Review Evidence Captured for the Exception Review the evidence captured for the exception, including the transaction reference, screen state and message detail.	Evidence is available to support the exception classification for later review.
7	Determine Likely Root-Cause Category Assess whether the exception is most consistent with a data, configuration, security, workflow or application-level root cause. SyntraFlow's failure classification distinguishes data, configuration, security, automation, application, environment and expected-validation causes — for example, an invalid receiver relationship typically points to a data or configuration issue, a missing balancing rule typically points to a configuration issue, and a failed approval routing typically points to an approval configuration or security issue. A possible Oracle application defect is never classified with certainty without supporting evidence.	A likely root-cause category is identified based on available evidence. Where the evidence does not clearly point to a specific cause, the exception is flagged for further investigation rather than attributed with certainty.
8	Record Recommended Corrective Action Record the recommended corrective action for the exception category — for example, correct the entity relationship, fix the account combination, open the period, add an approver, or correct the amount.	A recommended corrective action is recorded against the exception.
9	Confirm the Exception Does Not Silently PassBusiness assertion Confirm that the exception condition was not silently accepted or bypassed by Oracle Fusion.	The transaction did not complete as though the exception condition did not exist.
10	Confirm Transaction Status Correctly Reflects the ExceptionBusiness assertion Confirm that the resulting transaction status — for example Incomplete, Rejected, Error or Held — correctly reflects the unresolved exception. This is the main business assertion for the scenario — a correctly detected exception is a passing test, not a failure.	Transaction status accurately reflects the exception rather than indicating successful completion.

Expected Results

Each exception condition produces the expected Oracle Fusion error or validation message.
The exception is produced at the correct lifecycle stage — creation, approval or accounting.
The exception message and category match the expected classification for the triggered condition.
Transaction status correctly reflects the unresolved exception rather than silently succeeding.
Evidence is captured to support the exception classification.
A likely root-cause category and recommended corrective action are recorded.

Key Validation Checkpoints

Exception is triggered under the intended condition.
Exception message and category match the expected classification.
Exception occurs at the correct lifecycle stage (create, approval or accounting).
Transaction status reflects the exception rather than false completion.
Evidence is captured for the exception.
Root-cause category and corrective action are recorded.
Exception does not silently pass or get bypassed.
Unrelated valid transactions are not blocked by the exception condition.

Core Business Scenario

Intercompany Exceptions

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 exception scenario. Jarvis AI can extend this scenario by generating additional exception variations across entity, accounting, period/currency, workflow and data conditions using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually construct dozens of near-identical exception scenarios to cover every invalid entity, account, period, currency, approval or data condition. Jarvis uses the standard exception scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable intercompany exception scenario and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for exception scenario generation — Provider and Receiver Organizations, Ledgers, Accounts, Currencies and Approval context.

Jarvis AI

Analyses the standard exception scenario together with available test data and generates relevant category-specific variations.

Positive + Negative Test Variations

Correctly-detected exception scenarios and edge cases where detection or classification may be incomplete.

Regression Pack

Selected exception 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 exception classification.

Rather than maintaining a separate test for every possible intercompany exception condition, SyntraFlow maintains one core exception scenario and allows Jarvis AI to generate category-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Intercompany Exceptions 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

Invalid receiver correctly detected
Inactive entity correctly detected
Balancing-rule failure correctly detected
Invalid receivable account correctly detected
Closed period correctly detected
Invalid currency correctly detected
Missing approver correctly detected
Rejected transaction correctly detected
Out-of-balance amounts correctly detected
Missing transaction type correctly detected

Negative Scenarios

Exception silently ignored instead of blocking the transaction
Exception detected but misclassified into the wrong category
Exception condition blocks an unrelated valid transaction
Exception recovery leaves related balances in an inconsistent state
Exception detected but transaction status does not reflect it

These are representative examples only. Exception triggers, messages and classifications can depend on the customer's Oracle Fusion configuration, controls and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely represents every entity, account, period, currency and approval condition in a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct exception scenarios relevant to the customer's actual implementation across all five exception category groups.

Standard Library Definition

Exception Category   ${EXCEPTION_CATEGORY}
Provider Org         ${PROVIDER_ORG}
Receiver Org         ${RECEIVER_ORG}
Ledger               ${LEDGER}
Account              ${ACCOUNT}
Currency             ${CURRENCY}
Approval Context     ${APPROVAL_CONTEXT}
Expected Exception   ${EXPECTED_EXCEPTION_TYPE}

DataVault

Organizations
  Provider / Receiver combinations
Ledgers
  Configured ledgers per Business Unit
Accounts
  Valid and deliberately invalid combinations
Currencies
  USD, GBP, EUR + unconfigured pairs
Approval Context
  Approver hierarchies and routing rules

Jarvis AI Generates

Scenario 01 — Invalid Receiver Organization
Scenario 02 — Inactive Provider Entity
Scenario 03 — Balancing Rule Failure
Scenario 04 — Invalid Receivable Account
Scenario 05 — Closed Period
Scenario 06 — Missing Approver
...

Customer-specific test data and AI-generated exception variations are not published to the Syntra Standard Test Library. Where DataVault is connected, customer-specific dimensions such as organizations, accounts and approval context remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Representative examples of intercompany exception scenarios Jarvis can generate from this business scenario, spanning entity, accounting, period, currency, workflow and data conditions. 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	Invalid Provider Organization	Entity	Provider organization reference does not exist or is invalid	Syntra Ready
VAR-002	Invalid Receiver Organization	Entity	Receiver organization reference does not exist or is invalid	Syntra Ready
VAR-003	Inactive Provider Entity	Entity	Provider organization is inactive	Syntra Ready
VAR-004	Inactive Receiver Entity	Entity	Receiver organization is inactive	Syntra Ready
VAR-005	Unsupported Intercompany Relationship	Entity	Provider/receiver relationship is not defined or supported	Syntra Ready
VAR-006	Invalid Intercompany Receivable Account	Accounting	Receivable account combination fails validation	Syntra Ready
VAR-007	Invalid Intercompany Payable Account	Accounting	Payable account combination fails validation	Syntra Ready
VAR-008	Balancing Rule Failure	Accounting	Intercompany balancing rule is not satisfied	Syntra Ready
VAR-009	Invalid Accounting Segment	Accounting	One or more accounting flexfield segments are invalid	Syntra Ready
VAR-010	Invalid Ledger Reference	Accounting	Referenced ledger is not valid for the transaction	Syntra Ready
VAR-011	Closed Accounting Period	Period	Transaction date falls within a closed accounting period	Syntra Ready
VAR-012	Invalid Transaction Date	Period	Transaction date is outside a valid or open range	Syntra Ready
VAR-013	Invalid Currency Code	Currency	Currency code is not configured or not valid for the transaction	Syntra Ready
VAR-014	Missing Exchange Rate	Currency/Period	Required exchange rate is not available for the transaction date	Syntra Ready
VAR-015	Currency Mismatch Between Provider and Receiver	Currency	Provider and receiver currencies are inconsistent with configuration	Syntra Ready
VAR-016	Missing Approver	Workflow	No approver is configured for the approval rule	Syntra Ready
VAR-017	Rejected Intercompany Transaction	Workflow	Transaction is rejected during the approval stage	Syntra Ready
VAR-018	Incomplete Approval Chain	Workflow	Approval chain does not reach a final decision	Syntra Ready
VAR-019	Approval Routed to Inactive Approver	Workflow/Entity	Approval is routed to an approver who is no longer active	Syntra Ready
VAR-020	Approval Escalation Not Configured	Workflow	No escalation path exists when approval is not actioned	Syntra Ready
VAR-021	Missing Transaction Amount	Data	Required transaction amount is not entered	Syntra Ready
VAR-022	Out-of-Balance Debit and Credit Amounts	Data	Debit and credit amounts do not net to zero	Syntra Ready
VAR-023	Missing Transaction Type	Data	Required intercompany transaction type is not selected	Syntra Ready
VAR-024	Duplicate Transaction Reference	Data	Transaction reference matches an existing transaction	Syntra Ready

Why a Detected Exception Can Be a Passing Test

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion correctly enforces its intercompany validations when entity, accounting, period, currency, workflow or data conditions are not satisfied.

Invalid Receiver Organization + Undefined Relationship → Expected Relationship Validation Displayed

Negative Testing

Jarvis can also generate edge-case scenarios that stress-test whether an exception is detected, classified and reflected correctly at all — these surface potential gaps in Oracle's exception handling rather than confirm it.

Exception Silently Ignored → Transaction Should Have Been Blocked (potential defect requiring investigation)
Exception Detected but Misclassified → Wrong Category Assigned
Exception Condition Blocks an Unrelated Valid Transaction
Exception Recovery Leaves Related Balances in an Inconsistent State

A scenario PASSES when Oracle correctly detects the intended exception. A test is not marked as failed simply because Oracle rejected or flagged the transaction — it fails only when Oracle does not behave as expected.

Scenario	Oracle Outcome	Test Result
Invalid receiver	Validation occurs	PASS
Closed period	Period validation occurs	PASS
Unbalanced transaction	Balancing validation occurs	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

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

Intercompany Exception Regression Pack

Invalid Receiver Organization
Inactive Provider Entity
Balancing Rule Failure
Invalid Receivable Account
Closed Accounting Period
Invalid Currency Code
Missing Approver
Rejected Intercompany Transaction
Out-of-Balance Amounts
Missing Transaction Type

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 exception scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected exception 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 Exception Regression Pack
Schedule	Quarterly Update Regression
Tests	24 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

112

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 exception scenario, available DataVault test data and expected business outcomes to generate additional exception coverage for the customer's environment.

Generate

Positive and negative exception 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 Exceptions, 10 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

Jarvis AI — Generate Category-Specific Exception 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

Trigger the Exception Condition

May internally include

Open Create/Approve/Account Screen → Enter Deliberately Invalid Value → Submit → Capture Response

Business Step

Review the Exception Category and Message

May internally include

Open Message Detail → Capture Exception Text → Capture Exception Code → Map to Category

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 exception was correctly classified — 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
Trigger the Exception Condition	Pass	—
Observe the Resulting Exception	Pass	—
Confirm Transaction Status Correctly Reflects the Exception	Pass	Pass

Related Intercompany Tests

Exception handling is one stage of the same intercompany lifecycle — explore the related create, approval and accounting scenarios below.

Create Intercompany Transaction Intercompany Approval Intercompany Accounting

Turn This Standard Test into Your Oracle Intercompany Regression Suite

Start with the Syntra Standard intercompany exception test, use DataVault to provide environment-specific test data, let Jarvis generate additional category-specific exception 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 Record-to-Report Testing Tool Syntra DataVault DataVault Data Masking

Frequently Asked Questions

Does a detected exception mean the test failed?

No. A scenario PASSES when Oracle correctly detects the intended exception — for example, rejecting an invalid receiver, a closed period or an out-of-balance transaction. The test only fails if Oracle does not behave as expected, such as silently accepting an invalid condition.

What exception categories are covered by this test?

Entity/Organization (invalid provider, invalid receiver, inactive entity, unsupported relationship), Accounting (invalid receivable or payable account, balancing-rule failure, invalid segment, invalid ledger), Period/Currency (closed period, invalid transaction date, invalid currency, missing exchange rate), Workflow (missing approver, rejected transaction, incomplete approval) and Data (missing amount, out-of-balance amounts, missing transaction type, duplicate reference).

Does this test determine the root cause of an exception with certainty?

No. The scenario records a likely root-cause category — data, configuration, security, workflow or application — based on available evidence. Where the evidence does not clearly point to a specific cause, or a possible Oracle application defect is suspected, further investigation is recommended rather than a definitive conclusion.

How are the many intercompany exception variations generated?

Jarvis AI uses this standard exception scenario together with available DataVault test data — provider and receiver organizations, ledgers, accounts, currencies and approval context — to generate relevant variations across all five exception category groups for the customer's environment.

Can this exception test case be scheduled?

Yes. Selected exception variations can be grouped into a regression pack and scheduled for on-demand or unattended batch execution.

Does this test use real customer data?

The public Syntra Standard Test Library uses illustrative test data. Where DataVault is connected, customer-specific dimensions such as organizations, accounts, currencies and approval context can be used, protected according to DataVault's data policies.