Thursday, 31 July 2014

Order Import Interface (Sales Order Conversion)

Order Import Interface (Sales Order Conversion)

Order Import enables you to import Sales Orders into Oracle Applications instead of manually entering them.

Prerequisites:
  • Order Type
  • Line Type
  • Items
  • Customers
  • Ship Method/ Freight Carrier
  • Sales Person
  • Sales Territories
  • Customer Order Holds
  • Sub Inventory/ Locations
  • On hand Quantity
Interface tables:
  • OE_HEADERS_IFACE_ALL
  • OE_LINES_IFACE_ALL
  • OE_ACTIONS_IFACE_ALL
  • OE_ORDER_CUST_IFACE_ALL
  • OE_PRICE_ADJS_IFACE_ALL
  • OE_PRICE_ATTS_IFACE_ALL
Base tables:
  • OE_ORDER_HEADERS_ALL
  • OE_ORDER_LINES_ALL
Pricing tables:
  • QP_PRICING_ATTRIBUTES
Concurrent Program:
  • Order Import
Validations:
  • Check for sold_to_org_id. If does not exist, create new customer by calling create_new_cust_info API.
  • Check for sales_rep_id. Should exist for a booked order.
  • Ordered_date should exist (header level)
  • Delivery_lead_time should exist (line level)
  • Earliest_acceptable_date should exist.
  • Freight_terms should exist
Notes:
During import of orders, shipping tables are not populated. If importing customers together with the order, OE_ORDER_CUST_IFACE_ALL has to be populated and the base tables are HZ_PARTIES, HZ_LOCATIONS.

Orders can be categorized based on their status:
  1. Entered orders
  2. Booked orders
  3. Closed orders

Order Import API OE_ORDER_PUB.GET_ORDER and PROCESS_ORDER can also be used to import orders.

Important Columns:
Some important columns that need to populated in the interface tables:
OE_HEADERS_IFACE_ALL:
  • ORIG_SYS_DOCUMENT_REF
  • ORDER_SOURCE
  • CONVERSION_RATE
  • ORG_ID
  • ORDER_TYPE_ID
  • PRICE_LIST
  • SOLD_FROM_ORG_ID
  • SOLD_TO_ORG_ID
  • SHIP_TO_ORG_ID
  • SHIP_FROM_ORG_ID
  • CUSTOMER_NAME
  • INVOICE_TO_ORG_ID
  • OPERATION_CODE
  • OE_LINES_IFACE_ALL
  • ORDER_SOURCE_ID
  • ORIG_SYS_DOCUMENT_REF
  • ORIG_SYS_LINE_REF
  • ORIG_SYS_SHIPMENT_REF
  • INVENTORY_ITEM_ID
  • LINK_TO_LINE_REF
  • REQUEST_DATE
  • DELIVERY_LEAD_TIME
  • DELIVERY_ID
  • ORDERED_QUANTITY
  • ORDER_QUANTITY_UOM
  • SHIPPING_QUANTITY
  • PRICING_QUANTITY
  • PRICING_QUANTITY_UOM
  • SOLD_FROM_ORG_ID
  • SOLD_TO_ORG_ID
  • INVOICE_TO_ ORG_ID
  • SHIP_TO_ORG_ID
  • PRICE_LIST_ID
  • PAYMENT_TERM_ID

Difference between Conversion and Interface in Oracle Apps

Interfaces:

  • It is schedule concurrent Process which will be executed multiple times
  • We will not be knowing flat file Volume
  • We need to handle all the expected exceptions
  • Error Reports and sending mail alerts, If any error occurs
  • Only in Enhancement or customization projects
Conversion:
  • One time data transfer
  • We will be know exact falt file Volume
  • No need to know the exceptions
  • Not required to upload all records
  • Only in Implementation,Migration or up-gradation projects

Tuesday, 29 July 2014

Interfaces and Conversions in Oracle Applications

Interfaces and Conversions in Oracle Applications

Overview:
Oracle provides flexible and flexible tools in the form of Interface programs to import the master and transactional data like Customers, Invoices, and Sales Orders etc from external systems into Oracle Applications. This article briefs you about some of the major interface programs.

Conversion/Interface Strategy:

Data Mapping
During the data mapping process, list of all the data sets and data elements that will need to be moved into the Oracle tables as part of conversion are identified. Data mapping tables are prepared as part of this activity that show what are the data elements that are needed by the target system to meet the business requirements and from where they will be extracted in the old system.

Download Programs
After the conversion data mapping is complete, download programs are developed that are used to extract the identified conversion data elements from the current systems in the form of an ASCII flat file. The structure of the flat file must match the structure of the Oracle standard interface tables. These flat files generated may be in text form or a comma or space delimited, variable or fixed format data file.

Upload Program
Once the data has been extracted to a flat file, it is then moved to the target file system and the data from the file is loaded into user defined staging tables in the target database using SQL Loader or UTL_FILE utilities. Then programs are written and run which validate the data in the staging tables and insert the same into the Oracle provided standard Interface tables.

Interface Program
Once the interface tables are populated, the respective interface program (each data element interface has a specific interface program to run) is submitted. The interface programs validate the data, derive and assign the default values and ultimately populate the production base tables.

Interface/Conversion examples with details

oracle apps Interface Table Names

ORACLE FINANCIALS – PAYABLES - INVOICES
AP_INVOICES_INTERFACE
AP_INVOICE_LINES_INTERFACE
AP_INTERFACE_REJECTIONS
AP_INTERFACE_CONTROLS

ORACLE FINANCIALS – RECEIVABLES - CUSTOMERS
RA_CUSTOMERS_INTERFACE_ALL
RA_CUSTOMER_PROFILES_INT_ALL
RA_CONTACT_PHONES_INT_ALL
RA_CUSTOMER_BANKS_INT_ALL
RA_CUST_PAY_METHOD_INT_ALL
HZ_PARTY_INTERFACE

ORACLE FINANCIALS – RECEIVABLES - INVOICES
RA_INTERFACE_LINES_ALL
RA_INTERFACE_DISTRIBUTIONS_ALL
RA_INTERFACE_SALESCREDITS_ALL

ORACLE FINANCIALS – RECEIVABLES – LOCK BOX
AR_PAYMENTS_INTERFACE_ALL

ORACLE FINANCIALS – RECEIVABLES - TAX
AR_TAX_INTERFACE

ORACLE FINANCIALS - CASH MANAGEMENT – BANK STATEMENTS
CE_STATEMENT_HEADERS_INT_ALL
CE_STATEMENT_LINES_INTERFACE

ORACLE FINANCIALS - FIXED ASSETS
FA_INV_INTERFACE

ORACLE FINANCIALS - GENERAL LEDGER – JOURNAL ENTRY
GL_INTERFACE
GL_INTERFACE_HISTORY
GL_INTERFACE_CONTROL
GL_IMPORT_REFERENCES

ORACLE MANUFACTURING – COST MANAGEMENT
CST_PC_ITEM_COST_INTERFACE
CST_PC_COST_DET_INTERFACE

ORACLE MANUFACTURING - INVENTORY
MTL_REPLENISH_HEADERS_INT
MTL_REPLENISH_LINES_INT
MTL_SERIAL_NUMBERS_INTERFACE
MTL_SYSTEM_ITEMS_INTERFACE
MTL_TRANSACTION_LOTS_INTERFACE
MTL_TRANSACTIONS_INTERFACE

ORACLE MANUFACTURING – PURCHASING – PURCHASE ORDERS
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
PO_DISTRIBUTIONS_INTERFACE
PO_REQUISITIONS_INTERFACE_ALL
PO_REQ_DIST_INTERFACE_ALL
PO_RESCHEDULE_INTERFACE

ORACLE MANUFACTURING – PURCHASING - RECEIVING 
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
RCV_LOTS_INTERFACE
RCV_SERIALS_INTERFACE

ORACLE MANUFACTURING - ORDER ENTRY – SALES ORDERS
SO_HEADERS_INTERFACE_ALL
SO_HEADER_ATTRIBUTES_INTERFACE
SO_LINES_INTERFACE_ALL
SO_LINE_ATTRIBUTES_INTERFACE
SO_LINE_DETAILS_INTERFACE
SO_PRICE_ADJUSTMENTS_INTERFACE
SO_SALES_CREDITS_INTERFACE

ORACLE MANUFACTURING - MASTER SCHEDULING/MRP
MRP_FORECAST_INTERFACE
MRP_SCHEDULE_INTERFACE

ORACLE MANUFACTURING - SHOP FLOOR MANAGEMENT
WSM_LOT_JOB_INTERFACE
WSM_STARTING_LOTS_INTERFACE
WSM_LOT_MOVE_TXN_INTERFACE

ORACLE MANUFACTURING - QUALITY
QA_RESULTS_INTERFACE

ORACLE MANUFACTURING - WORK IN PROCESS
WIP_MOVE_TXN_INTERFACE
CST_COMP_SNAP_INTERFACE
WIP_COST_TXN_INTERFACE
WIP_JOB_SCHEDULE_INTERFACE
WIP_JOB_DTLS_INTERFACE

|Oracle apps Interface Table Names with standard concurrent porgram details

ORACLE FINANCIALS – PAYABLES - INVOICES
AP_INVOICES_INTERFACE
AP_INVOICE_LINES_INTERFACE
AP_INTERFACE_REJECTIONS
AP_INTERFACE_CONTROLS

C.P. = Payables Open Interface Import

ORACLE FINANCIALS – RECEIVABLES - CUSTOMERS
RA_CUSTOMERS_INTERFACE_ALL
RA_CUSTOMER_PROFILES_INT_ALL
RA_CONTACT_PHONES_INT_ALL
RA_CUSTOMER_BANKS_INT_ALL
RA_CUST_PAY_METHOD_INT_ALL
HZ_PARTY_INTERFACE

ORACLE FINANCIALS – RECEIVABLES - INVOICES
RA_INTERFACE_LINES_ALL
RA_INTERFACE_DISTRIBUTIONS_ALL
RA_INTERFACE_SALESCREDITS_ALL

C.P. = Autoinvoice Import Program

ORACLE FINANCIALS – RECEIVABLES – LOCK BOX
AR_PAYMENTS_INTERFACE_ALL

ORACLE FINANCIALS – RECEIVABLES - TAX
AR_TAX_INTERFACE

ORACLE FINANCIALS - CASH MANAGEMENT – BANK STATEMENTS
CE_STATEMENT_HEADERS_INT
CE_STATEMENT_LINES_INTERFACE
CE_HEADER_INTERFACE_ERRORS

CE_LINE_INTERFACE_ERRORS

C.P. = Bank Statement Import

ORACLE FINANCIALS - FIXED ASSETS
FA_INV_INTERFACE

ORACLE FINANCIALS - GENERAL LEDGER – JOURNAL ENTRY
GL_INTERFACE
GL_INTERFACE_HISTORY
GL_INTERFACE_CONTROL
GL_IMPORT_REFERENCES

C.P. = Program - Import Journals


Budget 

GL_BUDGET_INTERFACE

Daily Rates


Gl_DAILY_RATES_INTERFACE

ORACLE MANUFACTURING – COST MANAGEMENT
CST_PC_ITEM_COST_INTERFACE
CST_PC_COST_DET_INTERFACE

ORACLE MANUFACTURING - INVENTORY
MTL_REPLENISH_HEADERS_INT
MTL_REPLENISH_LINES_INT
MTL_SERIAL_NUMBERS_INTERFACE
MTL_SYSTEM_ITEMS_INTERFACE
MTL_TRANSACTION_LOTS_INTERFACE
MTL_TRANSACTIONS_INTERFACE

ORACLE MANUFACTURING – PURCHASING – PURCHASE ORDERS
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
PO_DISTRIBUTIONS_INTERFACE
PO_INTERFACE_ERRORS

C.P. = Import Standard Purchase Orders

PO_REQUISITIONS_INTERFACE_ALL
PO_REQ_DIST_INTERFACE_ALL
PO_RESCHEDULE_INTERFACE


C.P. = Requisition Import ( For Purchase Requisition )

ORACLE MANUFACTURING – PURCHASING - RECEIVING 
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
RCV_LOTS_INTERFACE
RCV_SERIALS_INTERFACE

ORACLE MANUFACTURING - ORDER ENTRY – SALES ORDERS
SO_HEADERS_INTERFACE_ALL
SO_HEADER_ATTRIBUTES_INTERFACE
SO_LINES_INTERFACE_ALL
SO_LINE_ATTRIBUTES_INTERFACE
SO_LINE_DETAILS_INTERFACE
SO_PRICE_ADJUSTMENTS_INTERFACE
SO_SALES_CREDITS_INTERFACE

ORACLE MANUFACTURING - MASTER SCHEDULING/MRP
MRP_FORECAST_INTERFACE
MRP_SCHEDULE_INTERFACE

ORACLE MANUFACTURING - SHOP FLOOR MANAGEMENT
WSM_LOT_JOB_INTERFACE
WSM_STARTING_LOTS_INTERFACE
WSM_LOT_MOVE_TXN_INTERFACE

ORACLE MANUFACTURING - QUALITY
QA_RESULTS_INTERFACE

ORACLE MANUFACTURING - WORK IN PROCESS
WIP_MOVE_TXN_INTERFACE
CST_COMP_SNAP_INTERFACE
WIP_COST_TXN_INTERFACE
WIP_JOB_SCHEDULE_INTERFACE
WIP_JOB_DTLS_INTERFACE

Sunday, 27 July 2014

Document Sequencing of Payments : AP Module 12 Release New Features

Document Sequencing of Payments

If you used document sequencing for payments in Release 11i, your document sequence category has been migrated from the payment document, which is associated with a bank account and hence, legal entity in Release 12, to the bank account uses entity. If you require, you can also specify the document sequence category at the bank account payment method and payment document levels. These changes are necessary to preserve the option of having document sequence categories vary across operating Units. 

Integration with Oracle Payments for Funds Disbursement
The process to issue payments from Oracle Payables (AP) changes in Release 12 to use the new Oracle Payments funds disbursement process. The benefit of these changes is to help ensure an implementation that best supports a controlled and efficient disbursement flow, and provide enhancements over the way payment processing was set up in different products.

A significant change for Payables users is that Payments uses XML Publisher for payment formatting. During the upgrade, Payments will upgrade the seeded Payables payment formats to Payments formats that can be used with configurable XML Publisher templates. If you have custom payment formats, you need to migrate them to XML Publisher in order to use them in Release 12. Payments continues to use the concept of Payment Methods, as they worked in Payables, however there are some minor enhancements, which are noted below. The Future Dated Payments feature has been renamed to Bills Payable in Release 12 and setup has moved from the payment document on an internal bank account to the payment method in Oracle Payments.

In Release 12, the process of making EDI payments using Oracle e-Commerce Gateway has changed, details are noted below.

In Release 12, the Automatic Bank Transmission and XML Payments features are obsolete, as Oracle Payments provides enhanced features that meet the same requirements.

During the upgrade, payment batches in Payables are upgraded to payment instructions in Oracle Payments. Payments created in those payment batches, however, are not upgraded. Payments remain in Oracle Payables for review and reporting. In Release 12, new payments can be viewed in both Payments and Payables.

Payment Formats

During the Release 12 Oracle Payments upgrade, one Oracle XML Publisher template is created and linked to one Oracle Payments format for each Oracle Payables (AP) payment program that is linked to a format definition. In Payables, you can create different format definitions linked to the same payment program. So for each AP format definition, the upgrade creates one Payment Process Profile linked to the Oracle Payments format.

The payment programs that controlled the building and formatting of payments and the programs that created the separate remittance advice documents are obsolete with Release 12 and the integration with Oracle Payments.

The following tables display the mapping from seeded 11i AP Payment Formats to the new Release 12 Oracle Payments XML Publisher Formats. Obsolete formats are so noted.


Source 11i Payment Format (Program)
Oracle Payables
Release 12 Oracle Payments Format Name (Code)
Long Check Format (APXPBFEG)
External Check Format
(IBY_PAY_CHK_STANDARD_2)
Long Check Format; stub after payment
(APXPBFEG)
External Check Format
(IBY_PAY_CHK_STANDARD_2A)
Long Laser Format (APXPBFEL)
Laser Check Format (IBY_PAY_CHK_LASER)
Long Laser Format; stub after payment
(APXPBFEL)
Laser Check Format (Stub After Payment)
(IBY_PAY_CHK_LASER_A)
Short Check Format (APXPBFEG)
External Check Format
(IBY_PAY_CHK_STANDARD_2A)
Short Form Feed Format (APXPBFEF)
External Form Feed Check Format
(IBY_PAY_CHK_FORM_FEED_2)
Short Form Feed Format; stub after payment
(APXPBFEF)
External Form Feed Check Format (Stub After
Payment) (IBY_PAY_CHK_FORM_FEED_2A)
Standard Check Format (APXPBFOR)
Standard Check Format
(IBY_PAY_CHK_STANDARD_1)
Standard Check Format; stub after payment
(APXPBFOR)
Standard Check Format (Stub After Payment)
(IBY_PAY_CHK_STANDARD_1A)
US Treasury Check (APXPBFUS)
US Treasury Format
(IBY_PAY_CHK_TREASURY)
BACS 1/2 Inch Tape (APXPBFBC)
UK BACS 1/2 Inch Tape Format
(IBY_PAY_EFT_BACS_UK)
EDI Outbound Program (APECEPYO)
Obsolete
NACHA Payment Format (APXNACHA)
US NACHA CCD Format
(IBY_PAY_EFT_NACHA_CCD_US)
XML Payment Format (APXMLPMT)
XML Payment Format (APXMLPMT) Obsolete

Source 11i Payment Format (Program)
Oracle Federal Payables
Release 12 Oracle Payments Format Name
(Code)
BD CCDP format (FVBLCCDP)
US Bulk CCDP Format
(IBY_PAY_EFT_FED_BULK_CCDP)
BD NCR Format (FVBLNCR)
US Bulk NCR Format
(IBY_PAY_EFT_FED_BULK_NCR_1)
Bulk PPDP format (FVBLPPDP)
US Bulk PPDP Format
(IBY_PAY_EFT_FED_BULK_PPDP)
BD Sal/Trv NCR Format (FVBLSLTR)
US Bulk Salary and Travel NCR Format
(IBY_PAY_EFT_FED_BULK_NCR_2)
Bulk Data CCD+ Consolidated Payment File
Program (FVCOCCDP)
US CCDP Consolidated Format
(IBY_PAY_EFT_FED_CCDP_CONSOL)
CTX Consolidated File Payment Program
(FVCONCTX)
US PPDP Consolidated Format
(IBY_PAY_EFT_FED_PPDP_CONSOL)
Bulk Data PPD+ Consolidated Payment File
Program (FVCOPPDP)
US CTX Consolidated Format
(IBY_PAY_EFT_FED_CTX_CONSOL)
SPS CCD Format (FVSPCCD)
US SPS CCD Format
(IBY_PAY_EFT_FED_SPS_CCD)
SPS CCDP Format (FVSPCCDP)
US SPS CCDP Format
(IBY_PAY_EFT_FED_SPS_CCDP)
SPS Check NCR Format (FVSPNCR)
US SPS NCR Format
(IBY_PAY_EFT_FED_SPS_NCR)
SPS PPD Format (FVSPPPD)
US SPS PPD Format
(IBY_PAY_EFT_FED_SPS_PPD)
SPS PPDP Format (FVSPPPDP)
US SPS PPDP Format
(IBY_PAY_EFT_FED_SPS_PPDP)
ECS Check NCR Format (FVTIACHB)
US ECS NCR Check Format
(IBY_PAY_EFT_FED_ECS_NCR)
ECS CCDP Format (FVTIACHP)
US ECS CCDP Format
(IBY_PAY_EFT_FED_ECS_CCDP)
CTX Vendor Format (FVTICTX)
US CTX Format (IBY_PAY_EFT_FED_CTX)
ECS CCD Format (FVTPCCD)
US ECS CCD Format
(IBY_PAY_EFT_FED_ECS_CCD)
ECS PPD Format (FVTPPPD)
US ECS PPD Format
(IBY_PAY_EFT_FED_ECS_PPD)
ECS PPDP Format (FVTPPPDP)
US ECS PPDP Format
(IBY_PAY_EFT_FED_ECS_PPDP)
Summary Schedules (FVSUMSCH)
Obsolete
ECS and SPS Summary Schedules
IBY_PAY_EFT_FED_ECS_SUM_SCHED and
IBY_PAY_EFT_FED_SPS_SUM_SCHED
Source 11i Payment Format (Program)
Argentina
Release 12 Oracle Payments Format Name
(Code)
Argentine Check Format (JLARPCFP)
Argentine Check Format
(IBY_PAY_CHK_AR)
Source 11i Payment Format (Program)
Austria
Release 12 Oracle Payments Format Name
(Code)
Austrian Foreign EFT (JEATIEFT)
Obsolete
Austrian Domestic (JEATREFD)
Obsolete
Austrian Transferral 1 (JEATPPF1)
Obsolete
Austrian Transferral 2 (JEATPPF2)
Obsolete
Austrian Check with Remittance Advice
(JEATPPF3)
Obsolete
Austrian Check with Remittance Advice FWG
(JEATPPF4)
Obsolete
Austrian Foreign Transfer Order (JEATPPF5)
Obsolete
Source 11i Payment Format (Program)
Belgium
Release 12 Oracle Payments Format Name
(Code)
Belgian Format 1 (JEBEEF01)
Belgian EFT Format
(IBY_PAY_EFT_DOMESTIC_BE)
Belgian Format 2 (JEBEEF02)
Belgian EFT Format
(IBY_PAY_EFT_DOMESTIC_BE)

Source 11i Payment Format (Program)
Brazil
Release 12 Oracle Payments Format Name
(Code)
Brazilian Check Format (JLBRPCFP)
Brazilian Check Format (IBY_PAY_CHK_BR)
Brazilian Bordero (JLBRPBOR)
Brazilian Bordero Format
(IBY_PAY_CHK_OBRDERO_BR)
Source 11i Payment Format (Program)
Chile
Release 12 Oracle Payments Format Name
(Code)
Chilean Check Format (JLCLPCFP)
Chilean Check Format (IBY_PAY_CHK_CL)

Source 11i Payment Format (Program)
Colombia
Release 12 Oracle Payments Format Name
(Code)
Colombian Check 1 (JLCOPCF1)
Colombian Check 1 Format
(IBY_PAY_CHK_1_CO)
Colombian Check 2 (JLCOPCF2)
Colombian Check 2 Format
(IBY_PAY_CHK_2_CO)
Source 11i Payment Format (Program)
Denmark
Release 12 Oracle Payments Format Name
(Code)
Danish GiroBank Domestic (JEDKEIGO)
Obsolete
Danish GiroBank Foreign (JEDKEUGO)
Obsolete
Danish Unitel (JEDKEUNI)
Obsolete

Source 11i Payment Format (Program)
Finland
Release 12 Oracle Payments Format Name
(Code)
Finnish LMP2 Payment Format (JEFILLMP)
Finnish LMP2 EFT Format
(IBY_PAY_EFT_LMP2_FI)
Finnish LUM Payment Format (JEFILLUM)
Finnish LUM EFT Format
(IBY_PAY_EFT_LUM_FI)
Finnish LMP3 Payment Format (JEFILLMP3)
Finnish LMP3 EFT Format
(IBY_PAY_EFT_LMP3_FI)
Finnish ULMP Payment Format (JEFILULM)
Obsolete
Source 11i Payment Format (Program)
France
Release 12 Oracle Payments Format Name
(Code)
Billet a Ordre France (JEFRAP02) (Also
referred to as: French PRMSRY Note EUR,
French Bill Of Exchange, French Bill of EXCH
EUR)
French Promissory Note Format
(IBY_PAY_PROMISSORY_NOTE_FR)
Cheque Francais (JEFRAP01)
French Check Format (IBY_PAY_CHK_FR)
Cheque Francais; stub after payment
(JEFRAP01)
French Check Format (Stub After Payment)
(IBY_PAY_CHK_FR_A)
Virement Francais (AFB) (JEFRAP03)
French EFT Format (IBY_PAY_EFT_FR)


Source 11i Payment Format (Program)
Norway
Release 12 Oracle Payments Format Name
(Code)
Norwegian BBS (JENOPBDR)
Norwegian BBS Format
(IBY_PAY_EFT_BBS_NO)
Norwegian Telepay (JENOPTGN)
Forwegian Telepay EFT Format
(IBY_PAY_EFT_TELPAY_NO)
Norwegian Datadialog Payment Format
(JENOPDDG)
Obsolete
Source 11i Payment Format (Program)
Poland
Release 12 Oracle Payments Format Name
(Code)
Polish Pekao Credit Transfers Format
(JEPLEFT1)
Polish Pekao Credit Transfers Format
(IBY_PAY_EFT_CREDIT_TRANS_PL)
Polish Pekao Payments (JEPLEFT2)
Polish Pekao Payment Order Format
(IBY_PAY_EFT_PAY_ORDER_PL)
Polish Citibank MTMS EFT Format
(JEPLEFT3)
Polish Citibank MTMS EFT Format
(IBY_PAY_EFT_CITI_MTMS_PL)
Source 11i Payment Format (Program)
Portugal
Release 12 Oracle Payments Format Name
(Code)
Portuguese Check (JEPTBFOR)
Portuguese Check Format
(IBY_PAY_CHK_PT)
Portuguese EFT (JEPTPEFT)
Portuguese EFT Format (IBY_PAY_EFT_PT)
Source 11i Payment Format (Program)
Spain
Release 12 Oracle Payments Format Name
(Code)
Spanish EFT (JEESPEFT)
Spanish Magnetic Format (IBY_PAY_EFT_ES)
Spanish Cheque (JEESAPCP)
Spanish Check Format (IBY_PAY_CHK_ES)
Spanish PRMSRY Note EUR (JEESAPLC)
Spanish Bill of Exchange Format
(IBY_PAY_CHK_BOE_ES)
Source 11i Payment Format (Program)
Sweden
Release 12 Oracle Payments Format Name
(Code)
Swedish Bankgiro Inland (JESEPBAI)
Swedish Domestic Bankgiro Format
(IBY_PAY_EFT_BANKGIRO_SE)
Swedish Bankgiro SISU (JESEPBSI)
Swedish SISU Bankgiro Format
(IBY_PAY_EFT_SISU_BANKGIRO_SE)
Swedish Bankgiro UTLI (JESEPBUT)
Swedish UTLI Bankgiro Format
(IBY_PAY_EFT_UTLI_BANKGIRO_SE)
Swedish Postgiro Inland (JESEPPOI)
Swedish Domestic Postgiro Format
(IBY_PAY_EFT_POSTGIRO_SE)
Swedish Postgiro Utland (JESEPPOU)
Swedish Foreign Postgiro Format
(IBY_PAY_EFT_FOR_POSTGIRO_SE)

Payment Methods
The upgrade migrates the seeded payment methods of check, electronic, wire, and clearing from Payables to the new, extensible Oracle Payments payment method entity.
Note the following changes:
  • Wire - No longer restricted to payments made outside Oracle Applications. You can link this payment method to a payment process profile for actual wire transfers.
  • Clearing - Seeded as inactive in Payments since users have enhanced options for handling intercompany processing in Release 12. It is recommended that you no longer use this payment method, but rather use the new Intercompany-processing feature.

EDI Payments using Oracle e-Commerce Gateway
The process to create EDI payments using Oracle e-Commerce Gateway has changed in Release 12. The EDI Outbound Program (APECEPYO) is obsolete. Setting the value for the Electronic Processing Channel in the Payment Process Profile setup page controls integration with Oracle e-Commerce Gateway. Release 11i format definitions are upgraded into payment process profiles with the electronic processing channel set appropriately. The format information on the process profile is populated with a seeded format. Actual formatting and transmission is performed by Oracle e-Commerce Gateway.

Certain fields were set in the Suppliers form for EDI payment information. In Release 12, these fields have been consolidated with standard payment details fields entered for a supplier, and the data values are migrated during the upgrade. The following table provides a mapping between the field names for the releases. 
Source 11i Entity
Release 12 Entity
Suppliers, EDI tab: Payment Method
Suppliers, Payment Details: Payment Method
Suppliers, EDI tab: Payment Format
Suppliers, Payment Details: Bank Instruction 1
Suppliers, EDI tab: Remittance Method
Suppliers, Payment Details: Delivery Channel
Suppliers, EDI tab: Remittance Instruction
Suppliers, Payment Details: Payment Text
Message 1
Suppliers, EDI tab: Transaction Handling
Suppliers, Payment Details: Bank Instruction 2

Example for customization R12 Payment Funds Disbursement XML file and adding/extend custom tags.

Standard PL/SQL package to use to extend or add additional tags to the XML file generated during a R12 Oracle Payments ‘Payment Process Request’ is IBY_FD_EXTRACT_EXT_PUB.

  • You cannot customize the package specification, but package body contains stubbed functions that you can customize.
  • We use this XML file as the data source for the XML Publisher cheque or wire or electronic file presentation layout.
We need to understand the structure of the XML file created by the Payments process request to use IBY_FD_EXTRACT_EXT_PUB package.
We can customize file in following levels.

Level1:
Outbound Payment Instruction: This is the top level of the XML File and there is one Outbound Payment Instruction per Payment process request.
Function: Get_Ins_Ext_Agg(p_payment_instruction_id IN NUMBER)
Query:

SELECT *
FROM iby_pay_instructions_all
WHERE payment_instruction_id = p_payment_instruction_id;

Level2:
Outbound Payment: This is the Payment Level i.e. an individual cheque or BACS payment amount to a supplier. There can be multiple Outbound Payments per Outbound Payment Instruction.
Function: Get_Pmt_Ext_Agg(p_payment_id IN NUMBER)
Query:

SELECT *
FROM iby_payments_all ipa
WHERE ipa.payment_id = p_payment_id;

Level3:
Document Payable: Details the documents like invoices being paid. There can be multiple Document Payable tags per Outbound Payment.
Function: Get_Doc_Ext_Agg(p_document_payable_id IN NUMBER)
Query:

SELECT *
FROM iby_docs_payable_all dp
WHERE dp.document_payable_id = P_document_payable_id;

Level4:
Document Payable Line: This level details the invoice line. There can be multiple Document Payable Line tags per Document Payable.
Function: Get_Docline_Ext_Agg(p_document_payable_id IN NUMBER, p_line_number IN NUMBER)

Level5:
Payment Process Profile: This level allows XML element to be introduced at document payable level and run once for each payment process request.
Function: Get_Ppr_Ext_Agg(p_payment_service_request_id IN NUMBER)
Query:

SELECT *
FROM iby_pay_service_requests WHERE payment_service_request_id = p_payment_service_request_id;

 

Example for customization R12 Payment Funds Disbursement XML file adding/extend custom tags.

 Here, i want to add alternate supplier name in the tag Extend/AltSupName. So modified the Get_Pmt_Ext_Agg function in IBY_FD_EXTRACT_EXT_PUB package as below.




FUNCTION Get_Pmt_Ext_Agg (p_payment_id IN NUMBER)
   RETURN XMLTYPE
IS
   v_supplier_name       ap_suppliers.vendor_name%TYPE;
   v_alt_supplier_name   XMLTYPE;
BEGIN
   BEGIN
      SELECT NVL (HP.ORGANIZATION_NAME_PHONETIC, HP.PARTY_NAME)
        INTO V_SUPPLIER_NAME
        FROM iby_payments_all IPA, HZ_PARTIES HP
       WHERE IPA.INV_PAYEE_PARTY_ID = HP.PARTY_ID
             AND ipa.payment_id = p_payment_id;
   EXCEPTION
      WHEN OTHERS
      THEN
         v_supplier_name := NULL;
   END;
   --build the XML string
   SELECT XMLCONCAT (
             XMLELEMENT ("Extend",
                         XMLELEMENT ("AltSupName", v_supplier_name)))
     INTO v_alt_supplier_name
     FROM DUAL;
   RETURN v_alt_supplier_name;
--RETURN NULL;
END Get_Pmt_Ext_Agg;

Give custom tag in document like as below:

Example for adding/extend custom tags to R12 Payment Funds Disbursement XML file, askhareesh blog for Oracle Apps  

Payables Open Interfaces


Payables Provides several open interfaces to import data into oracle
  • Payables Open Interface
  • Payables Expense Report Open Interface
  • Payables PCard Open Interface
  • Payables Credit Card Open Interface
  • Payables Matching Open Interface
  • Payables Supplier Open Interface
Payables Open Interface : Payables  open interface is an interface provided by oracle to import invoices into the system using various sources such as Auto invoice process, EDI ecommerece  gateway, invoices from credit card and procurement card transactions and invoices from external systems.  You can load standard invoices as well as credit memos using the Payables Invoice Open Interface. Once the invoices are loaded into the system, Payables Import program can be run to import the invoices into Oracle.
Payables Expense Report Interface: Accounts payables team can key in paper invoices  using the expense reports or employees can submit their expenses  using the invoice expense report.The payables Invoice Import Report can be submitted to validate the expense report data and  create expense reports in oracle
Payables PCard Open Interface : Some business can streamline the procure thopay process by using procurement cards. Employees can purchase the required items using credit cards and suppliers can send the relevant information to the payables interface. The payables invoice import program can be submitted to generate invoices  for these transactions..
Payables Credit Card Expenses Businesses use SQL loader scripts to load credit card expenditure related system into the interface tables which can later be imported into the system to create expense reports. Oracle has predefined the Loader Scripts for credit cards like : American Express, Visa etc.
Payables Matching Open Interface: Use SQL*Loader to load the required information into the purchasing interface tables. You will need to create a SQL*Loader control file to format the information you want to load. The file you write will vary greatly depending on the nature and format of the flat file you use. You match invoices to purchase order shipments during invoice entry.
Payables Supplier Interface : Businesses use this interface to enter the supplier and supplier site information in the system. Once the data is entered Payables Supplier import program can be run to create  suppliers in the system