How to create a sale order using open interfaces R12


Create header records in sale orders open interface tables

  • Order sources can be through Telesales, Online channel, iStores, Siebel CRM or any custom sources (Check OE_ORDER_SOURCES table)
  • original system document reference should be used to create sale order
  • Org id indicates operating unit for which sale order to be booked
  • Price list for sales order
  • Payment terms to be assigned to sale order
  • currency
  • bill to, ship to org id indicates site use id of customer accounts
  • sold from and sold to org id indicates operating units
  • ship from org id indicates sub-inventory org id
  • invoice to org id indicates bill to -site use id of customer accounts
  • customer id indicates customer account id
  • booked flag = 'Yes'
  • operation code = 'Insert' mode for new sale orders


INSERT
INTO apps.oe_headers_iface_all
  ( order_source_id ,
    orig_sys_document_ref ,
    org_id ,
    ordered_date ,
    order_type_id ,
    price_list_id ,
    transactional_curr_code ,
    salesrep_id ,
    payment_term_id ,
    sold_from_org_id ,
    sold_to_org_id ,
    ship_from_org_id ,
    ship_to_org_id ,
    invoice_to_org_id ,
    customer_id ,
    created_by ,
    creation_date ,
    last_updated_by ,
    last_update_date ,
    request_date ,
    booked_flag ,
    closed_flag ,
    operation_code ,
    change_sequence )
  VALUES
  ( 1001 ,
    v_orig_sys_doc_ref ,
    v_org_id ,
    TRUNC(p_date) ,
    v_order_type ,
    v_price_list_id ,
    'AED' ,
    v_salesrep_id ,
    v_payment_term ,
    v_sold_from_org ,
    v_sold_to_org ,
    v_ship_from_org ,
    v_ship_to_org ,
    v_invoice_to_org ,
    v_cust_id ,
    fnd_global.user_id ,
    TRUNC(p_date) ,
    fnd_global.user_id ,
    TRUNC(p_date) ,
    TRUNC(p_date) ,
    'Y' ,
    'N' ,
    'INSERT' ,
    NULL );

Create sale order lines in standard open interface tables

INSERT
INTO apps.oe_lines_iface_all
  ( order_source_id ,
    orig_sys_document_ref ,
    orig_sys_line_ref ,
    org_id ,
    line_type_id ,
    line_number ,
    inventory_item_id ,
    calculate_price_flag ,
    schedule_ship_date ,
    ordered_quantity ,
    order_quantity_uom ,
    sold_from_org_id ,
    sold_to_org_id ,
    ship_from_org_id ,
    ship_to_org_id ,
    invoice_to_org_id ,
    price_list_id ,
    unit_list_price ,
    unit_selling_price ,
    payment_term_id ,
    salesrep_id ,
    created_by ,
    creation_date ,
    last_updated_by ,
    last_update_date ,
    request_date ,
    subinventory ,
    change_sequence ,
    operation_code )
  VALUES
  ( 1001 ,
    v_orig_sys_doc_ref ,
    v_line_ref ,
    v_org_id ,
    1226 ,
    v_slno ,
    rec_lns.item_id,
    'N' ,
    TRUNC(p_date) ,
    rec_lns.qty ,
    rec_lns.uom ,
    v_sold_from_org ,
    v_sold_to_org ,
    v_ship_from_org ,
    v_ship_to_org ,
    v_invoice_to_org ,
    rec_lns.price_list_id ,
    rec_lns.unit_price ,
    rec_lns.unit_price ,
    v_payment_term ,
    v_salesrep_id ,
    fnd_global.user_id ,
    TRUNC(p_date) ,
    fnd_global.user_id ,
    TRUNC(p_date) ,
    TRUNC(p_date) ,
    rec_lns.route ,
    NULL ,
    'INSERT' );

Comments

Post a Comment

Popular posts from this blog

How to use lexical parameters in Data template (XML document) R12

Lexical parameters can be added in data definition using &variable name This is flexible variable string where you can execute runtime conditions based on user-inputs Example 1. Append &gc_journal_filter at the end of sql statement 2. Define beforereport function in package signature FUNCTION beforereport RETURN BOOLEAN; 3. Define all the report parameters as a package variable in package signature including lexical parameters 4. Implement beforereport function by building your runtime conditions to be added to SQL statements  FUNCTION beforereport RETURN BOOLEAN IS  BEGIN          IF p_journal_source IS NULL THEN       gc_journal_filter := ' AND jh.je_source IN (''AutoCopy'',''Manual'')';     END IF;          IF p_journal_category IS NULL THEN       gc_journal_filter := 'AND jh.je_category IN (''Other'') ';     END IF;    RETURN TRUE;  END;
Read more

Query to get FSG report details with row/column set

Below query is to fetch FSG report titles, names, and description along with will give a view to list of row sets and column sets associated with the report. -- FSG REPORTS -- SELECT fst.id_flex_structure_name , R.NAME , R.report_title , R.DESCRIPTION , R.column_set "COLUMN SET" , rw2.structure_id , rw2.DESCRIPTION "COL DESC" , R.row_set "ROW SET" , rw.DESCRIPTION "ROW DESC" , R.report_display_set "DISPLAY SET" , R.content_set "CONTENT SET" , R.row_order "ROW ORDER" , R.rounding_option "RND" , u.user_name , u.DESCRIPTION , R.creation_date FROM rg_reports_v R    , fnd_id_flex_structures_v fst    , fnd_user u    , rg_report_axis_sets_v rw    , rg_report_axis_sets_v rw2 WHERE r.structure_id = fst.id_flex_num AND R.row_set_id     = rw.axis_set_id AND r.column_set_id  = rw2.axis_set_id AND SUBSTR(fst.id_flex_structure_name,1,2) IN ('DC') AND R.created_by     = u.user_id OR
Read more

Sub Inventory Transfer API.

Image
Sub Inventory transfer is used to move materials from one sub-inventory to another within same organization. This is especially used to 1. Adjust on-hand quantities between sub-inventories 2. Transfer to another sub-inventories for specific business need like additional sales 3. Damages/expiry products can be moved to non-asset sub-inventories to discard it from inventory valuation report and so on., Key elements 1. From sub inventory 2. To sub inventory 3. Organization 4. Inventory item 5. Transact quantity 6. Transact unit of measure 7. Transaction type 8. Transaction action 9. Transact Reference 10. Transact date 11. Lot Number Open Interfaces mtl_transactions_interface - is used to populate sub inventory transfer details mtl_transaction_lots_interface - is used to populate lot details for particular sub inventory transfer Base Tables mtl_material_transactions - is used to get all type of material transactions like sub-inventory transfer, inter-org tra
Read more