Specific scenario in PROFITABILITY ANALYSIS

Can someone tell me his/her experience about a specific scenario in Profitability Analysis where he/she faced a problem and did something special in configuration/development in order to move from legacy to SAP system.
I would appreciate the help and award suitable points.
Thanks
Chandan

Hi,
Are you looking at KE30 - drilldown reports?
Rgds.

Similar Messages

Profitability Analysis for Project and Project Team

Hello Experts,
Need your ideas and expertise to the below business case, could be simple or complicated, please provide some insight.
the business case is like this. 2 specific project teams are available. there can be around 10 projects executed in a year. So in our PS we can have project team allocated to a project. workforce planning is done for the project for effective utilization, it is like 2 projects with 2 teams assigned. till now it is fine. the business calls for that 1 st team is assigned to another project only after closure of the assigned project.
Let us assume P1, P2,...P10 are the projects in a year. Assume T1, T2 are the teams available. Initially T1 is assigned to P1, T2 is assigned to P2.
Business confirms that T1 will be assigned to P3 only after completion of P1. This requirement is also straight. Assume that team T1 has executed 6 projects and team T2 has executed 4 projects.
The requirement is profitability analysis at project level i.e at P1, P2, ...P10 which is also pretty straight. Business requirement is also to have profitability analysis against each team i.e for T1 and T2. it is like each team has a project lead and team assigned under him. based on the expenses and revenue booked against the team, there will be performance evaluation of the team.( assume that P1, P3, P5, P6, P8,P9 are the projects executed by team T1, we need to have revenue and expenses of the said projects to be mapped to team T1 as well), so we have profitability analysis at team level.
Experts, require your advice on how to map the requirement. Is there any possibility to map projects to team rather assigning team to a project. please advice. provide some insight on how do we map the scenario.
Regards,
Murthy

Hello Murthy,
In SAP you carry out Month end closing activities. In order to carry out this activity, you post all period based data on the project. Subsequently data relevant for Profitability analysis can be determined for the given period and then this data can be settled to COPA.
This data can be evaluated in the project information system or in Profitability analysis.
You can check report KE30 for Profitability Analysis.
Refer SAP help for more details
http://help.sap.com/saphelp_erp2004/helpdata/en/7a/4c3aad4a0111d1894c0000e829fbbd/content.htm
Regards
Tushar

Exchange Rate in Profitability Analysis Document

How is the exchange rate populated in profitability analysis document?
We have couple of scenarios:
Scenario 1: Credit memo request created without any reference and credit memo is created successfully. Exchange rate populated in the profitability analysis document is the exchange rate which applicable to current date.
Scenario 2: Credit memo request created with reference to customer invoice document and credit memo is created successfully. Exchange rate populated in the profitability analysis document is the exchange rate which applicable to the past date. We dont know how the system picked the exchange rate which does not applicable to the current date.
Any poiniters to this issue?

HI,
try SAPNET note 429517.
Best regards, Christian

CAPTURING OF COST IN PROFITABILITY ANALYSIS FOR BY PRODUCT

Dear Team,
We had a requirement when standard material cost estimate is executed we can get the standard price for main material as well as by product for which values are flowing to COPA (T.code KE30).
The scenario works fine for Main Product, since the actuals as well as Costs are flowing to COPA. Where as only actuals are posting to byproduct as there are no separate cost estimate for Byproduct.
So only acutals are caputured to Profitability analysis.
At present we are manually changing the price of the byproduct material through MR21 which is constant through out the period.
Our requirement:- Since Byproduct doesnt have any separate BOM and Routing, Is it possible to capture this byproducts price to COPA.
or
capturing of COGS for this byproducts price is also ok.
Please anybody can guide me.
Thanks & regards,
Sandeep

Dear Santosh,
Thanks for your early reply.
It might work, Please elaborate.
Request you to send any document if you have any, since i am new in CO.
it was availbale in my user profile.
Thanks & regards,
Sandeep

Characteristic Derivation in Profitability Analysis

Dear Experts,
I am finding it bit difficult to understand the concept fully when it comes to the Characteristic Derivation in Profitability Analysis.
I had gone through the various SAP explanations of MOVE, LOOK UP, ENHANCEMENT, DERIVATION RULEu2026. And now I am having rough understanding of all of it. But I am finding it difficult to understand on how these various steps or rule impact the COPA output. In other words if someone can explain the usage of all the MOVE, LOOK UP, ENHANCEMENT, DERIVATION RULE steps with an example?
Thanks in advance
Paul

Hello Paul,
Its purely clients decision/requirements which determine whether derivation is required or not. But in all COPA implemenation you need at least couple of derivations.
I will explain a simple scenario for Table Look up. Suppose you are settling production orders linked to a sales order ( Make to order scenario).
When the production order settles variances to COPA, system will not transfer Customer ( sold to party) characteristics.
But you can tweak the system through a small derivation rule to bring the customer from sales order and pass it to COPA when production order is settled.
For table look up first you have to identify the table, here our reference is sales order (VBAP-VBELN) and the required field is sold to party (VBAP-KUNNR), both are in VBAK
In the source field for table look up
VBAP- VBELN = CO-PA- KAUFN ( means if sales order number from VBAP table is same as the COPA sales order number)
VBAK-KUNNR= CO-PA-KDNR ( then pull the customer number associated with that sales order and populate the COPA customer field)
Please carefully go through SAP help for derivation, it is clearly explained with simple examples
http://help.sap.com/saphelp_46c/helpdata/en/7a/4c37ef4a0111d1894c0000e829fbbd/frameset.htm
thanks
SAP FREAK

Customizing Monitor in Profitability Analysis

Hello SAP-team!
What functions are provided by the Customizing Monitor in Profitability Analysis?
ps: thanks to SAP-community!
Eugene

Hi,
Customizing monitor in Profitability analysis as follows..
General topics:
35288 Technical Documentation CO-PA
69384 Account-based Profitability Analysis
199467 New act assignment table as of Release 4.5
2. Master data:
a) Characteristics and value fields:
13377 Naming conflicts in characteristics and value fields
21207 Deleting a charctrstc/value field from an op.concern
40336 Maintaining foreign keys for characteristics
76493 Changing texts of characteristics or value fields
b) Characteristics derivation and submission of characteristics values
32719 Customer hierarchy in CO-PA
33968 SD/CO-PA: Characteristics from sales document tables
36557 SD/CO-PA: Transfer partner functions to CO-PA
62690 Product hierarchy in CO-PA
93652 Info: Variant configuration in CO-PA
134889 Info on derv. of char:Why not all flds avail.?
148609 Char.deriv.:deriv. rule vals miss.aft.upgrade&trnsp.
172740 Techn.docum.charct. derivtn as of Release 4.0
c) Valuation
40408 Valuation for record types 'B' and 'C'
62536 Valuation using conditions in Profitability Analysis
67240 Info: Valuation with material cost estimate
111232 INFO: Valuation for materials valuated separately
144337 INFO rounding differences: Valuation with costing
142628 Behaviour of user exit in periodic valuation
3. Actual data transfer:
20254 Values from SD are not transferred to CO-PA
37114 Incorrect setup/reversal of provisions
33178 +/- sign logic in CO-PA (SD/FI interface)
52849 Transfer of conditions with +/- signs
39635 Profitability segment by substitution exits
64768 FI/CO-PA: Problems with exchange rate differences
87704 Cost-of-goods-sold Reconciliation: FI to Co-PA
83702 Acct assignmt logic sales order proc. - REM
111309 Transfer of quantities into CO-PA
185826 Enhancement COPA0005
a) Correction of data inconsistencies
69370 Clearing data inconsistencies in CO-PA
70718 Correctn of data inconsistency for order recpt
140457 Correcting data inconsstncs in incoming orders
126937 Correction of billing data inconsistency
93051 Restructure of the segment level from line items
4. Planning:
67191 Useful tips on the CO Planning Processor
72110 KE11: Long runtimes/timeout
77476 Information: Top-down planning
124598 CO-PA Planning: FAQs
5. Information system:
21773 Performance in reporting (summarization data)
83204 Usage strategy for summarization levels
136216 Fast rollup for summ. levels for costing-based CO-PA
6. Tools:
134430 Euro conversion and CO-PA
19015 Termination during external data transfer
19410 Characteristic validation during external data transfer
44658 Error with batch input for KE21
40994 Transport Profitability Analysis (CO-PA) to 3.0
52636 CO-PA Customizing transport
128862 Transport Customizing CO-PA in 4.0A/B
131664 Transport of operating concern structures 4.0
144015 Client copy and CO-PA/EC-EIS
65999 Information: Supported ALE scenarios in CO-PA
94458 CO-PA Realignments: documentation
113050 Segment table repair after realignments
127334 Missing archiving of profitability segments
199959 Change assignmt for operating concern
67839 Generating parts of an operating concern environment
69829 Delete operating concern in Release 3.0
106314 Delete operating concern in Release 3.1
562043 - Transfer actual costs to Profitability Analysis
544241 - INFO:Customizing Monitor new fnc 'Report Overview'.
429517 - INFO: Currency translation Billing document -> CO-PA
428563 - Material cost estimate valuatn: Translaton for posting date
400237 - CO-PA INFORMATION: Line item in company code currency
199959 - Information: change assignmt for operating concern
199467 - Info: New act assignment table as of Release 4.5
185826 - Information: Enhancement COPA0005
172740 - Info.:Techn.docum.charct.derivtn as of Release 4.0
148609 - Char.deriv.:deriv.rule vals miss.aft.upgrade&trnsp.
144337 - INFO rounding differences: valuation with costing
144015 - CC-INFO: client copy and CO-PA/EC-EIS
142628 - Behaviour of user exit in periodic valuation
140457 - Info:Correcting data inconsstncs in incoming orders
136216 - Fast rollup for summ.levels for costing-based CO-PA
134889 - CO-PA Info on derv.of char:Why not all flds avail.?
134430 - Information: Euro conversion and CO-PA
131664 - INFO: Transport of operating concern structures 4.0
128862 - INFO: Transport Customizing CO-PA in 4.0A/B
127334 - Missing archiving of profitability segments
126937 - INFO: Correction of billing data inconsistency
124598 - Info: CO-PA planning: frequently asked questions
113050 - Segment table repair after realignments
111309 - INFO: Transfer of quantities into CO-PA
111232 - INFO: Valuation for materials valuated separately
106314 - Delete operating concern in Release 3.1
94458 - CO-PA Realignments: documentation
93652 - Info: Variant configuration in CO-PA
93051 - Restructuring the segment level from line items
83702 - INFO: Acct assignmt logic sales order proc. - REM
83204 - Usage strategy for summarization levels
77476 - Information: top-down planning
76493 - Changing texts of characteristics or value fields
75334 - INFO:Downloading CO-PA correctn package fm SAPSERV
72110 - KE11: Long processing times / timeout
70718 - INFO:Correctn of data inconsistency for order recpt
69829 - Delete operating concern in Release 3.0
69384 - Information: Account-based Profitability Analysis
69370 - INFO: Clearing data inconsistencies in CO-PA
67839 - Generating parts of an operating concern environment
67240 - Info: valuation with material cost estimate
67191 - Info: Useful tips on the CO Planning Processor
65999 - Information: Supported ALE scenarios in CO-PA
64768 - FI/CO-PA: Problems with exchange rate differences
62690 - Info: product hierarchy in CO-PA
62536 - Info: Conditions in Profitability Analysis
52849 - INFO: Transfer of conditions with +/- signs
52636 - INFO: CO-PA Customizing transport
44658 - Error with batch input for KE21
40994 - INFO:Transprt Profitability Analysis (CO-PA) to 3.0
40408 - Info: Valuation for record types "B" and "C"
40336 - Info: maintaining foreign keys for characteristics
39635 - Info: finding the profitability segment using a substitution
37114 - Incorrect setup/reversal of provisions
36557 - Info SD/CO-PA:transfer partner functions to CO-PA
35288 - Profitability Analysis: Technical Documentation
33968 - SD/CO-PA: Characteristics from sales doc tables
33178 - INFO: +/- sign logic in CO-PA (SD/FI interface)
32719 - INFO: Customer hierarchy in CO-PA
21773 - Performance in Reporting (Summarization data)
21207 - Deleting a charctrstc/value field from an op.concern
20254 - INFO: Values from SD not transferred to CO-PA
19410 - INFO: Char.validity check f.external data transfer
19015 - Termination during external data transfer
13377 - INFO: Naming conflicts in charactrst. & value flds.
Thanks
Prasada

Distributed Profitability Analysis from HCM system

We have a requirement to provide a distributed profitability analysis (PA) solution (account based) from our SAP HCM system (ECC6) to our backend SAP Finance system (ECC6).
Does anybody know whether this can be done?
I have found general information relating to distributed PA scenarios but none explicitly mention HCM as the source system.
For the scenarios I have found, it mentions using message type CODCMT as part of an ALE solution. Will this apply to HCM or have we got to look at alternatives such as (for example) bespoking the std IDoc solution for the posting of payroll results to include the PA data.
Any help would be greatly appreciated. Points will be allocated.
Regards
Ian

Hi
Posting a COPA document while delivery of goods (VL02N) is not a standard way of COPA value flows.
You can only transfer your billing values only at the time of VF02 and not at VL02N and even it is not logical
Because when you do post goods issue, at that point of time you are not accounting for any revenue. So it is not proper to flow the values into COPA and generate a document at goods issue
One more thing is that accounting entries are automatically generated during VL02N and you cant directly post on COPA using Direct Acct Assgn from FI/MM. It only works when you directly do an FI posting
Hope it gives u an idea
Regards
Ram

50 Fixed CO-PA Profitability Analysis Elements

We are in the blueprint stage of a new SAP implementation using the Life Sciences express solution. Our consultants advised us that there are 50 SAP fixed characteristics in CO-PA for Profitablity Analysis and we have the ability to add up to 50 non-fixed characteristics. The list of the 50 fixed characteristics that our consulting team provided to us appeared very strange. Many of them appear to related to the airline industry. For example:
KMATYP - Aircraft type
KMDEST - Desitnation
KMFLTN - Flight number
KMFLTY - Flight type
KMIATA - IATA season
KMOPDY - Day of operation
KMORIG - Departure location
KMLEGS - Route segment
After questioning the provided list, we have been assured that we have been provided is the correct list of 50 fixed characteristics for all SAP implementations. We are looking for validation that these value are indeed part of the correct list. If not, we would greatly appreciate receiving the correct full list.
Thank you,
Carrie

Hi Carrie,
I vaguely remember that CO-PA (Profitability Analysis) module was initially developed/used for Airline industry to analyze the contribution margins. I'm not 100% sure on this, think i read it somewhere. SAP has provided these characteristics and derivation rules (logic to derive the characteristic for a transaction) by default. In my experience, i have always seen clients using at least 10-20 custom fields in CO-PA, since these are client specific we need to create additional derivation rules (either table lookup/Move/Derivation rules/Enhancements). Fields from Material master and customer master tables are commonly used for analysis in CO-PA.
Best Regards,
Venkata Ganesh Perumalla

Profitability Analysis document

Dear All,
At the time reversal of Sales delivery system is not generating Profitability analyses document.
Scenario is like this
At the time of delivery to customer the standard price is 10, but at the time of reversing the delivery the Standard price is 12.the difference 2 system is posting to variance G/L Account.
For variance cost element we activated the PA Segment posting in OKB9.
but for variances system is creating only controlling document, it is not creating Profitability analysis document.
pls help me, issue is urgent.
Advance
Message was edited by: Nalluri Surendra

which CO document does the system creates : CCA document ?
on which cost centre ? PCA document ?
What is the CE category of the CE used for posting the variance ?

Implemented CO-PA (Profitability Analysis)

I would like to know if anyone has implemented Controlling - Profitability Analysis for a IS-Uitilities customer? I have some specific questions on this topic and would appreciate if someone could answer them.
Raj

Hi Ivor
Re: Implementation: ISU Biling COPA Integration
Excuse me Ivor Martin for jumping on the bandwagon, I am in the process of implementing ISU Biling COPA Integration. I do have the cookbook but it does not clarify certain things i would like you to help me with as follows:
1.Operating concern
I am busy widentifying characteristics to use from Billing document. My question is should I set up Opconcern as in pure COPA,i.e working from reporting structure & subsequent derivation of e.g profit center?
I would like to be certain about this. Please advice me also with any other information you dem relevant.
2.I would also like to know about the pros and cons of transferring updates if that is ok with you.
Thanks in advance.

Report Subscription fails, shows 'success', specific scenario

I have a report that will run successfully except for one very specific scenario. Any help or suggestions tracking down this issue would be helpful.
The report is named ProjectsWeeklyReport.rdl and takes a single parameter of a specific user's login account "DOMAIN\username"
The report runs successfully in the web regardless of the parameter (works for all users, including john.doe)
The report runs successfully in Report Builder regardless of the parameter (works for all users, including john.doe)
The report runs successfully as a subscription with the report included as a
MHTML file and a statically-selected parameter EXCEPT for john.doe. The same report works for all other users selected as the parameter
The report runs successfully as a subscription with the report included as a
Excel file (instead of an MHTML file) regardless of the statically-selected parameter (works for all users, including john.doe)
To summarize, in order for the report subscription email to fail, these conditions have to be met (otherwise the result is success):
- Report must have the parameter "DOMAIN\john.doe"
- Report must NOT be MHTML format in the email
I can see the subscribed report worked according to the ReportExecutionLog in MS SQL. Is there any reason why the MHTML version of the report subscription would fail to email? Any reason why it would fail as MHTML but be fine in other formats
(PDF & Excel both tested success)
For example, this one was never emailed:
InstanceName: APPSERVER\@Sharepoint
ItemPath: /{73419db6-f0e2-4096-a710-c630e8a26295}/Reports/ProjectsWeeklyReport.rdl
Username: DOMAIN\p_sps_app_pool_porta   (App pool account)
Execution ID: rkciwraxt5cmoi55niw3wx45
RequestType: Subscription
Format: MHTML
Parameters:   Engineer=DOMAIN%5Cjohn.doe
ItemAction: Render
TimeStart: 7/22/2014 4:27:05 PM
TimeEnd:   7/22/2014 4:27:12 PM
TimeDataRetrieval: 1200
TimeProcessing: 75
TimeRendering:   5667
Source: Live
Status: rsSuccess
ByteCount: 277050
RowCount: 431
NOTES:
There are no logs in Exchange message tracking of this email ever reaching our servers
The Manage Subscriptions page shows the report emailed successfully "Email sent to.." with the correct timestamp of 7/22 at 4:27 PM
And compare to this one that was successfully emailed:
InstanceName: APPSERVER\@Sharepoint
ItemPath: /{73419db6-f0e2-4096-a710-c630e8a26295}/Reports/ProjectsWeeklyReport.rdl
Username: DOMAIN\p_sps_app_pool_porta   (App pool account)
Execution ID: 1yycmuiwc4hzymzuyj1zbc45
RequestType: Subscription
Format: EXCELOPENXML
Parameters:   Engineer=DOMAIN%5Cjohn.doe
ItemAction: Render
TimeStart: 7/22/2014 4:21:10 PM
TimeEnd:   7/22/2014 4:21:18 PM
TimeDataRetrieval: 1574
TimeProcessing: 73
TimeRendering:   5912
Source: Live
Status: rsSuccess
ByteCount: 34180
RowCount: 431
Suggestions of where to look for errors? Troubleshooting ideas? Anything would be helpful! Thanks in advance.

Hi ElizabethCEE2010,
We can try to check the detail information about the error in the log file. The SQL Reporting Services log files are found on the reporting services point server, in the folder %programfiles%\Microsoft SQL Server\<SQL Server Instance>\Reporting Services\LogFiles.
Besides, to monitor and troubleshoot Subscriptions in Reporting Services, we can refer to the following two good blogs post by Dean Kalanquin:
Monitoring and Troubleshooting Subscriptions
Troubleshooting Subscriptions: Part II, Using the Reporting Services Trace Log File
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Order value fields by field label in the profitability analysis document

Hello,
I am displaying a profitability analysis document and I want to order the value fields by their technical name (VV001, VV002, VV003...) instead of in alphabetical order (the system orders them by the field label).
Is it possible?
Thank you very much
Bea

Hello,
Check in KE4M whether sd condition type FKLMG is mapped corresponding value field in COPA.As you are getting the value for other company codes, this setting should be there.
You can also try checking simulation of billing document transfer through KE4ST. Check the details analysis
thanks
Hari

Field catalog in Profitability Analysis

Hi,
In profitability analysis, if we want to use a particular characteristic or value field, then they should be maintained in field catalog.
Could anyone please explain me where we will define this field catalog.
Thanks
Chandra

You need to create the Characteristics and/or Value Fields using transaciton KEA5 / KEA6
Once this is done, assign these to the Operating Concern using transaction KEA0
In this transaction, enter the Operating Concern you need to modify, and then enter the Data Structure in the Data Structure tab. Assign the Characteristics / VFs in this screen (click on the respective tab to access the assignment). Once done, remember to generate the Operating Concern.
If you exit the maintenance screen on saving, the system normally prompts you to Generate the Op Co. Once this is generated, you can use these in your config./ analysis.
Cheers.

Project wise profitability analysis

Hi
I have to create MIS for project wise profitability analysis . In sales order we used additional tab as project and we assigned projects to each and every sales order
Now they want one Report "Project wise profitability analysis" . So i have do that through Infoset (Lis)
Please tell me what are the charecteristics & what are the keyfields to select to get the cost
(i want material number - Planned cost - Actual cost - variance)
Rgds
pradeep

Hi,
This is standard report to get acutal cost and planned cost and variance.
S_ALR_87013532 - Plan/Actual/Variance
S_ALR_87013566 - Actual Contribution Margin
S_ALR_87013568 - Project Results
Regards,
Chandra

Profitability Analysis not generated in Contract billing Document

I have created the Billing document against the contract order but the Profitability Analysis is not getting generated. But any sale order related billing document is created; system automatically creates the Profitability Analysis.
Can you tell me where the problem is or have I missed any steps?
Regards,
Devendra

1) For a service material (DIEN), We are creating an Sales Order (VA01) and doing a order based billing (VF01). In the Sales Order we are giving the plant (no shipping point and storage location as it is a DIEN material).
Once we do the billing we are able to see the Profitability Analysis document.
2) Now we are using the same material we are creating a Contract (VA41) for a period of one year and doing a monthly billing. In this case we are using VF04 for doing the bills that are due.
We are getting two results in this:
a) If we give a Plant in the contract, the Profitability Analysis document is not getting generated at the time of billing.
b) If we do not give any plant, the Profitability Analysis document is getting generated at the time of billing.
Please note that we are using the same material, same pricing procedure in both the above cases 1) and 2). Only difference is that the source documents are different i.e., one is Sales Order and the other one is Contract.
In our copa valuation we have assigned the conditions to value field, no derivation rule assigned.
Regards
Devendra
Edited by: Devendrap on Apr 14, 2009 10:38 AM

Specific scenario in PROFITABILITY ANALYSIS

Similar Messages

Maybe you are looking for