Archive for the ‘Oracle EBS Application’ Category

How To Update EBS XML Publisher Temporary Directory

January 5th, 2021, posted in Oracle EBS Application, Oracle Queries
Share
SQL> select value from apps.XDO_CONFIG_VALUES WHERE  property_code = 'SYSTEM_TEMP_DIR';
VALUE
--------------------------------------------------------------------------------
/u1/appl/SHAIK1/wrongdir_tmp



SQL> update apps.XDO_CONFIG_VALUES set value='/u01/share/temp' WHERE  property_code = 'SYSTEM_TEMP_DIR';
1 row updated.


SQL> commit;
Commit complete.



SQL> select value from apps.XDO_CONFIG_VALUES WHERE  property_code = 'SYSTEM_TEMP_DIR';
VALUE
--------------------------------------------------------------------------------
/u01/share/temp

Reference:-
How To Find the EBS XML Publisher Temporary Directory Via SQL? (Doc ID 1189723.1)

 

https://sites.google.com/site/shareapps4u/learning-topic/xml-publisher/how-to-use-xml-bursting-to-send-xml-report-via-email?tmpl=%2Fsystem%2Fapp%2Ftemplates%2Fprint%2F&showPrintDialog=1

Share

Change Allowed In Items Primary UOM in Oracle EBS R12.2.9 And Higher Versions

December 1st, 2020, posted in Oracle EBS Application
Share

Allowed to change Item’s Primary UOM in Oracle EBS R12.2.9 and higher versions

 

Prior to Oracle EBS R12.2.9, Item’s Primary Unit Of Measure(UOM) can be selected only at the time of item creation and cannot be updated once the item is saved.

There is a new feature added in Oracle EBS 12.2.9 latest version, where it is allowed change item’s primary UOM after the item is created When no transactions exist like material transactions, Sales Orders, Purchase Orders, Work Orders, Onhand etc.,

Item’s UOM won’t be updated if there are transactions or related records exists. This is to Maintain data Integrity and avoid corruption.

  1. Creating “VM TEST” master item with primary uom as Each.

oracle application,oracle ebs,oracle master item,oracle inventory master items,oracle apps dba

2. Extending “VM TEST” item to M1 inventory org.

oracle application,oracle ebs,oracle master item,oracle inventory master items,oracle apps dba

3. Query “VM TEST” item in M1 inventory org.

oracle application,oracle ebs,oracle master item,oracle inventory master items,oracle apps dba

Initially the item is created with primary UOM as “Each”. This item is newly created and there are no transactions exist.

4. Change primary uom from EACH to EA in the master item form ( primary UOM is master controlled item attribute) -> A concurrent request will be submitted when UOM is changed and saved.

oracle application,oracle ebs,oracle master item,oracle inventory master items,oracle apps dba

5. It runs “EGO Spreadsheet Java Concurrent Program” process and completes normal when the UOM is changed.

oracle application,oracle ebs,oracle master item,oracle inventory master items,oracle apps dba,EGO Spreadsheet Java Concurrent Program

Note: The concurrent program will have error like below if there are any transactions exists.

MESSAGE NAME: INV_UOM_CANNOT_UPDATE
ERROR MESSAGE : You cannot update UOM field when the inventory transactions exist in current or one of child orgs.

6. Re-Query “VM TEST” in the organization items form for M1 inventory org. You can see that primary UOM is changed to EA

oracle application,oracle ebs,oracle master item,oracle inventory master items,oracle apps dba,UOM is changed

Share

TSPITR Issue By Doing Mount Clone Database

November 15th, 2020, posted in Oracle EBS Application, Oracle Queries
Share

alter database mount clone database is a statement that forces all datafiles to be put OFFLINE when mounting the target instance.ORA-19588: archived log RECID 1003 STAMP 2001986 is no longer valid,oracle error,imam dba,dba imam,immam dba,dba immam,rman error
You’ll see it’s being used in the background when you run RMAN commands like:

transport tablespace
recover tablespace .. auxiliary destination ..
“recover table”  (12c feature)

In my case, i was trying to recover an 11.2.0.4 dropped table using “Tablespace Point In Time Recovery” by following the MOS note “How to Recover From a DROP / TRUNCATE / DELETE TABLE with RMAN (Doc ID 223543.1)“. The basic steps are:

– create pfile
– restore controlfile
– mount with “alter database mount clone database;”
– restore and recover a subset of the database with an RMAN script similar to:

RMAN> connect target /
        run {
        allocate channel c1 device type DISK;
        set until time "to_date( '13-01-2016 13:50', 'DD-MM-YYYY HH24:MI')";
        set newname for datafile 1 to "+RECO";
        set newname for datafile 3 to "+RECO";
        set newname for datafile 4 to "+RECO";
        set newname for datafile 23 to "+RECO";
        restore tablespace SYSTEM, UNDOTBS01, UNDOTBS02, TOOLS;
        switch datafile all;
        sql "alter database datafile 1,3,4,23 online";
        recover database skip forever tablespace TEMP,INDX,USERS,etc.;
        sql "alter database rename file ''+RECO/xxx/onlinelog/group_1.281.739547347'' to ''+RECO''";
        sql "alter database rename file ''+RECO/xxx/onlinelog/group_2.282.739547353'' to ''+RECO''";
        sql "alter database rename file ''+RECO/xxx/onlinelog/group_3.283.739547359'' to ''+RECO''";
        sql "alter database rename file ''+RECO/xxx/onlinelog/group_4.284.739547365'' to ''+RECO''";
release channel c1;
}

After completing the required steps, recovery raised the following error:

ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup

Of course i got the error when tried to open with resetlogs. After struggling with possible causes, i found an internal support note similar with my issue: “ORA-1547 After Recovery When Database Was Mounted As Clone (Doc ID 252181.1)“. The interesting part was this note was published at Oct 23, 2003 for versions 8.1.7.4 to 9.2.0.4 and the fix was:

Use the following workaround until the bug gets resolved :
Do not mount the database as CLONE as in :
SQL> alter database mount clone database;
but mount is as normal database with :
SQL> alter database mount;

But there’s no bug number stated in the note. Even i thought that mysterious bug must have been fixed many years ago, desperation made me try the workaround with mounting the instance with “alter database mount” and manually taking the required datafiles offline. Suprisingly it worked and i was able to open the database with resetlogs.

As a result, it’s fine for me that RMAN uses “mount clone database” statement internally, however when I’ll do TSPITR again you can be sure that I’ll mount the instance with the way I used to !!

Share

Get Current Patch Set Level of Oracle Applications Products For R12

October 11th, 2020, posted in Oracle EBS Application, Oracle Queries
Share

1) Login to OAM

(Responsibility “Oracle Applications Manager“, menu “OAM Support Cart“)

and Navigate: Support Cart -> Applications Signature -> Collect -> Check “Product Information” box -> Click on “View” (eyeglasses)

In R12

(Responsibility “System Administrator“, Menu “Oracle Application Manager“)
and Navigate : Applications Usage >> Products Installed

This will display the following patchset information :

Application Name
Current Patch Level
Product Version
Status (Installed, Shared Product, Inactive)

2) The patchset level information can be retrieved directly via sqlplus with the following diagnostic script :
$AD_TOP/sql/adutconf.sql

3) Use the below query to pull out the details

SQL>

SELECT fav.application_id,
fav.application_short_name, 
fav.application_name,
fav.basepath,
fav.creation_date,
fpi.status,
fpi.patch_level,
fpi.product_version,
fpi.TABLESPACE,
fpi.index_tablespace,
fpi.temporary_tablespace
FROM fnd_application_vl fav,
fnd_product_installations fpi
WHERE fav.application_id = fpi.application_id(+) 
ORDER BY creation_date DESC
Share

APP-PAY-06153:System Error. Procedure INIT_FORMS on Step 1

October 4th, 2020, posted in Oracle EBS Application
Share

APP-PAY-06153:System Error. Procedure INIT_FORMS on Step 1

 

Issue :

APP-PAY-06153:System Error. Procedure INIT_FORMS at Step 1 :

N:->Human Resources->Work Structures->Location

Oracle Application, Oracle Error,Oracle DBA,Oracle Apps DBA,APPS DBA

Solution :

N: System Administrator->Profile->System

Click find

Assign Site: FA: Vision Operations

Save and close

N:->Human Resource->Work Structure->Organization

 

Form is opened

Share