2015-11-06 - 22962.100 - Spec - JCPenney carrier from EDI 754 SAP orders (Julia by 2015-12-15) #ShippingNotification

SPECIFICATIONS

22962.100 - Spec - JCPenney carrier from EDI 754 SAP orders


Purpose

Carrier not being populated correctly in print form.

Admin Info

Purpose
 Update the logic in ZLD4 output form to pick the carrier id (KVGR2) from LIPS for JCP
Requested By
 Julia Kaminski
Spec Created By
 Siba Mohapatra
Spec Created Date
 11-06-2015
Spec QA by
 Deepak Yasam
Objects
 ZSD_PICK_PLAN2_NA
Document Status
 Completed


Estimates


Sl.No
 Activity
 Estimation in Hours
1
 Research
 02
2
 Documentation
 04
3
 Development/ Config
 06
4
 Unit test in DEV
 06
5
 Unit test in QUA
 00
6
 Other activity

TOTAL
 18

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
01
 Update form ZSD_PICK_PLAN2_NA to pull Carrier ID (KVGR2) from LIPS for JCP customer
 Julia Kaminski
 11/06/2015
 NA




















Functional Requirement

Purpose/WHY:

Print output is updating the carrier id from VBAK which is required to change and it should be picked from LIPS for JCP.

In Scope:

The logic of fetching from LIPS will hold only for JCP.

Out of Scope:
For other customers the carrier ID will be from SO only.

Solution Summary

It is required to update the form - ZSD_PICK_PLAN2_NA to pick the Carrier ID (Customer Group 2- KVGR2) from LIPS table for JCP customer.

The TVARVC table variable ZSD_JCP_SOLDTO_FOR_754 value is checked for JCP customer.


Test Plan

[List test scenarios/cases to be executed here]
S.No
 Test Scenario
 Expected Result
1
 1.Create a calloff with reference to contract.
2.Create corresponding delivery with carrier ID 277 .
3.Execute JCP 754 without any changes and Issue ZLD4 output in delivery.
 The carrier ID from the delivery (277 TMS ROUTING) should be displayed in the output
2
 1.Create a calloff with reference to contract.
2.Create corresponding delivery with carrier ID 277 .
3.Execute JCP 754 by chnaging the carrier ID to 194 and Issue ZLD4 output in delivery.
 The carrier ID from the delivery (194 UPSN GND) should be displayed in the output
3
 1.Create a calloff with reference to contract.
2.Create corresponding delivery with carrier ID 277 .
3.Execute JCP 754 by chnaging the carrier ID to 194 and Store ID .
4. Issue ZLD4 output in delivery.
 The carrier ID from the delivery (194 UPSN GND) should be displayed in the output

Solution Details




Issues

[List Issues / Bugs identified in configuration or development]