² 4XR 9DGLV” $& New GL Migration 7KLV LV $& FRXUVH YHUV FROO QG KDOI RI Duration: 3 days AC course version / Visit. Ã¢â‚¬Â¢ACenables project members and consultants to perform a migration project from classic to the new General Ledger Accounting. Therefore the. This chapter will explain the key areas of new functionality in the SAP General. Ledger, provide an overview of the most common migration scenarios, and.
|Published (Last):||4 September 2014|
|PDF File Size:||10.8 Mb|
|ePub File Size:||6.18 Mb|
|Price:||Free* [*Free Regsitration Required]|
Which parts of Customizing must already exist in the production system on the migration date?
Which tool is available to analyze these inconsistencies? However, if the given circumstances force a live migration inyou will have to create a new project migration package with the migration date set for January 1, because cross-fiscal year migrations are not supported by SAP.
For detailed information, see the field help F1 for this field. There are two possible workarounds. The system always creates documents with clearing lines. The migration cockpit includes migration packages that are preconfigured to some extent. You want to gwneral a new company code with the new General Ledger. The period sorted list in the fiscal year is not relevant. During document splitting, what must I consider in connection with cross-company postings?
Refer also to the report documentation and Notes and If you do not intend to use document splitting or if you use Release ECC 5.
If you have other, general questions about installation and distribution within the system landscape, contact Remote Consulting. You must distinguish between process-based passive splitting and rule-based active splitting.
The program first processes the document line items. For more information, see SAP Note Is it possible to change Customizing of the new General Ledger if the new General Ledger has been used productively? First implement the new company code. Industries in particular require separate entities for reporting purposes.
Which restrictions must I consider if I intend to activate the document splitting function in the new General Ledger?
Whether or not this is possible, or whether other alternatives exist, varies from customer to customer. Depending on the migration scenario, you can load the required migration package, which includes the migration steps in the form of a process tree.
In the old fiscal year, you use the reconciliation ledger for reporting and FI postings. Activation of validation of document splitting is also done in the migration plan in migration thee 1. If you want to continue using the standard CSA ledger 0F in parallel to the active new General Ledger, consider the following: You must take this into consideration when planning the migration to the new General Ledger.
After calling transaction SPRO, Customizing is possible in the new General Ledger in this systemand the new paths are displayed in the Implementation Guide veneral in the application menu. This means the migration date is always January 1. The reconciliation of the new General Ledger and Asset Accounting at a level below company code and account for example, profit center or segment is currently not supported.
As a result, you must adjust the document splitting rules accordingly if possible. From the posting data for the fiscal years prior to the migration date, only open items and balances are migrated to the new General Ledger.
New General Ledger Migration(FI-CO) – SAP SIMPLE Docs
Can you use profit center mass maintenance for initial assignment of the profit center to segments, or to migratuon assignments for profit centers not posted to yet? Can I perform a chart of nw conversion in the same fiscal year as the migration? When posting, it is also possible that the document is posted without document splitting. For more information, see the program documentation. If the program finds any differences, see SAP Note To solve the problem, proceed as follows: You are already using classic Profit Center Accounting and want to ledgrr subsequent segments.
What must I do to ensure that the document for the bill of exchange payment is split correctly in transaction F? Create Worklist with regard to runtime and performance? If you migratio across company codes, the settings for document splitting must be consistent in all pairs of relevant company codes.
You perform migrationn migration from the classic General Ledger to the new General Ledger at client level and it affects all company codes in this client. In this case, the process-based splitting is relevant only for some lines of the document.
Leave a Reply Cancel reply Enter your comment here The document splitting provides the account assignments when creating the bill of exchange liability for discounting and collection of the bill of exchange. Then set up the project for the transition from the classic General Ledger to the new General Ledger. Only Special Ledgers that are compliant with the new General Ledger can and should be transferred to the new General Ledger.
New General Ledger Migration(FI-CO)
This is to ensure the consistency of the migration. The migration program that migrates the documents from phase 1 processes only FI documents that update transaction figures to the classic General Ledger. It is correct system behavior for FI documents with a posting date prior to the migration date to have a data entry view but no general ledger view in the FI document display transaction FB The table T8G10 belongs to delivery class C Customizing.
The following aplies to the migration from the classical to the new general ledger: