Otherwise we rollback to the top-level 'virtual' savepoint currently in existence, which is my offending unnamed block.That is, a handled error is handled and so can be dealt with without rolling back all the way to the top. Commits define the end of a transaction (and start of a new one) - rollbacks only define the end of a transaction if they rollback to the last commit, rather than savepoint (whether explicit or implicit).Details like pre-requisites required, interface tables, interface program, base tables, validations that need to be performed after inserting the details into the interface tables and required columns that need to be populated in the interface table are discussed for each interface.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. Ordered_date should exist (header level) Delivery_lead_time should exist (line level) Earliest_acceptable_date should exist.Orders can be categorized based on their status: 1. Pre-requisites: Creating an Organization Code Combinations Templates Defining Item Status Codes Defining Item Types Interface tables: MTL_SYSTEM_ITEMS_INTERFACE MTL_ITEM_REVISIONS_INTERFACE (If importing revisions) MTL_ITEM_CATEGORIES_INTERFACE (If importing categories) MTL_INTERFACE_ERRORS (View errors after import) Concurrent Program: Item import In the item import parameters form, for the parameter ‘set process id’, specify the ‘set process id’ value given in the mtl_item_categories_interface table.The parameter ‘Create or Update’ can have any value.If does not exist, create new customer by calling create_new_cust_info API. Freight_terms should exist Notes: During import of orders, shipping tables are not populated. GET_ORDER and PROCESS_ORDER can also be used to import orders.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. 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 The Item Interface lets you import items into Oracle Inventory.
Also, PL/SQL does not roll back database work done by the subprogram.
It is possible to invoke these tools from your Java applications, but this is not a straightforward approach and not an efficient solution.
This is especially true if you wish to compress and decompress data on the fly (before transferring it to a remote machine for example).
Many sources of information contain redundant data or data that adds little to the stored information.
This results in tremendous amounts of data being transferred between client and server applications or computers in general.