How To Fix FAGL_MIG139 - New GL Acctg + FI-SL srce ledger use diff. doc. splitting methods: &1 &2


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FAGL_MIG - Migration to New General Ledger Accounting

  • Message number: 139

  • Message text: New GL Acctg + FI-SL srce ledger use diff. doc. splitting methods: &1 &2

  • Show details Hide details
  • What causes this issue?

    In Customizing for new General Ledger Accounting, you have selected a
    different document splitting method to the method used in the selected
    source ledger in Special Purpose Ledger (FI-SL).

    System Response

    When you use an FI-SL split ledger as the source ledger in a migration
    from the classic solution to new General Ledger Accounting, the FI-SL
    split ledger that you select must meet certain prerequisites (see SAP
    Notes 1163997 and 1600481). In the case of a migration to new General
    Ledger Accounting using scenarios 3 and 5, document splitting for the
    FI-SL split ledger must be activated with the same splitting method, for
    example.

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    In certain constellations, the FI-SL split ledger might use a different
    document splitting method to the one assigned in new General Ledger
    Accounting. This could be due to the fact that new General Ledger
    Accounting offers additional functions (such as the assignment of
    follow-up costs in the entry view). The splitting method selected for
    new General Ledger Accounting needs to meet the new requirements.
    The document splitting method contains rules that determine how the
    individual item types are handled. If different document splitting
    methods are used in the source ledger (FI-SL split ledger) and target
    ledger (NewGL ledger), system behavior before and after the migration
    date is different. This needs to be taken into consideration for the
    migration of the Phase 1 documents.
    Example:
    The FI-SL split ledger uses document splitting method 0000000002. In new
    General Ledger Accounting, document splitting method 0000000012 is
    assigned.
    In document splitting method 0000000012, it is assumed that the
    follow-up costs automatically contain account assignments in the entry
    view. Consequently, these line items are used as the basis for splitting
    other item types. Document splitting method 0000000002 does not contain
    item types for follow-up costs in the splitting basis because it was
    generally not possible to split follow-up costs in the entry view in the
    FI-SL split ledger.
    It is only possible to split follow-up costs in the entry view after
    activating new General Ledger Accounting, that is, during the activation
    phase of the migration and not as of the migration date. In general, the
    new splitting method 0000000012 is already used for migrating documents
    from the current year. For documents from phase 1 (posted between the
    migration date and the activation date), the FI-SL split ledger view can
    differ from the view in new General Ledger Accounting. In each customer
    project, the decision needs to be made explicitly as to whether such a
    difference is desired or whether it needs to be prevented by making
    alternative settings in the migration.
    In phase 1, cause-based account assignments are not yet derived
    automatically in the entry view. It may be necessary to set up a default
    account assignment for the time of the migration if one does not already
    exist. If the new splitting method 0000000012 is used in the migration
    (Phase 1), items for the follow-up costs with a default account
    assignment are used as the base items for other items (such as bank
    items). This can produce a different splitting result.
    If differences between the FI-SL split ledger and the migrated general
    ledger view of the phase 1 documents needs to be avoided, the
    "Alternative Document Splitting Method" can be used for these
    documents. The splitting method of the FI-SL split ledger can be used as
    the alternative document splitting method. This causes the documents
    from phase 1 to be posted in new General Ledger Accounting using the
    method assigned as the alternative document splitting method.

    How to fix this error?

    If an FI-SL split ledger with the differing document splitting method
    still needs to be assigned as the source ledger, error message FAGL_MIG
    139 can be changed from an error message into a warning message in
    transaction OBA5. By changing the message type, you confirm that you
    have understood the situation described here and accept the consequences
    that can result from it.

    Procedure for System Administrators


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message FAGL_MIG139 - New GL Acctg + FI-SL srce ledger use diff. doc. splitting methods: &1 &2 ?

    The SAP error message FAGL_MIG139 indicates that there is a discrepancy in the document splitting methods used between the New General Ledger (New GL) accounting and the Special Ledger (FI-SL) source ledger. This error typically arises during the migration process to the New GL or when trying to perform document splitting in a scenario where the configurations do not align.

    Cause:

    The error occurs when:

    1. The document splitting methods configured for the New GL and the FI-SL source ledger are different.
    2. The system expects both ledgers to use the same document splitting method to ensure consistency in financial reporting and data integrity.

    Solution:

    To resolve this error, you need to ensure that the document splitting methods for both the New GL and the FI-SL source ledger are aligned. Here are the steps to do this:

    1. Check Document Splitting Configuration:

      • Go to the configuration settings for document splitting in the SAP system.
      • Use transaction code OBCE to access the document splitting settings.
      • Verify the splitting method assigned to the New GL and the FI-SL source ledger.
    2. Align the Splitting Methods:

      • If the methods are different, you will need to either change the document splitting method for one of the ledgers to match the other or adjust the configuration to ensure they are compatible.
      • Make sure that the splitting characteristics and rules are consistent across both ledgers.
    3. Testing:

      • After making the necessary changes, perform a test transaction to ensure that the error no longer occurs and that document splitting works as expected.
    4. Consult Documentation:

      • Review SAP documentation or notes related to document splitting and New GL migration for any additional guidance or best practices.
    5. Seek Expert Help:

      • If you are unsure about making these changes or if the issue persists, consider consulting with an SAP FI consultant or your internal SAP support team for further assistance.

    Related Information:

    • Transaction Codes:
      • OBCE: Document Splitting Configuration
      • OBY6: New GL Configuration
    • SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional insights.
    • Migration Process: If you are in the process of migrating to New GL, ensure that all related configurations are reviewed and aligned before proceeding with the migration.

    By following these steps, you should be able to resolve the FAGL_MIG139 error and ensure that your document splitting methods are consistent across the New GL and FI-SL ledgers.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author