Top 115 New General Ledger Migration (FI-CO) Interview Questions and Answers

New General Ledger Migration(FI-CO) FAQ

1. Is a certificate available for the new General Ledger and migration to new General Ledger?

Yes. For information, see  868278 and service.sap.com/certificates.

2. Is a guide available for migration to the new General LedgerA migration guide is available?

Use the following link on SAP Service Marketplace: service.sap.com/~sapidb/011000358700003419192006D

3. How can I calculate the data volume in the new General Ledger (before the migration), and how can I evaluate the effects on system behaviour (especially on performance)?

For information, see 820495 and 1045430.

4. What restrictions are there during a new G/L migration regarding SAP CFM (Treasury) and/or SAP CML (Loans)

If you have selected migration scenario 4 or 5, you must contact SAP Support before the migration to the new General Ledger (preferably as part of the blueprint). This is because the migration scenario 4 or 5 with SAP CFM and/or SAP CML is not a standard migration, but a project-based migration.
For more information on SAP migration scenarios, refer to these FAQ and SAP Service Marketplace at: www.service.sap.com/GLMIG.

5. Which restrictions must I consider if I intend to activate the document splitting function in the new General Ledger?

For information, see 966000 and 985298.

In this context, see also the FAQ "Is there anything to bear in mind during the migration if document splitting is to be used?" in this note.

6. Which Special Ledgers can be transferred 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.

If you use additional currencies in a Special Purpose Ledger and want to replace this Special Purpose Ledger with the new General Ledger, you have to check the currencies used in the Special Purpose Ledger.  The migration programs read the data in the original FI document. If the Special Purpose Ledger you want to replace uses a currency that is not contained in the original FI document, you cannot migrate this data to the new General Ledger.   In this case, you must keep the relevant Special Purpose Ledger.

7. What must I consider in a system with more than one production client (multi-client system) regarding configuring, migrating and activating the new General Ledger?

The table FAGL_ACTIVEC with the field FAGL_ACTIVE (indicator: 'New General Ledger Accounting Is Active') is client-specific. All other tables that are relevant for the new General Ledger (tables with prefix FAGL_*) are also client-dependent.

If no data is exchanged between the productive clients, you can configure, migrate and activate the new General Ledger in each productive client independently.

8. Is it possible to upgrade to ECC5.0 or ECC6.0 and migrate from the classic General Ledger to the new General Ledger in the same fiscal year?

If you intend to use document splitting in the new General Ledger, activate the function for validating the document splitting in your productive system before the migration date. This means that you should upgrade to ECC 6.0 in one fiscal year, activate document split validation before the end of that fiscal year and migrate to the new General Ledger in the next fiscal year.

If you do not plan to use document splitting in the new General Ledger, you can upgrade to ECC5.0 or ECC6.0 and migrate to the new General Ledger in the same fiscal year.

Keep in mind that the function for validating document splitting is not available in ECC5.0.

9. What must I consider regarding migration to the new General Ledger and a local currency changeover (for example, changeover to the euro)?

Regarding the availability of tools for a local currency changeover in the new General Ledger, consider the following:

ECC 5.0 and 6.0:  Local currency changeover tools are available in the new General Ledger.

Regarding the projects for local currency conversion and migration to the new General Ledger, consider the following:

If document splitting is activated in the new General Ledger, it is not possible to perform local currency conversion and migration to the new General Ledger in the same fiscal year.

If local currency conversion and migration to the new General Ledger must take place in the same fiscal year, there is only one possible scenario:

Step 1: Local currency changeover in the classic General Ledger
Step 2: Migration to the new General Ledger without document splitting

All other scenarios, especially active document splitting in the new General Ledger, require that you perform local currency changeover and migration to the new General Ledger in different fiscal years.

10. Which system landscape is required for the test migrations?

For test migrations, you require a current copy of the productive client. The database and operating system of the test system must be comparable to the productive environment.

11. How should I check data consistency in the classic General Ledger before the beginning of the first test migration?

To check data consistency in the classic General Ledger before the beginning of the first test migration, proceed as follows:

1) Program RFINDEX

Execute the program RFINDEX twice.

In the first run, choose "Documents vs Indexes" in the selection screen.

In the second run, choose "Indexes vs Documents" in the selection screen.
For more information, see the program documentation.
If the program finds any differences, create a message on SAP Service Marketplace under the component FI-GL-GL-X.

2) Program SAPF190

Run program SAPF190 for the fiscal year prior to the migration and for the fiscal year in which the migration takes place.
If the program finds any differences, create a message on SAP Service Marketplace under the component FI-GL-GL-X.

3) Program RAABST02

If you use Asset Accounting, run program RAABST02.
If the program finds any differences, create a message on SAP Service Marketplace under the component FI-AA-AA-B.

4) Program RCOPCA44

If you use Profit Center Accounting, run program RCOPCA44.
If the program finds any differences, see SAP 81374.

Remove all inconsistencies before you start the first test migration.

12. Are there any recommendations for account control in G/L accounts before the start of the first text migration?

In G/L master data, the fields "Only balances in local crcy", "Open item management", "Display line items" and "Reconciliation account for account type" are relevant for the implementation of the new General Ledger.

Analyze these fields and adjust them if necessary before starting the first test migration.

"Only balances in local crcy": If the indicator "Only balances in local crcy" is not active, totals records of the account are updated to all currencies.  Check if this is necessary.  Postings in different currencies inflate the number of totals records in the table FAGLFLEXT.

"Open item management" (OI management):  Check for which accounts it is useful to manage open items.  Which accounts do you actually clear?

If use parallel ledgers in the new General Ledger, keep in mind that accounts with different valuations (for example, provision accounts) must not be managed on an open item basis.

If you use the foreign currency valuation program to post to accounts (program SAPF100 or transaction F.05), you should not manage these accounts on an open item basis.  For more information, see SAP 318399. You can configure foreign currency valuation in transaction OBA1.

You can use the report RFSEPA03 to switch off open item management in accounts that have been posted to.  For more information, see 175960.
"Display line items":  From a technical point of view, "Display line items" is no longer required for accounts that are not managed on an open item basis because the new General Ledger manages line items for each account in the table FAGLFLEXA.  After the migration from the classic General Ledger to the new General Ledger, you cannot switch offline item display until the external auditor has given approval.

"Reconciliation accounts for account type":  If you intend to activate document splitting, make sure that the reconciliation accounts for customers and vendors are controlled in the same way in all company codes. If, for example, a G/L account is a reconciliation account for customers, this must be the case in all relevant company codes because you have to classify accounts for document splitting at the chart of accounts level.

13. How can I display the IMG path and application menu for the new General Ledger in a Customizing system or in a test system for the migration?

To display the menu for the new General Ledger and the IMG path for implementing the new General Ledger, proceed as follows.

1) Execute the following step in the IMG (Implementation Guide):

Transaction SPRO -> Financial Accounting -> Financial Accounting Global Settings -> Activate New General Ledger Accounting.
Set the activation flag, and save the change in the subsequent Customizing order.
By setting (and saving) the activation flag, an entry is created in the FAGL_ACTIVEC table, which also contains other important information, for example regarding document splitting, GLT0 update, deriving the functional area in the entry view, and more.
After calling transaction SPRO, Customizing is possible in the new General Ledger (in this system), and the new paths are displayed in the Implementation Guide and in the application menu.

2) Immediately after step 1), deactivate the new General Ledger again in the same Customizing step and save the change in the Customizing order from

Step 1). However, the necessary entry remains in the table FAGL_ACTIVEC.
Important: If the new General Ledger is not active in any other client of this system, the IMG path disappears again.

3) Therefore, run the report RFAGL_SWAP_IMG_NEW. The IMG path will then be displayed again even though the new G/L is not active. You can now configure the new G/L in the test system without the new G/L is active, allowing you to start your first test migration.

4) However, in order to create a migration plan in the live system later (for example, to activate the document splitting validation in good time), transport the Customizing order from Steps 1) and 2) to your live system.

14. I want to add additional fields to the total record table (FAGLFLEXT) or line item table (FAGLFLEXA). What must I consider?

For information, see 961295 and 923687.

15. How should I set up my transport system in my new General Ledger project?

The following recommendation assumes that the transport management (workbench organizer and transport system: development, test, production) is set up in the productive ERP landscape.

You must store pure new General Ledger configurations, a configuration of validation of document splitting and activation of the new General Ledger in different transport orders. After completing the test, you can transport pure new General Ledger settings to a productive environment.   Transport the document splitting validation at a later stage.

Finally (after completing the migration), transport the activation indicator to the productive system.

16. Which parts of Customizing must already exist in the production system on the migration date?

If you use document splitting in ECC 6.0, we recommend that you activate the validation of document splitting in the production system at the latest on the migration date. This means that the new General Ledger including document splitting must be completely configured in the production system on the migration date and that all interfaces and ALE scenarios must be adjusted accordingly.

This does not apply to ECC 5.0 because the validation of document splitting is not available in ECC 5.0.

If you do not intend to use document splitting or if you use Release ECC 5.0, you can transport Customizing of the new General Ledger to the productive system after the migration date.

The indicator "New General Ledger Accounting Is Active" is transported with other basic settings of the new General Ledger in table FAGL_ACTIVEC. Ensure that the indictor "New General Ledger Accounting Is Active" is not set when you transport it to the production system.

17. When drawing up the project plan, what must I consider if I want to use document splitting?

We recommend that you activate document splitting validation at the latest on the migration date.
The new General Ledger including document splitting must be completely and finally configured before you activate document splitting validation.

18. Which are the criteria for creating a migration plan?

There are two basic types of migration plans:

• With document splitting
• Without document splitting.

If you plan to activate document splitting, this has a major impact on the migration.  You have to assign exactly one type to each migration plan. Therefore, if you want to activate document splitting for some company codes and not for others, you must create two migration plans.

Activation of validation of document splitting is also done in the migration plan in migration phase 1.

To create several migration plans, you also require different fiscal year variants. In this respect, only the first day of the fiscal year is relevant. The period sorted list in the fiscal year is not relevant.

If, for example, the fiscal year begins on January 1 in one company code and on March 1 in another company code, you must create two migration plans for the two company codes.

If company codes post across company codes and you want to activate document splitting in the new General Ledger, note the following: You must assign all company codes that post across company codes amongst each other to the same migration plan.

19. Can any date in the fiscal year be chosen as the migration date?

No. The migration date must be the first day of the fiscal year. No other date is possible.

If you want to perform the productive migration in fiscal year 20XY, you can perform test migrations in the previous fiscal year by setting the migration date to the first day of fiscal year 20XY # 1.

20. Which aspects must I consider regarding the activation date of the new General Ledger?

A prerequisite for the migration is that year-end closing has been performed for the previous fiscal year. The activation date does not have to be a particular date (for example, the first day of the month/period or the last day of the month/period). The migration requires downtime. The system can go live on any day in the month. We recommend that you choose a time slot for going live when the system standstill has minimal impact on your company. Consequently, weekends after or preceding public holidays are suitable dates, as are company holidays.

During the downtime, the migration programs are run. After successfully running the migration programs (but still during the downtime), figures before migration must be reconciled with figures after migration. After successfully completing the reconciliation, you can activate the new General Ledger.
Because the reconciliation of figures before and after the migration is usually done by the persons who are also in charge of the month-end closing, we recommended that you do not schedule activation of the new General Ledger at the same time as the month-end closing.

21. Is it possible to activate the new General Ledger at the company code level?

No. You activate the new General Ledger at the client level. This means that the new General Ledger is active for all company codes in the client at the same time.

22. Must I consider anything special for the tables ACCTHD, ACCTIT and ACCTCR in connection with the migration to the new General Ledger?

For more information, see 48009, section 8.

23. You want to configure a new company code with the new General Ledger. The existing company codes use the classic General Ledger. Can company codes use different general ledgers (classic and new) in the same client?

The implementation of new company code and the transition from the classic General Ledger to the new General Ledger are two different projects which you must schedule at different times.

You perform the migration from the classic General Ledger to the new General Ledger at the client level and it affects all company codes in this client.
Because the new General Ledger is activated at the client level, the new General Ledger would be active for all company codes, not only for the new company code. This would mean that the new General Ledger is active in the old company codes, but there was no migration from the classic General Ledger to the new General Ledger. This is not possible.

Therefore, it is not possible to start with a new company code in the new General Ledger while the classic General Ledger is still active in other company codes in the same client.

First, implement the new company code. Then set up the project for the transition from the classic General Ledger to the new General Ledger.
Alternatively: First set up the project for the transition from the classic General Ledger to the new General Ledger and migrate the data to the new General Ledger, then implement the new company code.

24. The system contains company codes that have no transaction data at all or company codes that have transaction data only in closed fiscal years and are no longer in use. These company codes are called inactive company codes. What must I consider regarding inactive company codes when migrating to the new General Ledger?

At the beginning of the current fiscal year, inactive company codes do not have open items, balance carryforwards or FI documents.
Therefore, exclude inactive company codes from the migration to the new General Ledger.

25. Must all company codes be migrated successfully before the new General Ledger can be activated?

Basically, all documents in all company codes must be migrated completely and without errors before you can activate the new General Ledger.
In exceptional cases, you can migrate some documents after activating the new General Ledger as long as the status of the migration plan has not been set to status "Migration ended". However, the project team must be aware of the consequences of missing documents for system operations. If, for example, you want to use document splitting, you cannot pay open payables from the current fiscal year until the document was migrated.

26. Is there a BAdI for transferring the balance carryforward from phase 0?

To derive the new account assignment fields (for example, Segment), you can use the BAdI FAGL_UPLOAD_CF. When deriving fields, you can use all fields in the structure GLU1 including any customer fields.

27. How can I use transaction FBCB post data to reconciliation accounts for assets and to accounts for input tax output tax?

Implement the corrections according to  937940.

28. What mass processing option is available for transaction FBCB?

Use batch input for mass processing of transaction FBCB. We recommend this, for example, if you want to split the balances of reconciliation accounts for assets to profit centres or segments.

29. Is the document splitting available for open items from previous fiscal years (phase 0)?

No. When migrating open items from previous years (phase 0) to the new General Ledger, the system does not split documents.
You can supplement the account assignment fields for open items from previous fiscal years in the form of a singular account assignment. This means that an open item can receive one value for each account assignment field. The BAdI FAGL_MIGR_SUBST provides this function.It is not possible to split the open item itself.  It is not possible to split the open item itself.

30. What must I do if I want the document splitting function to set partner assignments in company code clearing lines?

See 942542.

31. Is it correct that a clearing document has clearing items when the document split is active?

Yes. If document splitting is active, clearing documents will always have two line items in the entry view (table BSEG).  See 950773.
For information about clearing documents in phase 1, see 1054674.

32. Why does the batch input not issue an error message although the validation of document splitting is active and configured accordingly, and the condition for the validation is not met?

The view V_FAGL_SPL_PROC contains an entry that applies to all business transactions or for a specified business transaction in connection with the batch input indicator V_FAGL_SPL_PROC-BINPT. This configuration overrides the general setting for validation.

33. Why are account assignments missing from required entry fields for some documents from phase 1 even though validation of document splitting is active with an error message?

You reset cleared items in phase 1. Clearing documents do not receive the document splitting characteristics during posting because they receive the document splitting information from the cleared items during the migration. This relationship is lost due to the clearing reset. The BAdI can enrich the documents, or you can customize a clearing relationship for these documents in particular.

To avoid this situation, we recommend that you do not use transaction FBRA (Reset Cleared Items) during phase 1.
In addition, if the document to be reversed does not contain this account assignment, reversal documents will be posted without account assignments even though document splitting validation is active.

34. Does document summarization affect document splitting?

If you intend to use document splitting, you must consider document summarization as critical. You can never summarize fields that you want to use in document splitting (for example, profit centre, segment) and the relevant partner fields.

You must check which other fields you require for subsequent document splitting from phase 1 during the migration. The splitting is based on the data in table BSEG. Therefore, you cannot summarize the relevant fields.

After you activate the new General Ledger (phase 2), the system uses the table ACCIT (and no longer table BSEG) as the basis for document splitting.
Even if document splitting is not active, documents from phase 1 are subsequently posted from the table BSEG. Fields that were summarized in the classic General Ledger are also empty in the tables FAGLFLEXA/FAGLFLEXT after the migration.

35. If document splitting is active, which functions are available for processing bills of exchange?

If document splitting is active, the following relationship exists between document splitting and bill of exchange processing:

The document splitting provides the account assignments when creating the bill of exchange liability for discounting and collection of the bill of exchange. This function is available as of ERP 2004 Support Package 10.

ERP 2004 and 2005 do not provide any functions for document splitting of "bounced bills of exchange" (bill of exchange protest). The new invoice is posted without account assignments and not based on the input from the original invoice.
A workaround with default account assignment (by user exit or substitution) is possible for bounced bills of exchange. Alternatively, you can enter the original account assignment manually.

36. During document splitting, what must I consider in connection with cross-company postings?

If you post across company codes, the settings for document splitting must be consistent in all pairs of relevant company codes. This means that document splitting must be either active or inactive in both company codes forming a pair for cross-company postings.

37. Why does transaction FAGL_MIG_SIM_SPL (Simulation of Document Splitting) not behave in the same way as validation of document splitting and transaction FAGL_MIG_SPLIT (Subsequently Post Split Information)?

Transaction FAGL_MIG_SIM_SPL (Simulation of Document Splitting) takes into account only the document that is currently being processed, but no document flow. If the document being processed is part of document flow, transaction FAGL_MIG_SIM_SPL assumes that the original document already has entries in the tables that store document splitting information.

The validation of document splitting and transaction FAGL_MIG_SPLIT (Subsequently Post Split Information) both take into account the whole document flow.

38. Transaction FAGL_CHECK_LINETYPE (Check Business Transaction for Documents) shows, for example, errors in cross-company code transactions in the document of the non-leading company code. When document splitting information is built and the documents are migrated, the document splitting works correctly for both company codes.  Why does transaction FAGL_CHECK_LINETYPE (Check Business Transaction for Documents) not behave like the actual migration?

Transaction FAGL_CHECK_LINETYPE is not designed to simulate a complete business process. This means that, for example, a business process with cross-company code transactions for which the business process involves more than one document will not be checked correctly. Nevertheless these documents will be migrated correctly at a later stage and, as a result, the document splitting information will be built correctly.

Transaction FAGL_CHECK_LINETYPE always performs only a simple check to determine if Customizing is correct. The check will run into an error if the document that needs to be checked represents part of a complex business transaction.

39. You activated document splitting. You post the bill of exchange payment in transaction F-36. In transaction F-36 you choose "Incoming payment" and enter the customer. In the following screens, you enter the amount to be paid and select the invoices to be paid. When posting, the system issues message GLT2 201 "Balancing field "&1" in line item &2 not filled". When posting, it is also possible that the document is posted without document splitting. What must I do to ensure that the document for the bill of exchange payment is split correctly in transaction F-36?

The reason for this error is that you use a document type for the bill of exchange payment that is not configured according to requirements.

For the document splitting, you must process a clearing. You cannot process clearing from transaction F-36, therefore the document type must determine this. Configure a specific document type for the bill of exchange payment and use Customizing transaction GSP_VZ3 to assign this document type to business transaction 1010 variant 0001. Use this document type in transaction F-36.

Then use transaction OBU1 to change the default document type for transaction F-36.

40. What is the relationship between document splitting and validation?

You must distinguish between validation before document splitting and validation after document splitting. "Before document splitting" means that the validation is processed before document splitting.  "After document splitting" means that the validation is processed after the document splitting.

The purpose of validation before document splitting is to check that the prerequisites for document splitting are fulfilled. For example, the document type has a central control function for document splitting in the new General Ledger. Therefore it is vital for document splitting that you use the correct document type in each transaction. For example, you can use validation before document splitting for postings of bill of exchange payments (transaction F-36) to make sure that you use the document type which is configured for this purpose in transaction GSP_VZ3. To configure a validation before document splitting, use transaction OB28.

You can use a validation after document splitting to check the result of the document splitting. For this purpose, you can use the BAdI GLT0_AFTERSPLIT_VAL. For additional information, see Note 846004.

41. In which case does the document reversal trigger the reversal process in document splitting, and in which case are the document splitting rules processed?

The document splitting processes the reversal process for FI reversals (transaction FB08 and FBU8). In this case, no document splitting rules are processed. Instead, the system creates a reversed document from the account assignment information of the document to be reversed. The system determines the business transaction variant of the document to be reversed because some document splitting settings depend on the business transaction variant.
You must distinguish between process-based (passive) splitting and rule-based (active) splitting.

The system processes the process-based splitting in certain clearing processes and similar processes. This is triggered either by the process itself, for example in transaction FBRA (Reset Cleared Items, which is relevant only in special purpose ledgers with document splitting) or by FI reversal using business transaction RFBU or by the attributes of single document line items (clearing line items, line items belonging to an invoice).

For the FI reversal, the process-based splitting is relevant for the entire document. Each document line item "inherits" the account assignments of the relevant line item of the source document.

In the classic General Ledger, the system creates pure clearing documents for zero clearing. The relevant documents do not contain line items.
In the new General Ledger with active document splitting, the system does not create any zero clearings. The system always creates documents with clearing lines.

However, a clearing does not necessarily always have to be a zero clearing. You can also create a residual item or post differences. In this case, the process-based splitting is relevant only for some lines of the document.

Conclusion: If there is a rule-based or a process-determined split, it does not always apply to the entire document (that is only in exceptional cases). Usually,
only individual line items of a document are affected by the process-determined split - irrespective of which business transaction variant is processed.
A rule-based split always applies to business transactions that have no reference to a document that is already posted. In this case, one example is posting an invoice using an FI transaction. In addition, the rule-based split is processed by business transactions, which can be clearing processes or processes similar to clearing this is not necessary in every case. In this case, one example if the reversal by MM using MR8M. Reversals that are not executed using business transaction RFBU process the rule-based split. That is, depending on the document type of the document to be reversed, a reversal document type is assigned in OBA7.

In transaction GSP_VZ3, the system finds the business transaction variant for the reversal document type of the document to be reversed. Using the business transaction variant of this reversal document type, the Customizing of this reversal document type (defined in GSP_RD) is processed during the reversal document split. Keep in mind: Depending on the attributes of each line item, process-based (passive) splitting may be processed for single line items in this reversal as well.

42. What must I consider when creating the zero balance clearing account for document splitting?

See 961937.

43. Until when can I post to the previous fiscal year?

In this context, the "previous fiscal year" refers to the fiscal year prior to the migration date.

You can post to the previous fiscal year as long as you have not started the productive migration.

Once you have started the productive migration or migrated any objects (for example, open items), it is no longer possible to post to the previous fiscal year.
Once the new General Ledger has been activated, it is no longer possible to post to the fiscal year prior to the migration date either.

This means that the fiscal year closure for the previous fiscal year must be done in phase 1, that is, before starting the productive migration and before going live. All postings to the previous fiscal year must be stored before starting the productive migration. This includes postings according to the auditor#s instructions.

In many cases, you cannot be sure that no postings to the previous fiscal year will be required until the fiscal year closure has been certified.

44. What must I consider regarding down payment requests, parked documents and held documents?

The migration program that migrates the documents from phase 1 processes only FI documents that update transaction figures to the classic General Ledger. This program does not process down payment requests, parked documents and noted items.

You must check if you have to add values for the new fields you have introduced with the new General Ledger (for example, functional area, profit center, segment) in parked documents and noted items.

45. How can I transfer planning data from CO-OM (Controlling # Overhead Management) to the new General Ledger?

Proceed as follows to transfer planning data from CO-OM (Controlling # Overhead Management) to the new General Ledger:

First, configure Customizing for planning in the new General Ledger according to the steps in the implementation guide.
Then transfer existing planning data from CO-OM (planning data on cost centers and internal orders) to the new General Ledger. Choose the following path in the implementation guide:

• General Ledger Accounting (new)
• Planning
• Transfer Planning Data from CO-OM

46. How can I transfer planning data from classic Profit Center Accounting (EC-PCA) or from the classic General Ledger to the new General Ledger?

To transfer planning data from classic Profit Center Accounting (EC-PCA) or from the classic General Ledger to the new General Ledger, proceed as follows:
First, configure Customizing for planning in the new General Ledger according to the steps in the implementation guide.

No specific functions are available for transferring planning data from classic Profit Center Accounting (EC-PCA) or from the classic General Ledger to the new General Ledger.

There are two possible workarounds. You can use transaction GP52. Alternatively, you can use a rollup to transfer the planning totals to the new General Ledger. For the latter, you must allow rollup for the new General Ledger by making the required changes directly in two customizing tables. You can implement the second alternative only if you have sufficient technical knowledge.

Since both alternatives are workarounds, you must perform extensive tests.
If you have not planned locally in classic Profit Center Accounting and planning data was created exclusively in classic EC-PCA as a result of planning integration with CO-OM, transfer CO-OM planning data to the new General Ledger instead of transferring EC-PCA planning data.

47. What must I consider if the real-time integration from CO to FI is active and standard CSA (cost of sales accounting) ledger 0F is active?

You must distinguish between phase 1 (from migration date to activation date) and phase 2 (from activation date onwards).

Phase 1: The classic General Ledger is active, the real-time integration CO -> FI is active, and the standard CSA ledger 0F is active.
Since real-time integration is active, the reconciliation ledger will not create any more FI postings in phase 1. In phase 1, the FI documents from real-time integration must not be posted to the classic General Ledger only, but also to the ledger 0F.

When activating real-time integration CO -> FI, you must assign activity COFI to ledger 0F manually by the migration date at the latest. Use transaction GCL2 to assign activity COFI to ledger 0F.

Phase 2: The new General Ledger is active, the real-time integration CO -> FI is active, and the standard CSA ledger 0F is active.

If you want to continue using the standard CSA ledger 0F in parallel to the active new General Ledger, consider the following:
Since real time integration is active, the reconciliation ledger will not create any more FI postings. The FI documents from real-time integration must not be posted to classic General Ledger only, but also to the ledger 0F.
When activating real-time integration CO -> FI, you must assign activity COFI to ledger 0F manually. Use transaction GCL2 to assign activity COFI to ledger 0F.

If the Customizing settings for the variant for real-time integration specify that the real-time integration documents are posted with a ledger group, you must use transaction GCL2 to fill the "Reference Ledger" field in ledger 0F with the leading ledger of the new General Ledger (for example, 0L). Ledger 0F will then be updated only with FI documents that were posted to the relevant ledger of the new General Ledger (for example 0L).

48. In the variant for real time integration CO -> FI, enter the "Key Date: Active from" and activate the indicator "R.-Time Integ:Active". This activates real-time integration CO -> FI beginning on the specified date. Which point in time is recommended for activating the real-time integration CO -> FI?

A basic recommendation is to activate real-time integration CO -> FI either before or after activating the new General Ledger. This approach reduces the number of activities related to the activation of the new General Ledger during the downtime.

If you want to analyze cost elements in the new General Ledger we recommend that you activate real-time integration CO -> FI after activating of the new General Ledger. The reason is that the "Cost element" field in the migration is filled only for documents created in the classic General Ledger by real time integration (see SAP 1031706 and 1036248).

See also 1028743. Reasonable points in time for activating real-time integration CO -> FI are, for example, the beginning of the period, the quarter or the fiscal year that follows the activation of the new General Ledger.

Get Here Information about SAP FICO Books.

If you do not want to analyze cost elements in the new General Ledger we recommend that you activate real-time integration CO -> FI after on the migration date (where the key date is the migration date). In this case, Customizing of real-time integration must be available in the productive system at the latest on the last day of the old fiscal year.

The activation of real-time integration CO -> FI on the migration date represents a clear separation: In the old fiscal year, you use the reconciliation ledger for reporting and FI postings. In the new fiscal year, you use the new General Ledger for reporting and real-time integration creates the FI postings.
Another advantage of this approach is that you do not have to perform subsequent posting using report FAGL_COFI_TRANSFER_CODOCS.

49. How can I post cross-profit center, CO-internal allocations to FI?

In the variant for real-time integration CO -> FI, activate the indicator "Cross-Profit-Center". The same applies if you want to post CO-internal allocations to FI that cause a change in company code, business area, functional area, segment or grant.

50. The migration program used to transfer documents from phase 1 processes only FI documents. It does not process internal CO documents (for example, from assessments) that were created in phase 1. You require these documents in the new General Ledger, for example, because you want to replace classic Profit Center Accounting with the new General Ledger or because you evaluate cost elements in the new General Ledger. How can I migrate internal CO documents from phase 1 to the new General Ledger?

After activating the "Real-time integration CO -> FI", you can use the program "Transfer CO Documents into External Accounting" (FAGL_COFI_TRANSFER_CODOCS). This program finds all CO documents with a posting date (BUDAT) that is later than the "Key Date: Active from" date in the variant for real time integration CO -> FI and that have not been posted in real-time mode from CO into FI.
You may have to reopen closed periods for this activity.

51. The migration program used to transfer documents from phase 1 processes only FI documents. It does not process internal EC-PCA documents (for example, from distributions) that were created in phase 1. How can I migrate internal EC-PCA documents (for example, from distributions) from phase 1 to the new General Ledger?

It is not possible to migrate internal EC-PCA documents from phase 1 to the new General Ledger. If the internal EC-PCA documents result from allocations (for example, from distributions), you can create new cycles in the new General Ledger and rerun the cycles in the new General Ledger subsequently for the periods of phase 1.

52. Note 740519 describes the derivation of the functional area.

When the new General Ledger is active, can I still use the old functional area derivation for event 0005 (filled after the document entry view) instead of using event 0006?

You can continue to use the old derivation of functional area according to event 0005. There is a switch in Customizing that makes it possible to use event 0005 in the new General Ledger.

Choose the following path in the implementation guide:  Financial Accounting (New) -> Financial Accounting Basic Settings (New) -> Tools -> Customer Enhancements -> Enhance Determination of Functional Area
In this Customizing transaction, deactivate the indicator "Determine FArea on Entry Screen". For detailed information, see the field help (F1) for this field.

53. What must I consider in module CO (Controlling) regarding functional area and segment?

For information, see 764485 and 981184.

54. How can I update the functional area and segment in CO totals records?

To activate the update of the functional area and segment in the CO totals tables, perform the following step in the implementation guide:

• ECC 5.0: Controlling -> General Controlling -> Include Characteristics in CO Totals Records
• ECC 6.0: Controlling -> General Controlling -> Include Characteristics in CO Totals Records

For more information, see Note 764485.

55. Which entries are required in the productive client in the table T8G10?

The table T8G10 belongs to delivery class C (Customizing). For this reason, during the upgrade to SAP ERP, new entries are inserted only in client 000 in table T8G10. After the upgrade, transport the following entries of the table T8G10 from client 000 to your productive client:

TCODE PROCESS VARIANT
FB1D 1010 0001
FB1K 1010 0001
FB1S 1010 0001
FBRA 1020 0001

56. In the first run of the program FAGL_MIG_RPITEMS_CRESPLIT (Build Document Splitting Information for Documents To Be Transferred), the system may not process all documents successfully. What can I do?

This issue is most likely to occur if you have cross-company code postings. One reason can be the way the program internally sorts and processes the documents.

To resolve the problem, simply start the program FAGL_MIG_RPITEMS_CRESPLIT (Build Document Splitting Information for Documents To Be Transferred) again.

57. What must I consider in a mass run of the program FAGL_MIG_FICHAN (Supplement FI Documents: Create Worklist) with regard to runtime and performance?

The runtime of the program FAGL_MIG_FICHAN may be very long if a large amount of documents must be processed. This is due to the technical characteristics of spool administration.

For instance: In one program run, you want to process 100,000 documents with 1,000,000 lines in the table BSEG. You start the program FAGL_MIG_FICHAN in the background. The program first processes the document line items. The program then prepares the spool list. The program tries to save a list with 1,000,000 lines in the spool. The attempt to save the list may take very long. For one customer, the processing of 3,000,000 document line items took three hours, while the creation of the spool request was not yet finished after three days.

Solutions:

• Execute the program for only a few documents at a time. You can adapt the data volume by entering intervals for the document numbers in the selection screen.
• When processing a high volume of documents, choose "Display Errors Only" in the selection screen.

58. How can I improve the performance of the program FAGL_MIG_SUBSEQ_POST (Update Documents to New General Ledger Accounting)?

To improve the performance of the program FAGL_MIG_SUBSEQ_POST (Update Documents to New General Ledger Accounting), perform the following steps:

a) Update database statistics for the table FAGLFLEXA.

Before the migration, the table FAGLFLEXA is empty. The sequential processing of the program steps gradually fills the table FAGLFLEXA with data. When transferring documents from the current year to the new General Ledger, the program FAGL_MIG_SUBSEQ_POST whether each document exists in the table FAGLFLEXA. However, during the migration, the Cost-Based Optimizer (CBO) does not yet have the required information to select the right index for accessing the database tables.

To solve the problem, proceed as follows: As soon as you have migrated some data to the new General Ledger tables (for example, after migrating open items and before migrating documents from the current year), you should run the CBO or update table statistics.
The programs should then use the correct index for the database access and this should considerably reduce the runtime.
In more detail, proceed as follows: Activate the trace in transaction ST05. Start the program FAGL_MIG_SUBSEQ_POST, for example, for one document. Deactivate the trace and display the trace.

Position the cursor on "FAGLFLEXA" and choose "Explain". You can see when statistics were created for the last time and which index is being used. You can also start the update of the statistics from here.

b) "Execute with Para.Proc." in the selection screen of program FAGL_MIG_SUBSEQ_POST
We recommend that you activate "Execute with Para.Proc." in the selection screen of the program FAGL_MIG_SUBSEQ_POST, to reduce the runtime.
When you activate "Execute with Para.Proc.", you must set two R/3 parameters as follows:
rdisp/bufrefmode                        sendon,exeauto
rdisp/bufreftime                        set this parameter to the lowest possible value
For more information, see 384167 and 36283 as well as the related.
If you set the R/3 parameters accordingly, you will avoid error message GI 754 during parallel processing of the program FAGL_MIG_SUBSEQ_POST.

59. The program FAGL_MIG_OPITEMS_CRESPLIT generates the document splitting information for open items. Is it possible to parallelize the program FAGL_MIG_OPITEMS_CRESPLIT?

It is not possible to run the program FAGL_MIG_OPITEMS_CRESPLIT more than once at a time. This applies even if the selection refers to different migration plans.
If you try to start the program FAGL_MIG_OPITEMS_CRESPLIT for a second time in parallel mode, the system issues message MC 601 "Object requested is currently locked by user &" . .
This is due to the design of the program and the design of the migration.

60. The program FAGL_MIG_RPITEMS_CRESPLIT generates the document splitting information for documents of the current year. Is it possible to parallelize the program FAGL_MIG_RPITEMS_CRESPLIT?

It is not possible to run the program FAGL_MIG_RPITEMS_CRESPLIT more than once at a time. This applies even if the selection refers to different migration plans.
The program sets a LOCK on some of the database tables for the migration. This is to ensure the consistency of the migration.

61. What must I consider regarding the database before the productive migration?

There are two major aspects. First, perform a full backup before the productive migration is started. Second, deactivate database logging before starting the productive migration.

62. What can I do in order to minimize the downtime for productive migration?

Prerequisites for beginning the productive migration are that the fiscal year closure for the previous fiscal year has been finalized and approved by your auditor, that there is no further need for postings to the previous fiscal year and that the new General Ledger is finally configured.
The incremental approach minimizes the downtime required for the productive migration. The cornerstone of the incremental approach is to migrate most of the data whilst the system is up and running.

In detail, in the incremental approach means that you migrate balances and open items in a first wave before the downtime while the R/3 system is running as normal. In a second wave, you migrate documents of the current fiscal year - also while the system runs normally. During the downtime, migrate the remaining documents of the current fiscal in a third wave.

In the first wave, you can transfer balances and open items during phase 1 without any system downtime in parallel to normal production operation. If the migration of balances and open items fails, you can reset the migration during production operation using transaction FAGL_MIG_RESTORE_ALL.
In a second wave, you migrate documents of the current fiscal year to the new General Ledger during normal operation. You can start the second wave, for example, two weeks before the downtime. Run the programs "Create Worklist for Documents" (FAGL_MIG_RPITEMS_FILL), "Build Document Splitting Information for Documents To Be Transferred" (FAGL_MIG_RPITEMS_CRESPLIT) and "Update Documents to New General Ledger Accounting" (FAGL_MIG_SUBSEQ_POST).

After this initial migration of documents from the current year, you can repeat this process every day by scheduling recurring jobs (for example once a day at night time).

Each time you run the programs, the documents that have been posted since the last program run are migrated to the new General Ledger. After the initial migration of documents from the current year, always set the "Read Completely" indicator in the selection screen of the program "Create Worklist for Documents" (FAGL_MIG_RPITEMS_FILL).

In the third wave during the downtime, the system migrates the remaining documents from the current year that were posted since the second wave. During the system downtime, create a last worklist for documents of the current year and, for the last time, run the program that generates the document splitting information. Then transfer the remaining documents from the current fiscal year. To do this, once again run the programs "Create Worklist for Documents" (FAGL_MIG_RPITEMS_FILL), "Document Splitting Information for Documents To Be Transferred" (FAGL_MIG_RPITEMS_CRESPLIT) and "Update Documents to New General Ledger Accounting" (FAGL_MIG_SUBSEQ_POST).

In the third wave, consider the following two aspects: First, set the "Read Completely" indicator in the selection screen of the program "Create Worklist for Documents" (FAGL_MIG_RPITEMS_FILL). Second, deselect the indicator "Execute with Para. Proc." in the selection screen of the program "Update Documents to New General Ledger Accounting" (FAGL_MIG_SUBSEQ_POST).

After successfully reconciling the data of the classic General Ledger and the new General Ledger, activate the new General Ledger during the downtime.
To summarize, the incremental approach means that only the activities for the third wave are performed during the downtime. Everything else can be done before the downtime during normal R/3 operation.

63. How can I deactivate classic Profit Center Accounting (EC-PCA) after activating the new General Ledger?

Note 702854 explains how to deactivate classic Profit Center Accounting.
If you use document splitting for profit centers in ERP2004, delete the dummy profit center from the table TKA01 also. For this purpose, Note 702854 provides the program Z30PCA23. Use the program Z30PCA23 to delete the dummy profit center of classic Profit Center Accounting in the controlling area.

64. The tables that are required for the migration (tables FAGL_MIG*) take up a lot of disk space (for example, 350 MB). Can I delete the tables FAGL_MIG* after the productive migration?

No. The content of the tables FAGL_MIG* must remain in the database. The data from the tables FAGL_MIG* is required for controls and checks and to verify the migration.

65. Is it possible to change Customizing of the new General Ledger if the new General Ledger has been used productively?

See Note 891144.

66. Can I continue to use the reports RFINDEX and SAPF190 (from the classic General Ledger) to reconcile documents # transaction figures # indexes in the new General Ledger?

In the new General Ledger, use report TFC_COMPARE_VZ (transaction FAGLF03) to reconcile totals records (T tables, such as table FAGLFLEXT), line items (A tables, such as table FAGLFLEXA), secondary indexes (such as tables BSIS and BSAS), and FI documents (tables BKPF and BSEG/BSEG_ADD). Refer also to the report documentation and 862523 and 946596.

67. The classic General Ledger contains the reports RAABST01 and RAABST02 to reconcile the general ledger and Asset Accounting (FI-AA). Which reports are available to reconcile the new General Ledger and Asset Accounting (FI-AA)?

You can use report RAABST01 to reconcile the new General Ledger and Asset Accounting. As a prerequisite you require ECC 5.0 Support Package 01 or 752329.
You can use report RAABST02 to reconcile the new General Ledger and Asset Accounting. As a prerequisite you require ECC 5.0 Support Package 01 or ECC 6.0 Support Package 7. It is not possible to downgrade this function. See 897388.

Read here SAP FICO Transaction Codes.

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.
For general information about reconciling of the general ledger and Asset Accounting (FI-AA), see 543151.

68. CO-FI real-time integration and the new General Ledger are active. How can I reconcile data in the new General Ledger with data in Controlling (CO)?

Use transaction FAGLCORC for the reconciliation. For further information, see 908019.

69. In the new General Ledger, line items do not match the relevant totals records, or the totals records are not updated correctly. Which tool is available to analyze these inconsistencies?

See 940668.

70. What must I consider for allocations for balance sheet accounts and reconciliation accounts in the new General Ledger?

For information, see 830556 and 900962.

71. Which report in new General Ledger accounting has the same features as the report RCOPCA02 (Profit Center: Actual Line Items) in classic Profit Center Accounting?

Transaction FAGLL03 in new General Ledger accounting has the same features as the report RCOPCA02 (Profit Center: Actual Line Items) or transaction KE5Z in classic Profit Center Accounting.

72. Is it possible to select customer-specific fields in the line item display of the new General Ledger (transaction FAGLL03)?

945932 explains how to select customer-specific fields in the line item display of the new General Ledger (transaction FAGLL03).

73. Is it possible to display, sort and summarize customer-specific fields in the line item display (transaction FAGLL03) in the new General Ledger?

See 984305.

74. How can I display the offsetting account in the line item display?

SAP 112312 describes how you can display the offsetting account in the line item display in the classic General Ledger.
SAP 1034354 describes how you can display the offsetting account in the line item display in the new General Ledger.

75. Why is the "Alternative Account Number" field not displayed in reporting of the new General Ledger?

To display the "Alternative Account Number" field in report of the new General Ledger, please proceed as follows:
1) Implement  895609 and 939649.
2) To display #Alternative Account Number# in the line layout variant, proceed as follows:
- Call transaction O7R3 and add BSEG-LOKKT as special field.
- Then change the line layout variant. The system now displays the "Alternative Account Number" field.
3) In the line item display in the classic General Ledger (transaction FBL3N), you could enhance the custom selections in transaction SE36 as described in 310886. However, in the new General Ledger, the custom selection in transaction FAGLL03 has different sub-areas. Each of these areas corresponds to a structure:
G/L account master record SKA1_FS
G/L account company code SKB1_FS
G/L account line item BSIS_FS
Since the "Alternative Account Number" is not included in the structure SKB1_FS in the standard delivery, please implement the enhancement as described in 945932.  To include more fields in the custom selections of transaction FAGLL03, you can enhance the structures using an APPEND.

76. Segment reorganization is the term for the option of changing the segment in a profit center when transaction data is already stored. Is it possible to change the segment in a profit center when transaction data is already stored?

No. 940721 describes the current status in the standard R/3 system.
In the current SAP release planning, we have not included any functions for segment reorganization for future R/3 releases. It is not possible to say whether or when SAP will offer functions for segment reorganization in the R/3 standard system.
The feasible approach for segment reorganization will be a customer specific solution.
In the short term, you can use the following approach, which considers only a technical solution. Deimplement 940440, 1037986 and 940629 from your system. After this, define the "Segment" field as a time-based field in transaction 0KE7. Then you can change the segment in the profit center master data even if transaction data exists.
Take into account that this solution does not guarantee data integrity. For example, you must also manually repost the profit center balances from the old segment to the new segment.
 

77. The new General Ledger is active. The "Profit Center Update" scenario is assigned to the ledger. Cost centers are stored in the asset account master data. You change the profit center in a cost center that is used in the asset account master data. How are the relevant balances for each profit center (for example, for acquisition and production costs) reposted in the new General Ledger?

There is no automatic process that changes balances for each profit center in the new General Ledger after the profit center has been changed in a cost center that is used in asset master records. As a workaround, you can perform a manual correction posting.
Proceed as follows:
1) Identify the values that you must repost. For this purpose, you can use the report RABEST01. Fill the field "Cost center" in the selection screen of the report RABEST01 with the cost center that has been assigned to a different profit center.
2) Set the status to "1" in the company codes that require adjustment postings. To do so, use the following path in the implementation guide:

Financial Accounting -> Asset Accounting -> Preparing for Production Startup -> Production Startup -> Activate Company Code.
3) Use transaction OASV to perform adjustment postings to debit or credit the profit center on reconciliation accounts in asset accounting.
4) Afterwards, reset the status of the company codes to "0".

78. What is the migration cockpit?

The migration cockpit is the migration tool recommended by SAP. The migration cockpit includes migration packages that are preconfigured to some extent. You can load these packages for the migration from the classic General Ledger to the new General Ledger.
Depending on the migration scenario, you can load the required migration package, which includes the migration steps in the form of a process tree.
1041066 provides instructions for installing the migration cockpit.

79. Where can I find information about the SAP Migration Service?

See 812919.

80. When the new General Ledger is active, why do documents exist which have a data entry view but no general ledger view in the FI document display (transaction FB03)?

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. FI documents with a posting date prior to the migration date are not migrated to the new General Ledger. Therefore, no general ledger view is created for these documents.
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 FB03).

81. What must I consider for the currency settings for the new General Ledger?

As before, the leading ledger usually manages the document currency and the first local currency. There is also the option of managing two additional, parallel currencies. Non-leading ledgers can manage only (a selection of) the currencies that are defined for the leading ledger.
When replacing the classic Profit Center Accounting, check that the previous profit center accounting currency is managed as the local currency or parallel currency in FI since before the migration date. If this is not the case, see Note 39919 for information about subsequently implementing a parallel currency in FI. You cannot perform the required data enrichment for phase 0 and phase 1 immediately before or during the migration.

82. Do you require a Unicode system for SAP General Ledger Migration?

No, a Unicode system is not required.

83. Is there a migration scenario that represents parallel accounting using non-leading ledgers?

Using migration scenarios 4 and 5, migration can take place from the accounts approach to the non-leading ledger approach in the context of parallel accounting.

However, the new implementation of parallel accounting is not intertwined with the migration and basically represents a project of its own.  You can integrate this into the migration project, but is not, however, part of the SAP General Ledger Migration Service. All aspects for the implementation of parallel accounting, relating also to integration into the migration project, must be covered by additional consultation.

84. Are there recommendations for when the document splitting should be introduced?

Usually, the splitting is worthwhile if the customer wants to use Financial statement and Profit and Loss Statement (fields) in an additional entity. In the new General Ledger, this is always possible for the profit center and the segment. Industries in particular require separate entities for reporting purposes. PCTR and Segment are predefined standard fields. You can include additional fields in the tables using a standard mechanism (transaction FAGL_GINS).

85. Is there anything to bear in mind during the migration if document splitting is to be used?

If you want to use the document splitting (immediately) after migration from the classic General Ledger to the new General Ledger, (only) migration scenarios 3 and 5 are available for this. Both of these migration scenarios (or "migration packages") are already based on active document splitting within the migration from classic to new General Ledger Accounting.

Note:As of 2008, migration package 6 (=> Subsequent implementation of document splitting) also provides the option of activating the document splitting subsequently, if the new General Ledger is active without document splitting.

More information about all delivered migration scenarios or migration packages is available on SAP Service Marketplace under: www.service.sap.com/GLMIG, for example, in the PDF file "Overview Presentation: SAP General Ledger Migration".

86. How is the runtime affected when you use the document splitting? What has been experienced?

There is currently no research on this subject relating to what customers have experienced. However, there are issues and concerns from time to time. In 99% of cases, these are unfounded.  Refer to the following notes for additional information:
820495 NewGL: Data volume, performance and parallel ledgers 1045430 Calculation of the number of totals records
Using both, you should get an assessment of how the customer systems are performing under the given circumstances.

87. You are already using classic Profit Center Accounting and want to introduce subsequent segments. Can you use profit center mass maintenance for initial assignment of the profit center to segments, or to change assignments for profit centers not posted to yet?

1101561 manages the change options for the segment in profit center mass maintenance (transaction KE55) in the same way as in profit center individual maintenance (transaction KE52) using the view V_FAGL_SEGM_PRCT. If new General Ledger Accounting is not yet active in your system, the Maintain Segment indicator must also be set in the view V_FAGL_SEGM_CUST so that you can maintain the assignments.

The difference to KE52 is that the check for existence of transaction data (which may be very time-consuming) in mass maintenance cannot take place until you save.   It is not a problem if the segment was initial beforehand, in other words, the profit center was not assigned to any segment. If a segment was assigned before, the change may be 'rejected' (with the relevant error message). In mass maintenance, it is not possible to perform prior checks and then set the segment field for a profit center to Can be changed, and set to Cannot be changed for the next one.

88. Migration and the (EhP3) 'clearing specific to ledger groups' function. What must I take into account?

As of  EhP3 (SAP ERP 6.0), the clearing specific to ledger groups function will be available when you use the new general ledger.

The following aplies to the migration from the classical to the new general ledger:  It is not technically possible for you to convert the account master records to 'clearing specific to ledger groups' before or during the migration, that is, you cannot implement this together with the migration.

Therefore, you must convert the account master records in a separate step after the migration with an active new G/L. This separate step is not part of the SAP General Ledger Migration service.

This function is also not taken into account in the migration cockpit for migrations within the new General Ledger Accounting where EhP3 is also in use.

If you are an EhP3 customer and you are planning a migration using the SAP General Ledger Migration service, inform the General Ledger Migration Back Office

89. How or where do you install the migration cockpit in the system (NMI_CONT Add-On)?

Note the following relevant points:

1.  Install the cockpit in all of the systems in which the migration is to occur.
2. The NMI_CONT  add-on is an official SAP add-on and is handled as such. The way in which the customer performs the installation depends mainly on customer-specific internal processes.
3. See 97620 and 97621 for general information about installing add-ons (TCode SAINT) and Support Packages (TCode SPAM).
4. You must attend Course AC212 for detailed information about handling the cockpit.

If you encounter technical problems, contact Support. If you have other, general questions about installation and distribution within the system landscape, contact Remote Consulting.

90. If you want to carry out comparative reporting after the migration, how do you transfer the totals records of the previous fiscal year from classical General Ledger Accounting, the classical Profit Center Accounting, or from an SL ledger to new General Ledger Accounting?

See 893206 for information about cross-fiscal year reporting.

91. Which documents are transferred to new General Ledger Accounting?

The content of the worklist is used to construct the new totals tables (FAGLFLEXT) and the line item tables (FAGLFLEXA) from the documents of the current fiscal year for all G/L accounts by period. In the simplest case, you merely enter a migration plan that contains the company codes to be migrated.
Only open items are transferred from the previous fiscal years.

92. What options does SAP offer for mapping parallel accounting and which options are supported by standard migration scenarios?

The following solutions/options are available for mapping parallel accounting in a SAP system:

1) Account solution
=> possible in the classic General Ledger and the new General Ledger.

2) Ledger approach in FI-SL (Special Purpose Ledgers (of the component FI-SL) are updated by assigning accounting principles)
=> possible (only) with the classic General Ledger

3) Company code solution
=> possible only in the classic General Ledger

4) Ledger approach in the new General Ledger
=> possible only in the new General Ledger

5) Special customer solution

Standard migration scenarios support only (continuation of) the accounts approach or the replacement of the accounts approach by the ledger approach in the new General Ledger.

If you use mapping options 2, 3 or 5 in the classic General Ledger, and you want to switch to the account approach or ledger approach within the migration, this is always a customer specific migration. That is, this type of migration cannot be mapped completely with any of the available standard scenarios. Migrations such as this are often executed as customer-specific projects based on scenario 2 or 3. Whether or not this is possible, or whether other alternatives exist, varies from customer to customer.

It is not possible to continue to use or to implement options 2, 3 or 5 in a migration to the new General Ledger.

93. Why can I not specify a tax code in transaction FB01L (ledger-specific posting) even though the account is tax-relevant?

We are not aware of any business transactions in which ledger-specific postings require a tax key. Therefore, this field does not exist and is also not checked unlike in transaction FB01. Sales tax-relevant postings are always posted in all ledgers.

This may result in certain inconsistencies because (unlike posting with transaction FB01L) when you use periodic APC posting with transaction ASKBN, the tax code is set for ledger-specific posting. This is due to the attributes of the G/L account. Since Asset Accounting always posts net, you should always set the "Posting without tax allowed" indicator for the relevant G/L accounts.

94. What must I consider when adding a new user field (=> user field was not previously used) in a migration without document splitting?

- If you want to fill the field for at least the migration of documents in phase 1 and save the field in the totals table, it must be available at coding block level (=> CI_COBL) as of the migration date, and a derivation logic must be implemented (by the customer).

- For the balance carryforward of G/L accounts not managed on an open item basis in phase 0, you can use the standard BAdI to subsequently add a new user field (with implementation by the customer).

- For open items in phase 0, there is no standard option (for example, BAdI or program) as of January 2008 to subsequently add the user field.

95. Can I perform a chart of accounts conversion when the new General Ledger is active? See also the next FAQ.

Yes, this is usually possible. SAP (=> System Landscape Optimization (SLO) department) provides the "Chart of Accounts Conversion" service. For more information about the chart of accounts conversion, see http://service.sap.com/slo.

96. Can I perform a chart of accounts conversion in the same fiscal year as the migration?

This is usually possible. However, you must make clear differentiations and several (general) points must be considered:
This concerns two independent projects. However, these projects may have dependencies and should therefore be reconciled with each other. Ensure that you keep this in mind when planning both projects. You must inform the relevant SAP contact person about the planned projects.
Regarding the sequence of both projects, you must also consider the following:

=> For migration scenarios 1 and 2: You can always perform the chart of accounts conversion before and after the productive migration - there are usually no problems in this regard.

=> For migration scenario 3 (=> with document splitting): You should perform the chart of accounts conversion before the migration.
Reason: During a chart of accounts conversion, several accounts are usually merged. In other words, there are usually fewer accounts after the chart of accounts conversion than before the conversion. If, for example, you merge three accounts (which are assigned three item categories in new General Ledger Customizing) into one account, then this account will also have only one item category. This may mean that some processes can no longer be displayed/posted/entered with the specified document splitting rules, and the system may generate an error during posting. As a result, you must adjust the document splitting rules accordingly (if possible).

The abovementioned changes and conversion tests are easier to perform in migration phase 1 (that is, before productive migration in the classic General Ledger) than at a later stage when the new General Ledger is active (after the migration).

See also Note 891144 for information about configuration changes after activating the new General Ledger.

=> For migration scenario 4: Again, the time is not important here. However, the accounts approach "concept" MUST be retained after the chart of accounts conversion.

This means: Accounts that mirror different accounting principles for an accounts approach. For example, even though account 14711 and account 94711 can be converted (by SLO) (for example, to accounts 11234 and 91234), they cannot be deleted or merged into one account (for example, account 4711).
Reason: If you do this, the system displays only one amount (and this amount is incorrect) when the new account (=> 4711) is valuated.
Example (=> chart of accounts conversion before migration):
Balance (international) account 14711:    200 Euro
Balance (local) account 94711:            300 Euro
=> Assuming the accounts are now merged into account 4711:
There is only one amount (=> 500 Euro), and it is not clear whether this is the local or the international approach.
Often an incorrect assumption (=> for chart of accounts conversion after migration): During the migration, the accounts are merged. For example, as explained above, accounts 14711 and 94711 are merged into one account 4711.

It is correct that this occurs in the migration by transfer postings, and you can then valuate this one account for different ledgers (=> different accounting principles). After this you can delete the original accounts (14711 and 94711), for example using the SLO service, because these accounts are no longer required. Even though the accounts are no longer required in the future, if account 4711 is valuated before the migration date, only one amount is displayed (and this amount is incorrect) - see above.

Therefore: Even after migration, the chart of accounts conversion must take into account the accounts approach logic/concept to ensure that data can be correctly evaluated before the migration date.

=> For migration scenario 5: The above executions for migration scenario 3 and 4 must be observed.

97. Migration into the new General Ledger and introduction of a shortened fiscal year at the same time. What must I consider?

If you introduce a shortened fiscal year, this changes the fiscal year end and may also affect the planned migration date (for example, before the shortened fiscal year is introduced, the fiscal year end is December 12; after the shortened fiscal year is introduced, the fiscal year end changes to September 30). You must take this into consideration when planning the migration to the new General Ledger. For more information about shortened fiscal years, see 672255.

98. How do the migration date and the date of the live migration (new G/L Go-Live) relate to each other?

The migration date must be the first day of a fiscal year.
Example and assumptions: You are using the FI fiscal year variant K4 (12 periods + 4 special periods and a calendar year = a fiscal year). This means the migration date is always January 1. It is still assumed that the current date is June 7, 2008.

Assuming that the migration will be implemented in 2009 (for example an April or May weekend), various configurations will already be required in 2008, including in the live system. For precise details on these configurations, see SAP Standard Training AC212.
In the migration cockpit (SAP tool for migrating FI data from the classic G/L to the new G/L - for more information, see the FAQ "What is a migration cockpit?" in this note), the migration date is still set for January 1, 2009.

As already explained, the actual live migration / go-live for the new G/L will be carried out in Spring 2009.

If it not possible to avoid shifting the go-live, make sure that the live migration of your data planned for January 1, 2009 is still migrated in 2009. It is not possible to shift the go-live to 2010 if the migration date has already been set for January 1, 2009. This would constitute a "cross-fiscal year migration".

However, if the given circumstances force a live migration in 2010, you will have to create a new project (migration package) with the migration date set for January 1, 2010 because cross-fiscal year migrations are not supported by SAP.

99. Are there any restrictions that I should bear in mind during a new G/L migration when using the Lease Accounting Engine (LAE)?

No, if you use the LAE with version 03/2008, there are no limitations when using it with a new G/L.
Important: However, if you use the complete the SAP Leasing Process with FI-CA, and the corresponding document summarization, the restrictions in this note still apply - see the FAQ "Is the new General Ledger compatible with FI-CA (FI # Contract Accounting)?" See also 893906.

100. What is an activation date?

Read Here for more SAP FICO Interview Questions and Answers.
___________________________________________________________________

Appendix: Questions that do not directly apply to a new G/L migration, but which may be of interest in a migration project, include: 

1. In ECC 5.0, which functions are not supported and not released for the new General Ledger?

For information, see 741821, section FI-GL-GL, Release with limitations, New General Ledger:
"The following functions are not supported for the new general ledger and are therefore not released:..."

2. Is the new General Ledger compatible with FI-CA (FI # Contract Accounting)?

This question is relevant for each Industry Solution that uses component FI-CA (Contract Accounting) as accounts receivable accounting (IS-U, IS-T, IS-M, IS-PS-CA, FS-CD) and the non-industry-specific contract accounting FI-CAX.

As far as possible, FI-CA uses the new General Ledger in ERP2005 in the same way it uses the classic General Ledger.  Furthermore, FI-CA supports the account assignment "Segment", which was introduced as a new standard account assignment in FI.

As a rule, the new General Ledger is not compatible with FI-CA if you intend to use document splitting in the new General Ledger.  You must check the compatibility in each case depending on the release and the active industry solution used.

In ERP2005, it is not possible to post to a ledger group in FI-CA. Therefore, if you have to implement different accounting principles in parallel, you must use parallel accounts to process valuation postings that were posted in FI-CA (not directly in the general ledger). In FI-CA, this primarily affects foreign currency valuation. In a future ERP release, FI-CA will support ledger groups and will allow ledger groups as an option in foreign currency valuation.

3. Is the new General Ledger Accounting compatible with IS-A (Industry Solution Automotive)?

See 927241.

4. Is the new General Ledger compatible with Financial Services SAP Leasing?

See 893906.

Is the new General Ledger compatible with Real Estate (RE)?
See 784567.

5. What must I consider in a distributed system landscape regarding the new General Ledger (ALE)?

• For basic information about the new General Ledger and ALE, see 114814.
• For further information, see 892103, 892366, 899254 and 897083.

6. Are there any restrictions when using transfer prices in the new G/L?

See the section 'Transfer prices' in  826357.

7. What is the relationship between the new General Ledger and Material Ledger?

You can use the Material Ledger in combination with the classic General Ledger and in combination with the new General Ledger.
It is not possible to replace the Material Ledger with the new General Ledger.

8. Is profit center consolidation available in the new General Ledger?

Profit Center Consolidation is also available when the new General Ledger is active.  For more information, see 852971 and 826357.

9. Which extractors are available to extract data from the new General Ledger to BI (Business Warehouse)?

In ECC 5.0 (=> SAP ERP 2004) and ECC 6.0 (=> SAP ERP 6.0), there is an extractor for extracting totals records from the new General Ledger to BI: 0FI_GL_10.

Important: As of Enhancement Pack 3 (=> EhP3) / Business Function FIN_GL_CI_1 (=> New General Ledger Accounting), you can also use the line item extractor 0FI_GL_14 (=> DataSource: BWBCT_DS_0FI_GL_14). This also allows you to extract single documents of the leading ledger for BI reporting.
You can also generate extractors for non-leading ledgers (=> transaction code FAGLBW03). The generated extractors are called 3FI_GL_XX_SI, where XX is the name of the ledger.

For further information, see (for example) the SAP Library under "General Ledger (New): Line Items of Leading Ledger" or the documentation for the FIN_GL_CI_1 Business Function (=> transaction code SFW5).

10. What do I have to consider if I use the new General Ledger and HR?

Check whether 911172 and 1006691 are relevant for you.

11. How must I configure Asset Accounting (FI-AA) so that subledgers (parallel ledgers) use the same account determination as the leading ledger?

All depreciation areas should use the same accounts as the leading depreciation area.  To ensure this, fill the field "Different Depreciation Area" in transaction OADB with the correct values.  This field defines the depreciation area for account determination.

Keep in mind that you must not enter different accounts for the derived depreciation area in transaction AO90 because transaction AO90 overrides the generic setting from transaction OADB.

12. Is it possible to assign the scenario FIN_SEGM (Segmentation) to a ledger if this ledger does not have the scenario FIN_PCA (Profit Center Update) assigned?

The use of segments has been officially released by SAP in combination with the usage of profit centers only. For more information, see also 1035140.

13. When I carry out an FI-AA posting why does the error message GU 444 (still) occur?

See 1094630 first.

In certain circumstances, the error message GU 444 can still occur in asset accounting. This happens when a ledger group assigned to a depreciation area contains exactly one ledger, and this ledger is not used for the company code currently being used. However, if there are ledger groups with more than one ledger, and one of these ledgers is not used in a company code, you can still make a posting.

Reason: If asset accounting permitted this configuration, values and line items would still occur in the relevant depreciation areas in FI-AA, but values would not be updated in the corresponding account / ledger. This means that the RAABST02 report would always show differences, even though there are none.

Solution:
- New customers / new implementation:  Distribute the company codes across different valuation plans
- Existing customers: All company codes of a valuation plan use the same ledger

Example:
1.
Ledger   Company Code
H1       1000
H1       2000
H2       1000

Ledger   Ledger Group   FI-AA Depreciation Area
H1       H1             01
H2       H2             60
=> Error message GU 444 is issued for company code 2000

2.
Ledger   Company Code
I1       1000
I1       2000
H1       1000
H1       2000
HT*      1000         *HT = Daily ledger

Ledger   Ledger Group   FI-AA Depreciation Area
I1       I1             01
H1       H1             60
HT       H1             60
=> Error message GU 444 is not issued for company code 2000 because postings are possible in ledger H1.