Oracle Fusion Cloud

Sync audit history data from Oracle Fusion Cloud applications.

Overview
Setup Guide
Permissions
Troubleshooting

Connect Parable to Oracle Fusion Cloud to sync Payables and General Ledger (Ledger) audit history events. Parable queries the Oracle Fusion Cloud Audit REST service incrementally using 7-day date-range windows (UTC).

Warning: Data sensitivity: Audit payloads can include invoice and journal identifiers, internal IDs, user login names, and field-level attribute changes (amounts, vendors, accounts, and related financial metadata). Limit Parable access to users who are authorized to view Payables and General Ledger audit data in your organization.

Payables — Invoice Header

AP Invoice Header audit history (InvoiceHeaderVO) — creates, updates, and deletes

Payables — Invoice Line

AP Invoice Line audit history (InvoiceLineVO) — creates, updates, and deletes

Ledger — Journal Batch

GL Journal Batch audit history (JournalBatchVO) — creates, updates, and deletes

Ledger — Journal Header

GL Journal Header audit history (JournalHeaderVO) — creates, updates, and deletes

Ledger — Journal Line

GL Journal Line audit history (JournalLineVO) — creates, updates, and deletes

Data streams

This Provider Plugin defines 5 data streams.

Stream	Description	Sync
`audit_history_payables_invoice_header`	Retrieves Payables Invoice Header audit history events from Oracle Fusion Cloud. Captures create, update, and delete operations on AP Invoice Header objects (InvoiceHeaderVO). Syncs incrementally using 7-day date-range windows.	incremental
`audit_history_payables_invoice_line`	Retrieves Payables Invoice Line audit history events from Oracle Fusion Cloud. Captures create, update, and delete operations on AP Invoice Line objects (InvoiceLineVO). Syncs incrementally using 7-day date-range windows.	incremental
`audit_history_ledger_journal_batch`	Retrieves Ledger Journal Batch audit history events from Oracle Fusion Cloud. Captures create, update, and delete operations on GL Journal Batch objects (JournalBatchVO). Syncs incrementally using 7-day date-range windows.	incremental
`audit_history_ledger_journal_header`	Retrieves Ledger Journal Header audit history events from Oracle Fusion Cloud. Captures create, update, and delete operations on GL Journal Header objects (JournalHeaderVO). Syncs incrementally using 7-day date-range windows.	incremental
`audit_history_ledger_journal_line`	Retrieves Ledger Journal Line audit history events from Oracle Fusion Cloud. Captures create, update, and delete operations on GL Journal Line objects (JournalLineVO). Syncs incrementally using 7-day date-range windows.	incremental

Oracle Fusion Cloud

What You’ll Need

Credential	What it is
Username	Oracle Fusion Cloud username
Password	Oracle Fusion Cloud password
Base URL	Full base URL of your Oracle Fusion Cloud instance (e.g., `https://fa-exix-saasfaprod1.fa.ocs.oraclecloud.com`)

Info: Setup access in Oracle Fusion Cloud. These steps require Administrator, or a colleague with equivalent permissions who can create credentials for you. If that is not you, ask your Oracle Fusion Cloud administrator.

Oracle Fusion Cloud user with access to the Financials Audit REST service
The Financial Auditor or equivalent role that permits calling /fscmRestApi/fndAuditRESTService/audittrail/getaudithistory
Audit trail enabled for the Payables and Ledger products in Oracle Fusion Cloud

Step 1: Enable Audit Trail for Payables and Ledger

In Oracle Fusion Cloud, navigate to Setup and Maintenance → Manage Audit Policies.Enable audit for the Payables product and confirm the following business objects are checked:

Business Object	Internal Name
Invoice (Header)	`InvoiceHeaderVO`
Invoice Line	`InvoiceLineVO`

Enable audit for the Ledger product and confirm the following business objects are checked:

Business Object	Internal Name
Journal Batch	`JournalBatchVO`
Journal Header	`JournalHeaderVO`
Journal Line	`JournalLineVO`

Warning: If these objects are not enabled, Parable will receive empty results and no data will sync for that tap.

Step 2: Identify Your Instance Hostname

Your Oracle Fusion Cloud instance hostname looks like:

fa-exix-saasfaprod1.fa.ocs.oraclecloud.com

Find this in your browser address bar when logged into Oracle Fusion Cloud (without the https:// prefix).

Step 3: Create a Dedicated Integration User (Recommended)

For least-privilege access, create a dedicated integration user:

Navigate to Security Console → Users
Create a new user, e.g., parable_integration
Assign the Financial Auditor role (or a custom role granting read access to the Audit REST service)

Warning: Grant only the minimum roles required. The integration user only needs read access to the Audit REST service.

Step 4: Enter credentials in Parable

Enter the following in the Provider form:

Field	Value
Username	Your integration user username
Password	Your integration user password
Base URL	Full base URL of your instance (e.g., `https://fa-exix-saasfaprod1.fa.ocs.oraclecloud.com`)

Click Save & test connection.The Oracle Fusion Cloud Audit REST service requires a POST request with a JSON body. Pagination parameters must be on the URL query string (Oracle ignores pageNumber and pageSize in the JSON body). You can verify your credentials with curl:Payables (Invoice Header):

curl -X POST \
  "https://<your-fusion-host>/fscmRestApi/fndAuditRESTService/audittrail/getaudithistory?pageNumber=1&pageSize=5" \
  -H "Content-Type: application/json" \
  -u "<username>:<password>" \
  -d '{
    "product": "Payables",
    "businessObjectType": "oracle.apps.financials.payables.invoices.transactions.uiModel.view.InvoiceHeaderVO",
    "fromDate": "2026-01-01",
    "toDate": "2026-01-07",
    "timeZone": "UTC",
    "includeAttributes": true,
    "attributeDetailMode": true,
    "includeChildObjects": "true"
  }'

Ledger (Journal Batch):

curl -X POST \
  "https://<your-fusion-host>/fscmRestApi/fndAuditRESTService/audittrail/getaudithistory?pageNumber=1&pageSize=5" \
  -H "Content-Type: application/json" \
  -u "<username>:<password>" \
  -d '{
    "product": "Ledger",
    "businessObjectType": "oracle.apps.financials.generalLedger.journals.journalEntries.uiModel.view.JournalBatchVO",
    "fromDate": "2026-01-01",
    "toDate": "2026-01-07",
    "timeZone": "UTC",
    "includeAttributes": true,
    "attributeDetailMode": true,
    "includeChildObjects": "true"
  }'

Parable sends pageNumber and pageSize on the query string and caps each sync/backfill request to a 7-day fromDate/toDate window.A 200 OK response with "status": "SUCCESS" and an auditData array confirms your credentials and audit trail configuration are correct.

Success: Success! If you received a 200 OK response with valid data, your credentials are configured correctly. You can now configure this Provider in Parable.

Audit History Ledger Journal Batch

Developer identifier: audit_history_ledger_journal_batchAudit History Ledger Journal Batch contains ledger Journal Batch audit history events from Oracle Fusion Cloud. Captures create, update, and delete operations on GL Journal Batch objects (JournalBatchVO). Syncs incrementally using 7-day date-range windows.

Enables: trace create, update, and delete audit events for Oracle ledger journal batch objects across seven-day request windows.
Scope: Reads provider changes through POST /fscmRestApi/fndAuditRESTService/audittrail/getaudithistory using the declared incremental request boundary. Results contain only audit rows returned for the named Oracle business object to the configured account; it is not a full transaction extract.

Attribute

Developer identifier: audit_history_ledger_journal_batch.attributeAttribute records display name of the attribute that was changed. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact attribute value attached to each audit history ledger journal batch record record.
Interpretation: The provider supplies attribute at audit history ledger journal batch record granularity in the format stated by its description; omitted or redacted content remains unknown.

Attribute Details

Developer identifier: audit_history_ledger_journal_batch.attributeDetailsAttribute Details records array of attribute-level changes captured in the event. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded attribute details with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies attributeDetails on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Attribute Internal Name

Developer identifier: audit_history_ledger_journal_batch.attributeInternalNameAttribute Internal Name records internal name of the attribute that was changed. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact attribute internal name value attached to each audit history ledger journal batch record record.
Interpretation: The provider supplies attributeInternalName at audit history ledger journal batch record granularity in the format stated by its description; omitted or redacted content remains unknown.

Business Object

Developer identifier: audit_history_ledger_journal_batch.businessObjectBusiness Object states business object affected by the event (e.g. Journal Batch). It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal batch records by the exact provider-reported business object value when describing their recorded state.
Interpretation: The provider supplies businessObject per audit history ledger journal batch record record using its own state vocabulary; unknown and missing values must remain distinct.

Context Name1

Developer identifier: audit_history_ledger_journal_batch.contextName1Context Name1 records display name of the first context attribute for the change (returned when includeExtendedObjectIdentiferColumns is true). It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name1 value attached to each audit history ledger journal batch record record.
Interpretation: The provider supplies contextName1 at audit history ledger journal batch record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Name2

Developer identifier: audit_history_ledger_journal_batch.contextName2Context Name2 records display name of the second context attribute for the change. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name2 value attached to each audit history ledger journal batch record record.
Interpretation: The provider supplies contextName2 at audit history ledger journal batch record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Name3

Developer identifier: audit_history_ledger_journal_batch.contextName3Context Name3 records display name of the third context attribute for the change. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name3 value attached to each audit history ledger journal batch record record.
Interpretation: The provider supplies contextName3 at audit history ledger journal batch record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Value1

Developer identifier: audit_history_ledger_journal_batch.contextValue1Context Value1 records value of the first context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value1 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue1 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Context Value2

Developer identifier: audit_history_ledger_journal_batch.contextValue2Context Value2 records value of the second context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value2 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue2 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Context Value3

Developer identifier: audit_history_ledger_journal_batch.contextValue3Context Value3 records value of the third context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value3 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue3 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Date

Developer identifier: audit_history_ledger_journal_batch.dateDate records the timestamp of the audit event (yyyy-MM-dd HH:mm:ss). It anchors the named event or boundary on the record’s timeline.

Enables: place audit history ledger journal batch records on a timeline by date and select the records within an explicit reporting window.
Interpretation: The provider supplies date per audit history ledger journal batch record record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Description

Developer identifier: audit_history_ledger_journal_batch.descriptionDescription records human-readable description of the audit event. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact description value attached to each audit history ledger journal batch record record.
Interpretation: The provider supplies description at audit history ledger journal batch record granularity in the format stated by its description; omitted or redacted content remains unknown.

Description Internal

Developer identifier: audit_history_ledger_journal_batch.descriptionInternalDescription Internal identifies internal identifier of the affected object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal batch records to provider records that carry the same description internal, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies descriptionInternal as a record-level identifier on AuditHistoryLedgerJournalBatchRecord. It is not a uniqueness guarantee unless a connector directive says so.

Event Type

Developer identifier: audit_history_ledger_journal_batch.eventTypeEvent Type states type of audit event (e.g. Create, Object Data Update, Delete). It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal batch records by the exact provider-reported event type value when describing their recorded state.
Interpretation: The provider supplies eventType per audit history ledger journal batch record record using its own state vocabulary; unknown and missing values must remain distinct.

Developer identifier: audit_history_ledger_journal_batch.idID identifies synthetic primary key (SHA-1 hash of date, userInternalName, qualifiedBusinessObject, eventType, descriptionInternal, attributeInternalName, newValueId, newValue). It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same audit history ledger journal batch record source row before constructing its represented state.
Interpretation: Parable generates id at one value per audit history ledger journal batch record record, and x-transformDedupKey explicitly marks it as the record key.

Impersonator

Developer identifier: audit_history_ledger_journal_batch.impersonatorImpersonator records name of the impersonator when the action was performed under impersonation (returned when includeImpersonator is true). It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history ledger journal batch record record to the provider-reported person or account represented by impersonator.
Interpretation: The provider supplies impersonator as identity or attribution context on each audit history ledger journal batch record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

New Value

Developer identifier: audit_history_ledger_journal_batch.newValueNew Value records new value of the changed attribute. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded new value with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies newValue on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

New Value ID

Developer identifier: audit_history_ledger_journal_batch.newValueIdNew Value ID identifies internal ID of the new value, if the attribute references another object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal batch records to provider records that carry the same new value ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies newValueId as a record-level identifier on AuditHistoryLedgerJournalBatchRecord. It is not a uniqueness guarantee unless a connector directive says so.

Old Value

Developer identifier: audit_history_ledger_journal_batch.oldValueOld Value records prior value of the changed attribute before the audit event. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded old value with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies oldValue on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Old Value ID

Developer identifier: audit_history_ledger_journal_batch.oldValueIdOld Value ID identifies internal ID of the prior value, if the attribute references another object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal batch records to provider records that carry the same old value ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies oldValueId as a record-level identifier on AuditHistoryLedgerJournalBatchRecord. It is not a uniqueness guarantee unless a connector directive says so.

Qualified Business Object

Developer identifier: audit_history_ledger_journal_batch.qualifiedBusinessObjectQualified Business Object states fully qualified view object name of the business object. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal batch records by the exact provider-reported qualified business object value when describing their recorded state.
Interpretation: The provider supplies qualifiedBusinessObject per audit history ledger journal batch record record using its own state vocabulary; unknown and missing values must remain distinct.

User Internal Name

Developer identifier: audit_history_ledger_journal_batch.userInternalNameUser Internal Name records internal login name of the user who performed the action. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history ledger journal batch record record to the provider-reported actor represented by user internal name.
Interpretation: The provider supplies userInternalName as identity or attribution context on each audit history ledger journal batch record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

User Name

Developer identifier: audit_history_ledger_journal_batch.userNameUser Name records display name of the user who performed the action. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history ledger journal batch record record to the provider-reported actor represented by user name.
Interpretation: The provider supplies userName as identity or attribution context on each audit history ledger journal batch record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

Vo Foreign Key Map

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMapVo Foreign Key Map identifies map of view object foreign key values associated with the event. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal batch records to provider records that carry the same vo foreign key map, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies voForeignKeyMap as a record-level identifier on AuditHistoryLedgerJournalBatchRecord. It is not a uniqueness guarantee unless a connector directive says so.

Chart Of Accounts ID

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.ChartOfAccountsIdChart Of Accounts ID carries the source identifier named Chart Of Accounts ID for each audit history ledger journal batch record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal batch records to provider records that carry the same chart of accounts ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies ChartOfAccountsId as a record-level identifier on AuditHistoryLedgerJournalBatchRecord. It is not a uniqueness guarantee unless a connector directive says so.

Code Combination ID

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.CodeCombinationIdCode Combination ID carries the source identifier named Code Combination ID for each audit history ledger journal batch record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal batch records to provider records that carry the same code combination ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies CodeCombinationId as a record-level identifier on AuditHistoryLedgerJournalBatchRecord. It is not a uniqueness guarantee unless a connector directive says so.

Code Combination Id1

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.CodeCombinationId1Code Combination Id1 carries the source configuration value named Code Combination Id1 for each audit history ledger journal batch record row. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact code combination id1 when validating the configuration or technical definition of a audit history ledger journal batch record record.
Interpretation: The provider supplies CodeCombinationId1 as configuration or technical metadata on AuditHistoryLedgerJournalBatchRecord; consumers must preserve the exact syntax and documented vocabulary.

Conversion Type

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.ConversionTypeConversion Type carries the source state or classification named Conversion Type for each audit history ledger journal batch record row. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal batch records by the exact provider-reported conversion type value when describing their recorded state.
Interpretation: The provider supplies ConversionType per audit history ledger journal batch record record using its own state vocabulary; unknown and missing values must remain distinct.

Currency Code

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.CurrencyCodeCurrency Code carries the source currency code or label named Currency Code for each audit history ledger journal batch record row. It establishes the denomination used by companion financial amounts on the record.

Enables: interpret companion financial amounts on each audit history ledger journal batch record record in the source denomination named by currency code.
Interpretation: The source supplies CurrencyCode once per audit history ledger journal batch record record as its own currency code or label; Parable does not convert the associated amounts.

Currency Conversion Type

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.CurrencyConversionTypeCurrency Conversion Type carries the source state or classification named Currency Conversion Type for each audit history ledger journal batch record row. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal batch records by the exact provider-reported currency conversion type value when describing their recorded state.
Interpretation: The provider supplies CurrencyConversionType per audit history ledger journal batch record record using its own state vocabulary; unknown and missing values must remain distinct.

Entity Name

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.EntityNameEntity Name carries the source-authored value named Entity Name for each audit history ledger journal batch record row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact entity name value attached to each audit history ledger journal batch record record.
Interpretation: The provider supplies EntityName at audit history ledger journal batch record granularity in the format stated by its description; omitted or redacted content remains unknown.

Functional Currency Code

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.FunctionalCurrencyCodeFunctional Currency Code carries the source currency code or label named Functional Currency Code for each audit history ledger journal batch record row. It establishes the denomination used by companion financial amounts on the record.

Enables: interpret companion financial amounts on each audit history ledger journal batch record record in the source denomination named by functional currency code.
Interpretation: The source supplies FunctionalCurrencyCode once per audit history ledger journal batch record record as its own currency code or label; Parable does not convert the associated amounts.

Je Batch ID

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.JeBatchIdJe Batch ID carries the source identifier named Je Batch ID for each audit history ledger journal batch record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal batch records to provider records that carry the same je batch ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies JeBatchId as a record-level identifier on AuditHistoryLedgerJournalBatchRecord. It is not a uniqueness guarantee unless a connector directive says so.

Je Category

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.JeCategoryJe Category carries the source state or classification named Je Category for each audit history ledger journal batch record row. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal batch records by the exact provider-reported je category value when describing their recorded state.
Interpretation: The provider supplies JeCategory per audit history ledger journal batch record record using its own state vocabulary; unknown and missing values must remain distinct.

Ledger ID

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.LedgerIdLedger ID carries the source identifier named Ledger ID for each audit history ledger journal batch record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal batch records to provider records that carry the same ledger ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies LedgerId as a record-level identifier on AuditHistoryLedgerJournalBatchRecord. It is not a uniqueness guarantee unless a connector directive says so.

Ledgers Ledger ID

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.LedgersLedgerIdLedgers Ledger ID carries the source identifier named Ledgers Ledger ID for each audit history ledger journal batch record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal batch records to provider records that carry the same ledgers ledger ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies LedgersLedgerId as a record-level identifier on AuditHistoryLedgerJournalBatchRecord. It is not a uniqueness guarantee unless a connector directive says so.

Legal Entity ID

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.LegalEntityIdLegal Entity ID carries the source identifier named Legal Entity ID for each audit history ledger journal batch record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal batch records to provider records that carry the same legal entity ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies LegalEntityId as a record-level identifier on AuditHistoryLedgerJournalBatchRecord. It is not a uniqueness guarantee unless a connector directive says so.

Parent Je Header ID

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.ParentJeHeaderIdParent Je Header ID carries the source identifier named Parent Je Header ID for each audit history ledger journal batch record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal batch records to provider records that carry the same parent je header ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies ParentJeHeaderId as a record-level identifier on AuditHistoryLedgerJournalBatchRecord. It is not a uniqueness guarantee unless a connector directive says so.

Period Name

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.PeriodNamePeriod Name carries the source-authored value named Period Name for each audit history ledger journal batch record row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact period name value attached to each audit history ledger journal batch record record.
Interpretation: The provider supplies PeriodName at audit history ledger journal batch record granularity in the format stated by its description; omitted or redacted content remains unknown.

Tax Status Code

Developer identifier: audit_history_ledger_journal_batch.voForeignKeyMap.TaxStatusCodeTax Status Code carries the source state or classification named Tax Status Code for each audit history ledger journal batch record row. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal batch records by the exact provider-reported tax status code value when describing their recorded state.
Interpretation: The provider supplies TaxStatusCode per audit history ledger journal batch record record using its own state vocabulary; unknown and missing values must remain distinct.

Audit History Ledger Journal Header

Developer identifier: audit_history_ledger_journal_headerAudit History Ledger Journal Header contains ledger Journal Header audit history events from Oracle Fusion Cloud. Captures create, update, and delete operations on GL Journal Header objects (JournalHeaderVO). Syncs incrementally using 7-day date-range windows.

Enables: trace create, update, and delete audit events for Oracle ledger journal header objects across seven-day request windows.
Scope: Reads provider changes through POST /fscmRestApi/fndAuditRESTService/audittrail/getaudithistory using the declared incremental request boundary. Results contain only audit rows returned for the named Oracle business object to the configured account; it is not a full transaction extract.

Attribute

Developer identifier: audit_history_ledger_journal_header.attributeAttribute records display name of the attribute that was changed. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact attribute value attached to each audit history ledger journal header record record.
Interpretation: The provider supplies attribute at audit history ledger journal header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Attribute Details

Developer identifier: audit_history_ledger_journal_header.attributeDetailsAttribute Details records array of attribute-level changes captured in the event. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded attribute details with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies attributeDetails on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Attribute Internal Name

Developer identifier: audit_history_ledger_journal_header.attributeInternalNameAttribute Internal Name records internal name of the attribute that was changed. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact attribute internal name value attached to each audit history ledger journal header record record.
Interpretation: The provider supplies attributeInternalName at audit history ledger journal header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Business Object

Developer identifier: audit_history_ledger_journal_header.businessObjectBusiness Object states business object affected by the event (e.g. Journal Header). It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal header records by the exact provider-reported business object value when describing their recorded state.
Interpretation: The provider supplies businessObject per audit history ledger journal header record record using its own state vocabulary; unknown and missing values must remain distinct.

Context Name1

Developer identifier: audit_history_ledger_journal_header.contextName1Context Name1 records display name of the first context attribute for the change (returned when includeExtendedObjectIdentiferColumns is true). It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name1 value attached to each audit history ledger journal header record record.
Interpretation: The provider supplies contextName1 at audit history ledger journal header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Name2

Developer identifier: audit_history_ledger_journal_header.contextName2Context Name2 records display name of the second context attribute for the change. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name2 value attached to each audit history ledger journal header record record.
Interpretation: The provider supplies contextName2 at audit history ledger journal header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Name3

Developer identifier: audit_history_ledger_journal_header.contextName3Context Name3 records display name of the third context attribute for the change. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name3 value attached to each audit history ledger journal header record record.
Interpretation: The provider supplies contextName3 at audit history ledger journal header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Value1

Developer identifier: audit_history_ledger_journal_header.contextValue1Context Value1 records value of the first context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value1 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue1 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Context Value2

Developer identifier: audit_history_ledger_journal_header.contextValue2Context Value2 records value of the second context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value2 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue2 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Context Value3

Developer identifier: audit_history_ledger_journal_header.contextValue3Context Value3 records value of the third context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value3 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue3 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Date

Developer identifier: audit_history_ledger_journal_header.dateDate records the timestamp of the audit event (yyyy-MM-dd HH:mm:ss). It anchors the named event or boundary on the record’s timeline.

Enables: place audit history ledger journal header records on a timeline by date and select the records within an explicit reporting window.
Interpretation: The provider supplies date per audit history ledger journal header record record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Description

Developer identifier: audit_history_ledger_journal_header.descriptionDescription records human-readable description of the audit event. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact description value attached to each audit history ledger journal header record record.
Interpretation: The provider supplies description at audit history ledger journal header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Description Internal

Developer identifier: audit_history_ledger_journal_header.descriptionInternalDescription Internal identifies internal identifier of the affected object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal header records to provider records that carry the same description internal, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies descriptionInternal as a record-level identifier on AuditHistoryLedgerJournalHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Event Type

Developer identifier: audit_history_ledger_journal_header.eventTypeEvent Type states type of audit event (e.g. Create, Object Data Update, Delete). It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal header records by the exact provider-reported event type value when describing their recorded state.
Interpretation: The provider supplies eventType per audit history ledger journal header record record using its own state vocabulary; unknown and missing values must remain distinct.

Developer identifier: audit_history_ledger_journal_header.idID identifies synthetic primary key (SHA-1 hash of date, userInternalName, qualifiedBusinessObject, eventType, descriptionInternal, attributeInternalName, newValueId, newValue). It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same audit history ledger journal header record source row before constructing its represented state.
Interpretation: Parable generates id at one value per audit history ledger journal header record record, and x-transformDedupKey explicitly marks it as the record key.

Impersonator

Developer identifier: audit_history_ledger_journal_header.impersonatorImpersonator records name of the impersonator when the action was performed under impersonation (returned when includeImpersonator is true). It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history ledger journal header record record to the provider-reported person or account represented by impersonator.
Interpretation: The provider supplies impersonator as identity or attribution context on each audit history ledger journal header record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

New Value

Developer identifier: audit_history_ledger_journal_header.newValueNew Value records new value of the changed attribute. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded new value with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies newValue on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

New Value ID

Developer identifier: audit_history_ledger_journal_header.newValueIdNew Value ID identifies internal ID of the new value, if the attribute references another object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal header records to provider records that carry the same new value ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies newValueId as a record-level identifier on AuditHistoryLedgerJournalHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Old Value

Developer identifier: audit_history_ledger_journal_header.oldValueOld Value records prior value of the changed attribute before the audit event. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded old value with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies oldValue on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Old Value ID

Developer identifier: audit_history_ledger_journal_header.oldValueIdOld Value ID identifies internal ID of the prior value, if the attribute references another object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal header records to provider records that carry the same old value ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies oldValueId as a record-level identifier on AuditHistoryLedgerJournalHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Qualified Business Object

Developer identifier: audit_history_ledger_journal_header.qualifiedBusinessObjectQualified Business Object states fully qualified view object name of the business object. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal header records by the exact provider-reported qualified business object value when describing their recorded state.
Interpretation: The provider supplies qualifiedBusinessObject per audit history ledger journal header record record using its own state vocabulary; unknown and missing values must remain distinct.

User Internal Name

Developer identifier: audit_history_ledger_journal_header.userInternalNameUser Internal Name records internal login name of the user who performed the action. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history ledger journal header record record to the provider-reported actor represented by user internal name.
Interpretation: The provider supplies userInternalName as identity or attribution context on each audit history ledger journal header record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

User Name

Developer identifier: audit_history_ledger_journal_header.userNameUser Name records display name of the user who performed the action. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history ledger journal header record record to the provider-reported actor represented by user name.
Interpretation: The provider supplies userName as identity or attribution context on each audit history ledger journal header record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

Vo Foreign Key Map

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMapVo Foreign Key Map identifies map of view object foreign key values associated with the event. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal header records to provider records that carry the same vo foreign key map, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies voForeignKeyMap as a record-level identifier on AuditHistoryLedgerJournalHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Chart Of Accounts ID

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.ChartOfAccountsIdChart Of Accounts ID carries the source identifier named Chart Of Accounts ID for each audit history ledger journal header record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal header records to provider records that carry the same chart of accounts ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies ChartOfAccountsId as a record-level identifier on AuditHistoryLedgerJournalHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Code Combination ID

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.CodeCombinationIdCode Combination ID carries the source identifier named Code Combination ID for each audit history ledger journal header record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal header records to provider records that carry the same code combination ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies CodeCombinationId as a record-level identifier on AuditHistoryLedgerJournalHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Code Combination Id1

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.CodeCombinationId1Code Combination Id1 carries the source configuration value named Code Combination Id1 for each audit history ledger journal header record row. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact code combination id1 when validating the configuration or technical definition of a audit history ledger journal header record record.
Interpretation: The provider supplies CodeCombinationId1 as configuration or technical metadata on AuditHistoryLedgerJournalHeaderRecord; consumers must preserve the exact syntax and documented vocabulary.

Conversion Type

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.ConversionTypeConversion Type carries the source state or classification named Conversion Type for each audit history ledger journal header record row. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal header records by the exact provider-reported conversion type value when describing their recorded state.
Interpretation: The provider supplies ConversionType per audit history ledger journal header record record using its own state vocabulary; unknown and missing values must remain distinct.

Currency Code

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.CurrencyCodeCurrency Code carries the source currency code or label named Currency Code for each audit history ledger journal header record row. It establishes the denomination used by companion financial amounts on the record.

Enables: interpret companion financial amounts on each audit history ledger journal header record record in the source denomination named by currency code.
Interpretation: The source supplies CurrencyCode once per audit history ledger journal header record record as its own currency code or label; Parable does not convert the associated amounts.

Currency Conversion Type

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.CurrencyConversionTypeCurrency Conversion Type carries the source state or classification named Currency Conversion Type for each audit history ledger journal header record row. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal header records by the exact provider-reported currency conversion type value when describing their recorded state.
Interpretation: The provider supplies CurrencyConversionType per audit history ledger journal header record record using its own state vocabulary; unknown and missing values must remain distinct.

Entity Name

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.EntityNameEntity Name carries the source-authored value named Entity Name for each audit history ledger journal header record row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact entity name value attached to each audit history ledger journal header record record.
Interpretation: The provider supplies EntityName at audit history ledger journal header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Functional Currency Code

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.FunctionalCurrencyCodeFunctional Currency Code carries the source currency code or label named Functional Currency Code for each audit history ledger journal header record row. It establishes the denomination used by companion financial amounts on the record.

Enables: interpret companion financial amounts on each audit history ledger journal header record record in the source denomination named by functional currency code.
Interpretation: The source supplies FunctionalCurrencyCode once per audit history ledger journal header record record as its own currency code or label; Parable does not convert the associated amounts.

Je Batch ID

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.JeBatchIdJe Batch ID carries the source identifier named Je Batch ID for each audit history ledger journal header record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal header records to provider records that carry the same je batch ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies JeBatchId as a record-level identifier on AuditHistoryLedgerJournalHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Je Category

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.JeCategoryJe Category carries the source state or classification named Je Category for each audit history ledger journal header record row. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal header records by the exact provider-reported je category value when describing their recorded state.
Interpretation: The provider supplies JeCategory per audit history ledger journal header record record using its own state vocabulary; unknown and missing values must remain distinct.

Ledger ID

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.LedgerIdLedger ID carries the source identifier named Ledger ID for each audit history ledger journal header record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal header records to provider records that carry the same ledger ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies LedgerId as a record-level identifier on AuditHistoryLedgerJournalHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Ledgers Ledger ID

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.LedgersLedgerIdLedgers Ledger ID carries the source identifier named Ledgers Ledger ID for each audit history ledger journal header record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal header records to provider records that carry the same ledgers ledger ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies LedgersLedgerId as a record-level identifier on AuditHistoryLedgerJournalHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Legal Entity ID

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.LegalEntityIdLegal Entity ID carries the source identifier named Legal Entity ID for each audit history ledger journal header record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal header records to provider records that carry the same legal entity ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies LegalEntityId as a record-level identifier on AuditHistoryLedgerJournalHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Parent Je Header ID

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.ParentJeHeaderIdParent Je Header ID carries the source identifier named Parent Je Header ID for each audit history ledger journal header record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal header records to provider records that carry the same parent je header ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies ParentJeHeaderId as a record-level identifier on AuditHistoryLedgerJournalHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Period Name

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.PeriodNamePeriod Name carries the source-authored value named Period Name for each audit history ledger journal header record row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact period name value attached to each audit history ledger journal header record record.
Interpretation: The provider supplies PeriodName at audit history ledger journal header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Tax Status Code

Developer identifier: audit_history_ledger_journal_header.voForeignKeyMap.TaxStatusCodeTax Status Code carries the source state or classification named Tax Status Code for each audit history ledger journal header record row. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal header records by the exact provider-reported tax status code value when describing their recorded state.
Interpretation: The provider supplies TaxStatusCode per audit history ledger journal header record record using its own state vocabulary; unknown and missing values must remain distinct.

Audit History Ledger Journal Line

Developer identifier: audit_history_ledger_journal_lineAudit History Ledger Journal Line contains ledger Journal Line audit history events from Oracle Fusion Cloud. Captures create, update, and delete operations on GL Journal Line objects (JournalLineVO). Syncs incrementally using 7-day date-range windows.

Enables: trace create, update, and delete audit events for Oracle ledger journal line objects across seven-day request windows.
Scope: Reads provider changes through POST /fscmRestApi/fndAuditRESTService/audittrail/getaudithistory using the declared incremental request boundary. Results contain only audit rows returned for the named Oracle business object to the configured account; it is not a full transaction extract.

Attribute

Developer identifier: audit_history_ledger_journal_line.attributeAttribute records display name of the attribute that was changed. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact attribute value attached to each audit history ledger journal line record record.
Interpretation: The provider supplies attribute at audit history ledger journal line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Attribute Details

Developer identifier: audit_history_ledger_journal_line.attributeDetailsAttribute Details records array of attribute-level changes captured in the event. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded attribute details with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies attributeDetails on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Attribute Internal Name

Developer identifier: audit_history_ledger_journal_line.attributeInternalNameAttribute Internal Name records internal name of the attribute that was changed. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact attribute internal name value attached to each audit history ledger journal line record record.
Interpretation: The provider supplies attributeInternalName at audit history ledger journal line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Business Object

Developer identifier: audit_history_ledger_journal_line.businessObjectBusiness Object states business object affected by the event (e.g. Journal Line). It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal line records by the exact provider-reported business object value when describing their recorded state.
Interpretation: The provider supplies businessObject per audit history ledger journal line record record using its own state vocabulary; unknown and missing values must remain distinct.

Context Name1

Developer identifier: audit_history_ledger_journal_line.contextName1Context Name1 records display name of the first context attribute for the change (returned when includeExtendedObjectIdentiferColumns is true). It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name1 value attached to each audit history ledger journal line record record.
Interpretation: The provider supplies contextName1 at audit history ledger journal line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Name2

Developer identifier: audit_history_ledger_journal_line.contextName2Context Name2 records display name of the second context attribute for the change. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name2 value attached to each audit history ledger journal line record record.
Interpretation: The provider supplies contextName2 at audit history ledger journal line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Name3

Developer identifier: audit_history_ledger_journal_line.contextName3Context Name3 records display name of the third context attribute for the change. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name3 value attached to each audit history ledger journal line record record.
Interpretation: The provider supplies contextName3 at audit history ledger journal line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Value1

Developer identifier: audit_history_ledger_journal_line.contextValue1Context Value1 records value of the first context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value1 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue1 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Context Value2

Developer identifier: audit_history_ledger_journal_line.contextValue2Context Value2 records value of the second context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value2 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue2 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Context Value3

Developer identifier: audit_history_ledger_journal_line.contextValue3Context Value3 records value of the third context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value3 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue3 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Date

Developer identifier: audit_history_ledger_journal_line.dateDate records the timestamp of the audit event (yyyy-MM-dd HH:mm:ss). It anchors the named event or boundary on the record’s timeline.

Enables: place audit history ledger journal line records on a timeline by date and select the records within an explicit reporting window.
Interpretation: The provider supplies date per audit history ledger journal line record record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Description

Developer identifier: audit_history_ledger_journal_line.descriptionDescription records human-readable description of the audit event. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact description value attached to each audit history ledger journal line record record.
Interpretation: The provider supplies description at audit history ledger journal line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Description Internal

Developer identifier: audit_history_ledger_journal_line.descriptionInternalDescription Internal identifies internal identifier of the affected object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal line records to provider records that carry the same description internal, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies descriptionInternal as a record-level identifier on AuditHistoryLedgerJournalLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Event Type

Developer identifier: audit_history_ledger_journal_line.eventTypeEvent Type states type of audit event (e.g. Create, Object Data Update, Delete). It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal line records by the exact provider-reported event type value when describing their recorded state.
Interpretation: The provider supplies eventType per audit history ledger journal line record record using its own state vocabulary; unknown and missing values must remain distinct.

Developer identifier: audit_history_ledger_journal_line.idID identifies synthetic primary key (SHA-1 hash of date, userInternalName, qualifiedBusinessObject, eventType, descriptionInternal, attributeInternalName, newValueId, newValue). It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same audit history ledger journal line record source row before constructing its represented state.
Interpretation: Parable generates id at one value per audit history ledger journal line record record, and x-transformDedupKey explicitly marks it as the record key.

Impersonator

Developer identifier: audit_history_ledger_journal_line.impersonatorImpersonator records name of the impersonator when the action was performed under impersonation (returned when includeImpersonator is true). It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history ledger journal line record record to the provider-reported person or account represented by impersonator.
Interpretation: The provider supplies impersonator as identity or attribution context on each audit history ledger journal line record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

New Value

Developer identifier: audit_history_ledger_journal_line.newValueNew Value records new value of the changed attribute. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded new value with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies newValue on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

New Value ID

Developer identifier: audit_history_ledger_journal_line.newValueIdNew Value ID identifies internal ID of the new value, if the attribute references another object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal line records to provider records that carry the same new value ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies newValueId as a record-level identifier on AuditHistoryLedgerJournalLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Old Value

Developer identifier: audit_history_ledger_journal_line.oldValueOld Value records prior value of the changed attribute before the audit event. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded old value with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies oldValue on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Old Value ID

Developer identifier: audit_history_ledger_journal_line.oldValueIdOld Value ID identifies internal ID of the prior value, if the attribute references another object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal line records to provider records that carry the same old value ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies oldValueId as a record-level identifier on AuditHistoryLedgerJournalLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Qualified Business Object

Developer identifier: audit_history_ledger_journal_line.qualifiedBusinessObjectQualified Business Object states fully qualified view object name of the business object. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal line records by the exact provider-reported qualified business object value when describing their recorded state.
Interpretation: The provider supplies qualifiedBusinessObject per audit history ledger journal line record record using its own state vocabulary; unknown and missing values must remain distinct.

User Internal Name

Developer identifier: audit_history_ledger_journal_line.userInternalNameUser Internal Name records internal login name of the user who performed the action. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history ledger journal line record record to the provider-reported actor represented by user internal name.
Interpretation: The provider supplies userInternalName as identity or attribution context on each audit history ledger journal line record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

User Name

Developer identifier: audit_history_ledger_journal_line.userNameUser Name records display name of the user who performed the action. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history ledger journal line record record to the provider-reported actor represented by user name.
Interpretation: The provider supplies userName as identity or attribution context on each audit history ledger journal line record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

Vo Foreign Key Map

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMapVo Foreign Key Map identifies map of view object foreign key values associated with the event. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal line records to provider records that carry the same vo foreign key map, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies voForeignKeyMap as a record-level identifier on AuditHistoryLedgerJournalLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Chart Of Accounts ID

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.ChartOfAccountsIdChart Of Accounts ID carries the source identifier named Chart Of Accounts ID for each audit history ledger journal line record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal line records to provider records that carry the same chart of accounts ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies ChartOfAccountsId as a record-level identifier on AuditHistoryLedgerJournalLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Code Combination ID

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.CodeCombinationIdCode Combination ID carries the source identifier named Code Combination ID for each audit history ledger journal line record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal line records to provider records that carry the same code combination ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies CodeCombinationId as a record-level identifier on AuditHistoryLedgerJournalLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Code Combination Id1

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.CodeCombinationId1Code Combination Id1 carries the source configuration value named Code Combination Id1 for each audit history ledger journal line record row. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact code combination id1 when validating the configuration or technical definition of a audit history ledger journal line record record.
Interpretation: The provider supplies CodeCombinationId1 as configuration or technical metadata on AuditHistoryLedgerJournalLineRecord; consumers must preserve the exact syntax and documented vocabulary.

Conversion Type

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.ConversionTypeConversion Type carries the source state or classification named Conversion Type for each audit history ledger journal line record row. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal line records by the exact provider-reported conversion type value when describing their recorded state.
Interpretation: The provider supplies ConversionType per audit history ledger journal line record record using its own state vocabulary; unknown and missing values must remain distinct.

Currency Code

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.CurrencyCodeCurrency Code carries the source currency code or label named Currency Code for each audit history ledger journal line record row. It establishes the denomination used by companion financial amounts on the record.

Enables: interpret companion financial amounts on each audit history ledger journal line record record in the source denomination named by currency code.
Interpretation: The source supplies CurrencyCode once per audit history ledger journal line record record as its own currency code or label; Parable does not convert the associated amounts.

Currency Conversion Type

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.CurrencyConversionTypeCurrency Conversion Type carries the source state or classification named Currency Conversion Type for each audit history ledger journal line record row. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal line records by the exact provider-reported currency conversion type value when describing their recorded state.
Interpretation: The provider supplies CurrencyConversionType per audit history ledger journal line record record using its own state vocabulary; unknown and missing values must remain distinct.

Entity Name

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.EntityNameEntity Name carries the source-authored value named Entity Name for each audit history ledger journal line record row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact entity name value attached to each audit history ledger journal line record record.
Interpretation: The provider supplies EntityName at audit history ledger journal line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Functional Currency Code

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.FunctionalCurrencyCodeFunctional Currency Code carries the source currency code or label named Functional Currency Code for each audit history ledger journal line record row. It establishes the denomination used by companion financial amounts on the record.

Enables: interpret companion financial amounts on each audit history ledger journal line record record in the source denomination named by functional currency code.
Interpretation: The source supplies FunctionalCurrencyCode once per audit history ledger journal line record record as its own currency code or label; Parable does not convert the associated amounts.

Je Batch ID

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.JeBatchIdJe Batch ID carries the source identifier named Je Batch ID for each audit history ledger journal line record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal line records to provider records that carry the same je batch ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies JeBatchId as a record-level identifier on AuditHistoryLedgerJournalLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Je Category

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.JeCategoryJe Category carries the source state or classification named Je Category for each audit history ledger journal line record row. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal line records by the exact provider-reported je category value when describing their recorded state.
Interpretation: The provider supplies JeCategory per audit history ledger journal line record record using its own state vocabulary; unknown and missing values must remain distinct.

Ledger ID

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.LedgerIdLedger ID carries the source identifier named Ledger ID for each audit history ledger journal line record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal line records to provider records that carry the same ledger ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies LedgerId as a record-level identifier on AuditHistoryLedgerJournalLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Ledgers Ledger ID

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.LedgersLedgerIdLedgers Ledger ID carries the source identifier named Ledgers Ledger ID for each audit history ledger journal line record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal line records to provider records that carry the same ledgers ledger ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies LedgersLedgerId as a record-level identifier on AuditHistoryLedgerJournalLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Legal Entity ID

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.LegalEntityIdLegal Entity ID carries the source identifier named Legal Entity ID for each audit history ledger journal line record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal line records to provider records that carry the same legal entity ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies LegalEntityId as a record-level identifier on AuditHistoryLedgerJournalLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Parent Je Header ID

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.ParentJeHeaderIdParent Je Header ID carries the source identifier named Parent Je Header ID for each audit history ledger journal line record row. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history ledger journal line records to provider records that carry the same parent je header ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies ParentJeHeaderId as a record-level identifier on AuditHistoryLedgerJournalLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Period Name

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.PeriodNamePeriod Name carries the source-authored value named Period Name for each audit history ledger journal line record row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact period name value attached to each audit history ledger journal line record record.
Interpretation: The provider supplies PeriodName at audit history ledger journal line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Tax Status Code

Developer identifier: audit_history_ledger_journal_line.voForeignKeyMap.TaxStatusCodeTax Status Code carries the source state or classification named Tax Status Code for each audit history ledger journal line record row. It preserves the provider’s current classification of this record.

Enables: separate audit history ledger journal line records by the exact provider-reported tax status code value when describing their recorded state.
Interpretation: The provider supplies TaxStatusCode per audit history ledger journal line record record using its own state vocabulary; unknown and missing values must remain distinct.

Audit History Payables Invoice Header

Developer identifier: audit_history_payables_invoice_headerAudit History Payables Invoice Header contains payables Invoice Header audit history events from Oracle Fusion Cloud. Captures create, update, and delete operations on AP Invoice Header objects (InvoiceHeaderVO). Syncs incrementally using 7-day date-range windows.

Enables: trace create, update, and delete audit events for Oracle payables invoice header objects across seven-day request windows.
Scope: Reads provider changes through POST /fscmRestApi/fndAuditRESTService/audittrail/getaudithistory using the declared incremental request boundary. Results contain only audit rows returned for the named Oracle business object to the configured account; it is not a full transaction extract.

Attribute

Developer identifier: audit_history_payables_invoice_header.attributeAttribute records display name of the attribute that was changed. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact attribute value attached to each audit history payables invoice header record record.
Interpretation: The provider supplies attribute at audit history payables invoice header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Attribute Details

Developer identifier: audit_history_payables_invoice_header.attributeDetailsAttribute Details records array of attribute-level changes captured in the event. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded attribute details with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies attributeDetails on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Attribute Internal Name

Developer identifier: audit_history_payables_invoice_header.attributeInternalNameAttribute Internal Name records internal name of the attribute that was changed. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact attribute internal name value attached to each audit history payables invoice header record record.
Interpretation: The provider supplies attributeInternalName at audit history payables invoice header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Business Object

Developer identifier: audit_history_payables_invoice_header.businessObjectBusiness Object states business object affected by the event (e.g. Invoice). It preserves the provider’s current classification of this record.

Enables: separate audit history payables invoice header records by the exact provider-reported business object value when describing their recorded state.
Interpretation: The provider supplies businessObject per audit history payables invoice header record record using its own state vocabulary; unknown and missing values must remain distinct.

Context Name1

Developer identifier: audit_history_payables_invoice_header.contextName1Context Name1 records display name of the first context attribute for the change (returned when includeExtendedObjectIdentiferColumns is true). It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name1 value attached to each audit history payables invoice header record record.
Interpretation: The provider supplies contextName1 at audit history payables invoice header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Name2

Developer identifier: audit_history_payables_invoice_header.contextName2Context Name2 records display name of the second context attribute for the change. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name2 value attached to each audit history payables invoice header record record.
Interpretation: The provider supplies contextName2 at audit history payables invoice header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Name3

Developer identifier: audit_history_payables_invoice_header.contextName3Context Name3 records display name of the third context attribute for the change. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name3 value attached to each audit history payables invoice header record record.
Interpretation: The provider supplies contextName3 at audit history payables invoice header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Value1

Developer identifier: audit_history_payables_invoice_header.contextValue1Context Value1 records value of the first context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value1 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue1 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Context Value2

Developer identifier: audit_history_payables_invoice_header.contextValue2Context Value2 records value of the second context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value2 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue2 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Context Value3

Developer identifier: audit_history_payables_invoice_header.contextValue3Context Value3 records value of the third context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value3 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue3 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Date

Developer identifier: audit_history_payables_invoice_header.dateDate records the timestamp of the audit event (yyyy-MM-dd HH:mm:ss). It anchors the named event or boundary on the record’s timeline.

Enables: place audit history payables invoice header records on a timeline by date and select the records within an explicit reporting window.
Interpretation: The provider supplies date per audit history payables invoice header record record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Description

Developer identifier: audit_history_payables_invoice_header.descriptionDescription records human-readable description of the audit event (e.g. invoice number). It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact description value attached to each audit history payables invoice header record record.
Interpretation: The provider supplies description at audit history payables invoice header record granularity in the format stated by its description; omitted or redacted content remains unknown.

Description Internal

Developer identifier: audit_history_payables_invoice_header.descriptionInternalDescription Internal identifies internal identifier of the affected object (e.g. internal invoice ID). It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history payables invoice header records to provider records that carry the same description internal, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies descriptionInternal as a record-level identifier on AuditHistoryPayablesInvoiceHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Event Type

Developer identifier: audit_history_payables_invoice_header.eventTypeEvent Type states type of audit event (e.g. Create, Object Data Update, Delete). It preserves the provider’s current classification of this record.

Enables: separate audit history payables invoice header records by the exact provider-reported event type value when describing their recorded state.
Interpretation: The provider supplies eventType per audit history payables invoice header record record using its own state vocabulary; unknown and missing values must remain distinct.

Developer identifier: audit_history_payables_invoice_header.idID identifies synthetic primary key (SHA-1 hash of date, userInternalName, qualifiedBusinessObject, eventType, descriptionInternal, attributeInternalName, newValueId, newValue). It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same audit history payables invoice header record source row before constructing its represented state.
Interpretation: Parable generates id at one value per audit history payables invoice header record record, and x-transformDedupKey explicitly marks it as the record key.

Impersonator

Developer identifier: audit_history_payables_invoice_header.impersonatorImpersonator records name of the impersonator when the action was performed under impersonation (returned when includeImpersonator is true). It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history payables invoice header record record to the provider-reported person or account represented by impersonator.
Interpretation: The provider supplies impersonator as identity or attribution context on each audit history payables invoice header record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

New Value

Developer identifier: audit_history_payables_invoice_header.newValueNew Value records new value of the changed attribute. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded new value with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies newValue on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

New Value ID

Developer identifier: audit_history_payables_invoice_header.newValueIdNew Value ID identifies internal ID of the new value, if the attribute references another object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history payables invoice header records to provider records that carry the same new value ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies newValueId as a record-level identifier on AuditHistoryPayablesInvoiceHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Old Value

Developer identifier: audit_history_payables_invoice_header.oldValueOld Value records prior value of the changed attribute before the audit event. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded old value with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies oldValue on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Old Value ID

Developer identifier: audit_history_payables_invoice_header.oldValueIdOld Value ID identifies internal ID of the prior value, if the attribute references another object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history payables invoice header records to provider records that carry the same old value ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies oldValueId as a record-level identifier on AuditHistoryPayablesInvoiceHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Qualified Business Object

Developer identifier: audit_history_payables_invoice_header.qualifiedBusinessObjectQualified Business Object states fully qualified view object name of the business object. It preserves the provider’s current classification of this record.

Enables: separate audit history payables invoice header records by the exact provider-reported qualified business object value when describing their recorded state.
Interpretation: The provider supplies qualifiedBusinessObject per audit history payables invoice header record record using its own state vocabulary; unknown and missing values must remain distinct.

User Internal Name

Developer identifier: audit_history_payables_invoice_header.userInternalNameUser Internal Name records internal login name of the user who performed the action. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history payables invoice header record record to the provider-reported actor represented by user internal name.
Interpretation: The provider supplies userInternalName as identity or attribution context on each audit history payables invoice header record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

User Name

Developer identifier: audit_history_payables_invoice_header.userNameUser Name records display name of the user who performed the action. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history payables invoice header record record to the provider-reported actor represented by user name.
Interpretation: The provider supplies userName as identity or attribution context on each audit history payables invoice header record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

Vo Foreign Key Map

Developer identifier: audit_history_payables_invoice_header.voForeignKeyMapVo Foreign Key Map identifies map of view object foreign key values associated with the event. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history payables invoice header records to provider records that carry the same vo foreign key map, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies voForeignKeyMap as a record-level identifier on AuditHistoryPayablesInvoiceHeaderRecord. It is not a uniqueness guarantee unless a connector directive says so.

Audit History Payables Invoice Line

Developer identifier: audit_history_payables_invoice_lineAudit History Payables Invoice Line contains payables Invoice Line audit history events from Oracle Fusion Cloud. Captures create, update, and delete operations on AP Invoice Line objects (InvoiceLineVO). Syncs incrementally using 7-day date-range windows.

Enables: trace create, update, and delete audit events for Oracle payables invoice line objects across seven-day request windows.
Scope: Reads provider changes through POST /fscmRestApi/fndAuditRESTService/audittrail/getaudithistory using the declared incremental request boundary. Results contain only audit rows returned for the named Oracle business object to the configured account; it is not a full transaction extract.

Attribute

Developer identifier: audit_history_payables_invoice_line.attributeAttribute records display name of the attribute that was changed. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact attribute value attached to each audit history payables invoice line record record.
Interpretation: The provider supplies attribute at audit history payables invoice line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Attribute Details

Developer identifier: audit_history_payables_invoice_line.attributeDetailsAttribute Details records array of attribute-level changes captured in the event. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded attribute details with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies attributeDetails on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Attribute Internal Name

Developer identifier: audit_history_payables_invoice_line.attributeInternalNameAttribute Internal Name records internal name of the attribute that was changed. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact attribute internal name value attached to each audit history payables invoice line record record.
Interpretation: The provider supplies attributeInternalName at audit history payables invoice line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Business Object

Developer identifier: audit_history_payables_invoice_line.businessObjectBusiness Object states business object affected by the event (e.g. Invoice Line). It preserves the provider’s current classification of this record.

Enables: separate audit history payables invoice line records by the exact provider-reported business object value when describing their recorded state.
Interpretation: The provider supplies businessObject per audit history payables invoice line record record using its own state vocabulary; unknown and missing values must remain distinct.

Context Name1

Developer identifier: audit_history_payables_invoice_line.contextName1Context Name1 records display name of the first context attribute for the change (returned when includeExtendedObjectIdentiferColumns is true). It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name1 value attached to each audit history payables invoice line record record.
Interpretation: The provider supplies contextName1 at audit history payables invoice line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Name2

Developer identifier: audit_history_payables_invoice_line.contextName2Context Name2 records display name of the second context attribute for the change. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name2 value attached to each audit history payables invoice line record record.
Interpretation: The provider supplies contextName2 at audit history payables invoice line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Name3

Developer identifier: audit_history_payables_invoice_line.contextName3Context Name3 records display name of the third context attribute for the change. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact context name3 value attached to each audit history payables invoice line record record.
Interpretation: The provider supplies contextName3 at audit history payables invoice line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Context Value1

Developer identifier: audit_history_payables_invoice_line.contextValue1Context Value1 records value of the first context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value1 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue1 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Context Value2

Developer identifier: audit_history_payables_invoice_line.contextValue2Context Value2 records value of the second context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value2 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue2 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Context Value3

Developer identifier: audit_history_payables_invoice_line.contextValue3Context Value3 records value of the third context attribute for the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded context value3 with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies contextValue3 on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Date

Developer identifier: audit_history_payables_invoice_line.dateDate records the timestamp of the audit event (yyyy-MM-dd HH:mm:ss). It anchors the named event or boundary on the record’s timeline.

Enables: place audit history payables invoice line records on a timeline by date and select the records within an explicit reporting window.
Interpretation: The provider supplies date per audit history payables invoice line record record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Description

Developer identifier: audit_history_payables_invoice_line.descriptionDescription records human-readable description of the audit event. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact description value attached to each audit history payables invoice line record record.
Interpretation: The provider supplies description at audit history payables invoice line record granularity in the format stated by its description; omitted or redacted content remains unknown.

Description Internal

Developer identifier: audit_history_payables_invoice_line.descriptionInternalDescription Internal identifies internal identifier of the affected object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history payables invoice line records to provider records that carry the same description internal, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies descriptionInternal as a record-level identifier on AuditHistoryPayablesInvoiceLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Event Type

Developer identifier: audit_history_payables_invoice_line.eventTypeEvent Type states type of audit event (e.g. Create, Object Data Update, Delete). It preserves the provider’s current classification of this record.

Enables: separate audit history payables invoice line records by the exact provider-reported event type value when describing their recorded state.
Interpretation: The provider supplies eventType per audit history payables invoice line record record using its own state vocabulary; unknown and missing values must remain distinct.

Developer identifier: audit_history_payables_invoice_line.idID identifies synthetic primary key (SHA-1 hash of date, userInternalName, qualifiedBusinessObject, eventType, descriptionInternal, attributeInternalName, newValueId, newValue). It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same audit history payables invoice line record source row before constructing its represented state.
Interpretation: Parable generates id at one value per audit history payables invoice line record record, and x-transformDedupKey explicitly marks it as the record key.

Impersonator

Developer identifier: audit_history_payables_invoice_line.impersonatorImpersonator records name of the impersonator when the action was performed under impersonation (returned when includeImpersonator is true). It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history payables invoice line record record to the provider-reported person or account represented by impersonator.
Interpretation: The provider supplies impersonator as identity or attribution context on each audit history payables invoice line record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

New Value

Developer identifier: audit_history_payables_invoice_line.newValueNew Value records new value of the changed attribute. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded new value with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies newValue on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

New Value ID

Developer identifier: audit_history_payables_invoice_line.newValueIdNew Value ID identifies internal ID of the new value, if the attribute references another object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history payables invoice line records to provider records that carry the same new value ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies newValueId as a record-level identifier on AuditHistoryPayablesInvoiceLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Old Value

Developer identifier: audit_history_payables_invoice_line.oldValueOld Value records prior value of the changed attribute before the audit event. It preserves the recorded before, after, or contextual value needed to explain a change event.

Enables: compare the recorded old value with the corresponding changed attribute when explaining an audit or changelog event.
Interpretation: The provider supplies oldValue on each change record in the changed attribute’s own type or display format; it is not normalized into a common unit.

Old Value ID

Developer identifier: audit_history_payables_invoice_line.oldValueIdOld Value ID identifies internal ID of the prior value, if the attribute references another object. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history payables invoice line records to provider records that carry the same old value ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies oldValueId as a record-level identifier on AuditHistoryPayablesInvoiceLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Qualified Business Object

Developer identifier: audit_history_payables_invoice_line.qualifiedBusinessObjectQualified Business Object states fully qualified view object name of the business object. It preserves the provider’s current classification of this record.

Enables: separate audit history payables invoice line records by the exact provider-reported qualified business object value when describing their recorded state.
Interpretation: The provider supplies qualifiedBusinessObject per audit history payables invoice line record record using its own state vocabulary; unknown and missing values must remain distinct.

User Internal Name

Developer identifier: audit_history_payables_invoice_line.userInternalNameUser Internal Name records internal login name of the user who performed the action. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history payables invoice line record record to the provider-reported actor represented by user internal name.
Interpretation: The provider supplies userInternalName as identity or attribution context on each audit history payables invoice line record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

User Name

Developer identifier: audit_history_payables_invoice_line.userNameUser Name records display name of the user who performed the action. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the audit history payables invoice line record record to the provider-reported actor represented by user name.
Interpretation: The provider supplies userName as identity or attribution context on each audit history payables invoice line record record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

Vo Foreign Key Map

Developer identifier: audit_history_payables_invoice_line.voForeignKeyMapVo Foreign Key Map identifies map of view object foreign key values associated with the event. It is needed to resolve references that repeat the same provider identifier.

Enables: match audit history payables invoice line records to provider records that carry the same vo foreign key map, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies voForeignKeyMap as a record-level identifier on AuditHistoryPayablesInvoiceLineRecord. It is not a uniqueness guarantee unless a connector directive says so.

Service	Base Path
Audit REST	`/fscmRestApi/fndAuditRESTService/audittrail/`

Error	Meaning	Solution
`401 Unauthorized`	Invalid credentials	Verify username and password
`403 Forbidden`	Missing role	Assign the Financial Auditor role
`404 Not Found`	Audit service not available	Confirm REST services are enabled for your instance
`500 Internal Server Error`	Server issue	Contact Oracle support

Common Issues

No audit data returned

Audit trail must be enabled for the Payables and Ledger products in Oracle Fusion Cloud before Parable can sync data. Navigate to Setup and Maintenance → Manage Audit Policies and confirm both products are enabled with the business objects listed in the setup guide.

Account locked out

After multiple failed login attempts, Oracle Fusion Cloud may lock the account. Use the Security Console to unlock it.Oracle Audit REST API — Oracle Fusion Cloud Audit REST service documentationManage Audit Policies — How to enable audit trail for Oracle Fusion Cloud products

​Payables — Invoice Header

​Payables — Invoice Line

​Ledger — Journal Batch

​Ledger — Journal Header

​Ledger — Journal Line

​Data streams

​Oracle Fusion Cloud

​What You’ll Need

​Step 1: Enable Audit Trail for Payables and Ledger

​Step 2: Identify Your Instance Hostname

​Step 3: Create a Dedicated Integration User (Recommended)

​Step 4: Enter credentials in Parable

​Common Issues

​No audit data returned

​Account locked out

Payables — Invoice Header

Payables — Invoice Line

Ledger — Journal Batch

Ledger — Journal Header

Ledger — Journal Line

Data streams

Oracle Fusion Cloud

What You’ll Need

Step 1: Enable Audit Trail for Payables and Ledger

Step 2: Identify Your Instance Hostname

Step 3: Create a Dedicated Integration User (Recommended)

Step 4: Enter credentials in Parable

Common Issues

No audit data returned

Account locked out