Comparative Analysis between New GL and Classic GL New GL and Classic GL are two ways to implement General Ledger functionality in SAP ECC5 and ECC6. New GL provides lot of benefits over classic GL. The New GL benefits

- Provide an extension to the existing functionality in classic GL, or

- Provide new functionality compared to classic GL, or

- Provide a technologically superior way to perform a functionality in Classic GL

It is imperative to understand the differences between Classic and New GL to be able to understand which solution addresses the business requirements better. I am providing a comparative analysis of the basic differences between Classic and New GL.

(1) Extended Data Structure provides flexibility

SAP has consolidated the multiple totals table (GLT0, GLPCT, etc) in classic GL into a single FAGLFLEXT Totals table with New GL. One Summary Table provides flexibility and faster response time for reporting. FAGLFLEXT can also be enhanced by adding customer defined fields.

(2) Segment Reporting to ensure Statutory Requirements

IAS accounting standards define the statutory requirements for segment reporting. New GL has document splitting functionality that enables segment reporting. Standard Segment Reporting functionality is not available in Classic GL.

(3) Real Time Integration between FI and CO

Classic GL has the period-close reconciliation ledger functionality to synchronize FI and CO for cost transfers across functional area, business area and company code originating in CO. New GL has a real-time integration between FI and CO that happens with each transaction originating in CO instead of a summary posting done by reconciliation ledger during period-close.

(4) Parallel Accounting

New GL provides Non-leading ledgers for parallel accounting like IFRS and GAAP. Parallel accounting can also be implemented using Account based approach which is also available in classic GL.

(5) Reduce TCO by Faster Period Close Activities

Faster Period Close is possible with New GL as,

(a) Reconciliation Ledger is not required

(b) Balance sheet Adjustments are not required

(c) Profit and Loss Adjustment are not required

(d) Activities related to Special Purpose Ledger are not required

(e) Depreciation posting is online instead of a batch session

(6) Flexible Drill-down Reporting in New GL

New GL has advanced drill-down capabilities by segment and other characteristics.

Advanstages in new general ledger are:

1. The new General Ledger in mySAP ERP 2004 has the following advantages over the classic General Ledger in R/3 Enterprise:a) In the new General Ledger, you can display the parallel accounting using parallel accounts (as in R/3) or using parallel ledgers. The FI standard functions and reports are available for all parallel ledgers.b) The ‘Segment’ entity and the relevant reporting that are required for segment reporting according to IAS and U.S. GAAP are available in the new General Ledger.c) In addition, you can enhance the new General Ledger flexibly, that is, you can enter user-defined fields and update the relevant totals. Many standard reports can evaluate the information from the user-defined fields.d) When you use the new ‘Document Splitting’ function (online split), you can create financial statements at company code level and, if required, for entities, such as the segment. For each document, the system then creates a zero balance for the relevant entity, for example, for the segment.e) As a result, you no longer have to carry out time-consuming reconciliation tasks between FI and CO for the end of period since cross-entity processes are transferred in real-time to the new General Ledger in Controlling. Furthermore, you can, for example, navigate from the financial statements report results or the profit and loss statement report results to the relevant CO report.f) The new General Ledger uses the same interfaces as the General Ledger in R/3. As a result, users do not require any additional training.g) Due to the new ‘multi-dimensional’ aspect in the General Ledger, all data that is relevant for the General Ledger is stored in one environment. As a result, reconciliation tasks, for example, between the general ledger and Profit Center Accounting or the consolidation staging ledger, and processing steps that have to be carried out repeatedly in the individual applications (for example, balance carryforward) are no longer required. When you use the new General Ledger, you may not have to use the special ledger anymore.

2. Default deliveryIn new installations, the new General Ledger Accounting is activated by default in mySAP ERP. We do not recommend that new customers use the classic general ledger accounting since using the classic general ledger accounting requires additional migrations at a later stage. As a result, new customers require explicit authorization from SAP to use the classic general ledger accounting. If you want to use the classic general ledger accounting. create and send a CSS message to SAP before you start using the system.When you upgrade an R/3 system to mySAP ERP, the classic General Ledger remains active at first. If you want to convert your system to the new General Ledger, you can do so within a project after you have completed the upgrade. For more information about this topic, see point 3.

3. Migration supportTo ensure maximum security, SAP supports each migration project with a migration service. This basic technical service is based on standard migration scenarios and is provided in the form of migration packages for a fixed price. This service is provided by a NewGL migration back office, which was set up for this purpose. After you commission the service, you are provided with a license key. This releases the migration functions.

For initial installations (new SAP customers), the new G/L is active by default in mySAP ERP. SAP advises that customers with new installations use the new G/L. These customers can still use the classic G/L if they prefer, but this may cause difficulties for future G/L migration projects. If existing customers want to use the new G/L, they have to activate it. You can activate the new G/L by following the IMG menu path Financial

Accounting>Financial Accounting Global Settings>Activate New General Ledger Accounting or by transaction code FAGL_ACTIVATION. Make sure to select the New General Ledger Accounting Is Active check box.

During a release upgrade, the classic G/L (totals table GLT0) remains active at first. You can hide the old conventional G/L configuration menu by running program RFAGL_SWAP_IMG_OLD.

Activating the new G/L results in system-wide changes to the application menu, screens, and customizing paths. For example, a new configuration menu path appears in the IMG. However, new G/L migration is more than a technical transfer, so you should consider it a separate project. Your migration approach depends on the existing and target design of your G/L. Based on the complexity level, you may find it a simpler solution or more complicated solution leading to conceptual changes.

For example, if your current G/L design does not include parallel ledgers or account solutions for the parallel valuation,you can use the simple migration solution. However, the migration project becomes more complicated if, for example,you use an existing classic G/L with PCA, have an account approach for parallel accounting, or the target design can accommodate an account or parallel ledger approach with or without a split. These examples are only a fraction of possible finance architectures. As a best practice, you should complete a careful analysis on the existing finance processes and you should carefully determine the new G/L scope.

New Functionality in the New General Ledger

Segment Reporting

Segment reporting is a legal requirement in many countries. US GAAP, and IFRS require a segment to be reported if the total external revenue of the segment exceed 10% of the total revenue. They also require to report income statement and balance sheet to be reported by segment. The big change in Segment reporting is that there is now a separate filed in the Profit Center master record.

Document Splitting

Document Splitting is a functionality that allows full financial statement to be produced at a level lower that the company code. Also line items can be split by profit center, segments, functional areas, commitments items, funds, funds program, and grants. In order to utilize document splitting activation has to be completed. Some configuration steps will be document splitting method, business transaction, business transaction variant, item categories, etc.

Parallel Ledgers

With the globalization of many organization there is an increase requirement to produce parallel sets of financial statements in accordance with different financial principle such as US GAAP, IFRS etc.

Major Advantages of All These Three Functionality

Faster Period End Closing Document Splitting in Real Time Real time posting to CO to FI no longer at period end. Legal and Mgt. reporting are unified in one ledger. Higher ROI on your investment. Balanced books by any dimension Fast Close TCP Reduction Transparency for drilldown reporting. Legal Entity Reporting Segment Reporting.

Some Important Technical Facts about Migration

The line item table in the new G/L is FAGLFLEXA and the totals table is FAGLFLEXT. The migration does not make any changes to the existing classis G/L line items table BSEG or totals table BKPF, the secondary indexes or the

totals table GLT0. The migration does not make any changes to data in other ledgers, such as the profit center accounting, cost of sales, reconciliation, or special-

purpose ledger.

Main Transaction Codes for Migration

If migration is not successful for what ever reason. below are the main transaction codes:

Complete reset (FAGL_MIG_RESTORE_ALL) Reset of open items (FAGL_MIG_RESTORE_OP) Reset of documents transfer from current year (FAGL_MIG_RESTORE_RP) Main New GL tables FAGLFLEXA and FAGLFLEXT. Main Transaction CNV_MBT_NGLM

IMG Migration Activities:

Close Posting Periods in the prior Fiscal Year Create Work-list/Activate migration plan Create Work-list (FAGL_MIG_OPITEMS_FILL) and (FAGL_MIG_RPITEMS_FILL) as background jobs. Create work-lists individually/Create work-list for open items. Create work-lists individually/Create work-list for documents. Enrich the open items with account assignment information Transfer open items from previously created work-list Build documents splitting information Subsequently post documents for current fiscal year from work-list. Create GL Line items and balance carry forward for all GL accounts not managed on an open item basis. Display log for balance carry forward. Reset balance carry forward. Repost balance carry forward manually.

New General Ledger, Parallel Accounting

The new GL functions include “Parallel Accounting”, it’s an SAP feature where you can maintain different sets of books to satisfy all different requirements of Financial Statement users accurately, efficiently and effectively. Standard reports are already available and readily available to use.

How does Parallel Accounting works in SAP (FICO)? Requirement is; a leading ledger is created in the system (0L – ledger = GAAP). Then another ledger should be created and classified as non-leading ledger (1L – ledger = TAX).

All financial transactions in the system are posted to both ledgers if no ledger is specified in the transaction. If you generate a financial statement or gl account report, both ledgers contain the data of the transaction posted.

To post only to specific leger (e.g. 0L – ledger), the Ledger Group field in the header should be filled-up with 0L – ledger. The transaction won’t affect the other ledger (1L – ledger).

NewGL Configuration

NewGL Configuration:

1. Define Currencies for Leading Ledger:

Financial Accounting (New)>FAGS (New)>Ledgers>Ledger>Define

currencies of the leading ledger

2. Define Ledger for General Ledger Accounting

F/A (New) > FAGS/ (New) > Ledgers >Ledger > Define Ledgers for

General Ledger Accounting

3. Assigning Scenarios to Ledger

Financial Accounting (New)>FAGS(New)>Ledgers>Ledger>Assign

scenarios & Customer fields to ledger

4. Defining Segment

Enterprise Structure>Definition>Financial Accounting >Define segment

5. Activate Document Splitting :

FA(N)>GLA(N)Business Transactions> Doc.Splitting >Activate Doc

Splitting Spl Note: Always see that the tick is on inheritance

6. Classify G/L Accts for Document Splitting :

Financial Accounting (New)>General Ledger Accounting (New)>Business Transactions>Document splitting> Classify G/L Accts for Document Splitting

7. Classify Document Types For Document Splitting :

Financial Accounting (New)>General Ledger Accounting (New)>Business Transactions>Document Splitting> Classify Documents Types for Document Splitting

Define Zero Balancing Clearing Account: Financial Accounting (New)>General Ledger Accounting (New)>Business Transactions>Document splitting>Define Zero Balance Clearing Account

8. Define Document Splitting Characteristics For General Ledger Accounting:

Financial Accounting (New)>General Ledger Accounting (New)>Business Transactions>Document splitting>Define Doc Splitting Characteristic for General Ledger Accounting

Define Zero Balancing Clearing Account: Financial Accounting (New)>General Ledger Accounting (New)>Business Transactions>Document splitting>Define Zero Balance Clearing Account

10. Define Document Splitting Characteristics For Controlling.

Financial Accounting (New)>General Ledger Accounting (New)>Business Transactions>Document splitting>Define Doc Splitting Characteristic for Controlling

11. FI- Co Real Time Integration:

Financial Accounting (New)>FAGS (New)>ledgers>real time integration of Controlling with financial Accounting>Define variants for Real time integration

12. Assign variants for Real Time Integration to Company Codes:

Financial Accounting (New)>FAGS (New)>ledgers>real time integration of Controlling with financial Accounting>Assign variants for Real time integration to Co Codes

** Another Section to be cleaned up later **

ECC 6.0 New GL Functionality1. Activate New GL

The New General Ledger Accounting by a single click on the clock icon

You will reach to change view "activation of New GL A/cg" detail screen and tick the checkbox and save.

After activation of New General Ledger Accounting, you exit the IMG screen When you re-enter , you find that a new node is added Financial Accounting (New)

2. Define Segment

After activation of New General Ledger Accounting , a new sub node appears in the IMG structure.

This sub node is Define Segment

The menu path is:

SAP Customizing IMG ---> Enterprise Structure ---> Definition --> Financial Accounting --> Define Segment

In this IMG activity, you define your segments.

If you then define your profit centers, you can enter an associated segment in the master record of a profit center. The segment is then derived from the assigned profit center during

posting.

Activation has created a new field in Profit Center Master Record : the SEGMENT

3. Leading and Non- Leading Ledgers

In General Ledger Accounting , you can use several Ledgers in parallel. This allows you to produce financial statements according to different accounting principles. A ledger uses

several dimensions from the totals table it is based upon. When defining Ledgers , one must be defined as the Leading Ledger . The Leading Ledger is based on the same accounting

principles as that of the consolidated financial statements. It is integrated with all subsidiary ledgers and is updated in all company codes. This means that it is automatically assigned

to all company codes. In each company code, the Leading Ledger receives exactly the same settings that apply to that company code : the currencies, the fiscal year variant and

posting period variant .

You must designate one of your ledgers as the Leading Ledger. It is not possible to designate more than one ledger as the leading ledger.

The menu path is :

SAP Customizing IMG ----> Financial Accounting ( New ) -----> Financial Accounting Basic Settings (New) -----> Ledgers ----> Ledger -----> Define Ledgers for General Ledger

Accounting

Clicking on the checkbox identifies one of your ledgers as the Leading Ledger.

4. Activation of Non Leading Ledgers

Non Leading Ledgers are parallel ledgers to the Leading Ledger . They can be based on local accounting principle, for example. You have to activate a non- Leading Ledger for

individual company codes. Non- Leading Ledgers can have different fiscal year variants and posting period variants per company code to the Leading Ledger of this company code.

The menu path is :

SAP Customizing IMG ---> Financial Accounting ( New ) ----> Financial Accounting Basic Settings (New) -----> Ledgers ----> Ledger -----> Define and Activate Non --Leading Ledgers

5. Assign scenarios to ledgers

A Scenario combines Customizing settings from different business views. Each business view specifies which posting data is transferred from different application components in

General Ledger Accounting, such as cost Center update or ProfitCenter update .You assign the desired scenarios to your ledgers. For each ledger, you define which fields are filled

with posting data from other application components.

SAP delivers a number of scenarios in the standard system. It is possible to create additional scenarios.

The menu path is:

SAP Customizing IMG -----> Financial Accounting ( New ) -----> Financial Accounting Basic Settings (New) -----> Ledgers ---->Fields -----> Display Scenarios for General Ledger

Accounting.

[6.] Cost of sales accounting

Cost of sales accounting is a way to create a profit and loss statement (P & L) for a company by comparing the revenues to the costs or expenses incurred to obtain these revenues.

The expenses are mainly divided by functional area such as:

Manufacturing

Administration

Sales

Research and Development

We can activate Cost of Sales Accounting by the following menu path :

SAP Customizing IMG -----> Financial Accounting ( New ) -----> Financial Accounting Basic Settings (New) -----> Ledgers --->Ledger-----> Activate Cost of Sales Accounting

Assets Integration in new Genral ledger

1.From the AC210 course you will see that the new entities within New general ledger accouning such as the profit center/segment cannot be directly assigned to assets in asset master data.

Therefore it has to be derived from cost c enter or order that is linked to asset. This is maintained in the time-dependent data of the asset.

2. To derive the cost center on FI document and then onto NewGL, it is

necessary to:

Set cost center field 'optional' in field status (trx. OB14 & OB41)

-> for reconciliation GL account used for asset.

3. The account assignment types are defined in customizing in Asset Accounting under Financial accounting new ->Asset Accounting -> Intergration with the New General ledger -> Additional

Account assignment objects -> Specify addtional account assignment objects

Post-Capitalization of cash discount to Asset

Post-Capitalization of cash discount to asset is only possible if document splitting is active.

This is defined in customizing under spro -> Financial accounting (New) -> General ledger Accounting(new) -> Business transactions -> Document splitting -> Define Post Capitalization of Cash

discount to Assets. From the IMG Activity documentation you will see the following stated

Define Post-Capitalization of Cash Discount to Assets

Use

In this IMG activity, you define whether the cash discount that is applied in the payment of a asset-relevant invoice should be capitalized to the asset. When you select this setting, the cash

discount amount is not posted to the cash discount account in the payment document, but instead directly to the asset.

Example:

1. Invoice created with F-90

You will note that the cost center is not displayed in the entry or the new General ledger view. The asset balance sheet value is not forwarded to a CO account assignment object. To change

this see note 395762

2. Payment F-53

3.Review AW01N

Add DoneAre you sure you Click to toggle th

1. Creation of the zero balance clearing when no partner assignment specified

Tools o Attachments (5) o Page History o Restrictions o Info o Link to this Page… o View Wiki Markup

Creation of the zero balance clearing when no partner assignment specified

Purpose

This wiki provides a demonstration of the posting logic of zero balance clearing when no partner assignment is specified on the entry view of document.

Overview

From SAP Note: 973342 the following is stated:

2. Clearing pair creation ('old' procedure that is still used if a partner assignment has not been assigned explicitly)

As of ERP, this procedure is selected if no partner assignment is specified and if the procedure is to be used to find partner relationships.

In releases up to and including 4.7, this is the general procedure for creating zero balance clearing items.

The system sorts documents according to amounts and creates pairs using a specific heuristic procedure.

In this note, the procedure is displayed in a simplified way. The profit center account assignment is used as an example. However, the complete account assignment string, that is, the

combination of all characteristics relevant for document splitting and the financial statement characteristics (zero balance) of a line item, is relevant for displaying the summarized sorting as well

as the clearing pair creation.

The pair creation of the clearing is based on a model in which a debit balance is cleared against a credit balance. The amount is taken into account.

266109335

view

Step 1 - Create GL Document

Create a GL document using transaction FB50 with three line items, each with a different profit center.

Step 2 - Simulate posting

Simulate the posting selecting Document - > Simulate General Ledger function. Review

Select icon Expert Mode

Step 3 - Review of Postings

The pair creation of the clearing is based on a model in which a debit balance is cleared against a credit balance. The amount is taken into account. In our example the following is generated

Line items are sorted according to amounts:

9999 -1000

BANK 300

CP11 700

In this case, the following algorithm is used:

Compare the first and last balance item (in the first step: 1000 and 700).

Use a smaller absolute amount (700).

Generate a clearing of the first and last item (with 700).

In the first step, 9999 is cleared to CP11 with the amount 700. In this case, two clearing items are created: 9999 is debited and CP11 is credited. The partner assignment is created as follows:

PRCTR PPRCT Amount

Clearing 9999 to CP11 700

Clearing CP11 to 9999 - 700

In the course of the algorithm, the clearing amount is subtracted from the absolute value of the first and last item, in this case item 1 and item 3 (clearing amount = 700 ).

9999 - 300

BANK 300

CP11 0 < row is deleted

Eliminate the zero balance and repeat this procedure (do not resort the rows) until all zero balance clearing items are determined using the determination of the partner assignment.

Compare the first and last balance item (in the this step this is 1000 and 300 as the third row is deleted).

Use a smaller absolute amount (300).

Generate a clearing of the first and second item (with 300).

PRCTR PPRCT Amount

Clearing 9999 to BANK 300

Clearing BANK to PC01 - 300

In the example described above, the system creates four zero balance clearing items. All zero balance clearing items clear with 9999 according to the amount.

Cross Company Code Splitting

Document split (Note 1085921)

From note 1085921 the following is stated in relation to cross company code postings:

2.10.2 Leading Item / Cross Company posting

An inter-company posting creates at least two documents, one per each

company code. There are two possible solutions to process inter-company

documents:

1.Split each document in each company code separately.

In this case there should be only one entry in the splitting rule for the item category to be edited - 01100 CC <> CC of leading item.

The split is performed locally. Only the line items which belong to the currently processed company code are taken into consideration.

2.Process all documents together as one inter-company document.

In this case there should be two entries in the splitting rule for the item category to be edited:

" 01100 CC = CC of leading item

" 01100 CC <> CC of leading item

The split is performed for all the documents. Line items of all company codes involved are taken into consideration.

The Leading Item category needs to be defined in case account assignments need to be transferred across the company codes (only case 2.). It is needed in order to identify the leading

document where the account assignment will be transferred to.

The Document which does not contain the leading item will be processed first. The Company Code Clearing line (01100) of the document, which does not contain the leading item, is split based

on the local document. The Company Code Clearing line (01100) of the document, which does contain the leading item, is split on basis of the documents that have already been split locally in

the first step.

view

Cross company-code invoice posting and configuration

Cross company-code invoice posting and configuration

Configuration example based on 2. of note 1085921 Processing all documents together as one inter-company document

1 Configuration

IMG-> Financial accounting (New) -> General ledger accounting new -> Business transactions -> Document splitting -> Extended document splitting -> Define Document splitting Rule

Assign business/transaction Variant to rule

view

-----> F2

Leading item (cross cc)

The Leading Item needs to be defined incase we want to do cross company postings. In the business transaction variant in GSP_VD (IMG -> Financial accounting (New) -> General ledger

accounting (New) -> Business transactions -> Document splitting -> Extended Document splitting -> Define Business transactions variants), this item category needs to be defined as Required.

When creating a cross company posting we will create at least two documents / one per each company code. The System needs to find a document which will be the leading. Therefore an item

category of a leading item needs to be defined.

There are two entries in customizing for Company Code Clearing lines.

A) One for the Company Code that does not contain leading item and

B) One for the Company Code that includes leading item.

The company code clearing line assigned item category 01100 of the document where the company code is the company code of leading item, is split after the Partner company code, because

the splitting of the company code clearing line of this document depends on the splitting of the partner company codes line items.

2 Cross company code vendor invoice:

The Document which does not contain the leading item will be processed first.

Document in the other company code contains the leading item.

Based on the Cross Company clearing lines of this document the Cross Company clearing lines of document which has the leading item will be created.

1. Cross company code invoice posting based on constant and rule

Tools o Attachments (13) o Page History o Restrictions o Info o Link to this Page… o View Wiki Markup

Cross company code invoice posting based on constant and rule

Purpose

This wiki provides a demonstration of the configuration of document splitting for cross company code, based on constant, rule and resulting posting. The business transaction variant is defined

so that the account assignments of one company code are not provided in the other.

Overview

In a cross company code posting when using document splitting this allows the assignments not to be split into the other company code. This document provides the steps in configuration for

the document splitting rule and constant, following by the creation of an invoice to show posting which results, highlighting the split per account assignment. User should create Own business

transaction/transaction variant for same. Configuration example based on note 1085921 section 2.10.2 Leading Item / Cross Company posting - point 1 - Split each document in each company

code separately.

Step 1 - Define header data

To Define the header data for the document splitting rule go to IMG-> Financial accounting (New) -> General ledger accounting new -> Business transactions -> Document splitting -> Extended

document splitting -> Define Document splitting Rule. Assign Business Transaction/transaction Variant to rule

Press F2 to enter the header data. In this example item category 03000 is the leading item category of the cross company code transaction

240124011

Step 2 - Item categories to be edited

For the document splitting rule, create item category 01100 with dependence on leading item = 1 (CC = CC of leading item).

Set the Processing category to '0' and after pressing enter, enter in constant.

The constant which must be defined first is via IMG -> Financial accounting (New) -> General ledger accounting new -> Business transactions -> Document splitting -> Edit Constants for

Nonassigned Processes. In my example this would lead to the usage of the constant in the cross company clearing account of company code CP01

Create second entry of 01100. In 'Change view "item categories to be edited" , in field 'dependence on leading item', choose 'dependence on leading item' = '2' - this means cross company

clearing accounts of company codes which do not contain the leading item 03000 in the local company codes posting - in my example Company code CP02. For this second item category

01100 choose 'processing category' = '1' - Splitting based on base item categories

Step 3 Base item categories for second item category 01100

Double click on the base item category for the second item category 01100. Check the item categories assigned.

Step 4 Create Invoice

Create Vendor invoice using transaction FB60

___

Simulate new GL view

Select Expert mode. The expert mode shows you the Business transaction/transaction variant used and also the postings which will result when document is posted.

Post Document

Step 5 - Display invoice via FB03

Display the invoice via transaction FB03.

Check the entry view values for leading company code invoice document.

Select Button General Ledger View to review the general ledger values for the leading company code invoice

In FB03 enter in invoice document of non leading company code. Review the Entry view account assignments

Double click on the button for General Ledger View and review account assignments populated.

Cross-Company Code Transactions

Cross-Company Code Transactions

1. Definition

Use

Several company codes are involved in a cross-company code transaction. In a cross-company code transaction, the system posts a separate document with its own document number in each

of the company codes.

Individual documents are linked by a common cross-company code number. The system generates line items automatically (receivables and payables arising between company codes) in order

to balance the debits and credits in each document.

You may use only one company code for offsetting entries. That is to say, regardless of the number of company codes involved, you must make one of the following entries:

Only one company code on the debit side and the rest on the credit side.

Only one company code on the credit side and the rest on the debit side.

2. Configuration of cross-company clearing accounts

Transaction FBKP

view

* *To configure clearing accounts for cross company code postings you can use transaction FBKP

Select automatic postings

Choose Company code clearings

Double click on line item

Continue and enter values

You can also use transaction OBYA for configuration of Clearing between company codes

Debug program used in background

Purpose

This wiki provides a demonstration of how to debug a program that runs in the background.

Overview

This document will use transaction F110 as an example to analyse document splitting in debug on a test system.

Step 1 - Delete existing proposal run

In F110 delete existing proposal run which contains error.

Via Menu path Select Edit -> Proposal -> Delete

view

Step 2 - Create new proposal with the same parameters

Select button to Schedule Proposal

Fill a start time in the future and Schedule

Step 3 - Set breakpoint at relevant function moduleIn

Transaction SE37 enter in function module. Select Display. Click on Stop Icon "Set/Delete Session Breakpoint" - Ctrl+Shift+f12

Step 4 - Select job in transaction SM37

Execute job selection

Select Job and in the OK Code field enter value JDBG, press Enter from keyboard

The selected job is now started in debug mode, and the debugger initially stops in a system program.

Choose F8 to continue the job up to the breakpoint set.

Step 5 - Delete proposal after debug

Delete proposal after debug in F110 Via Menu path Select Edit -> Proposal -> Delete

From note 573128 you can see the following stated Caution: Although the job still appears in SM37 in the previous status after debugging, the entire job (or, more specifically, a copy of it) has

run during debugging and possible database changes are effective as a result of the job.

Document Splitting

Relevant SAP Notes: 826357 (Profit Center) and 852971(Consolidation)

Document Splitting has become available in the NewGL to allow realtime line item split across characteristics (dimensions) within the single journal entry. The most often used dimensions are

Profit Center and Segment. The desired outcome is the journal entry with additional line items that balance (net to zero) within the 'splitted' dimension, so a balanced entry within a balanced

entry is ensured. The main drawback is the proliferation of line items and complication of the journal entry (accounting document) that now requires more effort to analyze as to how each line

item has been derived rather than manually entered.

Simplified you can divide the document splitting process into three steps:

1. Passive split

During clearing (during a payment for example) the account assignments of the lines to clear are inherited to the clearing line items(s) (such as payables line item(s)

2. Active(rule-based) split

The system splits documents on the basis of (delivered or custom) document splitting rules

Document splitting rules can be configured

3. Clearing lines/zero balance formation by balancing char(and document)

The system creates clearing lines automatically to achieve a split

You can control this process with the "zero balance indicator"

1. IMG Menu Path to Document Splitting:

2. Detailed configuration with Profit Center flagged for zero balance:

3. Document splitting activation (and split method selection):

Splitting methods can further be customized according to transaction and (base) category items in the Extended Document Splitting node and it seems that they greatly enhance account

determination configuration, but are bound to create some confusion among the end users.

Please see a word document for more detail.

NewGL Scenarios

In the NewGL, scenarios are in the order of best and highest use:

1. FIN_PCA

2. FIN_SEGM

3. FIN_CONS

4. FIN_GSBER (Business Area)

5. FIN_UKV (Cost of Sales)

6. FIN_CCA

Scanarios are integration points out of FI which update relevant fields in PCA, CCA, etc. during the time of entry. The leading ledger needs to have at least one scenario assigned, but in most

cases all six are recommended. Since the non-leading ledgers do not update CO, assigning scenarios to them is a moot point. Bpth FIN_PCA and FIN_CONS can be used for downstream

consolidation along the responsibility and legal (tax) boundaries, respectively.

The decision as to how many scenarios you assign depends soley on which facts/business aspects you want to model in the General ledger accounting. You cannot define your own scenarios

IMG Menu Path:

view

Detailed Configuration:

Splitting Rule for Residual Item Posting in Invoice Currency

Page restrictions apply Attachments:15 Added by Cora Phelan, last edited by Cora Phelan on Mar 06, 2012 (view change)

Purpose

This wiki provides a demonstration of the configuration of document splitting rule for the Residual Posting in Invoice Currency.

Overview

You have activated the functionalities for Residual Item Posting in Invoice Currency via SPRO -> SAP Reference IMG -> Financial Accounting (New) -> Accounts Receivable and Accounts

Payable -> Business Transactions -> Open Item Clearing -> Clearing Differences -> Residual Item Posting in Invoice Currency. You need to know the customizing of the Split Processor for

splitting to work correctly.

Step 1 - Assign Document Type and Company Code to Residual Item Posting in Invoice currency.

In this example I reference document types, these are only used to show example. The document type(s) which you use will depend on your own business example. Also it is important that you

consider what the business transaction/transaction variants you are using when making a residual posting and the transaction you are using for same, this will help you determine the relevant

business transaction/transaction variant to customize. In this example I use business transaction/transaction variant 1010/0001

Link to this Page Link Tiny Link Wiki Markup Close Move Page – ‘Spl Set Page Locatio Move OK Cancel

Click to select th Search Recently Viewed There were no re Known Location The specified pa Browse Error reading the You could try relo HTTP Status

You must make a Failed to retrieve There were no pa Showing <b>{0}< Move failed. Ther You cannot move Splitting Rule for NewGL Configura ERPFI

ERP Financials You cannot move Page Ordering Back Reorder Move Unknown user or Page Restriction Editing restricted Cancel

Close Save 30113909

view

Step 2 - Create Customer Invoice

Create customer invoice using transaction FB70

Display Invoice created via FB03

Step 3 - Assign document types to Business Transaction/Transaction Variant

In transaction GSP_VZ3 I assigned document types AB and DZ to business transaction/transaction variant 1010 0001

.

Step 4 - Activate splitting indicator For Each Logical Transaction

In transaction GSP_RD, activate the splitting indicator "For Each Logical Transaction" in the section "Further subdivide document" for the business transaction/transaction variant 1010/0001 that

is assigned to the document types used in transaction GSP_VZ3

Step 5 - Assign item category 02000 to be split based on 02000

In GSP_RD buiness transaction/transaction variant 1010/0001 the item category 02000 is split based on 02000 (auto-split flag on) is necessary.

Step 6 - Create Residual Payment Document FB05

In transaction FB05 enter document type AB in header, proceed with residual payment.

Simulate

Click on Post

Review of Documents