3
Autoinvoice Topic 1 Line Transaction Flexfields The Line Transaction Flexfield serves the following purposes: 1. The Line Transaction Flexfield is used by AutoInvoice to validate that lines will not be imported into Oracle Receivables more than once. The combination of the values for the line transaction flexfield must be unique for each row. You can think of the line transaction flexfield as the primary key for ra_interface_lines_all. Many of the rules that apply to a table’s primary key apply to the Line Transaction Flexfield. Enabled segments for the flexfield context that is used can not be null. The combination of these segments plus the context must be unique. 2. AutoInovice uses the Line Transaction Flexfield to link three autoinvoice tables together. In this way the Line Transaction Flexfield may be viewed as a foreign key in ra_interface_salescredits_all and ra_interface_distributions_all. Remember that the line_transaction_flexfield is the primary key for ra_interface_lines_all. 3. The Line Transaction Flexfield may also be used to add other descriptive information to the invoice. Line Transaction Flexfield Setup: Navigation: In the AR Manager Responsibility, navigate to Setup => Financials => Flexfields => Descriptive => Segments Query the Line Transaction flexfield.

Autoinvoice - Line Transaction Flexfield

Embed Size (px)

DESCRIPTION

Happy Reading

Citation preview

Page 1: Autoinvoice - Line Transaction Flexfield

Autoinvoice Topic 1

Line Transaction Flexfields

The Line Transaction Flexfield serves the following purposes:

1. The Line Transaction Flexfield is used by AutoInvoice to validate that lines will not be imported into Oracle Receivables more than once. The combination of the values for the line transaction flexfield must be unique for each row.

You can think of the line transaction flexfield as the primary key for ra_interface_lines_all. Many of the rules that apply to a table’s primary key apply to the Line Transaction Flexfield. Enabled segments for the flexfield context that is used can not be null. The combination of these segments plus the context must be unique.

2. AutoInovice uses the Line Transaction Flexfield to link three autoinvoice tables together. In this way the Line Transaction Flexfield may be viewed as a foreign key in ra_interface_salescredits_all and ra_interface_distributions_all. Remember that the line_transaction_flexfield is the primary key for ra_interface_lines_all.

3. The Line Transaction Flexfield may also be used to add other descriptive information to the invoice.

Line Transaction Flexfield Setup:

Navigation: In the AR Manager Responsibility, navigate to Setup => Financials => Flexfields => Descriptive => Segments

Query the Line Transaction flexfield.

Page 2: Autoinvoice - Line Transaction Flexfield

The columns on the bottom left hand side of this form are the values that will be found in the columnra_interface_lines_all.interface_line_context.

You can create a new context here. If you are using Oracle Order Entry or/and Oracle ProjectAccounting, seeded contexts are provided. There is also a seeded context for Intercompany invoices.

Next you click on segments to define your segments:

The segments below are the seeded values for context “ORDER ENTRY”:

Page 3: Autoinvoice - Line Transaction Flexfield

In this example, there are seven segments defined. This means that autoinvoice must have values for eachof the seven segments. The column names are not evident in this screen shot. The column names areinterface_line_attribute1 through interface_line_attribute7.

ra_interface_lines_all.interface_line_attribute1 must not be nullra_interface_lines_all.interface_line_attribute2 must not be nullra_interface_lines_all.interface_line_attribute3 must not be nullra_interface_lines_all.interface_line_attribute4 must not be nullra_interface_lines_all.interface_line_attribute5 must not be nullra_interface_lines_all.interface_line_attribute6 must not be nullra_interface_lines_all.interface_line_attribute7 must not be null

You can put whatever values you like in the line transaction flexfields attribute columns. The onlyrequirement is that the combination of all the attribute columns must be unique for a given row.

Suggestion: Do not add a value set to the segments defined in your line transaction flexfield. Autoinvoicedoes not validate against your value set, where the form in Oracle Receivables does validate. If you passdata in the line transaction flexfield which will not meet the requirements of your value set, you willreceive errors when navigating to the Enter Invoice screen (Transactions => Transactions), then query theinvoice and go to the lines section.