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

Similar Messages

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.

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

Rejection for return delivery - Confirmation

Hi all,
While i'm doing "return delivery" system should ask 'Rejection
for return delivery'( like poor quality etc..) but, without this
indicator i can confirm the return delivery.
How to make this field as a mandatory ( rejection for return del)
Return deliery > Item > notes and attachment > rejection for rtn del
Thanks and regard
Hareesha

Hi,
You can implement the BADI "BBP_DOC_CHECK_BADI" to make the field mandatory.
BR,
Disha.
Pls reward points for useful answers.

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.

Vendor return delivery form Quality Management on inspection type 08

Dear all.
I have a query regarding vendor return delivery. The issue is on a transection when one of our user has wrongly post the material to restricted stock after rejecting it on an inspection lot (Orign 01), that actually has to return to vendor and lot is the second return delivery to vendor on the same P.O. and line no.
To correct this i have done a transfer posting and transfer the material back to quality inspection by using movement type 322. Now i have an inspection lot with 08 orign but this time the system is not allowing me to post a return delivery and showing "PU Qty deficit" error.
Any one has any idea! please advice.
I am very thankful for your help.

Dear Tahir,
Have checked the scenario and is working fine, I think there is some i found in your 3rd communication in this thread. Gajesh has given you right path, you are trying it differently so there is a error. Just do following and revert back:
You have applied 08 insp type and lot i generated again and you have posted it to block stock correct no??? and you have already removed 08 type now fine.
Now go to migo >> *select return delivery against original material document, put reason for movement and select stock type as block stock * and post the document.
You were trying to do reverse GR instead of return delivery hence system was not allowing, pl check and revert it works 100%.
Shekhar

Error while posting stock from quality to return delivery

Hi ,
I am working in decentralized warehouse. I am posting stock from quality to return delivery in t code QA32. The following is the error message i am getting . i have also checked the movement type settings they are fine for 553.
"Posting only to free or blocked stock due to missing goods receipt".
Please let me know if i am missing any thing in config......
Thanks
Ilyas

Hi Ilyas,
Can you check again the movement type? For return delivery movement type 122 is used and 553 is for GI scrapping from QI. You can check it in SPRO>QM>QI>Inspection lot completion> Define inventory postings.
reg,
Sudhir

Issue of Quality Inspection for consignment return delivery

Hello,
I am doing a returns delivery(from a Sales Order) from a Customer Consignment.
I am getting a error when I do a Post Goods Receipt(PGI). QM is active for that material.
The error I am getting is
"Change the inspection stock of material XXX in QM only"
Procedure says
"Check both the QM inspection setup data and the movement type for material XXX in the quality management view of the material master"
The movement type used in the returns delivery is 655(GD returns for QI).
What is the solution for this error. Do I need to change/add new Inspection type based on the Movement type?
Please let me know ASAP.
Thanks
Regards
SAP Fan..

Hi,
You can read this link for inspection for customer return [Inspection for customer return|http://help.sap.com/saphelp_47x200/helpdata/en/92/b808b1d52a11d2962200a0c930e04c/frameset.htm]
It looks the material master is set-up inspection type with 06 - returns from customer. Also the movement type 655 moves the goods into QI stock. In this case, the Quality personnel needs to change the inspection stock type using transaction code QA32. They will change the usage decision on the customer returns.
Once the change the inspection type is changed, you can do the post goods receipt.
Regards

Vendor Return Delivery through Quality Notification.

Hi Experts,
I m doing vendor return delivery through quality notification with action box , after giving PO NO. & Material document no we are getting the following error
1) Could not create return delivery
2) Deficit of PU IR quantity 2.000 EA
For the GR based IV reversal after IR tick is not active.
Kindly suggest possible reason for the same
Thanks & Regards
Rajesh

Hi
There is deficit of Quantity i.e the quantity lying in stock is less than 2. and secondly for GR based invoice verification the IR tick should be there in PO in Invoice tab.

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

Cancellation of RETURN delivery made by Quality

Similar Messages

Maybe you are looking for