Question 1

During the implementation phase of an SAP solution, SAP Solution Manager supports several different implementation approaches. Which of the following is a key approach supported by SAP Solution Manager, focusing on documenting and implementing end t…

Accepted Answer

Introduction / Context: SAP Solution Manager provides methodological support for implementing SAP solutions. One of its strengths is the ability to document, configure and test end to end business processes, rather than handling projects purely as technical or phase driven exercises. Understanding the process oriented implementation approach is important for certification exams and for real projects where business processes are at the center of solution design. Given Data / Assumptions: The question concerns the implementation phase of an SAP solution managed with SAP Solution Manager. Solution Manager can support different perspectives, including phase driven and process oriented approaches. The focus here is on an approach centered on business process documentation and realization. Some options describe approaches that are incomplete or misaligned with SAP best practice. Concept / Approach: A process oriented implementation approach in Solution Manager means that projects are structured around business processes and scenarios. Project teams document process flows, assign transactions and configuration activities to process steps, and design test cases based on process variants. This fits with SAP's best practice of starting from business requirements and then mapping them to SAP functionality, rather than implementing purely by technical modules or phases. Solution Manager supports this approach through its business blueprint, process documentation and test management capabilities. Therefore, we look for the option that clearly mentions a process oriented implementation approach. Step-by-Step Solution: Step 1: Identify the approach described in option B, which highlights a process oriented implementation centered on business process documentation and realization.Step 2: Recognize that this aligns with Solution Manager's Business Blueprint and Business Process Documentation functionalities, which allow teams to capture and maintain process centric views of the solution.Step 3: Examine option A, which mentions a phase driven implementation approach that ignores business processes. While phase based project planning exists, ignoring business processes contradicts SAP best practice.Step 4: Examine option C, which refers to reengineering driven implementation without reference to SAP best practices, which is not a typical Solution Manager promoted approach.Step 5: Examine option D, which describes unstructured prototyping without a formal concept, also inconsistent with Solution Manager's structured methodology.Step 6: Conclude that option B correctly represents a key implementation approach supported by SAP Solution Manager. Verification / Alternative check: Reviewing Solution Manager documentation shows functions such as Business Blueprint and Solution Documentation, which are explicitly designed for modeling and managing business processes. Implementation roadmaps and templates are organized by processes and scenarios. SAP also promotes process oriented implementation through tools like SAP Best Practices packages, which integrate naturally with Solution Manager. These references confirm that a process oriented approach is a core approach enabled by Solution Manager. Why Other Options Are Wrong: Option A suggests a phase driven approach that ignores business processes, which goes against SAP's guidance and Solution Manager's capabilities for process documentation. Option C emphasizes reengineering without SAP best practices, which may be part of some projects but is not highlighted as a key approach supported by Solution Manager. Option D describes unstructured prototyping without a formal concept, which conflicts with the structured nature of Solution Manager project templates and methodologies. Common Pitfalls: A typical pitfall is to think only in terms of project phases (for example, blueprint, realization, final preparation) and overlook the parallel process orientation that defines what is actually being implemented. Another is to assume that process documentation is optional rather than central. For exams, remember that SAP Solution Manager is strongly associated with process centric implementation, with tools that capture, visualize and test business processes end to end. Final Answer: The key implementation approach supported by SAP Solution Manager is a process oriented implementation approach centered on business process documentation and realization.

Question 2

In the context of mySAP Business Suite, which of the following best describes the role of the Technology component within the overall suite?

Accepted Answer

Introduction / Context: mySAP Business Suite is composed of various layers and components, including technology, industry solutions, cross industry solutions and services. The Technology component, historically associated with platforms like SAP NetWeaver, provides the technical foundation on which business applications run. Understanding this layered architecture helps consultants correctly position SAP products and answer certification questions about how the suite is structured. Given Data / Assumptions: mySAP Business Suite is an integrated family of applications. Technology is one of the listed components, alongside cross industry solutions, industry solutions and services. The Technology component refers to the technical platform rather than business functionality or consulting services. The question asks for the role of the Technology component within the suite. Concept / Approach: In SAP terminology, the Technology component of mySAP Business Suite refers to the underlying technical platform that provides integration, runtime services, portal capabilities, business intelligence and other infrastructure. Examples include the application server, middleware and integration layers. This platform enables the industry and cross industry solutions to work together. Therefore, when selecting the correct answer, we look for a description that clearly identifies Technology as the foundation providing infrastructure and integration, not as a standalone solution, service or hardware system. Step-by-Step Solution: Step 1: Examine option A, which states that Technology is the underlying platform that provides infrastructure and integration capabilities for the entire suite. This aligns with the role of SAP NetWeaver and similar platforms.Step 2: Examine option B, which incorrectly describes Technology as a standalone cross industry solution independent of any platform. This confuses business functionality with the platform itself.Step 3: Examine option C, which presents Technology as purely a consulting service offering, which does not match the actual software components of the SAP platform.Step 4: Examine option D, which refers to hardware based computer center management provided by third parties, which is outside the scope of SAP's Technology component in the Business Suite.Step 5: Conclude that option A accurately describes the role of Technology in mySAP Business Suite. Verification / Alternative check: Official SAP materials describe SAP NetWeaver and its successors as the technology basis for SAP applications, providing integration, portal and development tools. They explicitly position this technology layer as the foundation for industry and cross industry solutions in mySAP Business Suite. In contrast, services refer to consulting and support offerings, while industry solutions are application components targeted at specific sectors. This confirms that Technology is the foundational platform, as described in option A. Why Other Options Are Wrong: Option B mislabels Technology as a business solution rather than the platform. Option C removes the software aspect entirely, describing Technology as pure consulting, which is incorrect. Option D shifts the focus to hardware and third parties, while SAP's Technology component is software centric and part of the suite. These options do not reflect SAP's own description of the Technology layer. Common Pitfalls: Some learners confuse the term Technology with generic IT services or hardware, instead of recognizing it as a specific SAP application platform. Another pitfall is to lump all components of mySAP Business Suite together without understanding which part plays which role. For certification exams, it is important to know that Technology refers to the platform that supports and integrates the business solutions, rather than being just another application or service. Final Answer: Within mySAP Business Suite, the Technology component is the underlying technology platform that provides infrastructure and integration capabilities for the entire suite.

Question 3

In SAP Materials Management, you want to post a goods receipt for a production order, but the quantity should first be posted to goods receipt blocked stock before it can be moved to unrestricted use. Which movement type do you use to release a good…

Accepted Answer

Introduction / Context: In SAP Materials Management and Production Planning, material movements are recorded using movement types. Different movement types represent different business transactions, such as goods receipts, goods issues and stock transfers. When goods are initially posted to goods receipt blocked stock, a subsequent movement type is required to release them into unrestricted use. Understanding which movement types correspond to these business steps is essential for both daily operations and exam questions. Given Data / Assumptions: Goods have been received and posted to goods receipt blocked stock (for example, using a blocked stock movement). You now want to move quantities from GR blocked stock to unrestricted use stock. The question asks which movement type performs this release from GR blocked stock to unrestricted use. Movement type options include 101, 105, 501 and 505. Concept / Approach: Movement type 101 is commonly used for a standard goods receipt to unrestricted use stock. When a goods receipt is posted to GR blocked stock, a different movement, such as 103, might be used initially. After quality checks or other approvals, movement type 105 is used to transfer the quantity from GR blocked stock to unrestricted use stock. Movement types 501 and 505 are associated with receipts without purchase orders or other special cases. Therefore, to release goods from GR blocked stock into unrestricted use, the correct movement type is 105. Step-by-Step Solution: Step 1: Recall the standard SAP movement types: 101 for GR to unrestricted use, 103 for GR to GR blocked stock and 105 for release from GR blocked stock to unrestricted use.Step 2: Recognize that the business requirement described is to move goods that are already in GR blocked stock into unrestricted use.Step 3: Evaluate option B, movement type 105, which is defined as the movement to release quantities from GR blocked stock to unrestricted use, typically following a previous 103 posting.Step 4: Examine option A, 101, which is for direct GR to unrestricted use, not a transfer from blocked stock.Step 5: Examine option C, 501, and option D, 505, which are used for receipts without purchase orders or special cases and do not represent the standard release from GR blocked stock.Step 6: Conclude that movement type 105 is the correct choice for releasing goods from GR blocked stock into unrestricted use. Verification / Alternative check: In SAP help and configuration tables for movement types, movement 105 is documented as the follow on movement to 103, used to transfer quantities from GR blocked stock to unrestricted use. Process documentation and training guides for quality inspection flows also show the sequence 103 then 105. Demonstrations in a test system will confirm that when you perform a 105 movement, the system reduces GR blocked stock and increases unrestricted use stock for the material in question. Why Other Options Are Wrong: Option A, 101, posts the goods receipt directly into unrestricted use stock and is not used to transfer from GR blocked stock. Option C, 501, is for goods receipt without a purchase order into unrestricted use, unrelated to GR blocked stock. Option D, 505, is associated with special receipt or transfer scenarios that do not match the standard GR blocked stock release. None of these correctly implement the specific step of releasing goods from GR blocked stock into unrestricted use stock. Common Pitfalls: One common pitfall is to assume that 101 can be used in all goods receipt scenarios, including releases from blocked stock. Another is confusing GR blocked stock, which is specific to goods receipts, with other blocked stock types or quality inspection stock. For exam purposes, it is helpful to memorize key movement type pairs such as 103/105 for GR blocked and release, as well as 101 for direct GR to unrestricted use. This will make it easier to answer questions about stock postings quickly and accurately. Final Answer: The movement type used to release quantities from GR blocked stock into unrestricted use is 105.

Question 4

In SAP Materials Management, transaction MIGO is the central transaction for goods movements. For which of the following functions is MIGO typically used?

Accepted Answer

Introduction / Context: Transaction MIGO is one of the most frequently used transactions in SAP Materials Management. It provides a unified interface for posting goods movements such as goods receipts, goods issues and transfer postings, often with references to purchase orders, production orders or other material documents. Understanding the core purpose of MIGO helps end users manage inventory correctly and helps candidates answer certification questions about which tasks are suitable for this transaction. Given Data / Assumptions: The question is about the typical use of transaction MIGO in SAP Materials Management. MIGO focuses on goods movements and can work with references to various documents. Some options describe functions that belong to other modules or transactions. We must pick the function that best represents MIGO's primary purpose. Concept / Approach: MIGO is designed to post goods movements. A very common scenario is entering a goods receipt with reference to a purchase order (for externally procured materials) or to a production order (for internally produced materials). MIGO also allows displaying material documents and performing transfer postings, but its core use case in practice and in training examples is to post goods receipts and other stock movements. It is not a pure display transaction for purchase orders, and it is not used to maintain master data. Therefore, we look for the option that explicitly mentions entering a goods receipt with reference. Step-by-Step Solution: Step 1: Recall that MIGO is accessed for goods movements, including goods receipts, goods issues and transfer postings.Step 2: Recognize that entering a goods receipt with reference to a purchase order or production order is one of the most common and typical uses of MIGO.Step 3: Examine option C, which describes exactly this function: entering a goods receipt with reference.Step 4: Examine option A. While MIGO can display material documents, its primary purpose is not just display but posting. The wording of the question asks for a typical function, and option C is clearer and more specific.Step 5: Examine option B, display purchase order, which is mainly done using ME23N and not the core purpose of MIGO.Step 6: Examine option D, maintain vendor master data, which is handled through transactions such as XK01 or MK01 and is unrelated to MIGO.Step 7: Conclude that option C is the best representation of a typical function of MIGO. Verification / Alternative check: In SAP training courses and documentation, examples of MIGO usage nearly always involve posting goods receipts, either with or without reference to purchase orders or production orders. The initial screen of MIGO asks you to choose a transaction type such as Goods Receipt, Goods Issue or Transfer Posting, and a reference document type. While you can use MIGO to display material documents, this is secondary to its posting capabilities. This supports the choice of option C as the most appropriate answer. Why Other Options Are Wrong: Option A mixes display and posting but does not highlight the typical use case of goods receipt with reference, and could be considered too vague. Option B refers to a purchasing display function that is correctly handled with separate purchasing transactions, not MIGO. Option D is related to master data maintenance, which is not part of the scope of MIGO and belongs to vendor master transactions in FI and MM. Common Pitfalls: One pitfall is to remember only that MIGO is linked to material documents and assume it is primarily a display tool. Another is to confuse the many transactions in SAP MM and forget which ones handle master data versus transactional postings. For certification exams, remember that MIGO is the central transaction for goods movements, especially goods receipts and goods issues, often with references to purchasing or production documents. Final Answer: A typical function of MIGO is to enter a goods receipt with reference to a purchase order or production order.

Question 5

In SAP Materials Management, the user parameter EFB controls certain default behaviors when creating purchase orders. Which of the following statements correctly describes what parameter EFB can be used to allow?

Accepted Answer

Introduction / Context: In SAP Materials Management, user parameters influence how transactions behave for specific users. Parameter EFB is one such parameter that affects how purchase orders can be created. Understanding what EFB does is important for controlling purchasing discipline and for answering certification questions about user specific settings. This question asks you to identify the correct description of the functionality controlled by parameter EFB. Given Data / Assumptions: The context is creating purchase orders in SAP MM. Parameter EFB is a user parameter that can be set in user master data. It controls whether purchase orders may be created without a reference document. The options list various purchasing related behaviors that might be influenced by parameters. Concept / Approach: Parameter EFB is commonly associated with the flexibility to create purchase orders without referencing preceding documents such as purchase requisitions, contracts or scheduling agreements. In some organizations, policy dictates that POs should always be based on prior requisitions or agreements; in others, certain users are permitted to create free POs. The parameter helps enforce or relax this restriction. It does not control planned delivery time checks, display of outline agreement conditions or automatic copying of prices from earlier POs; those functions are managed by other settings and transaction logic. Step-by-Step Solution: Step 1: Recall that EFB is mentioned in SAP documentation as a parameter influencing PO creation without reference.Step 2: Examine option C, which states that EFB allows a user to create a purchase order without reference to a preceding document. This matches the commonly described behavior of EFB.Step 3: Consider option A, which suggests that EFB ensures planned delivery time is checked against the delivery date during source determination. This is handled by MRP and source determination settings, not by EFB.Step 4: Consider option B, which refers to displaying conditions from an outline agreement, which is a separate function not controlled by this parameter.Step 5: Consider option D, which deals with automatic defaulting of prices from the last PO, a standard MM feature not tied to parameter EFB.Step 6: Conclude that option C correctly describes what parameter EFB is used for. Verification / Alternative check: SAP help for user parameters and purchasing configuration notes that parameter EFB can be used to control whether purchase orders may be created without reference. Consultants sometimes set this parameter to enforce stricter purchasing procedures, requiring POs to be linked to requisitions, contracts or scheduling agreements. When EFB does not allow free POs, an attempt to create a PO without reference may trigger messages or be blocked depending on configuration. This is consistent with the description in option C. Why Other Options Are Wrong: Option A misattributes a function of MRP and source determination to a user parameter. Option B refers to the display of outline agreement conditions, which is part of standard PO functionality and customizing but not controlled by EFB. Option D describes copying the last purchase order price, which is governed by info records, price determination and document defaults, not by EFB. These options do not match the documented behavior of parameter EFB. Common Pitfalls: A common pitfall is to assume that a user parameter with a generic name like EFB could control any purchasing related behavior. However, SAP parameters usually have specific, documented purposes. Another pitfall is failing to distinguish between configuration at system or document type level and user specific parameters. For exam questions, focus on the precise wording of the parameter's documented effect: in this case, whether a PO can be created without a reference document. Final Answer: Parameter EFB is used to allow a user to create a purchase order without reference to a preceding document, such as a purchase requisition or contract.

Question 6

In SAP Materials Requirements Planning (MRP), what is the main purpose of specifying a planning horizon when you use a net change in planning horizon (NETPL) MRP run?

Accepted Answer

Introduction / Context: In SAP MRP, different planning types and horizons can be used to balance planning accuracy with system performance. The planning horizon is a time period in which planning relevant changes are considered when using a net change in planning horizon (NETPL) run. Understanding how the planning horizon interacts with NETPL is important for optimizing MRP performance and is a common topic in SAP PP and MM certifications. Given Data / Assumptions: The MRP type in use supports net change in planning horizon (NETPL). A planning horizon is defined in customizing or in the material master. The question asks for the main purpose of specifying this planning horizon. We assume the reader understands the difference between NETCH and NETPL planning types. Concept / Approach: NETPL (net change in planning horizon) is an MRP procedure that includes only materials for which there have been planning relevant changes within the defined planning horizon. The planning horizon limits how far into the future the system looks when deciding whether a material needs to be planned in a given run. By restricting the run to a defined horizon, system load is reduced while still ensuring that imminent requirements and changes are considered. The planning horizon does not directly decide whether forecasts are considered, does not filter by procurement type and does not itself choose between NETCH and NETPL; rather, it is used within NETPL to decide which materials are included. Step-by-Step Solution: Step 1: Recall that in NETPL, the system considers only materials with planning relevant changes in a certain future time window.Step 2: Understand that the planning horizon defines this time window, measured from the planning date into the future.Step 3: Examine option A, which states that only materials with planning relevant changes inside the planning horizon are included in the MRP run when NETPL is used. This is exactly how NETPL and planning horizon interact.Step 4: Examine option B, which mentions forecast inclusion. Forecast inclusion is controlled by other settings, not by the planning horizon itself.Step 5: Examine option C, which restricts NETPL to externally procured items, which is not the function of the planning horizon.Step 6: Examine option D, which describes choosing between NETCH and NETPL. This choice is made when configuring MRP types or running MRP, not by the planning horizon.Step 7: Conclude that option A is the correct description of the purpose of specifying a planning horizon for NETPL. Verification / Alternative check: SAP help for MRP procedures explains that NETPL looks only at materials that have undergone planning relevant changes within the planning horizon. Changes outside of that horizon are not considered in the current run, which improves performance but still ensures near term requirements are met. The planning horizon can be maintained in the MRP settings, and NETCH runs ignore it, considering the entire horizon instead. This confirms that the main purpose of the planning horizon is as stated in option A. Why Other Options Are Wrong: Option B confuses planning horizon with forecast control; forecast data usage is governed by other parameters such as consumption modes or forecast requirements types. Option C suggests that the planning horizon has an effect on procurement type filtering, which is incorrect; procurement type is defined at the material level and is independent of horizon. Option D treats the planning horizon as a switch between NETCH and NETPL, but the choice of planning type is made separately from horizon definition. Common Pitfalls: One pitfall is to think that planning horizon limits how far MRP plans requirements in general; in reality, it specifically affects which materials are included in a NETPL run based on changes in that period. Another is to overlook the difference between NETCH and NETPL and assume that defining a planning horizon will have the same effect for all planning types. For exams, remember that the planning horizon is particularly relevant for NETPL and is used to filter materials based on recent changes within a specified time window. Final Answer: The purpose of specifying a planning horizon is to ensure that only materials with planning relevant changes inside the planning horizon are included in the MRP run when NETPL is used.

Question 7

In SAP planning, you want to view the most up to date planning situation for a material, including the latest requirements and receipts. Which transaction provides the most current planning data in SAP, updated dynamically as changes occur?

Accepted Answer

Introduction / Context: When working with Materials Requirements Planning in SAP, you have different transactions to analyze the planning situation. Some lists show a static snapshot from the last MRP run, while others show a dynamic, always up to date picture, reflecting bookings and changes as they happen. Knowing which transaction to use for the most current planning data is essential for planners and is also a common exam topic in SAP PP and MM certifications. Given Data / Assumptions: The goal is to see the most up to date planning data for a material. The Stock/Requirements List (MD04) is a dynamic list. The MRP List (MD05) is a static snapshot from the last MRP run. Stock Overview (MMBE) focuses on stock quantities by stock type, and document lists show posted documents. Concept / Approach: The Stock/Requirements List (transaction MD04) is dynamically updated with each relevant transaction, such as goods movements, order changes and new requirements. It always shows the current situation of available stock, planned receipts and requirements. The MRP List (MD05) shows the situation as of the last MRP run and is not updated until the next run. Stock Overview (MMBE) shows quantities by stock type but does not provide the same planning view of future requirements and receipts. Document lists show historical documents, not the planning picture. Therefore, for the most current planning data, MD04 is the correct choice. Step-by-Step Solution: Step 1: Recall that MD04 (Stock/Requirements List) is a dynamic list that updates in real time as transactions are posted.Step 2: Recognize that MD05 (MRP List) is static and represents the outcome of the last MRP run, not current changes.Step 3: Understand that MMBE (Stock Overview) shows physical stock by type but not the full planning picture of future receipts and requirements.Step 4: Note that list displays of material or accounting documents show past postings, not live planning data.Step 5: Examine option A, which correctly identifies the Stock/Requirements List as providing the most up to date planning data.Step 6: Conclude that option A is the correct answer. Verification / Alternative check: In SAP documentation, MD04 is described as the primary tool for monitoring planning situations because it reflects all changes as they occur. If you post a goods issue, change a planned order or receive new sales orders, MD04 updates immediately. MD05, in contrast, retains the state from the last MRP run and is primarily used for analyzing MRP results at that time. Tests in a sandbox system will show that MD04 changes as soon as new transactions are posted, confirming its dynamic nature and suitability for current planning data. Why Other Options Are Wrong: Option B, the MRP List, is useful for understanding the outcome of an MRP run but does not include subsequent changes until the next run. Option C, Stock Overview, focuses on stock balances and does not show all future requirements and receipts in a time phased format. Option D, document lists, are suitable for audit and analysis of posted transactions but do not present the live planning picture required for day to day planning decisions. Common Pitfalls: Users sometimes rely on the MRP List for planning decisions and forget that it may not reflect the latest sales orders or production changes. Another pitfall is to treat stock reports as planning tools, which can overlook unfulfilled requirements and incoming receipts. For exams and real world practice, remember that the Stock/Requirements List is the primary, most up to date view of the planning situation and should be used when real time accuracy is important. Final Answer: The transaction that shows the most up to date planning data is the Stock/Requirements List (for example, transaction MD04).

Question 8

In SAP Materials Requirements Planning (MRP), several types of MRP areas can be defined to plan subsets of a plant. Which of the following is NOT a valid MRP area type in SAP?

Accepted Answer

Introduction / Context: MRP areas in SAP allow planners to run MRP for specific subsets of a plant, such as individual storage locations or subcontractors, while still maintaining an overall plant level view. Understanding the valid types of MRP areas is essential for correct configuration and is a typical topic in SAP PP and MM certifications. This question asks you to identify which of the listed types is not a valid MRP area type in SAP. Given Data / Assumptions: MRP areas can be defined to refine planning within a plant. Standard MRP area types include plant MRP areas, storage location MRP areas and subcontractor MRP areas. The list includes one item that does not exist as a separate MRP area type. We must choose the one that is not recognized in SAP as a valid MRP area type. Concept / Approach: In SAP, the basic MRP area is the plant MRP area, which covers the whole plant. Additional MRP areas can be created for specific storage locations (storage location MRP areas) or for subcontractors (subcontractor MRP areas) to handle consignment and subcontracting scenarios more precisely. However, there is no separate MRP area type called consignment MRP area; consignment stock can be handled within plant or storage location MRP areas or subcontractor areas as needed. Therefore, the option that names a consignment MRP area is the one that does not exist as a distinct type. Step-by-Step Solution: Step 1: Recall that valid SAP MRP area types include plant MRP areas, storage location MRP areas and subcontractor MRP areas.Step 2: Examine option B, Plant MRP area, which is a standard and valid type representing the entire plant.Step 3: Examine option C, Storage location MRP area, which is also valid and used to plan specific storage locations separately.Step 4: Examine option D, Subcontractor MRP area, which is a valid type used to plan materials for subcontractors.Step 5: Examine option A, Consignment MRP area, which is not listed as a separate standard MRP area type in SAP; consignment is a stock type and business scenario, not an MRP area type.Step 6: Conclude that option A is the invalid MRP area type. Verification / Alternative check: SAP documentation for MRP areas describes the three valid types: plant, storage location and subcontractor. It explains how each type is configured and used in planning. There is no reference to consignment MRP areas as a separate category. Consignment stocks are instead managed using consignment vendors and appropriate stock categories, often within plant or storage location MRP areas. This confirms that consignment MRP area is not a valid type. Why Other Options Are Wrong: Option B is a valid type and is the default MRP area for a plant. Option C is valid and allows granular planning for individual storage locations, such as high value or long lead time items. Option D is valid and supports planning for subcontractors, where stock is supplied to a subcontractor's premises. These options represent genuine MRP area types and therefore cannot be the correct answer to a question asking for the invalid type. Common Pitfalls: A common pitfall is to confuse stock categories, such as consignment stock, with organizational structures like MRP areas. Another is to think that any special procurement scenario automatically has a dedicated MRP area type. For the exam, remember that MRP areas in SAP are defined at plant, storage location and subcontractor level, and that consignment is treated as a stock and procurement category, not as an MRP area type. Final Answer: The option that is NOT a valid MRP area type is Consignment MRP area.

Question 9

In the standard SAP Time Evaluation schemas, time wage type selection (the step that creates wage types from time data) is carried out in which subschema?

Accepted Answer

Introduction / Context: In SAP HCM Time Management, time evaluation uses schemas and subschemas to process employees' time data. One important step in time evaluation is time wage type selection, where recorded time pairs (such as attendances, absences or overtime) are converted into wage types that can then be passed to payroll. Understanding in which subschema this selection occurs helps consultants adjust time evaluation logic and is a common topic in SAP HCM certification exams. Given Data / Assumptions: We are dealing with standard SAP time evaluation schemas. Time wage type selection refers to the processing step where time data is turned into wage types. The question asks for the subschema that performs this step. Subschema names include TC00, TC01, TC10 and TC11. Concept / Approach: Standard SAP time evaluation schemas, such as TM00, are composed of various subschemas and personnel calculation rules. Time wage type selection is typically handled in a dedicated subschema that calls the rules responsible for generating wage types from time pairs. In SAP documentation and schema analysis, subschema TC10 is designated for time wage type selection (including rules like KMOD and MODIF for wage type generation). Other subschemas, such as TC00 and TC01, handle more general time evaluation steps or country specific variations. Therefore, we look for the option that names TC10 as the subschema for time wage type selection. Step-by-Step Solution: Step 1: Recall from SAP HCM time schema documentation that TC10 is generally used for time wage type selection in standard time evaluation.Step 2: Recognize that TC00 and TC01 are higher level or country specific subschemas that organize broader parts of time evaluation, rather than focusing solely on wage type selection.Step 3: Examine option B, Subschema TC10, which correctly matches the standard naming for the time wage type selection subschema.Step 4: Examine options A, C and D (TC11, TC01, TC00) and note that they are either specialized or general subschemas not specifically dedicated to wage type selection.Step 5: Conclude that TC10 is the subschema responsible for time wage type selection. Verification / Alternative check: Reviewing the standard SAP time evaluation schema TM00 in the system, you can expand the included subschemas and see TC10 being called at the point where time wage types are generated. Documentation on time evaluation also describes TC10 as the subschema that contains the wage type selection rules. Other subschemas, such as TC00, are used for general evaluation flow, and TC01 or TC11 may be used for specific enhancements or country versions. This empirical check confirms that TC10 is the correct answer. Why Other Options Are Wrong: Option A, TC11, is not the standard subschema for time wage type selection and may be used for other purposes or country specific logic. Option C, TC01, is associated with other parts of the time evaluation process and is not the dedicated time wage type selection subschema. Option D, TC00, is a more general subschema that calls other subschemas including TC10, but it does not itself specialize in wage type selection. Common Pitfalls: One pitfall is confusing the main schema (such as TM00) with its subschemas and assuming that all processing is done in a single schema. Another is mixing up subschema names, which are similar and differ only by the last digit. For exam questions, it helps to memorize that TC10 is the standard subschema for time wage type selection, while TC00 and TC01 play more general roles in time evaluation. Final Answer: Time wage type selection in standard SAP time evaluation is carried out in Subschema TC10.

Question 10

Function GWT is used in time valuation to select time wage types for all absences, which are valued on the basis of the As If principle

Accepted Answer

TRUE

Question 11

AUC have depreciation key, which denotes that depreciation will not be calculated

Accepted Answer

TRUE

Question 12

Maximum number of sessions a user can open when he logs on to SAP A.Six B.One C.Three D.Five

Accepted Answer

: A

Question 13

Posting through a special ledger indicator affects A. offsetting entry to the main reconciliation account of the vendor/customer B. the alternative reconciliation account and the main reconciliation account of the vendor/customer C. the alternative …

Accepted Answer

: C

Question 14

Fast entry screens in FI are used to enter A. G/L, customer and vendor line items B. G/L line items C. customer and vendor line items D. Invoice receipt against GR

Accepted Answer

: B

Question 15

The order of fields as they appear during the log on to an R/3 system is A. client, user id, password B. client, user id, password, language C. user id, client, password, language D. language, client id, password

Accepted Answer

Answer: B

Question 16

The three tier in R/3 system is represented by A. user, data base, programs B. application, data base and customer of R/3 C. presentation client, R/3 application and data base D. data, user and application

Accepted Answer

: C

Question 17

In 1:n assignments, the operational charts of accounts in all assigned company codes and in the controlling area must be the same.

Accepted Answer

The charts of accounts must be the same.

Question 18

The benefits of the testing features include: A. Reduce time for test preparation and execution B. Central storage of testing material and test results C. Re-use of existing testing material. D. Single point of access to complete system landscape

Accepted Answer

Answer: A , B , C , D

Question 19

Solution Manager: A. Is an add-industry solution. B. Is installed as a part of each of your existing landscape C. Is a stand alone system that comunicates with the systems in your landscapes D. Is only used for the implementation of your solution

Accepted Answer

: C

Question 20

Why solution manager Faster implementation and more efficient operations of solutions A. Optimal access to all support services B. All available implementation and upgrade content is included C. Optimal support of all operations , maintenace and imp…

Accepted Answer

: A , B , C , D

SAP Certification Questions