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.

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 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

  • RCV-856 , Receivables Open Interface Error

    I am trying to import some receipts into
    Oracle using the Oracle Open interfaces.
    I get an error RCV-856 Receivables Open Interface. SHipment lines in errors. Can you help me with that

    First of all you should check whether shipmet information matches with your PO or not.If not then correct and then run the import.
    <BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Venkatesh Potdar ([email protected]):
    I am trying to import some receipts into
    Oracle using the Oracle Open interfaces.
    I get an error RCV-856 Receivables Open Interface. SHipment lines in errors. Can you help me with that<HR></BLOCKQUOTE>
    null

  • 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

  • 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

  • APIS FOR RECEIVING OPEN INTERFACE

    Hi all,
    Can any one help me regarding APIS for receiving open interface for ASN(Advanc shipment notice)
    regards
    SREE

    For 11i, all public APIs are listed at http://irep.oracle.com
    For R12, use the Integration Responsibility responsibility to look up the APIs
    HTH
    Srini

  • 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??

  • Receiving Open Interface

    Hi.
    I am looking for helps on Receiving transaction Interface which is R11 Features.
    I have load the receipt information for item which is serial control that means I have populate the RCV_Serial_Number table.
    Please provide ur valuable inputs for the same.
    Thanks in advance
    Suresh

    Please post your query in the correct forum. In your case that happens to be Supplier Scheduling.
    all the best.
    wfs

  • Receiving Open Interface - Web Service

    Hi,
    Does anyone have a sample payload having successfully used this service.
    Bit of a huge WSDL, so looking for a good basic start point.
    Also, can this be used to process returns?
    Thanks
    David

    Hi,
    I have managed to get data into the interface table.  But I think I may be missing mandatory fields.
    I'm getting a rather unhelpful error:
    <ns1:ErrorMessage>A receiving transaction processor error occurred. Package Name: derive_vendor_rcv_line_qty. Error Code: 1. Error Text: User-Defined Exception.</ns1:ErrorMessage>
    Can you have a look at my payload and see if anything obvious is missing?  Or incorrect combination of values?
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/scm/receiving/receiptsInterface/transactions/processorServiceV2/types/" xmlns:proc="http://xmlns.oracle.com/apps/scm/receiving/receiptsInterface/transactions/processorServiceV2/">
      <soapenv:Header/>
      <soapenv:Body>
          <typ:processor>
            <!--Zero or more repetitions:-->
            <typ:Receipt>
                <proc:ASNType>STD</proc:ASNType>
                <proc:BusinessUnit>RWG (Repair &amp; Overhauls) Ltd BU</proc:BusinessUnit>
                <proc:ShipToOrganizationCode>RWG_LTD_IO</proc:ShipToOrganizationCode>
                <proc:InvoiceDate>2015-03-15T09:00:00</proc:InvoiceDate>
                <proc:InvoiceNumber>12345</proc:InvoiceNumber>
                <proc:ReceiptNumber>600000</proc:ReceiptNumber>
                <proc:VendorName>RWG_TST1</proc:VendorName>
                <proc:TransactionType>RECEIVE</proc:TransactionType>
                  <proc:StagedReceivingTransaction>
                  <proc:AutoTransactCode>DELIVER</proc:AutoTransactCode>
                  <proc:POLineId>300000001278820</proc:POLineId>
                  <proc:Quantity unitCode="Ea">5</proc:Quantity>
                  <proc:TransactionQuantity unitCode="Ea">5</proc:TransactionQuantity>
                  <proc:ReceiptSourceCode>VENDOR</proc:ReceiptSourceCode>
                  <proc:SoldtoLegalEntity>RWG Repair and Overhauls Ltd</proc:SoldtoLegalEntity>
                  <proc:TransactionType>RECEIVE</proc:TransactionType>
                  <proc:TransactionDate>2015-03-08T00:00:00.000</proc:TransactionDate>
                </proc:StagedReceivingTransaction>
            </typ:Receipt>
          </typ:processor>
      </soapenv:Body>
    </soapenv:Envelope>

  • RCV_SPLIT_LOT_SERIAL_Error when running "Receiving Open interface " program

    Hi,
    I have an item which is both serial and lot controlled. So inserted a record into mtl_serial_numbers_interface and mtl_transaction_lots_interface tables and also a record into rcv_transactions_interface table with all the necessary values like vendor_id, UOM_CODE, primary_quantity, transaction_quantity etc...
    But when i run "Receving Transaction Processor" Program am getting the error "An error occurred while trying to split lot/serial lines. Please look into inventory log for more details." with error message name as "RCV_SPLIT_LOT_SERIAL_ERROR".
    Am not sure why am getting thos error even though primary_quantity and transaction_quantity are same in the lot interface table. Can anyone please let me know the solution for this. Thanks in Advance

    HI,
    Looks Like Item Attribute 'LOT SPLIT ENABLED' is OFF. Pls tick LOT SPLIT ENABLED and then try the transaction.
    This attribute is available at Inventory tab of Org Item Set up. There is one more attribute connected to this, which will automaticaaly on/off by resetting this.
    Sunil

  • How to receive intransit shipments for inter-organization transfer with in-transit receipt routing via Receiving Open Interface

    Somebody have samples about how to fill the ROI tables only to have the receipt from inter-organization transfer with in-transit routing.
    Thanks in advance.

    Pl. visit following links.
    Oracle Apps: 11.5.10 / R12 ROI How to Receive Intransit Shipment (Inter-org transfer) for Lot / Serial Controlled Items …
    11.5.10 ROI를 통해 INTRANSIT SHIPMENT(INTER-ORG TRANSFER)를 처리하는 방법

  • Using Receiving Open Interface for DELIVER Trans after RECEIVE trans

    I am currently using the ROI to import RECEIVE transactions and create the header receipt for POs. I now want to use the ROI to import the DELIVER piece of the exisitng receipt. Has anyone done this before? I thought I could reference the transaction_id and header_interface_id of the RECEIVE transaction, but the DELIVER transaction fails to import. This is for Standard Receipts as we don't use Direct Delivery. Any help is appreciated. Thanks!

    You need to refer SHIPMENT_HEADER_ID and SHIPMENT_LINE_ID of the Receipt that you have created earlier.
    Thanks,
    PS.
    user3977462 wrote:
    I am currently using the ROI to import RECEIVE transactions and create the header receipt for POs. I now want to use the ROI to import the DELIVER piece of the exisitng receipt. Has anyone done this before? I thought I could reference the transaction_id and header_interface_id of the RECEIVE transaction, but the DELIVER transaction fails to import. This is for Standard Receipts as we don't use Direct Delivery. Any help is appreciated. Thanks!

  • 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.

  • Access interface related entries from within Receiver Communication Channel

    Hi,
    when i open the interface determintation that i created, i can see.
    Sender Details:
    Communication Component:Sys_Sample_One_D
    Interface: UserMasterQuery_Outb
    Namespace: urn:sample.com:I_Legacy_JDBC_Application
    Receiver Details:
    Communication Component:Sys_Sample_Two_D
    Interface:EmployeeEmailProcessing_Inb
    Namespace:urn:sample.com:I_Legacy_FileApplication
    Interface Mapping: UserMasterResultset_to_EmployeeEmail
    I created a Generic File Receiver communication Channel for my receiver BS: CC_FileReceiver
    In the target FileName field of the Communication channel, i would not like to hardcode any filename value, but my requirement is, the filename should be the same as the name of the Receiver Interface, that has been used in the message exchange.
    in my case, it should be something like EmployeeEmailProcessing_Inb.xml
    How can we access dynamically the interface related entries in the Communication channel, and how can we set those values in the Target Filename value of the File Receiver communication channel.
    in short, if i use the same communication channel for other scenario, the received filename should be different based on the receiver interface name that is executed.
    It would be even more better if i could access/set the receiver namespace value as part of the TargetFileName or TargetFileDirectory values.
    pls let me know how this can be possible.
    Thanks in advance,
    Madhu

    Hi Shabarish,
    thanks for your blog.
    After i saw the blog, the UDF can be created in ESR.
    DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey key = DynamicConfigurationKey.create(u201Chttp://sap.com/xi/XI/System/Fileu201D,u201CFileNameu201D);
    String MyFileName = a + "_" + b +".xml";
    conf.put(key, myFileName);
    At this point, i can see that the required value is stored in certain key in the DynamicConfiguration.
    In the blog, i could not see anything related to ID.
    My question is, what do we need to do ID,
    when we create the FileReceiver Communication Channel, in that we need to specify the mandatory field "Source File Name". what value do we need to enter here.
    Are there any additional things do we need to do in Communication Channel in ID.

Maybe you are looking for

  • Error while creating database table

    Hi I am creating a table with 2 key fields of length 255 chars each. its giving me error Key field is greater than 780. Please suggest. Regards Aditya

  • Company Code Inventory Balances by Trading Partner in Classic GL

    Is there a way to display Company Code Inventory Balances by Trading Partner with drilldown by Material Number and Quantity within the Classic Ledger in ECC 6?  Please note we do not have SAP Consolidations enabled. Thanks in advance for your respons

  • STO with delivery from multiple plant

    Hi, My client requirement is for many-to-one STO. e.g. Some material is sent from Plant A and plant C to plant B. All the plants are in same company code. 1. I have cretaed vendor VA (and assigned plant A to it in purchasing org data) and VC (and ass

  • 503 Internal Server Error

    Hi all, We r in EP7 and ECC6. EP was working fine till yesterday when I tried to open today I am getting the error as 500   Internal Server Error Failed to process request. Please contact your system administrator. It appears only for ESS. Please gim

  • Computation in Bex

    Hi friends ,                  Is this possible in Bex 3.5. I have a computation to be done = 3 +2/20/2008                                                 = 5/31/2008 and not 2/23/2008. Right now when I add this I get like this 2/23/2008 but what I wa