Accessing PO Reports from INV


Some times you may Get requiremnet like running PO standard reports into Inventory

1) Login as sysadmin go To security-> responsibility-> define-> Query the Responsibility name as Inventory Super User, Vision Operations
Note down the menu name
ie : INV_NAVIGATE
Same as query the Responsibility name as Purchasing, Vision Operations
Note down the menu from menu box
ie : Purchasing SuperUser GUI



2) Go To Application -> menu

query the user menu Name as INV_NAVIGATE
And add the below entries like

Seq =1.1
Prompt =XX Purchasing Reports
Submenu= Purchasing SuperUser GUI
Function=Submit Requests
Description=XX Purchsing Menu
Grant=Yes


3) Save and compile menu

4) Switch Responsibility to Inventory
Identify the XX Purchasing Reports menu
Finally Run PO reports from Inv

Concurrent Program output in MS Excel format

1)Login as sysadmin
2) switch to Sysadmin responsibility
3)go to Install->Viewer Options
4) Add entries as Below

File Format =Text Mime
Type=application/vnd.ms-excel
Description=Microsoft Excel

5) save the changes
6) Run any concurrent program
7) Goto-> tools and Copy file
Your able to see the output into Excel format

CONCSUB

. By Using CONCSUB You can submit a concurrent request to execute and Controlling any concurrent program at UNIX(operating system level) without having to log on to Oracle Applications.
The CONCSUB executable is located at $FND_TOP/bin/CONCSUB

Syntax:

$ CONCSUB APPS username>/APPS password
responsibility application short name
responsibility name
username
[WAIT=N|Y|n seconds]
CONCURRENT
program application short name
program name
[PROGRAM_NAME=”description”]
[REPEAT_TIME= [REPEAT_INTERVAL= number]
[REPEAT_INTERVAL_UNIT= resubmission unit]
[REPEAT_INTERVAL_TYPE= resubmission type]
[REPEAT_END=resubmission end date and time]
[START=date]
[IMPLICIT= type of concurrent request
[parameter 1 ... parameter n]



Example :

CONCSUB APPS/APPS \
·················· SYSADMIN \
··················”System Administrator” \
·····················SYSADMIN \
·····················WAIT=N \
··· CONCURRENT \
··· FND \
··· FNDSCURS \
··· PROGRAM_NAME=’”Active Users”’


Syntax for Controlling Concurrent Managers

CONCSUB apps/apps_password SYSADMIN ‘System Administrator’ SYSADMIN WAIT=N CONCURRENT FND SHUTDOWN

Note : You can't use the CONCSUB to start the concurrent manager.Instead of that you can use startmgr which located in $FND_TOP/bin dir.

Enabling Report Trace via User Profile Option



1)Logon to apps under the System Administrator responsibility.

2)Navigate: Profile > System.

3)On the "Find System Profile Values" form, make sure the checkboxes for "User" and "Profiles with no Values" are checked.

4)Beside the "User" checkbox use the LOV to select the user who's activity you need to trace.

5)In the "Profile" field, type: Initialization SQL Statement - Custom
Then click the "Find" button.

6)Under the User column enter the following all on one line:
Begin fnd_ctl.fnd_sess_ctl('','','TRUE','TRUE','LOG','ALTER SESSION SET EVENTS=''10046 TRACE NAME CONTEXT FOREVER, LEVEL 4'' TRACEFILE_IDENTIFIER=''REPORT'''); end;
note: you can substitute any meaninful word for REPORT.

7)Swtich to the Responsibility needed to run the report.

8)Go directly to submit the process. When it has completed, UNSET the profile "Initialization SQL Statement - Custom" for this user and exit the application.

9)The trace file will be located in the directory identified by the following select:
select value from v$parameter where name = 'user_dump_dest';
and will include "REPORT" in the filename.

Use LEVEL 4 (as indicated above) for binds only.
Use LEVEL 8 for waits only.
Use LEVEL 12 for both.


Enabling Trace in the Before_Report Trigger

1)Open the rdf file with rwbuilder.

2)Edit the Before Report Trigger and add this line right after BEGIN

SRW.DO_SQL ('alter session set events=''10046 trace name context forever, level 4'' tracefile_identifier=''REPORT');

3)Recompile and save the report.

Use LEVEL 4 (as indicated above) for binds only.
Use LEVEL 8 for waits only
Use LEVEL 12 for both

When the report is run the trace file will be written to the udump directory which can be identified by the following select:
select value from v$parameter where name = 'user_dump_dest';

Trace will automatically turn off when the report ends.


Tracing From the Reports Builder

To enable tracing in the Reports Builder user interface:

1)Open your rdf in with rwbuilder.
2)Choose Program>Tracing.
3)Select the Trace Mode.
Select appropriate Trace Options. The trace file now logs information for the
entire Reports Builder session.

The trace file will be written to the directory from which you launched the Reports Builder.