SAP Logistics (PP) Interview

Explain how the PP Module is Organized in SAP.
The PP module is made up of the following components: 
  • PP-BD   Basic Data
  • PP-SOP   Sales and Operations Planning
  • PP-MP   Master Planning
  • PP-CRP   Capacity (Requirements) Planning
  • PP-MRP   Material Requirements Planning
  • PP-SFC   Production Orders
  • PP-KAN   Kanban
  • PP-REM   Repetitive Manufacturing
  • PP-PI   Production Planning for Process Industries
  • PP-PDS   Plant Data Collection
  • PP-IS   Information Systems 
Explain How ‘PP’ is ‘Integrated’ with Other Modules.
‘PP’ is one of the modules in SAP R/3 that is complex as the functions cut across many modules. The following modules are tightly integrated with PP:
  • CO   Controlling
  • FI   Financial Accounting
  • MM   Materials Management
  • SD   Sales & Distribution
  • PS   Project Systems
  • PD   Personnel Planning and Development
What is a ‘BOM’?
A ‘BOM (Bill of Material)’ is nothing but a structured list of components (with the object number, quantity, and unit of measure) that go into the making of a product or an assembly. Depending on the industry sector, they may also be called recipes or lists of ingredients. The structure of the product determines whether the bill of material is simple or very complex.

What are the ‘BOM Categories’ Supported by SAP?
The following are the various Categories of BOM: 
  • Equipment BOM
  • Material BOM
  • Sales Order BOM
  • Document Structure
  • Functional Location BOM
  • WBS BOM
What are all the ‘Technical Types of BOM’?
There are two ‘Technical Types of BOM’ supported in SAP:
  • Variant BOM
  • Material BOM
Differentiate ‘Variant BOM’ from ‘Multiple BOM.’
While a ‘Variant BOM’ groups together several BOMs that describe different objects (for example, different models of a car) with a high proportion of identical parts, a Multiple BOM groups together several BOMs that describe one object (for example, a product) with different combinations of materials for different processing methods.
The Variant BOMs are supported for the following BOM categories:
  • Material BOMs
  • Document structures
  • Equipment BOMs
  • Functional location BOMs
  • Multiple BOMs are only supported for Material BOMs.
Is it Possible to Convert a ‘Multiple BOM’ into a ‘Variant BOM’?
No. You can only create a ‘Variant BOM’ from a simple Material BOM. No multiple BOMs can exist for a material.

What is a ‘Work Center’ in PP?
A ‘Work Center’ in PP (PP-BD-BOM) is an organizational unit that can be a combination of machines or groups of craftsmen, people, and production lines, wherein certain operations are carried out to produce some output. Each of the work centers is assigned to a cost center. A work center can be assigned to a work center in SAP-HR, which will enable assignment of employees, qualifications, etc.

What is a ‘Routing’ in PP?
A ‘Routing’ in PP (PP-BD-RTG) is used to define the sequence of operations (work steps) and resources required to perform certain operations in order to produce a material with or without reference to an order. The standard values of planned time for the various operations need to be entered into the routing.
There are two different types of routing:
  • Routing
  • Rate routing
(A similar concept exists in PS where you define a ‘task list,’ which is similar to ‘routing’ in PP.)

What are All the ‘Sub-components’ of Production Orders?
The following are the ‘Sub-components of Production Orders’ (PP-SFC):
  • Order Planning
  • Order Execution
  • Order Close
What is a ‘Product Hierarchy’?
Used in pricing, a ‘Product Hierarchy’ is an alphanumeric character string consisting of a maximum of 18 characters. It thus defines the product and its composition.
Example:
A product hierarchy represented by ‘00050002000300040005.’ The first four characters ‘0005’ could indicate that the product is a car. The next four characters ‘0002’ could indicate the plant in which the car is manufactured. The third set of characters could indicate the color of the car. The next set may determine its engine capacity and so on. Thus, the product hierarchy helps in defining the product composition.

Define ‘BOM Group.’
A ‘BOM Group’ is a collection of BOMs that lets you describe a product or a number of similar products. The value in the BOM group field uniquely identifies the BOM group. You can use the BOM group as an alternative way of accessing the BOM. A BOM group comprises either all the alternatives of a multiple BOM or all the variants of a variant BOM.
When you create a BOM group, the system checks the special characters you use. Apart from the usual alphanumeric characters, you can use the following special characters: ‘-’,‘/’,‘_.’ You cannot use blanks.

Define ‘SOP’ (Sales & Operations Planning).
Suitable for long/medium-term planning, with an aim to streamline a company’s ‘Sales and Operational Planning, SOP’ is a forecasting tool enabling you to set up sales, production, and other supply chain targets based on existing, future, or historical data. SOP is most suitable for planning finished goods, and not for material component planning.

SOP plans are passed on to Demand Management (DEM) in the form of independent requirements, which in turn is fed into MPS (Master Production Scheduling) and MRP (Material Requirements Planning). The results of SOP can be passed on to profitability analysis, cost center accounting, and activity-based costing.

SOP contains two application components; namely, Standard SOP (PP-SOP) and Flexible Planning (LO-LIS-PLN). The Standard SOP comes pre-configured with the system. Flexible planning can be configured in a variety of ways.

What is known as ‘Demand Management’?
‘Demand Management’ (PP-MP-DEM) helps in determining the requirement quantities and delivery dates for finished goods assemblies. It uses the planned independent requirements and customer requirements (customer requirements come from sales orders). Planning strategies help in deciding the kind of demand program. If production is triggered by sales orders, then it is known as ‘Make-toOrder’ production; if is not then it is known as ‘Make-to-Stock’ production.

What is ‘Capacity Planning’?
‘Capacity Planning’ aims at economic use of resources. It is integrated with SD, PM, PS, and CS. There are two components within capacity planning: Capacity evaluation and Capacity levelling. Capacity planning supports short-term detailed planning, medium-term planning, and long-term rough-cut planning.

Explain ‘MRP’ (Material Requirements Planning).
‘MRP’ aims to guarantee material availability; it is used to procure/produce the required quantities on time (both for internal purposes and for sales and distribution). This involves monitoring of stocks and, in particular, the automatic creation of ‘procurement proposals’ for purchasing and production. PP-MRP assists and relieves MRP Controllers (who are responsible for all the activities from specifying when, what, type, etc., of material requirements) in their area of responsibility. With the automatic planning run in MRP, it is possible to determine any shortages so as to create procurement elements. With the system generating messages for critical parts and unusual situations, you can rework the planning results in the specific area with problems. 

The material requirements can be planned at plant level or for different MRP areas. With MRP at the plant level, the system adds together stocks from all of the individual storage locations, with the exception of individual customer stocks, to determine total plant stock. In the case of material requirements planning on an MRP area level, only the stocks from the storage locations or subcontractor assigned to the respective MRP areas are taken into account.

What are the Three ‘MRP Procedures’?
  • Materials Requirements Planning (MRP) 
  • Master Production Scheduling (MPS) 
  • Consumption-based Planning
What is ‘MPS’ (Master Production Scheduling)?
Executed as that of an MRP, ‘MPS’ is nothing but a special form of MRP, which aims to reduce storage costs and to increase planning stability. With MPS you can flag materials that greatly influence company profits or take up critical resources as master schedule items and check and plan them separately with a series of special tools.

What is ‘Consumption-based Planning’?
Using past consumption data, ‘Consumption-based Planning’ aims at determining future requirements. In the process, it makes use of material forecasts or any other ‘static’ planning procedures. The ‘net requirements’ calculation is triggered when the stock level falls below a reorder point. The net requirements can also be calculated by forecast requirements from a historical consumption pattern. 


Click below links for more SAP Logistics Interview Questions and Answers 
SAP SD Interview
SAP MM Interview

SAP Logistics (MM) Interview

What Functions are Supported in the SAP ‘Material Management’ (MM)?
The MM module of SAP supports the following functions:
  • MRP (Material Requirements Planning)
  • Procurement
  • Inventory Management
  • Inventory Valuation
  • Invoice Verification
What is ‘MRP’?
‘MRP (Material Requirements Planning)’ is nothing but the determination of which materials are required, when and in what quantities, based on current information and forecasts. 

Explain the Basic ‘Organizational Structure’ in MM.
The major Organizational Elements of MM include:
  • Purchasing Organization
  • Plant
  • Storage Location
The Purchasing Organization is typically attached to one Company Code. But a single Company Code can have one or more purchasing organizations. One or more Plants are attached to a purchasing organization. One or more Storage Locations are attached to a plant. One or more plants are assigned to a Company Code, but one plant is attached to only one Company Code.
Depending on how the purchasing organization has been structured, you may come across three types of structures as detailed below:
  • Cross-Plant Purchasing Organization - The purchasing organization caters to more than one plant of the same Company Code.
  • Plant-Specific Purchasing Organization - Each Plant has it is own purchasing organization. 
  • Cross-Company Code Purchasing Organization - A single purchasing organization is responsible for the procurement activities of more than one Company Code. The plants attached to this purchasing organization are also cross-Company Code. In this case, the purchasing organization is not attached to any of the Company Codes; instead, the various plants are attached to the purchasing organization. This kind of purchasing organization is known as a central purchasing organization. This kind of organizational structure is essential in the case of centralized procurement in an enterprise.
Define ‘Plant’ in SAP.
‘Plant’ in SAP can denote a manufacturing location, distribution center, or a warehouse. With unique numbers identifying each of the plants, though these are all not all necessarily financial entities, they can still be linked to a Business Area. The Plant is the place where you normally valuate the inventory in SAP. The system, however, checks for the inventory either at the Plant or Plant/Storage Location during an Order entry.

Explain the ‘Storage Location’ in SAP.
A sub-division of a plant, the ‘Storage Location,’ defines a location for materials that can be a warehouse, bin, or a storage area of raw materials/WIP/finished product. You will manage the physical inventory, material movement, picking, cycle counting, etc., at the storage-location level. In Warehouse Management, the storage location is further subdivided.

Explain the ‘Purchasing Organization’ in SAP.
This refers to the organizational structure in SAP that is responsible for procurement of materials. The ‘Purchasing Organization’ is the top-most organizational element in MM, and this can take any one of three forms such as (1) Cross-plant purchasing organizations (catering to more than one plant but within the same Company Code), (2) Plant-specific purchasing organizations (with a 1:1 relationship with the plant), and (3) Cross-company code purchasing organizations (catering to more than one Company Code). Entrusted with the activity of negotiating the price, delivery conditions, etc., of materials from vendors, the Purchasing Organization can further be subdivided into purchasing groups.

Explain the ‘Purchasing Group’ Concept in MM.
The ‘Purchasing Group’ carries out the actual activities of purchasing, and is assigned to a material in the material master. The activities of several purchasing organizations can be done by one purchasing group.

Explain the ‘Valuation Area’ Concept in MM.
The valuation of a material is done at the ‘Valuation Area,’ which can either be at the Company Code level or the Plant level. The level at which the valuation needs to happen is defined in the customizing. Note that once it is defined, you will not be able to change it later!
When the valuation is at the Company Code level, then the valuation of a material is uniform across the plants attached to that Company Code. On the other hand, if the valuation is at the plant level, then the value of the material is plantspecific and will vary from one plant to another. If you are using PP (Production Planning)/MRP in your company, then the valuation has to be at the plant level.

What is a ‘Factory Calendar’?
A ‘Factory Calendar’ is a calendar that is country-specific with a list of public holidays (maintained via the Holiday Calendar) and working days, which are Client-independent. The factory calendar helps in controlling goods issues/receipts. Each plant is assigned a factory calendar, and the calendar must be activated (through ‘CTS functionality’) before using it.

Explain How SD and MM are Connected in SAP.
The goods/services from a plant can be sold by one or more sales organizations. It is also possible that single sales organizations sells goods/services for several plants. When the sales organizations sells for more than one plant belonging to one or more Company Codes, then this is called inter-company sales, and will require you to make some special configurations in the system. A sales organization, attached to a Company Code, is further divided into distribution channels and divisions in SD. A division typically represents a product line, and is assigned to a material in the material master.

Outline the Functions Supported by ‘Material Master.’
The ‘Material Master’ is the central master record catering to various business functions in Logistics. The data stored in this master support a variety of business functions and operations such as:
  • Production Planning
  • MRP
  • Procurement
  • Invoice Verification
  • Inventory Management
  • Product Costing
  • Sales and Distribution
  • Quality Management
The data is stored, within a material master, at different organizational levels. The general data is valid for all the Company Codes at the Client level. The purchasing information is valid at the plant level. The sales information is valid at the sales organization/distribution channel. Lastly, when Warehouse Management is activated, the data is maintained at the warehouse number/storage type level.

Explain Why a ‘Material Master’ is Divided into ‘Views.’
Since the information in a material master needs to be maintained by a number of users across several modules, SAP has structured the master into a number of Views for facilitating easier access and updating of data. The views include:
  • Basic Data
  • Classification
  • Sales
  • Purchasing
  • Purchase Order text
  • Accounting
  • Foreign Trade 
  • Work Scheduling
  • Forecasting
  • Storage
  • Costing
  • Plant/Storage Location stock
  • MRP
What Information is Available in the ‘Accounting View’ of a ‘Material Master’?
The most important information maintained in the ‘Accounting View’ of a material master is the valuation class, which needs to be assigned to individual materials. The valuation class, in turn, helps in determining the relevant GL accounts for posting valuation-relevant transactions such as GR, GI, etc.
You will maintain the price control indicator in the accounting view, which enables determining how the stock of a material is to be valued (at Standard price (S) or Moving average price (V)).

Why do You Need ‘Material Types’ in MM?
One way to group materials is by ‘Material Type’ (the other being by Industry Sector’). This grouping helps determine what information or data is to be made available at the material master level for a particular material.
The material type (for example, FERT, HAWA, HALB, ROH, and so on) is used to control:
  • Which Views can be maintained on the master record
  • Which Fields are mandatory, optional, or for ‘display only’ in the material master
  • What kind of Procurement is allowed for that material (internal or external or both)
  • How to Number (Internal/External) and what Number Range is allowed
  • Whether Quantity and/or Value updating should be done in a particular Valuation Area
  • Which GL Accounts will be posted to (via the Valuation Class) during goods movement
  • The default Item Category Group (S&D) 
  • The default Price Control Indicator (S or V) and
  • Whether the default Price Control Indicator is changeable during material master maintenance
Explain the ‘Price Control Indicator.’
The ‘Price Control Indicator’ is used by SAP to determine how a material will be valuated, by default. The indicator can be set to:
  • Standard Price (S) or
  • Moving Average Price (V) 
When you set the indicator to ‘S,’ the system carries out all the inventory postings at the standard price. The variances  due to a different price of a material in goods movement or invoice receipts  if any, are all posted to price difference accounts. As a result, the standard price remains the same, unless it is changed intentionally by manual processing. This will be necessary only when the difference between the standard and moving average prices becomes very large. (While updating the price difference accounts, however, the system also updates the moving average price with these variances, so that you get a chance to adjust the standard price should the difference between the standard and moving average prices becomes very substantial.)

On the other hand, when you set the indicator to ‘V’ then all the goods receipts (GR) will be at the GR value. The system will then adjust the price in the material master by the GR price. However, if there is a difference between the moving average price of the material and the goods movement/invoice receipt, then the price difference is moved to the stock account, and the price of the material in the material master is adjusted accordingly.

Explain ‘Prices Maintenance’ for Materials Transferred from ‘Legacy’ to SAP.
Before you transfer the initial inventory from a legacy system to SAP, you need to create the relevant master data for the materials.

If you are planning to maintain a standard price for the materials, then you will create the material masters with ‘S’ as the price control indictor in SAP. With this control, when you enter the material inventory, the system valuates this stock with the standard price defined. In this case, you enter a new price and the system posts the price difference (between the standard price and the new price you entered) to a price difference account.

Similarly, if you are planning to maintain a moving average price for materials, then you will create the material masters with ‘V’ as the Price Control Indictor in SAP. With this control, when you enter the material inventory, the system valuates this stock with the moving average price defined. In this case, you enter a new price and the system adjusts the moving average price accordingly. If you enter only the quantity, and not any new price, the system continues to valuate the stock at the original moving average price, and the price of the material does not change.

What is the ‘Material Status’?
The ‘Material Status’ is a 2-digit code enabling you to control the usability of material for various MM and PP applications. This status key also controls warehouse management, transfers order instructions, quality inspection instructions, decides how the system behaves when a product cost estimate is created, and so on.
The material status can be maintained as (1) Plant-specific material status, (2) Cross-plant material status, and (3) Distribution material status.

What is the ‘EAN’?
The ‘EAN (International Article Number),’ equivalent to the UPC (Universal Product Code) of the United States, is an international standard number for identifying a material, which SAP allows you to assign (done in the ‘Eng./Design or Units of Measure’ screen) to the materials. The EAN is normally assigned to the manufacturer of a material. Made up of a prefix (to identify the country or company from where the material originates), article number, and a check digit (ensures correctness of an EAN number so that no incorrect entries are scanned or entered into the system).

What are Some of the ‘Partner Functions’ of a ‘Vendor’?
Through the definition of ‘Partner Functions’ in the Vendor Master, SAP helps to designate vendors for different roles. The partner role is designated by a 2-digit code.
  • VN   Vendor
  • PI   Invoice Presented by 
  • OA   Ordering Address
  • GS   Goods Supplier
  • AZ   Payment Recipient
A partner schema (also known as a partner procedure) is assigned to a vendor account group. The procedure specifies which partner roles are ‘allowed’/‘mandatory’/‘can be changed’ for a vendor master with that account group. You may assign three different partner schemas to an account group, one for each level of purchasing data, i.e., one at the purchase organization level, one at the VSR level, and one at the plant level. This enables maintaining different partners at different organizational levels.

What is a ‘Batch’ in the Context of ‘Batch Management’?
Representing a quantity of material with a homogenous set of properties/characteristics produced during a particular cycle of manufacturing, a ‘Batch’ is a subset of inventory quantity, which cannot be reproduced again with the same properties. A batch is linked to the classification system, and you can use it only when the classification system has been set up properly for batch management.

A batch is unique for a single material, and is unique at the Client level as well. That is, you will be able to use a batch number only once in the Client regardless of the plant and material. The batch will be known only in the plant where it was created. The batch numbers can either be manually assigned or system generated.

What are the Possible Values for ‘Procurement Types’?
The possible values for ‘Procurement Types’ are:
  • No procurement
  • External procurement
  • In-house production
  • Both procurement types
What are the ‘prerequisites’ for an ‘MRP Run’?
The following are the ‘prerequisites’ for an MRP Run: 
  • MRP activated
  • Valid MRP data for the material 
  • Valid MRP type
  • Valid material status
What is an ‘MRP Area’?
An ‘MRP Area’ is not an organizational structure, but a unit for which you can carry out Consumption-based MRP. The MRP area is used to carry out MRP for the components provided to a sub-contractor. There are three types of MRP areas that you will come across:
  • MRP Area for Storage Locations
  • MRP Area for Subcontracting Vendor Stock
  • MRP Area for the Plant
What is an ‘MRP List’?
An ‘MRP List’ displays the results of the last ‘planning run.’ Using a ‘collective display’ format, you will be able to display planning details for a number of materials for a given set of ‘selection parameters.’

Explain the ‘Re-Order Point’ Procedure.
The ‘Re-Order Point’ is the level of inventory that triggers material procurement. Once the inventory falls below this level, you need to create the order proposal either manually or automatically by the system.
In the case of the manual re-order point procedure, you will define the reorder point and the safety stock in the material master. On the other hand, in the automatic re-order point procedure, the system will calculate the re-order point and the safety stock based on the next period’s consumption pattern.

Explain the ‘Inventory Management’ Submodule.
The ‘Inventory Management’ submodule deals with the GR/GI of materials from/into the inventory. It also manages the transfer of materials from one storage location to another. As an important element of MM, this module is integrated with SD, PP, QM, and PM modules.

What is ‘Goods Movement’?
‘Goods Movement’ represents an event causing a change in the stock, with the change being value or status, stock type, or quantity. It also represents the physical movement of stock from one location to another. Goods movement is classified into:
  • Receipt of goods/services
  • Issue of materials
  • Stock transfers
What Happens During a ‘Goods Issue’?
The ‘Goods Issue (GI)’ results in a reduction in the stock quantity/value. The GI can be Planned (via sales order, production order, return delivery, delivery for internal, use etc.) or Unplanned (drawing a stock for a sample, scrapping, etc.).
The GI results in:
  • Creation of a Material/Accounting document
  • Update of Reservation for the issue (if any)
  • Update of GL accounts
  • Update of ‘points of consumption’ if applicable (cost center, project, etc.)
  • Update of Stock quantity
Explain ‘Stock Transfers.’
The physical movement of stock between locations is called a ‘Stock Transfer,’ which can be within a plant or between plants. Stock transfers can be carried out either in a single step or in two steps. The stock transfer may be from:
  • Company to Company
  • Plant to Plant
  • Storage Location to Storage Location
If there is a logical change in the stock type/status, then this kind of ‘transfer’ is called a ‘transfer posting.’ The transfer posting may be from:
  • Product to Product 
  • Quality Inspection to Unrestricted Use
  • Consignment Store to Storage Location
What is a ‘Stock Type’?
Used in the determination of available stock of a material, the ‘Stock Type’ is the sub-division of inventory at a storage location based on the use of that inventory. In SAP, there are many kinds of stock types:
  • Unrestricted (use) stock (the physical stock that is always available at a plant/storage location)
  • Restricted (use) stock 
  • Quality inspection stock (not counted for unrestricted use and may be made available for MRP)
  • Stock-in transfer 
  • Blocked stock (not to be counted as unrestricted stock and is not available for MRP)
Besides all of the above, which are all known as valuated stocks, you will also come across one more type called ‘GR blocked stock,’ which is a non-valuated stock.
The GR-blocked stock denotes all the stock accepted ‘conditionally’ from the vendors. This stock is not considered available for ‘unrestricted use.’ You will use the Movement Type 103 for the GR-blocked stock and Movement Type 101 is used for a normal GR.

Explain ‘Return Delivery.’
You will use ‘Return Delivery’ when you return goods to the supplier (vendor) for reasons such as damaged packaging, etc. Note that the ‘reason for return’ is mandatory as this will help you, later on, to analyze problems with a vendor. The system uses the Movement Type 122, and will create a return delivery slip, which will accompany the goods being returned.
If the ‘return’ is from a ‘GR-blocked stock,’ you need to use a different Movement Type: 104.

What are All the Various Types of ‘Physical Inventory’?
The following are the different types of ‘Physical Inventory’ in SAP MM: 
  • Periodic inventory (All the stocks are physically counted on a ‘key date’ (balance sheet date), and all the stock movements are blocked during physical counting)
  • Cycle counting (Physical counting is done at periodical intervals)
  • Sampling (Randomly selected stocks are counted physically, and the system uses this information to ‘estimate’ stock value on a given date)
  • Continuous (Stocks are tracked continuously throughout the fiscal year, with physical stock taking once a year, at least!)
What is a ‘Material Ledger’?
A ‘Material Ledger’ is nothing but a tool for inventory accounting that provides new methods for ‘price control’ for ‘material valuation’ (you can store the material inventory values in more than one currency). It makes it possible to keep the ‘material price’ constant over a period of time (say, over the life of a production order). The moving average price field is used to store a ‘periodic price.’ This periodic price stays constant and is the price used for valuation until you close the material ledger. At closing, the periodic price is updated based on the actual value of invoice receipts received for that material during the period.

Explain ‘Split Valuation.’ Why is it Necessary?
‘Split Valuation’ allows substocks of the same material to be managed in different stock accounts. This allows substocks to be valuated separately, and every transaction is carried out at the substock level. So, when processing a transaction, it is necessary to mention the substock.
The ‘split valuation’ is necessary if the material has:
  • Different Origins
  • Various Levels of Quality
  • Various Statuses
It is also required in situations where you need to make a distinction between ‘in-house produced materials’ and ‘materials procured externally,’ or if there is a distinction between ‘different deliveries.’

Explain the Basic Steps in ‘Configuring Split Valuation.’
The five basic steps for ‘Configuring Split Valuation’ are:
  • Activate ‘Split Valuation’ 
  • Define ‘Global Valuation Types’. For each Valuation type’ you need to specify: (a) whether ‘external’ purchase orders are allowed, (b) whether production orders are allowed, and (c) the account category reference.
  • Define ‘Global Valuation Categories’. For each valuation category specify: (a) default ‘valuation type’ to be used when purchase orders are created and whether this default can be changed, (b) default valuation type to be used when production orders are created and whether this default can be changed, and (c) whether a ‘valuation record’ should be created automatically when a GR is posted for a valuation type for which no record yet exists.
  • Allocate ‘Valuation Types’ to the ‘Valuation Categories’
  • Define which of the ‘Global Categories/Types’ apply to which ‘Valuation Areas’
Outline ‘Stock Valuation Methods’ for Material Revaluation.
There are three methods with which you can revaluate your stock for Balance Sheet purposes. Irrespective of the method you select, you will be able to valuate your stock either at the Company Code level or at the Valuation Area level:
  • LIFO (Last-In-First-Out): This method is based on the assumption that the materials received last were the ones issued/consumed first. The valuation is based on the initial receipt.
  • FIFO (First-In-First-Out): Here the assumption is that the materials received first are the ones consumed/issued first. So, the valuation is based on the most recent receipt. The FIFO method can also be used in conjunction with the lowest value method. By this you can determine whether the system should make a comparison between the FIFO determined price and the lowest value price. You can also determine whether the FIFO price should be updated in the material master record.
  • Lowest Value Method: Here, the stocks are valued at their original price or the current market price whichever is lower. This method is suitable when the inventory needs to be valued to take into account material obsolescence, physical deterioration, or changes in price levels.
How Does ‘Automatic Account Assignment’ Work in MM?
  1. ‘GL accounts’ are assigned to ‘Transaction Keys’ (BSX, WRX, PRD, UMG, GBB, etc.). 
  2. Transaction Keys identify which GL Accounts are to be debited or credited.
  3. Transaction Keys are assigned to ‘Value Strings’ (for example, WA01).
  4. ‘Movement Types’ (for example, 901) are associated with a ‘Value String.’
Explain ‘Automatic Account Assignment’ Configuration in MM.
There are four steps required to complete the ‘Automatic Account Assignment’ configuration settings for MM:
  • Finalize the ‘valuation level.’ 
  • Activate the ‘valuation grouping code’ option. (For this you need to group valuation areas using valuation grouping codes.)
  • Maintain ‘valuation classes’ and ‘account category references’ and their linkage to ‘material types.’ 
  • Maintain the ‘GL accounts’ for each combination of Chart of accounts, valuation grouping code, valuation class, and transaction key.
You may use the ‘automatic account determination wizard’ to complete the configuration settings, as the wizard guides you step-by-step.

Explain the ‘Transaction Keys’ in MM.
Also known as ‘process keys,’ the ‘Transaction Keys’ are pre-defined in the system to enable transaction postings in Inventory Management and Accounting (Invoice Verification). For each of the movement types in MM, there is a value string that stores these possible transactions.
The pre-defined transaction keys are:
  • BSX (used in Inventory Postings)
  • WRX (used in GR/IR Clearing Postings)
  • PRD (used to post Cost/Price differences)
  • UMB (used to post Revenue/Expenses from revaluation)
  • GBB (used in offsetting entries in Stock postings)
BSX, WRX, and PRD are examples of transaction keys that are relevant for a GR with reference to a purchase order for a material with standard price control. The transaction key UMB is used when the standard price has changed and the movement is posted to a previous period. Likewise, GBB is used to identify the GL account to post to as the offsetting entry to the stock account (when not referencing a purchase order) such as miscellaneous goods receipts, goods issues for sales orders with no account assignment, and scrapping. 

How Does the System Determine the Correct ‘GL a/c’ for a Posting?
Imagine that you are posting a goods movement.
  • Since the goods movement is from a plant, and the plant is assigned to a Company Code, the goods movement identifies the relevant Company Code.
  • As the Company Code has already been assigned to the Chart of Accounts, the system is able to identify the GL accounts.
  • The plant also determines the valuation area (and the optional ‘valuation grouping code’).
  • Since each movement type is assigned to a ‘value string’ which in turn is identified with a transaction key, the goods movement determines the correct transaction key.
  • Since each of the transaction keys is associated with the relevant GL accounts, through the value string, the movement type now identifies the relevant GL Account, and the transaction is posted.



Click below links for more SAP Logistics Interview Questions and Answers 


SAP Logistics (SD) Interview

What are the components of the SAP SD Module?
The important components in SAP Sales & Distribution module include:
  • Master data
  • Basic functions
  • Sales (including foreign sales and sales support)
  • Shipping and transportation
  • Billing
  • Sales support
  • Information systems
What are the important Organizational Elements of SAP SD?
The important Organizational Elements in SAP Sales & Distribution include:
  • Sales organization
  • Distribution channel
  • Division
  • Sales area
  • Sales group
  • Sales person
Explain the ‘Sales Organization.’ How it is assigned to a ‘Plant’?
The ‘Sales Organization’ is the top-most organizational element in SD. It represents and takes care of all the transactions relating to the selling and distribution of products or services. A distribution channel is assigned to one or more sales organization. The customer master can be maintained with different sales organization views.

The sales organization, identified by a 4-character code, is assigned to one or more plants. These plants are, in turn, assigned to a Company Code. So, it follows that any number of sales areas can be brought under a single Company Code.

Even though it is possible that you may have any number of sales organizations, it is recommended that you have a minimum number of these units in your setup. Ideal recommendation is for a single sales organization per Company Code. If you are selling the same product or service from more than one sales organization, then there is a clear indication that you have more sales organizations defined than what would ideally be required.

What is a ‘Distribution Channel’?
A ‘Distribution Channel’ depicts the channel through which the products or services reach the customers after they are sold (for example, wholesale, retail, direct sales, etc.). Represented by a 2-digit identifier, the distribution channel is assigned to one or more sales areas. As a result, one customer may be serviced through more than one distribution channel. Such as in a sales organization, the customer master data may have different distribution channel views.

What is a ‘Distribution Chain’?
A ‘Distribution Chain’ represents the possible combinations of sales organization(s) and distribution channel(s).

What is a ‘Division’?
A ‘Division’ depicts the product or service group for a range of products/services. For each division, you may define and maintain customer-specific parameters such as terms of payment, pricing, etc. The division may come under one or more distribution channels. 

What is a ‘Sales Area’?
A ‘Sales Area’ is a combination of the sales organization, distribution channel, and division.

Explain how ‘Human Elements’ are organized in SD.
There are three distinct organizational units in SD from the human angle:
  • Sales Office
  • Sales Group
  • Sales Person
The Sales Office represents the geographical dimension in sales and distribution. A sales office is assigned to a sales area. The staff of a sales office may be grouped into Sales Groups. This corresponds to sales divisions. A Sales Person is assigned to a sales group. This assignment is done at the personnel master record level. 

Where and how is a ‘Business Area Assignment’ done?
Business area assignment is done at two levels:
  • Plant level
  • Valuation area level
The ‘business area’ is assigned to the combination of ‘plant’/‘valuation area’ and the ‘division.’
A ‘Plant’ is Assigned to Which of the Entities in the SD Organization?
A Plant is assigned to:
  • Company Code
  • Combination of Sales Organization & Distribution Channel
  • Purchasing Organization
How is the ‘Shipping Point’ determined by the system?
The ‘Shipping Point’ is determined by the combination of shipping condition, loading group, and plant assigned to a shipping point. 

What are the important ‘Customer Master Records’?
Some of the important customer records are:
  • Sold-to-Party record
  • Ship-to-Party record
  • Bill-to-Party record
  • Payer record
What are the various sections of the ‘Customer Master Record’?
The different sections in a master record are:
  • General Data - You will be able to create general data such as addresses, telephones, contact persons, unloading points, etc., either from the accounting side or from the sales side.
  • Company Code Data - You will be able to create data in account management (credit management, payment details, taxations, insurance, etc.) that pertains to the Company Code in which the customer is created. You do this from the accounting side.
  • Sales & Distribution Data - The data for pricing, shipping, etc., comes under this category of information. You will create this from the SD area. You can have data for different sales areas for a single customer.
What is a ‘Customer-Material Information Record’?
The information relating to a material that applies only to a specific customer is known as ‘Customer-Material Information.’ This is nothing but the description of your ‘material by the customer,’ and you record this customer-specific information in the customer-material information record.

What is a ‘Sales Order’?
A ‘Sales Order’ is a contract between your Sales Organization and a Customer for supply of specified goods and/services over a specified timeframe and in an agreed upon quantity or unit. All the relevant information from the customer master record and the material master record, for a specific sales area, are copied to the sales order. The sales order may be created with reference to a ‘preceding document’ such as a quotation, then all the initial data from the preceding document is copied to the sales order.
The ‘sales order’ contains:
  • Organizational Data (sales organization, distribution channel, division, sales document type, pricing procedure, etc.).
  • Header Data (sold-to-party, sales office, sales group, pricing date, document date, order reason, document currency, price group, sales district, customer group, shipping condition, incoterms, payment terms, billing schedule, PO number, etc.).
  • Item Data (item category, order quantity, material, batch number, product hierarchy, plant, material group, shipping point, route, delivery priority, customer material, item number, etc.).
  • Schedule Line Data (schedule line, schedule line number, delivery date, order quantity, confirmed quantity, material availability date, loading date, proposed goods issue date, transportation date, movement type, shipping point, etc.).
What are the ‘Special Sales Document Types’?
  • SO   Rush Order
  • G2   Credit
  • RE   Return Order
  • KN   FoC (Free-of-Charge) Subsequent Delivery Order
  • RK   Invoice Correction Request
What is the ‘Consignment Stock Process’?
In the ‘Consignment Stock Process,’ you allow your stock or material to be at the customer’s site. You may also allow your stock or material to be made available at your site, but reserved for a particular customer. And you will allow the customer to sell or consume as much stock as he wants from this. You will then bill the customer only for the quantities that he has consumed or sold.

You will monitor the consignment stock—also known as special stock—in your system customer-wise and material-wise. You will use the standard sales order document type KB and standard delivery type LF for processing a consignment sales order.

Explain ‘Sales Document Blocking.’
You may be required to block a specific sales document type from further processing, when you want to block undesirable customers. You can achieve this for a specific customer or for a specific document type. You may also block it, in the customer master record, for a single sales area or for all the sales areas attached to the customer.

The blocking is done in customizing by assigning blocking reasons to the sales document types. Then in the customer master record do the necessary document block.

Can you ‘Block’ a transaction for a material that is ‘Flagged for Deletion’?
When you set the ‘deletion flag’ for a material at the plant level, you will still be able to enter an order even though the system will ‘warn’ you that the material has been flagged for deletion. If you need to block any transaction for a material, then you need to use the ‘Sales Status’ field in the ‘Sales Organization View’ of the material master. 

Can Items in a ‘Sales Order’ belong to different ‘Distribution Channels’?
No. The various items in a ‘Sales Order’ should belong to a single distribution channel only. However, the various items in a delivery can belong to different distribution channels.

Can the Items in a ‘Billing Document’ belong to different ‘Distribution Channels’?
No. The various items in a ‘Billing Document’ should belong to a single distribution channel only.

Differentiate between a ‘Sales Area’ and a ‘Sales Line.’
A ‘Sales Area’ is comprised of sales organization, distribution channel, and division whereas a Sales Line is the combination of the sales organization and the distribution channel.

Can a ‘Sales Area’ belong to different Company Codes?
No. A ‘Sales Area’ can belong to only one Company Code.

What is the ‘Storage Location Rule’?
The ‘Storage Location Rule’ assigned in the Delivery Document type determines the Storage Location, even when the storage location is entered during delivery creation. This is based on the following rules:
  • MALA: Shipping Point/Plant/Storage condition
  • RETA: Plant/Situation/Storage condition
  • MARE: MALA then RETA
How do you configure the ‘Partner Determination Procedure’ in SD?
The ‘Partner Determination Procedure’ is configured as outlined in the following steps:
  1. Create an account group
  2. Create and assign a number range to that account group 
  3. Create and assign the partner functions to the account group
  4. Create a partner determination procedure
  5. Assign the partner functions to the partner determination procedure
  6. Finally, assign the partner determination procedure to the account group
Where do you define ‘Unloading Points’ and ‘Goods Receiving Hours’?
The ‘Unloading Points’ and ‘Goods Receiving Hours’ are defined in the Customer Master>General Data>Unloading Points tab.

Where do you define the ‘Terms of Payment’ for a Customer?
The ‘Terms of Payment’ for a specific customer is defined in the Customer Master>Company Code Data>Payment Transactions Tab, and also in the Billing Document Tab in the Sales Area Data of the Customer Master.


Click below links for more SAP Logistics Interview Questions and Answers 
SAP MM Interview
SAP PP Interview

SAP CO Interview 3

Explain ‘Segments’ and ‘Cycles.’
A ‘Segment’ is one processing unit required to complete an automated allocation of distribution or assessment or reposting of planned/actual costs in controlling in SAP. A segment is made up of (a) allocation characteristics—to identify the sender/receiver, (b) values of the sender—plan/actual, type of costs to be allocated, and (c) values of the receiver—the basis for allocation, for example, the tracing factor such as SKF, percentages, etc.

When you combine multiple segments into a single process, then you call that the ‘Cycle.’ A Cycle helps you to process various segments in a chain-like fashion one after another. A Cycle consists of header data (valid for all Segments in a Cycle) and one or more Segments, with summarized rules and settings enabling allocation. The Segments within a ‘cycle’ can be processed iteratively (one segment waits for the results of another) or non-iteratively (all the segments are processed independently) or cumulatively (to take care of variations in receiver Tracing Factors or sender amounts).

Typically, when you start the cycles you will start them in a ‘test’ mode to see the allocations before actual postings. Technically, you can run the cycles in ‘production’ mode at any point of time, but the system will carry out the allocation postings only on the first day of a period. The utility of the cycle lies in the fact that you can run these period after period.

What is ‘Iterative Processing’ of Cycles?
‘Iterative Processing’ is nothing but the repetitive processing of sender/receiver relationships until the sender’s entire cost is transferred to the receiver(s). During iterative processing, you will not be able to use ‘fixed amounts’ as the ‘sender rules’; you will also not be able to define a percentage to remain on the sender. You will be able to use both plan and actual data while using the iteration.

What is ‘Splitting’? Explain the ‘Splitting Structure.’
‘Splitting’ is a process used to assign ‘activity-independent’ plans/actual costs, both primary and secondary, of a cost center to the individual activity types within that cost center. But the important requirement is that you will use this when there is no account assignment to the activity types.

You may either use the Splitting rules or the Equivalence number to achieve this. When you split the costs from a cost center, the cost center temporarily becomes more than one cost center for the purpose of allocation but again becomes a single cost center when posting happens in the subsequent period.

If you need to assign different cost elements or cost element groups to activities in more than one way, then you need to define a ‘Splitting Structure’ containing ‘splitting rules’ to determine the criteria of splitting ‘activity-independent’ costs to an activity type. If you have created the splitting structure in customizing and assigned the same to a cost center, then the system uses the splitting structure for cost apportioning; otherwise, it will use the equivalence number.

The ‘splitting rules’ determine the amount or the proportion of costs to be allocated to various activity types of a cost center and is based on the consumption of these activity types. The costs thus allocated may be a fixed sum, or a percentage, or it can even be based on the tracing factors or SKFs.

The ‘equivalence number’ is a basic method for splitting the costs when you manually plan for each of the activity types. By this, you will plan all activity-independent costs according to the equivalence numbers (the default is 1).

What is an ‘Activity Price Calculation’?
You will be completing the planning process only when you perform the ‘Activity Price Calculation,’ which is based on planned activities and costs. By doing this you are valuating the planned secondary costs at receiving cost centers. If you do not want to use activity price thus calculated, you are free to use the political price for the activity type.

As you are aware, the activity price is used for planned/actual allocation and is determined by using either the political price or the system-calculated activity price.

What is known as the ‘Political Price’ for an Activity Type?
The ‘Political Price’ is the price determined outside the SAP system, which is used in manual input using the required planning layout in planning.

What is ‘Allocation Price Variance?
‘Allocation Price Variance’ is the difference between the ‘political price’ of an activity type and the ‘system calculated activity price’ of the same activity type.

What is ‘Budgeting’?
‘Budgeting’ is used to augment the planning process at the cost-center level. While planning is considered the ‘bottom-up’ approach, budgeting is regarded as the ‘top-down’ method to control costs.

Budgeting usually comes ‘down’ from the ‘top (management)’ and is used to guide the planning process at the cost-center level. Note that budgeting is not integrated with postings; you will get an error when the system comes across a posting that will result in the actual values exceeding the budget for that cost center.

What are the ‘Direct Allocation’ Methods of Posting in CO?
The ‘Direct Allocation’ of posting in CO may be an actual cost entry or a transaction-based posting.

The actual cost entry is the transfer of primary costs from FI to CO, on a real-time basis, through the primary cost elements. You may also transfer transaction data by making the cost accounting assignment to cost objects from other modules such as FI-AA, SD, and MM:
  • FI-AA: Assign assets to a cost center (to post depreciation, etc.)
  • MM: Assign GR to a cost center/internal order
  • SD: Assign or settle a sales order to a cost center or internal order
Note that during actual cost entry, the system creates two documents. When you post the primary costs from FI to CO, the system will create a document in FI and a parallel document in CO, which is summarized from the point of the cost object/element.

Transaction-based postings are executed within the CO, again on a real-time basis, enabling you to have updated cost information on the cost centers at any point in time. You will be able to carry out the following transaction-based postings in CO:
  • Reposting
  1.   Line items
  2.   Transactions
  • Manual cost allocation
  • Direct activity allocation
  • Posting of Statistical Key Figures
  • Posting of sender activities
What is the ‘Indirect Allocation’ Method of Postings in CO?
The ‘Indirect Allocation’ of postings in CO may be used at the end of a period as a periodic allocation. This is done after you have completed all the primary postings. You may post the following periodic allocations using indirect allocation:
  • Periodic Reposting
  • Distribution
  • Assessment
  • Accrual Cost Calculation (Inputted Cost Calculation)
  • Indirect Activity Allocation
Explain ‘CO Automatic Account Assignment.’
For transferring primary costs to CO, on a real-time basis, you need to have ‘Automatic Account Assignments’ defined in the system. By doing this, you will always be able to post a particular cost to a specified cost center. You can also use this assignment for automatically posting the exchange rate differences (gain or loss), discount, etc., to CO.
You may also have additional account assignment at different levels such as:
  • Controlling area/account/Company Code in the customizing
  • Controlling area/account/cost element in the master record
  • Controlling area/account/Company Code/business area/valuation area in customizing
The system always goes through the route of customizing first, then to the cost element master record while accessing the account assignment rules.

How does ‘Validation’ differ from ‘Substitution’?
SAP uses validations and substitutions to check the integrity of data entered before posting a document. When you have both substitutions and validations defined, the system first completes the substitution then goes on to validate the entries. Note that only one validation and one substitution can be activated at a time for a controlling area per ‘call-up point.’ 

A ‘Validation’ uses Boolean logic for checking any type of combination of specified criteria (such as account type/cost center combination) for ensuring the validity before allowing you to post a document.
Example:
  • Validation Rule: If the cost element is ‘120000,’ then the cost center is ‘1200.’
  • Document: You try posting a document containing the cost element as ‘120000’ and the cost center is ‘1400.’
  • System Response: The system will throw an ‘error message’ after checking that the cost center value does not match the cost center value of the criteria for that given cost element value.
In contrast to validation which just checks for validity, substitution ensures that the system replaces a value assigned to one or more fields based on predetermined criteria, using, again, ‘Boolean logic.’ 
Example:
  • Substitution Rule: If the cost element is ‘120000,’ then the cost center is ‘1200.’
  • Document: You try posting a document containing the cost element as ‘120000’ and the cost center as ‘1400.’
  • System Response: The system will replace the entered cost center value of ‘1400’ with that of the correct value ‘1200.’
What is a ‘Call-up Point’?
A ‘Call-up Point’ is a particular point in transaction processing that triggers an action such as substitution or validation.

What is ‘Boolean Logic’?
‘Boolean Logic’ is based on simple logic to determine if a given statement is true or false. The logic works on the basic principle that a statement can either be true or false. In a complex statement (created using operators ‘and’/‘or’/‘nor,’ etc.) with many parts, the logic goes by assigning true or false from part to part, and then determines at the end whether the combination is true or false.

Explain ‘Reposting’ in Cost Center Accounting.
‘Reposting’ is one of the ‘transaction-based postings’ in Cost Center Accounting used to reallocate costs that were incorrectly posted to another cost center earlier. Also called internal reposting, there are two types:
  • Line Item Reposting
  • Transaction Reposting
Use Line Item Reposting only when a certain line item, from the original posting, needs to be reposted. Under this reposting, at the end of the transaction, the system creates a new CO document, but keeps the original FI document unchanged. In the new CO document created, the original FI number is referenced.

You will resort to the entire Transaction Reposting when the original posting was incorrect. Here, the original FI documents are not referenced to in the new CO document created, though the original FI document remains unchanged.

Is ‘Periodic Reposting’ Different from ‘Reposting’?
‘Periodic Reposting,’ a method under ‘indirect allocation,’ is used to correct multiple postings made to cost centers during a particular period. As such, this is similar to multiple reposting under ‘transaction-based postings.’

Periodic reposting is also similar to distribution, when you use this, at the period end, to transfer all costs from a ‘pooled cost center’ to other receivers. (Note that the ‘distribution’ is meant primarily for cost allocation, but periodic reposting is meant for correcting the posting errors.)

Explain ‘Manual Cost Allocation.’
‘Manual Cost Allocation’—one of the ‘transaction-based postings’—is used to post both primary and secondary actual costs (not the planned costs), and also to transfer external data. You may also use this to correct secondary costs that were incorrectly posted earlier. In the process of manual cost allocation, remember that you can use any type of cost element except 43, as this is meant exclusively for activity allocation.

You may use this among cost centers, internal orders, networks, network activities, sales orders, sales order items, WBS elements, etc., identifying these cost objects as senders/receivers.

What is ‘Direct Activity Allocation’?
‘Direct Activity Allocation’—one of the ‘transaction-based postings’—is used to record activities performed by a cost center and to allocate simultaneously to ‘receiving cost centers.’ You will use this ‘direct activity allocation’ only when you know the activity volumes of both the sender and the receiver. If not known, then use the indirect activity allocation at the period end.
You need to input the activity quantity, sender/receiver cost center and date to enable the system to allocate the costs; the system will automatically determine the allocation cost element and the activity price (either the planned price or the actual price). The system multiplies the activity consumed with that of the activity price to arrive at the allocated cost.

How do You Calculate ‘Accrued Costs’?
SAP provides two methods for calculating the Inputted or Accrued Costs in CO:
  • Target=Actual method
  • Cost Element Percent method
Describe the ‘Reconciliation Ledger.’
The ‘Reconciliation Ledger’ is used to keep track of all cross-Company Code transactions between FI and CO, as there is every chance that there may be some imbalance between the CO totals and FI totals when more than one Company Code is attached to a controlling area. This is because you may try to allocate costs from one cost center to another assigned to a different Company Code.

The reconciliation ledger records the Company Code, business area, functional area, amount, cost objects, cost element, currency (Company Code and controlling area), etc. You can make reconciliation postings at the end of a period to synchronize FI and CO with the configuration settings to automatically post the differences to FI.

While configuring the reconciliation ledger, you may use extended account assignments besides the normal account assignment for automatic transfer of reconciled postings. The extended account assignment helps make more comprehensive assignments to the relevant reconciliation accounts, with the option and flexibility of specifying any field in the reconciliation ledger (Company Code, cost element, functional area, etc.) for checking the ‘substitution rules.’
To aid in determining possible reconciliation postings, you can opt for selecting individual cost flows from all the relevant cost flows. This is accomplished by running the relevant report and looking for the relevant ‘data block’ (such as total cost flows, basic overview list, and detailed list).

What is ‘Variance Analysis’ in CO-OM-CCA?
‘Variance Analysis’ is the determination and interpretation of the difference(s) between the actual and planned (target) costs (within a cost center/cost center group) in cost center accounting. The analysis is intended to provide important clues to top management to plan better later.

What are the ‘Categories of Variances’ in CO-OM-CCA?
SAP helps to classify all variances into two categories:
  • Input Variance
  • Output Variance
Explain the ‘Input Variance.’
The ‘Input Variance’ is the result of the mismatch of amounts/quantities of inputs planned and actually used. You will be able to identify the following input side variances in the system:
  • Quantity Variance—when there is a difference between planned and actual quantity of activity consumption. The inference is that there is some production inefficiency leading to more consumption or there is some loss/shrinkage in the quantities.
  • Price Variance—when there is a difference between the planned and actual price of an activity. The inference will be that you may need to change the suppliers looking for lower prices or it is just a market condition.
  • Resource (use) Variance—when there is use of an unplanned cost element or there has not been a posting of a planned cost element. The inference is that there are some unidentified costs that may be planned in the next planning cycle, or just plain errors in postings.
  • Remaining (input) Variance—these are all miscellaneous variances where the system is not able to categorize a variance.
What is an ‘Output Variance’?
An ‘Output Variance’ is the result when the actual costs allocated from a cost center differ from the planned (or target) cost allocation from the cost center. The variances on the ‘output side’ may be any one of the following:
  • Volume Variance - This variance occurs with actual and planned activities (in terms of activity quantity and/or the activity itself). 
  • Output Price Variance - This variance occurs when the activity price used in the actual allocation is a political activity price (manually entered or plan price) differing from the system calculated activity price (target price).
  • Output Quantity Variance - This kind of variance occurs only on the actual side, when there is a difference between the actual activity quantity (manually) entered in the sender cost center, and the actual activity quantity allocated from that sender cost center.
  • Remaining Variance - This reflects the miscellaneous variance, at the cost center level, identified by the system on the output side but remains not categorized into any of the above three types. The possible reason can be that you have deactivated the output variances in the variance variant configuration or the output variance is less than the ‘minor difference’ you have defined in the ‘variance variant.’
How do You Deal with ‘Variances’?
Though the system identifies and calculates variances, they are not automatically dealt with by the system. Hence, these variances will remain at the cost center as a period-end balance and you need to act on that in one of the following ways:
  • You may do actual activity price calculation to revalue all internal allocations with a newly calculated price (as against the initial planned activity price), and post the difference to all the cost centers which initially received the allocations. This will help you in clearing all or a portion of output price variances.
  • You may ‘transfer’ the variance balance to other modules (such as CO-PA) for further analysis.
  • You may make additional automated allocations within CO-OM-CCA to one or more cost center.
What are All the ‘Standard Reports’ in CO?
SAP comes delivered with a number of ‘Standard Reports’ in the CO module. The reports are grouped under:
  • Planning reports
  • Comparison reports
  • Line item reports
  • Report for activity prices
  • Reports for variance analysis
  • Master data reports
  • Document display
All the reports are arranged in a ‘report tree’ with a hierarchical arrangement of reports under various nodes. Note that you will not be able to change the standard report tree supplied by SAP; if you need to you can copy it, define your own reports, and then attach these newly defined ones to the new report tree you just defined.

What is ‘Summarization’ in CO?
‘Summarization’ helps to condense and store the transaction data at the ‘cost center group’ level. You may do the summarization for the highest node of the standard hierarchy or any of the ‘alternate hierarchies.’ Once summarized, you will be able to create a vast number of reports with report run-time vastly reduced as all the data of the nodes are readily available from the summarized table.

Click below links for more SAP CO Interview Questions and Answers 
SAP CO Interview 1
SAP CO Interview 2