This section will be removed upon quality check by the topic expert/administrator before the document is moved to its target space.

Purpose

To provide a detailed explanation on how the different SSP Employee - Self - Service scenarios are working.

Overview

There are 3 scenarios that can be configured for the employees, based on the target system.  

1. Local scenario 
2. Central Procurement Local Scenario
3. Central Procurement Scenario - Connected System
4. Central Procurement Scenario - Ariba Integration (3EN)

It must be emphasized that flexible workflow is required for all scenarios and for each scenario SAP ships different workflow templates.
The customizing is done by a purchasing expert in the Fiori application Default Settings for Users F1995. 
The Employee user needs to be configured in the system as an Employee by the HR Team (PA30)
The Expert with role SAP_BR_BPC_EXPERT can configure which scenario is used for each employee, by selecting a plant/company code combination. 

The Local scenario

1. This scenario requires the least amount of configuration, as an S4 core system with customized purchasing can implement this.
2. The expert assigns a default plant and company code to the employee.
3. Then this employee can create purchase requisitions in the local system. 
4. From such purchase requisitions local contracts or RFQs can be created.
5. If the purchase requisition has a supplier than a purchase order can be created.
6.  This Purchase Order can be confirmed with the Fiori application Confirm Receipt of Goods New F4489. 

The Central Procurement- Local Scenario

In a central system the same system under the same client can be configured as a connected system. 
So for example central system is AAA-001, than AAA-001 can be assigned as a connected system. 

In this case the underlying coding is a bit different and the used workflow templates will also be different, as the logic will use the central purchase requisition workflow templates. 
 
The created purchase requisition can be seen in the central fiori applications. 
Nevertheless, the document and follow-on documents will only be created in the local central system. 

To use this scenario the expert user must assign a plant/company code pair to the employee in the Fiori application Default Settings for Users F1995.
In addition, the system must be a working central purchasing system. 

The Central Procurement Scenario - Connected System

This scenario is the most complicated as it requires customizing in both central and connected system. 
In central and connected system the SOA/XML service and Odata Services must be configured. 

The expert must assign a company code/plant pair to the employee which will determine the targeted connected system. 

How this transfer was implemented by SAP is documented under the following SAP Wiki:  SSP Purchase Requisition for Central Procurement

1. First a local Purchase Requisition is created and it is sent to approval.
2. If the approval is successful, the workflow user sends out the XML to the connected system. 
3. In the connected system a new purchase requisition is created as detailed in the following Wiki: Debugging and behavior guide to the SOA service PurchaseRequisitionReplicationRequest_In
4. This requisition in the connected system can be used to create RFQ, contract or purchase order. 
5. For all updates a response XML is sent by the connected to the central system.
6. If a Purchase Order is created than an XML is sent by the connected system to the central system. 

For the PR/PO pair to be shown in the Fiori application Confirm Receipt of Goods New F4489, the workflow and XML processing must run without error.     

If a such a Purchase Order is confirmed in the central system with the F4489 application, a confirmation XML is sent from the central system to the connected, to update the Purchase Order. 

The Central Procurement Scenario - Ariba Integration (3EN)

This scenario is not so special, as it uses the customizing of the previous scenario. 
The Ariba system can simply send an Odata REST API call API_PURCHASEREQ_PROCESS_SRV and fill the Requisitioner ID of the Employee user. 

The Ariba system can also send an XML with the same data to the central system with the PurchaseRequisitionReplicationRequest_In.

If this Employee user has customizing with company code/plant pair which targets a connected system, then the central logic will create the local PR and sends it further to the connected.

Related Content 

Related Documents 

SSP Purchase Requisition for Central Procurement

Guided Buying for Central Procurement with SAP Ariba Buying (3EN)

Debugging and behavior guide to the SOA service PurchaseRequisitionReplicationRequest_In

Related SAP Notes/KBAs