Programme SAP RFFMCY_CO_COPI - Transfer of CO Plan Data to BCS

Purpose
The program RFFMCY_CO_COPI copies CO planning version data to aFunds Management budget version in theBudget Control System(BCS).
You use this program in BCS after the budget preparation phase, in orderto copy CO plan data to Funds Management budget data, as a startingpoint for budget execution. You can generate budgets by transferring COplan data to BCS. For example, if you have 100 Euros in the CO address,you transfer 100 Euros to an FM budget address.
Please note that you can only generate budget data in the target versionusing the internal budgeting process ENTR.
Since this program generates budget entry documents, the generation ofthe original budget isdocumented in the header information.

Prerequisites
This program is only relevant for the componentBudget Control System(BCS).

Features
This data transfer can take place as often as desired. Please note thatthis transfer will overwrite all manual changes made in BCS. However,when manual changes are overwritten, CO and BCS continue to remain insync, with CO considered as the reference. This is a main difference tothe previous program RFFMCOPI (transaction FM9C), which is used in theFormer Budgeting.
You must specify the CO fiscal year and the period, which are copiedinto the target version. You can limit the selection of plan data tocertain cost centers, orders, projects and business processes.
Note: if no values are entered for the cost center
, order number, business processand project in the selection options, no cost objectwill be selected. You can also limit the selection to certain costelements. If you do not specify any values for the cost element in theselection options, all cost elements of the Controlling Area will beselected.
If you have specified values for the field Group name
, the corresponding selections will be deactivated. This means, forexample, that you cannot select a range of cost centers and a costcenter group at the same time.
Derivation
The program determines the receiver in FM according to the FM accountassignments made to CO account assignments.
Note that if you use a value for the fund or functional area in your COplan data, these values will overwrite the results of the derivation.
Also, note that if you use a value for a grant which is different fromspace/blank or different from the setting "not relevant for GM", theprogram will reject your cost object, since a budget with a grant valuecan only be posted to BCS via Grants Management.
Caution: If you make any changes to the accountassignment, the plan data used in FM until now will not be automaticallytransferred to the new receiver when the next plan data transfer takesplace. You must make sure that during the next transfer, all FMassignments involved in this change to an assignment are included. If anold address is no longer derived, you have to reverse the correspondingdocument.
For the transfer of data to the target version, you can specify:

  • whether the payment budget and/or the commitment budget should be
  • updated
    • a unique budget type - for this, you can also implement the Business
    • Add-In FMCY_COPI_CO, in order to havemore than one target budget type, depending on the CO planning data thatwas transferred. The input budget type is then overwritten. Please seethe documentation of the IMG activityEnhance CO Plan Data Transfer for furtherinformation.
      INCLUDE BCS_REASSIGNMENT_RULE OBJECT DOKU ID TX
      Additional restrictions for FM account assignment
      You can restrict the results of the derivation of CO account assignmentto the FM account assignment by using this option.
      Processing Options
      The data is updated on the target version side according to thespecified update mode. Note that for the optionReset and Overwrite, only the data that matches the selectioncriteria for the target (fiscal year, budget category, version, FMaccount assignments, and budget types) is reset.
      The Grouping settings allow you to specify the FM accountassignment element combinations to be grouped in one change document(line items table FMBDP). A new change document is always created foreach new fund. In the Grouping settings you can extend the grouping toone of the other FM account assignment elements (for example, you cancheckmark the field Funds Center in order to get a new documentfor each new combination of fund and funds center). To avoid overflow inthe change document number range (line items table FMBDP), you can onlyselect one account assignment element in addition to the fund.
      You can run the program either as a test run or an update run.Background processing is also possible.
      Header Information
      You have to specify the document type anddocument date for the budget entry documents created.You can also add further information such as the document header text,responsible person and so on. The header information is displayed in allgenerated budget entry documents.
      Document Family Number
      The documents created from one program run are grouped by adocument family number and can therefore be easilyretrieved again afterwards. For example, you can use the document familynumber for selection if you want to reverse all documents created in onerun, by using the program Reverse Budget EntryDocuments.
      Text line
      Each text line of document created will be filled by the original COaddress (for example, cost center K_100 and cost element 415000).

      Preconditions

      • It must be possible for FM account assignments to be derived from CO
      • account assignments. For more information, see the SAP Librarydocumentation on Funds Management in the section entitled "Integrationwith Cost and Project Controlling".
        • The report only includes planning for CO objects whose company code is
        • assigned to an FM area in the IMG activity"Assign Company Code to FM Area". Thecompany code also has to be assigned to a controlling area in the IMGactivity "Assign Company Code toControlling Area".
          • The program processes primary CO plan data from the COSP table
          • for the following activities:
            ,,Primary cost planning (RKP1)
            ,,Revenue element planning (RKP5)
            ,,Planning activity-dependent primary costs (RKP6)
            ,,Planning periodic reposting (RKPB)
            • The program processes secondary CO plan data in the COSS table
            • for the following activities:
              ,,Planning settlement for internal activity allocation (KOAM)
              ,,Planning settlement (KOAP)
              ,,Planning debit from settlement (KOAS)
              ,,Planning periodical overheads (KZPP)
              ,,Planning activities (RKP2)
              ,,Planning secondary costs (RKP3)
              ,,Planning activity-dependent secondary costs (RKP7)
              ,,Planning settlement costs (RKP8)
              ,,Planning activity-dependent settlement costs (RKP9)
              ,,Planning indirect activity allocation (RKPL)
              ,,Planning overhead cost assessment (RKPU)
              ,,Planning overhead cost distribution (RKPV)
              ,,Secondary order cost planning (RKPW)
              ,,Activity-dependent secondary order cost planning (RKPX)
              ,,Planned credits for overheads (RKPZ)

              Output
              The program generates a detailed SAP List Viewer output with the resultsof the program run, provided this option was selected. This output listcontains the following information:

              • FM account assignment element

              • Cost objects and cost element

              • Internal budgeting process

              • Budget type

              • Total amount of the budget entry document line

              • Indicator specifying the maximum error degree (error, warning,
              • information)
                • Document number - in case the document was not posted (test run or
                • errors), a temporary document number is generated by the program anddisplayed.
                  • By double-clicking on the document you can go to the document display
                  • screen.
                    If errors occurred, an application log is created and displayed.

                    Example
                    Manual budget changes in FM - plan data transfer
                    Assignment ,,Plan value
                    Cost center K_100 - Funds center S1 ,, 500
                    Cost elem. 415000 - Comm. item AB,,,,
                    During the transfer of plan data, an original budget of 500 wasgenerated for funds center S1 and commitment item AB. After the transferof plan data, you increase:

                    • the original budget (S1/AB) to 800

                    • the plan value (K_100/415000) to 650

                    • A subsequent planning data transfer changes the original budget for(S1/AB) to 650, because the difference between the two transfersis 150. The transfer overwrites the manual changes.
                      Changes in account assignments - transfer of plan data
                      After the transfer of plan data, you change the account assignment:
                      • from K_100/415000 to S1/AB

                      • from K_100/415000 to S9/XX

                      • In the subsequent data transfer, the budget of S1/AB remains unchangedand S9/XX is increased by 650. In order to remain consistent, you haveto decrease the budget of S1/AB by 650 when reversing the document inthe BCS example.

                        Note
                        SAP recommends that you carry out the transfer of CO plan data in aversion called "Template" or in a user-defined budget type, which youcan call, for example "BTCO".
                        You should copy this budget version to the template via the copy program
                        , after which the budgeting phase starts.
                        Please note that you should not use this template version as a realbudget version, because if you enter budget on this template version andthen rerun the CO transfer, your existing budget will be deleted by thisnew transfer. If you want to update your template version, there are twooptions:

                        • If you have made changes to the derivation tool, you can reverse all
                        • your entry documents via the document family number and run a new COtransfer.
                          • If you make no changes to the derivation tool and there are only planned
                          • values for this version, you can run the program using the option "Resetand Overwrite". However, please note that this scenario should only beused if only planned values exist for a version, with no manual changeshaving been made to the derivation tool previously.

932908Mass transactions in simulation mode