Customers who want to move all procurement activity for selected categories to the SAP SRM system.Customers who do not have an operational and/or productive backend system for materials management and have only financial accounting systems.This is applicable for the following customer types: Account assignments are checked locally with accounting data defined in SAP SRM. Only final invoice data is sent to the backend accounting system. In a standalone scenario, all procurement processes are executed in SAP SRM, and shopping carts and other procurement documents are processed in SAP SRM. Depending on the system that you want to be the main purchasing application, there are four scenarios of integration with backend ERP applications. SAP SRM is seamlessly integrated with the SAP ERP application and can be integrated with other non- SAP backend ERP applications as well. It provides an integrated enterprise procurement platform that enables integration of procurement with design, planning, inventory, and financial applications. SAP SRM provides four deployment scenarios, including the classic, extended classic, standalone, and decoupled scenario, and companies can decide on the level of integration with backend planning and accounting systems by implementing the appropriate deployment scenario. SAP SRM enables organizations to efficiently source and procure all categories of products, that is, direct materials, indirect materials, and services, and can be integrated with any backend planning, inventory, and accounting systems. However, based on the system availability and generation of various documents, SRM have four different types of deployment scenarios. Below diagram (Figure 1) depicts the entire SAP SRM lifecycle structure. Once the invoice is created, the buyer will process the payment. Goods receipt will be verified and an invoice will be created. Once the PO is created, the goods are supplied at the ship-to address and goods recieipt will be given. This will also give rise to a Purchase Order along with a unique number. Once the shopping cart is approved, a purchase requisition number will be generated and this will lead to generation of various process purchasing documents. Once a shopping cart is created, a corresponding Shopping Cart number is generated. This starts with creation of Shopping Cart. The following lifecycle is followed in SRM. Three types of multilevel hierarchy structures are used in SAP SRM master data The efficient processes in SAP SRM enable you to cut down your procurement expenses and to work more intensively with more suppliers than ever before. So it helps for building long-term relationships with the suppliers. SAP SRM will examine and forecast purchasing behavior, it also shorten the procurement cycles, and work with your partners in real time.
It introduced many facilities for better co-ordination between the suppliers and business activities. It is for strengthening the procurement processes of an organization by automating, accelerating of procure-to-pay processes for goods and services. It is based on the SAP NetWeaver platform hence it also known as SAP NetWeaver SRM. It is one of the parts of SAP Business Suite Software. SRM in SAP stands for Supplier Relationship Management. SAP Supplier Relationship Management (SAP SRM) :
0 kommentar(er)
