Using FI-SL on Distributed Systems 

Use

Using Application Link Enabling (ALE) and IDoc, you can transfer FI-SL ledger data across separate SAP systems. Using an export rollup, you can distribute ledger data from a local system to a central system.

Advantages of using FI-SL on distributed systems include:

The FI-SL database table that you distribute must have the same name and the same basic structure in all systems. However, you can define the table structure in the central system so that it contains fewer fields than in the local systems, because the central system may not need to store all detailed information. Nevertheless, table definitions should not be too different.

Also, the Customizing settings for the ledgers and local or global companies that are to be distributed must be identical to ensure data consistency.

Procedure

To distribute ledger data from a local system to a central system, you:

  1. Define a distribution model.

    2. The distribution model determines to which logical system (central system) the ledger data is to be distributed. You define the logical system either at ledger level or at ledger-local company/ledger -global company level. Once the logical system is defined, all local systems are informed that this is the logical system to which they must send their data.

    You define a distribution model in ALE Customizing (Cross-Application Components ® Distribution (ALE) ® Distribution customer model).

  2. Define an error workflow in the central system.

    3. The error workflow is used to detect and process any errors that occur when the FI-SL data is transferred to the central system.

    You define workflows using the Make basic settings for Workflow step in ALE Customizing (Cross-Application Components ® Distribution (ALE) ® Basic configuration).

  3. Update the field assignment table EDIMAP in the central system.

    4. The EDIMAP table must be updated in order to export data from a local system to a central system. This table determines the assignment of the field(s) in the FI-SL database table to the field(s) in the data transfer structure (IDoc field).

    You update the EDIMAP table using the Update Assignment Table EDIMAP step in FI-SL Customizing (Financial Accounting ® Special Purpose Ledger ® Tools ® Distribution (ALE)).

  4. Generate the export and import programs.

    5. The export and import programs must be generated in both the central system and all local systems.

    You generate these programs using the Generate Import/Export Programs step in FI-SL Customizing (Financial Accounting ® Special Purpose Ledger ® Tools ® Distribution (ALE)).

  5. Define an export ledger in the local system(s).

    6. If the data of a FI-SL ledger is to be sent to a central system, you must assign an export ledger to the FI-SL ledger.

    The export ledger stores the balances of all previous data transfers. If you export data more than once within one period, only the difference amounts from the last data transfer are sent to the central system.

    You define export ledgers using the Maintain Ledgers step in FI-SL Customizing (Financial Accounting ® Special Purpose Ledger ® Basic Settings ® Master Data).

  6. Create an export rollup in the local system(s).

    7. When you create the export rollup, you determine how data should be transferred from the local system to the central system. You can transfer data on a one-to-one basis or summarize data using a user-defined field movement.

    For more information, see Creating a Rollup .

  7. Execute the export rollup in the local system(s).

When you execute the rollup, the data is posted to the central system, which is defined in the distribution model, according to the criteria you have defined in the export rollup. You can execute the export rollup as often as you want within a period, since only difference amounts from the last data transfer are exported. The export ledger stores all data amounts that have been transferred.

For more information, see Executing a Rollup .