This appendix covers the following topics:
Use this list to identify profile options you need to change for your implementation. You can set profile options in any order and at the following levels, as indicated in the table:
You can access the Find System Profile Values window by logging into the System Administrator responsibility and navigating to Profile, and then System. To change profile options, follow the standard procedure outlined in the Oracle Applications User's Guide.
|Sequential Numbering||Always Used||S,A,R||Y||Assigns numbers to documents created by Oracle Financial products and provides a method of checking whether documents have been posted or lost. |
Set this option at the application level to Always Used. Do not set this option at the Responsibility level.
|CSI: Display Impacted Contracts||Optional||S,A,R,U||N||Determines whether or not a user must review a page to view impacted contracts before committing a change to an item instance in Oracle Installed. The two profile values are Optional (user has option to view the impacted contract page at any time when updating an item instance by clicking the View Impacted Contracts button) and Mandatory (user still has option to view impacted contracts at any time; however, when clicking the Apply button to commit a change to an item instance, the user must view the impacted contracts page and explicitly indicate whether to proceed with or cancel the change.|
|OKC: Change Request Approver||SYSADMIN||S,A,R,U||N||Identifies the default change request approver, which overrides the workflow approver.|
|OKC: Error Message Recipient||Able, Ms. Marsha||S||N||Identifies the resource (person) to notify in case the outcome execution has failed. This value can be overwritten in case the user selects another person to be notified when entering the outcome condition.|
|OKC : Event Listener Iterations||100||S, A||N||Allows System Administrators to set the work load of the listeners. The default load (listener its/iterations) is set to 100.|
|OKC: Global Update Privilege||Yes||S||N||If set to Yes, an active contract will have the status QA Hold when you open the contract. The Open for Update button will not appear if the profile is set to Yes.|
|OKC: Number of days to retain a message on the exception queue||30||S||N||In case of any exceptions encountered while running events, messages are thrown into the exception queues. This profile determines the retention period (in days) of such messages.|
|OKC: Outcome Listener Iterations||100||S, A||N||Allows System Administrators to set the work load of the listeners. The default load (listener its/iterations) is set to 100.|
|OKC: Public Group Creator||--||R,U||N||Set this profile option to Yes at the user level, to enable users to create public groups in Oracle Service Contracts.|
|OKC: Renewed Contract Identifier||R||S,A,R,U||N||Provides prefix identifier, which is attached to the system date and shown as a modifier on the renewed contract.|
|OKC: Schedule Rule Alert Window||--||R,U||N||Determines the number of days before a task is due when the user is notified of an upcoming task.|
|OKC: Schedule Rule Escalate||1||R,U||N||Determines the number of days after an incomplete task's due date when escalation begins.|
|OKC: Time UOM Class||Time||S||Y||Limits the units in the Map Time Units window. Note: This is case sensitive and Time should be entered using the exact case.|
|OKC: View Contracts By Organization||No||S,R||Required for multi-org installation||Set this profile option to Yes at the user level, to provide users visibility to contracts authored in the operating unit associated with their responsibility.|
|OKS: Accounting Duration Basis||GL Calendar||S||N||Indicates how accounting durations are calculated for variable accounting rules for service lines. If Monthly is selected, then the accounting rule duration calculation is based on the number of months that are in the billed service duration. Set the profile to monthly when service revenue is always recognized on a monthly basis. If the profile is set to GL Calendar, the accounting duration is determined by calling a GL API to determine the number of fiscal periods that are spanned by the billed service duration. The period used for the duration calculation is specified on accounting rule attached to the service line.
Note: If daily rate accounting rule is attached to the service being billed, then this profile is not referenced and Oracle Service Contracts instead passes both the rule start date and rule end date and allows Oracle Receivables to calculate the accounting rule duration.
|OKS: Billing Report and Log||Yes||S,A,R,U||N||Determines whether or not log messages are spooled to output and log files.|
For companies with a large contract base, the output and log files can be very large when running Service Contracts Main Billing program.
|OKS: Billing Schedule Level||Top Level||S,A,R,U||N||Defines the default level for billing schedules. You can:
|OKS: Category for Order Management Originated Contracts||Warranty||S||N||Determines the contract category for Order Management originated contracts.|
If set to Service, the service ordered interfaces to Contracts with category as Service Agreement and the line type Service.
If set to Warranty, the contract created is of the Warranty/ Extended Warranty category with the line type Extended Warranty.
If set to Subscription, the Contract category created for the service ordered is Subscription Agreement and the line type Service.
|OKS: Check Coverage Match||No||S,A,R,U||N||Set this profile option to Yes, to force the renewal consolidation process to preserve differences in coverage between source and target contracts.|
|OKS: Consolidate Warranty for Multiple Orders||Yes||S||Y||Determines if an order for products with multiple warranties, sold in Order Management, should be consolidated when the service contract is created. Similar warranties are grouped on a single contract rather than creating separate contracts.|
|OKS: Contact Center Date Range||10||S,A,R,U||Y (for viewing contracts from the Contact Center)||Controls the date range of contracts that can be viewed from the Contact Center. Enter the number of days prior to the current date.|
|OKS: Contracts Validation Source||Install Base||S,A,R,U||N||Allows the user to define the organization information that should be referenced when automatically creating a contract. You can set the profile as follows:
The organization that sells the product may be different from the organization that ships the product. If the selling organization has the relationship with the customer, and has agreed to make the sale, it may be that the selling organization should be the one to honor any warranty associated with that product, rather than the organization that shipped the product. In this case, the profile option could be set to Sold From Org - Order Management. The organization information is obtained by the sales order line information.
|OKS: Copy Notes||Yes||S,A,R,U||--||Allows notes to be copied.|
|OKS: Counter Validate||NO||S,A,R,U||N||Set to Yes, to consider only those counter readings marked as valid in Install Base for billing purposes. If set to No, all counter readings are considered for billing.|
|OKS: Credit Card Minimum Authorized Amount||50||S,A,R,U||N||Determines the minimum amount that is authorized against a credit card.|
|OKS: Credit Card Validation Level||Validate||S,A,R,U||N||Determines whether or not to authorize the credit card. The amount authorized is determined by the profile OKS: Credit Card Minimum Authorized Amount.|
Credit Card authorization is initiated when the QA process runs for a contract.
|OKS: Debug Error Log||No||S,A,R,U||N||Set to Yes to generate a debug file. |
Should remain set to No, unless directed by a support analyst.
|OKS: Default Contract Status for Transfers||Active||S||N||Determines the status of the new contract created for the new party.|
|OKS: Default Line Style||Service||S,A,R,U||Y||Defines the default line style of a service contract. Only Service, Extended Warranty, Warranty, Subscription, and Usage line styles are supported for Oracle Service Contracts.|
|OKS: Default Order Type for Subscriptions||Mixed||S,A,R,U||Y (if using tangible subscriptions)||Defines order type for subscription line orders.|
|OKS: Default Pricing Date||Sysdate||S,A,R,U||N||Defines the date used to determine the correct price list and pricing effectivity.|
|OKS: Default QA Checklist||Default Quality Assurance Check List||S,A,R,U||Y||Specifies the QA default when authoring new contracts. |
This profile option applies only to new contracts that are created during authoring.
|OKS: Default Sales Person for Renewal||Taylor, Mr. Phillip Charles||S,A,R,U||N||Sets the default sales person for sales credits on a renewed contract. It also populates this name in the Vendor Contact in the Party Contact Role. |
If the profile option OKS: Use Territories to Default Sales Person is set to Yes, the sales representative is retrieved from resource management instead of this profile option.
If OKS: Enable Sales Credits profile option is set to Drop, this profile option is ignored.
|OKS: Default Time Zone||Pacific/Pitcairn||S,A,R,U||N||Determines the default time zone for business process during Coverage template definition.|
|OKS: Enable Grace Period||No||S||N||Indicates whether users should be able set up a Grace Period, when authoring or updating a contract. This site level profile option default is No, which causes Grace Period fields on the Contracts Authoring form to be grayed out. If set to Yes, users can populate the Grace Duration and Grace Period fields. In addition, entitlements processing honors the grace period.|
|OKS: Enable Install Base Integration Notifications||Yes||S,A,R,U||N||Determines if notifications are to be sent for any contract creation or updates based on Install Base operations.|
|OKS: Enable Negative Invoicing||NO||S,A,R,U||N||Set to Yes, to enable negative amounts on invoices. If set to No, negative values are invoiced at zero value.|
|OKS: Enable Sales Credits||Retain||S,A,R,U||N||Determines how Sales Person, Revenue Type Distribution, Revenue Type, and Vendor Contact are derived during contract renewal. The options are:
|OKS: Full Credit for Product Return||Y||S||N||Determines if a full or partial credit should be issued when a subline is terminated as a result of a customer product return.|
|OKS: Intangible Subscription Pricing Method||Subscription Based||S||N||Determines the pricing method for Intangible Subscription items. Pricing method can be set to Effectivity based or Subscription based.|
|OKS: Item Display Preference||Name||S,A,R,U||Y||Specifies the display order in the list of values for Inventory items when selecting Covered Products or Covered Items, while creating a subline in the Authoring form.|
|OKS: Mass change security level||Advanced||S,A,R,U||Y||Defines list of update levels available to the user when making mass change. If set to Basic, then only the Contract and Contract Group level can be selected for updates. If set to Advanced, users can perform mass change updates at all levels.|
|OKS:Merge System Transfers||Yes||S||N||Determines if contracts covering multiple products in a system are merged into a single new contract when an instance is transferred.|
|OKS: Minimum Service Duration||1||S,A,R,U||N||Defines the minimum duration of a service for cotermination. If a service program sets its cotermination date for duration less than the minimum service duration, then the service program honors the minimum service duration to determine the cotermination date.|
|OKS: Minimum Service Period||Months||S,A,R,U||N||Defines the minimum period of a service for cotermination. If a service program sets its cotermination date for duration less than the minimum service duration, then the service program honors the minimum service duration to determine the cotermination date.|
|OKS: Notify Contract Administrator||CONMGR||S,A,R,U||Required for reassignment of sales reps||Identifies the administrator to be notified if unable to reassign the sales representative on the contract.|
|OKS: Notify Sales Administrator||CONMGR||S,A,R,U||Required for reassignment of sales reps||Identifies the administrator to be notified if the sales representative setup is incomplete.|
|OKS: Notify Sales Administrator||CONMGR||S,A,R,U||Required for reassignment of sales reps||Identifies the administrator to be notified when territory setup is incomplete.|
|OKS: Notify User of Install Base Integration Notifications||CONMGR||S,A,R,U||N||Identifies the user to be notified whenever a warranty or extended warranty is created or updated in Install Base.|
|OKS: Parallel Worker||NO||S,A,R,U||N||Defines how the Service Contracts Main Billing concurrent program is run for efficient performance. Set to Yes to spawn multiple concurrent requests for Service Contracts Main Billing program, when the billing load exceeds 500 lines.|
|OKS: Payment Method for AR Interface||Credit Card||S||N||Captures the payment method for a customer for integration with iPayment Server.|
|OKS: Raise Credit Memo for Install Base Transactions||YES||S||N||Determines if a credit memo is raised when a contract subline is terminated due to transfer, return, or termination of a customer product in Install Base.|
|OKS: Reprice Warning Message||YES||S,A,R,U||N||Suppresses the warning message while repricing or manually overriding the final price. If set to No, the warning message "This action is irreversible. Do you wish to Continue?" is suppressed.|
|OKS: Revenue Type Distribution for Sales Credit||100||S,A,R,U||N||Sets the credit percentage on a renewed contract for a sales representative. In order to pass QA, revenue distribution for a renewal contract must be 100%.|
If OKS: Enable Sales Credits is set to No, this profile option is ignored.
|OKS: Revenue Type for Sales Credits||Quota Sales Credit||S,A,R,U||N||Sets the Sales Credit type, for example quota or non-quota, for creating the sales credits during renewal. |
If OKS: Enable Sales Credits is set to Drop, this profile option is ignored.
|OKS:Service Request Creator||EBUSINESS||S,A,R,U||Y |
(if using automated service request creation)
|Sets default username for automated creation of service requests.|
|OKS: SMTP HOST||vissmtp02.visioncorp.com||S,A,R,U||Required for e-mail quote||Identifies name of the outgoing mail server used to deliver external e-mail notifications.|
|OKS: SMTP PORT||25||S,A,R,U||Required for e-mail quote||Identifies SMTP port number used by the SMTP server defined in OKS: SMTP Host profile option.|
|OKS: Source for State and Country Territory Qualifiers||Customer Party, Vendor Party||S||N||Enables users to determine whether qualifiers are based on customer party or vendor party|
|OKS: Subscription Item Filter||Subscription||S||N||Determines which items the user can select in a subscription line under a subscription agreement. If the value is set to Subscription, only subscription items can be selected. If the value is set to All, the user can select any subscription or products (except service warranty and usage items) at the subscription line.|
|OKS:Summary Transactions||NO||S,A,R,U||Y||If summary transaction is unchecked at the contract header level, determines if the summary or detailed transactions are sent to Oracle Receivables.|
|OKS: Territory Sales Person for First Year Contracts||Derive||S||N||Determines whether the application uses sales territories to assign sales agents (vendor contacts of role Salesperson) to new contracts created from orders in Oracle Order Management. |
A setting of Retain, causes the application to copy the sales person on the order.
A setting of Derive uses sales territories to assigns one resource as a vendor contact of type Salesperson to each contract.
|OKS: Transfer Party Relationship||CUSTOMER/SELLER||S||Y||Specifies the relationship that would identify related parties during the transfer management process. If this relationship does not exist between the parties, the parties are considered unrelated.|
|OKS:Transferred Contract Identifier||T||S||N||Specifies the modifier prefix for new contracts created for a transferred service.|
|OKS: UOM Code||Each||S,A,R,U||N||Sets the Unit of Measure (UOM) code for covered party, site, system, and customer.|
|OKS: Update Contract with Install Base Quantity||Yes||S||Y||Determines if the contract covered product quantity is updated as a result of the update to item instance quantity in Install Base. This does not apply to other transactions, such as a split quantity.|
|OKS: Usage Billing Calculation||Counter||S||Y||Determines readings to be considered in Usage billing computation.|
|OKS: Use Advanced Pricing for Manual Adjustment||YES||S,A,R,U||N||Controls integration with Advanced Pricing for manual override of the final price. If set to No, Advanced Pricing is not used to create or derive price adjustments. If set to Yes, Advanced Pricing is used to derive price adjustments. All adjustments is stored in Oracle Service Contracts and can be viewed from the pricing adjustment screen.|
|OKS: Use Inventory Org for Tax Calculations||YES||S||N||Determines whether to use the inventory organization for tax calculations.|
|OKS: Use Territories to Default Sales Person||YES||S,A,R,U||N||Determines whether to use Territories to default the sales representative for a renewed contract. If set to No, the sales representative is retrieved from OKS: Default Sales Person for Renewal. If set to Yes, the application retrieves the sales person assigned by territory. Territories must be setup if this profile is set to Yes. This profile must be set to Yes if using Reassign Resources concurrent request. If OKS: Enable Sales Credits is set to Drop, this profile option is not used to populate the sales person renewal agreement.|
|OKS: Vendor Contact Role||SALESPERSON||S,A,R,U||N||Sets the role for creating contacts during contract renewal as well as during extended warranty creation. Select any role from the list of values to be added to the party role contacts, which will be copied from the expiring contract. This profile option populates only the role. The person assigned to this role is named in the profile option OKS: Default Sales Person for Renewal. The Concurrent Process for Reassigning Resources looks to the Vendor Contact Role of SalesPerson to validate the name of the sales rep indicated in the territory assignment. Therefore, consider setting this profile option to Salesperson. If OKS: Use Territories to Default Sales Person is set to Yes and the vendor contact role is Salesperson, this party role contact name may be changed to match the territory assignment. If OKS: Enable Sales Credit is set to No, this profile option will be ignored.|