You must allow access to at least one attribute group while accesing EBS purchasing forms

Fresh Installation of R12 EBS Instance normally gives the below error message, We had the same issue in our freshly installed instanace and we solved it by licensing the Products from the below navigation.


Error = "You must allow access to at least one attribute group"

Login to EBS ==> Oracle Application Manager==>License Manager and License the Instance as per below screen shots.

Internet Explorer Has Modified This Page To Prevent Cross-site Scripting

Some time Oracle EBS users will get below errors on IE 9 or IE8 while opening oracle forms.

==> Error

Internet Explorer Has Modified This Page To Prevent Cross-site Scripting

==> Steps to Re-produce

The issue can be reproduced at will with the following steps:

1. Login to E-Business Suite
2. Select any Forms based responsibility
3. Select any Form function to launch Forms

==> Cause

MSIE 8 has implemented a new filter named "Cross Site Scripting [XSS] Filter"

==> Solution

Above issue can be solved by using below options

Click on internet options,

Go to the security section,

Click on the custom level button,

Scroll down to the bottom and disable, XSS filter, and save,

You can see if that is the only setting that needs to be changed,

If it still pops up, go back and disable these three as well,

1) Allow scriptlets

2) Automatic prompting for active x controls

3) Allow status bar updates via script


[Menu Bar ] >Tools > Internet Options >
[Tab] Security > [Button] Custom Level >
Scroll down to entry "Enable XSS Filter" > Select Disable XSS Filter >
Click OK
For permanent solution follow Note ID #  1059574.1]

Hijrah Calendar Support in Oracle E-Business Suite Release 12

Due to arabic localization we might need to have hijrah calender in instance please below note to enable this.


Hijrah Calendar Support in Oracle E-Business Suite Release 12 [ID 738581.1]

Concurrent Manager is not started in EBS Clone

While cloning we some time face the issue that test or development instance still showing production server name entries in test's standard manager or even table FND_CONCURRENT_QUEUES have the production entries.

We had this issue and we solved it by using the below steps:-


1. Shutdown all the managers.

2. Run the CMCLEAN.SQL (don't forget to commit).
134007.1 Ext/Pub CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables

=>See if you have wrong entries in target node columns of FND_CONCURRENT_QUEUES table

3. update FND_CONCURRENT_QUEUES set target_node='Test' where target_node='Prod'
commit;

=>See if you have wrong entries in node_name columns of FND_CONCURRENT_QUEUES table

update FND_CONCURRENT_QUEUES set node_name='target node' where node_name='source node'
commit;
4. Start the Standard manager and verify the table entrie with below query.

select * from FND_CONCURRENT_QUEUES


==> Below steps will also help out more in troubleshooting Concurrent Manager issues


When we cloned outinstance, We had an issue with concurrent manager and not started

We stoped the concurrent manager

$COMMON_TOP/admin/scripts/HOST_NAME
. adcmctl.sh stop apps/password

When I have checked the ICM logfile there is an error entry as
Could not initialize the Service Manager FNDSM_HOSTNAME_SID. Verify that HOSTNAME has been registered for concurrent processing.

The cause of this issue was FND_NODES table having incorrect node entries (old node from the Source Instance) and that no Service Manager was found for the existing node.

To solve this problem, need to perform the below steps

1.  Stop all middle tier services including the concurrent managers.

2.  Stop the database.

3.  Start the database.

4.  Connect SQLPLUS as APPS user and run the following :

EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;

5.  Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and webtiers to repopulate the required system tables.

6.  Connect to SQLPLUS as APPS user and run the following statement :
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';

If the above SQL does not returning any value then please do the following:

Go to $FND_TOP/patch/115/sql

Connect SQLPLUS as APPS user and run the following script :

SQL> @afdcm037.sql;

This script will create libraries for FNDSM and create managers for preexisting nodes.
Check again that FNDSM entries now exist:

select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';

7.  Go to cd $FND_TOP/bin
$ adrelink.sh force=y "fnd FNDLIBR"
$ adrelink.sh force=y "fnd FNDSM"
$ adrelink.sh force=y "fnd FNDFS"
$ adrelink.sh force=y "fnd FNDCRM"

8.  Run the CMCLEAN.SQL script from the referenced note below (don't forget to commit).

9.  Start the middle tier services including your concurrent manager.

Now cloned instance concurrent managers became active. Above is applicable to both 11i and R12 instances.

How to Open or Close Period in Purchasing - R12

Generally we have the business requirement to open or close the periods in oracle purchasing which can be done by using the below steps in R12.


1.       Navigate to Purchase Super User à Setup

       à Financials Accounting  àControl Purchasing Periods
      

After searching your required period from above screen Save it. Please also consult the ID # 335.1 for proper period closures due to dependency of subledgers.  

How to mount cdrom in Linux if not working since installation

while making stage of 12.1.3 in OEL 5.5 getting below error

./adautostg.pl: Permission denied

==> Reason of error:

there was not bootable cd

==> Steps to resolve this error:-

 unmount

umount /media/R1211start/

now check mount /mnt/cdrom

mount: can't find /mnt/cdrom in /etc/fstab or /etc/mtab

add cdrom in fstab and mtab file and write below line in /etc/fstab

==>First check if cdrom entry are exist in /dev

cdrom entry is exist or not

  ls /dev/cd*

make a backup copy of fstab file and then add below line in fstab file

cp /etc/fstab /etc/fstab.bkp

/dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0

mkdir -p /media/cdrom

unmount

umount /media/R1211start/

mount cd with right path

mount /dev/cdrom /media/cdrom

The GL date is not in an open period

Normally EBS end users will be getting the below error while receiving in Oracle Inventory:-

==> Error:

APP-PO-14230: The GL date is not in an open period
Or- APP-PO-14376: Please enter a GL date within an open purchasing period

==> Steps to Reproduce:

1. Navigate to Enter Receipts form:
2. Save a receipt.

==> Solution:-

1. Ensure the Receipt Date falls into a GL Period that has Status=Open or Future:

Setup / Financials / Accounting / Open and Close periods
-OR- Setup / Open and Close periods

2. Ensure the Purchasing Period is Open:

Setup / Financials / Accounting / Control Purchasing Period

3. Please note that the Inventory period must also be Open:

Accounting close cycle / Inventory Accounting Periods

(Note )To determine the Status of the periods, substitute the pertinent start and end dates in the sql below:

GL Period:

select set_of_books_id, period_name, decode(closing_status,'O','Open', 'C','Closed', 'F','Future', 'N','Never', closing_status) gl_status, start_date, end_date
from gl_period_statuses
where trunc(start_date) > sysdate-40 --adjust date as needed and trunc(start_date) < sysdate+1 and application_id = 101
order by application_id,start_date desc

PO Period:

select set_of_books_id, application_id, period_name, decode(closing_status,'O','Open', 'C','Closed', 'F','Future', 'N','Never', closing_status) po_status, start_date, end_date
from gl_period_statuses
where trunc(start_date) > sysdate-40 --adjust date as needed and trunc(start_date) < sysdate+1 and application_id = 201
order by application_id,start_date desc

==> Referecen Metalink ID [ID 552244.1