Failing to Submit Custom Programs in Oracle

hi,
Following the solution for the issue we been bumping in every new environment we create lately:
every single Concurrent Program created under Custom Application (XX...something) been failing to submit:

Oracle actually has a detailed solution for this issue, so I decided to re-post for all the unfortunate souls that does not have an access for Metalink:

Add the custom application to a data group.

1.  Under the System Administrator responsibility navigate to 

Security -->Oracle --> DataGroup.

2.  Query up a data group (Standard Data Group is appropriate).

3.  A list of applications associated with the standard data group will appear.

4.  Click on FILE in the toolbar menu then click on NEW.

5.  In the Application column select the custom application from the LOV.

6.  Add an Oracle ID to the ORACLE ID column (APPS is appropriate)

7.  Save the changes.

8.  Resubmit the concurrent request.

enjoy

How to set Default Output Type for Reports Submitted Using XML Publisher

hi All,

Its been a while since I had any new posts. Be assured its not due the lack of the issues ;-)

Today I want to address an issue that "hit close to home" and it remains a complete mystery how we even found our self with such a problem.

Lately I been heavily involved in Oracle EBS 11i upgrade to R12 project as Development, Integration and Deployment Lead. For User Acceptance Test phase we migrated all the custom developments to the freshly cloned EBS R12 environment (all data, setups, patches etc done as well) . Several of the customization developed for the client are custom XML Publisher reports.
The most important thing to mention about those reports - most of  them are developed using Data Template methodology and have XML Publisher Template for layout. MS Word RTF file attached to each template and its Preview Format is set to PDF (see bellow):

According to Oracle Note: 401328.1 output type for XML Publisher reports is defaulted to PDF.
However, to my great surprise, when we tried to run those reports, inside the output options of corresponding concurrent request we saw the default output format changed to RTF?!?

So basically every time users were trying to run one of the reports he (she) was prompted to open/save the RTF file.

Till now its a mystery how default format of 'PDF' was changed of 'RTF'.
After extensive search of how to get back on track, cause user won't change format manually for every request submitted, I came upon Note: 888972.1.

Generally, it explains how Patch 5612820 and Patch 7627832 provides you with solutions to setting and updating default Output Formats for XML Publisher Template.
Most relevant info in our case is profile option: FND: Default Template Output Type could be set to override the original format type.

Once the profile is set to PDF, default Output Format in concurrent request form is PDF as well and outputs are being viewed correctly by the browser.