High- Level Specification

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:

1. 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
2. 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.

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 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 a meaningless two-digit code which is unsuitable for address formatting.

Alternatives considered

No alternatives identified, SAP recommended consulting to update the export program with the additional fields.

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)

Insert the flowchart and fill in the steps

Assumptions

Describe any assumptions that have been made in the process of completing this design. What functionality is expected of configuration or other developments that pass information to this development and/ or retrieve the information processed by it (performance, triggers, exceptions, etc.)

Dependencies

Indicate any dependencies or constraints that may impact this development, in terms of requirements from internal or external applications, other work streams, time constraints, data or system access restrictions. Also, please specify scheduling or process dependencies, e.g. interface/batch job that must run beforehand or process steps that need to be completed prior to executing this development.

Security, Integrity and Controls

To detail the security requirements for processing this enhancement, any data integrity issues associated with the object and the teams that will be responsible for processing the object, i.e. authorization/roles required to who can execute the enhancements, etc.

- Custom Tables, enhancement, transaction codes, programs, Web Dynpro Application, Code Data Services (CDS), Open Data Protocol (OData), BI reports, and Functional Modules need to have at least one authority check either standard or custom. (custom should be an exception)

- All custom tables will be maintained in a certain Authorization Group (example: ZFIN, etc.)

- In the case of transaction codes an additional check other than the object S_TCODE is required. You can use SU24 to find the related authorization objects to check.

All other WRICEFs

- If the authorization check is already performed in the calling Programs, this section can be filled as “Follow calling programs authorization check” (example : BADI to redirect DMS to OpenText, in which the calling Manage Purchase requisition Fiori App already performed authorization check)

- If the authorization check is not checked in any of the development, this section should be filled with the proposed authorization check. You can refer to SU24 to see the standard authorization objects. (example: full custom Fiori App to enable user to download/upload the project plan)

Configuration Requirements

Specify the configuration requirements for this object. Like in case of substitution/ routine specify the configuration needed

Language Requirements

Specify the language requirements for this object. Specify the required language and type of translation, like labels, data.

Special Requirements

Specify any special requirements or considerations that may impact the enhancement based on specific locations, regulatory compliance or system limitations. Clearly outline requirements e.g. localization rules for countries like China

If the enhancement interacts with third-party systems such as Icertis, describe any additional integration, security or authentication considerations that must be taken into account.

Design Rationale

Functional Requirements

Detail the functional requirements that are desired to be achieved by the Enhancement compared to current functionality

Proposed Technology to Use

Typically, an enhancement will be based on an existing SAP BADI / user exit. If this is the case, please provide the proposed details of the BADI / user exit.

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.

Data Validation Considerations

Include an overview of the data validation requirement. Can be deleted if not needed.

Custom Tables

If any custom configuration tables are required, which will be read by the enhancement logic, then specify them here. Can be deleted if not needed.

Master Data

<Title Custom Table 1>

<Include an overview of the table and what it’s used for>

Configuration Table

Title Configuration Table 1

Include an overview of the table and what it’s used for

Selection Screen Enhancement

This section will give the details on the selection screen parameters, parameter type and whether it’s obligatory or not. This section can be used to define the Import Export parameters for Function Module or User Exit or Screens. Can be deleted if not needed.

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

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

Enhancement Implementation

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.

Change log