1. Implementing Order Management
  2. Specify Transaction Types When You Integrate Order Management with Oracle Receivables

Specify Transaction Types When You Integrate Order Management with Oracle Receivables

A sales order might include details you use to determine accounting for a financial transaction, such as an invoice memo, or a debit and credit memo.

You can create an order management extension that sets the value for the AR Transaction Type attribute according to details from the sales order, such as business unit, order type, line type, or item.

Assume you must create an invoice in Oracle Receivables with a different transaction type for each sales order. You can use AR Transaction Type to specify the accounting entries to use for the transaction.

Customer Name

Project Type

Sales Order Number

AR Transaction Type

Revenue Account

Customer 1

Support

Sales Order 1

Application Support

1111 Income from Application Support

Customer 2

Implementation

Sales Order 2

Oracle Implementation

1112 Income from Implementation

Note

  • Oracle Receivables doesn't set the default value for Receivables Transaction.

  • Here's the predefined behavior that Order Management uses to set the default value.

    Are You Fulfilling or Returning Order Lines?

    Transaction Type

    Fulfilling

    Invoice

    You can create an extension to modify this behavior.

    Returning

    Credit Memo

    Don't modify this behavior. You must use the Credit Memo transaction type for each return line.

  • If you specify AR Transaction Type in your extension, then write your extension so it uses one of these combinations of attributes:

    Attributes

    Description

    Line category and business unit

    Use this combination when you must assign the business unit according to the transaction type.

    • Use the same AR Transaction Type, such as ARTT-Invoice1, for order lines you're fulfilling.

    • Use the same AR Transaction Type, such as ARTT-Credit1, for return order lines.

    Use one of these combinations.

    • Line type and line category, and business unit

    • Line type or line category, and business unit

    Use this combination when you must assign the business unit according to transaction types.

    • Use more than one AR Transaction Type for order lines that you're fulfilling.

    • Use more than one AR Transaction Type for return order lines.

    Order category and business unit

    Use this combination when your source system sends a source order that includes return order lines but doesn't include order lines that you're fulfilling.

    Order type and business unit

    Use this combination when a sales order that you create in the Order Management work area includes return order lines but doesn't include order lines that you're fulfilling.

Create an Extension

Run an SQL to get the value you need for the Billing Transaction Type ID attribute.

SELECT  distinct LOOKUP_TYPE,
        LOOKUP_CODE                   
FROM    fusion.FND_LOOKUP_VALUES_TL
WHERE   LOOKUP_TYPE = 'ORA_DOO_ORDER_TYPES'
order by 1, 2
SELECT  RaCustTrxTypesAll.NAME                ,
       RaCustTrxTypesAll.CUST_TRX_TYPE_SEQ_ID,
       RaCustTrxTypesAll.SET_ID              ,
       SetIdSetPEO.SET_NAME                  ,
       SetIdSetPEO.SET_ID AS SET_ID1         ,
       RaCustTrxTypesAll.CUST_TRX_TYPE_ID    ,
       RaCustTrxTypesAll.END_DATE            ,
       RaCustTrxTypesAll.START_DATE          ,
       RaCustTrxTypesAll.TYPE
FROM    fusion.ra_cust_trx_types_all RaCustTrxTypesAll,
       fusion.fnd_setid_sets_vl SetIdSetPEO
WHERE   RaCustTrxTypesAll.SET_ID    = SetIdSetPEO.SET_ID
       AND RaCustTrxTypesAll.Type IN ('INV','CM','DM')

Assume the query returns a value of 1 for the Billing Transaction Type ID.

Create an extension that implements this logic:

If the Inventory Item Id attribute on the order line is 149, then set the Transaction Type attribute to 1.

  1. Test your set up.

    • Navigate to the Order Management work area, then create a new sales order.

    • Add an item that references the inventory item you specified earlier in this procedure.

    • Set the Receivables Transaction attribute on the order line, then click Submit.

    • Verify that Oracle Receivables correctly categorized the transaction.

Set Transaction Type Before You Convert

You can run your extension only on some events, such as when you select the business unit, customer, or order type, or when you add an order line.

Set the Validate Transaction Type's Sign Against Amount parameter to make sure the numeric sign (+ or -) for the receivables transaction on the order line matches the amount's sign on that line. For example:

  • if the Receivables Transaction attribute contains Credit Memo, and if the amount isn't negative, then this parameter prevents you from submitting the order.

See Manage Order Management Parameters.

Related Topics