Return to vendor through RCV open interface

Hi,
I would like to return to vendor items with serial numbers through RCV open interface. Is it possible?
We are using 11.5.7.
Thanks in advance,
Merav

you can activate action box at following path:
SPRO --> QM --> quality notification --> notification processing. --> Additional notification function --> Define action box.
i hope this would help you.
Thanks!!!

Similar Messages

  • Mark Invoices as Paid through Payables Open Interface

    Hi.
    I have looked at the table definitions for importing invoices into Oracle Payables through the Payables Open Interface. It is clear to me how simply writing to these two tables: AP_INVOICES_INTERFACE and AP_INVOICES_LINES_INTERFACE.
    However, the invoices that i want to import into Oracle have already been processed and paid. It seems that there is no way through these two tables to mark an invoice as Paid and pass in the associated the payment data (for example - a check number). I am retrieving data from an external invoice and payment processing web site and importing this into Oracle E-Business Suite through these two tables. So is there:
    - A way to mark these invoices as Paid through the import and include the check number it was paid with?
    - If not what is the best way to accomplish that in Oracle? Is there any other interface that Oracle provides that will allow this. Do I need to create some kind of routine or workflow in Oracle need to be created to do this? I am new to Oracle, so it is not clear at the moment.
    Thanks!
    Scott

    Scott,
    You cannot bring in paid invoices through payables open interface table.
    This is one workaround you can use.
    1. import the invoices through open interface, the interface record will be marked as Processed.
    2. As soon as your invoice is created, your liability account will be hit and will be increased and cash account will be decreased (I m not using the credit/debit terms purposefully).
    3. You then create a payment batch , and pay the invoice, this will balance the liability and cash accounts
    This way you can simulate the payment you did outside the system and still your books will be in sync.
    Things you would need to take care of:
    1. Payment Dates
    2. Stop the payment instrument (check/creditmemo/debitmemo) from going out
    Lastly, this is a OAF forum, you might get better replies in AP or EBiz forums, so please post your query there.
    Thanks
    Tapash

  • What else can be loaded through AP Open Interface

    Hi All,
    Its a functional query from one who has experience in AP Open Interfaces.
    Actually I'm looking it technically but want to know it at high level, that other than Invoices, what else can be populated or loaded through AP Open Interfaces ?
    Your earliest response will be highly appreciated.
    Regards,

    Hi;
    Please check below which could be helpful for your issue:
    http://docs.oracle.com/cd/A60725_05/html/comnls/us/ap/openimpt.htm
    http://www.shareoracleapps.com/2010/05/payables-open-interface-import-basics.html
    Regard
    Helios

  • Self-Assessed Tax Through Payables Open Interface Import

    Does anyone know what fields are required to process an invoice with use tax through the payable open interface import? We have a custom interface in 11i that loads these invoices and validates nightly. However, in R12 we are using E-Bus Tax engine to "manually" check the "Self Assess" while creating invoices. How can this same process be done through the import????????
    Edited by: user5893077 on Mar 2, 2011 3:50 PM

    Have you customized/setup the Project Accounting Workflow builder. You need to do some setup for this workflow builder so that the project accounts can be derived properly.

  • Limits on number of invoices put through AP Open Interface Tables

    Hi,
    a quick question.
    We have multiple AP systems which we are thinking of interfacing directly with eBusiness Suite. With a potential of approximately 20,000 invoices per night/batch (each invoice will have on average two distribution lines). All invoices are going into a single organisation.
    Does anyone have experience of this number of invoices (or greater) going through the AP Open Interface tables?
    Steve
    nb

    This should certainly be possible - we process about 15000 invoices every night in under 2 hours.
    HTH
    Srini

  • How to create cross charge AP invoice through Payables Open Interface Import

    Hi,
    I am working on developing an AP invoice interface program for creating cross charge invoices in Oracle 11i.
    Cross charge invoice means the supplier & site is from operating unit A, but the costing should hit the project number in Operating unit B.
    The pa_projects_all.allow_cross_charge_flag for the project number is set to Y. I am using below scripts to enter data into the interface tables:
    <code>
    INSERT INTO ap_invoice_lines_interface
                               (invoice_id,
                                invoice_line_id, line_type_lookup_code,
                                amount, org_id,
                                last_update_date, last_updated_by,
                                creation_date, created_by,
                                project_id, task_id,
                                expenditure_type, expenditure_item_date,
                                expenditure_organization_id
                        VALUES (v_invoice_id,
                                ap_invoice_lines_interface_s.NEXTVAL, 'ITEM',
                                c_line.invoice_amount, v_org_id,
                                TRUNC (SYSDATE), fnd_global.user_id,
                                TRUNC (SYSDATE), fnd_global.user_id,
                                v_project_id, v_task_id,
                                v_expenditure_type, v_expenditure_item_date,
                                v_organization_id
    INSERT INTO ap_invoices_interface
                         (invoice_id, invoice_num, invoice_date,
                          gl_date, vendor_id, vendor_site_id,
                          invoice_amount, invoice_currency_code,
                          exchange_rate, exchange_rate_type, exchange_date,
                          terms_id, terms_date, payment_method_lookup_code,
                          pay_group_lookup_code, payment_currency_code,
                          last_update_date, last_updated_by, creation_date,
                          created_by, SOURCE, org_id
                  VALUES (v_invoice_id, c_head.invoice_num, c_head.invoice_date,
                          c_head.gl_date, v_vendor_id, v_vendor_site_id,
                          c_head.invoice_amount, c_head.invoice_currency,
                          v_rate, 'Corporate', c_head.invoice_date,
                          v_terms_id, TRUNC (SYSDATE), v_payment_method,
                          v_paygroup, c_head.payment_currency,
                          TRUNC (SYSDATE), fnd_global.user_id, TRUNC (SYSDATE),
                          fnd_global.user_id, 'CONCUR', v_org_id
    <code>
    After inserting data into the interface tables, I submitted the Payable Open Interface Import with correct source and the record fails with below errors:
    REASON                         DESCRIPTION
    Account Required             An account is required
    PA Flexbuild Failed          Project Flexbuilder failed with error
    The above inserts are working fine for same entity invoices.
    I am not sure what could be the error.
    Any help is greatly appreciated.
    Thanks
    Imran

    Have you customized/setup the Project Accounting Workflow builder. You need to do some setup for this workflow builder so that the project accounts can be derived properly.

  • Return to vendor through OBD

    Hi Experts,
    For return to vendor process, we are creating return goods receipt using movement type 122 and at that time in back ground out bound delivery is creating. Kindly tell me next what steps need to be followed for excise related things and credit note?
    Regards
    Maria

    Hi,
    1. MIGO - Return delivery > Material Document (Here refer GR doc, system will determine mvmt type "122" automatically, select Stock type as "Blocked Stock" under Where tab)
    2. J1IS - Excise Invoice Other Movements
    Here click on u201Ccreateu201D button to create an outgoing excise invoice and reverse the CENVAT Amount.
    Here put all details as below and Press u201CEnteru201D.
    Ref.doc.type - MATD, Doc Number - Material document No of 122 mvmt, Doc Year, Series Group, Excise Group, Vendor
    Here check BED, ECS and SECess values to be reversed and click on u201CSaveu201D button to post the excise invoice.
    3. J1IV - Post and Print Outgoing Excise Invoice.
    4. MIRO - Credit memo w.r.t. Original PO.

  • Credit Memo through Open Interface in AP

    Hi,
    I need to create a credit memo through 'Payables Open Interface Import' program. It also needs to populate 'Credited Invoice' number with the standard invoice number (which is again created through the Open Interface).
    Issues:
    1) Which filed in AP_INVOICES_INTERFACE should be populated to hold the 'Credited Invoice' number ?
    2) Both standard invoice and credit memo invoice are created through single lauch of 'Payables Open Iterface' program. So, referred standard invoice will be in 'Never valdiated' status by the time credit memo is created. But 'Credited Invoice' takes only validated standard invoice numbers. So, do not know how it works out.
    Any inputs on this would be highly helpful !
    Thanks in Advance!
    regards,
    Mukthi.

    Hi,
    You'll find the relationship using:
    select cm.trx_number, trx.trx_number
    from ra_customer_trx_all cm,
    ra_customer_trx_all trx
    where cm.previous_customer_trx_id = trx.customer_trx_id
    When you create an on-account credit memo (both open receivable or not), apps stores the credited transaction id in the column previous_customer_trx_id of the created credit memo.
    You create on-account credit memos by creating referenced RMAs or in transactions form, by going to Actions->Credit.
    Hope it helps,
    Ketter Ohnes

  • Error while doing Return to vendor (122) against PO through QA11

    While doing Return to vendor (122) against Purchase Order through QA11 we are getting the error as Deficit of PU GR quantity 20,000.000 TH: RPO1010 FCHN 007A.
    Steps we are followed.
    1. Created Purchase for Quantity 20 TH with activation of Unlimited Delivery.(TH Means UOM (Thousand)
    2. GR has taken for 20,000 TH instead of 20 TH because of Unlimited Delivery as activated.
    3. Usage decision as given total Quantity accepted based On Inspection Lot generated at MIGO.
    4. Stock has come to Un-Restricted.
    5. For Short fall of  Purchase Order Quantity Increased the PO qty to 20,020.
    6. For Return to vendor we transfer the stock from Un-restricted to Quality by MB1B Mvt type 322.
    7. While Transfer Inspection Lot has generated.
    8. Based on that Inspection Lot we try to do return to vendor through QA11 against the same Purchase Order.
    While doing the Last step we are getting the above error.
    Pls. Kindly look into this and tell me whether this steps are correct, if correct any settings needs to be done to over come the error or tell the Correct Logic to return the Material.
    Thanks & Regards
    Sathish
    Ph:9940518715

    My thoughts on this is that the original PO was for 20TH.  therefore you will only be able to return 20TH against it regardless of what you receipted.  This is because SAP copies from the original PO document for the return and not the GR material document.
    You can try to edit the original PO and increase the amount to 20,020 and try again.  But I don't think you'll be able to edit that since it was fully receipted.
    Your probably going to have to do a return for 20TH and then a separate, stand-alone return for 20,000 TH.
    Craig

  • AP Invoice Open Interface Problem

    Hi,
    Im trying to load invoices through the open interface for AP. I am getting some invoices in but for some reason a large volume of the invoices are being rejected. The open interface is not logging any errors in ap_interface_rejections or on the interface report. It just ignores them. I can see in the log that 900 invoices got selected but only 300 created. HAs anyone had this problem and if so how to get around it?
    Thanks
    Keith

    Hi Keith,
    If this is a production environment I strongly suggest you raise an SR for this issue, as there are some known bugs for rejection of invoices during Open Interface run and Oracle support reps will be able to better help you.
    Please see:
    APXIIMPT: Payables Open Interface Rejects Invoices With Reason - INVALID_GLOBAL_CONTEXT (Doc ID 1548209.1)
    Payables Open Interface Import is not showing some of the Rejected Invoices in the Output Reports. (Doc ID 1476796.1)
    Thanks &
    Best Regards,

  • Supplier open interface import - Related issue

    Hi there,
    when i tried to import the the details of the suppliers from AP_SUPPLIERS_INT(interface table) to PO_VENDORS(base table) through "Suppliers open interface import",
    First time, It showed the rejeted records in the output report. then i cleared the errors in the rejected records.
    Second Time, It showed Rejected records as 0, but didn't show any details regarding imported records. Also not even a single record is imported to base table
    it didn't show neither any rejected record nor the data in the interface table to base table...
    "Supplier open interface import program" gets completed without any error.
    why this happens..?
    columns filled in interface table - AP_SUPPLIERS_INT are:
    vendor_interface_id
    Vendor_name
    segment1
    employee_id(Removed this col when it showed employee doesn't exist in rejected columns)
    payment_currency_code
    vendor_type_lookup_code
    did this in R12
    Expecting a solution for this...
    Thanks in Advance...

    Pl post details of OS, database and EBS versions.
    Pl see if MOS Doc 1060824.1 (R12: Supplier Open Interface APXSUIMP Errors with REP-0004 Output Does Not Indicate Reason for Rejection) is applicable
    HTH
    Srini

  • AP Open Interface Invoices Import/PO Matching

    I am trying to import invoices through invoice Open interface in AP. I also want to do invoice matching with it. But I am facing some errors.
    Anyone having experience with this scenario please respond me at [email protected]
    Faisal.

    HI,
    why not use "Payables Open Interface Import" report in the AP module, this report can automaticlly create invoice against input PO, the PO and invoice are matched after new invoice was created.
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Faisal Khan ([email protected]):
    I am trying to import invoices through invoice Open interface in AP. I also want to do invoice matching with it. But I am facing some errors.
    Anyone having experience with this scenario please respond me at [email protected]
    Faisal.<HR></BLOCKQUOTE>
    null

  • Payable open interface import Issue!

    Hello:
    I want to insert the Debit Memo invoice type through Payable open interface import API, But Payable open interface import program throw the error named is Invalid Inv type lookup code.
    I read out the Oracle Paybales documentation, Oracle does not support the DEBIT invoice type it only supports Standard and Credit type.
    Is there any possibility can we insert the DEBIT type from Payable open interface import program?.
    Please reply me ASAP.
    Thank you.
    Zeeshan

    Thank you Sanjit!
    Sanjeet Can you tell me the steps of How to register my stored procedure in APPS and how can I set my concurrent request.
    Please I need a steps.
    Regards
    Zeeshan

  • Payables open interface not populating voucher_num in R12

    Hi All,
    We are migrating a set of invoices from 11i to R12 and we want the voucher num to be brought in as is.
    The payables open interface table has processed the invoice successfully but the voucher_num did not get populated in the base table.
    Can anyone let me know how we can populate the voucher num as is from 11i through Payables open interface.
    Thanks in advance.
    Cheers,
    MJ

    For whatever it is worth....
    This is resolved by ledger set up--> Accounting Setups and adding the balancing segments for which the accounts relate to.

  • 11.5.10 RECEIVING OPEN INTERFACE를 통해 RETURN처리하는 방법

    제품 : MFG_PO
    작성날짜 : 2006-05-30
    11.5.10 RECEIVING OPEN INTERFACE를 통해 RETURN처리하는 방법
    ==================================================
    PURPOSE
    11.5.10에서 Receiving Open Interface를 통해 Return처리하는 방법을 기술함.
    Explanation
    11.5.10 is ROI supports for Standard Purchase Order
    . RETURN to RECEIVING transactions
    . RETURN to VENDOR transactions
    1. Receipt routing = Standard Receipt일 경우
    A) perform a "RETURN to RECEIVING" for a standard Purchase Order
    through ROI
    TRANSACTION_TYPE = RETURN TO RECEIVING
    PARENT_TRANSACTION_ID = (Transaction Id for DELIVER transaction)
    B) perform a "RETURN to VENDOR" for a standard Purchase Order
    through ROI
    TRANSACTION_TYPE = RETURN TO VENDOR
    PARENT_TRANSACTION_ID = (Transaction Id for RECEIVE transaction)
    2. Receipt routing = Direct Receipt일 경우,
    ==> only 1 step return is needed,
    TRANSACTION_TYPE = RETURN TO VENDOR
    TRANSACTION_ID = (Transaction Id for DELIVER transaction)
    3. a Lot and Serial Controlled Item의 경우,
    다음 table들에 data를 Insert해 주어야 합니다.
    RCV_TRANSACTIONS_INTERFACE,
    MTL_TRANSACTIONS_LOTS_INTERFACE,
    MTL_SERIAL_NUMBERS_INTERFACE.
    TEST
    step1> PO등록
    1) Standard Purchase Order number: # 8415
    Inventory Item = Lot-Serial-Controlled-1
    Receipt Routing = Standard Receipt
    Destination Type Code = Inventory
    step2) Receipt처리
    Receipt number :# 7970
    The deliver transaction's quantity=1
    item=Lot-Serial-Controlled-1
    Lot Number=S336
    Serial Number = SN0021
    step3> Return처리
    A) "RETURN to RECEIVING" for PURCHASE ORDER Example
    SQL>
    INSERT INTO RCV_TRANSACTIONS_INTERFACE
    (INTERFACE_TRANSACTION_ID,
    GROUP_ID,
    LAST_UPDATE_DATE,
    LAST_UPDATED_BY,
    CREATION_DATE,
    CREATED_BY,
    LAST_UPDATE_LOGIN,
    TRANSACTION_TYPE,
    TRANSACTION_DATE,
    PROCESSING_STATUS_CODE,
    PROCESSING_MODE_CODE,
    TRANSACTION_STATUS_CODE,
    QUANTITY,
    UNIT_OF_MEASURE,
    ITEM_ID,
    EMPLOYEE_ID,
    SHIPMENT_HEADER_ID,
    SHIPMENT_LINE_ID,
    RECEIPT_SOURCE_CODE,
    VENDOR_ID,
    FROM_ORGANIZATION_ID,
    FROM_SUBINVENTORY,
    FROM_LOCATOR_ID,
    SOURCE_DOCUMENT_CODE,
    PARENT_TRANSACTION_ID,
    PO_HEADER_ID,
    PO_LINE_ID,
    PO_LINE_LOCATION_ID,
    PO_DISTRIBUTION_ID,
    DESTINATION_TYPE_CODE,
    DELIVER_TO_PERSON_ID,
    LOCATION_ID,
    DELIVER_TO_LOCATION_ID,
    VALIDATION_FLAG
    VALUES
    (rcv_transactions_interface_s.nextval, --INTERFACE_TRANSACTION_ID
    rcv_interface_groups_s.nextval, --GROUP_ID
    SYSDATE, --LAST_UPDATE_DATE
    0, --LAST_UPDATE_BY
    SYSDATE, --CREATION_DATE
    0, --CREATED_BY
    0, --LAST_UPDATE_LOGIN
    'RETURN TO RECEIVING', --TRANSACTION_TYPE
    SYSDATE, --TRANSACTION_DATE
    'PENDING', --PROCESSING_STATUS_CODE
    'BATCH', --PROCESSING_MODE_CODE
    'PENDING', --TRANSACTION_STATUS_CODE
    1, --QUANTITY
    'Each', --UNIT_OF_MEASURE
    169845, --ITEM_ID
    13706, --EMPLOYEE_ID
    477550, --SHIPMENT_HEADER_ID
    484510, --SHIPMENT_LINE_ID
    'VENDOR', --RECEIPT_SOURCE_CODE
    7927, --VENDOR_ID
    204, --FROM_ORGANIZATION_ID
    'Stores', --FROM_SUBINVENTORY
    null, --FROM_LOCATOR_ID
    'PO', --SOURCE_DOCUMENT_CODE
    524018, --PARENT_TRANSACTION_ID
    40924, --PO_HEADER_ID
    46915, --PO_LINE_ID
    81963, --PO_LINE_LOCATION_ID
    84349, --PO_DISTRIBUTION_ID
    'INVENTORY', --DESTINATION_TYPE_CODE
    null, --DELIVER_TO_PERSON_ID
    null, --LOCATION_ID
    null, --DELIVER_TO_LOCATION_ID
    'Y' --VALIDATION_FLAG
    INSERT INTO MTL_TRANSACTION_LOTS_INTERFACE
    ( TRANSACTION_INTERFACE_ID,
    LAST_UPDATE_DATE,
    LAST_UPDATED_BY,
    CREATION_DATE,
    CREATED_BY,
    LAST_UPDATE_LOGIN,
    LOT_NUMBER,
    TRANSACTION_QUANTITY,
    PRIMARY_QUANTITY,
    SERIAL_TRANSACTION_TEMP_ID,
    PRODUCT_CODE,
    PRODUCT_TRANSACTION_ID
    VALUES
    ( MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL,--
    TRANSACTION_INTERFACE_ID
    SYSDATE, --LAST_UPDATE_DATE
    0, --LAST_UPDATED_BY
    SYSDATE, --CREATION_DATE
    0, --CREATED_BY
    0, --LAST_UPDATE_LOGIN
    'S366', --LOT_NUMBER
    1, --TRANSACTION_QUANTITY
    1, --PRIMARY_QUANTITY
    MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL, --
    SERIAL_TRANSACTION_TEMP_ID
    'RCV', --PRODUCT_CODE
    RCV_TRANSACTIONS_INTERFACE_S.CURRVAL --
    PRODUCT_TRANSACTION_ID
    INSERT INTO MTL_SERIAL_NUMBERS_INTERFACE
    ( TRANSACTION_INTERFACE_ID,
    LAST_UPDATE_DATE,
    LAST_UPDATED_BY,
    CREATION_DATE,
    CREATED_BY,
    LAST_UPDATE_LOGIN,
    FM_SERIAL_NUMBER,
    TO_SERIAL_NUMBER,
    PRODUCT_CODE,
    PRODUCT_TRANSACTION_ID)
    VALUES
    (MTL_MATERIAL_TRANSACTIONS_S.CURRVAL,--
    TRANSACTION_INTERFACE_ID
    SYSDATE, --LAST_UPDATE_DATE
    0, --LAST_UPDATED_BY
    SYSDATE, --CREATION_DATE
    0, --CREATED_BY
    0, --LAST_UPDATE_LOGIN
    'SN0021', --FM_SERIAL_NUMBER
    'SN0021', --TO_SERIAL_NUMBER
    'RCV', --PRODUCT_CODE
    RCV_TRANSACTIONS_INTERFACE_S.CURRVAL --
    PRODUCT_TRANSACTION_ID
    Commit;
    B) "RETURN to VENDOR" Transaction for PURCHASE ORDER
    INSERT INTO RCV_TRANSACTIONS_INTERFACE
    (INTERFACE_TRANSACTION_ID,
    GROUP_ID,
    LAST_UPDATE_DATE,
    LAST_UPDATED_BY,
    CREATION_DATE,
    CREATED_BY,
    LAST_UPDATE_LOGIN,
    TRANSACTION_TYPE,
    TRANSACTION_DATE,
    PROCESSING_STATUS_CODE,
    PROCESSING_MODE_CODE,
    TRANSACTION_STATUS_CODE,
    QUANTITY,
    UNIT_OF_MEASURE,
    ITEM_ID,
    EMPLOYEE_ID,
    SHIPMENT_HEADER_ID,
    SHIPMENT_LINE_ID,
    RECEIPT_SOURCE_CODE,
    VENDOR_ID,
    FROM_ORGANIZATION_ID,
    FROM_SUBINVENTORY,
    FROM_LOCATOR_ID,
    SOURCE_DOCUMENT_CODE,
    PARENT_TRANSACTION_ID,
    PO_HEADER_ID,
    PO_LINE_ID,
    PO_LINE_LOCATION_ID,
    PO_DISTRIBUTION_ID,
    DESTINATION_TYPE_CODE,
    DELIVER_TO_PERSON_ID,
    LOCATION_ID,
    DELIVER_TO_LOCATION_ID,
    VALIDATION_FLAG
    VALUES
    (rcv_transactions_interface_s.nextval, --INTERFACE_TRANSACTION_ID
    rcv_interface_groups_s.nextval, --GROUP_ID
    SYSDATE, --LAST_UPDATE_DATE
    0, --LAST_UPDATE_BY
    SYSDATE, --CREATION_DATE
    0, --CREATED_BY
    0, --LAST_UPDATE_LOGIN
    'RETURN TO VENDOR', --TRANSACTION_TYPE
    SYSDATE, --TRANSACTION_DATE
    'PENDING', --PROCESSING_STATUS_CODE
    'BATCH', --PROCESSING_MODE_CODE
    'PENDING', --TRANSACTION_STATUS_CODE
    1, --QUANTITY
    'Each', --UNIT_OF_MEASURE
    169845, --ITEM_ID
    13706, --EMPLOYEE_ID
    477550, --SHIPMENT_HEADER_ID
    484510, --SHIPMENT_LINE_ID
    'VENDOR', --RECEIPT_SOURCE_CODE
    7927, --VENDOR_ID
    204, --FROM_ORGANIZATION_ID
    'Stores', --FROM_SUBINVENTORY
    null, --FROM_LOCATOR_ID
    'PO', --SOURCE_DOCUMENT_CODE
    524017, --PARENT_TRANSACTION_ID
    40924, --PO_HEADER_ID
    46915, --PO_LINE_ID
    81963, --PO_LINE_LOCATION_ID
    84349, --PO_DISTRIBUTION_ID
    'RECEIVING', --DESTINATION_TYPE_CODE
    null, --DELIVER_TO_PERSON_ID
    null, --LOCATION_ID
    null, --DELIVER_TO_LOCATION_ID
    'Y' --VALIDATION_FLAG
    INSERT INTO MTL_TRANSACTION_LOTS_INTERFACE
    ( TRANSACTION_INTERFACE_ID,
    LAST_UPDATE_DATE,
    LAST_UPDATED_BY,
    CREATION_DATE,
    CREATED_BY,
    LAST_UPDATE_LOGIN,
    LOT_NUMBER,
    TRANSACTION_QUANTITY,
    PRIMARY_QUANTITY,
    SERIAL_TRANSACTION_TEMP_ID,
    PRODUCT_CODE,
    PRODUCT_TRANSACTION_ID
    VALUES
    ( MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL,--
    TRANSACTION_INTERFACE_ID
    SYSDATE, --LAST_UPDATE_DATE
    0, --LAST_UPDATED_BY
    SYSDATE, --CREATION_DATE
    0, --CREATED_BY
    0, --LAST_UPDATE_LOGIN
    'S366', --LOT_NUMBER
    1, --TRANSACTION_QUANTITY
    1, --PRIMARY_QUANTITY
    MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL, --
    SERIAL_TRANSACTION_TEMP_ID
    'RCV', --PRODUCT_CODE
    RCV_TRANSACTIONS_INTERFACE_S.CURRVAL --
    PRODUCT_TRANSACTION_ID
    INSERT INTO MTL_SERIAL_NUMBERS_INTERFACE
    ( TRANSACTION_INTERFACE_ID,
    LAST_UPDATE_DATE,
    LAST_UPDATED_BY,
    CREATION_DATE,
    CREATED_BY,
    LAST_UPDATE_LOGIN,
    FM_SERIAL_NUMBER,
    TO_SERIAL_NUMBER,
    PRODUCT_CODE,
    PRODUCT_TRANSACTION_ID)
    VALUES
    (MTL_MATERIAL_TRANSACTIONS_S.CURRVAL,--
    TRANSACTION_INTERFACE_ID
    SYSDATE, --LAST_UPDATE_DATE
    0, --LAST_UPDATED_BY
    SYSDATE, --CREATION_DATE
    0, --CREATED_BY
    0, --LAST_UPDATE_LOGIN
    'SN0021', --FM_SERIAL_NUMBER
    'SN0021', --TO_SERIAL_NUMBER
    'RCV', --PRODUCT_CODE
    RCV_TRANSACTIONS_INTERFACE_S.CURRVAL --
    PRODUCT_TRANSACTION_ID
    Commit;
    step4) RUN the Receiving Transaction Processor with (GROUP_ID=30053)
    step5) Check a data
    Navigate to Receiving / Receiving Transactions Summary form
    Example
    Reference Documents
    Note#360340.1

    I have done this by a direct insert.
    I had loaded a table called xx_eam_msii. It holds the item id , org id and locator id.
    The following works.
    INSERT
    INTO MTL_ITEM_LOC_DEFAULTS (INVENTORY_ITEM_ID ,ORGANIZATION_ID ,locator_id,DEFAULT_TYPE,subinventory_code
    ,LAST_UPDATE_DATE ,LAST_UPDATED_BY ,CREATION_DATE ,CREATED_BY )
    (select msi.inventory_item_id,msi.organization_id ,x.inventory_location_id,2,x.receiving_subinventory
    ,sysdate,11531,sysdate,11531
    from mtl_system_items_b msi, xx_eam_msii x
    where x.segment1 = msi.segment1 and msi.organization_id = x.organization_id
    and not exists (select 1 from MTL_ITEM_LOC_DEFAULTS misd
    where misd.inventory_item_id = msi.inventory_item_id and misd.organization_id = msi.organization_id
    and DEFAULT_TYPE = 2)
    Hope this helps,
    Sandeep Gandhi

Maybe you are looking for