Skip to content

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 and you can ignore the message.  APVENEXT is a new table added in September 2021 for the Elliott 8.5 release.  Purchase Order Print 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.  If the table is not defined in the DDF, the system displays this message.

In addition to APVENEXT, you may receive a similar message for CPINVXRF when printing invoices.  Elliott looks for the DDF files in the <ElliottRoot>\Bin85\DDF40 folder.  The Elliott 8.5 update does not update the DDF files by default since it might conflict with the PSQL relational engine database.

This problem is unique to Elliott 8.5 since the DDF files for the PSQL database relational engine will reside in the <ElliottRoot>\Bin86\DDF40\STDDDF folder starting with Elliott 8.6.  The Elliott 8.6 update will always update the DDF files in the <ElliottRoot>\Bin86\DDF40 folder to avoid a conflict with the PSQL relational engine.

In addition to APVENEXT and CPINVXRF, you may receive the same kind of message for other work files, even in Elliott 8.6.  For example, the first time you run New Item CSV File Import you may receive the following message:
    IMKITWRK: File not defined in DDF4 directory.

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

This message occurs for files not defined in the DDF and the physical file does not exist so an Open I-O will create it for the first time.  The following scenarios are exceptions to this rule:
  1. Files with "LCK" in positions 3-5 of the base file name.
  2. VTSREG4, a file used by Vertex.
  3. Files created by the Open Output command.  Typically Elliott will use Open Output for a work file, but IMKITWRK is an exception where we use Open I-O in New Item CSV File Import.

Feedback and Knowledge Base