Some interface tables used in EBS sort information some interface tables used in EBS sort information

From: http://www.cnblogs.com/songdavid/articles/2371077.html

 

Some interface tables used by EBS sort information AP interface tables: requests involved in ap_invoices_interfaceap_invoice_lines_interface: Import of open interfaces of the payable management system case: Import of shipping AP and fee export AP Po interface table: application: po_requisitions_interface_all request involved: Import Application procurement: po_headers_interfacepo_lines_interfacepo_distributions_interface request involved: Import standard purchase orders receive: transaction request involved: receive transaction processing processor case: freight guide procurement, MRP guide application, pop guide application GL interface table: gl_interface case: ad Fa interface table for I-guided journals and rebates-oriented journals: fa_mass_additions fa API: added fa_addition_pub.do_addition; modification: electronic asset inventory clearing transaction interface: mtl_transactions_interface1) it is generally used for various types of miscellaneous sending and receiving, cost update, and is not recommended for business-related transactions, such as so delivery. if you issue it yourself, the workflow will not go down. 2) after the import is successful, run cost manager to generate accounting entries. 3) this interface is also used for average cost update. If the item is not traded, the cost data will not enter the cst_item_costs fixed asset interface: fa_mass_additions1) note several triggers in the table fa_mass_additions. Other triggers are inserted automatically. The table is also deleted. 2) the depreciation method interface table cannot be provided, but is automatically inherited from the category. Therefore, update table is required after the import. 3) fa is not introduced through AP, there is no source lines information; if necessary, you can use the Insert table to implement 4) after the data is imported into the interface, submit the request set from Navigator: Mass additions/post mass additions, in this case, a report will display the import result. However, my test program can directly submit the request set. General ledger entry interface: gl_interface1) the simplest interface, not to mention the invoice payable interface: ap_invoices_interface/ap_invoice_lines_interface1) profile AP: Use invoice batch controls to define whether to use batch control 2) only credit/standard is supported; pay attention to positive and negative amounts, less than zero credit, more than zero standard3) prepayment/debit/expense report/mixed is not supported, credit or standard is used first, after entering the table, update the official table ap_invoices_all4) after the import, you can call the invoice validation automatic validate invoice receivables interface: ra_interface_lines_all/ra_interface_salescredits_all1). The relationship between several interface tables is different, Instead of ID association, it is defined by descriptive elastic domain Line Transaction flexfield. 2) the interface is used to specify the ID or name. You must specify the value based on the definition on transaction source) ra_interface_distributions_all can be left blank so that the system automatically generates the allocation row. 4) if there is no salesperson, you can provide a no sales person record with ID =-3 to the interface. This depends on whether the setting on Ar System Option miscellaneous requires the salesperson to receive the receipt interface: ar_interim_cash_receipts_all1) the AR receipt standard interface is lockbox and requires a pre-defined format. Oracle writes the interface data to ar_interim_cash_receip; we can skip the first step and directly Insert the data to ar_interim_cash_receipts_all, but we need to insert the table directly in batch. 2) view the data in the batch interface: the batch type of the data in ar_interim_cash_receipts_all is man) the currency of batch takes the base currency. The customer import interface for the receipt is ra_customers_interface_all/ra_customer_profiles_int_all/R. Principal) to export the customer, the principal must have a record 2) orig_system_party_ref is the same, customer_number is different, you can create multiple mermer3) ship to bill_to_orig_address_ref under a party available to the orig_system_address_ref, this will automatically associate 4) patch 3606744 and 3558213 are required; otherwise, statement and dunning site use cannot be imported. 5) Not all fields can be imported from the interface. Take hz_cust_site_uses_all as an example, after the import, you must update the following important fields: payment_term_id, order_type_id, warehouse_id, and territor. Y_id, primary_salesrep_id6) when updating shard primary_flag, note that both bill_to_flag and ship_to_flag of shard are P (primary) or Y sales order interface: shard/oe_actions_iface_all1) the whole close order can be queried through the interface table; close orders, Oracle is almost directly inserted into the table; others need to do a lot of verification 2) partial rows close the order, you can assign a line assign to a workflow that is only responsible for close (enter/fulfill/Close/end), so that after workflow back ground process is started, close3) Non-close order line numbers cannot be repeated, therefore, the interface table is empty. If you need to import the table The Te line table can be 4) the positive and negative numbers must be consistent with the line type, and the positive and negative pairs return. Otherwise, the interface reports an inventory item error. 5) several tables need to be updated for Order Number update: oe_order_headers_all/wsh_delivery_details/mtl_sales_orders6) The order line is split when the goods are received or the shipment is insufficient. When the split is made, the system copies almost all fields. If the unique field is encountered, it will fail. The problem I encountered was to record the line_id of the source system on the elastic domain and create a unique index for this elastic domain. As a result, the shipping part of the dropship order always reports the wrong order interface: po_headers_interface/po_lines_interface/po_distributions_interface1) quantity_billed can also be updated afterwards, so that the AP will not match again. 4) The approval record can be inserted directly into the table po_action_history5) Pay attention to the purchased valdiate org6) if the item does not have assign for ship_to_org, no data found error will be reported. Purchase receiving interface: rcv_shipment_headers/rcv_transactions_interface1) the receipt header is directly written into the table. The receipt line and receipt transaction are written through the interface. 2) Note that parent_transaction_id and receive need to be) if there is a problem with the Po interface, you can view the error information table po_interface_errors, which can solve most of the problems. 4) If you want to reproduce the original processing transaction, you can enter the interfaces receive, transfer, accept, reject, deliver, return to processing ing, return to vendor, and correct inventory item interfaces in batches in the following order: mtl_system_items_interface1). It is relatively easy to add items in master Org, 2) add items to other organizations (equivalent to update from the master assign). Note that the fields of Master org conctrol must keep the values of the master Organization (more, check the conctrol_level = 1) of mtl_item_attributes. 3) when adding an item to another organization, you must note that some fields must keep the value of the primary organization. Otherwise, the interface reports an error, they are buckets, dual_uom_control, buyer_id, buckets, purchasing_item_flag, internal_order_flag, and tags. If you want to give the item assign category, you can use category. The corresponding request is item category assignment open interface

Category: developer-Oracle Standard Interface

AP interface table: ap_invoices_interfaceap_invoice_lines_interface requests: Accounts Payable Management System open interface import case: Shipping AP, billing AP Po interface table: Application: po_requisitions_interface_all request: Import Application Purchase: request involved in po_headers_interfacepo_lines_interfacepo_distributions_interface: Import standard purchase orders receiving: accept request involved: receive transaction processing processor case: Import freight, MRP Import Application, pop Import Application GL interface table: case study of gl_interface: ADI-based book guide and fa-based book return-based book Guide Mouth table: fa_mass_additions fa API: added fa_addition_pub.do_addition modification: Inventory cleaning case: electronic assets inventory transaction interface: mtl_transactions_interface1) is generally used for various types of miscellaneous sending and receiving, cost update, it is generally not recommended for business-related transactions, such as so shipping. if you issue it yourself, workflow does not go down. 2) run cost manager to generate accounting entries after successful import. 3) this interface is also used to update the average cost. If the item is not traded, the cost data will not enter the cst_item_costs fixed asset interface: fa_mass_additions1) The fa_mass_additions table has several triggers; other tables will be inserted automatically, and the deletion will also be done 2) depreciation method The table cannot be given, but is automatically inherited from the category. Therefore, update Table 3 is required after the import. 3) the FA is not introduced through the AP and there is no source lines information, you can insert a table to implement 4) after the data is imported into the interface, submit the request set from Navigator: Mass additions/post mass additions, so that a report will display the import result. However, my test program can directly submit the request set. General ledger entry interface: gl_interface1) the simplest interface, not to mention the invoice payable interface: ap_invoices_interface/ap_invoice_lines_interface1) profile AP: Use invoice batch controls to define whether to use batch control 2) only credit/standard is supported; pay attention to positive and negative amounts, less than zero credit, more than zero standard3) prepayment/debit/expense report/mixed is not supported, credit or standard is used first, after entering the table, update the official table ap_invoices_all4) after the import, you can call the invoice validation automatic validate invoice receivables interface: ra_interface_lines_all/ra_interface_salescredits_all1). The relationship between several interface tables is different, Instead of ID association, it is defined by descriptive elastic domain Line Transaction flexfield. 2) the interface is used to specify the ID or name. You must specify the value based on the definition on transaction source) ra_interface_distributions_all can be left blank so that the system automatically generates the allocation row. 4) if there is no salesperson, you can provide a no sales person record with ID =-3 to the interface. This depends on whether the setting on Ar System Option miscellaneous requires the salesperson to receive the receipt interface: ar_interim_cash_receipts_all1) the AR receipt standard interface is lockbox and requires a pre-defined format. Oracle writes the interface data to ar_interim_cash_receip; we can skip the first step and directly Insert the data to ar_interim_cash_receipts_all, but we need to insert the table directly in batch. 2) view the data in the batch interface: the batch type of the data in ar_interim_cash_receipts_all is man) the currency of batch takes the base currency. The customer import interface for the receipt is ra_customers_interface_all/ra_customer_profiles_int_all/R. Principal) to export the customer, the principal must have a record 2) orig_system_party_ref is the same, customer_number is different, you can create multiple mermer3) ship to bill_to_orig_address_ref under a party available to the orig_system_address_ref, this will automatically associate 4) patch 3606744 and 3558213 are required; otherwise, statement and dunning site use cannot be imported. 5) Not all fields can be imported from the interface. Take hz_cust_site_uses_all as an example, after the import, you must update the following important fields: payment_term_id, order_type_id, warehouse_id, and territor. Y_id, primary_salesrep_id6) when updating shard primary_flag, note that both bill_to_flag and ship_to_flag of shard are P (primary) or Y sales order interface: shard/oe_actions_iface_all1) the whole close order can be queried through the interface table; close orders, Oracle is almost directly inserted into the table; others need to do a lot of verification 2) partial rows close the order, you can assign a line assign to a workflow that is only responsible for close (enter/fulfill/Close/end), so that after workflow back ground process is started, close3) Non-close order line numbers cannot be repeated, therefore, the interface table is empty. If you need to import the table The Te line table can be 4) the positive and negative numbers must be consistent with the line type, and the positive and negative pairs return. Otherwise, the interface reports an inventory item error. 5) several tables need to be updated for Order Number update: oe_order_headers_all/wsh_delivery_details/mtl_sales_orders6) The order line is split when the goods are received or the shipment is insufficient. When the split is made, the system copies almost all fields. If the unique field is encountered, it will fail. The problem I encountered was to record the line_id of the source system on the elastic domain and create a unique index for this elastic domain. As a result, the shipping part of the dropship order always reports the wrong order interface: po_headers_interface/po_lines_interface/po_distributions_interface1) quantity_billed can also be updated afterwards, so that the AP will not match again. 4) The approval record can be inserted directly into the table po_action_history5) Pay attention to the purchased valdiate org6) if the item does not have assign for ship_to_org, no data found error will be reported. Purchase receiving interface: rcv_shipment_headers/rcv_transactions_interface1) the receipt header is directly written into the table. The receipt line and receipt transaction are written through the interface. 2) Note that parent_transaction_id and receive need to be) if there is a problem with the Po interface, you can view the error information table po_interface_errors, which can solve most of the problems. 4) If you want to reproduce the original processing transaction, you can enter the interfaces receive, transfer, accept, reject, deliver, return to processing ing, return to vendor, and correct inventory item interfaces in batches in the following order: mtl_system_items_interface1). It is relatively easy to add items in master Org, 2) add items to other organizations (equivalent to update from the master assign). Note that the fields of Master org conctrol must keep the values of the master Organization (more, check the conctrol_level = 1) of mtl_item_attributes. 3) when adding an item to another organization, you must note that some fields must keep the value of the primary organization. Otherwise, the interface reports an error, they are buckets, dual_uom_control, buyer_id, buckets, purchasing_item_flag, internal_order_flag, and tags. If you want to give the item assign category, you can use category. The corresponding request is item category assignment open interface