My Oracle Support Banner

Convergence Migration From 11i To 12.2.3 Created Adjusting Period For An Organization (Doc ID 1919035.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Process Manufacturing Systems - Version 12.2.2 and later
Information in this document applies to any platform.

Symptoms

On :  12.2.2 version, Migration Issues 11i to R12

ACTUAL BEHAVIOR  
---------------
After applying patches 17006749, 17450269, 13801082, 14227472, an adjustment period was created and closed in the Inventory calendar for the organizations mapped between OPM and INV for Dec 31, 2014.

This makes the Open/Close Period form (the Inventory Accounting Periods form) not show the Future periods, so users can't open them.

EXPECTED BEHAVIOR
-----------------------
To not have an adjustment period created in Inventory periods and to see and be able to open the future periods

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Apply the patches above

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue,the INV periods are not accessible to open, and therefore batch recreation cannot occur.

 

Then, when attempting to apply the newer patch to resolve this:

When attempting to apply patch 18755464, you get errors like the following:

PL/SQL procedure successfully completed.

REM /*********************** End of Migration Run id ******************/
*
ERROR at line 577:
ORA-06550: line 577, column 1:
PLS-00103: Encountered the symbol "REM" when expecting one of the following:
:= . ( @ % ;
The symbol ":=" was substituted for "REM" to continue.

This is because every comment with pl/sql blocks has had REM added in front of it, and REM is not allowed within pl/sql blocks. The issue exists at least is files GMAFMIGT.sql, GMFG6P02.sql, GMFG6P03.sql, GMFG6P05.sql, GMFG6P11.sql and GMFG6P12.sql

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Apply patch 18755464:R12.GMF.C

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot migrate.


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.