Line Transactions Auto Import

6/20/2017 Document 1358419.
Setting Up Receivables Descriptive Flexfields In Oracle Fusion Receivables (Doc ID 1358419.1)
In this Document
Goal
AutoInvoice Setup for Fusion Receivables: A Case Study Using a Simple Script > Note 1358419.1
Fix
1. Creating a Line Transaction Flexfield
2. Creating a Linkto Transaction Flexfield
3. Creating a Reference Transaction Flexfield
4. Creating an Invoice Transaction Flexfield
5. Additional examples
6. Seeded Line Transaction Flexfield information
References
APPLIES TO:
Oracle Fusion Receivables Version 1.0Beta and later
Information in this document applies to any platform.
Executable:RAXTRX Autoinvoice Import Program
GOAL
AutoInvoice Setup for Fusion Receivables: A Case Study Using a Simple Script > Note 1358419.1
There are four types of transaction flexfields used by AutoInvoice:
Line Transaction Flexfield
Linkto Transaction Flexfield
Reference Transaction Flexfield
Invoice Transaction Flexfield
If you are using Autoinvoice, it is mandatory to define: (1) Line Transaction Flexfield (line level information) and (2) Invoice
Transaction Flexfield (header level information). If you do not explicitly define Linkto and Reference Transaction flexfields,
Autoinvoice will use the flexfield structure of the Line Transaction Flexfield to determine LinkTo and Reference information.
This document discusses the various transaction flexfields and demonstrates how to setup each of the four types. The setup for
Line Transaction Flexfield is discussed in most detail as it is required for the case study in Note 1345332.1, AutoInvoice Setup
for Fusion Receivables: A Case Study Using a Simple Script.
FIX
1. Creating a Line Transaction Flexfield
You must define the Line Transaction Flexfield if you are implementing AutoInvoice. Line Transaction Flexfields are unique for
each record in the interface table and therefore can be used as record identifiers.
When defining your Line Transaction Flexfield consider the following:
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=16q7c2sxe7_449&id=1358419.1 1/16
6/20/2017 Document 1358419.1
Unique Identification
You must define the combination of segment values to uniquely identify each incoming transaction line. Each line
must be unique in RA_INTERFACE_LINES_ALL. These unique lines are the basis of the data created in
RA_CUSTOMER_TRX_LINES_ALL which contains line items for existing chargebacks, credit memos, debit memos,
deposits, and invoices.
Grouping
You may also use Grouping Rules to group the segments of the Line Transaction Flexfield, such that identical
data in some attributes will create a single invoice.
Ordering
You may use the segment values in Line Transaction Flexfield segments with Line Ordering Rules to change the
sequence of invoice lines grouped into an invoice.
Information
You can view the Line Transaction Flexfield in your invoice lines. You can define segments of the flexfield to
contain descriptive information. You can later use this descriptive information to query and find your invoices in
the Transactions Workbench.
Use columns INTERFACE_LINE_ATTRIBUTE115 and INTERFACE_LINE_CONTEXT
The value you provide in INTERFACE_LINE_CONTEXT allows Autoinvoice to verify that you have provided the correct number
of segments in your interface data, to match the segments you defined in your Line Transaction Flexfield.
The following are some examples of Line Transaction Flexfields that are seeded by Oracle for AutoInvoice:
Contract Internal Invoices
Contract Invoices
Distributed Order Orchestration
Global Procurement
Intercompany
Global Intercompany
Detailed information on the segments associated to these seeded flexfields are provided below.
You can define as many Line Transaction Flexfield structures as you need to bring in transactions from outside sources.
User: AR Super Administrator
Navigation: Navigator > Setup and Maintenance
a. In Search Tasks field, enter 'Receivables Descriptive Flexfield', then click on the arrow button.
In the Search Results, click on go to Task icon against Manage Receivables Descriptive Flexfields.
b. In Search Tasks field, enter 'Line Transaction' in the Name, then click on Search button.
In the Search Results, click on Line Transaction and click on the Pencil Icon .
6/20/2017 Document 1358419.1
c. In the resulting screen click on the Manage Contexts button to to edit/create a Line Transaction Flexfield structure.You could
search to edit any existing descriptive flexfield or click on the create icon under Search Results.
d. Click on the Create Icon to create a New Context of the type Line Transactions
6/20/2017 Document 1358419.1
e. Give the Display name, Context Code and the description for the new descriptive flexfield structure and click on Save.
f. Now click on create icon under the Context Sensitive Segments to add the new segments and give the Columns that the
segments would use.
g. Enter the Segment Name, Code, Value Set, Table Column, Prompt, Display Height and Display Type.Click on Save and close.
6/20/2017 Document 1358419.1
h. Repeat the process for the other segments.
Click on the Create Icon.
i. Enter the second segment details and click on save and close.
6/20/2017 Document 1358419.1
j. Once you have added all the segments you wish to add click on save and close.
k. You can now see all the context of the type Line Transactions. Click on Done .
6/20/2017 Document 1358419.1
l. Now you need to validate the Descriptive flexfield you have created. Click on the flexfield you have created .
m. From the Actions Lov Select Validate.
6/20/2017 Document 1358419.1
n. Review the Results . You should see that the validation has passed. Click on ok .Your new transaction flexfield is ready for
use.
o. Deploy the flexfield
To use a flexfield at runtime, the flexfield must have been deployed at least once. Deployment generates or refreshes the
Application Development Framework (ADF) business component objects that render the flexfield in a user interface. Flexfields
are deployed for the first time during the application provisioning process.
You can deploy a flexfield to a sandbox for testing or to the mainline for use.
When deploy the Line Transaction Descriptive Flexfield (DFF) get an error which says Entity Usage list is
empty.
ERROR

Entity Usage List is empty
Deployment Aborted.
This was addressed in an Internal Bug 12433199 .(Fix to be included in Version 2)
The error was due to incorrect seeded data . Also Interface Line Transaction DFF is not implemented on the Line Detail
page.
Development has confirmed that the errors are benign. Line Transaction Flex do not need to be deployed, since the LTFs
are not used on any User Interface(UI); those are used only in Auto Invoice. Saving the definition will suffice. Thus the
error you get on deployment can be ignored. The error happens because there is no UI component using the LTF (there
should be no error, but there is).
6/20/2017 Document 1358419.1
A simple example of using this flexfield is shown below:
LINE_TYPE INTERFACE_LINE_CONTEXT INTERFACE_LINES_ATTRIBUTE1 INTERFACE_LINES_ATTRIBUTE2
LINE TIP ORDER 1 LEGACY LINE 1
The data from the Line Transaction flexfield is stored in RA_CUSTOMER_TRX_LINES_ALL.INTERFACE_LINE_ATTRIBUTE115
and
RA_CUSTOMER_TRX_LINES_ALL.INTERFACE_LINE_CONTEXT.
2. Creating a Linkto Transaction Flexfield
LinkTo Transaction Flexfields have the same structure as the Line Transaction Flexfield. LinkTo Transaction Flexfields are
used to relate rows within a batch of interface table data to each other. This is used to import tax and freight charges
associated to specific transaction lines.
Use columns LINK_TO_LINE_ATTRIBUTE115 and LINK_TO_LINE_CONTEXT to link a Freight or Tax Line to a particular
transaction line.
b. In Search field, enter 'LinkTo Transaction' in the Name, then click on Search button.
In the Search Results, click on LinkTo Transaction and click on the Pencil Icon .
c. In the resulting screen click on the Manage Contexts button to to edit/create a LinkTo Transaction Flexfields structure.
6/20/2017 Document 1358419.1
d. You could search to edit any existing descriptive flexfield or click on the create icon under Search Results.
e. Give the Display name, Context Code and the description for the new descriptive flexfield structure and click on Save.
f. Now click on create icon under the Context Sensitive Segments to add the new segments and give the Columns that the
segments would use.
g. Enter the values for the segment and click on save and close
h. Repeat the steps f, g above for adding additional segments
Note: Since the LinkTo Transaction Flexfield should contain the Line Transaction Flexfield data of the transaction line you are
linking it to, the structure should be similar to the Line Transaction Flexfield. In this example, this Linkto Transaction Flexfield
is meant to be used in conjunction with the Line Transaction Flexfield above.
The rest of the steps are similar to the ones described for Line Transaction Flexfield.
i. Save your work and exit.Once this has completed your new transaction flexfield is ready for use.
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_LINE_CONTEXT INTERFACE_LINES_ATTRIBUTE1 INTERFACE_LINES_ATTRIBUTE2
1 LINE TIP ORDER 1 LEGACY LINE 1
2 TAX TIP ORDER 1 LEGACY LINE 2
The values in the LINK_TO_ATTRIBUTE* fields in row 2, contain the values in the INTERFACE_ATTRIBUTE* fields in row 1.
This indicates that row 2 contains the TAX data for row 1 LINE.
The data from the Linkto Transaction flexfield is stored in RA_CUSTOMER_TRX_LINES_ALL.LINK_TO_ATTRIBUTE115 and
RA_CUSTOMER_TRX_LINES_ALL.LINK_TO_CONTEXT.
3. Creating a Reference Transaction Flexfield
6/20/2017 Document 1358419.1
Reference Transaction Flexfields have the same structure as the Line Transaction Flexfields, this is used to apply a credit
memo to an invoice, or associate an invoice to a commitment within the same interface batch data.
Use the REFERENCE_LINE_ATTRIBUTE115 and REFERENCE_LINE_CONTEXT columns to contain the line transaction flexfield
values of the invoice or commitment this transaction is associated to.
b. In Search field, enter 'Reference Transaction' in the Name, then click on Search button.
In the Search Results, click on Reference Transaction and click on the Pencil Icon .
c. In the resulting screen click on the Manage Contexts button to to edit/create a Reference Transaction Flexfields structure.
You could search to edit any existing descriptive flexfield or click on the create icon under Search Results.
d. Give the Display name, Context Code and the description for the new descriptive flexfield structure and click on Save.Next
click on create icon under the Context Sensitive Segments to add the new segments and give the Columns that the segments
would use.
e. Enter the values for the segment and click on save and close
f. Repeat the steps d,e above for adding additional segments
The value under Column is not completely shown, the first row has the value REFERENCE_LINE_ATTRIBUTE1 and the second
row has the value REFERENCE_LINE_ATTRIBUTE2.
[Note: Since the Reference Transaction Flexfield should contain the Line Transaction Flexfield data of the transaction you
are referencing, the structure should be similar to the Line Transaction Flexfield. In this example, this Reference
Transaction Flexfield is meant to be used in conjunction with the Line Transaction Flexfield above.]
Save your work and exit.Once this has completed your new transaction flexfield is ready for use.
The rest of the steps are similar to the ones described in the Line Transaction Flexfield section above.
Flexfield.
1 LINE TIP ORDER 3 LEGACY LINE 1
6/20/2017 Document 1358419.1
This data interfaces a credit memo against the invoice in the interface table that has INTERFACE_LINE* fields = ORDER 1 and
LEGACY LINE 1.
The data from the Reference Transaction flexfield is stored in
RA_CUSTOMER_TRX_LINES_ALL.REFERENCE_LINE_ATTRIBUTE115 and
RA_CUSTOMER_TRX_LINES_ALL.REFERENCE_LINE_CONTEXT.
4. Creating an Invoice Transaction Flexfield
Invoice Transaction Flexfield is for header level segments. If you define this flexfield, then the segments you use here should
also be included in the AutoInvoice grouping rules.
Use columns HEADER_ATTRIBUTE115 and HEADER_ATTRIBUTE_CATEGORY.
The flexfields captured here are stored at the transaction header level as opposed to the transaction line level used by the
previous 3 flexfields.
If you are interfacing data from Order Management, the data you populate in the Order header transaction flexfield
(Transaction Flexfield for Application = Order Management, Title = Additional Header Information) is interfaced into
RA_INTERFACE_LINES.HEADER_ATTRIBUTE_CATEGORY + HEADER_ATTRIBUTE115.
b. In Search field, enter 'Invoice Transaction' in the name, then click on Search button.
In the Search Results, click on Invoice Transaction Flexfield and click on the Pencil Icon .
c. In the resulting screen click on the Manage Contexts button to to edit/create a Invoice Transaction Flexfield structure.
You could search to edit any existing descriptive flexfield or click on the create icon under Search Results.
d. Give the Display name, Context Code and the description for the new descriptive flexfield structure and click on Save.Next
click on create icon under the Context Sensitive Segments to add the new segments and give the Columns that the segments
would use.
e. Enter the values for the segment and click on save and close
f. Repeat the steps d,e above for adding additional segments
The value under Column is not completely shown, the rows have the value INTERFACE_HEADER_ATTRIBUTE1 to
6/20/2017 Document 1358419.1
INTERFACE_HEADER_ATTRIBUTE3.
Note: The Invoice Transaction Flexfield should contain data that is unique per transaction (and not per transaction line). The
not
structure of this flexfield does need to correspond to the Line Transaction Flexfield data.
The rest of the steps are similar to the ones described for the Line Transaction Flexfield section.
Flexfield.
1 LINE ORDER 1 LEGACY LINE 1 TIP INV
2 LINE ORDER 1 LEGACY LINE 2
The data creates a 2line invoice with header information from Row1 getting saved into RA_CUSTOMER_TRX_ALL.
The data from the Invoice Transaction Flexfield are stored in RA_CUSTOMER_TRX_ALL.ATTRIBUTE115 and
RA_CUSTOMER_TRX_ALL.ATTRIBUTE_CATEGORY.
5. Additional examples
The following provides additional examples of how transaction flexfields capture data to reflect Freight, Taxes, credit memos
and commitments.
example 1:
Following shows interface data for an Invoice against a commitment. It demonstrates the use of Freight (at the header level),
and Tax.
ROW LINE INTERFACE_ INTERFACE_ INTERFACE_ LINK_TO_ LINK_TO_ LINK_TO_

TYPE LINE_CONTEXT LINES_ATTRIBUTE1 LINES_ATTRIBUTE2 CONTEXT ATTRIBUTE1 ATTRIBUTE2
1 LINE SERVICE A L1
2 LINE SERVICE A L2
3 FREIGHT SERVICE A H1
4 TAX SERVICE A L3 SERVICE A L1
Notes:
1) Each record in the interface table is uniquely identified by the combination of the values in INTERFACE_LINE_CONTEXT and
the enabled segments INTERFACE_LINES_ATTRIBUTE115.
In the above example 2 segments are enabled for the Context SERVICE,
therefore the combination of
INTERFACE_LINE_CONTEXT + INTERFACE_LINES_ATTRIBUTE1 + INTERFACE_LINES_ATTRIBUTE2 should be unique.
2) Tax records always have to be linked to a line record. In the above example, the TAX record in row 4 is linked to the LINE in
Row 1 by populating the LINK_TO* fields with the values contained in the INTERFACE_* fields of the row the TAX is linked to.
3) If Freight is defined at the header level then no need to populate the LINK_TO* fields, as shown in the above example. If
however, FREIGHT is associated to one of the lines, then you should populate the LINK_TO* fields with the value of the
INTERFACE_* fields of the LINE to which the FREIGHT is linked to.
6/20/2017 Document 1358419.1
4) This sample invoice is against a commitment, you can reflect that using either of 2 options: (1) you can populate the
REFERENCE_LINE_ID with the CUSTOMER_TRX_LINE_ID of the commitment, as shown above, the commitment is against
CUSTOMER_TRX_LINE_ID = 1234, or (2) populate the REFERENCE_* fields with the values in INTERFACE_* from the
commitment's record.
example 2:
The following shows interface data for a credit memo that credits the FREIGHT and the first LINE of the previous invoice. It
will be represented in the interface table as follows:
ROW LINE INTERFACE_ INTERFACE_ INTERFACE_ REFERENCE_ REFERENCE_

TYPE LINE_CONTEXT LINES_ATTRIBUTE1 LINES_ATTRIBUTE2 CONTEXT LINE_ATTRIBUTE1
1 LINE SERVICE A L4 SERVICE A
2 FREIGHT SERVICE A H2 SERVICE A
Notes:
1) The credit memo is associated to the invoice by populating the REFERENCE* fields with the value of the INTERFACE_* fields
of the invoice being credited.
2) Another option of associating a credit memo to an invoice is by populating the REFERENCE_LINE_ID field with the value of
the CUSTOMER_TRX_LINE_ID of the invoice that is being credited
example 3:
The following shows interface data for an OnAccount credit memo.
ROW LINE INTERFACE_ INTERFACE_ INTERFACE_ REFERENCE_ REFERENCE_ REFERE

TYPE LINE_CONTEXT LINES_ATTRIBUTE1 LINES_ATTRIBUTE2 CONTEXT LINE_ATTRIBUTE1 LINE_AT
1 LINE SERVICE B L1
Notes:
1) AutoInvoice assumes all records with transaction type associated to a Credit Memo, to be OnAccount credits if there are no
values filled in the REFERENCE_LINE_ID column or the REFERENCE_* fields. In the above example, by leaving the
REFERENCE* fields null, this record will be interfaced as an OnAccount Credit memo.
6. Seeded Line Transaction Flexfield information
Listed below are the more popularly used seeded Line Transaction Flexfields in AutoInvoice. The table shows the Context
Name (INTERFACE_LINE_CONTEXT) and the values in each of the segments associated to the Line Transaction Flexfield.
Context Name RA_INTERFACE_LINES_ALL field Description
Contract Internal Invoices INTERFACE_LINE_ATTRIBUTE1 Contract Number
INTERFACE_LINE_ATTRIBUTE2 Contract Id
INTERFACE_LINE_ATTRIBUTE3 Draft Invoice Number
INTERFACE_LINE_ATTRIBUTE4 Contract organization
INTERFACE_LINE_ATTRIBUTE5 Line ID
6/20/2017 Document 1358419.1
INTERFACE_LINE_ATTRIBUTE6 Type
INTERFACE_LINE_ATTRIBUTE7 Receiving Business Unit
INTERFACE_LINE_ATTRIBUTE8 Receiving Project Number
Contract Invoices INTERFACE_LINE_ATTRIBUTE1 Contract Number
INTERFACE_LINE_ATTRIBUTE2 Contract Id
INTERFACE_LINE_ATTRIBUTE3 Draft Invoice Number
INTERFACE_LINE_ATTRIBUTE4 Contract organization
INTERFACE_LINE_ATTRIBUTE5 Line ID
INTERFACE_LINE_ATTRIBUTE6 Type
Distributed Order Orchestration INTERFACE_LINE_ATTRIBUTE1 Source Order Number
INTERFACE_LINE_ATTRIBUTE2 Source Order System
INTERFACE_LINE_ATTRIBUTE3 DOO Order Number
INTERFACE_LINE_ATTRIBUTE4 Fulfillment Line ID
INTERFACE_LINE_ATTRIBUTE5 Price Adjustment ID
INTERFACE_LINE_ATTRIBUTE6 Delivery Name
INTERFACE_LINE_ATTRIBUTE7 WayBill Number
INTERFACE_LINE_ATTRIBUTE8 Bill of Lading Number
INTERFACE_LINE_ATTRIBUTE9 Customer Item
INTERFACE_LINE_ATTRIBUTE10 Fulfill Line Split Reference
INTERFACE_LINE_ATTRIBUTE11 Source Schedule Number
INTERFACE_LINE_ATTRIBUTE12 Fulfillment Line Number
Global Procurement INTERFACE_LINE_ATTRIBUTE1 PO Number
INTERFACE_LINE_ATTRIBUTE2 PO Line Number
INTERFACE_LINE_ATTRIBUTE3 Receiving Inventory Org
INTERFACE_LINE_ATTRIBUTE4 Purchasing Operating Unit
INTERFACE_LINE_ATTRIBUTE5 Receiving Operating Unit
INTERFACE_LINE_ATTRIBUTE6 PO Line Location ID
INTERFACE_LINE_ATTRIBUTE7 Reference
INTERFACE_LINE_ATTRIBUTE8 Create AP Invoice
Intercompany INTERFACE_LINE_ATTRIBUTE1 Order Number
INTERFACE_LINE_ATTRIBUTE2 Order Line Number
INTERFACE_LINE_ATTRIBUTE3 Shipping Warehouse
INTERFACE_LINE_ATTRIBUTE4 Selling Operating Unit
INTERFACE_LINE_ATTRIBUTE5 Shipping Operating Unit
INTERFACE_LINE_ATTRIBUTE6 Order Line ID
INTERFACE_LINE_ATTRIBUTE7 Reference
6/20/2017 Document 1358419.1
INTERFACE_LINE_ATTRIBUTE8 Organization ID
INTERFACE_LINE_ATTRIBUTE9 Create AP Invoice
INTERFACE_LINE_ATTRIBUTE10 Price Adjustment ID/Order ID
Global Intercompany INTERFACE_LINE_ATTRIBUTE1 batch_id
INTERFACE_LINE_ATTRIBUTE2 trx_id
INTERFACE_LINE_ATTRIBUTE3 line_id
INTERFACE_LINE_ATTRIBUTE4 batch_number
REFERENCES
NOTE:1358419.1 Setting Up Receivables Descriptive Flexfields In Oracle Fusion Receivables
NOTE:1345332.1 AutoInvoice Setup for Fusion Receivables: A Case Study Using a Simple Script
Didn't find what you are looking for?

Line Transactions Auto Import

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Line Transactions Auto Import

Загружено:

Авторское право:

Доступные форматы

6/20/2017 Document 1358419.

LINE_TYPE INTERFACE_LINE_CONTEXT INTERFACE_LINES_ATTRIBUTE1 INTERFACE_LINES_ATTRIBUTE2

LINE TIP ORDER 1 LEGACY LINE 1

ROW LINE_TYPE INTERFACE_LINE_CONTEXT INTERFACE_LINES_ATTRIBUTE1 INTERFACE_LINES_ATTRIBUTE2

1 LINE TIP ORDER 1 LEGACY LINE 1

2 TAX TIP ORDER 1 LEGACY LINE 2

ROW LINE_TYPE INTERFACE_LINE_CONTEXT INTERFACE_LINES_ATTRIBUTE1 INTERFACE_LINES_ATTRIBUTE2

1 LINE TIP ORDER 3 LEGACY LINE 1

ROW LINE_TYPE INTERFACE_LINE_CONTEXT INTERFACE_LINES_ATTRIBUTE1 INTERFACE_LINES_ATTRIBUTE2

1 LINE ORDER 1 LEGACY LINE 1 TIP INV

2 LINE ORDER 1 LEGACY LINE 2

ROW LINE INTERFACE_ INTERFACE_ INTERFACE_ LINK_TO_ LINK_TO_ LINK_TO_

4 TAX SERVICE A L3 SERVICE A L1

ROW LINE INTERFACE_ INTERFACE_ INTERFACE_ REFERENCE_ REFERENCE_

1 LINE SERVICE A L4 SERVICE A

2 FREIGHT SERVICE A H2 SERVICE A

ROW LINE INTERFACE_ INTERFACE_ INTERFACE_ REFERENCE_ REFERENCE_ REFERE

Context Name RA_INTERFACE_LINES_ALL field Description

Contract Internal Invoices INTERFACE_LINE_ATTRIBUTE1 Contract Number

Contract Invoices INTERFACE_LINE_ATTRIBUTE1 Contract Number

Distributed Order Orchestration INTERFACE_LINE_ATTRIBUTE1 Source Order Number

Global Procurement INTERFACE_LINE_ATTRIBUTE1 PO Number

Intercompany INTERFACE_LINE_ATTRIBUTE1 Order Number

Global Intercompany INTERFACE_LINE_ATTRIBUTE1 batch_id

Вам также может понравиться