Understanding Accounts Payable Constants

Constants provide a basic framework for how your JD Edwards EnterpriseOne Accounts Payable system works, based on your business needs. Generally, one person sets up all constants. It is recommended that you do not change constants after they are set up because this might produce undesirable results. It is also recommended that you ensure that only authorized personnel can access and change accounts payable constants.

Note:

Settings for constants are loaded during software initialization. Therefore, for the settings to take effect, you must restart the system after you define constants.

The accounts payable constants are stored in the General Constants table (F0009).

Constants for the JD Edwards EnterpriseOne Accounts Payable system include these options:

• Batch Control Required

  The Batch Control Required constant enables you to specify whether to track the total number and amount of a batch of vouchers. Turning on this constant enables you to verify the total amount expected against the total amount entered immediately after you enter each batch.

• Manager Approval of Input

  The Manager Approval of Input constant enables you to specify whether management approval of batches is required before batches can be posted.

• Automatic Offset Method

  The Automatic Offset Method constant enables you to specify how the system makes offsetting entries to the Accounts Payable liability and discount accounts when you post vouchers to the general ledger.

  Three offset methods are available:

  B: Batch offset

  S: Single offset per pay item

  Y: One offset per document

  You must consider the intercompany settlement method selected in General Accounting Constants when deciding on the automatic offset method to select.

  For intercompany settlement method 1 (Hub method), you can use any of the offset methods noted previously.

  For intercompany settlement method 2 (Detail method), you can use any of the offset methods noted previously.

  For intercompany settlement method 3 (Configured Hub method), you can use offset method S or Y, but not B.

• Invoice Number Editing (Release 9.2 Update)

  The Invoice Number Editing constant enables you to set up your system so that it notifies you when it detects duplicate invoices. Duplicate invoices might occur when a supplier invoice is accidentally entered twice. This constant also notifies you when it detects duplicate invoice number in a voided voucher. You can enter one of these codes:

  • H: Hard error upon duplication of an invoice number excluding voided transactions.

    By selecting option H, you can force users to enter a unique invoice number for each voucher. This allows you to reuse the invoice number in voided vouchers.

  • I: Hard error upon duplication of an invoice number including voided transactions.

    By selecting option I, you can force users to enter a unique invoice number in each voucher, including voided vouchers.

  • N: Do not edit for duplication.

  • Z: Warning upon duplication of an invoice number including voided transactions.

  • Y: Warning upon duplication of an invoice number excluding voided transactions.

• Aging Days for Accounts Payable

  The columns on your aging reports are calculated based on the number of days in each time interval that you set up.

See also:

• "Setting Up Batch Approval and Post Security" in the JD Edwards EnterpriseOne Applications Financial Management Fundamentals Implementation Guide.

• "Using Batch Control to Manage the Entry Process" in the JD Edwards EnterpriseOne Applications Financial Management Fundamentals Implementation Guide.