Cancellation of return delivery

Hi all,
I want to know, if we cancel the Return delivery document after doing Reverse goods Movement using VL09, then wht will happen to the stock.
will it go away or come into the stock.
plz. let me know.
thanx in advance
sourav

yes. the Quantity will decrese.
Regards,
Madhu.

Similar Messages

Cancellation of RETURN delivery made by Quality

Hi All,
I want to cancel the return delivery made to a vendor.
It was posted in QA11(usage decision) in Quality Mgmt.
In MBST, the system doesnot allow to cancel the document.
How should i proceed ?
pl give me a direction.
regards
gnk
Edited by: gnk gnk on Feb 17, 2008 7:15 AM

hi
you cannot cancel the return delivery alone what you can do is first reverse the PO's then try to cancel the inspection lot .Then do the fresh MIGO and then you can post the material to production
kindly refer the following link also
http://help.sap.com/saphelp_46c/helpdata/en/a6/df293581dc1f79e10000009b38f889/tree.htm
regards
thyagarajan

Difference between confirmation cancellation and return delivery

Dear Gurus,
can you explain to me the difference between confirmation cancellation and return delivery in terms of processes and impact on ECC postings?
Thank you in advance for your collaboration,
Fuffo
Edited by: Fuffo Fuffi on Dec 21, 2010 2:36 PM

Hi
Confirmation Cancellation --> is used for reversing a confirmation which is posted wrongly in the system. This is generally used for reversing a faulty transaction.
Return Delivery --> is used for sending the goods back to vendor. This happens when we receive goods from vendor and for some reasons the delivery does not meet customer's specification due to any reason. In these cases you record the goods movement as Return delivery sent back to Vendors.
Regards
Virender Singh

FM for creating GR cancellation or return delivery

hi experts,
i would like to know whether there is any FM/method to do the cancellation of GR in SRM 7. i found one BAPI for doinf confirmation BAPI_CONFEC_CREATE but not for cancellation. any ideas?
thanks

hi yadav
need your help again for updating the PO items. i using the below code. system is creating the change versions but with no items. not sure why
CALL FUNCTION 'BBP_PD_PO_GETDETAIL'
EXPORTING
*   I_GUID                           =
I_OBJECT_ID                      = po_no
*   I_ATTACH_WITH_DOC                = ' '
I_WITH_ITEMDATA                  = 'X'
IMPORTING
E_HEADER                         = ls_hdr
*   ET_ATTACH                        =
TABLES
E_ITEM                           = lt_item .
data : obj_hdr_guid type BBP_GUID,
      lo_po_inst type ref to /SAPSRM/IF_PDO_BO_PO_ADV,
      lo_po type ref to /SAPSRM/IF_PDO_BO_PO.
obj_hdr_guid = ls_hdr-guid.
TRY.
CALL METHOD /sapsrm/cl_pdo_factory_po_adv=>get_instance
EXPORTING
    iv_header_guid = obj_hdr_guid
    iv_mode         = 'EDIT'
    iv_process_type = 'ECPO'
*    iv_wiid         =
*    iv_user_id      =
RECEIVING
    ro_instance     = lo_po_inst
lo_po ?= lo_po_inst.
data: lt_parguid type BBPT_GUID,
      ls_parguid like line of lt_parguid.
ls_parguid-guid = ls_hdr-guid.
append ls_parguid to lt_parguid.
CALL METHOD lo_po->/sapsrm/if_pdo_item_list~get_item_list
EXPORTING
        it_parent_guid = lt_parguid
IMPORTING
    et_item_guid   = lt_itmguid
CALL METHOD lo_po->get_item_detail
EXPORTING
    it_item_guid         = lt_itmguid
*    it_requested_fields =
IMPORTING
    et_item              = lt_item
*    eo_meta_data_handler =
CHANGING
   co_message_handler   = lo_msg
data: lt_item_upd type BBPT_PD_PO_ITEM_ICU,
      ls_item_upd like line of lt_item_upd.
loop at lt_item into ls_item.
move-corresponding ls_item to ls_item_upd.
IF ls_item_upd-final_entry eq space.
     ls_item_upd-final_entry = 'S'.
else.
     ls_item_upd-final_entry = 'D'.
ENDIF.
ls_item_upd-quantity = '3'.
append ls_item_upd to lt_item_upd.
clear : ls_item_upd, ls_item.
endloop.
CALL METHOD lo_po->update_item
EXPORTING
    it_item            = lt_item_upd
CHANGING
    co_message_handler = lo_msg
*TRY.
CALL METHOD lo_po->/sapsrm/if_pdo_base~submit_update
CHANGING
    co_message_handler = lo_msg
* CATCH /sapsrm/cx_pdo_wrong_mode .
* CATCH /sapsrm/cx_pdo_abort .
*ENDTRY.
CALL METHOD lo_po->order
CHANGING
    co_message_handler = lo_msg
CALL METHOD lo_msg->get_messages
              IMPORTING
                et_messages = lt_messages_class.
    CATCH /sapsrm/cx_pdo_incons_user
    /sapsrm/cx_pdo_lock_failed
* CATCH /sapsrm/cx_pdo_abort .
* CATCH /sapsrm/cx_pdo_error .
* CATCH /sapsrm/cx_pdo_no_authorizatio .
/sapsrm/cx_pdo_no_authorizatio
/sapsrm/cx_pdo_order_invalid
/sapsrm/cx_pdo_parameter_error
/sapsrm/cx_pdo_pd_read_error
/sapsrm/cx_pdo_status_change
/sapsrm/cx_pdo_status_error
/sapsrm/cx_pdo_wf_mode_ban
/sapsrm/cx_pdo_wrong_bus_type
/sapsrm/cx_pdo_wrong_mode
    /sapsrm/cx_pdo_error
      /sapsrm/cx_pdo_abort into lo_root.
* CATCH /sapsrm/cx_pdo_abort .
* CATCH /sapsrm/cx_pdo_no_authorizatio .
lv_msg = lo_root->get_text( ).
* CATCH /sapsrm/cx_pdo_abort .
ENDTRY.
commit work.

Vendor Return delivery Cancellation

Dear Guruu2019s,
I have one problem regarding return delivery (122) cancellation.
One of our QA guy wrongly posted return delivery to vendor through QA11u2026
Now how to reverse it, Before QM module we had reversing through MBST codes..
After QM module system is not allowing to do cancellation of return delivery (122) document from
MBST.
Waiting for ur replies.

1) Create own report program refer to source code which is attached in SAP note 175842.
(The object name is 'RQEVAC50'.)
2) Assign the transaction 'QA11' as allowed transaction into movement type '123' at transaction OMJJ.
(This is configuration.)
3) Execute above program and input the inspection lot number then execute.
(Stock which was transferred from QI to other will be reversed to QI stock again.)
4) Post stock again at transaction QA11 or QA12.
Regards
Luke

Return Delivery docuent cancel

Dear Experts
We have one problem regarding Return delivery through QA32
We have done 'Return Delivery' from QA32 T Code
But Now accounting department cannot MIRO for the same GR document number
Henceforth when trying to cancel return delivery document, getting following error
'Material Document cannot be processed'
Please suggest, Either how to cancel the Return Delivery document or MIRO get done ?
B/R
Dharmesh Soni

'Material Document cannot be processed'
Dear Please tell us the full description of error?
You did UD before you done any return delivery through QA32?
Cheers
KK

Error during reversal of return delivery posting.

Hi,
We have received some goods returned from customer.
We created return order , return delivery and posted GR for return delivery to have stock in.
But now we realise that we have booked material agaonst wrong delivery so we need to cancel return delivery.
when i am trying to reverse return delivery with VL09 , geting error as "error during search for WM movemnt type (652 1 L) "
how i should cancel this return delivery
thnks

Hi,
Is L9005 the error message?
Please check your entry in table T321 (V_T321).
SPRO > LE > WM > Interfaces > IM > Define Movement Types - here choosse LE-WM interface to Inventory Management.
As per the error message you should maintain a record for your WH:
- reference mvt 652
- special indicator: 1 (this indicator is likely to be in the material master of your product too)
- movement indicator L
Regards,
Csaba

Returns Delivery Reversal

Hello Everyone,
I have a returns delivery which I need to reverse. However, in VL09, I am encountering this error:
"Deficit of BA Ret.blocked prev. 37,941.000 EA : <Material> <Plant> <Stor Location> <Batch>
Shortfall below the specified stock level or quantity amounting to 37,941.000 EA."
When I checked MMBE, there is zero stock for this material/batch. What is the best way so I could reverse the returns delivery?
Thanks a lot for your time!
Regards,
Olyn

Hi Olyn,
In this scenario you can't cancel the earlier material document which is created at the time of PGR ( i.e. Return Delivery). Becasue the stock which is returned is used by some one.
So to cancel this return delivery you need to full fill the same delivery qty in the plant against the same batch. Either do the Material to material transfer or else.
If you can't able to do this there only one option you can able to do is you need to cancel the previous Material document which is created at the time of PGR.. through MBST. At this time system through the error message saying that Material document cannot be processed with error message M7130.
Change the ctaegory from error to Warning against this message in OMCQ and process it it may useful. But it may impact ur stock levels.
Please co ordinate the same with team member and process it..
Regards
Durga Sana

Cancelation of Vendors return delivery document ( 122 Movment type)

Dear All,
We have a case where in all vendor receipts are quality checked and in case a quality lot is rejected a returns delivery is crated to the vendor with SD returns delivery type RLL..
We want to reverse this returns delivery and accept the the quality rejected lot. Can you please suggest how to do the same.
We tried to reverse the returns delivery with transaction VL09 we got an error " the vendor rejection returns delivery type RLL cannot be reversed.
We also tried out transaction MIGO Cancellation option and got an error "material document cannot be processed"
Please suuggest the procedure to reverse this material document.
Deepak.

H i Deepak!
   We also have the same scenario like yours.But I am struggling to get the pricing details from the purchasing document. I don't know how to control this function.Material price and ED elements to be copied from the reference purchase document.How are you handling this? Kindly reply me soon.
The following information may be useful to you.
Posting a Return Delivery with Reference to the Purchase Order
Choose the Enjoy transaction MIGO for posting goods movements. Enter the purchase order. In goods-receipt-based invoice verification, the system displays all the GR items. Choose the items that you want to return, specify the quantities, and choose movement type 122.
Posting a New Goods Receipt with Reference to a Return Delivery
If you receive a substitute delivery after you have returned goods to a vendor, it is advisable to reference the associated return delivery by using a reverse posting when you post the new goods receipt. This enables the system to suggest and update the data for this particular business process. This is particularly important in goods-receipt-based invoice verification, so that the link between the goods receipt, the return delivery, and the invoice remains intact (see also Subsequent Delivery).
The table below shows which reversal movement types you can use to reference the associated return delivery.
Goods receipt      Return Delivery              Substitute delivery
101                         122                                    123
103                         124                                    125
105                         122                                    123
For example, if you posted the goods into goods receipt blocked stock using movement type 103, you return them using movement type 124 (return delivery from goods receipt blocked stock). To post the substitute delivery back into goods receipt blocked stock, you do not use movement type 103, but reverse the material document for the return delivery. The system automatically suggests movement type 125, which maintains the link between the goods receipt, the return delivery, and the invoice.

Can we create cancellation/return delivery with BAPI_CONFEC_CREATE

hi experts,
i want to use the above BAPI to create cancellations and return deliveries in SRM 7. i am not able to figure out the exact data that needs to be passed to the BAPI to create cancellation/return delivery. i have used class approach to do the same and able to create them, but i am specifically interested in FM/BAPI
does anybody used this BAPI to create cancellations?
thanks

hi,
i could not make this BAPI work for cancellations but found another way of doing confirmations and cancellations using std FMs
here is the code for confirmation
CALL FUNCTION 'BBP_PD_PO_GETDETAIL'
   EXPORTING
     I_OBJECT_ID                      = is_conf_header-po_number
     I_WITH_ITEMDATA                  = 'X'
   IMPORTING
     E_HEADER                         = ls_header
     ET_ATTACH                        = lt_attach
   TABLES
     E_ITEM                           = lt_item
     E_ACCOUNT                        = lt_account
     E_PARTNER                        = lt_partner
     E_LONGTEXT                       = lt_longtext
     E_ORGDATA                        = lt_orgdata
     E_TAX                            = lt_tax
     move-corresponding ls_header to ls_new_header.
ls_new_header-process_type = 'CONF'.
ls_new_header-subtype = 'CF'.
ls_new_header-src_object_type = 'BUS2201'.
ls_new_header-src_guid = ls_header-guid.
clear ls_new_header-object_id.
loop at lt_item into ls_item.
read table it_conf_items into ls_conf_items with key po_item_number = ls_item-number_int.
if sy-subrc ne 0.
continue.
endif.
move-corresponding ls_item to ls_new_item.
ls_new_item-src_object_type = 'BUS2201001'.
ls_new_item-src_guid = ls_item-guid.
ls_new_item-final_entry = ls_conf_items-final_entry.
ls_new_item-quantity = ls_conf_items-quantity.
append ls_new_item to lt_new_item.
endloop.
loop at lt_partner into ls_partner.
   move-corresponding ls_partner to ls_new_partner.
   append ls_new_partner to lt_new_partner.
   endloop.
   loop at lt_orgdata into ls_orgdata.
     move-corresponding ls_orgdata to ls_new_orgdata.
     append ls_new_orgdata to lt_new_orgdata.
     endloop.
loop at lt_account into ls_account.
   move-corresponding ls_account to ls_new_account.
   append ls_new_account to lt_new_account.
   endloop.
lv_src_guid = ls_header-guid.       .
CALL FUNCTION 'BBP_PD_CONF_CREATE'
EXPORTING
I_SAVE                           = 'X'
   I_HEADER                         = ls_new_header
   I_SRC_GUID                       = lv_src_guid
   IT_ATTACH                        = lt_new_attach
IMPORTING
   E_HEADER                         = ls_e_header
   ET_ATTACH                        = lt_e_attach
TABLES
I_ITEM                           = lt_new_item
   I_PARTNER                        = lt_new_partner
   I_ORGDATA                        = lt_new_orgdata
   E_ITEM                           = lt_e_item
   E_ACCOUNT                        = lt_e_account
   E_PARTNER                        = lt_e_partner
   E_ORGDATA                        = lt_e_orgdata
    e_messages                       = lt_new_message
et_msg[] = lt_new_message[].
ls_conf_documents-doc_number = ls_e_header-object_id.
append ls_conf_documents to et_conf_documents.
CALL FUNCTION 'BBP_PD_CONF_SAVE'
EXPORTING
    IV_USERTYPE               = 'X'
   IV_HEADER_GUID            = ls_e_header-guid
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT
code for cancellation
get all the confirmations created for the PO
    CALL FUNCTION 'BBP_PD_CONF_GETLIST'
      EXPORTING
        i_for_po_id = is_conf_header-po_number
      TABLES
        e_pdlist    = lt_pdlist
        e_messages = lt_msgs.
delete GRS which are cancelled
    LOOP AT lt_pdlist INTO ls_pdlist WHERE subtype EQ 'CA'.
      DELETE lt_pdlist WHERE guid = ls_pdlist-src_guid.
    ENDLOOP.
delete the cancelllation documents. we don't need them anymore
    DELETE lt_pdlist WHERE subtype EQ 'CA'.
    loop at lt_pdlist into ls_pdlist.
      CALL FUNCTION 'BBP_PD_CONF_GETDETAIL'
       EXPORTING
          I_GUID                           = ls_pdlist-guid
          I_WITH_ITEMDATA                  = 'X'
      IMPORTING
         E_HEADER                         = ls_conf_hdr
       TABLES
         E_ITEM                           = lt_con_items
         E_PARTNER                        = lt_con_partner
move-corresponding ls_conf_hdr to ls_new_header.
ls_new_header-process_type = 'CONF'.
ls_new_header-subtype = 'CA'.
ls_new_header-src_object_type = 'BUS2203'.
ls_new_header-src_guid = ls_conf_hdr-guid.
clear ls_new_header-object_id.
loop at lt_con_items into ls_con_items.
move-corresponding ls_con_items to ls_new_item.
ls_new_item-src_object_type = 'BUS2203001'.
ls_new_item-src_guid = ls_con_items-guid.
append ls_new_item to lt_new_item.
endloop.
loop at lt_con_partner into ls_con_partner.
   move-corresponding ls_con_partner to ls_new_partner.
   append ls_new_partner to lt_new_partner.
   endloop.
      lv_src_guid = ls_conf_hdr-guid.
after that call BBP_PD_CONF_CREATE as we did for the confirmation followed by BBP_PD_CONF_SAVE and commit work.
Edited by: SRM7CON on Mar 7, 2012 12:04 PM
Edited by: SRM7CON on Mar 7, 2012 12:25 PM

Difference between return delivery and cancellation

What is the difference between return delivery and cancellation in MIGO transaction.
Can any one explain how to use them and where to use them.
thanks

HI there
I will make it simple with figures,,
Return Delivery
PO- 100 nos
GR-100 nos in to QI stock,,,
After the Inspection- 95 nos Accepted, 5 nos Rework
1. Return Delivery - Expecting the Subsequent Delivery- post the 5 nos into 122 (Return to Vendor), he will do the rework and provide the component back after the inspection if the qulaity is ok receive into 101
2.Return Delivery- Not expecting the delivery back- post the 5 nos into 122 (Return to Vendor) and close the PO, if the payment already create the Credit memo for the 5 nos,,,
Cancellation
Ex:
1. GR for the 100 nos into 103 instead of 101, so cancel the document through 104
At the time of cancel the document, Always use the origin material document, so that
1. All the data will be copied automatically
2. Reversal Movement type will be defaulted
3. Material Cost will be picked on the last material document,, if not it will pick the price from PO/Order.
Hope it helps you
Thanks
Senthil

Error Message during posting return delivery against materil document

Dear experts
I have created a purchase order with batch specific unit of measure KAI.
I created the inbound delivery document (say for eg: 30,000 KG)
I have taken GRN for the above IBD through MIGO transaction with 101 movement for all 30,000 KG.
Later i have posted the return delivery 122 movement with reference to above 101 material document. 30,000 KG
After this i realized that i need cancel the 101 movement document.
So cancelled the 122 movement document, and try to cancell the 101 material document.
Then system is issuing error message VLA 321 "Movement type 102 cannot be used here".
Also if i again want to post return delivery to send the stock back, then also i have error message. but this time it is VLA 319
"Return delivery qty greater than previously GR-posted qty:"
My Support package for SAP_APPL, relese 600 is SAPKH60019.
Please suggest me solution to fix these errors as these are not relavant for the situation.
Regards/Murali

Hi,
Can you please check this note...
Note 1050944 - GR for inbound delivery using inventory mgmt as of ECC 6.00
Note 1342935 - Error message BORGR 623 during GR reversal in MIGO
Regards
Bhuban

Issue with Return Delivery for movement type 262

Hi,
I have got a strange issue, the user is trying to do a MIGO Return Delivery for a material document using movement type 262, this he claims has been doing it for many materials. However when i go to the MKPF table i see the transaction Code field to be MIGO_GI for all the material documents for which he claims to have done return delivery. But under this transaction code we have only 4 options - Display, Issue, Cancel and Remove from storage.
Now when he tries to do the return delivery for movement type 262 he get an error message "Check table T156N: entry RL 262 does not exist" , but this has been very well maintained in the table.
Can you please let me know -
If it is possible to do a return delivery for a movement type 262?
If yes how to address the above error encountered.
Thanks in advance
Sachin

Hi Sachin,
If you think of return delivery to vendor with or w/o PO reference you can use movement types 161, 122, 124 as default settings.
Movement type 261 means withdrawal against production order and its reverse is MVT 262. The latter can be used e.g. via MB1A (or you can make storno of a confirmation by 261).
Are you sure your user is using the correct terminology ('return delivery')? Please check the material documents he/she claims to have booked as return delivery. (in MB51 you can get a list of all material movements of MVT 261 that belong to 'your user' and after that you can open the material document and check through which transaction the booking was made.)
BR
Csaba

After Return Delivery to Vendor cannot remove shipping notification in MD04

Hi.
Good Day.
I would like to ask help regarding to my issue.
We had to create a return delivery to send the goods back to the vendor A. The packaging item was blocked and we created the outbound delivery via transaction MBRL with reference to material document when we do GR with the inbound Delivery A. After having processed all necessary steps including the posting of the goods issue of outbound delivery, the inbound delivery A is again open and expects a goods receipt of the returned units. This can also be seen in MD04. Meanwhile the supplier has sent a new "compensation" delivery, with a different inbound delivery B. This was goods receipted and with this delivery the complaint/return process is finished from the supplier's and our point of view.
Problem: What remains is the original open inbound delivery A. Currently we have no idea how to get this one deleted, but we need to cancel it, because there won't be a credit note and there won't be another physical delivery for this inbound delivery A.
What I have done so far:
1) Tried using VL09 to inbound delivery A but there was no effects. probably because the inbound delivery A is already closed.
2) It is not possible to set the item of SA to finished because we my use that item again.
Thanks for your help.
Med'z

Hi Madhu.
Good Day.
First of all I really appreciate your response.
I tried to change the first inbound delivery but canu2019t do much. Because all fields were block since it is already completed.
The system shows the error "The goods movement status (partially or completely processed) does not allow the item to be deleted."
I also tried to change the schedule line but it didnu2019t do any effect with the issue.
Thank you,
Best regards.
Medel.

Reverse a Return Delivery with inspection lot posted (QM)

Hello experts,
I want to reverse with transaction VL09 a good movement of a return client delivery with inspection lot. I posted the inspection lot and transferred the material to Unrestricted use (transaction QA11).
Then I began the cancel Return Process and I transferred the material to Quality (movement type 322) to run VL09 with material in Quality stock, but the system displays the following error message:
You cannot cancel GR, since inspection lot is already partly posted
Message no. QA046
Diagnosis
You are attempting to reverse a goods receipt although quantity postings have already been made from the inspection lot. This means that stock for the goods receipt has already been transferred and, for this reason, a cancelation of the document is no longer possible.
Procedure
Ensure that the postings in QM (within the usage decision transactions) are carried out.
Please let me know what can I do to reverse the return delivery.
Thanks in advance.
Pablo

You are trying to do the process which you ahve already transferred through Transaction QA11.
The role of Cancel return Process has already been done by this transaction as the Stock has already been into Un- restricted.
Best Regards,
Ankur

Cancellation of return delivery

Similar Messages

Maybe you are looking for