Does value fields adding require transport

Hi All,
I have added value fields to the existing op concern in dev and regenerated the op concern
Do i have to do this individually in each client or will it be reflected automatically or do i need to use KE3i
Regards,
Reddy

Hi
Please create in each client. I created like this in my organization.
Value fields will not create Transport request Number. I could not find the value field radio button in KE3I.
Regards
Odaiah

Similar Messages

Transport COPA new value field

Hello SAP Experts,
I have created a new COPA value field. Now i would like to transport the same to Test (Acceptance or Quality) server, can you kindly let me know how can i proceed with this.
Your inputs are highly appreciable in this regard.
Many thanks in advance.
Regards,
Pavan Kumar P

Hi,
Please read note 131664 regarding the use transaction KE3I to transport operating concern structures.
In principle you can transport a new value field with a transport of an operating concern - part 'Structures: ABAP Repository objects' in transaction KE3I.
You need to perform the following steps:
1. Value field added in source system thro tcode KEA6
2. Regenerate the environment of operating concern in source system (tcode KEA0)
3. Transport using KE3I (select: ABAP repository objects)
4. Regenerate the environment of operating concern in target system.
Via transaction code KE3I you have the option to transport specific object classes. If you select 'Structures: ABAP Repository objects' the following settings are transported:
Cross-client objects in the SAP Repositiory
- Tables and structures of the operating concern (CE1xxxx - CE8xxxx)
- Domains and data elements for CO-PA characteristics
- Master data tables for CO-PA characteristics (without data)
Cross-client control tables
- CO-PA field catalog
- View directory
Normally we advise customer to add a new value field/characteristic to
DEV then transport to QAS and then transport to PRD. This ensures that
the operating concerns in the 3 systems are in sync.
regards
Waman

New Value Field

Dear Friends,
We are planning to add new value field in current copa structure, for this I need know :
1. As soon as we add new value field current operation conern gets deactivated ?
2. If there is only one server for development and production then as soon as we create value filed in development, what would be the impcat in production client ?
3. If server is same than transport of value field is required ?
4. If required then opernation concern shuld be re-generate after transport ?
5. If server is same then operating concern has to be regenerated in every client ? i.e. dev, testing, preprod, prod.
and what ever impact would be in this case and also if we have different server for dev nad product. Kindly let me know about you expert comment.
If there is any risk while regenerate operating concern, also please let me know.
Thanks
Ravi

Hi,
Activation of Operating concern has two aspects- Cross client and client specific... for your questions.. if you have operating concern in the same server it is enough if you activate only client specific one..
On each change of u r datastructure i.e changes to characteristics and value fields u need to generate.. till then it will be in Inactive mode..
In terms of different systems generally u can transfer the active operating concern on addition of new value field. However sometimes it may be required to activate specifically..
Regards
Sudhakar Reddy

New Value Fields in COPA

hi
All COPA configuration with characteristics and value fields is already transported to QAS.
I have created three new Value fileds in DEV and want to transport in QAS?

Use Tcode KE3I
Select operating Concern
Execute
create bot customising and Wrokbench requests for that
Select the operating concern Execute
Select ABAP repository objects and Enter
release the transports and Import them in QAs and you are done
Thanks
Naveen

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

"You must specify a value for this required field" in SharePoint list

HI All,
I have a couple of taxonomy fields in my content type. When I try to add a new item with my content type and save, I'm getting an error message "You must specify a value for this required field" against each taxonomy field. I'm not sure what am
I missing. I deleted the content type and added that again to my list but still no luck. Can someone please help me out? Thanks.
Regards,
SC Vinod

hi
it depends how you updated existing field. We faced with the problem that update of taxonomy site column was not propagated to the lists. In Sharepoint when content type is bound to the list, new hidden content type is created for that list - you may check
it if will enumerate
SPList.ContentTypes property. And when you try to update site column changes may not be propagated to these list content types. In order to update it you need to get reference on a field from list content type and update if explicitly.
Blog - http://sadomovalex.blogspot.com
Dynamic CAML queries via C# - http://camlex.codeplex.com

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

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.

New Value fields created in existing opr struc problem in transport request

Hi,
I have created new value fields in existing operating structure but system has now created any transport request for value field creation also for value field activation and later on operating concern generation on development environment.
What is the other way of doing transporting value field (also activation of same) from Dev to QA?
Regards,
Sayujya

Hi,
Creation of new value field or characterisitics will not generate any Transport request. Goto transaction KE3I and create transport request.
Regards,
Sreekanth

Transport COPA Value fields

Hello Experts,
I have the scenario wherein we need to change the description of certain value fields & transport it to test & production system. I know this can be done via KE3I in which we can transport the entire operating concern but my interest lies in whether there are any potential impacts on production system in which there is already transaction data? Does this function transport the entire customization tables of COPA ? If transported to live environment, any impacts?
These questions are only to those COPA experts who have transported operating concerns for live systems containg transaction data.
Regards,
Amol

Hi
I am interested to know why you are looking for this change if want to change for reporting purpose you can change in BW from where we are getting the reports .
when you regenerate Operating concern, the old data needs to be dropped and reloaded again
which is a mamoth task and not advisable by SAP as well ,as dropping data and reloading the same their is no validation cycle for the same
Thanks
Deepak

Transporting of Value field name/description translation in COPA

Hi,
I have a problem with Value field name/description translation in COPA. In English language all user defined value field names are defined properly with name and description.
In my native language their names are blank and its hard to use COPA reports as we don't see the description of particular value fields.
Is it possible to tranport the names of value fields from DEV system to PRD system? I have altready translated value fields on DEV but there is no option to create transport with the translations or changes in the names I made.
If it is possible to transport it to PRD, do I have to refresh and regenerate Operating concern in PRD?
I am not confident with refreshing Operating Concer on PRD client - as it might be generated with errors and stop all sales.
What would you advice?
Kind regards,
Karol

Hi Nakul,
Kindly check if you have reset the value field in KE4W. If this does not help then please provide us more details about the document that you have posted.
Regards,
Abhisek

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

HCM F&P - How to set the field as Required based on drop down values

Hi Experts,
I have a requirement to set the Date field as mandatory when a particular value is selected in drop down list. I have already tried with MessageBox though it displays the error message but process moves further i.e. on clicking Check & Send button it throws an error message but still it moves further and i can see only Send button. Ideally it should halt there itself.
Thanks & Regards,
Jitesh Talreja

Thanks for your valuable inputs
Chintan
I have already tried this. It only highlight the field with the red border but still allow to move further.
Mukesh
Yes, we can definately control this from the backend but that would be the last option i should execute. Ideally, this is something to be controlled in front end itself
Poornima
By setting the field attrbiute Required will set the field mandatory as a whole irrespective of drop down values or any other UI element.
Regards,
Jitesh Talreja

New Value Field Transport

Experts,
How shall I transport a new value field I have created. Also, I have assigned this value field to one of the operating concern...
I understand it has to be transported via KE3i. After that needs to Select Operating Concern..after that I am confused what to select ??
Please advice
Amit

Hi,
If Value field is assigned to Data structure then you need to regenerate operating concern in KEAO. you cannot transport single value fields in COPA. All value fields which are assigned to Data structure are picked during transport.
Regards,
Sreekanth

COPA new value field transport

Hi
Is there any way to trnsport only the single value field in COPA to other instance?
Regards
HK

Hi,
If Value field is assigned to Data structure then you need to regenerate operating concern in KEAO. you cannot transport single value fields in COPA. All value fields which are assigned to Data structure are picked during transport.
Regards,
Sreekanth

Does value fields adding require transport

Similar Messages

Maybe you are looking for