Professional Documents
Culture Documents
7/26/2022
SERP01
Table of Contents
1. General Information............................................................................................................................3
2. Document Control...................................................................................................................................3
2.1 Document Control History (Do not change if no change on the template).......................................3
2.2 Revision History (To be filled out by Business Analyst, Developer and Reviewers)...........................3
2.3 Change Control History (To be filled out by Developer and Business Analyst)..................................4
3. Detailed Requirement/Technical Description......................................................................................4
3.1. Brief Description of the customer requirement/s........................................................................4
3.2. Requirement Background (To be filled out by Business Analyst).................................................5
3.3. Design Clarification History (To be filled out by Developer and Business Analyst)......................5
3.3. Brief Technical Overview.............................................................................................................5
3.3.1. Data Dictionary (To be filled out by Developer).......................................................................5
3.3.2. Custom Table Settings (To be filled out by Developer)............................................................6
3.3.3. Forms (To be filled out by Developer)......................................................................................6
3.3.4. Enhancements (To be filled out by Developer)........................................................................6
3.3.5. Transaction Code(s) (To be filled out by Developer)................................................................7
3.3.6. Code Details (To be filled out by Developer)...........................................................................7
3.4. Other Requirements and Other Non-code Related Tasks (To be filled out by Developer)..........7
3.5. Data Relationship Diagram and Data Processing (To be filled out by Developer)........................8
3.6. Object documentation (To be filled out by Developer)...............................................................8
4. Configuration (To be filled out by Business Analyst)............................................................................8
5. Test Conditions (To be filled out by Business Analyst / QA)................................................................8
4.1. Test No.............................................................................................................................................8
4.2. Test Condition(s)...............................................................................................................................9
4.3. Results..............................................................................................................................................9
1. General Information
Customer Details
Company Name LEGRAND
Process Owner
Process
PID
Development Details
Developer
Start Date End Date
Review Details
Reviewer Review Date
Approval Details
Approver Approved Date
2. Document Control
2.1 Document Control History (Do not change if no change on the template)
* In this section, the document history of this design template will be logged. Increment one to the
version number for every document change.
2.2 Revision History (To be filled out by Business Analyst, Developer and Reviewers)
* In this section, the revision of the functional and technical design will be logged. Increment 0.1 for
every modification and will become whole number only if the document is signed-off or approved by
the reviewer(s).
The email addresses for the shipping notification are to be picked from a text field in the delivery
header. Emails are added in text OC – Email Ship Notification (text id Z940) and separated by an comma.
Once Label is created from ShipERPN for Small parcel or LTL , ShipERP Logic will check if there is any
email maintained in Delivery text field , if yes take those and sent shipment notification
Sincerely Yours
Company name
Copy /ERPIS/AI003 and Create a Z table , add logic inside the email FM
New table with below primary parameters and rest same as standard table
Developer need to apply some AXO / code fix for email body
3.3. Design Clarification History (To be filled out by Developer and Business Analyst)
* In this section, the exchange of design clarification will be logged. For example,
Clarification: 02/18/2021 - From what table are we pulling the delivery header?
Confirmation: 02/18/2021 - From table likp.
Clarification Confirmation
3.4. Other Requirements and Other Non-code Related Tasks (To be filled out by
Developer)
* In this section, non-code related requirements will be listed. Examples are RFC connection settings
that is performed by the developer. Indicate N/A if not applicable.
Requirement Description
N/A N/A
3.5. Data Relationship Diagram and Data Processing (To be filled out by Developer)
* In this section, design flowchart will be indicated.
Configuration
N/A
4.3. Results
* In this section, test results with screenshot are listed. Only list final results