Converting leads to opportunities - Value field

Hi,
I run monthly KPI's and one of them is the value of converted leads per month. The value that I am getting keeps changing from month to month & I am wondering where it is pulling the data from. Is it:
Value when converted
or
Value of resulting opportunity at the time I run the report
Any help would be appreciated.
Thanks,
Darren
Hi,
I'll try & explain this a bit better.
When I ran a 2 reports.
1.number of leads converted for the last few months
1.value of leads converted for the last few months
I ran the report 1 month ago and got the number 10 for August
I ran the report today & got number 2 for August.
Does anyone know why this number would change? I thought it would be from the date it was actually converted.
It does the same for values
Anyone know why this is??
Thanks
Edited by: Darren, on Nov 4, 2008 8:26 AM

Hi,
I'll try & explain this a bit better.
When I ran a 2 reports.
1.number of leads converted for the last few months
1.value of leads converted for the last few months
I ran the report 1 month ago and got the number 10 for August
I ran the report today & got number 2 for August.
Does anyone know why this number would change? I thought it would be from the date it was actually converted.
It does the same for values
Anyone know why this is??
Thanks

Similar Messages

How do I convert the ASCII character % which is 25h to a hex number. I've tried using the scan value VI but get a zero in the value field.

How do I convert the ASCII character % ,which is 25h, to a hex number 25h. I've tried using the scan value VI but I get a zero in the value field.

You can use String to Byte Array for this.

Add/ remove field on "Convert Lead"

Hi All,
Is it possible to edit/ remove field present on "Convert Lead" page.
When we try to convert a lead to opportunity on the "Convert Lead" page we can view below fields under "Opportunity" section
Do Not Convert to Opportunity // Auto-Create New Opportunity //Opportunity Name //Revenue //Close Date//Next Step //Description.
Is it posible to add or remove any fields.
thanks

Not in the current release this will be available on version R17 which will begin roll-out in March for the first PODS.
In R17 you will be able to customise this alot more.

Assignment of leads and opportunities by product

Hello everyone,
I need to assign leads and opportunities by product to selected personnel, is there anyway to detect more than 1 product in the lead or opportunity? This is because a lead and opportunity may have several products bundled together and it would be very repetitive for the sales person to create one lead\opportunity for each product they sell to the same customer.
Any ideas on how to accomplish this? I was initially thinking of using Books, but it allows for only field comparisons of single values and not multi-picklists. So in the end the problem still comes back to having more than 1 product in a lead\opportunity.
Hope you guys here have some suggestions. Thanks again!

Hi Venky,
Yes, the initial thought here is to use a multi-picklist; but unfortunately I don't think the assignment manager supports multi-picklists.
And yes, I would like to make it accessible to multiple people, not only one.
Basically, the process goes something like the following:-
1) Marketing obtains lead and enters into the system
2) Lead is channeled to a product manager
3) Product manager reassigns the lead to a salesperson
4) Salesperson converts the lead into an an opportunity - Product Manager should be able to view this opportunity
My question here is would the product manager still gain access to the lead once it is reassigned (salesperson is not reporting to the product manager in anyway)? And how can the product manager be able to view all opportunities which have the product he\she is in charge of?
My initial thought here is that we have to fall back on using Books?
Thanks.

Error converting leads; SBL-DAT-00553

In addtion to the SBL error code, the error also reads: Operation failed: Read Record type partner; Access Level No access
Is there some correlation between Leads and Partners that occurred in R20?
Addtional information
Recently there are some users that are unable to convert leads. It seems there are some users with the same role can convert leads while others cannont
The user is the owner of the lead, contact, opportunity and account.
Owner access profile --accounts and opportunities have a realted information section for Distributors. the access on the objects are read/edit/delete and the RI section for partners has been changed to Full
Could not find assocaiton between Lead and Contact to Partners
In the SR -- it was suggested that the required fields on the opportunity must be populated...however this is not the case. There are fields that are not present on the lead that are required fields for the opportunity and users can convert leads without these fields. As noted above checked the owner profile access. the role 'has access' to all the record types and 'can create' privleges

Folks,
We have encountered this issue as well and have worked through the recommended corrective steps above (excluding reimporting which is not a viable option with the number of users and contact records we have).
We have also confirmed that any relative related information fields are not read-only on our page layouts; however, we have obtained no resolution. We will open a SR with customer care; however we are wondering if anyone on the forums here has a definitive corrective resolution for this specific access denied error.
From the contact record level, the only way we are able to associate an account is to be the logged user whom also owns the contact record.
We are able to associate the contact if we are under the account, even if we do not own the contact record. So, the reverse holds true as to associating a contact from the account while the user is NOT the record owner.
Any additional insight would be appreciated.
~Jennifer~

Pring VALUE field as blank, if it's worth is 0.00

Hello,
I have value field (DATA: V_Net_Value TYPE KONV-NETWR) in my ALV grid display report. When i dont have any value, am getting 0.00 as output in my ALV report, but, user would like to see it as blank/nothing. Because of some reasons, i can not use a CHARACTER type field for outputting in order to get blank in ALV. Pls. let me know is there any other option/flag to get my requirement.
Thank you

There was a similar question which was discussed long back. You can check the idea suggested by Sourav Bhaduri here Replace amount in OOPS ALV
It sounds promising. I had not got a chance to try it till now. Other than this i donot see any other way( without converting it to type C ).
Just try like if input = '0.00' then output = space.

Delete COPA value fields in a productive system

Does anyone have practical experience with deleting COPA value fields in a productive system?
The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
Cheers, Peter

To delete characteristics or value fields, you should perform the following
activities:
1. Delete the corresponding characteristics and value fields from
Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use
the appropriate where-used list in the Customizing Monitor. You can
access it by choosing Tools -> Analysis -> Check Customizing Settings
(TA KECM).
You can jump directly from the where-used list to the relevant
Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an
operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the
operating concern before making any deletions, effect those changes and
save the data structure.
4. In order to be able to select the fields of the data structure,
choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove
them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking
whether the operating concern contains any data and whether the fields
to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the
re-activation. If the operating concern does not contain any data or
does not require the database system to be converted, the tables are
activated. You are then able to activate the environment for the
operating concern. In this case, the following activities no longer
apply.
If the operating concern already contains data, a system message tells
you that the database needs to be converted. If you proceed, an
activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages
telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can
be converted. In this case, you should answer "No" to the next prompt,
which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the
tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted
is shown for this. If the tables only contain a small amount of data
(less than 10 000 records), then all the tables can be converted in one
job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating
concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during
the conversion.
A copy of the table is generated during the conversion. The database
system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the
"Refresh" icon. Tables disappear from the list once they have been
converted sucessfully. If a conversion is taking a while, it is also
possible to leave the transaction. You can then continue the conversion
using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services ->
Jobs.
Using the database utility transaction. You access this by choosing
Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating
concern during operating concern maintenance. You need to activate all
tables after conversion.
11. To analyze errors that have occurred during the conversion, you can
use the database utility transaction by choosing Extras -> Logs. The log
has the same name as the conversion job: TBATG-date. You can also
restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application
help while still in the above transaction.
12. Once you have activated all the tables in the operating concern,
generate the operating concern environment from within operating concern
maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->
Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
Hope it helps

Remove Value Field from Operating Concern

Hi all,
I created a new value field in DEV and assigned it to the corresponding Operating Concern.
Now, after some discussions, it is not necessary this value field.
I want to "un-assign" from the Operating Concern they use.
No data is being posted to this value field and nothing has been transported to QA yet.
Is this possible? Any ideas?
Thanks and Regards,
Flower.

I guess you can delete the value field as it was not transported to QA and PRD.
Here is some information given by SAP.
Deleting characteristics/value fields from an operating concern
You can delete characteristics and value fields retrospectively from an operating concern that you have already activated. However, you should only use this deletion function for operating concerns that have not yet been used productively. You should also note that some database systems require the operating concern tables to be converted (database conversion) after the deletion has taken place if data had already been posted to the operating concern. Depending on the data volumes involved, the database conversion can take a matter of seconds or indeed several hours. Moreover, you cannot post data or run reports during the conversion. Due to integration, other applications are also affected when data is postedwith an assignment to profitability segments (such as settlement and direct assignment from FI/MM). If the operating concern has been transported to another system (such as the productive system), then the database conversion must also occur in that target system.
Depending on the fields that were deleted, the following tables need to be converted (where xxxx = operating concern):
Characteristics: CE1xxxx, CE2xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Amount fields: CE1xxxx, CE2xxxx and CE3xxxx
Quantity fields: CE1xxxx, CE2xxxx, CE3xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Before deleting fields from an operating concern with a large data volume (more that 10 000 records in a table), you should refer to the section "The Database Utility" in the ABAP dictionary documentation. This section describes the database conversion process.
For database systems that do not require conversion (such as DB2 for AS/400, Informix, MSSQL), it can still take a considerable amount of time for the operating concern to be activated.
To delete characteristics or value fields, perform the following activities:
1. Delete the corresponding characteristics and value fields from Customizing in all clients (this includes forms, reports, planning layouts, and so forth). To locate characteristics and value fields, use the appropriate where-used list in the Customizing Monitor. You can access it by choosing Tools -> Analysis -> Check Customizing Settings. You can jump directly from the where-used list to the relevant Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the operating concern before making any deletions, effect those changes and save the data structure.
4. In order to be able to select the fields of the data structure, choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking whether the operating concern contains any data and whether the fields to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the re-activation. If the operating concern does not contain any data or does not require the database system to be converted, the tables are activated. You are then able to activate the environment for the operating concern. In this case, the following activities no longer apply.
If the operating concern already contains data, a system message tells you that the database needs to be converted. If you proceed, an activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can be converted. In this case, you should answer "No" to the next prompt, which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted is shown for this. If the tables only contain a small amount of data (less than 10 000 records), then all the tables can be converted in one job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs. However, you should ensure that table CE4xxxx (where xxxx = operating concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during the conversion.
A copy of the table is generated during the conversion. The database system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function. You can display the current status of the conversion by selecting the "Refresh" icon. Tables disappear from the list once they have been converted sucessfully. If a conversion is taking a while, it is also possible to leave the transaction. You can then continue the conversion using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services -> Jobs.
Using the database utility transaction. You access this by choosing Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating concern during operating concern maintenance. You need to activate all tables after conversion.
11. To analyze errors that have occurred during the conversion, you can use the database utility transaction by choosing Extras -> Logs. The log has the same name as the conversion job: TBATG-date. You can also restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application help while still in the above transaction.
12. Once you have activated all the tables in the operating concern, generate the operating concern environment from within operating concern maintenance.
You can then use the operating concern again.
If you want to transport the operating concern into a different system, see the section "Notes on transport"
Note
Hope this helps
Thanks,
Reddy
Edited by: reddy sap on Sep 11, 2009 6:58 PM
Edited by: reddy sap on Sep 11, 2009 7:00 PM

Printing value fields with negative sign??

Hello Experts,
I have developed a interface, which writes the invoice data to application server/unix, this is a notepad. My specifications are as below,
MWSK1(2)   TaxCode                         65     2     KONV-MWSK1
KWERT(13) Condition Value                  67     13   KONV-KWERT
KSTEU(1) Condition Control                80     1     KONV-KSTE
I have to print KWERT value from 67th position until 13 positions, meaning until 80 positions, fine. My code is as below,
MOVE: wa_invoice_price-mwsk1 TO unix_file+64(2).
WRITE: wa_invoice_price-kwert    TO unix_file+66(13) RIGHT-JUSTIFIED.
MOVE: wa_invoice_price-ksteu    TO unix_file+79(1),
So, it printing like below (pls. note 0.04 minus value in right bottom corner)
P26701ZCG620101006C          100.00         0.00USD 1    UGL            0.00A A 9
P60001ZF3520101006C          100.00         0.00USD 1    UGLG          0.04-H B 9
But, business want to have like below (pls. note the DIFFERENCE for 0.04 minus value in right bottom corner),
P26701ZCG620101006C         100.00        0.00USD 1    UGL               0.00   A A 9
P60001ZF3520101006C         100.00         0.00USD 1    UGLG             0.04 - H B 9
meaning, the 13th position should be negative sign (if at all any value does have a negative sign, else its normal)....so, the negative sign should sit on 13th postion. As am using WRITE statement with RIGHT JUSTIFIED am facing thisissue!! as u know we can not send a 'P' type value to unix/apps server, pls. let me know how to get it done?
Thank you

why can't the user live with a leading sign, like '-   0.04'? If possible, do
shift <fieldname> circular up to '-'.
Or, if value is less than zero, set another variable to '-', else set to space, and multiply value with '-1', like:
if <field> < 0.
   lv_sign = '-'.                " neagtive value
<field> = <field> * '-1'. "reverse the sign
else.
lv_sign = space.          "positive value
endif.
then, adjust your field length and insert a sign column or simply add a column for the sign....

Value Field Change

Hi Guys
In CO-PA Repots ABSMG Qty Value filed used upto till date in One report. ABASMG QTY is based on base unit of material Master
For example: i have 5 segments, 4 segments are in TO is base unit, 1 segment is in KG base unit in material master
4 segments sale qty is 100 TO, 1 Segment Sale qty is 100 KG. My total Sales Qty is 100.100 TO
i was developed one report Qty value field is ABSMG, in this report is showing Sales Qty is 200.
Now i was change the Qty Value filed, new Value filed is VV000. this value field is based alternative base unit
and done the custamization CO-PA QTY is TO.
In this new report showing correct sales qty figures from today.
My requirement is Previous sales qty (ABSMG) also convert in TO.
How can it is possiable..
Please provide the soluation
Please helpful on this issue. it is very high priority
Regards
SIVA N

Hi,
To regenerate the PA segments there is a function 'KE4S' for postings from SD. You have to cancel old documents and re-post. Try in your 'Test environment' and read the program <F1 help> for various fields on this transaction to know the impact. If you have too many documents, then please be aware that this option involves two more doument lines.
Please also check the function 'KE4MS' (Store Qty in COPA std.unit of measure) and read the IMG documentation (COPA->Flow of Actual values ->Initial steps). I'm not sure if this can work for past documents...Pls check and post back how it worked.
Hope this helps.

How can i avoid leading zeros for a field in smartform?

how can i avoid leading zeros for a field in smartform?

Hi,
Using the Symbols.
&symbol(Z)& Omit Leading Zeros &symbol(S)& Omit Leading Sign
&symbol(<)& Display Leading Sign to the Left
&symbol(>)& Display Leading Sign to the Right
&symbol(C)& Compress Spaces
&symbol(.N)& Display upto N decimal places
&symbol(T)& Omit thousands separator
&symbol(R)& Right justified
&symbol(I)& Suppress output of the initial value
Regards,
Shiva Kumar

KE30 - UOM Value Field required

Hi,
We have some FG Materials which are sold in PAC and EA. and PAC is Base Unit of Measure while EA is Alternative Unit of Measure.
In PA Report - KE30, system is accurately showing Sales Quantity but business wants to see UOM of Sales Quantity as well, means they want to see how much of same material is sold in EA and PAC. I have created customized Value Field (VVXXX) for UOM but my issue is how can i derive Base Unit of Measure and Alternative Unit of Measure to this Value Field as i need to see this in PA Report. I have checked T-Code : KEDR but i am not able to map value field there.
Kindly guide steps to solve this problem !!!
Thanks in Advance
Regards,
Sapna

I assume you have defined (at least) 3 quantity value fields in the operating concern. (The value fields shown below can be named as per your convention and may differ from these.)
VVIQT - Invoiced Quantity (in sales unit of measure) --> PAC or EA
VVPAC - PAC Quantity (base unit of measure = stock keeping unit)
VVEAQ - EA Quantity
The first two fields above are easily mapped in customizing transaction KE4MI via path:
SPRO > Controlling > Profitability Analysis > Flow of Actual Values > Transfer of Billing Documents > Assign Quantity Fields
Assign the following:
SD Qty Field     Name                       CO-PA Qty Field        Name
FKIMG              Billed Quantity          VVIQT                       Invoiced Quantity
FKLMG             Billing Qty in SKU     VVPAC                     PAC Quantity
To derive the third field try using customizing transaction KE4MS via path:
SPRO > Controlling > Profitability Analysis > Flow of Actual Values > Initial Steps > Store Quantities in CO-PA Standard Units of Measure
Assign the following:
Source Quantity      Description          Quantity     Description      Unit
VVPAC                    PAC Quantity      VVEAQ      EA Quantity     EA
The above option is to derive standard units of measure, such as KG. I'm not 100% certain it will work in your requirement to access the alternative units of measure conversion rates for a material (table MARM). If this configuration does not derive the EA quantity and units as expected, then the user exit mentioned previously can be used to fill the fields with the converted amount and unit.
Best regards,
Jeffrey Holdeman
SAP Labs, LLC

Executing SSRS using the 'label' field instead of 'value' field

Hi,
We have in house custom SSRS reports built for our clients and each of those reports have a 'label' field and a 'value' field. Now the 'label' field is something that the client sees on the UI as a friendly name. When a client runs the report, it gets executed
against the 'value' field and so I was wondering if there was a way to tell SSRS to execute against 'label' field as oppose to 'value'.
Appreciate your response!
Thanks,
Darshan

I found the solution!!! By design, SSRS will not convert Label to Values. You will need to write custom code to do this. You need to do the below
a) You need create an instance of
ReportingService2010
rs =
newReportingService2010();
b) Then you need to populate the ParameterValue[] array and populate the 'Name' and 'Value' (here the 'Value' is actually the Label that the client sees on the UI)
c) Assign the following
string report = "[report_path]";
bool forRendering = true;
string historyID = null;
DataSourceCredentials[] credentials = null;
ItemParameter[] parameters = null;
and then call parameters = rs.GetItemParameters(report, historyID, forRendering, values, credentials);
d) The above call gives you the Label-Value pair mappings within the "parameters" object and if you have cascading parameters, you will need to recursively call parameters = rs.GetItemParameters(report, historyID, forRendering, values, credentials); which
will give you the complete set of the Label-Value pair mapping.
e) You then iterate through the above collection and the get the Value for that Label and pass it on to SSRS
I have tested this internally on several reports and it seems to be working. I can now pass in the displayed values to our custom web services and the above steps take care of populating the Label-Value pair mapping and then calling SSRS with the actual
'Value'
Darshan Patel

CRM report combining leads and opportunities

Hi,
I have LEADS and OPPORTUNITIES data in different cubes which are getting data std datasources. Now how do i create a report which shows the list of leads converted to opportunities?

Hi Madhu,
If you are using DSO 0CRM_OPPH / Cube 0CRM_C04, you will find IO 0CRMPLEAGUI - GUID of Preceding Lead, which captures the Lead GUID, which I assume is only when a Lead is converted to an Opportunity. You can check your data to confirm such cases. If so, restrict on 0CRMPLEAGUI where not # in your query to report such cases.
--Priya

Migrate MS Access 2007 multi-valued fields to MS SQL 2012

Hi! I do have a MS Access data base (made of MS Access 2007) which has an Attachement field. As you know Attachment DataType is a multi-valued field that replaces the Object Link Embedding (OLE) Object DataType in the new Access Database (ACCDB) file
format. At present the whole DB has reached to the max size which is 2GB. Since we want to use the data and add more data to it, I was tasked to findout ways of converting it to SQL server. I have tried to use Import and Export data x32 module to import data
from MS Access to MS SQL Express 2012. All the data were imported except the BLOBs at the Attachement filed. Could you please help me to import those BLOBs to MS SQL DB. Thx!

Hello,
About those OLE objects, please try the following article:
http://www.codeproject.com/Articles/90908/Saving-OLE-Object-as-Image-Datatype-in-SQL
Another recommended resources:
http://www.microsoft.com/en-us/download/details.aspx?id=28763
http://blogs.msdn.com/b/ssma/archive/2011/03/06/access-to-sql-server-migration-understanding-data-type-conversions.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Converting leads to opportunities - Value field

Similar Messages

Maybe you are looking for