By LuciaC-Oracle on Feb 11, 2014
- Service Contracts Public APIs
- Service Contracts Renewal Processing.
The Service Contracts billing process often gives rise to lots of questions and issues. If you've ever searched the MOS knowledge base for service contracts billing issues then you'll know that there are a lot of notes out there and it can be difficult to find exactly what you're looking for. So, we've created a new Troubleshooting Assistant to try and help you find what you need more quickly.
Take a look at Doc ID 1608580.2: Troubleshooting Assistant: Service Contracts Billing. The note allows you to select an area of billing that you are interested in, then you select the symptoms you are seeing or select sub-topics and then presents you with relevant notes based on your selections.
Don't forget that there is also the Information Center: Oracle Service Contracts (Doc ID 1271128.2) which is another way of accessing knowledge documents using topics other than executing a search.
Don't miss the upcoming CRM product family webcasts coming up in February and March.
Date: February 5, 2014 at 8:30 am EST, 7:30 am CT, 6:30 am MT, 5:30 am PT, 1:30 pm GMT, 7:00 pm IST
This one-hour session is recommended for technical and functional users who integrate with Oracle Payments to process online credit/purchase card transactions for inbound (receivables) payments via Oracle Payments, iStore, Order Capture, OM, Oracle Receivables and bank account transfers from Oracle Cash Management and settlements against credit cards and bank accounts or any users integrating with payment processing systems.
Details & Registration : Doc ID 1614255.1.
Date: February 19, 2014 at 10:00 am EST, 9:00 am CST, 8:00 am MST, 7:00 am PST, 3:00 pm GMT, 8:30 pm IST
This session will be useful for all customers planning to implement the Service Contracts Online Renewal feature. The session will explain how the feature works, how to set it up and troubleshooting tips.
Details & Registration : Doc ID 1614212.1.
Date: March 5, 2014 at 9:30 am EST, 8:30 am CST, 7:30 am MST, 6:30 am PST, 2:30 pm GMT, 8:00 pm IST
This one-hour session is recommended for technical and functional users who are relatively new to Field Service - Scheduler module. This will help them understand the various aspects that they need to keep in mind when using the Oracle Advanced Scheduler functionality.
Details & Registration : Doc ID 1614211.1.
Remember that you can access a full listing of all future webcasts as well as replays from Doc ID 740966.1.
Service Contracts has a number of different options for contract renewal. The Online Renewal type can be used for automatic renewal of a contract when customer agreement is required. When this approval type is chosen, the application sends an email notification to the customer requesting them to review the contract renewal details via a URL link to the Customer Acceptance Portal.
From the portal customers can review the renewal and have three options to select to continue:
The required setups are explained in detail in a new document: Doc ID 1602944.1: Service Contracts Online Renewal Setup Flow.
You can then use this information to implement a workaround such as creating the service contract manually OR you can log a service request with Oracle Support to get a datafix which will insert the missing order lines into OKS_REPROCESSING.select ord.order_number "Order_Number", ord.header_id "Order_Id", line.line_number, instance_number, line.service_reference_type_code, line.service_reference_line_id "Reference ID", line_id "Service_Line_ID" from csi_item_instances ib, oe_order_lines_all line, oe_order_headers_all ord where not ib.last_oe_order_line_id is null and ib.last_oe_order_line_id = line.service_reference_line_id and ord.header_id = line.header_id and line.flow_status_code = 'CLOSED' and line.service_reference_type_code = 'ORDER' and line.line_id not in (select order_line_id from oks_reprocessing);
For further details of what this means for E-Business Suite customers please see the E-Business Suite Technology Blog entry 'Microsoft Ending Support for Windows XP and Office 2003 in April 2014'.
Oracle recommends that E-Business Suite customers upgrade their desktops from Windows XP and Office 2003 to the latest certified equivalents. As of today, those are Windows 7 and Office 2010.
E-Business Suite Procurement, Sales and Repository Contracts include integration with MS Word for contract clause authoring and contract download/upload. The Contracts product integration with MS Word requires the Word document to be saved in Word 2003 xml format. Microsoft's latest versions (Word 2007, Word 2010 and Word 2013) still support saving the documents in 2003 xml format.
Please see Doc ID 1476036.1: Supported Formats in Contract Terms Authoring which includes:
A new Troubleshooting Assistant has been published to help you resolve Service Contracts QA check errors. Troubleshooting assistants help you to find a resolution to an issue by guiding you from the problem, through possible scenarios or symptoms, in to the proposed solution(s). Check out the new assistant in Doc ID 1556899.1.
For a full listing of all assistants in EBS check the index note Doc ID 1501724.1.
Prior to release 12.1 there was no supported way to import contracts into the EBS Service Contracts application - there were no public APIs nor contract load programs provided. From release 12.1 onwards the 'Service Contracts Import Program' is provided to load service contracts into the application. The Service Contracts Import functionality is explained in How to Use the Service Contracts Import Program - Scope and Limitations (Doc ID 1057242.1). This note includes an attached document which explains the program architecture, shows the Entity Relationship Diagram and details the interface table definitions.
The Import program takes data from the interface tables listed below and populates the contracts schema tables:
These interface tables must be loaded via a custom load program.
The Service Contracts Import concurrent request is then submitted to create contracts from this legacy data. The parameters to run the Import program are:
|Mode||Validate only, Import
| Batch Number
||Batch_Id (unique id populated into the OKS_HEADERS_INTERFACE table)
| Number of Workers
||Number of workers required (these are spawned as separate sub-requests)
| Commit size
||Represents number of successfully processed contracts commited to database
The program spawns sub-requests for the import worker(s) and the 'Service Contracts Import Report'. The data is validated prior to import and into the Contracts tables and will report errors in the Service Contracts Import Report program output file (Import Execution Report). Troubleshooting tips are provided in R12.1 - Common Service Contract Import Errors (Doc ID 762545.1); this document lists some, but not all, import errors. The document will be updated over time. Additional help is given in Debugging Tip for Service Contracts Import Errors (Doc ID 971426.1).
After you successfully import contracts, you can purge the records from the interface tables by running the Service Contracts Import Purge concurrent program. Note that there is no supported way to mass delete data from the Contracts schema tables once they are populated, so data loaded by the Import program must be fully tested and verified before the program is run to load data into a Production system.
A Service Contracts Import Test program has been provided which will take an existing contract in the application and load the interface tables using the data from that contract. This can be used as an example for guidance on how to load the interface tables. The Test program functionality is explained in How to Use the Service Contracts Test Import Program Provided in Release 12.1 (Doc ID 761209.1). Note that the Test program has some limitations which do not apply to the full Import program and is not a supported program, it is simply a testing tool.
New functionality has been released for Sales and Procurement Contracts in a new patch: Contracts 12.1.3++: Patch 13877401: 12.1.3 Rollup for Oracle Contracts Core.
The new functionality includes:
Plus many more new features. Read the following notes for details on all the new and changed functionality:
Oracle Procurement Contracts Release Notes, Release 12.1.3++ (Doc ID 1467140.1)
Oracle Sales Contracts Release Notes, Release 12.1.3++ (Doc ID 1467149.1)
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Documents (Doc ID 1302189.1)
The Oracle Core Contracts product supports multiple ways of creation
of the clause text. In the Create Clause Page or Update Clause Page
you can either edit text in Rich Text Editor (RTE) or use a
Microsoft Word document to edit and then import the clause text. In
addition, you can download the contract terms as a Microsoft Word
document, edit the clause text and upload the text.
When creating clauses by either of these methods, there are some restrictions on the formatting that can be used in the clause text. The restrictions vary depending on the functionality that is being used for contract download and upload when contract terms are added to other documents such as purchase orders or sales orders.
The following note provides a comprehensive listing of supported formatting depending on each scenario: Supported Formats in Contract Terms Authoring (Doc ID 1476036.1)
Other recent notes covering this area of functionality include:
Type Number Title
PROBLEM 1406773.1 Internal Error When Attempting To Download Contract In Procurement Contracts
PROBLEM 1402606.1 Contract Clause Text Displays As ##ARTICLEWML## Instead Of Clause Text
PROBLEM 1463480.1 Deviations Report Does Not Include Clause Text That Has Been Deleted
PROBLEM 1450666.1 Amendment Description In Imported And Exported Clauses Errors
If you are implementing or upgrading to R12.1.3 Procurement Contracts, Contract Terms Library or Repository Contracts, then please review the following note for a list of recommended patches to apply on top of 12.1.3: 1349213.1: Recommended Patches For R12.1.3 Procurement Contracts and Contracts Core.
Consider the following tips for creation Service Contracts from OM:
Service agreements/extended warranties can be created as a result of selling a Service item on a sales order. The process for creating the contract is different in 11i and R12.
In 11i the process uses the ASO queues as follows:
1. After the sales order is shipped, data is placed in ASO queues
2. Data is dequeued and OKS_REPROCESSING table is populated
3. The Service Contracts Order Capture Integration program must be run
In R12 the ASO queues are no longer used and the Service Contracts Order Capture Integration program is obsoleted. The R12 process is:
1. after the sales order is shipped, data is placed directly in the OKS_REPROCESSING table
2. the Service Contracts Order Processing Program must be run
(a) in both 11i and R12 the Workflow Background Process concurrent program must also be running, so that deferred workflows are progressed.
(b) in both 11i and R12 the contract creation will fail if there is an Install Base error and the referenced instance is not created.
The following notes can help in the troubleshooting this process:
September 20, 2011 at 9 am PT, 10 am MT, 12 noon ET
This one-hour session is recommended for technical and functional users who have to set up and trouble shoot service contract renewals.
A short, live demonstration (only if applicable) and question and
answer period will be included. Oracle Advisor Webcasts are dedicated to
building your awareness around our products and services. This session
does not replace offerings from Oracle Global Support Services.
The above webcast is a service of the E-Business Suite Communities in My Oracle Support.
For more information on other webcasts, please reference the Oracle Advisor Webcast Schedule.
Click here to visit the E-Business Communities in My Oracle Support
Note that all links require access to My Oracle Support.
Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.