PeopleSoft Receivables 9.1 PeopleBook

Configuring Page Features

This chapter list prerequisites and discusses how to:

Change the default date on customer options records.
Increase the number of rows in a grid.
Change activity types.
Add user history IDs to setID and business unit history.

Prerequisites

Oracle provides a tool called PeopleSoft Application Designer to assist with modifying and editing PeopleCode to change display options or the appearance of PeopleSoft Receivables pages.

Before trying to modify page features, become familiar with Application Designer and PeopleCode basics.

Changing the Default Date on Customer Options Records

When you select the Bill To Customer, Ship To Customer, or Sold To Customer check box on the General Info page for a customer, the system automatically builds a corresponding Options record (CUST_OPTION) in the background. The Receivable Update Application Engine process (ARUPDATE) requires valid Options records to process each of these customer types.

By default, the system automatically populates option records with an effective date of the current date when you create an Options record. If you need to post receivables transactions with an earlier accounting date than the default effective date, you can change the default effective date to January 1, 1900, to ensure that the Receivable Update process finds a valid Bill To Options record to process the customer. To change the default date to January 1, 1900, make the following PeopleCode modifications.

Bill To Customer Options

To change Bill To Customer options using CUST_OPTION. CUST_ID.RowInsert PeopleCode:

Change the following code:

/* Default to the current date */
CUST_OPTION.EFFDT = %Date;

To this:

/* Default to '1900/01/01' */
CUST_OPTION.EFFDT = Date3(1900, 1, 1);

Ship To Customer Options

To change Ship To Customer options using CUST_SHIPTO_OPT.EFFDT/FieldDefault PeopleCode:

Change the following code:

…
When-Other
  CUST_SHIPTO_OPT.EFFDT = %Date;
End-Evaluate;

To this:

…
When-Other
  CUST_SHIPTO_OPT.EFFDT = Date3(1900, 1, 1);
End-Evaluate;

Sold To Customer Options

To change Sold To Customer options using CUST_SOLDTO_OPT.EFFDT/FieldDefault PeopleCode:

Change the following code:

…
When-Other
  CUST_SOLDTO_OPT.EFFDT = %Date;
End-Evaluate;

To this:

…
When-Other
  CUST_SOLDTO_OPT.EFFDT = Date3(1900, 1, 1);
End-Evaluate;

Increasing the Number of Rows in a Grid

This section provides an overview of row limits in grids and discusses how to increase the number of rows in a grid.

Understanding Row Limits in Grids

You may want to limit the number of rows that appear in grids on high-volume inquiry or worksheet pages, such as the worksheets for payments, maintenance, transfer items, drafts, and direct debits. Oracle delivers PeopleSoft Receivables with a default of 100 rows in the grid—the maximum number of rows that can be contained in the grid at one time. This is referred to throughout this documentation as a chunk or grouping of rows.

Page Used to Increase the Number of Rows in a Grid

Page Name	Definition Name	Navigation	Usage
Installation Options - Receivables	INSTALLATION_AR	Set Up Financials/Supply Chain, Install, Installation Options, Receivables	Define the maximum numbers of rows that appear at one time in inquiry and worksheet grids.

Increasing the Number of Rows in a Grid

Access the Installation Options - Receivables page (Set Up Financials/Supply Chain, Install, Installation Options, Receivables).

Increase or decrease the default of 100 rows that appears in a grid (chunking) by changing the value in the Max Number of Rows in Scrolls field. The change may affect performance, but the impact depends on other factors. The greater the number of rows in the grid, the longer the time for the pages to appear. Experiment to find the number that works best.

The limit of rows in a grid works in conjunction with the up and down arrow buttons on the pages. Given the default of 100 rows, if the search criteria returns 100 or fewer rows from the database, they are all available in the grid and the arrow buttons are invisible. If the search criteria returns more than 100 rows, use the arrow buttons to view the different chunks of 100 rows in the grid.

Changing Activity Types

The Unit Activity page and the Unit Activity report use the selections in the Activity Type and Activity Type/Origin/Bank Code fields on the System Functions 1 page to summarize the data and how to break it down.

To add more activity type categories:

In Application Designer, open the ENTRY_USE_TBL record.
In the record window that appears, select and right-click the SYS_TRAN_TYPE field.
Click View Translates.
Click ADD to add translate values.

Adding User History IDs to SetID and Business Unit History

If you add new user-defined history IDs, they do not automatically appear on history inquiry pages. You need to perform three tasks for them to appear.

This section discusses how to:

Modify view text for history IDs.
Modify views for the Customer History page.
Modify views for the Unit History page.

Modifying View Text for History IDs

To modify the view text:

Open the record that you want to modify in Application Designer.
In the SQL object window that appears, select the row for the CUST_HIST_ID field.
Right-click and select View PeopleCode.
Modify the PeopleCode.

Modifying Views for the Customer History Page

If you create queries that use a business unit, the new history ID appears immediately on the Customer History page. If the business unit field is left blank, the new history ID does not appear until these views are modified:

HIST_SI_SUM_DVW
HIST_SI_LSM_DVW
SUBC_SI_SUM_DVW
SUBC_SI_LSM_DVW

For example, to add a new history ID called WIDGET_SALES, change the view text on each of the views as shown here.

HIST_SI_SUM_DVW

Change the view text to:

SELECT SETID,
    CUST_ID,
    CUST_HIST_ID,
    FISCAL_YEAR,
    ACCOUNTING_PERIOD,
    SUM(HIST_AMT),
    SUM(HIST_WEIGHT),
    SUM(HIST_COUNT),
    CURRENCY_CD
FROM PS_CUST_HIST_SI_VW
WHERE CUST_HIST_ID IN ('SALES', 'WIDGET_SALES')
GROUP BY SETID, CUST_ID, CUST_HIST_ID, FISCAL_YEAR, ACCOUNTING_PERIOD, CURRENCY_CD

HIST_SI_LSM_DVW

Change the view text to:

SELECT H.SETID,
    H.CUST_ID,
    H.CUST_HIST_ID,
    H.FISCAL_YEAR,
    H.ACCOUNTING_PERIOD,
    SUM(H.HIST_AMT),
    SUM(H.HIST_WEIGHT),
    SUM(H.HIST_COUNT),
    CURRENCY_CD
FROM PS_CUST_HIST_SI_VW H
WHERE H. CUST_HIST_ID IN ('SALES', 'WIDGET_SALES')
 AND H.FISCAL_YEAR = 
     (SELECT MAX(FISCAL_YEAR)
       FROM PS_CUST_HISTORY
      WHERE BUSINESS_UNIT
             = H.BUSINESS_UNIT
      AND CUST_ID = H.CUST_ID
      AND CUST_HIST_ID = H.CUST_HIST_ID)
 AND H.ACCOUNTING_PERIOD =
     (SELECT MAX(ACCOUNTING_PERIOD)
       FROM PS_CUST_HISTORY
      WHERE BUSINESS_UNIT
              = H.BUSINESS_UNIT
      AND CUST_ID = H.CUST_ID
      AND CUST_HIST_ID = H.CUST_HIST_ID
      AND FISCAL_YEAR = H.FISCAL_YEAR)
GROUP BY H.SETID,
    H.CUST_ID,
    H.CUST_HIST_ID,
    H.FISCAL_YEAR,
    H.ACCOUNTING_PERIOD,
    H.CURRENCY_CD

SUBC_SI_SUM_DVW

Change the view text to:

SELECT SETID,
    CUST_ID,
    SUBCUST_QUAL1,
    SUBCUST_QUAL2,
    CUST_HIST_ID,
    FISCAL_YEAR,
    ACCOUNTING_PERIOD,
    SUM(HIST_AMT),
    SUM(HIST_WEIGHT),
    SUM(HIST_COUNT),
    CURRENCY_CD
FROM PS_SUBC_HIST_SI_VW
WHERE CUST_HIST_ID IN ('SALES', 'WIDGET_SALES')
GROUP BY SETID,
    CUST_ID,
    SUBCUST_QUAL1,
    SUBCUST_QUAL2,
    CUST_HIST_ID,
    FISCAL_YEAR,
    ACCOUNTING_PERIOD,
    CURRENCY_CD

SUBC_SI_LSM_DVW

Change the view text to:

SELECT H.SETID,
    H.CUST_ID,
    H.SUBCUST_QUAL1,
    H.SUBCUST_QUAL2,
    H.CUST_HIST_ID,
    H.FISCAL_YEAR,
    H.ACCOUNTING_PERIOD,
    SUM(H.HIST_AMT),
    SUM(H.HIST_WEIGHT),
    SUM(H.HIST_COUNT),
    H.CURRENCY_CD
FROM PS_SUBC_HIST_SI_VW H
WHERE H. CUST_HIST_ID IN ('SALES', 'WIDGET_SALES')
 AND H.FISCAL_YEAR = 
     (SELECT MAX(FISCAL_YEAR)
       FROM PS_CUST_HISTORY
      WHERE BUSINESS_UNIT
             = H.BUSINESS_UNIT
      AND CUST_ID = H.CUST_ID
      AND CUST_HIST_ID = H.CUST_HIST_ID)
 AND H.ACCOUNTING_PERIOD =
     (SELECT MAX(ACCOUNTING_PERIOD)
       FROM PS_CUST_HISTORY
      WHERE BUSINESS_UNIT
              = H.BUSINESS_UNIT
      AND CUST_ID = H.CUST_ID
      AND CUST_HIST_ID = H.CUST_HIST_ID
      AND FISCAL_YEAR = H.FISCAL_YEAR)
GROUP BY H.SETID,
    H.CUST_ID,
    H.SUBCUST_QUAL1,
    H.SUBCUST_QUAL2,
    H.CUST_HIST_ID, 
    H.FISCAL_YEAR, 
    H.ACCOUNTING_PERIOD,
    H.CURRENCY_CD

Modifying Views for the Unit History Page

New history IDs do not appear on the Unit History page until you modify these views:

BU_SUM_DVW
BU_SUM_LP_DVW

For example, to add a new history ID called WIDGET_SALES, change the view text on each of the views as shown here.

BU_SUM_DVW

Change the view text to:

SELECT BUSINESS_UNIT,
    CUST_HIST_ID,
    FISCAL_YEAR,
    ACCOUNTING_PERIOD,
    SUM(HIST_AMT),
    CURRENCY_CD
FROM PS_CUST_HISTORY
WHERE CUST_HIST_ID IN ('SALES', 'WIDGET_SALES')
GROUP BY BUSINESS_UNIT, CUST_HIST_ID, FISCAL_YEAR, ACCOUNTING_PERIOD, CURRENCY_CD

BU_SUM_LP_DVW

Change the view text to:

SELECT H.BUSINESS_UNIT,
    H.CUST_HIST_ID,
    H.FISCAL_YEAR,
    H.ACCOUNTING_PERIOD,
    SUM(H.HIST_AMT),
    H.CURRENCY_CD
FROM PS_CUST_HISTORY H
WHERE H.CUST_HIST_ID IN ('SALES', 'WIDGET_SALES')
 AND H.FISCAL_YEAR = 
    (SELECT MAX(FISCAL_YEAR)
    FROM PS_CUST_HISTORY
    WHERE BUSINESS_UNIT = H.BUSINESS_UNIT
     AND CUST_HIST_ID = H.CUST_HIST_ID)
 AND H.ACCOUNTING_PERIOD = 
    (SELECT MAX(ACCOUNTING_PERIOD)
    FROM PS_CUST_HISTORY
    WHERE BUSINESS_UNIT = H.BUSINESS_UNIT
     AND CUST_HIST_ID = H.CUST_HIST_ID
     AND FISCAL_YEAR = H.FISCAL_YEAR)
GROUP BY H.BUSINESS_UNIT, 
    H.CUST_HIST_ID, 
    H.FISCAL_YEAR, 
    H.ACCOUNTING_PERIOD,
    H.CURRENCY_CD