Receiving Transaction Interface
Hi,
I am able to do create all transactions ('RECEIVE','ACCEPT','REJECT','DELIVER') using only one group_id It means I have to submit only one Receiving Transaction Process program to process all these transactions. It is working fine when I am creating new receipt.
Can someone help me here to get all transactions in same way(Using one Receiving Transaction Process request) when we have to add the transactions to already created receipts.
Thanks In Advance.
Thanks & Regards,
Santosh
Did you figure out how to create a DELIVER transaction via ROI when the RECEIVE transaction already exists?
Similar Messages
-
Receiving Transactions interface
Some records are there in rcv_headers_interface & rcv_transactions_interface whose processing_status_code is in error or pending but still we are able to see that records are successfully processed to base tables i.e rcv_shipment_headers, rcv_shipment_lines and rcv_transactions.
Kindly let me know how can we trace the error records which are not processed to rcv_shipment_headers, rcv_shipment_lines and rcv_transactions.the below script shows all the shipment lines along with shipment_header_id that are either 'EXPECTED' or 'PARTIALLY RECEIVED' these would not have made it to the rcv_transactions table.
find these shipment lines in the interface and try to process them.
SELECT * FROM po.rcv_shipment_lines rsl
WHERE rsl.SHIPMENT_LINE_STATUS_CODE != ''FULLY RECEIVED'
if you have errored records in the rcv_transactions_interface and rcv_headers_interface that are not received.
use the below script to find
SELECT rti.SHIPMENT_LINE_ID FROM po.rcv_transactions_interface rti
MINUS
SELECT rt.shipment_line_id FROM
po.rcv_transactions rt,
po.rcv_transactions_interface rti
WHERE rt.SHIPMENT_LINE_ID(+) = rti.SHIPMENT_LINE_ID
To check errors
select * from po.po_interface_errors pie
where pie.INTERFACE_LINE_ID = 24126926 (this is interface_transaction_id from receiving_transactions_interface for the errored record or you can use batch_id/group_id which the Receiving_transaction_processor program errors out with) -
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
SureshPlease post your query in the correct forum. In your case that happens to be Supplier Scheduling.
all the best.
wfs -
Hi all
We created a purchase order and received the quantity in inventory. when I am checking the receiving transaction Table one item only received but one transaction got stck in the receiving transaction interface nowhow to clear the stucked record please provide me the solution
Thanks
RajeshHi Rajesh,
What are the other values i.e. PROCESSING_MODE_CODE and TRANSACTION_STATUS_CODE in the RCV_TRANSACTIONS_INTERFACE table.
The processing_mode_code determines whether the record was received in ONLINE, IMMEDIATE or BATCH mode. The Transaction_Status_code value will be PENDING.
Please check the above values and set the values correctly and try to re-process the record.
NOTE: Also check if there is any error for the respective record in PO_INTERFACE_ERRORS
Thanks,
Raghav -
Interface and Base tables for Receiving Transaction Processor Program
Hi Everyone,
My requirement is to move data from staging table to rcv interface tables and then run Receiving transaction processor program. How will in know what interface tables i need to insert data into? and after I run the concurrent program what are the base tables that i need to check to confirm?
Please help!
Thanks
SunnyRCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
If you have serial numbers or lot numbers for the receipts, then you need to insert into
RCV_SERIALS_INTERFACE
RCV_LOTS_INTERFACE
Once the transactions are processed, you will see records in
RCV_SHIPMENT_HEADERS
RCV_SHIPMENT_LINES
For details on the interface, check irep.oracle.com
See Import PO Receipts using custom conversion. for some scripts.
And see http://www.oracleug.com/tables/purchasing/rcvheadersinterface and http://www.oracleug.com/tables/purchasing/rcvtrnsactionsinterface for details on the tables.
Hope this answers your question,
Sandeep Gandhi -
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.1I 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..
ThanksCurrently 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. -
ESYU: R11.5.10/R12 - ROI를 이용하여 Receiving Transaction을 Correct 하는 방법1
Purpose
Oracle Inventory Management - Version: 11.5.10 to 12.0
11.5.10/11i.SCM_PF.J/11i.PRC_PF.J (and higher)에서 ROI가 지원하는 새로운
functionality를 알아본다.
-. CORRECT to DELIVER to Inventory transactions
ROI를 이용하여 Standard Purchase Order에 대한 Receiving Transaction을
Correct 할 수 있는 방법은?
Solution
아래 예제 script는 Destination Type이 'inventory'인 Purchase Order의
Devlier to Inventory Transaction을 Receiving Open Interface(ROI)를 이용하여
Correct 하는 방법을 위한 것이다.
각 script는 가장 포괄적인 사용을 위해 Lot와 Serial을 control 하는 item을 가지고
test 되었다.
각 script는 한 record 만 RCV_TRANSACTIONS_INTERFACE,
MTL_TRANSACTION_LOTS_INTERFACE, MTL_SERIAL_NUMBERS_INTERFACE
tables에 insert 할 것이다.
Following SAMPLE scripts are intended
만일 item이 단지 standard item(non lot, serial control) 이라면, record는 단지
RCV_TRANSACTIONS_INTERFACE table에만 insert 된다.
Note: 11.5.10 (or 11i.SCM_PF.J)로 upgrade 하였거나 11.5.10을 install 한 후
Enhanced Receiving Validation을 위해 Note 367396.1에 설명되어져 있는
Recommended Patches list가 적용되어져 있는지 확인해야 한다.
1) Standard Purchase Order number # 6752 생성
Inventory Item = Lot-Serial-Controlled-1
Shipment Receiving Routing = Standard Receipt
Destination Type Code = Inventory
2) Item Lot-Serial-Controlled-1은 lot/serial control item
SQL> Select mp.organization_id Org_Id, mp.organization_code Org_Code,
msi.inventory_item_id, msi.segment1, decode(to_char(msi.lot_control_code),
'2','Y',
'1','N') LOT_CONTROL,
decode(to_char(msi.serial_number_control_code),
'1','None',
'2','Predefined',
'5','Dynamic at INV receipt',
'6','Dynamic at SO issue') SERIAL_CONTROL
from mtl_system_items_b msi,mtl_parameters mp
where msi.segment1 like '&item' and msi.organization_id=mp.organization_id;
위 select 결과:
LOT_CONTROL='Y' and SERIAL_CONTROL='Dynamic at INV receipt'
inventory_item_id=169845 for item=Lot-Serial-Controlled-1
3) 수량=10에 대해 Receipt number # 7746 생성(Receive and Deliver Transactions)
item=Lot-Serial-Controlled-1
Lot Number=S246
Serial Number from SN0001 to SN0010
4) RCV_TRANSACTIONS_INTERFACE table에 insert 할 필요한 정보를 찾기 위해
아래 script를 실행한다.
SQL> Select RSH.RECEIPT_NUM ,
PH.SEGMENT1 PO_NUMBER,
RT.TRANSACTION_ID ,
RT.TRANSACTION_TYPE ,
RT.TRANSACTION_DATE ,
RT.QUANTITY ,
RT.UNIT_OF_MEASURE ,
RT.SHIPMENT_HEADER_ID ,
RT.SHIPMENT_LINE_ID ,
RT.SOURCE_DOCUMENT_CODE ,
RT.DESTINATION_TYPE_CODE ,
RT.EMPLOYEE_ID ,
RT.PARENT_TRANSACTION_ID ,
RT.PO_HEADER_ID ,
RT.PO_LINE_ID ,
PL.LINE_NUM ,
PL.ITEM_ID ,
PL.ITEM_DESCRIPTION ,
PL.UNIT_PRICE ,
RT.PO_LINE_LOCATION_ID ,
RT.PO_DISTRIBUTION_ID ,
RT.ROUTING_HEADER_ID,
RT.ROUTING_STEP_ID ,
RT.DELIVER_TO_PERSON_ID ,
RT.DELIVER_TO_LOCATION_ID ,
RT.VENDOR_ID ,
RT.VENDOR_SITE_ID ,
RT.ORGANIZATION_ID ,
RT.SUBINVENTORY ,
RT.LOCATOR_ID ,
RT.LOCATION_ID,
RSH.SHIP_TO_ORG_ID
From
RCV_TRANSACTIONS RT,
RCV_SHIPMENT_HEADERS RSH,
PO_HEADERS_ALL PH,
PO_LINES_ALL PL
Where
RSH.RECEIPT_NUM = '&RECEIPT_NUMBER'
AND PH.SEGMENT1 like '&PO_NUMBER'
AND PH.PO_HEADER_ID = PL.PO_HEADER_ID
AND RT.PO_HEADER_ID = PH.PO_HEADER_ID
AND RT.SHIPMENT_HEADER_ID = RSH.SHIPMENT_HEADER_ID;
이 script는 RECEIPT_NUM=7746, PO_NUMBER=6752에 대해 아래의 두 개
records를 return 한다.
For TRANSACTION_TYPE=RECEIVE
TRANSACTION_ID=302978
DESTINATION_TYPE_CODE=RECEIVING
PARENT_TRANSACTION_ID=-1
QUANTITY=10
UNIT_OF_MEASURE=Each
SHIPMENT_HEADER_ID=250536
SHIPMENT_LINE_ID=261490
SOURCE_DOCUMENT_CODE=PO
EMPLOYEE_ID=13706
PO_HEADER_ID=36665
PO_LINE_ID=42138
ITEM_ID=169845
PO_LINE_LOCATION_ID=76782
DELIVER_TO_PERSON_ID=null
DELIVER_TO_LOCATION_ID=null
VENDOR_ID=7927
VENDOR_SITE_ID=4724
ORG_ID=204
SUBINVENTORY=null
LOCATOR_ID=null
LOCATION_ID=204
SHIP_TO_ORG_ID=204
For TRANSACTION_TYPE=DELIVER
TRANSACTION_ID=302979
DESTINATION_TYPE_CODE=INVENTORY
QUANTITY=10
UNIT_OF_MEASURE=Each
SHIPMENT_HEADER_ID=250536
SHIPMENT_LINE_ID=261490
SOURCE_DOCUMENT_CODE=PO
EMPLOYEE_ID=13706
PARENT_TRANSACTION_ID=302978
PO_HEADER_ID=36665
PO_LINE_ID=42138
ITEM_ID=169845
PO_LINE_LOCATION_ID=76782
DELIVER_TO_PERSON_ID=13706
DELIVER_TO_LOCATION_ID=204
VENDOR_ID=7927
VENDOR_SITE_ID=4724
ORG_ID=204
SUBINVENTORY=Stores
LOCATOR_ID=null
LOCATION_ID=204
SHIP_TO_ORG_ID=204
5) Delivery transaction RCV_TRANSACTIONS.TRANSACTION_ID=302979 와
관련된 Lot/Serial 정보를 확인하기 위해 아래 script를 실행한다.ACTION_ID=302979
SQL> Select LOT_TRANSACTION_TYPE,LOT_NUM,QUANTITY
from RCV_LOT_TRANSACTIONS
where source_transaction_id=&RTtransaction_id;
SQL> Select SERIAL_TRANSACTION_TYPE,SERIAL_NUM,SHIPMENT_LINE_ID,TRANSACTION_ID,
LOT_NUM
from RCV_SERIAL_TRANSACTIONS
where source_transaction_id=&RTtransaction_id;
Script 결과로 10 records가 보여지는데 각각은 SN0001 and SN0010 사이의 serianl no를
갖는다.
예를 들어,
SERIAL_NUM=SN0005 and SERIAL_NUM=SN0006
SERIAL_TRANSACTION_TYPE=TRANSACTION
SHIPMENT_LINE_ID=261490
SOURCE_TRANSACTION_ID=302979
TRANSACTION_ID=302979
LOT_NUM=S246
CORRECT to DELIVER to INVENTORY Transaction for PURCHASE ORDER Example
1) DELIVER to INVENTORY Transaction에 대한 CORRECT record를 ROI를 이용해
insert 한다.(RCV_TRANSACTIONS.TRANSACTION_ID=302979)
Delivered 된 수량을 10에서 8로 correct, SERIAL_NUM=SN0005 and SERIAL_NUM=SN0006
와 LOT_NUM=S246를 correct 한다.
Insert:
-. RCV_TRANSACTIONS_INTERFACE, MTL_TRANSACTION_LOTS_INTERFACE,
MTL_SERIAL_NUMBERS_INTERFACE tables에 1 record 씩 insert
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
'CORRECT', --TRANSACTION_TYPE
SYSDATE, --TRANSACTION_DATE
'PENDING', --PROCESSING_STATUS_CODE
'BATCH', --PROCESSING_MODE_CODE
'PENDING', --TRANSACTION_STATUS_CODE
-2, --QUANTITY
'Each', --UNIT_OF_MEASURE
169845, --ITEM_ID
13706, --EMPLOYEE_ID
250536, --SHIPMENT_HEADER_ID
261490, --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
302979, --PARENT_TRANSACTION_ID
36665, --PO_HEADER_ID
42138, --PO_LINE_ID
76782, --PO_LINE_LOCATION_ID
78674, --PO_DISTRIBUTION_ID
'INVENTORY', --DESTINATION_TYPE_CODE
13706, --DELIVER_TO_PERSON_ID
204, --LOCATION_ID
204, --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
'S246', --LOT_NUMBER
2, --TRANSACTION_QUANTITY
2, --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
'SN0005', --FM_SERIAL_NUMBER
'SN0006', --TO_SERIAL_NUMBER
'RCV', --PRODUCT_CODE
RCV_TRANSACTIONS_INTERFACE_S.CURRVAL --PRODUCT_TRANSACTION_ID
Commit;
2) Data가 제대로 insert 되었는지 확인을 위해 아래 scripts를 실행한다.
SQL> Select * from RCV_TRANSACTIONS_INTERFACE where PO_HEADER_ID=36665
INTERFACE_TRANSACTION_ID=232850
GROUP_ID=25057
TRANSACTION_TYPE=CORRECT
QUANTITY=-2
PARENT_TRANSACTION_ID=302979
DESTINATION_TYPE_CODE=INVENTORY
RECEIPT_SOURCE_CODE=VENDOR
SOURCE_DOCUMENT_CODE=PO
SQL> Select * from MTL_TRANSACTION_LOTS_INTERFACE
where PRODUCT_TRANSACTION_ID=&interface_txn_id;
TRANSACTION_INTERFACE_ID=11300777
LOT_NUMBER=S246
TRANSACTION_QUANTITY=2
NoteIMARY_QUANTITY=2
SERIAL_TRANSACTION_TEMP_ID=11300777
NoteODUCT_TRANSACTION_ID=232850
SQL> Select * from MTL_SERIAL_NUMBERS_INTERFACE
where PRODUCT_TRANSACTION_ID=&interface_txn_id;
TRANSACTION_INTERFACE_ID=11300777
NoteODUCT_TRANSACTION_ID=232850
FM_SERIAL_NUMBER=SN0005
TO_SERIAL_NUMBER=SN0006
3) Purchasing Responsibility에서 특정 Group ID(GROUP_ID=25057)에 대해
'Receiving Transaction Processor'를 실행한다.
4) Navigate to Receiving / Receiving Transactions Summary
PO 6752에 대해 Receipt Number 7746 가 Receive, Delivery, Correct to Inventory
transactions이 발생했는지 확인한다.
SQL> Select * from RCV_TRANSACTIONS where PO_HEADER_ID=36665
It returns 3 records
For TRANSACTION_TYPE=RECEIVE
TRANSACTION_ID=302978
DESTINATION_TYPE_CODE=RECEIVING
PARENT_TRANSACTION_ID=-1
QUANTITY=10
For TRANSACTION_TYPE=DELIVER
TRANSACTION_ID=302979
DESTINATION_TYPE_CODE=INVENTORY
PARENT_TRANSACTION_ID=302978
QUANTITY=10
For TRANSACTION_TYPE=CORRECT
TRANSACTION_ID=302982
DESTINATION_TYPE_CODE=INVENTORY
PARENT_TRANSACTION_ID=302979
QUANTITY=-2
FROM_SUBINVENTORY=Stores
5) Navigate to Purchase Orders/Purchase Orders Summary
Shipment, Distribution level에서 PO Number 6752에 대해 아래 수량을
확인한다.
Quantity Received=10
Quantity Delivered=8
Reference
Note 335699.1 -
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.1Any suggestion/advise please!
Thanks,
Genoo -
Receiving transaction Process Error
Hi All,
I am getting below error while running the "Receiving Transaction Processor" concurrent program.
Error : RCV_TP_ACCT_PERIOD_CLOSED
I verified PO, Inv and GL periods and all are open.
Please help me to resolve the issue.
Regards,
Sreehari.Please see if these docs help.
Aid to Resolving ROI Errors RCV_TP_INVALID_TRX_TYPE, RCV_TP_INVALID_AUTO_TRANSACT, RCV_TP_INVALID_RECEIPT_SOURCE,RCV_TP_INVALID_SOURCE_DOC,RCV_TP_INVALID_DEST_TYPE and RCV_TP_ACCT_PERIOD_CLOSED [ID 1301013.1]
New Period, And PO Receiving Open Interface Is Failing With 'Period Not Open' [ID 406257.1]
Aid To Resolving PO_INV_NO_OPEN_PERIOD and PO_INV_MUL_PERIODS Errors [ID 1311513.1]
If you still have the same issue, I would suggest you log a SR.
Thanks,
Hussein -
Urgent Please - Receiving Transaction Processor Issue
Hi,
We are on 11.5.10. I am trying to create PO receipts using the interface program "Receiving Transaction Processor". I inserted data into the rcv_headers_interface and rcv_transactions_interface tables. As this dta is for contract labor, i am assuming that there is no need to insert data into shipment_related interface table. Following shows the insert statement I made sure that I am running the process from the correct org (the org that i used in the filed destination_oprganization field). But still the process completes normally but po_interface_errors has a record with error message as :
"RVTSH-189: Subroutine rvtshiline() returned error
Cause: Subroutine rvtshiline() returned an internal error.
Action: Note this error number and the actions you are trying to perform.
Contact your system administrator for"
The receipt gets created succesfully from the form. Anyone knows the issue? Please help me...thanks
Here are the insert statements...
--Insert data into Interface tables
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,
creation_date,
created_by,
expected_receipt_date,
comments,
validation_flag,
packing_slip,
vendor_id,
vendor_site_id,
ship_to_organization_id
VALUES (rcv_headers_interface_s.NEXTVAL,
rcv_interface_groups_s.NEXTVAL,
'PENDING',
'VENDOR',
'NEW',
'RECEIVE',
SYSDATE,
fnd_global.user_id,
SYSDATE,
fnd_global.user_id,
SYSDATE,
'test',
'Y',
'ABC',
po_headers.vendor_id,
po_headers.vendor_site_id
po_distributions.destination_organization_id
--Insert record in transactions_interface
INSERT INTO rcv_transactions_interface
(interface_transaction_id,
header_interface_id,
processing_status_code,
receipt_source_code,
transaction_date,
GROUP_ID,
last_update_date,
last_updated_by,
creation_date,
created_by,
transaction_type,
processing_mode_code,
transaction_status_code,
quantity,
unit_of_measure,
source_document_code,
po_header_id,
po_line_id,
po_line_location_id,
po_distribution_id,
to_organization_id,
comments,
interface_source_code,
employee_id,
auto_transact_code,
destination_type_code,
attribute_category,
category_id,
item_description
VALUES (rcv_transactions_interface_s.NEXTVAL,
rcv_headers_interface_s.CURRVAL,
'PENDING',
'VENDOR',
SYSDATE,
rcv_interface_groups_s.CURRVAL,
SYSDATE,
fnd_global.user_id,
SYSDATE,
fnd_global.user_id,
'RECEIVE', --'NEW',
'BATCH',
'PENDING',
2,
po_lines.unit_meas_lookup_code,
'PO',
po_headers..po_header_id,
po_lines.po_line_id,
po_line_locations.po_line_location_id,
po_distributions.po_distribution_id,
po_distributions.destination_organization_id,
'TEST',
'RCV',
1234, --employee_id
'RECEIVE',
'RECEIVING',
po_distributions.destination_organization_id,
45074,
'Standard'
);Pl see you duplicate post here - PO Receipts Interface Error!!
For urgent issues, pl open an SR with Support
Srini -
Urgent Please - Receiving Transaction Processor
Hi,
We are on 11.5.10. I am trying to create PO receipts using the interface program "Receiving Transaction Processor". I inserted data into the rcv_headers_interface and rcv_transactions_interface tables. As this dta is for contract labor, i am assuming that there is no need to insert data into shipment_related interface table. Following shows the insert statement I made sure that I am running the process from the correct org (the org that i used in the filed destination_oprganization field). But still the process completes normally but po_interface_errors has a record with error message as :
"RVTSH-189: Subroutine rvtshiline() returned error
Cause: Subroutine rvtshiline() returned an internal error.
Action: Note this error number and the actions you are trying to perform.
Contact your system administrator for"
The receipt gets created succesfully from the form. Anyone knows the issue? Please help me...thanks
Here are the insert statements...
--Insert data into Interface tables
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,
creation_date,
created_by,
expected_receipt_date,
comments,
validation_flag,
packing_slip,
vendor_id,
vendor_site_id,
ship_to_organization_id
VALUES (rcv_headers_interface_s.NEXTVAL,
rcv_interface_groups_s.NEXTVAL,
'PENDING',
'VENDOR',
'NEW',
'RECEIVE',
SYSDATE,
fnd_global.user_id,
SYSDATE,
fnd_global.user_id,
SYSDATE,
'test',
'Y',
'ABC',
po_headers.vendor_id,
po_headers.vendor_site_id
po_distributions.destination_organization_id
--Insert record in transactions_interface
INSERT INTO rcv_transactions_interface
(interface_transaction_id,
header_interface_id,
processing_status_code,
receipt_source_code,
transaction_date,
GROUP_ID,
last_update_date,
last_updated_by,
creation_date,
created_by,
transaction_type,
processing_mode_code,
transaction_status_code,
quantity,
unit_of_measure,
source_document_code,
po_header_id,
po_line_id,
po_line_location_id,
po_distribution_id,
to_organization_id,
comments,
interface_source_code,
employee_id,
auto_transact_code,
destination_type_code,
attribute_category,
category_id,
item_description
VALUES (rcv_transactions_interface_s.NEXTVAL,
rcv_headers_interface_s.CURRVAL,
'PENDING',
'VENDOR',
SYSDATE,
rcv_interface_groups_s.CURRVAL,
SYSDATE,
fnd_global.user_id,
SYSDATE,
fnd_global.user_id,
'RECEIVE', --'NEW',
'BATCH',
'PENDING',
2,
po_lines.unit_meas_lookup_code,
'PO',
po_headers..po_header_id,
po_lines.po_line_id,
po_line_locations.po_line_location_id,
po_distributions.po_distribution_id,
po_distributions.destination_organization_id,
'TEST',
'RCV',
1234, --employee_id
'RECEIVE',
'RECEIVING',
po_distributions.destination_organization_id,
45074,
'Standard'
);Pl see your triplicate post here - PO Receipts Interface Error!!
For urgent issues, pl open an SR with Support.
Srini -
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
DavidHi,
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 & 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> -
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.1I 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 -
RCV_TP_INVALID_DEST_TYPE for Receiving Transaction Processor (Receiving Transaction Processor)
Hi
I have a receipt_num 1234 that has 14 lines in it ( from 29-46) and the po_number is 454545.
When I load the receipt with the receiving trans process a recipt get created for all lines except for 1.
This particular line which is 46 is still in the rcv_transactions_interface table as an error, when Update this table and SET processing_status_code = 'PENDING',
transaction_status_code = 'PENDING' and rerun the program it's does not load the data and it complete with a warning and when I look at the po_interface_errors I see this(RCV_TP_INVALID_DEST_TYPE). and put the processing_status_code = 'COMPLETED'and transaction_status_code = 'ERROR'.
Please help please help
nullRCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
If you have serial numbers or lot numbers for the receipts, then you need to insert into
RCV_SERIALS_INTERFACE
RCV_LOTS_INTERFACE
Once the transactions are processed, you will see records in
RCV_SHIPMENT_HEADERS
RCV_SHIPMENT_LINES
For details on the interface, check irep.oracle.com
See Import PO Receipts using custom conversion. for some scripts.
And see http://www.oracleug.com/tables/purchasing/rcvheadersinterface and http://www.oracleug.com/tables/purchasing/rcvtrnsactionsinterface for details on the tables.
Hope this answers your question,
Sandeep Gandhi
Maybe you are looking for
-
How do I get my photos off my iPhone onto my MacBook Pro
I just got a Mac book pro and want to put all the photos from my iPhone 5 onto my computer. What's the easiest and fastest way to do this? If it's iCloud/photo stream please give instructions because I tried that way and only 27 of my 600 photos and
-
Cannot validate digital signature - Reader 11.0.10 on Windows 8.1
We cannot validate digital signatures in Adobe Reader 11.0.10 on a Windows 8.1 PC, but the same signatures/documents can be validated in the same version of Reader on Windows 7 Pro. Is there a known issue with signature validation in Reader XI and Wi
-
Using complex objects in PieChart
Hi there, Can someone steer me in the correct direction! I have a pie chart that is bound to my model, an AC of VO's. The VO's are news articles with date, time, id, link, reach (value of 0-30 by increments of 5). When I set the data provider to this
-
Signature for Blackberry email using Active Sync
Am I missing how I can set a signature for my emails sent from my blackberry email for work with active sync? Seems like with the Torch, I did this on the device... Please help... Solved! Go to Solution.
-
Exported photos are too saturated (reds especially)
I use iPhoto to store all my photos and to do occasional quick edits. However, exported photos look so much more saturated than they do when viewed (double-clicked) within iPhoto, especially the red colors. This is also true when the photos are viewe