Procurement Card Configuration

The Procurement Card Configuration (PCNFG) table stores the procurement credit card configuration setup data that may be used to process a Procurement Card transaction. Use of this table is optional. If left blank, it will not be used by the associated Procurement Card reference tables, PR Transaction Type or PCard Chain process. This table has two sections:

  • General Information – This tab captures high level information about the Procurement Card configuration record selected.

  • Billing Cycle Information – This tab is used to designate individual billing cycles.  

Field InformationField Information

  • Infer Name from HRM – Controls whether the system infers the Name 1 field using employee data.

  • If set to Yes, the system retrieves Name 1 from the HRM record (or the non-HRM record if HRM data is unavailable), provided the employee is not a site employee and the card type is not a ghost card. If no employee data is found, Name 1 remains manually editable with a warning issued.

  • If set to No, inference does not apply, and users must manually enter the Name 1 field for all card types.

  • Name 1 Character Limit – Defines the maximum allowed length for the Name 1 field.

  • This is an integer field with a value greater than zero.

  • If the inferred name exceeds the configured limit, the system progressively shortens the format (for example, from full name to first name + last name, initials, or last name only) to fit within the limit.

  • For manually entered names, input is restricted to the set limit, trimming end characters if necessary.

  • Set Cardholder Name as Name 1 – Determines how the cardholder name is assigned.

  • If set to No, the cardholder name is inferred from the User Information (SCUSER) table using the cardholder ID.

  • If set to Yes, the cardholder name is directly set using the value stored in the Name 1 field.

These fields help ensure consistency in name inference, formatting, and assignment within the Procurement Card User Information (PRCUI) process.

To maintain this table, authorized users must manually enter individual billing cycles for each instance that a payment will be required. For instance, if a payment is required each month, you must enter a line into the Billing Cycle Information tab for each month of the Fiscal Year. This allows for flexibility in your payment schedules, and it allows you to easily change Scheduled Payment Dates for an individual month without changing that date for subsequent months.

The Infer Object on PRCUUAL  field determines the inference of Object and Sub Object values on the Unprocessed Procurement Card Activity (PRCUU) page. This field has two values, Commodity Object and Accounting Template.

  • When set to Commodity Object, the system, while loading the records on the PRCUU’s Accounting Line tab, infers Object and Sub Object values from the Commodity Object (COMMOB) table.

  • When set to Accounting Template, the system, while loading the records on the PRCUU’s Accounting Line tab, infers Object and Sub Object values from the Accounting Template (ACTPL) table.

The default value of the Infer Object on PRCUUAL field is Accounting Template. Refer to the “PRCUU – Accounting Lines” topic for more information on the inference of Object and Sub Object.