Monday, December 17, 2012

Controlling area


Controlling area
Controlling area is an organizational unit from the Accounting component in the R/3 System, used to represent a closed system for cost accounting purposes.
In the standard R/3 System, the controlling area constitutes the framework for planning, allocation and monitoring of costs.
One controlling area

When we have one controlling area:
v  The same operative chart of accounts is used.
v  Each enterprise entity in the controlling area only uses the specific accounts it requires. We can use a country chart of accounts to record country-specific requirements.
v  Posting periods are always the same. Special periods are, however, an exception.
v  We must agree on controlling master data, for example for cost elements, activity types, cost centers. Uniform procedures should exist for maintaining master data.
v  Work on period-end closing must be coordinated (planned and actual work). We must agree on a time schedule for work on period-end closing. We must define how costs are allocated and prices are calculated for services per cost center / cost center group
v  We have a choice of three currencies. Controlling area currency, object currency and transaction currency. For cost accounting for several company codes and several countries, the object currency corresponds to the transaction currency.
v  We have unlimited use of the project management function. We can work with one project definition, one project structure plan and one network. We have unlimited use of project management and reporting functions.
v  We have unlimited use of the cost distribution functions (cost center assessment and internal activity allocation.
Several controlling areas
We can define several controlling areas if we do not want to merge enterprise units in cost accounting. Ensure that the organizational structure provides for harmonized procedures and structures for cost accounting
When we have more than on controlling area:
v  We can define a separate operative chart of accounts for each controlling area. We can use the group chart of accounts for consolidation.
v  We can work with different posting periods. Controlling areas that are assigned to the same operating concern use the same posting periods.
v  Work on period-end closing do not need to be coordinated (planned and actual work).
v  We define controlling master data such as cost elements, activity types, cost centers for each specific controlling area.
v  We must ensure that the organizational structure caters for comprehensive project management. We can work with one project definition, one project structure plan and one network for each controlling area. We have unlimited use of project management and reporting functions within each controlling area. We may use the Executive Information System (EIS) if we would like project reporting to cover all controlling areas (cost elements, cost centers, orders).
v  We can use the Special Purpose Ledger (FI-SL) or Consolidation (EC-CS) components to draw up reports for all controlling areas. Ensure that we consolidate the appropriate elements from different controlling areas.




Monday, December 3, 2012

Chart of Depreciation

Depreciation:
A reduction in the value of an asset with the period of time, due in particular to wear and tear.
 Types of Depreciation:
v Straight line method without basis reduction: 
v Straight line method with basis reduction: 
v Diminishing balance method


Chart of  Depreciation:
Charts of depreciation are used in order to manage various legal requirements for the depreciation and valuation of assets. These charts of depreciation are usually country-specific and are defined independently of the other organizational units. A chart of depreciation, for example, can be used for all the company codes in a given country 
Country-Specific Charts of Depreciation
In the simplest scenario, all of wer company codes are in the same country and are subject to the same legal requirements for asset valuation, meaning that we only need one chart of depreciation.



Integration
Chart of Depreciation integration we can do at two levels.
v Company code level
v Chart of account level

Company Code/Chart of Depreciation
We have to assign each company code defined in Asset Accounting to exactly one chart of depreciation. In the interests of keeping asset values uniform in our company, we should restrict the number of charts of depreciation used to as few as possible. Company codes in countries with the same valuation rules or company codes of a certain industry sector generally use the same chart of depreciation.

Chart of Accounts/Chart of Depreciation
The assignment of a company code to a chart of accounts is independent from its assignment to a chart of depreciation. This means that several company codes can use the same chart of accounts, although they have different charts of depreciation (and vice versa).

Types of Errors


http://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/blank.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/space.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gif
http://help.sap.com/saphelp_46c/helpdata/en/images/blank.gifDifferent types of  errors in SAP
Master data error
Configuration error
Transaction error           
System error

MARA Table


MARA : General Material Data (Transparent Table)

MARA is a standard SAP Table available within R/3 SAP systems depending on your version and release level. Below is the standard documentation available for this table and a few details of the fields which make up this table. You can view this information and more if you enter the Table name MARA into the relevant SAP transaction such asSE11 or SE80. You can also view the data contained in this database table via these transactions or alternatively use transaction SE16

Delivery Class = A - Application table containing master and transaction data

Important Fields in MARA Table
MANDT       Client
MATNR       Material Number
http://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/blank.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/space.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gif
http://help.sap.com/saphelp_46c/helpdata/en/images/blank.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/blank.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/space.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gif
http://help.sap.com/saphelp_46c/helpdata/en/images/blank.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/blank.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/space.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gifhttp://help.sap.com/saphelp_46c/helpdata/en/images/nselect.gif
http://help.sap.com/saphelp_46c/helpdata/en/images/blank.gifERSDA        Creation Date
ERNAM       Name of person who created.
MTART        Material Type.
MATKL        Material Group.
MEINS         Base Unit of Measure.
ZEINR          Document Number.
ZEIAR          Document Type.
WRKST       Basic Material.
NTGEW       Net Weight.
VOLUM       Volume.
VOLEH        Volume Unit.
SPART         Division.
KZKFG       Configuration Material.
VHART       Shipping Material Type.
MAGRV      Material Group Shipping Material.
DATAB       Valid from Date.
ATTYP        Material Category.
PMATA       Pricing reference material. 


Friday, November 30, 2012

Testing in SAP

TYPES OF TESTING IN SAP FINANCIAL

Unit Testing 
When you test every single document is called unit testing.

String Testing 
One transaction full activity is called string testing . For example Vendor invoice, goods received and vendor payment.

Integration Testing 
It is purely with other modules and we have to check whether the FI testing is working with other related modules or not.

Regression Testing 
Testing for whole database. Bring all the data into another server and do the testing is called regression.

Thursday, November 15, 2012

Abbreviations in SAP



ABAP Advanced Business Application Programming
APJ Asia Pacific Japan
BCM Bank communication management
BAI Banking And Administrative institute
CO-PA Controling Production Accounting
CO-CCA Controlling Cost Centre Accounting
CO-PCA COntrolling Profit Center Accounting
WBS Work Breakdown Structure on the Project system.
CRM Customer relationship management
EC-PCA  Enterprise Controlling Profit Centre Accounting
EMEA Europe middle east Africa 
FAGLGLEXTG Financial Accounting General Ledger Flexible Table.
SOP Sales Operation Planning
SPRO System Project Reportery Object
SME Subject Matter Experts
POS Point of sale
SDN SAP Developer Network
SCN SAP Community Network
PLM Product lifecycle management
POA Performance optimization applications
SCM Supply chain management
SAP Systems, Applications, Products in Data Processing (German: Systeme, Anwendungen, Produkte)
LIV Logistic Invoice Variances
SBU Strategic Business Units

Tuesday, October 23, 2012

Master Data


What is Master Data?

Master data is any information that is considered to play a key role in the core operation of a business. It may include data about vendors, materials, customers, banks, general ledger accounts, inventory, suppliers, analytics and more. Master data is shared by all AOI groups across an organization and is stored on one system.