8 Setting Up Participating Applications

Oracle E-Business Suite and Oracle Transportation Management (OTM) must be set up in order for the financial process integration pack to work properly. This chapter includes the following sections:

• Section 8.1, "Setting Up Oracle Transportation Management"

• Section 8.2, "Setting Up Oracle E-Business Suite"

8.1 Setting Up Oracle Transportation Management

Note:

You must setup OTM before you use this process integration pack.

8.1.1 Setting Up Qualifiers

These qualifiers are used by OTM:

• Suppliers Integration Flow

  • ServiceProviderAliasQualifierXid = VENDOR_NAME_ALT: This qualifier value contains the alternate vendor name.

  • LocationRefnumXid = INACTIVE: This qualifier value contains the inactive date of supplier/site.

  • LocationRefnumXid = SUPPLIER_SITE_ID: This qualifier value contains the Site ID.

• Payable Invoices Integration Flow

  • ServiceProviderAliasQualifierXID = GLOG: This qualifier value contains the Supplier Number or Supplier Site Number (based on sync supplier site profile).

  • ServiceProviderAliasQualifierXID = SUPPLIER_ID: This qualifier value contains the Supplier Number (based on sync supplier site profile).

  • InvoiceRefNumQualifierXID = OP_UNIT: This qualifier value contains the AIA GUID That is ORGANIZATION_ID.COMMON value.

  • InvoiceRefNumQualifierXID = PREPAY_INV_NUMBER: This qualifier value contains the E-Business Prepayment Invoice Number

  • InvolvedPartyQualifierXID = REMIT-TO: This qualifier value contains the Remit to Supplier Number

• Receivable Invoices Integration Flow

  • InvoiceRefNumQualifierXID = OP_UNIT: This qualifier value contains the AIA GUID that is ORGANIZATION_ID.COMMON value.

  • InvolvedPartyQualifierXID = BILL-TO: This qualifier value contains the Bill to Customer Party ID.

  • InvolvedPartyQualifierXID = CUSTOMER: This qualifier value contains the Ship to Customer Party ID.

• Accruals and Reversals Integration Flow

  • ReleaseRefNumQualifierXID = OP_UNIT: This qualifier value contains the AIA GUID That is ORGANIZATION_ID.COMMON value.

For more information about qualifiers, see the Oracle Transportation Management User Guide.

8.1.2 Creating Contacts in Oracle Transportation Management

Create external systems for all inbound flows to OTM. This table lists the processes involved.

Table 8-1 Process for Creating External Systems for Inbound Flow

Process Name	External System ID
SyncCurrencyExchangeListLogisticsProvABCSImpl	CURRENCY_ESID
MergeCustomerPartyListLogisticsProvABCSImpl	MERGECUSTOMERPARTY_ESID
SyncSupplierPartyListLogisticsProvABCSImpl	SUPPLIER_ESID
SyncCustomerPartyListLogisticsProvABCSImpl	CUSTOMERPARTY_ESID

Note:

External System IDs and their corresponding processes are in the AIAConfigurationProperties.xml file.

To create external systems:

1. Log in to Oracle Enterprise Manager Fusion Middleware Control [http://<server host>:<server port>/em].

2. Click the desired process.

3. Click Show WSDL and endpoint URI.

   Figure 8-1 Creating Contacts in OTM

   
   

4. Click concrete WSDL URI and add style="document" attribute to soap:binding element.

5. Save the source on your local system.

6. Log in to OTM.

7. Go to Business Process Automation, Communication Management, Web Services and click New.

8. Click New for WSDL Document.

9. Click Document Detail.

   • Enter name for ID.

   • Upload the saved concrete WSDL.

   • Ensure Storage is set to Text and Mime Type as text/xml.

10. Click Finished.

11. Click Service Details.

    • Enter Service ID and Service Endpoint ID.

    • Enter Service Endpoint as Endpoint URI as depicted in the screen. See Section 8.1.2, "Creating Contacts in Oracle Transportation Management".

    • Enter user name and password of your weblogic server.

      Note:

      For OTM versions earlier than 6.1.2 encrypt the password before entering using Base64 encoding.

12. Click Finished.

13. Go to Business Process Automation, Communication Management, External Systems.

14. Click New.

    • Enter value for External System ID. See Section 8.1.2, "Creating Contacts in Oracle Transportation Management" for these values.

    • Select webservice created previously.

    • Select Operation as TransmissionReport.

    • Select the Service Endpoint created earlier.

15. Click Finished.

    • These steps create a contact automatically in OTM with the same name as of External System ID.

    • To verify, go to Business Process Automation, Communication Management, Contacts.

Note:

Update OTM_01.Contact_Domain Property in AIAConfigurationProperties.xml for each process with the domain in which External System is created for the corresponding process.

For more information about Oracle Transportation Management, see the Oracle Transportation Management User Guide.

8.1.3 Setting Up External Systems for Queues

To setup external systems

1. Login to OTM application.

2. Go to Business Process Automation, Communication Management, External Systems.

3. Click New.

4. Enter External System ID as AIA_PAYABLEINVOICE_AQ. Add a description

5. Enter the Queue Name as AIA_PAYABLEINVOICE_AQ under For Queue section.

   Figure 8-2 External System Manager

   
   

6. In the Out XML Profiles section, click n for New XML profile.

7. Enter Out XML Profile ID as AIA_VOUCHER_MAX.

8. Choose Default Mode as MAX.

9. Toggle Validate for Max.

   Figure 8-3 Out XML Profiles

   
   

10. Click Finished.

11. In the Out XML Profiles section, choose the XML Element ID as Voucher.

12. Click Save.

    Figure 8-4 Out XML - Profile ID and Element ID

    
    

13. Click Finished.

External systems should be defined and set up in Oracle Transportation Management (OTM) for each of the flows with the queue name:

1. AIA_PAYABLEINVOICE_AQ

2. AIA_INVOICE_AQ

3. AIA_ACCOUNTINGENTRY_AQ

8.1.4 Set up Automation Agents in Oracle Transportation Management

This section describes how to setup automation agents.

8.1.4.1 Create Order Release

1. Navigate to Business Process Automation, Agents and Milestones, Automation Agent, New.

   Figure 8-5 Agent Manager - Create Order Release (1 of 2)

   
   

2. Select Actions.

   Figure 8-6 Agent Manager - Create Order Release (1 of 2)

   
   

3. Click Finished.

8.1.4.2 Create Buy Shipment

1. Navigate to Business Process Automation, Agents and Milestones, Automation Agent, New.

   Figure 8-7 Agent Manager - Create Buy Shipment (1of 2)

   
   

2. Select Actions.

   Figure 8-8 Agent Manager - Create Buy Shipment (2 of 2)

   
   

3. Click Finished.

8.1.4.3 Modify Buy Shipment Cost

1. Navigate to Business Process Automation, Agents and Milestones, Automation Agent, New.

   Figure 8-9 Agent Manager - Modify Shipment Cost (1 of 2)

   
   

2. Select Actions.

   Figure 8-10 Agent Manager - Modify Shipment Cost (2 of 2)

   
   

3. Click Finished.

8.1.4.4 Create Sell Shipment

1. Navigate to Business Process Automation, Agents and Milestones, Automation Agent, New.

   Figure 8-11 Agent Manager - Create Sell Shipment (1of 2)

   
   

2. Select Actions.

   Figure 8-12 Agent Manager - Create Sell Shipment (2 of 2)

   
   

3. Click Finished.

8.1.4.5 Sell Shipment Cost Modified

1. Navigate to Business Process Automation, Agents and Milestones, Automation Agent, New.

   Figure 8-13 Agent Manager - Modify Sell Shipment (1 of 2)

   
   

2. Select Actions.

   Figure 8-14 Agent Manager - Modify Sell Shipment (2 of 2)

   
   

3. Click Finished.

8.1.4.6 Bill Approved

1. Navigate to Business Process Automation, Agents and Milestones, Automation Agent, New.

   Figure 8-15 Agent Manager - Bill Approved (1 of 2)

   
   

2. Select Actions.

   Figure 8-16 Agent Manager - Bill Approved (2 of 2)

   
   

3. Click Finished.

8.1.4.7 Voucher Created

1. Navigate to Business Process Automation, Agents and Milestones, Automation Agent, New.

   Figure 8-17 Agent Manager - Voucher Created (1 of 2)

   
   

2. Select Actions.

   Figure 8-18 Agent Manager - Voucher Created (2 of 2)

   
   

3. Click Finished.

8.2 Setting Up Oracle E-Business Suite

This section discusses Oracle E-Business Suite setup:

8.2.1 General Setup

To create Oracle E-Business Suite system profiles options:

1. Log in to Oracle E-Business Suite as System Administrator.

2. Open System Profile Values form.

3. Query these profile options, and set the indicated values at the site level:

For Oracle E-Business Suite:

• HZ: Generate Party Number to Yes

• HZ: Generate Party Site Number to Yes

• HZ: Raise API Events to All Events Enabled or Only Business Object Events Enabled

• HZ: Format Business Object Business Events as Bulk to N.

8.2.2 Synchronizing Currency Exchange Rates

To synchronize the currency exchange rates:

1. Go to Workflow Administrator, Business Event.

2. Enable the Currency Exchange Business Event oracle.apps.gl.CurrencyConversionRates.dailyRate.specify in Oracle E-Business Suite GL: Daily Conversion Rates Specified.

Note:

The status of the event should be Enable.

If the status is not enabled:

1. Click Update and change the status to Enabled.

2. Click Save.

   The subscription is automatically created during the installation of the PIP.

   Verify the value for the Phase field for the subscription.

3. Click the pencil button to see the Business Events Subscription details. The value in the Phase field should be changed to less than 100.

4. Click Save.

8.2.3 Synchronizing Supplier Data

To synchronize the supplier data, enable the payables supplier event oracle.apps.ap.supplier.event in Oracle E-Business Suite.

8.2.4 Synchronizing Payable Invoices

To synchronize payable invoices:

1. Define Payment Terms.

2. Define Distribution Sets or SLA Account Derivation Rules.

   You can either set up the distribution set with the correct accounting at the supplier site or if you are using Subledger Accounting (SLA) to derive the accounting, set up a dummy distribution set at the supplier site level (that is: 000-000-0000) and set up SLA with the account derivation rules to create the accounting. If you set up the distribution set at the supplier site level with the correct accounts and also set up the account derivation rules in SLA, the account derivation rules overrides the distribution set accounting and create the accounting in GL; therefore, when querying the invoices in AP, it has a different distribution versus the journal in GL.

1. Define Source Lookup, add Code OTM_01.

2. Define Line Source Lookup, add Code OTM_01.

3. Define Supplier, with primary pay site and attach payment term and distribution set to the pay site.

4. Open Payables Accounting Period.

8.2.5 Synchronizing Receivable Invoices

To synchronize receivable invoices:

1. Define Transaction Source - OTM_01:

   • Batch Source Options

   • Set Automatic Batch Numbering = Unchecked

   • Set Automatic Transaction Numbering = Unchecked

   • Set Copy Document Number to Transaction Number = Unchecked

   • Set Allow Duplicate Transaction Numbers = Unchecked

   • Set Reference Field Default Value= interface_header_attribute2

   • Customer Information Options

   • Set Bill To Customer = ID

   • Set Bill To Address= ID

   • Set Bill To Contact = None

   • Set Ship To Customer = ID

   • Set Ship To Address= ID

   • Set Ship To Contact = None

   • Set Payment Terms = ID

   • Accounting Information Options

2. Define Payment Terms.

3. Define Auto Accounting or SLA Account Derivation Rules.

   1. If you are using Oracle E-Business Suite AR AutoAccounting functionality, you must define AutoAccounting to specify the general ledger accounts for transactions that you enter manually or import using AutoInvoice. AutoAccounting uses this information to create the default revenue, receivable, freight, tax, unearned revenue, unbilled receivable, bills receivable accounts, and AutoInvoice clearing (suspense) accounts. The default accounting that AutoAccounting creates is considered interim accounting only. Oracle E-Business Suite AR integrates with SLA that accepts the default accounts that AutoAccounting derives without change. However, you can modify the accounting rules in Subledger Accounting to create accounting that meets your business requirements.

   2. You must define AutoAccounting by Operating Unit before you can enter transactions in Receivables.

4. Define Balance Forward Billing for Consolidated Billing.

5. Define Line Transaction Flexfield.

   1. Context Code =OTM

   2. Segment1 = Domain, Column=INTERFACE_LINE_ATTRIBUTE1

   3. Segment2= InvoiceXid, Column=INTERFACE_LINE_ATTRIBUTE2

   4. Segment3=InvoiceLineNumber

6. Attach payment terms to customer account sites.

8.2.6 Synchronizing Accruals

To synchronize accruals:

1. Define Interface Data Transformation Rules.

   1. Derive Period Name from the Accounting Date

   2. Derive Ledger ID from the Operating Unit

   3. Derive Code Combination ID

   4. Create PL/SQL functions, if any to use in an IDT transformation rule set and register the functions in the metadata structure.

   5. Create value sets, if any, to use in an IDT Transformation Rule Set.

   6. Create lookup tables, if any, to use in an IDT Transformation Rule Set and register the tables in the metadata structure.

   7. Define Transformation Rule Sets.

      IDT rules should be set up to look at the Perspective and the Is Reversal flag to create the logic whether the entry is a debit or a credit. Based on the Perspective, IDT should be set up to create the accounting for the balancing entry. Same goes for the Delta costs.

   8. Run Transformation Rule Sets by launching the Program, GL Interface Data Transformer, either standalone or along with Journal Import.

2. Define Journal import.

   1. If you want Journal Import to assign sequential numbers to your accrual entries, enable sequential numbering, specifying Automatic as both your numbering and document generation method.

   2. Disable dynamic insertion. Journal Import runs much faster when it does not have to create new account combinations dynamically.

8.2.7 Synchronizing Customers

To synchronize customers:

1. Navigate to Workflow Administrator, Business Event.

2. Enable these customers business events in Oracle E-Business Suite:

   • oracle.apps.ar.hz.OrgCustBO.create

   • oracle.apps.ar.hz.OrgCustBO.update

   • oracle.apps.ar.hz.CustAccount.merge

   • oracle.apps.ar.hz.Party.merge

Note:

The status of the event should be Enabled.

If the status is not enabled, do these for each event listed:

1. Click Update and change the status to Enabled and save the event.

   The subscription is automatically created during the installation of the PIP. Verify the value for the Phase field for the subscription.

2. Click the pencil button to review the Business Events Subscription details. The value in the Phase field should be changed to less than 100.

3. Save the subscription.

8.2.8 Setting Up Organizations

This section covers what you must do to set up organizations.

8.2.8.1 Obtaining Oracle E-Business Suite Operating Unit IDs

You must determine what organizations to support and then get the IDs for those organizations.

To get the Operating Unit details:

1. Login to Oracle E-Business Suite database.

2. Identify the Operating Units that must be synchronized or maintained in Oracle E-Business Suite.

If you want to pick other Operating Units, use this query:

select organization_ID, name from hr_operating_units

8.2.8.2 Obtaining Oracle Transportation Management Domains

You must determine which domains in OTM require support.

To get the Domain details:

1. Login to OTM application.

2. Navigate to Configuration and Administration.

3. Click Domain Management.

4. Select Domain Settings.

5. Click Search.

   The following screen appears.

   Figure 8-19 OTM Domains

   
   

8.2.8.3 Creating Status Type for Location in Oracle Transportation Management

You must determine which status type in OTM is required, for example, CUSTOMERPARTYSTATUS.

To create a Status Type:

1. Login to OTM application.

2. Navigate to Configuration and Administration.

3. Click New.

4. Enter Status Type ID, for example, CUSTOMERPARTYSTATUS.

5. Select LOCATION as Object Type.

6. Enter Sequence 1.

7. Enter two rows ACTIVE and INACTIVE.

8. Check the initial Value for ACTIVE row.

   Figure 8-20 OTM Location Status Type

   
   

8.2.8.4 Populating Cross-References

To populate cross-reference values for ORGANIZATION_ID table:

1. Login to database.

2. Connect to schema <AIA_INSTANCE>_xref.

3. Enter values into cross-reference table using the insert command.

See Example 8-1.

Example 8-1 Values for Cross-Reference Table

INSERT INTO XREF_DATA VALUES ('oramds:/apps/AIAMetaData/xref/ORGANIZATION_ID.xref','EBIZ_01','27F4D6303B2511DFBFA11DB680CBD54F','204','N','25-AUG-10 02.26.11.000000000 AM')
 
INSERT INTO XREF_DATA VALUES ('oramds:/apps/AIAMetaData/xref/ORGANIZATION_ID.xref','COMMON','27F4D6303B2511DFBFA11DB680CBD54F','COMMON_ORG_ID','N','25-AUG-10 02.26.11.000000000 AM')
 
INSERT INTO XREF_DATA VALUES 
('oramds:/apps/AIAMetaData/xref/ORGANIZATION_ID.xref','OTM_01','27F4D6303B2511DFBFA11DB680CBD54F','OTM_ORG_VALUE','N','25-AUG-10 02.26.11.000000000 AM')

Note:

Keep the row number (third column) same while inserting date for each pair of cross-reference values.

For more information about creating the cross-references, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite, "Working with Cross References".

8.2.8.5 Validating Cross-References

To validate cross-references:

1. Log in to the AIA XREF database.

2. Query the Table XREF_DATA to confirm that every organization used in the XML files has three records.

   Use the query in Example 8-2.

Example 8-2 Table XREF_DATA Query

select value||::||Xref_column_name from xref_Data where row_number in (select row_number from xref_data where xref_table_name = oramds:/apps/AIAMetaData/xref/ORGANIZATION_ID.xref and value in (204))

Replace the value for the organizations you selected. (The number of operating units depends on your setup.)