SD - Surya - Damodhier - 2017-07-19 - 48378 - Spec - ZOI Mexico Enhancement (Rizwan by 2017-08-04) #Mexico #OrderEntry #salesorders #EDISD #wipdoc #JapanSD #US #APAC

SPECIFICATIONS

48378 - Spec - ZOI Mexico Enhancement


Purpose

ZOI update for Mexico orders.

Admin Info

Purpose
 ZOI Mexico Enhancement
Requested By
 Rizwan Shan
Spec Created By
 Surya Basa
Spec Created Date
 07/19/2017
Spec QA by
 Surya Basa
Objects
 ZSD_CALL_OFFS
Document Status
 WIP


Estimates


Sl.No
 Activity
 Estimation in Hours
1
 Research
 08
2
 Documentation
 08
3
 Development/ Config
 40
4
 Unit test in DEV
 16
5
 Unit test in QUA
6
 Other activity

TOTAL
 72

References

Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]

SD - Surya - Venkat - Damodhier -2016-05-31 - 26580 - Re-architecture of ZJEDI (Dan by 2016-06-24)
SD - Deepak - Damodhier - 2017-06-01 - 35008 - Service Request - Rename Transaction ZJEDI(Rizwan by 2017-06-08)



Documents

[Attach any document(s) received for the requirement(s)]

ZOI_Mexico.pdf

Updated spec post discussion-

Multiple projects under different WF tasks are being worked up on this program-
1. 55995 - ZOI Japan (duplicate closed)
2. 55063 - Japan ZOI

3.41754 - Mass creation of ZRU Order (validate that this is available from ECom)


4.41754 - Assign ZANN item category as default for ZRU/NORM (removed TAN from default and added it in manual)

5.41754 - Assign TAN item category as default for ZRU/NORM (removed ZANN from default and added it in manual). Also in ZOI t.code program , all the ZRU orders would be created with ZANN item category as coded in the program.(if there are reference contracts then ZANN would be over written with TAN)



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]

1. Customer Material Number - the number maintained here should be populated on the customer material number field at the item level for each size
Sl.
 Change Details
 Requested By
 Requested On
 Notes if any
1
 1. Cust Id field should be populated on the Customer Material Number field at the item level.
Even if the field is blank, the Sales Order should be created with blank at item level.


2. JM partner field to be considered for Mexico and if present the existing logic should apply ASIS.


3. Mat ID and JAN ID/UPC both fields should be considered for loading orders, JAN ID to take precedence if present.
In case both are present and if there's a mismatch, the order should error out.
 Rizwan
 08/16/2017
 Additional effort of about 20hrs.
2
 JM partner should be considered as the fourth criteria in addition to SP,SH and PO# to create a call-off/sales order.
 Rizwan
 08/25/2017
 Additional effort of about 30hrs
3
 Order/Document type should be included as an input selection in addition to sales area.
 Babu
 08/25/2017
 NA
4
 Create the following order types in the respective sales areas -
Korea - 3100 - ZFD, ZFDR
Japan - 3200 - ZFOC
US - 1000 - ZFD, ZFDR
Canada - 1200 - ZFD, ZFDR
Mexico - 1500 - ZFD, ZFDR
China - 3300 - ZFD, ZFDR
Australia - 4000 - ZOR
 Babu
 08/30/2017
 Additional effort of approx. 8 hrs
5
 For ZFDR return orders, RRE reason code should be hard-coded in the program if the customer (SP) in the load file is maintained in the table ZFIRPGLE for the corresponding company code
 Babu
 08/31/2017
 Additional effort of approx. 8 hrs
6
 WF task 55063
- Extend the file format to be used globally - UPC and Material ID should be considered which ever is present in the load file. If both are present and in case of mismatch the entire order should fail.
- For orders created with ZOI and having ZJ delivery block, creation of delivery (manual/job) should be restricted.
 Rizwan
 9/15/2017
 Additional effort of approx 16hrs
7
 WF Task - 41754

Extend JCO PO type for 1500/ZRU and 3100/ZRU document
 Babu
 10/09/2017
 Additional efforts of 1 hour

Functional Requirement

Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]

Customer Service Mexico wants to be able to use ZJEDI with Mark for Store fields, also their want to use the tool by MID's, Size and Customer ID.

In Scope:

[List the activities to be included in scope]

Details mentioned in the spec.
Changes are applicable only for Mexico.

Out of Scope:

[Out of scope activities]

It has been confirmed that in case of return orders created by ZOI, the items therein will not be used or have any open contracts. In the event of which it may lead to faulty reports and incorrect doc flow.


Solution Summary

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

The program ZSD_CALL_OFFS should be updated to consider the new file format for Mexico only and other regions (Japan) should still be using the existing format.

The new format (.csv) is as below-
Sold to
 Ship to
 Cust PO #
 RDD
 JAN ID/UPC
 MID
 Size
 Qty
 Contract #
 Cust ID
 JM























Extend PO type JCO to all the required order types and respective sales orgs.
Create new order reason RRE and extend to all return orders and respective sales org for retail.

Test Plan

[List test scenarios/cases to be executed here]


Test ID
 Test Scenario
 Expected Results
SD001


Solution Details

[Provide complete technical details for configuration or programming here]

Config
1. Order types mentioned above are extended to the respective sales orgs and PO type (JCO) under the menu path -
SPRO-Sales&Distribution-Sales-Sales Documents-Sales Document Header-Assign Ordering Types

2. RRE (Retail Returns to WM) reason code was set up for return order type (ZFDR) under the menu path -
SPRO-Sales&Distribution-Sales-Sales Documents-Sales Document Header-Define order reason and assign order reason


Issues

[List Issues / Bugs identified in configuration or development]