Understanding Enabling the Buyer Direct Model

Setting up PeopleSoft Payables and eSettlements to work together using the PeopleSoft eSettlements Buyer Direct model involves creating a PeopleSoft eSettlements buyer for each PeopleSoft Payables business unit and a PeopleSoft eSettlements supplier for each active PeopleSoft Payables supplier. You can perform these operations using an Application Engine process to complete the enabling of all your existing PeopleSoft Payables business units and suppliers at once, in a batch, and you can also enable them online one at a time. Other topics discuss the latter method in detail.

Buyer Template

The administrator must create a buyer template to populate the required configuration tables when creating a new buyer. This template includes all required control values and is stored by SetID. Each buyer must be associated with a template, and you can use one template for the creation of many buyers.

You establish the information when you create your business units in PeopleSoft Payables, but you still must create a complete buyer template in PeopleSoft eSettlements. The only template field used in further processing is Account, which appears by default on self-service and XML invoices, if no other default values are found.

Enable PeopleSoft Payables Business Units and Suppliers for Buyer Direct Application Engine Process

The Enable AP BUs & Suppliers for BD (enable payables business units and suppliers for buyer direct model) Application Engine process (EM_ENABLE_BU) creates a PeopleSoft eSettlements buyer for each PeopleSoft Payables business unit, and a PeopleSoft eSettlements supplier for each PeopleSoft Payables supplier. For buyers, the process performs the following:

  1. Creates PeopleSoft eSettlements buyers by populating the Buyer Registration table (EM_BUY_REG_TBL) with all active PeopleSoft Payables business units that are not already registered as PeopleSoft eSettlements buyers.

  2. Populates four levels of buyer approval amounts in the Buyer Approval Amounts table (EM_BUYER_APPR) for each PeopleSoft Payables business unit.

    Populates the first row with unlimited invoice header approval amounts and each subsequent row with a value of 0.0. You must enter the actual approval amounts manually on the Review Buyer Details - Notifications and Approvals page, as well as assign approvers for each approval level by selecting from a list of valid PeopleSoft eSettlements roles.

  3. Populates the Business Unit Operator ID Security table (SEC_BU_OPR) for every PeopleSoft Payables business unit for user IDs that are associated with a role attached to any of the following role types: buyer user, buyer administrator, buyer accountant, or operational approver.

    Note: If the Update Security Setups SQR process (FIN9001) has been run with business unit security selected, the Enable AP BUs & Suppliers for BD process will assume that all PeopleSoft Payables business units already exist in the Business Unit Operator ID Security table and will not add a new row to the table. Therefore, if you have added any PeopleSoft Payables business units since you last ran the Update Security Setups SQR process, the Enable AP BUs & Suppliers for BD process does not add them to the Business Unit Operator ID Security table even though they do not already exist on the table. You must, in that case, add those business units to the Business Unit Operator ID Security table manually.

  4. Populates the Review Buyer Details - ChartField Configuration page with No Access for all ChartFields.

    Therefore, to give access to their suppliers, the buyer must access the page and select Display Only or Editable for each ChartField the buyer wants to make available to its suppliers.

For suppliers, the process works as follows:

  1. Creates PeopleSoft eSettlements suppliers by populating the PeopleSoft eSettlements Supplier Registration table (EM_VENDOR_REG) with all active PeopleSoft Payables suppliers.

    Once the supplier is created, all of their locations display in supplier registration—all of a supplier's locations are registered once the supplier is registered. If an existing supplier has a remit to supplier (location), that information also displays in supplier registration.

  2. Grants PeopleSoft eSettlements administrators update access to all supplier details, by populating the Supplier User table (VENDOR_USER) with all active PeopleSoft Payables suppliers for those users assigned to roles with a system administrator role type.

  3. Calls the Populate User Currency Prefs Application Engine process (EM_USRCURPRF) to populate the User's Current Preferences table (EM_USR_CUR_PREF) with the currency rate type entered on the run control.

Note: If financial sanctions validation is enabled at the installation level or at the bank level, the Enable AP BUs & Suppliers for BD process validates the supplier against any financial lists (for example, the Specially Designated Nationals (SDN) list), and lists the suppliers whose financial sanctions status is Review or Blocked on the Message Log page of the Process Monitor. The system still creates suppliers from these suppliers, however, the system does not allow payments to suppliers with a financial sanctions status of Review or Blocked.

Financial sanctions validation is discussed in detail in these topics and in PeopleSoft Source-To-Settle Common Information.