SAP FICO

SAP - FI ECC 6.0 New GL Functionality Config

Activate 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)
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
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.
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
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 Profit Center 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.
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.

SAP Upgrade – Key points to remember

Purpose of this post - to highlight why customers across industry need SAP ERP upgrades & how effectively these upgrade projects can be executed. This document also covers actual upgrade experience of customer XYZ Corp.

Note: Above given points covered in one link only.

SAP : Bank Guarantees Configuration

Bank Gaurantees are normally two stage transactions i.e

When you receive the Bank Gaurantee
When you receive the payment for which it was issued

The configuration for Bank Gaurantee can be done using the T Code FBKP.

You need to assign the GL accounts for the Special GL Indicator "G".In tis process you can do it for Customers or Vendors.

It is a GL Account Assignment to the Reconcilliation Account that is being assined the Customer or Vendor master.

When ever a Bank Gaurantee is received then we enter the data as Noted item.And the amount would be shown as a open item in the Bank Gaurantee GL account.

When the amount is received then in the entry screen for the amount received we also select the Special GL indicator G so that the Open Item gets cleared.

By doing so it would be possible to arrive at the list of the Gaurantees open at any point of time.

The steps are as follows :

1.T Code FBKP for GL Account Assignment to the Reconcilliation Account
2.T.Code F-49 for entering the Bank Gaurantee received as Noted Item.
3.T Code F-28 for Gurantee received from the Customer for the sales invoice. In the first screen in the Open Item Selection segment provide "G" as the Specil GL indicator after providing the Customer No.

The the system would automatically clear the Gaurantee along with the invoice amount.

We will not receive the BG from Customer nor pay to the Vendor. as Security there will be Deposit in our bank account.
the Entry for the same will be

DR FDR with Bank for BG.( % of the BG as deposit (asset)
DR Bank Charges.( % of BG, will be expense)
CR Bank CC A/c ( CC already allot for the client)

In case of delivery fullfillment with customer or after the fixed term the entry will be

Cr FDR with Bank for BG
Cr Intrest Chages ( Income on the Deposit)
Dr Bank cc A/c.

Things to be considered when implementing the user exit

No dialog boxes, warning messages, information or error messages must be issued in an exit, and a "COMMIT WORK" must not be rejected. This would, for example, interrupt the batch processing or cause problems with the documents to be posted.

If you find a serious error in the field contents in the exit, send a termination message (A or X), which will ensure that the transaction is terminated.

Do not use any ABAP commands that cause you to leave the exit directly, for example 'LEAVE (TO) SCREEN ...' or 'SUBMIT ...' or 'CALL TRANSACTION ...' In an exit, use only structure fields that belong to the Boolean class of the calling substitution, validation or rule.

The other structure fields are not filled or are not filled properly for the callup point of the calls of the substitution, validation or rule.

You may make changes to field contents in a substitution exit only if this field can be substituted in the Boolean class.

You can display these fields by choosing "Add entry" in the substitution maintenance. In the includes of the substitution exits, you must not use the commands MODIFY, INSERT or DELETE in the internally used structures such as BSEG or BKPF.

These structures are interpreted internally as database tables because they are defined by a TABLES statement. As a result, the system writes, deletes or changes database records if you use the commands mentioned above.

This can cause serious inconsistencies and problems in the document processing. If you want to change field contents in the exit type C_EXIT_PARAM_CLASS, you should make the changes in the internal table BOOL_DATA (for example BOLL_DATA-BSEG).

How to create a user exit for Validation / Substitution ?

Define your user exit in the FORM routine GET_EXIT_TITLES with the correct exit type (EXITS-PARAM). You can use the existing sample entries as a template for this.

The exit types required in the FORM routine GET_EXIT_TITLES are organized as follows:

C_EXIT_PARAM_NONE: No parameter apart from the return value (B_TRUE or B_FALSE), you do not need any parameters for the validation. If you do not want to substitute a field, use this parameter in the substitution (select "Only exit"). However, you must then use a TABLE statement in the FORM pool (not in the actual form) to identify the relevant structure.

C_EXIT_PARAM_FIELD: A Field is transferred as a parameter you only use this type in the substitution. Exactly one field is substituted. Enter user exits of this type in the substitution maintenance instead of assigning a constant value.

C_EXIT_PARAM_CLASS: A complete type is transferred as a parameter Matrix validations/substitutions ("Only exit"). This exit type can only be used for call up points with complete documents, for example in FI and LC. You cannot use this exit type for any other call up points.

The transferred type contains all information about a class.

An example is the use of the document header and all corresponding line items in the FI area.

In the FORM routine GET_EXIT_TITLES, change the fields NAME and TEXT of the internal table EXITS to the values you want. Use one of the sample routines as a template and copy these to the names you selected. You can now implement the functions you want in this FORM routine.

After you have finished creating the user exit, you can use it in your validations or substitutions.