1. What are the five steps in the Sales Cycle and what Modules do they originate from?
* Sales Order : SD Module
* Deliver Note : SD Module
* Goods Issue : MM Module
* Billing Document : SD Module
* Receive Payment: FI Module
2. Of the five steps listed above, which ones generate accounting documents and what are they?
* Goods Issue: Debit COGS and Credit Inventory
* Billing Document: Debit Accounts Receivable and Credit Sales/Revenue
* Payment Receipt: Debit Cash and Credit Accounts Receivable
3. What are all the activities in the Sales Cycle?
Inquiries, Quotations, Sales Order Processing, Credit Management, Delivery Processing, Goods Issue Processing, Billing Document Processing, Incoming Payment Processing, Automated General Ledger Update
4. What is an Inquiry in the Sales Cycle?
An Inquiry is a document created in the Sales & Distribution module that represents a query from a customer or prospective customer.
5. What is a Quotation?
A Quotation is a document created in the Sales & Distribution module that records information about materials possibly desired by a customer or prospective customer. The material number, price and alternative items is usually included on a quotation.
6. What is a Sales Order?
A Sales Order is a contractual agreement between a Sales Organization and a customer concerning goods to be delivered or services rendered.
7. When a Sales Order is processed, the system automatically executes what functions?
The system automatically executes:
* Credit Checking
* Pricing
* Material Availability Checking
* Transfer requirements to Materials Requirements Planning (MRP)
* Shipping Point and Route Determination
8. What is a Delivery Note?
The Delivery Note is a document created in the Sales & Distribution module that initiates the shipping activities associated with delivering materials to a customer
9. What financial transaction occurs when the Delivery Note is processed?
A Delivery Note does not create a financial transaction in the General Ledger.
10. What is the purpose of a Goods Issue?
A Goods Issue is a document posted in the Materials Management module that is used as the source document for recording changes in stock levels associated with delivering materials to customers and for recording the financial impact of such transactions in the General Ledger.
11. What is a Billing Document?
A Billing Document is a document posted in the Sales & Distribution module, which supports the creation of Customer Invoices, Credit or Debit Memos, and the recording of the financial impact of these transactions in the General Ledger.
12. What accounting transaction occurs when a Billing Document is posted?
As a result of a Billing Document, integration to the Financial Accounting module occurs with the automatic creation of an Accounting Document containing the following accounting entries:
* Debit to the Customer Account and the appropriate General Ledger Reconciliation Account assigned to it.
* Credit to the appropriate General Ledger Revenue Account.
Tuesday, September 14, 2010
Procurement Cycle
1. Name the five major activities (in the order they occur) in the Procurement Cycle.
• Purchase Requisition (MM)
• Purchase Order (MM)
• Goods Receipt (MM)
• Invoice Verification (MM)
• Vendor Payment (FI)
2. What is a Purchase Requisition?
A Purchase Requisition is a document that identifies an organization’s demand for a product or service from an outside vendor. It is an internal document (i.e., it is not visible to the vendor or any other outside organization).
3. What are the two ways a Purchase Requisition can be created?
• Automatically as a result of a Materials Requirements Planning (MRP) run.
• Manually by a user.
4. What is a Purchase Order?
A Purchase Order is a legal contract between a buyer and a vendor. It lists the materials or services to be purchased on specified terms and conditions (quantity, price / pricing conditions, delivery date).
5. Name the four steps necessary for creation of a Purchase Order.
• Source Determination
• Vendor Selection
• Purchase Order Processing
• Purchase Order Follow-Up
6. What are the different types of goods movements?
Goods receipts, goods issues, and transfer postings.
7. What is Invoice Verification?
Invoice verification is the process of matching Vendor Invoices to the Purchase Order and Goods Receipt documents. For matched vendor invoices, a payable is automatically created in the FI General Ledger.
8. How is the Payment Program used to make Vendor Payments?
The Payment Program is set to maximize cash discounts when paying open vendor items. It creates a list of proposed vendor items to be paid and suggests payment methods for each proposed payment. The user has the ability to make any changes before payments are made.
Note: The payment program selection strategy (e.g., maximization of cash discounts) is configurable.
9. Name the three different types of Materials Management documents.
• Order documents
• Goods receipt documents
• Invoice Receipt documents
10. From which modules can the above documents be viewed?
• Order documents can be viewed only in Materials Management.
• Goods and Invoice Receipt documents can be viewed from both Materials Management and Financial Accounting modules.
11. What is a Request for Quotation (RFQ)?
A RFQ is a request of quotes from vendors for a particular good or service. An RFQ can be created with reference to a Purchase Requisition or be created directly.
12. How is a Purchase Order created in SAP?
A Purchase Order (PO) can be created directly or with reference to a RFQ, a Contract, a Purchase Requisition, or another Purchase Order.
13. What is an Outline Agreement?
An Outline Agreement documents a long-term arrangement with a vendor to provide materials or services at an agreed price. It is valid for a period of time or until a pre-defined total quantity or total value is reached.
14. What are the different types of Outline Agreements?
Contracts and Scheduling Agreements
15. For what is an Account Assignment Category used?
Account Assignment category is used to manually create Order documents. It determines which account assignment data is required for an item in order to allocate costs.
16. What is the purpose of a Goods Receipt document?
A Goods Receipt document is created when goods are received at a plant/warehouse. At this time, an accounting document is created to make a General Ledger entry, and a materials document is created to record changes in physical inventory.
17. What is the purpose of an Invoice Receipt document?
When invoices are received from a Vendor, an Invoice Receipt document is created in the system. This document can be linked to a Purchase Order, a Goods Receipt, a Delivery Note, or a Vendor. In addition to the materials document, an accounting document is created, which updates the relevant Vendor Account (sub-ledger) and General Ledger Accounts.
• Purchase Requisition (MM)
• Purchase Order (MM)
• Goods Receipt (MM)
• Invoice Verification (MM)
• Vendor Payment (FI)
2. What is a Purchase Requisition?
A Purchase Requisition is a document that identifies an organization’s demand for a product or service from an outside vendor. It is an internal document (i.e., it is not visible to the vendor or any other outside organization).
3. What are the two ways a Purchase Requisition can be created?
• Automatically as a result of a Materials Requirements Planning (MRP) run.
• Manually by a user.
4. What is a Purchase Order?
A Purchase Order is a legal contract between a buyer and a vendor. It lists the materials or services to be purchased on specified terms and conditions (quantity, price / pricing conditions, delivery date).
5. Name the four steps necessary for creation of a Purchase Order.
• Source Determination
• Vendor Selection
• Purchase Order Processing
• Purchase Order Follow-Up
6. What are the different types of goods movements?
Goods receipts, goods issues, and transfer postings.
7. What is Invoice Verification?
Invoice verification is the process of matching Vendor Invoices to the Purchase Order and Goods Receipt documents. For matched vendor invoices, a payable is automatically created in the FI General Ledger.
8. How is the Payment Program used to make Vendor Payments?
The Payment Program is set to maximize cash discounts when paying open vendor items. It creates a list of proposed vendor items to be paid and suggests payment methods for each proposed payment. The user has the ability to make any changes before payments are made.
Note: The payment program selection strategy (e.g., maximization of cash discounts) is configurable.
9. Name the three different types of Materials Management documents.
• Order documents
• Goods receipt documents
• Invoice Receipt documents
10. From which modules can the above documents be viewed?
• Order documents can be viewed only in Materials Management.
• Goods and Invoice Receipt documents can be viewed from both Materials Management and Financial Accounting modules.
11. What is a Request for Quotation (RFQ)?
A RFQ is a request of quotes from vendors for a particular good or service. An RFQ can be created with reference to a Purchase Requisition or be created directly.
12. How is a Purchase Order created in SAP?
A Purchase Order (PO) can be created directly or with reference to a RFQ, a Contract, a Purchase Requisition, or another Purchase Order.
13. What is an Outline Agreement?
An Outline Agreement documents a long-term arrangement with a vendor to provide materials or services at an agreed price. It is valid for a period of time or until a pre-defined total quantity or total value is reached.
14. What are the different types of Outline Agreements?
Contracts and Scheduling Agreements
15. For what is an Account Assignment Category used?
Account Assignment category is used to manually create Order documents. It determines which account assignment data is required for an item in order to allocate costs.
16. What is the purpose of a Goods Receipt document?
A Goods Receipt document is created when goods are received at a plant/warehouse. At this time, an accounting document is created to make a General Ledger entry, and a materials document is created to record changes in physical inventory.
17. What is the purpose of an Invoice Receipt document?
When invoices are received from a Vendor, an Invoice Receipt document is created in the system. This document can be linked to a Purchase Order, a Goods Receipt, a Delivery Note, or a Vendor. In addition to the materials document, an accounting document is created, which updates the relevant Vendor Account (sub-ledger) and General Ledger Accounts.
Controlling Introduction
The SAP CO (Controlling) Module provides supporting information to Management for the purpose of planning, reporting, as well as monitoring the operations of their business. Management decision-making can be achieved with the level of information provided by this module.
Some of the components of the CO(Controlling) Module are as follows:
1. Cost Element Accounting
2. Cost Center Accounting
3. Internal Orders
4. Activity-Based Costing ( ABC)
5. Product Cost Controlling
6. Profitability Analysis
7. Profit Center Accounting
The Cost Element Accounting component provides information which includes the costs and revenue for an organization. These postings are automatically updated from FI (Financial Accounting) to CO (Controlling). The cost elements are the basis for cost accounting and enable the User the ability to display costs for each of the accounts that have been assigned to the cost element. Examples of accounts that can be assigned are Cost Centers, Internal Orders, WBS (work breakdown structures).
Cost Center Accounting provides information on the costs incurred by your business. Within SAP, you have the ability to assign Cost Centers to departments and /or Managers responsible for certain areas of the business as well as functional areas within your organization. Cost Centers can be created for such functional areas as Marketing, Purchasing, Human Resources, Finance, Facilities, Information Systems, Administrative Support, Legal, Shipping/Receiving, or even Quality.
Some of the benefits of Cost Center Accounting: (1) Managers can set Budget /Cost Center targets; (2) Cost Center visibility of functional departments/areas of your business; (3) Planning; (4) Availability of Cost allocation methods; and (5) Assessments/Distribution of costs to other cost objects.
Internal Orders provide a means of tracking costs of a specific job, service, or task. Internal Orders are used as a method to collect those costs and business transactions related to the task. This level of monitoring can be very detailed but allows management the ability to review Internal Order activity for better-decision making purposes.
Activity-Based Costing allows a better definition of the source of costs to the process driving the cost. Activity-Based Costing enhances Cost Center Accounting in that it allows for a process-oriented and cross-functional view of your cost centers. It can also be used with Product Costing and Profitability Analysis.
Product Cost Controlling allows management the ability to analyze their product costs and to make decisions on the optimal price(s) to market their products. It is within this module of CO (Controlling) that planned, actual and target values are analyzed. Sub-components of the module are:
• Product Cost Planning which includes Material Costing( Cost estimates with Quantity structure, Cost estimates without quantity structure, Master data for Mixed Cost Estimates, Production lot Cost Estimates) , Price Updates, and Reference and Simulation Costing.
• Cost Object Controlling includes Product Cost by Period, Product Cost by Order, Product Costs by Sales Orders, Intangible Goods and Services, and CRM Service Processes.
• Actual Costing/Material Ledger includes Periodic Material valuation, Actual Costing, and Price Changes.
Profitability Analysis allows Management the ability to review information with respect to the company’s profit or contribution margin by business segment. Profitability Analysis can be obtained by the following methods:
• Account-Based Analysis which uses an account-based valuation approach. In this analysis, cost and revenue element accounts are used. These accounts can be reconciled with FI(Financial Accounting).
• Cost-Based Analysis uses a costing based valuation approach as defined by the User.
Profit Center Accounting provides visibility of an organization’s profit and losses by profit center. The methods which can be utilized for EC-PCA (Profit Center Accounting) are period accounting or by the cost-of-sales approach. Profit Centers can be set-up to identify product lines, divisions, geographical regions, offices, production sites or by functions. Profit Centers are used for Internal Control purposes enabling management the ability to review areas of responsibility within their organization. The difference between a Cost Center and a Profit Center is that the Cost Center represents individual costs incurred during a given period and Profit Centers contain the balances of costs and revenues.
Primary configuration considerations:
There are several configuration steps that must be considered when implementing the CO (Controlling) Module. Creating the Controlling area is one of the first steps in the CO (Controlling) configuration process. SAP has provided standard controlling areas and company codes which can be utilized as a basis for creating your company’s Controlling Area. The SAP Standard for Controlling Area is “0001” and for company code is “0001”.
It is recommended that these be used as a basis to create the Controlling Area or Company Code that you would like to define. Certain defaults setting such as number ranges have already been set-up in the standard SAP settings, thereby eliminating the need to redo this configuration requirement. Through the SAP Configuration process, you can create a copy of the Standard Controlling Area and Company Code, then update the other fields as needed including the four character alpha numeric field which identifies these areas. (You may want to change the controlling area from “0001” to “A001” and the Company Code from “0001” to “ AA01” as an example.)
Keep in mind that Company Codes are assigned to Controlling Areas and affect the COA (Chart of Accounts), the Fiscal Year Variants, and Currency set-ups. Cost Center hierarchy and Reconciliation ledger settings are also include in the Controlling Area set-up.
The Control Indicator activates and deactivates certain functions in the Controlling Area. The Controlling Area can also be used for cross-company code business transactions. To enable this function the Controlling Area must be assigned to all company codes used for cross-company code accounting.
Number Ranges:
Configuration in the CO (Controlling) Modules requires maintenance of number ranges for documents generated from business transactions. A systems’ generated document number is assigned for every CO (Controlling) posting. These numbers are sequential and are required to be assigned to number range groups. The number range group consists of two number intervals, one for internal document numbering and one for external document numbering. The SAP R/3 system keeps track of those document numbers that are externally generated and fed to SAP via batches and User manual input, otherwise, the system generates the next internally assigned document number for the transaction posted.
As previously stated when defining the Controlling Area, you have the ability to copy the Standard SAP Controlling Area “0001” which already has the number ranges defined eliminating the need for maintenance of number ranges. Keep in mind that you also have the flexibility to change number ranges and number range groups to meet your business needs. As a caution, never overlap number intervals in a group. For example, if you decide to assign number range interval 10000000 thru 199999999 to the number range group “05”, you can not assign it to number range group “06”. Number ranges should never be transported for data consistency purposes, therefore create these manually in each system.
Within the CO (Controlling) Module, you can configure Plan Versions. Maintaining Plan Versions allows for set-up of planning assumptions and determination of plan rates for allocation and plan activity purposes. The SAP Standard Version “000” is created for a five year fiscal year plan. It is recommended that the standard version be utilized for your plan/actual comparisons if you do not require multiple plan versions. SAP always allows the flexibility to create additional Plan versions by coping the Standard Version “000” and changing certain fields as required. There is also the option of defining and creating a totally new Plan Version.
Other Configuration:
After the Controlling Area, Number Ranges, and Plan Versions have been defined and maintained, then settings for the other components in the CO (Controlling) Module should be maintained. (Cost Center Accounting, Cost Element Accounting, Activity-Based Costing, Internal Orders, Product Cost Controlling, Profitability Analysis, and Profit Center Accounting)
The Account Assignment Logic allows configuration for Validation and Substitution Rules whose purpose is to check certain input values as defined by the User.
More specifically, Validations allow for business transactions to either post or not post documents based on the criteria defined in the validation rule. Certain input conditions are checked as defined by the User and if those conditions are met then the document(s) are updated and/or posted in the system. If the condition is not met, then an error message is generated to the User with a brief explanation of the error. These messages are defined in Configuration and can be identified as a warning, error, or a note. You also have the option to deactivate messages.
Substitutions on the other hand, checks input values and replaces the values with another value if the criteria as defined is met.
Maintaining Currency and Valuation Profiles allows for the definition of valuation approaches to be used in accounting components. These valuation profiles are checked in the system when activated in the Controlling Area. Certain rules apply if there is a need to maintain the currency and valuation profiles: (1) Company Code Currency must be assigned to a legal valuation approach, (2) Valuation approaches must also be maintain in the material ledger, and (3) Profit Center valuations can only be maintained if you are using Profit Center Accounting.
The CO(Controlling)Module has multiple configuration steps that must be followed for complete implementation of this module. Each sub-component of the CO (Controlling) Module has it’s level of configuration requirements. Once you have defined your business needs in the Controlling Area, a determination can be made as to what should be configured and what you do not need.
Some of the components of the CO(Controlling) Module are as follows:
1. Cost Element Accounting
2. Cost Center Accounting
3. Internal Orders
4. Activity-Based Costing ( ABC)
5. Product Cost Controlling
6. Profitability Analysis
7. Profit Center Accounting
The Cost Element Accounting component provides information which includes the costs and revenue for an organization. These postings are automatically updated from FI (Financial Accounting) to CO (Controlling). The cost elements are the basis for cost accounting and enable the User the ability to display costs for each of the accounts that have been assigned to the cost element. Examples of accounts that can be assigned are Cost Centers, Internal Orders, WBS (work breakdown structures).
Cost Center Accounting provides information on the costs incurred by your business. Within SAP, you have the ability to assign Cost Centers to departments and /or Managers responsible for certain areas of the business as well as functional areas within your organization. Cost Centers can be created for such functional areas as Marketing, Purchasing, Human Resources, Finance, Facilities, Information Systems, Administrative Support, Legal, Shipping/Receiving, or even Quality.
Some of the benefits of Cost Center Accounting: (1) Managers can set Budget /Cost Center targets; (2) Cost Center visibility of functional departments/areas of your business; (3) Planning; (4) Availability of Cost allocation methods; and (5) Assessments/Distribution of costs to other cost objects.
Internal Orders provide a means of tracking costs of a specific job, service, or task. Internal Orders are used as a method to collect those costs and business transactions related to the task. This level of monitoring can be very detailed but allows management the ability to review Internal Order activity for better-decision making purposes.
Activity-Based Costing allows a better definition of the source of costs to the process driving the cost. Activity-Based Costing enhances Cost Center Accounting in that it allows for a process-oriented and cross-functional view of your cost centers. It can also be used with Product Costing and Profitability Analysis.
Product Cost Controlling allows management the ability to analyze their product costs and to make decisions on the optimal price(s) to market their products. It is within this module of CO (Controlling) that planned, actual and target values are analyzed. Sub-components of the module are:
• Product Cost Planning which includes Material Costing( Cost estimates with Quantity structure, Cost estimates without quantity structure, Master data for Mixed Cost Estimates, Production lot Cost Estimates) , Price Updates, and Reference and Simulation Costing.
• Cost Object Controlling includes Product Cost by Period, Product Cost by Order, Product Costs by Sales Orders, Intangible Goods and Services, and CRM Service Processes.
• Actual Costing/Material Ledger includes Periodic Material valuation, Actual Costing, and Price Changes.
Profitability Analysis allows Management the ability to review information with respect to the company’s profit or contribution margin by business segment. Profitability Analysis can be obtained by the following methods:
• Account-Based Analysis which uses an account-based valuation approach. In this analysis, cost and revenue element accounts are used. These accounts can be reconciled with FI(Financial Accounting).
• Cost-Based Analysis uses a costing based valuation approach as defined by the User.
Profit Center Accounting provides visibility of an organization’s profit and losses by profit center. The methods which can be utilized for EC-PCA (Profit Center Accounting) are period accounting or by the cost-of-sales approach. Profit Centers can be set-up to identify product lines, divisions, geographical regions, offices, production sites or by functions. Profit Centers are used for Internal Control purposes enabling management the ability to review areas of responsibility within their organization. The difference between a Cost Center and a Profit Center is that the Cost Center represents individual costs incurred during a given period and Profit Centers contain the balances of costs and revenues.
Primary configuration considerations:
There are several configuration steps that must be considered when implementing the CO (Controlling) Module. Creating the Controlling area is one of the first steps in the CO (Controlling) configuration process. SAP has provided standard controlling areas and company codes which can be utilized as a basis for creating your company’s Controlling Area. The SAP Standard for Controlling Area is “0001” and for company code is “0001”.
It is recommended that these be used as a basis to create the Controlling Area or Company Code that you would like to define. Certain defaults setting such as number ranges have already been set-up in the standard SAP settings, thereby eliminating the need to redo this configuration requirement. Through the SAP Configuration process, you can create a copy of the Standard Controlling Area and Company Code, then update the other fields as needed including the four character alpha numeric field which identifies these areas. (You may want to change the controlling area from “0001” to “A001” and the Company Code from “0001” to “ AA01” as an example.)
Keep in mind that Company Codes are assigned to Controlling Areas and affect the COA (Chart of Accounts), the Fiscal Year Variants, and Currency set-ups. Cost Center hierarchy and Reconciliation ledger settings are also include in the Controlling Area set-up.
The Control Indicator activates and deactivates certain functions in the Controlling Area. The Controlling Area can also be used for cross-company code business transactions. To enable this function the Controlling Area must be assigned to all company codes used for cross-company code accounting.
Number Ranges:
Configuration in the CO (Controlling) Modules requires maintenance of number ranges for documents generated from business transactions. A systems’ generated document number is assigned for every CO (Controlling) posting. These numbers are sequential and are required to be assigned to number range groups. The number range group consists of two number intervals, one for internal document numbering and one for external document numbering. The SAP R/3 system keeps track of those document numbers that are externally generated and fed to SAP via batches and User manual input, otherwise, the system generates the next internally assigned document number for the transaction posted.
As previously stated when defining the Controlling Area, you have the ability to copy the Standard SAP Controlling Area “0001” which already has the number ranges defined eliminating the need for maintenance of number ranges. Keep in mind that you also have the flexibility to change number ranges and number range groups to meet your business needs. As a caution, never overlap number intervals in a group. For example, if you decide to assign number range interval 10000000 thru 199999999 to the number range group “05”, you can not assign it to number range group “06”. Number ranges should never be transported for data consistency purposes, therefore create these manually in each system.
Within the CO (Controlling) Module, you can configure Plan Versions. Maintaining Plan Versions allows for set-up of planning assumptions and determination of plan rates for allocation and plan activity purposes. The SAP Standard Version “000” is created for a five year fiscal year plan. It is recommended that the standard version be utilized for your plan/actual comparisons if you do not require multiple plan versions. SAP always allows the flexibility to create additional Plan versions by coping the Standard Version “000” and changing certain fields as required. There is also the option of defining and creating a totally new Plan Version.
Other Configuration:
After the Controlling Area, Number Ranges, and Plan Versions have been defined and maintained, then settings for the other components in the CO (Controlling) Module should be maintained. (Cost Center Accounting, Cost Element Accounting, Activity-Based Costing, Internal Orders, Product Cost Controlling, Profitability Analysis, and Profit Center Accounting)
The Account Assignment Logic allows configuration for Validation and Substitution Rules whose purpose is to check certain input values as defined by the User.
More specifically, Validations allow for business transactions to either post or not post documents based on the criteria defined in the validation rule. Certain input conditions are checked as defined by the User and if those conditions are met then the document(s) are updated and/or posted in the system. If the condition is not met, then an error message is generated to the User with a brief explanation of the error. These messages are defined in Configuration and can be identified as a warning, error, or a note. You also have the option to deactivate messages.
Substitutions on the other hand, checks input values and replaces the values with another value if the criteria as defined is met.
Maintaining Currency and Valuation Profiles allows for the definition of valuation approaches to be used in accounting components. These valuation profiles are checked in the system when activated in the Controlling Area. Certain rules apply if there is a need to maintain the currency and valuation profiles: (1) Company Code Currency must be assigned to a legal valuation approach, (2) Valuation approaches must also be maintain in the material ledger, and (3) Profit Center valuations can only be maintained if you are using Profit Center Accounting.
The CO(Controlling)Module has multiple configuration steps that must be followed for complete implementation of this module. Each sub-component of the CO (Controlling) Module has it’s level of configuration requirements. Once you have defined your business needs in the Controlling Area, a determination can be made as to what should be configured and what you do not need.
SAP- Enterprise Controlling (EC)
EC-CS Enterprise controlling – Consolidations: The module where consolidations and elimination occur for both a legal entity (Company Code) and a management area (Profit Center). Consolidation gives you a reconciled view of your groups financial data and lets you create the reports required by corporate law (by group, company or business areas) as well as reports which reflect your company’s internal management structure (by profit center or region). This is possible due to powerful consolidation functions built on top of flexible structures. The raw data can be transferred via interfaces with FI-GL (General Ledger), FI-AA (asset accounting), MM (Materials Management, SD (Sales and Distribution) and EC-PCA. You can also analyze the results of the consolidation immediately in EC-EIS. DATA TYPES – i.e. CS Breakdown categories
• Company & Trading Partner controlled by FI are required to generate eliminations. Note: FI-GL/AR/AP line items always have Company in Document Header. Trading partner is in document line item where relevant
• Profit Centers & Partner Profit Centers controlled by PCA are needed to generate eliminations for Management Consolidation by line of business
• Consolidation Units and Partner Units controlled by CS are used to generate eliminations for various consolidations. Transaction data from CS-PCA updates Consolidation units and if appropriate stores the data by partner Unit.
• Transaction types controlled by FI are used for reporting of consolidated balance sheet flows in CS. Transaction Types are used by the Fixed Asset module to distinguish between beginning balance, additions, transfers, disposals and ending balances. Separate types are usefull to distinguish movements in equity holdings for financial investments.
• Functional Areas controlled by CO are used for reporting consolidated P&L Statements. Functional Areas combine accounts but distinguish balances by function (e.g. selling expenses, research & development costs etc.)
o FI-AA Assets Module is the primary user of Transaction Types. Transactions made in FI-AA are stored with a Transaction Type which identifies whether it is an addition or disposal, etc. These Asset Transaction Types can be mapped into consolidation transaction types.
o Data passing from PCA to CS populates a single field with either a Transaction type for selected Balance Sheet accounts or a Functional Area for selected P&L accounts.
o Transaction types and Functional Areas are for Reporting.
EC-PCA Profit Center Accounting – Profit center accounting forms an interface between the operative controlling (CO) applications and the Enterprise Controlling (EC) module It reflects the actual and plan postings from operative controlling and settlements components with which it is in targeted in real-time. It then summarizes this data according to profit centers, which reflect the internal structure of areas of responsibility within the company code
• Each profit center is assigned to one controlling area
• Reason for Profit Centers
1. to analyze areas of responsibility
2. to delegate responsibility to different decentralized units
• Profit Centers can be set up
1. Product (product lines, divisions)
2. Geographical factors (regions, sites)
3. Function (production, sales)
• Profit Centers are organized into an organizational hierarchy in which responsibility and incentive structures can be defined. Profit Center Hierarchy:
o Node one
(a) Profit Center one
o Node two
• Profit Center two
(a). Revenue
(b). Costs
• Profit Center three
• Planning can be done on a PCA
• In EC-PCA, the profit center is the lowest level at which you measure financial results
• Since CS-PCA is only complete at the end of the month, CS-PCA data in only rolled up to CS via FI-SL (Special Ledger) monthly.
Accounting Data Flows:
1. Real time data flows
2. Periodic data flows
EC-CS – Enterprise Controlling Consolidations
• Manual Entries
• EC-PCA – Enterprise Controlling Profit center accounting
o FI Balance Sheet Items
(1). SD, MM, PP, FI Journal Entries
FI Period End Update – Balance Sheet Sub Ledgers - SD, MM, PP, FI Journal Entries
CO-OH
o FI P&L - SD, MM, PP, FI Journal Entries CO - Allocations CO-PA
o FI P&L External Revenue and Cost of Sales - SD, MM, PP, FI Journal Entries
Module Functions:
Control – The module that manages cost reporting, analysis and control. This is the primary area for managing and evaluating financial performance.
CO-PA:
Profitability Analysis. That part of CO where operations will access its performance factors and profitability statements contain margins, standard cost variance, sales information, allocations and other related profit or loss data. This module helps analyze profitability of customers, markets and products at various levels of contribution margins. Profitability is measured down to the SD billing document line and is adjusted periodically against standard costs and other costs.
• Profitability analysis, like profit center accounting is another form of profitability accounting. However, it is incorporated in operative cost accounting, i.e. the profitability segments in CO-PA are accounting assignment objects and are thus directly integrated in the flow of data in cost accounting.
• In contrast to EC-PCA, where profits are found for areas of responsibility within the company, CO-PA lets you analyze the profitability of different segments of your operative business as defined according to products, customers, orders or any combinations of groups of these or as organizational units, such as company codes or business areas. The aim of CO-PA is to provide decision makers with information about the market.
• Master data and basic structures in CO-PA can be defined with sufficient flexibility to meet company specific requirements. This is done by choosing the objects for evaluation (characteristics) and key figures to create a company-specific multidimensional structure for analysis.
• Unlike EC-PCA, CO-PA lets you use an account-based or a costing based approach. In the costing based approach, define value fields for analysis. In account based the values are represented in accounts.
• EC-PCA and CO-PA should not be regarded as alternative components. They complement one another and jointly provide a flexible and comprehensive profitability accounting tool, allowing you both a market oriented view and a responsibility view.
• Data Source
1. Revenue Accounts
2. Expense Accounts
3. Allocation of Operating Expense (only across profit center)
4. Stock Transfers Across PCA
5. A/R Sub ledger (Month End Batch Job)
6. A/P Sub ledger (Month End Batch Job)
7. Other Balance Sheet Accounts
• Data Flows
CO-CCA:
Cost Center Accounting determines where costs are incurred in the organization. Assigned to the sub area where they have the most influence.
• By creating and assigning cost elements to cost centers, you make cost controlling possible, but also provide data for other components in CO such as Cost Object Controlling. Cost centers can use allocation methods to assign collect costs to other controlling objects.
• Cost center structure can reflect the structure of the organization. It generally remains constant over time.
• Cost Centers
CO-OPA:
- Internal Orders
CO-PC:
- Product Costing
CO-OH:
- Overhead
• Company & Trading Partner controlled by FI are required to generate eliminations. Note: FI-GL/AR/AP line items always have Company in Document Header. Trading partner is in document line item where relevant
• Profit Centers & Partner Profit Centers controlled by PCA are needed to generate eliminations for Management Consolidation by line of business
• Consolidation Units and Partner Units controlled by CS are used to generate eliminations for various consolidations. Transaction data from CS-PCA updates Consolidation units and if appropriate stores the data by partner Unit.
• Transaction types controlled by FI are used for reporting of consolidated balance sheet flows in CS. Transaction Types are used by the Fixed Asset module to distinguish between beginning balance, additions, transfers, disposals and ending balances. Separate types are usefull to distinguish movements in equity holdings for financial investments.
• Functional Areas controlled by CO are used for reporting consolidated P&L Statements. Functional Areas combine accounts but distinguish balances by function (e.g. selling expenses, research & development costs etc.)
o FI-AA Assets Module is the primary user of Transaction Types. Transactions made in FI-AA are stored with a Transaction Type which identifies whether it is an addition or disposal, etc. These Asset Transaction Types can be mapped into consolidation transaction types.
o Data passing from PCA to CS populates a single field with either a Transaction type for selected Balance Sheet accounts or a Functional Area for selected P&L accounts.
o Transaction types and Functional Areas are for Reporting.
EC-PCA Profit Center Accounting – Profit center accounting forms an interface between the operative controlling (CO) applications and the Enterprise Controlling (EC) module It reflects the actual and plan postings from operative controlling and settlements components with which it is in targeted in real-time. It then summarizes this data according to profit centers, which reflect the internal structure of areas of responsibility within the company code
• Each profit center is assigned to one controlling area
• Reason for Profit Centers
1. to analyze areas of responsibility
2. to delegate responsibility to different decentralized units
• Profit Centers can be set up
1. Product (product lines, divisions)
2. Geographical factors (regions, sites)
3. Function (production, sales)
• Profit Centers are organized into an organizational hierarchy in which responsibility and incentive structures can be defined. Profit Center Hierarchy:
o Node one
(a) Profit Center one
o Node two
• Profit Center two
(a). Revenue
(b). Costs
• Profit Center three
• Planning can be done on a PCA
• In EC-PCA, the profit center is the lowest level at which you measure financial results
• Since CS-PCA is only complete at the end of the month, CS-PCA data in only rolled up to CS via FI-SL (Special Ledger) monthly.
Accounting Data Flows:
1. Real time data flows
2. Periodic data flows
EC-CS – Enterprise Controlling Consolidations
• Manual Entries
• EC-PCA – Enterprise Controlling Profit center accounting
o FI Balance Sheet Items
(1). SD, MM, PP, FI Journal Entries
FI Period End Update – Balance Sheet Sub Ledgers - SD, MM, PP, FI Journal Entries
CO-OH
o FI P&L - SD, MM, PP, FI Journal Entries CO - Allocations CO-PA
o FI P&L External Revenue and Cost of Sales - SD, MM, PP, FI Journal Entries
Module Functions:
Control – The module that manages cost reporting, analysis and control. This is the primary area for managing and evaluating financial performance.
CO-PA:
Profitability Analysis. That part of CO where operations will access its performance factors and profitability statements contain margins, standard cost variance, sales information, allocations and other related profit or loss data. This module helps analyze profitability of customers, markets and products at various levels of contribution margins. Profitability is measured down to the SD billing document line and is adjusted periodically against standard costs and other costs.
• Profitability analysis, like profit center accounting is another form of profitability accounting. However, it is incorporated in operative cost accounting, i.e. the profitability segments in CO-PA are accounting assignment objects and are thus directly integrated in the flow of data in cost accounting.
• In contrast to EC-PCA, where profits are found for areas of responsibility within the company, CO-PA lets you analyze the profitability of different segments of your operative business as defined according to products, customers, orders or any combinations of groups of these or as organizational units, such as company codes or business areas. The aim of CO-PA is to provide decision makers with information about the market.
• Master data and basic structures in CO-PA can be defined with sufficient flexibility to meet company specific requirements. This is done by choosing the objects for evaluation (characteristics) and key figures to create a company-specific multidimensional structure for analysis.
• Unlike EC-PCA, CO-PA lets you use an account-based or a costing based approach. In the costing based approach, define value fields for analysis. In account based the values are represented in accounts.
• EC-PCA and CO-PA should not be regarded as alternative components. They complement one another and jointly provide a flexible and comprehensive profitability accounting tool, allowing you both a market oriented view and a responsibility view.
• Data Source
1. Revenue Accounts
2. Expense Accounts
3. Allocation of Operating Expense (only across profit center)
4. Stock Transfers Across PCA
5. A/R Sub ledger (Month End Batch Job)
6. A/P Sub ledger (Month End Batch Job)
7. Other Balance Sheet Accounts
• Data Flows
CO-CCA:
Cost Center Accounting determines where costs are incurred in the organization. Assigned to the sub area where they have the most influence.
• By creating and assigning cost elements to cost centers, you make cost controlling possible, but also provide data for other components in CO such as Cost Object Controlling. Cost centers can use allocation methods to assign collect costs to other controlling objects.
• Cost center structure can reflect the structure of the organization. It generally remains constant over time.
• Cost Centers
CO-OPA:
- Internal Orders
CO-PC:
- Product Costing
CO-OH:
- Overhead
Controlling Actual Postings and Allocations
1. [True] or False? Posting actual cost in Controlling involves the transferring of primary costs from other modules to Controlling, as well as moving costs within Controlling.
2. List the two main types of actual posting to CO.
There are two types of actual postings to CO, Transaction Based Postings and Periodic Allocations.
Transaction Based Postings (also known as Transaction based allocations) are posted on a real-time basis from other modules or within CO. This enables up-to-the-minute reporting of costs incurred on the cost centers at any time during the period. There are four transaction-based postings to CO:
From other modules:
• Direct postings to cost centers from other modules, such as FI, AM, and MM.
Within CO:
• Reposting
• Activity Allocation
• Posting of Statistical Key Figures.
Periodic Allocations exist entirely within CO. They occur at the end of the period after all primary postings have been completed. Periodic allocations require cycles and segments to be executed. There are five main types of periodic allocations:
• Periodic repostings (periodic transfers)
• Distribution
• Assessment,
• Imputed Cost Calculation
• Indirect Activity Allocation.
3. [True] or False Transaction based posting within CO may be accomplished through the use of any of the following: Reposting, Activity Allocation and posting of Statistical key figures.
4. How many documents are created when primary costs are posted to CO from another module?
Two documents are created when primary costs are posted to CO from another module:
• The original document in FI, AM or MM
• A parallel document in CO which displays the data from a cost accounting viewpoint. The CO document is summarized according to cost element and cost object.
5. True or False? Repostings are used to reallocate costs that were incorrectly posted to a cost center.
True. Repostings are used to reallocate costs that were incorrectly posted to a cost center. There are two types of internal repostings, Full-Transaction Reposting (i.e. Reposting of the entire transaction) and Line Item Reposting (i.e. Reposting of a portion of the original transaction).
In a Transaction Based Reposting, the entire original cost center posting is reversed and reposted to a different, corrected, cost center. The FI document number does not need to be referenced for the reposting. A new CO document number is created for the reposting. The original FI document remains unchanged (references old cost center).
A Line Item Reposting is used when only certain line items in the original posting are incorrect. The FI document number must referenced for the reposting. A new CO document number is created and the old cost center is referenced on the FI document.
6. List and define the two types of internal Reposting.
See answer to question 5 above.
7. Describe Manual Cost Allocation.
Manual Cost Allocation can be used to post primary cost as well as secondary costs to avoid the creation of a cycle for simple allocations, to transfer external data or to correct false secondary postings. Manual cost allocation applies to actual data only. You cannot copy this data into planning.
8. Define Direct Internal Activity Allocation.
Direct Internal Activity Allocation is the process of recording activities performed by a cost center and simultaneously allocating those activities to receiving cost centers based on consumption. In the case of direct activity allocation, the sender (output), and the receiver (consumption) activity volumes are known.
9. [True] or False? In direct activity allocation, the sender (output), and the receiver (consumption) activity volumes are known.
See answer to question 7 above.
10. True or False? Periodic allocations of cost exist in both FI and CO.
False, Periodic Allocations exist entirely within CO. They generally occur at the end of the period after all primary postings have been completed and they require cycles and segments to be executed. There are five main types of periodic allocations: Periodic repostings (periodic transfers), Distribution, Assessment, Imputed Cost Calculation and Indirect Activity Allocation.
11. [True] or False? Periodic allocations require cycles and segments to be executed.
See answer to question 9 above.
12. List three types of periodic allocations.
See Question 9
13. ___________enables the correction of multiple posting made to cost centers during the period, therefore producing the same results as several transaction-based repostings.
Periodic reposting enables the correction of multiple postings made to cost centers during the period, therefore producing the same results as several transaction-based repostings. This reposting functionality can also be utilized at the end of a period to transfer costs from a clearing cost center to appropriate receiving cost centers. When used in this fashion, periodic reposting is very similar to distribution.
The main difference between periodic repostings and distribution is the purpose for usage envisioned by SAP when the methods were created. Periodic reposting functionality, similar to transaction-based repostings, was designed for error correction, whereas distribution was designed as a primary cost allocation method. However, other than their intended purposes, the two methods are practically identical and either method may be used whenever desired.
14. Explain both the iterative and cumulative form of cycle processing.
Iterative processing: iterative sender/receiver relationships (sender is also amongst the receivers) are considered when this cycle is processed. The iteration is repeated until each sender is fully relieved of costs provided. Cycles may be set to iterative processing for both plan and actual data.
Cumulative processing: all posted sender amounts since the first period are accumulated and allocated based on the tracing factors accumulated since this period. The difference between the accumulated amount and the posted amounts in previous periods is posted in the current period. The postings in previous periods remain unchanged. Cycles may be set to cumulative processing for actual data only.
15. Describe imputed cost calculation in CO.
Imputed cost calculations are used to smooth the effect on cost centers for large, one-time charges, such as insurance premiums or employee bonuses. By smoothing one-time expenses in CO, price fluctuations from period to period can be avoided. There are two methods for calculating imputed costs in the R/3 system Cost Element Percent Method and Target = Actuals Method.
16. List and define the two main types of indirect activity allocations.
Indirect activity allocation is the process of allocating activities from a sender to a receiver cost object. The activities allocated to the receiver are multiplied by the planned activity price to determine the total amount.
There are two types of indirect activity allocations:
• Sender activities known
The activity type is allocated from the sender to the receiver based on receiver tracing factors (i.e. actual receiver statistical key figures, planned receiver activity types, etc.)
This type of indirect activity allocation must be set up with an activity type of Category 3. This category is defined for manual entry (of known sender values), using indirect allocation (tracing factors).
• Sender activities unknown
Activities are inversely allocated from the sender cost center using receiver tracing factors or fixed amounts/percentages.
This type of indirect activity allocation must be set up with an activity type of category 2. This category is defined for inverse determination (of sender values based on receiver consumption) using automatic allocation (to receivers).
17. Describe the use of the reconciliation ledger.
The reconciliation ledger keeps track of transactions between company codes within one controlling area, since such cross company allocations result in an imbalance between CO totals and FI totals. Because legal reporting is based in FI, all transactions that cross company codes in CO must be reflected in FI.
2. List the two main types of actual posting to CO.
There are two types of actual postings to CO, Transaction Based Postings and Periodic Allocations.
Transaction Based Postings (also known as Transaction based allocations) are posted on a real-time basis from other modules or within CO. This enables up-to-the-minute reporting of costs incurred on the cost centers at any time during the period. There are four transaction-based postings to CO:
From other modules:
• Direct postings to cost centers from other modules, such as FI, AM, and MM.
Within CO:
• Reposting
• Activity Allocation
• Posting of Statistical Key Figures.
Periodic Allocations exist entirely within CO. They occur at the end of the period after all primary postings have been completed. Periodic allocations require cycles and segments to be executed. There are five main types of periodic allocations:
• Periodic repostings (periodic transfers)
• Distribution
• Assessment,
• Imputed Cost Calculation
• Indirect Activity Allocation.
3. [True] or False Transaction based posting within CO may be accomplished through the use of any of the following: Reposting, Activity Allocation and posting of Statistical key figures.
4. How many documents are created when primary costs are posted to CO from another module?
Two documents are created when primary costs are posted to CO from another module:
• The original document in FI, AM or MM
• A parallel document in CO which displays the data from a cost accounting viewpoint. The CO document is summarized according to cost element and cost object.
5. True or False? Repostings are used to reallocate costs that were incorrectly posted to a cost center.
True. Repostings are used to reallocate costs that were incorrectly posted to a cost center. There are two types of internal repostings, Full-Transaction Reposting (i.e. Reposting of the entire transaction) and Line Item Reposting (i.e. Reposting of a portion of the original transaction).
In a Transaction Based Reposting, the entire original cost center posting is reversed and reposted to a different, corrected, cost center. The FI document number does not need to be referenced for the reposting. A new CO document number is created for the reposting. The original FI document remains unchanged (references old cost center).
A Line Item Reposting is used when only certain line items in the original posting are incorrect. The FI document number must referenced for the reposting. A new CO document number is created and the old cost center is referenced on the FI document.
6. List and define the two types of internal Reposting.
See answer to question 5 above.
7. Describe Manual Cost Allocation.
Manual Cost Allocation can be used to post primary cost as well as secondary costs to avoid the creation of a cycle for simple allocations, to transfer external data or to correct false secondary postings. Manual cost allocation applies to actual data only. You cannot copy this data into planning.
8. Define Direct Internal Activity Allocation.
Direct Internal Activity Allocation is the process of recording activities performed by a cost center and simultaneously allocating those activities to receiving cost centers based on consumption. In the case of direct activity allocation, the sender (output), and the receiver (consumption) activity volumes are known.
9. [True] or False? In direct activity allocation, the sender (output), and the receiver (consumption) activity volumes are known.
See answer to question 7 above.
10. True or False? Periodic allocations of cost exist in both FI and CO.
False, Periodic Allocations exist entirely within CO. They generally occur at the end of the period after all primary postings have been completed and they require cycles and segments to be executed. There are five main types of periodic allocations: Periodic repostings (periodic transfers), Distribution, Assessment, Imputed Cost Calculation and Indirect Activity Allocation.
11. [True] or False? Periodic allocations require cycles and segments to be executed.
See answer to question 9 above.
12. List three types of periodic allocations.
See Question 9
13. ___________enables the correction of multiple posting made to cost centers during the period, therefore producing the same results as several transaction-based repostings.
Periodic reposting enables the correction of multiple postings made to cost centers during the period, therefore producing the same results as several transaction-based repostings. This reposting functionality can also be utilized at the end of a period to transfer costs from a clearing cost center to appropriate receiving cost centers. When used in this fashion, periodic reposting is very similar to distribution.
The main difference between periodic repostings and distribution is the purpose for usage envisioned by SAP when the methods were created. Periodic reposting functionality, similar to transaction-based repostings, was designed for error correction, whereas distribution was designed as a primary cost allocation method. However, other than their intended purposes, the two methods are practically identical and either method may be used whenever desired.
14. Explain both the iterative and cumulative form of cycle processing.
Iterative processing: iterative sender/receiver relationships (sender is also amongst the receivers) are considered when this cycle is processed. The iteration is repeated until each sender is fully relieved of costs provided. Cycles may be set to iterative processing for both plan and actual data.
Cumulative processing: all posted sender amounts since the first period are accumulated and allocated based on the tracing factors accumulated since this period. The difference between the accumulated amount and the posted amounts in previous periods is posted in the current period. The postings in previous periods remain unchanged. Cycles may be set to cumulative processing for actual data only.
15. Describe imputed cost calculation in CO.
Imputed cost calculations are used to smooth the effect on cost centers for large, one-time charges, such as insurance premiums or employee bonuses. By smoothing one-time expenses in CO, price fluctuations from period to period can be avoided. There are two methods for calculating imputed costs in the R/3 system Cost Element Percent Method and Target = Actuals Method.
16. List and define the two main types of indirect activity allocations.
Indirect activity allocation is the process of allocating activities from a sender to a receiver cost object. The activities allocated to the receiver are multiplied by the planned activity price to determine the total amount.
There are two types of indirect activity allocations:
• Sender activities known
The activity type is allocated from the sender to the receiver based on receiver tracing factors (i.e. actual receiver statistical key figures, planned receiver activity types, etc.)
This type of indirect activity allocation must be set up with an activity type of Category 3. This category is defined for manual entry (of known sender values), using indirect allocation (tracing factors).
• Sender activities unknown
Activities are inversely allocated from the sender cost center using receiver tracing factors or fixed amounts/percentages.
This type of indirect activity allocation must be set up with an activity type of category 2. This category is defined for inverse determination (of sender values based on receiver consumption) using automatic allocation (to receivers).
17. Describe the use of the reconciliation ledger.
The reconciliation ledger keeps track of transactions between company codes within one controlling area, since such cross company allocations result in an imbalance between CO totals and FI totals. Because legal reporting is based in FI, all transactions that cross company codes in CO must be reflected in FI.
Controlling Planning
1. True or False? In SAP Integrated Planning Cycle the planning process begins with a Profit Plan.
False, in SAP Integrated Planning Cycle the planning process begins with a Sales Plan
2. True or False? Sales volumes calculated in sales planning or order volumes stored in the Sales Information System (SIS) can be fed into Production Process.
True, sales volumes calculated in sales planning or order volumes stored in the Sales Information System (SIS) can be fed into Production Process.
3. True or False? A version is a comprehensive set of planning data.
True. A version is a comprehensive set of planning data.
4. True or False? There can be multiple plan versions for “what if analysis”.
True.
5. Each plan version has information set by _____________.
Each plan version has information set by fiscal year.
6. Describe plan revaluation and its use in CO planning.
Revaluation is the process of increasing or decreasing a plan based on a percentage. Different percentages may be specified by cost center or by cost element.
Example: Management states that all planned costs will be at 95% of last year’s planned costs. To implement this directive, copy last year’s planned data into another version. Then revalue the new version by -5%.
Revaluation percentages may be changed at any time. A repeated revaluation with a different percentage reverses all previous revaluations. Revaluations are always based on the original plan values. To prevent resetting the results of a revaluation (during a repeated revaluation), a new revaluation with a different percentage can be defined.
• Value Column: Planning amounts or quantities for the associated lead column(s).
• Lead Column: Contains information describing the nature of the amount in the associated value column, such as cost center, cost element or activity type.
7. Describe what a planning layout is.
A planning layout determines the column and row structure for entering plan data. A layout must be defined for each type of planning to be performed.
8. Describe what a planning profile is.
Planning profiles are used to group planning layouts together. Planning profiles also determine the effective dates or time frame for planning. Multiple planning profiles may be created. Planning profiles can be assigned to user groups.
9. True or False? The planning profiles must be set in the application side for planning to take place.
True, the planning profile to be used must be set into the system from the application side before planning can occur, this tells the system which profile you will be using and defaults in the correct layouts.
10. Describe the steps involved in setting up a plan.
• Define Planner Profile: Assign the layouts previously created to the profile, up to 3 layouts (one for each type of planning), may be assigned.
• Set Planner Profile: Defaults in the appropriate layouts in each area based on the profile.
• Planning Transactions: Enter planning data as required.
11. Define Statistical Key Figure planning.
Statistical Key Figure Planning – Statistical key figures are used in the calculation of plan activity and as allocation bases for distributions and assessments.
12. Define Activity Type Planning.
Activity Type Planning – Planned activity output for a cost center will determine the planned volume of costs. Activity for a sending cost center must be planned before secondary cost planning can take place.
13. Define primary and secondary Cost Planning.
Primary/Secondary Cost Planning – This type of planning is performed last, since activity quantities are required to plan costs.
14. Define Activity Dependent Cost, Activity Independent Cost and Mixed Cost.
• Activity Dependent Costs are variable costs and they are costs that fluctuate based on activity. The greater the activity, the greater the cost. Example: Direct Labor costs that increase as production increases.
• Activity Independent Costs are Fixed Costs. Activity independent costs DO NOT fluctuate based on activity. Example: Insurance expense – regardless of output, insurance premiums will not change.
• Mixed Costs are a combination of both fixed and variable costs, therefore displaying the characteristics of both. Example: Utilities expense – the basic cost of heating a building (fixed portion) would increase as production increases (variable portion).
15. ___________ are used by the system to spread planned amounts across periods.
Distribution Keys are used by the system to spread planned amounts across periods. It allows for the entry of planned annual figures, which are then automatically spread across months.
16. The two automated methods for planning primary costs are _____________.
There are two automated methods for the planning of primary costs, imputed cost calculation and distribution. Cost which has no direct equivalent in FI, such as imputed rents. Cost which has a different equivalent in FI, primarily as it relates to the timing of cost. Imputed cost calculations are used to smooth the effect on cost centers for large, one-time charges, such as insurance premiums or employee bonuses. By smoothing one-time expenses in CO, price fluctuations from period to period can be avoided.
Distribution is the allocation of primary costs from a clearing cost center to the cost center responsible for incurring them. The identity of the primary cost is retained at the receiving cost center. Distribution may be used for allocating planned or actual primary costs only. Distribution simplifies the process of planning primary costs that are attributable to more than one cost center. Instead of manually planning individual amounts to many different cost centers, the total planned expense is planned to a clearing cost center, and the allocation to the receiving cost centers is performed automatically through a distribution cycle. Clearing cost centers (also called pooled cost centers) act as temporary holding areas for costs, they are not responsible for the costs but only exist to facilitate distributions and other allocation methods.
17. Define an Assessment and an Assessment Rule.
Assessment is the allocation of cost from one cost center to one or more other cost centers. The original cost center or the nature of the costs themselves are not retained, but are reclassified as a secondary cost element. Assessment is designed to group together and reclassify costs while simultaneously allocating them. Assessment may be used to allocate both planned and actual primary and secondary costs.
An assessment rule, using fixed amounts, statistical key figures or percentages, is defined to break down the assessment among the receiving cost centers.
18. Define a Cycle and a Segment
Cycles and Segments are utilized by the SAP system to perform automated allocations, such as distributions, assessments and repostings (covered in Ch.5) of both planned and actual costs.
A cycle may be defined as a holding place for the various rules that will define an automated allocation. Cycles are comprised of segments, each segment represents one set of data needed to complete the automated allocation.
A segment consists of the following:
• Allocation Characteristics – Identification of sending and receiving cost centers.
• Sender Values – What types of costs will be allocated, whether they are planned or actual amounts, and what percentage of total sender costs will be allocated.
• Receiver Values (Tracing Factors) – The basis for allocation – percentage, fixed amount or statistical key figure.
19. Describe plan reconciliation.
The plan reconciliation is used to check and reconcile the internal activity exchange. With the plan reconciliation, you can adjust the entire plan activity quantities automatically on the basis of scheduled activity on the cost centers.
20. What is done in the final step of the planning process?
The planning process is completed by performing an Activity Price Calculation within the system. This process calculates an activity price based on planned activities and costs and uses the calculated price to valuate planned secondary costs at receiver cost centers. Alternatively, a political activity price may be used in place of a calculated activity price, but the procedure must still be performed.
21. What is budgeting?
Budgeting may by implemented to augment the planning process. The CCA module supports budgeting at the cost center level. From an SAP standpoint, budgeting represents a top down approach to controlling costs, whereas planning represents a bottom up approach to cost control.
False, in SAP Integrated Planning Cycle the planning process begins with a Sales Plan
2. True or False? Sales volumes calculated in sales planning or order volumes stored in the Sales Information System (SIS) can be fed into Production Process.
True, sales volumes calculated in sales planning or order volumes stored in the Sales Information System (SIS) can be fed into Production Process.
3. True or False? A version is a comprehensive set of planning data.
True. A version is a comprehensive set of planning data.
4. True or False? There can be multiple plan versions for “what if analysis”.
True.
5. Each plan version has information set by _____________.
Each plan version has information set by fiscal year.
6. Describe plan revaluation and its use in CO planning.
Revaluation is the process of increasing or decreasing a plan based on a percentage. Different percentages may be specified by cost center or by cost element.
Example: Management states that all planned costs will be at 95% of last year’s planned costs. To implement this directive, copy last year’s planned data into another version. Then revalue the new version by -5%.
Revaluation percentages may be changed at any time. A repeated revaluation with a different percentage reverses all previous revaluations. Revaluations are always based on the original plan values. To prevent resetting the results of a revaluation (during a repeated revaluation), a new revaluation with a different percentage can be defined.
• Value Column: Planning amounts or quantities for the associated lead column(s).
• Lead Column: Contains information describing the nature of the amount in the associated value column, such as cost center, cost element or activity type.
7. Describe what a planning layout is.
A planning layout determines the column and row structure for entering plan data. A layout must be defined for each type of planning to be performed.
8. Describe what a planning profile is.
Planning profiles are used to group planning layouts together. Planning profiles also determine the effective dates or time frame for planning. Multiple planning profiles may be created. Planning profiles can be assigned to user groups.
9. True or False? The planning profiles must be set in the application side for planning to take place.
True, the planning profile to be used must be set into the system from the application side before planning can occur, this tells the system which profile you will be using and defaults in the correct layouts.
10. Describe the steps involved in setting up a plan.
• Define Planner Profile: Assign the layouts previously created to the profile, up to 3 layouts (one for each type of planning), may be assigned.
• Set Planner Profile: Defaults in the appropriate layouts in each area based on the profile.
• Planning Transactions: Enter planning data as required.
11. Define Statistical Key Figure planning.
Statistical Key Figure Planning – Statistical key figures are used in the calculation of plan activity and as allocation bases for distributions and assessments.
12. Define Activity Type Planning.
Activity Type Planning – Planned activity output for a cost center will determine the planned volume of costs. Activity for a sending cost center must be planned before secondary cost planning can take place.
13. Define primary and secondary Cost Planning.
Primary/Secondary Cost Planning – This type of planning is performed last, since activity quantities are required to plan costs.
14. Define Activity Dependent Cost, Activity Independent Cost and Mixed Cost.
• Activity Dependent Costs are variable costs and they are costs that fluctuate based on activity. The greater the activity, the greater the cost. Example: Direct Labor costs that increase as production increases.
• Activity Independent Costs are Fixed Costs. Activity independent costs DO NOT fluctuate based on activity. Example: Insurance expense – regardless of output, insurance premiums will not change.
• Mixed Costs are a combination of both fixed and variable costs, therefore displaying the characteristics of both. Example: Utilities expense – the basic cost of heating a building (fixed portion) would increase as production increases (variable portion).
15. ___________ are used by the system to spread planned amounts across periods.
Distribution Keys are used by the system to spread planned amounts across periods. It allows for the entry of planned annual figures, which are then automatically spread across months.
16. The two automated methods for planning primary costs are _____________.
There are two automated methods for the planning of primary costs, imputed cost calculation and distribution. Cost which has no direct equivalent in FI, such as imputed rents. Cost which has a different equivalent in FI, primarily as it relates to the timing of cost. Imputed cost calculations are used to smooth the effect on cost centers for large, one-time charges, such as insurance premiums or employee bonuses. By smoothing one-time expenses in CO, price fluctuations from period to period can be avoided.
Distribution is the allocation of primary costs from a clearing cost center to the cost center responsible for incurring them. The identity of the primary cost is retained at the receiving cost center. Distribution may be used for allocating planned or actual primary costs only. Distribution simplifies the process of planning primary costs that are attributable to more than one cost center. Instead of manually planning individual amounts to many different cost centers, the total planned expense is planned to a clearing cost center, and the allocation to the receiving cost centers is performed automatically through a distribution cycle. Clearing cost centers (also called pooled cost centers) act as temporary holding areas for costs, they are not responsible for the costs but only exist to facilitate distributions and other allocation methods.
17. Define an Assessment and an Assessment Rule.
Assessment is the allocation of cost from one cost center to one or more other cost centers. The original cost center or the nature of the costs themselves are not retained, but are reclassified as a secondary cost element. Assessment is designed to group together and reclassify costs while simultaneously allocating them. Assessment may be used to allocate both planned and actual primary and secondary costs.
An assessment rule, using fixed amounts, statistical key figures or percentages, is defined to break down the assessment among the receiving cost centers.
18. Define a Cycle and a Segment
Cycles and Segments are utilized by the SAP system to perform automated allocations, such as distributions, assessments and repostings (covered in Ch.5) of both planned and actual costs.
A cycle may be defined as a holding place for the various rules that will define an automated allocation. Cycles are comprised of segments, each segment represents one set of data needed to complete the automated allocation.
A segment consists of the following:
• Allocation Characteristics – Identification of sending and receiving cost centers.
• Sender Values – What types of costs will be allocated, whether they are planned or actual amounts, and what percentage of total sender costs will be allocated.
• Receiver Values (Tracing Factors) – The basis for allocation – percentage, fixed amount or statistical key figure.
19. Describe plan reconciliation.
The plan reconciliation is used to check and reconcile the internal activity exchange. With the plan reconciliation, you can adjust the entire plan activity quantities automatically on the basis of scheduled activity on the cost centers.
20. What is done in the final step of the planning process?
The planning process is completed by performing an Activity Price Calculation within the system. This process calculates an activity price based on planned activities and costs and uses the calculated price to valuate planned secondary costs at receiver cost centers. Alternatively, a political activity price may be used in place of a calculated activity price, but the procedure must still be performed.
21. What is budgeting?
Budgeting may by implemented to augment the planning process. The CCA module supports budgeting at the cost center level. From an SAP standpoint, budgeting represents a top down approach to controlling costs, whereas planning represents a bottom up approach to cost control.
Controlling Variance Analysis
1. What is the purpose of variance analysis?
Variance analysis is used to calculate and interpret differences between planned costs and actual cost within a cost center or cost center group. It also provides vital information that can be used to modify and improve planning in subsequent periods.
2. All variances in SAP can be classified as what two types of variances?
• Input Side Variance
• Output Side Variance
3. True or False? In SAP, Variance analysis can only be done in plan version 0.
True. Variance analysis can only be done in plan version 0; because, plan version 0 is the only planning version that can have actuals posted to it.
4. What are four input side variances SAP can identify?
• Price Variance
• Quantity Variance
• Resource Usage Variance
• Input Variance
5. Give an example and a root cause for a Price Variance.
Example: Wage increase from 12.00 to 12.50 an hour. Cause: Cost of living adjustment not accounted for in planning wages.
6. Give a mathematical formula for Price Variance
(Planed Price — Actual Price) X Quantity Planed
7. Give an example and a root cause for a Quantity Variance.
Example: Reduction in the hours it takes to produce a widget. Cause: Productivity increase not planned due to PwC reengineering efforts that exceeding company’s expectations.
8. Give a mathematical formula for Quantity Variance
Planed Price X (Planned Quantity- Actual Quantity)
9. Give an example and a root cause for a Resource Usage Variance
Example: Cost Element posted to wrong Cost Center. Cause: Error in planning or actual posting.
10. Give an example and a root cause for a Input Variance
Example: Cost element were planned and posted in actual, but no consumption quantities were recorded. Cause: Consumption quantity unknown during variance analysis.
11. What are the types of output side variances SAP can identify?
• Output Price Variance
• Volume Variance
• Output Quantity Variance
• Remaining Variance
12. What is the difference between an “Output Price Variance” and a “Price Variance” as defined in SAP?
• Output Price Variance is an output side variance
• Price Variance is an input side variance
13. Give an example and a root cause for a Volume Variance.
Example: 1000 man hours are planed for maintenance at 10 dollars. In actual 1100 hours of maintenance is produced by the maintenance cost center. Cause: Unforeseen requirement for additional maintenance.
14. What is the two step Process for calculating a Variance
Configuration
• Create Variance Variant
• Maintain Target Version
Execution
• Enter Parameters
• Execute Variance Calculation
• Print Variance Report
15. How many variances can be activated by the user in the variance variants?
4 input and 3 output
16. What is the purpose of the Variance Variant?
It indicates to the system which variance the system should attempt to calculate and identify during execution of the variance calculations
17. How can additional information be obtained on the cause of a variance, After running a Variance Report?
The drill-down function may be used for each line item
18. What are some of the options available to fully relieve all remaining cost, after variances have been calculated and reported?
• Sweep the remaining balance into another module (Such as PA) for further analysis
• Perform additional allocations within CCA to move all variance amounts to one or more other cost centers
• Perform an Actual Activity Price Calculation.
Variance analysis is used to calculate and interpret differences between planned costs and actual cost within a cost center or cost center group. It also provides vital information that can be used to modify and improve planning in subsequent periods.
2. All variances in SAP can be classified as what two types of variances?
• Input Side Variance
• Output Side Variance
3. True or False? In SAP, Variance analysis can only be done in plan version 0.
True. Variance analysis can only be done in plan version 0; because, plan version 0 is the only planning version that can have actuals posted to it.
4. What are four input side variances SAP can identify?
• Price Variance
• Quantity Variance
• Resource Usage Variance
• Input Variance
5. Give an example and a root cause for a Price Variance.
Example: Wage increase from 12.00 to 12.50 an hour. Cause: Cost of living adjustment not accounted for in planning wages.
6. Give a mathematical formula for Price Variance
(Planed Price — Actual Price) X Quantity Planed
7. Give an example and a root cause for a Quantity Variance.
Example: Reduction in the hours it takes to produce a widget. Cause: Productivity increase not planned due to PwC reengineering efforts that exceeding company’s expectations.
8. Give a mathematical formula for Quantity Variance
Planed Price X (Planned Quantity- Actual Quantity)
9. Give an example and a root cause for a Resource Usage Variance
Example: Cost Element posted to wrong Cost Center. Cause: Error in planning or actual posting.
10. Give an example and a root cause for a Input Variance
Example: Cost element were planned and posted in actual, but no consumption quantities were recorded. Cause: Consumption quantity unknown during variance analysis.
11. What are the types of output side variances SAP can identify?
• Output Price Variance
• Volume Variance
• Output Quantity Variance
• Remaining Variance
12. What is the difference between an “Output Price Variance” and a “Price Variance” as defined in SAP?
• Output Price Variance is an output side variance
• Price Variance is an input side variance
13. Give an example and a root cause for a Volume Variance.
Example: 1000 man hours are planed for maintenance at 10 dollars. In actual 1100 hours of maintenance is produced by the maintenance cost center. Cause: Unforeseen requirement for additional maintenance.
14. What is the two step Process for calculating a Variance
Configuration
• Create Variance Variant
• Maintain Target Version
Execution
• Enter Parameters
• Execute Variance Calculation
• Print Variance Report
15. How many variances can be activated by the user in the variance variants?
4 input and 3 output
16. What is the purpose of the Variance Variant?
It indicates to the system which variance the system should attempt to calculate and identify during execution of the variance calculations
17. How can additional information be obtained on the cause of a variance, After running a Variance Report?
The drill-down function may be used for each line item
18. What are some of the options available to fully relieve all remaining cost, after variances have been calculated and reported?
• Sweep the remaining balance into another module (Such as PA) for further analysis
• Perform additional allocations within CCA to move all variance amounts to one or more other cost centers
• Perform an Actual Activity Price Calculation.
Controlling Master Data
1. List the five types of master data in cost center accounting (CCA).
• Cost centers
• Cost elements
• Activity types
• Statistical key figures
• Resources
2. What characteristics do the master data types in CCA share?
• Time dependency (except for SKF)
• Can not be deleted once transaction data has been posted (except for SKF and resources)
• Can be arranged in groups (except for SKF)
3. Name the two types of cost elements and explain them.
Primary cost elements: They originate from outside the CO module (i.e. posted through FI). They have counter-parts in FI and are used as a method for moving costs into the CO module.
Secondary cost elements: Originate from within CO and have no FI counter-part. Secondary cost elements are used as a tool for moving costs for internal reporting within CO. They exist exclusively in CO.
4. True or False? Once a cost center has been created, the open or validity period of such center cannot be changed.
True. CCA master data is time dependent and once created cannot be changed. However, creating a new item and attaching its date range to the original date range may extend the effective date.
5. Define a cost center group.
A cost center group is a hierarchical structure consisting of nodes and attached cost centers. Cost center groups can facilitate the analysis of costs by allowing costs to be reported on the cost center level or at the group level.
6. Define the Standard Hierarchy and explain its use.
The standard hierarchy must, by definition, contain all cost centers from all company codes attached to the controlling area. This ensures that all costs posted in FI and assigned to a cost center are captured in CO.
7. True or False? All cost centers must be attached to either the standard hierarchy or an alternate hierarchy (cost center group).
False. All cost centers must be attached to the standard hierarchy in order to ensure that all costs posted in FI are captured in CO. They may furthermore be attached to as many alternate hierarchies (cost center groups) as desired.
8. True or False? Cost centers can be attached at any node level within the hierarchical structure.
False. Cost centers can only be attached to the lowest node levels within the hierarchical structure.
9. True or False? A cost center cannot be attached to more than one alternate hierarchy.
False.
10. Define activity types.
Activity types are units of measurement for the internal allocation of costs from within CO. Activity types define the main cost drivers or services performed by a cost center. Examples include direct labor hours, machine hours and maintenance hours.
11. Define activity price.
Activity types are used to derive the activity price. The total costs are divided by the total planned or actual activity quantity to derive the activity price (cost / activity type unit).
12. Provide two examples of statistical key figures.
Statistical key figures are derived from non-financial statistical data, such as the number of telephones or the square footage of a building. Statistical key figures are used for the allocation or planning of costs.
13. What are Resources?
Resources are goods and services, which are supplied internally and externally to an organization in order to produce business activities. They Resources are used to carry out detailed, quantity-based primary cost planning below the cost element level for cost centers, orders and WBS elements.
14. Name the two types of internal orders and explain the major distinctions.
An Individual Order collects costs of a one-time business activity. This order is typically settled in full at the time of completion and is closed after settlement.
A Standing Order collects costs for smaller, recurring jobs. These costs are settled on a periodic basis (typically at month-end). After settlement the order remains open for postings. The benefit of a Standing Order is, not having to create a new order for the same costs each month.
15. Define statistical orders.
A Statistical Internal Order can be defined to collect costs for informational purposes only and therefore need a real cost assignment (e.g. to a cost center) at the same time. The costs posted to a statistical internal order are not settled.
• Cost centers
• Cost elements
• Activity types
• Statistical key figures
• Resources
2. What characteristics do the master data types in CCA share?
• Time dependency (except for SKF)
• Can not be deleted once transaction data has been posted (except for SKF and resources)
• Can be arranged in groups (except for SKF)
3. Name the two types of cost elements and explain them.
Primary cost elements: They originate from outside the CO module (i.e. posted through FI). They have counter-parts in FI and are used as a method for moving costs into the CO module.
Secondary cost elements: Originate from within CO and have no FI counter-part. Secondary cost elements are used as a tool for moving costs for internal reporting within CO. They exist exclusively in CO.
4. True or False? Once a cost center has been created, the open or validity period of such center cannot be changed.
True. CCA master data is time dependent and once created cannot be changed. However, creating a new item and attaching its date range to the original date range may extend the effective date.
5. Define a cost center group.
A cost center group is a hierarchical structure consisting of nodes and attached cost centers. Cost center groups can facilitate the analysis of costs by allowing costs to be reported on the cost center level or at the group level.
6. Define the Standard Hierarchy and explain its use.
The standard hierarchy must, by definition, contain all cost centers from all company codes attached to the controlling area. This ensures that all costs posted in FI and assigned to a cost center are captured in CO.
7. True or False? All cost centers must be attached to either the standard hierarchy or an alternate hierarchy (cost center group).
False. All cost centers must be attached to the standard hierarchy in order to ensure that all costs posted in FI are captured in CO. They may furthermore be attached to as many alternate hierarchies (cost center groups) as desired.
8. True or False? Cost centers can be attached at any node level within the hierarchical structure.
False. Cost centers can only be attached to the lowest node levels within the hierarchical structure.
9. True or False? A cost center cannot be attached to more than one alternate hierarchy.
False.
10. Define activity types.
Activity types are units of measurement for the internal allocation of costs from within CO. Activity types define the main cost drivers or services performed by a cost center. Examples include direct labor hours, machine hours and maintenance hours.
11. Define activity price.
Activity types are used to derive the activity price. The total costs are divided by the total planned or actual activity quantity to derive the activity price (cost / activity type unit).
12. Provide two examples of statistical key figures.
Statistical key figures are derived from non-financial statistical data, such as the number of telephones or the square footage of a building. Statistical key figures are used for the allocation or planning of costs.
13. What are Resources?
Resources are goods and services, which are supplied internally and externally to an organization in order to produce business activities. They Resources are used to carry out detailed, quantity-based primary cost planning below the cost element level for cost centers, orders and WBS elements.
14. Name the two types of internal orders and explain the major distinctions.
An Individual Order collects costs of a one-time business activity. This order is typically settled in full at the time of completion and is closed after settlement.
A Standing Order collects costs for smaller, recurring jobs. These costs are settled on a periodic basis (typically at month-end). After settlement the order remains open for postings. The benefit of a Standing Order is, not having to create a new order for the same costs each month.
15. Define statistical orders.
A Statistical Internal Order can be defined to collect costs for informational purposes only and therefore need a real cost assignment (e.g. to a cost center) at the same time. The costs posted to a statistical internal order are not settled.
Controlling Organizational Structure
1. True or False? A controlling area has a one to one relationship with company codes.
False. A controlling area has a one to one relationship with the chart of account and, a one to many relationship with company codes.
2. After the controlling area has been configured, the assignment of company codes cannot be changed.
[True] or False.
3. When a number of company codes are assigned to a controlling area, cross company code accounting is possible. However, each company code must share what three attributes:
• The same chart of accounts
• The same fiscal year variant and year end date (the same fiscal year variant must be assigned to the controlling area and to all attached company codes)
• The same standard hierarchy of cost centers
4. Name three types of cost objects used in the CO.
• Cost centers
• Internal orders
• Profitability segment
5. If the controlling area currency is the same as the company code currency, the object currency is freely definable.
[True] or False.
6. Define the document currency.
The document currency is the currency of the transaction. The document currency is defined at the time the document is entered.
7. Define account assignment objects in CO and name three of them.
Account assignment objects in CO represent units to which costs are assigned. They are used to collect costs (‘cost bucket’) and can be planned and budgeted on. Three examples: cost center, internal order, business process.
8. CO number ranges are defined on company code level.
[True] or [False]. CO number ranges are defined for each controlling area.
False. A controlling area has a one to one relationship with the chart of account and, a one to many relationship with company codes.
2. After the controlling area has been configured, the assignment of company codes cannot be changed.
[True] or False.
3. When a number of company codes are assigned to a controlling area, cross company code accounting is possible. However, each company code must share what three attributes:
• The same chart of accounts
• The same fiscal year variant and year end date (the same fiscal year variant must be assigned to the controlling area and to all attached company codes)
• The same standard hierarchy of cost centers
4. Name three types of cost objects used in the CO.
• Cost centers
• Internal orders
• Profitability segment
5. If the controlling area currency is the same as the company code currency, the object currency is freely definable.
[True] or False.
6. Define the document currency.
The document currency is the currency of the transaction. The document currency is defined at the time the document is entered.
7. Define account assignment objects in CO and name three of them.
Account assignment objects in CO represent units to which costs are assigned. They are used to collect costs (‘cost bucket’) and can be planned and budgeted on. Three examples: cost center, internal order, business process.
8. CO number ranges are defined on company code level.
[True] or [False]. CO number ranges are defined for each controlling area.
SAP Taxes
1. Briefly explain the difference between a value-added tax and sales and use tax.
Value-added taxes are assessed on the additional value that is added to a product as it moves through the production chain from raw material to producer and finally to the consumer. Sales and use taxes are based on the final sales value of the product.
2. For what are jurisdiction codes used?
Jurisdiction codes are used in multi-level taxes to identify each taxing authority. When using jurisdiction codes, each level must be defined. For example, if there is a state, county and city sales tax then the following three codes would be created:
• State: 2500000000
• County: 2510200000
• City: 2510280930
3. Briefly describe the following:
a) Calculation Table – Contains all of the logic for calculating taxes including the access sequence, condition type, and tax procedure.
b) Tax Procedure – A country-specific template containing all of the processing logic and algorithms that support the tax amount computations. It contains the steps, condition types, reference steps, and account keys
c) Tax Code – Assigned to a tax procedure and is entered in the G/L master record and accessed when the G/L account is used in a document.
4. What settings are necessary for automatic tax account assignment?
The account key must be configured with posting keys, rules, and tax accounts. The rules determine if the tax code or account key will be used for account determination.
5. How can taxes be calculated?
Taxes may be calculated automatically by the system or entered manually by the user. In the case of manual entry, the system will verify that the amount entered is correct.
Value-added taxes are assessed on the additional value that is added to a product as it moves through the production chain from raw material to producer and finally to the consumer. Sales and use taxes are based on the final sales value of the product.
2. For what are jurisdiction codes used?
Jurisdiction codes are used in multi-level taxes to identify each taxing authority. When using jurisdiction codes, each level must be defined. For example, if there is a state, county and city sales tax then the following three codes would be created:
• State: 2500000000
• County: 2510200000
• City: 2510280930
3. Briefly describe the following:
a) Calculation Table – Contains all of the logic for calculating taxes including the access sequence, condition type, and tax procedure.
b) Tax Procedure – A country-specific template containing all of the processing logic and algorithms that support the tax amount computations. It contains the steps, condition types, reference steps, and account keys
c) Tax Code – Assigned to a tax procedure and is entered in the G/L master record and accessed when the G/L account is used in a document.
4. What settings are necessary for automatic tax account assignment?
The account key must be configured with posting keys, rules, and tax accounts. The rules determine if the tax code or account key will be used for account determination.
5. How can taxes be calculated?
Taxes may be calculated automatically by the system or entered manually by the user. In the case of manual entry, the system will verify that the amount entered is correct.
SAP Asset Accounting FAQs – Old Assets Data Master
1.Base on quantity, what are the three methods of old asset data transfer? In what status does the company code have to be so that the transfer is possible?
1) small quantity - Create old asset manually (dialog transaction)
2) large quantity - Batch-input procedure (RAALTD01)
3) very large quantity – Direct data import (RAALTD11)
The company code must be set up to the status for old assets data takeover when no posting is possible.
2.True or False? With the old assets data transfer through any of the three methods, appropriate G/L accounts in Financial Accounting are updated.
False. Balance reconciliation with the relevant G/L accounts must take place separately. G/L personnel can input these via FI or AA personnel can input them via the transfer balance screen in AA With up-to-date accounts in the already productive FI there is no need to update them.
3.What are the two possibilities for the transfer date.
• At the end of the last closed fiscal year
• In the fiscal year following the last closed fiscal year
4.What data is transferred at the year-end transfer and the sub-annual transfer?
Year-end transfer and transfer during fiscal year:
• Master data
• Cumulative values as of the end of the last closed fiscal year
Sub-annual transfer (if the transfer date after the closed fiscal year)
• Master data
• Cumulative values as of the end of the last closed fiscal year
• Depreciation and asset transactions posted in the current year (transfer parameters)
5.Explain the two methods of transferring the depreciation posted in the current year.
• Transferring the depreciation posted in the current fiscal year up to the point of transfer- it is necessary to specify the last posted depreciation period In the legacy system for each depreciation area for every asset company code.
• Posting the total depreciation for the current fiscal year up until the transfer date after the old data transfer –it is done in AA by performing a posting run for unplanned depreciation.
6.Which activities should be done before the production start-up? Give a brief description of each of them.
• Check consistency – major components configured, i.e. chart of depreciation, company codes, depreciation areas, asset classes, asset G/L accounts, AA customizing
• Reset company code – test application data can be deleted (asset master records and transactions of AA) but only of the company code has a test status. Customizing settings are not deleted.
• Reset posted depreciation – this function is performed when errors occurred during testing the depreciation posting run and it is necessary to return to the original status (includes depreciation data of an old assets data transfer). Manual adjustments in the relevant G/L expense and depreciation accounts need to be performed. The reset is possible only for a company code in a test status.
• Set/reset reconciliation accounts – The G/L accounts relevant for AA are defined as reconciliation accounts by a report changing their master records. After the transfer date these accounts can no longer be directly posted to.
• Transfer balances – Balances to the G/L accounts, which have been defined as reconciliation accounts, are transferred. (old data at fiscal year end)
• Activate company code – This function terminates the production start–up.
Asset FAQ’s.
1.Describe the function of depreciation areas.
Depreciation area 01, which can be set up as the book depreciation, can make automatic postings to the general ledger. Other depreciation areas may get their values from depreciation area 01 but calculate and post different depreciation values to the general ledger. Other depreciation areas can be set up to show: country specific valuation (i.e., tax depreciation); values/depreciations that differ from depreciation area 01 (i.e., cost-accounting reasons); consolidated versions in local/group currency, book depreciation in group currency; and the difference between book, 01, and country-specific tax depreciation (‘derived depreciation area’).
2.What information (sections) are included in the asset class?
An asset class consists of three main sections:
• A header, containing control parameters for master data maintenance and account determination,
• A master data section with default values for administrative data in the asset master record,
• A valuation section with control parameters for valuation and depreciation terms.
3.Describe the function of an asset class.
The most important function of an asset class is to establish the connection between the asset master records and the relevant accounts in the general ledger. The account determination in the asset class determines the posting top the general ledger accounts. Several asset classes can use the same account determination assuming the asset classes use the same chart of accounts and post to the same general ledger accounts.
4.If the company code is in implementation status and assets exist in an asset class with no transactions, you can delete and add new asset classes.
[True] or False
When the company code is in implementation status:
• No assets have been created in an existing asset class; this class is deleted and generated again
• There are assets in an existing asset class (but no transactions)
- Delete all asset classes and their assets and generate them again or
- Only add new asset classes.
• Transactions exist for the assets: you can only add new asset classes
If the company code is in production status: the system creates only asset classes that were not yet created. Exiting classes remain unchanged.
6.Define maintenance level. What are the possible maintenance levels?
Maintenance level defines the level (asset class, main asset number, sub-number) at which a field in an asset master record is to be maintained. Maintenance level definition is part of the screen layout rule.
If, for example, you define the maintenance level ‘main asset number’ for a field, then the field will be filled with a default value from the asset class. However you will be able to change the field when maintaining master data at the asset main number level.
The three maintenance levels are:
• Asset class
• Asset main number
• Asset sub-number
7.What significance is depreciation key ‘0000’?
Depreciation key ‘0000’ is a SAP delivered key that ensures depreciation and interest is not calculated and posted. This key can be used for the assets under construction, however, special tax depreciation and investment support are possible even on assets under construction.
8.What are the options for creating and asset master record?
The two options for creating an asset master record are:
• Use the asset class, to which the asset will belong, to provide default values. The asset class then supplies the most important control parameters in the asset master record.
• Use an existing asset as a reference for creating the new asset master record (possibly the reference asset has default values that are more suitable than those in the asset class).
9.Why might assets be divided up using sub-numbers?
A complex fixed asset can be represented in the system using several master records, that is, sub-numbers. Assets may be divided using sub-numbers if:
• Managing the values for subsequent acquisitions in following years (i.e., buildings) separately
• Managing the values for individual parts of assets separately,
• Dividing the asset according to various technical aspects.
10.Define work lists.
Work lists are used for mass retirements, mass changes and work on incomplete assets. There are three steps in using work lists:
• Select the objects (assets) to be changed
• Assign the task to be performed on the objects
• Release the work list and process the Workflow
1.Define a transaction type.
During the life of an asset there are a number of changes that affect the value of the asset. The FI-AA System recognizes a wide range of business transactions. Transaction types make it possible to handle all of the necessary postings appropriately.
2.It is possible that an asset acquisition is posted in two steps or in two different departments? How do the two entries clear?
When the asset acquisition is posted in two steps or two different departments, you normally post to a clearing account. Use a general ledger account with open item management to guarantee that this account can be cleared. Either the FI department includes this clearing account in their periodic run of SAPF123 (Automatic clearing program) or the clearing account has to be cleared in an additional step (Menu path: Posting > Acquisition > External acquisition > Clearing offsetting entry).
3.What is the difference between non-valued and valued? Explain their implications on Asset Accounting.
For non-valued, the goods receipt takes place before the invoice receipt and the values are not yet posted to Asset Accounting. The line items are created and the values are updated instead at the time of the invoice receipt. However, the system uses the date of the goods receipt as the capitalization date. At time of invoice receipt the asset is capitalized, line items are created, and the value fields are updated.
For valued, the goods receipt takes place before the invoice receipt and the values are posted directly to Asset Accounting. The asset is capitalized, line items are created, and the value fields in the asset are updated. When the invoice is received later, there may be differences between the invoice amount and the amount posted at the time of goods receipt. In this case, the corresponding adjustment postings are made to the asset.
4.There are certain pieces of information automatically set in the asset master record at time of acquisition. What are they?
The following information is automatically set in the asset master record at the time of the first acquisition posting:
• Date of capitalization
• Posting date of original acquisition
• Acquisition period
• Depreciation start date per depreciation area.
5.Most asset transfers are described as either inter-company or intra-company. What is the difference?
Inter-company transfer indicates a transfer between company codes. This transfer creates a new record at the target company and posts the values according to the posting method selected.
Intra-company transfer indicates a transfer within one company. Reasons for such a transfer include:
• The asset has changed location. As a result, you have to change organizational allocations (i.e., asset class, business area) in the master record that cannot otherwise be changed.
• The asset needs to split. Therefore, a portion of the original asset will be transferred to a new asset.
• The asset under construction needs to transfer its costs to a real (depreciable) asset.
6.Define transfer variant.
The transfer variant specifies:
• The method according to which the transferred asset is valued in the receiving company code
• The transaction types (retirement/acquisition) that are used for the transfer
Your specification of the transfer variant can be dependent on the following:
• The type of relationship between the company codes involved (legally dependent/independent)
• The cross-system depreciation area
7.For assets that the company produces itself, why are there two phases relevant to Asset Accounting? What are they?
The two phases relevant to Asset Accounting for assets produced in house are the under construction phase and the useful life phase. The assets have to be shown in two different balance sheet items during these two phases. Therefore, they have to be managed using a different object or asset master record for the under-construction phase and for the completed asset. The transfer from under-construction phase to completed asset is referred to as “capitalization of the asset under construction”.
8.True or False? Using the Asset Accounting module, it is no longer necessary or possible to manually plan depreciation.
False. In addition to the automatic calculation of depreciation using depreciation keys, you can also plan manual depreciation for individual assets in the FI-AA system.
Organizational Structure
1.What is the Asset Accounting sub-module?
The Asset Accounting sub-module manages a company’s fixed assets. Within the Financial Accounting system, FI-AA serves as a sub-ledger to the General Ledger, providing detailed information on asset-related transactions.
2.Define the chart of depreciation.
The chart of depreciation contains the defined depreciation areas. It also contains the rules for the evaluation of assets that are valid in a given country or economic area. The chart of depreciation is a catalog of country-specific depreciation areas structured to meet the various business needs.
Each company code is allocated to one chart of depreciation. Several company codes can work with the same chart of depreciation.
3.What is the difference between the chart of accounts and chart of depreciation?
The chart of accounts can be global, country specific and industry specifics based on the needs of the business. The chart of depreciation is only country specific. The charts are independent of each other.
4.How is Asset Accounting integrated with Cost Accounting (CO)?
Postings to depreciation can be made through a cost object such as a cost center or internal order. Also, an asset can be assigned to a cost center, internal order, activity type, or a maintenance order.
5.What is an asset class?
This is the main criterion for classifying assets by business and legal requirements. The asset class, created at the client level, consists of a master data and depreciation area section. Each asset master record must be allocated to one asset class.
6.Define depreciation area.
A depreciation area shows the valuation of assets for a particular purpose (for example, for individual financial statements, balance sheets for tax purposes, and cost accounting values).
SAP Asset Accounting – Information Systems
1.True or False? – The Asset Accounting Information System is a hierarchical structure containing standard reports creating a report tree that cannot be changed.
False. The standard reports provided by SAP can be copied and modified. Branches can be added or removed from a report tree.
2.What is the asset value display used for?
Asset value display offers extensive possibilities for planned as well as already posted asset values. For example, it is possible to compare results from different depreciation areas, simulate asset values over time, view posted transactions, and execute reports.
3.Describe simulation in the context of AA and simulation versions.
Simulation in the AA context is an experimental change to parameters affecting the valuation of assets. It can apply to a single asset, the entire asset portfolio, or a test depreciation area.
Simulation versions allow you to simulate a change in depreciation method (depreciation key and useful life) for asset value/depreciation reports and this way to forecast asset depreciation.
4.Describe the Asset History Sheet.
The asset history sheet is the most important and most comprehensive year-end report or intermediate report. It displays the various stages of a fixed asset’s history – from the opening balance through the closing balance – including any acquisitions, retirements or accumulated depreciation. SAP supplies country-specific versions of the sheet. It is often a required appendix to the balance sheet.
5.What is a sort version, and what is the maximum number of sort levels in a sort version?
The sort version defines the formation of groups and totals in an asset report. All fields of the asset master record can be used as group and/or sort criteria for defining of a sort version. It consists of a maximum of 5 sort levels determined via fields.
SAP Asset Accounting – Valuation and Periodic Processing
1.What is periodic processing, and what is it used for in Asset Accounting?
Periodic processing comprises the tasks that must be performed at periodic intervals. Since only the values from one depreciation area can be automatically posted online in Financial Accounting, the changes to asset values (transactions) from other areas with automatic postings have to be posted periodically to the appropriate reconciliation accounts.
2.What is the role of a depreciation area in handling different types of valuation? Why do we need to handle different types of valuation?
By using various depreciation areas that differ from each other in
• kinds of depreciation (ordinary, special, unplanned depreciation)
• depreciation terms (depreciation method, useful life)
• base values for depreciation calculation (APC, replacement value)
It is possible to perform different valuation and meet the calculation needs for specific purposes (e.g., balance sheet, cost accounting or taxes).
3.The system supports three direct types of depreciation. What are they? Define them.
• Ordinary depreciation is the planned reduction in asset value due to normal wear and tear. Therefore, the calculation of depreciation should be based on the normal expected useful life.
• Special depreciation represents depreciation that is solely based on tax regulations. In general, this form of depreciation allows depreciation by percentage within a tax concession period without taking into account the actual wear and tear of the asset.
• Unplanned depreciation is concerned with unusual circumstances, such as damage to the asset that leads to a permanent reduction in its value.
4.True or False? Depreciation is calculated by solely using the depreciation keys, which are defined at the chart of depreciation level and available in all company codes.
False. The depreciation keys are defined at the chart of depreciation level. Therefore, they are available in all company codes. SAP supplies depreciation keys for every chart of depreciation. The system calculates depreciation using depreciation keys and internal calculation keys.
5.What is a depreciation key and internal calculation key?
Depreciation key is used for calculating depreciation amounts. It controls automatic calculation of planned depreciation, interest and maximum percentage for manual depreciation.
Internal calculation key makes up a part of the depreciation key and it defines a method, base value and rate of percentage for depreciation, changeover rules (for declining depreciation), treatment of depreciation after useful life and period control for transactions.
6.Define derived depreciation area.
A derived depreciation area is calculated from two or more real areas using a calculation formula. You can use derived depreciation areas, for example, to calculate special reserves as the difference between tax and book depreciation. The book value rule in a derived depreciation area is checked each time a posting is made or depreciation is changed in the corresponding real area.
7.True or False? Generally, the system determines the depreciation start date from the asset value date of the first acquisition posting.
True.
8.True or False? If the definition of the depreciation key or depreciation terms is changed depreciation values are recalculated automatically. Only if the depreciation terms change values are recalculated
False.
9.When imputed interest is calculated, how does the system post this expense to the CO (Cost Accounting) module?
For cost accounting, you might have to calculate imputed interest on the capital tied up in assets. The system posts interest simultaneously during the periodic depreciation posting run. It posts to the accounts that are entered in the relevant account determination for each depreciation area. Furthermore, an additional account assignment can be made to the cost center or the internal order entered in each asset master record (same for depreciation).
10. What does the system use to calculate the replacement values, and what are the two ways of calculating the current replacement value?
Index series entered in the asset or in the asset class.
The two ways of calculating the current replacement value are historical (current year: acquisition year) and normal (current year: previous year).
11. True or False? The depreciation posting program automatically updates the asset values and G/L accounts. The program generates a batch-input session for the update of the G/L accounts.
False.
12. True or False? Replacement value of an asset can be determined by using an index series.
True. The “indexed replacement values” component makes it possible to calculate replacement values for assets, and to use replacement values as the basis for calculating depreciation. You determine the replacement value using index series. You enter the index series in the asset or in the asset class.
13. True or False? When the depreciation posting program (RABUCH00) is run, the system posts individual documents for the different depreciation types.
False. The depreciation posting program RABUCH00 updates the assets values and generates a batch-input session for the update of the general ledger. The posting session also posts the different depreciation types, interest and revaluation, in addition to the writing-off and allocation of special reserves. The system does not create individual documents, only summarized posting documents (per business area per account determination).
14. For automatic depreciation postings, should the document type be assigned an external or internal number range?
For each company code a document type must be defined for posting depreciation. The depreciation program should only use a document type that is limited to being used for batch input. In this way, unintentional use of the document type can be prevented. It is also essential that the document type is assigned a number range with an external number assignment. The depreciation program can then assign the document numbers itself. If the numbers are assigned in this way, the depreciation posting program can keep a check on posting to Financial Accounting. If errors occur, this numbering also makes it possible to make corrections.
15. Explain the difference between the methods for distributing forecasted depreciation to the posting periods.
The smoothing method distributes depreciation evenly to the periods from the current depreciation period to the end of the fiscal year (regardless of the value date of the transaction).
With the catch-up method, the depreciation on the transaction (from the start of capitalization up to the current period) is posted as a lump sum. The depreciation posting program, posts this amount in the posting period, in which the value date of the transaction lies.
1.Base on quantity, what are the three methods of old asset data transfer? In what status does the company code have to be so that the transfer is possible?
1) small quantity - Create old asset manually (dialog transaction)
2) large quantity - Batch-input procedure (RAALTD01)
3) very large quantity – Direct data import (RAALTD11)
The company code must be set up to the status for old assets data takeover when no posting is possible.
2.True or False? With the old assets data transfer through any of the three methods, appropriate G/L accounts in Financial Accounting are updated.
False. Balance reconciliation with the relevant G/L accounts must take place separately. G/L personnel can input these via FI or AA personnel can input them via the transfer balance screen in AA With up-to-date accounts in the already productive FI there is no need to update them.
3.What are the two possibilities for the transfer date.
• At the end of the last closed fiscal year
• In the fiscal year following the last closed fiscal year
4.What data is transferred at the year-end transfer and the sub-annual transfer?
Year-end transfer and transfer during fiscal year:
• Master data
• Cumulative values as of the end of the last closed fiscal year
Sub-annual transfer (if the transfer date after the closed fiscal year)
• Master data
• Cumulative values as of the end of the last closed fiscal year
• Depreciation and asset transactions posted in the current year (transfer parameters)
5.Explain the two methods of transferring the depreciation posted in the current year.
• Transferring the depreciation posted in the current fiscal year up to the point of transfer- it is necessary to specify the last posted depreciation period In the legacy system for each depreciation area for every asset company code.
• Posting the total depreciation for the current fiscal year up until the transfer date after the old data transfer –it is done in AA by performing a posting run for unplanned depreciation.
6.Which activities should be done before the production start-up? Give a brief description of each of them.
• Check consistency – major components configured, i.e. chart of depreciation, company codes, depreciation areas, asset classes, asset G/L accounts, AA customizing
• Reset company code – test application data can be deleted (asset master records and transactions of AA) but only of the company code has a test status. Customizing settings are not deleted.
• Reset posted depreciation – this function is performed when errors occurred during testing the depreciation posting run and it is necessary to return to the original status (includes depreciation data of an old assets data transfer). Manual adjustments in the relevant G/L expense and depreciation accounts need to be performed. The reset is possible only for a company code in a test status.
• Set/reset reconciliation accounts – The G/L accounts relevant for AA are defined as reconciliation accounts by a report changing their master records. After the transfer date these accounts can no longer be directly posted to.
• Transfer balances – Balances to the G/L accounts, which have been defined as reconciliation accounts, are transferred. (old data at fiscal year end)
• Activate company code – This function terminates the production start–up.
Asset FAQ’s.
1.Describe the function of depreciation areas.
Depreciation area 01, which can be set up as the book depreciation, can make automatic postings to the general ledger. Other depreciation areas may get their values from depreciation area 01 but calculate and post different depreciation values to the general ledger. Other depreciation areas can be set up to show: country specific valuation (i.e., tax depreciation); values/depreciations that differ from depreciation area 01 (i.e., cost-accounting reasons); consolidated versions in local/group currency, book depreciation in group currency; and the difference between book, 01, and country-specific tax depreciation (‘derived depreciation area’).
2.What information (sections) are included in the asset class?
An asset class consists of three main sections:
• A header, containing control parameters for master data maintenance and account determination,
• A master data section with default values for administrative data in the asset master record,
• A valuation section with control parameters for valuation and depreciation terms.
3.Describe the function of an asset class.
The most important function of an asset class is to establish the connection between the asset master records and the relevant accounts in the general ledger. The account determination in the asset class determines the posting top the general ledger accounts. Several asset classes can use the same account determination assuming the asset classes use the same chart of accounts and post to the same general ledger accounts.
4.If the company code is in implementation status and assets exist in an asset class with no transactions, you can delete and add new asset classes.
[True] or False
When the company code is in implementation status:
• No assets have been created in an existing asset class; this class is deleted and generated again
• There are assets in an existing asset class (but no transactions)
- Delete all asset classes and their assets and generate them again or
- Only add new asset classes.
• Transactions exist for the assets: you can only add new asset classes
If the company code is in production status: the system creates only asset classes that were not yet created. Exiting classes remain unchanged.
6.Define maintenance level. What are the possible maintenance levels?
Maintenance level defines the level (asset class, main asset number, sub-number) at which a field in an asset master record is to be maintained. Maintenance level definition is part of the screen layout rule.
If, for example, you define the maintenance level ‘main asset number’ for a field, then the field will be filled with a default value from the asset class. However you will be able to change the field when maintaining master data at the asset main number level.
The three maintenance levels are:
• Asset class
• Asset main number
• Asset sub-number
7.What significance is depreciation key ‘0000’?
Depreciation key ‘0000’ is a SAP delivered key that ensures depreciation and interest is not calculated and posted. This key can be used for the assets under construction, however, special tax depreciation and investment support are possible even on assets under construction.
8.What are the options for creating and asset master record?
The two options for creating an asset master record are:
• Use the asset class, to which the asset will belong, to provide default values. The asset class then supplies the most important control parameters in the asset master record.
• Use an existing asset as a reference for creating the new asset master record (possibly the reference asset has default values that are more suitable than those in the asset class).
9.Why might assets be divided up using sub-numbers?
A complex fixed asset can be represented in the system using several master records, that is, sub-numbers. Assets may be divided using sub-numbers if:
• Managing the values for subsequent acquisitions in following years (i.e., buildings) separately
• Managing the values for individual parts of assets separately,
• Dividing the asset according to various technical aspects.
10.Define work lists.
Work lists are used for mass retirements, mass changes and work on incomplete assets. There are three steps in using work lists:
• Select the objects (assets) to be changed
• Assign the task to be performed on the objects
• Release the work list and process the Workflow
1.Define a transaction type.
During the life of an asset there are a number of changes that affect the value of the asset. The FI-AA System recognizes a wide range of business transactions. Transaction types make it possible to handle all of the necessary postings appropriately.
2.It is possible that an asset acquisition is posted in two steps or in two different departments? How do the two entries clear?
When the asset acquisition is posted in two steps or two different departments, you normally post to a clearing account. Use a general ledger account with open item management to guarantee that this account can be cleared. Either the FI department includes this clearing account in their periodic run of SAPF123 (Automatic clearing program) or the clearing account has to be cleared in an additional step (Menu path: Posting > Acquisition > External acquisition > Clearing offsetting entry).
3.What is the difference between non-valued and valued? Explain their implications on Asset Accounting.
For non-valued, the goods receipt takes place before the invoice receipt and the values are not yet posted to Asset Accounting. The line items are created and the values are updated instead at the time of the invoice receipt. However, the system uses the date of the goods receipt as the capitalization date. At time of invoice receipt the asset is capitalized, line items are created, and the value fields are updated.
For valued, the goods receipt takes place before the invoice receipt and the values are posted directly to Asset Accounting. The asset is capitalized, line items are created, and the value fields in the asset are updated. When the invoice is received later, there may be differences between the invoice amount and the amount posted at the time of goods receipt. In this case, the corresponding adjustment postings are made to the asset.
4.There are certain pieces of information automatically set in the asset master record at time of acquisition. What are they?
The following information is automatically set in the asset master record at the time of the first acquisition posting:
• Date of capitalization
• Posting date of original acquisition
• Acquisition period
• Depreciation start date per depreciation area.
5.Most asset transfers are described as either inter-company or intra-company. What is the difference?
Inter-company transfer indicates a transfer between company codes. This transfer creates a new record at the target company and posts the values according to the posting method selected.
Intra-company transfer indicates a transfer within one company. Reasons for such a transfer include:
• The asset has changed location. As a result, you have to change organizational allocations (i.e., asset class, business area) in the master record that cannot otherwise be changed.
• The asset needs to split. Therefore, a portion of the original asset will be transferred to a new asset.
• The asset under construction needs to transfer its costs to a real (depreciable) asset.
6.Define transfer variant.
The transfer variant specifies:
• The method according to which the transferred asset is valued in the receiving company code
• The transaction types (retirement/acquisition) that are used for the transfer
Your specification of the transfer variant can be dependent on the following:
• The type of relationship between the company codes involved (legally dependent/independent)
• The cross-system depreciation area
7.For assets that the company produces itself, why are there two phases relevant to Asset Accounting? What are they?
The two phases relevant to Asset Accounting for assets produced in house are the under construction phase and the useful life phase. The assets have to be shown in two different balance sheet items during these two phases. Therefore, they have to be managed using a different object or asset master record for the under-construction phase and for the completed asset. The transfer from under-construction phase to completed asset is referred to as “capitalization of the asset under construction”.
8.True or False? Using the Asset Accounting module, it is no longer necessary or possible to manually plan depreciation.
False. In addition to the automatic calculation of depreciation using depreciation keys, you can also plan manual depreciation for individual assets in the FI-AA system.
Organizational Structure
1.What is the Asset Accounting sub-module?
The Asset Accounting sub-module manages a company’s fixed assets. Within the Financial Accounting system, FI-AA serves as a sub-ledger to the General Ledger, providing detailed information on asset-related transactions.
2.Define the chart of depreciation.
The chart of depreciation contains the defined depreciation areas. It also contains the rules for the evaluation of assets that are valid in a given country or economic area. The chart of depreciation is a catalog of country-specific depreciation areas structured to meet the various business needs.
Each company code is allocated to one chart of depreciation. Several company codes can work with the same chart of depreciation.
3.What is the difference between the chart of accounts and chart of depreciation?
The chart of accounts can be global, country specific and industry specifics based on the needs of the business. The chart of depreciation is only country specific. The charts are independent of each other.
4.How is Asset Accounting integrated with Cost Accounting (CO)?
Postings to depreciation can be made through a cost object such as a cost center or internal order. Also, an asset can be assigned to a cost center, internal order, activity type, or a maintenance order.
5.What is an asset class?
This is the main criterion for classifying assets by business and legal requirements. The asset class, created at the client level, consists of a master data and depreciation area section. Each asset master record must be allocated to one asset class.
6.Define depreciation area.
A depreciation area shows the valuation of assets for a particular purpose (for example, for individual financial statements, balance sheets for tax purposes, and cost accounting values).
SAP Asset Accounting – Information Systems
1.True or False? – The Asset Accounting Information System is a hierarchical structure containing standard reports creating a report tree that cannot be changed.
False. The standard reports provided by SAP can be copied and modified. Branches can be added or removed from a report tree.
2.What is the asset value display used for?
Asset value display offers extensive possibilities for planned as well as already posted asset values. For example, it is possible to compare results from different depreciation areas, simulate asset values over time, view posted transactions, and execute reports.
3.Describe simulation in the context of AA and simulation versions.
Simulation in the AA context is an experimental change to parameters affecting the valuation of assets. It can apply to a single asset, the entire asset portfolio, or a test depreciation area.
Simulation versions allow you to simulate a change in depreciation method (depreciation key and useful life) for asset value/depreciation reports and this way to forecast asset depreciation.
4.Describe the Asset History Sheet.
The asset history sheet is the most important and most comprehensive year-end report or intermediate report. It displays the various stages of a fixed asset’s history – from the opening balance through the closing balance – including any acquisitions, retirements or accumulated depreciation. SAP supplies country-specific versions of the sheet. It is often a required appendix to the balance sheet.
5.What is a sort version, and what is the maximum number of sort levels in a sort version?
The sort version defines the formation of groups and totals in an asset report. All fields of the asset master record can be used as group and/or sort criteria for defining of a sort version. It consists of a maximum of 5 sort levels determined via fields.
SAP Asset Accounting – Valuation and Periodic Processing
1.What is periodic processing, and what is it used for in Asset Accounting?
Periodic processing comprises the tasks that must be performed at periodic intervals. Since only the values from one depreciation area can be automatically posted online in Financial Accounting, the changes to asset values (transactions) from other areas with automatic postings have to be posted periodically to the appropriate reconciliation accounts.
2.What is the role of a depreciation area in handling different types of valuation? Why do we need to handle different types of valuation?
By using various depreciation areas that differ from each other in
• kinds of depreciation (ordinary, special, unplanned depreciation)
• depreciation terms (depreciation method, useful life)
• base values for depreciation calculation (APC, replacement value)
It is possible to perform different valuation and meet the calculation needs for specific purposes (e.g., balance sheet, cost accounting or taxes).
3.The system supports three direct types of depreciation. What are they? Define them.
• Ordinary depreciation is the planned reduction in asset value due to normal wear and tear. Therefore, the calculation of depreciation should be based on the normal expected useful life.
• Special depreciation represents depreciation that is solely based on tax regulations. In general, this form of depreciation allows depreciation by percentage within a tax concession period without taking into account the actual wear and tear of the asset.
• Unplanned depreciation is concerned with unusual circumstances, such as damage to the asset that leads to a permanent reduction in its value.
4.True or False? Depreciation is calculated by solely using the depreciation keys, which are defined at the chart of depreciation level and available in all company codes.
False. The depreciation keys are defined at the chart of depreciation level. Therefore, they are available in all company codes. SAP supplies depreciation keys for every chart of depreciation. The system calculates depreciation using depreciation keys and internal calculation keys.
5.What is a depreciation key and internal calculation key?
Depreciation key is used for calculating depreciation amounts. It controls automatic calculation of planned depreciation, interest and maximum percentage for manual depreciation.
Internal calculation key makes up a part of the depreciation key and it defines a method, base value and rate of percentage for depreciation, changeover rules (for declining depreciation), treatment of depreciation after useful life and period control for transactions.
6.Define derived depreciation area.
A derived depreciation area is calculated from two or more real areas using a calculation formula. You can use derived depreciation areas, for example, to calculate special reserves as the difference between tax and book depreciation. The book value rule in a derived depreciation area is checked each time a posting is made or depreciation is changed in the corresponding real area.
7.True or False? Generally, the system determines the depreciation start date from the asset value date of the first acquisition posting.
True.
8.True or False? If the definition of the depreciation key or depreciation terms is changed depreciation values are recalculated automatically. Only if the depreciation terms change values are recalculated
False.
9.When imputed interest is calculated, how does the system post this expense to the CO (Cost Accounting) module?
For cost accounting, you might have to calculate imputed interest on the capital tied up in assets. The system posts interest simultaneously during the periodic depreciation posting run. It posts to the accounts that are entered in the relevant account determination for each depreciation area. Furthermore, an additional account assignment can be made to the cost center or the internal order entered in each asset master record (same for depreciation).
10. What does the system use to calculate the replacement values, and what are the two ways of calculating the current replacement value?
Index series entered in the asset or in the asset class.
The two ways of calculating the current replacement value are historical (current year: acquisition year) and normal (current year: previous year).
11. True or False? The depreciation posting program automatically updates the asset values and G/L accounts. The program generates a batch-input session for the update of the G/L accounts.
False.
12. True or False? Replacement value of an asset can be determined by using an index series.
True. The “indexed replacement values” component makes it possible to calculate replacement values for assets, and to use replacement values as the basis for calculating depreciation. You determine the replacement value using index series. You enter the index series in the asset or in the asset class.
13. True or False? When the depreciation posting program (RABUCH00) is run, the system posts individual documents for the different depreciation types.
False. The depreciation posting program RABUCH00 updates the assets values and generates a batch-input session for the update of the general ledger. The posting session also posts the different depreciation types, interest and revaluation, in addition to the writing-off and allocation of special reserves. The system does not create individual documents, only summarized posting documents (per business area per account determination).
14. For automatic depreciation postings, should the document type be assigned an external or internal number range?
For each company code a document type must be defined for posting depreciation. The depreciation program should only use a document type that is limited to being used for batch input. In this way, unintentional use of the document type can be prevented. It is also essential that the document type is assigned a number range with an external number assignment. The depreciation program can then assign the document numbers itself. If the numbers are assigned in this way, the depreciation posting program can keep a check on posting to Financial Accounting. If errors occur, this numbering also makes it possible to make corrections.
15. Explain the difference between the methods for distributing forecasted depreciation to the posting periods.
The smoothing method distributes depreciation evenly to the periods from the current depreciation period to the end of the fiscal year (regardless of the value date of the transaction).
With the catch-up method, the depreciation on the transaction (from the start of capitalization up to the current period) is posted as a lump sum. The depreciation posting program, posts this amount in the posting period, in which the value date of the transaction lies.
Thursday, September 09, 2010
FI/CO Reports
FI/CO Frequently Used Reports
Controlling
S_ALR_87013611 Cost Centers: Actual/Plan/Variance
S_ALR_87013612 Range: Cost Centers
S_ALR_87013613 Range: Cost Elements
S_ALR_87013614 Cost Centers: Current Period/Cumulative
S_ALR_87013616 Cost Centers: Breakdown by Business Transaction
S_ALR_87013617 Range: Activity Types
S_ALR_87013618 Range: Statistical Key Figures
S_ALR_87013619 Range: Assigned Orders/WBS Elements
S_ALR_87013620 Cost Centers: Actual/Plan/Commitments
S_ALR_87013621 Range: Actual/Plan/Commitments
S_ALR_87013623 Cost Centers: Quarterly Comparison
S_ALR_87013624 Cost Centers: Fiscal Year Comparison
S_ALR_87013625 Cost Centers: Actual/Target/Variance
S_ALR_87013626 Range: Cost Elements
KSBL Cost Centers: Planning Overview
S_ALR_87013630 Activity Types: Plan Receivers
KSBT Cost Centers: Activity Prices
KSB1 Cost Centers: Actual Line Items
KSB2 Cost Centers: Commitment Line Items
KSBP Cost Centers: Plan Line Items
KSB5 CO Documents: Actual Costs
KABP CO Plan Documents
KS13 Cost Centers: Master Data Report
KA23 Cost Elements: Master Data Report
KL13 Activity Types: Master Data Report
KK04 Statistical Key Figures: Master Data Report
S_ALR_87013631 Cost Centers: Rolling Year
S_ALR_87013632 Cost Centers: Average Costs
S_ALR_87013633 Cost Centers: Actual/Plan/Variance/Previous year
S_ALR_87013635 Area: Actual/Plan 2 Currencies
S_ALR_87013636 Cost Centers: Object Comparison
S_ALR_87013637 Area: Internal Business Volume
S_ALR_87013638 Cost Centers: Current/Cumulative/Fiscal Year
S_ALR_87013639 Cost Centers: Actual/Target from Summarization
S_ALR_87013640 Cost Centers: Period Breakdown Actual/Plan
S_ALR_87013641 Cost Centers: Period Breakdown Actual/Target
S_ALR_87013642 Cost Centers: Breakdown Resources
S_ALR_87013643 Range: Orders
S_ALR_87013645 Statistical Key Figures: Period Breakdown
S_ALR_87013646 Activity Types: Period Breakdown
S_ALR_87013648 Range: Actual/Budget/Commitments
S_ALR_87012993 Orders: Actual/Plan/Variance
S_ALR_87012994 Orders: Current Period/Cumulative
S_ALR_87012995 List: Orders
S_ALR_87012996 List: Orders by Cost Element
S_ALR_87012997 List: Cost Elements by Order
S_ALR_87012998 Orders: Breakdown by Partner
S_ALR_87012999 Orders: Actual/Plan/Commitments
S_ALR_87013000 List: Actual/Plan/Commitments
S_ALR_87013001 Orders: Actual Yearly Comparison
S_ALR_87013002 Orders: Actual quarterly comparison
S_ALR_87013003 Orders: Actual Period Comparison
KABL Order: Planning Overview
S_ALR_87013004 Order: Plan Yearly Comparison
S_ALR_87013005 Orders: Plan Quarterly Comparison
S_ALR_87013006 Orders: Plan Period Comparison
KOB1 Orders: Actual Line Items
KOB2 Orders: Commitment Line Items
KOBP Orders: Plan Line Items
KOB4 Orders: Budget Line Items
KSB5 CO Documents: Actual Costs
KABP CO Plan Documents
KO2B Display Budget Document
KOK5 Internal Orders
KOSRLIST_OR Settlement Rules
KA23 Cost Elements
KK04 Statistical Key Figures
S_ALR_87013010 Orders: Breakdown by Period
S_ALR_87013011 Orders: Actual/Plan/Price Variance
S_ALR_87013012 Orders: Actual/Plan/Consumption
S_ALR_87013013 Orders: Actual in Transaction/Object/Group Currencies
S_ALR_87013014 List: Cost Elements (True Postings)
S_ALR_87013015 List: Actual Debit/Credit
S_ALR_87013016 List: Plan Debit/Credit
S_ALR_87013017 List: Actual/Plan/Variance, Cumulative
S_ALR_87013018 List: Total Plan/Actual/Commitments
S_ALR_87013019 List: Budget/Actual/Commitments
KOC4 Cost Analysis
General Ledger
S_PL0_86000028 Fin. Statement: Actual/Actual Comparison
S_ALR_87012284 Financial Statements
S_PL0_86000029 Fin. Statement: Plan/Actual Comparison
S_ALR_87012271 Cash Flow (Direct Method)
S_ALR_87012272 Cash Flow (Indirect Method) Variant 1
S_ALR_87012273 Cash Flow (Indirect Method) Variant 2
FSIB Background Processing
S_ALR_87012277 G/L Account Balances
S_PL0_86000030 G/L Account Balances (New)
S_PL0_86000031 Transaction Figures: Account Balance
S_ALR_87012301 Totals and Balances
S_PL0_86000032 Structured Account Balances
S_ALR_87012282 G/L Line Items, List for Printing
S_ALR_87012332 G/L Account Statements
S_AC0_52000887 Profit Center Receivables
S_AC0_52000888 Profit Center Payables
S_ALR_87012287 Document Journal
S_ALR_87012289 Compact Document Journal
S_ALR_87012291 Line Item Journal
S_ALR_87012293 Display of Changed Documents
S_ALR_87012341 Invoice Numbers Allocated Twice
S_ALR_87012342 Gaps in Document Number Assignment
S_ALR_87012344 Posting Totals
S_ALR_87012346 Recurring Entry Documents
S_ALR_87012347 Line Items Extract
S_ALR_87012326 Chart of Accounts
S_ALR_87012328 G/L Account List
S_ALR_87012330 Account Assignment Manual
S_ALR_87012308 Display Changes to G/L Accounts
S_ALR_87012333 G/L Accounts List
Bank
S_ALR_87012309 Cashbook
S_ALR_87012348 Cashed Checks per Bank Account
S_ALR_87012349 Outstanding Checks Analysis per G/L Account and V
S_ALR_87012351 Payment Advice Overview
S_ALR_87012350 G/L Account Payment Advice Notes
S_ALR_87012353 Payment Advice Overview (Header and Item Data)
S_ALR_87012352 G/L Account Payment Advice Notes
S_ALR_87012355 Payment Advice Notes: Reorganization
S_ALR_87012354 G/L Account Reorganization
S_ALR_87012322 Bill of Exchange List
S_ALR_87012321 SAP Minimal Variant
S_ALR_87012324 Extended Bill of Exchange Information
S_ALR_87012323 SAP Minimal Variant
Accounts Payable
S_ALR_87012077 Vendor Information System
S_ALR_87012082 Vendor Balances in Local Currency
S_ALR_87012093 Vendor Business
S_ALR_87012079 Transaction Figures: Account Balance
S_ALR_87012080 Transaction Figures: Special Sales
S_ALR_87012081 Transaction Figures: Sales
S_ALR_87012078 Due Date Analysis for Open Items
S_ALR_87012103 List of Vendor Line Items
S_ALR_87012083 List of Vendor Open Items for Printing
S_ALR_87012084 Open Items – Vendor Due Date Forecast
S_ALR_87012085 Vendor Payment History with OI Sorted List
S_ALR_87012104 List of Cleared Vendor Items for Printing
S_ALR_87012105 List of Down Payments Open On Key Date – Vendors
S_ALR_87012086 Vendor List
S_ALR_87012087 Address List
S_ALR_87012089 Display Changes to Vendors
S_ALR_87012090 Display/Confirm Critical Vendor Changes
S_P99_41000099 Payment List
S_P99_41000101 Check Register
S_ALR_87012119 Cashed Checks
S_P99_41000102 Number Ranges for Checks
Accounts Receivable
S_ALR_87012167 Accounts Receivable Information System
S_ALR_87012172 Customer Balances in Local Currency
S_ALR_87012186 Customer Sales
S_ALR_87012169 Transaction Figures: Account Balance
S_ALR_87012170 Transaction Figures: Special Sales
S_ALR_87012171 Transaction Figures: Sales
S_ALR_87012168 Due Date Analysis for Open Items
S_ALR_87012197 List of Customer Line Items
S_ALR_87012173 List of Customer Open Items for Printing
S_ALR_87012174 List of Customer Open Items
S_ALR_87012175 Open Items – Customer Due Date Forecast
S_ALR_87012176 Customer Evaluation with OI Sorted List
S_ALR_87012177 Customer Payment History
S_ALR_87012178 Customer Open Item Analysis by Balance of Overdue Items
S_ALR_87012198 List of Cleared Customer Items for Printing
S_ALR_87012199 List Of Down Payments Open On Key Date – Customers
S_ALR_87012179 Customer List
S_ALR_87012180 Address List
S_ALR_87012182 Display Changes to Customers
S_ALR_87012183 Display/Confirm Critical Customer Changes
S_ALR_87012195 Customer Master Data Comparison
Fixed Assets
AW01N Asset Explorer
S_ALR_87011963 … by Asset Number
S_ALR_87011964 … by Asset Class
S_ALR_87011965 … by Business Area
S_ALR_87011966 … by Cost Center
S_ALR_87011967 … by Plant
S_ALR_87011968 … by Location
S_ALR_87011969 … by Asset Super Number
S_ALR_87011970 … by Worklist
S_ALR_87010125 Sample for address data for an asset
S_ALR_87010127 Real Estate and Similar Rights
S_ALR_87010129 Transportation Equipment
S_ALR_87011978 Asset Balances for Group Assets
S_ALR_87011979 … by Cost Center
S_ALR_87011980 … by Location
S_ALR_87011981 … by Asset Class
S_ALR_87011982 … by Plant
S_ALR_87010137 Bar Codes
S_ALR_87010139 Leasing
S_ALR_87010141 Liabilities from Leasing Agreements
S_ALR_87011990 Asset History Sheet
S_ALR_87011992 Liabilities from Leasing Agreements
S_ALR_87011994 Asset Balances
S_ALR_87012004 Total Depreciation
S_ALR_87012006 Ordinary Depreciation
S_ALR_87012007 Special Depreciation
S_ALR_87012008 Unplanned Depreciation
S_ALR_87012009 Transfer of Reserves
S_ALR_87012011 Write-Ups
S_ALR_87012013 Depreciation Comparison
S_ALR_87012015 Manual Depreciation
S_ALR_87012018 Depreciation and Interest
S_ALR_87010173 Revaluation
S_P99_41000192 Posted depreciation by asset and posting period
S_ALR_87010175 Posted depreciation, related to cost centers
S_ALR_87012936 Depreciation on Capitalized Assets (Depreciation Simulation)
S_ALR_87012026 Depreciation Current Year
S_ALR_87012028 Net Worth Valuation
S_ALR_87012030 Insurance Values
S_ALR_87012033 Gain for transfer of reserves
S_ALR_87012035 Depreciation Current Year
S_ALR_87012037 Changes to Asset Master Records
S_ALR_87012039 Asset Transactions
S_ALR_87012041 Asset Portfolio (Current Book Values)
S_ALR_87012043 G/L Account Balances
S_ALR_87012048 Asset transactions
S_ALR_87012050 Asset Acquisitions
S_ALR_87012052 Asset Retirements
S_ALR_87012054 Intracompany Asset Transfers
S_ALR_87012056 Directory of Unposted Assets
S_ALR_87012058 List of Origins of Asset Debits
S_ALR_87012060 List of Origins by Cost Elements
S_ALR_87012075 Asset History
Controlling
S_ALR_87013611 Cost Centers: Actual/Plan/Variance
S_ALR_87013612 Range: Cost Centers
S_ALR_87013613 Range: Cost Elements
S_ALR_87013614 Cost Centers: Current Period/Cumulative
S_ALR_87013616 Cost Centers: Breakdown by Business Transaction
S_ALR_87013617 Range: Activity Types
S_ALR_87013618 Range: Statistical Key Figures
S_ALR_87013619 Range: Assigned Orders/WBS Elements
S_ALR_87013620 Cost Centers: Actual/Plan/Commitments
S_ALR_87013621 Range: Actual/Plan/Commitments
S_ALR_87013623 Cost Centers: Quarterly Comparison
S_ALR_87013624 Cost Centers: Fiscal Year Comparison
S_ALR_87013625 Cost Centers: Actual/Target/Variance
S_ALR_87013626 Range: Cost Elements
KSBL Cost Centers: Planning Overview
S_ALR_87013630 Activity Types: Plan Receivers
KSBT Cost Centers: Activity Prices
KSB1 Cost Centers: Actual Line Items
KSB2 Cost Centers: Commitment Line Items
KSBP Cost Centers: Plan Line Items
KSB5 CO Documents: Actual Costs
KABP CO Plan Documents
KS13 Cost Centers: Master Data Report
KA23 Cost Elements: Master Data Report
KL13 Activity Types: Master Data Report
KK04 Statistical Key Figures: Master Data Report
S_ALR_87013631 Cost Centers: Rolling Year
S_ALR_87013632 Cost Centers: Average Costs
S_ALR_87013633 Cost Centers: Actual/Plan/Variance/Previous year
S_ALR_87013635 Area: Actual/Plan 2 Currencies
S_ALR_87013636 Cost Centers: Object Comparison
S_ALR_87013637 Area: Internal Business Volume
S_ALR_87013638 Cost Centers: Current/Cumulative/Fiscal Year
S_ALR_87013639 Cost Centers: Actual/Target from Summarization
S_ALR_87013640 Cost Centers: Period Breakdown Actual/Plan
S_ALR_87013641 Cost Centers: Period Breakdown Actual/Target
S_ALR_87013642 Cost Centers: Breakdown Resources
S_ALR_87013643 Range: Orders
S_ALR_87013645 Statistical Key Figures: Period Breakdown
S_ALR_87013646 Activity Types: Period Breakdown
S_ALR_87013648 Range: Actual/Budget/Commitments
S_ALR_87012993 Orders: Actual/Plan/Variance
S_ALR_87012994 Orders: Current Period/Cumulative
S_ALR_87012995 List: Orders
S_ALR_87012996 List: Orders by Cost Element
S_ALR_87012997 List: Cost Elements by Order
S_ALR_87012998 Orders: Breakdown by Partner
S_ALR_87012999 Orders: Actual/Plan/Commitments
S_ALR_87013000 List: Actual/Plan/Commitments
S_ALR_87013001 Orders: Actual Yearly Comparison
S_ALR_87013002 Orders: Actual quarterly comparison
S_ALR_87013003 Orders: Actual Period Comparison
KABL Order: Planning Overview
S_ALR_87013004 Order: Plan Yearly Comparison
S_ALR_87013005 Orders: Plan Quarterly Comparison
S_ALR_87013006 Orders: Plan Period Comparison
KOB1 Orders: Actual Line Items
KOB2 Orders: Commitment Line Items
KOBP Orders: Plan Line Items
KOB4 Orders: Budget Line Items
KSB5 CO Documents: Actual Costs
KABP CO Plan Documents
KO2B Display Budget Document
KOK5 Internal Orders
KOSRLIST_OR Settlement Rules
KA23 Cost Elements
KK04 Statistical Key Figures
S_ALR_87013010 Orders: Breakdown by Period
S_ALR_87013011 Orders: Actual/Plan/Price Variance
S_ALR_87013012 Orders: Actual/Plan/Consumption
S_ALR_87013013 Orders: Actual in Transaction/Object/Group Currencies
S_ALR_87013014 List: Cost Elements (True Postings)
S_ALR_87013015 List: Actual Debit/Credit
S_ALR_87013016 List: Plan Debit/Credit
S_ALR_87013017 List: Actual/Plan/Variance, Cumulative
S_ALR_87013018 List: Total Plan/Actual/Commitments
S_ALR_87013019 List: Budget/Actual/Commitments
KOC4 Cost Analysis
General Ledger
S_PL0_86000028 Fin. Statement: Actual/Actual Comparison
S_ALR_87012284 Financial Statements
S_PL0_86000029 Fin. Statement: Plan/Actual Comparison
S_ALR_87012271 Cash Flow (Direct Method)
S_ALR_87012272 Cash Flow (Indirect Method) Variant 1
S_ALR_87012273 Cash Flow (Indirect Method) Variant 2
FSIB Background Processing
S_ALR_87012277 G/L Account Balances
S_PL0_86000030 G/L Account Balances (New)
S_PL0_86000031 Transaction Figures: Account Balance
S_ALR_87012301 Totals and Balances
S_PL0_86000032 Structured Account Balances
S_ALR_87012282 G/L Line Items, List for Printing
S_ALR_87012332 G/L Account Statements
S_AC0_52000887 Profit Center Receivables
S_AC0_52000888 Profit Center Payables
S_ALR_87012287 Document Journal
S_ALR_87012289 Compact Document Journal
S_ALR_87012291 Line Item Journal
S_ALR_87012293 Display of Changed Documents
S_ALR_87012341 Invoice Numbers Allocated Twice
S_ALR_87012342 Gaps in Document Number Assignment
S_ALR_87012344 Posting Totals
S_ALR_87012346 Recurring Entry Documents
S_ALR_87012347 Line Items Extract
S_ALR_87012326 Chart of Accounts
S_ALR_87012328 G/L Account List
S_ALR_87012330 Account Assignment Manual
S_ALR_87012308 Display Changes to G/L Accounts
S_ALR_87012333 G/L Accounts List
Bank
S_ALR_87012309 Cashbook
S_ALR_87012348 Cashed Checks per Bank Account
S_ALR_87012349 Outstanding Checks Analysis per G/L Account and V
S_ALR_87012351 Payment Advice Overview
S_ALR_87012350 G/L Account Payment Advice Notes
S_ALR_87012353 Payment Advice Overview (Header and Item Data)
S_ALR_87012352 G/L Account Payment Advice Notes
S_ALR_87012355 Payment Advice Notes: Reorganization
S_ALR_87012354 G/L Account Reorganization
S_ALR_87012322 Bill of Exchange List
S_ALR_87012321 SAP Minimal Variant
S_ALR_87012324 Extended Bill of Exchange Information
S_ALR_87012323 SAP Minimal Variant
Accounts Payable
S_ALR_87012077 Vendor Information System
S_ALR_87012082 Vendor Balances in Local Currency
S_ALR_87012093 Vendor Business
S_ALR_87012079 Transaction Figures: Account Balance
S_ALR_87012080 Transaction Figures: Special Sales
S_ALR_87012081 Transaction Figures: Sales
S_ALR_87012078 Due Date Analysis for Open Items
S_ALR_87012103 List of Vendor Line Items
S_ALR_87012083 List of Vendor Open Items for Printing
S_ALR_87012084 Open Items – Vendor Due Date Forecast
S_ALR_87012085 Vendor Payment History with OI Sorted List
S_ALR_87012104 List of Cleared Vendor Items for Printing
S_ALR_87012105 List of Down Payments Open On Key Date – Vendors
S_ALR_87012086 Vendor List
S_ALR_87012087 Address List
S_ALR_87012089 Display Changes to Vendors
S_ALR_87012090 Display/Confirm Critical Vendor Changes
S_P99_41000099 Payment List
S_P99_41000101 Check Register
S_ALR_87012119 Cashed Checks
S_P99_41000102 Number Ranges for Checks
Accounts Receivable
S_ALR_87012167 Accounts Receivable Information System
S_ALR_87012172 Customer Balances in Local Currency
S_ALR_87012186 Customer Sales
S_ALR_87012169 Transaction Figures: Account Balance
S_ALR_87012170 Transaction Figures: Special Sales
S_ALR_87012171 Transaction Figures: Sales
S_ALR_87012168 Due Date Analysis for Open Items
S_ALR_87012197 List of Customer Line Items
S_ALR_87012173 List of Customer Open Items for Printing
S_ALR_87012174 List of Customer Open Items
S_ALR_87012175 Open Items – Customer Due Date Forecast
S_ALR_87012176 Customer Evaluation with OI Sorted List
S_ALR_87012177 Customer Payment History
S_ALR_87012178 Customer Open Item Analysis by Balance of Overdue Items
S_ALR_87012198 List of Cleared Customer Items for Printing
S_ALR_87012199 List Of Down Payments Open On Key Date – Customers
S_ALR_87012179 Customer List
S_ALR_87012180 Address List
S_ALR_87012182 Display Changes to Customers
S_ALR_87012183 Display/Confirm Critical Customer Changes
S_ALR_87012195 Customer Master Data Comparison
Fixed Assets
AW01N Asset Explorer
S_ALR_87011963 … by Asset Number
S_ALR_87011964 … by Asset Class
S_ALR_87011965 … by Business Area
S_ALR_87011966 … by Cost Center
S_ALR_87011967 … by Plant
S_ALR_87011968 … by Location
S_ALR_87011969 … by Asset Super Number
S_ALR_87011970 … by Worklist
S_ALR_87010125 Sample for address data for an asset
S_ALR_87010127 Real Estate and Similar Rights
S_ALR_87010129 Transportation Equipment
S_ALR_87011978 Asset Balances for Group Assets
S_ALR_87011979 … by Cost Center
S_ALR_87011980 … by Location
S_ALR_87011981 … by Asset Class
S_ALR_87011982 … by Plant
S_ALR_87010137 Bar Codes
S_ALR_87010139 Leasing
S_ALR_87010141 Liabilities from Leasing Agreements
S_ALR_87011990 Asset History Sheet
S_ALR_87011992 Liabilities from Leasing Agreements
S_ALR_87011994 Asset Balances
S_ALR_87012004 Total Depreciation
S_ALR_87012006 Ordinary Depreciation
S_ALR_87012007 Special Depreciation
S_ALR_87012008 Unplanned Depreciation
S_ALR_87012009 Transfer of Reserves
S_ALR_87012011 Write-Ups
S_ALR_87012013 Depreciation Comparison
S_ALR_87012015 Manual Depreciation
S_ALR_87012018 Depreciation and Interest
S_ALR_87010173 Revaluation
S_P99_41000192 Posted depreciation by asset and posting period
S_ALR_87010175 Posted depreciation, related to cost centers
S_ALR_87012936 Depreciation on Capitalized Assets (Depreciation Simulation)
S_ALR_87012026 Depreciation Current Year
S_ALR_87012028 Net Worth Valuation
S_ALR_87012030 Insurance Values
S_ALR_87012033 Gain for transfer of reserves
S_ALR_87012035 Depreciation Current Year
S_ALR_87012037 Changes to Asset Master Records
S_ALR_87012039 Asset Transactions
S_ALR_87012041 Asset Portfolio (Current Book Values)
S_ALR_87012043 G/L Account Balances
S_ALR_87012048 Asset transactions
S_ALR_87012050 Asset Acquisitions
S_ALR_87012052 Asset Retirements
S_ALR_87012054 Intracompany Asset Transfers
S_ALR_87012056 Directory of Unposted Assets
S_ALR_87012058 List of Origins of Asset Debits
S_ALR_87012060 List of Origins by Cost Elements
S_ALR_87012075 Asset History
SAP Tables
Customising
General settings
Countries
T005 Countries
Currency
TCURC Currency codes
TCURR Wisselkoersen
TCURT Currency name
TCURX Decimal places for currencies.
Unit of measure
T006 Units of measure
Calendar functions
T247 Month names
TFACD Factory calendar definition
T015M Month names
TTZZ Time zones
TTZD Summer time rules
TTZDF Summer time rules (fixed annual dates)
TTZDV Summer time rules (variable dates)
TTZDT Summer time rules texts
TTZ5 Assign Time Tones to Countries
TTZ5S Assign time zones to regions
Enterprise structure
Definition
FI T880 Company
T001 Company code
CO TKA01 Controlling area
LO T001W Plant / sales organisation
T499S Locations
TSPA Division
SD TVKO Sales organisation / company code
TVTW Distribution channel
TVBUR Sales office
TVKBT Sales office text
TVKGR Sales group
TVGRT Sales group text
T171T Sales district text
MM T001L Storage locations
T024E Purchasing organization
T3001 Warehouse number
TVST Shipping point
TVLA Loading point
TTDS Transportation
Assignment
CO TKA02 Assign company code to controlling area
LO T001K Assign plant (valuation area) to company code
SD TVKO Sales organisation / company code
TVKOV Distribution channel / sales organisation
TVKOS Division to sales organization
TVTA Sales aria
TVKBZ Sales office to sales area
TVBVK Sales group to sales office
TVKWZ Plants to sales organization
MM T024E Purchasing organization / company code
T024W Plant to Purchase organization
T001K Link plant ( = valuation area) / company code
TVSWZ Shipping point to plant
T320 Assignment MM Storage Location to WM Warehouse
Financial accounting
Company code
T004 Chart of accounts
T077S Account group (g/l accounts)
T009 Fiscal year variants
T880 Global company data
T014 Credit control area
Fi document
T010O Posting period variant
T010P Posting Period Variant Names
T001B Permitted Posting Periods
T003 Document types
T012 House banks
Not categorized
T007a Tax keys
T134 Material types
T179 Materials: Product Hierarchies
T179T Materials: Product hierarchies: Texts
TJ02T Status text
TINC Customer incoterms
TVFK Billing doc types
T390 PM: Shop papers for print control
Basic data / administration
Workbench related tables
Data dictionary tables
DD02L Tables in SAP
DD02T Tables description
DD03L Field names in SAP
DD03T Field description in SAP
Workbench
TADIR Directory of R/3 Repository Objects
TRDIR System table TRDIR
TFDIR Function Module
TLIBG Person responsible for function class
TLIBT Function Group Short Texts
TFTIT Function Module Short Text
TSTC Transaction codes in SAP
TSTCT Transaction codes texts
T100 Message text (vb e000)
VARID Variant data
D020T Screen texts
TDEVC Development class
TDEVCT Texts for development classes
Administration
User administration
USR01 User master
USR02 Logon data
USR03 User address data
USR04 User master authorizations
USR11 User Master Texts for Profiles (USR10)
UST12 User master: Authorizations
USR12 User master authorization values
USR13 Short Texts for Authorizations
USR40 Prohibited passwords
TOBJ Objects
TOBC Authorization Object Classes
TPRPROF Profile Name for Activity Group
DEVACCESS Table for development user
Batch input queue
APQD DATA DEFINITION Queue
APQI Queue info definition
Job processing
TBTCO Job status overview table
TBTCP Batch job step overview
Spool
TSP02 Spool: Print requests
Runtime errors
SNAP Runtime errors
Message control
TNAPR Processing programs for output
NAST Message status
NACH Printer determination
EDI
EDIDC Control record
EDIDD Data record
EDID2 Data record 3.0 Version
EDIDS EDI status record
EDPAR Convert External < > Internal Partner Number
EDPVW EDI partner types
EDPI1 EDI partner profile inbound
EDPO1/2/3 EDI partner profile outbound
Change documents
CDHDR Change document header
CDPOS Change document positioned
JCDS Change Documents for System/User Statuses (Table JEST)
Reporting tree table
SERPTREE Reporting: tree structure
LIS structure/control tables
TMC4 Global Control Elements: LIS Info Structure
MASTER DATA:
Material master:
MARA Material master
MAKT Material text
MARC Material per plant / stock
MVKE Material master, sales data
MARD Storage location / stock
MSKA Sales order stock
MSPR Project stock
MARM Units of measure
MEAN International article number
PGMI Planning material
PROP Forecast parameters
MAPR Link MARC <=> PROP
MBEW Material valuation
MVER Material consumption
MLGN Material / Warehouse number
MLGT Material / Storage type
MPRP Forecast profiles
MDTB MRP table
MDKP Header data for MRP document
MLAN Tax data material master
MTQSS Material master view: QM
Basic data text (sap script)
STXB SAP script: Texts in non-SAP script format
STXH STXD SAP script text file header
STXL STXD SAP script text file lines
Batches
MCHA Batches
MCH1 Batches
MCHB Stock: batches
Customer master data
KNA1 Customer master
KNB1 Customer / company
KNVV Customer sales data
KNBK Bank details
KNVH Customer hierarchy
KNVP Customer partners
KNVS Shipment data for customer
KNVK Contact persons
KNVI Customer master tax indicator
Vendor
LFA1 Vendor master
LFB1 Vendor per company code
LFB5 Vendor dunning data
LFM1 Purchasing organization data
LFM2 Purchasing data
LFBK Bank details
Customer – material info record
KNMT Customer material info record
Bank data
BNKA Master bank data
Characteristics:
Characteristics:
CABN Characteristics ( o.a. batch/vendor)
CABNT Characteristics description
CAWN Characteristics ( o.a. material)
CAWNT Characteristics description
AUSP Characteristic Values
Class types and objects :
TCLAO Several class types for object
TCLA Class types ( vb. lfa1 => v10 en 010)
TCLAT Class type text
TCLT Classifiable objects
TCLC Classification status
Links:
INOB Link between Internal Number and Object
KLAH Class header data
KSSK Allocation Table: Object (vb.matnr) to Class
KSML Characteristics for a class (internal number)
FI/CO :
FI :
Master data
SKA1 Accounts
BNKA Bank master record
Accounting documents // indices
BKPF Accounting documents
BSEG item level
BSID Accounting: Secondary index for customers
BSIK Accounting: Secondary index for vendors
BSIM Secondary Index, Documents for Material
BSIP Index for vendor validation of double documents
BSIS Accounting: Secondary index for G/L accounts
BSAD Accounting: Index for customers (cleared items)
BSAK Accounting: Index for vendors (cleared items)
BSAS Accounting: Index for G/L accounts (cleared items)
Payment run
REGUH Settlement data from payment program
REGUP Processed items from payment program
CO :
TKA01 Controlling areas
TKA02 Controlling area assignment
KEKO Product-costing header
KEPH Cost components for cost of goods manuf.
KALO Costing objects
KANZ Sales order items - costing objects
Cost center master data
CSKS Cost Center Master Data
CSKT Cost center texts
CRCO Assignment of Work Center to Cost Center
Cost center accounting
COSP CO Object: Cost Totals for External Postings
COEP CO Object: Line Items (by Period)
. COBK CO Object: Document header
COST CO Object: Price Totals
Sales and Distribution (SD) :
VBFA Document flow (alg.)
VTFA Flow shipping documents
Sales order :
VBAK Header data
VBAP Item data
VBPA Partners in sales order
VBKD Sales district data
VBEP Data related to line items, delivery lines
Billing document :
VBRK header data
VBRP Item data
Shipping :
VTTK Shipment header
VTTP Shipment item
VTTS Stage in transport
VTSP Stage in transport per shipment item
VTPA Shipment partners
VEKP Handling Unit - Header Table
VEPO Packing: Handling Unit Item (Contents)
Delivery :
LIKP Delivery header
LIPS Delivery item
Pricing :
KONH Conditions header
KONP Conditions items
KONV Procedure ( billing doc or sales order)
KOND
Contracts :
VEDA Contract data
Material Management (MM) :
Material document
MKPF material document
MSEG material document (item level)
Purchasing
EKKO Purchase document
EKPO Purchase document (item level)
EKPV Shipping-Specific Data on Stock Tfr. for Purch. Doc. Item
EKET Delivery schedule
VETVG Delivery Due Index for Stock Transfer
EKES Order Acceptance/Fulfillment Confirmations
EKKN Account assignment in purchasing
EKAN Vendor address purchasing
EKPA Partner functions
EIPO Item export / import data
EINA Purchase info record (main data)
EINE Purchase info record (organisational data)
EORD Source list
EBAN Purchase requisition
EBKN Purchase Requisition Account Assignment
Warehouse Management (WM) :
Transfer requirement
LTBK Transfer requirement - header
LTBP Transfer requirement - item
Transfer order
LTAK Transfer order - header
LTAP Transfer order - item
Master data - stock positions
LQUA Quants
Inventory documents in WM
LINK Inventory document header
LINP Inventory document item
LINV Inventory data per quant
Quality Management (QM) :
Inspection lot / info record
QALS Inspection lot record
QAMB Link inspection lot - material document
QAVE Inspection usage decision
QDPS Inspection stages
QMAT Inspection type - material parameters
QINF Inspection info record (vendor - material)
QDQL Quality level
QDPS Inspection stages
Quality notification
TQ80 Notification types
QMEL Quality notification
QMFE Quality notification – items
QMUR Quality notification – causes
QMSM Quality notification – tasks
QMMA Quality notification – activities
QMIH Quality message - maintenance data excerpt
Certificate profile
QCVMT Certificate profile characteristic level: texts
QCVM Certificate profile characteristic level
QCVK Certificate profile header
Production Planning (PP)
Work center
CRHH Work center hierarchy
CRHS Hierarchy structure
CRHD Work center header
CRTX Text for the Work Center or Production Resource/Tool
CRCO Assignment of Work Center to Cost Center
KAKO Capacity Header Segment
CRCA Work Center Capacity Allocation
TC24 Person responsible for the workcenter
10.2 Routings/operations
MAPL Allocation of task lists to materials
PLAS Task list - selection of operations/activities
PLFH Task list - production resources/tools
PLFL Task list - sequences
PLKO Task list - header
PLKZ Task list: main header
PLPH Phases / suboperations
PLPO Task list operation / activity
PLPR Log collector for tasklists
PLMZ Allocation of BOM - items to operations
10.3 Bill of material
STKO BOM - header
STPO BOM - item
STAS BOMs - Item Selection
STPN BOMs - follow-up control
STPU BOM - sub-item
STZU Permanent BOM data
PLMZ Allocation of BOM - items to operations
MAST Material to BOM link
KDST Sales order to BOM link
10.4 Production orders
AUFK Production order headers
AFIH Maintenance order header
AUFM Goods movement for prod. order
AFKO Order header data PP orders
AFPO Order item
RESB Order componenten
AFVC Order operations
AFVV Quantities/dates/values in the operation
AFVU User fields of the operation
AFFL Work order sequence
AFFH PRT assignment data for the work order(routing)
JSTO Status profile
JEST Object status
AFRU Order completion confirmations
Production orders
AFFH PRT assignment data for the work order
CRVD_A Link of PRT to Document
DRAW Document Info Record
TDWA Document Types
TDWD Data Carrier/Network Nodes
TDWE Data Carrier Type
Planned orders
PLAF Planned orders
KANBAN
PKPS Kanban identification, control cycle
PKHD Kanban control cycle (header data)
PKER Error log for Kanban containers
Reservations
RESB Material reservations
RKPF header
Capacity planning
KBKO Header record for capacity requirements
KBED Capacity requirements records
KBEZ Add. data for table KBED (for indiv. capacities/splits)
Planned independent requirements
PBIM Independent requirements for material
PBED Independent requirement data
PBHI Independent requirement history
PBIV Independent requirement index
PBIC Independent requirement index for customer req.
Project system (PS)
Basic data
PRHI Work Breakdown Structure, Edges (Hierarchy Pointer)
PROJ Project definition
PRPS WBS (Work Breakdown Structure) Element Master Data
RPSCO Project info database: Costs, revenues, finances
MSPR Project stock
Equipment
EQUI Equipment master data
EQKT Equipment short text
EQUZ Equipment time segment
Plant maintenance (PM)
IHPA Plant Maintenance: Partners
OBJK Plant Maintenance Object List
ILOA PM Object Location and Account Assignment
AFIH Maintenance order header
Human resources
Settings
T582A Infotypes: Customer-Specific Settings
Master data
T527X Organizational Units
T528T Position Texts
T554T Attendance and Absence Texts
T501 Employee group
T503 Employee group, subgroup
T503K Employee subgroup
T510N Pay Scales for Annual Salaries (NA)
T549A Payroll Accounting Areas
T750X Vacancy
Infotypes
PA0001 Org. Assignment
PA0002 Personal Data
PA0006 Addresses
PA0007 Planned Working Time
PA0016 Contract elements
PA0008 Basic pay
PA0105 Communications
PA1007 Vacancies
PA1035 Training
PA2001 Absences
Other important table
JEST System Status with object number
TJ02 System status description.
MRP Related
MDKP Header Data for MRP Document
MDTB MRP Table
MDVL Planning file entry for long term planning
MDVM Enry in MRP file
PBVPV Material Index for consumption of planning
REUL Material stock transfer reservation index
SAFK Run schedule master data
SQ01 Abap query
EDMSG ALE message type table