Hierarchy
EA-PS (Software Component) SAP Enterprise Extension Public Services⤷
PSM-FM-MD (Application Component) Master Data⤷
FMCC (Package) FIFM: Cash budget management customizing
IMG Activity
| ID | FMBCS_V_FMBCSA_MIG | Activate Full Migration for Carryover Documents |
| Transaction Code | S_ALN_01002533 | (empty) |
| Created on | 20031222 | |
| Customizing Attributes | FMBCS_V_FMBCSA_MIG | Activate Full Migration for Carryforward Documents |
| Customizing Activity | FMBCS_V_FMBCSA_MIG | Activate Full Migration for Carryforward Documents |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FMBCS_V_FMBCSA_MIG |
Note:
The settings affected here are exclusively reserved for the use of the Budget Control System (BCS).
Use
Note
This IMG activity is only relevant if you have carried out fiscal year-end closing for the last fiscal year that you are using the Former Budgeting (FB) system.
In this IMG activity, you determine whether to apply a specific handling procedure for migrating the corresponding data. Document migration normally deals with data used since BCS activation. Therefore, the sender part of the carryover document (referring to the last fiscal year before BCS activation) is not taken into account by the document migration program.
Only the receiver part is migrated. As this leads to an unbalanced carryover, the FB process is mapped to represent a budget supplement in BCS.
To also migrate the sender part of the carryover, you need to carry out a migration of your budget totals including totals from the last year before BCS activation. Since no budgeting document is involved here, the budgeting process is not changed.
By checkmarking the full migration of carryover documents in this IMG activity, you to migrate the entire carryover document from FB via document-based migration. The corresponding data will then not be taken into account by the totals migration. The advantages are:
- the original process (carryover) is kept
- delta migration is sufficient if the year-end closing process is performed after the migration.
Note
This specific handling procedure cannot be used for budget release data. If you are using the release functionality, the system will not be able to determine which part of the released amount concerns carryover data. The specific handling of carryover documents will then lead to inconsistencies between released amounts and budgeted amounts in BCS.
Furthermore, for "carryback documents", the same logic also applies: the sender year is the first BCS year and receiver year is the last FB year. Unfortunately, such documents cannot be migrated, as BCS does not permit a carryback procedure.
Requirements
Standard settings
SAP does not deliver any standard settings.
Activities
- If necessary, set the indicator for full migration of carryover documents in your FM area by checkmarking the last column Carryover. Note that only FM areas for which BCS has been activated are available for selection.
- Save your entry.
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | FMBCS_V_FMBCSA_MIG | 0 | ALN0000194 | Budget Control System |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_FMBCSA_MIG | V - View | SM30 |
History
| Last changed by/on | SAP | 20031222 |
| SAP Release Created in | 500 |
