| Status | Approved |
|---|---|
| Owner | ROWLINSON-ext, Kerry |
| Stakeholders | |
| Jira Request ID | ERP-2583 - Getting issue details... STATUS |
| Jira Development ID | ERP-2611 - Getting issue details... STATUS |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | SAP ECC (both PF2 & WP2) |
| Business Process Reference |
Functional Overview
The functional design of the enhancements describes the scenario(s) where enhancements to existing SAP programs are required.
In the standard CIG integration from ECC to Ariba, only internsupplierid and buyersystemid domain are automatically populated with SAP PRS ID. To integrate Ariba Catalog with EZBuy, sap domain is also required. However, this sap domain is not populated via integration.
The custom development will be done to extend the Ariba CIG Master data export (ARBCIG_MASTER_DATA_EXPORT) via BADI to add custom fields in the extract file.
One field CustomDomainName is to have a constant value ‘sap’. The other field CustomDomainValue will contain the PRS Vendor ID. These fields will be available in the files produced in the full export and in the incremental load.
The mapping of country - region is not supported in the backend of SAP Ariba Sourcing, because it is only available in Ariba SLP. So, we cannot build our Ariba realm now.
If we want the region description to be displayed in the supplier address, the description must be provided in the integration CSV file instead of the region code.
Justification
The integration with Ariba Catalog with EzBuy will not be possible without the additional field being provided in the export file.
Alternatives considered
No alternatives identified, SAP recommended consulting to update the export program with the additional fields.
Scope and Objectives
Step | Description | Comment |
|---|---|---|
Assumptions
Dependencies
Security, Integrity and Controls
Configuration Requirements
Language Requirements
Special Requirements
Design Rationale
Functional Requirements
Proposed Technology to Use
Data Source Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Data Validation Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Custom Tables
Master Data
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Configuration Table
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Selection Screen Enhancement
| Field Name | Description | Select: | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|---|---|---|---|---|
Processing Logic
Volumetrics
Performance Considerations
Error Handling
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
Test Considerations/Dependencies
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Enhancement Implementation
| Enhancement Type | Standard Definition Name | Custom Implementation Name | Design Rationale Reference |
|---|---|---|---|