CV.

040 Financial Data Migration

Conversion Design

AR Sales Invoice Migration to EBS

Author: Jay Shearn

Creation Date: July 24, 2014
Last Updated: August 15, 2019
Document Ref: CV.040.SOPFIN_ARINV
Version: ISSUE V1.2

Approvals:

Chris Lee (RX)

David Wood (RX)

 September 8, 2014

DOCUMENT CONTROL

Change Record

Date Author Version Change Reference

29-Jul-2014 Jay Shearn Draft V0.1 No Previous Document

28-Aug-2014 Jay Shearn ISSUE V1.0 Issued for Review / Approval

29-Aug-2014 Jay Shearn ISSUE V1.1 Updated with link to CV.010 – Financials Data
Migration Requirements document on
Sharepoint

05-Sep-2014 Jay Shearn ISSUE V1.2 Embedded mapping spreadsheet removed

and saved as a separate document on
Sharepoint. Link available from within this
document.

Reviewers

Name Position

David Wood RX Q2C Workstream Lead

Chris Lee RX Q2C Global Process Owner

John Gee RX CRM Consultant

Tracy Evans RX UK Financial Controller

Chris Van De Walt HCL Data Migration Project Manager

Shaun Webley HCL Data Migration EBS Functional Consultant

Mathupal Thanumalayan HCL Data Migration EBS Technical Consultant

Distribution

Copy No. Name Location

1 Library Master RX Project Library

Company Confidential - For internal use only

P a g e |1
 September 8, 2014

Copy No. Name Location

Company Confidential - For internal use only

P a g e |2
 September 8, 2014

Table of Contents
Document Control ......................................................................................................................1

Introduction..................................................................................................................................4

Application Business Object Reference ..............................................................................7

Interface Functional Design ....................................................................................................8

Conversion Mapping .............................................................................................................. 19

Extract File Layouts and Excel Worksheets .................................................................... 20

Data Migration Process ......................................................................................................... 21

Data Clean Up ........................................................................................................................... 23

Data Normalization................................................................................................................. 24

Open and Closed Issues for this Deliverable ................................................................. 25

Appendix I – Insert Statement into Interface Tables for an Invoice ..................... 26

Company Confidential - For internal use only

P a g e |3
 September 8, 2014

INTRODUCTION

Purpose
The purpose of this document is to explain how to use the AR Sales Invoice interface allowing
integration of legacy or external data with the Oracle Receivables module, and how to define the
data that must be assembled to accomplish this.
This approach by populating the AR interface tables directly without reference to the sales orders in
Order Management will be taken as an alternative to migrating mid-cycle sales orders from SFDC to
EBS and producing subsequent sales invoices (open or closed) in AR as a result of the orders.

Background
This document will outline and define the tasks and processes necessary to upload data to the Oracle
E-Business Suite to create AR Sales Invoices and Credit Notes.

RX Data Migration Requirements

This document has been produced as a result of information detailed in the document and feedback
emails held on Sharepoint and should be read in conjunction with this document.
- CV.010 Financial Data Migration Requirements
Link to CV.010 Financial Data Migration Requirements

Scope and Approach

Scope: The scope of this document is limited to the creation of AR Sales Invoices and Credit Notes for
all mid-cycle RX shows.
Approach: Suitable data will be extracted from existing Reed systems, and exported to an MS Excel
spreadsheet where it will be enhanced / enriched / corrected / amended as necessary. The data will
consist of a header row for each invoice, and one or more lines rows. Each invoice line will only have
one revenue account assigned to it.
Once this is complete, the data will be uploaded to the appropriate Oracle interface table using an
SQL Loader process before being imported to the database via the use of the standard Oracle
AutoInvoice concurrent process.
There must be at least one AR Invoice Line for each AR Invoice Header defined. Distribution lines are
optional, if none are declared, the import process will create a single distribution for each line, using
the default receivables, revenue and tax accounts dependent on the Auto Accounting Rules defined
in AR.

NOTE: It is likely that specific distributions will be required to ensure the correct revenue account is
used.

Company Confidential - For internal use only

P a g e |4
 September 8, 2014

Audience
This document is intended to be used by those who will need to assemble to data to be migrated, and
those who will create the upload program (SQL Loader).

Business Rules
RX to complete.

Pre-Requisites and Dependencies

1. Pre-Requisite: The Oracle Receivables and Advanced Collections modules will be installed and
configured according to the relevant BR.100s.
2. Pre-Requisite: Reed Exhibitions Product items will already exist in the Master and Business Unit
Organizations where the import will be run, and will be configured for selling as necessary.
3. Pre-Requisite: An AR Source will be defined for migrated sales invoices.
4. Pre-Requisite: AR Transaction Types for Invoices and Credit Notes will be defined with separate
document sequences.
5. All HR records for Sales Reps and Collectors will be available prior to the migration of invoices.

Assumptions
1. All data to be considered will be cleaned and normalised prior to import to EBS.
2. All migrated invoices will not be required to be printed as customer facing documents once
migrated to EBS. Printing will have taken place via PRISM and any reprinting of these
transactions will take place in PRISM.
3. Products and Packages will be assigned an ‘Item Number’ that will identify them uniquely in the
EBS system.
4. Receivables distribution lines for all migrated invoices will be derived from the pre-configured
AutoAccounting Rules in AR. Revenue lines will be provided in the interface.

Definitions

Term Definition
EBS E-Business Suite. The target system for the conversion process.

PRISM The Reed Exhibitions Source system that will be providing the data for the conversion
process.

PRODUCT An object that Reed Exhibitions sell. This will sometimes be referred to as an Item in
the EBS system.

Company Confidential - For internal use only

P a g e |5
 September 8, 2014

Term Definition
PACKAGE An object that Reed Exhibitions sell. This will usually be a collection of PRODUCTS
grouped together to form a logical unit. A PACKAGE will be represented in EBS by the
creation of a Bill of Materials (BOM).

FLEXFIELD An additional, user-defined data element in EBS.

STAGING TABLE A data table used to hold information during a process.

INTERFACE TABLE A data table used by an Interface Program. This table usually holds the data being
imported EBS.

ORGANIZATION Reed has one EBS Organization per Business Unit. Packages will belong to a specific
organization.

SQL LOADER An Oracle product that provides a simple way of uploading data from a flat file to an
Oracle Database table.

REVENUE ACCOUNT or DISTRIBUTION The GL account code combination that the value of the sale will be posted to.

DISTRIBUTION LINE A sales invoice line may have one or more distribution lines. Each distribution line may
nominate a different REVENUE ACCOUNT.

Company Confidential - For internal use only

P a g e |6
 September 8, 2014

APPLICATION BUSINESS OBJECT REFERENCE

The following business objects are used in this migration process:

Manual / Production Table

Business Object Program Owned By Open Interface (once AutoInvoice is run)
Sales Invoice Header Program Q2C / Reed RA_INTERFACE_LINES_ALL RA_CUSTOMER_TRX_ALL

Sales Invoice Lines Program Q2C / Reed RA_INTERFACE_LINES_ALL RA_CUSTOMER_TRX_LINES_ALL

Sales Invoice Distributions Program Q2C / Reed RA_INTERFACE_DISTRIBUTIONS_ALL RA_CUST_TRX_LINE_GL_DIST_ALL

Sales Invoice Sales Credits Program Q2C / Reed RA_INTERFACE_SALESCREDITS_ALL RA_CUST_TRX_LINE_SALESREPS_ALL

Sales Invoice Revenue Recognition N/A N/A AR_INTERFACE_CONTS_ALL N/A

Import Errors N/A N/A RA_INTERFACE_ERRORS_ALL N/A

Company Confidential - For internal use only

P a g e |7
 September 8, 2014

INTERFACE FUNCTIONAL DESIGN

Overview
The following areas are covered within the Interface Functional Design section:

1. Oracle AR AutoInvoice Table structure

2. Required functional setup changes in AR
3. Data to interface transactions from legacy systems to AR
4. Import Process & Error Handling
5. Accounting Derivation

Oracle AR AutoInvoice Table Structure

A transaction consists of a header and one or more lines. Each of these lines will have one or more
distribution although this will not be required for GL reporting purposes as revenue balances will be migrated
directly into GL as part of the GL balances migration. The data is interfaced into AR via the AR AutoInvoice
tables which consist of:

- RA_INTERFACE_LINES_ALL
This table lists all the transaction header and line data, and is grouped by the AutoInvoice process
into transactions as a result of the configuration within AR.

- RA_INTERFACE_DISTRIBUTIONS_ALL
This table details the accounting distributions for a transaction, and is limited in this interface to
revenue and tax accounts only. Predefined AutoAccounting rules will be used to derive Revenue, Tax
and Receivable accounts. The interface will cater for revenue for a single transaction line to be split
into multiple revenue account combination allocations if required.

- RA_INTERFACE_SALESCREDITS_ALL
Rows must be populated in this table because the Receivables System Option ‘Require Salesperson’ is
set to ‘Yes’. This information will be derived from the information in the RA_INTERFACE_LINES_ALL
table.

- AR_INTERFACE_CONTS_ALL
This table stores information about contingencies that impact revenue recognition for the imported
transactions. No data is required to be populated in this table as revenue recognition is not going to
be used on migrated transactions.

- RA_INTERFACE_ERRORS_ALL
This table records all the errors encountered when running the AutoInvoice concurrent program to
import invoices from the interface tables.

Note: Where migrated data refers to existing data in EBS (e.g. customer accounts, transaction types,
accounting etc.), IDs for the data need to be provided when the interface tables are populated in order for

Company Confidential - For internal use only

P a g e |8
 September 8, 2014

the corresponding records to be identified. In this case, scripts must be written to identify the IDs and
lookups carried out before the data is loaded into the interface tables.

Additional AR Configuration
The following additional configuration is required in AR to support the interface for the migration process
only.

- Transaction Source
A new Transaction Source ‘PRISM’ will be defined in AR for creating migrated transactions.

The Transaction Source needs to be defined for each RX Operating Unit.

A Transaction Source determines whether AR automatically numbers transactions and what the
starting numbers are; additionally it determines what to do if an error occurs during the import
process and whether to expect an Oracle internal ID or a descriptive name for items of reference
data.

Rows are inserted into the open interface tables by Transaction Source, and the AutoInvoice import
program is run by Transaction Source.

The screen shots below depict the Transaction Source setup for migrated transactions.

Note: The information in the Batch Source tab will be different depending upon the Operating Unit
the Transaction Source it relates to. Thereafter, the other information is the same for each Operating
Unit.

o Batch Source Tab:

As this is an imported Transaction Source, and to automatically number new transactions

imported via the interface, the Automatic Transaction Numbering boxes must be checked and
a Last Number Used value entered. The Reference Field Default Value, will be set to
‘interface_header_attribute1 (i.e. Legacy Invoice Number) as this uses the Invoice Transaction
Flexfield attribute.

The Standard Transaction Type field will specify the Transaction Type the interface will use
when creating transactions of an Invoice Class for this source. The Transaction Type the
interface will use when creating transactions of a Credit Memo Class will be derived from the
Credit Memo Transaction Type associated with the Invoice Transaction Type recorded in this
field. See screen shot below.

Company Confidential - For internal use only

P a g e |9
 September 8, 2014

o AutoInvoice Options Tab:

If any problems occur with the interface (i.e. an invalid tax rate, invalid line or the GL Date is
in an unopened period), the AutoInvoice options have been set to reject the transaction. The
errored transaction will reside in the AutoInvoice tables with a status of ‘Error’ and will have
to be corrected before reimporting into AR.

o Customer Information Tab:

Company Confidential - For internal use only

P a g e | 10
 September 8, 2014

IDs for all the customer information will be supplied by PRISM as shown in the screen print
below.

Where no validation is required, the ‘None’ option has been chosen.

Sold To, Ship To, Bill To Contact, Payment Method and Customer Bank Account information
options are not significant for this Transaction Source, as this information is not required for
the AutoInvoice validation.

o Accounting Information Tab

PRISM will only supply the Accounting Flexfield segment ID for the Revenue account.

The Tax and Receivables values will be created during the AutoInvoice process using the
AutoAccounting Rules already defined in AR.

Payment Terms ID and the Revenue Account Allocation percentage will be supplied for each
transaction.

Company Confidential - For internal use only

P a g e | 11
 September 8, 2014

o Other Information Tab:

Agreement, Memo Line Rule, Sales Territory, Inventory Item, FOB Point, Freight Carrier and
Related Document options are not significant for this Transaction Source and are not required
for AutoInvoice validation.

o Sales Credit Validation:

Company Confidential - For internal use only

P a g e | 12
 September 8, 2014

IDs will be used to validate Sales Credit information.

- Transaction Type
CUST_TRX_TYPE_ID will be derived from the Transaction Source. For invoice and credit note
transactions this will be the Standard Transaction Type of the Transaction Source (i.e. XXXX-
MIGRATED_INV where XXXX is the Legal Entity (see below).

Note: This Transaction Type must be assigned to the migration document sequence.

- Salesperson
PRIMARY_SALESREP_ID is required as the Receivables System Option ‘Require Salesperson’ is set to
‘Yes’. This will be provided by the feed from PRISM.
Company Confidential - For internal use only

P a g e | 13
 September 8, 2014

- Distribution Account Class

Revenue Lines: ACCOUNT_CLASS is a constant value of ’REV’ (Revenue) to indicate that the
distribution rows are revenue distributions.

Tax Lines: ACCOUNT_CLASS is a constant value of ‘TAX’ to indicate that the distribution rows are tax
distributions.

- Conversion Type
CONVERSION_TYPE is the mandatory field in the open interface tables and will be populated with a
constant value of ‘Corporate’. AutoInvoice uses this conversion type to derive exchange rate for a
given transaction date using corporate daily conversion rates defined in AR. It then converts the
foreign currency amount for foreign currency transactions) into sterling for accounting purposes.

- GL Date and Transaction Date

GL_DATE will be hardcoded in the interface file as the transactions will not be posted in GL and
therefore this date is irrelevant. TRX_DATE will be the original invoice date held in PRISM. The dates
related to each transaction (i.e. TRX_DATE and GL_DATE) will be populated

- Line Transaction Flexfield

There is no AutoInvoice table that represents the transaction header. AutoInvoice provides interface
tables at transaction line level and lower (distributions and sales credits) and groups the lines sharing
common attributes into transactions.

To ensure AutoInvoice does not import duplicate transaction lines for a Transaction Source, the Line
Transaction Flexfield must be configured in AR so that the combination of its segment values is
unique for a line. AutoInvoice will reject lines where the combination of values already exists. The
combination of values is also used as a key to join transaction line information to its related rows in
the distribution and sales credit interface tables.

Company Confidential - For internal use only

P a g e | 14
 September 8, 2014

NB: Line 10 = INTERFACE_LINE_ATTRIBUTE1, Line 20 = INTERFACE_LINE_ATTRIBUTE2

Lines to be grouped into a transaction will share some common segment values at the line level. The
common segments are specified in a Grouping Rule in AR, which AutoInvoice uses to group lines into
transactions thus rolling-up the common line level segments to segments in the Invoice Transaction
Flexfield.

No enabled segment of the transaction flexfields may be NULL, even if the required attribute is set to
No.

A simple example of using this flexfield is shown below:

LINE_TYPE INTERFACE_LINE_CONTEXT INTERFACE_LINES_ATTRIBUTE1 INTERFACE_LINES_ATTRIBUTE2

LINE PRISM INVOICE123 LINE1

- Link-to Transaction Flexfield

Link-To Transaction Flexfields have the same structure as the Line Transaction Flexfield. Link-To
Transaction Flexfields are used to relate rows within a batch of interface table data to each other.
This is used to import tax associated to specific transaction lines.

Company Confidential - For internal use only

P a g e | 15
 September 8, 2014

NB: Line 10 = LINK_TO_LINE_ATTRIBUTE1, Line 20 = LINE_TO_LINE_LINE_ATTRIBUTE2

A simple example of using this flexfield is shown below, it builds on top of the example shown above
for Line Transaction Flexfield.

ROW LINE_TYPE INTERFACE_LI INTERFACE_LINE INTERFACE_LINE LINK_TO_CONTEX LINK_TO_ATT LINK_TO_AT

NE_CONTEXT S_ATTRIBUTE1 S_ATTRIBUTE2 T RIBUTE1 TRIBUTE2

1 LINE PRISM INVOICE123 ITEM LINE

2 TAX PRISM INVOICE123 TAX LINE PRISM INVOICE123 ITEM LINE

Company Confidential - For internal use only

P a g e | 16
 September 8, 2014

- Invoice Line Ordering Rules

To keep line numbering consistent between PRISM and AR, it is necessary to create an AutoInvoice
Line Ordering Rule, which can be associated with the AutoInvoice Grouping Rule and PRISM
Transaction Source).

The Line Ordering Rule will order lines being imported based on ascending order of the PRISM
transaction line number, which will be captured in the interface in the field
INTERFACE_LINE_ATTRIBUTE2.

- Invoice Grouping Rules

To ensure interface lines are grouped correctly into transaction headers and lines, an AutoInvoice
Grouping Rule specifies the characteristics, which must be common between interface lines to be
grouped into a transaction.

The structure of the Grouping Rule follows the structures of the line and invoice transaction flexfields
described previously. The Grouping Rule also specifies the Line Ordering Rule to be used.

EBS Products and Packages

EBS Products and Packages will be referenced on the migrated invoice lines. The information that will be
populated for migrated invoice lines will be:
Company Confidential - For internal use only

P a g e | 17
 September 8, 2014

- Inventory Item
- Description
- UOM Code
- Unit Selling Price
- Unit Standard Price
- Quantity Ordered

Transaction Accounting Derivation

This section outlines how the distributions in each of the following account classes will be determined in this
interface:

- REV: A revenue distribution records the income of the transaction in the profit and loss
- TAX: A tax distribution records any VAT that must be paid to HMRC in the balance sheet
- REC: A receivable distribution that records the debt collectable from the customer, also in the
balance sheet

The monetary value of each distribution is coded to a GL Account Code Combination, made up of a
combination of values in the Accounting Flexfield structure, shown below:

Segment1 Segment2 Segment3 Segment4 Segment5 Segment6 Segment7 Segment8 Segment9

Entity Account Sub- Management Event Activity Product Intercompany Spare

Account Centre Edition

Each segment has its own distinct list of valid values, the combination of values must be complete (no null
segment values) and the combination of values must be pre-existing and valid.

- Revenue Accounting (REV)

The revenue distribution lines will be specified in the interface and written to the
RA_INTERFACE_DISTRIBUTIONS_ALL table.

- Receivable Accounting (REC) / Tax Accounting (TAX)

As stated in the design overview, the PRISM interface will not pass distributions for the Tax and
Receivables posting. The purpose of this is so that AutoInvoice uses AutoAccounting to derive the
Receivable and Tax account code combinations for each transaction.

Tax Accounting & Calculation

It will be necessary to supply the calculated tax for a transaction line as a separate line but using the Link-to
Transaction flexfield to relate the tax lines to the original invoice lines. By providing the PRISM tax lines on
each invoice, this will prevent tax calculation differences between PRISM and EBS as EBS will not recalculate
the tax.

Company Confidential - For internal use only

P a g e | 18
 September 8, 2014

CONVERSION MAPPING
The following spreadsheets show the conversion mapping to be used. The table details map directly to the
Open Interface requirements.
Note: The details contained in this file are subject to change due to a review of the configuration of EBS and
the data to be migrated.
Link to Conversion Mapping for AR Sales Invoices

Company Confidential - For internal use only

P a g e | 19
 September 8, 2014

EXTRACT FILE LAYOUTS AND EXCEL WORKSHEETS

Please refer to the following document written by John Gee and stored in Sharepoint.

Link to EA UK - Migration, Prism Extract specification

Company Confidential - For internal use only

P a g e | 20
 September 8, 2014

DATA MIGRATION PROCESS

The following diagram details the process to extract data from PRISM, load the data into the EBS interface
tables and import it into EBS:

SQL Loader script

EBS AR AutoInvoice Interface Tables

EBS AR Concurrent Request

In order to accomplish the data migration of AR invoices, the following tasks and activities need to take place
in the following sequence:

1. Create and publish a mapping document / file that Reed Exhibitions can use as the basis for
the package extract. This defines the content of the extract from the legacy system(s), and
will be in Excel format.

2. Reed Exhibitions will be responsible for completing the mapping document / file.

3. The Excel file created in (2) above will be enhanced / enriched / corrected / amended as
necessary.

4. Once the file in (3) above is complete, the Excel file will need to be saved as a flat, delimited
file (usually pipe [|]). A SQL Loader process will then be required to take the file and load it
into the relevant Oracle Interface tables for further processing. This will be a bespoke
process.

Company Confidential - For internal use only

P a g e | 21
 September 8, 2014

5. The AutoInvoice concurrent process (Autoinvoice Master Program) will be called from the
application to take the interface data and upload to the Receivables invoice tables.

6. Any errors reported will be stored in the RA_INTERFACE_ERRORS_ALL table, and may be
accessed via a simple SQL query or via the application (Navigation Path: Receivables Manager
 Control  AutoInvoice  Interface Lines or Interface Exceptions). Once addressed, the
process from step (3) above should be re-iterated.

7. Once all the migrated transactions are created in AR, the standard ‘Create Accounting’
concurrent request will be run to create the accounting entries for the migrated transactions
with the following parameters:

 Ledger: UK Primary Ledger RX

 End Date: [Date of Migration}
 Mode: Final
 Errors Only: No
 Report: Detailed
 Transfer to General Ledger: Yes
 Post in General Ledger: No
 General Ledger Batch Name: [OU Name, AR Migrated Transactions]
 Include User Transaction Identifiers: Yes

8. The General Ledger batch created as a result of Step 7 will then be deleted or posted and
reversed to prevent the GL account codes being updated with the transaction balances.

Company Confidential - For internal use only

P a g e | 22
 September 8, 2014

DATA CLEAN UP
All migrated data will be subject to a process where it is enhanced / enriched / corrected / amended (where
necessary) prior to it being migrated to EBS via the interface tables.
RX will be responsible for this process.

Company Confidential - For internal use only

P a g e | 23
 September 8, 2014

DATA NORMALIZATION
As mentioned in the previous section, all migrated data will be subject to a process where it is enhanced /
enriched / corrected / amended (where necessary) prior to it being migrated to EBS via the interface tables.
RX will be responsible for this process.

Company Confidential - For internal use only

P a g e | 24
 September 8, 2014

OPEN AND CLOSED ISSUES FOR THIS DELIVERABLE

Item Status Item Requiring Action or Resolution Issue Log Responsibility Target Resolution Closed Date
ID (Open / ID (if Completion
Closed) applic.) Date

1 Due Date: The standard AutoInvoice functionality only allows the HCL – Jay Shearn ASAP
due date on an imported invoice to be calculated based on the
Payment Terms (TERMS_ID or TERM_NAME) data supplied in the
interface table (RA_INTERFACE_LINES_ALL).

Note from Metalink:

Passing in DUE_DATE
AutoInvoice does not allow you to pass interface data for due date.
The structure of RA_INTERFACE_LINES_ALL does not even have a
field to hold such a value. The only way to control the due date
derived by AutoInvoice is to pass in a transaction date (TRX_DATE)
and a payment term (TERM_ID or TERM_NAME). From these
values the code will calculate the due date. See Note 201241.1,
Troubleshooting AutoInvoice Date Derivation: GL Date, Invoice
Date, Due Date, Ship Date, Billing Date, Rule Date

****Check out Base Due Date on Trx Date ****

How do we get the PRISM due date populated against the migrated
invoice with the correct PRISM value? POC used ‘IMMEDIATE’
therefore Due Date = Transaction Date.

Company Confidential - For internal use only

P a g e | 25
 September 8, 2014

APPENDIX I – INSERT STATEMENT INTO INTERFACE TABLES FOR AN INVOICE

The following script will create a simple invoice using the AutoInvoice interface.

Note: This information is for reference purposes only and will need to be amended to suite RX’s
configuration and migrated data.

-- Item Line
INSERT INTO ra_interface_lines_all(interface_line_context, interface_line_attribute1,
interface_line_attribute2,
amount, batch_source_name, conversion_rate,
conversion_type, currency_code, cust_trx_type_id,
description, gl_date, line_type,
orig_system_bill_address_id, orig_system_bill_customer_id,
quantity, unit_selling_price,
term_id, taxable_flag, amount_includes_tax_flag,
set_of_books_id, org_id)
VALUES
(‘PRISM', 'INVOICE123’, ‘ITEM LINE’',
1000.00, 'PRISM', 1,
'User', 'GBP', 3627,
'Migrated Invoice 123', '31-JUL-2014', 'LINE',
1088, 2040,
10, 100.00,
5, 'N', 'N',
2024, 85);

-- Tax Line
INSERT INTO ra_interface_lines_all
(interface_line_context, interface_line_attribute1, interface_line_attribute2,
link_to_line_context, link_to_line_attribute1, link_to_line_attribute2,
amount, batch_source_name, conversion_rate,
conversion_type, currency_code, cust_trx_type_id,
description, gl_date, line_type,
orig_system_bill_address_id, orig_system_bill_customer_id,
quantity, unit_selling_price,
term_id, taxable_flag, amount_includes_tax_flag,
set_of_books_id, org_id,
tax_regime_code, tax, tax_status_code,
tax_rate_code, tax_jurisdiction_code, tax_rate)
VALUES
(‘PRISM’, ‘INVOICE123’, 'TAX LINE’',
Company Confidential - For internal use only

P a g e | 26
 September 8, 2014

‘PRISM’, 'INVOICE123', 'INVOICE LINE',

20.00, ‘PRISM’, TAX LINE,
'User', ‘GBP’, 3627,
'Migrated Invoice 123', '31-JUL-2014', 'TAX',
1088, 2040,
null, null,
1514, null, null,
2024, 85,
'GB VAT', 'GB VAT', ‘GB VAT STANDARD’,
'GB VAT STANDARD 20%', 'GB VAT', 20.00);

For some fields, constant values are passed and for other fields values need to be provided that tie in with the
setup steps within AR.

 INTERFACE_LINE_CONTEXT - identifies the Transaction Flexfield used by the interface data; this helps
AutoInvoice understand what data is being passed in the interface table's fields. The value here ties
in with the setup, where a Line Transaction Flexfield of ‘PRISM’ has been created and will be used for
data migration.

 INTERFACE_LINE_ATTRIBUTE1 and INTERFACE_LINE_ATTRIBUTE2 - the combination of values in

these two fields uniquely identify the transaction being migrated.

 AMOUNT - this field contains the value of the transaction; pass in a constant. This value should be
the product of the numbers that are passed in for QUANTITY * UNIT_SELLING_PRICE.

 BATCH_SOURCE_NAME - the value specified here identifies the transaction batch source to be used
by AutoInvoice when interfacing this transaction.

 CONVERSION_RATE - For non-functional currency transactions, this field would contain the exchange
rate value.

 CONVERSION_TYPE - Specify the conversion rate type.

 CURRENCY_CODE - Indicate the currency code of the transaction.

 CUST_TRX_TYPE_ID - identifies the ID associated to the transaction type.

 DESCRIPTION - enter a line item description.

 GL_DATE - the value specified here will be used by AutoInvoice as the GL_DATE of the transaction.
Typically the period in which this GL_DATE value falls should be an open period.

 LINE_TYPE - indicates the type of line this interface data defines.

 ORIG_SYSTEM_BILL_ADDRESS_ID and ORIG_SYSTEM_BILL_CUSTOMER_ID - identifies the Address ID

and Customer ID associated to the invoice.

Company Confidential - For internal use only

P a g e | 27
 September 8, 2014

 QUANTITY - specify the number of items.

 UNIT_SELLING_PRICE - specify the price of each item.

 TERM_ID - identifies the term ID associated with the Payment Terms of the invoice.

 TAXABLE_FLAG - indicates whether or not the transaction is taxable.

 AMOUNT_INCLUDES_TAX_FLAG - indicates whether or not the amount is inclusive of taxes.

 SET_OF_BOOKS_ID - identifies the Set of Books ID associated to the Operating Unit for the
transaction that is being created.

 ORG_ID - indicates the ID of the Operating Unit against which this transaction is created.

Company Confidential - For internal use only

P a g e | 28