Skip to end of metadata
Go to start of metadata

The External Requirement Processing ES bundle removes paper from the purchase request process by creating a link between third-party procurement systems and SAP SRM. This allows employees to submit purchase requests for supplies or services electronically.

Until now, employees had to submit purchase requests to purchasing departments by paper, email, or fax. This process is slow and error-prone since purchasing department employees have to manually enter the information into SAP SRM.

The External Requirement Processing ES bundle allows an employee to create a purchase request for a supply or service in a third-party procurement system such as Quintiq. Once the purchase request is saved, the enterprise services automatically deliver the information to SAP SRM, where a purchasing department employee can begin the procurement process for the supplies or service. The first employee receives notice that the purchase request has been delivered.

External Requirement Processing leverages enterprise SOA by connecting all kinds of third-party ERP systems with SAP Materials Management, SAP Plant Maintenance, and SAP Project System using enterprise services and SAP NetWeaver Process Integration (formerly XI).


Any small or large company that requires goods and services would benefit from the External Requirement Processing ES bundle. People who create purchase requests will use the services in this bundle as well as people who receive and fill purchase requests.

External Requirement Processing (click to enlarge)

For details on Service Operations, Business Objects and Process Components, please check the ES Workplace.

How to Use This ES Bundle

Within many organizations, purchase requests are completed in the good, old-fashioned way: scribbles on paper, or maybe faxed. Even when some systems are computer based, often times a department can't connect with purchasing because the systems are incompatible. This can lead to many inefficiencies - hard-to-track or lost orders, a cumbersome means of follow-up, and no centralized system for procuring, documenting, and monitoring purchase requests.

The External Requirement Processing ES bundle offers procurement-related services that facilitate all kinds of SAP SRM connectivity, allowing users to maintain and confirm purchase requests and enabling easy, flexible requisitions.

The functionality of the External Requirement Processing ES bundle is simple: the end user places a purchase request in any number of external procurement systems. The enterprise services then send it to SAP SRM, where the purchasing department can begin processing the order.

Use Case 1: An Employee Requisition Request

Dr. Moreno at Big City Hospital notices that the penicillin supply in the Pediatric Department is running low. This use case explains how the doctor could create a purchase request for the penicillin in a third-party procurement system and then send it to SAP SRM in the purchasing department for processing. This use case assumes the hospital has already established a connection between the third-party procurement system and SAP SRM.

Dr. Moreno would log onto the Pediatric Department's third-party procurement system and he would create a purchase request, which includes the brand of penicillin, the quantity and the date when he needs it. When he saves the purchase request, it triggers the enterprise service Maintain Purchase Request, which sends the Purchase Request (SRM) that the doctor created to the purchasing department's SRM system via SAP NetWeaver Process Integration (formerly XI).

When SAP SRM receives the Purchase Request (SRM), the system uses the Confirm Purchase Request to send confirmation back to Dr. Moreno telling him that the purchasing department has received the request. The purchasing department then begins processing the order for penicillin.

Future Directions

In the future, the External Requirement Processing ES bundle may provide greater functionality to the employee requisitioning supplies as described in Use Case 1. Instead of manually listing the product type, delivery date, and quantity, the employee will eventually be able to select information from a drop-down menu and the form will be populated with default data such as an account number and supplier address. This will help avoid mistakes during the requisitioning process. SAP is also working on an enhancement that will notify the employee of the status of the requisition (for example, whether the requisition has been processed, when the supplies will be delivered, and so on).


External Requirement Processing leverages SAP Materials Management, SAP Plant Maintenance, and SAP Project System as well as ERP solutions from third parties as well as SAP NetWeaver Process Integration (formerly XI).

System Requirements

Related ES Bundles

End-to-end Processes Where This ES Bundle Is Used