| Status | |
|---|---|
| Owner | ROWLINSON-ext, Kerry |
| Stakeholders | |
| Jira Request ID | |
| Jira Development ID |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | SAP ECC (both PF2 & WP2) |
| Business Process Reference |
Functional Overview
Supplier Master Data consists of general information stored in SAP that is used in SAP Ariba Sourcing solutions to construct Sourcing Projects and Sourcing Event. The SAP Ariba Sourcing Solutions provide the integration events for standard data imports from the SAP ERP System. Supplier Master Data is integrated from SAP ERP System to the SAP Ariba Sourcing solutions realms through SAP Ariba Cloud Integration Gateway (CIG) using Direct Connectivity. ERP-116 System Interface - Supplier Integration from SAP ECC (PRS) to Ariba details this integration.
The Ariba CIG Add-On is installed on SAP ERP and configuration completed to enable the program ARBCIG_MASTER_DATA_EXPORT to extract Supplier data from SAP standard Supplier tables.
The enhancements to ARBCIG_MASTER_DATA_EXPORT described in this functional specification are for two purposes:
- Two additional fields are required to be included in the CSV file sent to Ariba. in order to integrate the Ariba Catalog with EZBuy
CustomDomainName
CustomDomainValue - The value for the field 'State' is required to be changed to provide Ariba with the description of the State (region) instead of the SAP code as there is no mapping of country and region in SAP Ariba Sourcing.
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.
The 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 fields for the domain name and value being provided in the export file. With the integration of the supplier data from SAP being an automated process, manual updates to fill the sap domain field in Ariba are not feasible. 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 the standard integration.
The mapping of country to region is not supported in the backend of SAP Ariba Sourcing. It is only available in Ariba Supplier Lifecycle and Performance (SLP). Without this mapping the region description cannot be displayed in the supplier address. Whilst sometimes these are recognizable abbreviations, in SAP some of the values for region are meaningless two-digit codes which are unsuitable for address formatting.
Alternatives considered
No suitable alternatives identified, SAP recommended consulting to update the export program with the additional fields. Manual updates are possible but unsuitable due to the automatic integration of new and changed supplier records.
Scope and Objectives
Detail the functional scope and objectives of the Enhancements. Please also describe the gap that will be addressed by this enhancement (Compared to SAP Standard)
The standard SAP program ARBCIG_MASTER_DATA_EXPORT does not provide any configuration option to add additional fields or to control the use of the region code versus the description. SAP provides a BADI for these purposes.
Process steps:
Step | Description | Comment |
|---|---|---|
| 1 | New suppliers or changes to existing supplier records in SAP PRS system | Scheduled background job produces a supplier.csv file with details of the new and changed suppliers (LFA1 Vendor Client Level table only). The job details are based on the defined configuration for the supplier master data export to Ariba. |
| 2 | Supplier.csv file is sent via the managed gateway (CIG) to Ariba | The file is received via the managed gateway CIG to Ariba |
| 3 | File is processed creating new suppliers or changing existing suppliers in the parent realm in Ariba | File is processed in the parent realm in Ariba for use in Ariba Sourcing |
| 4 | File is processed creating new suppliers or changing existing suppliers in the child realm in Ariba | File is processed in the child realm in Ariba for use in Ariba Catalogs |
Assumptions
There are no identified assumptions.
Dependencies
There are no dependencies on this enhancement or on the integration of the supplier data. The Ariba CIG export for suppliers was specifically set up for the integration to Ariba for Syway, it was not in use at all prior and therefore these changes impact no other system receiving the supplier information.
Security, Integrity and Controls
There are no specific security, integrity or controls required for this enhancement.
Configuration Requirements
There are no additional configuration requirements associated with this enhancement.
Language Requirements
Region descriptions are held in SAP in multiple languages, only EN English description will be selected by this enhancement.
Special Requirements
There are no special requirements to be considered.
Design Rationale
Functional Requirements
The 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.
Instead of the region code in column G of the consolidated file, logic in the user exit is to look up the description of the region/state based on the country in column H. In SAP, look up table T005U, always in EN English, with Country Code and Region Code to retrieve Description field (T005U-BEZEI). The description is to replace the region/state code in Column G.
Proposed Technology to Use
Badi Name: ARBCIG_MASTERDATA
Available to enhance the Master Data Upload Request as required. Available in the ARBCIG_MASTER_DATA_EXPORT program.
Data Source Considerations
Include an overview of the source. Can be deleted if not needed.
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Data Validation Considerations
There are no data validations required for this enhancement.
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Custom Tables
Not applicable for this enhancement.
Master Data
Not applicable for this enhancement.
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Configuration Table
Not applicable for this enhancement.
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Selection Screen Enhancement
Not applicable for this enhancement.
| Field Name | Description | Select: Option or Parameter Check box or Radio button Import or Export | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|---|---|---|---|---|
Processing Logic
This section defines the detailed step-by-step logic implemented within the BAdI/User Exit to process the data received from the standard SAP program and database retrieval. It explains the operations performed on the data, the expected outcomes in different scenarios and how the system should behave in response to specific conditions.
Volumetrics
Provide volumetrics details: Initial load volumes, Number of Records, Expected Frequency, Expected Long term Growth)
Performance Considerations
Specify if there are any specific performance factors that need to be taken into consideration during development i.e. enhancement must be able to be executed by 10 users at the same time, etc.
Error Handling
Detail how errors will be handled: Notification, Restart/ Recovery and Re-Processing Procedures
Testing
How to Test
Please provide some guidance and/or test data to help the developer unit test the enhancement. Please include both positive and negative testing (to validate error situations handling). The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again or explain how to create new input data to the test. The developer will need logons for test users representing the various roles within the approval process.
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
Test Considerations/Dependencies
List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Enhancement Implementation
| Enhancement Type | Standard Definition Name | Custom Implementation Name | Design Rationale Reference |
|---|---|---|---|
Other Development Objects
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.
