New General Ledger

The general ledger in SAP R/3 is highly heterogeneous. In SAP R/3, customers have to implement several SAP components in order to fulfill international and industry-specific accounting requirements. To ease this problem, SAP has created a new, flexible general ledger solution in SAP ERP.

New G/L merges the classic general ledger with profit center accounting, special ledgers (including cost-of sales ledger), and the consolidation-staging ledger.


To make the settings and use the new General Ledger Accounting, one need to activate it.
To do this: SPRO--> Financial Accounting--> Financial Accounting Global Settings --> Activate new General Ledger Accounting  (Or T code is FAGL_ACTIVATION).


Activating General Ledger will have the following effects on SAP screen and system. 
- General Ledger customization will appear in the SAP reference IMG screen, 
  It will be under the settings Financial Accounting (new)-->Financial Accounting Global settings (new) and General 
  Ledger Accounting (new)- General Ledger Accounting functions appears in the SAP easy access menu under Accounting --> Financial   Accounting --> General Ledger


Activating new General Ledger will also activate the tables for the new GL.


FAGLFLEXT-Totals data table


FAGLFFLEXP-Plan line data table 


FAGLFEXA-Actual line data table


FAGL_SPLINFO_FAGL_SPLINFO_VAL-splitting data table

SAP Implementation guide

6 phases of Implementation SAP

1)      Preparationà landscape information/ preparation (server info. Cost, how many ppl going to use it etc)

àTeam size: two teams implementation team and core team

(Project managers and steering committee from implementation team and core team together called PMO: Project Management Organization)

àAs is study: study of current situation, processes, legacy system etc. This is done by core team.

àAs is flow chart (tools are Visio, arise etc)

àGather all the reports

àStudy legacy system

àInformation on drawing (handled by Document Management System DMO, also by PP)

àGather information on interfaces-must have, need to have, nice to have

àDocument As Is

àSign off

2)      Business Blueprint

(Requirement analyze phase)

àGather requirement for legacy

àTo be

àGAP analysis (difference between as is and to be)

àTo be process flow

àList of interfaces to be finalized (must have done now and need to have will be post go live)

àList of reports

àRICEFW objects (Reports, Interfaces, Conversion, Enhancements, Forms and Workflow)- These are customize reports.

àFunctional specification- for all RICEFW objects

àTechnical specification

àSign off on docs above

àTest scripts

àTest cases

àTest scenario-Simple, complicated and complex

àBusiness process procedure (ASAP)

àUsing PowerPoint all functional consultant give a demo

àUsing PowerPoint presentation give demo only for your module (workshop)

àUsing 800 client give a SAP demo-800 is IDES server (IDES never have customer information)

àQ&A database (to be answered by core team)

àOrganization structure

àCollision list (material, vendor and customer, unit of measure)

àTo be documentation

àTo be sign off (consultant and project manager)

3)      Realization

àCarry out baseline testing in 800 clients

àYou are provided with a new client 300

àCarry out basis configuration (back end) - done by consultant

àCopy of configuration sent to client 300

àTesting carried out in 200-300 is a golden client; no master data, just configuration so we cant do testing in 300 (testing by core team)

àYou are provided with a new client 400 (basic)

àCarry out additional configuration in 400 (200+400)

àCarry out configuration in 300

àTesting carried out in 400 (core team)

àYou are provided with a new client 600 (sandbox)

àCarry out additional configuration in 600 (600+200+400)

àCopy all configurations to client 300

àTesting carried out in 600

àUsing client 600

àUpload master data across all modules (sample load of few parts or entire data end as per client wants)

àAll RICEFW objects must be ready tested by you and ready for testing by business

àCarry out integration testing 1 in client 600 (across all modules)-simple scenario (10) and complicated scenario (10)

àIntegration testing 2in 600 (across all modules, group test), complex scenario (5)

àTraining needs and documents, identify roles and responsibility (based on SOX compliance)

àTraining client 610 produced by basis

4)      Pre go live phase

àSuggest business to clean up master data in legacy, all configurations from golden client will be moved to 910, 960 and 999

àMaster data templates provided by business- if we upload just sample data before then we need to provide templates here otherwise templates provided when entire data uploaded in previous phase)

àUpload master data there are 2 tools: LSMW and interfaces (interfaces like Biz Talk, tibco, XI etc)

àTraining session carried out

àYou are provided with a new client 910 (Development server)

àMaster data upload into 910

àSometimes Business carried out integration testing 3

àYou are provided with a new client 960 (quality and integration test server)

àMaster data upload into 960

àYou are provided with a new client 999 (production server)

àMaster data upload to 999

àCutover activities (in client 999); when to stop legacy, when to start SAP, when to run MRP, controlled start up

5)      Post production support:

àConfiguration change

àMaster data changes

àTransaction level changes

àSome more training

àMaster data to be plugged

àMissing authorization

àComplete all documentation work (For both configuration and end use depend upon client)