Oracle CRM On Demand for Partner Relationship Management Configuration Guide > Configuring Oracle CRM On Demand for Partner Relationship Management >
Migrating Fund Requests from Previous Releases
The Special Pricing Request and MDF Request record types were introduced in Release 18 to replace the Fund Requests record type. If you are currently using fund requests, then you can either continue to use them or you can manually migrate them to the Special Pricing Requests and MDF Requests record types. It is recommended that you do the latter with the current release. You can migrate fund requests either directly after the upgrade or later, depending on your needs. After the migration, you must not use Fund Requests with Special Pricing Requests and MDF Requests, because this will be problematic. You can access the existing fund request records through the Special Pricing Request and MDF Request record types. The manual migration to the Special Pricing Request and MDF Request record types involves using the Oracle CRM On Demand for Partner Relationship Management user interface and the batch update capabilities. A script is not provided. Before the migration, all of the fund request records that will be included in this process must have the record type defined as SPA or MDF. Complete the steps in the following procedure to manually migrate fund requests. To migrate fund requests
- Define the principal partner account for each migrated record.
For more information on creating and modifying partner records, see Oracle CRM On Demand Online Help.
For example, you can set the principal partner account as the partner organization of the record owner.
- Migrate the Fund Request Status field values to the Special Pricing and MDF Request Submission Status, Approval Status, and Claim Status field values as shown in the following table:
|
Special Pricing or MDF Request Field |
Status |
Submission Status |
Approval Status |
Claim Status |
In Process |
Not Submitted |
Blank |
Blank |
Pre-Approval Submitted |
Submitted |
Pending Approval NOTE: this status is set automatically after updating the Submission Status.
|
Blank |
Pre-Approval Denied |
Submitted |
Rejected |
Blank |
Pre-Approved |
Submitted |
Approved |
In Progress |
Claim Submitted |
Submitted |
Approved |
Claim Submitted |
Claim Denied |
Submitted |
Approved |
Claim Denied |
Claim Approved |
Submitted |
Approved |
Claim Approved |
- For all fund request submission status fields except In Process, you must set Submission Status to Not Submitted, save the record, and then set it to Submitted.
- For all Special Pricing and MDF Request Approval Status fields except In Process and Pre-Approval Submitted, you must set the Submission Status, save the record, and then update the Approval Status.
NOTE: You must ensure accurate migration of status field values, because these field values determine the logic for other record types that utilize funds.
- In Oracle CRM On Demand, Remove Fund Requests from User Roles, Access Profiles, Related Item lists, and so on. Replace Fund Requests with the Special Pricing Requests or MDF Requests accordingly.
After the manual migration, the Special Pricing and MDF Request fields must map to the corresponding Fund Request fields (depending on the type of fund request) as shown in the following table:
|
Special Pricing Request Field |
|
Pre-Approval Req. |
Total Amount Requested |
Amount Requested |
Granted |
Total Amount Authorized |
Amount PreApproved |
Claim Req. |
Total Claim Amount Req. |
Total Claim Amount Requested |
Approved |
Total Claim Amount Approved |
Total Claim Amount Approved |
Pre-Approval Date |
Not Applicable |
Pre-Approval Date |
|