OAF Setup for DB and APP Connection

All the custom page can be developed and tested in our work system with the help of JDeveloper before deploying it to the Oracle Application. But still it need access to Application and DB in order to avoid the unnecessary error while deploying the custom page in the E-Business Suite.

For developing any custom page we need both DB as well APP connection detail string in order to fetch the database objects and application infra for the proper deployment. If the custom development runs well in JDeveloper then it will surely works well in the Application side too.. !!!


A. Database Connection setup

Enter the following details in the DB Setup

Navigation: JDevloper (Tools --> Project Properties --> Oracle Application --> Database Connection)

Step 1: Enter the Database name (Naming Convention can be anything and not related to DB TNS entry)

Step 2: Enter the DB Username and Password

Step 3: Enter the DB Host name, Port and SID as per your DB TNS entry

Step 4: Test the connection and make sure it return the status "SUCCESS"

B. Application Setup for the Login User with DBC file

Keep the DBC file under the path "jdevhome\jdev\dbc_files\secure"



Make sure the FND user have the correct responsibility attached before mapping it in the APP setup

Enter the following details in the APP Setup

Navigation: JDevloper (Tools --> Project Properties --> Oracle Application --> Runtime Connection)

Step 1: Place the DBC file under the specified path as mentioned above and BROWSE and map it under the 'DBC File Name'

Step 2: Enter the Username and Pwd with right Application Short name and Responsibility Key.

DBC file in JDeveloper Tool

How to get the DBC file from APP Server to use it in JDeveloper Tool

Step 1: Login to APP Server and go to $INST_TOP

cd $INST_TOP/appl/fnd/12.0.0.0/secure

ls -ltr

-rw-------. 1 applmgr dba 827 Jul 10 06:13 DEV.dbc

Step 2: Permission will be limited for other users other than application manager, so cat the file and save it

cat DEV.dbc

Copy the content and save it with .dbc extension

Step 3: JDevloper Path for DBC connection

If once saved the file, place it under jdevhome\jdev\dbc_files\secure

If all 3 steps done, try playing with OAF Page !!!

Microsoft Visual Basic Run-time error '1004': Method 'VBProject' of object '_Workbook' failed

To fix this issue, pls perform the below setups in MICROSOFT EXCEL to accept the WEBADI transaction in VBProject Workbook.

In Excel, use the following navigation:

Step 1: Open the Microsoft Excel and go to FILE à OPTIONS

Step 2: On the left, click on the Trust Center

Step 3: Click on the Trust Center Settings button and go to Macro Settings and Click on “Trust access to the VBA project object model”

Upgrading the EBS system from INDIA LOCALIZATION to GST

Apply the GST patch as per below order,

GST : Path to GST Implementation - Patch Details (Doc ID 2268465.1) 
India GST - Latest Patches Released (RUP 11 onwards) (Doc ID 2342288.1) 

<Read pre-requisites or instructions from DOC ID 2268465.1 >

1) India GST functional patch

General Ledger Patch : Patch 19283503:R12.GL.C
Revised Co-Existence Patch : Patch 26153906:R12.JAI.C

2) TDS migration patch (This patch will migrate the TDS setup to the new system) -

Note: TDS Migration Steps Document(OFI-GST- TDS Migration.pdf)

Patch 26194366:R12.JAI.C 
Patch 26273448:R12.JAI.C 

IMPORTANT : These Patches can be applied with the Co -Existence patch

Note: All the OPEN transactions (Invoice / Purchase Order / Receipts) need to close before proceeding to the below steps.

3) GST Enablement  patch

GST Enablement patch Patch 26003443:R12.JAI.C 

4) TDS Enablement patch + Concurrent Program for Migrating the TDS Transactions

TDS Enablement patch Patch 26171921:R12.JAI.C  

5) RUP Patches

Apply RUP 11 patches
Step 1. Apply Patch 27421320:R12.JAI.C
Step 2. Apply Patch 27435589:R12.JAI.C (Inclusion Document)
Note : This patch will be pre-requisite for all patches which will be released in future.
Step 3. Apply Patch 22698083:R12.AP.C

Please read pre-requisites or instructions from DOC ID 2342288.1 >

Apply SEP Consolidation patches
Apply Patch 28656394:R12.JAI.C 
pre-requisites :
Patch 27421320:R12.JAI.C 
Patch 22698083:R12.AP.C 
Patch 27538659:R12.BOM.D

Patching cycle needs to apply in the correct listed order as a separate ADOP cycle. Don't consolidate all the patches in a single cycle because certain Techno-Functional activity needs to carried out in-between the patching implementation


At end of patch completion the Invoice workbench form will prevent the invoice creation due to package AP_INVOICES_UTILITY_PKG invalidation. Try the below steps which we have already posted to overcome this.

https://oracleapplications90.blogspot.com/2019/06/apinvoicesutilitypkg-package-body-is.html