Interested in SRM Video Training? Click here for a free SRM Overview Video
SAP Certified Application Associate – Supplier Relationship Management with SAP SRM 7.0
These questions are similar to the ones asked in the actual Test.
How should I know? I know, because although I got my SRM Certification five years back, I have re- certified with the latest version of the Associate Certification test.
The certification test Solution Consultant Supplier Relationship Management SAP SRM 7.0 EHP 1, verifies the knowledge in the area of SRM for the consultant profile.
This certificate proves that the candidate has a basic understanding within this consultant profile, and can implement this knowledge practically in projects.
The SAP Certified Application Associate can contribute to the success of the planning and implementation phases of the project in a mentored role and would typically have a maximum of three years experience in the solution area.
Project experience should not be prerequisite for a competent and well trained candidate to pass this exam.
Before you start here are some Key features of the SRM Associate Certification Exam
– The exam is Computer based and you have three Hours to answer 80 Questions.
– The Questions are (mostly) multiple choice type and there is NO penalty for an incorrect answer.
– Some of the Questions have more than one correct answers. You must get ALL the options correct for you to be awarded points.
– The Official Pass percentage is 65% (But this can vary). You will be told the exact passing percentage before you begin your test.
Sample Questions
Note: Unless stated otherwise, All questions have more than one correct answer.
Q1. With reference to Master Data in SRM 7.0, which of the following are true?
A. Master data such as products, business partners etc, is available locally in the SRM system.
B. In SRM, both materials and services are stored as products. These are differentiated by ‘Product Types’
C. Product categories correspond to material hierarchies in the SAP back end system.
D. If the product ID needs to be the same in SRM, as in the backend system, then this can be no longer than 21 characters.
Answer:
A, B
All master data is available locally in the SAP Supplier Relationship Management (SRM) system. This data includes, for example, product master records, business partner master records, and product categories. You copy the master data from the back-end system to SAP SRM.
In SAP SRM, both materials and services are stored as products. However, you can distinguish materials from services by the product type.
Product categories correspond to material groups in the SAP back-end system.
If the SAP SRM system communicates with an SAP back-end system, the length of the product ID is restricted to a maximum of 18 characters.
This should be the case even if the products are created locally, and not replicated from the back- end system. If you assign a product ID with more than 18 characters, a different number (with a maximum of 18 characters) has to be assigned in the back-end system.
Q2. SRM offers various types of multilevel hierarchies. You can use hierarchies to group together related product categories and suppliers, making them easier to find and report on. Which of the following multilevel hierarchies come as part of standard delivery?
A. Supplier Hierarchies
B. Price Hierarchies
C. Base Hierarchies
D. Central Contract Hierarchies
Answer:
A, D
The following multilevel hierarchies come as part of standard delivery:
• Product category hierarchies
• Supplier hierarchies
• Central contract hierarchies
Product category hierarchies provide the following:
• Extended search of product categories
• Import of product category hierarchies into the SAP SRM system, for example:
• Back-end material categories from SAP ERP
• Standard product category hierarchies (such as UNSPC, eClass)
• Customer-defined product categories
Supplier hierarchies provide the Structure and model of supplier relationships
Central Contract Hierarchies Group together similar contracts, making them easier to find and process.
Q 3. In SRM, you can selectively implement new functions or enhance existing ones by activating business functions. In this context, which of the following are true? (Only one answer is correct)
A. SAP Supplier Relationship Management (SAP SRM) provides a Single-step activation process.
B. Business functions are activated using the BLW switches
C. A Business function once activated can be deactivated under certain conditions
Answer:
C
SAP Supplier Relationship Management (SAP SRM) provides a two-step activation process for the implementation of new functions and the enhancement of existing functions.
This approach uses business functions and Customizing switches. You use business functions to display Customizing activities and Customizing switches.
Once the Customizing switches are visible, you use them to activate new fields or execute new code.
Activation of Business Functions
When you activate business functions, you activate Switch Framework switches (SFW switches).
SFW switches directly control whether new Customizing activities and Customizing switches are visible.
You can activate SAP SRM business functions in Customizing for SAP Supplier Relationship Management under SRM Server -> Activate Business Functions .
Deactivation of Business Functions
In SAP SRM, you can deactivate a business function if the following applies:
• The business function only activates Customizing switches and does not directly activate any code or fields.
• The Customizing switches corresponding to the business functions can be deactivated.
To deactivate a business function, the following steps need to be performed.
1. Check whether there are limitations at Customizing switch level. You can find this information in the business function description and in the documentation of the Customizing switch in Customizing for SAP Supplier Relationship Management.
If there are no limitations, deactivate the Customizing switch or switches in Customizing for SAP Supplier Relationship Management.
2. Run transaction Switch Framework Customizing (SFW5), select the business function, and deselect the Revertible checkbox. To do this, you need special authorizations.
3. Save and activate your changes.
Q 4. Which of the following is the sequence of events for the ‘Inbound Processing and Receipt Confirmation Without WM’ process? (Only one answer is correct)
A. Receive advanced shipping notification -> Create inbound delivery -> Post goods receipt -> Send proof of delivery -> Track and evaluate procurement process with SCEM
B. Receive advanced shipping notification -> Create inbound delivery -> Send proof of delivery -> Track and evaluate procurement process with SCEM
C. Create inbound delivery -> Post goods receipt -> Track and evaluate procurement process with SCEM
Answer:
A
You can use this business process for your inbound processing and receipt confirmation.
Whenever a company requires a product to be procured from an external source of supply, whether for use in production (raw materials) or for direct consumption (C-materials), the product will be delivered according to the official procurement document (a PO) agreed between two business partners.
The arrival of the goods could be announced by an advanced shipping notification (ASN) from the supplier. This states that the goods are to be delivered in a certain quantity at a defined date and time at a defined company location.
For the delivered product, an inbound delivery is selected and processed for putaway.
Once the goods are taken into stock, a goods receipt must be posted.
The actual physical receipt of materials at the warehouse or the receiving locations can be controlled in different levels of detail. For example, you can control the process only at a document level using purchase orders and stock transports orders for inbound deliveries and shipments, or you can go up to the pallet and material level.
The receiving process is supported in different ways depending on your needs. Optionally, you can use inbound deliveries, advanced material flow, and process control functions. These options include yard management, and warehouse management with task and resource management controlling the process down to pallet and package level using advanced strategies.
Inbound processing reflects the receipt of materials that are delivered to a receiving location. This receipt can be processed based on purchase orders, stock transport orders, or a returns order.
It includes the notification of goods to be received, the putaway, goods receipt posting, and the proof-of-delivery (POD) message to the supplier. By viewing the goods receipt from two perspectives, it is possible to follow the purchase order process and the physical material movements separately.
Q5. You can use the account assignment function in SAP Supplier Relationship Management (SAP SRM) for Purchase Order, Confirmations etc.
To carry out account assignment, you need to make the following settings:
A. Define the required account assignment categories in Customizing.
B. Define rules according to which the G/L account is to be determined automatically.
C. Optionally, define your own criteria for determining the G/L account using a Business Add-In.
D. Using multiple account assignment, You can distribute costs across accounts by percentage, by quantity, or by value.
Answer:
A, B, C, D
To carry out account assignment in SAP SRM, you need to make the following settings:
• You have defined the required account assignment categories in Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Account Assignment Define Account Assignment Categories.
• You have mapped the back-end account assignment categories to the account assignment categories in Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Account Assignment Define Account Assignment Categories.
• You have defined rules according to which the G/L account is determined automatically.
• You have defined that the criteria for determining the G/L account are based on the product category and the account assignment category (optional). You have made the settings for this in Customizing for SAP Supplier Relationship Management under SRM Server -> Cross- Application -> Basic Settings -> Account Assignment -> Define G/L Account for Product Category and Account Assignment Category.
• You have defined your own criteria for determining the G/L account (optional). You have made the settings for this in Customizing for SAP Supplier Relationship.
Using Multiple account assignment, You can distribute costs across accounts by percentage, by quantity, or by value.
When data is transferred to an SAP back-end system, the cost distribution by quantity and value is not always retained. Instead, the system changes the cost distribution type as follows:
o Cost distribution by quantity: Service items are converted to percentages.
o Cost distribution by value: Material and service items are converted to percentages.
• Flexible type of account assignment category
The account assignment category only defines the type of account assignment data that is entered in the generic fields for account assignment information.
The following account assignment categories are available:
o Asset
o Cost center
o Network
o Order
o Sales order
o WBS element
In the SAP back-end system the account assignment category is part of the item data, whereas in SAP SRM the account assignment category is managed at account level.
Q 6. You can calculate sales tax in SAP Supplier Relationship Management (SAP SRM). The tax is calculated when you create a shopping cart, enter a purchase order, or enter an invoice or a credit memo.
A. True
B. False
Answer:
A
You can use the tax calculation functions in the following applications:
• Create Shopping Cart
The system determines a tax indicator. You can change the default tax indicator. You can display the tax amounts per item and as total amount. You can define whether the tax amount is to be taken into account with approval using workflow.
• Process Purchase Order
You can change the default tax indicator. The system calculates the tax on the basis of the current data. You can display the tax amounts per item and as total amount.
• Enter Invoice
You can change the default tax indicator. Depending on the legal requirements, the system calculates the taxes either per item or as a total amount. In addition, you can enter the taxes manually for each tax code or as a total tax amount.
• Enter Credit Memo
You can change the default tax indicator. Depending on the legal requirements, the system calculates the taxes either per item or as a total amount. In addition, you can enter the taxes manually for each tax code or as a total tax amount.
• Evaluated Receipt Settlement
Tax is recalculated. You define the tax code in the purchase order.
Tax calculation can occur in the following systems:
• Back-end system: Tax calculation occurs in the financial accounting system
• External tax system
• Customer-specific implementation: Calculation occurs in SAP SRM
• SAP Transaction Tax Engine (TTE)
Q7. Pricing is a method of determining prices using the condition technique. SAP SRM uses Pricing when purchase documents are created. The system automatically determines the gross price and any surcharges and discounts that apply to a specific supplier according to defined conditions.
Which of the following are essential elements of the condition technique?
A. Condition Type
B. Condition Variant
C. Access Sequence
D. Calculation Schema
E. Procedure group
Answer:
A, C, D
Pricing consists of the following elements:
• Condition Type
A condition type serves to differentiate between prices in the system. You can define a separate condition type for each type of price, surcharge or discount that may arise in your business transactions. The condition type defines, for example, a discount as a fixed amount or as a percentage.
For example, you can apply release-based rebates that depend on former spend or volume, based on historical spend and not on a single purchase order. Therefore, you can assign a condition where the discounts are based on aggregated release value of the referenced contract or contract hierarchy (if the contract is part of a hierarchy) has been introduced.
You can also define group conditions with which scales are used in several items of a purchase order.
• Calculation Schema
The calculation schema describes a sequence of condition types that are used to determine prices. In SAP SRM, the calculation schema 0100 is defined as default. You can modify this and add your own condition types.
• Access Sequence
An access sequence is a search strategy with which the system looks for valid data for a specific condition type. You can define an access sequence for each condition type. In SAP SRM, the access sequences are predefined.
• Condition Table
A condition table contains price information on a master data type, for example, on a product master. If you define a product price or a special discount, for example, you create condition records in the relevant condition table.
Q8. SRM Users can use a supplier list to search for sources of supply for their purchases. This supplier list is compiled by the purchaser for specific products or product categories and contains suppliers and back-end contracts.
In order to integrate the supplier list into the Shop & Sourcing applications, which of the following activities are relevant?
A. Define number range for the supplier list
B. For the Shop application, specify if the supplier list needs to be used in isolation or in addition to the original source of supply list.
C. Use a Business Add-In to define detailed criteria.
D. Supplier lists can be created for products, product categories or product set-types.
Answer:
A, B, C
The number range for the supplier list has been defined.
This need to be done in Customizing for SAP Supplier Relationship Management under SRM Server -> Cross-Application -> Basic Settings ->Number Ranges ->SRM Server Number Ranges -> Define Number Ranges for Supplier List.
Carry out the following settings in Customizing:
• For the Shop application, you can specify that only the supplier list is to be used, or that the entries from the supplier list are displayed in an additional column in the original source of supply list.
• You can use a Business Add-In (BAdI) to define detailed criteria to display the supplier list.
• Supplier lists can be created for products or for product categories (and NOT for Product set-types). Product supplier lists take precedence over product category supplier lists
Possible sources of supply in the supplier list are:
• Suppliers
• Back-end contracts
You can do the following:
o Assign suppliers that belong to the purchasing organization selected on header level.
o Deactivate individual suppliers or back-end contracts within a supplier list. These are then no longer shown in the applications.
o Search for contracts directly in the back-end system using the input help, and subsequently transfer them.
Q9. In order to distribute the workload of purchasers, SRM offers the so called automatic assignment. In this context, which of the following are true?
A. Automatic assignment can be done for External requirements, Purchase Orders or Contracts.
B. The BADI BBP_PFRP_ASSIGN_BADI is used to define rules.
C. Documents can be assigned to purchasing groups that are themselves assigned to different purchasing organizations
D. One purchase requisition can have multiple lines, each of which is assigned to a different purchasing group.
Answer:
A, B, D
Automatic assignment of a purchasing group or purchasing organization can be carried out for the following documents:
• External requirements
• Purchase orders
• Contracts
• RFx
Assigned documents automatically appear for processing in the worklists of the purchasers that belong to the purchasing group or organization. The documents are automatically assigned to the purchasing group according to given criteria. This speeds up the entire procurement process, since documents do not have to be assigned manually in order for the purchasers responsible to process them.
It is also possible to reassign documents that have already been assigned to a purchasing group or organization — if the purchaser responsible for the group or organization is absent, for example.
You need to have implemented and activated the Business Add-In (BAdI) BBP_PGRP_ASSIGN_BADI.
Here the rules covering the assignment of purchasing groups to documents are defined. This BAdI contains a method for each type of document to be assigned:
• BBP_SC_PGRP_ASSIGN for external requirements
• BBP_PO_PGRP_ASSIGN for purchase orders
• BBP_CT_PGRP_ASSIGN for contracts
• BBP_BI_PGRP_ASSIGN for RFx
If you do not define any rules, the system distributes the documents to a standard purchasing group or organization, as defined in your organizational plan.
You can reassign these documents manually or redefine assignment rules in the above- mentioned BAdI and rerun the automatic workload distribution. To do this, you set the filter value ONLINE in the BAdI BBP_PGRP_ASSIGN_BADI.
Process Flow
The workload distribution process is outlined below. The two diagrams show the process for requirements. Details of each diagram are described underneath each diagram.
Caution
Documents cannot be assigned to purchasing groups that are themselves assigned to different purchasing organizations. Besides, purchasing groups and organizations must reference the same logical system in the back-end.
Workload Distribution for Requirements
Part A
1. A purchasing requisition is sent to SAP SRM, where it is converted into an external requirement.
2. Upon creation of the external requirements, method BBP_SC_PGRP_ASSIGN of the BAdI BBP_PGRP_ASSIGN_BADI applies the distribution rules.
3. If the requirement conforms to the rules, it is automatically assigned to the correct purchasing group (in this example, purchasing group 01).
4. If no assignment rules are maintained in the BAdI, the standard purchasing group (as defined in the organizational plan — in this example, 99) is assigned. The standard purchasing group is also assigned to the shopping carts that are created in SAP Supplier Relationship Management. In this case, you can proceed as follows:
o Assign a purchasing document manually
o Define the assignment rules and have the system automatically reassign a purchasing group.
If you do not redistribute the workload, the requirement retains the standard purchasing group.
Note
One purchase requisition can have multiple lines, each of which is assigned to a different purchasing group.
Q10. SAP SRM provides predefined technical events for business objects. Events can be triggered by any of the following:
A. Business changes made in the system
B. The results of report runs
C. Key Performance Indicators
D. Passed deadlines
Answer:
A, B, C, D
Event schemas are used to control the effects of the events that belong to the business objects. They can be used to define the deadline for triggering a reaction to the event. Event categories are used to define the nature of this reaction.
The system determines the recipient for event category Alert using alert category; it sends one of the following:
• An alert, using alert category.
• A message, using SAP Smart Form.
• A work item, using workflow.
Note that an event always occurs at a predefined time. However, you can trigger an alert or message before or after this time by specifying a negative or positive value. If you enter no deadline, the system assumes that the value is zero and the alert is triggered at the moment of the event.
More Questions? Have a look at:
SAP SRM 7.0; Associate Certification Exam Questions with Answers & Explanations