E1: 37: P3711Z1 Interoperability and Quality Management
(Doc ID 1555603.1)
Last updated on MAY 04, 2020
Applies to:JD Edwards EnterpriseOne Quality Management - Version XE and later
Information in this document applies to any platform.
This document explain Interoperability in the JD Edwards EnterpriseOne Quality Management System.
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
|Additional Comments for Control Columns|
|Required Data Columns|
|Frequently Used Optional Data Columns|
|Additional Comments for Optional Columns|
|Frequently Asked Questions|
|Question 1: In the Test Results – Unedited Transaction Table (F3711Z1), why must the Business Unit (MCU) and Business Unit 2 (MCU2) fields be populated?|
|Question 2: Is it possible to use P3711Z1/R3711Z1I to change existing lot test results in the F3711 table?|
|Question 3: Why do duplicate records display in the Test Results Table (F3711) when R3711Z1I is run twice over Change records?|
|Question 4: Why are the lot effectivity date fields blank in the Work Order Master Table (F4108) when creating lots to test in the Test Results Transaction program (P3711Z1)?|
|Question 5: Will R3711Z1I update the Lot and Location Lot Status (LOTS) values based on the processed results?|
|Question 6: Is there a way to record the machine number on which a test was performed using the F3711Z1?|