High- Level Specification
| Parameter | Value |
|---|---|
| Application System (Source) | Ariba Guided Sourcing |
| Application System ( Target) | Keelvar |
| Business Process Reference | 03.03.03.01. Manage Sourcing Projects |
Functional Overview
Ariba Guided Sourcing is interfaced with SAP ECC system (PRS) to sync Supplier Master Data. Bidders and Supplier Contacts Master Data is maintained in Ariba Guided Sourcing directly. The Supplier Master Data (including Bidders) along with Supplier Contact information is interfaced with Keelvar as well to allow the Sourcing Specialists the flexibility to invite participants to Keelvar Event. Ariba Supplier ID (System ID) is maintained as External ID in Keelvar ensuring the sync between the two systems. Whenever a supplier or Bidder is deactivated in Ariba Guided Sourcing, the supplier is also archived in Keelvar.
Scope and Objectives
The scope of this Functional Specification is to describe the interface between Ariba and Keelvar for synchronizing Supplier Master Data. Whenever a supplier/bidder is created in Ariba Guided Sourcing, the supplier will be pushed to Keelvar using Keelvar Supplier Management API. Similarly, whenever, a supplier/bidder is deactivated in Ariba, the Keelvar supplier record will be archived. Ariba Master Data API for Sourcing will be used to extract the data from Ariba Guided Sourcing
Process Flow Diagram
Step | Description | Comment |
|---|---|---|
1 | Supplier is created or deactivated in Ariba Guided Sourcing based on SAP ECC details using an Integration Event. Alternatively, a Bidder is created/deactivated in Ariba Guided Sourcing by Sourcing Specialist. | |
2 | A Scheduled Task picks up the list of all Suppliers modified since the last run | |
3 | SCPI extracts the delta vendor load using Ariba Master Data API for Sourcing and creates a payload for Keelvar Supplier Management API | |
4 | SCPI pushes the payload to Keelvar | |
5 | Keelvar creates new supplier records or updates the existing Supplier records or deactivates the supplier records based on the vendor active flag in Ariba Guided Sourcing |
Assumptions
Dependencies
Security, Integrity and Controls
Configuration Requirements
Special Requirements
Design Rationale
Data Structure
Source Structure
The following fields will be used to provide the required information for this interface:
| Field | Description |
|---|---|
Target Structure
The following fields will be used to provide the required information for this interface:
| Field | Description |
|---|---|
Mapping and Calculation
| Source Table | API or Portlet Name | Source Field | Required (Y/N) | Description | Target Field | API or Portlet Name | Target Field | Required (Y/N) | Description | Rule Type | Rule Instruction |
|---|---|---|---|---|---|---|---|---|---|---|---|
Processing Logic
Processing within Source
Processing within Middleware
Processing within Target
Interface Dependency
Interface Constraints
Delivery Requirements
Delta or Full Load Requirements
Interface Alert & Monitoring
Interface Reporting
Language Requirements
User Interface Requirements
Volumetrics
Performance Consideration
Error Handling
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Results |
|---|---|---|
Test Considerations/Dependencies
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|