Shulou(Shulou.com)05/31 Report--

This article mainly explains the "Analysis of EBS Common Interface Table". The content of the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "analyze EBS Common Interface Table".

AP interface table:

AP_INVOICES_INTERFACE

AP_INVOICE_LINES_INTERFACE

Requests involved:

Open interface import of payables management system

Cases involved: freight guide AP, cost guide AP

PO interface table:

Application:

PO_REQUISITIONS_INTERFACE_ALL

The request is involved:

Import request

Purchase:

Po_headers_interface

Po_lines_interface

Po_distributions_interface

Requests involved:

Import Standard Purchase Orders

Receive:

Rcv_headers_interface

Rcv_transactions_interface

Mtl_transaction_lots_interface

The request is involved:

Receive transaction processor

Cases involved: freight guide procurement, MRP guidance application, pop guidance application

GL interface table:

Gl_interface

Cases involved: ADI-guided journal, rebate-guided journal

FA interface table:

Fa_mass_additions

FA API:

Add fa_addition_pub.do_addition

Modify: fa_adjustment_pub.do_adjustment

Fa_asset_desc_pub.update_desc

Case involved: electronic assets liquidation

Inventory transaction API: mtl_transactions_interface

1) it is generally used for all kinds of miscellaneous sending and receiving and Cost Update. It is generally not recommended for business-related matters, such as SO delivery. If you send it yourself, it will cause Workflow not to go down.

2) run Cost Manager to generate accounting entries after successful import

3) the average cost update also passes through this API; if there is no transaction in the Item, the cost data will not enter the cst_item_costs

Fixed assets interface: fa_mass_additions

1) fa_mass_additions this table has several Trigger to pay attention to; it automatically inserts other tables, even when deleting them.

2) the depreciation method interface table cannot be given, but is automatically inherited from Category, so the Update table is required after import.

3) FA is not introduced through AP, and there is no Source Lines information; if necessary, it can be implemented by inserting tables.

4) after the data enters the interface, the request set is submitted from Navigator:Mass Additions/Post Mass Additions, so that a report will show the import results. However, my test program can directly submit the request set.

General ledger entry API: gl_interface

1) the simplest interface, forget it

Invoice payable API: ap_invoices_interface/ap_invoice_lines_interface

1) Profile AP: Use Invoice Batch Controls defines whether to use batch control

2) only CREDIT/STANDARD; is supported. Note that the amount is less than petty CREDIT and greater than petty STANDARD.

3) PREPAYMENT/DEBIT/EXPENSE REPORT/MIXED does not support it. Use CREDIT or STANDARD first, and then Update formal table ap_invoices_all after entering.

4) after import, you can call to request Invoice Validation automatic Validate invoice

Invoice Receivable API: ra_interface_lines_all/ra_interface_salescredits_all

1) the relationship between several interface tables is different from other interfaces, not through ID association, but by descriptive elastic domain Line Transaction Flexfield.

2) the interface to ID or Name should be given according to the definition on Transaction Source, not casually.

3) ra_interface_distributions_all can not be inserted in this table, so that the system can automatically generate allocation rows

4) if there is no salesperson, you can provide a No Sales Person record of ID=-3 to the interface. It depends on whether the settings on AR System Option Miscellaneous require salespeople.

Receipt Receivable Interface: ar_interim_cash_receipts_all

1) AR Receipt standard interface is Lockbox, which needs to be pre-defined Format;Oracle to write interface data to ar_interim_cash_receipts_all; according to Format definition. We can skip the first step and insert the data directly into ar_interim_cash_receipts_all, but Batch requires us to insert the table directly.

2) View the data in the Batch interface: the Batch Type of ar_interim_cash_receipts_all is Mannual Quick.

3) the Currency of Batch can take the standard currency, and the receipt should be in the required currency.

Customer Import Interface: ra_customers_interface_all/ra_customer_profiles_int_all/ra_contact_phones_int_all

1) A record is required to guide Customer,ra_customer_profiles_int_all

2) if the orig_system_party_ref is the same, but the Customer_Number is different, you can build multiple Customer under one Party.

3) the bill_to_orig_address_ref of ship to can be used as orig_system_address_ref of bill to, so it can be associated automatically.

4) you need to type Patch 3606744 and 3558213, otherwise Site Use of Statement and Dunning types cannot be imported.

5) not all fields can be entered from Interface; take HZ_Cust_Site_Uses_all as an example, after import, you need to directly Update the following more important fields: payment_term_id, order_type_id, warehouse_id, territory_id, primary_salesrep_id

6) when updating the Primary_flag of HZ_Cust_Site_Uses_all, be sure to update the bill_to_flag and ship_to_flag of hz_cust_acct_sites_all as P (Primary) or Y at the same time

Sales order API: oe_headers_iface_all/oe_lines_iface_all/oe_actions_iface_all

1) the whole Close order can go through the interface table; for the Close order, Oracle inserts the table almost directly; others need to do a lot of verification.

2) for the order of part of the line Close, you can give the line Assign a workflow that is only responsible for Close (Enter/Fulfill/Close/End), so that when Workflow Back Ground Process is up, it will Close.

3) the non-Close order line number cannot be repeated, so we leave the interface table empty; if necessary, the Update Line table can be imported.

4) the positive or negative quantity should be consistent with the type of Line Type, positive for Order and negative for Return, otherwise the API reports an Inventory Item error.

5) several tables need to be updated to update the order number: oe_order_headers_all/wsh_delivery_details/mtl_sales_orders

6) in the case of insufficient delivery or receipt of goods, the order line will be disassembled, and the system will copy almost all the fields if it encounters the field of Unique. The problem I encountered was that the line_id of the source system was recorded in the elastic domain, and the Unique index was built for this elastic domain, which led to the wrong receipt of the order part of the Dropship.

Purchase order API: po_headers_interface/po_lines_interface/po_distributions_interface

1) if there is a problem with the PO interface, you can see the error message table po_interface_errors, which can solve most of the problems.

2) after the base currency is imported, the Rate Date on the head is empty and the Update table is required.

3) quantity_billed can also be updated afterwards, so that AP will not Match again.

4) approval records can be directly inserted into table po_action_history

5) pay attention to the Valdiate ORG purchased

6) if Item does not have Assign for Ship_to_org, a No data found error will be reported.

Purchase receiving interface: rcv_shipment_headers/rcv_transactions_interface

1) the receipt header writes the table directly; the receipt line and the receiving transaction go through the interface

2) Note that parent_transaction_id,Receive needs to be emptied

3) if there is a problem with the PO interface, you can see the error message table po_interface_errors, which can solve most of the problems.

4) if you want to reproduce the original Receiving Transaction, enter the interfaces RECEIVE, TRANSFER, ACCEPT, REJECT, DELIVER, RETURN TO RECEIVING, RETURN TO VENDOR, CORRECT in batches in the following order

Inventory item API: mtl_system_items_interface

1) it is relatively simple to add Item to Master Org. You can give enough fields to it.

2) add Item to other organizations (equivalent to Update after Master Assign). Note that the field of Master Org Conctrol needs to maintain the value of the main organization (for more, see mtl_item_attributes 's Conctrol_level = 1)

3) adding Item in other organizations should also pay attention to some fields that need to maintain the value of the main organization, otherwise the interface will report an error. They are create_supply_flag, dual_uom_control, buyer_id, allowed_units_lookup_code, purchasing_item_flag, internal_order_flag, inventory_item_flag.

4) if you want to give it to Item Assign Category, you can use mtl_item_categories_interface. The corresponding request is Item Category Assignment Open Interface.

Several interface tables in EBS

Select * from RCV_TRANSACTIONS_INTERFACE-- pending receive transaction

Select * from MTL_TRANSACTIONS_INTERFACE-- pending material transaction

Select * from WIP_MOVE_TXN_INTERFACE-- pending mobile transaction

Select * from MTL_MATERIAL_TRANSACTIONS_TEMP-- unhandled material transactions

Select * from MTL_MATERIAL_TRANSACTIONS-- uncosted material transaction processing

Select * from WIP_COST_TXN_INTERFACE-- pending WIP costing transaction

Thank you for your reading, the above is the content of "Analysis of EBS Common Interface Table". After the study of this article, I believe you have a deeper understanding of the problem of analyzing EBS common interface table, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.