R00460 Implementing Work Order Z File Exports Using Subsystem Processing P48013 (JDEWO)

Purpose of Document

Goal

This document is part of an Information Center - to see other documents related to Shop Floor Control, please use the links provided below: Information Center: JD Edwards EnterpriseOne Shop Floor Control > Information Center: Using JD Edwards EnterpriseOne Shop Floor Control > Note 1342363.1

This document is a guide on how to implement work order header extraction through subsystem routine in Work Order Processing in addition to Question 5 listed on E1: 31: Outbound Interoperability for Shop Floor Management (R4801Z1X & R4801Z1P) - Document 1323732.1.

Note:

Not all the interoperability implemented have it's own extraction UBE/Function.
If possible, implement Business Service, XPI, EDI for interface.
If there is no standard Extraction UBE, then create your own UBE or Business function to meet your daily business requirement.

Solution

Overview

The following steps are to be used on how to hookup work order extraction through subsystem job.

Basic Set Up

1. Verify if UDC 00/TT - Transaction Type has definition for the transaction type required to perform (e.g. JDEWO):

User Def Code	Description	Description	Special Handling	Hard Coded
JDEWO	Work Order Header Transaction			Y

2. Verify if Transaction Type defined above has definition on Interoperability file for outbound (Flat File Cross-Reference -P47002):

Trans	Trans Description	Dir Ind	Dir Ind Description	Record Type	Record Type Description	File Name	Flat File Name
JDEWO	Work Order Header Transaction	2	Outbound	1	Header	F4801Z1

3. Verify UDC 00/TA - Transaction Action:

User Def Code	Description	Description	Hard Coded
01	Cancellation	D - Delete	Y
02	Add	A - Add	N
03	Delete	D - Delete	N
04	Change	C - Change	Y
06	Confirmation	I - Inquiry	Y
07	Duplicate	A - Add	N

Based on Transaction Action Code (e.g. 02 to Add) it reads the first character of Description 02 column. For this example, 02 is the code for Add.
Data Dictionary Alias TNAC (Transaction Action) has to be defined. Withing the application, the Action Code is hard coded to verity the transaction and how a certain routine sets this value.

4. Add Data Export Control record through Data Export Controls program (P0047) that writes the F0047 table as follow:

Trans Type	Or Ty	Disply Seq	Object Name	Version	Function Name	Function Library	Execute For Add	Execute For Upd	Execute For Del	Execute For Inq	Flat File Exp Mode	Ext DB Exp Mode	Ext API Exp Mode	Launch Immediately
JDEWO	WO	1	R4801Z1X	XJDE0001			1	1	0	0	0	0	0	1

For this example, whenever data gets added into Work Order Header table (F4801), the defined UBE Outbound Work Order Extraction (R4801Z1X), version XJDE0001 will be executed.
If Launch Immediately is set (to '1'), R4801Z1X|XJDE0001 will be executed whenever a new record is inserted into SVM900.F986113 via Interoperability Generic Outbound Subsystem UBE (R00460).

Execution

Test Case Scenario: whenever a certain work order gets created / updated this information is to be transferred to a 3rd party software based on Outbound Work Order Header table (F4801Z1).

1. Set / verify the Processing Option # 1. Transaction Type in Interop tab to 'JDEWO'.

2. Create a new work Work Order, for instance through Manufacturing Work Order Processing (P48013).

3. Verify that F4801Z1 file gets populated and a single row of data is inserted into SVM900.F986113 as below.

Outbound Work Order Header file (F4801Z1)

User ID	Batch Number	Transaction Number	Line Number	Doc Ty	Trans Type	Translation Format	Tran Date	Dir Ind	# Lines	S P	Trading Partner	Tr Ac	Or Ty
SDONGMYE	0	125918		WO	JDEWO			2	0			02	WO
SDONGMYE	0	125919		WO	JDEWO			2	0			02	WO

Subsystem Job Master table (SVM900.F986113)

Program ID	Version	JOBNBR	JOBSTS	Opt Cd	EXEHOST	ORGHOST	ENHV	User ID	BLOB
R00460	XJDE0001		R	W	DNVMGSC29	DNVMGSC29	JPD900	SDONGMYE	S.D.O.N.G.M.Y.E.\|.0.\|.1.2.5.9.1.8.\|.2.\|.J.D.E.W.O.\|.W.O.\|.0.2...
R00460	XJDE0001		R	W	DNVMGSC29	DNVMGSC29	JPD900	SDONGMYE	S.D.O.N.G.M.Y.E.\|.0.\|.1.2.5.9.1.9.\|.2.\|.J.D.E.W.O.\|.W.O.\|.0.2...

BLOB information can be reviewed only through UTB.
If there is running process of R00460 - Interoperability Generic Outbound Subsystem UBE, above records may not be seen.

4. Run Interoperability Generic Outbound Subsystem UBE (R00460) or through continuously running process of subsystem job R00460. The Processing Log table (F0046) gets populated based on the definition in Data Export Contorl table (F0047).

Processing Log file (F0046)

User ID	Batch Number	Transaction Number	Line Number	Type Trans	Or Ty	SEQ	OBNM	Version	EDSP
SDONGMYE	0	125918	2	JDEWO	WO	1	R4801Z1X	XJDE0001	N
SDONGMYE	0	125918	2	JDEWO	WO	1	R4801Z1X	XJDE0001	N

R00460 can be a continuously running process or may be submitted manually.

5. Verify the jobs triggered by subsystem kernel and processed by queue kernel, UBE kernel and callobject kernel.

Job Control Status Master table (SVM900.F986110)

Submit Type	Queue	Queue Type	Status	Description	Priority	Type	User	Job Details	Host	Job #	Environment	Origination Host	Process ID
BV	QBATCH	01	E	Done	5	UBE	SDONGMYE	R4801Z1X_XJDE0001_90485_PDF	DNVMGSC29	90485	JPD900	DNVMGSC29	1580
BV	QBATCH	01	E	Done	5	UBE	SDONGMYE	R4801Z1X_XJDE0001_90482_PDF	DNVMGSC29	90482	JPD900	DNVMGSC29	1580
BV	QBATCH	01	P	Processing	5	UBE	SDONGMYE	R00460_XJDE0001_90481_PDF	DNVMGSC29	90481	JPD900	DNVMGSC29	1580

R4801Z1X gets called SYNCHRONOUSLY through R00460.
If possible, do not set Launch Immediately flag through P0047.
Rather handle it through R00461.
Since R00460 is subsystem process, only one process ID is to be assigned).

Subsystem Job Master table (SVM900.F986113)

Job Name	Version	Job Type	Job Status	Host	Environment	Origination Host	User	Job #
R00460	XJDE0001	S	R	DNVMGSC29	JPD900	DNVMGSC06	SDONGMYE	90481

6. Purge the records from F4801Z1 through Outbound Work Order Purge (R4801Z1P)

Note:

- BLOB information from F986113 is made up of index fields of target table F4801Z1.
- User ID, Batch Number, Transaction Number, Transaction Direction, Transaction Type, Order Type and Transaction Action.
Review relationship among tables written above.
- Multiple kernels are to be used for this implementation so in your hitting any error you may debug by turning log for a specific kernel.

Additional details on the functionality provided by Interoperability Generic Outbound Subsystem UBE (R00460) can be found under the following solutions: E1: Interop: FAQ on R00460 - Document 1334253.1 and E1: 40: Interoperability JDEIL and Inventory Transaction - Document 1334242.1.

For detailed information on interoperability refer pdf implementation guide JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange 8.12 and 9.0 Document 945544.1.