| Status | |
|---|---|
| Owner | |
| Stakeholders | RAI-ext, Praveen BAVISKAR-ext, Amit |
| Jira Request ID | |
| Jira Development ID |
High-Level Specification
| Parameter | Value |
|---|---|
| Application System (Source) | Ariba |
| Application System (Target) | Icertis |
| Source System Interface | Ariba |
| Target System Interface | Icertis |
| Business Process Reference | ?? |
Functional Overview
To ensure consistent and automated management of supplier records across systems, a custom integration and job scheduling solution will be implemented. This solution will:
- Automate the synchronization of supplier status data between Ariba and Icertis.
- Ensure alignment of supplier deactivation in Icertis with the current status maintained in Ariba.
- Reduce manual intervention and the risk of data discrepancies between the two platforms.
- Support compliance and operational efficiency by maintaining accurate and up-to-date supplier information across systems.
Scope and Objectives
- Custom Time-Based Job in Icertis
A configurable, daily-scheduled job will be developed in Icertis to trigger the supplier deactivation synchronization process, with flexibility to adjust execution frequency and timing. - Supplier Status Check in Ariba
The job will connect to Ariba via API to retrieve supplier records, identify those marked as inactive, and process delta updates accordingly for synchronization. - Supplier Deactivation in Icertis
Inactive suppliers identified from Ariba will be deactivated in Icertis using the Business Bulk API, ensuring data consistency, integrity, and audit traceability.
Objectives
- Automate the synchronization of supplier deactivation status between Ariba and Icertis.
- Ensure daily alignment of inactive supplier records using a configurable time-based job in Icertis.
- Retrieve and process only newly deactivated suppliers from Ariba via API to optimize performance.
- Maintain data integrity and audit traceability during supplier deactivation in Icertis.
Process Flow Diagram
Step | Description | Comment |
|---|---|---|
1 | Schedule Job in Icertis | A configurable daily job triggers the synchronization process (delta update) |
2 | Connect to Ariba via API | The job establishes a connection to Ariba |
3 | Retrieve Supplier Records | Fetches supplier data from Ariba |
4 | Check supplier Active Flag | Evaluates which suppliers are inactive |
5 | Identify Inactive Suppliers | Filters suppliers marked as inactive |
6 | Deactivate suppliers in Icertis via Business Bulk API | Uses Business bulk API to update the status |
7 | Ensure data integrity | Mark identified suppliers as Deactivated (Deprovisioned) in Icertis |
Assumptions
- Supplier status (Active/Inactive) in Ariba is always up-to-date and reflects the correct business decision before synchronization.
- Job should run outside the business hours, parallel job run should be avoided to not impact the performance
Dependencies
Not Applicable
Security, Integrity and Controls
Not Applicable
Configuration Requirements
- Job Scheduling in Icertis
- Frequency: Daily execution (configurable to weekly or custom intervals).
- Execution Time: Adjustable to align with system maintenance windows or business hours.
- Retry Logic: Define retry attempts and intervals for failed runs.
- Notification Settings: Email or system alerts for job success/failure.
- API Connectivity with Ariba
- API Credentials: Secure storage and management of authentication tokens.
- Endpoint Configuration: URLs for supplier data retrieval (full list and delta updates).
- Timeout & Error Handling: Define thresholds for API response and fallback mechanisms.
- Data Processing & Synchronization
- Initial Full Load: Configuration for first-run logic to deactivate all inactive suppliers.
- Delta Updates: Enable incremental fetch based on last successful run timestamp.
- Bulk API Settings in Icertis: Batch size limits, concurrency settings for deactivation.
Special Requirements
Not Applicable
Design Rationale
Not Applicable
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
Ariba Supplier API (for supplier status retrieval) : AribaMDSOrganization
Icertis Business Bulk API (for supplier deactivation) : POST/v{version}/bulk/masterdata
Populate the table below to list the target / source data field mapping between the Source system and Target system
| 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
Describe the processing requirement from Source System
Processing within Middleware
Describe the processing requirement within Middleware Layer
Processing within Target
Interface Dependency
Interface Constraints
Delivery Requirements
- Frequency: Daily execution (configurable to weekly or custom intervals).
- Execution Time: Adjustable to align with system maintenance windows or business hours.
Delta or Full Load Requirements
- Initial Full Load: Configuration for first-run logic to deactivate all inactive suppliers.
- Delta Updates: Enable incremental fetch based on last successful run timestamp.
Interface Alert & Monitoring
Interface Reporting
Not Applicable
Language Requirements
Not Applicable
User Interface Requirements
Capture the requirements for the user interface (UI) associated with the interface. It should provide a clear description of how users will interact with the interface and how information will be presented to ensure usability and accuracy.
Volumetrics
Provide volumetrics details: Initial load volumes, Number of Records, Expected Frequency, Expected Long term Growth)
Performance Consideration
Specify if there are any specific performance factors that need to be taken into consideration during development i.e. interface must be able to handle 100 posting per-hour, etc.
Error Handling
Integration Logging: Job completion status and any errors to be logged for audit and troubleshooting.
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Results |
|---|---|---|
| 1 | Initial Full Load First run of the job with full supplier list from Ariba. |
|
| 2 | Daily Delta Update |
|
| 3 | No Changes Scenario Supplier previously inactive is reactivated in Ariba |
|
| 4 | Supplier Reactivation in Ariba |
|
| 5 | API Connectivity Failure Ariba API is unavailable during job execution. |
|
| 5 | Data Integrity Check Supplier record in Icertis already marked inactive before job runs. |
|
| 6 |
Test Considerations/Dependencies
Not Applicable
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
Appendix
See also
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.
