Client, company and company code
Once a business has decided to use the SAP FI(Financial Accounting) Module, there are several Configurations prerequisite steps that must be completed.Determining the organizational structure is one of the first steps in setting up the business functions in SAP as well as your reporting requirements.
The Organizational structure is created by defining the organizational units consisting of the following:
Client
Company
Company Code
Business Area
A Client is the highest unit within an SAP system and contains Master records and Tables. Data entered at this level are valid for all company code data and organizational structures allowing for data consistency. User access and authorizations are assigned to each client created. Users must specify which client they are working in at the point of logon to the SAP system.
A Company is the unit to which your financial statements are created and can have one to many company codes assigned to it. A company is equivalent to your legal business organization. Consolidated financial statements are based on the company’s financial statements. Companies are defined in configuration and assigned to company codes. Each company code must use the same COA( Chart of Accounts) and Fiscal Year. Also note that local currency for the company can be different.
Company Codes are the smallest unit within your organizational structure and is used for internal and external reporting purposes. Company Codes are not optional within SAP and are required to be defined. Financial transactions are viewed at the company code level. Company Codes can be created for any business organization whether national or international. It is recommended that once a Company Code has been defined in Configuration with all the required settings then other company codes later created should be copied from the existing company code. You can then make changes as needed. This reduces repetitive input of information that does not change from company code to company code as well as eliminate the possibility of missed data input.
When defining company codes, the following key areas must be updated:
Company Code Key- identifies the company code and consists of four alpha-numeric characters. Master data and business transactions are created by this key.
Company Code Name- identifies the name of the business organization within your organizational structure.
Address- identifies the street address, city, state, zip code for the company code created. This information is also used on correspondence and reports.
Country- identifies the country to which your business is based. Country codes within SAP are based on ISO Standards.
Country currency- identifies the local currency for the company code that you have defined.
Language- identifies the language to be used for you company code and is also used for text in your documents. SAP unlike other applications, offers over thirty languages including EN( English) , ES (Spanish), FR (French), DE (German), EL (Greek), IT(Italian), AR( Arabic), ZH (Chinese) , SV (Swedish) , and JA (Japanese) to name a few.
Showing posts with label fico Primary configuration considerations. Show all posts
Showing posts with label fico Primary configuration considerations. Show all posts
Friday, November 23, 2007
fico Primary configuration considerations
Subscribe to:
Posts (Atom)
Blog Archive
-
▼
2009
(81)
-
▼
June
(81)
- Lists in Unicode Systems
- The File Interface in Unicode Programs
- Character String and Byte String Processing in Uni...
- Structure Enhancements and Unicode Programs
- Structure Typing in Unicode Programs
- Conversion of Structures in Unicode Programs
- Access to memory sequences in Unicode programs
- Offset and Length Specifications in Unicode Programs
- Alignment in Unicode Systems
- Operand Types in Unicode Programs
- Names in Unicode Programs
- Comments and Literals in Non-Unicode Programs
- Differences between Unicode and Non-Unicode Programs
- Unicode - Overview
- Statements in Class and Interface Pools
- Statements for Defining Classes and Interfaces
- ABAP Objects - Keywords
- Inheritance Events
- Inheritance and Events
- Inheritance and Instantiation
- Inheritance and Constructors
- Inheritance and Static Components
- Inheritance and the Component Namespace
- Inheritance and Visibility
- Inheritance and Interfaces
- Inheritance and Polymorphism
- Abstract and Final Methods and Classes
- Redefining Methods
- Inheritance
- Definition of Classes and Interfaces
- Object Orientation
- CLASS-METHODS - FOR EVENT
- CLASS-METHODS - class_constructor
- CLASS-METHODS - RETURNING
- METHODS - IMPORTING, EXPORTING, CHANGING, RAISING
- CLASS-METHODS - IMPORTING, EXPORTING, CHANGING, RA...
- CLASS-METHODS
- Kernel Methods
- The C Destructor in Methods
- Interface Parameters in Methods
- Data Types and Constants
- Events In Components of classes
- Constructors In Components of Classes
- Methods in Components of classes
- Attributes
- Visibility Sections in Classes
- Components of Classes
- Classes
- ABAP Objects
- ABAP Programming Language - Overview
- Example of a Logical Database
- Logical Databases
- Position of the Basis System Within the R/3 System
- Running ABAP Programs
- Calling ABAP Dialog Modules
- Data Types in the ABAP Dictionary
- Pushbuttons on the Screen
- Processing Input/Output Fields
- Processing Screen
- Screens
- ABAP User Dialogs
- Reduce the Database Load
- Minimize the Search Overhead
- Minimize the Number of Data Transfers
- Minimize the Amount of Data Transferred
- Keep the Result Set Small
- Performance Notes
- Committing Database Changes
- Inserting or Changing Lines
- Deleting Lines
- Changing Line
- Inserting Lines into Tables
- Changing Data
- Reading Data
- Open SQL
- Checking User Authorizations
- Accessing the Database in the R/3 System
- ABAP Database Access
- ABAP HR Programming
- ABAP Tutorials for Beginners
- Download Abap certification material
-
▼
June
(81)
