Overview: Configuring and Using the FI-SL System 

This section explains the basic steps for configuring and using your FI-SL System. For more detailed information about system configuration, see the Implementation Guide (IMG) for Special Purpose Ledger .

  1. Designing your FI-SL system structure
  2. Before you install and set up your FI-SL System, you must carefully design your system structure. It is very important that you take time to design your system and data structures. A well-organized system structure leads to efficient running of your production system and improves system performance.

    Depending on your reporting requirements, you must determine which dimensions and field movements you want to use in your ledgers. (A dimension represents specific criteria in business processes. Technically, a dimension is a single field or column of a database table.)

     

     

    In the above graphic, Ledger 1 uses the dimensions "Account" and "Cost Center"; Ledger 2 uses the dimensions "Cost Center" and "Plant"; and Ledger 3 uses the dimensions "Product" and "Product Number". Since Ledgers 1 and 2 share the dimension "Cost Center" and all the dimensions used by the ledgers are defined in one table group, both ledgers can use one table structure (Table Group 1). Since the dimensions "Product" and "Product Number" do not exist in Table Group 1, Ledger 3 must use a different table group.

  3. Creating your FI-SL database tables
  4. Once you have designed your FI-SL system structure, you can create your database tables and specify which dimensions you want to include in your tables.

    FI-SL uses the following table types:

    · Object tables

    (for receiver/sender and transaction attributes)

    · Summary tables

    · Actual line item tables

    · Plan line item tables

    For more information about these table types, see FI-SL Database Tables.

    You use the Define Table Group function to define your database tables and store them in the ABAP Dictionary. A table group is a group of interdependent tables (object tables, summary tables, actual and plan line item tables).

    For more information about creating a table group, see the Define Table Group activity in the Special Purpose Ledger Implementation Guide (IMG).

    You can also create a rollup actual line item table and a rollup plan line item table, if, for example, you want to drill down from the rollup summary data to the original data in a Report Writer report.

    It is not currently possible to automatically install these tables using the Define Table Group function. If you want to use a rollup table, you must copy the standard tables delivered with your system (GLREFU: Rollup actual line item table and GLREFV: Rollup plan line item table) using the Copy table function in Customizing and modify them according to your requirements.

    For more information, see the Copy Table activity in the Implementation Guide (IMG) for Special Purpose Ledger.

    When you create your database tables, you must decide among other things the following:

    · Whether you require a local table (for a company code) or a global table (for a global company).

    · Which dimensions you want to include in the object/partner object table (for example, account, cost center, business area, and so on) and which of these dimensions you also require as partner dimensions (sender/receiver relationship).

    · Whether you require a second object table for transaction attributes.

    · Whether you want to include additional dimensions in the data part of the summary table. These dimensions are known as derived dimensions because they must be uniquely derivable from the other dimensions in a specific summary record.

    · Whether you want to include additional dimensions in your actual line item table. These dimensions are only used in document display (or in line item reporting).

    · Which currencies and quantities you want to use in your database tables

    · How many periods you require in your summary records

    · Which database indices you want to define for your FI-SL tables

    See also:

    Database Definition and Installation

  5. Installing your FI-SL database tables
  6. Once you have defined, saved, and activated your table group, you can install your database tables directly using the Table Group function.

    For more information, see the Define Table Group activity in the Implementation Guide (IMG) for Special Purpose Ledger.

    See also:

    Database Definition and Installation

  7. Creating your FI-SL master data
  8. After you have defined the dimensions that you want to use in your ledgers (table structure), you can define the master data (special purpose ledgers, companies, activities, and field movements) that you want to use in your system (see the following graphic).

     

    Special purpose ledgers: When you create your special purpose ledgers, you define, among other things, the ledger master data (such as the currencies and quantities the ledger should use, whether the ledger is open for posting, and whether the ledger can be used as a rollup ledger). You must also assign a company code or global company to your ledger so that data can be posted to the ledger. You then define which activities can update the ledger (company code/ledger/activity or global company/ledger/activity assignment). If you want to define additional criteria for posting data to your ledger, you can enter ledger selection conditions.

    Company codes and global companies: You can use company codes and global companies in your FI-SL system. Company codes are defined in the FI System and are the most commonly used companies in the FI-SL System. You can set up your system so that a company code directly updates a local ledger (ledger/company code assignment). Global companies usually group together one or more company codes. You can assign a company code to a global company so that the company code updates a global ledger (ledger/global company assignment) and a local ledger.

    Activities: The data entered in other SAP application areas or external systems is transferred into the FI-SL System using an activity. You must assign activities to your ledgers so that data can be updated in these ledgers.

    Field movements: You can create field movements to define which dimensions are filled within the FI-SL System. Field movements determine which dimensions from other SAP applications are transferred to the dimensions in the FI-SL System.

    For more information about creating master data, see the activities under Master Data in the Implementation Guide (IMG) for Special Purpose Ledger.

    You can also define your master data using the Graphic navigation function, which allows you to graphically display relationships between company codes, global companies, ledgers, and activities. If required, you can also branch to the assignment to change it. For more information about using the Graphic navigation function, see the Use Graphic Navigation activity in the Implementation Guide (IMG) for Special Purpose Ledger.

    See also:

    Master Data

  9. Defining additional requirements for working with your system
  10. After you have created the master data that you want to use in your system, you have to maintain additional system settings (such as posting periods and versions) required for working in your productive system.

    You can also define your own validations and substitutions for your system to check and/or substitute values and combinations of values as they are being entered in your system. Since validation and substitution occur before data is posted, only valid information enters the FI-SL System.

    For more information, see the Special Purpose Ledger Implementation Guide (IMG).

    See also:

    Additional FI-SL System Requirements

  11. Working with your FI-SL System

After you have completed the above steps, you can work in your FI-SL System, using the available functions to meet your specific business requirements.