SD- Deepak- Damodhier- 2016-07-06 - 27573 - Spec - The email shouldn't states as Batchuser (Rizwan by 2015-07-21) #salesorders #SDSupportForms

SPECIFICATIONS

27573-Spec- The email shouldn't state as batch user


Purpose


The ZBEA output sender name shouldn't state as batchuser.

Admin Info


Purpose
The ZBEA output sender name shouldn't state as batchuser.
Requested By
Rizwan Shah
Spec Created By
Deepak Yasam
Spec Created Date
07/06/2016
Spec QA by
Surya Basa
Objects
Z_SD_OA_COMM_MAIL

ZSD00100_EXTMAIL_EXCEL
Document Status
Completed


Estimates



Sl.No
Activity
Estimation in Hours
1
Research
00
2
Documentation
02
3
Development/ Config
24
4
Unit test in DEV
10
5
Unit test in QUA
00
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

























Functional Requirement


Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]
The ZBEA EMEA Email OA output sender name shouldn't be batchuser.

In Scope:

[List the activities to be included in scope]
Only ZBEA output is in the scope.

Out of Scope:

[Out of scope activities]
Other outputs should be triggered as standard.

Solution Summary


[Discuss this section with Requester and get approval prior to beginning work]

When the EMEA Email OA is triggered for the SO's the sender name should be NEWERACAP@NEWERACAP.COM.
The output program needs to be changed to achieve the desired business objective.



Test Plan

[List test scenarios/cases to be executed here]
Test ID
Test Scenario
Expected Results
SD-001
1.Create a EDI ZOR SO in 2000,10,00 sales area.
2.Issue ZBEA OA email output in the SO.
The OA excel file should be generated and the sender name should be displayed asneweracap@neweracap.com
SD-002
1.Create a manual ZOR SO in 2000,10,00 sales area.
2.Issue ZBEA OA email output in the SO.
The OA excel file should be generated and the sender name should be displayed asneweracap@neweracap.com
SD-003
1.Create a manual ZOR SO in 2000,10,00 sales area.
2. Reject some of the line items.
3.Issue ZBEA OA email output in the SO.
The rejected items shouldn't display any quantities in the OA excel file should be generated and the sender name should be displayed as neweracap@neweracap.com
SD-004
1.Create a manual ZOR SO in 2000,10,00 sales area.
2. some of the line items should be split with multiple sizes.
3.Issue ZBEA OA email output in the SO.
The split sizes should also be displayed along with other items in the OA excel file
and the sender name should be displayed as neweracap@neweracap.com
SD-005
1.Create a manual ZU3P SO in 2000,10,00 sales area.
2.Issue ZBEA OA email output in the SO.
The OA excel file should be generated and the sender name should be displayed asneweracap@neweracap.com
SD-006
1.Create a manual ZWEB SO in 2000,20,00 sales area.
2.Issue ZBEA OA email output in the SO.
The OA excel file should be generated and the sender name should be displayed asneweracap@neweracap.com
SD-007
1.Create a EDI ZWEB SO in 2000,20,00 sales area.
2.Issue ZBEA OA email output in the SO.
The OA excel file should be generated and the sender name should be displayed asneweracap@neweracap.com
SD-008
1. Create Contract and corresponding calloff in 2000,10,00 sales area.
2. Issue ZBEA OA email output in the Calloff.
The OA excel file should be generated and the sender name should be displayed asneweracap@neweracap.com
SD-009
1. Create Contract and corresponding (partial quantity) calloff in 2000,10,00 sales area.
2. Issue ZBEA OA email output in the Calloff.
The OA excel file should be generated with selected line items and the sender name should be displayed as neweracap@neweracap.com

Solution Details


[Provide complete technical details for configuration or programming here]



Issues


[List Issues / Bugs identified in configuration or development]