COPA - New field

Folks
A new field was added to the COPA table. I have to make that change to the BW cube.
How should I proceed. I know COPA has a generic datasource . Can some one guide me step by step.
Thanks

Hello
Check this Note. 0312711
Symptom:
CO-PA DataSources cannot be enhanced with BW standard means
Other terms:
RD159, RSA6, enhance DataSource, DSRC, Append Structure
Reason and Prerequisites:
Functions are missing. Without this note, error message RD159 is output for DataSources with enhancements.
Solution:
The correction below allows you to add append structures to DataSources of the profitability analysis. Error message RD159 continues to occur if fields are directly included in the generated structure because the fields have to be compared with those in the results area.
Hope this will help.
Best Regards....
Sankar Kumar
+91 98403 47141

Similar Messages

COPA - New field added

Folks
A new field was added to the COPA table. I have to make that change to the BW cube.
How should I proceed. I know COPA has a generic datasource . Can some one guide me step by step.
Thanks

Hello
Check this Note. 0312711
Symptom:
CO-PA DataSources cannot be enhanced with BW standard means
Other terms:
RD159, RSA6, enhance DataSource, DSRC, Append Structure
Reason and Prerequisites:
Functions are missing. Without this note, error message RD159 is output for DataSources with enhancements.
Solution:
The correction below allows you to add append structures to DataSources of the profitability analysis. Error message RD159 continues to occur if fields are directly included in the generated structure because the fields have to be compared with those in the results area.
Hope this will help.
Best Regards....
Sankar Kumar
+91 98403 47141

New COPA Value field not populating in BW

We created a NEW value field (VV0056) in SAP COPA that is NOT pulling manual journal entries into BW (document types AB and SA). All other value fields are pulling in all document types and balance to SAP u2013 itu2019s this new one that is not. We do not have any restrictions on selection of data coming into BW.
The manual journal entry is in our CE1* table in R/3.
We are still 3.x data loading in our BW 7 system.
Any ideas on what to look for? Your input is greatly appreciated.
Renee Mercede

Hi Renee
The new fields that has been added must be either in the COPA table or the corresponding datasource.
If it is added in the table
1) You need to enhance the corresponding datasource with a z-field that wiill represent the field added in the table.
2) This field will have to be populated through an ABAP routine.
3) Check the populated field values in RSA3.
4) Replicate the datasource in BW.
5) Create infoobject for the enhanced field.
6) Add infoobject in the corresponding BW data targets.
7) Change transformations / UR's - TR's.
8) Extract data.
If it is added in the datasource - which means you know from which base table this field needs to be populated.
Carry out steps (2) to (8) from above.
Cheers
Umesh

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

Adding new field to existing CO-PA data source

Hello BW gurus,
i was asked to add a new field vv531 in COPA data source, in order to do this when i was deleting the data source it is giving message "you are not allowed to change cross-client Customizing" .our bw development has 2 clients 20 & 40 . Generally wat ever changes are done in 20 are visible in 40. But now am not able to see the particular CO-PA data source in client 20.It is visible only in client 40. when i am trying to delete it from 40 it is giving the msg. Please suggest me over this bcause my dead line to complete this is nearing.
Thanks,
praveen

hello manfred,
thanks for the reply. i know for the fact tht we shud delete n recreate but when i am trying to delete it it is saying "you are not allowed to change cross client customising" . when the development was going on they have done it in development server client 20,which is also visible in client 40 with out transportation . 20 is whr changes are made ,40 is the one which is connected to BW development server. Now as per the requirement i shud make changes in 20 ,but when i am trying to do this it says "data source is defined in a different client" .pls help me out resolve this problem.
thanks&regards
praveen

Add a new field in report S_ALR_87012178 and use it for sorting

Hi all,
We're requested to add a new field KNVV-VKGRP in this report S_ALR_87012178 (program RFDOPR10). As this is a standard program, I'm thinking of copying it into a Z one due to the problems when editing the report.
Does anyone know the best way to do it? I'll appreciate it so much!!
Thanks a lot in advance!
Regards,

Hi,
The procedure to create the new VOFM.
1. Go to VOFM transaction
2. Page down until you find a new spot on the page to put in the VOFM number and description.
3. Put in the VOFM number and the description of the VOFM.
4. Now the VERY IMPORTANT part of the process. Double click on the VOFM description not the VOFM number to create this as a Development/Correction and not as a repair. If you double click on the number then this copies some existing code and prompts you for a repair.
5. Activate and generate the VOFM routine. Note: Configuration must be setup by the OM team for this step.
for example Go to the routine number that needs to be copied.
Put your cursor on the routine number field that needs to be copied.
Overwrite that number with your new routine number and hit enter.
The new routine will be created as a copy of the old routine and you can modify the new routine as you need it.
Ex.
You have to copy routine 104 to 904
Routine number Description Active
104 Bill.bus.item data X
Put your cursor on 104 and then change it to 904 and hit enter.
904 will be created as a copy of 104 and you can make your changes in 904.
Don't forget to activate it after you are done.
refer the below link
https://forums.sdn.sap.com/click.jspa?searchID=3604222&messageID=994791
Regards

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

Add a new field in va02,va03 and vf02 & data tran. in these fields VOFM

Hi All,
I have a requirement, I need to add a new field in the sales order header part and even a field in the billing document, once I add this field up in both the documents in the header part i need to create a copy routine using the VOFM transaction,
Can any body help me on what's the procedure to add a field in billing document as i dont find any screen exit for doing it and does the copy routine transfer the data ( Custom Field ) from Sales Order to the Billing Document, if yes can somebody help me with the procedure on how to and code of it.
Regards.

Hi,
The procedure to create the new VOFM.
1. Go to VOFM transaction
2. Page down until you find a new spot on the page to put in the VOFM number and description.
3. Put in the VOFM number and the description of the VOFM.
4. Now the VERY IMPORTANT part of the process. Double click on the VOFM description not the VOFM number to create this as a Development/Correction and not as a repair. If you double click on the number then this copies some existing code and prompts you for a repair.
5. Activate and generate the VOFM routine. Note: Configuration must be setup by the OM team for this step.
for example Go to the routine number that needs to be copied.
Put your cursor on the routine number field that needs to be copied.
Overwrite that number with your new routine number and hit enter.
The new routine will be created as a copy of the old routine and you can modify the new routine as you need it.
Ex.
You have to copy routine 104 to 904
Routine number Description Active
104 Bill.bus.item data X
Put your cursor on 104 and then change it to 904 and hit enter.
904 will be created as a copy of 104 and you can make your changes in 904.
Don't forget to activate it after you are done.
refer the below link
https://forums.sdn.sap.com/click.jspa?searchID=3604222&messageID=994791
Regards

SEPA tree: how to add new fields?

Hello @all,
I tried to add some fields to the SEPA tree in DMEE. The technical adding migt not be the problem, but in the output file the new added fields are not shown.
Can somebody give me hint, how to maintain the new fields that they are shown in the XML file, which is created?
TKS/BR
Black

Hi,
These are the steps I've done:(a lot similar to the MAX explanation)
1º Create a structure append in MARA where I added mu new fields;
2º Create the program SAPLZMGD1 as copy the std program SAPLMGD1;
3º Create a new subscreen in my custom program SAPLZMGD1, where the fields of APPEND structure of MARA are managed;
4ª For each new field, the user should include a field instruction between the modules PAI GET_DATEN_SUB and SET_DATE_SUB;
Ex: FIELD ZZNEW
CUSTOMIZING
1º Copy the std sequence 01 or 21(depends of the company) into your custom sequence Z1 by trx OMT3B;
2º In the new sequence Z1 I add a new DATA SCREEN (as copy of custom DATA SCREEN BASIC DATA 1 or 21),
3º In my new DATA SCREEN I added my new subscreens (you could add max 10 subscreen;
4º In the Control of sequence of screens to modify the reference of screens for his/her screen copies and created previously.
Refer
http://www.****************/Tutorials/ExitsBADIs/MM/MM01.htm
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/screen-exit-on-mm01-mm02-mm03-322705#
Regards

SD- conditions to be mapped to COPA value field data in BI

Hi Experts,
I have a req where in I have to map condition level Sales order data to some COPA value fields. Currently for one Sale order item there are multiple conditions that means multiple line items. But when I try to find the COPA value field for the same same (Sales order, Sales order item ) key I get only one line item.
This has to be done for BI integration, but needs to be done at the source system level.
So my questions are,
1) How can we get the condition level data from COPA? Is it possible to fetch the data at that granularity?
2) Is it possible to integrate SD & COPA data on condition level i.e. at Sales order, sales order item & condition level.

Hi,
In KEA0, Data structure tab click on pencil button (change view).
Then click on -> change
Now you will be able to select new value fields
Rememeber, after changing click on save, activate and then back button. system will ask for regeneration, click ok.
Regards
Raghu

Add new Fields in KEU1

Hi Friends,
   I want to add new fields in KEU1 for sender as internal order(Create Actual Assessment Cycle). How I can modify the fields in keu1.
Can anybody please tell me how could I do it.
Thanks & Regards.
Edited by: NITIN on Apr 21, 2010 9:44 AM

Hi,
               It is not possible to assess an order to COPA, therefore
the only way should be settling the internal order.Even if there are
any changes made in T811I and T811IA tables, there are no relevant
coding which reads the data from orders and post it to database.
Regards,
MLM

New field DBT.app_data, new flag DB_DBT_USERCOPY

Studying the BDB 4.5.20 header file I noticed a new field in DBT:
void* app_data;
as well as a new flag:
DB_DBT_USERCOPY.
They are not documented. Are they meant to be public?
Karl

No.
The flag and field are used by the Berkeley DB Java API to optimize data copies through JNI, they aren't intended to be public.
Regards,
--keith
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Keith Bostic
Oracle Corporation
[email protected]
keithbosticim (Yahoo IM)

Added new field to cube but data not passed from DSO

Hope someone can help.
(BI 7.0) We added new fields into a cube. The fields already existed in the DSO. When we ran the process chain in development for the first time after making this change, we notice that the 'historical' data for these fields is populated in the cube. When we do this in our quality system only new data passed to the cube is updated. In development in the sub-chain DTP request we see all previous requests listed under selections. In quality it is only the latest request. The only difference is that the DeltaInit flag in the DTP request in development is ticked (extraction mode) - but not in quality. Does anyone know whyb this is?

hi peter,
Adding fields to cube doesn't affect delta status...The delta DTP should be able to handle delta requests automatically.
I guess in you quality system, the cube already got all requests updated from ODS before you importing the change request. And in develop system none of the requests in ODS were updated before the change.
Regards,
Frank

Error while adding a new field to the Segment in we31

Hi ,
I am getting error when i am trying to add the new field to the cust. segment.
It is released for the adding the new fields i am cancelling the release , but i got a message like this
Error while resetting release of segment 'segment name'.
it is comming from the message class EA and message number 259.
Thanks in advance.
Reagrds,
bharani

Hi,
Have you tried Cancelling the release before adding the version?
Select the active version of the IDOC Segment and cancel its release first. Only then you will be able to add a version.
Please let me know if it worked!
Vijay

AET error while creating a new field

Hi Experts,
We have a requirement to create a check box/newfield on Account Details screen in Web UI. I am trying to create a new field using AET but am getting the following error message. Please help.
1. Error during generation of object CI_EEW_BUT000
2. Customizable CSOL conflict for objects changed in other TR.
We have a config TR involving the role field on account details component (BP_HEAD/ACCOUNTDETAILS). Do we need to release the transport before creating any new fields.
The generation of the field fails when I select the extension and click on 'SAVE and GENERATE'.
Please help.
Thanks,
Rohit

Hello Rohit,
Please apply note 1707978 to solve the issue.
thanks
Willie

COPA - New field

Similar Messages

Maybe you are looking for