Good Receipt with reference to delivery or stock transfer order
We have a stock transfer order between two plant. Requirement is as under.
Steps - Supplying plant is creating stock transfer order, doing delivery with reference to STO by VL10B.
Receiving plant is doing Good Reference with reference to delivery or STO t code MIGO.
Now the requirement is if A Plant is supplying 100 nos, at the receiving plant it should not allow less then 100 nos. it should give error that qty is not match with delivering qty.
Thanks in advance
Samir Bhatt
HI,
You mean to say that STO quantity must be equal to GR quantity or else system should throw an error
After STO and delivery PGI is done.
Then GR is made with refernce to STO.
Regards
KK
Similar Messages
-
Good receipt with reference to outbound delivery document
Hello Gurus,
Could someone please help with the following scenario?
Article 1234 has base unit of measure pc, altenative measure box, 1 box = 12 PC
In the purchase order (stock transfer order from one site to another site) 4 box of article 1234 is ordered. Outbound delivery created with reference to the above purchase order (stock transfer order) has quantity of 4 boxes (this is copied from PO). And then an transfer order is created with reference to the above outbound delivery and quantity requested is 4 boxes (copied from outbound delivery), but in the transfer order confirmation the confirmed quantity is 14 pcs (this is now confirmed with base unit of measure). And now if we check the outbound delivery doc, the confirm quantity is 14 pcs (1,167 box )
But when creating good receipt with reference to the outbound delivery document, the quantity confirmed is now 14.004 pcs (this is calculated with unit of measure conversion table, i guess). But actually good receipt quantity should be 14 pcs instead of 14,004 Pcs!
What can we do in order to have 14 pc in good receipt?
Thanks in advance for your great help.
Br, AilleenHi,
Thanks a lot for both of your answers. But if is there a way to receive 14 pcs instead of 14.004 pc although the system did the right calculation according to the conversion rules!
But in this case the supplying plant has issued 14 pcs but receiving plant has received 14,004 pcs and now there is discrepancy! Is there some enhancement or user exit could fix the situation or do I have to change the coding in order to solve this problem!
Thanks again for you helpful advice!
Br, Ailleen -
Problem on creation of Outbond Delivery for Stock Transfer Order
Hi all,
We have problem on the creation of Outbond delivery for stock transfer order because the system doesn't group in a unique delivery for different items of a STO order.
We used VL10B or VL10D but the behaviour is the same. Even if we have to handle few items of the Stock Transfer order already scheduled, the scope is to create a delivery which group everything while the system split in several delivery notes.
Could you advice me the way to set in customizing , master data I don't know where else , the rules in order to avoid to split deliveries for STO.
Secondly if we have already created a delivery note is it possible to add a further purchase order item as in sales order processing?
Thank you for any suggestion you will give
AndreaDear Kripa,
the first point has been solved. We have checked a SAP Note 386340 which is appropriate to this case.
The second point, the one referred to the additional items to an existing delivery note, is not yet closed and I would like to know further advices from you and the other guys connected to the forum in order to help us to solve the problem.
Thanks for your help
Andrea -
Create Goods Receipt with an Inbound Delivery
Hi,
Can you anybody help me, how to create a Goods Receipt with correspond to Inbound Delivery.
Which FM or BAPI avaliable for this. Anybody did it before please pass to me with details?
Thanks in Advance
Cino C B
Edited by: Cili on Feb 11, 2008 8:19 PMCheck BAPI_GOODSMVT_CREATE
Look at the documentation if you want to make a goods issue or a good receipt for purchase order or production order, etc.
Inbound delivery only means is going to enter the plant (ie. mvt 101) -
Open Qty is not copied in Delivery for Stock Transfer Order
Hi,
In the Stock Transfer Order process, Once the STO Order is created, I am creating delivery in the transaction VL10B or VL10G.
When I am clicking the background button Delivery gets generated. Then when i am going in the transaction VL02N and increasing the delivery Quantity which is more than STO order quantity, the system is accepting it. But i want the system to throw an error message if the delivery quantity is more than the order qauntity. For this I have made the following settings.
In the Transaction Code 0VLP, i have selected B in Check Over Delivery field. But still it is not throwing an error.
The reason for the same may be, the system is not copying the Open Delivery Qty from the STO Order (Which normally happens in Sale Order to Delivery process, bcos of Copy Control). This field has 0 value. So the system is not able check for over delivery.
If I get this value in the delivery then it should be working fine and the sytem will throw an error for over delivery.
Can you please suggest me a way to get this open qty value in delivery for STO order or suggest me some other option to check for over delivery in STO.
Regards
VijayDear Friend,
If I can understand you clearly.
to achieve your task the best way you can sit with your abaper and configure a routine and assign the same to T-code OVLK delivery type customizing :
In the Item requirement : Generally it is 202
reward points if helpful,
regards,
Amlan -
MIGO PROBLEM in the Good Receipt with reference to purchase order
Hello Everybody.
i m getting one problem with reference to MIGO tcode.
Might be anyone notice or not but i want to share with you.
in MIGO selected goods receipt then beside it ask for the different actions.
I use the purchase order no.
suppose i given po no 1
enter
now it will display the details of that po number (1) but at the same time po number field is again in the input mode and you can give more po number .
suppose now i have given po no 2.
enter
Then in same gr we will be having the item details of both po number( 1 & 2) .
This is my problem .I want to make restriction that in single gr it should take only one po number not more than that ,after giving one po ,it should make that field in display mode.
How to do that please guide me .
I will be grateful to you.
Thanks a lotYou can use a field exit on any field that gets filled when the first PO is entered
check that field (Something like challan Number , Delivery date)
if is if filled use the "screen" Table to make the PO Number field Display only . -
Good receipt with serial number already on stock W
dear all,
I have this issue:
Company "A" sent a material (with serial number) to another company "B" in SAP (Intercompany flow) with customer consignment stock (W).
Company B has to post the good receipt for that material but the system shows the error message that the serial number can't be used.
My question is:
is it possible to post the good receipt for a serial number already used in another plant, special stock W?
Thank you
EnricoSorry jurgen:
Serial number 1000152198 cannot be used here
System status ESTO is active (EQU 1000152198)
Thank you
Regards
Enrico -
Excise duty not determined in goods receipt with reference to PO.
Dear All,
I am implementing Condition based CIN. I have created PO and maintained all excise duties in XK11 transactions. Excise duty has determined in PO. But When I am creating MIGO with reference to PO the excise duty is not copied from Purchase order.
Please suggest.
Thanks & RegardsDear All,
If you have any idea, Please let me know.
Thanks & Regards -
Goods receipt with reference to Purchase Order
the requirment is that we should be able to restrict the one Goods receipt posting for one Purchase order. The standard system is supporting processing of multiple P.O's of different vendors in on GR.
could anybody suggest to configure the functionality
regardsHi,
There is no standard option available and I don't think that there is any feasible way of stopping this without the use of a user exit (as already suggested).
But even the user exit option would be complex because it would have to block off the PO number field after enter (or any other key) was pressed.
It would also have to stop the use of multiple entries via the "find" option.
If you have a valid reason for doing this, have you thought of trying to get your users to do as they are told instead of changing the system?
Why is it important to have one PO per GR ?
Steve B -
Over Delivery in Stock transfer Order
We have maintained Over delivery tolerance in the Stock Transport
Order,but during Goods Issue (VL10D,VL02N -641 mvt ) system does not
check the order quantity + overdelivery but allows to create delivery
for more than the overdelivery tolerance.
Pl.suggest how to restrict.
Thanks in advanceHi,
For goods issue u need to maintain tolarences for item category group or in customer master
what we maintain in po is for GR
regards
pradeep -
Problem in posting the goods receipt with reference to the inbound delivery
Hi All,
Below is the explanation of the scenario:
1. Materials are purchased (PO created in CAS as order unit) and inbound delivery document is created in cases as well.
2. When the TO is created for put away (we are performing put away using the hand held devices) the line item is split resulting in new line item number created
3. When the TO is confirmed the del quantity on the split line item is zeroing out and as a result the system is treating it as a service item with zero del quantity and is stopping from performing the GR with respect to the inbound delivery document
And also the inbound delivery is disappearing from the confirmation tab on the PO)
This is happening only with the materials which have an alternate unit set up in the material master (in this scenario CAS is the order unit and JAR is the base unit of measure)
Can some one help fix this?Hi,
There is no standard option available and I don't think that there is any feasible way of stopping this without the use of a user exit (as already suggested).
But even the user exit option would be complex because it would have to block off the PO number field after enter (or any other key) was pressed.
It would also have to stop the use of multiple entries via the "find" option.
If you have a valid reason for doing this, have you thought of trying to get your users to do as they are told instead of changing the system?
Why is it important to have one PO per GR ?
Steve B -
Creating goods receipt with refernce to PO number using BAPI_GOODSMVT_CREAT
Hi Gurus,
I have a requirment where in, I need to create a goods receipt with reference to a PO number which has been created by BAPI_PO_CREATE1, using another BAPI BAPI_GOODSMVT_CREATE. How can I do this? what are all the values that I need to fill in GOODSMVT Create BAPI.
Please help its very urgent... Need to submit by EOD.
Thanks,
Sumahi
hope this code will help you,.
Reward if help.
REPORT ZRICH_0001 .
Structures for BAPI
DATA: GM_HEADER TYPE BAPI2017_GM_HEAD_01.
DATA: GM_CODE TYPE BAPI2017_GM_CODE.
DATA: GM_HEADRET TYPE BAPI2017_GM_HEAD_RET.
DATA: GM_ITEM TYPE TABLE OF
BAPI2017_GM_ITEM_CREATE WITH HEADER LINE.
DATA: GM_RETURN TYPE BAPIRET2 OCCURS 0 WITH HEADER LINE.
DATA: GM_RETMTD TYPE BAPI2017_GM_HEAD_RET-MAT_DOC.
CLEAR: GM_RETURN, GM_RETMTD. REFRESH GM_RETURN.
Setup BAPI header data.
GM_HEADER-PSTNG_DATE = SY-DATUM.
GM_HEADER-DOC_DATE = SY-DATUM.
GM_CODE-GM_CODE = '04'. " MB1A
Write 971 movement to table
CLEAR GM_ITEM.
MOVE '412' TO GM_ITEM-MOVE_TYPE .
MOVE 'Q' TO GM_ITEM-SPEC_STOCK.
MOVE '3800533484' TO GM_ITEM-MATERIAL.
MOVE '1' TO GM_ITEM-ENTRY_QNT.
*MOVE 'PC' TO GM_ITEM-ENTRY_UOM.
MOVE '1060' TO GM_ITEM-PLANT.
MOVE '0007' TO GM_ITEM-STGE_LOC.
*MOVE '0901' TO GM_ITEM-MOVE_REAS.
MOVE 'P203601001' TO GM_ITEM-WBS_ELEM.
MOVE 'P203601001' TO GM_ITEM-VAL_WBS_ELEM.
APPEND GM_ITEM.
Call goods movement BAPI
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
EXPORTING
GOODSMVT_HEADER = GM_HEADER
GOODSMVT_CODE = GM_CODE
IMPORTING
GOODSMVT_HEADRET = GM_HEADRET
MATERIALDOCUMENT = GM_RETMTD
TABLES
GOODSMVT_ITEM = GM_ITEM
RETURN = GM_RETURN.
IF NOT GM_RETMTD IS INITIAL.
COMMIT WORK AND WAIT.
CALL FUNCTION 'DEQUEUE_ALL'.
ELSE.
COMMIT WORK AND WAIT.
CALL FUNCTION 'DEQUEUE_ALL'.
ENDIF.
WRITE:/ GM_RETMTD.
LOOP AT GM_RETURN.
WRITE:/ GM_RETURN.
ENDLOOP.
check the BAPI_GOODSMVT_CREATE.
Functionality
You can use this method to create a material document for a goods movement.
You can only create one material document each time you call up the method.
You can use a simulation function before posting the goods movement to check how the data is updated in the database. The standard system is configured so that the goods movement is posted immediately without simulating beforehand.
Ensure that you transfer the data in the same way as it is run in the database, for example,
Material number 18-figure with leading zeros
Batches with uppercase letters
Note that for all transactions/events listed below, the posting date is entered in the header data of the material document. In the BAPI2017_GM_HEAD_01 interface, fill the PSTNG_DATE (import structure GOODSMVT_HEADER) field.
Notes
Authorization check check
In the MM Inventory Management component, the method does not execute any authorization checks.
Note that during a posting of a goods movement, depending on the business transaction of the system, authorization objects of other applications can also be checked.
Transfer
The following information about the material document that is to be created is transferred to the method:
a structure with header data
a structure with the code for the movement
a table with the item data
a table with the serial numbers
The posting is carried out in the SAP R/3 via the MB_CREATE_GOODS_MOVEMENT function module.
Confirmations
Messages are returned in the Return parameter. The parameter documentation shows the return codes and their meanings.
Further Information
The method can only carry out your function if no error messages were generated in the Return table. This is the case if the header data and all the items were processed successfully.
Transaction control is not implemented. The calling program therefore has to execute the Commit Work itself after this method has been successfully called (in other words, if no errors were reported in the Return parameter).
Which fields have to be filled during the various transactions/ events?
The following sample scenarios demonstrate which fields have to be filled for which business transactions/events (code).
There are the following types of transactions/events:
1. GM_Code 01: Goods receipt for purchase order
2. GM_Code 02: Goods receipt for production order
3. GM_Code 03: Goods issue
4. GM_Code 04: Transfer posting
5. GM_Code 05: Other goods receipts
6. GM_Code 06: Reversal of goods movements
7. GM_Code 07: Subsequent adjustment to a subcontract order
Entering the movement indicator
Depending on the transaction, you must enter the following in the movement indicator:
GM_Code 01 (Goods receipt for purchase order): B
GM_Code 02 (Goods receipt for production order): F
For all other transactions, you leave the field blank.
For 1: GM_Code 01: Goods receipt for purchase order
Purchase order known
The following fields have to be filled:
Purchase order
Purchase order item
Movement type
Movement indicator
Quantity in unit of entry
ISO code unit of measurement for unit of entry or
quantity proposal
The following fields may have to be filled in some cases (incomplete listing):
Shelf life expiration date (if it has been configured like this in the system)
Reason for movement (if it has been configured like this in the system)
Batch (if the material is handled in batches and batch numbers are not assigned automatically)
Storage location (if a storage location has not been specified in the purchase order item)
The following fields can be filled (incomplete listing):
Stock type
Item text
Unloading point
Delivery completed indicator
You cannot fill the following fields (incomplete listing):
Account assignment fields (account assignment is adopted from the purchase order)
Reservation
Receiving/issuing material
Receiving/issuing plant
Receiving/issuing storage location
In the case of a purchase order item with the "subcontracting" item category, only the GR item in the interface is to be transferred. The system automatically determines GI items.
Purchase order unknown: Shipping notification known
The following fields have to be filled:
Delivery
Delivery item
Movement type
Other fields, such as those under "Purchase order known". The system determines the relevant purchase order item via the delivery/delivery item.
Purchase order unknown: Purchase order should be created automatically
The following fields have to be filled:
Material number
Plant
Storage location
Vendor
Movement type
Movement indicator
Quantity in unit of entry
ISO code unit of measurement for unit of entry
The following fields may have to be filled in some cases (incomplete listing):
Shelf life expiration date (if it has been configured like this in the system)
Reason for movement (if it has been configured like this in the system)
Batch (if the material is handled in batches and batches are not assigned automatically)
The following fields can be filled (incomplete listing):
Stock type
Item text
Unloading point
You cannot fill the following fields (incomplete listing):
Account assignment fields (automatic creation of purchase order items with account assignment is not supported)
Reservation
Receiving/issuing material
Receiving/issuing plant
Receiving/issuing storage location
Purchase order unknown: A purchase order should not be created
The following fields have to be filled:
Material number
Plant
Storage location
Vendor
Movement type
Movement indicator
Quantity in unit of entry
ISO code unit of measurement for unit of entry
The following fields may have to be filled in some cases (incomplete listing):
Shelf life expiration date (if it has been configured like this)
Reason for movement (if it has been configured like this)
Batch (if the material is handled in batches and automatic assignment of batch numbers is not set)
The following fields can be filled (incomplete listing):
Special stock indicator
Item text
Unloading point
Goods recipient
The following fields cannot be filled (incomplete listing):
Account assignment fields (automatic creation of purchase order items with account assignment is not supported)
Reservation
Receiving/issuing material
Receiving/issuing plant
Receiving/issuing storage location
Receiving/issuing batch
The input combinations listed above for the GM_CODE 01 can be combined within an input table so that they can be posted in a material document. Items can also be posted for different purchase orders, provided that all the purchase orders refer to the same vendor.
Transfer of subcontracting components
During the posting of the ordered material of a subcontract order with movement type 101, for the transfer of the subcontracting components, the filled unique identification of the document line (LINE_ID) is also required.
More information on LINE_ID and PARENT_ID
The following fields have to be filled for the components:
Unique identification of the document line
Identification of the immediately superior line
Material number
Plant
Storage location
Quantity in unit of entry
The following fields can be filled for the components:
All other fields in the method that are included in this list.
The following fields cannot be filled for the components:
All fields that are not included in the list above. The movement indicator must be initial.
Additional fields in goods-receipt-based invoice verification
When you post a goods receipt to purchase order with movement type 102, an issue with reference to a previously posted goods issue, the following fields must also be transferred:
REF_DOC_IT (LFPOS): Item of a reference document
REF_DOC (LFBNR): Document number of a reference document
REF_DOC_YR (LFBJA): Fiscal year of a reference document
Only when you transfer these fields is it guaranteed that the reference to the original goods movement stay the same.
For 2 GM_Code 02: Goods receipt for production order
The following fields have to be filled:
Order
Movement type
Movement indicator
Quantity in unit of entry
ISO code unit of measurement for unit of entry or
quantity proposal
The following fields may have to be filled in some cases (incomplete listing):
Shelf life expiration date (if the system has been configured like this)
Reason for movement (if the system has been configured like this)
Batch (if the material is handled in batches and automatic batch number assignment is not set)
Storage location (if storage location has not been specified in the order)
The following fields can be filled (incomplete listing):
Order item (co-product)
Stock type
Item text
Unloading point
"Delivery completed" indicator
The following fields cannot be filled (incomplete listing):
Account assignment fields (the account assignments are adopted from the purchase order)
Reservation
Receiving/issuing material
Receiving/issuing plant
Receiving/issuing storage location
Receiving/issuing batch
For 3 GM_Code 03: Goods issue
Goods issue without reference to a reservation
The following fields have to be filled:
Material number
Plant
Storage location
Movement type
Movement indicator
Quantity in unit of entry
ISO code unit of measurement for unit of entry
The following fields may have to be filled in some cases (incomplete listing):
Special stock (e.g. sales order, project, vendor etc.)
Shelf life expiration date (if the system is configured like this)
Reason for movement (if the system has been configured like this)
Batch (if the material is handled in batches and automatic batch number assignment is not set)
Account assignment fields
The following fields can be filled (incomplete listing):
Special stock indicator
Item text
Unloading point
Goods recipient
The following fields cannot be filled (incomplete listing):
Reservation
Receiving/issuing material
Receiving/issuing plant
Receiving/issuing storage location
Receiving/issuing batch
Goods issue with reference to a reservation
The following fields have to be filled:
Reservation number
Reservation item
Record type of the reservation
Movement indicator
Quantity in unit of entry
ISO code unit of measurement for unit of entry
The following fields may have to be filled in some cases (incomplete listing):
Shelf life expiration date (if this has been configured in the system)
Reason for movement (if this has been configured in the system)
Batch (if the material is handled in batches and automatic batch number assignment is not set)
Storage location (if not planned in the reservation)
The following fields can be filled (incomplete listing):
Special stock indicator
Item text
Unloading point
Goods recipient
The following fields cannot be filled (incomplete listing):
Movement type
Material
Plant
Account assignment fields
For 4 GM_Code 04: Transfer posting
Transfer posting without reference to a reservation
The following fields have to be filled:
Material number
Plant
Storage location
Movement type
Movement indicator
Quantity in unit of entry
ISO code unit of measurement for unit of entry
The following fields may have to be filled in some cases (incomplete listing):
Receiving material
Receiving plant
Receiving storage location
Receiving batch (if material is handled in batches and you want to change batches)
Receiving/issuing special stock (e.g. sales order, project, vendor etc.)
Shelf life expiration date (if this has been configured in the system)
Reason for movement (if this has been configured in the system)
Batch (if the material is handled in batches and automatic batch number assignment is not set)
The following fields can be filled (incomplete listing):
Special stock indicator
Item text
Account assignment fields (for automatic posting lines: Expense/income from stock transfer)
The following fields cannot be filled (incomplete listing):
Reservation
Transfer posting with reference to a reservation
See goods issue with reference to a reservation
For 5 GM_Code 05: Other goods receipts
Other goods receipt without reference to a reservation
See goods issue without reference to a reservation
Other goods receipt with reference to a reservation
See goods issue with reference to a reservation
For 6 GM_Code 06: Reversal of goods movements
You can use the Cancel method to reverse goods movements. But you may also want to cancel a goods movement without referring to a material document (see the Cancel method).
If you want to work without referring to the document, you have to fill the field BAPI_GM_ITEM_CREATE-XSTOB in the interface (import table GOODSMVT_ITEM). In this case, the system converts the movement type assigned in the interface to the reversal movement type. Alternatively, you can set the reversal movement type in the interface. In this case, the BAPI_GM_ITEM_CREATE_XSTOB field must be transferred blank.
If you want to cancel a goods movement with reference to a reservation (without using the Cancel method) you can only transfer the field BAPI_GM_ITEM_CREATE_XSTOB if it is filled. Movement types are not transferred when you post with reference to a reservation, as the movement type is contained in the reservation item.
For 7. GM_Code 07: Subsequent adjustment to a subcontract order
Ordered material of subcontract order
The following fields have to be filled:
Unique identification of document line (can be assigned to anything)
Posting date in document header
Document number of purchasing document
Item number of purchasing document
Material number check
Plant check
Movement type (select movement type 121)
Movement indicator (must be O)
Further entries are not allowed. The entry quantity for the ordered material of a subcontract order must be zero.
Components
The following fields have to be filled:
Unique identification of document line (can be assigned to anything)
Identification of the immediately superior line
Plant
Material number check
Quantity in unit of entry; can also be negative
The following fields can be filled:
Storage location
All other fields in the method that are included in this list.
The following fields may not be filled:
All fields that are not in the list above. The movement indicator must be blank.
More information on LINE_ID and PARENT_ID
Additional fields in goods-receipt-based invoice verification
When you post a subsequent adjustment, the following fields must also be transferred:
REF_DOC_IT (LFPOS): Item of a reference document
REF_DOC (LFBNR): Document number of a reference document
REF_DOC_YR (LFBJA): Fiscal year of a reference document
Only when you transfer these fields is it guaranteed that the reference to the original goods movement stays the same. -
Good Receipt with Scheduling agreement
Dear
We are creating scheduling agreemant & delivery Schedule.
Is there any posiblity to take good receipt with reference to SA perior to delivery date mentioned in the delivery schedule?
Schedule line 26.06.2009
Good Receipt 25.06.09
Thanks,
SAmir BhattHi,
I dont think so it is possible, But Still i can check with the change of some settings, before that you jst telme clearly wy do u have requirement? What was the reason?
Hari Prasad -
STO history not update in stock transfer order,
Hi, Experts,
I have create delivery against Stock transfer order , But i checked in some STO case - purchase order history tab not update, What is the reaon for this . can any body gives solution.
One more question, I had created STO & Then do PGI against this STO, After this i also take GRN for this, But when i had check ddocument flow for outbound delivery GRN document not update, But it display in STO history tab.
Pls give me solution for both question.
Thanks a lot in advance,
RegardsHi, Harsh Panara ,
1. Is this problem reproducible? If yes, you may need to create a message for it in service market place.
2. If this is only a single case, you can re-create the EKBE (po history) entry via report ZCREA_EKBE. Please check SAP note 433505.
3. Regarding the GR document and document flow, this is related with how you post the GR. If you post GR in MIGO with reference to the outbound delivery, it should be updated to the document flow. How did you post it? -
Make to order for stock transfer orders
Hi all
I have set up "make to order" strategy (20) in a production plant A.
When I create a sales order for an external customer, in production plant A, the system creates a requirement in a special stock for the sales order in MD04, which is exactly what I expect. In this way, a planned order is pegged to the sales order.
I would like to have the same mechanisn with a requirement from a stock transfer order. In other words, this STO requirement would appear in a special stock in the MD04.
I know that it is possible if the STO is allocated to a sales orders in the distribution plant, but I want to avoid this strategy in the dsitribution plant.
Is there any way to do that ?
Thank you for your reply
ThierryHi,
It's not possible in std SAP, as a demand from an STO is not a special segment requirement eg: say like a project segment or a sales order requirement.
Hope it clarifies.
Regards,
Vivek
Maybe you are looking for
-
When I run program UKM_TRANSFER_ITEMS it throws the following error. I suspect from the error message it is related to XI but I don't know what it means. Does anybody know? Message number is UKM_PI008
-
BUG: Double click on taskbar will not restore LR
Only right click+"Restore" brings LR from its minimized form. Click as well as double click are being ignored. Using Win XP pro.
-
How to use trace in analyzer of business explorer?
hi all, i was running a report in the analyzer, it is taking to much time and after that its connection is getting lost and i get an error as client out of memory. needed to see the trace so that i could analyze. can any one tell me how do i use the
-
New to 3D: how to create 3D in applets
hi! i'm new to 3D. although, i'm familiar to applets, i have no idea what tools java has to create 3d objects. any (good) links for introductionary tutorials? thanks!
-
Missing QuickTime.msi file - cannot uninstall or update itunes or quicktime
Using Windows 7, 64 bit. Got message that new versions of itunes and quicktime available. Downloaded and ran the files.' Installation failed, cannot find network path ...'. Also, 'quicktime.msi is missing'. Couldn't find the latter anywhere. Cannot