Correct version of JDeveloper for OA Extensions to use with E-Business suite 11i to R12.x

As the usage of JDeveloper has increased developing OA Extensions to ADF Faces, we need to understand which version of JDeveloper is to be installed depending on our need.

All the details of which version of JDeveloper to use is explained in ORACLE metalink note: 416708.1

Print This Post

Importing Supplier Bank Accounts using Supplier Open Interface

In R12, You can create Supplier Bank Accounts and associate them to a Payee during Supplier Open Interface Program.

Follow below steps:
1. Load Supplier & Supplier Sites Data to the respective Interface Tables AP_SUPPLIERS_INT and AP_SUPPLIER_SITES_INT.
2. Load the respective Suppliers bank Accounts Data to the ‘IBY_TEMP_EXT_BANK_ACCTS’ Table
3. Run the Suppliers Open Interface Import

In R12, While validating/creating Supplier and Supplier Sites Data and inserting to AP and HZ Tables, a Payee is created in to the IBY Table. If the Payee is created successfully then a check is made for any related rows in ‘IBY_TEMP_EXT_BANK_ACCTS’ Table and an IBY API is called to create a Bank Account and associate it to the respective Payee.

Following conditions are to be met for successful import of Bank Account:
- Suppliers
IBY_TEMP_EXT_BANK_ACCTS.calling_app_unique_ref1 = AP_SUPPLIERS_INT.vendor_interface_id
-Supplier Site
IBY_TEMP_EXT_BANK_ACCTS.calling_app_unique_ref2  = AP_SUPPLIER_SITES_INT.vendor_site_interface_id

Note:  Bank and Bank Branch should have already been defined in the System for the successful Bank Account Import.

Print This Post

Customizing: POR_CUSTOM_PKG

POR_CUSTOM_PKG is an Oracle standard package to allow Customization at the Requisition header, line and Distribution levels, its located at $ICX_TOP/patch/115/sql/PORCUSTB.pls

Following are the profiles related to POR_CUSTOM_PKG to enable the Customizations respectively,

POR: Enable Req Header Customization
POR: Enable Requisition Line Customization
POR: Enable Req Distribution Customization

For the profile changes to have an impact, Apache Bounce is mandatory after they have been changed.

The Custom package has 3 major procedures CUSTOM_DEFAULT_REQ_HEADER, CUSTOM_DEFAULT_REQ_LINE, and CUSTOM_DEFAULT_REQ_DIST referring to a Requisition header, Line and Distributions, where the customization can be implemented.

These procedures are called only when a NEW Requisition Headers, lines and Distributions are created rather than an UPDATE performed on them.

The POR_CUSTOM_PKG can be modified to default Descriptive Flexfield values from header to Line and Distribution and to update other values on Requisitions.
To enable the customization, the user has to navigate to the Page where the Requisition DFF value is active and Requisition Header DFF Additional header Information, Requisition Line DFF Additional Line Information, and Requisition Distribution DFF Additional Distribution Information on the Checkout page

Print This Post