If you're looking for SAP SRM Interview Questions & Answers for Experienced & Freshers, you are in right place. There are a lot of opportunities from many reputed companies in the world. According to research SAP SRM has a market share of about 29.0%.
So, You still have the opportunity to move ahead in your career in SAP SRM. Mindmajix offers advanced SAP SRM Interview Questions 2021 that helps you in cracking your interview & acquire a dream career as SAP SRM Developer.
1. Master data such as products, business partners, etc, is available locally in the SRM system_
2. In SRM, both materials and services are stored as products. These are differentiated by ‘Product Types’
3. Product categories correspond to material hierarchies in the SAP back-end system.
4. 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.
Ans: 1, 2
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 10 with more than 18 characters, a different number (with a maximum of 18 characters) has to be assigned in the back-end system.
|Check Out SAP SRM Tutorials|
1. Supplier Hierarchies
2. Price Hierarchies
3. Base Hierarchies
4. Central Contract Hierarchies
Ans: 1, 4
The following multilevel hierarchies come as part of standard delivery:
1. Product category hierarchies
2. Supplier hierarchies
3. Central contract hierarchies
Product category hierarchies provide the following:
1. Extended search of product categories
2. Import of product category hierarchies into the SAP SRM system, for example:
3. Back-end material categories from SAP ERP
4. Standard product category hierarchies (such as UNSPC, eClass)
5. 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.
1. SAP Supplier Relationship Management (SAP SRM) provides a Single-step activation process.
2. Business functions arc activated using the BLW switches
3. Business function once activated can be deactivated under certain conditions
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:
1.The business function only activates Customizing switches and does not directly activate any code or fields.
2. The Customizing switches corresponding to the business functions can be deactivated.
To deactivate a business function, perform 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 (SFWS), select the business function, and deselect the Revertible checkbox. To do this, you need special authorizations.
3. Save and activate your changes.
1. Receive advanced shipping notification .> Create inbound delivery -> Post goods receipt .> Send proof of delivery .> Track and evaluate procurement process with SCEM
2. Receive advanced shipping notification -> Create inbound delivery -> Send proof of delivery -> Track and evaluate procurement process with SCEM
3. Create inbound delivery -> Post goods receipt -> Track and evaluate procurement process with SCEM
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 P0) agreed between two business partners.
The arrival of the goods could be announced by an advanced shipping notification (MN) 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 put away.
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.
SRM stands for Supplier Relationship Management. It is an extended form of ERP where data gets transferred between SAP R/3 and the SRM screen (vice versa) so that every Vendor’s coordination will be better and which will fully avoid the paperwork and unwanted confusion.
It is very effective for the companies which have a large number of users who can directly purchase the material using the Shopping Cart in which the materials can be selected from the available Catalogs.
1. SAP SRM enables the organization to achieve the following business benefits: Sustainable cost savings- which enables the companies to achieve a closed-loop from source-to-pay.
2. Contract compliance – provides visibility into enterprise expenditures and enables the procurement organization to effectively demonstrate according to corporate guidelines.
3. Competitive advantage – gives the tools to partner with key suppliers, define supplier management approach, and determine the key metrics.
Entries should be created in the EBP system to link the EBP purchase orders, requisition, and reservation to the backend R/3 system. The logical system ID should reflect that of the EBP application server and client in which the number ranges are being configured. PO, RQ, RS were used to easily distinguish each number range.
Number ranges must be established for EBP shopping carts as well as any potential purchasing document so that unique numbers can be generated in the backend R/3 system from EBP.
The EBP system needs a number range established that automatically takes the next available number and assigns it to the document which will be created in R/3.configuration must also be established in R/3 to correlate with the ranges in EBP so that conflict never arises when purchasing document.
Before the Internet Transaction Server (ITS) can process EBP requests, entries in the table must be maintained to initiate a connection to a physical URL, which controls the menu on the left-hand side of the screen that shows all of the transactions users have access to.
The URL varies depending on which EBP client the configuration is performed in and it also consists of the base address for the integrated ITS instance. To enable EBP purchasing for each client, this configuration needs to be performed once.
Organizational attributes serve many purposes in the EBP system. The primary purpose is to set attributes that define the users` shopping experience. Examples of such attributes are company code, plant and cost centers that the user can order against, etc.
A user or supplier record cannot be assigned to an organizational unit it has a business partner recorded. This means, if Business Partner relationships are not established, users cannot be imported into the organizational structure from the User_Gen Transaction. Then the following error occurs: ‘Business partner of the organizational unit does not exist’.
An internal number range must be defined to build numerically local bid invitations for RFQ`s and Auction in the Bidding Engine and Live Auction application. These bids do not have a link to any R/3 purchasing document, they are completely local to the ERP system.
We use transaction SMQ1 in this case. The first thing that should be checked when downloading customizing objects is a possible stuck queue. The R/3 system uses the outbound queue (SMQ1) which is less likely to get stuck initially.
1. Generally in SRM business, partner means the entire stake Holders. Example: suppliers, customers, vendors, employees, etc. The function of the partner is to make the vendors as references, and then there will be invoicing party, supplying party, etc.
2. Business partner means those who supply the raw material to the customer i.e. buyer.
Supply management deals with the oversight and management of materials and services inputs, management of the suppliers, which provides vital inputs. The performance of supply management departments and professionals is measured in terms of the amount of money saved for the organization.
However, managing risk is one of the aspects of supply management; especially the risk of non-availability of quality goods and services important for an organization’s survival and growth.
The supply management function of an organization is responsible for various aspects such as managing supplier performance, implementing technologies, processes, policies, and procedures to support the purchasing process. Also, provide supplier relationship management process for providing the structure for how relationships with suppliers will be developed and maintained.
The key business process in SAP SRM includes:
1. Procure to pay- we can integrate catalog-based requisition and gain the benefits of e-procurement.
2. Catalogue management- manages catalog data as master data that is deeply integrated.
3. Centralize sourcing- gain visibility into the demand for goods and services.
4. Centralized contract management- consolidates contract information.
5. Supplier collaboration- links suppliers to our purchasing processes through the supplier portal.
A Purchasing Organization is the organizational unit within a business responsible for the procurement of goods and services for plants belonging to a particular region. It also negotiates terms and conditions of contracts and purchases from vendors and also assumes legal responsibility for those purchases for the Plants that PO is responsible for. Those Plants are dependant on its assignment.
You can replicate Purch Org,purch group, material master, vendor master from the backend. you can create PO in SRM and replicate Po in the R/3. All the procurement is done in SRM related to MM only.
Ans: If Stake reference of SRM then, In SRM all the stakeholders are partners. eg vendor, employees, etc.
The reason is to save time and reduce dependency on purchasing department that usually focuses on core purchasing tasks.
For example in the classic scenario, a purchase order is generated in ECC. For any changes to PO, we need to contact purchasing department.
So still we have a dependency. But in ECS, we can edit the PO in the SRM system itself and changes will be replicated to ECC. So we need not contact purchasing team and the burden on purchasing team for such requests will totally be eliminated. So for low spend purchases, we need to depend on purchasing department at all
In SRM depending on the type of business, there are different procurement processes, Some of them are listed below
1. Self-Service Procurement
2. Plan-Driven Procurement
3. Service Procurement
4. Strategic Sourcing
5. Operational Contract Management
6. Supplier Qualification
7. Catalog Content Management
You can do the changes in vendor master in R/3 and then replicate the vendor changes to the SRM system using transaction BBUPDVD(update vendor).
|Explore SAP SRM Sample Resumes! Download & Edit, Get Noticed by Top Employers!|
I am Ruchitha, working as a content writer for MindMajix technologies. My writings focus on the latest technical software, tutorials, and innovations. I am also into research about AI and Neuromarketing. I am a media post-graduate from BCU – Birmingham, UK. Before, my writings focused on business articles on digital marketing and social media. You can connect with me on LinkedIn.