Adding "Expected Value" field in Lead Product Tab

Hi,
I have a scenario where the presales cycle starts from Lead and my client wants to capture Expected value in the product Tab . As the products are from banking scenario eg Loan ,we are not maintaining any condition type for Value.
I have checked in Opportunity and ther in Product tab , it has fields like Expected Value , Net Value etc. Now if I need to get the same fields of opportunity in Lead in Product tab pls suggest me the wayout for the same.
All suggestion would be rewarded.
Thanks & Regards,
Ambrish Sahai

Hi,
You can make date fields available at item nivel without create custom fields.
All you have to do is create a date profile and assign it to your item category.
To create a date profile:
transaction SPRO->Customer Relationship Management->Basic Functions->Date Management->Define Date Profile
To assign to an item category:
transaction SPRO->Customer Relationship Management->Transactions->Basic Settings->Define Item Categories
I hope it helps!
Kind Regards,
Gabriel Santana

Similar Messages

Maintaining operating concern after adding new value field

Hello,
I added a new value field to our live operating concern,maintained the data structure throguh KEA0(Maintain operating concern).The changes are transported from Development to Quality,Changes were reflected in Q system.After testing in Q system transports were pushed to production system.The new value field is added to the operating concern. When i check the log for KEA0 in production system it displayed one message like:
Field VV088 was added to the reference structure
Message no. KE782.You probably either changed the operating concern or SAP-EIS aspect, and added the field VV099 to the definition.
The added a CO-PA value field:
In this case, the field is added to the definition or the summarization levels. This invalidates all existing levels. Consequently, you need to activate them again and fill them with data.
In production system maintaining operating concenr or KEAO is only in display mode.Is it needed to regenerate the operating concern once again in production, how to do it. Is the message talking about the KEDV summarization levels.?
thanks
rahul

Hi,
No no ....KEDV is nothing to do here....that is creation of summarization in CO-PA.
Since you added new value field you necessarily have to Regenerate the operating concern...
Use Tcode KEA0...go to Environment tab...there the status of Cross client part and client specific part both will be in RED....now just click on the Cross client (candle button)...now the system would regenerate the operating concern...once it is over do the same for the client specific...
Beware when you do regenerate the operating concern no body can enter any transaction in that server since it is cross client table ...hence better do it after business hours.
Hope this helps!
Running KEDU with rebuild is relevant only when you already have created summarization and called up the same in the CO-PA report "options" tab. If you did not created the summarization you are nothing to do with KEDU.
Next: The new value field has to be transported to PRD and hence even in PRD we have to do the regeneration manually.
Regards,
Velumani
Message was edited by: Velumani Arunachalam
Message was edited by: Velumani Arunachalam

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

Impact of adding new value fields in ongoing operating concern.

Hi All,
Want to know the steps of adding new value fields in the existing operating concern in COPA?
What is the overall impact of addition of New Value fields in the running Operating Concern?
How do we test the addition of new value fields?
Is the addition of New Value fields to the running Operating Concern advisable?
Your support and advice is highly anticipated and appreciated.
Thanks & Regards
9819528669

HI,
please search in SCN forum before you post:
Re: Adding a ValueField to an existing Operating Concern?
Best regards, Christian

Adding new value fields to an existing and productive operating concern

Hi,
I would like to have 5 new value fields active in 4 out of 6 operating concerns that I am working with.
Is it correct that I could do this one of the following ways:
1. Use a value field that exists already in an operating concern and rename it?
In this case is it necessary to regenerate the operating concern?
Do I transport the change ?
2. Create an entirely new value field, and assign it to the operating concern?
Is it necessary to regenerate the operating concerns in question?
Do I transport the change?
3. Select a value field that is currently in the system but is not assigned to any operating concern eg some kind of SAP delivered value field? How do I assign it to the op con? Do I need to re gen the op con?
Which way is the best or is there a 4th option?
Thanks for your help in adviance
Regards
Aisling

Hi,
This note is a catalogue of notes of consulting notes where SAP tell you steps, reports to use and son . If you read them (these notes and related notes) you have the steps, guides, reports that you must use. Better advice. Try a solution with all steps in mind and check it in a quality enviroment. As you know there a lot of things in CO-PA concern (you have your own tables, with your own fields, your reports as KE2Rxxxx, and so on), your secondary indexes, etc.. , the best is try the solution in your Quality Enviroment (a quasi-clone of your production enviroment) and check the results (create SO, invoices, after modifications to check possible problems,...).
Regards,
Eduardo
pd: I forgot. If the size of tables (CE4xxxx, CE1XXXX, ...check them with DB02) are so big, get the opinion of a Basis Consultant. Surely in the before note there notes about this issue.
Edited by: Eduardo Hinojosa on Apr 23, 2010 2:41 PM

Add value field to existing/ productive operating concern

Dear All,
I need to create a new value field and add it to an existing operating concern, which is already in use (there is already transaction data in the live system).
In my opinion I have to do the following steps:
1. Create new value field (KEA6).
2. Add value field to operating concern (KEA0).
3. Activate operating concern (KEA0).
4. Transport operating concern (KE3I).
Is that strategy ok?
Is it ok, to transport an operating concern, when the system is already "live" and there is transaction data in the system?
Thanks for your answers,
Regards,
Michael

Hi,
first create new value field in KEA6. then take those new Value field in your operating concern Data Structure in t-code KEA0. Then generate the operating Concern.
Regards,
Sreekanth

Adding a custom field in IW32 Components tab

Hi,
I had a requirement to add a custom field in the "components" tab of IW32 transaction.
I tried to find out an exit for this transaction but I haven't found any exit that fullfills this requirement.
Please provide me some information whether there is an Exit, BAdI or any enhancement spots available to add a custom field.
Thanks in Advance.

Hi,
you can add a custom tab in IW32 tcode via the function group XWOC.

Adding a new field in purchase order tab in Sales Order transcation

Hi Gurus
I need to add a new field in header portion 'Purchase order data' with a new field below the telephone no for the transcation VA01.What should I do here?is there any exit or Badi avaiable for this?
Thanks
Ganesh

Check these:
Add new fields to VA01 Transaction
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/va01-adding-elements-to-the-screen-392724
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/add-z-fields-to-additional-data-b-of-va010203-838629

Adding item data in Product tab for sales contract (crm_order_maintain)

Hi, can I use crm_order_maintain to add line items under the product tab for a sales contract while creating or modifying an order. Is there any sample code to add the line items, I could look at. I tried calling this FM from my custom tab and then called CRM_ORDER_SAVE but that did not add the line item. I guess I need to call it from the order_save badi and then call the crm_order_save FM as well from within the BADI. If someone could send me some sample code then I can double check if I am missing something.Am I on the right track to be using this FM for adding a line item under the product tab for the sales contract? Please help. thanks

Hi, I've encountered the same problem while I was creating a Sub-Contract from a Master Contract.
In my case the solution was:
first create the Sub-Contract,
CALL FUNCTION 'CRM_ORDER_MAINTAIN'
      CHANGING
        ct_orderadm_h     = i_ctorderadm_h
        ct_input_fields   = i_ctinput_fields
        ct_doc_flow       = i_ctdoc_flow
      EXCEPTIONS
        error_occurred    = 1
        document_locked   = 2
        no_change_allowed = 3
        no_authority      = 4
        OTHERS            = 5.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
              WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
    READ TABLE i_ctorderadm_h INTO wa_ctorderadm_h INDEX 1.
    APPEND wa_ctorderadm_h-guid TO i_objects_to_save.
in wa_ctorderadm_h-guid now we have the guid of the newly created Sub-Contract.
SELECT SINGLE it_type_to
             INTO v_it_type_to    " --> target item type
             FROM crmc_it_copy_ma
             WHERE it_type_from = wa_out_orderadm_i-itm_type.
     Prepare tables
        wa_ctorderadm_i-header =
        wa_out_orderadm_i-header.   "Retrieved from CRM_ORDER_READ
        wa_ctorderadm_i-handle = '0000000001'.
        wa_ctorderadm_i-number_int = '0000000001'.
        wa_ctorderadm_i-product = wa_out_orderadm_i-product.
        wa_ctorderadm_i-ordered_prod =
        wa_out_orderadm_i-ordered_prod.
        wa_ctorderadm_i-description = wa_out_orderadm_i-description.
        wa_ctorderadm_i-itm_type = v_it_type_to.
        wa_ctorderadm_i-order_date   = sy-datum.
        wa_ctorderadm_i-itm_language = sy-langu.
        wa_ctorderadm_i-mode = c_a.   "c_a = 'A'
        wa_ctorderadm_i-header = wa_ctorderadm_h-guid.
        APPEND wa_ctorderadm_i TO i_ctorderadm_i.
        wa_input_fields-ref_handle = '0000000001'.
        wa_input_fields-objectname = 'ORDERADM_I'.
        REFRESH i_input_field_names.
        wa_input_field_names-fieldname = 'DESCRIPTION'.
        APPEND wa_input_field_names TO i_input_field_names.
        wa_input_field_names-fieldname = 'HEADER'.
        APPEND wa_input_field_names TO i_input_field_names.
        wa_input_field_names-fieldname = 'ITM_TYPE'.
        APPEND wa_input_field_names TO i_input_field_names.
        wa_input_field_names-fieldname = 'MODE'.
        APPEND wa_input_field_names TO i_input_field_names.
        wa_input_field_names-fieldname = 'NUMBER_INT'.
        APPEND wa_input_field_names TO i_input_field_names.
        wa_input_field_names-fieldname = 'ORDERED_PROD'.
        APPEND wa_input_field_names TO i_input_field_names.
        wa_input_field_names-fieldname = 'ORDER_DATE'.
        APPEND wa_input_field_names TO i_input_field_names.
        wa_input_field_names-fieldname = 'PRODUCT'.
        APPEND wa_input_field_names TO i_input_field_names.
        wa_input_fields-field_names = i_input_field_names.
        APPEND wa_input_fields TO i_ctinput_fields.
After that I've called function 'CRM_ORDER_MAINTAIN', to copy the Items from the Master Contract.
CALL FUNCTION 'CRM_ORDER_MAINTAIN'
        EXPORTING
          it_sales          = i_sales
          it_schedlin_i     = i_schedlin_i
        CHANGING
          ct_orderadm_i     = i_ctorderadm_i
          ct_input_fields   = i_ctinput_fields
        EXCEPTIONS
          error_occurred    = 1
          document_locked   = 2
          no_change_allowed = 3
          no_authority      = 4
          OTHERS            = 5.
Maybe if you're not working with Contracts, the procedure is not properly correct.
I suggest to put a break-point into crm_order_maintain and try to add the Item manually.
If you reproduce exactly the standard, I'm shure it will work.
Lorenzo

Impact of Addition of New Value Fields in the existing Op. Concern-COPA

Hi All,
Want to know the steps of adding new value fields in the existing operating concern in COPA?
What is the overall impact of addition of New Value fields in the running Operating Concern?
How do we test the addition of new value fields?
Is the addition of New Value fields to the running Operating Concern advisable?
Your support and advice is highly anticipated and appreciated.
Thanks & Regards
9819528669
Ohter details are as follows...
VALUE FIELDS : Defines the Structure of your Costs & Revenues. (Op. Concern 120 Value Fields)
1)     The client requires three new value fields to be created. Value fields for :
-     Other Airport Charges - International
-     Cargo Commission Cost
-     Personal Cost (Direct)
2)     What are the Steps involved in creation of new value fields? The steps are :
1)     Before creating new value field we need to check whether we can use already existing UNUSED value fields (There are 62 value fields created for the op concern 1000, in production the value fields TBUL1-L7 i.e. to be used (I assume) screen shot1 provided. My predecessor has used value field VV291, VV292, VV380 original description being TBUL3, TBUL4, and TBUL1. I believe he has changed the description in development client and created a transport request ref screen shot 2)
2)     You can create new value field thru T-Code KEA6 (4-5 characters beginning with VV) u2013 My predecessor has reused the value fields originally created he has not created new one I believe. please provide give your comments)
3)     Specify whether this field is for Currency or Quantity (currency defined in attribute of op concern and quantity defined by its own field u2013 unit of measure) u2013 My predecessor has configured the three value fields as Currency.
4)     Describe how the values in this field are aggregated over characteristics. (SUM, LAS, AVG) u2013 My predecessor has aggregated all the three value fields as SUM and they are in Active status.
5)     After the value field is created you have to add the value field (active status only) to the operating concern by Editing the Data Structure. (I guess this is done in the next step)
6)     Assign newly created Value fields to the Operating Concern u2013 T-Code KEA0 (In development client the value fields are assigned to the op concern 1000 refer screen shot 3. In the production client also those three value fields exist (does it mean they are assigned? your comments please.) As they have the original description TBUL3, TBUL4, and TBUL1 refer screen shot 4.
7)     After the Data Structure is defined you need to activate them. (creates plan vs actual database) u2013 Go to the data structure tab and Choose Activate. The status in dev client is Active with correct description but in the production client it is Active with the OLD description. After addition of the value field you need to regenerate the operating concern. T-Code KEA0 u2013 right?
8)     Condition Types are assigned to Value Fields? Donu2019t know u2013 T-Code KE45 (I think this is NOT required in our case u2013 Please give your comments)
9)     Define and Assign Valuation Strategy u2013 Cost assigned to Value fields u2013 T-Code KE4U (I think this is also NOT required in our case)
10)     Define PA Transfer Structure for Settlement u2013 T-Code KEI1 (This step is crucial u2013 I think I have to to include newly created value fields, but am not aware how to do it and what is the connectivity or what happens after this is done)
Note: My predecessor has created a Transport Request No# KEDK902167 for the value fields created by him.
3)     Whether my predecessor has performed all the steps for value field creation? How to test it and check that?
4)     If yes then, Do I need to perform additional configuration or can I proceed to transport it to Production?
5)     What is COPA Allocation Structure & PA Transfer Structure? Where and Why It is used?
6)     What are the different methods of cost and revenue allocations in SAP?
7)     I have checked the status of the value fields across clients, It is as followsu2026
     Value Field     Value Field For     Description     Development      Quality     Production
1     VV291     Other Airport Charges International     TBUL3     Exists      DNE     DNE
2     VV292     Cargo Commission Cost     TBUL4     Exists      DNE     DNE
3     VV380     Personal Cost u2013 Direct     TBUL1     Exists      DNE     DNE
#DNE : Does Not Exist (assumed since the description given to value field is not the same as in development client.)

HI sree,
ofter creation value field and saving that time reqwest number appeare copy the reqwest number and go through the se01 select that reqwest number select and transport click the truck symbole, and draft a mail to basis guyw.
Thank You!
Best Regards,
pradheep.

Value Field not fetching the data

Dear COPA Experts,
There has been an addition to the cost component structure for my current client. The cost component has been created and CK11n is showing the correct data for the correct cost component. I had to add value fields to my current COPA report to reflect the figures from the cost component. For that, I had created and activated the Value Fields in KEA6 and assigned it to the Operating concern in KEA0 and activated it. Then, I had assigned the value fields to the cost component structure in KE4R. I had then added the value field in the COPA form through KE95.
When a new cycle is completed, It does not reflect the valuation in KE30 report. I had crossed checked in KE24 which is a standard report. The result in KE24 and KE30 report is same, i.e the valuation is not even reflected in KE24 report.
Please guide me to where am I missing something?
Best Regards...

Hi,
"When a new cycle is completed, It does not reflect the valuation in KE30 report". This statement is not clear. Are you expecting KEU5 cycles to populate this value field ? Normally this value field should be populated during billing (VF01) when the value of the cost component is populated in the value field.
regards
Waman

Issue in Creation of new Value Field in CO-PA

Hi,
I have a query in CO-PA Value Field Linking.
In my Development Client,
1. Created a New Value Field (No Transport Request Generated)
2. Linked to the above to new Conditon type created in SD. (Tranport request was generated) i.e. in Flow of Actual Values->Transfer of Billing Documents->Assign Value Fields
However then i try creating a new Value Field in my Production Client it throws a message 'You have no authorization to change Fields".
Is this an issue with authorization or i need to transport the Value field too from Development to Production client.
Please Advise.
Thanks in Advance,
Safi

Thanks Phaneendra for the response.
The creation of Value field did not create any tranportation request. Will this too be transported if i transport the Operating Concern.
Please Advise.
Thanks,
Safi

Having problems when adding new Curency value field + currency field.

I need to add a new Currency field (CURR, length 15, 2 decimal places) plus the Currency field itself to a view.
I'm really struggerling. I have looked at the existing SAP fields in the Component workbench and I have to admit I can not see how a field is linked/related to the currency itself. Is this link established purlely at the disctionary level?.
Has anyone added their own Z field value and Z currency field before. I can create both fields and display them, but what I can not work out is how I related them within the component workbench, or is this done from the dictionary?.
Any help would be greatly appreciated.
I should have been able to look at an existing SAP example and work out how it's done, but so far I can not see/determine how this is achieved, even though someone has mentioned that it's controlled via the GET_I_field method. Looking at this method I was expecting to see some mention of both the Currency value field and the Currency field. But as I don't see these confusion reigns.
Jason

That's correct, but am I right in thinking that you can't actually create the currency key field itself?.
I am aware that currency value fields can be created which reference a currency key field, but can see nothing that allows me to create a currency key field to be referenced.
I hope that makes sense.
Also, I have amended the structure, changing my value fields from Decimal 15,2 to Currency 15,2 and have created a new currency key field in the structure and referenced this from the Currency value field.
Witin the Component/view/context node I can see this new currency key field, but it appears as STRUCT.fieldlabel whereas my currency value field appears in the context node as EXT.fieldlabel, because it was created in the AET.
My problem is that when attempting to add the currency key field onto the screen I don't have it to select from within the list of structures/attributes. All the others attributes in the context node seem to be there, except the new currency key field/attribute.
The attribute has a SET_fieldlabel, GET_fieldlabel, GET_M_Fieldlabel and a GET_I_Fieldlabel, which I believe is all that should be required.
Does anyone know what my problem could be?.
Jason

Adding new characteristics and value fields in COPA

I have recently added several new characteristics and one new value field to the operating concern in the development system.
I am not exactly sure how to create the transport. This is the first time I have done a transport in COPA so I was hoping someone out there would have some tips on how this is done.
Also any helpful tips with transporting this type of change is much appreciated.
Thanks,
Laurie Hensiek

Refer to the documentation at http://help.sap.com/saphelp_46c/helpdata/en/c6/f22c7dd435d1118b3f0060b03ca329/frameset.htm
This is under the node Tools>production startup>transport.

Settle Production Variances to COPA- Cost elements and Value fields

Dear All,
I know this question has been discussed in the past, but I have one specific doubt regarding this topic.:
When assigning cost elements to variance categories in t-code KEI1, how do we figure out what combination of cost elements (in the top half of the screen) constitute Input Price Variance, Scrap variance etc (in the bottom half of the screen)? I know the net of the postings on those cost elements tells us what variances we are looking it, but how do we get the cost elements (group) for let's say, 'Input/Output Quanity Varinace or 'Lot size Variance' ?
Or is this a futile exercise? May be I should just create three types of variances: Labor, Machine and Overhead. And I know what cost elements (net of the postings) would, in total, make up the $ variance in each of those categories. I can then use them in my report painter reports.
Please help clear the fog for me.
Ajay?
Thanks a lot,
Deepak

Hi Deepak,
Welcome to SDN!!
There are 2 ways of updating variances in COPA... I Prefer the 2nd option always...
1. Category wise variances (Input Prc, Usage var, etc) - Here, create a Cost ele group, where in you include all the Cost elements that can be posted to the Prod orders
For the sake of simplicity, you can include Cost elements 1 to 99999999 in the Cost element group...
2. Cost Comp Structure wise variances -
a. Create as many assignment lines in PA Trf Structure as in your Cost Comp Str...
Eg: If your Cost Comp Str in OKTZ has Raw Mat, Labor, Overhead - Create 3 Assignments in PA Trf Structure..
b. Assign the same cost elements in the SOURCE as in the Cost Comp Str
c. Choose the radio button "Costs/Revenues" in your assignment line, instead of " Variance on Production orders"
d. Assign each Assignment line to a separate Value Field
br, Ajay M

Adding "Expected Value" field in Lead Product Tab

Similar Messages

Maybe you are looking for