R12: PA: 12.1.3 PA Expansion Exceptions During Character Set Conversion WE8ISO8859P1 to AL32UTF8 (Doc ID 2117527.1)

Last updated on MARCH 17, 2016

Applies to:

Oracle Project Foundation - Version 12.1.3 and later
Information in this document applies to any platform.

Goal

1. Upgrading E-Business Suite 11.5.10.2 to 12.1.3 and migrating platforms from Red Hat Linux 5 to Oracle Solaris Sparc (SuperCluster).

2. At the same time, changing the character set from the WE8ISO8859P1 to AL32UTF8.

Have run the Data migration Assistant for Unicode (DMU - Version 2.1) against the database and this has highlighted a number of expansion or Invalid Representation exceptions in the Project Accounting (PA) schema.

Have raised issues with the other product groups including the Fixed Assets (FA) product group, where there are similar issues and cannot update records through the User Interface (UI). The FA group fully supports a data fix where a direct table update is done to a number of FA objects.column_names, because FA can confirm there is no referential integrity on the column via the UI or database triggers etc.

Are direct table updates on the object.column_names listed below fully supported by Oracle?

Owner Object_name Column_name
-----------------------------------------------------------------
PA PA_BUDGET_VERSIONS VERSION_NAME
PA PA_BUDGET_VERSIONS DESCRIPTION
PA PA_BUDGET_LINES DESCRIPTION
PA PA_EXPENDITURE_COMMENTS EXPENDITURE_COMMENTS
PA PA_RESOURCE_ASSIGNMENTS ASSIGNMENT_DESCRIPTION
PA PA_TXN_INTERFACE_AUDIT_ALL EXPENDITURE_COMMENT
PA PA_PROJECTS_ALL DESCRIPTION
PA PA_PROJECTS_ALL LONG_NAME

Solution

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