interface tables & ap

7/30/2019 Interface Tables & AP

1/7

Wednesday, September 10, 2008

All modules Interface Tables

GL INTERFACE TABLES

TNAME TABTYPE------------------------------ ------- ----------------------

GL_BUDGET_INTERFACE TABLE

GL_DAILY_RATES_INTERFACE TABLE

GL_IEA_INTERFACE TABLE

GL_INTERFACE TABLE

GL_INTERFACE_CONTROL TABLE

GL_INTERFACE_HISTORY TABLE

AP INTERFACE TABLES

TNAME TABTYPE------------------------------ ------- ------------------------

AP_INTERFACE_CONTROLS TABLE

AP_INTERFACE_REJECTIONS TABLE

AP_INVOICES_INTERFACE TABLE

AP_INVOICE_LINES_INTERFACE TABLE

AR INTERFACE TABLES

TNAME TABTYPE

------------------------------ --------------------------------------AR_PAYMENTS_INTERFACE_ALL TABLE

AR_TAX_INTERFACE TABLE

HZ_DQM_SYNC_INTERFACE TABLE

HZ_PARTY_INTERFACE TABLE

HZ_PARTY_INTERFACE_ERRORS TABLE

RA_CUSTOMERS_INTERFACE_ALL TABLE

RA_INTERFACE_DISTRIBUTIONS_ALL TABLE

RA_INTERFACE_ERRORS_ALL TABLE

RA_INTERFACE_LINES_ALL TABLE

RA_INTERFACE_SALESCREDITS_ALL TABLE

FA INTERFACE TABLES

TNAME TABTYPE

------------------------------ ------- ----------------------

FA_BUDGET_INTERFACE TABLE

FA_INV_INTERFACE TABLE
http://freshers-oracleapplications.blogspot.com/2008/09/all-modules-interface-tables.htmlhttp://freshers-oracleapplications.blogspot.com/2008/09/all-modules-interface-tables.html


2/7

FA_PRODUCTION_INTERFACE TABLE

FA_TAX_INTERFACE TABLE

INVENTORY INTERFACE TABLES

TNAME TABTYPE------------------------------ ------- ------------------------------------

MTL_CC_ENTRIES_INTERFACE TABLE

MTL_CC_INTERFACE_ERRORS TABLE

MTL_CI_INTERFACE TABLE

MTL_CI_XREFS_INTERFACE TABLE

MTL_COPY_ORG_INTERFACE TABLE

MTL_CROSS_REFERENCES_INTERFACE TABLE

MTL_DEMAND_INTERFACE TABLE

MTL_DESC_ELEM_VAL_INTERFACE TABLE

MTL_EAM_ASSET_NUM_INTERFACE TABLE

MTL_EAM_ATTR_VAL_INTERFACE TABLEMTL_INTERFACE_ERRORS TABLE

TNAME TABTYPE

------------------------------ ------- --------------------------------------

MTL_INTERFACE_PROC_CONTROLS TABLE

MTL_ITEM_CATEGORIES_INTERFACE TABLE

MTL_ITEM_CHILD_INFO_INTERFACE TABLE

MTL_ITEM_REVISIONS_INTERFACE TABLE

MTL_ITEM_SUB_INVS_INTERFACE TABLE

MTL_OBJECT_GENEALOGY_INTERFACE TABLE

MTL_RELATED_ITEMS_INTERFACE TABLEMTL_RESERVATIONS_INTERFACE TABLE

MTL_RTG_ITEM_REVS_INTERFACE TABLE

MTL_SECONDARY_LOCS_INTERFACE TABLE

MTL_SERIAL_NUMBERS_INTERFACE TABLE

TNAME TABTYPE

------------------------------ ------- ------------------------------------

MTL_SO_RMA_INTERFACE TABLE

MTL_SYSTEM_ITEMS_INTERFACE TABLE

MTL_TRANSACTIONS_INTERFACE TABLE

MTL_TRANSACTION_LOTS_INTERFACE TABLEMTL_TXN_COST_DET_INTERFACE TABLE

PO INTERFACE TABLES

TNAME TABTYPE

------------------------------ ------- -------------------------

PO_DISTRIBUTIONS_INTERFACE TABLE


3/7

PO_HEADERS_INTERFACE TABLE

PO_INTERFACE_ERRORS TABLE

PO_LINES_INTERFACE TABLE

PO_REQUISITIONS_INTERFACE_ALL TABLE

PO_REQ_DIST_INTERFACE_ALL TABLE

PO_RESCHEDULE_INTERFACE TABLERCV_HEADERS_INTERFACE TABLE

RCV_LOTS_INTERFACE TABLE

RCV_SERIALS_INTERFACE TABLE

RCV_TRANSACTIONS_INTERFACE TABLE

BOM INTERFACE TABLES

TNAME TABTYPE

------------------------------ ------- ----------------------------------

BOM_BILL_OF_MTLS_INTERFACE TABLE

BOM_INTERFACE_DELETE_GROUPS TABLEBOM_INVENTORY_COMPS_INTERFACE TABLE

BOM_OP_RESOURCES_INTERFACE TABLE

BOM_OP_ROUTINGS_INTERFACE TABLE

BOM_OP_SEQUENCES_INTERFACE TABLE

BOM_REF_DESGS_INTERFACE TABLE

BOM_SUB_COMPS_INTERFACE TABLE

CST_COMP_SNAP_INTERFACE TABLE

CST_INTERFACE_ERRORS TABLE

CST_ITEM_COSTS_INTERFACE TABLE

CST_ITEM_CST_DTLS_INTERFACE TABLE

CST_PC_COST_DET_INTERFACE TABLECST_PC_ITEM_COST_INTERFACE TABLE

WIP INTERFACE TABLES

TNAME TABTYPE

------------------------------ ------- --------------------------

WIP_COST_TXN_INTERFACE TABLE

WIP_INTERFACE_ERRORS TABLE

WIP_JOB_DTLS_INTERFACE TABLE

WIP_JOB_SCHEDULE_INTERFACE TABLE

WIP_MOVE_TXN_INTERFACE TABLEWIP_SCHEDULING_INTERFACE TABLE

WIP_TXN_INTERFACE_ERRORS TABLE

ORDER MANAGEMENT INTERFACE TABLES

TNAME TABTYPE

------------------------------ ------- -----------------------------------


4/7

SO_CONFIGURATIONS_INTERFACE TABLE

SO_HEADERS_INTERFACE_ALL TABLE

SO_HEADER_ATTRIBUTES_INTERFACE TABLE

SO_LINES_INTERFACE_ALL TABLE

SO_LINE_ATTRIBUTES_INTERFACE TABLE

SO_LINE_DETAILS_INTERFACE TABLESO_PRICE_ADJUSTMENTS_INTERFACE TABLE

SO_SALES_CREDITS_INTERFACE TABLE

SO_SERVICE_DETAILS_INTERFACE TABLE

WSH_DELIVERIES_INTERFACE TABLE

WSH_FREIGHT_CHARGES_INTERFACE TABLE

WSH_PACKED_CONTAINER_INTERFACE TABLEPosted by Sunil Dutt at8:55 AM

Oracle API Availability - Oracle Payables(AP)

Posted on June 25th, 2007 by Sanjit Anand| Print This Post| Email This Post

This is in continuation to APIs availability,Here are the APIsavailability in AP.

Credit Card Transaction Processing

Manual Credit Card Entry: A form is available for entry through the Oracle

Payables application.

Credit Card Transaction Interface Table: This process loads transaction data

from the credit card issuer (American Express, Diner's Club, MasterCard andVisa) into Oracles AP module. Oracle Payable then uses this data to confirm

transactions with employees. Once the transactions have been approved the credit

card transaction lines are imported into Payables Open Interface using the CreditCard Invoice Interface Summary program. The credit card transactions are then

available for final import to Oracle Payables where the transactions become

invoices.

Creating Invoices

In Oracle Payables four methods are available for entering an invoice into the system.

Manual Invoice Entry: Two methods for manual invoice entry exist. Using

Oracle Payables system Invoice Workbench which includes the Invoice Batches
http://freshers-oracleapplications.blogspot.com/2008/09/all-modules-interface-tables.htmlhttp://freshers-oracleapplications.blogspot.com/2008/09/all-modules-interface-tables.htmlhttp://www.blogger.com/email-post.g?blogID=498943946528406089&postID=4238731512938821795http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/print/http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/print/http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/print/http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/emailpopup/http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/emailpopup/http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/emailpopup/http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/emailpopup/http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/print/http://www.blogger.com/email-post.g?blogID=498943946528406089&postID=4238731512938821795http://freshers-oracleapplications.blogspot.com/2008/09/all-modules-interface-tables.htmlhttp://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/print/http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/emailpopup/


5/7

window and Distribution window users can enter complex invoices, and invoices

requiring online validation. In addition this functionality is useful in processing

invoices that require special attention such as immediate payment.

The second method of manual invoice entry, Invoice Gateway, is used when

entering high volumes of invoices. Generally these invoices do not require online

validation or defaulting of accounting information. After entering invoices usingthe gateway, the invoice import must be run, at that time validation and defaulting

is performed. This method of entry can be used in lieu of invoice interfaces.

Although, using the gateway can accomplish similar results to that found with aninterface process, manual entry is no substitute.

Automatic Invoice Creation: Oracle Payables provides functionality to produce

periodically recurring invoices. This functionality may be used to substitute

manual invoice entry or the payables open interface. In the case of recurringinvoices that would normally come from an external system choosing to setup a

recurring invoice formula may be an alternative.

Using Payables Open Interface: Choose this method for processing large

volumes of invoices that originate in external system. Additionally, this process isuseful in handling employee expense reports generated through self-service

applications, expense reports entered by the Payables Department, invoices for

employee credit card expenses, Oracle Projects billing and time and expenses, andEDI invoices transferred from the Oracle EDI gateway.

Purchase Order Matching

Oracle Payables can be implemented without Oracle Purchasing, to allow

this several purchasing tables are installed initially which must be

populated using custom interfaces. Only two-way matching is availablewhen data is loaded using the interface method. Two-way approvalverifies that purchase order and invoice information match within your

tolerances as follows: Quantity billed on the purchase order shipment is

less than or equal to Quantity ordered on the purchase order shipment.Invoice price on the purchase order shipment is less than or equal to

Purchase order price on the purchase order shipment.

Receipts can only be matched in an install that also includes OraclePurchasing.

The only method for interfacing data into the purchasing tables described

in this section is through a customized interface from an external source.

Note: Interfacing this information is not supported by Oracle.

Loading PO_HEADERS: Each record in this table represents a

purchase order, which is an order for goods or services from a single supplier.

Each purchase order may have multiple lines (PO_LINES). In addition, eachblanket purchase order may have multiple blanket releases (PO_RELEASES),

which release an amount from the blanket.


6/7

Loading PO_LINES: Each record in this table represents a purchase order line,

which identifies the items and unit price for the goods ordered on a purchase

order. Each purchase order line may have multiple shipments(PO_LINE_LOCATIONS).

Loading PO_LINE_LOCATIONS: Each record in this table represents a

purchase order line, which identifies the items and unit price for the goodsordered on a purchase order. Each purchase order line may have multipleshipments (PO_LINE_LOCATIONS).

Loading PO_DISTRIBUTIONS/PO_DISTRIBUTIONS_AP_V: Each record in

this table/view represents a purchase order distribution, which identifies theaccount charged for the items on a purchase order shipment.

Loading PO_RELEASES: Each record in this table represents a blanket release

for a purchase order. A blanket release may create multiple shipments.

Loading AP_INVOICES/AP_INVOICE_DISTRIBUTIONS: Each purchase

order shipment can be matched to multiple invoices(AP_INVOICES), and a

single invoice may be matched to multiple purchase order shipments. When you

match an invoice to a purchase order shipment, Payables creates an invoicedistribution AP_INVOICE_DISTRIBUTIONS) from each purchase order

distribution on the shipment. When you match an invoice to a single purchase

order distribution, Payables creates a single invoice distribution from the purchaseorder distribution.

Vendor Interface

Existing and new vendors must be loaded into the Oracle Payables application to supportpayables activities. Two methods may be used to enter vendors into Oracle Applications,

manual entry and direct loading using a customized loader program.

Manual Vendor Loading: Use the Enter Vendor window. Using this

functionality vendor header information as well as vendor site information can be

entered.

Vendor Interface: When interfacing vendors into Oracle Applications two tables

must be loaded the PO_VENDORS and PO_VENDOR_SITES_ALL. The vendortable contains all header information and the site table contains information about

each the vendor locations such as "ship to" and "bill to". Using this method makes

sense when the volume of new vendors is large. Note: Interfacing this information

is not supported by Oracle.

Those who are in 11.5.10 they will find yet another method ie by interface .You have to Load data into the staging tables first ie.AP_SUPPLIERS_INT -

Supplier InformationAP_SUPPLIER_SITES_INT - Supplier Sites Information

,AP_SUP_SITE_CONTACT_INT - supplier Contact details This uses Vendor ID,

Vendor Site Code to relate the contacts to specific vendor. Once data get loadedthree interface program should be kicked out which is as

o Supplier Open Interface Import.


7/7

o Supplier Sites Open Interface Import

o Supplier Site Contacts Open Interface Import

interface tables & ap

Documents