Cache/Work File (workfile) in Procurement

Purpose of Document

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.

Question 1 : What are the temporary tables used in processing Procurement?

Answer 1 : The tables listed below can hold transactional data in the memory or in the database but F43121Z and F4314Z are purely used for cache (long pointer data structure to hold PO receipt and Voucher Match),

• F4301Z - PO Header Work File
• F4311Z - Purchase Order Generator File
• F43121Z - Receiver workfile (Does not write physical table/file in the routine)
• F4314Z - Voucher Match Selection File (does not write physical file)

cf.,

• R4311Z1I (PO Unedited Transaction Inbound Processor)
• R07071 (EDI Receiving Advice Edit/Create - Purchasing)
• F4301Z1 - Purchase Header Work File
• F4311Z1 - Purchase Order Detail Unedited Transaction Table
• F43121Z1 - Receipts Unedited Transaction Table

Question 2 : Why are temporary tables used in Processing Purchase Order?

Answer 2 : The reason is to optimize performance and data integrity. For example, if a huge volume of data has to be handled, writing a temporary file can be more cost effective (by avoiding round trips to database server) than making use of cache as physical memory which has its own limitation.

This calculation assumes the keys and indices to a certain table is left unchanged. If keys or indices are changed, the cache should still work, however the following calculation will be off. Approximately 193K will be used by the cache that is non-data related. Plus, the size of memory will be equivalent to the size of data in a certain table. In Unicode and 2 bytes Asian language, it requires two bytes per character. That is why, the usage of memory in Unicode environment will be higher than single byte environment.

For example (based on E1 application release 9.1),

F4301Z = (in bytes) 193000 + (2750 * Number of rows)
F4311Z = (in bytes) 193000 + (5794 * Number of rows)
F43121Z = (in bytes) 193000 + (5581 * Number of rows)
F4314Z = (in bytes) 193000 + (6464 * Number of rows)
: Note that the size of data can be retrieved by checking F4301Z.h in include folder.

Question 3 : How does system determine whether to write cache or workfiles (work files)?

Answer 3: Possible parameters are as follows:

Values for parameter:

1 - Write Work File
2 - Write Cache

Question 4: Is there a diagram to represent the flow of data through voucher match?

Answer 4: Refer below flow chart

Question 5: If there is data in these tables can it be purged?

Answer 5: Yes the data from these work file tables (F4301Z, F4311Z, F43121Z, F4314Z) can be purged.
In general, these files are made up of columns:

• CTID - ComputeID
• PEID - ProcessID
• TCID - TransactionID

Question 6 : Can the parameters to write to cache or a workfile be changed?

Answer 6 : Do NOT change any parameters as it will cause memory error across system and you may experience slower performance.

Question 7 : Table (Data) Structure has been changed through baseline ESUs, what is the follow-up action?

Answer 7: If there is any change in Table Structure, the table needs to be generated through EnterpriseOne OMW tools. Usually this has to be described in Special Instruction of baseline ESU that has been installed. By generating table which synchronize table specification in your Database (Update metadata in your DB), this action is MANDATORY.
In the log, there is cache written in F42UI002 but we cannot find this table. Is this a valid table ID? If so where can we find it?
Note: F42UI002 is just data structure to hold extended value of Sales Order Header Information. This data structure is defined at B4202090.h file and is referenced by B4200310.h, B4200311.h and B4200312.h files. Upon compilation JDE will assign memory for this data structure.

Question 8: Which applications can create a purchase order?

Answer 8 :

Multiple applications can create/update purchase order, simplified object list is,