E1: 43: Cache/Work File (workfile) in Procurement (F4301Z, F4311Z, F43121Z, F4314Z) (Doc ID 1463725.1)

Last updated on APRIL 25, 2023

Applies to:

JD Edwards EnterpriseOne Procurement and Subcontract Management - Version XE and later
Information in this document applies to any platform.

Purpose

This note is to discuss cache and workfile in EnterpriseOne procurement. This note is a trouble shooting guide when the issue is coming from cache or work file.

Document discusses Work Files in Procurement (F4301Z, F4311Z, F43121Z and F4314Z) based on the list of applications below,

P4310 - Purchase Orders
P43032 - Purchase Order Generator
P43060 - Order Release
P43101 - Purchase Order Workbench

Note that Purchase Order can be created/updated through multiple applications (including Sales and Manufacturing and so on). For this example, any routine which writes F4301 (Purchase Order Header)/F4311 (Purchase Order Detail) are defined as purchase order.

In creating Purchase Order, temporary tables (namely Work File/Workfile/WF) such as F4301Z (PO Header Work File), F4311Z (Purchase Order Generator File), F43121Z (Receiver workfile) and F4314Z (Voucher Match Selection File) can be used to hold data temporarily before it gets committed to Purchase Order Header/Detail, PO Receipt and Voucher Match.

In this note, workfile/work file stands for physical tables whereas cache stands for memory/cache or data structure. In purchase order processing cache is to be used heavily because (as temporary table stored value for limited times) cache can be referenced in any other form/application till it gets terminated.

Unlike Sales Order, only P43060 (Order Release/Generate) has implementation to write work file to support consolidation (because lines can not be consolidated with cache). However R4311Z1I (PO Unedited Transaction Inbound Processor) shall not utilize work file unlike R47010 (EDI Inbound Purchase Order Edit/Create). In your running P43060 if you specify line consolidation option, which writes F4301Z/F4311Z.