RECEIVING OPEN INTERFACE TABLE의 STRUCK RECORDS 정보 취합 SCRIPT

제품 : MFG_PO     
작성날짜 : 2005-01-27     
RECEIVING OPEN INTERFACE TABLE의 STRUCK RECORDS 정보 취합 SCRIPT
=================================================================
PURPOSE
RCV_TRANSACTIONS_INTERFACE table에 있는 struck receipt records의 정보를
취합하여, struck 원인 및 해결에 도움을 줄 수 있다.
(Oracle Purchasing - Version: 11.5.2 to 11.5.9)
Explanation
Receiving Open Interface Tables에 걸려 있는 receipt struck의 source
document의 추가 정보를 어떻게 취합할 수 있을것인가?
(RCV_TRANSACTIONS_INTERFACE)
Source document는 아래 중 하나가 될 수 있다.
* Purchase Order
* Return Material Authorization (RMA)
* Internal Requisition
아래에 소개하는 scripts는 interface tables에 많은 수의 records가 있을때,
많은 수의 records의 정보를 한 번에 취합하길 원할때 사용하면 유용하다.
만약 interface tables에 단지 몇 개의 records만 있다면 Note: 171257.1
- Oracle Procurement (Purchasing)/iProcurement Diagnostic Tests 에 소개
되어져 있는 적당한 diagnostic script를 이용하는편이 낫다.
Example
1.Error가 발생한 Purchase Order receipts의 추가 정보를 취합하는 script:
SELECT SUBSTR(POH.SEGMENT1,1,10) "PO Number",
POR.RELEASE_NUM "Release Num",
POL.LINE_NUM "Line Num",
RTI.INTERFACE_TRANSACTION_ID "Intf Trx Id",
RTI.TRANSACTION_DATE "Trx Date",
RTI.PROCESSING_MODE_CODE "Proc Mode",
RTI.TRANSACTION_STATUS_CODE "Trx Status",
RTI.PROCESSING_STATUS_CODE "Proc Status",
SUBSTR(PIE.ERROR_MESSAGE,1,75) "Error Message",
POH.ORG_ID "Op Unit Id",
RTI.PO_HEADER_ID "PO Hdr Id",
RTI.PO_RELEASE_ID "Rel Id",
RTI.PO_LINE_ID "PO Line Id",
RTI.PO_LINE_LOCATION_ID "Line Loc Id",
RTI.QUANTITY "Intf Qty",
POLL.QUANTITY "Order Qty",
POLL.QUANTITY_RECEIVED "Qty recvd",
POD.QUANTITY_DELIVERED "Qty Delv",
NVL(POLL.CLOSED_CODE,'OPEN') "Closed Code",
OOD.ORGANIZATION_CODE "To Inv Org",
RTI.DESTINATION_TYPE_CODE "Dest Type",
RTI.TRANSACTION_TYPE "Intf Trx Type",
NVL(POLL.QTY_RCV_EXCEPTION_CODE,'NONE') "Qty Exception",
POLL.QTY_RCV_TOLERANCE "Qty Tolerance",
POLL.RECEIVE_CLOSE_TOLERANCE "Receipt Tolerance"
FROM RCV_TRANSACTIONS_INTERFACE RTI,
PO_HEADERS_ALL POH,
PO_RELEASES_ALL POR,
PO_LINES_ALL POL,
PO_LINE_LOCATIONS_ALL POLL,
ORG_ORGANIZATION_DEFINITIONS OOD,
PO_DISTRIBUTIONS_ALL POD,
PO_INTERFACE_ERRORS PIE
WHERE POH.PO_HEADER_ID = RTI.PO_HEADER_ID
AND POR.PO_RELEASE_ID(+) = RTI.PO_RELEASE_ID
AND POL.PO_LINE_ID = RTI.PO_LINE_ID
AND OOD.ORGANIZATION_ID(+) = RTI.TO_ORGANIZATION_ID
AND POLL.LINE_LOCATION_ID = RTI.PO_LINE_LOCATION_ID
AND POD.LINE_LOCATION_ID = POLL.LINE_LOCATION_ID
AND RTI.INTERFACE_TRANSACTION_ID = PIE.INTERFACE_TRANSACTION_ID(+);
2.Error가 발생한 RMA receipts의 추가 정보를 취합하는 script:
SELECT RTI.INTERFACE_TRANSACTION_ID "Interface Transaction ID",
RTI.PROCESSING_STATUS_CODE "Processing Status",
RTI.PROCESSING_MODE_CODE "Processing Mode",
RTI.TRANSACTION_STATUS_CODE "Transaction Status",
RTI.TRANSACTION_TYPE "Transaction Type",
RTI.TRANSACTION_DATE "Transaction Date",
RTI.OE_ORDER_HEADER_ID "Order header Id",
OOH.ORDER_NUMBER "Order Number",
OOH.ORG_ID "Oper Unit Id",
RTI.OE_ORDER_LINE_ID "Order Line Id",
OOL.INVENTORY_ITEM_ID "Order Item",
OOL.FLOW_STATUS_CODE "Line Flow Status Code",
RTI.QUANTITY "Intf Qty",
RTI.UNIT_OF_MEASURE "Intf UOM",
OOL.ORDERED_QUANTITY "Qty Ordered",
OOL.SHIPPED_QUANTITY "Qty Shipped",
OOL.FULFILLED_QUANTITY "Qty Fulfilled",
OOL.OPEN_FLAG "Open Flag",
OOL.CANCELLED_FLAG "Cancelled",
WH.ORGANIZATION_CODE||' - '||WH.ORGANIZATION_NAME
"Ship To Organization",
WH1.ORGANIZATION_CODE||' - '||WH1.ORGANIZATION_NAME
"Ship From Organization",
OOL.BOOKED_FLAG "Booked",
SUBSTR(PIE.ERROR_MESSAGE,1,75) "Error Message"
FROM RCV_TRANSACTIONS_INTERFACE RTI,
OE_ORDER_LINES_ALL OOL,
OE_ORDER_HEADERS_ALL OOH,
ORG_ORGANIZATION_DEFINITIONS WH,
ORG_ORGANIZATION_DEFINITIONS WH1,
PO_INTERFACE_ERRORS PIE
WHERE OOL.HEADER_ID = RTI.OE_ORDER_HEADER_ID
AND OOL.LINE_CATEGORY_CODE = 'RETURN'
AND OOL.LINE_ID = RTI.OE_ORDER_LINE_ID
AND OOH.HEADER_ID = RTI.OE_ORDER_HEADER_ID
AND OOL.SHIP_TO_ORG_ID = WH.ORGANIZATION_ID(+)
AND OOL.SHIP_FROM_ORG_ID = WH1.ORGANIZATION_ID(+)
AND RTI.INTERFACE_TRANSACTION_ID = PIE.INTERFACE_TRANSACTION_ID(+)
ORDER BY RTI.INTERFACE_TRANSACTION_ID;
3.Error가 발생한 Internal Requisition receipts의 추가 정보를 취합하는
script:
SELECT RTI.RECEIPT_SOURCE_CODE "Receipt Source Code",
RTI.REQUISITION_LINE_ID "Intf Req Line Id",
RTI.SHIPMENT_HEADER_ID "Ship Hdr Id",
RTI.SHIPMENT_LINE_ID "Ship Line Id",
RTI.ITEM_ID "Item Id",
RTI.QUANTITY "Intf Qty",
RTI.UNIT_OF_MEASURE "UOM",
RTI.FROM_ORGANIZATION_ID "From Org Id",
RTI.TO_ORGANIZATION_ID "To Org id",
PRH.REQUISITION_HEADER_ID "Req Hdr Id",
PRH.SEGMENT1 "Req Num",
PRL.REQUISITION_LINE_ID "Req Line Id",
NVL(PRL.QUANTITY_DELIVERED,0) "Qty Delv",
NVL(PRL.QUANTITY_CANCELLED,0) "Qty Canc",
PRL.QUANTITY "Qty Ordered",
PRL.QUANTITY - (nvl(PRL.QUANTITY_CANCELLED,0) +
NVL(PRL.QUANTITY_DELIVERED,0))"Qty Remaining",
PRL.SOURCE_TYPE_CODE "Source Type",
PRH.TRANSFERRED_TO_OE_FLAG "XFR to OE Flag",
NVL(PRL.CANCEL_FLAG,'N') "Cancelled",
NVL(PRL.CLOSED_CODE,'OPEN') "Closed Code",
LIN.LINE_ID "ISO Line Id",
NVL(LIN.ORDERED_QUANTITY,0) "ISO Line Qty",
NVL(LIN.SHIPPED_QUANTITY,0) "ISO Ship Qty",
NVL(FULFILLED_QUANTITY,0) "ISO Fulfilled Qty",
NVL(LIN.CANCELLED_QUANTITY,0) "ISO Cancelled Qty",
NVL(LIN.OPEN_FLAG,'N') "ISO Line Open",
NVL(LIN.BOOKED_FLAG,'N') "ISO Line Booked",
NVL(LIN.CANCELLED_FLAG,'N') "ISO Line Cancelled",
OOH.ORDER_NUMBER "ISO Order Number",
PIE.COLUMN_NAME "Intf Column",
SUBSTR(PIE.ERROR_MESSAGE,1,75) "Error Message"
FROM RCV_TRANSACTIONS_INTERFACE RTI,
PO_REQUISITION_HEADERS_ALL PRH,
PO_REQUISITION_LINES_ALL PRL,
PO_INTERFACE_ERRORS PIE,
OE_ORDER_LINES_ALL LIN,
OE_ORDER_HEADERS_ALL OOH
WHERE PRL.REQUISITION_HEADER_ID = PRH.REQUISITION_HEADER_ID
AND RTI.REQUISITION_LINE_ID = PRL.REQUISITION_LINE_ID
AND LIN.SOURCE_DOCUMENT_ID = PRH.REQUISITION_HEADER_ID
AND LIN.SOURCE_DOCUMENT_LINE_ID = PRL.REQUISITION_LINE_ID
AND LIN.SOURCE_DOCUMENT_TYPE_ID = 10 --Internal Requisition
AND OOH.HEADER_ID = LIN.HEADER_ID
AND PIE.INTERFACE_TRANSACTION_ID(+) = RTI.INTERFACE_TRANSACTION_ID
ORDER by PRH.SEGMENT1;
Reference Documents
Note 263368.1

Any suggestion/advise please!
Thanks,
Genoo

Similar Messages

  • SAMPLE RECEIVING OPEN INTERFACE SCRIPT(ROI 이용자를 위한 SCRIPT)

    제품: MFG_PO
    작성날짜 : 2006-05-11
    SAMPLE RECEIVING OPEN INTERFACE SCRIPT(ROI 이용자를 위한 SCRIPT)
    ================================================================
    PURPOSE
    Receiving Open Interface(ROI)를 좀더 쉽게 사용할 수 있도록 만들어진
    tool이라고 할 수 있다. 이 script를 이용을 통해 user는 PO no, user id,
    Org id를 입력하면 script는 PO에서 최소한의 data를 가져와 receiving
    transaction을 생성하기 위해 ROI에 data를 입력한다.
    Receiving Transaction Processor는 insert 된 data를 실행한다.
    Explanation
    Instructions:
    1.Script exroi.sql을 local computer에 copy 하거나 sqlplus 환경의 text
    edior에 script 내용을 cut&paste 한다.
    2.사용가능한 PO no, User id, Org id를 결정한다.
    3.sqlplus prompt에서 아래와 같이 입력한다.
    SQL> @ezroi.sql
    4.PO no, User id, Org id를 입력하라는 prompt를 볼 수 있을 것이다.
    5.exroi.sql script를 관련된 PO data를 가져와 rcv_headers_interface 및
    rcv_transactions_interface tables에 insert 한다.
    만일 PO shipment lind이 closed, cancelled, fully received 되었다면
    ROI table에 data를 insert 하지 않는다.
    Note: 이 script가 data를 validate 하진 않으며,ROI API 자체 validation
    이 실행될 뿐이다.
    6.Script가 끝나면 Receiving Transaction Processor를 실행하여 insert 된
    lines을 처리할 수 있다. Transaction Status Summary 화면을 통해 실행된
    line이 pending 인지 error 상태인지 확인할 수 있다.
    Notes:
    1.Org_id parameter 값을 찾는법:
    a) Application에 접속, Help> Diagnostics> Examine으로 이동.
    Block:$Profile$, Field: ORG_ID 를 선택한다.
    b) ORG_ID 값을 note 해 놓고 ORG_ID prompt시 이 값을 입력한다.
    2.User_Name parameter 값을 찾는법:
    a) Application에 접속, Help> Diagnostics> Examine으로 이동.
    Block:$Profile$, Field: USER_NAME 를 선택한다.
    b) USER_NAME 값을 note 해 놓고 USER_NAME prompt시 이 값을 입력한다.
    Example
    "eZROI.sql' script...
    --*** eZROI ***
    --*** by ***
    --*** Preston D. Davenport ***
    --*** Oracle Premium Applications Support ***
    --*** Oracle Worldwide Global Support Services ***
    --*** Date: 23-JUL-2003 - Beta release ***
    --*** Date: 09-SEP-2003 - Rev A Added multi- ***
    --*** shipment line capability ***
    --*** Parameters: ***
    --*** ORG_ID Organization ID ***
    --*** USER_NAME FND User Name ***
    --*** PO_NUMBER Purchase Order Number ***
    --*** This script intended for a standard Purchase ***
    --*** Order document to be inserted into the Oracle ***
    --*** Receiving Open Interface (ROI) via the standard ***
    --*** Oracle open interface api for a simple Receive ***
    --*** transaction. ***
    --*** Note: This script only considers open Purchase ***
    --*** Orders. This script will not allow over- ***
    --*** receipt, cancelled or closed PO's to be ***
    --*** inserted into the ROI and received ***
    CLEAR BUFFER
    SET VERIFY OFF
    SET LINESIZE 140
    SET PAGESIZE 60
    SET ARRAYSIZE 1
    SET SERVEROUTPUT ON SIZE 100000
    SET FEEDBACK OFF
    SET ECHO OFF
    DECLARE
    X_USER_ID NUMBER;
    X_PO_HEADER_ID NUMBER;
    X_VENDOR_ID NUMBER;
    X_SEGMENT1 NUMBER;
    X_ORG_ID NUMBER;
    X_LINE_NUM NUMBER;
    BEGIN
    DBMS_OUTPUT.PUT_LINE('***ezROI RCV API Insert Script***');
    SELECT PO_HEADER_ID , VENDOR_ID , SEGMENT1 , ORG_ID
    INTO X_PO_HEADER_ID , X_VENDOR_ID , X_SEGMENT1 , X_ORG_ID
    FROM PO_HEADERS_ALL
    WHERE SEGMENT1 = '&PO_NUMBER'
    AND ORG_ID = &ORG_ID;
    SELECT USER_ID INTO X_USER_ID
    FROM FND_USER
    WHERE USER_NAME = UPPER('&USER_NAME');
    INSERT INTO RCV_HEADERS_INTERFACE
    HEADER_INTERFACE_ID ,
    GROUP_ID ,
    PROCESSING_STATUS_CODE ,
    RECEIPT_SOURCE_CODE ,
    TRANSACTION_TYPE ,
    LAST_UPDATE_DATE ,
    LAST_UPDATED_BY ,
    LAST_UPDATE_LOGIN ,
    VENDOR_ID ,
    EXPECTED_RECEIPT_DATE ,
    VALIDATION_FLAG
    SELECT
    RCV_HEADERS_INTERFACE_S.NEXTVAL ,
    RCV_INTERFACE_GROUPS_S.NEXTVAL ,
    'PENDING' ,
    'VENDOR' ,
    'NEW' ,
    SYSDATE ,
    X_USER_ID ,
    0 ,
    X_VENDOR_ID ,
    SYSDATE ,
    'Y'
    FROM DUAL;
    DECLARE
    CURSOR PO_LINE IS
    SELECT PL.ITEM_ID , PL.PO_LINE_ID , PL.LINE_NUM ,
    PLL.QUANTITY , PL.UNIT_MEAS_LOOKUP_CODE ,
    MP.ORGANIZATION_CODE , PLL.LINE_LOCATION_ID ,
    PLL.CLOSED_CODE , PLL.QUANTITY_RECEIVED ,
    PLL.CANCEL_FLAG, PLL.SHIPMENT_NUM
    FROM PO_LINES_ALL PL ,
    PO_LINE_LOCATIONS_ALL PLL ,
    MTL_PARAMETERS MP
    WHERE PL.PO_HEADER_ID = X_PO_HEADER_ID
    AND PL.PO_LINE_ID = PLL.PO_LINE_ID
    AND PLL.SHIP_TO_ORGANIZATION_ID = MP.ORGANIZATION_ID;
    BEGIN
    FOR CURSOR1 IN PO_LINE LOOP
    IF CURSOR1.CLOSED_CODE IN ('APPROVED','OPEN')
    AND CURSOR1.QUANTITY_RECEIVED < CURSOR1.QUANTITY
    AND NVL(CURSOR1.CANCEL_FLAG,'N') = 'N'
    THEN
    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 ,
    PO_LINE_ID ,
    ITEM_ID ,
    QUANTITY ,
    UNIT_OF_MEASURE ,
    PO_LINE_LOCATION_ID ,
    AUTO_TRANSACT_CODE ,
    RECEIPT_SOURCE_CODE ,
    TO_ORGANIZATION_CODE ,
    SOURCE_DOCUMENT_CODE ,
    DOCUMENT_NUM ,
    HEADER_INTERFACE_ID ,
    VALIDATION_FLAG
    SELECT
    RCV_TRANSACTIONS_INTERFACE_S.NEXTVAL ,
    RCV_INTERFACE_GROUPS_S.CURRVAL ,
    SYSDATE ,
    X_USER_ID ,
    SYSDATE ,
    X_USER_ID ,
    0 ,
    'RECEIVE' ,
    SYSDATE ,
    'PENDING' ,
    'BATCH' ,
    'PENDING' ,
    CURSOR1.PO_LINE_ID ,
    CURSOR1.ITEM_ID ,
    CURSOR1.QUANTITY ,
    CURSOR1.UNIT_MEAS_LOOKUP_CODE ,
    CURSOR1.LINE_LOCATION_ID ,
    'RECEIVE' ,
    'VENDOR' ,
    CURSOR1.ORGANIZATION_CODE ,
    'PO' ,
    X_SEGMENT1 ,
    RCV_HEADERS_INTERFACE_S.CURRVAL ,
    'Y'
    FROM DUAL;
    DBMS_OUTPUT.PUT_LINE('PO line: '||CURSOR1.LINE_NUM||' Shipment: '||CURSOR1.SHIPMENT_NUM||' has been inserted into ROI.');
    ELSE
    DBMS_OUTPUT.PUT_LINE('PO line '||CURSOR1.LINE_NUM||' is either closed, cancelled, received.');
    END IF;
    END LOOP;
    DBMS_OUTPUT.PUT_LINE('*** ezROI COMPLETE - End ***');
    END;
    COMMIT;
    END;
    SET VERIFY ON
    Reference Documents
    Note 245334.1

    I have the same problem on ESXI 5.5 for over a month now, tried the patches, tried the LTS kernel which others say results in an immediate result without patches, nothing seems to work and nobody seems to be able to offer a solution.
    Did you make any progress ??
    Error! Build of vmblock.ko failed for: 3.10.25-1-lts (x86_64)
    Consult the make.log in the build directory
    /var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
    make[2]: *** No rule to make target '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/linux/inode', needed by '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/vmblock.o'. Stop.
    Makefile:1224: recipe for target '_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock' failed
    make[1]: *** [_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock] Error 2
    make[1]: Leaving directory '/usr/src/linux-3.10.25-1-lts'
    Makefile:120: recipe for target 'vmblock.ko' failed
    Last edited by crankshaft (2014-01-10 11:32:32)

  • Receiving Open Interface related doubt

    Hi All,
    We are currently on Oracle Release 12.0.4 and need some help/information regards Receiving Open Interface tables : rcv_headers_interface & rcv_transactions_interface tables.
    We import the ASN which is being sent across from the Supplier via EDI directly into the Receiving Open Interface tables and then RTP program ( Receiving Transaction Processor ) program processes these into the base tables
    to complete the receipt process..
    Now for some reason or the other lets say because of EDI data issues or some other system issue with the RTP program , the Interface records end up in error status & the users have to manually complete the Receipt in Oracle Forms directly..
    Now this Interface data over a period in time keeps accumulating while the corresponding PO Document would already have been Received manually in Oracle.
    Because of this errored interface records the Interface tables keep growing in size in terms of data volume..
    Now is there a way script or a program which validates these interface records and purges these automatically based on some validations on its own..
    For Example : for a po if the records are stuck in the interface table but the po shipment has already been received in manually and in Closed Status, then it would automatically purge these records from interface tables.
    Could someone please help us with this as soon as possible with any suggestions or workarounds..
    Thanks

    Currently there is no purge program available to purge the records in RTI. Further the oracle support wont be able to provide a delete script to delete the records in RTI (The reason being, the records are populated by the customer and customers are the best persons to validate the records and delete them on their own).
    However, for ASN's
    You may write a query based on the RTI.po_distribution_id and then check, whether the corresponding po shipment\distribution is already received \ closed for receiving and then you may delete.

  • Receiving Open Interface not picking Inter-Org records from Interface

    Hi,
    I am trying to receive the inter org transfer through the Receiving Open interface, but the interface not picking the data from the interface tables (RCV_HEADERS_INTERFACE, RCV_TRANSACTION_INTERFACE).
    I am in 11.5.10.2, all the sources worked fine like Vendor, Internal Order, Customer but the issue is with the Inventory source (inter orgs)
    Please could you advise what could be the reason for the interface for not picking the Inventory source data from the interface table.
    Below are the interface insert script that am using..
    INSERT INTO RCV_HEADERS_INTERFACE
    (HEADER_INTERFACE_ID,
    GROUP_ID,
    PROCESSING_STATUS_CODE,
    RECEIPT_SOURCE_CODE,
    TRANSACTION_TYPE,
    AUTO_TRANSACT_CODE,
    LAST_UPDATE_DATE,
    LAST_UPDATED_BY,
    LAST_UPDATE_LOGIN,
    CREATION_DATE,
    CREATED_BY,
    SHIPMENT_NUM,
    RECEIPT_HEADER_ID,
    SHIP_TO_ORGANIZATION_ID,
    EXPECTED_RECEIPT_DATE,
    EMPLOYEE_ID,
    VALIDATION_FLAG
    VALUES
    (rcv_headers_interface_s.nextval , --Header_Interface_Id
    rcv_interface_groups_s.nextval, --Group_Id
    'PENDING', --Processing_Status_Code
    'INVENTORY', --Receipt_Source_Code
    'RECEIVE', --Transaction_Type
    'DELIVER', --Auto_Transact_Code
    SYSDATE, --Last_Update_Date
    -1, --Last_Updated_By
    -1, --Last_Update_Login
    SYSDATE, --Creation_Date
    -1, --Created_By
    'ICR-001', --SHIPMENT_NUM
    21073573, --RECEIPT_HEADER_ID
    2266, -- SHIP_TO_ORGANIZATION_ID
    SYSDATE+1, --Expected_Receipt_Date
    5543, --Employee_Id,
    'Y' --Validation_Flag
    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,
    CATEGORY_ID,
    QUANTITY,
    UNIT_OF_MEASURE,
    ITEM_ID,
    AUTO_TRANSACT_CODE,
    SHIPMENT_HEADER_ID,
    SHIPMENT_LINE_ID,
    SHIP_TO_LOCATION_ID,
    RECEIPT_SOURCE_CODE,
    TO_ORGANIZATION_ID,
    DESTINATION_TYPE_CODE,
    DELIVER_TO_PERSON_ID,
    LOCATION_ID,
    DELIVER_TO_LOCATION_ID,
    SUBINVENTORY,
    LOCATOR_ID,
    HEADER_INTERFACE_ID,
    VALIDATION_FLAG,
    SHIPPED_DATE
    --SELECT
    VALUES
    rcv_transactions_interface_s.nextval, --Interface_Transaction_id
    rcv_interface_groups_s.currval, --Group_id
    SYSDATE, --Last_update_date
    -1, --Last_updated_by
    SYSDATE, --Creation_date
    -1, --Created_by
    -1, --Last_update_login
    'RECEIVE', --TRANSACTION_TYPE_RECEIVE
    SYSDATE, --TRANSACTION_DATE
    'PENDING', --PROCESSING_STATUS_CODE
    'BATCH', --PROCESSING_MODE_CODE
    'PENDING', --TRANSACTION_STATUS_CODE
    203, -- CATEGORY_ID
    20, --QUANTITY
    'EACH', --UNIT_OF_MEASURE
    4379131, --ITEM_ID
    'DELIVER', --AUTO_TRANSACT_CODE
    21073573, --SHIPMENT_HEADER_ID
    16566939, --SHIPMENT_LINE_ID
    101629781, --SHIP_TO_LOCATION_ID
    'INVENTORY', --RECEIPT_SOURCE_CODE
    2266, --TO_ORGANIZATION_ID
    'INVENTORY', --DESTINATION_TYPE_CODE
    13706, --DELIVER_TO_PERSON_ID
    101629781, --LOCATION_ID
    101629781, --DELIVER_TO_LOCATION_ID
    'FG', --SUBINVENTORY 
    46259, --LOCATOR_ID  
    rcv_headers_interface_s.currval, --Header_interface_id
    'Y', --VALIDATION_FLAG 
    SYSDATE
    Thank you,
    Genoo
    Edited by: Geno on May 25, 2013 4:54 AM

    Any suggestion/advise please!
    Thanks,
    Genoo

  • Open Interface Table Sequence

    Hi,
    We are attempting to build a custom interface for receiving transactions and have the following requirements:
    We want to create receiving transaction for the PO line
    We want to create a lot for the items in the inventory
    We have seen that there is the receiving open interface and also the mtl transaction interface that can probably do this together but want to know the tables to populate. Specifically, is there a link between he receiving transaction's line number and the lot that is created for it ?
    Regards.

    As Sam said, there is no API for the table - you need to SQL*Loader or inserts (via SQL script or PL/SQL or whatever).
    We have a number of processes that generate transactions for Projects where we use Stored PL/SQL based concurrent programs which insert records into PA_TRANSACTION_INTERFACE_ALL.

  • Open Interface Table for iExpense Template

    Where can I find the table name of the Open Interface for uploading master records of GL, AR, AP, FA? I can only find the name to upload journal entries and AR, AP Invoice. Can someone advise me where can I find the open interface tables list for master records?
    In particular, I would like to upload the Expense Item Template for Internet Expense of AP. I want to update the items by SQL Loader. (not the entries or transactions but master records of existing item code in the Expense template)
    Thank you very much.

    Hi;
    Please review:
    Oracle Trading Community Architecture User Guide
    Regard
    Helios

  • 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

  • Modifying Unit Price of Parchase Order Line by the Receiving Open Interface

    I’m using the” Receiving open Interface” to make receptions of standard purchase orders line by interface (RCV_TRANSACTIONS_INTERFACE) and what I need is to change the unit price of the item in the line of Purchase Order,
    the idea is that it takes the value that I’m populating by the interface table “RCV_TRANSACTIONS_INTERFACE” and not the value that is in the Standard purchase Order line (unit_price)
    It´s possible to do that in this way?? How can I do that??
    Message was edited by:
    alejandrojrc

    Any sugestion??

  • Use of open interface tables in R12

    Hello,
    Can someone tell me the status of using open interface tables in release 12. Is this still a supported mechanism for importing data into the product, or must you use a PL/SQL/Java API, XML gateway etc?
    iREP for 11.5.10 lists these open interface tables, but they are missing from the embedded iREP in R12. However, looking in the database for the RA_CUSTOMERS_INTERFACE_ALL shows that the tables exists. Is it supported to still use open interface tables, or are they just there for legacy upgrade purposes? If it is supported, where is the documentation for these R12 open interface tables?
    I wish to integrate into various modules using Oracle Data Integrator and it seems to only have 'integration knowledge modules' to support open interface tables.
    i look forward to your response.
    Cheers,
    John

    Hi Helios,
    Thanks for your response. Two of the links do not work.
    All I really need to know for sure is that R12 supports open interface tables.
    Perhaps I didn't use the embedded R12 iRep correctly - the standard view by product family certainly didn't show any open interface table, and they did not appear in the 'interface type' drop down list. However, I notice from an example on the web that you can pivot the results by interface type. I will try that when the environment becomes available again.
    cheers,
    John

  • Reg : Open Interface Tables in Oracle Manufacturing Suite

    Hi Gurus,
    Can anybody help me providing link to get Oracle Open Interface Tables related to Manufacturing ( PO.INV,BOM,WIP,DRP/MRP ) Suire and their usage details ( i know Oracle Documentation has all these details in Open Interface documents ), i am looking for short white papers or brief notes on the Open Interface tables.
    Please help
    Regards

    Sure there is quite good documetation on Open interface tables for the Oracle Manfacturing suite.... You can explore matalink for getting the latest documentation. or you can browse http://oracletimes.blogspot.com which has the resource links for various documetation.
    Thanks
    Navin

  • CRM Open Interface Tables for Integrating with CRM

    HI all, We are evaluating integration with CRM from Telco Billing system. The TRMs of CRM talk about using some published open Interface table in CRM. I could not find any TRM or User manual where I can get this info.
    Also need to know API for CRM for intregation. PL. reply to [email protected] . Thanks - Pradip

    I think you also need V14496-01 Part 1 of 2 and V14496-01 Part 2 of 2 (English Language Extension Packs).
    Installation is explained in the Bookshelf: V29095-01

  • Bank Branch upload through open interface Table

    Hello All,
    I am currently doing Bank and Branch Conversion. My question is , is there any Open Interface Table available for bank and branch upload although there is api available .Please let know if any interface table and seeded program is available for bank and branch import.
    Version : 12.1.1
    Thank & Regards
    Aboo

    But RA_CUSTOMER_BANK_INT_ALL is not existing in the 11.5.10, 12.0 and 12.1.1.
    One more thing, I am able to create bank, branch and bank account (for customers), once the bank account is created i am able to see in the database
    select * from iby_ext_bank_accounts where EXT_BANK_ACCOUNT_ID = <ID> but when i am looking into the customer screen, i am not able to see the bank account data added to the customer account.
    But i clicked on the Add button and looked for the bank account, it is showing. So every time when i am creating bank account for a customer, once created , do i need to add in the screen?
    please provide any sugession , its confusing.
    Thanks & Regards
    Aboothahir

  • Flex field values open interface tables

    Hi ,
    Could anyone please tell me which of the Oracle Apps. Open interface tables used to upload Gl. Segment values.
    Thanks
    Jonny

    If just DFF Attribute column try direct update of attribute column.
    Otherwise perhaps the APIs have them?
    Regards,
    Gareth

  • Suppliers Open Interface Tables- DFF Value on Contacts

    Hi all... I am creating an R12 Interface using the 3 Supplier open interface tables
    AP_SUPPLIERS_INT
    AP_SUPPLIER_SITES_INT
    AP_SUP_SITE_CONTACT_INT
    Here's the thing... I need to pass a legacy id value to the Contacts in order to do updates. I was hoping to use the attribute1 field. The problem is, the site contact interface table doesn't have any attribute columns!
    Is there a way around this? Does anyone know why this table is missing columns?
    Thanks

    If just DFF Attribute column try direct update of attribute column.
    Otherwise perhaps the APIs have them?
    Regards,
    Gareth

  • AP Open Interface Tables

    Hi,
    I am in charge to write a routine to export invoices data to Oracle AP R11.0.300.
    My question is: There's a something similar to Open Interface Tables of R11i aplicable to this version?

    The are two table you must take into account: AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE. The first one is for invoice headers and the second one for invoice lines. you can get a description of the table in the ap user's guide, appendix G, Payables Open interface

Maybe you are looking for

  • An internal error has occurred

    Hi there, I get the following error in Lightroom 2, Mac OSX 10.5.4 An internal error has occurred. bad argument #3 (boolean expected, got number) When I try to export a photo, regardless of whether I click the "Export" button, use the file menu or ri

  • Advanced Software Rendering Solution For Games

    I am actually looking to talk to someone at sun but figured someone in this forum might be interested in what I have done as well. A few years back I developed a feature rich 3D api for java that is 100% software based. I realize there are some other

  • Passing data into a variable

    Hi,  All I want to do is pass numerical data into a variable, and then access it later.  Specifically, I use the Read Vector Space Position VI to find the X and Y positions of my motors. When I press a button, I want the X and Y position at that mome

  • Why can I cache method & field ids but not class?

    In my efforts to understand JNI, I've been making heavy use of http://java.sun.com/docs/books/jni/. I'm having trouble reconciling some of the points it makes with regard to caching; in particular, section 4.4.1 has an example of caching a jmethodID

  • When importing tunes from cd disc, songs from 1 albumn all appear as a differnet albumn, only happens from compilations, how can this be fixed?

    when importing tunes from cd disc, songs from 1 albumn all appear as a differnet albumn, only happens from compilations, how can this be fixed? I am using PC with windows 7. Thanks.