CO-PA

[Former Member]

Hi , i have no knowledge in CO-PA. But now i am assigned n this part. Please help me

[Former Member · Accepted solution]

Hi

Before you start COPA - u need to get a fair view of SD conditions, and decide on your data structure

Pls contact me if you wish to at kat_sreedhar@yahoo.com

I can help u out but need quite a few information before we start

[Former Member]

Hi,

COPA

SAP R/3 4.7

March 2004

English

Profitability Analysis (J17)

SAP AG

Neurottstr. 16

69190 Walldorf

Germany Building Block Configuration Guide

Copyright

© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without

the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic Server™ are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Activate Profitability Analysis

2. Make the following entries:

COAr Year P I OpCo P

BP01 2003 2 BPDE

9 Master Data

9.1 KA01 Create Additional Cost Elements - New

Use

Create all cost elements for manually as described below.

Prerequisites

The accounts for these cost elements already exist in the company code. This has been configured by installing the Core FI Germany building block.

Procedure

1 Access the activity using one of the following navigation options:

SAP R/3

Role Menu Installation  Master Data  Create Primary Cost Element

Transaction code KA01

SAP menu Controlling  Cost Center Accounting  Master Data  Cost Elements  Individual Processing

2. Activities: Enter cost element key and valid-from and valid-to date, then click button Master data and enter remaining data. Then choose Save.

3. Overview of data records:

Key Valid from Valid to Descripton Long Text CE Cat

500000 01.01.2000 31.12.9999 Sales revenue dom. Sales revenue domestic 11

500100 01.01.2000 31.12.9999 Other sales deduc. Other sales deductions 12

501000 01.01.2000 31.12.9999 Sales revenue for. Sales revenue foreign 11

502000 01.01.2000 31.12.9999 Sales revenue aff. Sales revenue affiliated companies 11

503020 01.01.2000 31.12.9999 Revenue hours(SP) Revenue from hours (Service Provider) 11

503030 01.01.2000 31.12.9999 Revenue third Party Revenue third Party 11

503040 01.01.2000 31.12.9999 Revenue Expenses Revenue Expenses 11

518200 01.01.2000 31.12.9999 Customer rebates Customer rebates 12

Result

Additional cost elements have been created.

9.2 KA02 Change Additional Cost Elements - Text

Use

This activity is performed to add country-dependent texts.

Prerequisites

The cost elements for which this activity provides the country-dependent texts have been created in the previous step.

Make sure that you are logged on to the system in your country language before performing this activity.

Procedure

1. Access the activity using one of the following navigation options:

SAP R/3

Role Menu Installation  Master Data  Change Cost Element

Transaction code KA02

SAP menu Controlling  Cost Center Accounting  Master Data  Cost Elements  Individual Processing

2. Activities: Enter cost element key, then click button Master data and enter remaining data. Choose Save.

3. Overview of data records:

Key Descripton Long Text

500000 Umsatzerlöse Inland Umsatzerlöse Inland

500100 Sonst. Erlösschm. Sonstige Erlösschmälerungen

501000 Umsatzerlöse Ausland Umsatzerlöse Ausland

502000 Umsatzerlöse Verbund Umsatzerlöse Verbundene

503020 Erlöse Servicel.(SP) Umsatzerl.aus Serviceleistungen

503030 Erlöse Fremdlstg(SP) Umsatzerl.aus Fremdleistung

503040 Erlöse Auslagen (SP) Umsatzerlöse aus Auslagen

518200 Kundenboni Kundenboni

Result

Country-dependent texts of additional cost elements have been added.

9.3 Change Cost Element Group

Use

The purpose of this activity is to assign all cost elements to one of the cost element groups.

Procedure

1. Access the activity using one of the following navigation options:

SAP R/3

Role Menu Installation  Master Data  Change Cost Element Groups

Transaction Code KAH2

SAP Menu Accounting à Controlling à Cost Center Accounting à Master Data à Cost Element Group à Change

On the Change Cost Element Group: Initial Screen, provide cost element group and choose Hierarchy.

On the Change Cost Element Group: Structure screen, choose button Cost Element.

Provide minimum and maximum value of cost element range to be assigned. Then choose Save.

Data Records:

Group min max

BP_REV #500000 #500000

BP_REV #500100 #500100

Result

You have assigned all cost elements to a cost element group.

10 Troubleshooting in CO-PA

10.1 Inconsistencies in Derivation Rules/Creation of Billing Document Not Possible

10.1.1 Installation of SAP Note 446279

Use

This sections describes how to use SAP Note 446279 to fix inconsistencies in the derivation rules in CO-PA.

They might occur in case of client copies, installation of different operating concerns via BC Set with different derivation rules.

Please use the report RKEDRCHECK described in this section to check whether you have inconsistencies in your operating concern.

Procedure

1. Access the activity using one of the following navigation options:

SAP R/3 Troubleshooting in CO-PA

Transaction SA38

User Menu System  Services  Reporting

2. On the Screen “ABAP Execute Program” fill in the program name RKEDRCHECK and choose Execute (F8).

3. On the Characteristic Derivation: Check table screen, the following two options are offered to the user:

Description

1. Check in all clients

2. Delete inconsistent steps

4. Choose Check in all clients and then choose Execute to see whether you have inconsistencies in your system.

5. Choose the Back button.

6. In case you had inconsistencies, select Delete inconsistent steps and choose the Execute button.

7. Save your entries and choose the Back button.

Result

The inconsistencies in the derivation tables have been removed. If your problem is not solved, proceed with the next section.

10.1.2 Regeneration of Derivation Rules

Use

Sometimes it can occur that derivation rules are inconsistent and that inconsistencies are not removed by processing SAP Note 446279. In this case, you can try to solve the problem by regenerating derivation rules.

Procedure

1. Access the activity using one of the following navigation options:

SAP R/3 Troubleshooting in CO-PA

Transaction KEDR

IMG Menu Controlling  Profitability Analysis  Master Data  Define Characteristic Derivation

On the Characteristic Derivation: Display Strategy screen, choose menu path Extras  Regenerate. Confirm when the dialog box appears.

Result

The derivation rules have been regenerated.

10.1.3 Manual Removal of Inconsistencies in the Derivation Rules

Use

If neither processing SAP Note 446279 nor regenerating derivation rules resolves your problem, derivation rules must be edited manually.

Procedure

1. Access the activity using one of the following navigation options:

SAP R/3 Troubleshooting in CO-PA

Transaction KEDR

IMG Menu Controlling  Profitability Analysis  Master Data  Define Characteristic Derivation

2. On the Characteristic Derivation: Display Strategy screen, choose Display all Steps.

3. Mark first step of type Table lookup and choose Details. The step is likely to be inconsistent when on Characteristic Derivation Display Table Lookup screen on tab Definition in area Source Fields for Table Lookup in column Origin there is more than one different table mentioned.

4. If this is the case, try to understand by logical means what the step is supposed to do. In particular, memorize or write down table and field names used. Try to figure out which of the tables mentioned (see step 3) makes sense considering the characteristic to be derived. (For example, if the sales office is to be derived, table MARA (Material Master) makes no sense as the origin table, as the sales office derives from customer related and not from material related data).

5. Choose the Back button.

6. On the Characteristic Derivation: Display Strategy screen, choose the Change button. Select the step examined earlier if inconsistent and choose Delete Step.

7. Create corrected step based on your findings of step 4. To do so, refer to Define Characteristic Derivation section.

8. Repeat steps 3 to 7 for all steps of category Table Lookup.

Result

The inconsistencies in the derivation rules have been removed. If you worked carefully, you should have derivation settings equivalent to what they had supposed to be before.

10.2 General Troubleshooting – Regenerating the Operating Concern

Use

Regenerating the operating concern is a useful instrument in all kinds of troublesome situations in profitability analysis. While regenerating the operating concern, the system automatically provides for data consistency, which makes it possible to use this instrument of trouble shooting even after transaction data has been created.

Procedure

1. Access the activity using one of the following navigation options:

SAP R/3 Troubleshooting in CO-PA

Transaction KEA0

IMG Menu Controlling  Profitability Analysis  Master Data  Define Characteristic Derivation

2. On the Maintain Operating Concern screen, in the Data Structure tab, choose DisplayChange and confirm the message regarding cross-client-settings.

3. In area Data structure, choose Change.

4. On the Edit Data Structure: Characteristics screen, choose Extras  Characteristics  Unlock and confirm when the dialog box appears.

5. Choose the Save button.

6. Choose the Activate button.

7. Choose the Back button.

8. Confirm pop-up regarding regeneration of operating concern.

Result

The operating concern has been regenerated.

[Former Member]

Hi,

Please check this online documents perhaps they may help.

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/COPA/COPA.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/COPA/COPA_ALE_064.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/COPA/WFT200_000.pdf

Hope this helps.

Cheers,

Gimmo