Considerations for running General Ledger on multiple application servers

If you process transactions for the same general ledger company on more than one application server, then you will have additional considerations for setup and processing. For example, each business unit in your organization might run a complete set of applications on a different application server and send just the account balances to the corporate headquarters application server for reporting. To do this, be sure to include these procedures in your General Ledger setup and periodic processing:

Duplicate the General Ledger setup information from the target application server to each source application server. See Lawson Administration: Server Setup and Maintenance.
Periodically transfer summarized period balance data or summarized transaction data from each source application server to the target application server. See Transferring balances and transactions from other application servers and Interfacing data into General Ledger.

Example

This example shows a sample processing scenario involving three application servers, with the same two General Ledger companies processing transactions on each application server. In this scenario, you must install the full General Ledger application on each application server. To consolidate company data, you must copy summarized balance or transaction data from the source application servers to the target application server.

Illustration: running General Ledger on three application servers

Considerations for transferring data

If you process transactions for the same general ledger company on more than one application server, then you can transfer data from one application server to another to consolidate financial information for the company. You can transfer:

period balance data, which creates summarized balance information for each posting account for a fiscal year
summarized transaction data, which creates summarized balance information for each posting account for each period of a fiscal year

balances from one or more general ledger companies to a designated consolidation company, which consolidates financial information for an organization


If you want to	Files unloaded from the source application server	Files updated on the target application server
Transfer company period balances	Period balance data from the General Ledger Consolidation (GLCONSOL (for UNIX/Windows) DBGLGCN (for IBMi)) file	General Ledger Amounts (GLAMOUNTS (for UNIX/Windows) DBGLGAM (for IBMi)) General Ledger Units (GLUNITS (for UNIX/Windows) DBGLGLU (for IBMi)) Currency Amount (CUAMOUNT (for UNIX/Windows) DBGLCAM (for IBMi)) General Ledger Consolidation (GLCONSOL (for UNIX/Windows) DBGLGCN (for IBMi))
Transfer transaction data	Transaction data from the Currency Amounts (CUAMOUNT (for UNIX/Windows) DBGLCAM (for IBMi)) file, General Ledger Units (GLUNITS (for UNIX/Windows) DBGLGLU (for IBMi)) file, or both	General Ledger Transaction (GLTRANS (for UNIX/Windows) DBGLGLT (for IBMi)) Note: You must then post the transaction data to update the General Ledger Amounts (GLAMOUNTS (for UNIX/Windows) DBGLGAM (for IBMi)), General Ledger Units (GLUNITS (for UNIX/Windows) DBGLGLU (for IBMi)), General Ledger Consolidation (GLCONSOL (for UNIX/Windows) DBGLGCN (for IBMi)), and Currency Amounts (CUAMOUNT (for UNIX/Windows) DBGLCAM (for IBMi)) files on the target application server.

See Transferring balances and transactions from other application servers.

If your subsystems and the General Ledger application run on separate application servers or use different databases, then you will need to transfer subsystem transactions to the General Ledger application. See Defining a Remote Site and Transferring remote site subsystem transactions.