FI-GLX - Basic Functions
`
`The following Help Topics are available:
`
`Ma_sie.r_EJles
`
`For Help on Help, Press F1
`
`Version
`
`SAP-00004033
`
`

`
`Version
`Prepared for R/3 Release 2.2.
`September 94
`
`SAP-00004034
`
`

`
`Copyrights
`
`@1994 SAP AG. All rights reserved.
`Neither this documentation nor any part of it may be copied or reproduced in any form or by any
`means or translated into another language, without the prior consent of SAP AG.
`SAP AG makes no warranties or representations with respect to the content hereof and specifically
`disclaims any implied warranties of merchantability or fitness for any particular purpose. SAP AG
`assumes no responsibility for any errors that may appear in this document. The information
`contained in this document is subject to change without notice. SAP AG reserves the right to
`make any such changes without obligation to notify any person of such revision or changes. SAP
`AG makes no commitment to keep the information contained herein up to date.
`
`SAP-00004035
`
`

`
`Overview of FI-GLX
`
`This section contains the following topics:
`
`SAP-00004036
`
`

`
`What is Extended General Ledger?
`
`SAP’s integrated product line covers the entire commercial software needs of customers from a
`wide variety of industries. Within the integrated SAP software package, you can integrate nearly
`all aspects of your business.
`Each of the SAP products meets your reporting requirements using various reporting techniques.
`In some situations, you may require more information than is provided in an individual application.
`Example:
`You may want to combine or summarize information from many different application areas---at
`levels of detail not provided by an individual application. This information is available, but only if
`you access the systems that contain the information.
`The FI-GLX System is designed to provide summary information from multiple applications at a
`level of detail that you define. By using the variety of modules provided by FI-GLX, you can
`combine, summarize, allocate, and plan data that originate from other SAP and external systems.
`
`¢octs. recv.
`
`I
`
`Extended General Ledger ReportWriter
`
`I
`
`I Managernentl
`
`Legal I
`
`ConsolidationI
`
`Statistical
`reporting
`
`With FI-GLX, you can accumulate and report on information across the entire SAP System without
`compromising the high level of integration you have already achieved. The operating functions of
`the individual applications remain unchanged when you add the FI-GLX System.
`
`SAP-00004037
`
`

`
`The FI-GLX
`
`FI-GLX System Modules
`
`The FI-GLX System is organized into integrated, add-on functions, or modules.
`System contains the following modules:
`¯
`Integration Manager
`¯ Direct Input in FI-GLX
`¯ Rollups
`¯ Currency Translation
`¯ Boolean Logic Manager
`¯ Set Manager
`¯ Planning
`¯ Allocations
`¯ Balance carry forward
`¯ Report Writer
`¯ Validations/substitutions
`¯ Miscellaneous utilities
`
`SAP-00004038
`
`

`
`FI-GLX Integration with Other SAP Systems
`
`All SAP Systems operate under the philosophy that you only enter a business transaction once.
`Entered transaction data are then available real-time to all other SAP Systems.
`FI-GLX collects data at the original point of entry and validates the data immediately during entry.
`With this maximum integration, you do not need to run batch interfaces or reconcile data with
`other systems.
`
`Interface with Other R/3 Systems
`
`Most data that enter the FI-GLX System come from transactions occurring in many different places.
`A business transaction can enter the FI-GLX System via another SAP application, via direct input to
`the FI-GLX System, or via external systems.
`All data that enter the FI-GLX System are processed by the Integration Manager. Through
`user-defined selection, validation, and substitution conditions, the Integration Manager determines
`if and how data should be posted to the FI-GLX data bases.
`
`I a roI Iso
`
`encountin~l
`
`Invoicing
`
`I
`
`y
`
`AM
`Fixed
`assels
`
`Financial Systems
`
`IAcc0unts receivable Ipayable 1
`IIs’cIAccounts lac0unts
`
`Material
`Management
`
`/Cost
`
`verificati0n
`
`m
`
`management
`
`Accounting
`
`Activities I
`
`JCO-ABC
`JCO-JOB I
`
`Order I
`accountingl
`
`Example:
`¯ Data can be transmitted from Financial Systems (FI and AM), as well as from other SAP
`Systems such as Payroll (HR) and Invoicing (SD) (via the FI System).
`¯ The Cost Accounting modules (CO) transmit relevant data about Activities (CO-ABC,
`CO-CCA) and financially relevant data from Order Accounting (CO-JOB).
`¯ The Material Management System (MM) supplies information on inventory movements, as well
`as the results of invoice verification.
`
`SAP-00004039
`
`

`
`For information about how data enter the FI-GLX System, see ~a E.ntry.
`
`Shared Functionality with Consolidation
`
`The FI-GLX System interfaces with many other SAP Systems, but it has a unique relationship with
`SAP’s Consolidation System (FI-LC).
`Benefits of using the two systems together, include:
`¯ same data base type. The FI-GLX and FI-LC Systems both use an FI-GLX summary data
`base.
`shared functionality. The two systems share many of the same functions, processing
`techniques, and files.
`Example:
`The FI-GLX System uses the currency translation methods of the FI-LC System, while the FI-LC
`System can use the reporting techniques of the FI-GLX System.
`similar transaction structure. Business transactions of consolidation companies are easily
`identified by the FI-GLX System. FI-GLX automatically retains the subsidiary code connected
`to a business transaction so that you can use the transaction data in the FI-GLX System.
`Example:
`You can use the FI-LC data for reporting the sales of a partner subsidiary.
`flexible installation. During installation, you can combine the functions of the two systems
`according to your individual needs.
`Even if you are not responsible for preparing consolidated financial statements, the FI-LC System
`has many useful functions. Primarily, the FI-LC System is integral to the preparation of data in the
`Financial (FI) and Fixed Assets (AM) Systems. When you combine the FI-GLX and FI-LC
`Systems, you also benefit from the common design, shared functionality, and common techniques
`and utilities of both systems.
`
`SAP-00004040
`
`

`
`FI-GLX Data Structures
`
`The FI-GLX System is delivered with example data base structures that you can copy and then use
`to organize and set up your system. Before designing your system structure, you must determine
`which dimensions from all available dimensions you will use in your ledgers. (A dimension is a
`single field or column of a data base table.)
`
`DATA BASE STRUCTURES
`
`Object Table 1
`
`I
`
`,
`
`Con,or
`
`Object Table 2
`
`U Produot Number
`¯
`
`LEDGER I
`ACCOUNT / COST CENTER
`
`LEDGER 2
`COST CENTER / PLANT
`
`LEDGER 3
`PRODUCT/PRODUCT NOS.
`
`Example:
`In the above figure, 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
`Numbers. Because Ledgers 1 and 2 share the dimension Cost Center and all the dimensions
`used by the ledgers exist in one object table, one table structure can be used by the two ledgers
`(Object Table 1). Because dimensions Product and Product Number do not exist in Object Table
`1, Ledger 3 must use a different object table.
`Alter you have determined the structure of your ledger(s), you can define the structure of your data
`base tables. For information about ledger structures, see .Eb.G.L.)~..Sys:t#.m.8#.tu~.e.rs.
`This section contains the following topic:
`
`SAP-00004041
`
`

`
`FI-GLX Data Base Tables
`
`You define the dimensions for
`
`The FI-GLX System is delivered with example data base tables that can be copied and changed
`according to customer needs. You cannot activate and use the tables as they are delivered.
`Each data base table contains a user-defined data structure, which determines the dimensions
`(fields) of a data base table.
`Dimensions can be:
`¯ fixed dimensions: You cannot delete or change fixed dimensions in a data base table.
`Example:
`Client and Ledger are examples of fixed dimensions.
`¯ variable dimensions: You can create, change, and/or delete variable dimensions, as required
`during your system installation.
`Example:
`Cost Center and Account are examples of variable dimensions.
`Variable dimensions form the coding block of a data base table.
`a data base table using the R/3 Repository (Data Dictionary).
`Note
`The SAP-delivered data base tables are only suggested example structures. You cannot use
`these data base tables as delivered. Instead, you must copy the tables and make necessary
`changes according to your system requirements.
`Beginning with Release 2.1, FI-GLX is delivered with the following group of interdependent data
`base tables:
`an object table: Object tables are transparent data base tables that contain:
`¯
`fixed dimensions: you cannot change fixed dimensions. The dimensions Client and
`Company Code/Company are fixed dimensions in an object table.
`¯ variable dimensions: you can change these dimensions as required during your system
`installation. When you define summary and line item data bases, you define the receiver
`and sender dimensions for the variable dimensions in the object table.
`¯ object numbers: object numbers point to fixed fields (Object Number- Receiver, Object
`Number - Sender) contained within a summary and/or line item data base table.
`Examples of object tables delivered with FI-GLX are GLT001 (for local ledgers) and GLT002 (for
`global ledgers).
`a summary data base: The summary data base contains summarized transaction data across
`documents for business transactions that enter the FI-GLX System.
`Examples of summary data base tables delivered with FI-GLX are GLT01 (for local ledgers) and
`GLT02 (for global ledgers).
`an actual line item data base: The actual line item data base is an optional data base that
`stores detailed document lines for actual documents.
`Examples of actual line item data bases are GLS01 (for local ledgers) and GLS02 (for global
`ledgers).
`a planning line item data base: The planning line item data base is an optional data base
`that stores detailed document lines for plan documents that enter the FI-GLX System.
`Examples of planning line item data bases are GLP01 (for local ledgers) and GLP02 (for global
`
`SAP-00004042
`
`

`
`ledgers).
`The summary and line item data bases each contain:
`¯
`fixed dimensions: you cannot change fixed dimensions, by a customer. The dimensions
`Client, Ledger, Record Type, and Version are examples of fixed dimensions in a summary/line
`item data base tables.
`object numbers: object numbers determine how the data base table will be accessed from the
`object table. Object numbers are different for each summary and line item data base.
`variable dimensions: for each variable dimension in the object table (for which the
`summary/line item data base table is defined), you must define a receiver (R) field for the
`dimension; you can define a sender (S) field, if needed.
`Note
`In releases previous to 2.1, FI-GLX was delivered with summary and line-item data bases that
`contained both fixed and variable dimensions. Beginning with release 2.1, the summary and
`line-item data bases contain only fixed dimensions and the receiver and sender variable
`dimensions; definitions of variable dimensions are now contained in the object table of the
`summary/line item data base.
`For information about the different types of data bases, refer to the BA Implementation Guide
`(IMG).
`Your system has been delivered with two groups of interdependent tables: (1) for local ledgers:
`object table GLT001, summary table GLT01, line item tables GLS01 and GLP01; and (2) for global
`ledgers: object table GLT002, summary table GLT02, line item tables GLS02 and GLP02. These
`tables are only examples and must be copied to use them in your system.
`To copy and change a delivered table, you:
`
`1. Copy the existing table using the FI-GLX Customizing function (Tools--> Customizing->
`Configuration-> Accounting-> Financial accounting -> Extended G/L-> Basic data -> Table
`installation -> Copy table).
`2. Make the necessary changes in the R/3 Repository (Data Dictionary), using transaction SE11.
`3. Install the new table using the FI-GLX Customizing function (Tools-> Customizing->
`Configuration-> Accounting-> Financial accounting -> Extended G/L-> Basic data -> Table
`installation -> Update GLU1).
`You copy and change the delivered data base tables using the Customizing function. For
`information, see the FI-GLXImplementation Guide (IMG).
`Note
`Beginning with Release 2.2, tables GLT1 and GLT2 will no longer be delivered as active tables,
`and the interdependent tables (for local ledgers: GLT001, GLT01, GLS01, GLP01; for global
`ledgers: GLT002, GLT02, GLS02, GLP02) will be used in place of GLT1 and GLT2. If you are
`installing new tables in Release 2.1, it is recommended that you copy the interdependent tables.
`To copy these tables prior to Release 2.2, you must first activate the tables in table T800A using
`the Customizing function. For information, see the FI-GLXImplentation Guide (IMG).
`
`Coding Block
`
`One of the first tasks in setting up your FI-GLX System is to define the variable dimensions that
`your ledger(s) will use. Next you must determine your data base structure.
`Variable dimensions comprise the coding block of your ledger, and determine which dimensions will
`be stored in the key part (secondary key) of a data record. They also determine which variable
`
`SAP-00004043
`
`

`
`fields of the data record key can be filled when a document is posted to FI-GLX. Dimensions are
`defined in the R/3 Repository (Data Dictionary).
`Note
`When you set up your system, you should first determine the dimension combinations and ledger
`structures that you will use in your system. Efficient structure of your coding block (variable
`dimensions) will result in reduced amount of required data storage.
`Each data base table contains a structure of fixed and variable dimensions. Example data base
`structures are provided with your delivered system. During your system setup, you can copy these
`data structures and change the variable dimensions as required.
`
`Data Base Record Structure
`
`The secondary key of your data base structure determines your data base records structure and
`how data will be retrieved by the system. (The secondary key is the key of the summary and line
`item data bases.)
`FI-GLX data base records are split into two parts:
`¯ keypart: In this part of an FI-GLX data base record, the system stores your data based on the
`fixed and variable dimensions defined for the data base table where the data is stored.
`Example:
`If you define a ledger that uses the dimensions Account and Cost Center, these dimensions are
`stored in the key part of the data record. For each combination of accounts and cost centers,
`an entry exists in the data base table.
`¯ data part: In this part of an FI-GLX data record, the system stores the values (amounts and
`quantities) for each key part.
`Example:
`You can store data records for transaction, local/global, and group currency, and quantities and
`additional quantities for actual, plan, actual allocation, and planned allocation amounts.
`You cannot change the data dimensions used to store data amounts and quantities in the
`summary data base.
`Note
`The above description of the structure of a data base record is not a technical description. For
`technical information about data structures, refer to the FI-GLXImplementation Guide (IMG).
`
`Online Coding Block Definition
`
`You define the dimensions for a data base table in the R/3 Repository (Data Dictionary), which you
`can maintain with an online, menu-driven function.
`For each dimension that you use in the FI-GLX System, you define the attributes of the dimension
`and the FI-GLX data base table name that will use the dimension in the R/3 Repository (Data
`Dictionary). Examples of dimension attributes are the record type stored in the dimension, the
`dimension length, and the dimension description.
`Example:
`The variable dimensions Account, Cost Center, Product, Plant, and Source are defined for a group
`of interdependent data base tables (object/summary/line item tables).
`To define these dimensions for a group of interdependent data base tables, you would:
`1. Define the dimensions Account, Cost Center, Product, Plant, and Source in the R/3 Repository
`
`SAP-00004044
`
`

`
`.
`
`(Data Dictionary).
`If a dimension is used in other parts of the SAP System, you should use the same data element
`for the dimension.
`For information about using the R/3 Repository (Data Dictionary), refer to the BA
`Implementation Guide (I M G).
`Define the dimensions for each data base table that will contain the dimension in its data base
`structure.
`Note
`If you create new data base tables in your FI-GLX System, you must define dimensions for the
`table.
`For information about using the R/3 Repository (Data Dictionary), refer to the BA Implementation
`Guide (IMG).
`The maximum length of variable dimensions defined in the object data base table is 110 bytes.
`Note
`Before your system is productive and before ledgers have been posted to, you can define
`additional dimensions in the data base structure and delete unnecessary variable dimensions, but
`you cannot change fixed dimensions. If you change/create dimensions in the data base structure,
`you should review your current Customizing definitions (for example, review your field movements
`to ensure that deleted fields are not defined in a field movement).
`The data base structure is defined separately for each table installation and is not hard-coded in the
`FI-GLX System. For information about a data base structure, see the online definition of the data
`base using the Data Dictionary function.
`
`FI-GLX Summary Data Base
`
`The summary data base contains summarized transaction data across documents for business
`transactions that enter the FI-GLX System. Data is summarized for each period. Example
`summary data base structures are delivered with your system (GLT01 for local ledgers, GLT02 for
`global ledgers). These tables are only examples and must be copied to use them in your system.
`
`FI-GLX Line Item Data Bases
`
`Example line item data bases are also delivered with your FI-GLX System. Example line item data
`base structures are delivered for actual data (GLS01 for local ledgers, GLS02 for global ledgers)
`and for plan data (GLP01 for local ledgers, GLP02 for global ledgers). These tables are only
`examples and must be copied to use them in your system.
`Normally, most of the business transactions affecting the FI-GLX System will come from other SAP
`R/3 Systems (for example, transactions for material purchases or customer invoicing). Documents
`are stored in the source application data base where the documents are entered. You can also
`store these documents, along with the detailed transaction information, in an optional FI-GLX line
`item data base.
`You usually store data in an FI-GLX line item data base when:
`¯ you want to input data directly to the FI-GLX System, for example, when data come from an
`external system or when the data are only used by the FI-GLX System.
`¯ you want to store a document in an FI-GLX line item data base, in addition to the source
`application data base.
`¯ you want to create a detailed audit trail of document information that is posted to the FI-GLX
`System.
`
`SAP-00004045
`
`

`
`You can only display an underlying document of a summary record from the FI-GLX System if the
`document is stored in the FI-GLX line item data base. If the document you want to display is only
`summarized in a summary data base, you will not be able to view individual document information.
`With the added flexibility of storing documents in an FI-GLX line item data base, you can define
`when you need an audit trail in the FI-GLX System and when the audit trail can remain in the
`source system. By storing documents in an FI-GLX line item data base, you can also retrieve and
`review the documents in more detail from the FI-GLX System.
`With the FI-GLX Customizing transaction, you can define at which levels an FI-GLX line item data
`base should be updated:
`¯
`for an FI-GLX company
`¯
`fora ledger
`¯
`for a ledger/activity combination
`¯
`for an FI-GLX company/ledger combination
`¯
`for an activity/ledger/company combination
`¯
`for an activity
`If you set the line item update indicator in any one of the above places in the FI-GLX system, the
`line item data base will be updated; however, the line item data base will only be updated for the
`item(s) you flag.
`Example:
`If you set the line item indicator for a specific activity, such as RFBU, only documents with the
`activity will update the line item data base.
`One record per document line will be written to the line item data base for a ledger, regardless of
`how many times you set the line item update indicator in your system setup. For information about
`setting the line item update indicator, see your online FI-GLXImplementation Guide (IMG).
`
`SAP-00004046
`
`

`
`KFI-GLX System Setup
`
`Alter you have defined the fields that you want to use in your ledgers (table structure), you can
`begin defining the ledgers, FI-GLX companies, currencies, and accounting periods that you will use
`in your system.
`Note
`Before you can define the coding block (variable dimensions) of your GLX tables, you must
`determine the dimensions and field movements you will use in your ledgers.
`One of your first tasks before installing and setting up your FI-GLX System is to decide how you
`want to structure the system. This section explains the basic concepts for the structure of your
`FI-GLX System, for example, local and global ledger definition. For information about installing the
`FI-GLX System, refer to the FI-GLX Implementation Guide (IMG).
`This section contains the following topics:
`,EI:G LX.~.y.s.t.~ m..~.e.t~.e~.s
`,EI-G LX..~.y.s.t.e m..~.e.t.~.ar~i.e.s
`EI-GLX.~.y.st.em.~.e.t.up:..Quanti.t Le.s..arldAmo.un.t s
`E I-G.L X.~.y.s.t.e m.~.e.t, up.;.P...o.s.t ~ r]g P..e. r.i.o d s
`EI-G LX.~.y.st.e m.~.e.t.up;.EiLeJId Mo.v.eme~ts
`-
`
`-
`
`SAP-00004047
`
`

`
`FI-GLX System Setup: Ledgers
`
`FI-GLX data bases are sub-divided into separate logical units, or ledgers. A ledger is a collection
`of data in an FI-GLX data base.
`Example:
`You can create one ledger that contains cost center-related information and another ledger that
`contains product-related information.
`You can create ledgers according to:
`¯ time (for example, years, quarters, months, weeks, days)
`¯ dimensions or combinations of dimensions (for example, Account, Cost Center, and Product)
`¯
`fiscal requirements (for example, local ledgers, global ledgers)
`¯
`currency type (for example, transaction currency, local/global currency, group currency)
`¯ quantities and additional quantities (for example, with quantities/additional quantities or without
`quantities/additional quantities)
`¯ different group currencies
`Each ledger uses several dimensions that define a sub-set of the coding block of an object table.
`You can define your system so that you have one ledger for each data base table structure, and/or
`more than one ledger per table structure. After you have defined the maximum coding block in the
`R/3 Repository (Data Dictionary), you define which dimensions will be used by each ledger.
`
`, Ledger#1
`
`f’
`
`,~Ledger#2
`
`’ ~
`
` Ledger#3
`
`definitions
`
`J~Ledger ~J
`!
`
`Transaction
`Type
`IPr°du°t IPlantl ....I....
`I
`I
`I
`I
`
`JAccount JActivity I ....
`ITyp° I
`
`I ....
`I
`
`Transaction
`Type
`IAccountlActivity Center ISub-
`IProduct IPlant BusinesslTransaction
`I-rype
`I
`Igr°uPI
`I Area JType
`
`[~ Ledger#4
`
`[~.Total
`I*" Block
`I~ Coding
`
`The dimensions that can be used in a ledger are determined by the field grouping code assigned to
`
`SAP-00004048
`
`

`
`the ledger. The field grouping code contains the dimensions that are taken over from the source
`data base table into the FI-GLX data base table.
`Several ledgers can use the same dimensions defined in a data base table.
`
`Report 1
`
`"~ Report 2
`w,-
`
`Account
`
`Ledger 1
`
`. JReport 1
`
`Report3
`
`Example:
`In the above figure, the data base table contains the variable dimensions Account, Cost Center,
`Product, Plant, and Source.
`You want to create two reports:
`¯ Report 1 uses the dimensions Cost Center and Product.
`¯ Report 2 uses the dimensions Cost Center and Account.
`When you define the ledger for the reports, you could define one ledger that uses the dimensions
`Product, Account, and Cost Center. However, a more efficient use of the data base storage might
`be to define two ledgers:
`¯ Ledger 1, with the dimensions Cost Center and Product
`¯ Ledger 2, with the dimensions Cost Center and Account
`When the system selects and stores data records for Report 1 (dimensions Cost Center and
`Product), it only selects and stores data records for the two dimensions, instead of for all three
`dimensions (Product, Account, and Cost Center). You could also create a report (Report 3), which
`is a combination of Ledgers 1 and 2.
`The setup of your ledgers, as in the example, depends on a number of factors. For information
`about system setup, see your online FI-GLXImplementation Guide (IMG).
`Each ledger contains some or all of the dimensions defined in the data base table that the ledger
`uses. For any particular business transaction, one or more ledgers can be selected for posting.
`The structure you use for your ledger(s) depends on your specific reporting needs. When
`determining your ledger structure(s), you should remember that every combination of dimensions
`that a ledger uses results in a new data record in the data base.
`One large ledger that contains many of the dimensions of your data base table may serve the
`purpose of many smaller ledgers. But by using two smaller ledgers that contain specific dimension
`combinations, you can reduce the volume of data records in the data base. For information about
`summarization of data in ledgers, see FI-GLX Data Entr~..D.ata..S.y.mma.r!zatj.o.rl
`The FI-GLX System uses two types of ledgers:
`¯
`local ledgers
`¯ global ledgers
`
`SAP-00004049
`
`

`
`Note
`Your system is delivered with two example summary data bases: GLT01 and GLT02. These
`data bases are only examples and can only be copied and changed according to customer
`requirements.
`
`Local Ledgers
`
`You can use local ledgers to store data posted for SAP (local) company codes.
`Example:
`The SAP-delivered example data base table GLT01 is used for local ledgers.
`
`Global Ledgers
`
`You can use global ledgers to store data posted for:
`¯ FI-GLX (global) company codes, and/or
`¯ SAP (local) company codes that are assigned to FI-GLX company codes.
`Example:
`You can assign an SAP (local) company code to a local ledger. You can also assign the same
`SAP (local) company code to an FI-GLX (global) company code (which is assigned to a global
`ledger. When a document for the SAP (local) company code posts to the system, it posts to
`the local ledger and to the global ledger.
`The SAP-delivered example data base table GLT02 is used for global ledgers.
`
`Multiple Ledgers
`
`In the FI-GLX System you can summarize different kinds of business transactions into different
`ledgers, or have many business transactions update many different ledgers. You can also define if
`a ledger is mandatory for all business transactions.
`In the following figure, the same document posts to more than one ledger, but with different
`information.
`
`SAP-00004050
`
`

`
`LEDGER 1
`
`Account
`
`Cost Center
`Article
`Number
`
`LEDGER2
`
`DOCUMENT
`
`Posting Key
`
`Account
`
`Amount
`
`cFuC reign
`rrenoy
`Amounf
`Personnel
`Number
`Fi×edAsset
`Number
`Order
`Number
`Article
`Number
`Project
`Number
`Affiliate
`Number
`
`Cost Center
`
`When you define a ledger, you assign one or more companies to the ledger. When a transaction
`is entered for a company code, the system posts the transaction to the assigned ledgers.
`You can also create multiple ledgers according to your financial needs.
`You do this by specifying
`which dimensions the ledger should use.
`You may need several ledgers if you:
`¯
`report in more than one group currency
`¯ using different fiscal year variants, simultaneously process different fiscal calendars
`¯ use different levels of detail in your FI-GLX System and/or your FI System
`¯ using different activities for a ledger, simultaneously process different types of data (for
`example, specific activities are assigned to a ledger; other activities are not assigned)
`
`Ledger Definition
`
`For each ledger, you define:
`¯ Dimensions to be used by the ledger (as determined by the field movements defined for the
`ledger and the data base used to define the ledger)
`
`SAP-00004051
`
`

`
`¯ Ledger master file information
`¯ Local/global companies assigned to a ledger
`¯ Activities assigned to a ledger (for a company or for all companies)
`¯ Ledger selection criteria
`¯ Currency for the ledger
`¯ Fiscal calendar for the ledger/company combination (the fiscal calendar does not have to be the
`same as the SAP company assigned to the FI-GLX company)
`
`Ledger Selection
`
`The FI-GLX ledger selection facilities allow you to define the exact conditions under which a ledger
`will be selected for posting. The FI-GLX Integration Manager uses these ledger selection
`conditions to determine which ledger should be selected for posting.
`Each business transaction is posted to the FI-GLX data bases according to user-defined rules.
`Example:
`You may define a ledger to be selected for posting when:
`¯ a particular group of accounts are part of the business transaction
`¯ a particular group of products are involved in a business transaction
`¯ a particular group of transaction types are posted
`Ledger selection conditions can be simple or complex. Any field value or field value combinations
`contained in the business transaction can be used as part of the rule.
`For information about defining ledgers, see your online FI-GLXImplementation Guide (IMG).
`
`Parallel Posting of Ledgers
`
`You can define which business transactions and dimensions flow into a ledger, and you can specify
`if a ledger is mandatory for a business transaction. You can also summarize different kinds of
`business transactions into a ledger, or post one business transaction to many different ledgers.
`If a ledger selection condition is met for more than one ledger for one business transaction, the
`business transaction will be posted to more than one ledger.
`
`SAP-00004052
`
`

`
`FI-GLX System Setup: Companies
`
`A company code is normally defined as a balanced set of legal books. In certain environments, a
`company could be a subset or division of a legal entity.
`Note
`For statistical ledgers, the requirement of a balanced set of books is not mandatory.
`The FI-GLX System uses two types of company codes:
`¯ SAP (local) company codes
`¯ FI-GLX (global) company codes
`
`SAP (Local) Company Codes
`
`These four-digit company codes are defined in the FI System. You can set up your system so that
`an SAP (local) company code directly updates a local ledger, or you can assign an SAP (local)
`company code to an FI-GLX (global) company code so that the SAP (local) company code updates
`a global ledger.
`For information about defining SAP (local) company codes, see the FI Implementation Guide (IMG).
`
`FI-GLX (Global) Company Codes
`
`These six-digit company codes are defined in the FI-GLX System. When setting up a FI-GLX
`company in the FI-GLX System, you:
`1. Define the FI-GLX companies that are to be included in your FI-GLX System, using a six-digit
`code.
`2. Assign an SAP four-digit company code to the FI-GLX company code, if desired.
`3. Assign the FI-GLX company to your global ledger.
`For information about defining FI-GLX companies, see your online FI-GLX Implementation
`Guide (IMG).
`Because the FI-GLX System uses global company codes, you can combine local company codes
`within one global company code.
`Example:
`You define five FI local company codes, which are subsidiaries of a parent company. You can
`then define an FI-GLX global company code, which combines the five FI local company codes into
`one company. If you assign the FI local company codes to a local ledger, you can report on the
`subsidiaries individually; if you assign the FI-GLX global company code to a global ledger, you can
`report on the combination of subsidiaries within the parent company.
`
`Multiple Companies
`
`Because an SAP installation may operate as a service bureau for many clients or corporations, the
`SAP System uses a multiple company concept.
`The six-digit FI-GLX company code is a subdivision within a client and is usually defined as a
`balancing set of books. You can maintain any number of companies within an FI-GLX client.
`Normally, the company codes in other SAP applications are transferred into FI-GLX on a
`one-to-one basis---for each SAP company code there can be an FI-GLX company. If no data have
`been posted in the system, it is possible to reorganize and combine SAP company codes within an
`FI-GLX company.
`
`SAP-00004053
`
`

`
`FI-GLX System Setup: Quantities and Amounts
`
`¯
`
`It is possible to store three currency amou