SD - Surya - Karthik - 2016-11-28 - 28322 - Spec - Print MSRP on Packslip (Rizwan by 2016-12-25) #SDSupportUPCLabels #OrderEntry #EMEA #wipdoc
SPECIFICATIONS
28322 - Spec - Print MSRP on Packslip
Purpose
Print MSRP on Packslip.
.
Admin Info
Purpose
|
Print MSRP on Packslip
|
Requested By
|
Rizwan Shah
|
Spec Created By
|
Surya Basa
|
Spec Created Date
|
11/28/2016
|
Spec QA by
|
Surya Basa
|
Objects
|
ZXTRKU02
ZXDELVRY03
|
Document Status
|
WIP
|
Estimates
Sl.No
|
Activity
|
Estimation in Hours
|
1
|
Research
|
04
|
2
|
Documentation
|
08
|
3
|
Development/ Config
|
08
|
4
|
Unit test in DEV
|
08
|
5
|
Unit test in QUA
|
08
|
6
|
Other activity
|
|
|
TOTAL
|
36
|
References
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]
Documents
[Attach any document(s) received for the requirement(s)]
Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
Sl.
|
Change Details
|
Requested By
|
Requested On
|
Notes if any
|
1
|
Print MSRP only if S39 is found; if S39 & S40 are found do nothing
|
Rizwan Shah
|
01/19/2017
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]
EMEA would like to print MSRP on the packslip using the Delivery IDOC output (Message Type - WHOSRD; Basic Type - /AFS/DELVRY03) if a particular VAS (S-Code) is found on the Delivery.
In Scope:
[List the
activities to be included in scope]
The change should be only applicable for EMEA (sales orgs - 2000/2100/2200) on Outbound deliveries and its associated objects -
Message Type - WHOSRD
Basic Type - /AFS/DELVRY03
Extension - ZXDELVRY03
Out of Scope:
[Out of scope activities]
Inbound IDOCs are out of scope.
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
1. VAS - S Codes (S39/
S40) would be used by way of maintaining VAS conditions using the key combo - sales org/dist ch/div/customer.
2. MSRP ( ZMRP) value should flow to the IDOC in the corresponding segment if the VAS code was found.
3. Assuming VAS were present and ZMRP not maintained then the field should not be populated on the IDOC.
4. Assuming VAS were not present and ZMRP maintained then the field should not be populated on the IDOC.
5. VAS code should be checked on each item.
Test Plan
[List test scenarios/cases to be executed here]
Test ID
|
Test Scenario
|
Expected Results
|
SD001
|
S39 maintained on SO; create delivery to trigger the iDoc - ZMRP maintained
|
iDoc should have ZMRP value populated
|
SD002
|
S40 maintained on SO; create delivery to trigger the iDoc - ZMRP maintained
|
iDoc shouldn't populate ZMRP field
|
SD003
|
S39 & S40 maintained on SO; create delivery to trigger the iDoc - ZMRP maintained
|
iDoc shouldn't populate ZMRP field
|
SD004
|
S39 & S40 not maintained on SO; create delivery to trigger the iDoc - ZMRP not maintained
|
iDoc shouldn't populate ZMRP field
|
SD005
|
S39 not maintained on SO; create delivery to trigger the iDoc - ZMRP not maintained
|
iDoc shouldn't populate ZMRP field
|
SD006
|
S39 maintained on SO; create delivery to trigger the iDoc - ZMRP not maintained
|
iDoc shouldn't populate ZMRP field
|
SD007
|
S40 maintained on SO; create delivery to trigger the iDoc - ZMRP not maintained
|
iDoc shouldn't populate ZMRP field
|
SD008
|
S39 & S40 maintained on SO; create delivery to trigger the iDoc - ZMRP not maintained
|
iDoc shouldn't populate ZMRP field
|
SD009
|
S39 & S40 maintained randomly on multiple items - ZMRP maintained
|
iDoc should have ZMRP value populated only on the items with S39
|
|
|
|
Solution Details
[Provide complete technical details for configuration or programming here]
Solution details will be updated on completion of development and testing.
Issues
[List Issues / Bugs identified in configuration or development]
NA