Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Auto Invoice: Transaction Flexfield

Posted on May 26th, 2007 by Sanjit Anand ||Email This Post Email This Post

Have you tried OracleappsHub in ipad/iphone/smart Phone? Don't wait. try it today

Why set up is important for transaction flex field in autoinvoice? Does my Autoinvoice get failed if I would not do set up or not passing information for Transaction flex field? Yes, You can’t. The way the auto invoicing works is designed it worked to Uniquely identify for each transaction.

Then what are those Transaction Flex Fields?

Transaction flexfields are descriptive flexfields that AutoInvoice uses to identify transactions and transaction lines. Oracle Receivables lets you determine how you want to build your transaction flexfield structure and what information you want to capture. There are four types of transaction flexfields:

  • Line Transaction Flexfield
  • Reference Transaction Flexfield
  • Link-To Transaction Flexfield
  • Invoice Transaction Flexfield

The key point is the Line Transaction Flexfield must be defined if AutoInvoice is being used. The Line Transaction Flexfield can be used to reference and link to other lines because the Line Transaction Flexfield is unique for each transaction line. AutoInvoice always uses the Line Transaction Flexfield structure for both the Link-to and Reference information when importing invoices. It is only necessary to explicitly define the Link-to, Reference, and Invoice Transaction Flexfield structures if this information is to be displayed on a custom window.

You must define both the line-level and header-level Transaction Flexfield. To define the line-level Transaction Flexfield, query ‘Line Transaction Flexfield’ in the Title field of the Descriptive Flexfield Segments window and enter the context and segments associated with this Transaction Flexfield. To define the Transaction Flexfield at the header-level, query ‘Invoice Transaction Flexfield’ and enter the context and segments associated with this Transaction Flexfield. All segments in the line level transaction flexfield that refer to header information must also exist in the header level transaction flexfield. For example if you define a line-level Transaction Flexfield with 4 segments and only the last 2 segments refer to line-level information, define the header Transaction Flexfield using the first two segments.

Where to setup
AR gives you the option of using QuickPicks to display reference information for imported invoices. You can use the System Profile Option AR: Transaction Flexfield QuickPick to select the Transaction Flexfield Segment you want to display in Invoice QuickPicks throughout Oracle Receivables.
1

Business Case:

Lets say my autoinvoice having two sources,

1.More4Apps – where data is coming from excel based More4apps.
2.PROJECTS INVOICES – for Creating Project invoices.

So to process these, we have set up like this:

If Source is More4Apps then required INTERFACE_LINE_ATTRIBUTE1 till 2 (Fig :2)
If source is PROJECTS INVOICES then required INTERFACE_LINE_ATTRIBUTE1 till 8 (Fig :3)
11

Fig 2: Setup for Fisrt source as above

12

Fig 3: Setup for second source as above

What is mean, pretty simple based out of source the respective column should be populated. At the time of validation auto invoice will try to validate first the DFF field, based out of Context Value, The value in context field would be the same which appears while defining. And the process should take the value as reference and create a transaction in the AR.

Related Posts

Posted in 11i, EBS Suite, Finance, Oracle Receivable | 7 Comments »Email This Post Email This Post |

Have you tried OracleappsHub in ipad/iphone/smart Phone? Don't wait. try it today
7 Responses
  1. Sachin Says:

    Could some one explain what exactly are LINE-LEVEL and HEADER-LEVEL

  2. Shrikant Naik Says:

    Good

  3. Abhishek Says:

    Thanks for the information. My doubts were cleared

  4. Krist Says:

    I still don’t understand whats the different usage of INTERFACE_LINE_CONTEXT & LINK_TO_LINE_CONTEXT.

    What should I define there ?

    Thank you

  5. Sanjit Anand Says:

    INTERFACE_LINE_CONTEXT & LINK_TO_LINE_CONTEXT are flex field set up that you can extend to integrate with your external billing system or any other oracle module like OM, PA like wise.

    In simple word you can understand how much information you want to populate from external system/inside products

    Take a case, I have a externall billing system, The need is to capatured the information for REV Line with these 3 information, thats why I have to used 3

    take this 2 case
    Here is how we want to bring the fields in Oracle INTERFACE_LINE_ATTRIBUTE1..3 and for tax line i need to capture what are my rev line , in that case i need to utilize LINK_TO_LINE_ATTRIBUTE1 ..3 to tag with my rev line from source.

    here is example which explains two cases:

    Case 1: For REV Line
    INTERFACE_LINE_CONTEXT ‘SMG Billing’
    INTERFACE_LINE_ATTRIBUTE1 ‘10023’
    INTERFACE_LINE_ATTRIBUTE2 ’01’
    INTERFACE_LINE_ATTRIBUTE3 ‘LINE’

    LINK_TO_LINE_CONTEXT null
    LINK_TO_LINE_ATTRIBUTE1 null
    LINK_TO_LINE_ATTRIBUTE2 null
    LINK_TO_LINE_ATTRIBUTE3 null

    Case 2 : Tax Line
    INTERFACE_LINE_CONTEXT ‘SMG Billing’
    INTERFACE_LINE_ATTRIBUTE1 ‘10023’
    INTERFACE_LINE_ATTRIBUTE2 ’01’
    INTERFACE_LINE_ATTRIBUTE3 ‘TAX’

    LINK_TO_LINE_CONTEXT ‘SMG Billing’
    LINK_TO_LINE_ATTRIBUTE1 ‘10023’
    LINK_TO_LINE_ATTRIBUTE2 ’01’
    LINK_TO_LINE_ATTRIBUTE3 ‘LINE’

    In this example attribute 1 is an order number, 2 is the line number and attribute 3 is simply used to differentiate between invoice lines
    and tax lines. The combination of the three attributes is unique, and the Invoice line attributes have been repeated on the tax line in the link to line attribute fields.

  6. shahu Says:

    Hi Sanjit Anand….

    Very good solution

  7. juwan Says:

    How do you populate the Transaction Information Flexfield (the second invoice header flexfield on the Transactions screen) using AutoInvoice?

    Is it possible to populate the Transaction Information flexfield at all using AutoInvoice?

Leave a Comment

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.