My Oracle Support Banner

Error Occurs In EBS-OTM Standard Integration When PO Approved - Due to Length Differences (Doc ID 843147.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Management - Version: 5.5.04.04 to 6.1.0 - Release: 5.5 to 6.1
Information in this document applies to any platform.
***Checked for relevance on 15-Apr-2011***

Symptoms

-- Problem Statement:
On 5.5.04.05, When attempting to integrate a PO from EBS to OTM, the following error occurs:

ERROR
CAUGHT THE FOLLOWING EXCEPTION WHILE PROCESSING TRANSACTION:
glog.util.exception.CreateExceptionWrapper java.sql.SQLException: ORA-12899:
—ñ"GLOGOWNER"."LOCATION_ADDRESS"."ADDRESS_LINE"‚Ì’l‚ª‘å‚«‚·‚¬‚Ü‚·(ŽÀÛ: 86AÅ‘å: 55)
java.sql.SQLException: ORA-12899:
—ñ"GLOGOWNER"."LOCATION_ADDRESS"."ADDRESS_LINE"‚Ì’l‚ª‘å‚«‚·‚¬‚Ü‚·(ŽÀÛ: 86AÅ‘å: 55) at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at
oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Create a PO in EBS with Locations that has a very long address line - More than 200 characters
in it
2. Approve the PO and see that the Transmission from EBS to OTM fails in OTM with the error that
the Location Address Line is too long

3. The same errors occur for other fields as well

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
  Symptoms
  Cause
  Solution
  References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.