OTM-EBS Payables Integration White Paper v2

Oracle Transportation Management
E-Business Suite (Payables) integration with OTM

ORACLE WHITE PAPER | JANUARY 2017
Table of Contents
TITLE 3
ABSTRACT 3
TERMINOLOGY 3
INTEGRATION FLOW 3
ORACLE PAYABLES XML MAPPING 4
REFERENCE DATA INTEGRATION 9
MASTER DATA & SETUP IN OTM 14
THE EXECUTION STEPS IN OTM 21
EBS INTERFACE TABLES DATA VERIFICATION 31
THE EXECUTION STEPS IN EBS 32
VALIDATE, PAY AND ACCOUNT INVOICE IN EBS 39
BPEL 44
APPENDIX 48
REFERENCES 51
1 | EBS-OTM INEGRATION
DATA DISCLAIMER: The screenshots herein include data for demonstration
purposes only. Please use your own data for successful testing.
2 | OTM-EBS INEGRATION
TITLE
The outbound integration from Oracle Transportation Management (OTM) to Oracle
Payables (AP) through the use of BPEL.
ABSTRACT
The purpose of this document is to show the steps that you need to follow in order to start
an OTM outbound integration flow to EBS Payables via BPEL that you can use as a
tutorial example that helps the one to test and replicate the clients’ issue in-house.
TERMINOLOGY
OTM = Oracle Transportation Management
EBS = Oracle E-Business Suite
AP = Account Payables
OTM.Voucher = EBS.Innvoice
INTEGRATION FLOW
Outbound OTM-AP integration flow (Buy Shipment Side)
OTM: Create a shipment -> Create and approve a Invoice -> Send out the generated
Voucher to EBS (AP) using the ‘Send Voucher interface’
BPEL: The Send Voucher interface transmits the voucher data to Oracle Payables
through BPEL
EBS: The invoice is then created, validated, and ultimately paid in Oracle Payables
ORACLE PAYABLES XML MAPPING
The following table shows the mapping between OTM and EBS – Oracle Payables.
Source OTM /
Target AP
BPEL AP
Invoices Description
Integration
Interface
Usage
exchangeRate In BPEL set to Exchange rate type for foreign currency invoices.
Type "CORPORAT EXCHANGE_RATE_TYPE: Type of exchange rate
E." used to calculate the exchange rate between theinvoice
currency and your functional currency. If the value in
the INVOICE_CURRENCY_CODE column is a
foreign currency code, then enter a value in this column
to indicate which exchange rate type you are using. You
can enter a predefined or user–defined exchange rate
type. If the invoice record has a foreign currency and
you do not enter a value for
EXCHANGE_RATE_TYPE, then during import the
system uses the Exchange Rate Type selected in the
Payables Options window. If the invoice currency and
your functional currency are associated fixed–rate
currencies, such as euro and another EMU currency,
then enter EMU Fixed.Validation - Payables uses five
types of exchange rates: User, Spot, Corporate, EMU
Fixed, and user–defined. If you use Spot, Corporate, or
any user–defined rate type, the value you enter here is
validated against the GL Daily Rates table. If you use
EMU Fixed, Payables provides the exchange rate during
import. If you use User as the exchange rate type, You
must either enter a value for EXCHANGE_RATE or, if
the Payables OptionCalculate User Exchange Rate is
enabled, you can enter a value for
NO_XRATE_BASE_AMOUNT instead. Destination -
AP_INVOICES_ALL.EXCHANGE_RATE_TYPE
invoiceAmou Map from Invoice Amount INVOICE_AMOUNT: Amount of the
nt OTM Voucher invoice. Do not exceed the precision of the currency of
AmountToPay the invoice. For example, if you are entering an amount
in US dollars, then do not enter more than two numbers
after the decimal point. Validation - This value must
equal the sum of the AMOUNT values in the
AP_INVOICE_LINES_INTERFACE table for lines
with the same INVOICE_ID. The amount must
correspond to the invoice type. For example, Standard
invoices must have an amount of zero or greater.
Destination -
AP_INVOICES_ALL.INVOICE_AMOUNT
invoiceCurren ISO standard Currency of invoice. INVOICE_CURRENCY_CODE:
cyCode OTM Currency code for the invoice. If you do not enter a
GlobalCurrenc value, then the supplier site value defaults during
yCode import. Validation - If you enter a code in a foreign
currency, then you must enter a valid, active currency
code from Destination -
FND_CURRENCIES.CURRENCY_CODE.AP_INVOI
CES_ALL.INVOICE_CURRENCY_CODE
invoiceDate Map to Invoice Date INVOICE_DATE: Date of the invoice. If
InvoiceDate you do not enter a value, then the system uses the date
from voucher. that you submit the Payables Open Interface Import as
Supplier's the invoice date. Validation - The value must be in valid
invoice date date format. Destination -
This date is AP_INVOICES_ALL.INVOICE_DATE
used to drive
Accounting
Date/GL Date.
invoiceId Call AP to Invoice ID Required, Primary key. This value is
retrieve assigned in the Quick Invoices window by the
sequence, and AP_INVOICES_INTERFACE_S sequence. Unique
then apply to identifier for this invoice within this batch. You assign
header and the same value to the invoice’s lines in the
lines. AP_INVOICE_LINES_INTERFACE table to identify
the data as belonging to the same invoice.
invoiceNum Concatenated Vendors number/invoice number Required if there is
field more than one invoice for the supplier during import.
InvoiceNum INVOICE_NUM: Enter the invoice number that you
plus want to assign to the invoice created in Payables from
VoucherGid this record. The number must be unique for the supplier.
AP Invoice If you do not enter a value, then during import, Payables
Number <= 50 uses the system date at the time of import as a default. If
characters. you enter more than one invoice for a supplier, then be
Must be a sure to enter unique invoice numbers rather than using
unique number the default, or the invoices will have duplicate invoice
for the numbers and will be rejected during import. Validation -
supplier. Must be a unique number for the supplier. If you assign
Carrier Invoice a duplicate number for the supplier, Payables Open
Num = "JBHT- Interface Import does not create an invoice from this
1002322-1" record. Destination -
Voucher Gid = AP_INVOICES_ALL.INVOICE_NUM
"EBS.1234567
8." Invoice
number will be
a concatentated
field of
CarrierInvoice
Num plus
VoucherGID =
"JBHT-
1002322-
1|EBS.234567
8"
invoiceTypeL BPEL Type of Invoice (can be STANDARD or CREDIT)
ookupCode transformation. INVOICE_TYPE_LOOKUP_CODE: Type of invoice:
Positive Credit or Standard. If you do not enter a value, then the
amount system assigns a value during Payables Open Interface
voucher = Import based on the value of INVOICE_AMOUNT. If
"STANDARD, INVOICE_AMOUNT is less than zero, the invoice will
" Negative be Credit. If INVOICE_AMOUNT is zero or greater,
amounts on the invoice will be Standard. Validation - The value
voucher = must be Credit or Standard. The invoice type must
"CREDIT." correspond to the invoice amount if it is Credit or
Standard. For example, a Credit invoice must have an
invoice amount that is less than zero. Destination -
AP_INVOICES_ALL.INVOICE_TYPE_LOOKUP_CO
DE
source Source = Source of the invoices. SOURCE: Source of the invoice
"TRANSPOR data. Examples include Quick Invoices, EDI Gateway
TATION (e–Commerce Gateway), Credit Card, Oracle Assets,
MANAGEME Oracle Property Manager, ERS (Evaluated Receipt
NT." Settlement), RTS (Return toSupplier), iSupplier Portal,
XML Gateway, and user–defined. You define additional
values for Source in the Oracle Payables Lookups
window. If you have defined additional sources, you
should use a source name for only one type of source.
For example, do not use the same source name for
invoices that you enter in Quick Invoices, and invoices
you load with SQL*Loader. The Source name also
determines which records will be selected for import or
purge. You specify a Source name when you submit
Payables Open Interface Import or Purge Payables Open
Interface. Validation - If you do not use a predefined
source you must enter the name exactly as you have
defined the lookup value in the Oracle Payables
Lookups window, or Payables Open Interface Import
will not create an invoice from the record. The lookup
value must have the Type SOURCE. See: Lookups in
the Oracles Payables User Guide. Destination -
AP_INVOICES_ALL.SOURCE
vendorNum Map to Supplier number VENDOR_NUM: Supplier number.
ServiceProvide You must identify the supplier by entering a value for
r Alias Qualf one of the following columns in this table:
="VENDOR_ VENDOR_ID,VENDOR_NUM, VENDOR_SITE_ID,
NUM." VENDOR_SITE CODE, or PO_NUMBER. If you have
not yet entered the supplier in the Suppliers window,
then enter it before import. Validation - The number
must be for an existing, valid supplier. You can obtain a
list of valid values from PO_VENDORS.SEGMENT1.
None. This value is used to enter Destination -
AP_INVOICES_ALL.VENDOR_ID.
vendorSiteCo Map from Supplier site code VENDOR_SITE_CODE: Supplier
de SeerviceProvid site name. If you do not provide a valid value to identify
er Alias Qualf the pay site in VENDOR_SITE_CODE or
= VENDOR_SITE_ID, then import searches for a valid
"VENDOR_SI supplier pay site in the following order:
TE_CODE." Primary pay site for supplier
Single existing pay site for supplier
Derived from PO number matched at the header level
Import rejects the invoice if it cannot identify a valid
supplier site. Validation - This must be a valid, active
supplier site for the supplier you specify
(VENDOR_NUM or VENDOR_ID). You can obtain a
list of valid values from
PO_VENDORS.VENDOR_SITE_CODE. The site must
also be a pay site. Destination - None. This value is used
to enter AP_INVOICES_ALL.VENDOR_SITE_ID.
amount Represents the Line amount
amount for this
invoice line.
One line per
invoice in
delivered
integration.
"CREDIT" =
negative
"STANDARD
" = positive.
lineTypeLook BPEL set to Type of invoice line (Item, Freight, Tax, Miscellaneous)
upCode "FREIGHT"
DistCodeCon BPEL Accounting flexfield for account associated with a
catenated conditional distribution line
logic in
mapped to
location
reference
number
qualifier
“ACCOUNT_
NUMBER”
from the
source location
or if not
available on
the source
location the
value is taken
from
“ACCOUNT_
NUMBER” on
the service
provider
location.
Reference:
http://docs.oracle.com/cd/E18727_01/doc.121/e13432/T441621T448116.htm#t_omxmlm
ap
REFERENCE DATA INTEGRATION
Certain data must be synchronized between the two systems. (EBS to OTM)
01. Where you can find the VENDOR_NUM and VENDOR_SITE_CODE in OTM?
You can find this information on the “Service Provider that is assigned to the
Planned Shipment”
This page is accessed via Shipment Management > Shipment Management >
Buy Shipments
If you click on the Service Provider ID “CAR-12521”, you will go to the Service Provider
screen
Click “Edit” and scroll down to the “Service Provider Alias” section/grid
02. Where you can find the ACCOUNT_NUMBER in OTM?
You can find this information on the Shipment’s “Source Location”
Example: Shipment ID: 01043
This page is accessed via Shipment Management > Shipment Management >
Buy Shipments
Click on the “+” sign
Then click on the “+” sign for the “Shipment Stops”
The first stop is the Shipment’s “Source Location”. Just click on the stop ID, the shipment
stop screen will show up
Click on the “Location ID” link, the Location screen will show up
MASTER DATA & SETUP IN OTM
OTM Shipment
You have to have a planned and rated OTM shipment to start with for this flow.
Example: Shipment ID: 01026
This page is accessed via Shipment Management > Shipment Management > Buy
Shipments
Invoice Approve Rule & Profile
To set up the approval of invoices, follow these general steps:
01. Create invoice approve rules.

This page is accessed via Financials > Payment Rule Management > Invoice
Approve Rule.
Example: Invoice Approve Rule ID: EBS-OTM
02. Assign invoice approve rules to invoice approve rule profiles.
This page is accessed via Financials > Payment Rule Management > Invoice
Approve Rule Profile.
Example: Invoice Approve Rule Profile ID: EBS-OTM
03. Assign invoice approve rule profiles to service providers (that is assigned to the
OTM Shipment).
This page is accessed via Contract and Rate Management > Service Provider
Manager.
Example: Service Provider ID: CAR-12521
04. Assign the invoice approve rule profile to a user.
This page is accessed via Configuration and Administration > User Management
> User Manager.
The User ID: ADMIN
External System
External System that is configured for the BPEL.
This page is accessed via Business Process Automation > Communication Management
> External Systems.
Example: External System ID: VOUCHER FROM OTM
NOTE: Please refer to the “Setting Up an External System for EBS Integration” in the Appendix
section at the bottom of the document for the procedures to setup External System and Web
Service to be used for EBS integration.
THE EXECUTION STEPS IN OTM
Generate Invoice
01. Login to OTM and go to Shipment Management > Shipment Management > Buy
Shipments > Search for our example shipment 01026
02. Select the shipment > Click ‘Actions’ > Financials > Invoice > Create Invoice
A new screen will show up ‘Generate Invoice’ > Click ‘Create Invoice(s)’
You will get a new screen ‘Generate Invoice Results’. You can see an Invoice
created. The Invoice ID is 20170205-0002
APPROVE INVOICE
03. Go to Financials > Payment Invoice Management > Payment Invoice > Search
for Invoice ‘20170205-0002’
Select the invoice > Click ‘Actions’ > Financials > Invoice > Approve Invoice
A new screen will show up ‘Approve Invoice’ > Click ‘Finished’
You will get a new screen ‘Approve Invoice By Line’. Now you just approved this
Invoice.
Were I can see the status that tells me the invoice is approved?!
Click on the Invoice ID line > that will open the Invoice in ‘View’ mode > Click the
‘Status’ button on the left of the screen
A new window will show up. You can see the ‘APPROVAL’ status is
‘APPROVAL_APPROVED_MANUAL’
Voucher Generated
A voucher will automatically generate as soon as you approve the invoice.
Where I can find it?
Go to Financials > Payment Invoice Management > Voucher > Enter ‘20170205-0002’ in
the Invoice ID field > Click search
The Voucher ID: 000002
Run the Send Voucher Interface

Select the Voucher > Click ‘Actions’ > Utilities > Send Voucher Interface
Enter the External System ‘VOUCHER FROM OTM’, Notify Type ‘SERVICE’ and Click
‘Send’
Check On the Outbound Transmission
Now you just sent the OTM Voucher from OTM to EBS via BPEL. Let us have a look at the
Outbound Transmission
Navigate to Business Process Automation -> Integration -> Transmission Manager
The transmission status is “PROCESSED” which means that the outbound integration to
EBS went successfully without errors.
You can click on the “Raw XML” button to extract the outbound XML for review. You can
also click on the “Report” button to review the error(s) in case the Transmission status
was ERROR which means failed to be transmitted from OTM out.
Sending the Voucher from OTM to EBS will create an Invoice in EBS.
EBS INTERFACE TABLES DATA VERIFICATION
Please run the following queries to verify the data on the EBS interface tables before
running the import program in the Account Payables (explained in the Execution Steps in
EBS section below)
The queries will help you to verify and make sure; the EBS interface tables have the
required data from OTM for a successful invoice(s) import.
SELECT invoice_id,invoice_num,vendor_id,vendor_num,vendor_site_code,status
FROM ap_invoices_interface
WHERE SOURCE='TRANSPORTATION MANAGEMENT'
SELECT invoice_id,line_type_lookup_code,dist_code_concatenated
FROM ap_invoice_lines_interface;
Please verify the Distribution_code_Combination that is coming from OTM is valid and
exists in EBS, otherwise the invoice import will fail in EBS. Please refer to the
Reference Data Integration section above.
THE EXECUTION STEPS IN EBS
By now, you have sent a Voucher/Invoice from OTM to the EBS Interface Tables. The
next step is to login to EBS and manually import the OTM invoices from the Interface
Tables to EBS.
01. Log into the EBS instance
02. From the left side menu, navigate to Payables, Vision Operations (USA)
03. Navigate to Invoices > Inquiry > Invoices
04. Go to “View” > Requests
05. Click “Submit a New Request”
Enter the Name “Payables Open Interface Import” > OK
Enter the Source “Transportation Management” > OK > Submit
NOTE: As a prerequisite, you need to the “Transportation Management” source

to lookup value. Please refer to the Appendix section at the bottom of the
document for the steps that you need to follow to add the “Transportation
Management” source to lookup value.
Keep clicking “Refresh Data” until the Request’s Phase changes to “Completed”
> Then click “x” to close the Requests window
You will back to the “Find Invoices” window
The voucher/Invoice was sent from OTM to EBS on March 24th, so you will query
for the invoice from that date.
VALIDATE, PAY AND ACCOUNT INVOICE IN EBS
The following steps show you the rest for the EBS business flows after importing the
OTM invoice to EBS.
Invoice validation:
02. Navigate to (Responsibility) >Invoice > Entry
03. Query for the Invoice, example ‘PAR_STD000015|EBSOTM.000015’
04. Action > Validate
Invoice payment:
Once the invoice is validated, it can be paid in full.
04. Action > Pay in Full
05. Make a Electronic Pay to supplier
Invoice accounting:
Once the invoice is paid, you can account the invoice and post the entry to GL
04. Action > Create Accounting , Select Final Post
BPEL
BPEL is the “translator” for all the communications between EBS and OTM. All the
integration flows between EBS and OTM go through SOA/BPEL (middleware) to
transform the EBS and OTM communications to XML files, which can be transmitted to
and from each of the applications considering the data mapping tables between the two
applications.
There is one transmission been transmitted between EBS (AP) and OTM via BPEL.
 OTM to EBS: Voucher
Let us have a look on how to find this transmission in SOA/BPEL and how to review the
BPEL XMLs.
01. Log into BPEL (Via the Oracle Enterprise Manager)
02. Navigate to SOA -> soa-infra (soa_server1) -> On the right hand frame, click on
“Instances” tab.
Insert the date, which your transmissions were transmitted on, and click “Search”
Click on the "Instance ID" > for example instance 70003
OtmVoucherToOracleApInvoice [1.0], the "Flow Trace" window will open up
Click on “OtmVoucherToOracleApInvoice”
Go to the “Flow tab”
You can click on “View Raw XML” to get to the XML file for review.
APPENDIX
SETTING UP AN EXTERNAL SYSTEM FOR EBS INTEGRATION
Creating an external system to represent EBS (using BPEL)
This procedure covers setting up external systems to be used for EBS integration.
External System for Voucher out of OTM
If the WSDL for the BPEL flow is not already loaded in OTM, retrieve it from the BPEL server as
follows:
1. Enter the URL of the BPEL service that your Oracle Consultant provided to you.
2. Log into the BPEL server.
On the left for the deployed BPEL processes, select the flow that you will be sending to.
3. Select OtmVoucherToOracleApInvoice
4. Click the WSDL tab.
BPEL generates the WSDL document
5. Right-click on the WSDL location URL.
6. Save the WSDL locally to your hard drive.
7. Write down the endpoint location – it will be used as the service endpoint when setting up
the external system.
Now that you have downloaded the WSDL files and copied the endpoint locations, you are ready
to create your external system in OTM.
Setting Up the Web Service
8. Log into OTM
Go to Business Process Automation > Communication Management > External Systems >
External System Manager
9. Click New.
10. Enter an External System ID, such as VOUCHER FROM OTM
11. Scroll down to the Web Services section.
If a web service already exists, go to task #12. Otherwise, you need to create a new web service,
go to task #13 to create a new web service.
12. Search for and select an existing web service.
13. Click n (new) to the right of the Web Service field.
OTM displays the Web Service page.
14. Click n (new) to the right of the WSDL Document field.
OTM displays the Document page.
15. Leave the Document Type field blank.
It is not necessary to select a document type.
16. Click Document Detail.
17. In the Document Manager, specify the ID (OTMVOUCHERTOORACLEAPINVOICE).
18. Select a Storage type of Text.
Note that the Mime Type field will be populated automatically after the WSDL file is loaded.
19. Click Upload to upload the WSDL file you retrieved from the BPEL server.
OTM displays the Upload Document page.
20. Click Browse.
OTM displays the Windows Choose file dialog box.
21. Browse to and select the XML file that you downloaded from the BPEL Console web site.
22. Click Open.
OTM displays the Upload Document page again.
23. Click Upload.
24. Click Finished.
OTM displays the Web Service page again.
25. Click Service Details.
26. Enter a Service ID (OTMVOUCHERTOORACLEAPINVOICE).
27. Enter a Service Endpoint ID (OTMVOUCHERTOORACLEAPINVOICE).
28. Enter a Service Endpoint, which is the URL that you copied from the BPEL WSDL Endpoint
Location (e.g. http://servername.com/orabpel/default/OtmVoucherToOracleApInvoice/1.0)
29. Click Save to the right of the Timeout field.
30. Click Finished.
OTM displays the External System Manager page again.
31. Select the Trans Ack Expected option button.
This indicates that a TransmissionAck XML is expected to be returned by the BPEL flow. The
“OtmVoucherToOracleApInvoice” flow return the TransmissionAck.
32. Only if you are completing the OtmVoucherToOracleApInvoice flow, select the Use Ack
Status option button.
This indicates that the status in the TransmissionAck should be used as the status of the
Transmission (e.g. PROCESSED or ERROR).
33. Click Finished to save the external system record.
How to add the “Transportation Management” source to lookup value in EBS?
02. Navigate to Payables (Responsibility) > Setup > Lookups > Payables
03. Query for Type 'SOURCE'
04. Click on New Icon '+' from Form Menu
05. Enter Code as 'TRANSPORTATION MANAGEMENT' , Meaning as 'Transportation
Management' , Description as 'Transportation Management'
06. Save the change
REFERENCES
Integrating Oracle Transportation Management with Oracle. (n.d.). Retrieved from
http://docs.oracle.com/cd/B40089_10/current/acrobat/120otmintg.pdf
Oracle Transportation Management to Oracle E-Business Suite XML Mapping. (n.d.). Retrieved from
http://docs.oracle.com/cd/E18727_01/doc.121/e13432/T441621T448116.htm#t_omxmlmap
Oracle Corporation, World Headquarters Worldwide Inquiries
500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200
CONNECT W ITH US
blogs.oracle.com/oracle
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
twitter.com/oracle means, electronic or mechanical, for any purpose, without our prior written permission.
oracle.com Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0417
E-Business Suite (OM/Shipping) integration with OTM

January 2017
Author: Islam Bahgat

OTM-EBS Payables Integration White Paper v2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OTM-EBS Payables Integration White Paper v2

Uploaded by

Copyright:

Available Formats

Oracle Transportation Management

E-Business Suite (Payables) integration with OTM

ORACLE PAYABLES XML MAPPING 4

REFERENCE DATA INTEGRATION 9

MASTER DATA & SETUP IN OTM 14

THE EXECUTION STEPS IN OTM 21

EBS INTERFACE TABLES DATA VERIFICATION 31

THE EXECUTION STEPS IN EBS 32

VALIDATE, PAY AND ACCOUNT INVOICE IN EBS 39

REFERENCE DATA INTEGRATION

02. Where you can find the ACCOUNT_NUMBER in OTM?

You can find this information on the Shipment’s “Source Location”

Click on the “+” sign

Then click on the “+” sign for the “Shipment Stops”

Example: Shipment ID: 01026

01. Create invoice approve rules.

Example: Invoice Approve Rule ID: EBS-OTM

Example: Invoice Approve Rule Profile ID: EBS-OTM

Example: Service Provider ID: CAR-12521

The User ID: ADMIN

Example: External System ID: VOUCHER FROM OTM

A new screen will show up ‘Approve Invoice’ > Click ‘Finished’

A voucher will automatically generate as soon as you approve the invoice.

Where I can find it?

Run the Send Voucher Interface

Navigate to Business Process Automation -> Integration -> Transmission Manager

EBS INTERFACE TABLES DATA VERIFICATION

01. Log into the EBS instance

03. Navigate to Invoices > Inquiry > Invoices

05. Click “Submit a New Request”

NOTE: As a prerequisite, you need to the “Transportation Management” source

02. Navigate to (Responsibility) >Invoice > Entry

03. Query for the Invoice, example ‘PAR_STD000015|EBSOTM.000015’

04. Action > Validate

Once the invoice is validated, it can be paid in full.

01. Log into the EBS instance

02. Navigate to (Responsibility) >Invoice > Entry

03. Query for the Invoice, example ‘PAR_STD000015|EBSOTM.000015’

04. Action > Pay in Full

05. Make a Electronic Pay to supplier

01. Log into the EBS instance

02. Navigate to (Responsibility) >Invoice > Entry

03. Query for the Invoice, example ‘PAR_STD000015|EBSOTM.000015’

04. Action > Create Accounting , Select Final Post

 OTM to EBS: Voucher

01. Log into BPEL (Via the Oracle Enterprise Manager)

Creating an external system to represent EBS (using BPEL)

External System for Voucher out of OTM

2. Log into the BPEL server.

4. Click the WSDL tab.

BPEL generates the WSDL document

5. Right-click on the WSDL location URL.

6. Save the WSDL locally to your hard drive.

Setting Up the Web Service

8. Log into OTM

10. Enter an External System ID, such as VOUCHER FROM OTM

11. Scroll down to the Web Services section.

12. Search for and select an existing web service.

13. Click n (new) to the right of the Web Service field.

OTM displays the Web Service page.

14. Click n (new) to the right of the WSDL Document field.

OTM displays the Document page.

15. Leave the Document Type field blank.

It is not necessary to select a document type.