| Oracle® Retail Financial Integration for Oracle Retail Merchandise Operations Management and Oracle Financials Oracle® Retail Financial Integration for Oracle Retail MOM and Oracle Financials Release 19.0 F23583-03 |
|
 Previous |
 Next |
| Oracle® Retail Financial Integration for Oracle Retail Merchandise Operations Management and Oracle Financials Oracle® Retail Financial Integration for Oracle Retail MOM and Oracle Financials Release 19.0 F23583-03 |
|
Previous |
Next |
This chapter describes how to request the chart of accounts combination validation and discusses:
Oracle Retail interfaces
Oracle GL interfaces
Data requirements
Oracle General Ledger (GL) is the system of record for chart of accounts segment combinations. Chart of accounts (segments) combinations are set up manually in Oracle Retail Merchandising System (RMS), Retail Invoice Matching (ReIM), and Retail Sales Audit (ReSA). This manual setup enables assignment of transaction data in sales audit, stock ledger, and invoice match to specific account codes. ReIM also creates segment combinations dynamically during the invoice match transaction processing.
While creating the valid segment combinations, Oracle Retail validates each created combination individually against Oracle GL. Any valid segment combination in Oracle Retail must exist as a valid combination in Oracle GL. Oracle Retail publishes the segment combination to Oracle GL for validation. Oracle GL verifies the combination and returns the status to Oracle Retail. If the combination is valid, the combination is stored in the Oracle retail database tables for future validation purpose.
Oracle Retail sends these data for validation to Oracle GL:
Requesting system (RMS, ReIM, or ReSA)
Set of books (GL business unit)
Segment or ChartField combination values
Oracle GL sends the validation status whether the combination is valid. The RFI layer copies all the other information from the original request and sends these response data to Oracle Retail:
Requesting system (RSM, ReIM, or ReSA)
Set of books (GL business unit)
Date
Validation status - valid or invalid
These are the prerequisites for this integration:
The following DVM's are available in RFI_XREF_DVM table if EBS or CFIN is the Oracle Financials system:-
COA_GLELEMENT_REIM_DVM
COA_GLELEMENT_RESA_DVM
COA_GLELEMENT_RMS_DVM
COA_STATUS_DVM
Also, Set of Books should be setup in RMS/ReSA/ReIM similar to EBS GL or CFIN GL
The following DVM's are available in RFI_XREF_DVM table if PeopleSoft is Oracle Financials system:-
COA_GLELEMENT_LEDGER_GROUP_DVM (Set of Books mapped to corresponding Ledger Group for PeopleSoft GL Business Unit)
COA_STATUS_DVM
COA_GLELEMENT_DVM
Also, Set of Books should be setup in RMS/ReSA/ReIM similar to PeopleSoft GL Business unit
This design assumes that:
The Oracle Retail request contains a field called requesting system that identifies the system that is requesting the service so that the correct Retail segment is retrieved from the Domain Value Map (DVM) lookup.
DVM (Retail segments to Oracle accounts) may be set up differently for each system (RMS, ReSA, or ReIM).
Oracle GL receives the array of the values for each segment. If the structure is segement1-segment2-segment3-segementn, then Oracle GL expects that the array size (in this case is n) and the array of value in the order of 1 to n is passed.
Multiple sets of GL accounts can be sent from Oracle Retail to the Oracle Financials validation web service.
Once the validated chart of account is stored in Retail, Oracle GL doesn't send any updates if chart of account becomes invalid.
The Account Segment values in Oracle Financials system (EBS, PeopleSoft or CFIN) and Retail are same.
These services are delivered with the chart of accounts combination validation integration flow:
GlAccountValidationServiceCons
GlAccountValidationService
GlAccountValidationServiceProviderImpl
This diagram illustrates the chart of accounts combination validation integration flow:
When the chart of accounts validation process is initiated:
Oracle Retail calls the GlAccountValidationServiceCons Consumer service with Requesting System, Set of Books Id, Segment 1..N values whenever a GL account is required to be validated.
The GlAccountValidationServiceCons Consumer service calls the GlAccountValidationService service which routes the request to GlAccountValidationServiceProviderImpl Provider service
The GlAccountValidationServiceProviderImpl Provider service does the following transformations.
The Set of Books ID from Oracle Retail is transformed to ChartOfAccountIdentification field in E-business suite using Chart of Accounts DVM lookup COA_GLELEMENT_<Requesting System>_DVM (for e.g. if RMS is the requesting system, COA_GLELEMENT_RMS_DVM is used) lookup has the entry like < Set of Books ID >-SEGMENT1 for Retail value and < ChartOfAccountIdentification>-SEGMENT1 for the E-business suite value.
The COA_GLELEMENT_<Requesting System>_DVM lookup is also used to transform the Segment combination in Retail to Segment Combination in E-business suite.
GlAccountValidationServiceProviderImpl Provider service invoked the E-Business suite account validation API. E-Business suite account validation API validates the account combination and returns valid/invalid status.
Regardless of whether the account is valid or invalid, a transformation occurs in GlAccountValidationServiceProviderImpl Provider service to populate the account_status field. A COA_STATUS_DVM DVM is used to transform the E-Business suite value to the Oracle Retail value.
If the account is valid, then sets the valid CCID received from E-Business suite account validation API to the response; otherwise, set the received CCID to the response variable.
These services are delivered with the chart of accounts combination validation integration flow:
GlAccountValidationServiceCons
GlAccountValidationService
GlAccountValidationServiceProviderImpl
This diagram illustrates the chart of accounts combination validation integration flow:
When the chart of accounts validation process is initiated:
Oracle Retail calls the GlAccountValidationServiceCons Consumer service with Requesting System, Set of Books Id, Segment 1..N values whenever a GL account is required to be validated.
The GlAccountValidationServiceCons Consumer service calls the GlAccountValidationService service which routes the request to GlAccountValidationServiceProviderImpl Provider service
The GlAccountValidationServiceProviderImpl Provider service does the following transformations.
The Set of Books ID from Oracle Retail is transformed to ChartOfAccountIdentification field in E-business suite using Chart of Accounts DVM lookup COA_GLELEMENT_DVM (for e.g. if RMS is the requesting system, COA_GLELEMENT_RMS_DVM is used) lookup has the entry like < Set of Books ID >-SEGMENT1 for Retail value and < ChartOfAccountIdentification>-SEGMENT1 for the E-business suite value.
The COA_GLELEMENT_DVM lookup is also used to transform the Segment combination in Retail to Segment Combination in E-business suite.
GlAccountValidationServiceProviderImpl Provider service invoked the PeopleSoft COMBO_CF_EDIT_REQUEST service validation API which validates the account combination and returns valid/invalid status.
Regardless of whether the account is valid or invalid, a transformation occurs in GlAccountValidationServiceProviderImpl Provider service to populate the account_status field. A COA_STATUS_DVM DVM is used to transform PeopleSoft value to the Oracle Retail value.
If the account is valid, then sets the valid CCID received from PeopleSoft account validation API to the response; otherwise, set the received CCID to the response variable.
These services are delivered with the chart of accounts combination validation integration flow:
GlAccountValidationServiceCons
GlAccountValidationService
GlAccountValidationServiceProviderImpl
AccountCombinationService
This diagram illustrates the chart of accounts combination validation integration flow:
When the chart of accounts validation process is initiated:
Oracle Retail calls the GlAccountValidationServiceCons Consumer service with Requesting System, Set of Books Id, Segment 1..N values whenever a GL account is required to be validated.
The GlAccountValidationServiceCons Consumer service calls the GlAccountValidationService service which routes the request to GlAccountValidationServiceProviderImpl Provider service
The GlAccountValidationServiceProviderImpl Provider service does the following transformations.
The Set of Books ID from Oracle Retail is transformed to Ledger ID field in CFIN using Chart of Accounts DVM lookup COA_GLELEMENT_DVM (for e.g. if RMS is the requesting system, COA_GLELEMENT_RMS_DVM is used) lookup has the entry like < Set of Books ID >-SEGMENT1 for Retail value and <ChartOfAccountIdentification>-SEGMENT1 for the Financials Cloud value.
The COA_GLELEMENT_DVM lookup is also used to transform the Segment combination in Retail to Segment Combination in Financials Cloud.
GlAccountValidationServiceProviderImpl Provider service invoked the Financials Cloud AccountCombinationService service validation API which validates the account combination and returns valid/invalid status.
Regardless of whether the account is valid or invalid, a transformation occurs in GlAccountValidationServiceProviderImpl Provider service to populate the account_status field. A COA_STATUS_DVM DVM is used to transform CFIN value to the Oracle Retail value.
If the account is valid, then sets the valid CCID received from Financials Cloud account validation API to the response; otherwise, set the received CCID to the response variable.
