Otmvouchertooracleapinvoice Interface Xsl Mapping Incorrect
Last updated on JULY 09, 2014
Applies to:Oracle Transportation Management - Version: 5.5.03 to 5.5.03.01
This problem can occur on any platform.
In the 'OtmVoucherToOracleApInvoice' integration, the ACCOUNT_NUMBER Reference set in the Source Location is not propagating to the AP_INVOICE_LINES_INTERFACE table.
An incorrect mapping was identified for the xsl mapping in the file 'Transformation_ToApInvoice.xsl' that is causing this to happen. This file is located in $OTM_HOME/utils/integration/bpel/flows/OtmVoucherToOracleApInvoice.zip file.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms