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

Similar Messages

ERec - Data Transfer from eRec system to HCM System

Hello All,
Currently am able to do the data transfer from eRec system to HCM system but am finding some inconsistencies here.
In our scenario we are on ehp4 and no XI in place, We are doing via RFC only. Stanalone eRec system
So here are few queries and if someone can address these would be really great and appreciate the help
1) While i do the data transfer activity, when i select activity and don not give the Hiring Date in the Org Assignment Column it throws an error "When transferring data using XI, the hiring date must be specified". But am not using XI, then why should it give this error?
Also is it not possible that i do the data transfer without any hiring date?
Also there are two options Planned and Completed. When i do the data transfer i keep it in planned status and do it it automatically saying that Complete
Is this correct
2)Now when i do the data transfer it is getting appeared in HR system when i execute the PA48 tcode.
Here my queries are
a) Suppose i do a data transfer for a candidate Abc on 10.10.2010 and run the PA48 tcode it appears in the list as hire date 10.10.2010
Now as a recruiter am again doing the data transfer for the same candidate Abc for 11.10.2010 and againg when i see PA48 there is again another entry for the Abc candidate for hiring
Is this correct process. How should these duplicate entries to be avoided. Pls help me
3) Also i case if I want additions infotypes to be transferred in PA48 how should we go for this development
Pls help me in these queries

Hi ,
Check the following OSS notes.
1. 1006679
2. 997181 ( Read the attachment in the OSS note ) gives the detailed information regarding EREC and HR)
Let me know if you need more info.
Regards,
Ram

Problem with data distribution from HCM to e-Recruiting

Hello masters:
I have a problem when I try to distribute data from HCM to e-Recruiting. I´m getting code 51 just for the PA infotypes segments (E1P0000, E1P0001, etc.). The error message tha I am receiving is:
"Error in subroutine read_namtb for structure of infotype".
My e-Recruiting system is SAP EHP 1 for SAP NetWeaver 7.0, so I'm using Business Partners for storing data from PA infotypes.
I'm using message type HRMD_ABA, basic type HRMD_ABA05.
I think it could be the implementation HRRCF00_INBD_NEWMOD from the badi HRALE00INBOUND_IDOC, because it usually get inactive even though I go to activate it.
Does anybody knows what can I do?
Thanks in advance!
Edited by: Rodrigo Arenas Arriola on Jun 25, 2009 2:45 AM

Hello Rodrigo,
Ifyou are using EhP1 for NW 7.0 you should have E-Recruiting 600 EhP 4 on your system.
I never encountered this special error message so far, so i have to "guess". The message indicates that the system had trouble reading some infotype information.
The ALE distribution for EhP4 is storing the PA data in new infotypes 558*. The error you get points to a missing BAdI activation. If the BAdIs are not activated correctly, ALE will try to write the information from the PA infotypes 1 to 1 into the E-Recruiting system. But E-Recruiting does not know the PA infotypes which should exactly lead to the error you get.
Could you check the following settings:
BAdI                     Implementation
HRSYNC_P                 CONV_HR_DATA_TO_EREC -> active
HRALE00INBOUND_IDOC      HRRCF00_INBD_NEWMOD -> active
HRALE00SPLIT_INBOUND     HR_INB_PROCESS_IDOC -> inactive
HRALE00INBOUND_IDOC      HRRCF00_DELETE_SPREL -> inactive
Kind Regards
Roman

Transfer IT0022 and IT0023 from HCM to E-recruiting via ALE

Hello,
In our HCM system we created a distribution model with HRMD_A type message and. Also we create several filter group with relevant data (infotype, object type...).
We need to transfer the IT0022 and IT0023 from HCM to e-recruiting, so we included these Infotypes into a filter group in the distribution model. We execute de t.code PFAL in the HCM system to distribute the data through ALE and the system include the data (IT0022, IT0023 and others) into the Idoc, but an error occur in the receptor system.
When we check the status message for the IDoc through t.code WE02 (in the receptor system), the status record is 51 - Infotype 0023 will be ignored (also Infotype 0022) and the Application document is not posted.
We need to transfer these two aditionals infotypes. Is there some missing configuration?
Thanks and kind regards

I assume, that you use e-recruiting as standalone system.
In e-erecruiting there are no PA infotypes. The inbound processing cannot work with those two infotypes. Therefore the inbound processing crashes.
Also there is no mapping possible with work experience and education of PA to e-recruiting in standard.
The only infotypes which are supported by standard are:
0001, 0002, 0006, 0105 + 1000 and 1001
If you want distribute further data, you will have to implement inbound processing and mapping yourself.
Also the target message type hrmd_aba05 in e-erecruiting the hrmd_a is mapped to does not contain those infotypes.
So you will need a specialist extending the idocs and extending the inbound processing BADI.
But before you do that, think if you can really map HR and e-recruiting infotypes, because fields and values do not match in generall. So this might be impossible!!!!
Regards
Sebastian
Edited by: Sebastian Menger on Apr 29, 2010 12:29 PM

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

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.

This is regarding interface from legacy system to SAP

Hi All,
We have trasferred the one file from legacy system to SAP, and it was created a session in SM35, it contains 1000 errors.
we don't want correct those errors and these entries should be delated, could you please let me know are these errors can I see in any error table in SAP, is this facility is availbe in SAP or not?
becuase it isl very difficult to go and delete the entries one by one in sm35
Regards
Nama

Hi,
1) No updates will have been done for the items with errors.
2) Mark the Batch, then press F2 to call up the analysis. You can check here for the cause.
3) If you are not going to correct the items or the cause so as to post them, just delete the batch.
Kind regards

How to upload the data from legacy system database to SAP data base

Hi.
We are doing analysis of Legacy system and which needs to be converted to SAP system i.e. SAP implementation.
I just want to know , how we migrate the existing whole data( from legacy system) into SAP system.
and which method is the best method to use data migration from legacy to SAP system if data legacy data amount is huge.
Please suggest me.
Thanks.

Hi
We can either use the BDC or BAPI or LSMW or Direct Input techiniques for the data transfers.
The combination of both Session and Call transaction can be used to achieve this that includes the error handling also. This invloves the screen interaction.
These days, BAPIs are used to overvome some upgrade problems. For easy upgradation, we cna go for BAPIs. Here ther is no screen intercation.
LSMW mainly used for master data transfers using some standrad programs.
As per your client or company desicions we can choose any of them.
Please refer to these links for more understanding -
BDC Vs LSMW -
BDC VS LSMW
BDC Vs BAPI -
BDC VS LSMW
Thanks & Regards,
Chandralekha.

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

Data request deletion problem from remote system.

Hi experts.
Now i am facing one critical problem . The description is as following:
we design the edw level in one phsical BW machine(A) which contains only dso infoprovider. This machine(A) works as datasource to provide data to another physical BW machine(B).
The dso in A system is exported as datasource , Cubes in B system load data through this datasource .
We first do the initialization with data contained on B system and then load delta data from A system. But if we want to delete some request in system A ,the system indicate this request can not be deleted unless the initialization in system B is deleted( this will lead to all the data missing in system B).
Can anyone explain this mechanism to me , please help me suggesting some kind of methods to delete the request in system A without deleting the initialization information in system B.
Thanks in advance.
Waiting online for your kindly reply.

1. Ask your Basis to look into it.
2. try analyse your Baqckground Process in SM51.
3. Is your Deletion Job started immediately or any Delay?
4. If That cube or ODS has only this request which you are deleting, go with Context Menu Cube or ODS (by right click) --> Delete Contents.
Delete Contents will improve performence compare to Request Deletion..
If you have request more than this, you should not go for this.
Nagesh Ganisetti.
Assign points if it helps.

Error while exporting data from HCM to VDS

Hi,
When i am trying to export data from the SAP HCM system using the RPLDAP_EXTRACT, the export fails and the log shows that the LDAP_CREATE failed. In the VDS log,
com.sap.idm.vds.oper.main_listener Message:
Exception on add: class java.lang.Integer:null incompatible with class
java.lang.String:null
I verified the database connectivity from VDS to IDS when seems fine since the LDAP_SEARCH is working fine.
Cheers !
Zaheer

It was a bug in SP2, it is fixed in SP2 Patch 4.
Cheers !!
Zaheer

Upgrade from HCM 8.8SP1 to 9.1

We need to upgrade our PeopleSoft HCM system from 8.8 SP1 to 9.1, at the same time we need to do some technical architecture upgrade:
PeopleTools upgrade from 8.45 to 8.50 or 8.51
IBM AIX upgrade from 5.3 to 6.1
Oracle database from 9.2.0.5 to 11g
Looking for Upgrade documentation ,project plans, and the upgrades path and steps.
If possible please provide me details of the related knowledge base article ID's.
Thanks in anticipation,

Hi,
I hope this link would be helpful.
It has all the related documents, reports and templates.
https://support.oracle.com/CSP/ui/flash.html#tab=KBHome%28page=KBHome&id=%28%29%29,%28page=KBNavigator&id=%28bmDocTitle=PeopleSoft%20Enterprise%20HRMS%208.8x%20to%209.1%20Feature%20Pack%20--%20December%202010%20Upgrade%20Home%20Page&bmDocDsrc=KB&bmDocID=1268944.1&from=BOOKMARK&viewingMode=1143&bmDocType=REFERENCE%29%29
Cheers,
Prad

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.

Error in loading data into PSA from source system.

Hi Experts !!!
Good morning .
I am trying to load data from SRM source system into BI system.When I execute infopackage,the data is not loaded into PSA and status of the process immediately becomes yellow.After sometime it gets timed out and converts to RED.When I checked the error documentation I found that the iDOCS response was not received from the source system.Detailed error is as below.
System Response
There are idocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
Further Analysis
Check the TRFC log
you can access this log using the wizard OR menu path "Environment > Transact. RFC> In the source system
However,I was not able to navigate to this path.I think if I can navigate to this path,I can manually push IDOCS from source system to BI system.
Regards,
Mandar.

Hi,
Check the DataSource in RSA3, if it is working fine and able to see the data in RSA3, there is no problem in DS level, then check the Mappings and any routines in BW for that DS, if this is also fine then check the below options.
See Dumps in ST22, SM21 also.
Check RFC Connection between ECC and BW systems, i.e. RSA1-->Source System->Right Click on Source system and Check.
You must have the following profiles to BWREMOTE or ALEREMOTE users.So add it. Bcoz either of these two users will use in background to get extract the data from ECC, so add these profiels in BW.
S_BI-WHM_RFC, S_BI-WHM_SPC, S_BI-WX_RFC
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
See in SDN
Re: Loading error in the production system
IDOC getting struck at TRFC (SM58)
1.Reorg of table (ARFCSSTATE )
2.Incraesing the resources in the system (no of processes and memory ) , as this issue happens owing to this.
Source system tries to send TRFC to target and if there are no WP's available it will come to Transaction Recorded state, and form here it will not try to send this TRFC.So you have to execute this manually.
Also we can increase the timeout parameter so that it can try few more times to send before actually it comes to recorded state.
Regards,
Suman

Distributed Profitability Analysis from HCM system

Similar Messages

Maybe you are looking for