ECC 6.0 New GL Functionality and General FAQ

ECC 6.0 New GL Functionality
1.Activate the New General Ledger Accounting by a single click on the clock icon

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

3. 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)
4.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.
5.Activation has created a new field in Profit Center Master Record : the SEGMENT
6.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.
7. 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
8.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 not 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.
9. 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

Offsetting Account Report ECC 5.0
Offsetting account report for vendors in ECC 5.0 is possible after implementing the OSS Note 1034354

---------------------------------------------------------------------------------------------------------------------------
All frequently asked questions about Financial specfic topics can be found here.

Electronic Bank Reconciliation
The primary configuration steps necessary to set up Electronic Bank Statements (EBS) Processing in SAP.
1. Create House Bank and Account ID (FI12)
2. Setup EDI Partner Profile for FINSTA Message Type (WE20)
3. Configure Global Settings for EBS (IMG)
Create Account Symbols
Assign Accounts to Account Symbols
Create Keys for Posting Rules
Define Posting Rules
Create Transaction Types
Assign External Transaction Types to Posting Rules
Assign Bank Accounts to Transaction Types
Also check out this very useful link which shows how to configure in detail
http://www.sap-topjobs.com/sapFI/bankreco4/index.htm

Fiscal Year Variant:
Definition

The fiscal year variant contains the number of posting periods in the fiscal year and the number of special periods.

You can define a maximum of 16 posting periods for each fiscal year in the Controlling component (CO). To define the fiscal year variant, go into Customizing for Financial Accounting (FI) under Financial Accounting Global Settings ® Fiscal Year ® Maintain Fiscal Year Variant.

Integration
You need to specify the fiscal year variant for each company code.

When you create a controlling area, you also need to specify the fiscal year variant. The fiscal year variants of the company code and controlling area may only differ in the number of special periods used. You need to ensure that the fiscal year variants match, in other words, they may not have a time conflict.

You can assign a company code using a fiscal year variant with 12 posting periods and four special periods to a controlling area that has a fiscal year variant with 12 posting periods and one special period. The time frame, for example, from April 1 to March 31 in the following year, must be identical in each fiscal year variant.

However, it cannot be assigned to a controlling area with 52 posting periods for example.
*****************************************************************************************

Fiscal year is the way financial data is stored in the system. You have 12 periods in SAP and also four special periods. These periods are stored in what is called the fiscal year variant.
There are two types of Fiscal Year Variant
? Calendar Year - Jan-Dec, April -March
? Year Dependent Fiscal Year.
Link on SDN ERP Financial forum:
Fiscal Yr Variant: https://www.sdn.sap.com/irj/sdn/thread? ... D=2500716&
Changing Fiscal Year Variant Help Needed: https://www.sdn.sap.com/irj/sdn/thread? ... D=2462193&

Link in HELP:
http://help.sap.com/saphelp_47x200/help ... ameset.htm

Automatic payment Run:
Use
For each company code using the payment program, certain basic specifications must be in place.

Since the payment program can be used for more than one company code, you must also specify the company code that is making the payment.

To control the payment program, you must specify the following in advance:

How payment requests are selected and, if necessary, grouped together for one payment
The payee
How the payment method is selected
How the bank is selected
Which forms and other data carriers are used
Activities
You make these specifications when:
Configuring the payment program
Entering data in the master records of your business partner
Entering data in the payment requests
Entering data for the payment run in hand
When configuring the payment program, you specify the company codes that are involved in automatic payments and also which company code makes the payments (paying company code).
The payment program identifies the open payment requests and selects the items to be paid. It basically pays items as late as possible. You specify the exact time of payment when configuring the payment program

The selection of open payment requests is determined by the following factors:

The due date of the items is basically determined by the due date and the level of urgency indicator in the payment request
For each payment run, you specify the date of the next payment run. The program uses this date to determine whether an item is to be included in the current or the next payment run.
You block the items that, regardless of their due date, you do not want to pay. To do this, you enter a blocking key in the item that represents the reason for blocking. If you want to block the account of a customer or vendor from payment, you enter the blocking key in their master record.

The standard system contains several blocking keys, which you can add to or change.

The payment program creates a payment proposal during the payment run. The payment is made on the basis of this payment proposal list. The blocked items are displayed separately in the list. You can process the payment proposal, and, for example, set or cancel the payment block on an item.

It is also possible to specify that a blocking key cannot be changed from the payment proposal transaction.
On the whole, the payment date is used as the clearing date. There exist, however, the following exceptions.

Items whose posting date comes after the posting date of the payment run will be paid, provided they are already due.

The clearing date for such payments is not the payment date, but rather the latest posting date possible. Thus any danger of the clearing date coming before the posting date is prevented in the context of paid items. Errors are avoided in this way.

Grouping of Payment Requests
Use.
Wherever possible, the payment program will always group payment requests together for payment. However, you can also specify that an individual payment (separate payment) is made for a particular item. For certain payment methods, only individual payments are possible.

The payment program can only group together open payment requests into one payment if the open items in an account have the same:

Payment currency
Payment method in the item
Bank in the item
Contents of the grouping fields
You can also settle payment requests from different company codes together as well as customer and vendor items.

Items in an account are not grouped together if you:

Make payments seperately per business area. This procedure entails separate payments being created per business area.
Wish to make individual payments.
For further information, follow the link

http://help.sap.com/saphelp_erp2005vp/h ... ameset.htm

--------------------------------------------------------------------------------------------------------------------------------
Payment Processing is a component of SAP's R/3 Financial Accounting module (FI). FI is a powerful module integrating many activities, including General Ledger, accounts payable, accounts receivable and assets accounting. You will learn to process simple and complex payment transactions. In addition, you will maintain data and systems settings for accurate and effective payment processing in this course
http://www8.sap.com/businessmaps/41A4EF ... 1D646F.htm

Link in HELP: http://help.sap.com/saphelp_47x200/help ... ameset.htm

Message Control for Warnings or Error:
http://www.sap-basis-abap.com/sapfi023.htm

Copy G/L Accounts Master records from one client to another:
http://www.sap-basis-abap.com/sapfi019.htm

Clearing of GR/IR account:
http://www.sap-basis-abap.com/sapfj021.htm http://help.sap.com/printdocu/core/Prin ... IVWERE.pdf

LSMW:
The LSM Workbench is an SAP-based tool that supports you when transferring data from non-SAP systems ("Legacy Systems") to SAP systems once or periodically.
The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the SAP system via batch input, direct input, BAPIs or IDocs.
Furthermore, the LSM Workbench provides a recording function that allows generating a "data migration object" in an entry or changing transaction.
http://service.sap.com/lsmw

Validation and Substitution:
Validations and substitutions are used to check the conditions while posting a document in sap system.

The step of Validation is.

1) Prerequisites
2) Step
3) Message

Setting up the FI Validations:
http://www.sap-basis-abap.com/sapfi004.htm

https://websmp104.sap-ag.de/~form/handl ... NUM=842318

https://websmp104.sap-ag.de/~form/handl ... NNUM=42615

Month end & Year end closing:
https://www.sdn.sap.com/irj/sdn/thread? ... D=1538427&

Here are more specific on Asset Module Closing:
http://help.sap.com/saphelp_erp2005vp/h ... ameset.htm
GUIDANCE FOR YEAR END CLOSING OF ASSET MODULE :

Run Depreciation for Asset accounts and posted the depreciation((t-code AFAB)Use "Reason for Posting" : Planned Posting Run or Unplanned Posting Run(this is not recommended)
Repeat run depreciation in latest period if necessary(t-code AFAB)Use "Reason for posting" : Repeat
Close the fiscal year of asset ( t-code AJAB )
Open next fiscal year of asset ( t-code AJRW ) You can undo the closed fiscal year of asset in t-code : OAAQ
MONTH CLOSING OF ASSET MODULE :
Run Step 1 and Step 2 above.
NOTE :
You must execute step 1 until 4 in the background.
Authorization Objects a Simple Guide:
https://www.sdn.sap.com/irj/sdn/go/port ... 30ea4a585c

User exits in FI/CO:
http://www.sap-img.com/abap/a-short-tut ... -exits.htm

Setting up the FI Substition with user exit program control.
Here, it is detailly explained how to set up FI Substitutions with extended user exit functionality.
https://www.sdn.sap.com/irj/sdn/thread? ... dID=287697

Duplicate Invoice Check

In which cases a check for double invoices is run through (prerequisites)? Which function module is relevant? Which fields are relevant?

Solution/Answer:

Prerequisite:
---------------
If the field 'Chk double inv.' is marked in the vendor account.
The Function Module name is FI_DUPLICATE_INVOICE_CHECK

It will check

The following fields must be identical for Duplicate invoice check

Company code (BUKRS)
Vendor number (LIFNR)
Currency (WAERS)
Reference number (XBLNR)
Amount in document currency (WRBTR)
Document date (BLDAT)

If the document is having any one of the above filed different then the system does not consider it as a duplicate invoice.http://help.sap.com/saphelp_47x200/help ... ameset.htm

Clearing of accounts - If Customer is vendor or Vice Versa:
The clearing between the customer and vendor can happen by following the below settings

1. The customer number must be entered in the corresponding vendor master record
a. FK02->General Data -> Control
In the 'Account control' tab, in the 'Customer' field, enter the customer number

b. In the Company Code Data --> Payment Transaction Accounting, select the checkbox - 'Clrg with Cust'

2. The vendor number must be entered in the corresponding customer master record
a. FD02->General Data -> Control
In the 'Account control' tab, in the 'Customer' field, enter the vendor number

b. In the Company Code Data --> Payment Transaction Accounting, select the checkbox - 'Clearing with vendor'

3. For testing, create a vendor invoice through FB60 and customer invoice through FB70. Note that customer and vendor are properly selected.

4. For clearing the open items. Use the Tcode F-32. On clicking the 'Process open Items', the vendor invoice (KR) and customer invoice (DR) are shown automatically. It will generate the FI document with proper entry.

Note: Partial / Residual payment between customer and vendor is also possible

SAP release notes(Older 4.6 v/s to ECCC- New releases)
easy way of finding release notes http://solutionbrowser.erp.sap.fmpmedia.com