05-15-2012 2:41 PM
Hello All,
The requirement is to display some fields in CN41N Report in Object Currency. Currenlty it is diplayed in CO AREA currency.
SAP has given note no : 1628596 for the same.
However what is confusing in the note is this Quote "After you perform the manual advance steps, implement the correction instructions.". Are we suppose to create the structures as given in the notes or the implementation of the Note will take care of the creation of structures.
This is the note quote.
Reason
In the structure overview, the project structure overview, the progress analysis, or the project planning board, you cannot display costs and finance data in the object currency.
This note delivers the implementations to use the function.
Other terms
Customer connection, Product Lifecycle Management, Project System
Object currency, CN41, CNS41, CN41N, CNE5, CNSE5, CJ2B, CJ2C, interface note, CustConn
Reason and Prerequisites
A function is missing.
You must have implemented Notes 1626081, 1628475, and 1628595.
Solution
Improvement
You can also display accounting data in the object currency on the project planning board, as well as in the structure reports.
Customer uses
One report is now sufficient to analyze accounting data in the controlling area and the object currency in parallel.
Delivery
After you perform the manual advance steps, implement the correction instructions.
We recommend that you import the relevant Support Package because using transaction SNOTE to implement the note requires many manual steps.
Due to the complexity of the changes (creation of structures, of the BAdI, etc), they should only be implemented by experienced developers.
05-15-2012 2:44 PM
05-15-2012 2:54 PM
Yes.there are stucutes..data elements and in the end a BADI too. SAP has given a long list of things to do..I have pasted this below..
------------------------------------------------------------------------
|Manual Pre-Implement. |
------------------------------------------------------------------------
|VALID FOR |
|Software Component SAP_APPL SAP Application |
| Release 470 Until SAPKH47036 |
| Release 500 Until SAPKH50025 |
| Release 600 Until SAPKH60020 |
| Release 602 Until SAPKH60210 |
| Release 603 Until SAPKH60309 |
| Release 604 Until SAPKH60410 |
| Release 605 Until SAPKH60506 |
| Release 606 Until SAPKH60601 |
------------------------------------------------------------------------
(The components are specified in uppercase followed by the short description. Before you perform point 2, save, check, and activate these.)
AUFERLPLANOC (Current Order Revenue Plan In Object Currency)
AUFERLPLN2OC (Order Revenue Plan (Version 2) In Object Currency).
AUFKSTPLANOC (Current Order Cost Plan In Object Currency)
AUFKSTPLN2OC (Order Cost Plan (Version 2) In Object Currency)
AUFTRANFOC (Residual Order Plan In Object Currency)
BUDGETOC (Budget Of A Task (Request Variant Replaces OC))
DEBFINPLNOC (Current Customer Financial Budget In Object Currency)
DZHLNGOC (Customer Total Payments (Down Payments And Payments) OC)
FESTPROBLOC (Fixed Price Commitment In Object Currency)
FREIGABEOC (Release In Object Currency)
ISTERLOESEOC (Actual Revenues In Object Currency)
ISTKOSTENOC (Actual Costs In Object Currency)
KREDFINPLNOC (Current Vendor Financial Budget In Object Currency)
KSTOBLGESOC (Total Cost Commitment In Object Currency)
KZHLNGOC (Vendor Total Payments (Down Payments And Payments) OC)
PROERLPLANOC (Current Project Revenue Plan In Object Currency)
PROERLPLN2OC (Project Revenue Plan (Version 2) In Object Currency)
PROKSTPLANOC (Current Project Cost Plan In Object Currency)
PROKSTPLN2OC (Project Cost Plan (Version 2) In Object Currency)
(Here and in the following sections, the components are specified in uppercase followed by the component type. Before you perform the next numbered point, save, check, and activate these.)
Component Component type
PROKSTPLAN_OC PROKSTPLANOC
PROKSTPLN2_OC PROKSTPLN2OC
AUFKSTPLAN_OC AUFKSTPLANOC
AUFKSTPLN2_OC AUFKSTPLN2OC
PROERLPLAN_OC PROERLPLANOC
PROERLPLN2_OC PROERLPLN2OC
AUFERLPLAN_OC AUFERLPLANOC
AUFERLPLN2_OC AUFERLPLN2OC
KREDFINPLN_OC KREDFINPLNOC
DEBFINPLN_OC DEBFINPLNOC
BUDGET_OC BUDGETOC
FREIGABE_OC FREIGABEOC
AUFTRANF_OC AUFTRANFOC
FESTPROBL_OC FESTPROBLOC
KSTOBLGES_OC KSTOBLGESOC
ISTKOSTEN_OC ISTKOSTENOC
ISTERLOESE_OC ISTERLOESEOC
KZHLNG_OC KZHLNGOC
DZHLNG_OC DZHLNGOC
On the "Currency/quantity fields" tab, enter the reference table RPSCO_LIS and the reference field OWAERS for all fields.
Component Component type
EV_PLAN_ORG1_OC EVPLANORG1
EV_ACT_ORG1_OC EVACTORG1
EV_ACT_CORR1_OC EVACTCORR1
On the "Currency/quantity fields" tab, enter the reference table RPSCO_LIS and the reference field OWAERS for all fields.
Component Component type
.INCLUDE RCJ_EVVALUE_OC
EV_COST_VAR_ORG_OC EWALVARORG
EV_SCHED_VAR_ORG_OC EVSCHVARORG
EV_SCHED_VAR_CORR_OC EWALVARCORR
EV_COST_VAR_CORR_OC EVSCHVARCORR
On the "Currency/quantity fields" tab, enter the reference table RPSCO_LIS and the reference field OWAERS for all fields.
Component Component type
.INCLUDE RCJ_RPSCO_LIS_OC
.INCLUDE RCJ_EV_OC
Component Component type
.INCLUDE RCJ_RPSCO_LIS_OC
Component Component type
.INCLUDE RCJ_EV_OC
select "Structure Overview" (Field string name STRUCR, Include name RCNSTRUCR)
Execute the program; the system should highlight the new fields in color. Add the new fields to the following groups ("Grp" column):
PROKSTPLAN_OC COST
PROKSTPLN2_OC COST
AUFKSTPLAN_OC COST
AUFKSTPLN2_OC COST
PROERLPLAN_OC REV
PROERLPLN2_OC REV
AUFERLPLAN_OC REV
AUFERLPLN2_OC REV
KREDFINPLN_OC FIN
DEBFINPLN_OC FIN
FESTPROBL_OC OBLG
KSTOBLGES_OC OBLG
ISTKOSTEN_OC COST
ISTERLOESE_OC REV
KZHLNG_OC FIN
DZHLNG_OC FIN
EV_PLAN_ORG1_OC EVVL
EV_ACT_ORG1_OC EVVL
EV_ACT_CORR1_OC EVVL
Start the generation of the includes (Shift + F4).
"Period Drilldown" (Field string name CNZVR, Include name RCNCNZVR).
Name Text
ACL Order Revenue Plan OC 000
ACM OrdRevPlanOC000
ACR Order Revenue Plan OC 000
ACS OrRevPlOC000
AOL Order Cost Plan OC 000
AOM OrdCostPlanOC000
AOR Order Cost Plan OC 000
AOS OrCstPlOC000
PCL Project Revenue Plan OC 000
PCM ProjRevPlan OC 000
PCR Project Revenue Plan OC 000
PCS PrRevPlOC000
POL Project Cost Plan OC 000
POM ProjCostPlan OC 000
POR Project Cost Plan OC 000
POZ PrCstPlOC000
Sym Text
POC Costs (OC)
To ensure that the fields for the object currency are visible, you must set the field OBJ_CUR_FLG of the structure SWITCH_VALUES to 'X' in the implementation of the BAdI PS_FUNCTION_SWITCH (enhancement spot ES_PS_BADI).
05-15-2012 3:13 PM
then you have to do them.
It sounds like importing the support package would be the better option.
Rob
05-15-2012 3:48 PM
Well Rob,
Currently we are on support pack 19..and the required functionality is in support pack 21.
So you mean If I ask the basis team to import the pack 21..all of this creations of different objects will be taken care of..
Thank you for the inputs,
Rajesh.
05-15-2012 3:55 PM
I think so; however, you could raise an OSS message to confirm this.
Importing support packs isn't a risk free strategy either. You will have to run transaction SPAU after the support pack is implemented to see if you have further work to do. And you will have to test.
Rob