Remove Reason For Rejection From Sales Order Using BAPI_SALESORDER_CHANGE

Hi
I have a sales order and would like to remove the rejection reason.
I am trying to use BAPI_SALESORDER_CHANGE with the following code:
(0000xxxxxxx is my material #. i just removed the actual #).
MOVE: '0000050106' TO SALESDOCUMENT.
MOVE: 'U' TO T_HEADER_INX-UPDATEFLAG.
MOVE:                        30 to t_order_item_in-ITM_NUMBER,
                                  ' ' to t_order_item_in-REASON_REJ,
      '0000000000xxxxxxxx' to t_order_item_in-material.
APPEND t_order_item_in.
MOVE: 'U' TO t_order_item_inx-updateflag.
MOVE: 'X' to t_order_item_inx-REASON_REJ,
           'X' TO t_order_item_inx-material.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
    salesdocument              = SALESDOCUMENT
    order_header_inx           = T_HEADER_INX
tables
    RETURN                     = T_RETURN
    ORDER_ITEM_IN              = T_ORDER_ITEM_IN
    ORDER_ITEM_INX             = T_ORDER_ITEM_INX
WAIT UP TO 5 SECONDS.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT          = 'X'
IMPORTING
   RETURN        = t_return
WAIT UP TO 5 SECONDS.
can anybody help?
the BAPI returns success messages saying the item was processed successfully but the reason code is still there.
However, if i pass in any other reason code like 02 or 06, it works!.
thanks.

Thanks for your help. =)
I also realized that I forgot to add the SO Item # into the T_ORDER_ITEM_INX-ITM_NUMBER fields.
But now it works.

Similar Messages

BAPI_SALESORDER_CHANGE to update reason for rejection of sales order item

Hi,
The FM BAPI_SALESORDER_CHANGE is not working properly as I am getting below error when try to update the reason for rejection at sales order item level.
The delivery is done for this salesorder. Is it because the reason for rejection field is not as an input field when delivery done?
error in return table is " Field 'ABGRU' cannot be changed, VBAPKOM 000010 ready for input"
Request your suggestions to avoid this error.
Thanks

>
anikaushi wrote:
> Hi,
> The delivery is done for this salesorder. Is it because the reason for rejection field is not as an input field when delivery done?
>
> error in return table is " Field 'ABGRU' cannot be changed, VBAPKOM 000010 ready for input"
>
>
> Thanks
Yes, Most likely.. You can confirm this by trying to change a order without delivery and see if it goes thru (to ensure that you have passed correct parameters)...
you may have to delete the delivery (and if billing document exist, cancel it), before you can reject the line item... it would be safer to raise an error message and let the users manually delete delivery document as long as you don't have large volumes of this scenario..
Please see the SDN thread for how you can avoid this error...
Re: Cancel Sale Order after Issued Billing

REMOVE REASON FOR REJECTION FROM THE SALES ORDER

Hi,
When i am trying to change status of items 130+140 from net cancellation to "open" (remove reason for rejection), saving is not possible because of this error message!
Item 000130 :Target qty of reference: 1 PC (total referenced: 2 PC).
Also an information message: Subsequent documents already exist for item 000140.

Thanks for your help. =)
I also realized that I forgot to add the SO Item # into the T_ORDER_ITEM_INX-ITM_NUMBER fields.
But now it works.

Dump while supplying Reason for Rejection in sales order

Hi Gurus,
when I am suppling the Reason for Rejection ("Cancelled") for a line item in existing Sales Order, the sales order is going to dump,this is the case with production system where as the same is working fine with testing system,ofcourse I am using different sales order numbers for both the cases....what may be the reason...
Please suggest.
Thanks for the help....Have a Nice Day..

Hi
Kindly post the error details.
After dump, use t code ST22, click on today, click on the error & analyse.
thank you.

Not able to put reason for rejection at sales order level.

Hi Gurus,
I have an issue where I am not able to put reason for rejection for line item in sales order. It gives error as please delete the follow on document purchase order line item number 10. I have already deleted the line item in purchase order. Then tried but did not work. Tried by deleting the purchase requision item also but it did not work.
Tried to undelete the item from PO and then again tried to put reason for rejection but it could no worked out.
Please guide me what can be the solution.
Regards
Vinod

As far a I understand you created PO for line item
So first check whether GR is reversed or not for PO
Then mark this line item for deletion in PO and then in PR
Check if you have created any billing document for PO if so reversed that invoice
Also check if you have created any delivery for the Line item in sales order if yes then reversed the same
If you have Sales order related Billing, and if you have done billing reverse the same
If you have Delivery related Billing, and if you have done billing reverse the same
After reversing all docuemnts created for Sales order then only try to reject the line item
You can check table VBFA for document flow

Customize reason for rejection in sales order

Hi,
Reason for rejection for line items in a sales order are displayed from the table TVAG.
My requirement is to display this drop down list based on TVAG and another custom table.
I wanted to know the place where this field VBAP-ABGRU is populated in standard code so that I can suppress that and display only those which are required.
Thanks in advance.
Abhishek

Syed,
It is always advicable to reject the order by giving a reason for rejection rather than deleting the sales order.
Once you delete the sales order, the number will be skipped, the system will not create another sales order with the same number.
Once you reject the order by a reson for rejection, the system will not allow to process the order further, the requirement will be reversed. The order status also will become as closed, so no further processing allowed (like delivery, PGI ... etc).
If you put delivery block in the item level of the order, the order can't be delivered, but the overall tatus of the order will be being processed.
So it is advicable to reject the order by giving an appropriate reson for rejection.
Prase

Reason for Rejection in Sales order

Hi,
when my customer sends me a PO cancel request, iam going to delete the Sales order in my SAP system.
what is the best way to do this, either to delete the SO or keep the Sales order with Reason for Rejection code?
If it is a Reason for rejection, what happens to the SO,
1)will it allow for further processing for e.g: Delivery creation.
2)will the Availability check carried out for this?, and is the stock going to be blocked for this?
what is the difference between Reason for rejection and the Delivery block, both at the Header and item level.
Pls reply,its urgent...
Regards
SR

Syed,
It is always advicable to reject the order by giving a reason for rejection rather than deleting the sales order.
Once you delete the sales order, the number will be skipped, the system will not create another sales order with the same number.
Once you reject the order by a reson for rejection, the system will not allow to process the order further, the requirement will be reversed. The order status also will become as closed, so no further processing allowed (like delivery, PGI ... etc).
If you put delivery block in the item level of the order, the order can't be delivered, but the overall tatus of the order will be being processed.
So it is advicable to reject the order by giving an appropriate reson for rejection.
Prase

Reason for Rejection at Sale sorder item - Not updating the quotation

Dear All,
I have quotation with 100 quantity and created 2 sales orders with reference to the quotation with qunatity 60 and 40.
Next changed the first sales order with reason for rejection at item level for 60 quantity.
But sales order status is still complete, where it should open and may create one sale sorder with 60.
now, issue is when ever reason for rejection in sales order, it should update the status of quotation.
Is this standard behavior???
Thanks in Advance.

Hi,
When you put the reason for rejection in the sales order, it is SAP standard to put the sales order complete. When the sales order is complete, then I believe system considers the quotation to be complete as well.
Try the below. It might help.
a. Delete the line item with 60 qty. Now check if the quotation has opened up. If yes, then, there you go with a solution... Else,
b. Check the configuration for sales order document type. Check what is the marking done for completion of the quotation. Put in the right one so that quotation is not marked (or updated) as complete when the reason for rejection is put in the sales order.
Hope this helps
Thanks
Mukund S

Workflow: Select Reason for rejection from dropdown list.

Hi all
I have to create a step where the Manager has to select the
Reason for Rejection from a dropdown list refering to a custom
parameter table maintained from t-code sm30.
Please post your suggestions on this.
Thanks for your time,
Mallik

Thanks for your Reply,
But It doesn't seem to work because It has to display a (table parameter) field containing the predefined Reasons for Rejection(dropdown list or more like search
help) from which the supervisor has to select one and it has to be attached and sent as a mail.
thanx

What are required feilds values for creating a sales order using va01?

What are required feilds values for creating a sales order using va01?
Please give examples if possible.

Hi,
go through this URL:
<a href="http://web.mit.edu/cao/www/SB2002/CR/VA01.htm">http://web.mit.edu/cao/www/SB2002/CR/VA01.htm</a>
Hope this will help you.
Thanks
Shiva

Update ship-to partner in sales order using BAPI_SALESORDER_CHANGE

Dear all,
We are trying to update the ship-to partner in a sales order using BAPI_SALESORDER_CHANGE. This is working correctly for most of our orders, so we do fill the BAPI correctly. However for some of our orders on item level a different payer is specified than on header level. However in that case the BAPI will not update the ship-to partner, but given an error message VPD 034 u2018The document must contain the same credit control areas for all payersu2019. Debugging already learned that actually the message is given not because of different credit control areas, but due to the fact that the payers and therefore the credit customers are different (although in the same credit control areas). For this reason we can not update the ship-to party of a large number of our sales orders with this BAPI. Actually we have 2 questions:
· Has somebody experienced the same issue and did you manage to solve it somehow, so the BAPI could be used for this purpose of updating partner data?
· Do you know other ways of updating the partners or partner address of an existing sales order in the background?
Thanks in advance for your assistance.
Regards,
Satish.

It was caused by standard SAP.

Change sales order using BAPI_SALESORDER_CHANGE

Hi i want to add a new line item to the existing sales order using BAPI_SALESORDER_CHANGE
but when i am trying it is giving
'Schedule line 0001 for item 000020 does not exist ' error..
please help me..

*********I wanted to add an new line item.***.. this is my code..********
LOOP AT gt_input3 INTO st_input3.
*Finding Max No of line Items
    IF fl_set IS INITIAL.
      READ TABLE gt_vbap INTO st_vbap WITH KEY vbeln = st_input3-vbeln.
      IF sy-subrc EQ 0.
        lv_posnr = st_vbap-posnr.
        fl_set = 'X'.
      ENDIF.
    ENDIF.
*Populate Item details
    lv_posnr = lv_posnr + 10.
    lv_vbeln = st_input3-vbeln.
    lv_order_header_inx-updateflag = 'U'.
    st_order_item_in-itm_number = lv_posnr.
    st_order_item_in-material = st_input3-matnr.
    st_order_item_in-target_qty = st_input3-imv_qty.
    st_order_item_in-plant = st_input3-werks.
    st_order_item_in-store_loc = st_input3-lgort.
   st_order_item_in-store_loc = st_input3-lgort.
    APPEND st_order_item_in TO lt_order_item_in.
*Populate item updation Details
    st_order_item_inx-itm_number = lv_posnr.
    st_order_item_inx-updateflag = 'U'.
    st_order_item_inx-material = 'X'.
    st_order_item_inx-plant = 'X'.
    st_order_item_inx-store_loc = 'X'.
    st_order_item_inx-target_qty = 'X'.
    APPEND st_order_item_inx TO lt_order_item_inx.
*Populate the Schedule Lines
    st_schedule_lines-itm_number = lv_posnr.
    st_schedule_lines-sched_line = '0001'.
    st_schedule_lines-req_qty = st_input3-imv_qty.
    APPEND st_schedule_lines TO lt_schedule_lines.
*Populate the update details of schedule lines
    st_schedule_linesx-itm_number = lv_posnr.
    st_schedule_linesx-sched_line = '0001'.
    st_schedule_linesx-req_qty = 'X'.
    st_schedule_linesx-updateflag = 'U'.
    APPEND st_schedule_linesx TO lt_schedule_linesx.
       AT END OF vbeln.
*Call BAPI Sales order change
      CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
        EXPORTING
          salesdocument    = lv_vbeln
          order_header_inx = lv_order_header_inx
        TABLES
          return           = lt_return
          order_item_in    = lt_order_item_in
          order_item_inx   = lt_order_item_inx
          schedule_lines   = lt_schedule_lines
          schedule_linesx = lt_schedule_linesx.
*Save Sales Order
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = 'X'.
      CLEAR lv_posnr.
      READ TABLE lt_return INTO st_return WITH KEY type = 'E'.
      st_ipfile_err3-message = st_return-message.
*Error Log
      LOOP AT gt_temp3 INTO st_temp3.
        IF st_ipfile_err3-message IS NOT INITIAL.
          MOVE st_temp3-record TO st_ipfile_err3-record.
          IF fl_set1 IS INITIAL.
            APPEND st_temp_err TO gt_ipfile_err3.
            fl_set1 = 'X'.
          ENDIF.
          APPEND st_ipfile_err3 TO gt_ipfile_err3.
        ELSE.
          APPEND st_temp3 TO gt_audit3.
        ENDIF.
        CLEAR : st_temp3,
                st_temp_err,
                st_ipfile_err3,
                fl_set.
      ENDLOOP.
      REFRESH : gt_zrman,

Blocked for payment from sales order

Hi!
Do you know to do to the FI document will come blocked from sales order?
For example, I did a sale order with a client x. The payment terms of this client is setting to block the payment.
So, when I did a sales order, and do all SD process, after billing it, on FBL5N the client document isn't blocked for payment.
Do you know any way to block it from a sales order??
Regards,
Danielle.

hai,
A is also fine. If the payment terms is applicable for both customer as well as vendor, then the system will block for payment and in FBL5N also system will show with block indicator A. Or
Try to block in same FBL5N, select particular document, goto environment in menupath select change document and block it and then save. Again run FBL5N check the block indicator.
There is no additional configuration is required apart from my first reply.
govind.
Message was edited by:
govindaraj s

Send 'Reason for Rejection' from Task Process back to User

I have a SharePoint 2013 workflow that uses "Start a task process" to get approval for documents in a library. On the task list, I have a field named 'reason for rejection' that the approvers would complete if they're going to reject the document.
When the document is rejected the workflow sends an email back to the person who created the document. Is it possible to somehow include the reason for rejection in the email? If not, is there some other solution for getting this information back to
them (other than just saying to contact the approvers)?

Hi Andrea_2,
According to your description, my understanding is that you want the email which is sent by workflow after the document is rejected to contain the field "reason for rejection".
Instead of adding the field into the email which is sent after the document is rejected, I suggest you add an "Send email" action when a single task is rejected, and make the mail is sent to the creator of the document.
You can do as the followings:
Open the workflow with SharePoint Designer 2013.
Open and edit the workflow, then click "Approval(**)".
Click "Change the behavior of a single task"
In the "When a task completes" scetion, add a "Send email" action in the ELSE IF branch, like the screenshot below:
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Update sales order using BAPI_SALESORDER_CHANGE --- URGENT!!!!

Hello,
<b> I want to update Batch, Pricing date, Header text & Item text using BAPI_SALESORDER_CHANGE.</b>
But i am not able to do it.
i have written a code, but it's still not updating:
PARAMETERS: p_vbeln LIKE vbak-vbeln.
TYPES: BEGIN OF t_return.
        INCLUDE STRUCTURE bapiret2.
TYPES: END OF t_return.
TYPES: BEGIN OF t_order_item_in.
        INCLUDE STRUCTURE bapisditm.
TYPES: END OF t_order_item_in.
TYPES: BEGIN OF t_order_item_inx.
        INCLUDE STRUCTURE bapisditmx.
TYPES: END OF t_order_item_inx.
TYPES: BEGIN OF t_schedule_lines.
        INCLUDE STRUCTURE bapischdl.
TYPES: END OF t_schedule_lines.
TYPES: BEGIN OF t_schedule_linesx.
        INCLUDE STRUCTURE bapischdlx.
TYPES: END OF t_schedule_linesx.
TYPES: BEGIN OF t_order_text.
        INCLUDE STRUCTURE bapisdtext.
TYPES: END OF t_order_text.
DATA: l_vbeln              LIKE          bapivbeln-vbeln,
      i_order_header_inx   LIKE          bapisdh1x,
      i_order_header_in    LIKE          bapisdh1,
      i_return             TYPE TABLE OF t_return,
      i_order_item_in      TYPE TABLE OF t_order_item_in,
      wa_order_item_in     LIKE LINE OF i_order_item_in,
      i_order_item_inx     TYPE TABLE OF t_order_item_inx,
      wa_order_item_inx    LIKE LINE OF i_order_item_inx,
      i_schedule_lines     TYPE TABLE OF t_schedule_lines,
      wa_schedule_lines    LIKE LINE OF i_schedule_lines,
      i_schedule_linesx    TYPE TABLE OF t_schedule_linesx,
      wa_schedule_linesx   LIKE LINE OF i_schedule_linesx,
      i_order_text         TYPE TABLE OF t_order_text,
      wa_order_text        LIKE LINE OF i_order_text,
      w_return             LIKE          bapiret2,
      l_date               TYPE char10.
CLEAR l_vbeln.
l_vbeln = p_vbeln.
          UPDATE REJECTION REASON IN SALES ORDER                *
*WRITE sy-datum TO l_date.
i_order_header_inx-updateflag = 'U'.
REFRESH i_order_item_in.
CLEAR wa_order_item_in.
wa_order_item_in-itm_number = '000010'.
wa_order_item_in-batch = '2007450027'.
wa_order_item_in-price_date = sy-datum.
wa_order_item_in-reason_rej = '00'.
APPEND wa_order_item_in TO i_order_item_in.
REFRESH i_order_item_inx.
CLEAR wa_order_item_inx.
wa_order_item_inx-itm_number = '000010'.
wa_order_item_inx-updateflag = 'U'.
wa_order_item_in-batch = 'X'.
wa_order_item_in-price_date = 'X'.
wa_order_item_inx-reason_rej = 'X'.
APPEND wa_order_item_inx TO i_order_item_inx.
*wa_order_text-doc_number = l_vbeln.
**wa_order_text-TDOBJECT = 'EHSWA_MAN'.
***wa_order_text-text_id = '0001'.
**wa_order_text-TDTEXT = 'Header Texts'.
*wa_order_text-text_line = 'SYNGENTA HEADER'.
***wa_order_text-function = 'U'.
wa_order_text-doc_number = l_vbeln.
wa_order_text-itm_number = '000010'.
*wa_order_text-TDOBJECT = 'EBAN'.
wa_order_text-text_id = '0001'.
*wa_order_text-TDTEXT = 'Item text'.
wa_order_text-text_line = 'SYNGENTA TEXT'.
wa_order_text-function = '004'.
APPEND wa_order_text TO i_order_text.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
    salesdocument               = l_vbeln
ORDER_HEADER_IN             =
    order_header_inx            = i_order_header_inx
SIMULATION                  =
BEHAVE_WHEN_ERROR           = ' '
INT_NUMBER_ASSIGNMENT       = ' '
LOGIC_SWITCH                =
NO_STATUS_BUF_INIT          = ' '
TABLES
    return                      = i_return
    order_item_in               = i_order_item_in
    order_item_inx              = i_order_item_inx
PARTNERS                    =
PARTNERCHANGES              =
PARTNERADDRESSES            =
ORDER_CFGS_REF              =
ORDER_CFGS_INST             =
ORDER_CFGS_PART_OF          =
ORDER_CFGS_VALUE            =
ORDER_CFGS_BLOB             =
ORDER_CFGS_VK               =
ORDER_CFGS_REFINST          =
   schedule_lines              = i_schedule_lines
   schedule_linesx             = i_schedule_linesx
   order_text                  = i_order_text
ORDER_KEYS                  =
CONDITIONS_IN               =
CONDITIONS_INX              =
EXTENSIONIN                 =
IF sy-subrc = 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait   = 'X'
    IMPORTING
      return = w_return.
ENDIF.
Please help out.
Please send the code of it.
Thanks in advance...

START-OF-SELECTION.
Get Blocked Orders
PERFORM sub_select_orders.
PERFORM order_reason_for_reject.
END-OF-SELECTION.
Display output
PERFORM sub_display_output.
*&      Form sub_select_orders
      text
FORM sub_select_orders .
SELECT a~vbeln
         a~erdat
         a~erzet
         a~auart
         b~posnr
         FROM ( vbak as A
         INNER JOIN VBAP AS B
         on Bvbeln = AVBELN )
         INTO TABLE i_order_data
         WHERE a~vbeln IN s_ordno AND
               A~auart IN s_auart AND
               A~erdat IN s_orddt AND
               A~vkorg IN s_vkorg AND
               A~vtweg IN s_vtweg AND
               A~spart IN s_spart .
IF sy-subrc NE 0.
    MESSAGE i001.
No data selected
    LEAVE LIST-PROCESSING.
ENDIF.
ENDFORM.                    " sub_get_blocked_orders
*&      Form order_reason_for_reject
      text
--> p1        text
<-- p2        text
FORM order_reason_for_reject .
LOOP AT i_order_data INTO w_order_data.
    w_output-vbeln = w_order_data-vbeln.
    w_ordhdrx-updateflag = c_update.
Update Order Reason for rejection .
    w_orditem-ITM_NUMBER = w_order_data-posnr.
    w_orditem-reason_rej = p_abgru.
    append w_orditem to i_orditem .
    w_orditemx-ITM_NUMBER = w_order_data-posnr.
    w_orditemx-updateflag = c_update.
    w_orditemx-reason_rej = 'X'.
    append w_orditemx to i_orditemx .
    At end of vbeln .
    w_output-vbeln = w_order_data-vbeln .
      CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
        EXPORTING
          salesdocument    = w_order_data-vbeln
          order_header_in = w_ordhdr
          order_header_inx = w_ordhdrx
        TABLES
          ORDER_ITEM_IN    = i_orditem
          ORDER_ITEM_INX   = i_orditemx
          return           = i_bapiret.
      READ TABLE i_bapiret WITH KEY type = c_error
                           TRANSPORTING NO FIELDS.
      IF sy-subrc EQ '0'.
        move 'Order Reason for rejection update Failed' to
        w_output-message .
      ELSE.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            wait   = c_check
          IMPORTING
             return = i_return.
      move 'Order Reason for rejection update successful' to
      w_output-message .
     endif .
     refresh :i_orditemx , i_orditem .
    Endat .
    APPEND w_output TO i_output.
    CLEAR w_output.
endloop .
ENDFORM.                    " order_reason_for_reject

Remove Reason For Rejection From Sales Order Using BAPI_SALESORDER_CHANGE

Similar Messages

Maybe you are looking for