SD - Surya - Venkat - Damodhier -2016-05-31 - 26580 - Re-architecture of ZJEDI (Dan by 2016-06-24) #OrderEntry #US #JapanSD #Mexico #EDISD #ABAPPending

SPECIFICATIONS

26580 - Spec - Re-architecture of ZJEDI

Purpose

---

Review the options to re-architect ZJEDI to be significantly more efficient.

Admin Info

---

Purpose	Review the options to re-architect ZJEDI to be significantly more efficient.
Requested By	Dan Brennan
Spec Created By	Surya Basa
Spec Created Date	05/31/2016
Spec QA by	Surya Basa
Objects	ZCALL_OFF ZJEDI
Document Status	WIP

Estimates

---

Sl.No	Activity	Estimation in Hours
1	Research	08
2	Documentation	08
3	Development/ Config	60+02
4	Unit test in DEV	100
5	Unit test in QUA	60
6	Other activity
	TOTAL	238

References

---

Prior Tickets

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

2014-11-11 - 10735 - Spec - Program to create call offs with ref to Contracts for Japan cust. portal orders
2015-06-10 - 19859 - Spec - Japan EDI Upload Error

Documents

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

FSDE - ZJEDI Enhancements.docx

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	Rejection reason ZJ should not occur, the user specifically stated contract they would like to be referenced	Daniel Brennan	08-02-2016
2	ZJ rejection reason should be removed altogether from the program, The Japan and Mexico teams want to either (a) specify the contract to be referenced, or if they don't then (b) simply let the sales order choose the first contract it finds.	Daniel Brennan	08-02-2016
3	Performance tuning to the program to take lesser time while running over 1000 lines.	Daniel Brennan	10-03-2016

Functional Requirement

---

Purpose/WHY:

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

Review the options to re-architect ZJEDI to be significantly more efficient. Also, the option of including ship-to-DC, mark-for-store.

In Scope:

[List the activities to be included in scope]

• IDOC will be directly created by the program
• The program is enhanced to work globally, Mexico to start with initially.

Out of Scope:

[Out of scope activities]

PO types other than JCO (Japan Call Off) will not be validated by the program.

Solution Summary

---

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

Config:

1. Extend PO type JCO (Japan Call Off) to the required sales org - order type combination.

Program:

1. Program should work globally for all sales areas (currently restricted to Japan - 3200/10/00).
2. The program should create the IDOC directly. ROC functionality should no longer work.
3. Include sales area (sales org/dist channel/div) in the input selection of ZJEDI transaction.
4. Validate contract (new field in the input file) validity if specified in the input file and create call-off/s with reference or don't load lines if invalid with appropriate message.
5. Validate JM partner number (new field in the input file) if specified in the input file and create call-off/s with JM partner or don't load lines if invalid with appropriate message.
6. Validate PO type JCO if extended to the input sales area-order type combination if not don't load file with appropriate message.
7. If no contract number is specified in the input file old logic should kick in.
8. If contract number is specified in the input file, the call off should be created for the items referencing the contract.
9. The existing logic should function as is in addition to the new design.
10. Error log table should be updated with the input selection (user, time stamp, file name, sales area) information.

Test Plan

[List test scenarios/cases to be executed here]

NEC New Functionality:

Test ID	Test Scenario	Expected Results
NE001	Spreadsheet is loaded with contract reference populated for all items	Sales order should be generated with reference to contract(s) specified
NE002	Spreadsheet is loaded with contract reference populated for some items	Sales order should be generated with reference to contract(s) specified, and other items follow existing logic (search for contracts…if none found, link to free-available)
NE003	Spreadsheet is loaded with “Mark-for-Store” populated	JM partner should be added to sales order
NE004	Spreadsheet is loaded without “Mark-for-Store” populated	No JM partner should be added to sales order
NE005	Spreadsheet is loaded for non-Japan customer	All functionality should work for non-Japan sales org
NE006	Confirm IDOC is generated directly in SAP	IDOC should be generated without middleware (IBM)

BMS Existing Functionality:

Test ID	Scenario Description	ATP Check Z2=with Lead Time Z3= w/o Lead Time	Contract	Inventory	Expected Results
1	Multiple call-offs in input file, but each material has only 1 open valid contract; inventory is available				Call offs should be created referencing the ref. contract
		Z2	Single Contract	Available	Order line should be loaded with contract reference
		Z2	Single Contract	Available	Order line should be loaded with contract reference
		Z3	Single Contract	Available	Order line should be loaded with contract reference
		Z3	Single Contract	Available	Order line should be loaded with contract reference
		Z2	Single Contract	Available	Order line should be loaded with contract reference
		Z2	Single Contract	Available	Order line should be loaded with contract reference
2	Multiple call-offs in input file, each material can have either 1 open valid contract or no Contract; Inventory may or may not be available				Call offs should be created with reference where available; otherwise create standalone SO line.
		Z2	Single Contract	Available	Order line should be loaded with contract reference
		Z3	Single Contract	Available	Order line should be loaded with contract reference
		Z3	Single Contract	Not available	Order line should be loaded with J0 rejection reason
		Z3	No contract	Not available	Order line should be loaded w/o contract reference with J0
		Z2	No contract	Not available	Order line should be loaded w/o contract reference
		Z2	No contract	Available	Order line should be loaded w/o contract reference
3	Multiple call-offs in input file, each material has multiple open valid Contracts or no contract; Inventory available				Call offs should be created referencing earliest RDD contract with ZJ delivery block and ZJ rejection
		Z2	Multiple Contract	Available	Order line should be loaded with first valid Contract & with delivery block and reject reason
		Z2	Multiple Contract	Available	Order line should be loaded with first valid Contract & with delivery block and reject reason
		Z3	Multiple Contract	Available	Order line should be loaded with first valid Contract & with delivery block and reject reason
4	Some materials have valid open contracts but RDD is outside the contract validity dates; Inventory may or may not be available				Materials with valid open contracts loaded with ref. Z2 materials w/o valid open contracts loaded w/o ref. Z3 materials w/o valid open contracts loaded w/J0 rej. Code
		Z2	Single Contract	Available	Order line should be loaded with contract reference.
		Z2	Multiple Contract	Available	Order line should be loaded with reference to 1st valid contract & with delivery block and reject reason
		Z3	No contract	Not available	Order line should be loaded with J0 rejection reason because of no inventory and w/o contract reference.
		Z3	No contract	Available	Order line should be loaded without contract reference.
		Z2	Single Contract	Available	Order line should be loaded with contract reference.
		Z2	Exists but not in Req Del Dt	Available	Order line should be loaded without any contract reference
5	DUPLICATE ORDERS: If sales order already in system with (Sold-To+Ship-To+PO ); then load this order but put on delivery block on Order				Call offs should be created with reference where available and w/o if not and with delivery block
		Z2	Single Contract	Available	Order line should be loaded with reference to contract and with delivery block
		Z2	Single Contract	Available	Order line should be loaded with reference to contract and with delivery block
		Z3	No contract	Available	Order line should be loaded w/o reference to contract and with delivery block
		Z3	No contract	Available	Order line should be loaded w/o reference to contract and with delivery block
		Z2	Single Contract	Available	Order line should be loaded with reference to contract and with delivery block
		Z2	Single Contract	Available	Order line should be loaded with reference to contract and with delivery block
		Z2	Multiple Contract	Available	Order line should be loaded with reference to 1st valid contract & with delivery block and reject reason
6	Multiple call-offs exist in the input file for a contract line with SINGLE size. The first call-off consumes the entire contract quantity. Subsequent call-offs should be loaded in sales order w/o ref.				Call offs should be created with reference for available and w/o reference where not available
		Z2	Single Contract	Available	Call off should be loaded with contract reference
		Z2	No contract	Available	Sales order should be loaded w/o reference and inventory from free available should be consumed
7	Multiple call-offs exist in the input file for a contract line with MULTIPLE sizes. The first call-off consumes ONE size fully but the contract line is still open due to other sizes. Subsequent call-offs for the consumed size should be loaded in sales order w/o ref.				Call offs should be created with reference for open lines and w/o reference if no-open quantity on contract
		Z2	Single Contract	Available	1st call off should be created with contract reference and open contract quantity should be consumed for size 738
		Z2	Single Contract	Available	2nd call off should NOT be created with contract reference consuming inventory from free available w/o delivery block
8	Requested Qty is greater than open contract quantity; inventory available				Order is loaded w/reference and open contact Excess quantity should be loaded w/o reference
		Z2	Single Contract	Available	Entire order should be loaded with reference to the contract with the total quantity
	Do not reference contracts with PO Type =JPC				Load order w/o reference to PO
		Z2	Single Contract	Available	Order line should be loaded w/o reference to contract.
9	Multiple contracts for same material - one PO Type = JPC and the other non-JPC. Call-offs will be created w/ref to non-JPC contract.				Call-offs will be created w/ref to non-JPC contract.
		Z2	Multiple Contract	Available	Order line should be loaded with reference to Contract with PO type non-JPC.
10	Several (at least 4) open contracts for the same material. Call-offs will be created w/ref to earliest non-JPC contract.
		Z2	Multiple Contract	Available	Order line should be loaded with reference to earliest Contract w/o PO type JPC and with ZJ block at header & rejection at item level.
11	Requested Qty is greater than open contract quantity; inventory not available				Order should load w/ref for open qty and w/o ref for excess. ATP should use Lead time
		Z2	Single	Not Available	Order line should be loaded with reference to contract
12	Input Validation: BLANK PO - Do not load records with blank PO; log errors				Call offs should not be loaded; log error
		Z2	Single Contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z2	Single Contract	Available
		Z3	No contract	Available
		Z3	No contract	Available
13	Input Validation: BLANK SOLD TO - Do not load records with blank Sold-To; log errors				Call offs should not be loaded; log error
		Z2	Single Contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z2	Single Contract	Available
		Z3	No contract	Available
		Z3	No contract	Available
14	Input Validation: BLANK SHIP TO - Do not load records with blank Ship-To; log errors				Call offs should not be loaded; log error
		Z2	Single Contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z2	Single Contract	Available
		Z3	No contract	Available
		Z3	No contract	Available
15	Input Validation: Do not load if RDD blank or invalid; log errors				Call offs should not be loaded; log error
		Z2	Single Contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z2	Single Contract	Available
		Z3	No contract	Available
		Z3	No contract	Available
16	Input Validation: Do not load if Cancel date blank or invalid; log errors				Call offs should not be loaded; log error
		Z2	Single Contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z2	Single Contract	Available
		Z3	No contract	Available
		Z3	No contract	Available
17	Input Validation: Do not load if Quantity value ZERO or blank; log errors				Call offs should not be loaded; log error
		Z2	Single Contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z2	Single Contract	Available
		Z3	No contract	Available
		Z3	No contract	Available
18	Input Validation: Do not load if Invalid JAN ID/ Blank; log errors				Call offs should not be loaded; log error
		Z3	No contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z3	No contract	Available
19	Repeat scenario 1 with materials not used above and w/o a valid season				Call offs should be loaded with ZS rejection
20	Repeat scenario 1 with cancel and RDD in the past				Call offs should be loaded with ZD rejection and cancel and RDD pushed out (180 days for RDD and 210 days for cancel date)

BMS New functionality:

Test ID	Test Scenario	ATP Check	Contract Input	Inventory	Expected Results
SD001	Input Validation: Invalid contract number				Call offs should not be loaded; log error
SD002	Input Validation: Invalid JM partner				Call offs should not be loaded; log error
SD003	Input Validation: Invalid sales area-customer combination				Call offs should not be loaded; log error
SD004	Input Validation: JCO PO type not maintained				Call offs should not be loaded; log error
SD005	Multiple call-offs exist in the file with multiple lines; input contract number references only one call off
		Z2	Yes/Multiple	Available	Order line should be loaded with contract reference from the input; Order line should be loaded with open contract/s other than that of input if found and ZS delivery block and ZS rejection should be applied; Order line should be loaded w/o contract reference and consume inventory from free available
		Z3	Yes/Multiple	Not Available	Order line should be loaded with contract reference from the input; Order line should be loaded with open contract/s other than that of input if found and ZJ delivery block and ZJ rejection should be applied; Order line should be loaded w/o contract reference and J0 rejection should be applied
SD006	Multiple call-offs exist in the file with multiple lines; input contract number references only one call off
		Z2	Yes/Single	Available	Order line should be loaded with contract reference from the input; Order line should be loaded w/o contract reference and consume inventory from free available
		Z3	Yes/Single	Not Available	Order line should be loaded with contract reference from the input; Order line should be loaded w/o contract reference J0 rejection should be applied

Solution Details

---

[Provide complete technical details for configuration or programming here]

Issues

---

[List Issues / Bugs identified in configuration or development]