COPA - Replicating Seasons in COPA

Hi All
I need to configure Seasons from SD to flow into COPA - have no clue where in config am supposed to do that?
thank u for the support
Rukshana

Hi Rukshana,
I am not very sure what you mean by season and what you are trying to capture in that. If you have created it as a charachteristic then you need to have a derivation rule in transaction KEDR.You need to include the charachteristic in your operating concern and KEQ3 as well. if you have created as a value field then the setting is in KE4I.
Regards,
Abhisek

Similar Messages

Replicating COPA derivation rules in BI

Hi All,
We have a requirement where we are creating an extractor and COPA derivation rules available in ECC needs to be replicated in BI. My doubts are-
1. Could this be directly achieved in BI, if yes then how would we maintain sync between the ECC derivation rules and the replicated ones in BI. If there is some update on these rules, how would the respective BI rules get updated?
2.Should this be handled during extraction in ECC itself. If yes, what is the best approach for this?
any pointers catering to the above questions and anything related to mapping derivation rules in BI would be a great help.
Thanks in advance for your help and time.
Regards,
Bansi.

Hi AMK,
As a protocol that is followed on this site, please do provide points in case the replies helped, this helps in motivating the people to keep posting for the queries and also helps in keeping the spirits of the team high.
Regards
Ashish

KE24 - no line items in account-based COPA

Hello,
I am trying to configure Account-based COPA. I did all the configuration and create a report with a form assigned. The account I have posted is a revenue cost element and has profitability segment as an optional field and is updated with segment data.
Since account-based COPA updates only COEP and CE4XXXX tables I am able to see the record being updated in these tables. But when I run KE24 and COPA report both of them yield no results.
Please see attached for the detailed configuration and copa report set up.
Note: I replicated the exact same scenario in another system with same config and also using the same accounts I was able to generate the KE24 and also COPA report. The only difference between these two systems being the database. System where COPA is working is on SQL DB and where it is not is on HANA DB.

Pablo,
My issue was because of HANA Database. So I had run a report called RKE_HDB_EXTEND_COEX which extends the COEP/COEJ tables into HDB. After running this the issue was resolved.
Not sure if you have the same cause. Let me know.
Thanks,
Raj

Copying any text in symbol copies ALL text in symbol

Running Illustrator CS4, Mac 10.5.4, Quad Intel
Selecting any text within a symbol--even one word of a paragraph for instance--copies *all* of the text in the symbol (including text in any nested symbols). (This has been convenient when stripping text into a Word file, but not convenient when trying to do other text tasks.) Happens no matter where in the symbol hierarchy I am.
Has anyone encountered this? Have searched the forum, and the web--can't find any mention anywhere. Have replicated the error on several machines with unique installs of Illustrator.
Any advice or explanation will be appreciated.

Copy the symbol, if you wish paste in front or paste on the canvas outside the artboard.
Break the link.
If you update the symbol delete delinked copy and make a new one. You can hide the copy as well.
Or you might try using variables.

After burning original master with No copies allowed, How to make 1000 copies.

After burning original master with No copies allowed, How to make 1000 copies?
I am authoring a DL DVD disc for a Yoga Institute, after burning original master with No copies allowd condition using, CGMS - CSS conditions, How to make 1000 copies.
If I buy DVD duplicator ( replicator?) and hook up to PC via USB , then use the duplicator burner to make copies, how it works. As I tried on www days, after days, burning my eyes, all information is confusing.
This is challanging project and I am entering newly in the market. So this is my death or life. Please help.
OS WIN7 64 bit, CS5.5 Master Collection
Encore Version 5.1.0.342
Thanks in advance

Thank you Chris and Stan,
Now I got little true idea how it works.
Copy protection is not my idea, as the Yoga intitute is a non profit organization, very little is also very important for them to run the place.
Every little help counts.
What are the other good options to do in house.
Can you please suggest any links for " in detail study."
Again thank you all of you and thanks to Adobe staff also
Aradhana

Runtime error during COPA-Ext

Hi Guys
I am new to SAP BW.
I am trying to schedule an initial load but I end up getting the following error message.
This is an extract from the dump.
call function 'RSAN_LOGSYS_DETERMINE'
        destination g_dest
        exporting
          i_client = l_s_desdisp-rfcclient
        importing
          e_logsys = l_rfclogsys.
      if l_rfclogsys <> p_logsys.
        message x000.
      endif.
    endif.
the p_logsys has my correct system name, but l_rfclogsys has some other name.
The Data flow shows a smooth data flow from the dATA source to my infocube and all transfer/update rules are active. The source system is connected succfully to the bw system. (I replicated succfully).
The strange thing is when I perform a delta upload on older packages, there is no dump!!
Can some one please help!!!!!! Points assured
Thanks and Regards
Sameer

Hi,
where do you get this error? I believe in your source system. If yes, I think you have some records posted in your COPA-tables that correspond to a logical system that doesn't exist anymore. Did you rename the logical system? Did you copy your system from another system?
regards
Siggi

COPA datasource - Infoobject identification / automatic generation

Hi,
I have generated COPA data source in R/3, replicated in on BW side and now I'm trying to map fields to infoobjects (+undestand which ones are key fields for the staging DSO). Data source is deplicated as 7.0 one.
My planned flow is: data source -> write optimized DSO -> standard DSO -> Cube.
I have pdf on COPA extraction from sdn by SAP which says, that BW shoudl automatically either match or generate new Ifobojects for all fields that were direcly maintained in COPA - there should be en option application proposal
Here is the excerpt:
"InfoObjects are only created automatically for value fields and user-defined characteristics if the DataSource is mapped to an InfoSource using the source system view in the SAP BW Administrator Workbench. In this case, a dialog box appears in which you can choose Application Proposal. With this function, any missing InfoObjects are created for value fields, measure unit fields, and the user-defined characteristics described above when the InfoSource is generated."
I assume this si only when data source is 3.5 one? Does it mean that I need to create all infoobject myself (the ones for which I cannot identify business content) as I have 7.0 data source? Is there any benefit for using 7.0 data source?
Second question - are fields like VV001 Intercompany Price - caluclated in COPA? I have several fields that follow the patter VVxxx (xxx being a number) for which I cannot find corresponding content infoobjects.
Could you also give me corresponding infoobjects for fields PRABA (Price reduction - 0PRICE_RED?) and VRPRS
(Stick Value or CoGS - no ide here)?
Thanks in advance.
Edited by: Marcin Byra on Jan 6, 2010 4:35 PM

Hi Voodi,
I followed ur instructions and tried to create a transformation between 3.x infosource and 7.0 datasource. system prompted to create new infsource and copied all the infoobjects which were part of the 3.x standard infosource.
But still system does not propose any infoobjects for the value fields starting with VV* . In BW3.5 for all VV* fields, system used to propose infoobjects strating with 0GV*. Did u get system to propose these infoobjects?
Thanks for ur help

Virtual copies are not synchronized in a second Lightroom catalogue although metadata are written in XMP and synchronization with metadata was selected

Dear community,
I operate one Mac with Lightroom 5.7 that is configured to store all metadata in xmp files. The Lightroom catalogue is stored locally on the Mac and only contains references to the images and their xmp files that are stored on a network device. There is another Mac with the same configuration having a separate local Lightroom catalogue and access to the same images on the network device.
At a starting point, both Lightroom catalogues are identical - they refer to the same images on the network device and contain the same metadata.
When I update image properties on the first Mac, these changes are reflected in the xmp file. After using the option "synchronize" with activated "metadata synchronization" on the second Mac, the modified image properties are visible on the second Mac. This is fine.
However, when I create a virtual copy on the first Mac, I realize that the corresponding xmp file gets updated. However, even after synchronization, the virtual copy is not visible on the second Mac. I may modify image properties of the original image and get these modifications replicated to the second Mac, but the virtual copies remain on the first Mac.
What needs to be done that also virtual copies get synchronized?
Thank you very mich for your support.
Best regards,
Peter

I do not doubt that File Export / File Import will work to transfer the virtual copies.
My question was related to the fact whether the imported folder should not previously exist on the second Mac.
Consider the following situation:
time = 0:
first Mac: folder A is in a first status
second Mac: folder A is in a first status
time = 1:
first Mac: folder A is in a second status, export folder A in second status
second Mac: folder A is in a first status, import folder A in second status
My question is: What happens with these two folder A on the second Mac? Does folder A in the Lightroom catalogue of the second Mac gets overwritten? Do I receive an error message because folder A is already present in the Lightroom catalogue?
I understand your answer that everything will be fine on the second Mac if there is no folder A at all at the second Mac while I import the new folder A. Under this assumption, I can import folder A and it will show the second status. Clearly.
My question is only related to the fact that there is already a folder A on the second Mac, with the same images, but with different metadata and/or virtual copies.

COPA from CO or SD,FI

Would it be easier for BI to extract COPA from CO or would it be easier if BI did it directly from SD and FI ? Also what kind of development time are we looking for the COPA extraction compared to bringing it in from CO or SD and FI directly? What do you recommend?
Thanks
Daniel

Hi Daniel,
Ideally BI should extract COPA data from a COPA datasource being created in R/3 using T code KEB0.
An active operating concern defined in R/3 system is required to create a COPA Data source in R/3. Once The Data Source is created it needs to be replicated to BW and a cube needs to be modelled to hold the data.
The Controlling and Profitability Analysis module is used to analyse the results of the operations based on multi-segments. Example: The sales values can be analyzed on region, product, and customer, and so on.
In an integreated enviornment, the postings will be made from various modules.
If you are looking COPA from FI point of view, you need to activate the Profitability Segment field in the field status groups.
The key steps you need to perform in CO-PA are:
-Decision on costbased or account based or both
-create operating conern
-create / assign characterists and value fields.
-chacteristic values.
-derivation rules.
-characteristic group and assigning to business transactions.
-PA transfer structure.
-Key figure schema.
-Reports.
CE1, CE2, CE3 and CE4 are the tables created when you create a COPA Data source and would be represented as
CE1 *** , CE *** = Line Item Tables
CE2 *** = Plan Line Item
CE3 *** = Value Fields , Key Fig
CE4 *** = Segment Table
Operating Concern name
COPA is of two types -Accounting based and Costing Based. The bewlow sepcified links has all information.
Also Check
http://help.sap.com/bp_biv235/BI_EN/html/BW/COPABaselineAnal.htm
In the above link check out for CO-PA Base line.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/COPA/COPA.pdf

Three copies ARD3, need way to share computer lists

I know the questions has been asked, and answered. I did a search and tried every solution I could find on this forum. But nothing works.
We have 3 copies of ARD3 deployed in one shop. One Task Server (running on our OD replica server), and two ADMIN workstations.
We desperately need to be able to share computer lists!
I have tried copying over:
~/Library/Preferences/com.apple.RemoteDesktop.plist
(and)
/Library/Application\ Support/Remote\ Desktop
...but while our Unix command (and other) templates, labels, and history lists make it over...our computer lists do not. This is a HUGE problem as we try to work as a team in large environments.
We have spent $1500 on ARD 2.2, and ANOTHER $1500 on ARD 3.2 and are still not able to sync lists. ARD is great stuff, but we need guidance (a step by step procedure) for copying computer lists from one computer to another.
Thanks,
Don

Yes, it used to work...but for some reason it doesn't anymore. Not sure why. All the other settings come over (Unix templates, Reports templates, Labels, etc.) but the computer list shows up blank. When I copy over the plist file, I'm prompted for a password...none work, so I have to reset...I wonder if that's causing it?
Thanks,
Don

COPA Delta Mechanism

Hi All,
Can any one explain about Delta Mechanism in COPA ie.,
How delta works in COPA,
From where the delta record are picked,
When the Delta Queue is filled,
what is Safety Delta,
What is Relignment and when we go for that, etc.....
Thanks in Advance,
Regards
Ramakrishna Kamurthy

Hi Ramakrishana,
Up to and including Plug-In Release PI2003.1, a DataSource is only
defined in the current client of the R/3 System. This means that a
DataSource can only be extracted from this client. The DataSource has a
timestamp for the delta method, and this timestamp is only valid for th
current client. This timestamp is managed by Profitability Analysis.
With Plug-In Release PI2004.1 (Release 4.0 and higher), timestamp
management was converted to a new method, called generic delta. This
method works in connection with an SAP BW system with Release 2.0 and
higher. With this method, timestamp management is no longer performed b
Profitability Analysis, but instead by the Service API (interface on th
R/3 side between Profitability Analysis and SAP BW). Exclusively in
Release 3.1I, Profitability Analysis continues to support timestamp
management.
Compared to timestamp management in Profitability Analysis, the generic
delta allows for several enhancements:
o   You can apply the delta method simultaneously using the same
     DataSource from more than one R/3 System client because a separate
     timestamp is saved for each logical system.
o   You can apply the delta method for the same R/3 System client
     simultaneously using the same DataSource from several SAP BW
     systems.
o   You can perform several initializations of the delta method with
     different selections using the same DataSource from a given SAP BW
     system for the same R/3 System client.
o   The DataSource commands the Delta Init Simulation mode. With
     timestamp management in Profitability Analysis, this mode had to be
      implemented using the Simulate Delta Method Initialization function
      (see SAP Note 408366).
For more information on the generic delta, see Delta Transfer, whereby
the steps of the Specify Generic Delta for a DataSource section are
performed automatically for Profitability Analysis when a DataSource is
created. For this, the field determining the delta is taken as the
timestamp for Profitability Analysis (TIMESTMP), and the timestamp is
stored for summarization levels and line item tables. However, in
contrast to generic DataSources, the TIMESTMP field is not generated in
the extraction structure because this is not necessary for DataSources
in Profitability Analysis. As with timestamp management in Profitabilit
Analysis, an upper limit of 30 minutes is set as the safety interval.
You find the timestamp of a DataSource for the delta method in the
current logical system either in the Header Information for the
DataSource using the IMG activity Display Detailed Information on
DataSource or using the IMG activity Check Delta Queue in the Extractor
IMG. The timestamp is shown here when you choose the selection button i
the Status column for the combination of DataSource and SAP BW system.
DataSources created after implementing PI2004.1 automatically apply the
new method. DataSources that were created in Plug-In releases prior to
PI2004.1 still continue to use timestamp management in Profitability
Analysis but can be converted to the generic delta. For this, an
additional selection option Convert to Generic Delta appears in the
selection screen of the IMG activity Create Transaction Data DataSource
when a DataSource with timestamp management in Profitability Analysis i
entered. Conversion from the generic delta to timestamp management in
Profitability Analysis is not supported.
Conversion is only possible for DataSources that are defined in the
current client of the R/3 system and for which the delta method has
already been successfully initialized or for which a delta update has
successfully been performed. This is the case once the DataSource has
the replication status Update successful. Furthermore, no realignments
should have been performed since the last delta update.
For the conversion, the timestamp for the current R/3 System client is
transferred from Profitability Analysis into the timestamp of the
generic delta. In this way, the transition is seamless, enabling you to
continue to perform delta updates after the conversion. If delta updates
are to be performed from different R/3 System clients for this
DataSource, you first need to initialize the delta method for these
clients.
The conversion must be performed separately in each R/3 System because
the timestamp information is always dependent on the current R/3 System
and is reset during the transport. If, however, a converted DataSource
is inadvertently transported into a system in which it has not yet been
converted, delta extraction will no longer work in the target system
because the timestamp information is deleted during the import into the
target system and is not converted to the timestamp information of the
generic delta. If in this instance no new delta initialization is going
to be performed in the target system for the DataSource, you can execute
program ZZUPD_ROOSGENDLM_FROM_TKEBWTS from SAP Note 776151 for the
DataSource. This program reconstructs the current time stamp information
from the information for the data packages transported thus far and
enters this time stamp information into the time stamp information for
the generic delta. Once this program has been applied, delta extraction
should work again. Normally, however, you should ensure during the
transport that the DataSource uses the same logic in the source system
and the target system.
After the conversion, the DataSource must be replicated again from the
SAP BW system.
A successful conversion is recorded in the notes on the DataSource,
which you can view in the IMG activity Display Detailed Information on
DataSource.
Since the generic delta does not offer any other log functions apart
from the timestamp information (status: Plug-In Release PI2004.1),
Profitability Analysis still logs the delta initialization requests or
delta requests. However, the information logged, in particular the
timestamps, only has a statistical character because the actual
timestamp management occurs in the generic delta. Since the delta method can be performed simultaneously for the same R/3 System client using the
generic delta from several SAP BW systems, the information logged is
stored for each logical system (in R/3) and SAP BW system. When a delta
initialization is simulated, only the timestamp of the generic delta is
set; Profitability Analysis is not called. Consequently, no information
can be logged in this case. Messages concerning a DataSource are only
saved for each logical system (in R/3). You can use the IMG activity
Display Detailed Information on DataSource to view the information
logged.
Another enhancement from Plug-In Release PI2004.1 means that you can no
longer exclusively perform full updates for DataSources of the Extractor
Checker of the Service API that have recently been created or converted
to the generic delta. The following update modes are possible:
o   F - Full update: Transfer of all requested data
o   D - Delta: Transfer of the delta since the last request
o   R - Repeat transfer of a data package
o   C - Initialization of the delta transfer
o   S - Simulation of the initialization of the delta transfer
In the case of all update modes other than F, you have to specify an SAP
BW system as the target system so that the corresponding timestamp
and/or selection information for reading the data is found. The Read
only parameter is set automatically and indicates that no timestamp
information is changed and that Profitability Analysis does not log the
request.
Update mode I (transfer of an opening balance for non-cumulative values)
is not supported by Profitability Analysis.
Assign Points if useful
Regards
Venkata Devaraj

Regarding COPA extraction

Hi All,
We have created a datasource for COPA(Account Based), used generic InfoCube, replicated DataSources and created TR and UR.
The data is available in R/3. But when we are checking the data in RSA3. Obviously, we are unable to extract the data to BW. Can anybody provide us with a solution for this situation.
Regards
YJ

Hi PRK,
First of all thank you for your interest.
Let me explain you clearly:
When I am extracting the data using Extractor Checker, first I am receiving the following error:
'Make an entry into all the required fields'
Next I entered the values for 'Controlling Area', 'Company Code' and 'Period/year'(I had entered the correct date format).
Next I am receiving the following error:
'Errors occured during extraction'
I will be thankful for your help.
Regards
YJ

Create Multiple Copies of a Field - Mac

I'm trying to make multiple copies of a field using DC on a Mac. The directions/support indicate that I should "right click" on the field - which, of course, cannot be done on a Mac. So how do I create multiple copies of a field on a Mac?
In general, all of the directions for creating forms assume I am on a PC. Where/How do I find directions for creating forms with DC on a Mac?
Thanks,
Lawrence

Hi Lawrence,
Please let me know the os version and hardware model of your mac.
Please refer this link, it 'might' help with your mac right click issue - http://www.wikihow.com/Right-Click-on-a-Mac
I have replicated this issue for you on my mac, please refer the below screenshot and let me know if you still face a challenge.
and this would lead to the following window :
Now does this helps? Please feel free if you still have any question.
Regards,
Rahul

PLIKZ field for COPA data source not there in Extract structure.

Hello all,
When I create a data source for COPA the PLIKZ field from the segment level is not maintained in the Extract structure and it is not replicated to BW also. But the other field GJHAR is maintained in the Extract structure which is also there in the segment level!!
Clarify me why it is not available in extract structure? Also we are in 4.7 version and 3, 5 in BW.
Points will be assigned!!!
Thanks
Ram

Hello Friends,
Could some one help me why the field PLIKZ is not available in the Extract structure when i create a COPA Data source?
Need ur suggestions urgently!!!
Helps please
Thanks in advance once again

Windows copies in smartforms

Hi
I need to print the same information in two window in the same page ( the information printed in both windows are identical).
I am creating a new smartform , and I using the funcionality "Copies Window" for do two main window in the same page.
Now, when I do any change or changes inside my 'main window', could replicated automatically in ' main window copies ' but this not occurs.
I know that is posible using Sapscript but is it posible using smartforms?
Best regards
Gregory Gotera

Hi Gregory
You can take copies of your window in smartform
Regards
Arun VS

COPA - Replicating Seasons in COPA

Similar Messages

Maybe you are looking for