Understanding PeopleSoft CRM-Related Bill By Fields

When integrating PeopleSoft CRM and Transaction Billing Processor with Billing, PeopleSoft recommends that you populate the following bill-by fields to enable the Billing Interface to group invoices according to PeopleSoft CRM-specific transactions (such as service order, case ID, and so forth).

Note:

These fields are not available in bill entry, do not appear in bill inquiry, have no exposure in the 360-degree view, and do not appear on invoices. Depending on the invoice format you select, you can display this information on invoices using bill notes.

Field Description Notes

SO_ID

Service Order ID.

This is a 10-character field.

BUSINESS_UNIT_RF

Field Service Business Unit.

Field Service Business Unit is a key for service orders.

This is a 5-character field.

SOURCE_REF_NO

Reference Number

Populate this field with any generic reference number, and use this field in conjunction with the SOURCE_REF_TYPE and SOURCE_REF_KEY fields.

This is a 35-character field.

SOURCE_REF_KEY

Reference Key

Populate this field with any generic reference key. For example, you can populate this field with a business unit, set ID, or any other key value.

Use this field in conjunction with the SOURCE_REF_NO field.

This is a 5-character field.

SOURCE_REF_TYPE

Reference Type

Populate this field with any generic reference type that identifies the generic reference number (SOURCE_REF_NO). Initial translate values for this field are:

  • 001: CRM Agreement.

  • 002: CRM Case.

  • 003: CRM Order.

  • 004: CRM Service Order.

This is a 3-character field.

The following rules are used by the CRM products to populate these fields:

  • To pass an agreement number to PeopleSoft Billing, the system concatenates the agreement number and renewal number, and uses this value to populate the SOURCE_REF_NO field. The SOURCE_REF_KEY field is populated with the agreement set ID, and the SOURCE_REF_TYPE field is populated with the translate value for CRM Agreement.

  • To pass a case ID to PeopleSoft Billing, the system populates the SOURCE_REF_NO field with the case ID value, the SOURCE_REF_KEY field with the case business unit, and the SOURCE_REF_TYPE field with the translate value for CRM Case.

  • To pass an agreement number and a case ID to PeopleSoft Billing, the system populates the SOURCE_REF_NO field with the case ID value, the SOURCE_REF_KEY field with the case business unit, and the SOURCE_REF_TYPE field with the translate value for CRM Case. The agreement number is passed to Billing in an invoice note.

  • The PeopleSoft CRM Order Capture application populates the following fields:

    • SOURCE_REF_NO, with the order number.

    • SOURCE_REF_KEY field, with the order capture business unit.

    • SOURCE_REF_TYPE, with the translate value for the PeopleSoft CRM order.

  • To pass a service order to PeopleSoft Billing, the system uses the service order number to populate the SO_ID field, and the BUSINESS_UNIT_RF field with the service order number business unit. Additionally, the SOURCE_REF_NO field is populated with the service order number, the SOURCE_REF_KEY field with the field service business unit, and the SOURCE_REF_TYPE field with the translate value for CRM Service Order.

Note:

Whenever the SOURCE_REF_NO field is populated in the Billing Interface, the SOURCE_REF_TYPE field must also be populated. Additionally, if there is no value for the SOURCE_REF_NO field, then the SOURCE_REF_TYPE and SOURCE_REF_KEY fields must be left blank as well.

Because PeopleSoft CRM can pass credit card transactions to PeopleSoft Billing, you should include Payment Method with the bill-by fields you use for PeopleSoft CRM.

Related Topics