My Oracle Support Banner

E1: 31: Inbound Inventory Issues Transaction (R31113Z1I) / Work Order Inventory Issues Interoperability (Doc ID 1169303.1)

Last updated on SEPTEMBER 11, 2023

Applies to:

JD Edwards EnterpriseOne Shop Floor Control - Version XE and later
Information in this document applies to any platform.

Purpose

This document explains the use of Interoperability (Z file processing) for Work Order Inventory Issues for Inbound and Outbound transactions. Basic setup including control columns, required data columns, and frequently used optional data completions to complete the transactions are included. The specific logic to distinguish between Planned and Unplanned issues is also detailed in the document.

 
On the inbound side, this transaction is used to update EnterpriseOne (E1) tables with inventory issue information.
On the outbound side, this transaction is used to generate records that can be used by a third party to update their system with the inventory issue information.

Overview

Work Order Inventory Issues transactions are used to determine the actual quantities of ingredients that are used in the production process according to the routing and parts list instructions for the work order.

On the inbound side, this transaction is used to update EnterpriseOne (E1) tables with inventory issue information.

On the outbound side, this transaction is used to generate records that can be used by a third party to update their system with the inventory issue information.

The permanent E1 tables primarily affected by this transaction are the Work Order Parts List table (F3111), Item Ledger File (F4111) and the Item Location File (F41021).

Related Knowledge Content

To further understand the key facts on the functionality provided by the interactive Work Order Inventory Issues (P31113) program, refer the following:

E1: 31: P31113 Understanding Manufacturing Inventory Issues - Document 625996.1.
E1: 31: P31113 Inventory Issues FAQ - Document 760520.1.
E1: 31: P3111/P31113 Inventory Issues & Parts List Common Error Messages - Document 629931.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.

Scope

Users of EnterpriseOne's Manufacturing Shop Floor Control module will find this bulletin helpful when testing the R31113Z1I interoperability functionality.

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
 Overview
 Related Knowledge Content
Scope
Details
 Relationships to Other Transactions
 Transaction-Specific Instructions
 Inbound Transactions - Outbound Work Order Parts List (F3111Z1) Table
 Control Columns
 Required Data Columns
 Frequently Used Optional Data Columns
 Processing Inventory Issues Transactions (R31113Z1I)
 Outbound Transactions - Table F3111Z1
 Issuing from Multiple Locations, Planned and Unplanned Issues using Inbound Inventory Issues Transaction (R31113Z1I) UBE
 Test Case
 Frequently Asked Questions
 Question 1.  Why Fixed/Variable Quantity (FORQ) field on F3111Z1 table is converting from "V" to "F" in the F3111 table after running the UBE R31113Z1I?
 Question 2.  What ID should appear in the cardex of the IM transaction? Is it the User ID in F3111Z1 or the User ID of the person who ran R31113Z1I?
 Question 3. Why TRQT value in the F3111Z1 shows the accumulated issued quantity?
 Question 4:  Will the system generate a batch number on an Inventory Issue (JDEII) type transaction P3111Z1?
 Question 5:  Does the R31113Z1I UBE work with service work orders and update the F31171 extension table?
 Question 6:  Why does batch program R31113Z1I not populating the User Reserved fields in table F3111?
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.