PeopleSoft Billing Implementation Tasks
PeopleSoft Setup Manager enables you to review a list of setup tasks for the organization for the products that you implement. The setup tasks include the components that you must set up, listed in the order in which you must enter data into the component tables, and links to the corresponding documentation.
PeopleSoft Billing also provides component interfaces to help you load data from the existing system into Billing tables. Use the Excel to Component Interface utility with the component interfaces to populate the tables.
This table lists all of the components that have component interfaces:
Component |
Component Interface |
Reference |
---|---|---|
Charge Code |
BI_CHARGE_CI |
|
Discounts and Surcharge Code |
BI_DISC_SUR_CI |
|
Standard Note |
STANDARD_NOTE |
See Standard Notes Page. |
Sales and Use Tax Authorities |
TAX_AUTHORITY_CI |
As your organization processes the continuous stream of transactions within your PeopleSoft system, the events and notifications framework enables you to monitor the transaction flow and alert your organization to any errors, changes, and stalled transactions.
The messages generated by the events and notifications framework can notify you of the problem, give you a detailed description of the issue, and provide a link to the PeopleSoft page where you can resolve it. One of the ways to use the events and notifications framework is to create PeopleSoft Queries on one or more PeopleSoft tables, add the alert using the Alert Setup component, and then complete the alert setup steps. This method enables you to monitor data within a PeopleSoft table; for example, searching for stalled transactions, instead of looking at the results of a PeopleSoft process. When the Alerts process (EOEN_ALERT) is run, the PeopleSoft table is queried and the alert messages can be generated. These messages can be routed to the appropriate person (PeopleSoft user or non-PeopleSoft user) using an email, a PeopleSoft worklist entry, an XML message, or the PeopleSoft Notification Dashboard.
For the PeopleSoft Billing application, sample data includes the following PeopleSoft queries that have been setup to work with the events and notifications framework. These queries may require minor modifications to work in your environment. In addition, your billing specialist must be setup with a user profile to receive email. You can copy and alter these queries to create new alert messages.
Query |
Process Name |
Process Category |
Description |
---|---|---|---|
BI_CRCARD_ERRORS |
BI_CREDIT_CARD |
ERROR_TRANSACTIONS |
Generates alert messages for credit card transactions that are in error. This PeopleSoft Query gives detailed information about each transaction using the INTFC_CRCARD staging table and the Bill Header table (BI_HDR). |
BI_CRCARD_ERR_SUM |
BI_CREDIT_CARD |
ERROR_SUMMARY |
Generates alert messages for credit card transactions that are in error. This PeopleSoft Query uses the INTFC_CRCARD staging table to display data summarized by business unit, amount, and currency. |
BI_FINALIZATION_ERRORS |
BI_INVOICE |
ERROR_TRANSACTIONS |
Generates alert messages for billing finalization errors (ERROR_STATUS_BI) in the Bill Header table (BI_HDR). |
BI_FINALIZATION_ERR_SUM |
BI_INVOICE |
ERROR_SUMMARY |
Generates alert messages for billing finalization errors (ERROR_STATUS_BI) in the Bill Header table (BI_HDR). This query displays data summarized by business unit, amount, and currency. |
BI_INTFC_BI_ERROR |
BI_INTERFACE |
ERROR_TRANSACTIONS |
Generates alert messages for billing interface errors (ERROR_STATUS_BI) in the Billing Interface table (INTFC_BI). |
BI_PENDING_BILLS |
BI_INVOICE |
PENDING_TRANSACTIONS |
Generates alert messages for invoices that have not been finalized after a certain number of days. Note: Define the number of days using the Workflow Batch Parameters page. |
BI_PENDING_BILLS_CON |
BI_INVOICE |
PENDING_TRANSACTIONS_CONS |
Generates alert messages for consolidated invoices that have not been finalized after a certain number of days. Note: Define the number of days using the Workflow Batch Parameters page. |
BI_PENDING_BILLS_SUM |
BI_INVOICE |
PENDING_TRANSACTIONS_SUMMARY |
Generates alert messages for invoices that have not been finalized after a certain number of days. This query displays the invoices summarized by business unit, amount, and currency. Note: Define the number of days using the Workflow Batch Parameters page. |
BI_PENDING_CON_BILLS_SUM |
BI_INVOICE |
PENDING_TRANS_SUMMARY_CONS |
Generates alert messages for consolidated invoices that have not been finalized after a certain number of days. This query displays the consolidated invoices summarized by business unit, amount, and currency. Note: Define the number of days using the Workflow Batch Parameters page. |
BI_PENDING_CRCARD |
BI_CREDIT_CARD |
PENDING_TRANSACTIONS |
Generates alert messages for credit card transactions that have not been processed after a certain number of days. Note: Define the number of days using the Workflow Batch Parameters page. |
BI_PENDING_CRCARD_SUM |
BI_CREDIT_CARD |
PENDING_TRANSACTIONS_SUMMARY |
Generates alert messages for credit card transactions that have not been processed after a certain number of days. This query displays the credit card transactions summarized by business unit, amount, and currency. Note: Define the number of days using the Workflow Batch Parameters page. |
BI_PENDING_WRKSHEET |
BI_WORKSHEET |
PENDING_TRANSACTIONS |
Generates alert messages for billing worksheets that have not been processed after a certain number of days. Note: Define the number of days using the Workflow Batch Parameters page. |
BI_WORKSHEET_ERRORS |
BI_WORKSHEET |
ERROR_TRANSACTIONS |
Generates alert messages for billing worksheets that are in error. |
BI_PENDING_INTFC |
BI_INTERFACE |
PENDING_TRANSACTIONS |
Generates alert messages for billing interface transactions (INTFC_BI table) that have not been processed after a certain number of days. Note: Define the number of days using the Workflow Batch Parameters page. |
See Workflow Batch Parameters Page.
Notification Composer Framework
Oracle PeopleSoft delivers Notification Composer Framework in Enterprise Components to manage the setup and administration of notifications in one central location. Once you have adopted the Notification Composer feature, you must use it to create new notifications and manage your existing notifications.
These PeopleSoft Billing business processes, which are delivered with FSCM Update Image 49 or later must use Notification Composer:
Billing Invoice Courtesy Copy
Billing Invoice Customer Contact
Credit Invoice Approval
For more information about Notification Composer Framework, see Understanding Notification Composer.
Other Sources of Information
In the planning phase of the implementation, take advantage of all PeopleSoft sources of information, including the installation guides, table-loading sequences, data models, and business process maps. A complete list of these resources appears in the preface in the PeopleSoft Application Fundamentals documentation, with information about where to find the most current version of each.
See the product documentation for PeopleTools: Setup Manager and PeopleTools: Component Interfaces