Or Ebs 1311 Intg

Oracle Retail / Oracle EBusiness Suite
Integration Guide Using Accelerator July 2009
Note: The following is intended to outline our general
product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracles products remains at the sole discretion of Oracle.
Contents
1 Introduction .................................................................................................................. 1 Related Documents.................................................................................................................1 Overview..................................................................................................................................2 Integrated Data Flows ............................................................................................................3 Oracle Retail BPEL Process Manager Patch ........................................................................3 Software Release Levels .........................................................................................................3 Oracle E-Business Suite Release Levels ........................................................................3 Oracle Retail Release Levels ...........................................................................................4 2 Solution Footprint........................................................................................................ 5 3 Architecture.................................................................................................................. 7 Oracle E-Business SuiteOracle Retail Outbound Process Flow ......................................8 Oracle RetailOracle E-Business Suite Inbound Process Flow .........................................9 Integration Performance ......................................................................................................10 Install the BPEL Server.........................................................................................................10 Deploy BPEL Processes ........................................................................................................11 Deploy New BPEL Processes .......................................................................................11 Install the Integration Accelerator Patch ...........................................................................13 Installation ......................................................................................................................13 Setting up the Integration Accelerator Patch .............................................................14 Oracle E-Business Suite General Ledger Chart of Accounts to RMS.............................15 Oracle E-Business Suite Exchange Rates to RMS..............................................................17 Oracle E-Business Suite Vendor Reference Data to RMS ................................................19 Setting Up Supplier Sites ..............................................................................................19 Transferring Supplier Information from Oracle E-Business Suite to RMS ............19 Oracle E-Business Suite Payment Terms to RMS .............................................................22 Oracle E-Business Suite Freight Terms to RMS ................................................................24 Oracle Retail Stock Ledger, Invoices, and Sales to General Ledger ...............................25 ReIM Approved Payments to Accounts Payable .............................................................27 ReIM Journal Entries to General Ledger............................................................................30 BPEL Process Manager Error Handling.............................................................................31 BPEL Process Manager Processing and Scheduling.........................................................33 4 RMS Business Processes Configuration ................................................................ 35 RMS System Options ............................................................................................................35 Organization Units ...............................................................................................................35 Currency Exchange Rates ....................................................................................................35 Supplier Address Types.......................................................................................................35 Country Codes.......................................................................................................................35 RMS General Ledger Setup .................................................................................................35 Suppliers.................................................................................................................................35
iii
Freight Terms, Payment Terms, Currency Exchange Rates, and General Ledger Chart of Accounts ............................................................................................................................36 Oracle E-Business Suite Org Units and Site IDs ...............................................................36 Supplier Address ...........................................................................................................38 Store and Warehouse Maintenance.............................................................................39 System Parameter Maintenance..........................................................................................40 General Ledger Cross-Reference.........................................................................................40 General Ledger Account Maintenance...............................................................................40 5 Oracle Retail Invoice Matching................................................................................. 41 Matched Invoices and Approved Documents ..................................................................41 Prepaid Invoices....................................................................................................................41 Non-Merchandise Invoices..................................................................................................41 Posting Transaction Codes to the Accounts Payable Staging Table ..............................41 6 RMS Stock Ledger ..................................................................................................... 43 7 ReSA Sales Information ............................................................................................ 45 Design Overview ..................................................................................................................45 8 Business Intelligence ................................................................................................ 47 Select Business Intelligence Designer Responsibility.......................................................47 Switch to Business Intelligence Administrator Responsibilities ....................................49 Switch System Administrator Responsibility ...................................................................49 9 Middleware Configuration......................................................................................... 51 Database Adapter Configuration........................................................................................51 Configure the Oracle E-Business Suite Connection Pool .........................................53 Configure the Oracle Retail Connection Pool ............................................................54 Configure the Oracle E-Business Suite Data Source .................................................55 Configure the Oracle Retail Data Source ....................................................................56 Configure the Oracle E-Business Suite Connection Factory ....................................57 Configure the Oracle Retail Connection Factory.......................................................59 Notification Services.............................................................................................................60 JMS Adapter Configuration for RIB ...................................................................................60 Create and Configure Connection Factories ..............................................................60 Configure JMS Connection Factory Settings (application.xml and oc4jra.xml files) for RIB Server .................................................................................................................62 A Appendix: General Ledger Chart of Accounts Mapping........................................ 65 B Appendix: Supplier Mapping .................................................................................... 67 C Appendix: Supplier Address Mapping..................................................................... 73 D Appendix: Currency Rates Mapping........................................................................ 75 E Appendix: Freight Terms Mapping .......................................................................... 77 F Appendix: Payment Terms Mapping........................................................................ 79
iv
G Appendix: Stock Ledger, Sales Journal, Miscellaneous Payments ..................... 81 H Appendix: New Matched Invoices for Payment...................................................... 87 IM_AP_STAGE_HEAD to AP_INVOICES_INTERFACE ...............................................87 IM_AP_STAGE_DETAIL to AP_INVOICE_LINES_INTERFACE.................................88 V_IM_FINANCIALS_STAGE to GL_INTERFACE..........................................................89
1
Introduction
This document describes considerations for integration of Oracle Retail applications with Oracle E-Business Suite. This document provides information for the implementation team to assess product requirements, configuration opportunities, and constraints related to this integration.
Note: The financial applications noted in this document are
part of Oracle E-Business Suite. Where not otherwise specified, a financial application (for example, General Ledger) refers to an Oracle E-Business Suite application, not an Oracle Retail application.
Related Documents
For more information, see the following documents in the Oracle Retail / Oracle EBusiness Suite documentation: Oracle Retail Merchandising Batch Schedule Oracle Retail Merchandising System Data Model Oracle Retail Merchandising System Operations Guide Oracle Retail Merchandising System User Guide Oracle Retail Sales Audit User Guide Oracle Retail Invoice Matching Operations Guide Oracle Retail Invoice Matching User Guide Oracle BPEL Process Manager Developers Guide Oracle BPEL Process Manager Installation Guide Oracle BPEL Process Manager Development Guide 10g Release 3 (10.1.3.1). This version of the guide also is valid for 10.1.3.4 (see Metalink Note 741499.1) General Ledger User Guide Release 12 (part number B31218-01) Oracle Payables User Guide Release 12 (part number B25454-01) Other Oracle E-Business Suite documentation, available at the following URL: http://www.oracle.com/technology/documentation/index.html
Integration Guide Using Accelerator 1
Overview
Oracle Retail applications have a generic interface to integrate with financial applications. This document describes the specific requirements and considerations for integration with Oracle E-Business Suite 12.0.4 and Oracle Merchandise Operations Management (MOM) applications. The following illustration shows applications available to the retailer through this integration.
2 Oracle E-Business Suite
Integrated Data Flows

This integration supports the following flows:
1.
Oracle E-Business Suite financial applications can provide financial reference data to the Oracle Retail Merchandising System (RMS). (This includes chart of accounts, vendors, currency exchange rates, and freight and payment terms data.) The program used to import data to RMS supports multiple charts of accounts, as well as control parameters at the supplier site level, such as lead time and payment terms. Oracle Retail Invoice Matching (ReIM) matches invoices to purchase order receipts and reconciles discrepancies. Matched invoices can be forwarded to Oracle Accounts Payable for payment. ReIM can also forward certain transactional data (such as write-offs and prepayments) directly to the General Ledger open interface. RMS tracks all inventory movements within the system through its stock ledger. Daily and period-based financial information transfers can be scheduled to the General Ledger. Oracle Retail Sales Audit (ReSA) allows summarized sales information to be forwarded to General Ledger. High-volume sales details can be aggregated by item, store and day, and transaction type. Oracle Accounts Payable (AP) can act as the payment system for supplier invoices in the context of this integration.
2.
3.
4.
5.
Oracle Retail BPEL Process Manager Patch

Patch 8733303 is required to deploy BPEL processes for this integration.
Software Release Levels

After patching processes are completed, manual setup and synchronization are required for the configuration. These considerations are detailed further later in this document. The following are the Oracle E-Business Suite and Oracle Retail release levels to which this document applies. For more information about software patches, see release notes on Metalink: https://metalink.oracle.com
Oracle E-Business Suite Release Levels

Oracle Retail applications can interface with the following Oracle E-Business Suite release levels:
Oracle E-Business Suite Release 12.0.4

Oracle E-Business Suite Accounts Payable patch 6252889 Oracle Application Server 10g (10.1.3.4) Oracle Database 10gR2 (10.2.0.3.0) Oracle BPEL (Business Process Execution Language) Process Manager 10.1.3.4.0 with patch 7272722 (p7272722_101340_LINUX.zip).
Oracle Retail Release Levels

The following Oracle Retail applications are certified for interface with Oracle E-Business Suite: Oracle Retail Merchandising System (RMS) 13.1.1 Oracle Retail Sales Audit (ReSA) 13.1.1 Oracle Retail Invoice Matching (ReIM) 13.1.1 Oracle Retail Integration Bus 13.1.1
2
Solution Footprint
The financial integration solution is delivered through middleware through a publishsubscribe model. Financial reference data is published from Oracle E-Business Suite. Oracle Retail then subscribes to these processes through its own middleware architecture. On the outbound transactional flows, the middleware populates financial staging tables. These staging tables are then polled and used to populate the standard financial open interface capabilities in General Ledger (GL) and Accounts Payable (AP).
BPEL Oracle Retail Sales Audit
Sales Journal Sales Data Post to Stock Ledger
Sales Data Post to Stock Ledger
Direct Access Layer RIB
Stock Ledger
Oracle Retail Merchandising System

Currency, Exchange Rates, Receipt Terms, Terms Ranking, Status Location Type, Deal Bill Backs
Suppliers and Locations Currency Rates Freight Terms Payment Terms GL Chart of Accounts Credit Prepaid Asset Receipt Write-Offs Debit Memos Credit Memos Credit Notes Forced and Prepaid Invoices Matched Invoices Non-Merchandise Invoices
Oracle E-Business Suite (General Ledger, Stock Ledger)
Batch
Oracle Retail Invoice Matching
Oracle E-Business Suite (Accounts Payable)
Oracle Retail and Oracle E-Business Suite IntegrationLogical View
The integration process described here supports the partitioning of financial data among multiple sets of books (SOBs). The CHART_OF_ACCOUNTS_ID SOB identifiers are defined in the first phase of integration. This allows Oracle Retail applications to identify the integration SOBs for extraction and publication of the financial reference data from Oracle E-Business Suite. The Oracle Retail GL Setup table FIF_GL_SETUP holds the reference data to facilitate the integration. The Oracle E-Business Suite operating unit also is defined in Oracle Retail applications. This is the document-level layer in the enterprise model (for example, purchase orders). The operating unit is added to the Oracle Retail enterprise model to allow more granular financial recognition (supplier, store, warehouse, and so on).
3
Architecture
The integration solution is managed using these middleware components: Oracle BPEL (Business Process Execution Language) Process Manager Oracle Retail Integration Bus (RIB) Oracle BPEL Process Manager is a Java-based solution that runs on Oracle Application Server. Oracle BPEL Process Manager uses database adapters to connect to data sources in Oracle E-Business Suite. RIB is a Java-based, asynchronous message bus. It subscribes to messages created and published by BPEL processes--to inject the message payload data elements into the RMS database. The following Oracle Retail applications use Java Message Service (JMS) adapters to connect to RIB: Oracle Retail Management System (RMS) Oracle Retail Invoice Matching (ReIM) Oracle Retail Sales Audit (ReSA) The applications integrated are as follows: General Ledger (GL) Accounts Payable (AP) Oracle Retail Merchandising System (RMS) Oracle Retail Invoice Matching (ReIM) Oracle Retail Sales Audit (ReSA) The four major components of the model are: Oracle E-Business Suite Release running on Oracle Application Server (OAS) 10g (10.1.3.4.0) Oracle BPEL Process Manager 10.1.3.4.0, which requires Oracle Application Server 10g (10.1.3.4.0) Oracle Retail 13.1.1 applications (RMS, ReIM, ReSA) Oracle Retail Integration Bus 13.1.1 The BPEL and RIB middleware components are used to link and transform data as follows: Outbound data from Oracle E-Business Suite is sent on a net change basis to RIB. This data is processed within Oracle Retail applications, and the appropriate tables are updated. Summarized financial transactions from Oracle Retail applications are staged to financial tables. These tables are processed by BPEL processes to extract the data and populate the financial open interfaces in GL and AP. From that point, standard open interface processing is adopted. Installation of the integration accelerator patch is required to create a link between the BPEL and RIB systems.
Note: This solution is an integration accelerator. Extra effort
is required from the software implementer, such as setting default values and/or custom enhancements.
Oracle E-Business SuiteOracle Retail Outbound Process Flow

The following figure shows the outbound reference data flows that are supported for Oracle E-Business Suite through Oracle BPEL Process Manager.
Outbound Process Flow
The outbound process flow is as follows:

1.
From General Ledger, account code combinations, suppliers, currency rates, freight terms, and payment terms are retrieved on a net change basis. All records added or changed are processed on a scheduled basis. BPEL processes extract these records and perform data transformations to XML record formats that are compatible with RIB topics. The XML messages are published to RIB. The subscribing RIB adapter attempts to update the appropriate business data object, based on message topic and action (create, modify, or delete). Once the update is completed, the message is dropped from the JMS topic. If an error occurs while an update is attempted, the message is written to RIB Error Hospital for manual review or automatic re-publication to the adapter.
2. 3.
Oracle RetailOracle E-Business Suite Inbound Process Flow

The following figure shows the inbound transactional data flows that are supported for Oracle E-Business Suite through Oracle BPEL Process Manager.
Inbound Process Flow
The inbound process flow is as follows:

1.
The Oracle Retail business process extracts data objects to the standard financial integration staging tables. These tables are: Matched purchase order receipts (new invoices) Debit and credit memos Inventory movements (stock ledger) Sales audit (sales journal)
2.
BPEL processes read the financial staging tables directly. These processes extract the details and perform data transformation to populate the standard GL or AP open interfaces. After the standard open interface tables are populated, normal import and error management processes are performed in Oracle E-Business Suite.
3.
Integration Performance
A major consideration for the integration has been performance. Retail volumes are characteristically substantial and the solution needs to support high volumes. For the outbound reference data from Oracle E-Business Suite, the volumes are not considered a concern, other than potential data load of GL account code combinations, for example. The inbound transactional processes have been heavily tested for performance. Oracle Retail applications populate their standard financial staging tables through their normal business processes. These processes have been optimized accordingly.
Install the BPEL Server

The following installation process requires full system root and database administration rights.
1. 2. 3.
Install Oracle Database 10gR2 (10.2.0.1), and patch the database to level 10.2.0.2 Create user bpel1/bpel1 with a DBA role. Apply patches to the Oracle E-Business Suite and RMS databases, as noted in Chapter 1.
Note: R12 RUP4 should be installed. If an earlier version is
installed, the following patches must be applied: 6509776:R12.AP.A and 6665695:R12.AP.A

4. 5. 6. 7. 8.
Create user access for BPEL processes on Oracle E-Business Suite and RMS databases. Install Oracle Application Server 10.1.3.4.0 with J2EE and HTTP server options. Run the Integration Repository Creation Assistant to create the BPEL hydration databases in the BPEL database (first step). Install Oracle SOA Suite (Oracle BPEL Process Manager 10.1.3.4.0 only) in the same ORACLE_HOME as Oracle Application Server. Configure Oracle BPEL Process Manager. See Chapter 9, Middleware Configuration, for the configuration steps to set up the database adapters, RIB JMS adapters, and BPEL e-mail notification service.
9.
Start the Oracle BPEL Process Manager engine.
For more information, see the Oracle BPEL Process Manager Installation Guide 10g Release 3 (10.1.3.1.0) for UNIX and Microsoft Windows (part number E10402-01). See also Metalink Note 741499.1.
Deploy BPEL Processes

The BPEL processes are defined in patches (jar files) on Metalink. Patch 8733303 is required to deploy BPEL processes for this integration. These processes cannot be seeded within Oracle BPEL Process Manager. They require manual deployment through the BPEL Process Manager Console.
Deploy New BPEL Processes

See Oracle BPEL Process Manager documentation for information about using BPEL Process Manager and the BPEL Console.
1.
Start the BPEL Process Manager Console (BPEL Console) and log in.
BPEL Process Manager Console Login
2.
Click the BPEL Processes tab. New BPEL processes can be added by way of this interface.
Deploy New BPEL Processes 3.
Click Browse to view directories for the processes to deploy. These are as follows:
BPEL Process
Business Process General ledger chart of accounts General ledger currency exchange rates Vendors Payment terms Freight terms RMS stock ledger transactions to General Ledger ReSA inbound sales to General Ledger ReIM approved payments to Accounts Payable ReIM to General Ledger
SendVendorsToRMS.jar SendPaymentTermsToRMS.jar SendFreightTermsToRMS.jar
4.
After each process is deployed, update the following properties for each process (see the following figure): COA_ID (chart of accounts ID) portType (port type) SYSADMIN_EMAIL (system administrators e-mail address)
BPEL Process User Properties
Install the Integration Accelerator Patch

Installation of the integration accelerator patch is required to create a link between the BPEL and RIB systems. This software patch is available from Oracle Retail and enables the integration between Oracle E-Business Suite and Oracle retail applications. See the following documentation for more information about the installation procedure. For information about Oracle Retail hot fixes that must be applied prior to procedures in this document, see the Oracle Retail - Oracle E-Business Suite Integration Solution Summary document included in this download. Oracle Application Server Installation Guide 10g Release 3 (10.1.3.1.0) for Linux x86 B31013-01 Oracle BPEL Process Manager Installation Guide
Installation
Complete the following steps to install Oracle E-Business Suite R12 and Service Oriented Architecture (SOA) Suite 10.1.3.1 and to integrate them with the Oracle Retail Merchandising System (RMS) and Oracle Retail Integration Bus (RIB) data sources.
1.
Install Oracle E-Business Suite R12 (12.0.4.0) using Rapid Install release 12. Verify that the installation was successful. If there were any errors or failures, they must be fixed before continuing. Enable Oracle E-Business Suite R12 DB Tier sys user password for remote access. This is needed for synchronizing the SOA Suite user with the database while SOA installation is being performed.
2.
3. 4. 5.
Create three new SOA users (orabpel, oraesb, and orawsm) in the Oracle E-Business Suite R12 database. Create a separate OS Home directory for installing the SOA Suite. Make changes for corresponding path for the separate oraInventory (oraInst.loc). Unzip SOA Suite 10.1.3.1.0 (soa_linux_x86_101310_disk1.cpio) in the new Home directory. Follow the README, install/soa_schemas/irca, and run the irca.sh script to populate the seed data in the above three SOA Suite Users. Install the SOA Suite. Verify that the installation was successful. If there were any errors or failures, they must be fixed before continuing. Upgrade the SOA Suite to 10.1.3.4.0. Apply the Upgrade Patch Set 7272722 on top of the existing SOA Suite Home. Follow the Patch Set ReadMe instructions. Apply Integration Patch 6252889 on the applications tier through Admin.
6. 7. 8.
Setting up the Integration Accelerator Patch

Prior to setting up the integration accelerator patch, verify that the following conditions exist in the destination environment: Patches 6252889:R12.AP.A, 6509776:R12.AP.A, and 6665695:R12.AP.A must be applied before installation of this pack. Ensure that you have the UNIX login with proper privileges (for example, applmgr). Install the Common Pack. Complete the following steps to set up the integration accelerator patch. This should only be done after Oracle E-Business Suite and Service Oriented Architecture (SOA) Suite have been installed.
1. 2. 3.
Unzip the pack on a windows machine. Create a staging directory (for example, /tmp) on the UNIX server that hosts the concurrent manager. FTP the compressed archive file (shown below) containing the customizations to the ./tmp directory in binary mode.
8733303.zip
4.
Log in to the UNIX server and change directory (../tmp). Uncompress the archive file in the staging directory using the following command.
uncompress 8733303.zip
Note: Retail_EBS.tar file is created.

5. 6. 7.
Extract the files from the archive using the following command.
tar -xvf Retail_EBS.tar
Navigate to the directory CODE/AP/DB_OBJECTS. Execute the following.

chmod 755 * sh APRETEKVIEWS.install
8. 9.
Navigate to the directory CODE/GL/DB_OBJECTS. Execute the following.

chmod 755 * sh GLRETEKVIEWS.install
The commands in steps 7 and 9 recreate all the database objects in the Apps Schema for AP and GL.
Oracle E-Business Suite General Ledger Chart of Accounts to RMS

Oracle E-Business Suite sends the general ledger code combinations reference data to Oracle Retail applications. This data is extracted by the BPEL Process Manager and published to the Oracle Retail Integration Bus (RIB) as XML messages on the JMS topic in RIB. RIB APIs then pick up these messages for insertion into RMS application. The BPEL Process Manager has error handling routines to accommodate system error scenarios, while the RIB APIs have built-in error handling routines for errors on their end. These errors are written to the RIB Hospital (error repository). The design assumes all of the following: The interface requires valid, detailed account code combinations. Combinations are created by attaching the chart of accounts to the ledger. Multiple ledgers can share the same chart of accounts. Each chart of accounts contains segmentsor value setsthat identify company, department, and so on. Oracle RMS 13.0.x accommodates only 10 general ledger segments, even though the staging table (FIF_GL_ACT) imports 15 segments from EBS. The General Ledger Chart of Accounts (GLCOA) data interface to RMS transfers the ledger accounts details in Oracle E-Business Suite to multiple sets of books in Oracle RMS (by way of FIF_GL_ACCT). The corresponding CHART_OF_ACCOUNTS_IDs must be provided by the implementation team at the time of deployment to allow this setup. Set up the General Ledger chart of accounts. Go to Setup Set of Books in Oracle Retail. Enter the Oracle CHART_OF_ACCOUNTS_IDs to synchronize the systems.
Oracle E-Business Suite chart of accounts segments are 25 characters in length; Oracle Retail RIB accepts up to 25 characters (where type is Varchar2). The BPEL process requires the CHART_OF_ACCOUNTS_ID as a parameter to the deployment descriptor property COA_ID at installation time. This parameter is used to bind to the SQL statement to select code combinations for a particular chart of accounts related to the set of books. The implementation team provides the value for the SYSADMIN_EMAIL descriptor property from the BPEL Console.
SendGLCCToRMS BPEL Process
Oracle E-Business Suite Exchange Rates to RMS

Oracle E-Business Suite sends foreign currency conversion rates information to Oracle Retail applications. This data is extracted by the BPEL Process Manager and published to the Oracle Retail Integration Bus (RIB) as XML messages on the JMS topic in RIB. RIB APIs then pick up these messages for insertion into RMS. The BPEL Process Manager has error handling routines to accommodate system error scenarios, while the RIB APIs have built-in error handling routines for errors on their end. These errors are written to RIB Hospital (error repository). The design assumes all of the following: Oracle E-Business Suite and Oracle Retail applications store currency conversion rates in different ways. Oracle E-Business Suite maintains the rates with respect to a from currency to a to currency on a particular date; however, Oracle Retail applications store only the rates in the context of a to currency for a given date. The from currency is assumed to be the RMS primary currency. Oracle E-Business Suite sends all conversion rates to Oracle Retail applications in the message, and the Oracle Retail API populates its table with only those currencies where the from currency is equal to the RMS primary currency. Different types of currencies are used in Oracle E-Business Suite and Oracle Retail applications. Oracle E-Business Suite considers only spot, corporate, and user rate types as default exchange rate types. Oracle Retail applications allow for multiple rate types, but they only use Consolidation rate type for default processing. (This is determined based on a system option in RMS.) As part of the configuration, a crossreference must be created in RMS that allows the data from Oracle E-Business Suite to be translated correctly into RMS terminology. This cross-reference is held in the FIF_CURRENCY_XREF table in RMS. Currency codes (for example, USD) are the same in both Oracle E-Business Suite and Oracle Retail applications. The list of valid currencies is maintained separately by scripts in each application. However, because the currency code size is smaller in Oracle Retail applications (3 characters), currency codes in Oracle E-Business Suite must be entered with three or fewer characters. For the JNDI entries, the implementation team must provide the required installation-specific connection information in the oc4j-ra.xml file for the corresponding adapters. The JNDI entries to be modified are as follows: Database adapter oc4j-ra.xml: Oracle Database connection information JNDI name: eis/DB/OracleConnection JMS adapter oc4j-ra.xml: Oracle Retail RIB JMS topic connection information JNDI name: eis/JMS/SendCurrencyRates The implementation team provides the value for the SYSADMIN_EMAIL descriptor property from the BPEL Console.
The BPEL process requires a starting conversion date as a parameter to the deployment descriptor property VDATE at installation time. This parameter is used to bind to the SQL statement to select currency conversion rates with conversion dates greater than the setup date VDATE specified in the Oracle Retail applications. Oracle Retail applications successfully subscribe only to exchange rates with current and future dates. Exchange rates should be entered individually for each date. Exchange rates entered through Rates Manager, Date range functionality, or the interface table, are datestamped, but not time-stamped. This means that the creation/update date stamp is less than the last time BPEL polled, and these records would be ignored.
SendCurrRatesToRMS BPEL Process
Oracle E-Business Suite Vendor Reference Data to RMS

Oracle E-Business Suite sends vendor reference data to Oracle Retail applications. This data is extracted by the BPEL Process Manager and published to the Oracle Retail Integration Bus (RIB) as XML messages on the JMS topic in the RIB. RIB APIs then pick up these messages for insertion into RMS. The BPEL Process Manager has error handling routines to accommodate system error scenarios, while the RIB APIs have built-in error handling routines for errors on their end. These errors are written to RIB Hospital (error repository).
Setting Up Supplier Sites

For every supplier, any number of supplier sites with different addresses and contacts can be created. Supplier sites can be used to identify the purpose of the supplier address. For example: Payment: These sites are used to enter invoices and for making payments. Purchasing: These sites are used to create purchase orders. RFQ (request for quotations) only: These sites are used to create requests for quotations in a purchasing site. An RFQ site cannot be used for creating purchase orders.
Note: Only Payment and Purchasing address types are
included in the interface between Oracle E-Business Suite and RMS. As a part of the integration, the Oracle Retail supplier model includes the Oracle Operating Unit as an attribute of the supplier address. Addresses provided by Oracle E-Business Suite include this data element and use it as a cross-reference between the two applications. The Organization ID is mapped to operating unit, which is where actual business transactions take place. For each site, the following information is entered at the supplier level: Contact information (name address, telephone number, and so on), organization, business classification, products, receiving, and payment details.
Note: The contact information (address line1, city, state,
country, and postal code) is mandatory for each supplier site. A single supplier can buy from several sites and send payment to several sites. However, one site may be treated as a primary pay site.
Transferring Supplier Information from Oracle E-Business Suite to RMS

The Vendor data interface to RMS transfers the supplier and supplier address details in Oracle E-Business Suite to Vendor in Oracle RMS. The number of fields required in RMS is 63 for supplier and 23 for supplier address. Oracle E-Business Suite is not required to furnish all the details. Some fields are limited to RMS and can be modified through RMS screens only. The data is transferred in XML file format.
Oracle E-Business Suite and Oracle Retail application have different vendor models. The Oracle Retail Vendor table stores information about suppliers, and the Address table stores information about vendor addresses. The addresses are striped by purpose. For example, if a supplier uses the same address as an order, mailing, and remittance address, this information is entered as three separate address records with different purposes. The Oracle E-Business Suite supplier model is Operating Unit striped. As a part of the integration, the Oracle Retail supplier model has been modified to include the Oracle Operating Unit as an attribute of the supplier address. Addresses provided by Oracle E-Business Suite include this data element. This is used as a cross-reference between the two applications. Only two address types are interfaced from Oracle to RM Oracle Pay (Remittance in Oracle Retail applications) and Oracle Purchase (Ordering in Oracle Retail). These address types are maintained by Oracle through the interface and include the Oracle Operating Unit. Other address types are maintained in RMS and do not include the Oracle Operating Unit. Oracle Retail applications require many different attributes at the supplier level that are specific to the retail industry and not currently available in the Oracle E-Business Suite vendor model. Only the minimum supplier information is transferred to Oracle Retail applications. The attributes specific to retail are entered by RMS users. Oracle E-Business Suite interfaces all the suppliers (not employees) information to Oracle Retail applications. Oracle Retail applications maintain profile information (supplier contact, contact phone number, and so on) at the supplier level, as well as at the address level. Oracle E-Business Suite maintains all the profile information at the site level. Oracle E-Business Suite applications send the profile information from the first purchasing site for the supplier to be used as the supplier-level profile information in Oracle Retail applications. If no contact is found, the default is UNKNOWN. Oracle E-Business Suite has effective dates to maintain the state of the supplier/site records. Oracle Retail applications have an enabled flag to maintain the same information. Oracle E-Business Suite compares the effective dates to the system date when interfacing to Oracle Retail applications to populate the enabled (SUPP_STATUS) flag. When running in an environment with value-added tax (VAT), RMS requires VAT regions to be associated with suppliers. Oracle E-Business Suite has no concept similar to the RMS VAT region and thus cannot provide this information to RMS. When RMS receives a vendor message from Oracle E-Business Suite when VAT functionality is enabled, the suppliers in RMS are created without a VAT region and are created in inactive status, regardless of the status indicated in the message. For suppliers to be valid and usable in RMS, users must manually modify the newlycreated supplier records in RMS, adding a VAT region and updating the status to active. Currency codes are not a required element for Oracle E-Business Suite suppliers, but they are required in RMS. If Oracle E-Business Suite sends a supplier without a currency code, RMS creates the supplier with status = Inactive, and with currency code = the primary currency defined in RMS. The RMS user can manually update the currency code of the supplier as necessary.
SendVendorToRMS BPEL Process
Oracle E-Business Suite Payment Terms to RMS

Oracle E-Business Suite sends payment terms reference data to Oracle Retail applications. This data is extracted by the BPEL Process Manager and published to the Oracle Retail Integration Bus (RIB) as XML messages on the JMS topic in the RIB. RIB APIs then pick up these messages for insertion into RMS. The BPEL Process Manager has error handling routines to accommodate system error scenarios, while the RIB APIs have built-in error handling routines for errors on their end; these errors are written to RIB Hospital (error repository). This design assumes all of the following: Oracle E-Business Suite sends only interface payment terms in the base installed language to Oracle Retail applications. The other language translations are handled in Oracle Retail applications as needed, using base translation functionality. Payment terms rank information is not mandatory in Oracle E-Business Suite. It is a required attribute for Oracle Retail applications. Oracle E-Business Suite sends a default value of 1 for the rank for any payment terms that have no rank specified in Oracle E-Business Suite. The payment terms name is used for the payment terms description when the Description field is not populated in Oracle E-Business Suite. The Payment Terms Enabled flag value is evaluated based on the start and end effective dates of the payment terms and the current system date. The Due Days, Due Amount, Discount Days, Discount Percent, and Discount Months Forward values default to 0 when they are not populated in Oracle E-Business Suite. The Due Day of the Month, Discount Day of the Month, and Due Cut Off Day default to 1 when they are not populated in Oracle E-Business Suite. The discount calculated by Oracle Retail applications may be different from the discount calculated by Oracle Accounts Payable because of differences in data models.
SendPaymentTermsToRMS BPEL Process
Oracle E-Business Suite Freight Terms to RMS

Oracle E-Business Suite sends freight terms reference data to Oracle Retail applications. This data is extracted by the BPEL Process Manager and published to the Oracle Retail Integration Bus (RIB) as XML messages on the JMS topic in the RIB. RIB APIs then pick up these messages for inserting into RMS. The BPEL Process Manager has error handling routines to accommodate system error scenarios, while the RIB APIs have built-in error handling routines for errors on their end; these errors are written to RIB Hospital (error repository). This design assumes that Oracle E-Business Suite only sends terms in the base installed language to Oracle Retail applications. The other language translations are handled in Oracle Retail applications as needed, using base translation functionality.
SendFreightTermsToRMS BPEL Process
Oracle Retail Stock Ledger, Invoices, and Sales to General Ledger

Oracle Retail applications populate the STG_FIF_GL_DATA staging table with general ledger transactional data related to Oracle Retail Sales Audit (ReSA) and stock ledger. Oracle E-Business Suite pulls this general ledger data from the Oracle Retail staging table, performs transformations, and populates the GL_INTERFACE table in Oracle E-Business Suite. This process is orchestrated by BPEL Process Manager using database adapters. BPEL Process Manager has error handling routines to accommodate system error scenarios. If an error is encountered, a notification is sent to a designated person with the role of system administrator. The notification contains pertinent information about the BPEL process that encountered the error. The system administrator uses the BPEL Console to troubleshoot and reprocess the data. This design assumes all of the following: The Oracle Retail batch process that populates the STG_FIF_GL_DATA table populates the complete dataset for a given period (daily, monthly, and so on). There are no checks and balances to validate whether the journals are balanced before processing the records. Invoking the standard concurrent program Journal Import is a manual process. The modality for invoking this program is an implementation decision and not part of this design. Batch information is not available in Oracle Retail staging tables. Batch names are automatically generated by Oracle E-Business Suite Journal Import. This generates a unique batch name for each run of Journal Import. This design depends on an agreed-upon data mapping between the Oracle Retail staging table STG_FIF_GL_DATA and the Oracle E-Business Suite table GL.GL_INTERFACE. This data mapping includes any required transformations and application of business rules to ensure data integrity in General Ledger. Refer to Appendix A for details about data mapping and transformations. Oracle Retail applications always populate the code_combinations_id and do not send the accounting segment information. (The accounting segment information is still populated in the table; however, Oracle E-Business Suite does not use this information.) The following master data synchronization and setup/configuration must be completed before running this interface: The chart of accounts must be synchronized between Oracle E-Business Suite (master) and Oracle Retail applications (slave). Currency codes and rates must be synchronized between Oracle E-Business Suite (master) and Oracle Retail applications (slave). Oracle Retail journal source and category must be set up in General Ledger. For Currency Conversion Type, only Corporate and Spot conversion types are supported out-of-box by this design. Period names and the accounting calendar must be synchronized between Oracle E-Business Suite (master) and Oracle Retail applications (slave). Only actual journals are interfaced; the design does not handle budget and encumbrance journals.
As part of setup, the following journal sources and journal categories must be created manually: Journal sources of RETEK, ReSA and retail invoices Journal categories of RETEK, ReSA, write offs, prepayments, and manual payments
Retail.FIF_GL_SETUP.PERIOD_NAME must be populated with the relevant accounting period from General Ledger Calendar. This must be maintained as a manual business process.
SendSalesJournalsToOFI BPEL Process
Oracle BPEL Product Development has provided a patch to enable batch delete and batch commit for the DB Adapter polling service. Apply this patch on the BPEL server where the general ledger inbound BPEL process is deployed, by executing the following code:
java -jar D:\bpm_ga1\integration\orabpel\system\appserver\oc4j\j2ee\home\admin.jar ormi://localhost/ admin welcome -deployconnector -file DbAdapter.rar -name DbAdapter
Run this command from the location where you have downloaded the .rar file. This needs to be done only if the Oracle BPEL Process Manager version does not include this patch.
ReIM Approved Payments to Accounts Payable

Full invoice matching processing is completed in the Oracle Retail Invoice Matching System (ReIM), with payment recommendations imported to Oracle E-Business Suite Accounts Payable. ReIM matches merchandise receipts with merchandise invoices, performing automated and manual matching and discrepancy resolution processing. Matched invoices are posted to interface staging tables that specify the amount and date to pay, vendor, Oracle Site ID, general ledger chart of accounts information, and payment terms. Other payables documents including debit memos, credit memos, and credit notes are also interfaced to Oracle Accounts Payable through the ReIM staging tables IM_AP_STAGE_HEAD and IM_AP_STAGE_DETAIL. Certain transactions from ReIM are not sent to Accounts Payable, but instead are sent to Oracle E-Business Suite General Ledger through the IM_FINANCIAL_STAGE table. The Oracle Retail financial staging table IM_FINANCIALS_STAGE, which stores the general ledger transactions from ReIM, is the primary starting point for the BPEL import process to Oracle E-Business Suite. To support the transformation and population into Accounts Payable, standard interface payables transactions are written to the Oracle Retail header and detail staging tables for the Oracle BPEL process, IM_AP_STAGE_HEAD and IM_AP_STAGE_DETAIL.
ReIM Approved Payments to Accounts Payable
The Accounts Payable open interface import, which currently accepts only the liability account code_combination_id at the invoice header level, has been enhanced to also accept the concatenated segments as input. It generates the code_combination_id accordingly, and this is stamped on the imported invoice header record in AP_INVOICES.
This design assumes all of the following: The Oracle Retail staging tables IM_FINANCIALS_STAGE, IM_AP_STAGE_HEAD, and IM_AP_STAGE_DETAIL are populated by an Oracle Retail batch process. This batch process populates the complete dataset for the period it is run, typically daily. Chart of accounts synchronization between Oracle and Oracle Retail takes place through a separate asynchronous process. The synchronization is performed as an offline business process, and it is not in the scope of this design. A designated general ledger administrator must handle manually any omissions or errors related to general ledger code combinations. General ledger cross-reference mapping is set up in ReIM by transaction type. This setup process allows dynamic mapping to different general ledger chart of accounts values by RMS location and merchandise hierarchy information. When ReIM is implemented with Oracle E-Business Suite, the Trade Accounts Payable transaction codes in ReIM are not dynamically mapped to general ledger chart of accounts values, but the Accounts Payable flex field functionality allows functionality similar to the ReIM dynamic mapping process, based on the dynamic mapping of detail lines in the interface tables. For importing invoices from ReIM to Accounts Payable interface tables, the Oracle Retail staging tables populate the segment information for the accounting flex fields for both header and detail staging tables; however, the Accounts Payable interface tables accept the concatenated segments for these flex fields. This BPEL process assumes that a hyphen ( - ) is the delimiter for the chart of accounts implementation in Oracle E-Business Suite. The GetReIMJournalsToOracle BPEL process assumes that VAT codes in Oracle Retail Invoice Matching and Oracle E-Business Suite are the same. These codes must be synchronized manually. All of the outbound processes that interface the setup data from Oracle E-Business Suite applications to Oracle Retail applications are run before the inbound transaction interface processes are run.
SendInvoicesAuthorizationsToOFI (Inbound ReIM Invoices)
ReIM Journal Entries to General Ledger

The general ledger transaction postings from Oracle Retail Invoice Matching (ReIM) are taken from the financial staging table IM_FINANCIALS_STAGE. Transactions are processed and populate the standard GL_INTERFACE table, which is the table used to import journal entry batches into Oracle E-Business Suite General Ledger through Journal Import.
Note: Patch 7330546 is required to enable the import of
transaction postings form Oracle Retail Invoice Matching to Oracle E-Business Suite general ledger. Unmatched merchandise receipts that are written off, as well as prepaid matched invoices, are written to this staging table. These transactions have an impact on the general ledger, but they do not require creation of payments or netting against other payments.
GetReIMJournalsToOracle (Inbound ReIM Journals)
The financial staging tables in Oracle Retail applications are not purged automatically. It is assumed that Oracle E-Business Suite will be responsible for the housekeeping of these tables. Batch information is not available in Oracle Retail staging tables. Batch names are automatically generated by Oracle E-Business Suite Journal Import. This generates a unique batch name for each run of Journal Import.
BPEL Process Manager Error Handling

BPEL provides a high degree of error handling capability. Through the Notification Service setup, the user can configure a system administrator e-mail address to which notifications of BPEL process errors are sent. Each BPEL process has an identifying process instance. This is forwarded to the system administrator for corrective action. From the BPEL Processes tab on the BPEL Console, the administrator can select Perform Manual Recovery for the identified process instance.
BPEL ConsoleBPEL Processes
The Instances tab shows a full list of processes. This lists the undelivered messages. The query capabilities allow query by State (delivered, not delivered, and so on) and Lifecycle (date/time ranges). After selecting a message, the user can correct it using either HTML or XML.
For HTML, the HTML prompt for the message is displayed. The user can manually enter the correct data through the field-level prompts.
HTML Message Correction
For XML, the error XML data can be manually corrected.
XML Message Correction
When the message is corrected using either method, the administrator submits the message for reprocessing.
BPEL Process Manager Processing and Scheduling

The BPEL processes are scheduled to occur at defined intervals, based on volume and business practice. The database adapter polls the source Oracle database at predetermined time intervals for new or changed records for the outbound reference data processes. The defined time interval is five minutes. After the BPEL process is initiated, it looks for create/update records in the appropriate tables/views in Oracle E-Business Suite. It selects only the records with the last_update_date greater than the last processing run, which persists in the AP_SEQUENCE_HELPER table. For example: The adapter uses a control (sequencing) table AP_SEQUENCING_HELPER to refer to the LAST_UPDATE_DATE for each process. The general ledger chart of accounts process references GL_CODE_COMBINATIONS for create/update. After selecting and raising the records to the BPEL instances, the LAST_READ_DATE in AP_SEQUENCING_HELPER is updated to the latest value processed. Selected records are processed in the BPEL flow and published to the Oracle Retail JMS for subscription by RIB. RIB is likewise configured to subscribe at predetermined intervals.
4
RMS Business Processes Configuration
RMS System Options
As part of the RMS system options setup script, set the following options as indicated: FINANCIAL_IND=Y FINANCIAL_AP = O A value of the letter O indicates that the financial system to which RMS is interfaced is Oracle E-Business Suite.
Organization Units
Use the Organizational Unit window (RMS Start Menu > Control > Setup > Org Unit > Edit) to define organizational units in RMS that match those being set up in Oracle E-Business Suite. When an organizational unit is entered in RMS, the valid operating units are those that are associated with the set of books (SOB) that is being used for the general ledger interface.
Currency Exchange Rates

Determine the Exchange Type being sent by Oracle (for example, Corporate) that you want RMS to use. Then use the Currency Exchange Type Mapping Window (RMS Start Menu> Action> Currency Exchange Types) to map that External Exchange Type being sent by Oracle E-Business Suite to the RMS Exchange Type, Consolidation (the RMS system option for Consolidation will need to be set).
Supplier Address Types

When defining valid address types in RMS, set the EXTERNAL_ADDR_IND to Y for the order and remittance address types. For all other address types, leave this value as the default N. Address types that are designated as External do not allow maintenance through the RMS Supplier dialog.
Country Codes
When country codes are defined and seeded in RMS, only 2-character codes should be used, because Oracle E-Business Suite uses 2-character country codes by default.
RMS General Ledger Setup

The RMS table FIF_GL_SETUP holds the Oracle E-Business Suite SOB ID to which it links. This requires manual setup after the SOB is determined. The FIF_GL_SETUP file holds a single SOB record.
Suppliers
Suppliers are created in Oracle E-Business Suite and exported to RMS; they cannot be created using the RMS forms. However, after the supplier exists in RMS, all data values for the supplier (except supplier name and status) continue to be updated using the RMS forms. (Functionality for partners data is not affected.)
Freight Terms, Payment Terms, Currency Exchange Rates, and General Ledger Chart of Accounts
This data is created and updated in Oracle E-Business Suite and exported to RMS; it is not created or updated in RMS. The only form in RMS that would normally allow for update of this data is the Currency Exchange Rates form, which is available in view mode only.
Oracle E-Business Suite Org Units and Site IDs

The data concepts of Org Units and Site IDs were added in RMS to mirror data maintained in Oracle E-Business Suite. RMS forms were added to manage and view Oracle Org Units and Site IDs, and the RMS windows for Store and Warehouse maintenance were changed so that each store and warehouse is assigned to an Org Unit. The following figures show these forms.
Organizational Unit Form
Navigate: Control > Setup > Org > Edit
In the Org Unit ID field, enter the ID of the Oracle E-Business Suite organizational unit. This must match the Org Unit entered in Oracle E-Business Suite. In the Org Unit Name field, enter the name of the organizational unit.
Organizational Unit Address Form
Supplier Address
An Org Unit button was added to the Supplier Address window. This allows the user to see the organization relationship with Oracle E-Business Suite suppliers.
Address Form
When the user clicks Org Unit, the Organizational Unit Address window opens and shows the organizational unit relationship to the Site ID. The financial staging table adds this to the transaction for invoices. This allows Accounts Payable to identify the operating unit when importing the data. The Organizational Unit Address window is for viewing only; no changes can be made in RMS to the organizational until assigned to a supplier. Supplier address types of Order and Remittance are created in Oracle E-Business Suite and exported to RMS; they are not created using RMS forms. After these addresses exist in RMS, the address fields (Street, City, State, and so on) are updated in Oracle EBusiness Suite and sent to RMS, but the contact information fields are maintained in RMS. The RMS import process creates any other required supplier address types by copying the order or remittance addresses received from Oracle E-Business Suite. After these exist in RMS, they are updated only in RMS. Any optional supplier address types continue to be created and updated only in RMS. Any non-supplier addresses (such as partner addresses and store addresses) continue to be created and updated only in RMS.
Store and Warehouse Maintenance

The organizational unit has also been added to the Store Maintenance and Warehouse forms. This allows the Oracle E-Business Suite operating unit to be associated with the store or warehouse. When RMS is set up for single-channel operation, the organizational unit is set at the physical warehouse level. When RMS is set up for multi-channel operation, the organizational unit is set up at the virtual warehouse level. Financial sales audit and inventory information can then be identified by Oracle E-Business Suite through the interface routines and posted to the appropriate general ledger accounts. An organizational unit must be designated for each store and warehouse location in RMS. The following figures show the Store Maintenance and Warehouse Maintenance forms.
Store Maintenance Form
Warehouse Maintenance Form
System Parameter Maintenance

Where SYSTEM_OPTIONS.FINANCIAL_AP is O, disable auto generate supplier / partner numbers and associated check boxes.
General Ledger Cross-Reference

Navigate: RMS main menu > Finance> GL Cross Reference. The General Ledger Search
window opens. Associate general ledger accounts with Department, Location. Where SYSTEM_OPTION_FINANCIAL_AP is O, disable debit and credit account IDs.
General Ledger Account Maintenance

Navigate: ReSA main menu > Action > Sales Audit > Control > Setup > GL Account
Maintenance. The General Ledger Search Form window opens. Where SYSTEM_OPTIONS.FINANCIAL_AP is O, the form requires valid CC_IDs to be entered. The user can select segments and labels from the table FIF_GL_ACCT. Turn off the debit and credit account CC_IDs.
5
Oracle Retail Invoice Matching
When integrated with Oracle E-Business Suite, Oracle Retail Invoice Matching (ReIM) exports data to accounts payable staging tables or to financial staging tables, depending on the specific type of transaction. This is done if the financial system for accounts payable and general ledger systems is Oracle E-Business Suite and the Oracle Retail Merchandising System (RMS) System Options table has the following setting: FINANCIAL_AP = O
Matched Invoices and Approved Documents

Invoices can be matched through auto-matching or online matching. Credit notes can be matched with credit note requests in online matching processes. The unit costs and quantities of all items (at a summary level) on the invoice are compared to the unit costs and quantities on the receipt. If the costs and quantities on the invoice and receipt agree within defined tolerances, there is a match.
Prepaid Invoices
Invoices can be paid before matching is complete, to meet payment terms requirements. Users determine whether to prepay an invoice. Prepaid invoices are still eligible for matching against receipts; an indicator on the invoice record prevents it from being paid twice. When a prepaid invoice is matched, the results are posted to the IM_FINANCIALS_STAGE table for interface to the general ledger, rather than to the IM_AP_STAGE_HEAD and IM_AP_STAGE_DETAIL tables for interface to accounts payable.
Non-Merchandise Invoices
Non-merchandise invoices include bills for non-merchandise costs only. Nonmerchandise invoices cannot contain items. Either suppliers or partners can create nonmerchandise invoices. Merchandise invoices, however, can contain non-merchandise lines.
Posting Transaction Codes to the Accounts Payable Staging Table

IM_AP_STAGE_HEAD Invoice Type Lookup Code: If document type = MRCHI or NMRCHI or CRDMEC or CRDMEQ, this value is set to STANDARD; otherwise this value is set to CREDIT. IM_AP_STAGE_DETAIL The rules for Line Type Lookup Code are as follows: If the tran code is UNR, VWT, REASON, or CRN, this value is ITEM. If this is a generated tax line, this value is TAX. If none of the above, this value is MISCELLANEOUS.
6
RMS Stock Ledger
The Oracle Retail Merchandising System (RMS) tracks all inventory movements within the system through its stock ledger. Daily and period-based financial information transfers can be scheduled to General Ledger. RMS allows three different levels to interface stock ledger information to General Ledger: Monthly Daily by subclass, class, or department Daily by transaction The daily summarized interface and the monthly interface do not provide any access to detailed reference information. For each interface (daily detail, daily summary, and monthly summary), specific transaction types can be included or excluded in the interface. This is determined in the general ledger cross-reference mapping. One interface, or a combination of interfaces, can be run to provide stock ledger data to General Ledger. Care must be taken to capture all necessary data, without duplicating any data. This program summarizes stock ledger data from the monthly stock ledger table (MONTH_DATA), based on the level of information required, and writes the data to the financial general ledger staging table. The transactions extracted are determined by the code_type, GLRT (general ledger rolled transactions). The data written is then sent to the financial applications for general ledger purposes. Stock ledger information can be rolled up at department, class, or subclass level. The level at which information is rolled up is determined by the gl_rollup field in the SYSTEM_OPTIONS table.
7
ReSA Sales Information
Oracle Retail Sales Audit (ReSA) allows summarized sales information to be forwarded to General Ledger for the sales journal. High-volume sales details can be aggregated by item, store and day, and transaction type. The retailer decides the aggregation level. Interfacing data directly from ReSA to General Ledger is an optional process. Sales data from ReSA is also posted directly to the RMS stock ledger, and it can be interfaced to General Ledger through the stock ledger to general ledger interface. The decision to interface directly from ReSA to General Ledger is the retailers decision. Setup steps are required to interface this data accurately to General Ledger without duplicating data.
Design Overview
The Oracle Retail SAEXPGL batch module posts all properly configured user-defined ReSA totals to General Ledger. Totals without errors are posted to the appropriate accounting ledger, as defined in the ReSA cross-reference user module. Depending on the ReSA system option Unit of Work, the data is sent at either the store/day or individual total level. Newly-revised totals that are already posted to the ledger have their previous revision reversed, and the new totals are posted to the appropriate accounts. Transactions from previous periods are posted to the current period.
8
Business Intelligence
Oracle Daily Business Intelligence is a prebuilt decision support system for Oracle applications. The solution has been extended to include integrated data sourced directly from Oracle Retail, with extension for customers to view Daily Business Intelligence for accounts payable, sales, and expenses. For Oracle Retail, the Business Intelligence application requires the configuration described in this chapter.
Select Business Intelligence Designer Responsibility

1. 2. 3.
Navigate to the Reporting menu and select Overview Pages. Select Financials in the Functional Area drop-down list. Navigate to the Payables Management Page and click Duplicate.
Modify the Duplicate Payables Management Page

4.
Modify the KPI list:

a. b. c. d. e.
Remove the original KPI list. Click New in the KPI content area to add a new region and move it to the left. In the newly added KPI list region, click Select. Select Customer Defined Functional Area and Type= KPI List. Click Create to create the new KPI list. Title = Payables Management KPIs Comparison Graph = None Show Change Column = Yes Value Column Heading = YTD/QTD/MTD Invoices Entered Invoices Paid Paid Late (measure = Percent Invoices Paid Late) Invoice to Payment Days Payments
f.
Add 5 new KPI Measures.
g. h. 5.
Click Implementation Properties to select the corresponding measures (same names as KPIs). Click Apply to save changes. For each KPI, remove the Drilldown URL. Electronic and Paid Late Invoices (graph in the KPI region group) Invoices Graph (in the Invoices Region group) Discounts region group Holds region group
Remove irrelevant content by clicking the trash can icon:
6.
Add new content by clicking New in the appropriate region group. Use arrows to move the new region to the appropriate position within the region group.
a.
In the KPI region group, add the Paid Late Invoices graph to the right of the KPIs list : Click Select within the newly added region. Select Financials in the Functional Area and Graph Type Navigate to the Paid Late Invoices graph and select it. Click Select within the newly added region. Select Financials in the Functional Area and Graph Type. Navigate to the Invoice Activity graph and select it.
b.
In the Invoices region group, add the Invoices graph:
7.
Add links to the Microstrategy reports: Primary Supplier Performance Scorecard Supplier Compliance Comparison TY vs. LY Returns to Supplier Detail Primary Supplier Sales and Profit Analysis Top Performers Delivery Accuracy Supplier Invoice Cost Follow these steps:
a. b. c. d.
Click Select in the Links page region on the Payables Management page. Under Custom Defined functional area, Type=Links. Click Create to create a new Links region. Enter Name = Links and a Description for the region. In a separate browser, navigate to the appropriate Microstrategy reports, copy the URL for each one, and add the URLs to the newly-defined Links region.
Note: Make sure to add all the necessary links at once,
because it is not possible to save a partial list and return to it later.

8. 9.
Click Apply to save changes. Navigate to the Payables Status Page. Click the Duplicate icon.
Modify the Duplicate Payables Status Page

1.
Modify the KPI list by defining a new one:

a. b. c. d. e.
Remove the original KPI list. Click New in the KPI content area to add a new region and move it to the left. In the newly-added KPI list region, click Select. Select Customer Defined functional Area and Type= KPI List. Click Create to create the new KPI list. Title = Payables Status KPIs Comparison Graph = None Show Change Column = No Value Column Heading = YTD/QTD/MTD
48 Oracle Retail / Oracle E-Business Suite
f.
Add these new KPI measures: Open Payables Amount Invoices Due Amount Number of Invoices Due Weighted Average Days Due Invoices Past Due Amount Number of Invoices Past Due Weighted Average Days Past Due
g. h. 2.
Click Implementation Properties to select the corresponding measure (same names as KPIs). Click Apply to save changes. For each KPI, remove the Drilldown URL. Discounts region group Holds region group
Remove irrelevant content by clicking the trash can icon:
3.
Click Apply to save changes.
Switch to Business Intelligence Administrator Responsibilities

1. 2. 3.
Navigate to the Setup: Global -> Overview Pages. Select Customer Defined in the Functional Area. Click Enable for the newly defined pages.
Switch System Administrator Responsibility

1. 2. 3. 4.
Update the description of the newly-created pages. Navigate to Application: Function. Search for User Function Name = Payables Management and Payables Status, and function name starting with PMD_. In the Description field: For the Payables Management page, enter Page that displays payables management details, such as invoices entered and payments by organization. For the Payables Status page, enter Page that displays payables status details, such as invoices entered and payments by supplier.
5.
Define a new menu structure similar to the pre-seeded structure for the Payables Intelligence Responsibility, but inclusive of all the changes. The following are sample steps, but these steps do not include everything that needs to be done:
a.
Define a new Intelligence Overview submenu, similar to the pre-seeded submenu but with new pages. The prompts and corresponding function names are as follows: Payables Management Payables Management (newly defined PM page) Payables Status - Payables Status (newly defined PS page)
b. c. d.
Define a new Invoices At Risk Reports submenu, similar to the pre-seeded menu but without holds-related reports. Define a new top-level menu to be associated with the Payables Intelligence or other appropriate responsibility. Include a newly-defined Intelligence Overview submenu.
e. f. g. h.
Include the pre-seeded Invoices and Payments reports submenu. Include a newly-defined Invoices At Risk Reports submenu. Define a new Payables Management KPIs submenu. Define a new Payables Management KPI Content Area submenu that contains the following: Newly defined Payables Management KPIs list menu Paid Late Invoices function Links
i.
Define a new Payables Management KPI list menu that includes functions corresponding to individual KPIs.
9
Middleware Configuration
This section describes the changes required to middleware files following installation. It provides the required steps for post-installation configuration for the Oracle BPEL Process Manager. See the following documents for more information about the standard configuration of the middleware components: Oracle BPEL Process Manager Administrator's Guide 10g Release 3 (10.1.3). See also Metalink Note 741499.1. Oracle BPEL Process Managers Development Guide 10g Release 3 (10.1.3). See also Metalink Note 741499.1.
Note: The examples shown in this chapter include values
for demonstration purposes. Actual values may need to be entered manually to override a default value. Examples of such values include DB Host Name and Connection Pool.
Database Adapter Configuration

Follow these steps to configure BPEL database adapters.
1.
Open the Enterprise Manager Console. The Cluster Topology window opens.
2. 3.
Click on the OC4J instance that you want to set up. Click on the Administration tab.
4.
Under Services, click the Go to Task icon for JDBC Resources. The JDBC Resources window opens.
5.
Under Connection Pools, click Create. The Create Connection Pool - Application window opens.
6. 7. 8.
Select your application from the Application drop-down list. Under Connection Pool Type, select the radio button for New Connection Pool. Click Continue. The Create Connection Pool window opens.
Note: Repeat these steps as necessary to create the
connection pools as described in this chapter.
Configure the Oracle E-Business Suite Connection Pool

1.
Enter Oracle E-Business Suite connection pool details as follows: Name: Oracle EBS Connection Pool Connection Factory Class: oracle.jdbc.pool.OracleDataSource (do not change the default) URL: Do one of the following: Enter the JDBC URL of your Oracle E-Business Suite database. Select the radio button for Generate URL from Connection Information.
2.
Enter your Oracle E-Business Suite database details as follows:

Value Thin Your Oracle E-Business Suite database host name Your Oracle E-Business Suite database listener Port Your Oracle E-Business Suite database Identifier Type: SID/Service Name Your SID/Service Name TNS alias, if applicable (you can leave this blank)
Name Driver Type: DB Host Name: DB Listener Port: DB Identifier Type: SID/Service Name: TNS Alias: 3. 4.
Under Credentials, enter the Username and Password. Check the connection details by clicking Test Connections > Test.
The following figure shows an example of the completed form:
5.
Click Finish. You should now be able to see the connection pool you created.
Configure the Oracle Retail Connection Pool

1.
Enter Oracle Retail connection pool details as follows: Name: Oracle Retail Connection Pool Connection Factory Class: oracle.jdbc.pool.OracleDataSource (do not change the default) URL: Do one of the following: Enter the JDBC URL of your Oracle Retail database. Select the radio button for Generate URL from Connection Information.
2.
Enter your Oracle Retail database details as follows:

Value Thin Your Oracle Retail database host name Your Oracle Retail database listener port Your Oracle Retail database Identifier Type: SID/Service Name Your SID/Service Name TNS alias, if applicable (you can leave this blank)
Name Driver Type DB Host Name DB Listener Port DB Identifier Type SID/Service Name TNS Alias 3. 4. 5.
Under Credentials, enter your Oracle Retail Username and Password. Check the connection details by clicking Test Connections > Test. Click Finish. You should now be able to see the connection pool you created
Configure the Oracle E-Business Suite Data Source

1. 2. 3. 4. 5.
Under Data Sources in the JDBC Resources window, click Create. Select your application from the Application drop-down list. Select the data source type as Managed Data Source. Click Continue. Enter data source details as follows:
Value Oracle EBS Data Source loc/EBSDatabase Local Transactions Only Oracle EBS Connection Pool 0
Name Name JNDI Location Transaction Level Connection Pool Login Timeout (seconds) 6.
Click Finish. The following figure shows an example of the completed form:
Configure the Oracle Retail Data Source

1. 2. 3. 4. 5.
Under Data Sources in the JDBC Resources window, click Create. Select your application from the Application drop-down list. Select the data source type as Managed Data Source. Click Continue. Enter data source details as follows:
Value Oracle Retail Data Source loc/RetekDatabase Local Transactions Only RetailConnection 0
Name Name JNDI Location Transaction Level Connection Pool Login Timeout (seconds) 6.
Configure the Oracle E-Business Suite Connection Factory

1. 2. 3.
Click on Cluster Topology and navigate back to the OC4J instance (see steps 1 and 2). Navigate to the Applications tab. Click default. The Application: default window opens.
4. 5.
Click on DbAdapter. Click the Connection Factories tab.
6. 7.
Click Create. Leave the Connection Factory Interface set to the default value. Click Continue.
8.
Enter Connection Factory details as follows: JNDI Location: eis/DB/OracleConnection Configuration properties:
Name dataSourceName defaultNChar platformClassName sequencePreallocationSize usesBatchWriting usesNativeSequencing xADataSourceName
Value loc/EBSDatabase false oracle.toplink.platform.database.oracle.Oracle10Platform 50 true true (leave null)
9.
Click Finish.
Configure the Oracle Retail Connection Factory

1. 2.
Click Create. Enter Connection Factory details: JNDI Location: eis/DB/OracleRetailConnection Configuration properties:
Name dataSourceName defaultNChar platformClassName sequencePreallocationSize usesBatchWriting usesNativeSequencing xADataSourceName 3.
Value loc/RetekDatabase false oracle.toplink.platform.database.Oracle9Platform 50 true true (leave null)
Notification Services
The BPEL error handling in this integration supports e-mail notification to the system administrator for any BPEL processing errors. Each process has a Catchall block to trap errors and sends an e-mail to the predefined system administrator. The e-mail provides an error message and process instance ID in error. The system administrator can use the instance ID to query the process from the BPEL console and take required action. The system administrator e-mail address is specified as the descriptor preference property SYSADMIN_EMAIL. The value of this property can be changed at run time from the BPEL Console without redeploying or bringing down the BPEL Server. Setup for the e-mail notification is documented in the Oracle BPEL Process Manager Developers Guide 10g, Release 3 (10.1.3.1.0), part number B28981-03, in Section 14, Oracle BPEL Process Manager Notification Service.
JMS Adapter Configuration for RIB

This section describes how to configure the BPEL Process Manager to communicate with the Oracle Retail Integration Bus (RIB) infrastructure.
Create and Configure Connection Factories

You must create and configure the following Connection Factories: eis/Jms/SendCodeCombinations eis/Jms/SendCurrencyRates eis/Jms/SendFreightTerms eis/Jms/SendPaymentTerms eis/Jms/SendVendors To create each new Connection Factory, follow these steps:
1. 2. 3. 4. 5. 6. 7.
Open the Enterprise Manager Console. The Cluster Topology window opens. Click on the OC4J instance that you want to set up. Click the Applications tab. Click on the default application. Under Modules, select the JmsAdapter. Go to Connection Factories. Click Create. The following screen displays:
Create and configure each of the Connection Factories as described in the following topics.
eis/Jms/SendCodeCombinations
To create this Connection Factory, do the following:
1. 2. 3. 4. 5.
Leave the Connection Factory Interface set to the default value. Click Continue. Enter JNDI Location: eis/Jms/SendCodeCombinations Set Connection Pooling: No Connection Pool. Set other values as follows:
Value AUTO_ACKNOWLEDGE jms/QueueConnectionFactory
Name acknowledgeMode connectionFactoryLocation factoryProperties isTopic isTransacted password username
true true As per your RIB settings As per your RIB settings
Configure JMS Connection Factory Settings (application.xml and oc4jra.xml files) for RIB Server
The JMS connection factories must be set up in the application.xmla and oc4j-ra.xml.
Name Resource Provider Classname Server name Username Password Value Resource Provider Name Resource Provider URL User name password
$ORACLE_HOME/j2ee/home/config/application.xml
<resource-provider class="oracle.jms.OjmsContext" name="<Resource Provider Name>"> <description>RIB AQ</description> <property name="url" value="jdbc:oracle:thin:@ <Resource Provider URL>" /> <property name="username" value="<username>" /> <property name="password" value="<password>" /> </resource-provider>
$ORACLE_HOME /j2ee/home/application-deployments/default/JmsAdapter/oc4jra.xml
<connector-factory location="<Connection Factory Name>" connector-name="Jms Adapter"> <config-property name="connectionFactoryLocation" value="java:comp/resource/<Resource Provider Name>/TopicConnectionFactories/myTCF"/> <config-property name="factoryProperties" value=""/> <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/> <config-property name="isTopic" value="true"/> <config-property name="isTransacted" value="true"/> <config-property name="username" value="<username>"/> <config-property name="password" value="<password>"/> <connection-pooling use="private">
<property name="waitTimeout" value="300" /> <property name="scheme" value="fixed_wait" /> <property name="maxConnections" value="20" /> <property name="inactivity-timeout-check" value="all" /> <property name="minConnections" value="0" /> <property name="initial-capacity" value="0" /> <property name="inactivity-timeout" value="60" /> </connection-pooling>
Create a separate Connection Factory as required for each process. Replace the connection factory name (location), value, user name, and password as appropriate.
A
Appendix: General Ledger Chart of Accounts Mapping
The following table describes the mapping of chart of accounts data mapping from the Oracle E-Business Suite General Ledger Chart of Accounts to Oracle Retail Management System (RMS).
Field Passed from Oracle E-Business Suite code-combination-id segment1 segment2 segment3 segment4 segment5 segment6 segment7 segment8 segment9 segment10 segment11 segment12 segment13 segment14 segment15 Segment_attribute 1 Segment_attribute 2 Segment_attribute 3 Segment_attribute 4 Segment_attribute 5 Segment_attribute 6 Segment_attribute 7 Segment_attribute 8 Segment_attribute 9 Oracle Retail RIB GLCOADesc PRIMARY_ ACCOUNT ATTRIBUTE1 ATTRIBUTE2 ATTRIBUTE3 ATTRIBUTE4 ATTRIBUTE5 ATTRIBUTE6 ATTRIBUTE7 ATTRIBUTE8 ATTRIBUTE9 ATTRIBUTE10 ATTRIBUTE11 ATTRIBUTE12 ATTRIBUTE13 ATTRIBUTE14 ATTRIBUTE15 DESCRIPTION1 DESCRIPTION2 DESCRIPTION3 DESCRIPTION4 DESCRIPTION5 DESCRIPTION6 DESCRIPTION7 DESCRIPTION8 DESCRIPTION9 API Create API Update Oracle Retail Database FIF_GL_ACCT PRIMARY_ACCOUNT ATTRIBUTE1 ATTRIBUTE2 ATTRIBUTE3 ATTRIBUTE4 ATTRIBUTE5 ATTRIBUTE6 ATTRIBUTE7 ATTRIBUTE8 ATTRIBUTE9 ATTRIBUTE10 ATTRIBUTE11 ATTRIBUTE12 ATTRIBUTE13 ATTRIBUTE14 ATTRIBUTE15 DESCRIPTION1 DESCRIPTION2 DESCRIPTION3 DESCRIPTION4 DESCRIPTION5 DESCRIPTION6 DESCRIPTION7 DESCRIPTION8 DESCRIPTION9
(Key) Pass Pass Pass Pass Pass Pass Pass Pass Pass Pass Default Default Default Default Default Default Default Default Default Default Default Default Default Default
(Key) Pass Pass Pass Pass Pass Pass Pass Pass Pass Pass Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore
Appendix: General Ledger Chart of Accounts Mapping
Field Passed from Oracle E-Business Suite Segment_attribute 10 Segment_attribute 11 Segment_attribute 12 Segment_attribute 13 Segment_attribute 14 Segment_attribute 15 Chart_of_accounts_ID
Oracle Retail RIB GLCOADesc DESCRIPTION10 DESCRIPTION11 DESCRIPTION12 DESCRIPTION13 DESCRIPTION14 DESCRIPTION15 SET_OF_BOOKS_ID
API Create
API Update
Oracle Retail Database FIF_GL_ACCT DESCRIPTION10 DESCRIPTION11 DESCRIPTION12 DESCRIPTION13 DESCRIPTION14 DESCRIPTION15 SET_OF_BOOKS_ID
Default Default Default Default Default Default (Key)
Ignore Ignore Ignore Ignore Ignore Ignore (Key)
B
Appendix: Supplier Mapping
The following table describes the mapping of supplier data from Oracle E-Business Suite Accounts Payable to Oracle Retail Management System (RMS).
Field Passed from Oracle E-Business Suite ap_suppliers. segment1 ap_suppliers. vendor_name ap_supplier_ sites_all. vendor_site_ code NULL SUP_NAME_ SECONDARY SUPPLIER_ PARENT Oracle Retail API RIB Create VendorHdrDesc API Update Oracle Retail Database - SUPS Window Edit (supvwedt) Comments
SUPPLIER SUP_NAME
(Key) Pass
(Key) Pass
SUPPLIER SUP_NAME
(Key) Disable
NULL for Supplier. Mandatory for Supplier Site (ap_suppliers. segment1) (One occurrence) po_vendor_co ntacts.first_ name po_vendor_co ntacts.last_ name CONTACT_ NAME Pass Ignore
CONTACT_ NAME
Normal
Oracle E-Business Suite stores this data at either the supplier or supplier site level. One occurrence is sent, which is used in Oracle Retail for create only. After that, any updates are done by the user through the Oracle Retail window. See note for CONTACT_NAME.
(One occurrence) po_vendor_co ntacts.area_ code po_vendor_co ntacts.phone
CONTACT_ PHONE
Pass
Ignore
CONTACT_ PHONE
Normal
Field Passed from Oracle E-Business Suite (One occurrence) po_vendor_co ntacts.fax_ area_code po_vendor_co ntacts.fax NULL (Derived) ap_suppliers
Oracle Retail API RIB Create VendorHdrDesc
API Update
Oracle Retail Database - SUPS
Window Edit (supvwedt)
Comments
CONTACT_FAX
Pass
Ignore
CONTACT_FAX
Normal
See note for CONTACT_NAME.
CONTACT_ PAGER SUP_STATUS
Default (See note)
Ignore (See note)
CONTACT_ PAGER SUP_STATUS
Normal (See note) For API: see information in the functional specification. For window: Disable this field unless the client uses VAT and current status is inactive. In that case, if the user tries to change the status to active, invoke the standard edit that the VAT region must be valued to change status to active.
Default: N
QC_IND
Default Default Default Default Default Default Pass
Ignore Ignore Ignore ignore Ignore Ignore Ignore
QC_IND QC_PCT QC_FREQ VC_IND VC_PCT VC_FREQ CURRENCY_ CODE
Normal Normal Normal Normal Normal Normal Normal See note for CONTACT_NAME.
Default: NULL QC_PCT Default: NULL QC_FREQ Default: N Default: N VC_IND VC_PCT VC_FREQ (One occurrence) ap_supplier_ sites_all. invoice_ currency.code (One occurrence) ap_supplier_ sites_all. language LANG CURRENCY_ CODE
Pass
Ignore
LANG
Normal
Field Passed from Oracle E-Business Suite (One occurrence) ap_supplier_ sites_all.terms_ id (One occurrence) ap_supplier_ sites_all.freight _terms_lookup _code Default: N Default: N ------Default: N Default: N Default: N Default: N --Default: Y
API Update
Comments
TERMS
Pass
Ignore
TERMS
Normal
FREIGHT_ TERMS
Pass
Ignore
FREIGHT_ TERMS
Normal
RET_ALLOW_ IND RET_AUTH_ REQ
Default Default
Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore
RET_ALLOW_ IND RET_AUTH_ REQ RET_MIN_DOL_ AMT RET_COURIER HANDLING_ PCT EDI_PO_IND EDI_PO_CHG EDI_PO_ CONFIRM EDI_ASN EDI_SALES_ RPT_FREQ EDI_SUPP_ AVAILABLE_IND EDI_ CONTRACT_ IND EDI_INVC_IND EDI_ CHANNEL_ID COST_CHG_ PCT_VAR COST_CHG_ AMT_VAR
Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal
RET_MIN_DOL_ Default AMT RET_COURIER HANDLING_ PCT EDI_PO_IND EDI_PO_CHG EDI_PO_ CONFIRM EDI_ASN EDI_SALES_ RPT_FREQ EDI_SUPP_ AVAILABLE_ IND EDI_ CONTRACT_ IND EDI_INVC_IND Default Default Default Default Default Default Default Default
Default: N
Default
Ignore
Normal
Default: N -------
Default Default
Ignore N/A Ignore Ignore
Normal Normal Normal Normal
COST_CHG_ PCT_VAR COST_CHG_ AMT_VAR
Default Default
Field Passed from Oracle E-Business Suite Default: N
API Update
Comments
REPLEN_ APPROVAL_ IND SHIP_METHOD PAYMENT_ METHOD CONTACT_ TELEX CONTACT_ EMAIL SETTLEMENT_ CODE PRE_MARK_ IND AUTO_APPR_ INVC_IND DBT_MEMO_ CODE FREIGHT_ CHARGE_IND AUTO_APPR_ DBT_MEMO_ IND PREPAY_INVC_ IND BACKORDER_ IND VAT_REGION
Default
Ignore
REPLEN_ APPROVAL_ IND SHIP_METHOD PAYMENT_ METHOD CONTACT_ TELEX CONTACT_ EMAIL SETTLEMENT_ CODE PRE_MARK_ IND AUTO_APPR_ INVC_IND DBT_MEMO_ CODE FREIGHT_ CHARGE_IND AUTO_APPR_ DBT_MEMO_ IND PREPAY_INVC_ IND BACKORDER_ IND VAT_REGION
Normal
------po_vendor_co ntacts.email_a ddress Default: N Default: N Default: N Default: A Default: Y Default: N
Default Default Default Pass
Ignore Ignore Ignore Ignore
Normal Normal Normal Normal See note for CONTACT_NAME.
Default Default Default Default Default Default
Ignore Ignore Ignore Ignore Ignore Ignore
Normal Normal Normal Normal Normal Normal
Default: N Default: N Default: 1000 (See note)
Default Default (See note)
Ignore Ignore Ignore
Normal Normal Normal For API: see information in the functional specification.
--Default: N -----
INV_MGMT_ LVL
Default
INV_MGMT_ LVL SERVICE_PERF_ REQ_IND INVC_PAY_ LOC INVC_ RECEIVE_LOC
SERVICE_PERF_ Default REQ_IND INVC_PAY_ LOC INVC_ RECEIVE_LOC Default Default
Field Passed from Oracle E-Business Suite --Default: NDD -----
API Update
Comments
ADDINVC_ GROSS_NET DELIVERY_ POLICY COMMENT_ DESC DEFAULT_ ITEM_LEAD_ TIME DUNS_ NUMBER DUNS_LOC BRACKET_ COSTING_IND VMI_ORDER_ STATUS DSD_ SUPPLIER_IND END_DATE_ ACTIVE
Default Default Default Default
ADDINVC_ GROSS_NET DELIVERY_ POLICY COMMENT_ DESC DEFAULT_ ITEM_LEAD_ TIME DUNS_ NUMBER DUNS_LOC BRACKET_ COSTING_IND VMI_ORDER_ STATUS DSD_IND N/A SCALE_AIP_ORD ERS
----Default: N --Default: Y ---
Default Default Default Default Default Ignore
Ignore Ignore Ignore Ignore Ignore Ignore
Normal Normal Normal Normal Normal N/A
C
Appendix: Supplier Address Mapping
The following table describes the mapping of address and site ID data from Oracle E-Business Suite Accounts Payable to Oracle Retail Management System (RMS).
Note: Records in Oracle E-Business Suite are sent to Oracle
Retail applications when the following fields are populated in Oracle E-Business Suite: address_line1, city, and zip.
Field Passed from Oracle E-Business Suite ap_supplier_sites _all.vendor_site_ id (literal) MODULE Oracle Retail RIB VendorAddrDesc API Create API Update Oracle Retail Database ADDR Window Edit (addr) Comments
(Key)
(Key)
ADDR_KEY
N/A
(Key)
(Key)
MODULE
N/A
This should always be the literal SUPP. This is the supplier number.
ap_supplier. segment1 Null Default: 1 (Derived) ap_supplier_sites _all.purchasing_ site_flag ap_supplier_sites _all.pay_site_flag Default: N
KEY_VALUE_1
(Key)
(Key)
KEY_VALUE_1 N/A
KEY_VALUE_2 SEQ_NO ADDR_TYPE
Default Generate (See note)
Ignore Ignore (See note)
KEY_VALUE_2 N/A SEQ_NO ADDR_TYPE N/A N/A
PRIMARY_ ADDR_IND
Generate Pass
Generate Pass
PRIMARY_ ADDR_IND ADD_1
Normal Disable
Logic in API determines.
ap_supplier_sites ADD_1 _all.address_line 1 ap_supplier_sites ADD_2 _all.address_line 2 ap_supplier_sites ADD_3 _all.address_line 3 ap_supplier_sites CITY _all.city
Pass
Pass
ADD_2
Disable
Pass
Pass
ADD_3
Disable
Pass
Pass
CITY
Disable
Appendix: Supplier Address Mapping
Field Passed from Oracle E-Business Suite
Oracle Retail RIB VendorAddrDesc
API Create
API Update
Oracle Retail Database ADDR
Window Edit (addr)
Comments
ap_supplier_sites STATE _all.state ap_supplier_sites COUNTRY_ID _all.country ap_supplier_sites POST _all.zip (One occurrence) CONTACT_ po_vendor_conta NAME cts.first_name po_vendor_conta cts..last_name (One occurrence) CONTACT_ po_vendor_conta PHONE cts.area_code po_vendor_conta cts.phone Null CONTACT_ TELEX
Pass Pass Pass Pass
Pass Pass Pass Ignore
STATE COUNTRY_ID POST CONTACT_ NAME
Disable Disable Disable Normal Oracle EBusiness Suite passes the first contact name for each address created. Oracle EBusiness Suite passes the first contact name for each address created.
Pass
Ignore
CONTACT_ PHONE
Normal
Default Pass
Ignore Ignore
CONTACT_ TELEX CONTACT_ FAX
Normal Normal Oracle EBusiness Suite passes the first contact name for each address created. Oracle EBusiness Suite passes the first contact name for each address created.
(One occurrence) CONTACT_FAX po_vendor_conta cts.fax_area_code po_vendor_conta cts.fax (One occurrence) CONTACT_ po_vendor_conta EMAIL cts.email_ address
Pass
Ignore
CONTACT_ EMAIL
Normal
N/A N/A N/A
N/A N/A N/A
Default Default Default
N/A N/A N/A
EDI_ADDR_ CHG COUNTY PUBLISH_IND
N/A N/A N/A
Multiple occurrences of information at lower level: ORG_ID ORACLE_ORG_ UNIT_ID Pass Pass ORACLE_ ORG_ UNIT_ID N/A
D
Appendix: Currency Rates Mapping
The following table describes the mapping of currency rates data from Oracle E-Business Suite to Oracle Retail Management System (RMS).
Field Passed Oracle Retail from Oracle RIB E-Business CurrRateDesc Suite API Create API Update Oracle Retail Window Database Edit Currency Rates Currency Exchange Rates CURRENCY_ CODE EFFECTIVE_ DATE EXCHANGE_ TYPE Allow view only Allow view only Allow view only Read the FIFCURRENCYXREF table to translate incoming value to rms-exchangetype. Comments
fromcurrency conversiondate conversiontype
FROM_ CURRENCY CONVERSION_ DATE USER_ CONVERSION_ TYPE
(Key)
(Key)
(Key)
(Key)
Translate and use for key
Translate and use for key
conversionrate to-currency
CONVERSION_ RATE TO_CURRENCY
Pass
Pass
EXCHANGE_ RATE N/A
Allow view only N/A Check this value against the currency-code field in the system-options table. If they do not match, ignore this record.
Use for filter
Use for filter
E
Appendix: Freight Terms Mapping
The following table describes mapping of freight terms data from Oracle E-Business Suite to Oracle Retail Management System (RMS).
Field Passed from Oracle E-Business Suite lookup-code meaning start_date_active end_date_active enabled-flag Oracle Retail RIB FrtTermDesc API Create API Update Oracle Retail Database FREIGHT_TERMS
FREIGHT_TERMS TERM_DESC START_DATE_ACTIVE END_DATE_ACTIVE ENABLED_FLAG
(Key) Pass Pass Pass Pass
(Key) Pass Pass Pass Pass
FREIGHT_TERMS TERM_DESC START_DATE_ACTIVE END_DATE_ACTIVE ENABLED_FLAG
F
Appendix: Payment Terms Mapping
The following table describes mapping of payment terms data from Oracle E-Business Suite to Oracle Retail Management System (RMS).
Note: In the table, an asterisk (* ) indicates that this field is
maintained at header level in Oracle E-Business Suite.

Field Passed from Oracle E-Business Suite AP_TERMS_TL(AT) AP_TERMS_LINES (ATL) Oracle Retail Database TERMS_HEAD AT.Term_Id AT.Name AT.Description AT.Rank Default NULL Derived (AT) TERMS TERMS_CODE TERMS_DESC RANK DUE_DAYS ENABLED_ FLAG AT.Start_Date_Active AT.End_Date_Active Default NULL Default NULL START_DATE_ ACTIVE END_DATE_ ACTIVE DISCDAYS DISCDAYS (Key) Pass Pass Pass (Key) Pass Pass pass TERMS TERMS_CODE TERMS_DESC RANK Oracle Retail RIB PayTermDesc Oracle Retail RIB PayTermDtl API Create API Update Oracle Retail Database TERMS_HEADER
Oracle Retail Database TERMS_DETAIL AT.Term-id ATL.sequence-num ATL.due-days ATL.due-amount due-day-of-month TERMS TERMS_SEQ DUE_DAYS DUE_MAX_ AMOUNT DUE_DOM (Key) (Key) Pass Pass Pass (Key) (Key) Pass Pass Pass TERMS TERMS_SEQ DUEDAYS DUE_MAX_ AMOUNT DUE_DOM
Appendix: Payment Terms Mapping
Field Passed from Oracle E-Business Suite AP_TERMS_TL(AT) AP_TERMS_LINES (ATL) ATL.due-monthsforward ATL.discount-days ATL.discount-percent ATL.discount-day-ofmonth ATL.discountmonths-forward ATL.fixed-date Derived (ATL) ATL.start-date-active* ATL.end-date-active* ATL.due-cutoff-day*
Oracle Retail RIB PayTermDesc
Oracle Retail RIB PayTermDtl
API Create
API Update
Oracle Retail Database TERMS_HEADER
DUE_MM_FWD DISCDAYS PERCENT DISC_DOM DISC_MM_FWD FIXED_DATE
Pass Pass Pass Pass Pass Pass
Pass Pass Pass Pass Pass Pass Pass Pass Pass Pass
DUE_MM_FWD DISCDAYS PERCENT DISC_DOM DISC_MM_FWD FIXED_DATE ENABLED_FLAG START_DATE_ ACTIVE END_DATE_ACTIVE CUTOFF_DAY
ENABLED_FLAG Pass START_DATE_ ACTIVE END_DATE_ ACTIVE CUTOFF_DAY Pass Pass Pass
G
Appendix: Stock Ledger, Sales Journal, Miscellaneous Payments
The following table describes the mapping of Oracle Retail stock ledger, sales journal, and miscellaneous payments data to Oracle E-Business Suite.
Column Name STATUS Data Type VARCHAR2(50) Column Name STATUS SET_OF_BOOKS_ ID ACCOUNTING_ DATE CURRENCY_ CODE Data Type VARCHAR2(50) NUMBER(15) DATE VARCHAR2(15) Reqd Yes Yes Yes Yes Remarks Straight mapping. Straight mapping. Oracle Retail sends a valid value. Straight mapping. Straight mapping. Oracle Retail synchronizes reference data with Oracle E-Business Suite. Straight mapping.
SET_OF_BOOKS_ NUMBER(15) ID ACCOUNTING_ DATE CURRENCY_ CODE DATE VARCHAR2(15)
DATE_CREATED DATE CREATED_BY ACTUAL_FLAG USER_JE_ CATEGORY_ NAME USER_JE_ SOURCE_NAME CURRENCY_ CONVERSION_ DATE CURRENCY_ CONVERSION_ TYPE NUMBER(15) VARCHAR2(1) VARCHAR2(25)
DATE_ CREATED CREATED_BY ACTUAL_FLAG USER_JE_ CATEGORY_ NAME USER_JE_ SOURCE_NAME CURRENCY_ CONVERSION_ DATE USER_ CURRENCY_ CONVERSION_ TYPE CURRENCY_ CONVERSION_ RATE
DATE NUMBER(15) VARCHAR2(1) VARCHAR2(25)
Yes Yes Yes Yes
Straight mapping. Straight mapping. Oracle Retail sends a valid value. Straight mapping. Oracle Retail sends a valid value. Straight mapping.
VARCHAR2(25) DATE
VARCHAR2(25) DATE
Yes
VARCHAR2(30)
VARCHAR2(30)
The only valid values are Corporate and Spot.
NUMBER
Not sent by Oracle Retail. Conversion rate is derived from the GL_DAILY_RATES table based on conversion date, conversion type, currency_code, and functional currency. Not sent by Oracle Retail because the code_combination_id is sent.
ACCT_ SEGMENT1
VARCHAR2(25)
SEGMENT1
VARCHAR2(25)
Column Name ACCT_ SEGMENT2
Data Type VARCHAR2(25)
Column Name SEGMENT2
Data Type VARCHAR2(25)
Reqd
Remarks Not sent by Oracle Retail because the code_combination_id is sent. Not sent by Oracle Retail because the code_combination_id is sent. Not sent by Oracle Retail because the code_combination_id is sent. Not sent by Oracle Retail because the code_combination_id is sent. Not sent by Oracle Retail because the code_combination_id is sent. Not sent by Oracle Retail because the code_combination_id is sent. Not sent by Oracle Retail because the code_combination_id is sent. Not sent by Oracle Retail because the code_combination_id is sent. Not sent by Oracle Retail because the code_combination_id is sent. Straight mapping and truncation per Oracle Retail column sizing constraints. Straight mapping and truncation per Oracle Retail column sizing constraints. Not sent. This is derived during GL import from the GL Daily Rates table.
ACCT_ SEGMENT3
VARCHAR2(25)
SEGMENT3
VARCHAR2(25)
ACCT_ SEGMENT4
VARCHAR2(25)
SEGMENT4
VARCHAR2(25)
ACCT_ SEGMENT5
VARCHAR2(25)
SEGMENT5
VARCHAR2(25)
ACCT_ SEGMENT6
VARCHAR2(25)
SEGMENT6
VARCHAR2(25)
ACCT_ SEGMENT7
VARCHAR2(25)
SEGMENT7
VARCHAR2(25)
ACCT_ SEGMENT8
VARCHAR2(25)
SEGMENT8
VARCHAR2(25)
ACCT_ SEGMENT9
VARCHAR2(25)
SEGMENT9
VARCHAR2(25)
ACCT_ SEGMENT10
VARCHAR2(25)
SEGMENT10
VARCHAR2(25)
ENTERED_DR_ AMOUNT
NUMBER(20,4)
ENTERED_DR
NUMBER
ENTERED_CR_ AMOUNT
NUMBER(20,4)
ENTERED_CR
NUMBER
ACCOUNTED_ DR
NUMBER
Column Name
Data Type
Column Name ACCOUNTED_ CR
Data Type NUMBER
Reqd
Remarks Not sent. This is derived during GL import from the GL Daily Rates table. Straight mapping. Straight mapping. Straight mapping. Straight mapping. Straight mapping. Straight mapping. Do not map. Straight mapping. The period names are manually synchronized. Leave null. For internal use only. Do not map. Do not map. Do not map.
TRANSACTION_ DATE DATE REFERENCE1 REFERENCE2 REFERENCE3 REFERENCE4 REFERENCE5 VARCHAR2(20) VARCHAR2(20) VARCHAR2(20) VARCHAR2(20) VARCHAR2(20)
TRANSACTION_ DATE REFERENCE21 REFERENCE22 REFERENCE23 REFERENCE24 REFERENCE25 JE_BATCH_ID
DATE VARCHAR2(100) VARCHAR2(240) VARCHAR2(100) VARCHAR2(100) VARCHAR2(240) NUMBER(15) VARCHAR2(15)
PERIOD_NAME
VARCHAR2(15
PERIOD_NAME
JE_HEADER_ID JE_LINE_NUM CHART_OF_ ACCOUNTS_ID FUNCTIONAL_ CURRENCY_ CODE CODE_ NUMBER(15) COMBINATION_ ID ATTRIBUTE1 ATTRIBUTE2 VARCHAR2(20) VARCHAR2(20) CODE_ COMBINATION_ ID ATTRIBUTE1 ATTRIBUTE2 GL_SL_LINK_ID GL_SL_LINK_ TABLE ATTRIBUTE3 ATTRIBUTE4 ATTRIBUTE5 ATTRIBUTE6 VARCHAR2(20) VARCHAR2(20) VARCHAR2(20) VARCHAR2(20) ATTRIBUTE3 ATTRIBUTE4 ATTRIBUTE5 ATTRIBUTE6 CONTEXT
NUMBER(15) NUMBER(15) NUMBER(15) VARCHAR2(15)
NUMBER(15)
Straight mapping.
VARCHAR2(150) VARCHAR2(150) NUMBER VARCHAR2(30) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150) VARCHAR2(150)
Do not pull these columns. Do not pull these columns. Leave these null. Leave these null. Do not pull these columns. Do not pull these columns. Do not pull these columns. Do not pull these columns. Do not pull these columns.
Column Name
Data Type
Column Name CONTEXT2 INVOICE_DATE TAX_CODE INVOICE_ IDENTIFIER INVOICE_ AMOUNT CONTEXT3 USSGL_ TRANSACTION _CODE DESCR_FLEX_ ERROR_ MESSAGE JGZZ_RECON_ REF REFERENCE_ DATE
Data Type VARCHAR2(150) DATE VARCHAR2(15) VARCHAR2(20) NUMBER VARCHAR2(150) VARCHAR2(30)
Reqd
Remarks Do not pull these columns. Do not map. Do not map. Do not map. Do not map. Do not map. Do not map.
VARCHAR2(240)
Do not map.
VARCHAR2(240) DATE
Do not map. Do not map. Do not map.
PGM_NAME
VARCHAR2(100) ENCUMBRANCE_ NUMBER TYPE_ID BUDGET_ VERSION_ID AVERAGE_ JOURNAL_ FLAG ORIGINATING_ BAL_SEG_ VALUE SEGMENT11-30 NUMBER VARCHAR2(1)
Do not map. Do not map. Do not map.
VARCHAR2
Do not map.
VARCHAR2(25)
Do not map. Do not map. Do not map. Do not map. Do not map. Do not map. Do not map. Do not map.
REFERENCE1,3,4,6 VARCHAR2(100) -9 REFERENCE10,2,5 REFERENCE11-20 REFERENCE26-30 DATE_CREATED_ IN_GL WARNING_ CODE STATUS_ DESCRIPTION VARCHAR2(240) VARCHAR2(100) VARCHAR2(240) DATE VARCHAR2(4) VARCHAR2(240)
Column Name
Data Type
Column Name STAT_AMOUNT GROUP_ID REQUEST_ID SUBLEDGER_ DOC_ SEQUENCE_ID
Data Type NUMBER NUMBER(15) NUMBER(15) NUMBER
Reqd
Remarks Do not map. Do not map. Do not map. Do not map.
SUBLEDGER_ NUMBER DOC_SEQUENCE_ VALUE
Do not map.
H
Appendix: New Matched Invoices for Payment
The following tables describe the mapping of data from Oracle Retail Invoice Matching (ReIM) to Oracle E-Business Suite Accounts Payable.
IM_AP_STAGE_HEAD to AP_INVOICES_INTERFACE
IM_AP_STAGE_HEAD DOC_ID SEQ_NO INVOICE_TYPE_LOOKUP_ CODE INVOICE_NUMBER VENDOR ORACLE_SITE_ID CURRENCY_CODE EXCHANGE_RATE EXCHANGE_RATE_TYPE DOC_DATE AMOUNT BEST_TERMS_DATE SEGMENT1 SEGMENT2 SEGMENT3 SEGMENT4 SEGMENT5 SEGMENT6 SEGMENT7 AP_INVOICES_INTERFACE Comments INVOICE_ID NONE INVOICE_TYPE_LOOKUP_ CODE INVOICE_NUM VENDOR_ID VENDOR_SITE_ID INVOICE_CURRENCY_ CODE EXCHANGE_RATE EXCHANGE_RATE_TYPE INVOICE_DATE INVOICE_AMOUNT TERMS_DATE ACCTS_PAY_CODE_ CONCATENATED ACCTS_PAY_CODE_ CONCATENATED ACCTS_PAY_CODE_ CONCATENATED ACCTS_PAY_CODE_ CONCATENATED ACCTS_PAY_CODE_ CONCATENATED ACCTS_PAY_CODE_ CONCATENATED ACCTS_PAY_CODE_ CONCATENATED All segments (1-10) concatenated with - are mapped to ACCTS_PAY_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to ACCTS_PAY_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to ACCTS_PAY_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to ACCTS_PAY_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to ACCTS_PAY_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to ACCTS_PAY_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to ACCTS_PAY_CODE_CONCATENATED. Expecting the value USER in this column
IM_AP_STAGE_HEAD SEGMENT8 SEGMENT9 SEGMENT10 CREATE_DATE_TIME
AP_INVOICES_INTERFACE Comments ACCTS_PAY_CODE_ CONCATENATED ACCTS_PAY_CODE_ CONCATENATED ACCTS_PAY_CODE_ CONCATENATED CREATION_DATE All segments (1-10) concatenated with - are mapped to ACCTS_PAY_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to ACCTS_PAY_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to ACCTS_PAY_CODE_CONCATENATED.
IM_AP_STAGE_DETAIL to AP_INVOICE_LINES_INTERFACE
IM_AP_STAGE_DETAIL AP_INVOICE_LINES_ INTERFACE INVOICE_ID LINE_NUM NONE LINE_TYPE_LOOKUP_ CODE AMOUNT TAX_CODE DIST_CODE_ CONCATENATED DIST_CODE_ CONCATENATED DIST_CODE_ CONCATENATED DIST_CODE_ CONCATENATED DIST_CODE_ CONCATENATED DIST_CODE_ CONCATENATED DIST_CODE_ CONCATENATED DIST_CODE_ CONCATENATED DIST_CODE_ CONCATENATED DIST_CODE_ CONCATENATED CREATION_DATE All segments (1-10) concatenated with - are mapped to DIST_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to DIST_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to DIST_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to DIST_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to DIST_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to DIST_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to DIST_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to DIST_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to DIST_CODE_CONCATENATED. All segments (1-10) concatenated with - are mapped to DIST_CODE_CONCATENATED. Comments
DOC_ID SEQ_NO TRAN_CODE LINE_TYPE_LOOKUP_ CODE AMOUNT VAT_CODE SEGMENT1 SEGMENT2 SEGMENT3 SEGMENT4 SEGMENT5 SEGMENT6 SEGMENT7 SEGMENT8 SEGMENT9 SEGMENT10 CREATE_DATE_TIME
V_IM_FINANCIALS_STAGE to GL_INTERFACE
V_IM_FINANCIALS_STAGE STATUS ACTUAL_FLAG TRAN_CODE DEBIT_CREDIT_IND DOC_ID PARENT_ID DOC_DATE RECEIPT_ID RECEIPT_DATE VENDOR_TYPE VENDOR ORDER_NO CURRENCY_CODE AMOUNT BEST_TERMS BEST_TERMS_DATE MANUALLY_PAID_IND PRE_PAID_IND CREATE_ID CREATE_DATETIME SEGMENT1 SEGMENT2 SEGMENT3 SEGMENT4 SEGMENT5 SEGMENT6 SEGMENT7 SEGMENT8 SEGMENT9 SEGMENT10 VAT_CODE VAT_RATE CREATED_BY DATE_CREATED SEGMENT1 SEGMENT2 SEGMENT3 SEGMENT4 SEGMENT5 SEGMENT6 SEGMENT7 SEGMENT8 SEGMENT9 SEGMENT10 TAX_CODE REFERENCE20 REFERENCE24 CURRENCY_CODE ACCOUNTING_DATE REFERENCE25 REFERENCE22 GL_INTERFACE STATUS ACTUAL_FLAG REFERENCE23 Comments Hard-coded value of NEW in the view definition Hard-coded value of A in the view definition
V_IM_FINANCIALS_STAGE DEAL_ID LOCAL_CURRENCY INCOME_LOCAL_CURRENCY EXT_DOC_ID SET_OF_BOOKS_ID USER_JE_SOURCE_NAME USER_JE_CATEGORY_NAME ENTERED_DR ENTERED_CR
GL_INTERFACE
Comments
REFERENCE21 SET_OF_BOOKS_ID USER_JE_SOURCE_NAME USER_JE_CATEGORY_NAME ENTERED_DR ENTERED_CR Constant value Retail Invoices Write offs, prepayments, or manual payments

Or Ebs 1311 Intg

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Or Ebs 1311 Intg

Hochgeladen von

Copyright:

Verfügbare Formate

Oracle Retail / Oracle EBusiness Suite

Integration Guide Using Accelerator July 2009

Note: The following is intended to outline our general

Integration Guide Using Accelerator 1

2 Oracle E-Business Suite

Integrated Data Flows

Oracle Retail BPEL Process Manager Patch

Software Release Levels

Oracle E-Business Suite Release Levels

Oracle E-Business Suite Release 12.0.4

Oracle Retail Release Levels

4 Oracle E-Business Suite

Sales Data Post to Stock Ledger

Direct Access Layer RIB

Oracle Retail Merchandising System

Oracle E-Business Suite (General Ledger, Stock Ledger)

Oracle Retail Invoice Matching

Oracle E-Business Suite (Accounts Payable)

Oracle Retail and Oracle E-Business Suite IntegrationLogical View

Integration Guide Using Accelerator 5

Integration Guide Using Accelerator 7

Oracle E-Business SuiteOracle Retail Outbound Process Flow

Outbound Process Flow

The outbound process flow is as follows:

8 Oracle E-Business Suite

Oracle RetailOracle E-Business Suite Inbound Process Flow

Inbound Process Flow

The inbound process flow is as follows:

Integration Guide Using Accelerator 9

Install the BPEL Server

installed, the following patches must be applied: 6509776:R12.AP.A and 6665695:R12.AP.A

Start the Oracle BPEL Process Manager engine.

10 Oracle E-Business Suite

Deploy BPEL Processes

Deploy New BPEL Processes

BPEL Process Manager Console Login

Integration Guide Using Accelerator 11

Deploy New BPEL Processes 3.

SendVendorsToRMS.jar SendPaymentTermsToRMS.jar SendFreightTermsToRMS.jar

12 Oracle E-Business Suite

BPEL Process User Properties

Install the Integration Accelerator Patch

Integration Guide Using Accelerator 13

Setting up the Integration Accelerator Patch

Note: Retail_EBS.tar file is created.

Navigate to the directory CODE/AP/DB_OBJECTS. Execute the following.

Navigate to the directory CODE/GL/DB_OBJECTS. Execute the following.

14 Oracle E-Business Suite

Oracle E-Business Suite General Ledger Chart of Accounts to RMS

Integration Guide Using Accelerator 15

SendGLCCToRMS BPEL Process

16 Oracle E-Business Suite

Oracle E-Business Suite Exchange Rates to RMS

Integration Guide Using Accelerator 17

SendCurrRatesToRMS BPEL Process

18 Oracle E-Business Suite

Oracle E-Business Suite Vendor Reference Data to RMS

Setting Up Supplier Sites

Transferring Supplier Information from Oracle E-Business Suite to RMS

Integration Guide Using Accelerator 19

20 Oracle E-Business Suite

SendVendorToRMS BPEL Process