Tmerpsapbase12 V 0

Systems Application Program
FICO ECC 6.O V
Application Reference Manual Basic Settings
Author: Nagarjuna J V
TMERP/SAP/BASE12_V 0 things possible.
Effort makes right
Table of Contents
Chapter 1.....................................................................................................................................................4 Landscape .................................................................................................................................................4 1.0.SAP Landscape....................................................................................................................................4 1.0.1.Development Server..........................................................................................................................4 1.0.1.1.Sandbox..........................................................................................................................................5 1.0.1.2.Golden Client..................................................................................................................................5 1.1.SAP Environment.................................................................................................................................5 1.2.Log into SAP system............................................................................................................................5 Chapter 2.....................................................................................................................................................8 Organization Structure...............................................................................................................................8 2.0.Need for an Organization Structure.....................................................................................................8 2.1.Organization Structure in SAP.............................................................................................................9 2.1.1.Client..................................................................................................................................................9 2.1.2.Operating Concern............................................................................................................................9 2.1.3.Company .........................................................................................................................................10 2.1.4.Company Code................................................................................................................................10 2.1.5.Business Area..................................................................................................................................11 2.1.6.Profit Centre.....................................................................................................................................11 2.2.Customization of Enterprise Structure..............................................................................................11 2.2.1.Define Company (Transaction Code: OX15)..................................................................................11 2.2.2.Definition of Company Code 2.2.3.Definition of Business Area (Transaction Code: OX02)............................................................16 (Transaction Code: OX03)............................................................17
2.2.4.Assign Company Code to Company (Transaction Code: OX16).................................................18 Chapter 3...................................................................................................................................................20 Basic Settings...........................................................................................................................................20 3.0Maintain Fiscal Year Variant (Transaction Code: OB29)...................................................................20 3.0.1.Assign Company Code to a Fiscal Year Variant (Transaction Code: OB37)................................24 3.1Posting Periods...................................................................................................................................26 3.1.2.Assign Variants to Company Code 3.1.3.Open & Close Posting Periods (Transaction Code: OBBP)............................................27
(Transaction Code: OB52)........................................................27
Page 2 of 37
Partha Institute for ERP Education Edited by
Effort makes right
3.2Account Types.....................................................................................................................................28 3.3Field Status Variant.............................................................................................................................29 3.4Document Types and Number Ranges...............................................................................................30 3.5Tolerance Groups................................................................................................................................36
Page 3 of 37
Effort makes right
Chapter 1
Landscape
1.0. SAP Landscape
Landscape is like a server system or like a layout of the servers or the architecture of the servers. Visually, SAP is divided into three different landscapes: Development server (DEV), Quality Assurance Server (QAS) and Production server (PROD). DEV would have multiple clients. For example 190- Sandbox, 100- Golden, 180- Unit Test.
QAS may again have multiple clients. For example 300- Integration Test, 700 to 710 Training.
PROD may have something like a 200 production. Pipeline is the environment where the configuration in the development system is moved to the QAS & finally to the production system. The whole idea is to ensure that the configuration of these systems is in sync at any point of time. This approach throws up the transport management system concept. Transport management system is the coordination of the movement of objects and configuration changes from the DEVSYS to the QAS and then to the Production system. Let us have a detail discussion about the above.
1.0.1.
Development Server
The consultant carries out the customization as per clients requirement in the development server. Each client coming under the development server is explained below:
Page 4 of 37
Effort makes right
1.0.1.1.Sandbox
The essence of sandbox is to test the configuration of the business processes of a company, especially at the inception of the project (before the Business Blueprint is signed). It can also serve as practice environment even after go live. Once we are satisfied about the configuration, the same is redone in the Golden client.
1.0.1.2.Golden Client
Here the actual configuration is done which is then transported to the test client.
1.1.
SAP Environment
a. SAP R/1
b. SAP R/2
c.
SAP R/3 (Real Time 3-Tier Architecture)
d. SAP ECC (Enterprise Central Component)
e. SAP EHP (Enhancement Package)
1.2.
Log into SAP system
Step 1: Double click on sap logon
icon.
Step 2: Place the cursor on Page 5 of 37
and click on select Log on Partha Institute for ERP Education Edited by
button.
Effort makes right
Step 3: Each server is identified with the combination of application server, system ID (server name), and system number.
Page 6 of 37
Effort makes right
Step 4: Give the username and the password. SAP supports 47 languages. To view the labels and screen contents in languages other than English enter the value in language field and press enter . The client for demo system is 800. The user ID gets locked if we provide wrong credentials for three times. In that case the password needs to be reset by the BASIS consultant.
Step 5: Select the second option and press enter SAP Easy Access screen.
(or) select confirm selection
for entering into the
Page 7 of 37
Effort makes right
Chapter 2
Organization Structure
2.0. Need for an Organization Structure
Every organization is collectively a representation of small units. Business organizations analyze the results of operations through financial statements and reports drawn through Management Information Systems. The financial statements have to be submitted to the legislative authorities of the country where the organization is located and by which it is governed. It may also be required to submit the same in the prescribed format to the banks, financial institutions, investors, tax authorities, to the stock exchanges if the company is listed in stock exchange. Therefore, the need for a defined organization structure is necessitated to ensure smoothness in conducting the operations.
Page 8 of 37
Effort makes right
2.1.
Organization Structure in SAP
Organization Structure in SAP system has following entities: i. ii. iii. iv. v. vi. Client Operating Concern Company Controlling Area Company Code Business Area or Profit Centre
2.1.1.
Client
The client is the highest level in the hierarchy of organization structure of SAP. Master data defined at this level reduces the redundancy in maintaining data across different levels of organizational units. The same can be used by multiple company codes. Each client is an independent unit with separate master records and a complete set of tables and data.
2.1.2.
Operating Concern
Page 9 of 37
Effort makes right
2.1.3.
Company
Company is an organizational unit which facilitates consolidation of financial results and hence, reports like Consolidated Profit and Loss account and Consolidated Balance Sheet can be drawn. Specifications or master data at this level cannot be maintained. Definition of company is optional and is necessitated when the concept of Group Company comes into picture.
2.1.4.
Company Code
This organizational unit serves the base for legal reporting. Specifications and master data defined at this level can be used exclusively for this company code. Multiple company codes can be created in SAP system. Assignment of company code to company is mandatory in case of group company.
Com pany
Partha G roup of Industries
Com pany Code
P arth a C lean ing S ystem s Ltd. (P)
Business Area
M um bai B ranc h O ffic e
D elhi B ranc h O ffic e
K olk ata S ales H y derabad P lant O ffic e
1.0 Illustration of single legal entity
Company
Partha Group of Industries
Company Code
Partha Cleaning Systems (P) Ltd.
India
Partha Education Systems Inc . US
JVN AG Berlin
Business Area
Mumbai Branch Office
Hyderabad Plant
Training Centre Washington
Training Centre Berlin
1.1 Illustration of Group Company
Page 10 of 37
Partha Institute for ERP Education
Edited by
Effort makes right
2.1.5.
Business Area
The organizational unit used for internal reporting is referred as business area. The basis for deciding a business area may be taken as either location of the manufacturing plant, warehouse, factory outlet, administrative office or operating product. The organization entity used in logistics modules i.e. material management, sales and distribution, and production planning is Plant. The same is configured as business area in Financial Information (FI) module. It is used while posting of transactions so as to enable drawing of financial statements. They can be used across company codes. Definition of business area is optional.
2.1.6.
Profit Centre
Profit centre is an organizational unit defined within controlling module. It is also a statistical cost object used for drawing financial statements at profit centre level. It is specified while posting transactions. In turn, the profit centre is assigned to the cost centre which is a real cost object. Lately, the organizations prefer to use profit centre instead of business area for drawing internal reporting. Detail discussion on profit centre will be taken in controlling module.
2.2.
Customization of Enterprise Structure Define Company (Transaction Code: OX15)
2.2.1.
Path
SAP Easy Access screen Tools Customizing IMG (Implementation Guide) Execute Project In short, enter the following transaction code in the command bar SPRO
Page 11 of 37
Edited by
Effort makes right
Step 1: Click on SAP Reference IMG
Path
Enterprise Structure Definition Financial Accounting Define Company IMG Activity
Page 12 of 37
Edited by
Effort makes right
Step 2: Enter the Company ID, Company Name, Street, PO Box, Postal Code, City, Country, and Currency. Click on Save after filling in all details
Page 13 of 37
Edited by
Effort makes right
Step 3: On saving, the system prompts for a transport request. This request is used to transport the customization settings from one server to another server. For the first time when a request is prompted, we have to create a request. From the next time, the system will store the request and depending upon the necessity, we may have to create a request. Once request is created, press enter or click on complete the transaction. to
Page 14 of 37
Edited by
Effort makes right
Information To open a new session

Click on or type /nor /o in the command bar. At a particular moment, maximum of six sessions can be opened. /n opens a new session with the simultaneous closure of current session while /o retains the current session and opens a new session.
To view table contents (Transaction code-SE16N)

When data is entered in the foreground and saved, it gets stored in the form of tables in the background. The information will be retrieved by the system whenever the user prompts for it. To view the content in the table, type /nse16n or /ose16n in the command bar. 1. System opens another interface. 2. Specify value (e.g. T880) in the Table Name field
3. In Global Company Data, specify value in the Company field. (e.g.100003) 4. Click on
Execute.
Transport Request (Transaction Code: SE10 or SE09)

Transport Request serves the purpose of copying data from one server to another server. While saving, if the request appearing in the dialogue box is not yours, click on new request where you can see all the transport requests created by various users. Select the request that you have created and a double click on request will bring back to the transport request dialogue box. Click on confirm selection .
To view transport request: Path:

1. Type SE10 in the command bar. 2. Transport Organizer dialogue box opens. 3. Specify User (in IDES system, by default value will be SAPUSER) 4. Mark Modifiable checkbox in Request Status tab 5. Click Display
Page 15 of 37
Edited by
Effort makes right
2.2.2. Definition of Company Code (Transaction Code: OX02)

Path:
SPRO SAP Reference IMG Enterprise Structure Definition Financial Accounting Edit, Copy, Delete, Check Company Code Click on IMG Activity
Procedure:
1. Click on Edit Company Code Data 2. Click on New Entries 3. Enter Company Code. This is a four digit element. To maintain consistency, numerical values are used. For example 1002 4. Enter Company Name, Additional data, City, Country, Currency, Language 5. Select Address 6. Enter Title as Company, Name (e.g. Master Systems Private Limited), Search Terms for identification (e.g. MSPL), Street address 7. Press Enter 8. Click or Click on Copy
.System displays message: Data was saved.
Page 16 of 37
Edited by
Effort makes right
Information How to view table name where data is saved?

While data is saved, Transport Request dialogue box appears. Click on object attributes code information is stored in T001. . The company
2.2.3. Definition of Business Area (Transaction Code: OX03)

Path:
SPRO SAP Reference IMG Enterprise Structure Definition Financial Accounting Define Business Area IMG Activity
Procedure:
1. New Entries
Page 17 of 37
Edited by
Effort makes right
2. Enter Business Area (e.g.1100) and Description (e.g. Chennai BA) 3. Click on save 4. Click on
System displays message: Data was saved
The data is stored in the TGSB table.
2.2.4. Assign Company Code to Company (Transaction Code: OX16)

Path:
Page 18 of 37
Edited by
Effort makes right
SPRO SAP Reference IMG Enterprise Structure Assignment Financial Accounting Assign Company Code to Company
Procedure
1. Click on Position 2. Specify your Company Code and press enter 3. Specify value in Assign Company 4.
System displays message: Data was saved.
Page 19 of 37
Edited by
Effort makes right
Chapter 3
Basic Settings
3.0 Maintain Fiscal Year Variant (Transaction Code: OB29)
The financial year of organization is called as fiscal year in SAP. Fiscal year consists of twelve normal or regular periods plus four special periods. Normal periods are used for posting regular transactions. Special periods are used for entering year end activity adjustments. The purpose of special periods is to identify and control year-end adjustments from regular transactions. These are also referred as virtual periods. When transactions are posted with special periods system automatically updates those figures to the last period of fiscal year.
Fiscal year is of two types: (a) Calendar year: e.g. January to December (b) Non calendar year: e.g. June to July, October to September, and April to March
The same is also classified in other way: (a) Year independent fiscal year (b) Year dependent fiscal year
Below are standard fiscal year variants: K4 V3 V6 V9 Calendar fiscal year April March July June October September
Page 20 of 37
Edited by
TMERP/SAP/BASE12_V 0 things possible. Special periods for adjustment are 13, 14, 15, and 16. 13 Recommendations of auditor
Effort makes right
14 Recommendations of legal advisor 15 Recommendations of CEO/CFO
Path:
SPRO SAP Reference IMG Financial Accounting (New) Financial Accounting Global Settings (New) Ledgers Fiscal Year and Posting Periods Maintain Fiscal Year Variant (Maintain Shortened Fiscal Year)
Procedure:
1. New Entries
2. Enter Fiscal Year Variant, Number of posting periods & special periods
3. Select Entry
4. Double click on
5. New Entries
6. Enter details of Month, Days, Period, & Year Shift
7. Click on
and save in your request.
For understanding purpose, let us take fiscal year 2011-12
Page 21 of 37
Edited by
Effort makes right
Page 22 of 37
Edited by
Effort makes right
The details are saved in T009.
Page 23 of 37
Edited by
Effort makes right
3.0.1. Assign Company Code to a Fiscal Year Variant (Transaction Code: OB37)
Path:
SPRO SAP Reference IMG Financial Accounting (New) Financial Accounting Global Settings (New) Ledgers Fiscal Year and Posting Periods Assign Company Code to a Fiscal Year Variant IMG Activity
Procedure:
1. Position
2. System displays information: No postings are possible without fiscal year variants. Ignore the
warning message and press Enter
3. Enter Company Code ( e.g. 1003)
4. Enter Fiscal Year Variant
5.
Page 24 of 37
Edited by
Effort makes right
Page 25 of 37
Edited by
Effort makes right
3.1 Posting Periods

Using this setting one can control posting of transactions to particular period.
3.1.1Define Variants for Open Posting Periods (Transaction Code: OBBO)

Path:
SPRO SAP Reference IMG Financial Accounting (New) Financial Accounting Global Settings (New) Ledgers Fiscal Year/ Posting Periods Posting Periods Define Variants for Open
Procedure:
1. New Entries
Page 26 of 37
Edited by
Effort makes right
2. Specify Variant (e.g. 7100) and Name (e.g. Posting period/variant for Asian Paints) 3.
3.1.2. Assign Variants to Company Code (Transaction Code: OBBP)

Path:
SPRO SAP Reference IMG Financial Accounting (New)Financial Accounting Global Settings (New) LedgersFiscal Year/ Posting PeriodsPosting PeriodsDefine Variants for Open
Procedure:
1. Position your Fiscal Year Variant
2. Enter the Company Code (e.g. 1003) 3. Press Enter

4.
3.1.3. Open & Close Posting Periods (Transaction Code: OB52)

Path:
SPRO SAP Reference IMG Financial Accounting (New) Financial Accounting Global Settings(New) Ledgers Fiscal Year And Posting Periods Posting Periods Open And Close Posting Periods
Procedure:
1. New Entries Page 27 of 37 Partha Institute for ERP Education Edited by
TMERP/SAP/BASE12_V 0 things possible. 2. Specify value for posting period variant 3. and save in your request.
Effort makes right
How to delete lock entries? (Transaction Code: SM12)

1. Enter transaction code SM12 in the command bar 2. Press List 3. Select Entry 4. Delete 5. Click
3.2 Account Types

As a part of period end activities, on the last day of every month the relevant posting period has to be enabled for posting of transactions. Every organization has business transactions which can be majorly classified into Asset, Vendor, Customer, Material & General ledger. In SAP, the same are configured as account types to enable control on posting of transactions. According to the needs of organization, a particular account type can be kept opened & remaining closed. Each account types use an abbreviation for easy identification: A Asset; D Debtors; K Creditors; M Material; S General Ledger; + - Include all above account types; V Contract Accounts. Note: Along with + which will open the period for all account types, we have to enter other account types individually. SAP recommends defining account types as per latter format since it promotes greater precision in posting transactions. For example, period is December
Var. A 7100 + 7100 A 7100 D 7100 K 7100 M 7100 S Page 28 of 37
To Account 999999999 999999999 999999999 999999999 999999999 999999999
From Fisc To Perio al Perio d 1 year d 2 Year 9 2011 13 2011 9 2011 13 2011 9 2011 13 2011 9 2011 13 2011 9 2011 13 2011 9 2011 13 2011 Partha Institute for ERP Education
From Fisca Peri l od 2 Year 13 2011 13 2011 13 2011 13 2011 13 2011 13 2011 Edited by
To Perio d 2 16 16 16 16 16 16
Year 2011 2011 2011 2011 2011 2011
TMERP/SAP/BASE12_V 0 things possible. Click and save in your request.
Effort makes right
Using account type indicator, periods can be opened or controlled at business transaction levels.
3.3 Field Status Variant

Field Status Variant controls the requirement of fields during posting of a business transaction. It consists of field status groups. Each group will have 80 fields relevant to following transactions: 1. 2. 3. 4. General data Additional account assignment Materials management Payment transactions Asset Accounting Taxes, etc.
5.
6.
Every entry in a group will have suppress, required entry, and optional status. Suppress indicates that the field will not appear in the screen. Required indicates that the field is mandatory for posting or parking a document. Optional indicates that the field exists in the screen but not mandatory. SAP by default, provides 80 fields while posting of a document (business transaction).
3.3.1. Create Field Status Variant (Transaction Code: OBC4)

Path:
SPRO SAP Reference IMG Financial Accounting (New) Financial Accounting Global Settings (New) Ledgers Fields Define Field Status Variants
Procedure:
Page 29 of 37
Edited by
TMERP/SAP/BASE12_V 0 things possible. 1. Select entry 1000 (standard group) 2. Select Copy as
Effort makes right
3. Specify Field Status Variant (e.g. 1003) and change Description as MSPL Basic Settings 4. Press Enter 5. Select Copy all. System generates Message: No. of dependant entries copied: 47 6. Click and save in your request.
Data is saved in T004.
3.3.2. Assign Company Code To Field Status Variant (Transaction Code: OBC5)
Path
SPRO SAP Reference IMG Financial Accounting (New) Financial Accounting Global Settings (New) Ledgers Fields Assign Company Code to Field Status Variant
Procedure 1. Position your Company Code 2. Assign Field status variant 3.

3.4 Document Types and Number Ranges

Document types are used to identify the types of business transaction. For example, SA KR KZ DR DZ General Ledger transaction Vendor Invoice Vendor Outgoing Payments Customer Invoice Customer Incoming Payments Partha Institute for ERP Education Edited by
Page 30 of 37
TMERP/SAP/BASE12_V 0 things possible. AF Asset Depreciation
Effort makes right
The document types are associated with document number ranges.
3.4.1. Define Document Types Code: OBA7)

Path:
(Transaction
SPRO SAP Reference IMG Financial Accounting (New) Financial Accounting Global Settings (New) Document Document Types Define Document Types For Entry View
Procedure:
1. Position required document type 2. Double click on document type, for example SA 3. Enter Number Range 1, and click on Number Range Information. You may also specify for which business transaction the number range can be utilized. 4. Enter Company Code 5. Click on Change Intervals and then on Insert Intervals 6. Enter Number, Year (validity date range for number range), From and To Number 7. Click on Insert or press Enter 8. Click on . System gives message:
The number range intervals are not included in automatic recording of customizing changes. Transport request should be generated manually by the consultant.
Page 31 of 37
Edited by
Effort makes right
9. Ignore message by pressing Enter Note:
System displays message: The changes were saved.
Do not mark Ext. (external field) check box as it will ask document number externally while saving document. If Ext. is not selected, the number range is internal. System automatically picks up document number sequentially from the document range provided.
3.4.2. Define New Document Type (Transaction Code: OB47)

Procedure:
1. New Entries 2. Specify Document Type 3. Specify Number Range. Mark account types allowed that are necessary 4. Mark reference number 5.
Data gets stored in T003.
3.4.3. Maintain Number Ranges (Transaction Code: FBN1)

Path:
Page 32 of 37
Edited by
Effort makes right
SPRO SAP Reference IMG Financial Accounting (New) Financial Accounting Global Settings (New) Document Document Number Ranges Documents in Entry View Define Document Ranges for Entry View
Procedure:
1. Specify Company Code 2. Click on Change Intervals
3. Click on Insert Interval
Page 33 of 37
Edited by
Effort makes right
4. Position required Document Type, for example SA 5. Double click on Document Type
6. Click on Number Range Information
Page 34 of 37
Edited by
Effort makes right
7. Enter Number, Year, From Number, and To Number 8. Enter and
9. System displays message. Ignore message and press Enter
Do not mark
Page 35 of 37
Edited by
Effort makes right
3.5 Tolerance Groups 3.5.1. Tolerances for Employees (Transaction Code: OBA4)
Path:
SPRO Financial Accounting (New) General Ledger Accounting (New) Business Transactions Open Item Clearing Clearing Differences Define Tolerance Groups for Employees
Procedure:
1. New Entries 2. Group and Currency are to be left blank, then it is referred as Null Tolerance Group
Give Company Code. Fill the value in the Amount per Document, Amount per Open Item Account Item, and Cash Discount per Line Item.
3. Mention Permitted Payment Differences in Revenue and Expense.
Page 36 of 37
Edited by
Effort makes right
4.
3.5.2. Define Tolerance Groups for G/L Accounts (Transaction Code: OBA0)
Procedure:
1. New Entries
2. Enter Description for Tolerance Group
3.
Page 37 of 37
Edited by

Tmerpsapbase12 V 0

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Tmerpsapbase12 V 0

Hochgeladen von

Copyright:

Verfügbare Formate

Systems Application Program

FICO ECC 6.O V

Application Reference Manual Basic Settings

TMERP/SAP/BASE12_V 0 things possible.

Effort makes right

(Transaction Code: OB52)........................................................27

Partha Institute for ERP Education Edited by

TMERP/SAP/BASE12_V 0 things possible.

Effort makes right

Partha Institute for ERP Education Edited by

TMERP/SAP/BASE12_V 0 things possible.

Effort makes right

Partha Institute for ERP Education Edited by

TMERP/SAP/BASE12_V 0 things possible.

Effort makes right

SAP R/3 (Real Time 3-Tier Architecture)

d. SAP ECC (Enterprise Central Component)

e. SAP EHP (Enhancement Package)

Log into SAP system

Step 1: Double click on sap logon

Step 2: Place the cursor on Page 5 of 37

TMERP/SAP/BASE12_V 0 things possible.

Effort makes right

Partha Institute for ERP Education Edited by

TMERP/SAP/BASE12_V 0 things possible.

Effort makes right

(or) select confirm selection

for entering into the

Partha Institute for ERP Education Edited by

TMERP/SAP/BASE12_V 0 things possible.

Effort makes right

Partha Institute for ERP Education Edited by

TMERP/SAP/BASE12_V 0 things possible.

Effort makes right

Organization Structure in SAP

Partha Institute for ERP Education Edited by

TMERP/SAP/BASE12_V 0 things possible.

Effort makes right

Partha G roup of Industries

Com pany Code

P arth a C lean ing S ystem s Ltd. (P)

M um bai B ranc h O ffic e

D elhi B ranc h O ffic e

K olk ata S ales H y derabad P lant O ffic e

1.0 Illustration of single legal entity

Partha Group of Industries

Partha Cleaning Systems (P) Ltd.

Partha Education Systems Inc . US

Mumbai Branch Office

Training Centre Washington

Training Centre Berlin

1.1 Illustration of Group Company

Partha Institute for ERP Education

TMERP/SAP/BASE12_V 0 things possible.

Effort makes right

Customization of Enterprise Structure Define Company (Transaction Code: OX15)

Partha Institute for ERP Education

TMERP/SAP/BASE12_V 0 things possible.

Effort makes right

Step 1: Click on SAP Reference IMG

Partha Institute for ERP Education

TMERP/SAP/BASE12_V 0 things possible.

Effort makes right