How to enable field "reason for rejection" of view "status" in CRMD_ORDER

Hello Everyone
I need to activate/enable field "Reason for Rejection" in view "Status" of transaction CRMD_ORDER though a delivery document is created for the sales order.
Can some one pls let me know where do I need to code to make field "Reason for Rejection" enabled.
FYI, the same logic was applied for VA02 as well and the logic is written in userexit "USEREXIT_FIELD_MODIFICATION" which is working fine.
Apprecriate your quick response.
Thanks
Dharma

Hi Raj,
Usually we use function module CRM_STATUS_UPDATE to
change user status in document. But if you want to
trigger next process or change from certain user status to next status interactively by the system, you can
use Badi CRM_ORDER_STATUS (here you have after and before
method).
Hope this could help.
Rgds,
Gun.

Similar Messages

How to sets the Reason for Rejection of the Open Sales Order Lines

Hello gurus,
          I want to set the Reason for Rejection of the Open Sales Order Lines, Case is like :
If current date is exeed the Auto Void Confirmed Back Order Days(for item level) + date (last responding from customer), then reason for rejection should be set, So i want the logic to find out the date is exceed or not.
Thanks
Anjana

Hello anjana,
   Actually your question is some confusing, but if u want to get eldest change as active sales order then logic is as follows:
1. On base of OBJNR u have to get UDATE from JCDS table
2. then write logic as:
SORT i_jcds BY objnr stat chgnr DESCENDING.
      LOOP AT i_jcds INTO wa_jcds1.
        CLEAR lv_stat.
        lv_stat = wa_jcds1-stat.
        AT NEW objnr.
          AT NEW stat.
            CLEAR: wa_tab.
            wa_tab-objnr = wa_jcds1-objnr.
            wa_tab-stat = lv_stat.
          ENDAT.
        ENDAT.
        IF wa_jcds1-inact = 'X'.
          CLEAR lv_tabix.
          IF sy-tabix > 1.
            lv_tabix = sy-tabix - 1.
          ELSE.
            lv_tabix = 1.
          ENDIF.
          READ TABLE i_jcds INTO wa_jcds2 INDEX lv_tabix.
          IF sy-subrc = 0.
            wa_tab-chgnr = wa_jcds2-chgnr.
            wa_tab-udate = wa_jcds2-udate.
            wa_tab-utime = wa_jcds2-utime.
            APPEND wa_tab TO i_tab.
          ENDIF.
          CONTINUE.
        ELSE.
          wa_tab-chgnr = wa_jcds1-chgnr.
          wa_tab-udate = wa_jcds1-udate.
          wa_tab-utime = wa_jcds1-utime.
        ENDIF.
        AT END OF objnr .
          AT END OF stat.
            APPEND wa_tab TO i_tab.
          ENDAT.
        ENDAT.
      ENDLOOP.
      DELETE ADJACENT DUPLICATES FROM i_tab COMPARING objnr stat.
      SORT i_tab BY objnr stat udate utime.
      DELETE ADJACENT DUPLICATES FROM i_tab COMPARING objnr.
3. now in i_tab table u'll get eldest UDATE
Hope its work for u.
Thanks & Regards,
Sumit Joshi

Open outbound delivery/reason for rejection

Hi,
we have the issue, with open documents in SD, which looks like open in SAP treasury module
I try to reproduce the issue:
1.VA01- standard Order
2. VL01N - otbound delivery
3. VF01 - Invoice
4.VF11 - Cancel invoice
5. VL09 - Reverse good movement
And the result of this case is that all document are completed or cleared except Outbound delivery, which is open and has status A - Not yet processed...
In SAP Treasury looks standard order items as open....
There are no possibility to set field Reason for rejection in Sales order, because this field is not ready for input.
Any help how to solve this issue.
Thanks
Petr

also consequent invoice and cancelled invoice will be deleted and we lost the history
Not sure what do you mean by cancelled invoice would be deleted, which is not possible. For information, if you check the document flow for a sale order, you can very well see the invoice and subsequent cancelled invoice but of course, you cannot see the delivery if it is reversed and deleted.
G. Lakshmipathi

Change System Status of SO item dynamically based on Reason for Rejection

Hi ppl,
Our SAP user has raised a requirement as described below:
In sales order (in creation mode (VA01) or change mode (VA02)), if at the item level, the reason for rejection is mentioned, then the system status for that item should be automatically set to Technically Complete SET (TECO); and if the user removes the reason for rejection for the item, then the system status Technically Complete should be RESET automatically.
We are looking for any user-exit or BADI available which would be allow this dynamic change of system status based on the reason for rejection field. (No manual interaction for setting or resetting the system status).
Technically, the functionality is based on the below fields:
Reason for Rejection: VBAP-ABGRU
System Status: JEST-STAT
Please provide suitable inputs.
Thanks,
Dawood
Edited by: Dawood.S.Ghasletwala on Jun 29, 2009 3:14 PM

program: SAPMV45A
User exit: USEREXIT_SAVE_DOCUMENT_PREPARE.
loop at xvbap where updkz NE 'D'.
if not xvbap-abgru is initital.
"set your system state here.
else.
"reset your system state here.
endif.
endloop.
hmmm you can as well try if you got all you need to know already in userexit: USEREXIT_CHECK_VBAP.
Edited by: Florian Kemmer on Jun 29, 2009 11:53 AM

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

How does the field ABGRU-Reason for Rejection get populated in routines

Hi All,
How does the field ABGRU-Reason for Rejection get populated in routines(VOFM)?
BELNR,KPOSN,etc...fields are populated through KOMK and KOMP structures, similar way what structure is used for ABGRU?
by the time the control from VA01 comes to routine the values of VBAK and VBAP are cleared, so these structures like KOMP and KOMK are used.
Thanks in advance.

You need to add rejection reason field ABGRU as a new field to pricing field catalog (KOMG structure) through APPEND structure KOMPAZ. KOMG inherits new fields from KOMKAZ (for header level fields) or KOMPAZ (for item level fields) structures and it is not directly modified but through KOMKAZ and KOMPAZ structures
Since VBAP-ABGRU can vary from item to item, add it to item pricing communication structure KOMPAZ in SE11. Once KOMPAZ is added with new ABGRU field and activated it will automatically appear in pricing field catalog (KOMG)
Afterwards the ABGRU field will then start to appear in the field catalog where you can create condition table (V/03) including the ABGRU as a field. Once done the rest is assigning the condition table to access sequence which is in turn assigned to the relevant condition type that you want to price based on partner function (all under IMG -> SD -> Basic functions -> Pricing -> Pricing control)
In the pricing user exit userexit_pricing_prepare_tkomp in include MV45AFZZ, you will need a few lines of coding to fetch VBAP-ABGRU for the item and pass it to tkomp-abrug field. This will then be used by system to read the new condition table that you created.
tkomp-abgru= xvbap-abgru
So if you populate special pricing based on ABGRU (with possibly other conditions) in the condition table then that condition record will be read for the corresponding condition type.
You would of course need a developer to modify KOMPAZ structure and code the user exit for moving the rejection reason to tkomp
That is in short how you can achieve this

How can I disable the Reason for Rejection field in VA02 line items

Hi,
I dont want the users to be able to change the reason for rejection field in the sales order line items. Can someone please suggest a tried and tested way of doing this
Thanks for reading.

Set up an auth object for the field. In userexit field modification check the auth object and set the field to be grayed out if they don't have authority. Users can then not change the value of the field Sample code
IF screen-name = 'VBAP-ABGRU'.
       AUTHORITY-CHECK OBJECT 'Z_BLK_REAS'
               ID 'ABGRU' DUMMY.
      IF sy-subrc EQ 0.
        screen-input = 1.
      ELSE.
        screen-input = 0.
      ENDIF.
ENDIF.

How can I pass value in status and reason for rejection using BAPI_LEAD_CREATEMULTI when creating multiple lead

Hello,
I want pass value in STATUS and Reason for rejection according to requirement when i am creating multiple lead using BAPI_LEAD_CREATEMULTI. Please help me how can i pass value. Please give some sample code that in which table i have to pass values and please also tell me INPUT_FIELDS values. Please help me
Regards,
Kshitij Rathore

Hello,
Please help me for solve this problem. I am trying to solve problem from last 4 days but i didn't get any solution.
Regards,
Kshitij Rathore

Workflow : How to put condition on Reason for Rejection ( BUS2032 ).

Hi Experts,
The situation is :
I am trying to implement a condition on "Reason for Rejection" . If there is any change in the " Reason for Rejection " ( VA02 ) tab of a particular item , a mail should be sent to a particular person . How do I design a condition so that it would trigger a mail. What all information do I need. A clear suggestion would be very helpful.
Previously we created a workflow in the " BUS2032 " on " CHANGED " event. I tried to get item level information ( old and new ) from the same Bussiness Object. What do I need to do to get the information ( old and new ).
Thanks in advance,
Raghava Vakada.

Hi Experts,
Please very very urgent,
It is very helpful to me,
<b>Please Please.......</b>
Thanks in advance,
Raghava Vakada

How to add new tab after reason for rejection tab using tcode va01

Hello,
how to add new tab after reason for rejection tab using tcode va01.

Hi,
You can check this link...
Hope it will be helpful to you.
[https://forums.sdn.sap.com/click.jspa?searchID=23016273&messageID=6825861]
[http://www.sapdevelopment.co.uk/enhance/fexits.htm]
-Maharshi
Edited by: Maharshi Vyas on Mar 3, 2009 12:45 PM

How add new tab after reason for rejection tab using tcode va01

Hello,
How to add new tab after Reason for Rejection tab using tranzaction code VA01.
pls suggest solution.

I don't think you can add a tab after reason for rejection tab. There are custom tab, which you can use for your convenient, given by SAP. You can look into the below details:
Program : SAPMV45A
Screen: 8459(Item) and 8309(Header).
Kuntal.

How to put Reason for rejection to line item level?

Hi
I am updating the Sales order at line item and putting the reason for rejection but it didnt updates the database. Below is the code.
      LOOP AT LT_VBUP1 INTO WA_VBUP1.
         ON CHANGE OF WA_VBUP1-VBELN.
          CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
            EXPORTING
              SALESDOCUMENT    = WA_VBUP1-VBELN
              ORDER_HEADER_INX = LV_ORDER_HEADER_INX
            TABLES
              RETURN           = IT_RETURN
              ORDER_ITEM_IN    = IT_ORDER_ITEM_IN
              ORDER_ITEM_INX   = IT_ORDER_ITEM_INX.
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
            EXPORTING
              WAIT = 'X'.
          CLEAR WA_TY_SOCLOSE.
          IF SY-SUBRC EQ 0.
            LT_TY_SOCLOSE-VBELN = LV_SALESDOCUMENT.
            LT_TY_SOCLOSE-STCLOSE = 'Y'.
          ELSE.
            LT_TY_SOCLOSE-VBELN = LV_SALESDOCUMENT.
            LT_TY_SOCLOSE-STCLOSE = 'N'.
          ENDIF.
          APPEND LT_TY_SOCLOSE.
        ENDON.
        CLEAR: WA_ORDER_ITEM_IN,WA_ORDER_ITEM_INX.
        WA_ORDER_ITEM_IN-ITM_NUMBER = WA_VBUP1-POSNR.
        WA_ORDER_ITEM_IN-REASON_REJ = 'Y1'. " Putting order of rejection for the archiving
        WA_ORDER_ITEM_INX-ITM_NUMBER = WA_VBUP1-POSNR.
        WA_ORDER_ITEM_INX-UPDATEFLAG = 'U'.
        WA_ORDER_ITEM_INX-REASON_REJ = 'X'.
        APPEND WA_ORDER_ITEM_IN TO IT_ORDER_ITEM_IN.
        APPEND WA_ORDER_ITEM_INX TO IT_ORDER_ITEM_INX.
        CLEAR WA_VBUP1.
      ENDLOOP.
Correct me where I am putting wrong.
Regards
Mohinder

LOOP AT LT_VBUP1 INTO WA_VBUP1.
ON CHANGE OF WA_VBUP1-VBELN.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = WA_VBUP1-VBELN
ORDER_HEADER_INX = LV_ORDER_HEADER_INX
TABLES
RETURN = IT_RETURN
ORDER_ITEM_IN = IT_ORDER_ITEM_IN
ORDER_ITEM_INX = IT_ORDER_ITEM_INX.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT = 'X'.
CLEAR WA_TY_SOCLOSE.
IF SY-SUBRC EQ 0.
LT_TY_SOCLOSE-VBELN = LV_SALESDOCUMENT.
LT_TY_SOCLOSE-STCLOSE = 'Y'.
ELSE.
LT_TY_SOCLOSE-VBELN = LV_SALESDOCUMENT.
LT_TY_SOCLOSE-STCLOSE = 'N'.
ENDIF.
APPEND LT_TY_SOCLOSE.
ENDON.
CLEAR: WA_ORDER_ITEM_IN,WA_ORDER_ITEM_INX.
WA_ORDER_ITEM_IN-ITM_NUMBER = WA_VBUP1-POSNR.
WA_ORDER_ITEM_IN-REASON_REJ = 'Y1'. " Putting order of rejection for the archiving
WA_ORDER_ITEM_INX-ITM_NUMBER = WA_VBUP1-POSNR.
WA_ORDER_ITEM_INX-UPDATEFLAG = 'U'.
WA_ORDER_ITEM_INX-REASON_REJ = 'X'.
APPEND WA_ORDER_ITEM_IN TO IT_ORDER_ITEM_IN.
APPEND WA_ORDER_ITEM_INX TO IT_ORDER_ITEM_INX.
***********************************************************************<<<<do this bit here
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = WA_VBUP1-VBELN
ORDER_HEADER_INX = LV_ORDER_HEADER_INX
TABLES
RETURN = IT_RETURN
ORDER_ITEM_IN = IT_ORDER_ITEM_IN
ORDER_ITEM_INX = IT_ORDER_ITEM_INX.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT = 'X'.
CLEAR WA_VBUP1.
ENDLOOP.

Reason for rejection in ME28

Hi all,
How can I add an input enabled column where I can type the reason for rejection in the ALV display of ME28.
I can add the new field in structure MEREP_OUTTAB_PURCHDOC (via append structure) but how can I make it input enabled?
Regards,
Steph

I added an enhancement in the following:
include: LMEREPI20
method: get_fcat
code:
    LOOP AT my_fcat ASSIGNING <fcat>.
      CASE <fcat>-fieldname.
        WHEN 'ZZREASON'.
          <fcat>-edit    = 'X'.
      ENDCASE.
    ENDLOOP.

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

Reason for Rejection for blocking line item for delivery

Hi All,
I am working on this project where based on earlier configuration, by selection reason for rejection, delivery for line item is getting blocked.
I want to change this settings because reason for rejection should not be controlling the blockage it should be merely be the reason. Delivery should be blocked if it is blocked by selecting delivery block field in schedule line for the line item.
How can I change the settings for the reason for rejection?

Dear ankit.k.agarwal
If you assign a reason for rejection system will block the particular sales order and that sales order shouldn't be used any longer.
This is the standard SAP behavior and the program was written like that.
Still if you want to do , you have to go for an enhancement to change the standard program(It is not suggestible)
In stead you add a new field in sales order(field exit) and convince your key/core users to maintain the reason for rejection in that field .
Co ordinate with your technical team
Thanks&Regards
Raghu.k

How to enable field "reason for rejection" of view "status" in CRMD_ORDER

Similar Messages

Maybe you are looking for