SERP02

Drop ship reference field

Legrand

ERP Integrated Solutions, Inc.

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

ShipERP Functional-Technical Specification | © 2021 ERP Integrated Solutions Page 2 of 11

Inc.
 SERP01

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.

Version # Date Modified Modified By Brief Description of

Change
1.0 07/26/2022 Irfaan Adhien Initial Draft

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).

Version # Date Modified Modified By Brief Description of

Change

ShipERP Functional-Technical Specification | © 2021 ERP Integrated Solutions Page 3 of 11

Inc.
 SERP01

2.3 Change Control History (To be filled

out by Developer and Business Analyst)
* In this section, the transport request of the changes will be logged. BA will also list out the transport
requests used for the configuration.

Transport Date Programmer Functional Brief Description of Change

Request Created Name Name
Number

3. Detailed Requirement/Technical Description

3.1. Brief Description of the customer requirement/s
Process requirement:

Reference field in labels - Drop Ship ( EDI-IDOC) -- Sales order number from the Customer & PO number
from end customer need to be printed in labels.

If values are maintained in below fields (assuming this will be maintained IFF shipment is Drop ship ) pull
from below else follow standard logic

Sales order number from customer (VBKD-IHREZ_E)

PO number from end customer (VBKD-BSTKD_E)

ShipERP Functional-Technical Specification | © 2021 ERP Integrated Solutions Page 4 of 11

Inc.
 SERP01

ShipERP Functional-Technical Specification | © 2021 ERP Integrated Solutions Page 5 of 11

Inc.
 SERP01

STEPS DEV TO DO

1) Create Z table copying /erpis/s001 and add fields below

REF SHIPPING POINT+ CARRIER CODE + VBKD-BSTKD_E + VBKD-IHREZ_E

Lasts two will be flags

If both the fields BSTKD_E and -IHREZ_E are BLANK in table VBKD , skip this and go to next table to get
values

ShipERP Functional-Technical Specification | © 2021 ERP Integrated Solutions Page 6 of 11

Inc.
 SERP01

3.2. Requirement Background

(Tobe filled out by Business Analyst)

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

<MM/DD/YYYY> - <Clarification Details> <MM/DD/YYYY> - <Conformation Details>

3.3. Brief Technical Overview

3.3.1. Data Dictionary (To be filled out by Developer)

* In this section, data dictionary changes such as database table, view, data type, type group, domain,
search help and lock object and etc. will be listed with screenshot.

Table/Data Dictionary Name Table/Data Dictionary Type

N/A N/A

Data Dictionary Setting and Attributes

3.3.2. Custom Table Settings (To be filled out by Developer)

* In this section, impacted table settings on custom table setting will be listed with screenshot.

Table Setting and Attributes

ShipERP Functional-Technical Specification | © 2021 ERP Integrated Solutions Page 7 of 11

Inc.
 SERP01

3.3.3. Forms (To be filled out by Developer)

* In this section, form technical details will be listed with screenshot. Indicate N/A if not applicable.

Form Name Form Type (SapScript / Smartforms / Adobe )

Form Details and Attributes

3.3.4. Enhancements (To be filled out by Developer)

* In this section, impacted or new enhancements including Z technical details will be listed. Indicate
N/A if not applicable.

Enhancement Name Description Location

Enhancement Details and Attributes

3.3.5. Transaction Code(s) (To be filled out by Developer)

* In this section, impacted or new transaction codes technical details will be listed. Indicate N/A if not
applicable.

Transaction Code Program Description

N/A N/A N/A

Transaction Code Details and Attributes

3.3.6. Code Details (To be filled out by Developer)

* In this section, impacted or new code technical details will be listed via screenshot or through
ABAPGIT repository. Code inspector and package check screenshot can also be included in this section.

ShipERP Functional-Technical Specification | © 2021 ERP Integrated Solutions Page 8 of 11

Inc.
 SERP01

Program Name Type Location

(specify if program/class/function
module/badi/user exit/routine, etc.)

Code Details and Program Attributes

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.

Data Relationship Diagram and Data Processing

3.6. Object documentation (To be filled out by Developer)

* In this section, impacted objects are list. We can refer to the transport request number to get the
technical details.

Object Name Object Type Description

ShipERP Functional-Technical Specification | © 2021 ERP Integrated Solutions Page 9 of 11

Inc.
 SERP01

4. Configuration (To be filled out by Business Analyst)

* In this section, required configuration performed are listed. Indicate N/A if not applicable.

Configuration
N/A

5. Test Conditions (To be filled out by Business Analyst / QA)

4.1. Test No.
* In this section, number of test conditions will be indicated.

Number of Test Cases: 1

4.2. Test Condition(s)

* In this section, test condition and detailed scenario with screenshot are listed.

Test No. Type Detailed Scenario

4.3. Results
* In this section, test results with screenshot are listed. Only list final results

ShipERP Functional-Technical Specification | © 2021 ERP Integrated Solutions Page 10 of 11

Inc.
 SERP01

Test No. Result

ShipERP Functional-Technical Specification | © 2021 ERP Integrated Solutions Page 11 of 11

Inc.