APVENEXT or CPINVXRF File Not Defined in DDF40 Directory

Release: 09/23/2021
Version: 8.5

QWhen printing a PO this morning I received the following error.

DDF Error Trying to Create File
APVENEXT: File not defined in DDF40 directory.



A - This is a one-time message unique to Elliott 8.5 and it is unlikely that you need to access this table through the SQL relational engine. Therefore you can ignore it.  The nature of the issue is APVENEXT is a new table added in September 2021 for the Elliott 8.5 release. During the printing of POs, the system detects that  APVENEXT.BTR does not exist and creates the BTR automatically. Before creating APVENEXT.BTR, Elliott will look up the DDF definition for this table and find it is not defined. Therefore, the system displays this message.

In addition to APVENEXT during PO printing, you may also a receive similar message for CPINVXRF during invoice printing.  The DDF files that the system tries to look up are in the <ElliottRoot>\Bin85\DDF40 folder.  In Elliott 8.5, during update installation, by default the installation doesn't update DDF files since it might conflict with the PSQL database engine relational database.

Starting with Elliott 8.6, the DDF files for the PSQL database relational engine will reside in the  <ElliottRoot>\Bin86\DDF40\STDDDF folder. Therefore, Elliott 8.6 installation will always update DDF files in the  <ElliottRoot>\Bin86\DDF40 folder without conflicting with the PSQL engine.  Therefore, this is a unique problem that occurs in Elliott 8.5 only.

In addition to to APVENEXT or CPINVXRF, you may receive the same kind of message one time for other files system consider as work file.  This may happen even for Elliott 8.6.  For example, if you use New Item CSV File Import for the first time, you may receive the following message:
    IMKITWRK: File not defined in DDF4 directory.

This is a normal message and you can simple click OK and ignore it. 

Our current logic will complains for files if not defined in DDF when open I-O where system need to create it for the first time.  Except we won't complain for the followings scenarios:
  1. File with "LCK" in bytes 3-5 of the base file name.
  2. VTSREG4 - Vertex
  3. File with Open OUTPUT.  Typically, Elliott will Open OUTPUT (instead of I-O) with a work file and Elliott won't complain if DDF is not defined in that case.  IMKITWRK is an exception where we open I-O instead of output in New Item CSV Import Program.
EMK

Feedback and Knowledge Base