You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
| Status | |
|---|
| Owner | |
|---|
| Stakeholders | |
|---|
| Jira Request ID | |
|---|
| Jira Development ID | |
|---|
High- Level Specification
| Implementing System | |
|---|
| Invoked by/Invokes | |
|---|
| Business Process Reference |
|
|---|
Functional Overview
The functional design of the system interface defines the API to be provided or consumed.
Scope and Objectives
Process Flow Diagram
Assumptions
Dependencies
Security, Integrity and Controls
Configuration Requirements
Special Requirements
Design Rationale
API Use
Data Structure
The following fields will be used to provide the required data structure of the interface:
| Parent | Field | Description | Mandatory (Y/N) | Data Type |
|---|
|
|
|
|
|
|
|
|
|
|
Calculation and Validation
| Parent | Field | Rule Type | Rule Instruction |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
eDocument mapping
| General | Syensqo XML (Target) | SAP eDoc Standard Mapping (Source) | Custom Mapping (Source) |
|---|
| S-NR | Flow (SD/FI/MM/ALL) | Field Details | Condition | Syensqo XML Node | Syensqo XML Field | SAP eDoc Standard Node | SAP eDoc Standard Field | Fixed Value | Custom Logic |
|---|
|
|
| | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Processing Logic
Delta or Full Load Requirements
Interface Alert & Monitoring
Language Requirements
User Interface Requirements
Sequencing
Performance Consideration
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Results |
|---|
|
|
|
|
|
|
Test Considerations/Dependencies
Development Details
Package
| Package Name | Parent Package |
|---|
|
|
|
|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|
|
|
|
|
|
|
|
|
See also
No files shared here yet.
