Oracle Revenue Management and Billing ORMB-EBS Implementation Guide

Oracle® Revenue Management and Billing
Version 2.5.0.1.0
ORMB-EBS Implementation Guide

Revision 1.1
E84279-01
February, 2017
Oracle Revenue Management and Billing EBS Implementation Guide
ORMB-EBS Implementation Guide

E84279-01
Copyright Notice
Copyright © 2017, Oracle and/or its affiliates. All rights reserved.
Trademark Notice
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be
trademarks of their respective owners.
This software and related documentation are provided under a license agreement containing
restrictions on use and disclosure, and are protected by intellectual property laws. Except as expressly
permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any
form, or by any means. Reverse engineering, disassembly, or de-compilation of this software, unless
required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-
free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS
Programs, software, databases, related documentation and technical data delivered to U.S.
Government customers are "commercial computer software" or "commercial technical data"
pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental
regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject
to restrictions and license terms set forth in the applicable Government contract, and, to the extent
applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-
19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle
Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It
is not developed or intended for use in any inherently dangerous applications, including
applications which may create a risk of personal injury. If you use this software in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and
other measures to ensure the safe use of this software. Oracle Corporation and its affiliates
disclaim any liability for any damages caused by use of this software in dangerous applications.
This software and documentation may provide access to or information on content, products and
services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third party content, products and
services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages
incurred due to your access to or use of third party content, products or services.
ii Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

Change Log
Revision Last Update Updated Section Comments
1.1 08-Jan-2018 Section 2.3.1.1: General Ledger Integration Updated Information
Section 2.4.4.3: AP Data Integration Point Modified Information
Section 2.4.5.1: GL Integration Point for EBS Modified Information
Section 2.4.5.2: A/P Request Integration Point for Modified Information
EBS
Section 2.4.5.3: A/P Data Integration Point for EBS Modified Information
Section 4.1.1.2: AP Request Integration Point Updated Information
Section 4.1.2.3: AP Data Integration Point Updated Information
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. iii
Contents
1. Glossary ............................................................................................................................................... vi
2. Solution Overview.................................................................................................................................1
2.1 Summary .....................................................................................................................................1
2.2 Business Process Task Flow.........................................................................................................1
2.2.1 General Ledger Process .................................................................................................2
2.2.2 Account Payable Request Process .................................................................................4
2.2.3 Account Payable Data Process.......................................................................................6
2.3 Best Practices ..............................................................................................................................8
2.3.1 One-Time Configuration Settings ..................................................................................8
2.4 Solution Flow ............................................................................................................................13
2.4.1 Integration Prerequisites .............................................................................................13
2.4.2 ODI Process Flow .........................................................................................................13
2.4.3 Solution Diagram for Integration using ODI ................................................................13
2.4.4 Database Details for Integration .................................................................................15
2.4.5 Logic Used in the Integration Points............................................................................17
2.4.6 Process Scheduling ......................................................................................................21
2.4.7 Trouble Shooting .........................................................................................................21
3. Physical Data Model ...........................................................................................................................23
4. Configuration ......................................................................................................................................24
4.1 Configuring the Integration.......................................................................................................24
4.1.1 EBS Configuration ........................................................................................................28
4.1.2 ORMB Configuration ....................................................................................................31
5. Verifying the Integration ....................................................................................................................36
5.1.1 GL Integration Point.....................................................................................................36
5.1.2 A/P Request Integration Point .....................................................................................36
5.1.3 A/P Data Integration Point ..........................................................................................36
6. Running ODI Process Flows ................................................................................................................38
6.1.1 GL Request ...................................................................................................................38
6.1.2 AP Request...................................................................................................................38
6.1.3 AP Data Request ..........................................................................................................38
7. Available Extension Points in ODI .......................................................................................................39
7.1.1 GL Extension Point .......................................................................................................39
7.1.2 AP Request Extension Point.........................................................................................39
7.1.3 AP Data Extension Point ..............................................................................................40
8. Appendix: A.........................................................................................................................................41
8.1 EBS Data Mapping .....................................................................................................................41
iv Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

8.1.1 GL Transaction .............................................................................................................41

8.1.2 A/P Request .................................................................................................................50
8.1.3 A/P Data .......................................................................................................................73
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. v

1. Glossary
Term Definition
ORMB Oracle Revenue Management and Billing System
EBS Oracle E-Business Suite Revenue Accounting General Ledger and Accounts Payable
GLDL General Ledger Download Flat File
GL General Ledger
AP Accounts Payable
LKM Load Knowledge Module
IKM Integration Knowledge Module
CKM Check Knowledge Module
vi Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

2. Solution Overview
2.1 Summary
This document provides information on the integration between Oracle Revenue Management and
Billing (ORMB) and Oracle E-Business Suite Revenue Accounting General Ledger and Accounts Payable
using Oracle Data Integrator tool. The sections below provide an overview of the participating
applications and information regarding the business processes addressed by this integration.
2.2 Business Process Task Flow

This integration of products incorporates three areas of key functionality to facilitate the transfer of
information between two applications. Data is sent from Oracle Revenue Management and Billing to
Oracle E-Business Suite Payables for General Ledger and Accounts Payable and vice versa to support the
following transactions and actions:
RMB Oracle E-Business Suite

A bill is created/ cancelled The general ledger is updated with the journal
information.
A payment is created/ cancelled
An adjustment is created / cancelled
An adjustment whose type indicates A/P Request Customer and A/P Request information is used to
is created create a one-time supplier and supplier site. An
account payable Invoice is created and associated
with this supplier and supplier site.
RMB Oracle E-Business Suite

A payment is created for an invoice related to an Payment information is sent from EBS to ORMB.
ORMB A/P request. The A/P Request is updated with the payment
information.
A check related to an invoice linked to an A/P
request is re-issued.
A check related to an invoice linked to an A/P The A/P request and its associated adjustment
request is voided and the liability is closed. are cancelled.
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 1

The flow of data between the two systems is illustrated below:
2.2.1 General Ledger Process

For general ledger transactions, ORMB is considered the sub-ledger and EBS is considered the general
ledger.
 General Ledger transactions are written in one direction; from ORMB to EBS.
 Financial transactions are moved from the sub-ledger to the general ledger when two
consecutive ORMB batch processes, GLASSIGN and GLS, are run according to a set schedule.
These are standard processes released with ORMB.
 The GLASSIGN and GLS processes group all the financial transactions in ORMB that must be
included in a batch. The Integration Point checks for batches of financial transactions that are
ready to be sent, extracts and summarizes the data, translates the data from a sub-ledger format
to the format required by the general ledger, and writes it to the EBS integration table. The
standard General Ledger integration table released with the EBS product is used.
 Once the entries are created in EBS staging tables, the journal creation, editing and posting to
the ledger must be executed within EBS. The standard Journal Import process must be executed
to create the necessary journal entries within the General Ledger. You can accomplish this by
scheduling the standard EBS Journal Import process or by manually running this process through
the Standard Request Submission (SRS) provided within EBS.
2 Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

Figure 1 GL Process Flow Diagram
Following are the steps for the GL Process flow:

1. Run GLASSIGN batch program in ORMB which simply calls each GL’s details distribution code’s GL
assignment algorithm and updates the GL detail with the GL account number. (Ref: Steps 1 & 2 in
flow diagram).
2. Run GLS batch program in ORMB which creates FT download staging records for all FTs that are
ready to be added/registered to the GL. (Ref: Steps 3 & 4 in flow diagram).
3. ODI extracts this FT information from ORMB to be interfaced with EBS when scheduler runs for this
scenario EBS_MASTER_GL_PKG in ODI. (Ref: Steps 5, 6 & 7 in flow diagram).
4. ODI updates the Next_Batch_Nbr for GLDL in CI_Batch_Ctrl table in RMB. (Ref: Step 8 in flow
diagram).

5. ODI transforms and inserts the data into EBS interface tables and reports errors in transformation if
any. (Ref: Steps 9 to 14 in flow diagram).
6. ODI updates the Last_Update_DateTime in CI_Batch_Ctrl table in ORMB. (Ref: Steps 16 in flow
diagram).
7. Run Journal Import process in EBS to import FTs. (Ref: Steps 17 in flow diagram)
8. Any errors in interface tables must be corrected in EBS and the Journal Import process must be re-
run. (Ref: Steps 18 & 19 in flow diagram).0.
2.2.2 Account Payable Request Process

 AP Request transactions are written in one direction from ORMB to EBS. Customer, customer
account, and AP Request information is extracted from ORMB and imported to the EBS as
Invoice import information. Customer and AP Request information is used to create a one-time
supplier and supplier site that is used for invoice creation.
 The integration extracts AP Requests from ORMB where the status of the AP Request is ‘N’ which
indicates that the AP Request is ‘Not Selected for Payment'. Once the data has been integrated,
the integration software updates the AP Request status in ORMB to ‘R’ indicating it has been
‘Requested for Payment’.
 Once the customer and refund request data is loaded into EBS by ODI, the standard Payables
Open Interface Import (APXIIMPT) process must be executed to create invoices. This can be
accomplished using a scheduled process or by manually running the process through the
standard user interface provided within the EBS product.

Figure 2 AP Process Flow Diagram
Following are the steps in AP Request flow:

1. Create and freeze an adjustment in ORMB and run GLASSIGN batch program. (Ref: Steps 1 & 2 in
flow diagram).
2. ODI extracts AP Refund Request information from ORMB. (Ref: Steps 3, 4 & 5 in flow diagram).
3. ODI invokes vendor and vendor site API in EBS to create/update vendor and vendor site which
checks if the vendor is available in EBS, if not already available creates a new vendor. Similarly
checks if the vendor site is available in EBS for the vendor created and adds the same in EBS if not
available. (Ref: Steps 6 in flow diagram).
4. ODI updates the Next_Batch_Nbr for APDL in CI_Batch_Ctrl table in RMB. (Ref: Steps 7 in flow
diagram).

5. ODI scenario EBS_MASTER_APREQ_PKG transforms and inserts the data into EBS interface tables
and reports any errors in transformation when the scheduler runs (Ref: Steps 8 to 14 in flow
diagram).
6. In case of an error, ODI decrements the Next_Batch_Nbr for APDL in CI_Batch_Ctrl table in RMB
(Ref: Steps 15 in flow diagram).
7. ODI updates the status of A/P Request in ORMB. (Ref: Step 16 in flow diagram).
8. Run Payables Open Interface Import process in EBS to import Invoices. (Ref: Steps 17 in flow
diagram).
9. Any errors in the interface tables must be corrected in EBS and Payables Open Interface Import
process must be re-run. (Ref: Steps 18 & 19 in flow diagram).0.
2.2.3 Account Payable Data Process

AP data transactions are written in one direction from EBS to ORMB.
 Payment information for system-generated checks to customers is generated, processed in EBS
and then exported to ORMB.
 This payment information corresponds to the AP Refund Requests originally generated in RMB
and exported to Oracle EBS for payment processing. The Integration Point updates the original
AP Request in ORMB with the details of the payment including the check number and date.
 Once a payment has been created in EBS and the information is integrated to ORMB, the AP
Request status in ORMB is updated to ‘P’ indicating that the AP Request has been paid.
Additional statuses that can occur include ‘C’ – Closed or on Hold and ‘X’ – Cancelled.
Please refer the table below to review how canceled payments are handled.
EBS ORMB AP Request Resulting Action ORMB Adjustment Resulting

Action
Payment is completed Payment information updated and No change
status changes to “P” for Paid
Payment stopped and Payment status changes to “C” for No change
placed on hold Closed
Payment is re-issued Payment information updated and No change
status changes to “P” for Paid
Payment is cancelled Payment status changes to “X” for Adjustment is cancelled
and the liability is closed Cancelled

Payment Cancellation Process

When a payment is cancelled in EBS, the following options are available:
Re-Issue
If a check is re-issued for any reason in EBS, the new information is sent across the integration and is
updated on the AP Request in ORMB and the AP Request status is set to ‘P’ indicating that the AP
Request has been paid.
The AP Request in ORMB only holds the most recent check information sent (no history of checks re-
issued).
Initiate Stop/Void Hold

If a payment is stopped or put on hold, the cancellation information is sent to ORMB as updates to the
AP Request. The AP Request payment status flag in ORMB is set to ‘C’ indicating a ‘Closed’ status. Only
the AP Request is affected, the adjustment in ORMB is not impacted.
Void cancel
If the payment is void cancelled and all liability is closed, the integration cancels the AP Request and calls
an ORMB service to cancel the adjustment related to the request. The AP Request payment status flag in
ORMB is set to ‘X’ indicating a ‘Cancelled’ status. The adjustment is also cancelled using the standard
adjustment maintenance object within the ORMB application software. An ORMB algorithm CI_ADCA-
CRTD ‘Adjustment Cancellation – Create To Do Entry’ can be configured to create a To Do List entry to
notify the users about the cancellation of the adjustment and AP Request within ORMB.
Figure 3 AP Data Process Flow Diagram

Following are the steps in AP Data process flow when a payment is made in EBS:
1. Payment is made in EBS for invoices originated from ORMB. (Ref: Step 1 in flow diagram)
2. ODI scenario EBS_MASTER_APDATA_PKG extracts, transforms and updates the Payment
information in ORMB (Ref: Steps 2 to 8 in flow diagram) and reports if any errors in transformation.
3. ODI updates the Last Run Date of AP Data Process in Integration Schema (Ref: Step 9 in the flow
diagram).0.
Figure 3 AP Data Process Flow Diagrams for Cancellation
Following are the steps in the AP Data process flow when a payment is cancelled in EBS:
1. Payment is cancelled in EBS for invoices originated from ORMB (Ref: Step 1 in flow diagram)
2. ODI scenario EBS_MASTER_APDATA_PKG updates the cancellation information in ORMB and
invokes CIAdjustmentMaintenance Web Service in ORMB to cancel the adjustment. (Ref: Steps 2 to
9 in the flow diagram) and reports if any errors in the transformation.
3. ODI updates the Last Run Date of AP Data process in integration schema (Ref: Step 10 in flow
diagram).0.
2.3 Best Practices

The following sections provide business information helps achieve accurate and error-free movement of
data between ORMB and EBS.
Note: Detailed configuration settings specific to the integration is provided in the section titled
Configuring the Integration. Refer to the product specific documentation for information on how to
complete product specific configuration tasks.
2.3.1 One-Time Configuration Settings

Following are the one-time configuration settings that must be coordinated manually to ensure proper
results from the movement of data between the two applications.

General Ledger Configuration

Oracle E-Business Suite Revenue Accounting General Ledger is the source of truth for all General Ledger
information. Oracle Utilities Revenue Management and Billing is considered to be the sub-ledger. It is
assumed that the General Ledger has already been configured to accommodate you business needs.
Distribution Codes
RMB uses distribution codes to map sub-ledger transactions to the General Ledger accounts. As part of
your RMB setup, it is assumed that you have properly mapped your distribution codes to the General
Ledger chart of accounts.
General Ledger Divisions for Non-Integrated Transactions

If some of the transactions created in RMB must not be integrated to your General Ledger you must
configure a separate General Ledger Division for these transactions. You must then configure the
integration product to distinguish which General Ledger Division must be integrated with the General
Ledger..
2.3.1.1 General Ledger Integration

Oracle E-Business Suite Revenue Accounting General Ledger accounts are structured using account
segments. These are set up in your existing Oracle E-Business Suite Revenue Accounting Flexfield
according to your business practices. Oracle Revenue Management and Billing distribution codes must
be configured to mirror the segments in Oracle E-Business Suite Revenue Accounting. The segment
positions are separated by dots ‘.’ in Oracle Revenue Management and Billing according to the Oracle E-
Business Suite Revenue Accounting segments defined in the Accounting Flexfield.
Create your Accounting Flexfield in the Oracle E-Business Suite Revenue Accounting General Ledger (if it
does not exist) then set up your Oracle Revenue Management and Billing distribution codes to map to
the General Ledger account structure using dot separators.
You should understand the differentiation between GL accounts and ORMB customer billing account
properly. A customer billing account is a collection of information associated with a customer that is
used in the Oracle Revenue Management and Billing payment and billing process, and does not relate to
the Oracle E-Business Suite accounting definition of account (General Ledger Account). The Oracle
Revenue Management and Billing distribution code is used to map to the Oracle E-Business Suite
general ledger account.
Oracle E-Business Suite Revenue Accounting General Ledger Settings
Configure General Ledger settings in Oracle E-Business Suite Revenue Accounting according to the
following guidelines, keeping in mind that Oracle E-Business Suite Revenue Accounting is the source of
truth for the general ledger.

 Journal Generator Process: Schedule the Journal import process to create journals from Oracle
Revenue Management and Billing information inserted into interface tables by the integration
software. When you configure Oracle E-Business Suite Revenue Accounting to run this process
automatically at a preset time, ensure you have matched this timing with the timing of other
actions completed by Oracle Revenue Management and Billing and the integration product.
Alternatively you may use the Standard Request Submission (SRS) within Oracle E-Business Suite
Revenue Accounting to run the Journal Import process manually.
 Accounting Entry Definition: If not already configured, pre-configure an Accounting Flexfield
definition in Oracle E-Business Suite Revenue Accounting to indicate the staging table where
incoming accounting entries must be stored. Ensure that all mandatory fields on the staging
tables are mapped.
 The integration software relies on other Oracle E-Business Suite Revenue Accounting
configuration information including: Calendars, Ledger, Journal source, Journal Category. These
are usually already configured as part of your implementation. If these do not already exist
configure them for the integration software to run correctly.
Oracle Revenue Management and Billing General Ledger Settings
Configure General Ledger settings in Oracle Revenue Management and Billing according to the following
guidelines, keeping in mind that Oracle E-Business Suite Revenue Accounting is the overriding source for
the general ledger.
 Schedule the GLASSIGN and GLS batch processes to run at an appropriate time of day. These
processes get sub ledger information in Oracle Revenue Management and Billing and all
information that has not been posted to the General Ledger, making them ready to extract,
transform and load to the General Ledger. When you configure Oracle Revenue Management
and Billing to run this process automatically at a preset time, ensure you have coordinated this
timing with the timing of other actions done by Oracle E-Business Suite Revenue Accounting and
the integration product. (Alternatively you may use the standard user interface within Oracle
Revenue Management and Billing to run these batch processes manually).
 Ensure that Distribution Codes are configured in Oracle Revenue Management and Billing to
properly reflect the General Ledger accounts that must be debited and credited for each type of
financial transaction created.
Integration Software General Ledger Settings
As part of the technical configuration you must configure the following information:
 E-mail address of the person be notified in case the integration software detects and logs an
error while performing the integration
 The Ledger ID, Ledger Source and Ledger Category to be used for journals in Oracle E-Business
Suite Revenue Accounting that are fetched from Oracle Revenue Management and Billing
through the integration.

 If you enter an Oracle Revenue Management and Billing GL Division name in the configuration
table then only financial transactions associated with this GL Division are extracted for
integration to Oracle E-Business Suite Revenue Accounting GL. Leave this configuration
information blank if you want all Oracle Revenue Management and Billing financial transactions
to be integrated to Oracle E-Business Suite Revenue Accounting GL.
Accounting
The following table shows the basic accounting debits and credits that can be achieved through the
setup indicated above:
Oracle Revenue Management and Debit Account Credit Account

Billing Event
Charges generated by billing Accounts Receivable Revenue
Customer making payment Cash Accounts Receivable
A/P Request adjustment Accounts Receivable Accounts Payable Clearing
2.3.1.2 Accounts Payable (A/P) Request and A/P Data Integrations
Oracle E-Business Suite Revenue Accounting General Ledger and Accounts Payable
A/P Settings
The Oracle E-Business Suite Revenue Accounting Payables Open Interface Import (APXIIMPT) must be
run to read the data from the A/P Invoice Interface tables and create invoices corresponding to the
Oracle Revenue Management and Billing A/P Requests. This process can be run manually or scheduled
to run at a pre-determined time.
Configuration needed for A/P Request and A/P Payment integrations includes:
 Payables Open Interface Import (APXIIMPT): Schedule this process to create A/P Invoices for the
Oracle Revenue Management and Billing information inserted into interface tables by the
integration product software. When you configure Oracle E-Business Suite Revenue Accounting
to run this process automatically at a preset time, ensure you have matched this timing with the
timing of other actions done by Oracle Revenue Management and Billing and the integration
product. (Alternatively you can use the Standard Request Submission (SRS) within Oracle E-
Business Suite Revenue Accounting to run the Payables Open Interface Import (APXIIMPT)
process manually).
 Payment Terms Code: Create a new payment terms code for processing the payments for Oracle
Revenue Management and Billing customers. These codes are used to define defaults such as
when payments must be made based on the invoice date, which status must be paid, any
applicable discounts, rebates and other pertinent payment information.
 Invoice Source: Create an Invoice Source so that all the invoices from the Oracle Revenue
Management and Billing are identified with this source in Oracle E-Business Suite Revenue
Accounting system.
Note: Refer to the Oracle E-Business Suite Revenue Accounting General Ledger and Accounts Payable
User documentation for specific guidelines on configuring these settings.

Oracle Revenue Management and Billing A/P Settings
Configure Accounts Payable settings in Oracle Revenue Management and Billing according to the
following guidelines, keeping in mind that Oracle E-Business Suite Revenue Accounting is the overriding
source for the general ledger account information.
 CIS Division: The Oracle Revenue Management and Billing CIS Division characteristic value for
A/P Operating Unit must match the A/P Org ID in Oracle E-Business Suite Revenue Accounting.
 Characteristic for Distribution Code: An Oracle Revenue Management and Billing characteristic
associated with the distribution code assigned to an adjustment type used to create A/P
Requests in Oracle Revenue Management and Billing must be setup and its value must match the
value in the accounting combinations defined in Oracle E-Business Suite Revenue Accounting.
Note: Refer to the Oracle Utilities Oracle Revenue Management and Billing User documentation for
more information on the configuration settings referenced in this section.
Integration Software A/P Settings
The integration product extracts the A/P Requests that have yet not been processed from Oracle
Revenue Management and Billing. After the necessary translations and transformations on the
Supplier/Invoice data extracted from Oracle Revenue Management and Billing are applied, the data is
loaded into the Oracle E-Business Suite Revenue Accounting A/P Invoice Interface tables.
This integration product requires you to configure the following:
 E-mail address of the person to be notified if the integration software detects and logs an error
while performing the A/P Request and A/P Data integrations.
 The Oracle Revenue Management and Billing characteristic type holding the Oracle E-Business
Suite Revenue Accounting A/P Org ID.
 The A/P Invoice information required by Oracle E-Business Suite Revenue Accounting including
Vendor, Vendor Site, Invoice Source, Payment terms, Payment Method and A/P Org ID.
Accounting
The following shows the basic accounting debits and credits that can be achieved through the above A/P
setup:
Event Debit Account Credit Account

A/P Request Adjustment in Oracle Revenue Management Accounts Accounts Payable
and Billing (as part of the General Ledger Integration) Receivable Clearing
A/P Invoice Created in Oracle E-Business Suite Revenue Accounts Payable A/P Liability
Accounting Clearing
A/P Invoice Payment in Oracle E-Business Suite Revenue A/P Liability Cash
Accounting

2.4 Solution Flow

2.4.1 Integration Prerequisites
Following are the prerequisites the integration:
1. RMB application installed and running
2. EBS V12.2.4 application installed and running
3. ODI v12.1.3.0.0 installed and running. 0.
Note: For more information, refer to ORMB-EBS Integration Guide.
2.4.2 ODI Process Flow

ODI uses standard data mapping at the database level to extract, transform and load data to fetch it
from the source database system and insert into the target database system. After the source system
generates financial data:
 ODI extracts and consolidates the financial data.
 ODI then transforms the data into the appropriate format for loading into the target system.
 ODI then loads the data into the appropriate interface table in the target.
 When the target system receives this data, it validates and converts imported data into the
appropriate format of entries in the target application.
2.4.3 Solution Diagram for Integration using ODI
Figure 1 GL and AP Request Solution Flow Diagram

Figure 2 AP Data Solution Flow Diagram
Knowledge Modules (KM) implement “how” the integration processes occur. Each Knowledge Module
type in the diagrams above (LKM/CKM/IKM) refers to a specific integration task. A Knowledge Module is
a code template for a given integration task. This code is independent of the Declarative Rules to be
processed. At design-time, the Declarative Rules describing integration processes are created. These
Declarative Rules are merged with the Knowledge Module to generate code ready for runtime. At
runtime, Oracle Data Integrator sends this code for execution to the source and target systems to load,
join and transform the data.
Above figure 1 & figure 2 shows the data flow automatically generated by Oracle Data Integrator (ODI)
to load the final target tables. The business rules (data mapping/transformation rules) will be
transformed into code by the Knowledge Modules (KM). The code produced will generate several steps.
These steps will extract and load the data from the source tables to the staging area (Loading Knowledge
Modules - LKM). Other internal ODI stages will transform and integrate the data from the staging area to
the target tables (Integration Knowledge Module - IKM).
In case of Figure 1:- Source ORMB - Staging area ODI - Target EBS. (GL/AP Request)
In case of Figure 2:- Source EBS - Staging area - Target ORMB. (AP data Request)
To ensure data quality, the Check Knowledge Module (CKM) will apply the user defined constraints to
the staging data to isolate erroneous records in the ODI Error table.
At this point we have the source database (either EBS or ORMB), ODI database for the master and work
repositories (2 schemas) and the target database (either EBS or ORMB).

2.4.4 Database Details for Integration

The following table shows the integration process, source application, target application, tables, and
process used to load the data that is imported from the other system.
General Ledger as EBS
Integration Source Target System Process Integration Process

Process System
General Ledger ORMB EBS Journal Import GL_INTERFACE
AP Request ORMB EBS Payables Open AP_INVOICES_INTERFACE
Interface Import AP_INVOICE_LINES_INTE
RFACE
AP Data EBS ORMB The appropriate AP The appropriate AP
Request within Request within ORMB
ORMB
The following new database tables are required to operate RMB process integration for the EBS product.
Table Description
INTEGRATION_LOOKUP_TABLE A lookup table to store all the configuration parameters used by
the ODI processes. This table is also used to configure the email
addresses to be notified in case of any error. This table is seeded
with data at the time of integration product installation.
INTEGRATION_ERROR_STORE The table is used to hold the information of the errors
encountered during integration transactions. For each error
encountered by the ODI processes, a record in the
INTEGRATION_ERROR_STORE table. The mail notification process,
MailNotification, accesses this table to get the error information
needed to construct the notification email. This table is delivered
with no data.
2.4.4.1 GL Integration Point
RMB
The following ORMB tables are used when extracting Financial Transaction data for sending to the GL as
Journal Vouchers:
 CI_FT
 CI_FT_GL
 CI_DST_CODE_EFF
 CI_FT_PROC (FT Process)
 CI_BATCH_CTRL (Batch Control)
 CI_BATCH_RUN

 CI_BATCH_JOB
EBS
GL_INTERFACE is used to stage the incoming accounting entries from ORMB.
2.4.4.2 AP Request Integration Point
RMB
The following tables are used when extracting AP Request information from ORMB:
 CI_ADJ_APREQ
 CI_ADJ
 CI_SA
 CI_ACCT
 CI_ACCT_PER
 CI_PER
 CI_PER_NAME
EBS
The following AP Invoice staging tables are used to stage the incoming AP Requests from ORMB:
 AP_INVOICES_INTERFACE
 AP_INVOICE_LINES_INTERFACE
Error messages are stored in AP_INTERFACE_REJECTIONS table.

Oracle Application APIs to create/update Vendor and Vendor Site
Release R12:
 AP_VENDOR_PUB_PKG.CREATE_VENDOR
 AP_VENDOR_PUB_PKG.CREATE_VENDOR_SITE
 AP_VENDOR_SITES_PKG.UPDATE_ROW
2.4.4.3 AP Data Integration Point
EBS
The Payment Information is extracted from the following application tables:

 AP_INVOICES_ALL
 AP_CHECKS_ALL

 AP_INVOICE_PAYMENTS_ALL
RMB
The CI_ADJ_APREQ application table is updated with the payment Information received from EBS. This
table is considered as an interface table for the purpose of this integration point even though it is a core
ORMB table.
2.4.5 Logic Used in the Integration Points

The following describes the logic used in ODI that forms part of this integration product.
2.4.5.1 GL Integration Point for EBS
ODI Polls to Verify whether FTs are ready for extraction
ODI polls RMB to verify whether financial transactions are ready for extraction.
If GLS has run since the last run of the integration
AND the GLS run has completed successfully
Retrieve the Batch of Rows identified in CI_BATCH_RUN (created by GLS)
Else
Do nothing
Update the NEXT BATCH NUMBER in CI_BATCH_CNTRL
Increment the NEXT_BATCH_NBR by 1 in CI_BATCH_CTRL WHERE BATCH_CD is GLDL
Extract Financial Transactions from RMB
Select the information shown in the table below:

FROM CI_FT_PROC, CI_FT_GL, CI_FT FT, CI_DST_CODE_EFF
WHERE the rows were marked by GLS belonging to the latest batch ready to be integrated.
Summarize and group the rows
BY FTPR.BATCH_NBR, FTGL.DST_ID, FTGL.GL_ACCT, FT.CIS_DIVISION, FT.GL_DIVISION,
FT.CURRENCY_CD, DST.STATISTICS_CD, FT.ACCOUNTING_DT, DST.FUND_CD
Field Name Source/Value/Description

Source System Set to RMB
BATCH_NBR The batch number for the group of FT’s extracted. The batch number is
assigned to the financial transaction when GLS is run.
DIST_ID The distribution code used in RMB to derive the GL account information. A
sample data example is R – ELERES for electric residential revenue financial
transactions.

Field Name Source/Value/Description

GL_ACCT The actual GL account with ‘.’ separating the substructure numbers like
department. For example 101.73653.8873..87
CIS_DIVISION The CIS Division
GL_DIVISION The GL Division
CURRENCY_CD The currency of the amount, such as USD.
STATISTICS_CD The identifier of the type of statistical amount being sent to GL.
ACCOUNTING_DT The effective accounting date for the GL transactions
AMOUNT The dollar amount of the GL debit or credit
STATISTIC_AMOUNT The quantity associated with the Statics Code.
When the above is executed successfully, continue by executing the following:
Update the LAST UPDATE TIME FOR GLDL in CI_BATCH_CNTRL
Set the last update date and time by setting

CI_BATCH_CTRL LAST_UPDATE_DTTM to SYSDATE WHERE BATCH_CD = 'GLDL'
Update the NEXT BATCH NUMBER in CI_BATCH_CNTRL
Increment the NEXT_BATCH_NBR by 1 in CI_BATCH_CNTRL where the BATCH_CD is GLDL
2.4.5.2 A/P Request Integration Point for EBS
Update the NEXT BATCH NUMBER in the CI_BATCH_CNTRL
Increment the NEXT_BATCH_NBR by 1 in CI_BATCH_CNTRL where the BATCH_CD is APDL
ODI Polls to Verify whether A/P Requests are ready for Extraction
ODI Polls RMB to verify whether A/P Requests are ready for extraction.
If there are A/P Requests where the CI_ADJ_APREQ PYMNT_SEL_STAT_FLG is N (not selected for
payment)
AND the associated adjustment is in a frozen status
Process the A/P Requests that have not been integrated before and mark all with the next APDL Batch
Number
Else do nothing.
Extract of Customer and A/P Refund Request
An extract of customer and A/P refund request is made from RMB.

Select the following information

AP_REQ_ID, GL_ACCT,CHAR_VAL, SA_ID, ADJ_ID, CRE_DT, ADJ_TYPE_CD, CIS_DIVISION, CHAR_VAL,
ENTITY_NAME, COUNTRY, ADDRESS1, ADDRESS2, ADDRESS3, ADDRESS4, CITY, NUM1, NUM2, COUNTY,
HOUSE_TYPE, STATE, POSTAL, CURRENCY_CD, CURRENCY_PYMNT, GEO_CODE, IN_CITY_LIMIT,
PYMNT_METHOD_FLG, ADJ_AMT, SCHEDULED_PAY_DT
(See mapping table A/P Request within this document for more details)
FROM CI_ADJ_APREQ, CI_ADJ, CI_SA, CI_ADJ_TYPE, CI_DST_CODE_EFF, CI_DST_CD_CHAR,
CI_CIS_DIV_CHAR
Where the PYMNT_SEL_STAT_FLG status flag is N (Not Selected for Payment)
AND the Adjustment is frozen
Updating CI_ADJ_APREQ Status
UPDATE CI_ADJ_APREQ
SET PYMNT_SEL_STAT_FLG to R (Requested for Payment)
Update the NEXT BATCH NUMBER in the CI_BATCH_CNTRL table
Increment the NEXT_BATCH_NBR by 1 in CI_BATCH_CNTRL where the BATCH_CD is APDL
2.4.5.3 A/P Data Integration Point for EBS
Extract the Payment Information from EBS
SELECT the following information

Select APA.invoice_id
,APA.invoice_num ADJ_ID
,APA.invoice_date
,APA.PAYMENT_STATUS_FLAG
,APA.POSTING_STATUS
,APA.CANCELLED_BY
,APA.CANCELLED_DATE
,APA.CANCELLED_AMOUNT
,AIPA.BANK_ACCOUNT_NUM
,AIPA.REVERSAL_FLAG
,AIPA.REVERSAL_INV_PMT_ID
,ACA.CHECK_DATE payment_date
,ACA.CHECK_NUMBER payment_number
,ACA.STATUS_LOOKUP_CODE

,ACA.VOID_DATE
,ACA.STOPPED_BY
,ACA.STOPPED_DATE
,APA.PAYMENT_REASON_COMMENTS AP_REQ_ID
,ACA.CHECK_ID
,ACA.amount
,ACA.released_date
FROM ap_invoices_all APA
AP_INVOICE_PAYMENTs_all AIPA
ap_checks_all ACA
WHERE APA.invoice_id = AIPA.invoice_id
AND AIPA.check_id = ACA.check_id
AND APA.source = ‘RMB’
AND (APA.CANCELLED_DATE >= TO_DATE ('2008-01-31','YYYY-MM-DD') -- last date the interface was run
OR APA.CREATION_DATE >= TO_DATE ('2008-01-31','YYYY-MM-DD')-- last date the interface was
run
OR ACA.stopped_date >= TO_DATE ('2008-01-31','YYYY-MM-DD')-- last date the interface was run
OR ACA.released_date >= TO_DATE ('2008-01-31','YYYY-MM-DD')-- last date the interface was run
OR ACA.void_date >= TO_DATE ('2008-01-31','YYYY-MM-DD') -- last date the interface was run
UNION
Select APA.invoice_id
,APA.invoice_num ADJ_ID
,null released_date
,APA.invoice_date
,APA.PAYMENT_STATUS_FLAG
,APA.POSTING_STATUS
,APA.CANCELLED_BY
,APA.CANCELLED_DATE
,APA.CANCELLED_AMOUNT
,null BANK_ACCOUNT_NUM
,null REVERSAL_FLAG
,null REVERSAL_INV_PMT_ID
,null payment_date

,null payment_number
,null STATUS_LOOKUP_CODE
,null VOID_DATE
,null STOPPED_BY
,null STOPPED_DATE
,APA.PAYMENT_REASON_COMMENTS AP_REQ_ID
,null CHECK_ID
,null AMOUNT
FROM ap_invoices_all APA
WHERE APA.CANCELLED_DATE = #LastRunDate6
AND APA.SOURCE= #invoice_source1
and apa.invoice_id not in (SELECT invoice_id FROM ap_invoice_payments_all aipa1)
For each payment selected above, check if this payment is already applied in RMB.
If AP_INVOICES_ALL.CANCELLED_DATE <> NULL and AP_INVOICES_ALL. PAYMENT_STATUS_FLAG<>’Y’
(Payment is void /cancelled)
If the payment has been canceled in EBS, update the CI_ADJ_APREQ. PYMNT_SEL_STAT_FLG to ’X’
(Canceled) and invoke the service C1AdjustmentMaintenance to cancel the Adjustment corresponding
to this payment.
2.4.6 Process Scheduling

Depending on the size and complexity of the accounting system and business practices, transactions
generated in either of the participating applications are sent to the alternate application as per a daily or
weekly schedule. The information transfer between applications is scheduled as per frequency that is
most appropriate for the organization. Agent feature in ODI can be used for scheduling the scenarios for
various flows. Agent needs to be running for scheduler to work. Ensure all the schema details for the
repositories are configured in odiparams file. Please refer to ODI specific documentation for further
information on scheduling.
2.4.7 Trouble Shooting

2.4.7.1 E-mail Notification
During the main integration processes, if any error occurs, the errors are logged in the Integration Error
table, INTEGRATION_ERROR_STORE and the notification sub process is invoked. The e-mail notification
sub process reads the information in the error table and sends an e-mail notification, based on settings
configured for the integration layer. This e-mail contains the following information:
• Subject: “Source System” “Target System”
• Body
• Source system
• Integration batch number

• Error Code
• Error Summary
• Error Message
Note: For all errors encountered during GLS/GLASSIGN jobs run or while running programs in EBS are to
be rectified manually in the respective systems.
2.4.7.2 Any Integration Point
Error Process Details Resolution

Scenario
System or ODI If ODI shuts down in the If ODI shuts down in the middle of a long
Network middle of an integration running process, a re-run should be
Down process. performed.

3. Physical Data Model

No changes to the existing data model in ORMB due to this integration.

4. Configuration
4.1 Configuring the Integration

The integration between ORMB and EBS incorporates three integration points to facilitate transfer of
information between the two applications. You must completely configure all involved products to
prepare the integration product for use.
The following sections describe how to configure each area for each integration point.
Configuration check list for EBS:
Step Information Comments

A1 Accounting Identify and document the Accounting Flexfield to be used with the
Flexfield integrated data. This should be decided before starting integrations so all
the journals are accounted and posted to these accounts.
A2 Ledger Id / Set of Specify the ledger to which all the accounting entries are to be created
Book ID and posted. In E-Business Suite Release12, the Ledger ID is used.
A3 Journal Source Specify the source of the journal from which it is created.
A4 Journal Category Specify the category to which all the journals belong.
A5 Organization ID Document the AP Operating Unit(s) to be used with the integrated data.
Example: ‘Vision Operations’. Derive the Organization ID with respect to
the Operating Unit. Example: 204.This is used in checklist step B3.
A6 Payment Terms Create or document the payment terms code to be used for paying AP
Code vouchers coming from ORMB. Example: Net07 (RMBREFUND). This is
used in checklist step D5.
A7 Invoice Source Create the invoice source to be used in Payables Import program
Example: ‟RMB‟ to group all invoices coming from ORMB.
A8 Lookup for Multi- Populate values in INT_RMB_EBS_MORG_SETUPS lookup for Multi-Org
Org setup setup.
Configuration Check List for RMB

B1 GL Division Configure the GL Division(s) to be used in the integration. Example: US1.
This must match the GL Division specified in step C7.


B2 Distribution Codes Configure your distribution codes. See details of required setup in this
document. Example: 01.520.5250.0000.000 with ‘01’ corresponding to
Company, ‘520’ corresponding to Department and so on. See details of
all mapping segments later in this document. This needs to be set up in
sync with the Oracle E-Business Suite Revenue Accounting Flexfield.
B3 Operating Unit Configure a characteristic type to hold the value of the Operating Unit to
Characteristic be used. Example characteristic type: EBSORGID.
Type This is used in checklist step D6. The value you create in this
characteristic (Example: 204) must match what you documented in step
A5.
B4 Create Cancel Create a Cancel Reason code. This must match the Cancel Reason code
Reason Code specified in step E5.
B5 Link the The CIS Division you are using (Example: CA) now has a characteristic
characteristic type type linked to it (Example: EBSORGID) that holds the name of the Org ID
created in step B3 to use (Example: 204).
with the CIS
Division
Configuration Check List for Integration Product (ODI)
Configuration is done in INTEGRATION_LOOKUP_TABLE. Most of these columns receive a default value

as part of the installation of the product. You may choose to override the default as needed.
Note: No user interface exists in this release. Use approved database tools to set column values.
Step INTEGRATION_KEY INTEGRATION_VALUE Comments

C1 RMB.EBS.GL.EMAIL [email protected] Enter the e-mail address to be notified if errors
occur in the GL integration point. Example:
[email protected].
C2 RMB.EBS.GL. 1 For E-Business Suite Release 12, set this to the
LEDGER_ID ID of the ledger to which the journals are to be
created. Example: Vision Operations (USA) (1).
C3 RMB.EBS.GL. RMB EBS This is journal category.
USER_JE_CATEGOR Example: ‘RMB EBS’
Y_NAME
C4 RMB.EBS.GL. RMB EBS This is the Journal Source.
USER_JE_SOURCE_ Example: ‘RMB EBS’
NAME
C5 RMB.EBS.GL. A To create the actual journals.
ACTUAL_FLAG Example: ‟A‟


C6 RMB.EBS.GL.GL_DI US1 or ALL If this value is ALL, then financial transactions
VISION associated with all GL divisions in ORMB are
integrated. If this column has a value, then
only financial transactions associated with this
specific GL Division indicated are integrated.
Examples: US1.
C7 RMB.EBS.GL.JOUR NEW This is Journal Import status.
NAL_IMPORT_STAT
US
C8 EBS.RMB.MAIL_HO Enter the mail host IP address
ST
C9 RMB.EBS.GL.CUST Set this flag ‘Y’ for selecting Custom
OM.TRANS.FLAG transformation flow for GL. Set this to ‘N’ for
selecting the default transformation.
For AP Request Integration Point in ODI

D1 RMB.EBS.APREQUEST Enter the e-mail address to be
.EMAIL notified if errors occur in the AP
Request integration point.
Example: [email protected].
D2 RMB.EBS.APREQUEST 40182 Not used in this release. Do not
.VENDOR_ID change.
D3 RMB.EBS.APREQUEST 7004 Not used in this release. Do not
.VENDOR_SITE_ID change.
D4 RMB.EBS.APREQUEST RMB Invoice Source to use when the
.INVOICE_SOURCE integration creates invoices in E-
Business Suite.
D5 RMB.EBS.APREQUEST 10194 Set to valid ID for Payment terms in
.TERMS_ID E-Business Suite.
D6 RMB.EBS. EBSORGID Characteristic Type to store Oracle
AP.CHAR_TYPE_CD_ E-Business Suite Revenue
ORGID Accounting AP Operating Unit. This
must match what you documented
in step B3. Example: EBSORGID.
D7 RMB.EBS.APREQUEST 204 Valid ID for Organization code in E-
.ORG_ID Business Suite to be used when
integration creates vendors in EBS.


D8 RMB.EBS.APREQUEST CHECK Specifies the payment method for
.PAYMENT_METHOD the invoices created by the
integration. The supported value is
'CHECK'. Do not modify this default
value.
D9 RMB.EBS.RMB.LANG ENG Language to be used in ORMB used
UAGE.CODE to get Adjustment Type Description
D10 RMB.EBS.APREQUEST RMB Specifies the Prepayment reference
.PREPAYMENT_REF source.
D11 RMB.EBS.APREQUEST Refund Request from RMB Default Line description for Invoices
.DEFAULT.LINE.DESC in EBS
RIPTION
D12 RMB.EBS.APREQUEST ADJ_ID The column whose value is suffixed
.VENDOR.NAME.SUF to the vendor name when creating
FIX a supplier in EBS. Possible values
are PER_ID, ACCT_ID, ADJ_ID, SA_ID
and AP_REQ_ID.
D13 RMB.EBS.APREQUEST STANDARD Type of Invoice
.TYPE_OF_INVOICE
D14 RMB.EBS.APREQUEST Set this flag ‘Y’ for selecting Custom
.CUSTOM.TRANS.FLA transformation flow for APREQ. Set
G this to ‘N’ for selecting the default
transformation.
For AP Data Integration Point in ODI

E1 EBS. [email protected] Enter the e-mail address to be notified if
RMB.APDATA.EMAIL errors occur in the AP Data integration point.
E2 EBS.RMB.APDATA.LA 11-02-2008 10:01:01 Last updated time of ODI process run. This is
STRUNDTTM used to determine the payment data to be
extracted and moved across the integration
point. This column is updated by the
integration application each time it is run.
E3 EBS.RMB.APDATA.IN RMB Specifies the Invoice source
VOICE_SOURCE
E4 EBS.RMB.CANCEL.CA APVC Valid cancel reason code to be passed to
NCEL_REASON ORMB when cancelling the adjustment
associated with the AP Request.


E5 EBS.RMB.APDATA.CU Set this flag ‘Y’ for selecting Custom
STOM.TRANS.FLAG transformation flow for APDATA. Set this to
‘N’ for selecting the default transformation.
E6 RMB.EBS.APDATA.W Enter WSDL for calling Webservice. For
EBSERVICE.WSDL example:
http://<Host>:<Port>/spl/XAIApp/xaiserver/C
1AdjustmentMaintenance?WSDL
E7 RMB.EBS.APDATA.W Enter the Response Directory path for
EBSERVICE.RESPDIR webservice Response.
E8 RMB.EBS.APDATA.W Enter the Webservice Response Timeout.
EBSERVICE.RESPTOU
T
E9 RMB.EBS.APDATA.W Enter the application User ID.
EBSERVICE.HTTPUSE
R
E10 RMB.EBS.APDATA.W Enter the Application password encoded
EBSERVICE.HTTPENC using ODI utility.
PWD Go to command prompt and change directory
to the ODI domain home -> \bin. Type
command: encode <password>.
For example:
<ODI_DOMAIN_HOME>\bin>encode
Password The encoded password is generated
as a7yXbeCWoU7d4kOCwvmOu3O2y.
Enter this value in the
INTEGRATION_LOOKUP_TABLE to be used by
ODI to call webservice.
Configuration generic to all integrations for ODI:

F1 RMB.EBS.ADMIN.E [email protected] Enter the from e-mail address if error occurs in
MAIL the integration.
4.1.1 EBS Configuration

Configure the GL accounts (Accounting Flexfield) and other information in Oracle E-Business Suite.
Note: Please refer to your product-specific user documentation regarding steps to configure the GL.

Until the Accounting Flexfield, its respective segments, other GL definitions and settings (Ledger) are
configured in Oracle E-Business Suite, no new settings are required for the GL integration point.

Configure the Payment Terms in EBS
To configure the payment terms follow the steps below:

1. Open Oracle E-Business Suite and navigate to Payables Vision Operations (USA) Responsibility.
Go to Setup > Invoice >Payment.
2. Define the payment terms as per the following table:
Field Label Value

Name Net 07
Description Payment Due after 7 Days
Effective Date From 01-JAN-1990
% Due 100
Days 7
3. Capture the TERMS_ID by navigating to Help->Diagnostics->Examine. Change the Field name to

'TERM_ID'. This value must be specified in Step A6 of the checklist. 0.
Configure the Invoice Source in EBS
To configure the invoice source follow these steps:

1. Open Oracle E-Business Suite and Navigate to Payables Vision Operations (USA) Responsibility.
Go to Setup > Lookups > Payable.
2. Search for lookup type 'SOURCE' and add a new lookup code as follows:
Field Label Value

Code RMB
Meaning Oracle Revenue Management and Billing
Description Oracle Revenue Management and Billing
3. The code value must be specified in Step A7 of the checklist. 0.
Configure the Journal Source in EBS
To configure the journal source follow these steps:

1. Open Oracle E-Business Suite and Navigate to General Ledger, Vision Operations (USA)
Responsibility.
Go to Setup > Journal > Sources

2. Add a new source as follows:
Field Label Value

Source RMB EBS
Source Key RMB EBS
Description RMB EBS Journals
Import Journal References Select the checkbox
3. The source value must be specified in Step A3 of the checklist.0.
Note: Please refer to your Oracle E-Business Suite documentation for further instructions.
Configure the Journal Category in EBS
To configure the journal category follow these steps:
1. Open Oracle E-Business Suite and navigate to General Ledger, Vision Operations (USA)
Responsibility.
Go to Setup > Journal > Categories.
2. Add a new source as follows:
Field Label Value

Category RMB EBS
Category Key RMB EBS
Description Oracle Revenue Management and Billing
3. The category value must be specified in Step A4 of the checklist.0.
Configure the Lookup for Multi-Org setup in EBS
User and responsibility are required to set the Org Context in the pl/sql procedure to create a Supplier
and Site.
To setup the values in the Lookup follow these steps:
1. Open Oracle E-Business Suite and navigate to Applications Developer Responsibility.
Go to Application > Lookups > Common
2. Search for INT_RMB_EBS_MORG_SETUPS Lookup Type.0.
Code Meaning Comments

INT_USER OPERATIONS Provide the User Name
INT_PAYABLES_RESP Payables, Vision Operations (USA) Provide the Payables Responsibility
Name


No configuration is required in Oracle E-Business Suite Revenue Accounting for this integration point.
Standard application tables are used for selecting data from Oracle E-Business Suite Revenue Accounting
to export payment information to ORMB.
4.1.2 ORMB Configuration

To configure the ORMB portion of the integration you must define settings for all three integration
points.
Refer to your user documentation for instructions regarding specific steps in RMB.

To enable this integration point, you must configure the following information in ORMB.
Configure GL Division
If you decide to integrate the financial transactions for a specific GL Division in ORMB to E-Business
Suite, identify the GL Division. This value must be specified in Step C7 of the check list.
Configure Distribution Codes
Map your distribution codes in ORMB to the appropriate GL Accounts in the Oracle E-Business Suite
Revenue Accounting GL. First configure the distribution codes and then assign them to various entities
within ORMB.
The following table shows a sample configuration of one distribution code. Only fields relevant to the
integration are included in this table.
Field Label Value Comments

Distribution Code Example: R-ELERES The distribution code to be used for financial
transactions of a certain type.
Description Example: Electric A description of how the distribution code is used.
residential revenue
GL Account GLCNST-DFLT The standard product, or customer modified, algorithm
Algorithm you use for determining the GL Account String from the
distribution code.
GL Account 1 of 1 Create at least one set of account details as needed by
Details the algorithm chosen above. Only one set of account is
used based on the status and effective date.
Effective Date 01-01-1900 The date you need to make the following GL Account
string active to be used by the system, and therefore
the integration software.
Status Active Only active status accounts are used by the product and
therefore by the integration.


GL Account 01.520.5250.0000.000 Input the GL Account String as explained below.
The distribution code links the GL Account to activities. As in the example above, a bill payment receives
the code R-ELERES so that this revenue for electric residential service is applied to the account
01.520.5250.0000.000.The algorithm GLCNST-DFLT provides the hook which allows the integration to
get the GL Account from the distribution code and recognize it in Oracle E-Business Suite to the correct
GL Journal entry.
GL Account String
Oracle E-Business Suite Revenue Accounting GL accounts are structured using account segments. These
are set up in your existing Oracle E-Business Suite Revenue Accounting system according to the business
practices.
The ORMB GL Account positions must be configured to mirror the segments & values in Oracle E-
Business Suite Revenue Accounting. The segment positions are fixed in ORMB so that the first segment
is Company, the second segment is Department ID, and so on, as shown in the following table.
Oracle E-Business Suite Revenue Accounting ORMB Distribution (GL_ACCT ) segment position
Account Column name
Company Position1
Department Position 2
Account Position 3
Sub-Account Position 4
Product Position 5
As the segments are configured, separate each segment with a dot (.).
Example
A sample GL Account string is 01.520.5250.0000.000
When interpreted by the standard mapping in the product, this GL Account String in the sub ledger
equates to the following in the EBS GL:
• Company - 01
• Department - 520
• Account - 5250
• Sub-Account - 0000
• Product -000
Please refer to the data mapping table for details on how the segments must be mapped.

Configure GLASSIGN, and GLS for ORMB Extract
To successfully execute extracts from ORMB, two processes must be configured with the appropriate
batch parameters and set to run on a scheduled basis. These processes can be scheduled using the
ORMB scheduling tool or an enterprise scheduler that meets the open architecture standards used by
ORMB.
Configure the Accounting Entry Template Characteristic Type
For each CIS Division used in ORMB, you must configure a characteristic value to have the AP Operating
Unit to be used in Oracle E-Business Suite Revenue Accounting GL.
Complete the following configuration in ORMB to reference the AP Operating Unit corresponding to the
CIS Division as follows.
1. Create a Characteristic Type.
Admin Menu > C > Characteristic Type
The value for this characteristic type stores the value of the Oracle E-Business Suite Revenue Accounting
Org ID. In this example it is EBSORGID. Add the Org ID of Oracle E-Business Suite Revenue Accounting as
a characteristic value.
2. Set up the details on the characteristic type as follows:
Characteristic Type EBSORGID The code associated with the characteristic
type. This will be used in future steps.
Description EBS Org ID A description of the use for this
characteristic type.
Type of Char Value Predefined Value No freeform text is allowed, only a
predefined set of values.
Allow Search by Allowed Allow searches
Char Val
Characteristic 204 The name of the Oracle E-Business Suite
Value Revenue Accounting Org ID to be used.
Description Oracle E-Business Suite
Operating Unit
3. Select the Characteristic Entities tab to allow the characteristic type to be associated with the
Distribution Code:

Characteristic Division This characteristic type can be inserted on a
Entity CIS Division.

4. Attach the Characteristic Type, created above, to any Divisions that are used for AP Request
Adjustments. In sample data an example is provided as the CA - CIS Division.0.
Admin Menu > D > Division

Division Example: CA The Division to be used.
Description Example: California A description of how the Division is used.
Characteristic tab
Effective Date Example: 01-01-1900 The date you wish the characteristic type
and value to become active and used by the
system, and therefore the integration
software.
Characteristic Type Oracle E-Business Suite The characteristic type you created above.
Revenue Accounting Org
ID
Characteristic Example: 204 The value you gave to the characteristic type
Value created
Note: Only fields relevant to the integration are included in this table.

No ORMB configuration is required to enable this integration point.
AP payment data is extracted from Oracle E-Business Suite Financials when an AP Request invoice is
paid. This data is then translated by ODI and inserted into the ORMB AP Request that initiated the
invoice.
ODI invokes the ORMB service, named C1AdjustmentMaintenance, when a payment is canceled in
Oracle E- Business Suite Revenue Accounting General Ledger and Accounts Payable. The service uses the
cancel reason contained in its configuration when canceling the adjustment associated with an AP
Request. The sample data cancel reason is pre-configured as “APVC” (Accounts Payable Void Check) in
ORMB version 2.2 and later.
You should verify that the cancel service C1AdjustmentMaintenance is configured and the Cancel
Reason to which it refers is also configured correctly.
Admin Menu > X > XAI Inbound Service

XAI In Service Adjustment Maintenance This service is used to change data
Name associated with adjustment transactions.
Description Adjustment Maintenance
for AP Cancel


Long Description Adjustment Maintenance
for AP Cancel
Active Checked Active check box checked.
Request Schema C1AdjustmentMaintenan Used by ODI to call this service.
ce.xsd
Response Schema C1AdjustmentMaintenan Used by ODI to receive the response from
ce.xsd this
Transaction Type Update Service used to update an existing
adjustment transaction.
You can test this service using XAI Dynamic Submission as follows:
Admin Menu > X > XAI Dynamic Submission

XAI In Service AdjustmentMaintenance This service is used to change data
Name associated with adjustment transactions.
Transaction Type Update
Cancel Checked Cancel check box checked.
Adjustment ID Example: 078644601179 The key value of the adjustment for which
you wish to test the cancel service.
Cancel Reason Example: APVC AP Void Check cancel reason. This must be
configured as a cancel reason.
Click Submit and review the results.

5. Verifying the Integration

Best practice to verify the implementation is to start each application individually then manually run the
integration points.
5.1.1 GL Integration Point

1. Identify Financial Transactions in CI_FT table to be sent to Oracle E-Business Suite Revenue
Accounting GL for creating Journal Entries. If needed, generate a bill, adjustment or payment event
to create financial transactions.
2. Run the GLASSIGN process to assign the Account Number to the FT in CI_FT.
3. Run the GLS process to mark the FTs in the CI_FT table for download. The staging process for
creating a GL download (GLS) creates a staging record for every financial transaction that is ready for
download. This process populates the FT / Batch Process table with the unique ID of all financial
transactions to be interfaced to the GL. This process marks each staging record with the batch
process ID (defined on the installation record) for the GL interface. It also stamps the current run
number for the respective batch control record.
4. Run the GLS process. Invoke the GL Integration Point process from ODI or wait for its next run to
occur. The package should do the following:
• Select the FT in the CI_FT table based on the batch code and the run number provided to it by
ODI
• Extract and group (summarize) the Financial Transactions (FT) and push them into ODI.
• After extracting the FT, increment the NEXT _BATCH_NBR in the CI_BATCH_CTL table.
• Data is transformed by the ODI process and written to the GL journal staging table in the Oracle
E-Business Suite Revenue Accounting General Ledger and Accounts Payable.
5. Use the Oracle E-Business Suite GL Journal import process to load the GL data into the Oracle E-
Business Suite Revenue Accounting GL base tables.0.
5.1.2 A/P Request Integration Point

1. Create an A/P Request for a refund customer in ORMB. You will need to generate an adjustment of
the appropriate type to do this.
2. Invoke the ODI Integration Point Process to extract the A/P Request Information, and the
corresponding customer information from ORMB, transform it, and load it into Oracle E-Business
Suite Revenue Accounting General Ledger and Accounts Payable A/P Invoice Interface tables.
3. Run the Payables Open Interface Import (APXIIMPT) in Oracle E-Business Suite Revenue Accounting
to create Invoices from the A/P Check Request and Customer data that is staged in the Invoice
Interface tables.0.
5.1.3 A/P Data Integration Point

1. Generate a payment in Oracle E-Business Suite Revenue Accounting Payables for an Invoice created
by the ORMB A/P Request process above.
2. Invoke the ODI Integration Point process to update the A/P Check Request table (CI_ADJ_APREQ)
with the payment information from Oracle E-Business Suite Revenue Accounting.

3. If you wish to further test a cancellation of payment functionality, cancel the payment made above
in Oracle E-Business Suite Revenue Accounting Payables.
4. Invoke the ODI Process Manager process to update the A/P Check Request table (CI_ADJ_APREQ)
with the Payment Information from Oracle E-Business Suite Revenue Accounting. This cancels the
A/P Request and the adjustment.0.

6. Running ODI Process Flows

The ODI artifacts are run as scenarios in the production environments. Scenarios can be scheduled
based on the frequency of transformation of particular flows. Other options to run scenarios are
through the ODI console or through command prompt. Refer to the ODI documentation for information
on scenarios in ODI. Executing the scenarios will transform the data for EBS and populate the requisite
interface tables.
6.1.1 GL Request
Execute the following scenario for GL Request. Based on the customization flags, respective scenarios
will be invoked from the following master scenario.
Scenario to execute EBS_MASTER_GL_PKG Version 001
6.1.2 AP Request
Execute the following scenario for AP Request. Based on the customization flags, respective scenarios
will be invoked from the following master scenario.
Scenario to execute EBS_MASTER_APREQ_PKG Version 001
6.1.3 AP Data Request

Execute the following scenario for AP data Request. Based on the customization flags, respective
scenarios will be invoked from the following master scenario.
Scenario to execute EBS_MASTER_APDATA_PKG Version 001

7. Available Extension Points in ODI

7.1.1 GL Extension Point
When the ODI process customization point needs to be invoked, ensure that the transaction flag on the
Custom ODI component is set to ‘Y’ for each of the flows in the integration lookup table. For GL Request,
RMB.EBS.GL.CUSTOM.TRANS.FLAG key should be set to ‘Y’.
Base transformation implementation is copied as custom transformation interface with the shipped
product. The implementation team can modify the custom transformation to include additional
mappings. For the complete flow understanding of the base ODI package in terms of the
procedures/interfaces/packages used, refer the User interface for ODI which provides diagrammatic
representation for the ODI packages.
The custom transformation is used to map elements coming from the GL/FT tables in Oracle RMB to
fields in the GL_INTERFACE table in EBS that are still unmapped.
Package where extensibility can be done EBS_CUSTOM_GL_PKG

Interface where extensibility can be done CUSTOM_GL_INTERFACE,
EBS_CUSTOM_GL_TEMP_INTERFACE
7.1.2 AP Request Extension Point

When the ODI process customization point needs to be invoked, make sure that the transaction flag on
the Custom ODI component is set to “Y” for each of the flows in the integration lookup table. For AP
Request, RMB.EBS.APREQUEST.CUSTOM.TRANS.FLAG key should be set to ‘Y’.
The custom transformation is used to map elements from the Adjustment A/P Request tables in ORMB
to fields in the Oracle E-Business Suite Invoice Interface tables that are still unmapped.
Package where extensibility can be done EBS_CUSTOM_APREQ_PKG

Interface where extensibility can be done CUSTOM_AP_INVOICES_INTERFACE,
CUSTOM_AP_LINES_INTERFACE

7.1.3 AP Data Extension Point

When the ODI process customization point needs to be invoked, ensure that the transaction flag on the
Custom ODI component is set to “Y” for each of the flows in the integration lookup table. For AP Data,
EBS.RMB.APDATA.CUSTOM.TRANS.FLAG key should be set to ‘Y’.
The custom transformation is used to map elements coming from the Oracle E-Business Suite table to
fields in the ORMB Adjustment A/P Request table that are still unmapped.
Package where extensibility can be done EBS_CUSTOM_APDATA_PKG

Interface where extensibility can be done CUSTOM_AP_DATA_INTERFACE ,
AP_DATA_TEMP_FRM_PAYMENTS_ALL
Note: Post all customization changes regenerate the scenarios for the changes to reflect.

8. Appendix: A
8.1 EBS Data Mapping
The following sections show the fields that are mapped for the integration for EBS.
8.1.1 GL Transaction
8.1.1.1 EBS GL Table Mapping to ORMB
Column Data Description ORMB Column Data Type Remarks
Type Table
STATUS VARCHA Journal Import status (Required field) ‘NEW’, for all new
R2 (50) transactions
LEDGER_I NUMBER Ledger defining column Derived from ODI
D (Release Identifies the EBS to use
12) for posting Value = 1
(Corresponds to ‘Vision
Operations (USA) ’ Ledger
Name)
ACCOUNTI DATE Effective CI_FT ACCOUN DATE Date used by GL to define
NG_DATE date of the TING_DT the accounting period
transaction into which the Financial
(Required) Transaction is booked.
CURRENC VARCHA Currency CI_FT CURREN CHAR (3)
Y_CODE R2 (15) (Required) CY_CD
DATE_CRE DATE Standard Who column (Required) Derived from ODI Value
ATED =sysdate
CREATED_ NUMBER Standard Who column (Required) Value= -1
BY
ACTUAL_F VARCHA Balance type (actual, budget, or ‘A’
LAG R2 (1) encumbrance)(Required)
USER_JE_ VARCHA Journal entry category user defined name ‘RMB EBS’
CATEGOR R2 (25) (Required)
Y_NAME
USER_JE_ VARCHA Journal entry source user defined name ‘RMB EBS’
SOURCE_ R2 (25) (Required)
NAME


Type Table
CURRENC DATE Date of exchange rate
Y_CONVE
RSION_DA
TE
ENCUMBR NUMBER Encumbrance type defining column
ANCE_TYP
E_ID
Leave blank
BUDGET_ NUMBER Budget version defining column
VERSION_
ID
USER_CU VARCHA Type of exchange rate
RRENCY_C R2 (30)
ONVERSIO
N_TYPE
CURRENC NUMBER Foreign currency exchange rate
Y_CONVE
RSION_RA
TE
AVERAGE VARCHA Average journal flag
Leave blank
_JOURNAL R2 (1)
_FLAG
ORIGINATI VARCHA Originating balancing segment value
NG_BAL_S R2 (25)
EG_VALUE
SEGMENT VARCHA COMPANY CI_FT_ GL_ACCT Varchar2
1 R2 (25) GL Position1 (254)
SEGMENT VARCHA DEPARTME CI_FT_ GL_ACCT Varchar2
2 R2 (25) NT GL Position (254)
2
Use dot (.) as the
SEGMENT VARCHA ACCOUNT CI_FT_ GL_ACCT Varchar2
delimiter to extract this
3 R2 (25) GL Position (254)
information from the
3
Gl_Acct. 2 dots (..)
SEGMENT VARCHA SUB- CI_FT_ GL_ACCT Varchar2 indicate skip or null.
4 R2 (25) ACCOUNT GL Position (254)
4
SEGMENT VARCHA PRODUCT CI_FT_ GL_ACCT Varchar2
5


Type Table
SEGMENT VARCHA PROGRAM CI_FT_ GL_ACCT Varchar2
6 R2 (25) CODE GL Position (254)
6
SEGMENT VARCHA ALTERNATE CI_FT_ GL_ACCT Varchar2
7 R2 (25) ACCOUNT GL Position (254)
7
SEGMENT VARCHA PROJECT CI_FT_ GL_ACCT Varchar2
8
SEGMENT VARCHA AFFILIATE CI_FT_ GL_ACCT Varchar2
9
SEGMENT VARCHA FUND CI_FT_ GL_ACCT Varchar2
10 R2 (25) AFFILIATE GL Position (254)
10
SEGMENT VARCHA OPERATING CI_FT_ GL_ACCT Varchar2
11 R2 (25) UNIT GL Position (254)
AFFILIATE 11
SEGMENT VARCHA BUDGET CI_FT_ GL_ACCT Varchar2
12 R2 (25) REFERENCE GL Position (254)
12
SEGMENT VARCHA CHARTFIELD CI_FT_ GL_ACCT Varchar2
13 R2 (25) 1 GL Position (254)
13
14 R2 (25) 2 GL Position (254)
14
15 R2 (25) 3 GL Position (254)
15
SEGMENT VARCHA FUND CODE CI_DST FUND_C Varchar2 Only used when fund
16 R2 (25) _CODE D (12) accounting is enabled in
_EFF ORMB.
SEGMENT VARCHA
17 R2 (25) Derived from ODI Leave
Key flexfield segments
SEGMENT VARCHA blank
18 R2 (25)


Type Table
SEGMENT VARCHA
19 R2 (25)
SEGMENT VARCHA
20 R2 (25)
SEGMENT VARCHA
21 R2 (25)
SEGMENT VARCHA
22 R2 (25)
SEGMENT VARCHA
23 R2 (25)
SEGMENT VARCHA
24 R2 (25)
SEGMENT VARCHA
25 R2 (25)
SEGMENT VARCHA
26 R2 (25)
SEGMENT VARCHA
27 R2 (25)
SEGMENT VARCHA
28 R2 (25)
SEGMENT VARCHA
29 R2 (25)
SEGMENT VARCHA
30 R2 (25)
ENTERED_ NUMBER Base Currency Amount
DR Leave blank if the
Base Base Amount is negative
Currency Currency
ENTERED_ NUMBER Leave Leave it Leave blank if the amount
Amount Amount
CR blank if Bank if is positive
Leave Leave
the the
ACCOUNT NUMBER blank if blank if
amount is Amount is Base Currency Amount
ED_DR the the Leave blank if the
positive Positive
Amount is Amount is Amount is negative
negative negative
ACCOUNT NUMBER Leave it Bank if the
ED_CR Amount is Positive
TRANSACT DATE Date of transaction Leave blank
ION_DATE


Type Table
PERIOD_N VARCHA Accounting period Leave blank
AME R2 (15)
REFERENC VARCHA
E1 R2 (100)
REFERENC VARCHA
E2 R2 (240)
REFERENC VARCHA
E3 R2 (100)
REFERENC VARCHA
E4 R2 (100)
REFERENC VARCHA
E5 R2 (240)
REFERENC VARCHA
E6 R2 (100)
REFERENC VARCHA
E7 R2 (100)
REFERENC VARCHA
E8 R2 (100)
REFERENC VARCHA
Journal Import reference columns Leave blank
E9 R2 (100)
REFERENC VARCHA
E10 R2 (240)
REFERENC VARCHA
E11 R2 (240)
REFERENC VARCHA
E12 R2 (100)
REFERENC VARCHA
E13 R2 (100)
REFERENC VARCHA
E14 R2 (100)
REFERENC VARCHA
E15 R2 (100)
REFERENC VARCHA
E16 R2 (100)
REFERENC VARCHA
E17 R2 (100)


Type Table
REFERENC VARCHA
E18 R2 (100)
REFERENC VARCHA
E19 R2 (100)
REFERENC VARCHA
E20 R2 (100)
REFERENC VARCHA
E21 R2 (240)
REFERENC VARCHA
E22 R2 (240)
REFERENC VARCHA
E23 R2 (240)
REFERENC VARCHA
E24 R2 (240)
REFERENC VARCHA
E25 R2 (240)
REFERENC VARCHA
E26 R2 (240)
REFERENC VARCHA
E27 R2 (240)
REFERENC VARCHA
E28 R2 (240)
REFERENC VARCHA
E29 R2 (240)
REFERENC VARCHA
E30 R2 (240)
JE_BATCH NUMBER Journal entry batch defining column Leave blank.
_ID Populated by the Import
Process when the Record
errors
JE_HEADE NUMBER Journal entry header defining column Leave blank
R_ID Populated by the Import
errors


Type Table
JE_LINE_N NUMBER Journal entry line number Leave blank
UM Populated by the Import
errors
CHART_O NUMBER Key flexfield structure defining column Leave blank
F_ACCOU
NTS_ID
FUNCTION VARCHA Ledger base currency Leave blank
AL_CURRE R2 (15)
NCY_COD
E
CODE_CO NUMBER Key flexfield combination defining column Derived from the
MBINATIO Segments Entered Above
N_ID
DATE_CRE DATE Date Journal Import created batch Leave blank
ATED_IN_
GL
STATUS_D VARCHA Journal import status description Leave blank Populated by
ESCRIPTIO R2 (240) the Import Process when
N the Record errors
STAT_AM NUMBER Statistical Leave blank
OUNT amount
GROUP_I NUMBER Interface CI_FT_PR BATCH_N NUMBER This is the ORMB GLDL
D group OC BR (10) Batch Number.
defining
column
REQUEST_ NUMBER Concurrent program request ID Leave blank
ID Populated by the Import
errors
SUBLEDGE NUMBER Sequential numbering sequence defining column
R_DOC_SE
QUENCE_I
D
Leave blank
SUBLEDGE NUMBER Sequential numbering sequence value
R_DOC_SE
QUENCE_
VALUE


Type Table
ATTRIBUT VARCHA Descriptive flexfield segment
E1 R2 (150)
ATTRIBUT VARCHA Descriptive flexfield segment
E2 R2 (150)
GL_SL_LIN NUMBER Link to associated subledger data
K_ID
GL_SL_LIN VARCHA Table containing associated subledger data
K_TABLE R2 (30)
CONTEXT VARCHA Descriptive flexfield context column
R2 (150)
CONTEXT2 VARCHA Descriptive flexfield context column
R2 (150)
INVOICE_ DATE Value added tax descriptive flexfield column
DATE
TAX_COD VARCHA Value added tax descriptive flexfield column
E R2 (15)
INVOICE_I VARCHA Value added tax descriptive flexfield column
DENTIFIER R2 (20)
ATTRIBUT VARCHA Descriptive flexfield segment Leave Blank
E3 R2 (150)
ATTRIBUT VARCHA
E4 R2 (150)
ATTRIBUT VARCHA
E5 R2 (150)
ATTRIBUT VARCHA
E6 R2 (150)
ATTRIBUT VARCHA
E7 R2 (150)
ATTRIBUT VARCHA
E8 R2 (150)
ATTRIBUT VARCHA
E9 R2 (150)
ATTRIBUT VARCHA
E10 R2 (150)
ATTRIBUT VARCHA
E11 R2 (150)


Type Table
ATTRIBUT VARCHA
E12 R2 (150)
ATTRIBUT VARCHA
E13 R2 (150)
ATTRIBUT VARCHA
E14 R2 (150)
ATTRIBUT VARCHA
E15 R2 (150)
ATTRIBUT VARCHA
E16 R2 (150)
ATTRIBUT VARCHA
E17 R2 (150)
ATTRIBUT VARCHA
E18 R2 (150)
ATTRIBUT VARCHA
E19 R2 (150)
ATTRIBUT VARCHA
E20 R2 (150)
INVOICE_ NUMBER Value added tax descriptive flexfield column Leave blank
AMOUNT
CONTEXT3 VARCHA Descriptive flexfield context column Leave blank
R2 (150)
USSGL_TR VARCHA Government transaction code
ANSACTIO R2 (30)
N_CODE
DESCR_FL VARCHA Descriptive flexfield error message
EX_ERROR R2 (240)
_MESSAG
E
Leave blank
JGZZ_REC VARCHA Global reconciliation reference
ON_REF R2 (240)
REFERENC DATE Reference Date
E_DATE
SET_OF_B NUMBER Ledger defining column
OOKS_ID


Type Table
BALANCIN VARCHA Balancing segment value
G_SEGME R2 (25)
NT_VALUE
MANAGE VARCHA Management segment value
MENT_SE R2 (25)
GMENT_V
ALUE
FUNDS_R VARCHA Reserved for Oracle internal use
ESERVED_ R2 (1)
FLAG
8.1.2 A/P Request

8.1.2.1 AP_INVOICES_INTERFACE
Columns Data Type Description ORMB Column Data Type Remarks
Table
INVOICE_ID Number Invoice identifier AP_INVOICE
S_interface_
S.nextval
INVOICE_N VARCHAR2 Invoice CI_ADJ ADJ_ID CHAR (12)
UM (50) number
INVOICE_TY VARCHAR2 Type of Invoice (can be STANDARD or CREDIT) ‘STANDARD’
PE_LOOKUP (25)
_CODE
INVOICE_DA DATE Invoice date CI_ADJ CRE_DT DATE
TE
PO_NUMBE VARCHAR2 Purchase order number Leave blank
R (20)
VENDOR_ID NUMBER Supplier identifier Example
(15) Validated against PO_VENDORS.VENDOR_ID Value
=40182 Set
to the ID of
the vendor
created by
this
integration
point.
VENDOR_N VARCHAR2 Supplier number Leave blank
UM (30)


Table
VENDOR_N VARCHAR2 Supplier name Leave blank
AME (240)
VENDOR_SI NUMBER Supplier site identifier. Validated against Example
TE_ID (15,0) PO_VENDOR_SITES_ALL.VENDOR_SITE_ID Value =7004
Set to the ID
of the
vendor site
created by
this
integration
point.
VENDOR_SI VARCHAR2 Supplier site code Leave blank
TE_CODE (15)
INVOICE_A NUMBER Invoice CI_ADJ ADJ_AMT Number
MOUNT amount (15,2)
INVOICE_CU VARCHAR2 Currency of invoice. Validated against Leave blank
RRENCY_CO (15) FND_CURRENCIES.CURRENCY_CODE
DE
EXCHANGE_ NUMBER Exchange rate for foreign currency invoices Leave blank
RATE
EXCHANGE_ VARCHAR2 Exchange rate type for foreign currency invoices. Leave blank
RATE_TYPE (30) Validated against
GL_DAILY_CONVERSION_TYPES.CONVERSION_TYPE
EXCHANGE_ DATE Date exchange rate is effective, usually accounting date Leave blank
DATE of a transaction
TERMS_ID NUMBER Payment terms identifier. Validated against Derived
(15,0) AP_TERMS_TL.TERM_ID from ODI
Value =
10194Confi
guration
parameter
TERMS_NA VARCHAR2 Payment terms name Leave blank
ME (50)
DESCRIPTIO VARCHAR2 Invoice CI_ADJ_APR ENTITY_NA VARCHAR2
N (240) description EQ ME|CITY|C (240)
OUNTRY|A
DDRESS1|C
OUNTY|
STATE|
POSTAL


Table
AWT_GROU NUMBER Withholding tax group identifier. Validated against Leave blank
P_ID (15,0) AP_AWT_GROUPS.AWT_GROUP_ID
AWT_GROU VARCHAR2 Withholding tax group name Leave blank
P_NAME (25)
LAST_UPDA DATE Standard Who column - date when a user last updated Sysdate
TE_DATE this row.
LAST_UPDA NUMBER Standard who column - user who last updated this row Leave blank
TED_BY (15,0) (foreign key to FND_USER.USER_ID).
LAST_UPDA NUMBER Standard who column - operating system login of user Leave blank
TE_LOGIN (15,0) who last updated this row (foreign key to
FND_LOGINS.LOGIN_ID).
CREATION_ DATE Standard who column - date when this row was created Sysdate
DATE
CREATED_B NUMBER Standard who column - user who created this row Leave blank
Y (15,0) (foreign key to FND_USER.USER_ID).
ATTRIBUTE_ VARCHAR2 Descriptive flexfield structure definition column. Leave blank
CATEGORY (150)
ATTRIBUTE1 VARCHAR2
(150)
ATTRIBUTE2 VARCHAR2
(150)
ATTRIBUTE3 VARCHAR2
(150)
ATTRIBUTE4 VARCHAR2
(150)
ATTRIBUTE5 VARCHAR2
(150)
Descriptive flexfield segment Leave blank
ATTRIBUTE6 VARCHAR2
(150)
ATTRIBUTE7 VARCHAR2
(150)
ATTRIBUTE8 VARCHAR2
(150)
ATTRIBUTE9 VARCHAR2
(150)
ATTRIBUTE1 VARCHAR2
0 (150)


Table
ATTRIBUTE1 VARCHAR2
1 (150)
ATTRIBUTE1 VARCHAR2
2 (150)
ATTRIBUTE1 VARCHAR2
3 (150)
ATTRIBUTE1 VARCHAR2
4 (150)
ATTRIBUTE1 VARCHAR2 CI_ADJ_APR
5 (Release (150) EQ.
11.5.10) AP_REQ_ID
GLOBAL_AT VARCHAR2
TRIBUTE_CA (150)
TEGORY
GLOBAL_AT VARCHAR2
TRIBUTE1 (150)
GLOBAL_AT VARCHAR2
TRIBUTE2 (150)
GLOBAL_AT VARCHAR2
TRIBUTE3 (150)
GLOBAL_AT VARCHAR2
TRIBUTE4 (150)
GLOBAL_AT VARCHAR2
TRIBUTE5 (150) Reserved for country-specific functionality Leave Blank
GLOBAL_AT VARCHAR2
TRIBUTE6 (150)
GLOBAL_AT VARCHAR2
TRIBUTE7 (150)
GLOBAL_AT VARCHAR2
TRIBUTE8 (150)
GLOBAL_AT VARCHAR2
TRIBUTE9 (150)
GLOBAL_AT VARCHAR2
TRIBUTE10 (150)
GLOBAL_AT VARCHAR2
TRIBUTE11 (150)


Table
GLOBAL_AT VARCHAR2
TRIBUTE12 (150)
GLOBAL_AT VARCHAR2
TRIBUTE13 (150)
GLOBAL_AT VARCHAR2
TRIBUTE14 (150)
GLOBAL_AT VARCHAR2
TRIBUTE15 (150)
GLOBAL_AT VARCHAR2
TRIBUTE16 (150)
GLOBAL_AT VARCHAR2
TRIBUTE17 (150)
Reserved for country-specific functionality Leave Blank
GLOBAL_AT VARCHAR2
TRIBUTE18 (150)
GLOBAL_AT VARCHAR2
TRIBUTE19 (150)
GLOBAL_AT VARCHAR2
TRIBUTE20 (150)
STATUS VARCHAR2 Status of the data in or after the Payables Open Interface Import
(25) Import Process
inserts
Value =
PROCESSED
/REJECTED
SOURCE VARCHAR2 Prepayment Reference Derived
(80) from ODI
Value =
‘RMB’
GROUP_ID VARCHAR2 Group identifier Leave blank
(80)
REQUEST_I NUMBER Concurrent Program who column - concurrent request id Leave blank
D of the program that last updated this row (foreign key to
FND_CONCURRENT_REQUESTS.REQUEST_ID).
PAYMENT_C VARCHAR2 Cross currency payment rate type (must be EMU Fixed in Leave blank
ROSS_RATE (30) Release 11)
_TYPE


Table
PAYMENT_C DATE Cross currency payment rate date Leave blank
ROSS_RATE
_DATE
PAYMENT_C NUMBER Exchange rate between invoice and payment; in Release Leave blank
ROSS_RATE 11 the value is always 1 unless they are associated fixed-
rate currencies
PAYMENT_C VARCHAR2 Cross currency payment currency. Validated against Leave blank
URRENCY_C (15) FND_CURRENCIES.CURRENCY_CODE
ODE
WORKFLOW VARCHAR2 Flag that indicates if the Payables Open Interface Leave blank
_FLAG (1) Workflow must process the record (Y or N)
DOC_CATEG VARCHAR2 Sequential numbering (voucher number) document Leave blank
ORY_CODE (30) category. Validated against
FND_DOC_SEQUENCE_CATEGORIES.CODE
VOUCHER_ VARCHAR2 Voucher number; validated (Sequential Numbering Leave blank
NUM (50) enabled), or non-validated (Sequential Numbering not
enabled)
PAYMENT_ VARCHAR2 Name of the payment method Leave blank
METHOD_L (25)
OOKUP_CO
DE
PAY_GROUP VARCHAR2 Name of the pay group Leave blank
_LOOKUP_C (25)
ODE
GOODS_REC DATE Date invoice items received Leave blank
EIVED_DATE
INVOICE_RE DATE Date invoice received Leave blank
CEIVED_DA
TE
GL_DATE DATE Accounting date to default to invoice distributions Derived
from ODI
Leave blank
ACCTS_PAY NUMBER Accounting Flexfield identifier for A/P liability account. Leave blank
_CODE_CO (15,0) Validated against
MBINATION GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
_ID


Table
USSGL_TRA VARCHAR2 Default transaction code for creating US Standard GL Leave blank
NSACTION_ (30) journal entries (Oracle Public Sector Payables). Validated
CODE against
GL_USSGL_TRANSACTION_CODES.USSGL_TRANSACTION
_CODE
EXCLUSIVE_ VARCHAR2 Flag that indicates whether to pay invoice on a separate Leave blank
PAYMENT_F (1) payment document
LAG
AMOUNT_A NUMBER Amount of invoice applicable to a discount Leave blank
PPLICABLE_
TO_DISCOU
NT
PREPAY_NU VARCHAR2 The invoice number of an existing, fully paid prepayment Leave blank
M (50) to be applied to the imported invoice
PREPAY_DIS NUMBER No longer Leave blank
T_NUM (15,0) used
PREPAY_AP NUMBER The amount of prepayment that the user wants to apply Leave blank
PLY_AMOU to the invoice. This amount should be positive.
NT
PREPAY_GL DATE The accounting date to be used for the prepayment Leave blank
_DATE application. If left null, the invoices GL_DATE is used
INVOICE_IN VARCHAR2 Prorate Leave blank
CLUDES_PR (1) Discount
EPAY_FLAG
NO_XRATE_ NUMBER Invoice amount in the functional currency. Used only Leave blank
BASE_AMO when the Calculate User Exchange Rate option is
UNT enabled, and used only for foreign currency invoices
when the exchange rate type is User. The system uses
this value and the invoice amount to calculate the
exchange rate.
VENDOR_E VARCHAR2 Supplier e-mail address for XML invoice rejections Leave blank
MAIL_ADDR (2000)
ESS
TERMS_DAT DATE Date used with payment terms to calculate scheduled Leave blank
E payment of an invoice
REQUESTER NUMBER Requester of invoice is used by the Invoice Approval Leave blank
_ID (10,0) Workflow process to generate the list of approvers
SHIP_TO_LO VARCHAR2 Ship to location for purchase order matching. Used for Leave blank
CATION (40) XML invoices


Table
EXTERNAL_ VARCHAR2 Internal document reference number from Accounts Leave blank
DOC_REF (240) Receivables system. Used for XML invoices
PREPAY_LIN NUMBER The invoice line of an existing Prepayment to be applied Leave blank
E_NUM to the imported invoice
REQUESTER VARCHAR2 The first name of the employee who requested goods or Leave blank
_FIRST_NA (150) services on the invoice line. This value is used to derive
ME the requester ID. If you use Invoice Approval Workflow
then you can define rules that use the requester ID to
generate a hierarchical list of approvers for the line
REQUESTER VARCHAR2 The last name of the employee who requested goods or Leave blank
_LAST_NAM (150) services on the invoice line. This value is used to derive
E the requester ID. If you use Invoice Approval Workflow
APPLICATIO NUMBER Application Leave blank
N_ID (15,0) Identifier
PRODUCT_T VARCHAR2 Product Leave blank
ABLE (30) source table
name
REFERENCE VARCHAR2
_KEY1 (150)
REFERENCE VARCHAR2
_KEY2 (150)
REFERENCE VARCHAR2 Primary key information that uniquely identifies a record
Leave blank
_KEY3 (150 in other products view.
REFERENCE VARCHAR2
_KEY4 (150)
REFERENCE VARCHAR2
_KEY5 (150)
APPLY_ADV VARCHAR2 A value of Y indicates that applicable advances are Leave blank
ANCES_FLA (1) applied against expense reports and other invoices.
G
CALC_TAX_ VARCHAR2 Indicates whether tax must be calculated for the Leave blank
DURING_IM (1) imported invoice.
PORT_FLAG
CONTROL_A NUMBER Allows user to enter total tax amount to be prorated by Leave blank
MOUNT E-Business Tax.


Table
ADD_TAX_T VARCHAR2 Indicates whether the invoice amount must be grossed Leave blank
O_INV_AMT (1) up by the calculated tax.
_FLAG
TAX_RELATE NUMBER Tax Driver: Invoice ID of related document for tax Leave blank
D_INVOICE_ (15,0) purposes.
ID
TAXATION_ VARCHAR2 Replaces a GDFF: This country sets the context for other Leave blank
COUNTRY (30) tax drivers. The value defaults to the LE country but can
be overridden by the user
DOCUMENT VARCHAR2 Replaces a GDFF: In certain countries, a tax or Leave blank
_SUB_TYPE (150) governmental authority defines and classifies document
types for reporting purposes
SUPPLIER_T VARCHAR2 Replaces a GDFF: In some countries such as Thailand, Leave blank
AX_INVOICE (150) there is a requirement to report on a supplier issued
_NUMBER "tax" invoice that is distinct from the regular invoice. The
tax invoice is either attached to the standard Supplier
Invoice (when the value = Goods); or, the supplier may
issue it when he receives the payment.
SUPPLIER_T DATE Replaces a GDFF: To satisfy reporting requirements in Leave blank
AX_INVOICE certain countries, the Tax Invoice Date on the supplier-
_DATE issued tax invoice needs to be recorded.
SUPPLIER_T NUMBER Replaces a GDFF: The supplier exchange rate is entered Leave blank
AX_EXCHAN in online invoices to calculate the supplier tax amount for
GE_RATE foreign currency invoices. The gain/loss in the tax
amount for foreign currency invoices is the difference
between the in-house tax amount using the in-house
exchange rate and the supplier tax amount using the
supplier exchange rate provided. A manual journal entry
is posted to the GL to incorporate the gain/loss.
TAX_INVOIC DATE Replaces a GDFF: To satisfy reporting requirements in Leave blank
E_RECORDI certain countries, the company-specific Tax Invoice Date
NG_DATE and Number needs to be captured. This field is used to
record the date the company receives/ records the
supplier-issued tax invoice and is required to comply with
reporting requirements.
TAX_INVOIC VARCHAR2 Replaces a GDFF: To satisfy reporting requirements in Leave blank
E_INTERNAL (150) certain countries, the company-issued Tax Invoice Date
_SEQ and Number. This field is used to record the company-
specific tax invoice number, in sequence, issued by the
company for a supplier-issued tax invoice. This is
required to comply with the reporting requirements.


Table
LEGAL_ENTI NUMBER Legal Entity Identifier Leave blank
TY_ID (15,0)
LEGAL_ENTI VARCHAR2 Legal Entity Name Leave blank
TY_NAME (50)
REFERENCE VARCHAR2 A reference to a record in another application Leave blank
_1 (30)
_2 (30)
OPERATING VARCHAR2 Organization name Leave blank
_UNIT (240)
BANK_CHAR VARCHAR2 Bearer of bank charge cost. Bank charge bearers are Leave blank
GE_BEARER (30) defined as the lookup IBY_BANK_CHARGE_BEARER
REMITTANC VARCHAR2 Remittance message for use in payment processing Leave blank
E_MESSAGE (150)
1
E_MESSAGE (150)
2
E_MESSAGE (150)
3
UNIQUE_RE VARCHAR2 Unique remittance identifier provided by the payee Leave blank
MITTANCE_I (30)
DENTIFIER
URI_CHECK VARCHAR2 Unique remittance identifier check digit Leave blank
_DIGIT (2)
SETTLEMEN VARCHAR2 The priority with which the financial institution or Leave blank
T_PRIORITY (30) payment system must settle payment for this document.
The available values for this column come from the FND
lookup IBY_SETTLEMENT_PRIORITY
PAYMENT_R VARCHAR2 Payment reason code Leave blank
EASON_CO (30)
DE


Table
PAYMENT_R VARCHAR2 Free text CI_ADJ_APR AP_REQ_ID CHAR (12)
EASON_CO (240) field EQ
MMENTS available for
(Release entering a
R12) reason for
the
payment
PAYMENT_ VARCHAR2 Payment method identifier Value =
METHOD_C (30) CHECK
ODE (not
available for
Release
11.5.10)
DELIVERY_C VARCHAR2 Delivery channel code Leave blank
HANNEL_CO (30)
DE
PAID_ON_B NUMBER When an expense report gets split in both pay scenario, Leave blank
EHALF_EMP (15,0) the new expense report's paid_on_behalf_employee_id
LOYEE_ID gets populated with the original expense report's
employee_id
NET_OF_RE VARCHAR2 Flag to indicate invoice amount is net of retainage Leave blank
TAINAGE_FL (1)
AG
REQUESTER VARCHAR2 The employee number of the employee who requested Leave blank
_EMPLOYEE (30) goods or services on the invoice line
_NUM
CUST_REGIS VARCHAR2 Customer legal registration code Leave blank
TRATION_C (30)
ODE
CUST_REGIS VARCHAR2 Customer legal registration number Leave blank
TRATION_N (30)
UMBER
PARTY_ID NUMBER Party Leave blank
(15,0) identifier
PARTY_SITE NUMBER Party Site Leave blank
_ID (15,0) identifier
PAY_PROC_ VARCHAR2 Type of payment processing transaction or document Leave blank
TRXN_TYPE (30)
_CODE


Table
PAYMENT_F VARCHAR2 The function or purpose of the payment Leave blank
UNCTION (30)
PAYMENT_P NUMBER Number representing payment priority of a scheduled Leave blank
RIORITY (2,0) payment (1 to 99)
PORT_OF_E VARCHAR2 Customs location code Leave blank
NTRY_CODE (30)
EXTERNAL_ NUMBER External bank account identifier Leave blank
BANK_ACCO (15,0)
UNT_ID
8.1.2.2 AP_INVOICE_LINES_INTERFACE
Columns Data Type Description ORMB Columns Data Type Remarks
Table
INVOICE_ID NUMBER Invoice identifier. Validated against AP_INVOICE
(15,0) AP_INVOICES_INTERFACE.INVOICE_ID S_interface_
S.currval
INVOICE_LI NUMBER Invoice line AP_INVOICE
NE_ID (15,0) identifier _lines_interf
ace_S.nextv
al
LINE_NUMB NUMBER Invoice line Value =1
ER (15,0) number
LINE_TYPE_ VARCHAR2 Type of invoice line (Item, Freight, Tax, Miscellaneous) 'MISCELLAN
LOOKUP_C (25) EOUS'
ODE
LINE_GROU NUMBER Value to identify each item line to prorate Leave blank
P_NUMBER
AMOUNT NUMBER Line amount CI_ADJ ADJ_AMT Number
(15,2)
ACCOUNTIN DATE Accounting SYSDATE
G_DATE date
DESCRIPTIO VARCHAR2 Description Value
N (240) =‘Refund
Request
from RMB’
AMOUNT_I VARCHAR2 No Longer Used Leave blank
NCLUDES_T (1)
AX_FLAG


Table
PRORATE_A VARCHAR2 Prorate indicator for this line to be prorated across all Leave blank
CROSS_FLA (1) lines with the same LINE_GROUP_NUMBER
G
TAX_CODE VARCHAR2 Tax code. Validated against AP_TAX_CODES_ALL.NAME Leave blank
(15)
FINAL_MAT VARCHAR2 Final match indicator for distribution line matched to ‘N’ indicates
CH_FLAG (1) purchase order not
matching to
the PO
PO_HEADER NUMBER Purchase order header identifier used for PO matching. Leave blank
_ID Validated against PO_HEADERS_ALL.PO_HEADER_ID
PO_NUMBE VARCHAR2 Purchase order number used for PO matching. Leave blank
R (20) Validated against PO_HEADERS_ALL.SEGMENT1
PO_LINE_ID NUMBER Purchase order line identifier used for PO matching. Leave blank
Validated against PO_LINES_ALL.PO_LINE_ID
PO_LINE_N NUMBER Purchase order line number used for PO matching. Leave blank
UMBER Validated against PO_LINES_ALL.PO_LINE_NUM
PO_LINE_LO NUMBER Purchase order line location identifier used for PO Leave blank
CATION_ID matching. Validated against
PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID
PO_SHIPME NUMBER Purchase order shipment number used for PO matching. Leave blank
NT_NUM Validated against
PO_LINE_LOCATIONS_ALL.SHIPMENT_NUM
PO_DISTRIB NUMBER Purchase order distribution line identifier used for PO Leave blank
UTION_ID matching. Validated against
PO_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_ID
PO_UNIT_O VARCHAR2 No longer Leave blank
F_MEASURE (25) used
INVENTORY NUMBER Inventory item identifier. Validated against Leave blank
_ITEM_ID MTL_SYSTEM_ITEMS.INVENTORY_ITEM_ID
ITEM_DESC VARCHAR2 Inventory Leave blank
RIPTION (240) item
description
QUANTITY_I NUMBER Quantity invoiced against purchase order shipment Leave blank
NVOICED
SHIP_TO_LO VARCHAR2 Ship to location code Leave blank
CATION_CO (60)
DE


Table
UNIT_PRICE NUMBER Unit price for purchase order matched invoice items Leave blank
DISTRIBUTI NUMBER Distribution set identifier. Validated against Leave blank
ON_SET_ID (15,0) AP_DISTRIBUTION_SETS_ALL.DISTRIBUTION_SET_ID
DISTRIBUTI VARCHAR2 Distribution set name. Validated against Leave blank
ON_SET_NA (50) AP_INVOICE_DISTRIBUTION_SETS_ALL.DISTRIBUTION_SE
ME T_NAME
DIST_CODE VARCHAR2 Accounting CI_DST_CO GL_ACCT VARCHAR2 Extract all
_CONCATEN (250) flexfield for DE_EFF (48) the
ATED account segments
associated that comes
with a from the
distribution ORMB side
line and
separate
them by ‘-‘
DIST_CODE NUMBER Accounting flexfield identifier for account associated
_COMBINAT (15,0) with a the distribution line. Validated against
ION_ID GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
AWT_GROU NUMBER Withholding tax group identifier. Validated against Leave blank
P_ID (15,0) AP_AWT_GROUPS.GROUP_ID
AWT_GROU VARCHAR2 Withholding tax group name Leave blank
P_NAME (25)
LAST_UPDA NUMBER Standard who column - user who last updated this row Leave blank
TED_BY (15,0) (foreign key to FND_USER.USER_ID).
LAST_UPDA DATE Standard who column - date when a user last updated SYSDATE
TE_DATE this row.
LAST_UPDA NUMBER Standard who column - operating system login of user Leave blank
TE_LOGIN (15,0) who last updated this row (foreign key to
FND_LOGINS.LOGIN_ID).
CREATED_B NUMBER Standard who column - user who created this row Leave blank
Y (15,0) (foreign key to FND_USER.USER_ID).
CREATION_ DATE Standard who column - date when this row was created SYSDATE
DATE
ATTRIBUTE_ VARCHAR2 Descriptive flexfield structure definition column. Leave blank
CATEGORY (150)
ATTRIBUTE1 VARCHAR2
Descriptive flexfield segment Leave blank
(150)


Table
ATTRIBUTE2 VARCHAR2
(150)
ATTRIBUTE3 VARCHAR2
(150)
ATTRIBUTE4 VARCHAR2
(150)
ATTRIBUTE5 VARCHAR2
(150)
ATTRIBUTE6 VARCHAR2
(150)
ATTRIBUTE7 VARCHAR2
(150)
ATTRIBUTE8 VARCHAR2
(150)
ATTRIBUTE9 VARCHAR2
(150)
ATTRIBUTE1 VARCHAR2
0 (150)
ATTRIBUTE1 VARCHAR2
1 (150)
ATTRIBUTE1 VARCHAR2
2 (150)
ATTRIBUTE1 VARCHAR2
3 (150)
ATTRIBUTE1 VARCHAR2
4 (150)
ATTRIBUTE1 VARCHAR2
5 (150)
GLOBAL_AT VARCHAR2
TRIBUTE_CA (150)
TEGORY
GLOBAL_AT VARCHAR2
TRIBUTE1 (150) Descriptive flexfield segment Leave Blank
GLOBAL_AT VARCHAR2
TRIBUTE2 (150)
GLOBAL_AT VARCHAR2
TRIBUTE3 (150)


Table
GLOBAL_AT VARCHAR2
TRIBUTE4 (150)
GLOBAL_AT VARCHAR2
TRIBUTE5 (150)
GLOBAL_AT VARCHAR2
TRIBUTE6 (150)
GLOBAL_AT VARCHAR2
TRIBUTE7 (150)
GLOBAL_AT VARCHAR2
TRIBUTE8 (150)
GLOBAL_AT VARCHAR2
TRIBUTE9 (150)
GLOBAL_AT VARCHAR2
TRIBUTE10 (150)
GLOBAL_AT VARCHAR2
TRIBUTE11 (150)
GLOBAL_AT VARCHAR2
TRIBUTE12 (150)
GLOBAL_AT VARCHAR2
TRIBUTE13 (150)
GLOBAL_AT VARCHAR2
TRIBUTE14 (150)
GLOBAL_AT VARCHAR2
TRIBUTE15 (150)
GLOBAL_AT VARCHAR2
TRIBUTE16 (150)
GLOBAL_AT VARCHAR2
TRIBUTE17 (150)
GLOBAL_AT VARCHAR2
TRIBUTE18 (150)
GLOBAL_AT VARCHAR2
TRIBUTE19 (150)
GLOBAL_AT VARCHAR2
TRIBUTE20 (150)
PO_RELEAS NUMBER Blanket purchase order release identifier used for PO Leave blank
E_ID matching. Validated against
PO_RELEASES_ALL.PO_RELEASE_ID


Table
RELEASE_N NUMBER Blanket purchase order release number used for PO Leave blank
UM matching. Validated against
PO_RELEASES_ALL.RELEASE_NUM
ACCOUNT_S VARCHAR2 Value for account segment of accounting flexfield. Leave blank
EGMENT (25) Payables overlays this value on the accounting flexfield
during import
BALANCING VARCHAR2 Value for balancing segment of accounting flexfield. Leave blank
_SEGMENT (25) Payables overlays this value on the accounting flexfield
during import.
COST_CENT VARCHAR2 Value for cost center segment of accounting flexfield. Leave blank
ER_SEGMEN (25) Payables overlay this value on the accounting flexfield
T during import.
PROJECT_ID NUMBER Identifier for project used to build default accounting Leave blank
(15,0) flexfield. Validated against
PA_PROJECTS_ALL.PROJECT_ID
TASK_ID NUMBER Identifier for project task used to build default Leave blank
(15,0) accounting flexfield. Validated against
PA_TASKS.TASK_ID
EXPENDITU VARCHAR2 Project expenditure type used to build default Leave blank
RE_TYPE (30) accounting flexfield. Validated against
PA_EXPENDITURE_TYPES.EXPENDITURE_TYPE
EXPENDITU DATE Project expenditure item date used to build default Leave blank
RE_ITEM_D accounting flexfield
ATE
EXPENDITU NUMBER Identifier for project organization used to build default Leave blank
RE_ORGANI (15,0) accounting flexfield. Validated against
ZATION_ID PA_EXP_ORGS_IT.ORGANIZATION_ID
PROJECT_A VARCHAR2 No longer Leave blank
CCOUNTING (30) used
_CONTEXT
PA_ADDITIO VARCHAR2 Flag that indicates if project related invoice distributions Leave blank
N_FLAG (1) have been transferred into Oracle Projects (Y or N)
PA_QUANTI NUMBER Project item quantity used to build accounting flexfield Leave blank
TY (22,5) for project-related distribution line.
USSGL_TRA VARCHAR2 USSGL transaction code for creating US Standard GL Leave blank
NSACTION_ (30) journal entries (Oracle Public Sector Payables). Validated
CODE against
GL_USSGL_TRANSACTION_CODES.USSGL_TRANSACTION
_CODE


Table
STAT_AMO NUMBER Amount associated with a distribution line for measuring Leave blank
UNT statistical quantities.
TYPE_1099 VARCHAR2 1099 type Leave blank
(10)
INCOME_TA VARCHAR2 Reporting region for distribution line for 1099 supplier. Leave blank
X_REGION (10) Validated against
AP_INCOME_TAX_REGIONS.REGION_SHORT_NAME
ASSETS_TRA VARCHAR2 Flag that indicates if distribution line is tracked in Oracle Leave blank
CKING_FLA (1) Assets (Y or N).
G
PRICE_COR VARCHAR2 Flag that indicates if line produces price correction. Leave blank
RECTION_FL (1)
AG
ORG_ID NUMBER Organizatio
(15,0) n identifier
RECEIPT_NU VARCHAR2 The receipt number to which an invoice is matched. Leave blank
MBER (30) Validated against
RCV_SHIPMENT_HEADERS.RECEIPT_NUM
RECEIPT_LI VARCHAR2 The receipt line number to which an invoice is matched. Leave blank
NE_NUMBE (25) Validated against RCV_SHIPMENT_LINES.LINE_NUM
R
MATCH_OP VARCHAR2 The value of the Invoice Match option on the PO Leave blank
TION (25) shipment.
PACKING_SL VARCHAR2 Packing slip identifier Leave blank
IP (25)
RCV_TRANS NUMBER Receipt identifier used for Receipt matching. Validated Leave blank
ACTION_ID against RCV_TRANSACTIONS.TRANSACTION_ID
PA_CC_AR_I NUMBER Identifier of the corresponding receivable intercompany Leave blank
NVOICE_ID (15,0) invoice in Oracle Receivables.
PA_CC_AR_I NUMBER Line number of the corresponding receivable Leave blank
NVOICE_LIN (15,0) intercompany invoice in Oracle Receivables.
E_NUM
REFERENCE VARCHAR2 A reference CI_ADJ_APR AP_REQ_ID CHAR (12) Leave blank
_1 (30) to a record EQ
in another
application
_2 (30)


Table
PA_CC_PRO VARCHAR2 Indicates the processing status of this invoice line by Leave blank
CESSED_CO (1) Oracle Projects in the Receiver Operating Unit
DE
TAX_RECOV NUMBER No Longer Used Leave blank
ERY_RATE
TAX_RECOV VARCHAR2 No Longer Used Leave blank
ERY_OVERRI (1)
DE_FLAG
TAX_RECOV VARCHAR2 No Longer Used Leave blank
ERABLE_FLA (1)
G
TAX_CODE_ VARCHAR2 No Longer Used Leave blank
OVERRIDE_ (1)
FLAG
TAX_CODE_ NUMBER Tax code identifier for the tax code to be used. Validated Leave blank
ID (15,0) against AP_TAX_CODES_ALL.TAX_ID
CREDIT_CAR NUMBER Credit card transaction ID if the line is a credit card Leave blank
D_TRX_ID (15,0) charge
AWARD_ID NUMBER Grants requirement to store award Leave blank
(15,0)
VENDOR_IT VARCHAR2 Optional. Validated against Leave blank
EM_NUM (25) PO_LINES_ALL.VENDOR_PRODUCT_NUM
TAXABLE_FL VARCHAR2 A value of Y indicates that the line is taxable Leave blank
AG (1)
PRICE_COR VARCHAR2 Number of the invoice that this price correction invoice is Leave blank
RECT_INV_ (50) correcting. Validated against
NUM AP_INVOICES_ALL.INVOICE_NUM
EXTERNAL_ VARCHAR2 Internal document reference number from Accounts Leave blank
DOC_LINE_ (240) Receivables system. Used for XML invoices
REF
SERIAL_NU VARCHAR2 Serial Leave blank
MBER (35) number for
item
MANUFACT VARCHAR2 Name of the manufacturer Leave blank
URER (30)
MODEL_NU VARCHAR2 Model Leave blank
MBER (40) information


Table
WARRANTY VARCHAR2 Warranty Leave blank
_NUMBER (15) number
DEFERRED_ VARCHAR2 Flag that indicates whether to generate deferred Leave blank
ACCTG_FLA (1) accounting for this line.
G
DEF_ACCTG DATE The start date of the deferred expense period. Leave blank
_START_DA
TE
DEF_ACCTG DATE The end date of the deferred expense period Leave blank
_END_DATE
DEF_ACCTG NUMBER Number of periods to generate deferred expenses. Used Leave blank
_NUMBER_ in combination with PERIOD_TYPE. Alternative to
OF_PERIOD END_DATE
S
DEF_ACCTG VARCHAR2 Period type used in combination with Leave blank
_PERIOD_TY (15) NUMBER_OF_PERIODS to generate deferred expenses.
PE Validated against XLA_LOOKUPS with lookup type
XLA_DEFERRED_PERIOD_TYPE
UNIT_OF_M VARCHAR2 Unit of Measure for quantity invoiced. Validated against Leave blank
EAS_LOOKU (25) MTL_UNITS_OF_MEASURE.UNIT_OF_MEASURE
P_CODE
PRICE_COR NUMBER Invoice line subject to the price correction Leave blank
RECT_INV_L
INE_NUM
ASSET_BOO VARCHAR2 Asset Book Defaults to the distributions candidate for Leave blank
K_TYPE_CO (15) transfer to Oracle Assets.
DE
ASSET_CATE NUMBER Asset Category Defaults to the distributions candidate for Leave blank
GORY_ID (15,0) transfer to Oracle Assets
REQUESTER NUMBER Requester identifier. Valid values from active HR Leave blank
_ID (15,0) employees. Validated against
PER_ALL_PEOPLE_F.PERSON_ID
REQUESTER VARCHAR2 The first name of the employee who requested goods or Leave blank
_FIRST_NA (150) services on the invoice line. This value is used to derive
ME the requester ID. If you use Invoice Approval Workflow


Table
REQUESTER VARCHAR2 The last name of the employee who requested goods or Leave blank
_LAST_NAM (150) services on the invoice line. This value is used to derive
E the requester ID. If you use Invoice Approval Workflow
REQUESTER VARCHAR2 The employee number of the employee who requested Leave blank
_EMPLOYEE (30) goods or services on the invoice line. This value is used to
_NUM derive the requester ID. If you use Invoice Approval
Workflow then you can define rules that use the
requester ID to generate a hierarchical list of approvers
for the line
APPLICATIO NUMBER Application Identifier Leave blank
N_ID (15,0)
PRODUCT_T VARCHAR2 Product source table name Leave blank
ABLE (30)
REFERENCE VARCHAR2 Primary key information that uniquely identifies a record Leave blank
_KEY1 (150) in other products view
PURCHASIN VARCHAR2 Item category concatenated segments Leave blank
G_CATEGOR (2000)
Y
PURCHASIN NUMBER Item category unique identifier Leave blank
G_CATEGOR (15,0)
Y_ID
COST_FACT NUMBER Identifier of the cost component class. Cost Component Leave blank
OR_ID (15,0) Classes are used to identify the individual buckets or
component costs that make up the total cost of an item,
for example, direct material costs, freight costs, labor
costs, production or conversion costs and so on.


Table
COST_FACT VARCHAR2 Cost component class name. Cost Component Classes are Leave blank
OR_NAME (80) used to identify the individual buckets or component
costs that make up the total cost of an item, for example,
direct material costs, freight costs, labor costs,
production or conversion costs and so on.
CONTROL_A NUMBER Optional, user-enterable value to ensure that the Leave blank
MOUNT calculated tax is the same as on the physical document.
ASSESSABLE NUMBER User-enterable amount to be used as taxable basis Leave blank
_VALUE
DEFAULT_DI NUMBER Already addressed by lines project Tax Driver: Code Leave blank
ST_CCID (15,0) combination identifier of the GL account associated with
the transaction line. Note that this is necessary to
support the Account Method VAT feature.
PRIMARY_I VARCHAR2 Tax Driver: The purpose for which a product may be Leave blank
NTENDED_ (30) used. The actual use is stored at the distribution level.
USE
SHIP_TO_LO NUMBER Tax Driver: Ship to location ID. Value entered by user Leave blank
CATION_ID (15,0) only if line is not matched by PO.
PRODUCT_T VARCHAR2 Tax Driver: Type of product. Leave blank
YPE (240) Possible values: Goods, Service.
This value will default from the Inventory Item attributes.
Otherwise, value is entered by user.
PRODUCT_C VARCHAR2 Tax Driver: Product category Leave blank
ATEGORY (240)
PRODUCT_F VARCHAR2 Tax Driver: Product fiscal classification Leave blank
ISC_CLASSIF (240)
ICATION
USER_DEFIN VARCHAR2 Tax Driver: Fiscal Classification. Leave blank
ED_FISC_CL (240)
ASS
TRX_BUSINE VARCHAR2 Tax Driver: Transactions category assigned by user. Leave blank
SS_CATEGO (240)
RY
TAX_REGIM VARCHAR2 Tax Regime Code: The set of tax rules that determines Leave blank
E_CODE (30) the treatment of one or more taxes administered by a
tax authority. e.g., VAT Regime in Argentina
TAX VARCHAR2 A classification of a charge imposed by a government Leave blank
(30) through a fiscal or tax authority.


Table
TAX_JURISD VARCHAR2 Internal ID of the Tax Jurisdiction Leave blank
ICTION_CO (30)
DE
TAX_STATU VARCHAR2 Tax status code. e.g., taxable standard rate, zero rated, Leave blank
S_CODE (30) exempt, non-taxable
TAX_RATE_I NUMBER Internal identifier for tax rate effective on the invoice Leave blank
D (15,0) date.
TAX_RATE_ VARCHAR2 Tax rate name associated with tax rate identifier. Leave blank
CODE (150) Tax_rate_id is unique while a tax_rate_code may have
different tax rates based on date ranges
TAX_RATE NUMBER The rate specified for a tax status in effect for a period of Leave blank
time.
INCL_IN_TA VARCHAR2 Flag to indicate if the amount in the tax line is included or Leave blank
XABLE_LINE (1) not in the taxable line.
_FLAG
SOURCE_AP NUMBER Source document application identifier Leave blank
PLICATION_I
D
SOURCE_EN VARCHAR2 Source document entity code Leave blank
TITY_CODE (30)
SOURCE_EV VARCHAR2 Source document event class code Leave blank
ENT_CLASS_ (30)
CODE
SOURCE_TR NUMBER Source document transaction identifier Leave blank
X_ID
SOURCE_LI NUMBER Identifier of the lowest level for which tax is calculated Leave blank
NE_ID
SOURCE_TR VARCHAR2 Source document transaction level type Leave blank
X_LEVEL_TY (30)
PE
TAX_CLASSI VARCHAR2 Tax Classification Code Leave blank
FICATION_C (30)
ODE
DEF_ACCTG DATE The start date of the deferred expense period Leave blank
_START_DA
TE

8.1.3 A/P Data

8.1.3.1 EBS Accounting A/P Data table mapping to ORMB
ORMB Columns Data Description PS Table Columns Data Type Remarks
Table Type
CI_ADJ_A PAY_DOC VARCHA Advice ID AP_CHE CHECK_ID NUMBER
PREQ _ID R2 (20) CKS_ALL (15)
CI_ADJ_A PAY_DOC DATE Advice Date AP_CHE CHECK_D DATE
PREQ _DT CKS_ALL ATE
CI_ADJ_A PYMNT_I CHAR Payment AP_CHE CHECK_N NUMBER
PREQ D (10) Number CKS_ALL UMBER (15)
CI_ADJ_A PAID_AM NUMBER Paid Amount AP_CHE AMOUNT NUMBER
PREQ T (15,2) CKS_ALL
CI_ADJ_A PYMNT_S CHAR (1) Payment Derived from ODI. Value = ‘P’ (For valid
PREQ EL_STAT_ Selections Payment) Value =’C’ (For Void hold or Initiate
FLG Status stop)And Value =’X’ (For Void Cancel)
CI_ADJ_A AP_REQ_I CHAR A/P Request AP_INV PAYMENT VARCHAR
PREQ D (12) ID OICES_A _REASON 2 (240)
LL _COMME
NTS
CI_ADJ_A ADJ_ID CHAR Adjustment AP_INV INVOICE_ VARCHAR If liability
PREQ (12) ID OICES_A NUM 2 (50) is closed
LL the
‘Adjustme
nt
Maintena
nce’
service is
invoked
for this
Adjustme
nt ID.
CI_ADJ_A PYMNT_S CHAR (1) Payment Derived from ODI.
PREQ EL_STAT_ Selections When AP_CHECKS_ALL.STOPPED_DATE IS NOT
FLG Status NULL or AP_CHECKS_ALL. VOID_DATE IS NOT
NULL then Value=’C’
When AP_INVOICES_ALL.CANCELLED_DATE IS
NOT NULL then Value=’X’
CI_ADJ CAN_RSN CHAR (4) Cancel APVC
_CD Reason Code

Oracle Revenue Management and Billing ORMB-EBS Implementation Guide

Uploaded by

Copyright:

Available Formats

Oracle Revenue Management and Billing ORMB-EBS Implementation Guide

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Revenue Management and Billing ORMB-EBS Implementation Guide

Uploaded by

Copyright:

Available Formats

Oracle® Revenue Management and Billing

ORMB-EBS Implementation Guide

ORMB-EBS Implementation Guide

ii Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

iv Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

8.1.1 GL Transaction .............................................................................................................41

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. v

vi Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

2.2 Business Process Task Flow

RMB Oracle E-Business Suite

RMB Oracle E-Business Suite

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 1

The flow of data between the two systems is illustrated below:

2.2.1 General Ledger Process

2 Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

Figure 1 GL Process Flow Diagram

Following are the steps for the GL Process flow:

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 3

2.2.2 Account Payable Request Process

4 Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

Figure 2 AP Process Flow Diagram

Following are the steps in AP Request flow:

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 5

2.2.3 Account Payable Data Process

EBS ORMB AP Request Resulting Action ORMB Adjustment Resulting

6 Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

Payment Cancellation Process

Initiate Stop/Void Hold

Figure 3 AP Data Process Flow Diagram

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 7

Figure 3 AP Data Process Flow Diagrams for Cancellation

2.3 Best Practices

2.3.1 One-Time Configuration Settings

8 Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

General Ledger Configuration

General Ledger Divisions for Non-Integrated Transactions

2.3.1.1 General Ledger Integration

Oracle E-Business Suite Revenue Accounting General Ledger Settings

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 9

Oracle Revenue Management and Billing General Ledger Settings

Integration Software General Ledger Settings

10 Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

Oracle Revenue Management and Debit Account Credit Account

2.3.1.2 Accounts Payable (A/P) Request and A/P Data Integrations

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 11

Oracle Revenue Management and Billing A/P Settings

Integration Software A/P Settings

Event Debit Account Credit Account

12 Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

2.4 Solution Flow

Note: For more information, refer to ORMB-EBS Integration Guide.

2.4.2 ODI Process Flow

2.4.3 Solution Diagram for Integration using ODI

Figure 1 GL and AP Request Solution Flow Diagram

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 13

Figure 2 AP Data Solution Flow Diagram

14 Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

2.4.4 Database Details for Integration