Oracle Apps Open Interfaces

Oracle Apps Open Interfaces

I N T E R The concept of Open Interface Objectives .
To Understand .
F
A C E
The tasks involved in Open Interfaces
Customer Interface AutoInvoice AutoLock Box

I N T E R Purpose
To Integrate Oracle Financial with External / Feeder Systems
F
A C E
To Import Historical Data from Previous systems

I N T E R
Oracle Applications
Interface Tables Oracle Applications Import Program Oracle Applications System Feeder System Data Feeder Program
Overview
F
A C E

I N T E R
- SQL*Loader
Feeder program types
- PL/SQL
- PRO*C - PRO*COBOL
F
A C E

I N T E R - Easy Import - Data Validation - Review of Import - Error Identification Features of Import Programs
F
A C E
- Error Correction

I N T E R Commonly Used Interfaces
- Customer Interface - Invoices for Receivables Interface - LockBox/Receipts Interface - Invoices for Payables Interface - Inventory Item Interface - Inventory Transaction Interface - Journal Entries - Mass Editions - PO Requisitions - Sales Orders
F
A C E

I N T E R
RA_CUSTOMER_INTERFACE
Customer Interface
Over View
Feeder System Use an import program to format & load data into Customer Interface tables
RA_CUSTOMER_PROFILES_INTERFACE
F
A C E
RA_CONTACT_ PHONES_INTERFACE
RA_CUSTOMERS_ BANKS_INTERFACE
RA_CUST_PAY_ METHOD_INTERFACE
Submit Customer Interface to validate data & transfer it to Customer tables (Executable - RACUST) Customer Tables

I N T E R Customer Interface
Validations QuickCodes - Countries - Site use codes - Credit ratings - Customer classes . Payment Methods Payment Terms Customer profile classes Bank Information ..
F
A C E

I N T E R
Orig_System_Address_Ref (If you are importing an address)
Customer Interface
Required Data
Column Name ( Ra_Customers_Interface ) Validation
Must not exist in RA_CUSTOMERS for insert record Must exists in RA_CUSTOMERS for update record (Desc:- Unique customer identifier for feeder system Must not exist in RA_ADDRESSES for insert record. Must exists in RA_ADDRESSES for update record. (Desc:- Unique address identifier for feeder system)
Orig_System_Customer_Ref
F
A C E
Site_Use_Code Must exists in AR_LOOKUPS.Lookup_Code (If you are importing a business purpose) Customer_Number Must be NULL if automatic customer numbering is used It should be unique within RA_CUSTOMERS Customer_Name Same customer reference cannot have different name Insert_Update_Flag Customer_Status Interface_Status I for insert & U for update A for active & I for inactive Should be NULL (Desc:- Error messages that apply to this interface record.) Y or N to indicate whether this is the primary business purpose. Only for new records & you have value in Orig_System_Address_Ref
Primary_Site_Use_Flag (If you are importing an address)

Required Data ( Ra_Customers_Profiles_Interface )
Column Name
Orig_System_ Customer_Ref
Validation
Must not exist in RA_CUSTOMERS for insert record. Must exists in RA_CUSTOMERS for update record. Must not exist in RA_ADDRESSES for insert record. Must exists in RA_ADDRESSES for update record.
F
A C E
Orig_System_Address_Ref (If you are importing a profile for customer address) Customer_Profile_Class_Name
Must exists in AR_CUSTOMER_PROFILE_CLASSES with Status=A I for insert & U for update Should be NULL Y for yes & N for no Must exists in AR_LOOKUPS.Lookup_Code
Insert_Update_Flag Interface_Status Credit_Hold Credit_Rating

I N T E R
Orig_System_Address_Ref Orig_System_Contact_Ref
Customer Interface
Required Data
Column Name
( Ra_Contact_Phones_Interface ) Validation
Must not exist in RA_CUSTOMERS for insert record. Must exists in RA_CUSTOMER for update record. Required if telephone no for an address. Required if telephone no for contact To uniquely identify this telephone in your original system. Must exists in AR_LOOKUP.Lookup_Code Required if telephone no for contact I for insert & U for update Should be NULL
F
A C E
Orig_System_Telephone_Ref Telephone_Type Contact_Last_Name Insert_Update_Flag Interface_Status

I N T E R
Primary_Flag
Customer Interface
Required Data
( Ra_Customer_Banks_Interface )
Column Name
Validation
Must not exist in RA_CUSTOMERS for insert record. Must exists in RA_CUSTOMER for update record. Y or N to indicate whether this is primary bank account for customer or Bill-To address To get bank account effective Should exists in AP_BANK_ACCOUNTS. Bank_Name Should be NULL
F
A C E
Start_Date Bank_Account_Name
Interface_Status

I N T E R
Column Name
Customer Interface
Required Data
( Ra_Cust_Pay_Method_Interface )
Validation
Must not exist in RA_CUSTOMERS for insert record. Must exists in RA_CUSTOMER for update record. Y or N Effective Date Must exists in AR_RECEIPTS_METHOD
F
A C E
Primary_Flag. Start_Date Payment_Method_Name
Interface_Status
Should be NULL

I N T E R
RA_CUSTOMERS RA_ADDRESSES RA_CONTACTS RA_PHONES RA_CUST_RECEIPT_METHODS AR_CUSTOMER_PROFILES
Customer Interface
System Tables updated by Customer Interface
F
A C E

TIPS
Customers with multiple addresses (Say two addresses) - Enter two records in RA_CUSTOMER_INTEFACE - With identical Orig_System_Customer_Ref - But different Orig_System_Address_Ref Customers with multiple contacts (Say two contacts) - Enter two records in RA_CONTACT_PHONES_INTERFACE - With identical Orig_System_Customer_Ref - But different Orig_System_Contact_Ref
F
A C E

TIPS Customers with multiple telephone numbers (Say two telephones) - Enter two records in RA_CONTACT_PHONES_INTERFACE - With identical Orig_System_Customer_Ref - But different Orig_System_Contact_Ref Addresses with multiple business purposes (Say two purposes) - Enter two records in RA_CUSTOMERS_INTERFACE - With identical Orig_System_Customer_Ref - With identical Orig_System_Address_Ref - But different Site_Use_Code
F
A C E

I N T E R Invoice Interface - Receivable
Using AutoInvoice (Executable - RAXMTR) Invoices Credit memos Debit memos On-Account credits
F
A C E

I N T E R
RA_INTERFACE_LINES
Invoice Interface - Receivable

Over View
Feeder System Use an import program to load data into Interface tables
RA_INTERFACE_DISTRIBUTIONS
F
A C E
RA_INTERFACE_ SALESCREDITS
Submit the AutoInvoice Interface Program
Oracle Receivable Tables
RA_Interface_Errors

Validations
- Accts code combination id - Payment term - Transaction type - Line Code - Batch source
F
A C E
- Salesperson - Unit of measure

Steps Required
- Running AutoInvoice program - Reviewing the AutoInvoice execution & validation reports - Correcting errors - Rerunning AutoInvoice program
F
A C E

System Tables updated with AutoInvoice Program
- RA_BATCHES
- RA_CUSTOMER_TRX
- RA_CUSTOMER_TRX_LINES - RA_CUST_TRX_LINE_GL_DIST - RA_CUST_TRX_LINE_SALESREPS - AR_PAYMENT_SCHEDULES
F
A C E
- AR_RECEIVABLE_APPLICATIONS

I N T E R Receipts
Using Autolockbox
- Submit Import Reads & formats the data from flat file into autolockbox tables using SQL*Loader script.
F
A C E
- Submit Validation Validates & transfers data into QuickCash tables.

- Submit Post Quick Cash Applies the receipts & updates customers balances.
Note : These steps can be submitted individually or at the same time from the Submit Lockbox processing window.

I N T
Import program Lockbox processing report
Receipts
Over view
Bank file/ Data file
E R
Ar_Payments Interface table Auto lockbox validation Lockbox processing report
F
A C E
Ar_Interim_Cash_Receipts Ar_Interim_Lines Post batch Post batch execution report
AR Standard tables

I N T E R Receipts
Identifying Customers for a receipt
- Customer Number
- MICR Number -The customer number is not included in the transmission format -The MICR number is passed - AutoAssociate -To determine the customer using matching number -Matching numbers like : Transaction Number Sales order number
F
A C E

I N T E R Receipts
To use AutoAssociate
- Check the AutoAssociate check box while defining the LockBox
- Matching numbers must be unique within the transmission - All invoices to which any single receipt will be applied must belong to the same customer Note : If Customer number or MICR number is not included in the transmission and auto associate is set to No, LockBox imports the receipt as unidentified. You can do the application manually.
F
A C E

I N T E R Receipts
System Tables to be updated after QuickCash post
- AR_CASH_RECEIPTS - AR_RECEIVABLES_APPLICATIONS - AR_CASH_RECEIPT_HISTORY
F
A C E

I N T E R
THANKS
F
A C E

Oracle Apps Open Interfaces

Uploaded by

Copyright:

Available Formats

Oracle Apps Open Interfaces

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Apps Open Interfaces

Uploaded by

Copyright:

Available Formats

Oracle Apps Open Interfaces