STO over receipts & IS-CWM 2.00

Standard SAP does not allow over receipts to happen during Goods Receipt of a STO
Does IS-CWM 2.00 allow over receipts to happen during Goods Receipt.

Similar Messages

STO Over & Under Receipts

In our project 75% of our STO Receipts happens though EDI using WMMBID02 idoc type. There are always lots of shortages and overages happening during the Goods Receipt of the STO.
Standard SAP does not allow over receipts to happen during Goods Receipt of a STO i.e. if 100 Cases was PGIed, system will not allow to receive 120 Cases at the time of GR.
Standard SAP puts shortages that occur during Goods receipt of a STO as In-transits i.e. if 100 Cases was PGIed, and 80 Cases was received at the time of GR it will put 20 Cases into In transit bucket.
What process was followed to handle such Over receipts and Under receipts during the Goods Receipt of a STO.

Hi There.
Normally you will have to receive the estimated amount (E.G. The original 100 on the STO) and then transfer the difference (or write-on and write-off) based upon the under/over delivery
Your finance team will need to look at the movements to see if any special accounting is required (Intra/Inter company)
Unfortunately there is not a clean method for this
Regards
Steve

Issue with STO over delivery

I am sure this topic has been taken up so many times before. I have browsed through almost all of them. I still do not have a way of restricting STO over delivery! Require your expertise!!.
My requirement is that STO over deliver should not occur when using VL10* transactions alone.
We tried to export a flag (say delv_flag)from program 'RVV50R10C' to shared buffer and import the same into BADI LE_SHP_DELIVERY_PROC (DELIVERY_FINAL_CHECK) to capture error message when STO over delivery is created. The entire logic is built based on this flag alone.We are deleting the flag in V50R_MAIN of the program 'RVV50R10C'.
There are some issues with this method:
1. In some cases the delete flag statement gets executed before importing from memory and hence an STO over delivery gets created. (I don't know how or why!).
2. When VL10* transaction is executed, the delivery flag is set. At this point in time, if the user tries to delete delivery without exiting the transaction, the BADI will get triggered and error message will be displayed. This is not correct functionality since error message should be displayed only for VL10* transactions.
Suggestion:
If I change the location of exporting the flag to include 'LV50R_VIEWF43' (form delivery_create), do you suppose it would work? Would Idocs trigger this?
If anybody has worked on similar requirement please share your inputs. Urgent!!!!
PS:
I have read about delivery tolerances too "The overdelivery tolerance functionality is available only for the deliveries created with reference to sales orders and not for deliveries created with reference for PO's or STO's".

Dear Sapna Morey
I think OMCQ T.Code-- Select message M7--024 Change from Waring to error
Please try once with this it may work To control over delivery tolarency in STO
Dear Lakshmipathi G sir
i have one doubt please clear me sir please
To control Over delivery tolarance in sap standard is not available , then what is the use of the above one.
Because i have searched a lot , i didnt find the logic about this
Thanks a lot sir please help me sir
Thanks

Approval for Over receipt GR

Hi Experts,
My client want to restrict Over receipt of goods.
He want to trigger approval procedure for this scenario.
e.g PO Qty = 10, GR Qty = 11 , System should not allow user to post GR. System will trigger approval procedure & if authority approves over receipt then only post this GR.
Could you please provide some inputs for this scenario...
Thanks in advance.
Regards,
Jackie

Hi Malinath,
Over receipt tolerance in PO - is perfectly fine.
It will restrict user to post over deliveries...but the reqt is
Client want to trigger approval procedure for this scenario.
e.g PO Qty = 10, GR Qty = 11 , System should not allow user to post GR. System will trigger approval procedure & if authority approves over receipt then only post this GR.
Could you please provide some inputs for this scenario...
Thanks in advance.
jackie

Over Receipt Controls for OSP Items in 11.5.9

Is anyone aware if Over Receipt Controls is set to Warning in the organization Receiving parameters does this work for OSP items? Doesn't seem to but hopefully I am missing something.

Is anyone aware if Over Receipt Controls is set to
Warning in the organization Receiving parameters does
this work for OSP items? Doesn't seem to but
hopefully I am missing something.hai stick,
over receipt control will work provided if u have defined the over completion tolerance for the particular job
regards,
gan

STO Over / Under Delivery

Dear Expert,
I am new to SAP MM and would like to getting some advises on the mentioned situation. For plant to plant transfer, I am going to use the STO. However, if the issued quantity is different from the actual received quantity. How should I handle it?
I have found that it's advised to first GR the issued quantity and then reverse the variance to the issuing plant. If not, there will have opened quantity in the STO and the STO can't be closed. However, how can I link up my reverse document with the original STO? I am expecting to use MvT 301 to transfer back the variance to the issuing plant but there is no place to mark the relationship to the original STO. Please help! Thanks in advance.

the STO process is used to make your activities planable in advance, which is not possible with pure IM movements as they are executed only when the movement happens.
In general SAP does in the STO process not expect that something is lost in transit. (which actually is only the case in <1% of all differences that I ever analyzed in STO processes)
I actually do not really understand why one has to receive such exceptional cases with difference immediately in SAP. Since it is a process between plants (like brother and sister) it should be very easy to take the phone and call your partner to discuss what happened.
the shipping plant could cancel the goods issue and create a correct one in minutes and then you could do your receipt with right quantity.
This STO process is a real integrated process, which requires to talk to each other. Decisions should be made together, instead of working in silos and just posting the differences back to the other plant or leaving the difference alone in transit or scrapping it the receiving plant.
Especially the scrapping cares only about one part of the medal.
Example. if plant B shipped 100 but posted 200 as goods issue, and you receive 200 in plant A and scrap 100 in plant A, then you are fine in plant A. But plant B has still wrong inventory, because they never physically shipped what they posted in SAP. They may find it in the next physical count.
Movements like 551 that are created without reference cannot reference a STO. You may enter the PO number in a text field, but this is not really a reference for me.
Concentrate to do the process right, then you do not need to reference any difference posting.

Over Receipt on Production Order

We received more goods on a production order that we were supposed to. Is there a way to do a return of goods on that production order? Or do I just have to do a goods issue to fix inventory and leave the variance as is?

hI Jim
first you have to seen whether the goods revived for prodiction have been used in production ie please check if they still hold the same denomination stature as comapred with earlier if yes then u can use gooods issue or even inventory transfer as per your system.
if the goods are used in production then as said by gordon u would require a disaambly bom
Hope it would help u
Regards,
Manish

STO - Not deleted from Product View ATP Column

Hi,
We have a situation where the old and Processed STO ( Goods Receipt done and Final Delivery Flag set) is still displayed Product View(APO) in the ATP column.
When we delete this item it gets CIFed again over from ECC. This happens only with the orders where partial qty is delivered.
What do we do to get this deleted permanently?
Regards
A
Edited by: Asokan Tharmalingam on Jul 30, 2010 5:08 AM

Hi A,
Delivery completion flag is to be checked at item level also for the PO. Please get help from R/3 side. The STO cannot be removed from APO unless it is closed in R/3.
regards,
B

Create Delivery against STO define overdelivery tolerance

Hello,
Can anyone please suggest if there is a way to create Delivery More Than Open STO Quantity?
My scenario goes like this lets say I have STO with Quantity 100 KG. I am creating delivery with 60 Quantity and system is allowing me to create delivery.
now I have 40 KG open so system is still allowing create delivery and Its allowing me to create of any amount although I dont have any Overdelivery Tolerance set up in STO or in Material Master.
but If I try to create delivery again its says its not able to find the STO and hence does not create delivery so my requirement is to define over delivery tolerance and allow SAP to create delivery on STO over STO Quantity.
I am using BAPI_OUTB_DELIVERY_CREATE_STO to create delivery.
putting my requirement as example
STO- 100 KG
first delivery - 40 KG - as of now sap create delivery
second delivery - 50 kg - here as well
third delivery - 45 Kg - here as well
fourth delivery - 50 kg - does not create
I know this seems bit confusing I tried to explain Please let me know if need more details.
Thanks
Shail

Thanks Jurgen,
One of my friend suggested me to try the copy control setting against delivery and changing the Quantity is calculated positively, negatively or not at all to zero which explains
Indicates whether, during copying, the quantity or value in the target document has a negative effect, positive effect, or no effect at all on the quantity still to be completed in the source document."
I tried using this but still not working.
I guess this may work if I create delivery from SO and not STO.
for now I have requested User to Bump up the STO Quantity.
but I want to find out which field and where the system check and determine if STO is fully delivered or does not have open quantity
Thanks
Shail

Excluding certain supplies/receipts in SNP

Hi,
we have a requirement wherein we want to exclude certain types of supplies. e.g STO's from ECC system to be added to the TLB confirmed receipts in SNP. To be clear the TLB confirmed details show two supply docuements. with different sources of supply. but we want to exclude one of them viz. a returns STO creating receipts at the location. both the supply documents have exactly the same attributes and hence find no basis to exclude from CFM1. we tried excluding from purchase info records.. sources of supply tab and tinkered around it. but the requirement seems to be not addressed with this exclusions in vendors and supplying plants.
Could someone help me resolve this.
Regards,
Loknath

Hi,
To my knowledge, you cannot do that directly in integration model. See if you can use a user exit like APOCF019 or a custom user exit to filter out these supplies/receipts.
Check this [link|http://help.sap.com/saphelp_scm50/helpdata/en/8f/987337e68ae526e10000009b38f889/content.htm] for more standard user exits.

How does Over received Qtys against a PO is handled in ORMS ?

Hi all ,
while we do receiving in ORWMS or ORSIM if we happen to do over receiving how does the same information is passed back to ORMS against an Purchase order.
regards,
Deepak

Deepak
We use third-party store and warehouse inventory management, but we do then interface the received qty's back into RMS using the RMSSUB_RECEIPT.CONSUME package.
There are no in-built limitations to over-receiving in RMS. You will simply end up with an order line (ORDLOC) with qty received > qty ordered. Similarly, if you processed an ASN in advance of receiving (where ASN did not indicate an over-shipment), this will be displayed as received qty > expected qty on SHIPSKU.
The stock ledger will reflect the actual received qty. There are no special postings as there are in relation to Transfers where there is special logic to handle over/under receipts, controlled by system options.
I do not know if you can configure controls on whether or not to allow over-receipts within ORSIM or ORWMS.
Alan

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)

Trading partner need to post in IR

Trading Ptr on STO Invoice Receipt entries. Trading Partner flows through to all line items on FI doc for Goods Receipts, but not for Invoice Receipts on STO PO''s. On Invoice Receipts, Trading Ptr is only posted on the Intraco A/P line item. Can we get Trading Ptr to post on ALL line items in the I/R doc as well?

go to your invoice in VF03
then go via the menu: environment - account determination analysis - revenue accounts
here you see per valid condition how the acccount is picked up.
kr
Nico

Trouble with executing RTP using fnd_transaction.synchronous

Background: We have an existing PL/SQL program executed via a concurrent program that processes RECEIVE type receipts. This program inserts RECEIVE type records into the RCV_TRANSACTIONS_INTERFACE table for further processing by executing the Receiving Transactions Processor in a subsequent concurrent program stage. All receive receipts are currently processed in batch mode with the RTP.
We are now trying to implement three way match. Part of the process involves handling RETURN TO VENDOR and CORRECT type receipts. Unfortunately, according to 360340.1 on Oracle Support, return to vendor is a two step process (at least for us). I've noted that simultaneously inserting the RETURN TO RECEIVING and RETURN TO VENDOR receipt records into the RCV_TRANSACTIONS_INTERFACE table and having the RTP process both these records in one fell swoop does NOT work. It errors out and I get the following error in PO_INTERFACE_ERRORS:
The Quantity entered for receipt is greater than the available Quantity. The sum of quantity to be received and already received, 10, is greater than the sum of ordered quantity and over receipt tolerance, 0.
Interestingly, a return to vendor receipt works if I insert the RETURN TO RECEIVING record first, then run the RTP, then insert the RETURN TO VENDOR record, then run the RTP. Thus, I need separate executions of the RTP in order for this to work. Can someone tell me if I can do this with one execution of the RTP batch mode? Would I have something wrong in the RETURN TO RECEIVING and RETURN TO VENDOR records in the RCV_TRANSACTIONS_INTERFACE table? I know this has to be a two step return process (RETURN TO RECEIVING and RETURN TO VENDOR), but I'm wondering why I can't just execute the RTP once - why do I have to execute it twice?
If I have to execute the RTP twice, then it leads me to the question addressed in the subject of this message. My current design is I would like to execute the RTP via fnd_transaction.synchronous after each record is inserted into the RCV_TRANACTIONS_INTERFACE table. I've tried executing the RTP via fnd_transaction.synchronous after the insert of RETURN TO RECEIVING and RETURN TO VENDOR, but it does not work for me. In fact, I've tried executing the RTP via fnd_transaction.synchronous after the insert of a receive transaction (RECEIVE) just for testing - and it does not work. I've turned on debugging and I see an ORA-1403 error in the fnd_concurrent_debug_info table:
ORA-01403: no data found
I've used some info from the following page:
http://karthikrajasekaran.blogspot.com/2009/12/receiving-transaction-processor.html
I've set the apps context, too... So I'm not sure what's going on. Does anyone have an idea?

Check the below query, I think this might help.
select okhb.contract_number contract_number
,msi.segment1 line_item
,msi.description line_item_description
,msi_sub.segment1 sub_line_item
,msi_sub.description sub_line_item_description
from
okc_k_headers_b okhb
,okc_k_lines_b oklb
,okc_k_items oki
,mtl_system_items_b msi
,okc_k_lines_b sub_ln
,okc_k_items sub_items
,csi_item_instances cii
,mtl_system_items_b msi_sub
where
okhb.contract_number = 'NK20269112'
and okhb.contract_number_modifier = '1 yr'
and okhb.id = oklb.chr_id
and oklb.id = oki.cle_id
and oki.jtot_object1_code = 'OKX_SERVICE'
and oki.object1_id1 = msi.inventory_item_id
and oki.object1_id2 = msi.organization_id
and oklb.id = sub_ln.cle_id
and sub_ln.lse_id IN (7, 8, 9, 10, 11, 18, 25, 35)
and sub_ln.id = sub_items.cle_id
and sub_items.jtot_object1_code = 'OKX_CUSTPROD'
and sub_items.object1_id1 = cii.instance_id
and sub_items.object1_id2 = '#'
and cii.inventory_item_id = msi_sub.inventory_item_id
and cii.inv_master_organization_id = msi_sub.organization_id

PO number for B2B Sales Orders.

Hello,
B2B orders lines are in the status "PO Created".
But while checking the PO number in the Supply TAB, PO number is blank and greyed out.
Intrestingly we can see the PO line number.
Any pointers?
Thanks
Radha.

Hi Luko,
Thanks for the notes.
Note 746241.1 says the following
When performing a back to back order for a lot controlled item and then an over-receipt of the original booked item within the tolerances, the status of the Sales Order is not changing from 'PO-Created' to 'Awaiting Shipping'. Reservations are not being transferred from PO to Sales order.
It works fine if the quantity received is equal to the quantity ordered.
we have receiving equal quantity as ordered.
Please suggest.
Thanks
Radha.

STO over receipts & IS-CWM 2.00

Similar Messages

Maybe you are looking for