Frequently Asked Questions in SAP in the context of New G/L

-
A.1 Technology

What is the maximum number of segments in the key of the new totals table FAGLFLEXT?

In Special Ledger there are 45 object number tables, each with 15 key fields . The SL totals table can contain a maximum of 45 key fields. These 45 key fields also contain some fixed standard fie lds such as COMPANY CODE, G ENERAL LEDGER ACCOUNT, PROFIT CENTER, and SEGMENT.  In New General Ledger, fields li ke COMPANY CODE, ACCOUNT, PROFIT CENTER, and SEGMENT are standard in the table key. In addition, two customer includes are available where the customer can include an additional 15 fields (other SAP standard fi elds such as the plant or cus­tomer-defined fields). Keep in mind that many additional fields can result in high data volume, which causes performance problems in processes such as reporting, foreign currency valuation, and allocation .

What are the sizing impacts if New General Ledger is used and what impact does turning on New G/L have on performance issues?

The impact depends on the implemented functions. Sizing and performance remain the same if no additional functions are used. Mainly it is "additional ledgers for parallel accounting" or "document split" that have an impact.

Can line items and totals be managed together?

 No. Line items and totals are managed in different tables. There is no option to manage them all in one table.

When table logic has changed (FAGLXX replaces GLTO), how does the data source for SAP NetWeaver 81 evolve in turn?

The data sources have to be created first. There will be the technical name 3FI_GL_XX_TI, which is a placeholder (naming convention), where XX has to be replaced by the ledger description. For a ledger "LL," the data source would be 3FI_GL_LL_TI if it has been created before. The transaction for creating your own data sources in New General Ledger is FAGLBW03. The only data source for the New General Ledger delivered by SAP is OFI_GL_10, which extracts data only from the leading ledger. If data from the non-leading ledger is requested, the procedure described previously occurs. In some cases, an extract structure is required to create a data source. This structure has to be generated using Transaction FAGLBW01. This structure has to be created if the ledger for which the data source is needed is not based on the delivered standard totals table FAGL­FLEXT.


Extending fields in New General Ledger tables

How is the enhancement with customer-defined fields technicalry mapped? Can a customer who has enhanced the BSEG using COBL up to now continue  to use COBL in New General Ledger. or is there another procedure?

The procedure is identical. Technically, the customer field is inserted using an include (CI_COBL in COBL).

 Does SAP give recommendations on how many customer dimensions with how many characteristics customers should have?

SAP offers no recommendation on this issue. It must be decided at the project level. The important parameter is performance during data evaluation. It is also possible to work with a few different led­gers, each with one characteristic.

 When fields are extended in New General Ledger tables, does this extension easily allow for tasks such as reporting (line item detail and balances, and SAP processes such as year-end balance carry­ forwards, including the extended field, and so on?

All customer-defined fields are extended within the line-item structures and are available in the entry view for general inquiry/reporting. Fields can also be customized for inclusion in the totals table, making them available in the ledger view. Only fields included in the totals table have balances carried forward.

Can only customer-defined extensible fields be included, or can existing SAP fields be included as well (for instance, material number)?

A limited number of standard fields can be included in New General Ledger totals table via normal Customizing. Fields that are not available can be installed as customer fields; however, it is necessary to make the derivation in order for the values to be populated.

Is there any functionality that extending fields in the tables won't allow for?
Customer fields must have substitution or derivation logic and/or be available for input in order to receive values.

Is there anything to be considered when extending fields within New General Ledger tables?
There will be impacts on table growth within summary tables for each extended field . According to SAP's development department (see Note 820495), having five to six million rows in summary tables create a situation in which performance degradation may be apparent for activities including allocations, month-end processes, reporting, and SAP NetWeaver BI extracts. Splitting and zero-balancing on extended fields will affect table growth as well.

What other considerations will impact system performance?
Document-splitting functionality and zero-balancing functionality create additional line items.

Comments

Post a Comment

Popular posts from this blog

Using T-Code GGB1 (Substitution Maintenance) to create FI Substitutions

-
Image
Substitution in SAP FI is done to insert/infuse values into existing set of value(s) in fields. There are many cases where functional consultant don’t want to clutter up things using User-exits and SAP Enhancements. This is one of the best tool/method provided for keeping all the things/coding tidy as far as simple Substitutions are concerned. For complex Substitution, of-course User-exit (within the Substitution) needs to be written down as per requirements. In this step-by-step document, we will traverse through a simple Substitution case involving Customer User-Exit showing the flexibility of SAP Substitution. Our Example Case: Substitute ‘Additional asset description’ field (ANLA-TXA50) value with 15 digit code maintained in Key word for G/L accounts in G/L account master. 1. Execute Tcode  GGB1  and define the Substitution. Insert step in it. Here you can define the prerequisite based upon your requirements. In our case lets say we want it in all cases so we ...
Read more

SAP PSM-FM (Fund Management - BCS) Master Data and Derivation Tool

-
Image
  Organizational Structures LESSON OVERVIEW The lesson will explain the organize structures in Funds Management. LESSON OBJECTIVES After completing this lesson, you will be able to: Organize structures in Funds Management         Figure 6: Organizational Elements Within Accounting Depending on the level at which accounting data is viewed, the organization is represented in the SAP system using the following structures: The organizational unit for Funds Management is the financial management area (FM area). The organizational unit for Controlling is the controlling area. The organizational unit for Financial Accounting is the company code. The FM area and the controlling area take precedence over the company code.         Figure 7: Organizational Structures         Figure 8: Organizational Structures - Scenario 1 Scenario 1 :  Funds/Functional Area/Funded Prog...
Read more

SAP PSM-FM (Fund Management-BCS) Integration with other SAP Module

-
Image
  Financial and Asset Accounting Integration LESSON OVERVIEW This lesson will explain the process to integrate Funds Management, core processes within purchasing and the uses of Asset Accounting components. LESSON OBJECTIVES After completing this lesson, you will be able to: Define the business processes that are integrated in Funds Management Explain the ways in which the Controlling, Project System, Asset Accounting, Plant Maintenance, and Sales and Distribution application components can be integrated with Funds Management Compare the different core processes that take place within purchasing, and within payroll and trip cost accounting Troubleshoot the individual steps to be followed and a detailed explanation of how they are inter-linked and how assessed value is adjusted         Figure 146: Financial and Asset Accounting Integration         Figure 147: Integration FI - Funds Management A commitmen...
Read more