SAP certification training centers in India

SAP certification training centers in India

Here a  list of SAP certification training centers in India, Please contact below SAP authorized training centers if you have any queries related to certification cost, duration etc.

SAP Certification training centers in Delhi
Atos IT Solutions and Services Pvt. Ltd.	VIPPS Center, II Local Shopping Center Masjid Moth, Greater Kailash Part II, New Delhi – 110 048 Tel: 011-29220694/ 0695/0697/1247 E-Mail ID: sapatcdel.in@atos.net
Shivansh Solutions Pvt. Ltd	Corp. Office : 506-507, Kailash Building 26, Kasturba Gandhi (K.G.) Marg, New Delhi-110001, INDIA Phone: +91-11-4188 0000 Email: contact@shivansh.co.in
HCL Infosystems	F – 1, Sector 8 Noida- 201301, India Phone: +91 120 2425453/54
JKT SAP Academy	A-60, Sector-2 Noida- 201301, India. Tel: +91 120 4350201, 99992 60055 Email ID: sapacademynoida@jktech.com
Siemens Information Systems	VIPPS Center, 2, Local Shopping Center, Masjid Moth,GK-II, New Delhi -110048 Phone: 91-11-29221247 / 48 & 29220695/96 Fax: 91-11- 2921 4685 Email: sapatcdel.in@siemens.com
SAP Certification training centers in Mumbai
Atos IT Solutions and Services Pvt. Ltd	10th Floor, Tower – B, 247 Park, Vikhroli Corporate Park, Lal Bahadur Shastri Marg, Vikhroli (West), Mumbai -400 083 Tel:+91-022-25799700-05 Fax:+91-022-25799707 Email ID: sapatcmum.in@atos.net
Bharat Petroleum Corporation Ltd	BPCL SAP Training Centre ‘A’ Installation, Sewree (East),Sewree Fort Road, Near Sewree Station, Mumbai – 400015,India Tel: 022 – 24117829/24117831 Email ID: bpclsaptc@bharatpetroleum.in
Delphi Computech Pvt Ltd	Office no 206,Kesar krupa building, above Saraswat Bank, Chandavarkar Road,Borivali west, Mumbai- 400092 Tel:+9122 28956980/ 81/ 82/ 83/ 84 Email ID: info@delphicomputech.com
	601, B Wing , Heritage Plaza, 28, Teligally, Andheri (East ) Mumbai -400069 Tel: +912265249396 / 3946 Email ID: info@delphicomputech.com
	06, Thacker Tower, 1st Floor, Near Saraswat Bank, Sector 17, Vashi, Navi Mumbai 400703 Tel: +912266738489/ 90/ 91/ 92/ 93, Email ID: info@delphicomputech.com
Genovate Solutions India	A Wing, 2nd Floor, Phoenix House, 462 Senapati Bapat Marg, Lower Parel, Mumbai 400013 Tel: +91 22-30421839/ 24979498/ 30421840/41/42 Fax: +91 22 30421844 Email ID: info@lithanhall.com
SAP Certification training centers in Hyderabad
Ami Tech (India) Pvt. Ltd.	202, NSIC-EMDBP, Email ID: mohan.karedla@amitech.in Kamalanagar, ECIL Post, Hyderabad – 500 062,Email ID: mohan.karedla@amitech.in
Atos IT Solutions and Services Pvt. Ltd	ASTRAL HEIGHTS, 6-3-352/2&3,3rd Floor, After Panjagutta Police Station, Next to Himalaya Book Depot Banjara hills, Road No 1, Hyderabad-50003,Email ID: sapatchyd.in@atos.net
Lithan Genovate	2nd Floor, ANK\’s Towers, Raj Bhavan road, Somajiguda, Near Yashoda Hospital Hyderabad – 500082, Email ID: info@lithanhall.com
SAP Certification training centers in Bangalore
ATOS IT Solutions&Service	Atos IT Solutions and Services Pvt. Ltd. Gopalan Millennium Habitat, Ground and First Floor, No. 133,Kundanahalli Road, Brookefield, Bangalore-560 037, Phone:  080 -6743 5524 /25 /27 /19 /21 Email Id:  sapatcblr.in@atos.net
Lithan Genovate	R B Fashion house 62, jyoti Niwas, College road Koramangala, Bangalore – 560095 Phone: 91-80-41400666 / 41400555 / 32406056 / 42288538, Email Id: info@lithanhall.com
eDrishyaa IT India Pvt Ltd	No.620 , 2nd floor , Dr. Rajkumar Road, Rajajinagar2nd Block, ( Above Blue Hyundai Car showroom )Bangalore 560010. Email Id: info@editindia.in, Phone: 093437 74362
SAP India Pvt Ltd	Salarpuria Soft Zone,2nd Floor Wing A, Sarjapur Outer Ring Road Bangalore- 560 103 Email Id: info.india@sap.comPhone: 91 (80) 4136 5555
Source One Management Services Pvt. Ltd	Site No: 15, 3rd floor, Bannerghatta Main Road, J.P Nagar 3rd Phase, Opp to Shopper Stop, Above Raymond Showroom,Bangalore-560078 Karnataka Phone: 91-080-67586333 Email Id: sap.academy@msourceone.com
Siemens Information Systems Ltd	#206, LOGOS, Ground Floor, The Bible Society Building, M.G.Road, Bangalore- 560001 Phone: 91-80-25095577/79, 65700 001 / 02 Contact Person: Ms. Dhanashree Chachad Email Id: sapatcblr.in@siemens.com

Gaps

How to avoid problems during the implementation resulting from not identifying the local needs? How to find and properly identify the differences between the SAP template system for the corporation and local legal and business needs? The Fit & Gap analysis may be helpful – a standard element of BCC Go Forward methodology for projects of rollout type.

Many Polish companies face the challenge of implementing the standard SAP system operating in a corporation. Increasingly, they are not only the recipient of the system used in the international headquarters of the corporation, but they are the owner of the template system (regardless of the fact, whether they are original Polish companies or the Polish departments of the international corporations).

The implementation of such a project is an organizational and communication challenge both for the parent company and for the local company, particularly if both companies are located in different countries. The parent company is interested in the biggest possible adaptation of the local company to the corporation processes, above all due to the requirement of process unification in accordance with the best practices operating in the company.

The second essential aspect is also the optimization of the implementation, and hence its costs. But regardless of how much the parent company would like to see the template as a consistent entirety, two types of differences will occur:

• Legal Gaps – specific legal regulations, particularly in the financial, sales and human resources area (e.g. correction invoice in Poland and credit/debit memo in Germany);
• the differences in the local business process (local gaps) – particular companies may have own business processes that do not appear in the template (e.g. the unique production process in the corporation) or other specific requirements not resulting directly from the legal regulations, but critical for the business activity (e.g. special discount system for the key customer who has a large share in the company’s turnover).

Many people participating in the project believe that each difference will cause the increase of the implementation budget. However, it does not have to be the case. The awareness of the difference does not automatically mean that it has to be implemented in the system.However, it means the possibility of selecting the method of its processing:

• implementation in SAP system,
• leaving in the external system,
• manual processing outside the IT system or organizational change that eliminates the given requirement,

and presentation of the selected method to the persons from the local company.The experience shows that such an attitude builds the confidence in the new system (“my needs are not ignored”) that essentially influences the engagement of the persons from the local companies into subsequent project activities.

Prior the Fit & Gap analysis, the parent company should determine which areas of the system will be subject to the analysis.It depends above all on the business profile of the local company

How to find “gaps”?

How to find “gaps”?

We know already that the differences definitely exist but how to define them? How to avoid problems during the implementation resulting from not identifying the local needs? The Fit & Gap analysis may be helpful – a standard element of BCC Go Forward methodology for the rollout project.

Prior the Fit & Gap analysis, the parent company should determine which areas of the system will be subject to the analysis (will be implemented in the local company as a target).It depends above all on the business activity profile of the local company – if it is for example a dealership, then the logistics processes will be included in the scope of the analysis, and the production processes will be excluded.

The Fit & Gap analysis may be performed by the parent company organization or by the implementation partner.If the partner is responsible for the execution, the trainings for the consultants in the area of the existing template may be necessary prior the analysis (particularly if the documentation of the template is not available).

Fit & Gap analysis is divided into three stages:

Stage 1. Preparation of a solution template for the trainings. This stage includes gathering of the template documentation (business blueprint, manuals, technical documentation) and preparation of the training system (e.g. on the test system). The sample data (e.g. materials, customers, vendors) should be obtained from the new company and loaded to the training system. It shall enable the employees of the local company to better identify the discussed processes.

Stage 2. Training of the project team members (key users) in the scope of implemented processes in the template system.The owners of the template business processes present the functionality available in the system to the users from the local company.The implementation consultants, a particularly the consultants familiarized with the local legal regulations, should participate in such a training.

In particular cases, if there is a problem in the local company to communicate in the project language, this stage may be divided into two sub-stages: Training of the implementation consultants in the scope of template processes executed by the owners of the processes in the project language, and then training of the members of the project team from the local company by the implementation consultants in the local language.

Stage 3. Sessions of project teams devoted for the determination of the differences between the presented processes and local needs.On the basis of the knowledge gained during the trainings, the employees of the local company indicate the differences between the process modelled in ERP system and the process currently operated in the company.It is necessary to indicate all perceived differences.

The decision, whether the difference will be implemented in SAP system or an organizational change by the company will be required or whether the process will remain in the existing form, should not influence the fact of registering the discrepancy. The reported differences should be registered, using the project tools applied in the organization (e.g. a list of differences in SharePoint portal or at least common Excel sheet available in the network directory). Each difference should be described by means of the following attributes:

• ID of the difference (GAP_ID) – numeric identifier,
• module – specification of the area, where the gap was identified (e.g.MM, FI),
• process that it refers to – specification of the process that this difference refers to (e.g. purchase of the raw material),
• reporting person – full name of the person reporting the difference,
• business need – business justification for the existence of the given difference,
• type (legal, local) – information whether the given difference results from the legal regulations,
• priority (high, medium, low) – information on the degree of the significance of the difference,
• estimated workload of the implementation of the changes in the system (e.g. number of days of the consultant work) – it allows to compare the significance of the change with the workload for its implementation.

Additionally, the tool used for the registration of the differences should enable the changing of the difference status (e.g. accepted, rejected, under analysis) and tracking of the change history.

The decision, whether the difference will be implemented in SAP system or an organizational change by the company will be required or whether the process will remain unaltered, should not influence the fact of registering the difference

“I do not understand the standard”

During the Fit & Gap analysis, it is necessary to consider several factors that may adversely influence its course.

In the international projects, one of the challenges is to determine the project communication language (usually it is the English language) and the selection to the project team of the persons effectively using this language. If one of the key persons does not communicate in the project language, it is necessary to devote time and budget for the translation of the project documentation to the local language and again to the project language. Additionally, the presence of the local consultant, knowing the language, may be necessary to perform the analysis in the given area (in this case, an earlier knowledge transfer about the template to the local consultant is to be taken into consideration).

An essential factor negatively affecting the success of the rollout projects is the fear of the changes that the new system brings to the company. The trainings in the scope of the template system, which are the elements of the Fit & Gap analysis, are a good practice to overcome these concerns.Additionally, making the system available to the members of the project teams and encouraging them to self execution of the processes facilitate the further communication.

Another factor is the difficulty in understanding the local circumstances by the international consultants. “We are already integrated with this bank, so it will surely also work in Poland” - such a sentence is often heard from the corporate consultants. They do not take into consideration that the same bank in different countries uses different file formats for integration. Unfortunately, we often meet with similar simplifications and erroneous assumptions that are identified only during testing or after going live. The engagement of the local consultant allows to minimize the occurrence of this risk.

Why do we need a local consultant?

As illustrated by the examples cited earlier, the involvement of the local consultant is one of the key elements of the success of Fit & Gap analysis (as well as of the entire project). What can and should be expected? Below, we present three major tasks:

• Delivery of the gap list that occur most often during the implementations in the given country and/or in the given industry (ready material for the discussion with the local company, checklist in order to ensure that we have not missed something that might be important);
• Verification on a current basis of the requirements placed by the members of the project team (with regards to the legal requirements) and suggestion of solutions generally applied in other local companies instead of “reinventing the wheel” by the consultants from the corporation;
• Better level of communication with the employees of the local company (elimination of the problems resulting from the language barriers).

We have differences and what’s next?

Each of the difference registered during the analysis should be then verified with regards to the reasons of its operation:

• Does the current mode of operation result from the legal regulations?If yes, it is likely to take this difference into consideration in the system. In the specific cases, it may be decided to implement the given functionality outside the system.
• Does the current mode of operation result from the local organization? If yes – what happens, if the process will be changed to comply with the corporate one? If the current process is better than the corporate process, two scenarios are possible: Decision on the implementation of the change in the system, but only for the local company or decision on the change of the template process (it cannot be excluded that during the rollout the corporation will also learn something from its branches).

The entire Fit & Gap analysis should last from two to three weeks (depending on the complexity of the implementation).Its result should be a list of all registered differences along with the information on the method of their execution after the implementation.Since the implementation of these differences may influence the processes that are already operating in other countries, it is necessary to remember to plan tests of these processes prior going live (so called regression tests) for other countries using this system. But this is a step belonging to the next stages of the project that will be performed much easier thanks to the reliably performed Fit & Gap analysis.

GAP ANALYSIS

GAP ANALYSIS

Gap means small cracks. In SAP world or in Information Technology world, gap analysis is the study of the differences between two different information systems or applications (example: existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be."

Gap Analysis is undertaken as a means of bridging that space. Actual Gap Analysis is time consuming and it plays vital role in Business Blueprint [AS IS Process] stage.

A through Gap Analysis will identify the gaps between how the business operates and its needs against what the package can cannot do. For each gap there will be one of three outcomes which must be recorded and action taken,

1. GAP must be closed and customized software can be developed
2. GAP must be closed but software cannot be written therefore a workaround is required
3. GAP does not need to be closed.

A point worth mentioning here is that at time people confuse between user-exits and Gap Analysis. User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench, its not new functionality which we are trying to build in sap but its slight enhancement within the same code.

Gap analysis is start point of Realization and once business Blueprint is finished we have to find the realization of sap system for client requirement and there will be certain gaps when compared to system fit. Those gaps can be closed either by re-engineering of business process to fit with SAP or we have to use USER exits in case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system.

The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.
Examples:

1. MGM Studios and Lycos sometime back worked with SAP to develop its new intellectual property management and media advertising management functionality, respectively.
2. A leading Oral care product company wanted the promotion of free-goods where they wanted 'Buy one get 2 different products free'.

Financial Accounting Configuration in SAP FICO step by step  

Enterprise Structure Configuration Settings

Enterprise Structure :- The SAP Financial Accounting enterprise structure is organisational structure that represent an enterprise structure in SAP and Enterprise Structure is the key building block to the entire organisation.

Below are the Steps of Enterprise Structure Settings and configuration 

1. Define Company
2. Define Company Code
3. Assign Company Code to Company
4. Define Business Area
5. Define Functional Area
6. Define Credit Control Area
7. Assign Company Code to Credit Control Area

Step 1 :- Define Company

SAP Menu Path :- SPRO –> IMG –> Enterprise Structure –> Definition –> Financial Accounting –> Define Company

Transaction Code :- OX15

 Step 2 :-  Define Company Code

 SAP Menu Path :- SPRO –> IMG –> Enterprise Structure –> Definition –> Financial Accounting –> Edit, Copy, Delete, Check Company Code

Step 3 :- Assign Company Code to Company

Sap Menu Path :- SPRO –> IMG –> Enterprise Structure –> Assignment –> Financial Accounting –> Assign Company Code to Company

Transaction Code :- OX16

 Step 4 :- Define Business Area

 SAP Menu Path :- SPRO –> IMG –> Enterprise Structure –> Definition –> Financial Accounting –> Define Business Area

Transaction Code :- OX03

 Step 5 :- Define Functional Area

 SAP Menu Path :- SPRO –> IMG –> Enterprise Structure –> Definition –> Financial Accounting –> Define Functional Area

 Step 6 :- Define Credit Control Area

 SAP Menu Path :- SPRO –> IMG –> Enterprise Structure –> Definition –> Financial Accounting –> Define Credit Control Area

Transaction Code :- OB45

 Step 7 :- Assign Company Code to Credit Control Area

Sap Menu Path :- SPRO –> IMG –> Enterprise Structure –> Assignment –> Financial Accounting –> Assign Company Code to Credit Control Area

Financial Accounting Global Settings Configuration Steps 

Step 1 :- Define Fiscal year

Step 2 :-  Assign Company Code to Fiscal Year variant

Step 3 :- Define variant for opening Posting period

Step 4 :-  Define Variant for open and close posting period

Step 5 :-  Assign Variant to Company code

Step 6 :- Define Field status variant

Step 7 :-  Assign Company code to Field Status Variants

Step 8 :- Define Posting Keys

Step 9 :- Define Document types

Step 10 :- Define Document Number Range

Step 11 :- Define Tolerance group for Users

Step 1 :- Define Fiscal year

SAP Path :- SPRO –> IMG –> Financial Accounting –> Financial Accounting Global Settings –> Fiscal Year –> Maintain Fiscal year variant

Transaction Code :- OB29

 Step 2 :- Assign Company Code to Fiscal Year variant

SAP Path :- SPRO –> IMG –> Financial Accounting –> Financial Accounting Global Settings –> Fiscal Year –> Assign Company Code to Fiscal Year variant

Transaction Code :- OB37

Step 3 :- Define variants for opening Posting period

SAP Path :- SPRO –> IMG –> Financial Accounting –> Financial Accounting Global Settings –> Documents –> Posting Period –> Define variants for opening Posting period

Transaction Code :- OBBO

 Step 4 :- Define Variant for open and close posting periods

SAP Path :- SPRO –> IMG –> Financial Accounting –> Financial Accounting Global Settings –> Documents –> Posting Period –> open and close posting periods

Transaction Code :- OB52

 Step 5 :- Assign Variants to Company code

SAP Path :- SPRO –> IMG –> Financial Accounting –> Financial Accounting Global Settings –> Documents –> Posting Period –> Assign Variants to Company code

Transaction Code :- OBBP

 Step 6 :- Define Field status variants

SAP Path :- SPRO –> IMG –> Financial Accounting –> Financial Accounting Global Settings –> Documents –> Line Item –> Controls –> Define Field status variants 

Transaction Code :- OBC4

Step 7 :- Assign Company code to Field Status Variants 

SAP Path :- SPRO –> IMG –> Financial Accounting –> Financial Accounting Global Settings –> Documents –> Line Item –> Controls –>   Assign Company code to Field Status Variants

Transaction Code :- OBC5

Step 8 :- Define Posting Keys

SAP Path :- SPRO –> IMG –> Financial Accounting –> Financial Accounting Global Settings –> Documents –> Line Item –> Controls –>   Define Posting Keys

Transaction Code :- OB41

 Step 9 :- Define Document types

SAP Path :- SPRO –> IMG –> Financial Accounting –> Financial Accounting Global Settings –> Documents –> Document Header –> Define Document types

Transaction Code :- OBA7

Step 10 :- Define Document Number Range

SAP Path :- SPRO –> IMG –> Financial Accounting –> Financial Accounting Global Settings –> Documents –> Document Header –>Document Number Range –> Define Document Number Range

Transaction Code :- OBA7

Step 11 :- Define Tolerance group for Users

SAP Path :- SPRO –> IMG –> Financial Accounting –> Financial Accounting Global Settings –> Documents –> Line Item –> Controls –>   Define Tolerance group for Users

Transaction Code :- OBA4

General Ledger Accounting Configuration Steps

General Ledger Accounting :- The General ledger accounting is the complete record of all business transactions. 

GL Accounting Configuration Steps :-

• Step-1 :- Define Chart of Accounts
• Step-2 :-Assign Company Code to Chart of Accounts
• Step 3 :- Define Account Groups
• Step 4 :- Define Retained Earning Account
• Step 5 :- Creation of GL Master Records
• Step 6 :- Define Tolerance Group for GL Account

Step 1 :- Define Chart of Accounts

SAP Path :- SPRO -> IMG –> Financial accounting –> General ledger Accounting –> GL Accounts –> Master Data–> Preparations –> Edit Chart of Accounts list

Transaction Code :- OB13

Step-2 :-Assign Company Code to Chart of Accounts

SPRO -> IMG –> Financial accounting –> General ledger Accounting –> GL Accounts –> Master Data–> Preparations –> Assign Company Code to Chart of Accounts

Transaction Code :- OB62

Step 3 :- Define Account Groups

SAP Path :- SPRO -> IMG –> Financial accounting –> General ledger Accounting –> GL Accounts –> Master Data–> Preparations –> Define Account Groups

Transaction Code :- OBD4

Step 4 :- Define Retained Earnings Account 

SAP Path :- SPRO -> IMG –> Financial accounting –> General ledger Accounting –> GL Accounts –> Master Data–> Preparations –> Define Retained Earnings Account 

Transaction Code :- OB53

Step 5 :- Creation of GL Master Records

SAP Path :- SPRO -> IMG –> Financial accounting –> General ledger Accounting –> GL Accounts –> Master Data–> Preparations –> GL Account Creation and Processing –> Edit G/L Account 

Transaction Code :-  FS00

Step 6 :- Define Tolerance Group for GL Account

SAP Path :- SPRO -> IMG –> Financial accounting –> General ledger Accounting –> Business transactions –> Open Item Clearing –> Clearing Differences –> Define Tolerance Groups for GL Accounts

Transaction Code :- OBA0

Accounts Payable Configuration Steps :-

Accounts Payable Overview :- Accounts Payable is a Subsidiary Ledger account. Accounts payable records and manages accounting data for all vendors. When  postings are made in Accounts Payable simultaneously recorded in the General ledger account.

Steps in Accounts Payable Configuration are as follows

1. Step 1 :- Creation of Vendor Account Groups
2. Step 2 :- Create number range for vendors account 
3. Step 3 :- Assign number range to vendor account groups
4. Step 4 :- Define tolerance group for vendor
5. Step 5 :- Creation of vendor master
6. Step 6 :- Creation of GL as Reconciliation Accounts
7. Step 7 :- Document types and no. ranges
8. Step 8 :- Vendor Payment Terms
9. Step 9 :- Automatic Payment Program

Step 1 :- Creation of Vendor Account Groups

SAP Path :SPRO –> Financial accounting –> Accounts Receivable and Accounts Payable –> Vendor Accounts –>Master data –> preparation for creating vendor master data –> Define Account Groups with Screen Layout (Vendors)

Transaction Code :- OBD3

Step 2 :- Create number ranges for vendors account

SAP Path :- SPRO –> Financial accounting –> Accounts Receivable and Accounts Payable –> Vendor Accounts –> Master data –> Preparation for creating vendor master data –> Create number ranges for vendors account

Transaction Code :- XKN1

 Step 3 :- Assign Number Range to Vendor Account Groups

SAP Path :SPRO –> Financial accounting –> Accounts receivable and accounts payable –> Vendor Accounts –>Master data –> preparation for creating vendor master data –> Assign Number Range to Vendor Account Groups

Transaction Code :- OBAS

Step 4 :- Define tolerance group for vendors

SAP Path :SPRO –> Financial accounting –> Accounts receivable and accounts payable –> Business transactions –> Outgoing payments –> Manual outgoing payments –> Define Tolerances (Vendors)

Transaction Code :- OBA3

 Step 5 :- Creation of Vendor Master

SAP Path :- SAP Menu –> Accounting –> Financial Accounting –> Account payable –> Master Records –> Maintain Centrally –> Create 

Transaction Code :- XK01

 

Step 6 :- Creation of GL as Reconciliation Accounts ( Sundry Creditors )

SAP Menu Path:- SAP Menu  –> Accounting –> Financial Accounting –> General Ledger –> Master Records –> Individual Processing  –> Create Centrally

Transaction Code :- FS00

Step 7 :-Document types and no. Ranges  ( KZ, KR, KA )

SAP Menu Path :- SPRO –> IMG –>Financial Accounting –>Financial Accounting Global Setting –>Document–>Document Number ranges –> Define Document Number Ranges

Transaction Code :- FBN1

Step 8 :- Vendor Payment Terms

SAP Menu Path:- IMG –> Financial Accounting –> Accounts Receivable & Accounts Payable –> Business Transactions –> Outgoing Invoices/Credit Memos –> Maintain Terms of Payment

Transaction Code :- OBB8

Step 9 :- Automatic Payment Program

Menu Path:- IMG –> Financial Accounting –> Accounts Receivable & Payable –> Business Transactions –> OutgoingPayments –> Automatic Outgoing Payments –> Payment method/Bank Selection for Payment program

Transaction Code :- FBZP

Accounts Receivable

SAP FICO Accounts Receivable Configuration Steps

• Step 1 :- Creation of Customer Account Group
• Step 2 :- Create Number Ranges for for Customer Accounts
• Step 3 :- Assign Number range to Customer Accounts groups
• Step 4 :- Define tolerance group for Customer
• Step 5 :- Creation of GL Reconciliation Accounts ( Sundry Debtors )
• Step 6 :- Creation of Customer master records
• Step 7 :- Document types and Number range ( DR, DZ, DA )
• Step 8 :- Bill of Exchange
• Step 9 :- Dunning

Step 1 :- Creation of Customer Account Group :- 

SAP Path :- SPRO –> Financial Accounting –> Accounts Receivable and Accounts Payable –> Customer Accounts –> Master Data –> Preparation for creating customer master data –> Define Account Groups with Screen layout ( Customer )

Transaction Code :- OBD2

Step 2 :- Create Number Ranges for  Customer Accounts

SAP Path :- SPRO –> Financial Accounting –> Accounts Receivable and Accounts Payable –> Customer Accounts –> Master Data –> Preparation for creating customer master data –> Create Number Ranges for Customer Accounts

Transaction Code : XDN1

Step 3 :- Assign Number range to Customer Accounts groups :-

SAP Path :- SPRO –> Financial Accounting –> Accounts Receivable and Accounts Payable –> Customer Accounts –> Master Data –> Preparation for creating customer master data –> Assign Number ranges to Customer Accounts groups

T Code :- SPRO

Step 4 :- Define tolerance group for Customer :-

SAP Path :- SPRO –> Financial Accounting –> Accounts Receivable and Accounts Payable –> Business Transactions –> Incoming payments –> Manual incoming payments –> Define Tolerance ( Customer )

T Code :- OBA3

Step 5 :- Creation of GL Reconciliation Accounts ( Sundry Debtors )

SAP Menu Path:- SAP Menu  –> Accounting –> Financial Accounting –> General Ledger –> Master Records –> Individual Processing  –> Create Centrally

Transaction Code :- FS00

Step 6 :- Creation of Customer master records

SAP Menu Path :- SAP Menu –> Accounting –> Financial Accounting –> Accounts Receivable –> Master Records –> Create

T Code :- XD01

Step 7 :- Document types and Number range ( DR, DZ, DA )

SAP Menu Path :- SPRO –> IMG –>Financial Accounting –>Financial Accounting Global Setting –>Document–>Document Number ranges –> Define Document Number Ranges

Transaction Code :- FBN1

Step 8 :- Bill of Exchange :-

SAP Menu Path :- SPRO –> IMG –> Financial Accounting –> Bank Accounting –> Business Transactions –> Bills of Exchange Transactions –> Bills of exchange receivable –> Define Alternative recon a/c for bills of exchange

Transaction Code :- OBYN

Step 9 :- Dunning :-

SAP Path :- SPRO –> Financial Accounting –> Accounts Receivable and Accounts Payable –> Business Transactions –>Dunning –> Basic Settings for Dunning –> Define Dunning Area

Transaction Code :- OB61

Asset Accounting

Asset Accounting Overview:- Asset Accounting is an important module in SAP and manages assets of an organisation by master records. Asset accounting is a sub ledger to the SAP FI module for managing the Asset records.

 SAP Asset Accounting Configuration Steps :-

• Step 1 :- Copy Reference Chart of Depreciation/ Depreciation Area
• Step 2 :- Assign Chart of Depreciation to Company Code
• Step 3 :- Specify Account Determination
• Step 4 :- Create screen Layout Rule
• Step 5 :- Define Number range Interval
• Step 6 :- Define Asset Classes
• Step 7 :- Determine Depreciation area in the Asset Class
• Step 8 :- Assignment of General Ledger Accounts
• Step 9 :- Specify Intervals and Posting Rules
• Step 10 :- Define Screen Layout for Asset master data
• Step 11 :- Define Screen Layout for Asset Depreciation Areas
• Step 12 :- Define Depreciation Methods
• Step 13 :- Maintain Depreciation keys
• Step 14 :- Depreciation Run
• Step 15 :- Create Asset Master

 Step 1 :- Copy Reference Chart of Depreciation/ Depreciation Area

SAP Menu Path :- SPRO –> Financial Accounting –> Asset Accounting –> Organisational Structure –> Copy Reference Chart of Depreciation/ Depreciation Area

T code :- EC08

Step 2 :- Assign Chart of Depreciation to Company Code

SAP Menu Path :- SPRO –> Financial Accounting –> Asset Accounting –> Organisational Structure –>Assign Chart of Depreciation to Company Code

T Code :- OAOB

 Step 3 :- Specify Account Determination

SAP Menu Path :- SPRO –> Financial Accounting –> Asset Accounting –> Organisational Structure –> Asset Classes –> Specify Account Determination

 Step 4 :- Create screen Layout Rule

SAP Menu Path :- SPRO –> Financial Accounting –> Asset Accounting –> Organisational Structure –> Asset Classes –> Create screen Layout Rule

 Step 5 :- Define Number range Interval

SAP Menu Path :- SPRO –> Financial Accounting –> Asset Accounting –> Organisational Structure –> Asset Classes –> Define Number range Interval

T Code :- AS08

 Step 6 :- Define Asset Classes

SAP Menu Path :- SPRO –> Financial Accounting –> Asset Accounting –> Organisational Structure –> Asset Classes –> Define Asset Classes

T Code :- OAOA

Step 7 :- Determine Depreciation area in the Asset Class

SAP Menu Path :- SPRO –>IMG –> Financial Accounting –> Asset Accounting –> Valuation –> Determine Depreciation area in the Asset Class

T Code :- OAYZ

 Step 8 :- Assignment of General Ledger Accounts

SAP Menu Path :- SPRO –>IMG –> Financial Accounting –> Asset Accounting –> Integration with General Ledger –> Assign General Ledger Accounts

T Code :- AO90

 Step 9 :- Specify Intervals and Posting Rules

SAP Menu Path :- SPRO –>IMG –> Financial Accounting –> Asset Accounting –> Integration with General Ledger –> Post Depreciation to General Ledger –> Specify Intervals and Posting Rules

T Code :- OAYR

 Step 10 :- Define Screen Layout for Asset Master data

 SAP Menu Path :- SPRO –>IMG –> Financial Accounting –> Asset Accounting –> Master Data –> Screen Layout –> Define Screen Layout for Asset Master data

 Step 11 :- Define Screen Layout for Asset Depreciation Areas

 SAP Menu Path :- SPRO –>IMG –> Financial Accounting –> Asset Accounting –> Master Data –> Screen Layout –> Define Screen Layout for Depreciation Areas

T Code :-  AO21

 Step 12 :- Define Depreciation Methods

• Define Base methods
• Define Decline Balance Methods
• Define Multi Level methods

SAP Menu Path :- SPRO –>IMG –> Financial Accounting –> Asset Accounting –>Depreciation –> Valuation methods –>Depreciation  Key –> Calculation methods –> Define Base methods

SAP Menu Path :- SPRO –>IMG –> Financial Accounting –> Asset Accounting –>Depreciation –> Valuation methods –>Depreciation  Key –> Calculation methods –> Define Decline Balance Methods

SAP Menu Path :- SPRO –>IMG –> Financial Accounting –> Asset Accounting –>Depreciation –> Valuation methods –>Depreciation  Key –> Calculation methods –> Define Multi Level methods

 Step 13 :- Maintain Depreciation keys

SAP Menu Path :- SPRO –>IMG –> Financial Accounting –> Asset Accounting –>Depreciation –> Valuation methods –>Depreciation  Key –> Maintain Depreciation Key

T Code :- AFAMA

 Step 14 :- Depreciation Run :-

SAP Menu Path :- SPRO –>IMG –> Financial Accounting –> Fixed Assets –> Periodic Processing –> Depreciation Run –> Execute

T Code :- AFAB

 Step 15 :- Create Asset Master

SAP Menu Path :-  SAP Menu –> Accounting –> Financial Accounting –> Fixed Assets –> Asset –> Create

T Code :- AS01

 Bank Accounting

Bank Accounting :- Bank account is an important module in SAP fi which  is used to handle accounting transactions  that you process with your bank. Bank Accounting  includes the management of organisation Bank Master data and processing of incoming and outgoing payments.

Bank Accounting Configuration Steps :-

Step 1 :- Define House Banks

Step 2 :-  Create Bank Key

Step 3 :- Electronic Bank Statement Configuration

• Creation of Accounts Symbols
• Assign Accounts to Accounts symbols
• Create Keys for Posting Rules
• Define Posting Rules
• Create Transaction Type
• Assign External Transaction Types to Posting Rules
• Assign Bank Accounts to Transaction Types

Step 4 :- Manual Bank Statement

Step 5 :- Define Posting Keys  and Posting Rules for Check Deposit

Step 6 :- Create and Assign Business Transactions

Step 7 :- Define Variants for Check Deposit

Step 1 :- Define House Banks

Menu Path :- SPRO –> IMG –> Financial Accounting –> Bank Accounting –> Bank Accounts –> Define house banks

Transaction Code :- FI12

Step 2 :-  Create Bank Key

SAP Menu Path :- SAP Menu –> Accounting –> Financial Accounting –> Accounts Receivable –> Master Records –> Bank –> Create ( Create bank Key )

Transaction Code :- FI01

Step 3 :- Electronic Bank Statement Configuration

Sap Menu Path :- SPRO –> IMG –> Financial Accounting –> Bank Accounting –> Business Transactions –> Payment Transactions –> Electronic Bank Statement –> Make Global Settings for Electronic Bank Statement

• Creation of Accounts Symbols
• Assign Accounts to Accounts symbols
• Create Keys for Posting Rules
• Define Posting Rules
• Create Transaction Type
• Assign External Transaction Types to Posting Rules
• Assign Bank Accounts to Transaction Types

Step 4 :- Manual Bank Statement :-

Sap Menu Path :- SPRO –> IMG –> Financial Accounting –> Bank Accounting –> Business Transactions –> Payment Transactions –> Manual Bank Statement –> Create and Assign Business transactions

Step 5 :- Define Posting Keys  and Posting Rules for Check Deposit

Sap Menu Path :- SPRO –> IMG –> Financial Accounting –> Bank Accounting –> Business Transactions –> Check Deposit –> Define Posting Keys  and Posting Rules for Check Deposit

Step 6 :- Create and Assign Business Transactions

Sap Menu Path :- SPRO –> IMG –> Financial Accounting –> Bank Accounting –> Business Transactions –> Check Deposit –> Create and Assign Business Transactions

Step 7 :- Define Variants for Check Deposit

Sap Menu Path :- SPRO –> IMG –> Financial Accounting –> Bank Accounting –> Business Transactions –> Check Deposit –>  Define Variants for Check Deposit