Views for Extracting Data
| View | Description |
|---|---|
| Account Profiles (customerProfilesExtract) |
The Customer Account Profile business object provides the details of a specific profile class record assigned to a customer account for a specified time period and modified according to the account requirements. |
| Accounting Calendar Periods (accountingCalendarPeriodsExtract) |
An accounting period provides the details of the periods of an accounting calendar. |
| Accounting Calendars (accountingCalendarsExtract) |
An accounting calendar contains the periods of an accounting year. For example, one company can have a fiscal calendar that starts in May and ends in June. Another company can use calendars based on the calendar year, January to December. |
| Accounting Class Assignments (accountingClassAssignmentsExtract) |
An accounting class assignment contains information about the post accounting program short name, accounting class usage short name, and the accounting class short name for use in Post-Accounting programs. |
| Accounting Period Statuses (accountingPeriodStatusesExtract) |
The Accounting Period Status stores the statuses of your accounting periods for a ledger and subledger application. Each row includes the accounting period name and status. |
| Accounting Period Types (accountingPeriodTypesExtract) |
An Accounting Period Type contains the details of the system generated period type along with number of periods per year and calendar or fiscal year type of calendar. This determines the system assigned name for the accounting calendar. |
| Activity Taxes (receivablesActivityTaxesExtract) |
The Receivables Activity Tax provides the asset and liability tax rates by legal entity for each receivables activity. |
| All Types Validation Request Line Results (allTypesValidationRequestLineResultsExtract) |
An all types validation request line result contains the identifiers of a source transaction line or distribution with a budgetary control validation request result. All transaction types are included. |
| All Types Validation Request Transaction Results (allTypesValidationRequestTransactionResultsExtract) |
An all types validation request transaction result contains the transaction identifiers and transaction number for a source transaction with a budgetary control validation request result. All transaction types are included. |
| Application Exception Rule Details (receivablesApplicationExceptionRuleDetailsExtract) |
The Receivables Application Exception Rule Detail provides the details of the rules that process overpayments and underpayments after receipt application by AutoApply and the AutoMatch Rule Set. |
| Approval Limits (receivablesUserApprovalLimitsExtract) |
The Receivables User Approval Limit provides the details of the minimum and maximum amounts per currency and transaction activity that a Receivables user has to approve adjustments, credit memo refunds, and receipt write-offs. |
| Asset Accounting Lines (assetAccountingLinesExtract) |
An accounting line contains journal entry lines for every asset transaction that has a financial impact on the primary asset book. These accounting lines are used to create journal entries in Oracle Subledger Accounting and transfer them to Oracle General Ledger. |
| Asset All Segments Categories (assetAllSegmentsCategoriesExtract) |
The all segments category stores the flexfield segment values, category identifier, structure instance number, active start and end date of the category, and property and inventory details. |
| Asset All Segments Keys (assetAllSegmentsKeysExtract) |
The all segments key stores the flexfield segment values of the asset key and key code combination identifier, structure instance number, and active start and end date to track assets. |
| Asset All Segments Locations (assetAllSegmentsLocationsExtract) |
The all segments location stores the flexfield segment values, location identifier, structure instance number, and the active start date and end date required for transferring assets from one location to another. |
| Asset Book Periods (assetBookPeriodsExtract) |
This view lists the information about the depreciation period status, period open date, and period close date for each asset book. |
| Asset Books (assetBooksExtract) |
This view contains information about descriptive details of the book, the book class, ledger, and currency details of the assets. |
| Asset Calendar Periods (assetCalendarPeriodsExtract) |
This view lists the calendar periods with the start and end date of the calendar period. The Calculate Depreciation process uses this information to check the transaction date and also to define the open and close date for the asset calendar in the asset book. |
| Asset Calendars (assetCalendarsExtract) |
A calendar contains depreciation calendar information, such as the fiscal year and the number of accounting periods per fiscal year for the asset book. |
| Asset Cash Generating Units (assetCashGeneratingUnitsExtract) |
A cash generating unit represents the smallest identifiable group of assets that generates cash inflows that are largely independent of the cash inflows from other assets or groups of assets. |
| Asset Category and Unit Histories (assetCategoryAndUnitHistoriesExtract) |
The category and unit history stores information about asset category changes, capitalizations, unit adjustments, and partial unit retirements. |
| Asset Category Book Defaults (assetCategoryBookDefaultsExtract) |
Depreciation rules defined for each asset category automatically default to asset addition and retirement transactions. You can set up many distinct default rules for each asset category, depreciation book, and date placed in service range combination to reduce the chance of selecting an incorrect depreciation method or prorate convention. |
| Asset Category Books (assetCategoryBooksExtract) |
A category book contains the cost and reserve accounts for an asset book and the category combination. |
| Asset Deferred Depreciation Details (assetDeferredDepreciationDetailsExtract) |
A deferred depreciation detail stores information about deferred depreciation amounts calculated for each distribution of the assets used to created journal entries. |
| Asset Depreciation Ceilings (assetDepreciationCeilingsExtract) |
A depreciation ceiling stores the depreciation expense, depreciation cost, and investment tax credit information for an asset book. |
| Asset Depreciation Methods (assetDepreciationMethodsExtract) |
This view contains definitions for depreciation methods, such as the name, description, type, depreciation calculation basis, and life that's used to depreciate assets, in addition to information about the method ID and prorate periods per year. |
| Asset Distributions (assetDistributionsExtract) |
This view contains assigned units, employees, the depreciation expense account, or location information about the asset when the asset is added retired, transferred, reinstated, or reclassified. |
| Asset Financial Details (assetFinancialDetailsExtract) |
This view contains financial information, descriptive details, depreciation rules, and the period details of the asset. |
| Asset Fiscal Year Dates (assetFiscalYearDatesExtract) |
A fiscal year date stores the calendar and fiscal year in which the transaction occurs, including the start date, end date, and midyear date of the fiscal year for the asset book. |
| Asset Impairment Details (assetImpairmentDetailsExtract) |
Impairment details include the allocated impairment loss details, such as the net selling price, value in use, and impairment loss for each asset in the primary asset book. |
| Asset Impairments (assetImpairmentsExtract) |
An impairment transaction stores the impairment transaction details, such as the net selling price, value in use, and impairment loss for the asset and cash generating unit in the primary asset book. |
| Asset Lease Expense Details (assetLeaseExpenseDetailsExtract) |
A lease expense detail contains the lease interest expense and lease expense values for a leased asset for each period at the distribution level. |
| Asset Lease Expense Summaries (assetLeaseExpenseSummariesExtract) |
A lease expense summary contains the lease interest expense and lease expense values for a leased asset for each period. |
| Asset Leases (assetLeasesExtract) |
A lease stores information about assets that are leased, such as the lease terms, lessor, and whether the lease is an operating or capital lease asset. |
| Asset Periodic Depreciation Details (assetPeriodicDepreciationDetailsExtract) |
This view contains the distribution details, descriptive details, depreciation period, and depreciation amount for each of the assets in the asset book calculated by the Calculate Depreciation process, and generates depreciation expense journal entries. |
| Asset Periodic Depreciation Summaries (assetPeriodicDepreciationSummariesExtract) |
A periodic depreciation summary history shows depreciation information used to audit and inquire on transactions accounted for in Oracle Subledger Accounting. |
| Asset Periodic Financial Details (assetPeriodFinancialDetailsExtract) |
A periodic financial detail stores information about group asset periodical financial information. It also stores information about group financial information changes, such as group additions, adjustments, member asset additions, member asset adjustments, member asset retirements, group reclassifications, and unplanned depreciation transactions. |
| Asset Price Indexes (assetPriceIndexesExtract) |
A price index measures how prices change over a period of time. They're used to revalue assets to their fair market value rather than their historical cost. |
| Asset Prorate Conventions (assetProrateConventionsExtract) |
A prorate convention contains the date that maps a date placed in service to a prorate date for depreciation calculation. |
| Asset Reporting Book Periods (assetReportingBookPeriodsExtract) |
A reporting book period contains information about the depreciation period status, period open date, and period close date for each reporting asset book. |
| Asset Reporting Books (assetReportingBooksExtract) |
A reporting book represents the secondary grouping in which fixed assets of the entity are recorded, tracked, depreciated, reported, and accounted for in the reporting currencies or in a secondary ledger with different currency than its primary ledger. |
| Asset Retirements (assetRetirementsExtract) |
A retirement transaction stores information such as the retirement date, cost retired, retirement convention, and gain or loss in the primary asset book. |
| Asset Revaluations (assetRevaluationsExtract) |
A revaluation transaction contains the carrying value of a company's fixed asset or group of fixed assets to account for any major changes in their fair market value. |
| Asset Source Lines (assetSourceLinesExtract) |
A source line contains asset acquisition invoice information from source applications, such as Oracle Payables, Oracle Receiving, and Oracle Project Costing, for tracking and reporting purposes in the primary asset book. A source line contains all costs imported from source applications, including, items, freight, taxes, project labor, and expenses. |
| Asset Transaction Between Assets Histories (assetTransactionBetweenAssetsHistoriesExtract) |
A transaction between assets history contains information about interasset transactions, in which two or more dependent transactions are performed at one time. |
| Asset Transactions (assetTransactionsExtract) |
A transaction stores addition, adjustment, transfer, retirement, CIP capitalization, and mass copy information for an asset in the asset book. |
| Assets (assetsExtract) |
An asset contains the descriptive information such as units, asset type, tag number, manufacturer number, serial number, and model number added in the asset book. |
| AutoAccounting Rules (receivablesAutoAccountingRulesExtract) |
The Receivables AutoAccounting Rule provides the details used to derive default accounting values for revenue, receivables, freight, tax, unearned revenue, and unbilled receivables accounts during transaction processing in Oracle Receivables. It defines the sources and structure of the accounting combinations used in the generation of journal entries for customer transactions. |
| AutoInvoice Grouping Rules (receivablesAutoInvoiceGroupingRulesExtract) |
The AutoInvoice grouping rule is a set of rules that determines how the invoice interface lines should be grouped to create invoices. It includes details such as name, description, line ordering rule, transaction class, from and to date, and optional grouping characteristics. The AutoInvoice uses these rules to create invoices. The rules specify various transaction attributes that must be identical for the same transaction. For example, if the transaction number is part of the grouping rule and two interface lines have different transaction numbers, then two transactions are created. |
| AutoInvoice Line Ordering Rules (receivablesAutoInvoiceLineOrderingRulesExtract) |
The Receivables AutoInvoice Line Ordering Rule specifies how the individual lines of an imported transaction are ordered and numbered after AutoInvoice groups transactions into invoices, debit memos, or credit memos. It defines the sequence of attributes that determines the order of lines within each grouped transaction. Each line ordering rule can be assigned to one or more grouping rules, ensuring that lines are consistently ordered according to business requirements during the invoice import and creation process. |
| AutoMatch Rule Sets (receivablesAutoMatchRuleSetsExtract) |
The AutoMatch rule set provides the details of the AutoMatch rule set. The details include reference set, name, description, start date, end date, customer recommendation threshold, minimum match hold, combined weighted hold, and days of closed invoices hold. |
| Automatic Bills Receivable Transactions Batch Reports (automaticBillsReceivableTransactionsBatchReportsExtract) |
The Automatic Bills Receivable Transactions Batch Report provides a detailed or summary listing of bills receivable generated in a batch from customer drawee transactions. This report is utilized to review the contents of a bills receivable batch either after its creation or while it's still in Draft status. It's designed to help verify the bills receivable created through the Create Bills Receivable Batch process. |
| Backup Collectors (backupCollectorsExtract) |
The Backup Collector provides information about the backup for a primary collector. This refers to the ability to assign a backup collector or a collector group who can access and manage the primary collector's accounts, especially in cases where the primary collector is unavailable due to absence, illness, or other reasons. This ensures continuity in the collections process without disrupting the workflow. |
| Balance Forward Bills (balanceForwardBillsExtract) |
The balance forward bill contains information about balance forward bills, including bill number, bill-to customer number, customer site, bill-from, bill-to, billing date, due date, currency, amount due, beginning balance, ending balance, payment terms, payments, adjustments, credits, current charges, tax, and late charges. Balance forward bills are generated by the Generate Balance Forward Bill process. The balance forward bill contains all transactions created within the period specified by the balance forward billing cycle. |
| Bank Account Business Unit Assignments (bankAccountBusinessUnitAssignmentsExtract) |
The bank account assignment provides the assignment details of the operating unit with the bank account. |
| Bank Account Statement Balances (bankAccountStatementBalancesExtract) |
The bank account statement balance provides information about statement balances. |
| Bank Account Statement Line Fees and Charges (bankAccountStatementLineFeesandChargesExtract) |
The bank account statement lines contain information related to bank statement lines, such as line number, booking date, transaction code, transaction type, reconciliation reference, transaction amount, transaction identification information, and so on. It includes reconciled and unreconciled bank statements lines. |
| Bank Account Statement Lines (bankAccountStatementLinesExtract) |
The bank account statement lines contain information related to bank statement lines, such as line number, booking date, transaction code, transaction type, reconciliation reference, transaction amount, transaction identification information, and so on. It includes reconciled and unreconciled bank statements lines. |
| Bank Account Statements (bankAccountStatementsExtract) |
The bank account statement provides the details of the statement header issued by the bank, which includes information for reconciliation and cash balances such as Prior-day bank statements and intra-day bank statements. |
| Bank Accounts (bankAccountsExtract) |
The bank account provides the details of the internal bank accounts of a company that are used to receive payments and disburse funds. It contains legal entity-level bank account information. Each bank account must be affiliated with one bank branch. |
| Bank Branches (bankBranchesExtract) |
A bank branch represents a branch of a bank. It includes details such as the branch name, alternate branch name, branch number, and branch type. |
| Bank Statement Reconciliation Matching Rules (bankStatementReconciliationMatchingRulesExtract) |
The bank statement reconciliation matching rules contain reconciliation matching rules that are used during automatic reconciliation. Each rule determines how the bank statement lines and system transactions are automatically matched. |
| Bank Statement Reconciliation Tolerance Rules (bankStatementReconciliationToleranceRulesExtract) |
The bank statement reconciliation matching rules contain reconciliation matching rules that are used during automatic reconciliation. Each rule determines how the bank statement lines and system transactions are automatically matched. |
| Bank Statement Transaction Codes (bankStatementTransactionCodesExtract) |
The bank statement transaction codes contain information related to transaction codes such as description, transaction type, domain, family, and subfamily. Bank statement transaction codes are the internal codes that are used on a bank statement line to identify the type of transaction being reported. |
| Bill Presentment Deliveries (receivablesBillPresentmentArchitectureDeliveriesExtract) |
The Receivables Bill Presentment Delivery provides the information used for delivering printed Receivables transactions using the delivery methods Email, Paper, or XML. It captures all relevant delivery details for each transaction, supporting the Bill Presentment Architecture delivery process. |
| Billing Cycle Dates (receivablesBalanceForwardBillingCycleDatesExtract) |
The Billing Cycle Bill Date provides the details of billing dates of the Receivables invoice consolidated billing cycle that manages time-based criteria for combining eligible charge lines from multiple sources into Receivables invoices. It also provides the details of the balance forward billing cycle used to determine the dates to generate balance forward bills. |
| Bills Receivable Transaction Histories (billsReceivableTransactionHistoriesExtract) |
The Bills Receivable Transaction History business object provides the details of each bills receivable transaction, including activities and the life cycle of bills receivable events. |
| Budgetary Control Balances (budgetaryControlBalancesExtract) |
A budgetary control balance contains budget and consumption balances for a control budget, budget account, and budget period. |
| Budgetary Control Budget Entries (budgetaryControlBudgetEntriesExtract) |
A budget entry is a group of budget entry lines that are successfully entered or imported into Budgetary Control. It contains information such as whether the entry is an initial budget or budget adjustment, and whether the amounts in the entry are expressed as additions to or subtractions from the current budget balances or directly as the updated budget balances. |
| Budgetary Control Budget Entry Control Budget Impacts (budgetaryControlBudgetEntryControlBudgetImpactsExtract) |
A budget entry control budget impact represents the budget balance of a control budget, budget period, and budget account that's updated by a budget entry line. A single budget entry line can update multiple control budgets. Multiple budget entry lines entered by month and detailed segment value can be aggregated and update a yearly period and a single parent budget account. |
| Budgetary Control Budget Entry Lines (budgetaryControlBudgetEntryLinesExtract) |
A budget entry line represents the combination of budget segment values of a budget line. |
| Budgetary Control Validation Request Control Budget Results (budgetaryControlValidationRequestControlBudgetResultsExtract) |
A budgetary control validation request control budget result contains the control budget, budget account, budget period, validation result, budgetary control balance impacted by the transaction line, and whether the balance was updated or not. |
| Budgetary Control Validation Requests (budgetaryControlValidationRequestsExtract) |
A budgetary control validation request contains the information of each request, such as the type of transaction being validated and the validation result. |
| Business Functions (businessFunctionsExtract) |
A business function represents a business process or an activity performed by people working within a business unit and describes how a business unit is used in transaction processing. For example, a business unit can perform procurement of goods and services and payables invoicing business functions. |
| Business Unit Function Assignments (businessUnitFunctionAssignmentsExtract) |
A business unit function assignment represents the details of the business functions enabled for a business unit. For example, you can enable the Payables Invoicing business function for a business unit. |
| Business Units (businessUnitsExtract) |
A business unit represents a unit of an enterprise that performs one or more business functions and may have service provider relationships between the units. It typically focuses on a specific market segment, product line, geographic region, or set of services. The business transactions are recorded, reported, and accounted against the business unit. |
| Case Folder Templates (creditCaseFolderTemplatesExtract) |
A credit case folder template is used to create a new credit case folder. The credit case folder template contains data points, the definition of their use in credit reviews, and a scoring model for a customer or customer account. A credit case folder is created from a template for a combination of credit classification and review type. |
| Cash Transactions (cashTransactionsExtract) |
The cash transaction provides the details of the external transactions related to cash activity that isn't recorded within the application, such as bank charges or interest transactions created from bank statement lines, bank account balance adjustments, bank statement reconciliation differences, transactions imported from third-party systems and so on. |
| Collections Aging Bucket Details (collectionsAgingBucketDetailsExtract) |
The collections aging bucket detail provides the line level detail for aging buckets. |
| Collections Aging Buckets (collectionsAgingBucketsExtract) |
The collections aging bucket provides periods within which all customer transactions will be classified, such as 7 buckets aging definition and 4 buckets aging definition. |
| Collections Customer Messages (collectionsCustomerMessagesExtract) |
Collections Customer Messages include actionable transaction and customer-level data derived from the intent of each inbound customer interaction, such as emails. |
| Collections Customer Scoring Segments (collectionsCustomerScoringSegmentsExtract) |
The customer segment is used to limit the segment of customers against whom a particular collections strategy is applied. Essentially, it defines filters that restrict the scope of customers or accounts targeted by a strategy, enabling more precise and efficient collections management. This segmentation helps in improving system performance and accuracy by focusing scoring engines and strategies on specific subsets of delinquent customers, rather than the entire customer base. The filters in this object define criteria that identify these subsets, ensuring that collections efforts are targeted and relevant. |
| Collections Customer Segments (collectionsCustomerSegmentsExtract) |
The customer segment is used to limit the segment of customers against whom a particular collections strategy is applied. Essentially, it defines filters that restrict the scope of customers or accounts targeted by a strategy, enabling more precise and efficient collections management. This segmentation helps in improving system performance and accuracy by focusing scoring engines and strategies on specific subsets of delinquent customers, rather than the entire customer base. The filters in this object define criteria that identify these subsets, ensuring that collections efforts are targeted and relevant. |
| Collections Customer Strategy Segments (collectionsCustomerStrategySegmentsExtract) |
The customer segment is used to limit the segment of customers against whom a particular collections strategy is applied. Essentially, it defines filters that restrict the scope of customers or accounts targeted by a strategy, enabling more precise and efficient collections management. This segmentation helps in improving system performance and accuracy by focusing scoring engines and strategies on specific subsets of delinquent customers, rather than the entire customer base. The filters in this object define criteria that identify these subsets, ensuring that collections efforts are targeted and relevant. |
| Collections Preferences (collectionsPreferencesExtract) |
The Collections Preference provides the details of the individual questions that make up a collections questionnaire in Oracle Advanced Collections. These questions are typically used to capture customer preferences, commitments, or explanations during collection activities such as calls, emails, or follow-ups. |
| Collections Score to Status Mappings (collectionsScoretoStatusMappingsExtract) |
The mapping of score to status links customer credit or risk scores to their delinquency status, such as Delinquent, Current, Bankrupt, and Predelinquent. |
| Collections Scoring and Strategy Assignments (collectionsScoringandStrategyAssignmentsExtract) |
The collections scoring and strategy assignment provides the details of the segments of Oracle Collections. It's used to determine the appropriate scoring formula to be used and the strategy to be assigned to a subset or segment of delinquent customers. |
| Collections Scoring Data Point Histories (collectionsScoringDataPointHistoriesExtract) |
The collections data point history maintains a detailed history of collections scoring data, capturing the values of individual data points used during the scoring process. It provides result of every run of the Scoring process for Customer, Account, or Site. This historical record enhances transparency and traceability in scoring calculations. |
| Collections Scoring Data Points (collectionsScoringDataPointsExtract) |
The scoring data point provides details of the score component type configuration data that are collected from the Receivables or Collections modules such as transaction amounts that are overdue, percent of the balance that's overdue, number of transactions that are delinquent, and days outstanding. It's usually in the form of a select statement or function that returns one numeric component value from the database based on existing information. |
| Collections Scoring Formula Data Points (collectionsScoringFormulaDataPointsExtract) |
The scoring formula data point provides the details of the data points selected from the list and used within a scoring formula. The values calculated by a data point are weighted and used in the scoring formula. Collections deliver formulas where a higher score indicates a better chance of collectability and a lower score indicates a lower chance of collectability. One can configure formulas where higher scores result in lower chance of collectability and lower scores a higher chance of collectability, effective way to manage your collections resources and strategies. |
| Collections Strategies (collectionsStrategiesExtract) |
The collections strategy provides the template details for a strategy. |
| Collections Strategy Associated Tasks (collectionsStrategyAssociatedTasksExtract) |
The collections strategy associated task provides the details of the reference table to associate strategy to strategy task. |
| Collections Strategy Groups (collectionsStrategyGroupsExtract) |
The collections strategy group provides the details of the strategy, grouped within a strategy method. |
| Collections Strategy Tasks (collectionsStrategyTasksExtract) |
The collections strategy task provides the details of the strategy task work items. |
| Collectors (collectorsExtract) |
A collector represents the functionality and details related to a customer's collector responsible for collecting past due amounts from customers and sending dunning letters. The details include the collector's name, reference set, type, employee, and inactive date. |
| Consolidated Billing Cycles (receivablesInvoiceConsolidatedBillingCyclesExtract) |
This provides the details of the Receivables Invoice Consolidated Billing Cycle that manages time-based criteria for combining eligible charge lines from multiple sources into invoices within the Receivables system. |
| Control Budget All Segments Accounts (controlBudgetAllSegmentsAccountsExtract) |
A budget all segments account is a combination of budget segment values used in budgetary control. The budget segments can be based on applicable accounting segments or project attributes. Thirty segments are included for the budget account, even if the budgeting flexfield structure has less segments. Any segments not used by the budget account aren't populated. |
| Control Budget Period Statuses (controlBudgetPeriodStatusesExtract) |
A control budget period status determines if a period within a control budget is only available for budgeting, available for budgeting and consumption, or unavailable. |
| Control Budgets (controlBudgetsExtract) |
A control budget contains structural information, such as the budget chart of accounts and budget calendar, and budgetary control validation options, such as whether a transaction with insufficient funds should be stopped or allowed to continue with or without warning and how much tolerance can be factored into the validation. Separate control budgets are used to record budget and consumption balances that are structured by different budget chart of accounts, budget calendar, or period range. |
| Conversion Rate Types (currencyConversionRateTypesExtract) |
A currency conversion rate type defines conversion rate types such as Corporate, Daily, Period End, and Period Average. These conversion rate types are used to convert foreign currency journal amounts to ledger currency equivalents or translate and remeasure account balances to a reporting currency. |
| Cross-Validation Combination Sets (cross-ValidationCombinationSetsExtract) |
A cross-validation combination set validates segment value combinations for at least two segments of a chart of accounts. Any segment for a chart of accounts can be included in the combination set. |
| Cross-Validation Combinations (cross-ValidationCombinationsExtract) |
A cross-validation combination is a combination that's associated with a cross-validation combination set. |
| Currencies (currenciesExtract) |
Currencies are defined and populated through seed data and used to create transactions within the application. This object encapsulates various properties and functionalities related to a specific currency. |
| Currency Conversion Rates (currencyConversionRatesExtract) |
A currency conversion rate defines the daily conversion rates between two currencies to convert foreign currency amounts or translate and remeasure account balances to a reporting currency. |
| Currency Settings (receivablesCustomerProfileClassCurrencySettingsExtract) |
The Receivables Customer Profile Class Amounts business object provides the minimum amount limits per currency necessary to process receipts, statements, dunning amounts and dunning invoice amounts for the given customer profile. |
| Customer Account Contacts (customerAccountContactsExtract) |
The Customer Account Contact provides the details about the designated persons who serve as contacts for the customer account. |
| Customer Account Score Histories (customerAccountScoreHistoriesExtract) |
The Customer Account Score History provides the details of the historical data related to collection scores in Oracle Fusion Advanced Collections. This keeps track of the scoring results assigned to customer accounts as part of the collections activities, allowing users to review how scores have changed over time. |
| Customer Account Site Business Purposes (customerAccountSiteBusinessPurposesExtract) |
The Customer Account Site Business Purpose business object provides the details of the business purposes assigned to customer account sites, for example Bill-to, Ship-to, and Statements. Each customer account site can have one or more business purposes. |
| Customer Account Sites (customerAccountSitesExtract) |
The Customer Account Site business object provides the details of all customer account sites across all business units. A customer account site is one specific location belonging to a customer account. A single customer account can have multiple sites. |
| Customer Accounts (customerAccountsExtract) |
The Customer Account business object provides the details of the specific business activities that the deploying company engages in with a customer party of type Organization or Person. |
| Customer Bankruptcies (customerBankruptciesExtract) |
The customer bankruptcy provides the detail of the business workflow tasks for a bankrupt customer. |
| Customer Bankruptcy Dispositions (customerBankruptcyDispositionsExtract) |
The customer bankruptcy disposition provides the details of the collection bankruptcy disposition history. |
| Customer Bill-To Site Score Histories (customerBillToSiteScoreHistoriesExtract) |
The Customer Bill-To Site Score History provides the details of the historical data related to collection scores in Oracle Fusion Advanced Collections. This keeps track of the scoring results assigned to bill-to sites as part of the collections activities, allowing users to review how scores have changed over time. |
| Customer Case Folder Transactions (customerCaseFolderTransactionsExtract) |
The customer case folder selected transactions contains details of the actual transactions grouped for the case. Grouped transactions allows to perform a limited number of actions on a dynamic set of transactions that are added to the case folder. |
| Customer Case Folders (customerCaseFoldersExtract) |
The customer case folder contains a group of transactions. The grouped transactions allows to perform a limited number of actions on a dynamic set of transactions that are added to the case folder. |
| Customer Collections Ad Hoc Tasks (customerCollectionsAdHocTasksExtract) |
The customer collections Ad Hoc task provides the details of the additional tasks added by a user to a strategy. |
| Customer Collections Strategies (customerCollectionsStrategiesExtract) |
The customer collections strategy configuration used when running strategy management for collection based on a score and contains work items. |
| Customer Collections Task Details (customerCollectionsTaskDetailsExtract) |
The customer collections task detail describes the actionable work generated by a web-service when a strategy task is created. |
| Customer Correspondence Transactions (customerCorrespondenceTransactionsExtract) |
The customer correspondence provides the details of document sent to a customer, such as a dunning letter and invoice copy. |
| Customer Correspondences (customerCorrespondencesExtract) |
The customer correspondence transaction provides the transaction details of dunning. |
| Customer Delinquencies (customerDelinquenciesExtract) |
The customer delinquency provides the transactional data details of the customer delinquencies. |
| Customer Dunning Configuration Details (customerDunningConfigurationDetailsExtract) |
The customer dunning configuration details provides information such as dunning letter name and wait days. Dunning letter names refer to the specific titles or templates associated with each stage of the dunning process. Each letter corresponds to a specific type of communication, typically based on how overdue the account is. Wait days refer to the number of days that must pass before a specific dunning letter is triggered or sent. This determines the interval between when a customer becomes overdue and when the first, second, third, or subsequent dunning letters are sent. |
| Customer Dunning Configurations (customerDunningConfigurationsExtract) |
The customer dunning configuration provides details of the call back information and reference data set specific setup configuration for dunning that identifies the letters to be sent as aged or staged. |
| Customer Profile Currency Settings (customerCurrencyObjectSettingsExtract) |
The Customer Profile Currency Setting provides the details of the credit limits specified for a customer account and bill-to site profile in different currencies. |
| Customer Promise Application References (customerPromiseApplicationReferencesExtract) |
A Customer Promise Application Reference in Oracle Fusion provides details about payments and adjustments made to promised invoices. It tracks the applied amount, payment date, whether a payment was reversed, and the reversal date. This reference links promise details, receivable applications, and adjustments, helping to manage and reconcile payments against customer promises. |
| Customer Promise Details (customerPromiseDetailsExtract) |
The customer promise detail provides the detail of a promise to pay on delinquent invoices. |
| Customer Score Histories (customerScoreHistoriesExtract) |
The customer score history provides the details of the historical data of collection scores. |
| Customer Upload Batch History (receivablesCustomerUploadBatchHistoryExtract) |
The Receivables Customer Upload Batch History business object provides historical information about customer upload batches. When a batch name and compressed file are submitted through the Upload Customers window and confirmed, the batch details are stored in both the Upload Customers Summary and History tables. |
| Customer Upload Batches Overview (receivablesCustomerUploadBatchesOverviewExtract) |
The Receivables Customer Upload Batch Overview table provides summary information about customer upload batches. When a batch name and compressed file are submitted through the Upload Customers window and confirmed, the batch details are stored in both the Upload Customers Overview and History tables. |
| Cycle Dates (receivablesStatementCycleDatesExtract) |
The Receivables Statement Cycle Date provides the details of the dates specified for each interval of a statement cycle. Statements are generated for all customers assigned the statement cycle on the date of each interval. |
| Data Access Assignment (dataAccessAssignmentExtract) |
A data access assignment represents data access assignments to a user in a given role. |
| Data Point Translations (creditDataPointTranslationsExtract) |
The translatable information for the business object. Each business object record will have a set of translation records, one per installed language. Translation records are automatically maintained as you manage the business object. |
| Data Points (creditDataPointsExtract) |
A credit data point is a single piece of credit information about a customer. Data points form the basis for making determinations about a customer's creditworthiness. Examples of data points include: the number or amount of past due invoices, the bank account average balance, the percentage of invoices paid promptly, and the customer credit ratings with external agencies. |
| Data Points (creditCaseFolderTemplateDataPointsExtract) |
A data point is a single piece of credit information about a customer. A credit case folder template contains the data points available by default in a credit case folder for the credit review. |
| Data Points (creditScoringModelDataPointsExtract) |
A credit scoring model data point contains the definition of the value and weight of each data point as it relates to all other data points in the credit scoring model. The definition of a data point includes its range of values, the score assigned to each value, and the relative weighting factor of the data point. The aggregate of all data points constitutes the scoring method of a particular credit scoring model. |
| Delinquent Customers (delinquentCustomersExtract) |
The delinquent customer business object provides the delinquency summary information of all delinquent customers, accounts, or sites. This information is used by collector or collections agents to assess the status of accounts and to prioritize actions that may need to be taken to resolve the debt. |
| Details (collectionsScoringFormulaDataPointDetailsExtract) |
The scoring formula data point detail provides range that defines the thresholds for scoring and value that refers to the specific scoring values assigned based on various data points for scoring components. For example, set ranges like 0 to 50 that's low risk, 51 to 80 that's medium risk, and 81 to 100 that's high risk. Factors like payment history, age of the invoice, credit limits, and customer financial health contribute to the score. |
| Details (receivablesApplicationRuleDetailsExtract) |
The Receivables Application Rule Detail provides detailed information about each of the four application rules that are part of an application rule set. The application rule set determines how to reduce the open line, tax, freight, and late charge amounts for both receipt and on-account credit memo applications. Application rule sets are assigned to the transaction types of the related transactions and to Receivables system options. |
| Distribution Lines (receivablesDistributionSetLinesExtract) |
The Receivables Distribution Set Line provides the details of each of the general ledger account distributions in a distribution set allocated a portion of the miscellaneous receipt amount. The sum of the distributions for a given receipt equal the amount of the receipt. |
| Document Sequence Audits (receivablesDocumentSequenceAuditsExtract) |
The Receivables Document Sequence Audit provides the audit details for every document number generated by the document sequencing framework, supporting transaction completeness and traceability in Oracle Receivables. Document sequences uniquely number Receivables transactions, such as invoices and credit memos, to provide proof of completeness and an audit trail. Document sequencing also provides an audit trail for every accounting event in Oracle Fusion applications that generates document numbers. |
| Encumbrance Types (encumbranceTypesExtract) |
An encumbrance type stores information about encumbrance types, including their identifiers and descriptions. It serves as a comprehensive source for encumbrance type information. |
| External Accounting Transaction Headers (externalAccountingTransactionHeadersExtract) |
An external accounting transaction header contains the Oracle Fusion Accounting Hub transaction information used by the accounting program to generate subledger accounting entries. |
| External Accounting Transaction Lines (externalAccountingTransactionLinesExtract) |
An external accounting transaction line contains the Oracle Fusion Accounting Hub transaction line information. There is a one-to-many relationship between the accounting transaction header and the accounting transaction line, which is used by the accounting program to generate subledger accounting entries. |
| External Transaction Tax Lines (externalTransactionTaxLineExtract) |
External transaction tax line represents the lines for a specific tax related to one or more transaction lines for an external transaction. |
| Financial Sequence Versions (sequenceVersionsExtract) |
A financial sequence version stores information relating to the versions of a sequence definition, such as the version ID and the name of the sequence version. |
| Funds Transfer Error Handling (receivablesFundsTransferErrorHandlingExtract) |
The Receivables Funds Transfer Error Handling provides the details of the mapping between credit card or electronic funds transfer (EFT) error codes and their corresponding corrective actions within Oracle Receivables. This configuration enables the system to intelligently respond to payment processing errors that occur during automatic receipt creation or remittance batch processing. |
| General Ledger Accounts All Segments (generalLedgerAccountsAllSegmentsExtract) |
A general ledger account combination represents the specific grouping of segment values within the Oracle General Ledger. It provides details of all the valid account combinations for each accounting flexfield structure within the General Ledger. |
| General Ledger Segment Value Assignments (generalLedgerSegmentValueAssignmentsExtract) |
A general ledger segment value assignment contains information about the balancing segment values that are assigned to a ledger such as a balancing segment value, the ledger it's assigned to, and the start and end date of the assignment. |
| Grouping Attributes (receivablesAutoInvoiceGroupingAttributesExtract) |
The Receivables AutoInvoice Grouping Attribute provides the details of the list of optional transaction attributes that are available to include in an AutoInvoice grouping rule along with the mandatory attributes. |
| Grouping Rule Attributes (receivablesAutoInvoiceGroupingRuleAttributesExtract) |
The Receivables AutoInvoice Grouping Rule Attribute provides the details used to define the optional transaction attributes in an AutoInvoice grouping rule used to group transaction lines into transactions during the AutoInvoice import process. Every grouping rule contains all the mandatory transaction attributes. |
| Intercompany Organizations (intercompanyOrganizationsExtract) |
An intercompany organization contains details about the providers and receivers of intercompany transactions, including the associated legal entity and business unit for each organization. These organizations serve as both the initiator and the recipient of intercompany transactions. |
| Intercompany Transaction Batch Distributions (intercompanyTransactionBatchDistributionsExtract) |
An intercompany transaction batch distribution contains the distribution details if a user has entered distributions using the automatic proration mode. The amounts entered are prorated for the recipients and distributions lines are created in intercompany transaction distribution line. |
| Intercompany Transaction Batches (intercompanyTransactionBatchesExtract) |
An intercompany transaction batch represents records of transactions within or across legal entities of a parent entity. |
| Intercompany Transaction Distribution Lines (intercompanyTransactionDistributionLinesExtract) |
An intercompany transaction batch distribution contains the distribution details if a user has entered distributions using the automatic proration mode. The amounts entered are prorated for the recipients and distributions lines are created in intercompany transaction distribution line. |
| Intercompany Transaction Headers (intercompanyTransactionHeadersExtract) |
An intercompany transaction header contains the transactions that make up an intercompany transaction batch. |
| Intercompany Transaction Lines (intercompanyTransactionLinesExtract) |
An intercompany transaction line holds line-level details for an intercompany transaction. |
| Intercompany Transaction Types (intercompanyTransactionTypesExtract) |
An intercompany transaction type denotes the type of an intercompany transaction, whether it involves invoicing, and whether it requires manual or automatic approval. |
| Interest Tiers (receivablesLateChargeScheduleInterestTiersExtract) |
The Receivables Late Charge Schedule Interest Tier business object provides a set of period date ranges that identify the number of days overdue and the late charge rate assigned to each period. |
| Intervals (receivablesStatementCycleIntervalsExtract) |
The Receivables Statement Cycle Interval determines how often to generate statements for all customers assigned the statement cycle. Valid values are: weekly, monthly, quarterly. |
| Invoice Installment (payablesInvoiceInstallmentsExtract) |
Invoice installment provides details of the scheduled payments for a supplier invoice. Each supplier invoice has one or more installments, and this information is used to determine when to make payments on an invoice and how much to pay in an automatic payment batch. Each row of this object stores the installment amount, discount available, payment priority, payment status, and so on. |
| Invoice Transaction (payablesInvoiceTransactionsExtract) |
An invoice transaction represents details of all the transactions related to purchases made for producing goods and services or managing business operations, excluding payment requests, taxes, joint ventures, and intercompany transactions. |
| Journal Batches (journalBatchesExtract) |
A journal batch contains information such as batch name and description, status, and running total debits and credits. The batch status indicates whether it has been posted, selected for posting, or in the process of being posted. |
| Journal Categories (journalCategoriesExtract) |
A journal category contains the category information that identifies the purpose of a journal, such as Adjustments or Invoices. |
| Journal Headers (journalHeadersExtract) |
A journal header consists of journal entries with a one-to-many relationship between journal entry batches and journal entries. It stores these entries, containing the associated batch identifier, entry name, description, status, and other information about the journal entry. |
| Journal Lines (journalLinesExtract) |
A journal line contains the journal entry lines information for the journal entry. Journal lines contain the associated journal entry header identifier, line number, and associated account information along with the debits or credits. |
| Journal Lines Reconciliation (journalLinesReconciliationExtract) |
A journal line reconciliation contains reconciled transactions for those accounts where clearing accounts reconciliation is enabled. |
| Journal Sources (journalSourcesExtract) |
A journal source is defined to identify the origin of journals, such as Receivables or Payables. General Ledger supplies a number of predefined journal sources but users can create their own journal sources as well. A journal source contains details about the source name assigned to each journal entry in the general ledger during journal header creation. |
| Late Charge Schedules (receivablesLateChargeSchedulesExtract) |
A late charge schedule outlines the penalties or fees incurred when a payment isn't made by its due date. It provides detailed information on the late charge schedules, including charge schedule names and descriptions. |
| Ledger Balances (ledgerBalancesExtract) |
A ledger balance provides actual, budget, and encumbrance balances for reconciliation and financial reporting. It includes actual, budget, and encumbrance balances in both ledger and foreign currencies for detail and summary accounts. It also provides quarter-to date and year-to- date balances, and period activity balances for each account. |
| Ledger Budget Balances (ledgerBudgetBalancesExtract) |
A ledger budget balance provides general ledger budget balances data used for variance reporting. The budget balances data is loaded into the balances cube for reporting. The budget balances data consists of the budget name, ledger, accounting period, and currency information. |
| Ledger Configuration Details (ledgerConfigurationDetailsExtract) |
The ledger configuration detail defines the detailed input values for a its related secondary ledgers and legal entities, such as ledger type, ledger name and ledger ID. This configuration also specifies the state of each of their configuration steps. |
| Ledger Daily Balances (ledgerDailyBalancesExtract) |
A ledger daily balance provides daily aggregate balances for detail and summary balance sheet accounts when the ledger is enabled for average balance processing. It includes balances in ledger, foreign, entered, and statistical currencies, and translated daily aggregate balances for each nonadjusting period that has ever been opened. |
| Ledger Relationships (ledgerRelationshipsExtract) |
The ledger relationship provides the details of the relationships between ledgers. Each relationship between a primary ledger and a secondary ledger or between a ledger and its reporting currency is stored separately. |
| Ledger Set Assignments (ledgerSetAssignmentsExtract) |
A ledger set assignment contains information about each ledger or ledger set that's contained within a ledger set. Each contained ledger set is expanded into its corresponding ledgers. |
| Ledgers (ledgersExtract) |
A ledger represents a record-keeping book used to track financial transactions. It serves as a central repository for all financial activities within an organization, providing a chronological and systematic account of debits, credits, and balances. Ledgers play a crucial role in financial management, budgeting, and maintaining accurate financial records, tracking expenses, revenues, assets, liabilities, and equity. |
| Legal Entities (legalEntitiesExtract) |
A legal entity represents an entity created under a commercial law which can own property, create obligation, recruit people, trade, account for themselves to regulators, taxation authorities, and owners. It identifies the legal owner or custodian for each business transaction for legal compliance and reporting. |
| Legal Entity Balancing Segment Values (legalEntityBalancingSegmentValuesExtract) |
A legal entity balancing segment value stores the balancing segment values that are assigned to a legal entity. |
| Legal Entity Registrations (legalEntityRegistrationsExtract) |
A legal entity registration represents the status of a legal entity and the right to do business in a territory such as a country. The legal entity can have multiple registration as required by various legislations. Example, A legal entity has to register separately under Company Law, Income Tax Law, and Value Added Tax Law. |
| Legal Reporting Unit Registrations (legalReportingUnitRegistrationsExtract) |
The registration status of the legal reporting unit that has the right to conduct business in a territory, such as a state. For example, the Goods and Services Tax in India requires each entity or line of business to take a separate registration in each state where it has business operations. |
| Legal Reporting Unit Tax Registrations (legalReportingUnitTaxRegistrationExtract) |
Legal reporting unit tax registration represents the tax registration for a legal reporting unit. |
| Line Ordering Attributes (receivablesAutoInvoiceLineOrderingAttributesExtract) |
The Receivables AutoInvoice Line Ordering Attribute provides the details of the columns used to define AutoInvoice line ordering rules. This attribute list comes from the RA_INTERFACE_LINES_ALL table that stores the transaction header and line information of transactions imported using AutoInvoice. |
| Line Ordering Rule Attributes (receivablesAutoInvoiceLineOrderingRuleAttributesExtract) |
The Receivables AutoInvoice Line Ordering Rule Attribute provides the details of the transaction attributes used to define line ordering rules in AutoInvoice. AutoInvoice uses these attributes to determine how to sort and sequence transaction lines when grouping them into invoices, debit memos, and credit memos. AutoInvoice provides transaction attributes from the RA_INTERFACE_LINES_ALL table for use with line ordering rules. The values belonging to a transaction attribute can also be organized in a transaction from least to greatest (Ascending) or greatest to least (Descending). By assigning and sequencing these attributes in line ordering rules, businesses can ensure that invoices are organized in a logical and meaningful way, improving clarity and alignment with business processes during AutoInvoice import. |
| Payables Aging Period Lines (payablesAgingPeriodLinesExtract) |
An aging period line stores details about an individual aging period. The Invoice Aging Report retrieves data based on multiple aging period lines defined in this table. Each row represents a date range used by the report to assign invoices. |
| Payables Aging Periods (payablesAgingPeriodsExtract) |
An aging period stores the header information about the aging period defined for the Invoice Aging Report. Each period used in the report requires a separate row in this object. The PERIOD_NAME column specifies the name assigned to each aging period. |
| Payables Invoice Batches (payablesInvoiceBatchesExtract) |
Invoice batch stores summary information about invoices entered in batches when the Batch Control Payables option is enabled. There is one row for each batch of invoices entered in system. It uses this information to group together invoices that a person entered in one batch. |
| Payables Invoice Distribution (payablesInvoiceDistributionsExtract) |
Invoice distribution provides the allocation details of the costs or charges from an invoice to various accounts or departments within an organization. The details include distribution code combination, distribution amount, and so on. The invoice distributions are entered manually or system generated. An invoice can have multiple distributions, and there is one row for each distribution. |
| Payables Invoice Hold and Release Codes (payablesInvoiceHoldandReleaseCodesExtract) |
A hold code stores the details of a hold or a release code used for invoices. Each row represents a distinct hold or release code. Users can select a predefined hold code from this object when entering or validating an invoice. The system automatically applies these hold codes during Invoice Validation to manage holds, such as matching discrepancies or tax variances. |
| Payables Invoice Holds (payablesInvoiceHoldsExtract) |
The invoice hold provides details regarding holds imposed on a supplier invoice by either end users or the Oracle Payables application. It includes details such as hold date, hold reason, release reason, line held, hold resolution status, and so on. |
| Payables Invoice Line (payablesInvoiceLinesExtract) |
An invoice line represents a specific item or charge listed on an invoice. It provides a detailed breakdown of the products, services, or expenses included in the invoice, along with their respective quantities, unit prices, and total amounts. Invoice lines record invoice lines entered manually, generated automatically, or imported from the Open Interface. An invoice can have one or more invoice lines. An invoice line can have one or more invoice distributions. |
| Payables Invoice Payment (payablesInvoicePaymentExtract) |
Invoice payment records contain details regarding payments made to suppliers, including payment amount, payment number, bank information, and other relevant data. Each payment made for an invoice is represented by a single row in the database. |
| Payables Invoice Workflow History (payablesInvoicesWorkflowHistoryExtract) |
Invoice workflow history stores all the workflow history of each invoice that passes through the Invoice Workflow process. The process creates a record for each approver assigned to review an invoice. |
| Payables Payment (payablesPaymentExtract) |
Payment represents the payments issued to suppliers or refunds received from suppliers. This information is utilized to accurately record and manage outgoing payments to suppliers or incoming refunds from suppliers. |
| Payables Payment Distribution (payablesPaymentDistributionExtract) |
The payment distribution stores the distributions details for each payment accounting event. |
| Payables Payment History (payablesPaymentHistoryExtract) |
The payment history provides the clearing or unclearing status details of payments, as well as the maturity history for future dated payments. Each future dated payment is represented by a row once it matures. Additionally, a row is created in the payment history when a payment is cleared or uncleared. |
| Payables Payment Term Lines (payablesPaymentTermLinesExtract) |
A payment term line stores detailed information about payment terms, outlining the timing and method of payments. These terms are assigned to suppliers and invoices, automatically generating payment installments when a Payables Invoice is created. Each payment term consists of one or more lines, with each line specifying a due date or discount date, and creating a corresponding installment. |
| Payables Payment Terms (payablesPaymentTermsExtract) |
The payment terms specify the timing of payments, including due dates and discount periods. They're assigned to suppliers and invoices, automatically creating payment installments when an invoice is generated. Each payment term consists of one or more lines, with each line corresponding to a separate installment and specifying a due date or discount date. Payment terms are predefined and selected when entering suppliers or invoices to ensure scheduled payments are generated accordingly. |
| Payables Prepayment Application Distributions (payablesPrepaymentApplicationDistributionsExtract) |
Prepayment application distribution stores the information regarding the allocation of prepayment amounts to specific invoice distributions. These records are generated as part of the data extraction preprocessing from Accounts Payable to Subledger Accounting. |
| Payment Schedules (receivablesPaymentTermPaymentSchedulesExtract) |
A receivables payment term payment schedule outlines the specific terms and conditions governing the payment schedule. This includes information about payment terms lines, including payment terms sequence, relative amount, due by days, due by date, day of the month, months ahead, discounts, and percentages. It stores detailed line information for all payment terms. Split payment terms have multiple lines for all payment terms. Payment terms lines are used to calculate when a payment is due and how much of a payment is due. |
| Post Accounting Programs (postAccountingProgramsExtract) |
A post accounting program contains information about the post accounting program short name, associated application identifier and additional details for use in downstream processing, after accounting is completed. |
| Purchase Transaction Tax Lines (purchaseTransactionTaxLineExtract) |
A purchase transaction tax line represents the tax information associated with a transaction line of a purchase transaction. |
| Ranges (creditScoringModelDataPointRangesExtract) |
A credit scoring model data point range contains the numeric and alphanumeric ranges of values assigned to each data point in the credit scoring model. |
| Receipt Activities (receivablesReceiptActivitiesExtract) |
The Receivables Receipt Activity provides the details of the accounting entries for both the cash and credit memo applications, which includes the amount applied, status and related details. Cash applications represent cash receipt applications. If the cash receipt isn't confirmed, applications of that receipt aren't reflected in the payment schedule of the transaction the receipt is applied against. |
| Receivables Activities (receivablesActivitiesExtract) |
A receivables activity represents various transactions and events that occur within the accounts receivables of a business. This activity encompasses a wide range of actions related to managing and processing receivables. The receivables activity includes details such as business unit, name, description, activity type, active option, GL account source, tax rate code source, and distribution set for miscellaneous receipts. Receivables activities provide default accounting information for all activities in Receivables other than transactions and receipts. The receivables activity types are Adjustment, Bank Error, Bills Receivable Funds Recovery, Credit Card Chargeback, Credit Card Refund, Earned Discount, Late Charges, Miscellaneous Cash, Payment Netting, Prepayments, Receipt Write-offs, Refund, Short Term Debt, and Unearned Discount. |
| Receivables Adjustment Approval Action Histories (receivablesAdjustmentApprovalActionHistoriesExtract) |
The Receivables Adjustment Approval Action History business object provides the details of each step in the life cycle of an adjustment. |
| Receivables Adjustments (receivablesAdjustmentsExtract) |
An adjustment refers to any modification made to the accounts receivable balance of an organization. It provides information related to adjustments such as adjustment number, adjustment date, receivables activity, accounting date, installment number, installment balance, and adjustment status. The adjustment information is used to update the AMOUNT_ADJUSTED and AMOUNT_DUE_REMAINING columns in the AR_PAYMENT_SCHEDULES_ALL table. If an adjustment is created with a receipt, the ASSOCIATED_CASH_RECEIPT_ID column in the AR_PAYMENT_SCHEDULES_ALL table stores the receipt ID when the adjustment is created against the invoice, debit memo, or chargeback. |
| Receivables Application Exception Rules (receivablesApplicationExceptionRuleExtract) |
The receivables application exception rule setup describes and groups rules for handling underpayments or overpayments, such as adjusting underpayments or issuing refunds for overpayments. |
| Receivables Application Rule Sets (receivablesApplicationRuleSetsExtract) |
The Receivables Application Rule Set business object provides the details of how a payment applied to a transaction reduces the open balance of the line, tax, freight, and late charge amounts on the transaction. |
| Receivables AutoCash Rule Sets (receivablesAutoCashRuleSetsExtract) |
The AutoCash rule sets determine how receipts are applied to transactions and how customer balances are updated after receipt application. The AutoCash rule set provides the details of the AutoCash rule sets, including the order in which rules appear in a rule set, their name, description, and options to include discounts, finance charges, dispute items, and apply partial payments. |
| Receivables Customer Account Payment Method Details (receivablesCustomerAccountPaymentMethodDetailsExtract) |
The customer account payment method detail provides the details of the receipt method assigned to a customer or customer site. |
| Receivables Distributions (receivablesDistributionsExtract) |
The Receivables Distribution business object provides the details of the accounting distributions for cash receipts, adjustments, credit memo applications, cash receipt applications, and bills receivable transactions. |
| Receivables Enterprise Configurations (receivablesEnterpriseConfigurationsExtract) |
The Receivables Enterprise Configuration business object provides the Receivables system options used to configure the specific Receivables environment for an individual business unit. |
| Receivables Invoicing Rule and Revenue Scheduling Rules (receivablesInvoicingRuleandRevenueSchedulingRulesExtract) |
The Receivables Invoicing Rule and Revenue Scheduling Rule business object provides details of the rules that can be used for imported and manually entered transactions to specify revenue recognition schedules. |
| Receivables Late Charge Lines (receivablesLateChargeLinesExtract) |
The Receivables Late Charge Line business object provides the details of the late charge calculations on each transaction line. |
| Receivables Late Charge Schedule Interest Tier Levels (receivablesLateChargeScheduleInterestTierLevelsExtract) |
The Receivables Late Charge Schedule Interest Tier Level business object provides the details of the rate (flat amount or percentage of open balance) assigned to each period in the interest tier. |
| Receivables Late Charges (receivablesLateChargesExtract) |
The Receivables Late Charge business object provides the details of the late charges assigned to a transaction. |
| Receivables Lockbox Transmissions (receivablesLockboxTransmissionsExtract) |
The Receivables Lockbox Transmission business object provides the details of the validation of the data imported from the bank file using a lockbox file transmission. |
| Receivables Lockboxes (receivablesLockboxesExtract) |
The Receivables Lockbox provides details about the lockbox service, which is offered by commercial banks to corporate customers for outsourcing their accounts receivable payment processing. Oracle Fusion Receivables ensures that the data is valid before creating receipt batches. This verification occurs using Lockbox definitions when transferring receipts from your bank file into the Receivables system. |
| Receivables Manual Receipt Batches (receivablesManualReceiptBatchesExtract) |
The Receivables Manual Receipt Batch and Receivables Automatic Receipt Batch business object provides information that includes the receipt batch name, the total number of receipts in the batch, the total receipt amount, currency, and the deposit date and accounting date, as well as information about each receipt in the manual or automatic receipt batch. |
| Receivables Miscellaneous Cash Receipt Distributions (receivablesMiscellaneousCashReceiptDistributionsExtract) |
The miscellaneous cash receipt distribution is the process of allocating or distributing cash receipts received from miscellaneous sources across various accounts or categories within the accounts receivables. Miscellaneous cash refers to nonrevenue income, such as stock revenue, interest income, and investment income. This distribution ensures that the cash received is appropriately applied to outstanding invoices, credits, or other receivable entries, reflecting accurate financial information within the organization's accounting system. The miscellaneous cash distribution includes details such as receipt type, status, business unit, receipt method, receipt number, receivables activity, distribution set, reference, currency, entered amount, accounted amount, tax rate code, tax account, receipt date, accounting entries, and accounting date. The miscellaneous cash distribution stores one record for each receipt distribution. |
| Receivables Payment Term Discounts (receivablesPaymentTermDiscountsExtract) |
The Receivables Payment Terms Discount business object provides details of the discount settings on a payment terms record. |
| Receivables Payment Terms (receivablesPaymentTermsExtract) |
The receivables payment terms contain the information related to payment terms that outline the timing and method of payment, as well as any applicable discounts or penalties for early or late payment. The information includes reference set, name, description, billing cycle, base amount, discount basis, discount basis date, from and to dates, print lead days, and installment option. |
| Receivables Receipt Distribution Sets (receivablesDistributionSetsExtract) |
A distribution set represents a predefined set of rules or instructions to distribute receipts across multiple accounts or categories automatically. The distribution set typically includes details such as name, business unit, description, total percent distribution, and active status. The distribution sets and distribution set lines are used to automatically distribute miscellaneous receipt payments. In a distribution set, the sum of all the allocation percentages for each line item must be equal to 100%. |
| Receivables Receipt Histories (receivablesReceiptHistoriesExtract) |
The receipt history provides information about each step in the lifecycle of a receipt, including history status, accounting date, entered amount, accounted amount, conversion rate, reversal category, and reversal reason. |
| Receivables Receipt Method Remittance Bank Accounts (receivablesReceiptMethodRemittanceBankAccountsExtract) |
The Receivables Receipt Method Remittance Bank Account business object provides the details of the remittance bank accounts assigned to a receipt method. |
| Receivables Receipt Methods (receivablesReceiptMethodsExtract) |
The receipt method contains information that defines how payments are applied or allocated within receivables. The information includes the receipt class, receipt method name and description, the option for debit memos to inherit receipt numbers, the option for receipt to inherit transaction numbers, grouping number of receipts rule, receipt maturity date rule, and lead days. For automatically created receipts, receipt methods define the rules for creating these receipts. For manually created receipts, receipt methods define user-definable receipt types. Each receipt method is linked with a specific set of remittance bank accounts, which can be assigned to a receipt. For instance, if you receive lockbox transmissions from multiple banks, you can create a lockbox receipt method with the bank accounts from the banks assigned to them. |
| Receivables Receipt Remittance References (receivablesReceiptRemittanceReferencesExtract) |
The Receivables Receipt Remittance Reference business object provides the number and document reference used to match receipts to transactions. |
| Receivables Receipt Sources (receivablesReceiptSourcesExtract) |
The Receivables Receipt Source outlines the default values for the receipt class, bank account, and payment method for each receipt within a receipt batch, which are grouped for batch processing. This functionality also assists Oracle Receivables in managing the grouping, processing, and accounting of receipts effectively. |
| Receivables Receipts (receivablesReceiptsExtract) |
The receivables receipt contains information about receipts, including receipt number, receipt method, receipt type, status, business unit, customer, receipt date, amount, and total applied amount. One record is created for each receipt. |
| Receivables Standard Memo Lines (receivablesStandardMemoLinesExtract) |
The memo line provides information about standard memo lines for invoices, debit memos, on-account credits, debit memo reversals, and chargebacks, including unit of measure, standard price, memo line translation, tax rate code, standard invoicing and revenue scheduling rules, and reference set. It also derives the revenue account when AutoAccounting is based on standard line items. |
| Receivables Transaction Deferred Revenues (receivablesTransactionDeferredRevenuesExtract) |
The Receivables Transaction Deferred Revenue business object provides the details of deferred, or unrecognized, revenue assigned to an unearned revenue account. |
| Receivables Transaction Distributions (receivablesTransactionDistributionsExtract) |
The transaction distribution is a process of allocating or distributing the amounts within a receivable transaction to various accounts or categories. The transaction distribution provides the details of the accounting records for revenue, unearned revenue, and unbilled receivables for each invoice or credit memo line. At least one distribution must exist for each invoice or credit memo line. |
| Receivables Transaction Lines (receivablesTransactionLinesExtract) |
A Transaction Line is a specific line item within a transaction record. This line item contains detailed information about a particular transaction related to receivables, such as an invoice, credit memo, debit memo, and bills receivables. The line typically includes details such as item, description, memo line, quantity, unit price, amount, sales order, and tax. For invoices entered manually, the quantity ordered and quantity invoiced are the same. For imported invoices, quantity ordered, quantity invoiced, unit standard price, and unit selling price can differ. Some fields like description, tax rule, quantity ordered, UOM code, unit standard price, and unit selling price are required. The credit memos other than on-account credits, must have a PREVIOUS_CUSTOMER_TRX_LINE_ID value. |
| Receivables Transaction Payment Schedules (receivablesTransactionPaymentSchedulesExtract) |
A receivables transaction payment schedule outlines the timeline and terms for payments to be made by customers for sales of goods or services. The details include information about all transactions except adjustments and miscellaneous cash receipts. It's updated when activities occur against an invoice, debit memo, chargeback, credit memo, on-account credit, or receipt. When a receipt is applied to a transaction, the system updates the amount applied, the remaining amount due, and the transaction status. The status changes from open to closed when the amount due remaining is zero. |
| Receivables Transaction Source (receivablesTransactionSourcesExtract) |
The Receivables Transaction Source business object determines specific behavior of Receivables transactions, including transaction numbering, transaction type and credit memo defaulting, and AutoInvoice behavior for imported transactions. |
| Receivables Transaction Types (receivablesTransactionTypesExtract) |
The transaction type contains information about transaction types, including transaction type set, legal entity, transaction type name, description, transaction class, transaction status, from date, creation sign, generate bill option, invoice type, credit memo type, application rule set, and payment terms. It contains every transaction type used for invoices, bills receivable, and credit memos. |
| Receivables Transactions (receivablesTransactionsExtract) |
The receivables transaction contains information about transactions, details including transaction number, bill-to-customer, transaction type, transaction date, due date, accounting date, payment terms, and remit-to address, invoices, debit memos, credit memos, and bills receivable are distinguished by their associated transaction types. |
| Recommendation Lines (receivablesRemittanceReferenceRecommendationLinesExtract) |
The Receivables Remittance Reference Recommendation Line business object provides the details of each line of a transaction recommended for receipt application. |
| Recommendations (receivablesRemittanceReferenceRecommendationsExtract) |
The Receivables Remittance Reference Recommendation business object provides the details of how Receivables recommends remittance references for matching and applying customer payments to transactions. This includes the cash receipt, the recommended transaction, the recommendation status, matching score, and applied matching rules. |
| Reference Accounts (receivablesTransactionTypeReferenceAccountsExtract) |
The Receivables Standard Memo Line Reference Account business object determines the accounts to use on invoices that use memo lines, when AutoAccounting depends on memo line. |
| Reporting Book Asset Accounting Lines (reportingBookAssetAccountingLinesExtract) |
A reporting book accounting line contains journal entry lines for every asset transaction that has a financial impact on the reporting asset book. These accounting lines are used to create journal entries in Oracle Subledger Accounting and transfer them to Oracle General Ledger. |
| Reporting Book Asset Deferred Depreciation Details (reportingBookAssetDeferredDepreciationDetailsExtract) |
A deferred depreciation detail stores information about deferred depreciation amounts calculated for each distribution of the assets used to create journal entries for the reporting book. |
| Reporting Book Asset Financial Details (reportingBookAssetFinancialDetailsExtract) |
Reporting book financial detail transactions store the financial information and depreciation rules required for calculating depreciation in the reporting asset book. |
| Reporting Book Asset Impairments (reportingBookAssetImpairmentsExtract) |
A reporting book impairment transaction stores the impairment transaction details, such as the net selling price, value in use, and impairment loss for the asset and cash generating unit in the reporting asset book. |
| Reporting Book Asset Lease Expense Details (reportingBookAssetLeaseExpenseDetailsExtract) |
A lease expense detail stores lease expense details for each asset associated with the lease at the distribution level in the reporting asset book. |
| Reporting Book Asset Lease Expense Summaries (reportingBookAssetLeaseExpenseSummariesExtract) |
A lease expense summary contains lease expense details for each asset associated with the lease in the reporting asset book. |
| Reporting Book Asset Periodic Depreciation Details (reportingBookAssetPeriodicDepreciationDetailsExtract) |
The periodic depreciation detail stores the depreciation amount for each of the assets in the reporting asset book calculated by the Calculate Depreciation process and generates depreciation expense journal entries. |
| Reporting Book Asset Periodic Depreciation Summaries (reportingBookAssetPeriodicDepreciationSummariesExtract) |
The periodic depreciation summary stores the depreciation expense, year-to-date depreciation, depreciation reserve, impairment reserve, and revaluation reserve for assets in the reporting asset book. |
| Reporting Book Asset Retirements (reportingBookAssetRetirementsExtract) |
A retirement transaction stores information such as the retirement date, cost retired, retirement convention, and gain or loss in the reporting asset book. |
| Reporting Book Asset Revaluations (reportingBookAssetRevaluationsExtract) |
A reporting book revaluation transaction contains the carrying value of a company's fixed asset or group of fixed assets to account for any major changes in their fair market value. |
| Reporting Book Asset Source Lines (reportingBookAssetSourceLinesExtract) |
A reporting book source line contains asset acquisition invoice information from source applications, such as Oracle Payables, Oracle Receiving, and Oracle Project Costing, for tracking and reporting purposes in the reporting asset book. A source line contains all costs imported from source applications, including, items, freight, taxes, project labor, and expenses. |
| Revenue Additional Satisfaction Events (revenueAdditionalSatisfactionEventsExtract) |
The Revenue Additional Satisfaction Event business object provides the details of additional satisfaction events applied to the revenue document lines. |
| Revenue Adjustments Details (receivablesRemitToLocationsExtract) |
The Receivables Remit-to Location business object provides the details of the address on transactions and statements where customers are to send payment for their open receivables. |
| Revenue Billing Lines (revenueBillingLinesExtract) |
The contract billing line provides the billing information for performance obligation lines. |
| Revenue Contingencies (receivablesRevenueContingenciesExtract) |
The Receivables Revenue Contingency provides the details of the seeded and user-defined revenue contingency definitions. These contingencies represent conditions that must be satisfied before revenue can be recognized on a transaction. Each definition includes the type of contingency, the triggering event, and the resolution criteria. Revenue contingencies are used to enforce compliance with accounting standards by deferring revenue recognition until specific contractual or regulatory conditions are met. This helps ensure that revenue is recognized accurately and in accordance with the organization's revenue policies. |
| Revenue Contract Accounting Events (revenueContractAccountingEventsExtract) |
The accounting event provides the details of the accounting events of customer contract. |
| Revenue Contract Billing Line Applications (revenueContractBillingLineApplicationsExtract) |
The Revenue Contract Billing Line Application business object provides the billing application information for source document lines. |
| Revenue Contract Devolve Performance Obligation Details (revenueContractDevolvePerformanceObligationDetailsExtract) |
The Devolve Performance Obligation Detail business object provides summary information of promised detail lines for devolved performance obligations. Each row represents total of all the promised detail line amounts apportioned by accounting period. |
| Revenue Contract Performance Obligation Immaterial Revision Details (revenueContractPerformanceObligationImmaterialRevisionDetailsExtract) |
The Performance Obligation Immaterial Revision Detail business object provides the details of actions performed on the performance obligations of customer contract when immaterial change is processed. |
| Revenue Contract Performance Obligations (revenueContractPerformanceObligationsExtract) |
The customer contract performance obligation provides the details of the performance obligations of customer contract. |
| Revenue Contract Pricing Dimension Combinations (revenueContractPricingDimensionCombinationsExtract) |
The pricing dimension combination provides pricing dimension details for establishing the standalone selling price of a product or price. |
| Revenue Contract Promised Detail Satisfaction Events (revenueContractPromisedDetailSatisfactionEventsExtract) |
The Revenue Contract Promised Detail Satisfaction Event business object provides the information about satisfaction events of the performance obligation lines in a customer contract. |
| Revenue Contract Promised Details (revenueContractPromisedDetailsExtract) |
The customer contract promised detail outlines the promised detail lines in a customer contract. |
| Revenue Contract Promised Line Billing Events (revenueContractPromisedLineBillingEventsExtract) |
The Revenue Contract Promised Line Billing Event business object provides the information about billing events of the performance obligation lines within a customer contract. |
| Revenue Contract Promised Line Distributions (revenueContractPromisedLineDistributionsExtract) |
The promised detail line distribution provides the distribution details of the performance obligation line. |
| Revenue Contract Promised Line Immaterial Revision Details (revenueContractPromisedLineImmaterialRevisionDetailsExtract) |
The Promised Line Immaterial Revision Detail business object provides the details of actions performed on the promised detail lines of customer contract when immaterial change is processed. |
| Revenue Contract Standalone Selling Prices (revenueContractStandaloneSellingPricesExtract) |
The standalone selling price provides the details of unit standalone selling prices |
| Revenue Contracts (revenueContractsExtract) |
The customer contract provides the details of the customer contract. This includes performance obligations and promised detail lines. |
| Revenue Pricing Lines (revenuePricingLinesExtract) |
The pricing line provides the revised net value details for a document line. |
| Revenue Source Document Additional Sublines (revenueSourceDocumentAdditionalSublinesExtract) |
The Revenue Contract Source Document Additional Subline business object provides the fulfillment details of additional satisfaction event details for each promised detail. |
| Revenue Source Document Lines (revenueSourceDocumentLinesExtract) |
The source document line detail includes document lines from upstream applications, identified as contracts and performance obligations, and used in standalone selling price calculations. |
| Revenue Source Document Sublines (revenueSourceDocumentSublinesExtract) |
The Revenue Source Document Subline business object provides the fulfillment details for each promised detail line from upstream application. |
| Revenue Source Documents (revenueSourceDocumentsExtract) |
The contract source document provides the details of the documents from the upstream applications. |
| Rules (receivablesApplicationRulesExtract) |
The Receivables Application Rule provides the individual application rules that are part of an application rule set. The order in which the application rules are arranged in an application rule set determines when and how to reduce the open line, tax, freight, and late charge amounts for both receipt and on-account credit memo applications. |
| Rules (receivablesAutoCashRulesExtract) |
The Receivables AutoCash Rule provides detailed information about each AutoCash Rule that's part of an AutoCash Rule Set. The six AutoCash rules determine how to apply a receipt to an open debit item. |
| Sales Credit Types (receivablesSalesCreditTypesExtract) |
The Receivables Sales Credit Type business object determines the sales credits allocated to salespersons on Receivables invoices. The Quota sales credit type is for revenue allocations and the Nonquota sales credit type is for nonrevenue allocations. |
| Sales Transaction Tax Line (salesTransactionTaxLineExtract) |
A sales transaction tax line represents the tax information associated with a transaction line of a sales transaction. |
| Score Histories (collectionScoreHistoriesExtract) |
The Collections Score History provides the details of the historical data related to collection scores in Oracle Fusion Advanced Collections. This keeps track of the scoring results assigned to customers, accounts, or bill-to sites as part of the collections activities, allowing users to review how scores have changed over time. |
| Scoring Formulas (collectionsScoringFormulasExtract) |
The collections scoring formula provides the details of the score definitions. |
| Scoring Models (creditScoringModelsExtract) |
A credit scoring model is used to calculate a customer's credit score. It contains the data points and scoring method used for a particular credit review. Users can create a different scoring model for each type of credit review required. |
| Segment Value Column Flattened Hierarchies (segmentValueColumnFlattenedHierarchiesExtract) |
A segment value column flattened hierarchy contains the relationship between various nodes in a given tree version in a column flattened manner for the General Ledger related tree structures. |
| Segments (receivablesAutoAccountingRuleSegmentsExtract) |
The Receivables AutoAccounting Rule Segment provides the details used to define each individual segment of a chart of accounts combination as part of the AutoAccounting setup in Oracle Receivables. This provides the segment-level configuration for AutoAccounting rules. Each row in this table represents a single segment (such as Company, Department, Account) of an accounting combination and specifies the source from which the value of that segment should be derived during transaction processing. |
| Standalone Selling Price Profile Assignments (standaloneSellingPriceProfileAssignmentsExtract) |
The standalone selling price profile assignment provides the details of the assignments of Vendor-Specific Objective Evidence templates to items. |
| Standard Messages (receivablesCustomerStatementStandardMessagesExtract) |
The Receivables Customer Statement Standard Message setup provides the details of the texts that Receivables prints at the bottom of the customer statements. |
| Statement Cycles (receivablesStatementCyclesExtract) |
The statement cycle is a period over which transactions are compiled and processed. The cycle can be weekly, monthly, or quarterly. Statement cycles are assigned to customer profile classes and determine when statements are sent to customers. The details include statement cycle name, description, interval, active option, business unit, and print dates. Cycle intervals are weekly, monthly, or quarterly. Statement cycles are assigned to customer profile classes and determine when statements are sent to customers. |
| Statement Deliveries (customerStatementDeliveriesExtract) |
The Customer Statement Delivery provides all the necessary details for delivering customer statements via email, including delivery method, recipient email addresses, and email content metadata, facilitating automated and auditable statement distribution in Oracle Fusion Receivables |
| Statistical Units of Measure (statisticalUnitsofMeasureExtract) |
A statistical unit of measure contains information about where both statistical and monetary amounts for the same account are used within a single journal entry. |
| Subledger Accounting Entry Distribution Links (subledgerAccountingEntryDistributionLinksExtract) |
A subledger accounting entry distribution link contains the subledger accounting entry header identifier, line number, account information, related debits or credits, and source distribution identifiers. This information is used to establish the relationship between source transactions and subledger accounting entry lines. |
| Subledger Accounting Entry Headers (subledgerAccountingEntryHeadersExtract) |
A subledger accounting entry header consists of accounting entries generated by the Accounting program with a one-to-many relationship between subledger accounting entry and subledger accounting entry lines. It stores these entries, containing the associated accounting entry header identifier, ledger identifier, accounting period, subledger application, journal category, accounting entry status, transfer status, and other information about the accounting entry. |
| Subledger Accounting Entry Lines (subledgerAccountingEntryLinesExtract) |
A subledger accounting entry line contains the accounting entry lines information for each subledger accounting entry. These lines contain the associated accounting entry header identifier, line number, and associated account information and related debits or credits. |
| Subledger Accounting Event Classes (subledgerAccountingEventClassesExtract) |
A subledger accounting event class contains information related to subledger event classes associated with a transaction entity. It stores details such as the application identifier, entity code, event class code, and other relevant information associated with the event class. |
| Subledger Accounting Event Types (subledgerAccountingEventTypesExtract) |
A subledger accounting event type contains information related to the subledger accounting event types associated with an event class. It stores details such as the application identifier, entity code, event class code, event type code and other relevant information associated with the event type. |
| Subledger Accounting Events (subledgerAccountingEventsExtract) |
A subledger accounting event contains all information related to a specific accounting event and the transactions linked to the event which are used to generate accounting entries. It stores details associated with the accounting event such as the associated accounting event identifier, application identifier, event type, event status, event processing status, and other information associated with the accounting event. |
| Subledger Accounting Methods (subledgerAccountingMethodsExtract) |
A subledger accounting method represents a set of accounting rules which are designed to adhere to a standard set of accounting requirements. It stores details such as the accounting method code, accounting method type code, associated chart of accounts and other relevant information associated with the accounting method. |
| Subledger Applications (subledgerApplicationsExtract) |
A subledger application refers to the predefined applications or accounting hub source systems that use subledger accounting rules to generate accounting entries for their transactions. It stores details such as the application identifier, application type code, associated journal source and other relevant information associated with the subledger application. |
| Subledger Journal Line Rules (subledgerJournalLineRulesExtract) |
A subledger journal line rule outlines the details of an accounting entry line within a subledger accounting entry. Each journal line rule is linked to a specific event class and contains details such as application identifier, entity, event class, natural side, accounting class and other relevant information associated with the journal line rule. |
| Subledger Mapping Set Inputs (subledgerAccountingMappingSetInputsExtract) |
A subledger mapping set input contains information about the input sources assigned to subledger mapping sets. It consists of details such as the mapping set short name, application identifier, mapping set input identifier, sequence of the input source, lookup type or value set assigned to the input source and other such information associated with the mapping set input source. |
| Subledger Mapping Set Types (subledgerAccountingMappingSetFlavorsExtract) |
A subledger mapping set type contains the assignment information between mapping sets and chart of accounts or value sets. It consists of details such as the mapping set short name, application identifier, identifier of the chart of accounts or value set, flexfield segment code and other such information associated with the mapping set type. |
| Subledger Mapping Set Values (subledgerMappingSetValuesExtract) |
A subledger mapping set value contains the output values that map to each combination of input values for subledger mapping sets. It consists of details such as the mapping set short name, application identifier, mapping set value identifier, input values, output value and other such information associated with the mapping set value. |
| Subledger Mapping Sets (subledgerAccountingMappingSetsExtract) |
A subledger mapping set contains the mapping set header information such as the mapping set short name, application identifier, accounting flexfield assignment code, accounting flexfield segment code, number of inputs and other information which is used in account rules to derive an account combination, segment value or value set value. |
| Subledger Sources (subledgerSourcesExtract) |
A subledger source contains all predefined subledger sources and user-defined sources which are used to configure accounting rules. It stores details such as the application identifier, source type, data type and other relevant information associated with the source. |
| Subledger Supporting Reference Sources (subledgerSupportingReferenceSourcesExtract) |
A subledger supporting reference source contains the association of supporting reference with the corresponding subledger sources. It stores details such as the application identifier, supporting reference, source, source type and other relevant information associated with the supporting reference source. |
| Subledger Supporting References (subledgerSupportingReferencesExtract) |
A subledger supporting reference stores additional source information about an accounting entry at the line level. It stores details such as the application identifier, supporting reference identifier, supporting reference order and other relevant information associated with the supporting reference. |
| Subledger Transaction Entities (subledgerTransactionEntitiesExtract) |
A subledger transaction entity represents a transaction for which accounting events have been generated in subledger accounting. It stores details such as the associated entity code, source identifiers, and security identifiers, which are provided by the subledger based on its data and security model. |
| Summary Tax Lines (summaryTaxLineExtract) |
Summary tax line provides summarized information for transaction tax lines associated with a Payable transaction. |
| Supporting Reference Balances (supportingReferenceBalancesExtract) |
A supporting reference balance provides the beginning and period activity balances for a combination of supporting references and an account. This information can be used to report on additional supporting information and reconcile with the source systems. |
| Supporting Reference Combinations (subledgerSupportingReferenceCombinationsExtract) |
A supporting reference combination consists of a unique combination of supporting references which is associated with a supporting reference combination identifier. |
| Tax Jurisdictions (taxJurisdictionExtract) |
Tax jurisdiction represents a geographic area where a tax is levied by a specific tax authority. |
| Tax Rates (taxRateExtract) |
The tax rate is a percentage of an amount, a value per unit quantity, or a fixed sum per transaction at which an individual or corporation is taxed and is effective for a period of time. |
| Tax Regime (taxRegimeExtract) |
The tax regime is a set of tax rules that determines the treatment of one or more taxes administered by a tax authority. |
| Tax Statuses (taxStatusExtract) |
This view provides details on the tax status extract. |
| Taxes (transactionTaxExtract) |
A tax is a classification of a charge imposed by a government through a fiscal or tax authority. |
| Taxpayer Identifier (taxpayerIdentifierExtract) |
Taxpayer identifier is a unique identifier assigned to a party by a tax authority, indicating their obligation to pay and report direct taxes, such as corporation taxes. |
| Third Party Site Tax Profiles (thirdPartySiteTaxProfileExtract) |
Third party site tax profile represents the tax profile defined for a third party site such as a customer site or supplier site. The tax profile represents the details of a party's transaction tax activities. It can include tax registration, tax exemptions, configuration options, main and default information, party fiscal classifications, tax reporting codes, and account details. |
| Third Party Site Tax Registrations (thirdPartySiteTaxRegistrationExtract) |
Third party site tax registration represents the tax registration for a third party site such as a customer site or supplier site. |
| Third Party Tax Profiles (thirdPartyTaxProfileExtract) |
Third party site tax profile represents the tax profile defined for a third party site such as a customer site or supplier site. The tax profile represents the details of a party's transaction tax activities. It can include tax registration, tax exemptions, configuration options, main and default information, party fiscal classifications, tax reporting codes, and account details. |
| Third Party Tax Registrations (thirdPartyTaxRegistrationExtract) |
Third party tax registration represents the tax registration for a third party such as a customer or supplier. |
| Transaction Classes (receivablesAutoInvoiceGroupingRuleTransactionClassesExtract) |
The Receivables AutoInvoice Grouping Rule Transaction Class provides the details required to determine how transaction lines belonging to a transaction class are grouped into transactions during the AutoInvoice import process. A grouping rule contains a number of mandatory attributes that apply to all transactions, and it can optionally contain one or more optional attributes. Two or more transaction lines must contain identical mandatory and optional transaction attributes, as defined in the grouping rule, for AutoInvoice to group them together in the same transaction. |
| Transaction Histories (receivablesRevenueAdjustmentsDetailsExtract) |
The Receivables Revenue Adjustments Detail business object provides the details of the revenue adjustments on transactions. |
| Transaction Level Segments (collectionsStrategyTransactionLevelSegmentsExtract) |
The strategy transaction level segment provides the details of the transaction segments that can be used to define tasks for collections strategy. These transaction segments are used to define how different types of transactions should be treated within a collections strategy. By linking transaction types to specific strategy tasks, businesses can implement more targeted, automated, and effective collections strategies that are tailored to the specific nature of each transaction. This ensures that resources are focused on the right tasks at the right time, improving the overall efficiency and effectiveness of the collections process. |
| Transaction Strings (receivablesAutoMatchTransactionStringsExtract) |
The Receivables AutoMatch Transaction String provides the details of the string handling settings of the AutoMatch rule set used to transform and compare reference strings to transaction numbers during automatic receipt application. |
| Transmission Fields (receivablesLockboxTransmissionFormatFieldsExtract) |
The Receivables lockbox transmission format field provides the details of each field in a lockbox transmission, including field type, field starting position, field ending position, description, data type formats, and other information. |
| Transmission Formats (receivablesLockboxTransmissionFormatsExtract) |
The Receivables Lockbox Transmission Format business object provides the details of the predefined lockbox transmission formats. |
| Transmission Records (receivablesLockboxTransmissionFormatRecordsExtract) |
The Receivables lockbox transmission format record provides the details of each record in a lockbox transmission format, including record identifier, record type, and description. Lockbox receipt processing makes use of transmission formats, also called control files (.ctl), to specify how the data in a bank file is organized for import into the Receivables interface tables. |
| Withholding Summary Tax Lines (withholdingSummaryTaxLineExtract) |
Withholding summary tax line is the summarized withholding tax line information for a transaction. |
| Withholding Tax Lines (withholdingTaxLineExtract) |
Withholding tax line represents the withholding tax for an item line. |