25.06.2008 Page 1 of 3

Note 834815 - Upgrade to SAP ECC 6.00 with FM

Note Language: English Version: 9 Validity: Valid from 02.10.2006

Summary

SymptomYou use FI-CA integrated with Funds Management and want to upgrade to SAPECC 6.00.

More TermsHHM, FP-FM, IS-PS-CA, ACT_<REL>, ACT_700, DT963, DFKKMOP, DFKKOP,DFKKORDERPOS, DFKKORDERPOS_S, FKKORDERPOS, DFKKMOPK, DFKKOPK

Cause and PrerequisitesWhen you upgrade to a release, the FICA_FM switch (FI-CA Core, FundsManagement) or ISU_FM switch (Utilities: Funds Management) is activated ifyou already use FI-CA integrated with Funds Management. As a result, thesystem automatically writes structures SI_FKKFMOP and SI_FKKFMOPK with theFM table fields into the document tables, which replace customer includesCI_FKKFMOP and CI_FKKFMOPK.Note 773065 recommends that you include fields STAKZ and XANZA in customerinclude CI_FKKORDERPOS. These fields are contained in table DFKKORDERPOSand structure FKKORDERPOS in SAP ECC 6.00.During an automatic upgrade, the FM table fields and, if required, theSTAKZ and XANZA fields, are duplicated and this may result in activationerrors. You can prevent these activation errors if you implement themeasures described below before the upgrade.

SolutionA) Execute the following actions BEFORE you start the upgrade:

o Use Note 932814 to implement the entries for the new SI includesSI_FKKFMOP and SI_FKKFMOPK.

o Use transaction SE11 to display table DFKKOPK. Double-click fieldSI_FKKFMOPK to create the SI include SI_FKKFMOPK. In this SIinclude, create the same fields as those in the CI includeCI_FKKFMOPK. In a case without modification, add the followingfield only:.INCLUDE IFKKFMOBJSave and activate the object (package FKKFMCHK). Ignore the warning"Field....is duplicated". Use transaction SE11 to delete the CIinclude CI_FKKFMOPK. Check the newly created include SI_FKKFMOPKand reactivate it if the status is "partially active".

o Repeat this action for the SI include SI_FKKFMOP (CI includeCI_FKKFMOP). Use transaction SE11 to display table DFKKOP.

o If the CI include CI_FKKORDERPOS contains only the fields STAKZ andXANZA, delete this CI include using transaction SE11. If the CIinclude CI_FKKORDERPOS also contains other fields, use transactionSE11 to change data type CI_FKKORDERPOS and delete the componentsSTAKZ and XANZA. Activate the CI include.

Important: This procedure does not convert tables sincethe fields are only transferred from one include toanother, and the display in the database remainsunchanged. Use transaction SE11 to execute all

25.06.2008 Page 2 of 3

Note 834815 - Upgrade to SAP ECC 6.00 with FM

activations.

B) If you do not implement the measures described in A) beforethe upgrade and you encounter activation errors as a result,follow the procedure below:

CAUTION: Only implement this part of the note if you encounter activationerrors during the upgrade in the activation phase.Log on to the shadow system. The user that you log on with must not be userDDIC. If required, you must unlock the system and create a user, if youhave not already done so for the modification adjustment (SPDD). See theupgrade guide, chapter "Sequence", subchapter "ACT_<REL>" for a descriptionof the procedure.Call transaction SE11 and select include CI_FKKFMOP as a data type. Deletethe include. Also delete include CI_FKKFMOPK.If required, delete include CI_FKKORDERPOS if it contains only fields STAKZand XANZA, or delete components STAKZ and XANZA from the include if itcontains other fields.You can then continue with the upgrade as described in the guide. Thefollowing activation errors remain and you can ignore these:

1EEDO519X"Table" "CI_FKKFMOP" could not be activated

1EEDO519X"Table" "CI_FKKFMOP" could not be activatedand, if applicable,

1EEDO519X"Table" "CI_FKKFMOP" could not be activated

Important: Further activation errors can generally be attributed to anothercause and must not be ignored.

If you delete the CI include, this results in several inconsistent objectsthat produce errors in the XPRAS_UPG phase. If you encounter errors in theXPRAS_UPG phase, proceed as follows:

o Delete the existing runtime objects for both CI includes(CI_FKKFMOP, CI_FKKFMOPK and, if required, CI_FKKORDERPOS) usingthe DD_NAMETAB_DELETE function module(SE37: Choose the path Function Module Menu -> Test -> Single Test)

o Generate runtime objects for the following objects using theDD_TABL_ACTM function module (input parameter: Mode = 12, TABNAME =object to be generated).For details see Note 211492: Inconsistency between ABAP Dictionary<-> database

DFKKMOPDFKKOPDFKKORDERPOSDFKKORDERPOS_SDFKKMOPKDFKKOPKBAPI_TE_DFKKORDERPOS

After the upgrade, use transaction SE38 to start theFMGL_CHANGE_APPL_IN_LEDGER report, as described in Note 840783.

25.06.2008 Page 3 of 3

Note 834815 - Upgrade to SAP ECC 6.00 with FM

Header Data

Release Status: Released for CustomerReleased on: 03.05.2007 15:17:08Priority: Recommendations/additional infoCategory: Upgrade information

Main Component XX-PROJ-FI-CA Contract AccountingAdditional Components:

IS-T-CA Contract Accounting

IS-U-CA Contract Accounts Receivable and Payable

IS-PS-CA Public Sector Contract Accounting

IS-M-CA Contract Accounts Receivable and Payable

Valid Releases

Software Component Release FromRelease

To Release and Following

FI-CA 464 464 464

FI-CA 471 471 471

FI-CA 472 472 472

Related Notes

Number Short Text

1088904 Add. info. on upgrading to SAP ECC 6.0 SR3 ABAP

961410 Add. info. on upgrading to SAP ECC 6.0 SR2 ABAP

932814 Upgrade to SAP ECC 6.00 with FM: New SI includes

913971 Add. info. on upgrading to SAP ERP Central Component 6.0 SR1

850111 Business Function Sets for upgrading from IS-PS-CA 4.64 - 47

840783 Error message FAGL_LEDGER_CUST 020 or FAGL_LEDGER_CUST 023