Ans: 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 paper work and unwanted confusions. It is very effective for the companies which have 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.
Ans: 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.
Contract compliance - provides visibility into enterprise expenditures and enables the procurement organization to effectively demonstrate according to corporate guidelines.
Competitive advantage - gives the tools to partner with key suppliers, define supplier management approach, and determine the key metrics.
Ans: 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
Ans: 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 arise when purchasing document.
Ans: Before the Internet Transaction Server (ITS) can process EBP requests, entries in 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 the EBP client the configuration is performed in and it also consists of base address for the integrated ITS instance. To enable EBP purchasing for each client, this configuration needs to be performed once.
Ans: Organizational attributes serve many purposes in 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.
Ans: 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 organizational unit does not exist'.
Ans: An internal number range must be defined to build numerically local bid invitation for RFQ`s and Auction in the Bidding Engine and Live Auction application. These bids does not have a link to any R/3 purchasing document, they are completely local to the ERP system.
Ans: 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.
Ans: Generally in SRM business, partner means the entire stake Holders. Example: suppliers, customers, vendors, employee, etc. The function of partner is to make the vendors as reference, and then there will be invoicing party, supplying party, etc.
Business partner means those who supply the raw material to the customer i.e. buyer.
Ans: 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 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.
Ans: 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.
Ans: The key business process in SAP SRM includes:
Ans: 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.
Ans: You can replicate Purch Org,purch group, material master, vendor master from backend. you can create PO in SRM and replicate Po in the R/3. All the procurement done in SRM related to MM only.
Ans: If Stake reference of SRM then, In SRM all the stake holders are partners. eg vendor, employees etc.
Ans: SRM means supplier relationship management. Just as a robust company puts in an effort to develop customer relationships, the company should strengthen its procurement processes by automation and efficiency. SRM can examine and forecast the company's purchasing pattern, work with vendors in real time, and shorten procurement cycles.
Ans: SRM handles analytics, supplier collaboration, operational contracts, service purchasing, self-service procurement, catalog content, supplier qualification, strategic sourcing, and plan-driven procurement.
Ans: Supplier self-services (SUS) service agent
The SUS order processor
The SUS invoicing party
The SUS administrator supplier
The one-client invoice verification clerk
The survey reviewer
The strategic purchaser
The component planner
The employee and the invoice verification clerk.
This is about one third of the sub modules in SRM.
Ans: SRM can be used two ways. First, employees can purchase materials and services they need to complete the company's goals. This process is simplified by a Web-based GUI that simultaneously filters by corporate spending and purchasing compliance. The second way is by an automated system which procures materials as part of a company's supply-chain workflow.
Ans: No, you can re-use mappings by exporting the mapping file and uploading it back for re-use. The next time you want to use it, use the QA System Import Manager, open the import file involved, and select the mapping file from Catalog Items Import Map.
Ans: SRM has many tables. Among them, the product table, product category table, Web survey questionnaire, business address services, communication usages, account assignment, PO item confirmation, business transaction item purchasing, value limits, tax, tolerances, transactions, partners, links, chopping cart, invoice and credit memo, and SRM confirmations.
Ans: 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.<br>
Ans: 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 arise when purchasing document.
Ans: Before the Internet Transaction Server (ITS) can process EBP requests, entries in 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 the EBP client the configuration is performed in and it also consists of base address for the integrated ITS instance. To enable EBP purchasing for each client, this configuration needs to be performed once.
Ans: An update request can be divided into one primary (Vi) and several Secondary update components (V2). Time-critical operations are placed in Vi component and those whose timing is less critical are placed in V2 components. If a Vi update fails, V2 components will not be processed.
Details about SAP SRM