Configuring AP Feed Files

Overview

A custom AP feed file comes at the end of the generic check creation process. These feeds are generated out of the process queue as part of the same “Record Check” process which actually creates the CHECK, REMITBAT, and REMITDTL records.

Two types of feeds exist:

a feed created on a per-check basis

a feed which spans all checks in one “check generation run”

To configure AP Feeds:

1 Open the CUSTSYS.MDB.

2 Open the CUST_EVNT table.

3 Type the required entry in the following fields:

Field	Required Entry
OWNER_KEY	The OWNER_KEY (as appropriate for the customer).
EVNT	“Payment”
EVNT_SEQ_NUM	An integer which simply uniquely identifies the record.
EVNT_CLASS	“AP Feed” or “AP Feed Combined Checks” depending on whether a feed file per-check, or feed file per-process (spanning checks) is desired, respectively.
IN_USE_FLAG	Currently ignored, but will be used in the future.
<remaining fields>	Currently unused.

4 If the CUST_EVNT record you want is present, then type the required entry in the following fields for the CUST_RPT records:

Field	Required Entry
OWNER_KEY	The OWNER_KEY (as appropriate for the customer).
CUST_RPT_KEY	“AP Feed File” or “AP Feed Combined Checks File” depending on the value given for EVNT_CLASS in the CUST_EVNT table.
RPT_INST_NUM	An integer specifying the instance of the report. Multiple feeds of differing formats may also be generated.
CUST_RPT_DESC	A name given to the generated feed by which the customer may identify with it. This is used in a message box as the end of the process.
SQL MEMO	A function call to be EVALuated. This will typically be a call to “Generic_Cust_Feed_File( ... )”, but could be a call to a custom coded routine.

<remaining fields>

Currently unused.

See Also

Generic_SQL_Export Function