Kontakt

Ansicht
Dokumentation

RFFMCY_CO_COPI - Transfer of CO Plan Data to BCS

RFFMCY_CO_COPI - Transfer of CO Plan Data to BCS

BAL Application Log Documentation   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

The program RFFMCY_CO_COPI copies CO planning version data to a Funds Management (FM) budget version in FM budgeting.

You use this program in FM budgeting after the budget preparation phase, in order to copy CO plan data to FM budget data, as a starting point for budget execution. You can generate budgets by transferring CO plan data to FM budgeting. For example, if you have 100 euros in the CO address, you transfer 100 euros to an FM budget address.

Note that you can only generate budget data in the target version using the internalbudgeting process ENTR.

Since this program generates budget entry documents, the generation of the original budget is documented in the header information.

Prerequisites

This program is only relevant for the FM budgeting.

Features

This data transfer can take place as often as desired. Note that this transfer overwrites all manual changes made in FM budgeting. However, this means that CO and FM budgeting remain in sync, with CO considered as the reference.

You must specify the CO fiscal year and the period.

If you choose the classical data source based on database table COSP and COSS, you must specify the source version.

If you choose the Financial Plan data source based on database table (ACDOCP), you must specify the ledger and Plan Category. Those plan values will be copied into the target version. You can limit the selection of plan data to certain cost centers, orders, projects, business processes and real estate objects.

Note: if no values are entered for the cost center, order number, business process, project, WBS Element, company code, Business Entity Number, Number of Building, Number of Land, Number of Rental Object and Contract Number in the selection options, no cost object will be selected. You can also limit the selection to certain cost elements. If you do not specify any values for the cost element inthe selection 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, for example, that you cannot select a range of cost centers and a cost center group at the same time.

Derivation

The program determines the receiver in FM according to the FM account assignments made to CO account assignments.

Note that if you use a value for the fund or functional area in your CO plan data, these values will be overwritten by the results of the derivation.

Also, note that if you use a value for a grant which is different from space/blank or different from the setting "not relevant for GM", the program will reject your cost object, since a budget with a grant value can only be posted to FM budgeting by way of Grants Management.

Caution: If you make any changes to the account assignment, the plan data used in FM until now will not be automatically transferred to the new receiver when the next plan data transfer takes place. You must make sure that during the next transfer, all FM assignments involved in this change to an assignment are included. If an old address is no longer derived, you have to reverse the corresponding document.

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 have more than one target budget type, depending on the CO planning data that was transferred. The input budget type is then overwritten. For more information, see the documentation of the IMG activity Enhance CO Plan Data Transfer.

Additional restrictions for FM account assignment

You can restrict the results of the derivation of CO account assignment to the FM account assignment by using this option.

Processing Options

The data is updated on the target version side according to the specified update mode. Note that for the optionReset and Overwrite, only the data that matches the selection criteria for the target (fiscal year, budget category, version, FM account assignments, and budget types) is reset.

If you use the intermediate table FMBUCOPI, the update mode is no more required.

The Grouping settings allow you to specify the FM account assignment element combinations to be grouped in one change document (line items table FMBDP). A new change document is created for each new fund. In the Grouping settings you can extend the grouping to one of the other FM account assignment elements (for example, you can checkmark the field Funds Center in order to get a new document for each new combination of fund and funds center). To avoid overflow in the change document number range (line items table FMBDP), you can only select 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 thedocument type and document 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 all generated budget entry documents.

Document Family Number

The documents created from one program run are grouped by a document family number and can therefore be easily retrieved again afterwards. For example, you can use the document family number for selection if you want to reverse all documents created in one run, by using the program Reverse Budget Entry Documents.

Text line

Each text line of document created is filled by the original CO address (for example, cost center K_100 and cost element 415000).

Requirements

  • It must be possible for FM account assignments to be derived from CO account assignments. For more information, see the SAP Library documentation on Funds Management in the section entitled "Integration with Cost and Project Controlling".
  • The program processes primary CO plan data from the COSP table ( if you choose the classical data source ) 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 results of the program run, provided this option was selected. This output list contains 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 and displayed.
  • 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 was generated for funds center S1 and commitment item AB. After the transfer of 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 transfers is 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 unchanged and S9/XX is increased by 650. In order to remain consistent, you have to decrease the budget of S1/AB by 650 when reversing the document in the BCS example.

Note

SAP recommends that you carry out the transfer of CO plan data in a version called "Template" or in a user-defined budget type, which you can call, for example "BTCO".

You should copy this budget version to the template via the copy program, after which the budgeting phase starts.

You should not use this template version as a real budget version, because if you enter budget on this template version and then rerun the CO transfer, your existing budget will be deleted by this new transfer. If you want to update your template version, there are two options:

  • If you have made changes to the derivation tool, you can reverse all your entry documents by means of the document family number and run a new CO transfer.
  • 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 "Reset and Overwrite". However, note that this scenario should only be used if only planned values exist for a version, with no manual changes having been made to the derivation tool previously.





Addresses (Business Address Services)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 14912 Date: 20240601 Time: 024557     sap01-206 ( 272 ms )