Functional Specification Document
Module: EWM
Development Description: EWM IBGI Processes
Phase I
Document No.: XXXXXXX
Version No.: 1.0
Effective Date: 30.10.2020
Functional Specification Document –EWM
Document No: FS_BBD_EWM_002 EWM IBGI Process
Table of Contents
1.0 DOCUMENT HISTORY.............................................................................................................................3
1.1 DOCUMENT VERSION..............................................................................................................................3
1.2 DOCUMENT APPROVAL / REVIEW DETAILS..................................................................................................3
1.1 REFERENCE DOCUMENT DETAILS...............................................................................................................3
1.2 ABBREVIATIONS USED (IF ANY).................................................................................................................3
1.3 DEFINITIONS USED (IF ANY).....................................................................................................................4
2.0 FUNCTIONAL SPECIFICATION................................................................................................................4
2.1 DEVELOPMENT SUMMARY.......................................................................................................................4
2.2 APPLICABILITY........................................................................................................................................5
2.3 OBJECTIVE OF THE DEVELOPMENT.............................................................................................................5
2.4 DEPENDENCIES AND CONSTRAINTS............................................................................................................6
2.5 ASSUMPTIONS AND NOTES.......................................................................................................................6
2.6 RELEVANT TRANSACTION CODES...............................................................................................................7
2.7 REFERENCE SAP PROGRAMS....................................................................................................................7
2.8 SELECTION PARAMETERS TO EXECUTE THE TRANSACTION / PROGRAM.............................................................7
2.9 OUTPUT LAYOUT (FOR REPORT, INTERFACE, ENHANCEMENT AND FORM ONLY)................................................8
2.10 ERROR HANDLING...................................................................................................................................8
2.11 USER EXIT/ENHANCEMENT......................................................................................................................8
2.12 BATCH SCHEDULE REQUIREMENT..............................................................................................................8
3.0 PROGRAM LOGIC / PSEUDO CODE / FIELD MAPPINGS.......................................................................8
3.1 AUTHORIZATION CHECK REQUIREMENT......................................................................................................9
3.2 OTHER SPECIAL REQUIREMENT (SUCH AS GRC REQUIREMENTS).....................................................................9
3.3 FUNCTIONAL VALIDATION REQUIREMENT (IF ANY).......................................................................................9
3.4 FLOW CHART (IF ANY)...........................................................................................................................10
Confidential Page 2 of 9
Functional Specification Document –EWM
Document No: FS_BBD_EWM_002 EWM IBGI Process
4.0 Attachments & Annexure....................................................................................................................10
1.0 Document History
Document Category Functional Specification Document
Document title EWM IBGI Process
Author Sowntharya Lakshmi
Lead Consultant
1.1 Document Version
Date Version Author Status - Description
30.10.2020 1.0 Sowntharya Initial draft
1.2 Document Approval / Review Details
Function Name Department Sign & Date
Sowntharya 30.10.2020
Prepared By
Reviewed By
1.3 Reference Document Details
Department /
Title of the Document Version No Organization Reference / Remarks
1 EWM
EWM IBGI Process
Confidential Page 3 of 9
Functional Specification Document –EWM
Document No: FS_BBD_EWM_002 EWM IBGI Process
1.4 Abbreviations Used (If any)
Abbreviation Description
Outbound Delivery Order
ODO
Outbound Delivery
OD
Invoice Before Goods Issue
IBGI
Cost of goods sold
COGS
Post Goods Issue
PGI
1.5 Definitions Used (If any)
Definitions Description
2.0 Functional Specification
2.1 Development Summary
Function Description
Development ID
Gap ID
Author
Name of Development EWM IBGI Process
Short Description EWM IBGI Process
Development Type (RICEFW) E
Module/Business Process EWM / Outbound
Required Transaction Code /N/SCWM/PRDO and /N/SCWM/TU
Complexity (L/M/H) H
Confidential Page 4 of 9
Functional Specification Document –EWM
Document No: FS_BBD_EWM_002 EWM IBGI Process
Function Description
Priority (L/M/H) H
Frequency On daily basis
Functional Consultant Sowntharya Lakshmi
Process Owner Warehouse Team
2.2 Applicability
The process described in this document are applicable to the below mentioned entities / tracks.
Business Vertical Applicability
No
The Arvind Stores
No
Fashion division
No
Sports division
Yes
Arvind True Blue Ltd
Yes
Arvind Lifestyle
Yes
Arvind Ruff and Tuff Ltd
Yes
Arvind Internet Limited
No
Garment export division
2.3 Objective of the Development
The cogs and the revenue are generated even before the stocks are been dispatched from the
warehouse, this is getting the company into the wrong reporting of Revenue and hence we need to
resolve by using IBGI concept. Basically, Invoice Before Goods Issue (IBGI) must be triggered from
EWM once pick and pack is completed. This will create invoice document in ECC and then the
process of LR creation in ALM, Manual PGI in EWM, Tax invoice creation in ECC, TU Load in ECC and
then physical dispatch will happen from warehouse. By implementing IBGI concept, company will be
benefited with the revenue and cogs booking more efficiently.
IBGI concept in EWM is the standard SAP EWM concept. We will be implementing the standard
concept along with Arvind specific requirements.
Confidential Page 5 of 9
Functional Specification Document –EWM
Document No: FS_BBD_EWM_002 EWM IBGI Process
Two systems are involved in achieving IBGI concept (ECC and EWM). This FS will explain about the
detailed custom requirement in EWM. For ECC FS, kindly refer FS “XXXXXXXXXXXXXX”. The major
challenge in the development is creation of single invoice for multiple deliveries. As per standard
EWM concept, single invoice can’t be created for multiple deliveries. This will be achieved during
posting in ECC by ECC development objects. This information can be tracked in ECC FS
”XXXXXXXXXXXXXXXXXXXX”
Below are the custom requirements in EWM to achieve IBGI Process
1. Restrict GI at HU, ODO and OD level.
2. Restrict GI cancellation at HU, ODO, OD level
3. Restrict OD creation for partial line items of delivery
4. Auto OD creation via PPF or running report SPPFP or at delivery level
5. Validate during OD creation (IBGI), that pick and pack is completed for all the delivery types
except rush orders types and no nested HU are packed in delivery and then no HU’s are lying
with resources
6. During manual GI in EWM at TU level, system should check that invoice is created in ECC and
EWM, no queues are stuck in ECC inbound queues
7. During reversal process, system should validate first that invoice is cancelled in ECC, reverse GI
at TU level not at ODO or OD level, do cancpick and nullify the quantities and post the document
from EWM to ECC.
2.4 Dependencies and Constraints.
Outbound delivery flown to EWM, Pick and Pack completed in EWM are major dependency activities
and rule table entries are mandatory for all the warehouses
2.5 Assumptions and Notes
1. Outbound delivery flown to EWM and available in EWM
2.6 Relevant Transaction Codes
Transaction Code Description
Outbound Delivery Order
/N/SCWM/ODO
Outbound Delivery
/N/SCWM/OD
Transportation Unit
/N/SCWM/TU
Selection and Processing of Actions
SPPFP
Confidential Page 6 of 9
Functional Specification Document –EWM
Document No: FS_BBD_EWM_002 EWM IBGI Process
2.7 Reference SAP Programs
NA
Program Name Description
2.8 Selection Parameters to execute the Transaction / Program
NA
Field Name Description
2.9 Output Layout (For Report, Interface, Enhancement and Form only)
NA
2.10 Error Handling
1. Pick not completed for IBGI
2. Pack not completed for IBGI
3. Nested HU available. Please correct before IBGI
4. HU’s are lying with resource instead of GI Zones. Please correct before triggering
OD/IBGI
5. GI not possible because of ECC stuck queue “XXXXXXXX”
6. GI not possible because of no invoice creation in ECC
Confidential Page 7 of 9
Functional Specification Document –EWM
Document No: FS_BBD_EWM_002 EWM IBGI Process
7. GI Reversal not possible since invoice is not cancelled in ECC
2.11 User Exit/Enhancement
User Exit Name Component name Description
YEWM_QUANTIT To restrict GI at HU, ODO and OD
Y_TOLERENCE
XXXXXXXX Validate pick and pack completed, no nested HU’s,
HU’s not in resource
XXXXXXXX During auto OD creation or via report validation
based on the pick and pack completed, no Nested
HU’s and HU’s not in resource
XXXXXXXXX GI not possible if no invoice created in ECC and no
ECC inbound queue stuck
XXXXXXXXX GI Reversal not possible when invoice is not
cancelled in ECC
2.12 Batch Schedule Requirement
NA
3.0 Program Logic / Pseudo Code / Field Mappings
Detail the logic of the program.
Restrict GI at HU, ODO and OD level: Use enhancement “XXXXX” to restrict GI at ODO, OD and HU level.
This validation will be triggered only for the outbound processes for tcodes /SCWM/PRDO and /SCWM/FD.
The validation is based on the actions (on click of the button) for “/SCWM/ACT_POST_GM” and
“/SCWM/ACT_POST_GM” and custom rule table entries for the specified warehouse maintained.
Restrict GI cancellation at HU, ODO, OD level: Use enhancement “XXXXX” to restrict GI at ODO, OD and HU
level. This validation will be triggered only for the outbound processes for tcodes /SCWM/PRDO and
/SCWM/FD. The validation is based on the actions (on click of the button) for” /SCWM/ACT_CANCEL_GM”
and custom rule table entries for the specified warehouse maintained.
Restrict OD creation for partial line items of delivery: Use enhancement “XXXXX” to restrict OD creation
from HU tab based on the action value “/SCWM/S_SP_A_HU” and validate if OD created only from item tab
for all the delivery line items based on the action value “/SCWM/S_SP_A_ITEM” and
“/SCWM/ACT_TRANSFER_FD”. Always delivery line items and selected line items should match.
Validation before IBGI when manual OD created: Use enhancement “XXXXX” to validate pick and pack
completed, no nested HU’s and HU’s are not in resources. Use method
Confidential Page 8 of 9
Functional Specification Document –EWM
Document No: FS_BBD_EWM_002 EWM IBGI Process
“/SCWM/CL_DLV_MANAGEMENT_PRD-~Query” to fetch the header level pick and pack status and use
method “/scwm/if_dlv_service_hu~dlv_get_hu_assignment” to check HU’s in resource or not and no nested
HU’s.
Validation before IBGI when auto OD created or using report ‘SPPFP: Use enhancement “XXXXX” to
validate pick and pack completed, no nested HU’s and HU’s are not in resources. Use method “XXXXXX” to
fetch the header level pick and pack status and use method “XXXXXXX” to check HU’s in resource or not and
no nested HU’s.
Validation during GI at TU level: Use enhancement “XXXXX” to restrict GI if invoice not created in ECC and
queue stuck in ECC. Use RFC FM “XXXXXXX” to validate invoice creation in ECC and FM “XXXXX” to check any
stuck queues in EWM
Validation during GI Reversal at TU level: Use Enhancement “XXXXX” to restrict GI cancel when invoice is
not cleared in ECC. This will be achieved via RFC FM “XXXXXX”.
3.1 Authorization Check Requirement
NA
3.2 Other Special Requirement (such as GRC requirements)
NA
3.3 Functional Validation Requirement (If any)
1. Warehouse maintenance in rule table
2. Condition records maintained for Auto OD creation
3.4 Flow Chart (If any)
4.0 Attachments & Annexure
NA
Confidential Page 9 of 9
