Structuring Contracts

This chapter provides an overview of structuring contracts and discusses how to:

• Define contract statuses.

• Define contract types.

• Define revenue and billing plan templates.

• Define billing plan detail templates.

• Define billing summarization templates.

• Define renewal plan templates.

• Define hold reasons.

• Define tiered pricing templates.

• Define rate sets and rate plans.

• Define discounts and surcharges.

• Define document sequencing options.

• Define legal entities.

• Define early-out options.

• Define milestones.

• Define revenue reconciliation options.

• Define email notifications.

• Define amendments.

Understanding Contract Structure

All tables and setup specific to Contracts are discussed in the following sections. For setting up additional Contract features that are shared by other applications, see PeopleSoft Enterprise Applications Fundamentals PeopleBook.

Note. For contracts with a classification type of Government, you must first set up the Contracts core structure before setting up the tables and structure for government contracts. Government contracts rely on Contracts' core structure to support the government contract features and functions. This combined setup is required to enable you to utilize the additional features and functions of the government contracts system.

See Structuring Contracts for Government Contracting.

See Also

Defining Financials and Supply Chain Management Common Definitions

Defining Contract Statuses

To define contract statuses, use the Contract Status component (CA_STATUS_PNLG_GBL).

This section discusses how to define contract statuses.

Understanding Contract Statuses

The contract status provides you with a visual indicator of where your contract is within the contract life cycle and it designates when a contract is available for lookup and processing. Contracts delivers a set of system-defined processing statuses that control what processing can occur against a contract. When you set up your Contracts system, you define a group of contract statuses that are applicable to your business flow. When you define a contract status, you map it to a system-defined processing status. You can map multiple contract statuses to each system-defined processing status. The contract statuses you define will be those that you see displayed on the pages throughout your Contracts system.

Understanding Processing Statuses

The processing status is a system-defined value controlling the application processing that can occur against a contract. Every contract that you create in Contracts is associated with a contract status that has been mapped to a processing status of Pending, Active, or Closed. Here’s a summary of the processing statuses and a list of the attributes associated with each status.

Status Flow

This diagram shows the flow between status values and the functionality for each header status value.

Contract header processing status

The processing statuses can only flow forwards; that is, you cannot:

• Change the status from Active back to Pending.

• Change the status from Closed back to Active.

• Change the status from Closed back to Pending.

When you initiate a change in the processing status for a contract, the system performs a series of checks to ensure that the contract meets all necessary criteria to move to the next processing status level. Unless the contract meets all necessary criteria, the processing status cannot advance.

Defining Your Own Contract Statuses

In Contracts, you define contract statuses that are applicable to your company’s business environment. These contract statuses are used in the Status field of the Contract - General page and indicate where a contract is within its contract life cycle. When you define a contract status, you map that status to one of the three processing statuses described previously. The system then uses the mapped processing status to control processing activity for a contract.

Here are contract status types that you might want to define and how you might link these contract status types to processing status types.

This table provides three examples of how you might map these sample contract status types to processing statuses:

The system does not enforce a contract status hierarchy for contract statuses that are mapped to the same processing status. For example, using Processing Status Example 2 from the previous table, the system will not always force a user to move the contract status from Proposed to In Negotiation to Letter of Intent.

This diagram shows the contract status setup for a user who allows processing any time after a letter of intent is signed. However, this user does not require that the contract always go from Proposed or In Negotiation to Letter of Intent.

Sample contract status setup

You can optionally enable status security for a Contracts business unit by selecting the Enforce Contract Status Security check box on the Contracts Definition - BU Definition page. When status security is enabled, only those users to whom you assigned permission for a status can manage that contract status.

Page Used to Define Contract Statuses

Defining Contract Statuses

Access the Contract Status page.

Select the processing status to which this contract status should be mapped.

Warning! Once you have defined a contract status and used it on a contract, do not remap that contract status to a different processing status. Doing so causes a change in processing status for any contracts mapped to that contract status.

Defining Contract Types

To define contract types, use the Contract Type component (CA_CONTR_TYPE_PNLG_GBL).

This section describes how to define contract types.

Page Used to Define Contract Types

Defining Contract Types

Access the Define Contract Type page.

Defining Revenue and Billing Plan Templates

To define revenue and billing plan templates, use the Revenue/Billing Plan Template component (CA_PLAN_TMPL_GBL).

This section provides an overview of revenue and billing plan templates and discusses how to define revenue and billing plan templates for use on your contract lines.

Understanding Revenue and Billing Plan Templates

You can set up revenue and billing plan templates to automate the creation of revenue and billing plans. You can also optionally associate events with your revenue and billing plan templates depending on your plan method. These events will populate onto your contract line when you associate the revenue or billing plan template with a contract.

Templates provide you with the flexibility to automate your revenue and billing plan process. You can select options on the template to automatically set the bill plan and revenue plan to Ready status when these actions occur:

• Activate a contract.

  Check boxes on the revenue and billing plan pages indicate whether the system should mark the plan Ready automatically upon contract activation. The value in this check box on the revenue and billing plan pages populates from the option defined on the Revenue/Billing Plan Template page. The default for this option on the template is to leave the plan Pending. Therefore, you must select this option on the template for automation to occur.

• Process an amendment.

  A check box on the amendment page indicates whether the system should mark the contract line Ready automatically upon amendment processing. The value in this check box on the amendment page populates from the option defined on the Revenue/Billing Plan Template page. The default for this option on the template is to leave the plan Pending. Therefore, you must select this option on the template for automation to occur.

  Note. This automation applies only if a revenue or billing plan template is associated with the new contract line.

• Approve a renewal.

  A check box on the Define Renewal Plan page indicates whether the system should mark the renewal plan Ready automatically upon approval of the renewal cycle. The default for this option is to leave the plan Pending. Therefore, you must select this option on the template for automation to occur.

  Note. This automation applies only if a revenue or billing plan template is associated with the new contract line.

In addition, you can override the template values defined from the product at these locations:

• Product Search page.

• Define Renewal Cycle page.

• Amendment Details page.

Note. If you are have a contract with a classification of government, the template for immediate billing plans contains an additional check box for approving progress payments worksheets.

See Progress Payment Billing.

Page Used to Define Revenue and Billing Plan Templates

Creating Revenue and Billing Plan Templates

Access the Revenue/Billing Plan Template page.

Plan Template ID	The system displays the unique template identifier that you entered for this template.
Plan Method	The system displays the billing plan method or revenue plan method that you selected for this template. Possible values include: Apportionment, As Incurred, Immediate, Milestone, Percent Complete, Recurring, and Value Based Billing.
Description	Enter a description for your revenue or billing plan template.
Number of Events	Enter the number of events for templates with Recurring or Apportionment plan methods.
Schedule ID	Select a schedule ID for templates with Recurring or Apportionment plan methods.

Automatically Ready Plan

Basis Date Determination

These fields are available for Apportionment, As Incurred, Milestone, and Recurring billing and revenue plan templates only.

The system uses the basis date as a building block for event dates on Milestone and As Incurred plans, and to determine the start date on Apportionment and Recurring plans.

Note. The basis date cannot occur before the value selected for the Basis Date Source. For example, if you select the Basis Date Option as Specify Day of Month, and you choose the day of the month as the fifteenth (15), then a contract sign date of August 20th, would result in a basis date of September 15th.

Event Detail

The following fields are available for As Incurred and Milestone billing and revenue plan templates only.

Defining Billing Plan Detail Templates

To define billing plan detail templates, use the Billing Plan Detail Templates component (CA_BP_DTL_TMPL_GBL).

This section provides an overview of billing plan detail templates and discusses how to create billing plan templates for use on your contract lines.

Understanding Billing Plan Detail Templates

Billing plan detail templates are specific to a billing plan and are not required to create a billing plan. Use these templates to override the billing defaults that are defined for a contracts billing business unit and contract header. If you specify values for the fields on this page, these values will override the billing defaults. If you do not want to override your billing defaults, you do not need to enter any information on this page.

If you specify a billing plan template and do not specify a billing plan detail template, the system creates the billing plan and populates the billing options on the billing plan with the usual default values (from the contract). If you select a billing plan detail template, then the system overrides the defaults from the contract with the values specified on the template. However, if a value from the billing plan detail template is not valid on the billing plan, then the system uses the default value from the contract.

Page Used to Define Billing Plan Detail Templates

Creating Billing Plan Detail Templates

Access the Billing Plan Detail Template page.

When you first create a new billing plan detail template, all fields appear blank. Use this page to override the billing defaults that you defined for this contract's business unit on the Contracts Definition - Defaults and the Contract General - Billing Options pages. If you specify values for the fields on this page, these values will override the billing defaults. If you do not want to override your billing defaults, do not need to enter any information on this page.

Note. If a value from the billing plan detail template is not valid on the billing plan, then the system uses the default value from the contract.

Customer Information

Billing Options

Billing Default Overrides

Bill Line Summarization

Defining Billing Summarization Templates

To define billing summarization groups, use the Billing Summarization Group (BI_SUM_GROUP_GBL) component.

To define billing summarization IDs, use the Billing Summarization ID (BI_SUMMARIZATION_GBL) component.

To define billing summarization templates, use the Billing Summarization Template (BI_SUM_TEMPLATE) component.

This section provides an overview of billing summarization templates and discusses how to create billing summarization templates to use on your contract lines.

Understanding Billing Summarization Templates

Summarization templates enable you to combine transactional bill line data into a single summarized bill line format for printing on the invoice. Summarization templates are assigned at the billing plan level for amount-based and rate-based contract lines. When the Contracts/Billing Interface process is run, the system passes the summarization template to Billing to combine contract line transaction data for printing on the invoice. For immediate, milestone and percent complete billing plans, additional criteria can be specified on the billing plan to print summarized billing plan lines, while leaving other billing plan lines at the detail level.

Before you can utilize the billing summarization functionality, you must set up the billing summarization components in Billing. To set up billing summarization criteria for Contracts billing, you must complete the following steps:

1. Define summarization group types.

2. Define summarization identifiers.

3. Define summarization templates.

4. Assign summarization templates to billing plans manually or using the Billing Plan Detail Template.

5. Assign summarization group types to billing plan lines for immediate, milestone and percent complete billing plans manually or using the Billing Plan Detail Template.

Note. Summarization templates cannot be assigned to billing plans that use the Value-Based or Recurring billing method.

Defining Summarization Group Types

Summarization group types are used by immediate, milestone and percent complete billing plans to enable you to select the contract lines associated with the billing plan to be summarized. When defining summarization group types you must define a summarization group type ID and summarization group identifiers. When determining how contract bill lines will be summarized, you must associate a summarization group type and summarization group identifier to the contract billing plan line. Only summarization group identifiers associated with the summarization group type will be available for selection.

When the Contracts/Billing Interface process is run, the system sends the summarization group type and summarization group ID data assigned to the contract bill lines to Billing. Billing groups all contract billing lines that are assigned to the same summarization group Id together onto one summarized bill line on the invoice.

Defining Summarization Identifiers

The summarization identifier enables you to select the fields from the Billing Line (BI_LINE) table to use to summarize your billing lines. The fields that you select for your Summarization ID setup will be the fields that you can choose from when defining the summarization rules for your summarization template.

For contract billing, when defining the Summarization ID, you must also include the summarization group type (SUM_GROUP_TYPE) and summarization group identifier (SUM_GROUP_ID)as summarization fields. Including these fields enables the system to successfully pass the summarization bill line data to Billing. If these fields are not included on your Summarization ID definition, Contracts will issue a warning message when the billing plan is set to Ready status.

Defining Summarization Templates

Summarization templates are configurable templates that enable you to define summarized text and grouping rules, as well as customized group header and detail data that appears on the invoice. Once defined and assigned to a contract billing plan, summarization templates enable the system to create summarized invoices for transaction billing data for amount and rate-based contract lines.

Summarization templates enable you to define the configuration that determines how bill lines will be summarized and printed on the invoice. Summarization templates consist of the following three pages:

• Common Definitions page.

  Identify the Summarization ID, associated field names to use for summarization, and group header and detail rules. This setup defines the overall summarization rules.

• Group Header page.

  Define any customized text and details that will print on the summarization invoice, as well as the order in which the fields should display, for fields designated as group header fields on the Common Definitions page.

• Group Detail page

  Define any customized text and the sort order for the group detail lines for fields designated as group detail fields on the Common Definitions page.

See Also

PeopleSoft Enterprise Billing PeopleBook

Pages Used to Define Billing Plan Summarization Templates

See Also

Pages Used to Set Up Summarization

Defining Renewal Plan Templates

To define renewal plan templates, use the Renewal Templates component (CA_RNW_TMPL_GBL).

This section provides an overview of renewal plan templates and discusses how to define renewal plan templates to use on your amount-based contract lines.

Understanding Renewal Plan Templates

You can set up renewal plan templates to automate the creation of renewal plans, automatically create billing and revenue plans, and set pricing and accounting distribution criteria for the renewed contract line. If you have revenue and/or billing plans associated with your renewal template, use the Auto-ready options to enable the system to automatically set the revenue and/or billing plans to Ready status upon approval of the renewal cycle.

See Also

Defining Renewable Products, Templates, and Contract Lines

Page Used to Define Renewal Plan Templates

Creating Renewal Plan Templates

Access the Renewal Plan Template page.

Renewal Plan Template

The system applies a unique identifier to each renewal template.

Used for Renewal Plan and Cycle Creation

Used for Cycle Approval

Other Options

See Also

Entering Renewals

Defining Hold Reasons

To define hold reasons, use the Hold Reason component (CA_HOLD_RSN_GBL).

This section discusses how to define renewal hold reasons for your renewal cycles.

Page Used to Define Renewal Hold Reasons

Defining Hold Reasons

Access the Hold Reasons page.

Hold Reason

Define a hold reason code and associated descriptions for the system to use when you place a renewal cycle on hold. The code for the hold reason that was entered when creating the hold reason displays on the top of the page.

Defining Tiered Pricing Templates

To define tiered pricing templates, use the Tiered Pricing component (PC_TIER_TEMPLATE_GBL).

This section provides an overview of tiered pricing templates and discusses how to define tiered pricing templates.

Understanding Tiered Pricing Templates

You can define tier templates to use when selecting tiered pricing for rate-based contract lines. Tiered pricing allows you to charge varying rates based on the quantity incurred against an activity, such as the length of time worked on an activity. Tier templates may contain one or more tiers that may be defined by one transaction identifier and one or more price breaks. You use the templates when defining tiered pricing for a contract line to facilitate data entry.

See Also

Tiered Pricing

Defining Tiered Pricing

Page Used to Define Tiered Pricing Templates

Creating Tiered Pricing Templates

Access the Tiered Pricing Template page.

Tiered Pricing Template	The system assigns a unique identifier for the tier pricing template.
Sequence Number	Indicates the arbitration resolution order. This number represents the priority of the tier in the event that a transaction matches more than one transaction identifier.
Transaction ID	Select an identifier for the tier. The transaction identifier includes a combination of values for the source type, source category, and source subcategory. The system matches transactions from Project Costing with tiers based on the transaction identifier definitions.
Unit of Measure	Select a unit of measure for the price break quantities.

Price Breaks

Defining Rate Sets and Rate Plans

Access the Rate Sets page.

See Defining Rate Sets and Plans.

See Rate Setup.

Defining Discounts and Surcharges

This section discusses how to define fixed-amount discounts and surcharges. See the Related Projects page for rate-based discounts.

Page Used to Define Fixed-Amount Discounts and Surcharges

Defining Fixed-Amount Discounts and Surcharges

Access the Discounts/Surcharge page.

Discounts and surcharges are discussed in the PeopleSoft Enterprise Billing PeopleBook.

See Setting Up Discounts and Surcharges.

Defining Contract Document Sequencing Options

To define contract document sequencing options, use the Contracts GL Options component (CA_BUGL_OPT_GBL).

This section provides an overview of document sequencing options and discusses how to define document sequencing options.

Understanding Document Sequencing Options

Statutory legal requirements in some countries require that all financial transactions (documents) be classified into different transaction types, and that within each transaction type, all documents entered be numbered sequentially. PeopleSoft Document Sequencing helps you maintain established business practices by meeting both of these requirements.

In Contracts, you can assign specific document types to revenue transactions. Upon activating the Document Sequencing feature, the system automatically assigns a sequence number to each revenue recognition transaction that you generate in Contracts. When you reverse or redistribute revenue accounting entries in Contracts, the Document Sequencing feature assigns new document sequencing numbers.

Note. For Contracts, the Document Sequencing feature applies only to revenue accounting entries since they are the only accounting entries generated within Contracts. For all accounting entries that are sent to Billing, Billing document sequencing options apply.

See Also

Defining Document Sequencing

Defining Common Journal Definitions

Page Used to Define Contract Document Sequencing Options

Defining Contract Document Sequencing Options

Access the Contracts GL Options page.

GL Business Unit (General Ledger business unit)

You assign journal templates and document types at the General Ledger business unit level. Any contracts you have associated with this General Ledger business unit will use the journal templates and document types you define on this page.

You must enter a document type if you are using the Document Sequencing feature for the General Ledger unit. Document types represent the business purpose of a financial transaction. Within the domestic sales journal code, for example, you may have document types, such as domestic customer invoices, customer credit memos, and customer debit memos. Document types are assigned to one and only one journal code.

There is a document type group box for each revenue transaction type: Deferred Revenue Doc Type, Fixed-Amount Revenue Doc Type, and Rate-Based Revenue Doc Type. For each type, you must specify the document type for the initial transaction and for the reversal of that transaction. If you want to use the same document type for revenue reversals, select the Same as Revenue check box for the appropriate type of revenue transaction.

Journal Templates

Select the journal template to be used when the system creates journals to feed to your general ledger. Templates summarize your Contracts accounting entries and determine the journal header, date options, and other characteristics. You must select a journal template for deferred revenue, fixed-amount, and rate-based entries.

Defining Legal Entities

To define legal entities, use the Legal Entity component (CA_LEGAL_PNLG_GBL).

This section provides an overview of legal entities and discusses how to define legal entities.

Understanding Legal Entities

Use legal entities in Contracts to track the legal entity within your company who signs a particular contract. The contract header contains two important pieces of information: the Contracts business unit designating the group within your company that is processing the contract, and the legal entity designating which group within your company signed the contract. Your company’s tax department can then keep tabs on who signed the contract in case a reassignment needs to be done, such as in the case of a reorganization of your company's business structure. The contract header also contains a region code that you can use to break your business into smaller or larger areas and for operational purposes (sales and customer service purposes).

These examples show how you can designate the legal entity on a contract:

Example 1

Two legal entities can sell products/services and assign those products/services to the same Contracts business unit. Here the Legal Entity field enables you to differentiate on the contract the legal entity that signed the contract.

The first sale is by PeopleSoft USA to Cracker Barrel Restaurant. The contract header details are as follows:

The second sale to the same customer is made by Vantive. The contract header details are as follows:

Example 2

One legal entity can sell products/services and assign those products/services to the separate Contracts business unit. Here the Legal Entity field enables you to identify all the contracts signed by a legal entity across multiple Contracts business units.

PSLATIN sells products and services to Cracker Barrel Restaurant in Mexico.

PSLATIN sells products and services to Cracker Barrel Restaurant in Brazil. The business process dictates that this company write separate contracts for different countries within its legal jurisdiction.

Example 3

A contract is sold to a company that is acquired by another company. Here the Legal Entity field enables you to keep a historical record of the legal entities involved with a given contract.

Intrepid sold goods and services to Cracker Barrel Restaurant and was then acquired by PeopleSoft. Upon data entry/conversion to the system, the contract is entered as follows:

An assignment letter is sent to welcome the customer to PeopleSoft, informing the customer that PeopleSoft is reassigning the contract to PeopleSoft. This change is made to the contract via amendment processing.

Page Used to Define Legal Entities

Defining a Legal Entity

Access the Legal Entity page.

Enter a description for each Legal Entity that you create.

Note. Legal entities in Contracts are not directly linked to the legal entities in General Ledger.

Defining Early-Out Options

To define early-out options, use the Early Out Option component (CA_EARLYOUT_PNG_GBL).

This section discusses how to define early-out options.

Page Used to Define Early-Out Options

Defining Early-Out Options

Access the Early Out Option page.

Enter a description for each Early Out Reason Code that you create. These codes can be entered on the Special Payment Terms Page for informational purposes.

Defining Milestones

To define milestone classifications, use the Milestone Classification component (CA_MS_CLASS_PNLG_GBL).

To define milestone templates, use the Milestone Template component (CA_MS_DEFN_PNLG_GBL). Use the CA_MS_DEFN_PNLG_CI component interface to load data into the tables for this component.

This section provides an overview of milestone templates and discusses how to define:

• Milestone classifications.

• Milestone templates.

• Milestone condition templates.

• Custom SQL statements for milestone conditions.

Understanding Milestone Templates

A milestone is a significant event in the life of a contract. Milestone functionality in Contracts enables you to tie activities, such as billing or revenue recognition, to reaching a milestone. Application Engine processing or email notifications can be triggered when that milestone is reached. During system setup, you define a generic set of milestone templates and milestone conditions. You then use these generic milestones and milestone conditions to establish contract-specific milestones when setting up your contracts.

When you define a generic milestone, you can specify one or more milestone conditions. The application uses the status of a milestone’s condition to determine when the milestone is reached. Contracts supports four different milestone condition types: Date, User Init (user initiated), Milestone, and SQL (Structured Query Language).

You can define any number of conditions for each milestone and then make the triggering of the milestone conditional upon the reaching of one condition, or all conditions, associated with that milestone.

As the completion of a milestone can result in a bill being generated or revenue being booked, you need to enable milestone security to restrict the ability to manage milestones to a limited set of employees. You enable milestone security by creating milestone classifications and then associating each generic milestone with a milestone classification.

See Also

Setting Up Milestone Security

Setting Up Milestones

Pages Used to Define Milestones

Defining Milestone Classifications

Access the Milestone Classification page.

Primary Permission List

Select the lists that will have access to manage milestones associated with the value in the Milestone Classification field.

Defining Milestones

Access the Milestone Template page.

Milestone Classification

Defined on the Milestone Classification page and used to limit the ability to manage a milestone to users who are logged on as a member of a permission list specified for the selected classification.

All Contract Types

Select this check box to make this milestone template available for all contract types you defined for this setID on the Contract Types page. If you do not select this check box, you must manually add to the Contract Types scroll area the contract types for which this milestone template is available. This milestone template is then accessible on lists for only those contracts of the defined contract types.

Defining Milestone Condition Templates

Access the Milestone Conditions Template page.

Milestone Conditions Definitions

Add the milestone conditions applicable to this Milestone Template. You can define multiple conditions for a milestone template. For example, billing may only occur based on the completion of product installation or based on a specified date, whichever is earlier. You can define two conditions within a milestone to meet this event. One condition (installation) could be another milestone, and the second condition could be the specific date. When you use the milestone on a contract, you can specify if one or all of these conditions will need to be met in order for the milestone to be satisfied. If you specify that only one condition is needed to satisfy the milestone, then whichever condition is true first will trigger the milestone.

Defining SQL Statements for Milestone Conditions

Access the SQL Statement page.

Enter the SQL statement representing the condition the system should test.

For example:

EXISTS (SELECT 1 FROM PS_CA_CONTR_HDR WHERE CONTRACT_NUM = 
PS_CA_MS_COND.CONTRACT_NUM AND LEGAL_REVIEW_FLG = Y)

The SQL executed for SQL conditions in the Milestone Application Engine follows. The first bind statement is the SQL statement you wrote, so it must logically fit into the syntax.

UPDATE PS_CA_MS_COND
SET MS_COND_STATUS = C, COMPLETION_DATE = %CurrentDateIn 
WHERE %Bind(CA_MS_AET.SQL_STMT, NOQUOTES, STATIC)
AND PS_CA_MS_COND.MS_COND_SEQ = %Bind(CA_MS_AET.MS_COND_SEQ) 
AND PS_CA_MS_COND.MS_SEQNUM = %Bind(CA_MS_AET.MS_SEQNUM) 
AND PS_CA_MS_COND.CONTRACT_NUM = %Bind(CA_MS_AET.CONTRACT_NUM)

Important! SQL milestone conditions are an advanced option that should be created only by persons with extensive knowledge of SQL. We advise that these conditions be reviewed by the manager of your information systems department.

Defining Reconciliation Options

To define reconciliation options, use the Reconciliation Options by User component (CA_RECON_DEFN_COMP_GBL).

This section discusses how to define the parameters for reconciliation.

Page Used to Define Reconciliation Options

Defining Reconciliation Options

Access the Reconciliation Options by User page.

Review By

Select the search parameters for reconciliation. The system requires that you Review By or Break On either the contract line or activity level. You may select all Review By check boxes. The check boxes you select dictate the parameters on which you can break.

Break On

Select the filtering values for reconciliation. These choices determine how your data appears on the reconciliation pages. The more fields you break on, the more detail you see when reconciling. If you did not select either the Contract Line or Activity check box as a Review By parameter, you must select one of the two here. This enables adjustments initiated from the Reconciliation Billing and Revenue page to be tied to a contract line for future reconciliation and revenue management purposes.

Note. You must select the General Ledger ChartFields that you want to have available for reconciliation. If you do not select a particular ChartField here, you will not be able to reconcile or make adjustments to that level.

Defining Email Notifications

To define email notifications, use the Support Teams by Contract Business Unit (CA_EMAIL_BU_PNG_GBL) and the Support Teams by Contract Type (CA_EMAIL_TYPE_PNG_GBL) components.

This section provides an overview of email notifications and discusses how to designate email notifications at two levels:

• Contracts business unit.

• Contract type.

Understanding Email Notifications

Contracts enables you to use the email notification functionality of PeopleSoft workflow to notify employees within your organization of a change in the status of a contract or a change in the status of one of the contract components.

You can set up email notification for support teams and limit the notification to just the manager of a support team. In addition to establishing email notification for support teams, you can designate email notifications for anyone with an email address.

When you are configuring your contracts system, you can designate email notifications at the Contracts business unit level and at the contract type level. When you create a contract, you can optionally enable email notification at the contract level. The system uses the following hierarchy (left to right) to determine which established set of email notification parameters to use: Contract Number - Contract Type - Contracts Business Unit. In other words, if parameters are found for the contract number, the system uses them. If not, the system looks to the contract type, and so on.

Before you can establish email notification for support teams, you must first have defined your team members and set up your support teams. You enter the email ID for support team members on the Member Data page.

See Also

Maintaining Support Teams

Setting Up Customer Support Personnel

Prerequisites

You must have first created your support team codes on the Support Team Members page.

Common Elements Used in this Section

Pages Used to Define Email Notifications

Defining Support Teams by Contract Business Unit

Access the Support Teams by Business Unit page.

Defining Support Teams by Contract Type

Access the Support Teams by Contract Type page.

Defining Amendments

To define amendment types and reasons, use the Amendment Type (CA_CHG_TYPE_PNG_GBL) and Amendment Reason (CA_CHG_RSN_PNG_GBL) components.

This section provides an overview of amendments and discusses how to define:

• Amendment types.

• Amendment reasons.

See Also

Amending Contracts

Understanding Amendments

Contracts requires that any changes that you make to an active contract’s products or terms and conditions be processed through an amendment. When you create an amendment, Contracts creates a copy of the current contract details and preserves this as a historical record. The system then creates a new amendment, where you can define the contract changes.

Before you can create amendments, you must define amendment types and amendment reasons. Amendment types work with amendment reasons to provide contract viewers with a quick explanation as to why an amendment is being made.

Pages Used to Define Amendments

Defining Amendment Types

Access the Amendment Type page.

Amendment Type	High-level classification that you assign to an amendment. Amendment types are dictated by your internal amendment policies. For example, you may want to create an amendment type of Add, Change Order, New Purchase Order, RMA, Internal Change, and so on. Note. A predefined amendment type value of ACTV exists and is used by the system. This amendment type is not editable.
Effective Date	Select an effective date for this amendment type.
Status	Set the status for this amendment type. Values include Active and Inactive.

Defining Amendment Reasons

Access the Amendment Reason page.