Language change to Operating Concern in KETR

Hi,
I have one operating concern for all company codes it is the global operating concern it was maintain in EN language ,and other languages also,
But when user lo -gin in FR(French Language) when he was doing Top down Distribution in (KE28) he is getting an error that is
"Operating concern"1000" was not maintained in FR Language"
Now i want to know how to change the the operating language to FR(French language) any one please suggest me the required steps ,
Thanks in advance
Naresh
Edited by: Gadupudi naresh on Jan 2, 2012 4:58 PM

Hi Naresh,
First you need to log in to your system in French. Then in transaction KETR you can select target and source language. Select operating concern, charachteristic and value fields. After this you can exacute the transaction. Please remember to regenerate the operating concern after this operation.
Regards,
Abhisek

Similar Messages

Change the currency of Operating Concern COPA

Hi,
In my SAP environment there are 4 controlling areas. Only one of them is assigned to Operating concern. The remaining 3 have COPA inactive.
I would like to extend the existing operating concern to remaining 3 controlling areas, but before I do that I need to change the Operating concern currency as the one currently set is only relevant for only one controlling area and company code which is GBP. I need to change it to group currency - USD.
When I use F1 help on currency field in Operating Concern settings in configuration, I get information that 'once data has been posted, however, a change in the operating concern currency would cause the existing data to be interpreted as if it were posted in the new currency (for example: USD 1000.00 in old currency -> DEM 1000.00 in new currency).'
Even though we have transactional data posted in that operating concern , it is not being used by any department and we are quite happy to have existing data interpreted in USD instead of GBP. No reports are being generated in COPA currently so it will not be an issue for us. We want new data to be proper and constistent.
When I try to change the currency in operating concern config, the field is greyed out. I believe there is more complex workaround for that, but the only note I found on this is 651142 which says that SAP provides different tools to reorganize operating concern. But no further details are included.
If anybody managed to change operating concern currency, please help me with that.
Regards,
Karol

Hi Karol
I read the note given by you.. It asks you to contact the SAP for SLO Service (System Landscape Optimization )
This is a chargeable service by SAP... In case you decide to go ahead with this, do share your experience with us
Create an OSS msg and give ref of this note... I would suggest to go with SAP service and not with any one else's experiences... The tools that SAP is talking about are available only with SAP..
You may try to archive the existing data from COPA tables and then see if the currency field opens up for editing.. Am not sure about it..
Regards
Ajay M

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

Operating concern not able to activate in CO-PA

Dear All,
I created some new Characterstics and value fields in the CO-PA. After that I have taken my required Characterstics and value fields in my data structure in Operating concern. When Click on Check tab button ( i.e. Cntr+F2 ) it is giving the message structure definition is O.K.
After that I am able to SAVE that.
BUT when I want to activate the data structure is giving the DUMP ERROR.
The message is " What happened?
     One of the columns addressed in a table or view does not exist in the database.
     table) exists in the ABAP/4 Dictionary, but not in the database.
Short text
    SQL error in the database when accessing a table.
It's critical issue in my development client and my whole work has stopped.
Kindly do the needful.
Thanking You
Regards
K. S. Sai Kumar

Hi,
Sayeed,
Even I am not able to change the Characteristics and Value fields like previous condition.
I mean If I want make the change in operating concern it is giving the message " No Objects Reset " Message no. KX473
I have to solve this problem very urgently.
KIndly do the needful.
Thanking You
Regards
K. S. Sai Kumar

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

Operating Concern - Transport

Hi All,
I'm trying to create a New operating concern, new characteristics and value fields in the gold client. But these customizing changes are not "automatically" collected in a transport request.
Can someone tell me what is the right way to go about with configuring CO-PA Organizational elements and Data structures in the gold client and collect all these settings in a transport.
Many thanks for your help
SB

Hi,
For transporting Operating Concern please use transaction code KE3I. You need to create a manual transport request. Many of the CO-PA requests can be included in transport request from this transaction. While incorporating the characterstics and value fields excercise caution and check the transport request regarding the objects included.
There is also an OSS note on CO-PA transports. You can check the same.
Thanks
Murali.

Problem in generating operating concern - COPA

Hi COPA gurus,
When activating operating concern BPUS through T-Code KEA0, following are the error details we found :
The system is not allowing to activate the operating concern and saving it with following error "Error saving data structure CE1BPUS", Message no. KX655
The error details with Data Structure are
"Reference field CE0BPUS-REC_WAERS for CE0BPUS-VVR10 has incorrect type"
Table CE0BPUS was activated with warnings
As we analyzed the above error in Structure CE0BPUS, the field REC_WAERS and VVR10 is referring to each other, but the data type is different. For REC_WAERS data type is CUKY and the No. of Character is 5, where for VVR10 the data type is blank and the No. of Character is 15.
Same error we are getting for Table CE1BPUS which is updated after updating the structure CE0BPUS.
Please help.

Hi Sangram,
There looks to be some issue with the value field VVR10. Please remove the field from operating concern and try again. There must be some changes to the value feld which created this inconsistancy.
Best Regards,
Abhisek

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

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

Delete COPA characteristics which not used in any operating concern

Hello SAP experts,
Please advise me on how to delete PA characteristic "WW001" created by mistake that we are hoping to delete if possible. However, when attempting to delete in KEA5, the error log appear as
Data element RKEG_WW001 is used in these table/view
CACS_S_COND_MA
JVKOMP
KOMG
KOMGF
KOMGFNEW
KOMGFOLD
KOMP
KOMPAKE
STR_KOMG
TRCON_IT_KOMP
WB2_EKOMP
And does not allow the deletion
WW001 have already been delete from the operating concerns.
Please shed some light on how to do this?
Thanks in advance for your help
Yang

Hi,
In order to delete a characteristic 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.
It is not possible to transport information about 'deleting of
characteristics (value fields)' with transaction KE3I. Only
characteristics and value fields included in operating concern (to be
transported) are transported with KE3I. Deleted characteristics and
value fields are ignored. You have to delete these characteristics and
value fields manually in each system.
Best regards,
Maria Luisa

Transport KE30 reports between operation concerns

Dear all,
I have a problem with the transport of some profitability reports between 2 operation concerns. The reports are confirmed and approved in the first oc, but there's still a dummy copy of these in the second oc.
So here's my process...
I set at first my oc in KEBC. Then I select in KE30 the reports for transport. I chose report definition, report form, key figure scheme and transport all languages. 2 transport requests appeared (customizing and workbench) and they have objects inside (SE01). After that I went to KECP for copy specific objects.
Here's now my problem that I can insert only one transport request. I tried both in separated steps but it didn't work. Also I created a "transport of copies request" in SE01, included the objects of both requets. Also the import from the first to the second oc didn't work.
Can you please give some inputs?
Thanks!
Kind Regards,
Rafael

hello,
did you check
1. Verified that the tnsnames.ora contains a single line entry for the Reports server.
2. Verified that the port is used only once.
3. Verified that the default domain in the sqlnet.ora matches the Reports server entry (.world).
4. Deinstalled and reinstalled the Reports server service.
5. Verified that the Reports server account has a default printer assigned and is set up as a "Use this account" account.
regards,
the oracle reports team

Can I install on the iMac Russian Language? For example, it is possible to install the Russian language in the operating system OS X Lion, if my iMac I bought in the U.S.?

Can I install on the iMac Russian Language? For example, it is possible to installthe Russian language in the operating system OS X Lion, if my iMac I bought in the U.S.?

OS X is the same no matter where it is sold, and Lion can be switched to Russian in a few seconds by changing settings in the system preferences.

Can CO-PA report be shared by 2 operating concern?

I have a report that would like to be used for 2 operating concerns, is it possible to do so?
Currently, the report is only available for 1 of the opearating concern, if I set the opearating concern to another, the report cannot be listed by KE32.
Do I need to create the report again for the other opearating concern?
Thanks.

Hi,
Yes you have to create the report again if Operating concern is changed
Regards
Balaji

OPERATING CONCERN

Hi All.,
I have created the Operating concern with some characteristics & value fields.
Now my client want to add two more characteristics to the operating concern by removing the existing ones.
when i am trying to add them it is not happening.
Is there any limit for number of entries in operating concern, if there is a limit how can i do it.
Please help me out in this regard.,
Regards..,
Raja

Hi,
You can delete the characterstics only if the postings are not made for the characteristics.
Procedure:
1) Use KEA0, enter data structure in change mode. select the characteristics to be removed from the left hand side of screen click on transfer button to move them to right hand side.
2) need to activate and save the characteristics screen
3) need to re-generate the environment.
You may get so many system messages follow carefully.
Impact on cross client also.
Regards,
Murali

COPA - Operating Concern

I seem to have accidently partially activated the S_AL operating concern which in turn created additional fields in structures ACCTSD and COPAFIELDS, this was all done in our Dev client. Our Dev client is now not in line with our QA and Prod clients. Is it possible to reverse what I have done and remove the additional fields created?
Thanks
Greg

Hi,
Go T.code: KEA0
Go to Change operating concen and them go to Data structure.
Then go to value Value fields and select fields that you have created and not required in the left hand side column (data structure) and move them by clicking on arrow to right side column (transfer from).
Assign points if helpful.
Regards,

Language change to Operating Concern in KETR

Similar Messages

Maybe you are looking for