You can evaluate your company’s suppliers to obtain a basis for your business relationship with them and to optimize your supply base. Based on the feedback you gather through questionnaires, you obtain a scorecard for each supplier evaluated. The scorecard helps you to assess a supplier’s strengths and shortcomings and to initiate measures for improvement. Evaluation scorecards also enable you to easily compare suppliers within a peer group.
Ultimately, a combined real-time view across operational and questionnaire-based scores provides a holistic view of your supplier’s performance.
Story Flow Summary
- Category Manager Checks the Overall Supplier Evaluation KPI for VF Vendor using "Overall Supplier Evaluation" app and observes that the score for Questionnaire Evaluation for the current period is not there.
- Category Manager uses "Manage Activities" app to creates an activity and a task for buyer to get supplier evaluation done
- Buyer checks the open tasks in "Process Tasks" app and sees that supplier evaluation for VF Vendor is required to be triggered.
- Buyer uses "Manage Templates" app to selects the Template, clicks on 'Start Group-based Evaluation, inputs the necessary details like evaluation period, response deadline etc and submits the evaluation request
- The Appraiser sees the Evaluation request email, opens the app, evaluates the supplier and submits the response.
- Buyer checks the responses and updates the task of triggering the evaluation as 'complete'
- Using "Monitor Tasks" app, Category Manager checks the status of the tasks and finds that the evaluation is completed
- Category Manager checks the Overall Supplier Evaluation KPI for the supplier
This blog is in continuation to my previous blog on S/4HANA Cloud connection with SAP Data Intelligence. You can refer the following blog for more details:
This blog will focus on S/4HANA Cloud Operational Data Service entry sheet (SES) from service procurement. The creation of the SES in the S/4HANA cloud and replicating the same into HANA DB by SAP Data intelligence Pipeline can be accomplished with three main tasks.
- Setting for S/4HANA Cloud System
- Creation of table with required structure of Service entry sheet into HANA Database
- Setting in the SAP Data Intelligence Cluster
Setting for S/4HANA Cloud System
You can follow the sequence of steps to set up the connection of S/4HANA Cloud system.
1. Logon to the S/4HANA Cloud system with the appropriate credentials:
2. On successful logon to the S/4HANA Cloud system, go to group “Communication Management”.
3. Click the app Display Communication Scenarios.
4. Search for communication scenarios specific to service entry sheet and note down the Scenario ID SAP_COM_0146 for Service Entry Sheet Integration.
5. Go back and open the app Communication arrangements.
6. Click on New to create a new communication arrangement
A popup for selecting the communication scenario appears. Search and select the required communication scenario.
7. Search and select the communication scenarios SAP_COM_0146 as shown.
8. After you select the communication scenario SAP_COM_0146, then add the new arrangement name and click Create.
9. The Communication system and user name are automatically filled in the service entry sheet.
1 Exposed OData URL will look like below
11. Below is the metadata
12. Below OData URL is an example to get service entry sheet
Create Connection of HANA DB to SAP DI Connection Management
This involves the followings tasks:
- Setting up the connection in connection management in SAP Data Intelligence
- View connection details in the metadata explorer
You can follow the steps provided below for setting up the SAP Data Intelligence cluster.
1. Specify the SAP Data Intelligence cluster URL in the browser, then enter the tenant name assigned to you and click Proceed.
2. Enter user name and password in the next screen, then click Sign In.
The SAP Data Intelligence Launchpad/cluster appears as shown.
3. Click the application “Connection Management” to set up S/4HANA Cloud connection with SAP Data Intelligence.
The SAP Data Intelligence Connection Management screen appears, where the connection types are displayed.
4. Click the Connections Tab.
5. Click CREATE to create a new connection.
6. You can enter all the required details for the new connection.
7. Go to HANA DB Database explorer in a separate tab and create a table like the service entry sheet structure.
8. Go to SAP DI Launchpad and launch metadata explorer to view the created table in the HANA DB connection
9. Click browse connections in the metadata explorer.
10. Select created HANA DB connection in the metadata explorer and view the created table for the HANA DB connection
11. Click the application “Modeler” to create Pipeline.
12. Click on the + button to create Graph in modeler
A blank Pipeline will be created as below.
13. Click Save to save pipeline and provide the necessary information
14. After adding the required information, click OK .
15. Add operator as shown and follow the steps.
16. Click Open configuration
17. Add OData URL and users as below.
Again, click open configuration as below.
18. Add HANA DB connection
Below details will be displayed for the configuration.
19. Select the tables created for Service entry sheet into HANA DB
Fill below details as provided in the screen shot
Map the required source and target fields.
Run or schedule the Pipeline
Below you can see the status and log table to track the progress
Below screen shot contains the service sheet entry in the app - Manage Service Entry Sheets.
Below is the table ZSES created under PKUMAR schema into the HANA DB available on AWS. As we can see the SES entry is 13.
Create a new service sheet entry with reference to the PO 4500000105 with adding additional details
Click Save to create new Service entry Sheet
Below screen shown displays the newly created service sheet entry data.
After service sheet entry is created then scheduled SAP DI pipeline will get additional created data and push to HANA DB as maintained into pipeline. Below two screen shot is the SAP DI Pipelines created for the same.
There is pipeline scheduled at every minute so service entry sheet 14 will get updated into the HANA DB. But in general use case, there need to be an event processing mechanism to push the newly created Service entry sheet.