Difference between COPA and BW

Hi,
I want to know what are the difference between COPA and BW. Some one already implemented COPA for our client and now the client is asking what are the advantages of implementing of BW and Why they are going for BW? Because already COPA was already implemented.
Sateesh

Hi,
BW is a business warehouse of OLAP-type for SAP. BW has several standard 'cubes' for every component in SAP; GL, FM, etc. Amongst them there is also CO-PA. CO-PA by itself is sort of OLAP-cube, so putting it to BW could be only from technical reasons (perfomance, for example) or customer-specific definitions. In BW, like every modern OLAP tool, you can build your own cubes, merge several cubes, define additional key figures, build sophisticated reports, etc. Thus, it's more powerful tool in terms of BI analysis. Therefore, situation where you need BW only for CO-PA is possible and potentially justified.
Regards,
Eli

Similar Messages

Difference between COPA and COPA cube

Hello,
We have recently implemented COPA. There is a difference between COPA R3 and COPA BW. What can be the reason. Can it be internal orders if so how can we check and correct that.
thanks

Hi,
Where can you find the difference ? In the data being pulled into BW ?
First check for a sample data in R/3 RSA3 and see data for the same selections in BW PSA or any staging layers.
Reconciliation Analysis in Financial Accounting
http://help.sap.com/saphelp_46c/helpdata/en/03/fb58a20d9611d3b65e0000e82d962e/content.htm
ECC FI and BW Reconciliation
R/3 - BW reconcilation
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/968dab90-0201-0010-c093-9d2a326969f1
Hope this helps.
Thanks,
JituK

Difference between COPA and Logistic Delta Mechanisam

Dear All,
May i knw the difference between the COPA and Logistic Delta Mechanisam h it works.
In our Production system, when ever a logistic delta fails we take action and repeat it then it will featch the delta on the same day,
where as in COPA delta, when it fails we take action and when we repeat it will fetch zero records and in the next day the delta will come.
What is the difference in both
What exactly is happeing in R/3 for these both delta mechanisam.
Thanks in advance,
K Janardhan Kumar

Hi Guru,
I will explain about delta extraction with timestamp in general with an example:
timestamp is generally in yyyymmddhhmmss format
let's assume delta runs daily at 09:00 morning.Last delta ran at 09.00 yestreday.And today when delta runs it picks the data ranges between
09:01 (yesterday's) to 09:00(today).
if one record is posted at 09:10 today,then it will not be picked by today's delta(coz' it is posted after 09:00)
Hope now you are clear about timestamp.........
In case of COPA ,we are using timestamp as a tool to identify delta
now COPA delta mechanism has one more concept "saftey delta ":let's put a question to ourselves ,why we should use this;
SAP answer is "The reason for the selection of the safety delta is that there are possible level differences of the clocks on different application servers. If the delta is selected on a level that is too low, it is possible that records
are not taken into account when uploading into the BW."
'Safety delta' usually will be set to 30 mins during the initialization /delta upload(default).
This means that only records that are already half an hour old at the starting point of the upload are loaded into BW
Ex:
we have made following settings for copa
timestamp=09:00
safety delta=30 mins
now when you run daily delta,it picks data ranges between (current timestamp-safety delta) i.e 08:30 instead of 09:00(yesterday's)
to 09:00 today
check this oss notes 502380 for better understanding on COPA delta mechanism
Symptom
There is some confusion about how the delta process works with CO-PA DataSources and the old logic (time stamp administration in the Profitability Analysis) or there are data inconsistencies between the BW and OLTP systems.
As of PlugIn Release PI2004.1 (Release 4.0 and higher), a new logic (generic delta) is used during the delta process. Old DataSources can be converted to the new logic. New DataSources automatically use the new logic. With the new logic, the time stamp administration is located in the Service-API and no longer in the Profitability Analysis.
This note refers only to DataSources with the old logic.
Reason and Prerequisites
Administration of the delta process for CO-PA DataSources partly occurs in the OLTP system. In particular, the time up to which the data was already extracted is stored in the DataSource control tables (old logic).
Solution
Since the control tables for the delta process for the extractor are managed in the OLTP, the following restrictions apply:
1. There should only ever be one valid initialization package for a DataSource. Data inconsistencies may occur between BW and OLTP if, for example, you schedule an Init for various selections for the same DataSource and data is posted between the individual initializations to the Profitability Analysis. The reason for this is that each time the time stamp for the DataSource is initialized in the OLTP, the current value (minus the safety delta, see note 392876) is reset. Records from a previous selection are therefore no longer selected with the next delta upload if they were posted before the last initialization run with another selection.
2. Initialization can always only be carried out from one system. Inconsistencies may occur if the same DataSource is used from several BW systems and if data is posted between the initialization runs. This is because the time stamp for the replication status is reset for every initialization or delta upload in the OLTP. Records may therefore be missing in the system that was first updated if updates were made in the result area before the Init or delta run. In the system that was the second one to be updated, the records that were loaded into the first system are missing for a delta upload.
In the case of large datasets, you should therefore perform initialization either using several DataSources or with a combination of one or more full uploads and an init upload. Full uploads without errors are possible for closed periods/fiscal years because no additional changes are made to this data. Initialization should be performed, for example, from the current fiscal year. The full updates for the closed periods can also be split in time. If required, more characteristics, for example, the action type, can also be used for the selection. For information on the period selection, see note 425844
Hope you are clear now!!!!!!!!!
Cheers
Swapna.G
Message was edited by:
swapna gollakota

Difference between COPA-PCA

HI Guru's,
What are the major differences between COPA and PCA..
regards
JK

Hi,
this is a pure consulting issue and cannot be dealt within a few sentences.
PCA and COPA can be used simultaneously.
Please have a look on http:// help.sap.com --> ERP (english documentation) --> SAP ERP Central Component --> Financials --> Enterprise Controlling (EC) (for information regarding PCA) or follow the path Controlling (CO) --> Profitability Analysis (COPA) regarding information of COPA.
For a brief comparison between COPA and PCA follow the path:
Enterprise Controlling --> Profitcenter Accounting --> The Concept of Profit Center Accounting --> Role of Profit Center Accounting in the SAP System --> The Distinction Between Profit Center Accounting and Profitability Analysis (CO‑PA):
Profitability Analysis (CO‑PA), like Profit Center Accounting, is another form of profitability accounting. However, it is incorporated in operative cost accounting. That means that the profitability segments in CO‑PA are accounting assignment objects and are thus directly integrated in the flow of data in cost accounting.
In contrast to EC-PCA, where profits are found for areas of responsibility within the company, CO-PA lets you analyze the profitability of different segments of your operative business -- defined according to products, customers, orders, or any combinations or groups of these -- or organizational units, such as company codes or business areas. The aim of CO-PA is to provide the accounting department and decision-makers in sales, marketing, product management and corporate planning with information about the market.
You can define the master data and basic structures in CO‑PA flexibly to meet your companys specific requirements. By choosing just the objects for evaluation (characteristics) and key figures you require, you can create a company‑specific multidimensional structure for analysis.
Unlike EC‑PCA, CO‑PA lets you use an account‑based or a costing‑based approach. In the costing‑based approach, you can define your own value fields for analysis. In account‑based CO‑PA, the values are represented in accounts.
EC‑PCA and CO‑PA should not be regarded as alternative components. On the contrary, they complement one another and jointly provide you with a flexible and comprehensive profitability accounting tool, allowing you both a market‑oriented viewpoint as well as a responsibility‑ and person‑oriented one.
Best regards,
Andreas

GR/IR account clearing using MR11 causing differences between FI and COPA

Hi All,
We have Costing based Profitability Analysis enabled. We are facing an issue in 3rd party drop ship orders and COPA. Cost of Goods Sold Drop Ship GL account is being charged when we use MR11 to clear GR/IR account. This is causing reconciliation issues between COPA and the General Ledger.
Does anybody know how to update COPA when we carry out GR/IR clearing using MR11. Is there a workaround?
Any clues will be highly appreciated.
Thanks.
Ram

Hi ram
I have a couple of questions
1. Is the 100 USD of Sales order amount, the sale order value to be billed to the customer or the value of the goods to be delivered to the customer
2. You said that Gr is done for 99, but MIRO is done for 100... Is this a case of price difference?
3. you said upon customer billing, 100 is posted to COGS in COPA....How does the system gets this value, Is this the VPRS value or any thiing else?
Also, when you reply back, I would need one more info from you... Follow the following steps
1. Take the GRIR clearing document (material doc no), where in the 1 USD is posted to COGS
2. Go to table ACCTIT and enter this doc no
3. You will find the line items posted in this doc... Just check against this 1 USD line item, what is the transaction key i.e. GBB or PRD or what else?
Regards
Ajay M

Difference Between Cost and Account Based COPA

Hi
What is the difference between Cost and Account based COPA from a BI perspective ( both functionally and technically)
Thanks
Rashmi.

Hi Rashmi,
Greetings.
There is lot of reading material available on forums and help.sap.com
For start you can try with this:
Link:[http://help.sap.com/saphelp_46c/helpdata/en/7a/4c37ef4a0111d1894c0000e829fbbd/content.htm]
Thanks
Sachin

Difference in Price per unit and Standard cost between COPA and PCA

Hi
I did a comparison between COPA and PCA for January. For few products,there is a difference in the Standard cost and PPU between the two reports(product wise). What might possibly be the reason for the difference. And how to analyze the root cause of this difference.
Thanks
Jaswanth

Hi
By PPU - Do you mean PUP i.e. Per Unit Price of Material Ledger??
If yes, then you are not comparing apple to apple.. Std cost is bound to be diff than actual cost
br, Ajay M

Difference between photoshop and illustrator effects?

Under the effects menu in cs5, what is the difference between photoshop and illustrator effects? when do you use the photoshop ones?
Thank you.

The Photoshop effects are copies of similar effects from Photoshop. As such, they can only be applied to raster art, such as that edited in Photoshop. When you apply a Photoshop effect the Illustrator art you apply it to is rasterized in the background and the effect is applied to the rasterized version of the art. If you expand the appearance of anything with a Photoshop effect on it it will be rasterized. The other effects retain all or part of the vector art. When you expand the effect or save a PDF at least some of the original vector art will remain as vectors, although some effects (Drop Shadow, Blur, Feather, Inner Glow, etc.) to add rasterized art to the file.
The rasterization is non-damaging, in that the original vector, type, or other objets remain fully editable. If you remove the effect the rasterization goes away. There is no dialogue for rasterization resolution in the effect; you set that in Effect > Document Raster Effect Settings.

Difference between exipre and obosolete

Hi ALL,
WHAT IS THE EXACT DIFFERENCE BETWEEN exipre and obosolete WITH REFERENCE RMAN.

afzal wrote:
Hi ALL,
WHAT IS THE EXACT DIFFERENCE BETWEEN exipre and obosolete WITH REFERENCE RMAN.As it was mentioned above, obsolete means that the backup is no longer needed according the retention policy. But the expired means that couldn't be found after CROSSCHECK command executed. See the following example. In this example the retention policy is set to redundancy 1 which means that the backup which have more than one copy, is marked as an obsolete. Then I delete a backup, run CROSSCHECK command and see that the deleted backup marked as EXPIRED
RMAN> show retention policy;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
RMAN> backup datafile 2;
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
no obsolete backups found
RMAN> backup datafile 2;
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Backup Set           1      30-JAN-11
Backup Piece       1      30-JAN-11          /u01/oracle/product/10.2.0/db_1/flash_recovery_area/TEST/backupset/2011_01_30/o1_mf_nnndf_TAG20110130T131902_6nbc877l_.bkp
RMAN> list expired backup;
RMAN> exit
Recovery Manager complete.
[oracle@linux_server ~]$ rm -rf /u01/oracle/product/10.2.0/db_1/flash_recovery_area/TEST/backupset/2011_01_30/o1_mf_nnndf_TAG20110130T131902_6nbc877l_.bkp
[oracle@linux_server ~]$ rman target /
RMAN> list expired backup;
using target database control file instead of recovery catalog
RMAN> crosscheck backup;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=159 devtype=DISK
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/u01/oracle/product/10.2.0/db_1/flash_recovery_area/TEST/backupset/2011_01_30/o1_mf_nnndf_TAG20110130T131902_6nbc877l_.bkp recid=1 stamp=741791943
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u01/oracle/product/10.2.0/db_1/flash_recovery_area/TEST/backupset/2011_01_30/o1_mf_nnndf_TAG20110130T131914_6nbc8lh0_.bkp recid=2 stamp=741791954
Crosschecked 2 objects
RMAN> list expired backup;
List of Backup Sets
===================
BS Key Type LV Size       Device Type Elapsed Time Completion Time
1       Full    18.72M     DISK        00:00:03     30-JAN-11
        BP Key: 1   Status: EXPIRED Compressed: NO Tag: TAG20110130T131902
        Piece Name: /u01/oracle/product/10.2.0/db_1/flash_recovery_area/TEST/backupset/2011_01_30/o1_mf_nnndf_TAG20110130T131902_6nbc877l_.bkp
List of Datafiles in backup set 1
File LV Type Ckp SCN    Ckp Time Name
2       Full 516141     30-JAN-11 /u01/oracle/product/10.2.0/db_1/oradata/test/undotbs01.dbf
RMAN>

Difference between Import and Add

Just curious what the difference between Import and Add File/Folder in iTunes is? I know consolidate will create a copy of your files and put them into the iTunes library.

Import is for audio files.
Add to library is for MP3, AAC, Apple Aossless, aiff and wav files.
I know consolidate will create a copy of your files and put them into the iTunes library.
Close. The iTunes library what is in iTunes.
Consolidate copies the files into the iTunes music folder.

Difference between collect and move stmts

hi
anyone plz explain...
1. Difference between collect and move stmts
2. Badi and user exit.
gowri

Hi,
1.COLLECT:COLLECT is used to create unique or compressed datsets. The key fields are the default key fields of the internal table itab .
If you use only COLLECT to fill an internal table, COLLECT makes sure that the internal table does not contain two entries with the same default key fields.
If, besides its default key fields, the internal table contains number fields,the contents of these number fields are added together if the internal table already contains an entry with the same key fields.
If the default key of an internal table processed with COLLECT is blank, all the values are added up in the first table line.
If you specify wa INTO , the entry to be processed is taken from the explicitly specified work area wa . If not, it comes from the header line of the internal table itab .
After COLLECT , the system field SY-TABIX contains the index of the - existing or new - table entry with default key fields which match those of the entry to be processed.
COLLECT can create unique or compressed datasets and should be used precisely for this purpose. If uniqueness or compression are unimportant, or two values with identical default key field values could not possibly occur in your particular task, you should use APPEND instead. However, for a unique or compressed dataset which is also efficient, COLLECT is the statement to use.
If you process a table with COLLECT , you should also use COLLECT to fill it. Only by doing this can you guarantee that the internal table will actually be unique or compressed, as described above and COLLECT will run very efficiently.
If you use COLLECT with an explicitly specified work area, it must be compatible with the line type of the internal table.
In 'move' the actually data copies into another data field
2.
Difference between BADI and USER-EXIT.
i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
ii) BADI's are oops based.
A. BAdI Definition
1. SE18
2. Enter the name for the BAdI to be created in customer namespace and press "Create".
3. Enter a definition for your BAdI and on the interface tab enter a name for the BAdI interface. SAP proposes a name and it is pretty good. Meanwhile a BAdI class is also created which is not in our concern.
e.g for "ZTEST", SAP proposes "ZIF_EX_TEST" for the interface and "ZCL_EX_TEST" for the class.
4. Save your BAdI.
5. Double-click on the interface name. It will pass to a Class Builder session to make you implement your interface. If you are not familiar to the Class Builder; it's a bit like Function Builder and it will be easy to discover its procedure.
6. Save and activate your interface.
B. Calling your BAdI from an application program
1. Declare a reference variable with reference to the Business Add-In interface.
e.g. DATA exit_ref TYPE REF TO zif_ex_test.
2. Call the static method GET_INSTANCE of the service class CL_EXITHANDLER. This returns an instance of the required object.
e.g.
CALL METHOD CL_EXITHANDLER=>GET_INSTANCE
CHANGING instance = exit_ref .
3. After those two steps, you can now call all of the methods of the BAdI where it is required in your program. Make sure you specify the method interfaces correctly.
C. BAdI Implementations
1. SE19
2. Enter the name for the BAdI implementation to be created in customer namespace and press "Create".
3. It will request the BAdI definition name to which this implementation will be tied.
4. Enter a definition for your implementation and on the interface tab enter a name for the implementing class. Again SAP proposes a name and it is pretty good.
e.g for "ZIMPTEST", SAP proposes "ZCL_IM_IMPTEST".
5. Save your implementation.
6. To implement a method, just double-click on the method name and you will be taken to the Class Builder to write the code for it. Here you redefine the BAdI interface methods.
7. You must activate your implementation to make it executable. You can only activate or deactivate an implementation in its original system without modification. The activation or deactivation must be transported into subsequent systems
Regards

Difference between Null and null?

What is the difference between null and NULL?
When is each used?
Thanks,

veryConfused wrote:
There is a null in java, but no NULL. null means no value. However, when assigning value, the following is different:Although the empty String has no special role. Null means, the referential type is not assigned (doesn't refer) to a specific object. The empty String is just another object though, so seeing it or pointing it out as something special when it actually isn't at all (no more special than new Integer(0) or new Object[0]) just adds to the confusion.

Difference between GUI_UPLOAD and WS_UPLOAD

Hi,
Please make me clear about the difference between GUI_UPLOAD and WS_UPLOAD. In which cases we need to use these modules...??
Thanks,
Satish

I would suggest to always use the GUI_UPLOAD. I say this because this is the function module which is used in the GUI_UPLOAD method of the class CL_GUI_FRONTEND_SERVICES.   Really, you should probably use the class/method instead of the function module.
data: filename type string.
filename = p_file.
call method cl_gui_frontend_services=>gui_upload
         exporting
              filename                = filename
              filetype                = 'ASC'
         changing
              data_tab                = iflatf
         exceptions
              file_open_error         = 1
              file_read_error         = 2
              no_batch                = 3
              gui_refuse_filetransfer = 4
              no_authority            = 6
              unknown_error           = 7
              bad_data_format         = 8
              unknown_dp_error        = 12
              access_denied           = 13
              others                  = 17.
Regards,
Rich Heilman

Difference between char and varchar, also the difference between varchar2

Hi,
Can anyone explain me the difference between char and varchar, and also the difference between varchar and varchar2...

Varchar2 is variable width character data type, so if you define column with width 20 and insert only one character to tis column only, one character will be stored in database. Char is not variable width so when you define column with width 20 and insert one character to this column it will be right padded with 19 spaces to desired length, so you will store 20 characters in the dattabase (follow the example 1). Varchar data type from Oracle 9i is automaticlly promoted to varchar2 (follow example 2)
Example 1:
SQL> create table tchar(text1 char(10), text2 varchar2(10))
2 /
Table created.
SQL> insert into tchar values('krystian','krystian')
2 /
1 row created.
SQL> select text1, length(text1), text2, length(text2)
2 from tchar
3 /
TEXT1 LENGTH(TEXT1) TEXT2 LENGTH(TEXT2)
krystian 10 krystian 8
Example 2:
create table tvarchar(text varchar(10))
SQL> select table_name,column_name,data_type
2 from user_tab_columns
3 where table_name = 'TVARCHAR'
4 /
TABLE_NAME COLUMN_NAME DATA_TYPE
TVARCHAR TEXT VARCHAR2
Best Regards
Krystian Zieja / mob

The difference between Lion and Mountain Lion

Can some one explain to me the difference between Lion and Mtn Lion? I'm currently 10.6.8 Is it beneficiall for me to upgrade?

Mountain Lion is an enhanced version of previous OS X and so that is Mavericks.
About upgrading it all depends on what your needs are and if your hardware supports it.
System requirements for OS X Lion
System requirements for OS X Mountain Lion
OS X Mavericks: System Requirements
Please check also applications compatibility. From Lion onward, you cannot run PPC application.

Difference between COPA and BW

Similar Messages

Maybe you are looking for