| Status | Approved |
|---|---|
| Owner | ROWLINSON-ext, Kerry |
| Stakeholders | |
| Jira Request ID | ERP-243 - Getting issue details... STATUS |
| Jira Development ID | ERP-256 - Getting issue details... STATUS |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | SAP ECC PF2, SAP ECC WP2 |
| Business Process Reference | 03.04.04.01. Manage Outline Agreements (R2) |
Functional Overview
The functional design of the enhancements describes the scenario(s) where enhancements to existing SAP programs are required.
Scope and Objectives
Step | Description | System | Comment |
|---|---|---|---|
1 | A purchase contract is executed in Icertis | Icertis | A legal purchase contract is executed in Icertis which is relevant to be represented in SAP ECC by an outline agreement: |
2 | New entry in custom table for the Icertis Contract | SAP ECC | Integration automatically creates the Icertis Contract record in custom table in both SAP ECC systems (WP2 & PF2) with the Tenant ID, Agreement Type, System ID, Icertis Agreement Code and the relevant data fields from the contract header. Individual Purchasing Organization values and the System Id are stored in a separate custom table. |
| 3 | One or more Outline Agreements are created | SAP ECC | One outline agreement per purchasing organization is created in SAP ECC |
| 4 | Icertis Agreement Code is entered on the outline agreements | SAP ECC | The update program is used to enter the Icertis agreement code on the header of each of the relevant outline agreements |
| 5 | An outline agreement exists in SAP without a corresponding legal contract in Icertis | SAP ECC | |
| The update program is used to select a reason why a legal contract is not available or not possible to define for the outline agreement. |
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 |
|---|---|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
Appendix
Custom Authorization Group Naming Convention
This table is based on the Syensqo development standards document. It provides the naming conventions for authorization groups to associated with custom reports and tables to comply with security requirements.
ABAP | ZFI | ZMM | ZPS | ZCO | ZSD | ZBC | ZFI | ZCA |
|---|---|---|---|---|---|---|---|---|
| TABLES | ZFIT | ZMMT | ZPST | ZCOT | ZSDT | ZBCT | ZFIT | ZCAT |