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

Similar Messages

Info about a new value field in a live operating concern

Hi Team,
I'm working on 4.7 system.
I have a live Operating Concern with 120 value fields in "Active" Status.
Some of them never have been posted until now. I need a new "Quantity type" value field, but I can't create another one because I already have 120.
In addition, the value fields that have not been used until now are "Amount type" ones.
Is it possible to delete or modify one of these value files and create another "Quantity type" one, considering that Operating Concern is productive? And how can I do it? What kind of problems could I have?
Best Regards,
Gio

Hi Gio,
Good evening and greetings,
Please go through the SAP Note No.21207 on Deleting a Characteristic / Value Field from an active Operating Concern. This should clarify your questions.
Please reward points if the note is of some use to you.
Thanking you,
With kindest regards
Ramesh Padmanabhan

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

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

Profitability segment number 02209 does not exist in operating concern ESAA

Hello Experts,
Please help us on one issue which we are facing here that
"Profitability segment number 02209 does not exist in operating concern ESAA"
please could you please let us know why are facing this issue and where to check if this Profitability segment number.
Thanks and Regards,
Mangal Modi

HI,
This can occur if you have deleted data from table CE41001 and have
already assigned data to profitability segments in this operating
concern.
Check the OSS note: 93051, hope it may help you..
Thanks

No attributes exist for operating concern

Dear Friends:
In our configuration client, the operating concern is active and has attributes were defined and transported. But in Unit testing client, the system says
"No attributes exist for operating concern"
How to over the problem?Please advise?
How should i reward the answers?
Regards
MSReddy

First try regenerating the operating concern in KEA0 in the envirionment tab. Select the activate buttons. If that does not work then retransport your operating concern using tcode KE3I.
pls assign points if helpfu;l as a way to say thanks.

KE24- No Attributes exist for operating concern

Dear Gurus,
while iam generating the ke24 report, am getting the error message as No attributes exist for operating concern.
Please help me out in this problem.
BR,
Deepak.

Hi Deepak
You can access change logs in KEA0 by accessing Extras -> History log. I guess this would only be available in Dev client though.
Secondly you can also try regenerating the Operating cocern by activating it under the Environment Tab in KEA0
Alternatively, you can also try reimporting the operating concern by using KE3I
Hope it helps
Regards
Mustafa

Want to add OBTYP field in existing filtergroup in BD64

Hi Guru's,
I want to add OBTYP field in existing filtergroup in BD64 can any one help me in this regard.

Hi......
Check these links :
http://help.sap.com/saphelp_nw70/helpdata/EN/ae/d4712d2cad43ffb56f82733a560c3d/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/01/3b15301edf48169f91ec2b5b0cbe2c/frameset.htm
It may help you.......
Regards,
Debjani.....

Add value field to operating concern

Hello,
I have created a new value field VV955 and want to add it to my operating concern in transaction KEA6.
I go into change mode for all value fields for my operating concern and add a new line with my value field. When I hit the save button, it says "Field VV955 exists as Val. fld in field catalog -> choose another name".
Also when I go into change mode in KEA0 where you can drag value fields from left to the right, the value field is blue which means I cannot assign it to my operating concern.
Any suggestions?
Thanks
Anne

Hi,
While creating value field it will only consider long text. Inoperating concern Data structure in KEA0 you can assgin value field it will display in blue first, when you select to data structure you can see value field and save the value field.
Regards,
Sreekanth

CRM - Add New Field in Competitor Product Screen

We are looking for the right way to enhance the competitor product screen (object prod_cp) in CRM 7.0. We have explored several options and we would like to have a confirmation that we selected the right option for the CRM level we are on now. We checked enhancement options via eewb and aet. However, in transaction axtreg there are 129 objects that can be enhanced but object prod_cp is not part of that list so I assume both tools mentioned cannot be used to enhance the competitor product screen (we want to add new fields and put business logic behind it). Is this a correct conclusion? I based the conclusion on post below:
AET enhancement capabilities
Found a OSS note 1088910 which looks like something we could use instead in CRM 7.0:
appl enhancement          component view for customer
Competitor products (PRDCP)     PRDCPOV/CustomHeader
Is this correct?
If this is not correct, how can we enhance the competitor product screen without changing the sap standard code (like append a Z structure to table comm_product_idx and then....are there any enhancement sports for this screen where we can add our custom code?). Do we have to use the framework enhancement concept?
Also found OSS note 1448299 that provides information about business functions for the Application Enhancement Tool (AET) in SAP Enhancement Package 1 for SAP CRM 7.0 and I saw that we will be able to enhance the competitor product screen as soon as we have upgraded to Ehp 1 just by switching on business function crm_inf_1. Is that correct?
Rgds,
Josephine

Hi Josephine,
You can enhance any standard CRM 7.0 component. follow this wiki on how to enhance standar CRM7.0 components
http://wiki.sdn.sap.com/wiki/display/CRM/HowtoGuide-EnhancingtheUIinCRM+7.0
You have two options to add new field to the competitor product screen
1. Using AET. Application Enhancement Tool, require very limited technical knowledge and i believe even function person can add a new field on the webui screen using AET. Search sdn with AET and you will find lot of information.
2. Create a z table with the new field value and product id (unique key).
    Create a value node in the standar component.
    On load of the webui screen fetch the details of the new field from the ztable and display it
    On the save of the webui screen if the value of the new field has changed update the z table.
Regards

REG: How to add new fields to existing Infospoke

Hi All,
We have an existing Infospoke, It has ODS as a Source and some fields are being pulled.
But here is the scenario....
I need some extra fields that are available in other ODS. How to add that fields ?
By some research came to know that.. I need to lookup on the ODS and populate into existing Infospoke.How to add these fields to InfoSpoke using BAdi implementaion.
Note: already BAdi is active in the infospoke.
Please help me in this regard

Hi Chase,
As you mentioned that BADI is already implemented then I guess you should be able to extend the existing BADI itself.
For doing lookup first you should know the key fields of source DSO then by using the existing field of Infospoke you will have to read data from DSO.
DATA: it_data type standard table of 'DSO Name'.
select Key1 key2 etc...
          Field1 Field2 Field3 Field4
          from DSO
          into table it_data
          for all entries of infospoke
         where key1 = infospoke1-key1
                     key2 = infospoke2-key2.
This will give you all the required records from source DSO into internal table it_data. Now you using this table you can populate the original table of Infospoke.
Regards,
Durgesh.

How can I add table fields with existing structure ?

I like to add PSTLZ field to stucture KOMGG.Is it possible to add table field with the existind structure.If yes how can I do this?kindly help me on this.

hi
go to se11
in change mode select the button append
create new append which starts from Zpstlz in this komgg structure and add data element and domain to this field and activate with request number
then in field catalogue this field should be visible ,here ends your append
now it is ready to use in condition tables.
reward if helps !!!!!

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

Can we add new field to existing Sales Analysis by Item report?

I would like to add sum total weight of all the items sold so far to the above system report?
How could i do that please?
Thanks.

You need to have your own report. This system report is hard coded. You do not have option to add fields there.
Thanks,
Gordon

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.

Add value field to existing/ productive operating concern

Similar Messages

Maybe you are looking for