Cannot Create Journal By Mass Allocation Function, Version:-R12.1.1

Cannot Create Journal By Mass Allocation Function [ID 857664.1]
        Version:-R12.1.1

         

Cannot Create Journal By Mass Allocation Function [ID 857664.1] In this Document
  Symptoms
  Cause
  Solution
  References

---

 

1.Applies to:-

Oracle General Ledger - Version: 12.1
Information in this document applies to any platform.
***Checked for relevance on 28-Feb-2011***

Program:Run MassAllocations
Program Short Name:GLAMAS

1. Symptoms

In R12.1.1
When attempting to generate the mass allocations
the following error occurs.

ERROR
Finished executing request completion options.
glamai() - fatal sql error

STEPS
The issue can be reproduced at will with the following steps:
GL Responsibility > Journals > Generate > Allocation

1. Cause

Cause of the issue is due to missing database objects GL_ALLOC_INT_1,GL_ALLOC_INT_2 and GL_ALLOC_INT_3.
-To verify the cause, check if the missing database objects exists.
Also check if the trace file for the Mass Allocations gives Parse Error for the statement

"delete from GL_ALLOC_INT_1"
Solution :-

Create the missing objects GL_ALLOC_INT_1,GL_ALLOC_INT_2 and GL_ALLOC_INT_3.

-The missing object should be created from the xdf file gl_alloc_int_1.xdf,gl_alloc_int_2.xdf and
gl_alloc_int_3.xdf

-The xdf file is placed under $GL_TOP/patch/115/xdf/.

  SOLUTION steps:-
          
[oracle@dev1211 R12]$ cd oracle/VIS/db/tech_st/11.1.0/
[oracle@dev1211 11.1.0]$ . VIS_dev1211.env 
[oracle@dev1211 11.1.0]$  sqlplus
SQL*Plus: Release 11.1.0.7.0 - Production on Wed Feb 1 03:25:57 2012
Copyright (c) 1982, 2008, Oracle.  All rights reserved.

Enter user-name: /as sysdba

Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> conn apps/apps
Connected.


SQL> desc dict;         
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 TABLE_NAME                                         VARCHAR2(30)
 COMMENTS                                           VARCHAR2(4000)

SQL> select * from dict where table_name like '%GL_ALLOC_INT_1%';

no rows selected

Sometimes it is needed to verify or re-create a Database Object,

which is created via a odf- or xdf-file.

In the earlier Releases of the E-Business-Suite the odf-files 

(Object Description File) was introduced to create DB Objects 

like tables, synonyms, views, Indexes, etc using the appropriate 

AD-Utility. These odf-files are available in Release 10.7, 11.0.3, 

11i and R12. But the odf-files are more and more replaced by the

 xdf-files, starting with the Release 11i and further implemented in R12.

To verify and create Database Objects, defined in a odf-File you are

using the Utility adodfcmp, which is located under the

 $AD_TOP/bin.>>>

[oracle@dev1211 bin]$ pwd
/data/R12/oracle/VIS/apps/apps_st/appl/ad/12.0.0/bin

To verify and create Database Objects, defined in a xdf-File you are 

using the Java Utility FndXdfCmp, which is located under the 

$JAVA_TOP/oracle/apps/fnd/odf2.

[oracle@dev1211 odf2]$ pwd
/data/R12/oracle/VIS/apps/apps_st/comn/java/classes/oracle/apps/fnd/odf2
                                   
Usage of the Java Utility FndXdfCmp :-

[oracle@dev1211 xdf]$ pwd

/data/R12/oracle/VIS/apps/apps_st/appl/gl/12.0.0/patch/115/xdf


[oracle@dev1211 xdf]$ 
adjava -mx512m -nojit oracle.apps.fnd.odf2.FndXdfCmp gl gl apps apps 

thin dev1211.iwarelogic.com:1541:vis all gl_alloc_int_1.xdf 

$FND_TOP/patch/115/xdf/xsl

[oracle@dev1211 xdf]$ 
adjava -mx512m -nojit oracle.apps.fnd.odf2.FndXdfCmp gl gl apps apps 

thin dev1211.iwarelogic.com:1541:vis all gl_alloc_int_2.xdf 

$FND_TOP/patch/115/xdf/xsl
[oracle@dev1211 xdf]$ 
adjava -mx512m -nojit oracle.apps.fnd.odf2.FndXdfCmp gl gl apps apps 

thin dev1211.iwarelogic.com:1541:vis all gl_alloc_int_3.xdf 

$FND_TOP/patch/115/xdf/xsl


SQL> conn / as sysdba

Connected.


SQL> SELECT OBJECT_NAME FROM ALL_OBJECTS 

WHERE OBJECT_NAME LIKE 'GL_ALLOC_INT_1';

OBJECT_NAME

------------------------------

GL_ALLOC_INT_1

GL_ALLOC_INT_1


SQL> SELECT OBJECT_NAME FROM ALL_OBJECTS 

WHERE OBJECT_NAME LIKE 'GL_ALLOC_INT_2';



OBJECT_NAME

------------------------------

GL_ALLOC_INT_2

GL_ALLOC_INT_2


SQL> SELECT OBJECT_NAME FROM ALL_OBJECTS WHERE 

OBJECT_NAME LIKE 'GL_ALLOC_INT_3';



OBJECT_NAME

------------------------------

GL_ALLOC_INT_3

GL_ALLOC_INT_3

SQL> select object_name,object_type from all_objects where 

object_name like '%GL_ALLOC_INT%';



OBJECT_NAME                    OBJECT_TYPE

------------------------------ -------------------

GL_ALLOC_INT_1                 SYNONYM

GL_ALLOC_INT_1                 TABLE

GL_ALLOC_INT_1_N1              INDEX

GL_ALLOC_INT_2                 TABLE

GL_ALLOC_INT_2                 SYNONYM

GL_ALLOC_INT_2_N1              INDEX

GL_ALLOC_INT_3                 TABLE

GL_ALLOC_INT_3                 SYNONYM

GL_ALLOC_INT_3_N1              INDEX



9 rows selected.


-Refer the Note.551325.1
for creating the objects using xdf file. 

1. References

NOTE:551325.1 - How to verify or create a Database Object using a odf or xdf file ?

Products :-

Oracle E-Business Suite > Financial Management > Financial Control and Reporting > 

Oracle General Ledger