Lead Reject Reason Code

In the out of the box lead process in CRM OnDemand, when you click the reject lead button you are taken to an unconfigurable form and asked to enter a lead reject reason, when you click save this information is then appended to the end of the comments field.
Because it is in the comments field it's difficult to report on, and because its free form it's difficult to analyze. Has anyone come up with any workable ideas on
1) how to either analyze lead reject information
2) report on lead reject information
3) a different way to collect lead reject information

Hi, Its so interesting. We had the same requirement with one of our clients. We came up with a custom solution, which would support a picklist for reject reason and would solve the reporting issues as well. Here is what was done
- Ended up not using the oob reject button
- created 2 custom fields on the lead page. 1 for reject reason , 1 for status,
- We also hid the oob status field and made the custom status field update through wf, when the lead is rejected, converted etc..
This worked out well. Hope this will help

Similar Messages

The system shall allow for reporting by rejection reason code

Allow the reporting of a reason code when an order is rejected for the purpose of tracking lost sales
The system shall allow for reporting by rejection reason code to allow for tracking lost sales.

A custom ABAP will have to be developed looking at table VBAK and VBAP to determine the reason for rejection, then group it by order number.

Delete codes for rejection reasons in customizing

Hello,
We had some rejection codes, that we used for our sales orders.
Now we want to delete all these codes in customizing step, because we won't use them anymore.
Will it cause any trouble for my SD documents, that the deleted rejection codes have already been used for?

If you still have active documents with the deleted rejection reasons then you will almost certainly have problems trying to process them further.
1. If the document has been rejected you probably will not need to process it further anyway.
2. If you do encounter a problem, I expect you would be able to select a different rejection code.
If you are worried, you should test in a sandpit client.
Deleting reason codes which have been used is really not good practice, hence my suggestion that you change the descriptions.

How to set default reject reason in VA01 (create sales order)

Hi
Everybody can tell me how to set default reject reason for item in sales order.
in our sap system there are a default reject reason as '90'. We want to set it as "Null".
Thanks
Henry

Hi,
Assigning a default Reason for Rejection is not in standard SAP. I am sure there is some enhancement/user exit which updates the reason for rejection.
Please get the help of an ABAPer, create the sales order in debugging mode and he will find out the logic behind the automatic reason for rejection.
Before that you can find the exits in the include MV45AFZZ for any code related to this.
Hope this helps

STATUS_READ & line item rejection reason - too complex

Hi All,
I have to trigger an output to a smartform via an output routine. I have to do the following checks in my output routine before I decide to propose the output or decline to propose the output if conditions fail.
1. Order header can have status PEND, Hold, Release. IF the status has changed to anything else except pending, i should propose output.
2. Again if a line item is rejected with certain reason code, then also I have to propose the output.
Both the above conditions must be checked before proposing the output. My issue is how do I know what was the old value of status and rejection reason.
I tried using FM STATUS_READ, but it does not give something like this was the old value and this is the new value. I do not find any FM to get item rejection reason. Do I have to use change documents for these.
examples
a)Order with 2 Framing Configurable Line Items. The user status of the order is changed from PEND to QAHD. The standard order output label is proposed for both line items on the order. At a later time, one of the line items is rejected for reason 90 (for example). At that time a new label is created, just for that specific line item with the rejected artwork text on the label.
In this case if I use STATUS_READ, i will get active status as QAHD, so I will try to propose normal output so I am fine. Later when the item is rejected, I will again get staus as QAHD and I will propose output for one unrejected item which is WRONG. I had already proposed the output in past, so I should not. I should only propose output for the rejected item.
b)Order with 2 Framing Configurable Line Items. The user status of the order is still in a PEND status. The user changes one of the line items to a rejected for reason 91 (for example). A label is printed just for that line item with the rejected artwork text on the label. At a later time, the user status on the order is changed from PEND to QARD. A label will print, only for the unrejected line item and the label is the standard order output label for HJ.
In this case I do not know where to get the old rejection reason of item. If I do a database select, I will get current rejection reason 91, but how do I know if I had already proposed the output or not for a certain item.
c)Another scenario to think about is that there is nothing preventing the user from setting a rejection status on an item and changing the user status at the same time and saving it. In that case we would want only one label per piece (the rejected label for the rejected item and the standard label for the non-rejected item).
I think I have to check the time order was updated and do something like that.
All inputs are welcomed.
Thanks
Pulin

Write the code like
concatenate 'OR' int_orders-aufnr into d_objnr.
    call function 'STATUS_READ'
         EXPORTING
              client          = sy-mandt
              objnr           = d_objnr
         TABLES
              status          = t_status
         EXCEPTIONS
              object_not_found.
Read table t_status with key stat = 'I0076'.
if sy-subrc eq 0.
do not print output.
endif.
Thanks
Seshu

Multiple reason code in payment advice

We have requirement to put multiple reason code at the time of cash application which we can do manually via f-28 and via payment advice
F-28 is working fine but payment advice is not
Steps
Booked AR invoice of $1000
Create payment advice of $1000 with below line item and reason code.
AR Cr 200$ with reason code p1
AR Cr 300$ with reason code p2
AR Cr 400$ with reason code p3
AR Cr 100$ with reason code p4
Apply cash using payment advice.
Issue
The first line of payment advice is booked as on account AR Cr 200$ without reason code p1 and residual is created for other 3 lines
I am expecting the result should be that it should create residual for all the 4 lines with correct reason code.
Expected result
AR Cr 200$ with reason code p1
AR Cr 300$ with reason code p2
AR Cr 400$ with reason code p3
AR Cr 100$ with
Is it something i am missing at the time of creating payment advice or applying cash.
I tested and had issue with the first item of payment advice. There should be something I missed in the payment advice creation .
Thanks in advance for help.
AB

Hi,
What you could possibly do if the reasons for rejection are similar for each lot is to create these combinations as UD codes and assign them to your selected set. Else you could record the reasons for the rejection in the long text and display this long text on your reporting.
Regards,
Roderick

Quality Rejection reason

Dear Sir's,
Our user wants to see the Rejection reason in stock report i.e MB52,MB51.
Is it any t-code where we can seen the Block stock with rejection reason.
The rejection reason feed at the time of "Usage Decision".
Please suggest me.
Thanks in advance.
Regards
Ajit Sharma

Hi Ajit,
It is not possible to view the rejection reason in MB52 as it is a Stock report.
You can get the rejection reason details in Reason for Movement column in MB51 report.
Thanks & Regards
V.Devaraj

Multiple Reason Code in UD

During UD, is it possible to select more than one reason code for rejection.
I wanted to reject inspection lot for more than 1 reason.
How to do this?
Rkumar

Hi,
What you could possibly do if the reasons for rejection are similar for each lot is to create these combinations as UD codes and assign them to your selected set. Else you could record the reasons for the rejection in the long text and display this long text on your reporting.
Regards,
Roderick

In Authorization task, require entry of a Reject "reason" ?

In Authorization task, require entry of a Reject "reason" ?
When the Authorizer "Rejects" an authorization task, we want to require entry of the "Reject Reason".
The only thing we've thought of so far is to have a field that's mandatory during that moment...but we don't want them to have to enter anything if they "Approve", so we really want that field to be 'conditionally mandatory'....based on which button they click...

We are also trying to implement the similar functionality. I have overwritten the confirm_action() function the code to take of the requirement i.e., showing a textarea while in authorization phase and making it mandatory while the user hits 'Reject' button. But the issue that I am seeing is, this textbox is becoming mandatory for 'Reject' button, but it is not storing the user comments when it was rejected. Also, this textbox is becoming mandatory, when the user hits the 'Approve' button as well, but doesn;t insist the user to fill in. Any help in achieving this function is greatly appreciate.

Incoming payment by F-28: Reason code error while posting

Hello everyone,
I want to post Incoing Payment using F-28 net of TDS. I want the separate GL account to be picked up automatically for the difference when I enter the Reason Code 003.
I did the following customization for the same.
1. Financial Accounting> Accounts Receivable and Accounts Payable> Business Transactions>Incoimng Payments> Incoming Payments Global Settings>Overpayment/Underpayment> Define Reason Codes:- Here I selected the Indicator 'C' for reason code 003 which is for "Indicator: Charge off difference via separate account". The reason code 003 is for TDS Netted
2. Below the Define Reason Code node, I selected the node 'Define Accounts for Payment Differences' . Selected the key ' Rules' and selected the checkbox 'Reason Code'. Then clicked on 'Accounts' and enetered the desired GL account against the reason code '003'.
After doing the above customization I posted the Incoming payment using T code F-28. I entered the difference in the field 'Difference Posting'. Then entered reason code '003' which is for 'TDS netted' in the field 'Reason Code'. Now, I am getting the follwoing error.
Reason codes with automatic charge-off are not permitted here
Message no. F5605
Diagnosis
The reason code entered is designed to ensure that the payment difference amount is posted to an account specially set up for this purpose. Postings of this nature usually require additional specifications (e.g. tax code, business area). If the difference stems from a single open item, the necessary specifications can be taken from that item. In the case that led to this error message, however, the difference does not stem soley from one item, which means that this method cannot be used.
System Response
The reason code entered is not accepted.
Procedure
You can either select a different reason code, which would create a new open item for the customer or vendor OR write off the difference using the function Charge off diff.. This function either takes you into a pre-configured account assignment model or into the document overview. From here you can enter the required difference postings.
How can I proceed ahead?
Thanks and Regards,
Pradnya

Hi Saulo,
Thanks for ur reply.
I had alreay done the config in OBXL and OBBE. Only thing I wanted to know is while posting Incoming Payment by F-28, how to use this reason code.
Ur reply was a gr8 help for me.
Regards,
Pradnya

Clearing Payment to a G/L account set up in Reason Code

I am having a problem posting an overpayment/underpayment to a G/L account using a reason code. What I am attempting to do is, using F-28, have the remainder of an underpayment post to a G/L account attached to the reason codes. What I need to have work is that in F-28 I do not want to have to enter any data on what the residual amount is, it should just take whatever is not paid and apply it to the G/L account tied to the reason code. I have set 3 new reason codes in OBBE to test different possibilities with the checkboxes in that transaction, and have attached each of the reason codes to accounts using OBXL. What is happening now is that when I enter a short pay amount for an invoice and I enter a reason code in the RCd field in the residual tab - I hit save and it seems to try to attach the remaining amount to an account that is currently tied to a blank reason code in our setup in OBXL. I would think that since I am placing a code in the RCD field, that it would use the account tied to that. I have also tried to use the reason code field below, but encounter the same results or, with one of my codes that has the "charge off difference via separate account" checkbox checked, it will not allow that code in that field below.
There must be a way to take the shortpay amoun,t and without entering the residual amount anywhere, use the G/L account tied to the reason code to post the remainder to. Can anybody help on what I may need to do to get this to work?
Thanks -
PS. This is not a tolerance issue as I have set the tolerances for both the customer and the user high enough to allow under/overpayments.

No... this is SAP standard.... if you are treating them as residual payment and the GL is seperate than the small diff GL we have to enter the amount there..... as system cannot understand whats the differnece when we dont put the amount there......
we can always see the field NOT ASSIGNED in the bootom.. it is just the matter of copy paste for the user.... it has to come thro user discipline.... i dont see a standard sap way of doing it,....

Sales orders with rejection reason in R3 are not nullified in BW

Hi,
Actaully One sales order xs26665 has been uploaded into BW from R/3 with OrderQty 100
After cancellation of same order xs26665 in R/3 by putting Rejection Reason, R3 extractor is generating two records as specified
1st record specifies order xs26665 with Order Qty = -100
2nd record specifies oredr xs26665 with Order Qty = 100 and updating filed "reason for rejection" = EQ.
Because of this two records which are generated in R3 after cancellation which are loaded in to BW, The value of Order Qty for sales order xs26665 is not geting nullified and it still shows final value which is = 100 as order qty.
This records is first geting uploaded in to ODS and further in to a cube in BW using deltas.
Rgds,
C.V.
Message was edited by:
C.V. P

Hi CVP,
make sure that the datasource that you are extracting the data from has got the field ROCANCEL and that the keyfield Quantity is marked or checked in the column Inversion.,.. (3rd field in your datasource... Selection Hide Inversion & Field Only).. There check the Inversion box for your Quantity field... only on enabling this would your Quantity in BW get negated... The cancelled order would then be marked as 'X' for the field ROCANCEL which inturn would be picked up by the BW through the InfoObject 0STORNO..
Hope it solves your issue...
Regards
Manick

Two deductions for invoice with same reason code posted as one line item

Hi
We have a scenario wherein we are taking two or more deductions on the same invoice and are using the same reason code which have a setting of charge off.
SAP system displays the FI posting with same reason codes with charge off setting as one line item.
However we want the FI Posting to display separate line items per deduction and not combine amounts of deductions based on same reason code with charge off setting.
Any comments are appreciated.
Edited by: Kirti Bhardwaj on Jul 24, 2011 9:46 AM

Hi,
you can use different reason codes in distribute differences screen once you have fist selected one reason code for one invoice.

Validation at line item level for F-32 to input Reason code

Hi Gurus,
I would like to write a validation / substitution for F-32 transaction code where in the Reason code field need to be mandatory field (With out input in to this field value the user should not come out of the transaction)
Please guide me how to write validation with out user exit
Thanks

Hi Suresh,
I guess the idea of MEENAKSH is good, perhaps you have an error in the Tcode, because in table BKPF the Tcode stored is FB1D and not F-32 :
So put the following in GGB0 and check again :
Prerequisite :
BKPF-TCODE = FB1D
Check :
BSEG-RSTGR <> ' '
Message :
Error : Reason code required
in the other hand, you can active a trace in GGB0 (Menu > Extras > Activate trace) to see what's the exactly the error
So it's not a question of screen.
Regards.

Is there a way to hide some reason codes in dispute management without deleting?

Within SAP Dispute management (UDM_DISPUTE) we would like to remove some of the available reason codes in the drop down on the search screen and available to assign drop down, but not physically delete them. Is there a way to do this?
I know if I physically delete them out of the Reason code list (SPRO -> FSCM -> dispute management -> Dispute Case Processing -> Case types -> Create Values for Attribute "Reason") then if an old dispute case that used that reason code is displayed, the four digit number code will be displayed rather than the description. So we would prefer to not physically delete the code / description from the reason codes but somehow make them non-display, or inactive.
Any thoughts on this?

Hello Stephen,
you may consider the functionality "personal list", putting all valid reason codes in and leaving out those you do not want to show. Maybe your Authorisation / Security Team can also help you performing this exercise for all affected users at once.
Regards,
Christoph

Lead Reject Reason Code

Similar Messages

Maybe you are looking for