This chapter covers the following topics:
This chapter provides details on the basic tasks you must perform to implement Oracle Channel Revenue Management. It contains the following information and instructions:
Tasks that you should perform before proceeding with the rest of the Oracle Channel Revenue Management implementation
Tasks that affect all Oracle Channel Revenue Management modules (Channel Rebate and Point-of-Sale Management, Accounts Receivable Deductions Settlement, Price Protection, and Supplier Ship and Debit)
We recommend that you perform the tasks in the order in which they are presented in this chapter. Tasks include:
Setting up the Time Dimension Structure: This defines how the calendars used in Oracle Channel Revenue Management function and interact.
Setting System Parameters: These define the accounting structure for various modules.
Creating Oracle Trade Management Users: This process sets up the implementation user and the employee users for the modules.
Performing Basic Setups: These setups include setting up activities, categories, rules, and other building blocks of the Oracle Channel Revenue Management process.
Performing Customer Setups: This process is used to set up your customers in the application, including classifications, relationships, and customer trade profiles.
Setting Up Buying Groups: Buying groups are set up to enable to leverage high volume purchase discounts.
Implementing and Verifying Oracle Applications: These applications are the basis for running Oracle applications. They include Resource Manager, Notes, Territory Manager, Task Manager, and Calendar (HTML and Forms-based).
Oracle Channel Revenue Management includes enhanced support for different organizational environments. An operating unit is a business entity with its own set of business rules. Oracle Channel Revenue Management customers generally set up entities for one or more of the following reasons:
Geographical differences: A United States operation versus a Japan operation.
Product and target customer differences: A business unit that sells commodity products to Original Equipment Manufacturers (OEMs) and a business unit that sells consumer products through retailers. These two types of customers make different decisions regarding sales, marketing, and pricing. These decisions need to be made independently.
Differences in divisions: Business units that operate independently but also compete with each other.
Because these operating units function independently, you require to restrict the flow of transaction information between them. With org-striping you can logically partition application data within a single database to ensure data privacy. This means that business transactions of one operating unit cannot be accessed by other operating units within the same company.
For example, Vision Industries includes two organizations, Vision A and Vision B. Vision A sells cosmetics, while Vision B sells pharmaceutical products. Vision Industries can maintain transactions of Vision A and Vision B separately in Oracle Channel Revenue Management by defining Vision A and Vision B as operating units.
To increase support of the application being used under different operating units, Oracle Channel Revenue Management includes the following:
Enhanced Operating Unit Support in Offer, Fully Accrued Budget and Price List integrating with Advanced Pricing and Order Management. The profile option OZF: Global Flag on Pricing Related Objects defaults whether a global flag is checked when the offer is passed to Advanced Pricing.
Support for different business or data model organization structures on an operating unit (org-striped) basis or a shared service basis using the MOAC Profile Option.
Claim users with access to multiple operating units can view all claims across multiple operating units without switching responsibilities.
Enhanced synchronization with Oracle Financial application and Oracle Supply Chain application in Organization Support
Oracle Channel Revenue Management is sometimes referred to as a bridging application between Customer Relationship Management (CRM) and Enterprise Resource Planning (ERP).
Org-striping involves segregating areas based on operating units. In real-time scenarios, companies set up different operating units (OU) or business entities for different reasons. These operating units have their own business rules and they function independently. This means that the business transactions of one OU may or may not be accessed by another OU.
The Oracle MOAC security model enables you to use a single responsibility to access multiple operating units. The MOAC feature is also known as security by operating unit. The MOAC profile option MO: Default Operating Unit (described below) allows you to set operating unit details for offers, budgets, and price lists.
Org-striping enables you to restrict offers, budgets, and pricelist to the respective operating units using the settings in the MO: Default Operating Unit.
The MOAC feature includes the following profile options:
MO: Security Profile: Use this profile option to associate a predefined security profile to a user responsibility. This profile option controls the access for one responsibility to multiple operating units. It determines if the user can access one, multiple, or all operating units in the system.
MO: Default Operating Unit: Optionally, use this profile to set up a default operating unit value for a user. The operating unit must be a valid value within the user's security profile. When the user logs in, the value that you set here appears as the default value in the operating unit field on all the transaction screens. You can set this profile option at the following levels:
Site: if a user wants a different default operating unit for each responsibility or when a user has different organization access for each responsibility.
User: if a user wants the same operating unit as the default value for all the responsibilities that are assigned to the user.
A multi-org enabled setup provides users the flexibility to enter setup and transaction data, and run concurrent programs for multiple operating units without having to switch responsibilities. The "Operating Unit" field in the transaction user interface provides a list of operating units. Users can select the required operating unit from this LOV. The security profile settings and responsibility of the user determine the operating units that appear in the LOV.
With responsibilities, you can access more than one operating unit at a time, so you can perform business tasks for entities that have multiple organizations across all accessible operating units using a single responsibility.
Set the profile option MO: Default Operating Unit to a valid value, to stamp opportunities with your default operating unit.
This profile option setting is mandatory. Stamping your new opportunity with the default operating unit does not limit your access to the opportunity and the stamp is not visible. New account sites and new account relationships are also stamped with your default operating unit if the profile option is set. Again, this stamp is not visible, however it is displayed on the Account Details form if you have access to it through your responsibility.
If the profile MO: Default Operating Unit is not set to a valid value, an error message displays when you attempt to create a new account site, or a new account relationship:
For the Account Site: You will not be able to create the Account Site since your default operating unit has not been set or has been set to a value that is not valid. Please contact your System Administrator.
For the Account Relationship: You will not be able to create the Account Relationship since your default operating unit has not been set or has been set to a value that is not valid. Please contact your System Administrator.
See the Oracle Applications Multiple Organizations Implementation Guide for information on setting the profile MO: Default Operating Unit, implementation considerations for operating unit security, and other details on enabling Oracle Channel Revenue Management users to access multiple operating units.
The following table lists and describes how the various Oracle Channel Revenue Management modules use operating units.
| Oracle Channel Revenue Management Module | Use of Operating Unit |
|---|---|
| Channel Rebate and Point-of-Sale Management | To synchronize with modifiers in the Oracle Pricing application offers in Oracle Channel Rebate and Point-of-Sale Management include the OZF: Global Flag for Pricing Related Objects profile option. |
| Channel Rebate and Point-of-Sale Management | Budgets in Channel Rebate and Point-of-Sale Management use operating units in the following manner:
|
| Channel Rebate and Point-of-Sale Management | In Channel Rebate and Point-of-Sale Management the OZF: Global Flag on Pricing Related Objects profile option determines whether a price list has the global flag checked in the background. The price list header screen contains the global flag for price lists |
| Channel Rebate and Point-of-Sale Management | You can use the OZF:Trade Planning Territories Limited to Operating Unit profile to create and maintain territories for Trade Management purposes enabling you to segregate territories by operating unit. This eliminates the requirement of setting up all territories with account sites as matching attributes. You can set tthis profile option at the site level. This profile option can handle either org-specific or non-org specific quota allocation. |
| Channel Rebate and Point-of-Sale Management | The OZF:Trade Planning Territories Limited to Operating Unit profile option enables the Account Manager dashboard to expose sales orders within one or multiple operating units. The account’s account site for all operating units (plus any other matching attributes) will be derived for the territory, and sales data will be based on those sites. |
| Accounts Receivable Deductions Settlement | In the claims function you can switch from one operating unit to another. The Claims Summary page displays all claims pertaining to all operating units that you have access to. This eliminates the need to switch responsibility. Additionally, when you create a claim (single or mass) and if you have access to multiple operating units, the claim creation page allows you to select the operating unit. |
| Channel Rebate and Point-of-Sale Management |
|
Setting up the time structure is the first task you must perform when implementing Oracle Channel Revenue Management. The Time Structure facilitates activities such as quota creation quota allocation, target allocation, offer forecasting, and reporting features such as sales performance graphs.
Note: You must set up the time structure properly before running any concurrent programs for populating materialized views.
The time structure you set up provides data at these levels:
Day
Week
Enterprise Period
Enterprise Quarter
Enterprise Year
Oracle Trade Management must have a defined Oracle General Ledger calendar. Ensure that the Oracle General Ledger Calendar is set up correctly. For more information, see the Oracle General Ledger User Guide.
To use Oracle Trade Management pages effectively, ensure that Enterprise calendar has periods defined from the Global Start Date to any future dated transactions on which you will report. For example, if you are reporting on future dated transactions such as quotas or forecasts, periods must be defined for all possible future dates.
When adding more periods in the General Ledger calendar, do not change any profile options. Re-run the concurrent program to update the time structure with the new "TO DATE" parameter and view the log.
Use the following instructions to set up the time structure:
Set the following profile options to define the calendar that should be used by your Oracle Trade Management team. Assign values to these profiles based on your specific business needs.
Note: You should not change these parameters after completing the implementation process. If you change the parameters after data is loaded into Oracle Trade Management, then you must truncate all tables and rerun all concurrent processes.
To set profile options follow these steps:
Log in with Oracle Trade Management Administrator responsibility.
Navigate to Setup>Profiles.
Set the profile option to the value shown in the table. For a complete description of each of these profiles refer to Appendix A, System Profile Options.
| Profile Option | Suggested Value | Required/Optional |
|---|---|---|
| OZF: Start Day of the Week | 2 | Required |
| OZF: Period Type | Month | Required |
| OZF: Global Start Date | 01/01/1997 | Required |
| OZF: Degree | 1 (Use a positive integer.) | Optional |
Run the Update Time Structure concurrent program. Suggested parameters are:
FROM DATE: 1-JAN-1997 0:0:0
TO DATE: 31-DEC-2005 0:0:0 (the last date previously defined in General Ledger)
All Level: Y
For the procedure to run concurrent programs, see the Concurrent Programs section.
Complete the following procedures to set up calendars and rates.
Set up at least one accounting calendar based on your business requirements. You can define multiple calendars, with a different calendar assigned to each set of books. For example, you can use a monthly calendar for one set of books and a quarterly calendar for another.
You can set up a calendar can for any fiscal year, with up to 366 accounting periods for actuals, and 60 periods for budgets. The periods can be of different lengths, but they must all be the same period type for one set of books. Otherwise, General Ledger will not recognize them.
You can define an accounting calendar for past or future periods. Be sure that the enterprise calendar has periods defined from the Global Start Date to any future dated transactions upon which you will report.
Oracle recommends defining periods for two or more years into the future. This is useful for forecasting and quotas. Define a complete financial year and define all the periods.
The GL period type should be defined in the same language as the instance.
Accounting calendars can be created in Oracle Trade Management or in General Ledger. Period (calendar) types must be created before creating Accounting calendars.
To set up the Accounting Calendar, log in to Oracle Trade Management with Trade Management User responsibility.
Log in to Trade Management and navigate to Trade Management: Administration > General > Globalization.
On the Calendar Types page click Create
Enter the calendar name.
Enter a prefix. For example, Jan or Q1, or FY04.
Select a type.
Enter a year.
Before setting up an accounting calendar, you must create period types. You can create period types in General Ledger or in the Oracle Channel Revenue Management user interface.
To enter period types in the Oracle Channel Revenue Management user interface follow these steps:
Log into Oracle Trade Management with Trade Management User responsibility.
Navigation: Trade Management: Administration > General > Globalization > Calendar Types.
To create new periods, enter the appropriate information in the Period Types section and click Update.
To display a particular period type or group of periods:
Enter the appropriate year and period type in the Find Period Types section of the page and click Search.
Period Types: Period Types are created in General Ledger in the background. All Period Types are available in the General Ledger.
The calendar defined in this step becomes a value in the List Of Values (LOVs) for the profile.
To set up the calendar, log on with System Administrator responsibility.
Navigation: Profile > System.
Steps:
In the Application field enter Marketing.
In the Profile field enter AMS: Marketing Cal%.
At the Site level, use the list of values to view the available AMS: Marketing Calendar options.
Select the appropriate Accounting Calendar created previously. For more information, see Setting up the Accounting Calendar.
Save your work.
This is a generic calendar available to all Oracle Trade Management users. Different users can have different views of the Calendar, but they cannot personalize the content. The Calendar displays marketing objects based on statuses and time range.
In Oracle Trade Management, the Calendar supports Campaigns and Offers.
To centrally set up the objects that are shown in the Calendar and to implement the calendar use the following procedures:
Before users can view the Calendar, their group must be assigned the CRM Foundation Calendar Items Group Usage. Only users on groups with “Calendar Item” usage will be able to view Objects. For more information, see the Oracle Marketing User Guide.
To assign usage to a resource group, log in to Oracle Trade Management with Oracle Trade Management User responsibility.
To assign usage to a resource group follow these steps:
Navigate to Trade Management: Administration > Resources > Groups >Summary
Click a group name to display the Group Detail page. Click Update to save changes.
Fill in the mandatory fields on the Group Detail page including Group Name and Active From.
In Group Usages, select CRM Foundation Calendar Items from the drop-down menu to enable Calendar functionality.
Before users view the Calendar, they must specify in their user profile what objects they want to view. Users can further personalize the Calendar by saving preferences based on their needs.
To configure user profiles for Calendar preferences follow these steps:
Log into Oracle Trade Management with Oracle Trade Management User responsibility.
Navigate to Trade Management Administration: Trade Management >Setup.
Click on the Profile icon.
Navigate to Calendar>Personalize Calendar.
In the Personal preferences page, click Yes in the Display Items drop-down menu.
Click Update.
You must decide on what information the calendar displays. You can choose to display information based on:
Additional criteria such as date.
Objects including Campaign Schedule, Event Schedule, One-off Events, and Offers.
To specify Calendar parameters, follow these steps:
Log in to Oracle Trade Management with Oracle Trade Management user responsibility.
Navigate to Trade Management: Administration > Trade Management > Setup > Calendar Criteria > Create.
At the Calendar Criteria Overview select Create.
At the Create Marketing Calendar Criteria page fill in the required details including Object, Custom Setup, Start Date and End Date and Priority.
Select Object Status. For example, if the Object selected for display is “Campaign Schedule”, the status chosen may be Active Schedules. In this case, only Active Campaign Schedules will appear on the Marketing Calendar.
Click Update to save your work.
Before the new object or criteria displays on the Calendar, run the concurrent program AMS: Interface Marketing Objects to Calendar. This program is a workflow background process that updates the Calendar as needed. For the procedure to run a concurrent program, see the Concurrent Program section.
You can maintain period–average, period-end, and revaluation exchange rates for any foreign currency that you have enabled. General Ledger uses:
Period–average and period-end rates when you translate your actual and budget account balances.
The revaluation rate when you revalue account balances that are denominated in a foreign currency.
To set up period rates, define rate types (conversion types) in General Ledger. Perform type mapping in General Ledger or in Oracle Trade Management.
To set up period rates, log in to Oracle Trade Management with Trade Management User Responsibility.
Navigation: Administration > General > Globalization > Period Rates.
You can create or modify pseudo period rates. You can also create new period rates.
Notes:
Period: The conversion type automatically defaults based on the type mapping.
The GL Daily Rate is the actual exchange rate between two currencies on a particular day. Use this procedure to enter the rate so it can be used throughout the application whenever currency conversion is performed for that date. Define the rate type (conversion type) in General Ledger before you enter rates.
To view, update, or create GL Daily Rates, log in to Oracle Trade Management.
Navigation: Administration > General > Globalization > Period Rates. (is Period Rates correct - there is no GL Daily Rate)
After entering rates, you can update information, and make changes to the data at any point of time.
Notes:
Conversion rate: While creating a new GL Daily Rate, the inverse conversion rate is automatically calculated when the conversion rate entered.
On the System Parameters page you can define:
Accounting preferences
Price Protection accounting preferences
Claim source setup defaults, such as a default claim type, reason, claim owner, and so on
Claim settlement defaults, such as a default RMA transaction type, debit memo type, credit memo type, write off adjustment type, chargeback type, and transaction type, and rule based settlement thresholds and approvals.
Autopay frequency and preferences
Pay Over Earnings thresholds
Indirect Sales and Trade Planning preferences
Price Protection Process Execution preferences
Supplier Ship and Debit adjustment preferences
System parameter defaults define the following basic information:
Operating Unit: Use the search icon to select an Operating Unit.
Set of Books: When a user creates a budget in Oracle Trade Management, it can be in any currency. In the background, however, a functional currency is recorded with the budget. The functional currency (defined for this set of books) is the main currency used by the Oracle General Ledger set of books. Oracle General Ledger postings are created in this functional currency.
Accounting Method: Select Accrual.
Accounting section: Oracle General Ledger integration parameters including default accounts.
Sales, Expense, and Charge Account: For accruals created from Lump sum, Accrual, Scan Data or Volume offers. If the option to post off invoice discounts to Oracle General Ledger is enabled, this is also used for the debit entry there. The accounting created will be debit sales/expense/charge, credit revenue account from the invoice in Oracle Receivables. The accounting entries, Debit Sales or Expense or Charge account, and Credit Liability are created in Oracle Trade Management and tracked as liabilities in Oracle General Ledger.
Accrual liability account: Accruals created either from a Lump Sum, Accrual, Scan Data, or Volume offers may be treated as liabilities by some companies. Crediting the liability account increases the liability balance.
Receivable clearing account: This Oracle General Ledger entry, along with Debit Liabilities, is created when a claim or deduction is created and associated to promotional accruals if the claim settlement method is a credit memo.
Vendor clearing account: This Oracle General Ledger entry, along with Debit Liabilities, is created when a claim or deduction is created and associated to promotional accruals if the claim settlement method is a check.
To set up System Parameter defaults, see the Setting System Parameter Defaults section in this guide.
The remaining sections of the System Parameters page do not need to be completed at this time. Some require other setups to be completed before values can be entered. The instructions for completing these sections are provided in other sections of this document and are referenced below.
Claim Section
To complete this section in System parameters, you must first create claim types and reasons. For information on completing this section of the system parameters page, see Setting System Parameter Defaults section of the Oracle Accounts Receivable Deductions Settlement Implementation Guide.
Settlement Section
Instructions are provided in the Setting System Parameter Defaults section.
Autopay Section
Instructions are provided in the Setting Autopay in System Parameters and the Setting System Parameter Defaults sections of the Oracle Accounts Receivable Deductions Settlement Implementation Guide.
Earnings Payment Section
Instructions are provided in the Setting System Parameter Defaults section of the Oracle Accounts Receivable Deductions Settlement Implementation Guide.
Price Protection Section
Instructions are provided in the Oracle Price Protection Implementation Guide.
Indirect Sales Section
Instructions are provided in the Setting System Parameter Defaults section of the Oracle Channel Rebate and Point-of-Sale Management Implementation Guide.
Planning Section
Instructions are provided in the Setting Up Quota Allocations section of the Oracle Channel Rebate and Point-of-Sale Management Implementation Guide.
Rule Based Settlement Section
Instructions are provided in the Oracle Accounts Receivables Deductions and Settlement Implementation Guide.
Supplier Ship and Debit Section
Instructions are provided in the Oracle Supplier Ship and Debit Implementation Guide.
Perform this step to set up the implementation user as an Administrator, who is able to access all objects in Oracle Trade Management. Use the following high level procedure to update group access.
Log on with CRM Administrator responsibility.
Navigation: Resource Manager.
Add the implementation user to a resource group using the Trade Management Administrator Responsibility.
Run the Concurrent Program, AMS: Group Access Refresh to finish the process of creating the implementation user.
Select the resource group in the AMS: Admin Group profile option.
The following information describes how to create Oracle Trade Management users and employees.
Create the Implementation User before implementing Oracle Trade Management, and assign the roles and responsibilities necessary to complete implementation tasks. Having a single implementation user makes the process easier as only one user and password is required to complete all steps.
This section describes the following procedures:
Creating the employee
Creating the Implementation User
Creating Custom Responsibility
Setting the Default Responsibility
Importing the Employee as a Resource
Granting Access to Customer and Administration Tabs
Updating Group Access
To create an employee follow these steps:
Log in with US HRMS Manager Responsibility.
Navigation: People > Enter and Maintain.
In the Find Person box, select New and enter the appropriate information.
Save your work. A confirmation will appear in the lower left corner of the window.
Select Assignment and enter Organization, Team/Group, Location, and Supervisor
If a dialog box with Update and Correction buttons displays, select Correction to revise existing data and Update to create a new record.
Save your work. A confirmation will appear in the lower left corner of the window.
Select Yes to use the new location.
Save your work.
Important: In Oracle Trade Management, page level security has been enabled for the Notes, Team, and Tasks options. Users can access these options in Trade Management objects such as offers and budgets only if they belong to the team that has access to these objects. Admin users can access these options regardless of the team to which they belong.
To use Oracle Channel Revenue Management, you should import an employee you created previously, into the application as a resource. As a prerequisite, the employee should exist in the Resource Manager.
To import the employee as a resource, log in with the CRM Administrator responsibility.
Navigation: Resource Manager > Maintain Resources > Import Resources.
Locate the employee you previously created.
Enter employee’s name in the name fields and select Search.
Select Create Resource.
Click OK to accept default values
Click Save Resource (record the transaction number)
Click Details to validate that the User Name field is populated with the proper user created for this employee resource.
To create the implementation user, log into Forms with System Administrator responsibility.
Navigation: Security : User > Define.
Notes:
Assign the following responsibilities to the Implementation User:
General Ledger Super User
HRMS Manager
Inventory
CRM Administrator
Oracle Trade Management User
Oracle Trade Management Administrator
Account Manager
Workflow User Web Applications
System Administrator
Receivables
Oracle Payable
Oracle Pricing User
Receivables Manager
Two procedures are presented below. Use the seeded Oracle Trade Management User responsibility for Oracle Trade Management. With this responsibility, the user can access basic Marketing functions (core) and Oracle Trade Management. To restrict user access to Oracle Trade Management functionality, create a custom responsibility.
Seeded Trade Management Users
TRADEMGR/WELCOME
Oracle Trade Management Administrator
Oracle Trade Management User
Account Manager
To assign a default responsibility to the Implementation user, log in to Oracle Trade Management, and select your default responsibility.
To change the default responsibility at any time, log into Oracle Trade Management.
Navigation: Profile > Navigation Preferences.
Use the following high-level procedure to create a custom responsibility:
Check these steps.
Log in with System Administrator responsibility.
Select Application>Menu
Create the menu structure.
Select Responsibility > Define.
Create the new responsibility.
Assign the menu to the new responsibility.
For specific procedures on creating a custom responsibility, see the Oracle Applications System Administrator's Guide.
A sample menu structure for a custom Oracle Trade Management responsibility is provided in the following table:
Sample Trade Management Custom Responsibility Menu Structure
| Prompt | Submenu | Function |
|---|---|---|
| Home | ASF_HOME | ASF_HOME |
| Customer | OZF_NEW_CUSTOMER_MENU | ASF_ORGZN_SUMRY |
| Product | Oracle Marketing New Product Menu | Products Overview |
| Quota | OZF_NEW_QUOTA_MENU | OZF_TP_QUOTA_OVER |
| Budget | OZF_NEW_BUDGET_MENU | OZF_FUND_OVER |
| Trade Planning | OZF_NEW_TRADE_PLANNI NG_MENU | OMO Programs Overview |
| Claim | OZF_NEW_CLAIM_MENU | OZF_CLAM_SUMMARY |
| Indirect Sales Management | OZF_NEW_INDIRECT_SALE S_MENU | OZF_RESL_SUMMARY |
| Administration | OZF_NEW_ADMIN_MENU | ASF_SETUP_OPP_CALTYP E_MAIN |
| Calendar | OZF HTML Calendar Main Menu | JTF HTML Calendar. Daily View |
You can use roles and groups to control user access to application windows, tabs, and functions.
Specify Roles and Groups to gain access to the Customer and the Administration tabs.
To specify roles and groups, log into Oracle Forms with the CRM Administrator responsibility.
Navigation: Resource Manager. Notes:
Notes:
Resource: Select the user.
Roles: Select a role type of Sales and a Role of Sales Representative.
Group tab: Select a group with Usages of Sales and TeleSales and Oracle Marketing. Ensure that the Group Member Role Sales Representative is associated with the above group on the Resource Details screen.
Perform this step to set up the implementation user as an Administrator, who is able to access all objects in Oracle Trade Management. Use the following high level procedure to update group access.
Log on with CRM Administrator responsibility.
Navigation: Resource Manager.
Add the implementation user to a resource group.
Run the Concurrent Program, AMS: Group Access Refresh.
Select the resource group in the AMS: Admin Group profile option.
This section includes the instructions for performing the following basic setups:
An Activity manages the relationship between an object's Activity Type and the Marketing Medium.
Activities are used to identify the general purpose of a promotion, for example, Advertising or Listing allowance.
Use the Activity page within the Administration tab to:
Manage the relationship between an object's Activity Type, Activity, and the available Marketing Medium.
Specify the available Activity and Marketing Mediums combination for a given Activity Type.
You can create Activities within the application and link them to an existing Activity Type. When an Activity Type is selected for a Object Create or Custom Setup, the Activities that have been created for the Activity Type populate the Activity LOV.
If you are also implementing Oracle Marketing, then you can also use the activity setup screen to set up related activities. For more information, see the Oracle Marketing Implementation Guide.
To create an activity, follow these steps:
Log into Trade Management as a Trade Management User.
Navigate to Trade Management : Administration >Trade Management > Setup > Activity.
Enter an Channel Name.
Select an Channel Category = deal. and mark as Active. Only Active Activities are available within the application.
Associate Marketing Medium. 6.
Click Go
Select a Marketing Medium from the list of active Marketing Mediums displayed.
Select Active From and Active To dates. These dates should fall within the Active From and Active To dates of the Marketing Medium.
Marketing Medium shown up on the Object details page based on the Association of the Marketing Medium with the various activities in the create Activity screen. A single Marketing Medium may be associated with multiple Activities.
Click the create button to save your work.
Marketing mediums relate to a specific channel used by a customer to execute a promotion's performance activity. Therefore, they differ by activity.
For example, a trade promotion for a new toy includes the activities of Advertisement and In-Store Display. The advertising appears in the local newspaper, community magazine, and on the radio. In-Store displays include an End-Aisle Display and a display by the cash register.
Use the following procedure to create a marketing medium.
To create a marketing medium, log in to Oracle Trade Management with Trade Management User responsibility.
Navigation: Trade Management : Administration > Trade Management > Setup > Marketing Medium. Click Create.
Notes:
Marketing medium name: This name should reflect the activity type and the activity with which it will be associated.
Channel: Choose the appropriate activity that this medium will support. For example, if the Marketing Medium is Direct Mail House, choose Direct Mail for the activity.
Categories are used to group objects. Use them as selection and search criteria to locate objects. In Oracle Channel Rebate and Point-of-Sale Management Oracle Channel Revenue Management, budgets categories are used to impose a business rule and to integrate with General Ledger.
Creating Categories
To create a category, log in to Oracle Trade Management.
Navigation: Administration > Trade Management > Setup > Category.
For more information on categories, see Setting System Parameters.
Verifying Categories
To verify that a category is properly implemented, log in to Oracle Trade Management.
Navigation: Budget > Budgets > Create.
Verify that the category you created is displayed as a value in the Category drop-down menu.
To create thresholds, log into Oracle Trade Management with Oracle Trade Management responsibility.
Navigation: Trade Management : Administration > Trade Management > Setup > Thresholds. Click Create.
In Oracle Channel Revenue Management, budgets, offers, claims, quota, and price list use custom setups.
Custom setups determine:
Source Code Suffix: Use for budgets, offers and claims.
Side Navigation Menu: The side navigation menu is the vertical menu that appears after an object is created.
Menu Items: Menu items are the functional areas within the application where data can be created or where objects are viewed.
Component Groups: Menu items are logically grouped into various sections based on functionality. Component Groups include Planning, Execution, Tracking, Collaboration and Approval. Within each Component Group is a logical collection of menu items.
Approval requirements for:
Budgets: Approval rule setup
Offers: Whether a budget, budget approval, theme approval, and adjustment approval are required
Claims: Whether or not approval is required
Custom setups are not org-striped. Therefore the same setups appear in every operating unit. A few seeded custom setups are included with Oracle Trade Management. Use the following procedure to create additional custom setups.
To create Custom Setups, log in to Oracle Trade Management with Oracle Trade Management User responsibility.
Navigation: Trade Management : Administration > Trade Management > Setup > Custom Setup. Click Create.
Notes:
Active: Select to make the setup available for users.
Allow Essential and Optional Grouping: Select if you want to change the default grouping.
Source Code Suffix: The suffix that you enter is reflected when an object is created. The suffix can be alpha, numeric or a combination and the maximum number of characters is 3.
To configure a custom setup after creating it, log into Oracle Channel Revenue Management.
Navigation: Trade Management:Administration > Trade Management > Setup > Custom Setup > Custom Setup link.
Notes:
Display Sequence: Use this column to control the order in which the objects appear. For example, if Products should appear directly below Main, then Product should be sequentially numbered directly after Main. Main is not an optional setting and must be included. In this example, Main could be given a value of 10, and Product could be given a value of 11.
Available Attributes: Use this column to indicate if the attributes for this object should be made available.
Essential: To control the display order of a particular object, check the Essential box (be sure to select the Essential check box that aligns with the correct object). Anything not checked in the “Essential” column is considered “Optional” and is listed in alphabetical order.
Essential Display Sequence: Display sequence is a numeric setting used to order objects in cue cards. If the Essential box is checked, numeric values need to be provided enables the “Essential” objects to be ordered appropriately. The Display Sequence column is used to determine the order when “Business Process View” profile value is selected. You can set up the business process view at the user level.
You can select Offer along with Scan Data or Lump sum:
Scan data offers: A common promotional tactic executed by companies in most all consumer goods industries. Common examples of scan data promotions are coupons or consumer rebate programs, which may be received by a manufacturer as an import file from a POS system.
Lump sum offers: In addition to offers made to customers tied to specific product transactions (for example, $1.00 off per case), a supplier may pay customers for other services and expenses. These include payments to secure shelf space (slotting allowances), events (new store opening activities), and payments to reimburse customers for advertising costs, for example. For these situations, the vendor uses a Lump sum offer to issue a check or credit to the customer for a specific amount.
A profile option allows the reversal of product family accruals for Lump sum and Scan Data offers. If enabled, the option works as follows. If an offer line specifies a product family only, then the following Oracle General Ledger entries are created during claim settlement:
Reversal of original accrual posting.
Debit original liability account by associated earnings amount
Credit original sales/expense account by associated earnings amount
Recreation of accrual posting. The base accounts are taken from the budget or budget category (should be the same as the original base accounts, unless the base Oracle General Ledger accounts on a budget or category have been changed.) Account Derivation Rules are used for the following:
Debit sales/expense account by associated earnings
Credit liability account by associated earnings amount
The Account Derivation Rules provide the configuration of the Oracle General Ledger accounts to post actuals for particular products even when accrual postings were created for product families. The claim itself does not need any validation.
For regular actual postings, there is a profile option that drives whether the liability account should be constructed by the Account Derivation Rules or should be taken directly from the original liability account. For these postings, this profile option is bypassed and the liability account referenced in the step above is always used. Both of the following entries are offsetting entries — the debit entry offsets the credit entry created in the step above; the credit entry offsets the debit entry created by Oracle Receivables or Oracle Payables. Therefore, no call to the Account Derivation Rules is necessary for:
Debit liability account by associated earnings amount
Credit receivables/vendor clearing account by associated earnings amount
You can also scatter lump sum postings by dividing the budget total into smaller amounts and creating postings to the budget and General Ledger periodically.
You can create the following types of rules.
Mandatory Rules
Locking Rules
Approval Rules
You can set up mandatory rules to require users to enter data in specific data fields on specific screens. You can create rules to make certain data fields mandatory. Certain values in the selected columns are seeded as mandatory and cannot be removed.
In Oracle Trade Management, procedures that use mandatory rules include budgets, offers, claims, adjustment types, claim types, budget thresholds, budget request, claim reason, system parameters, trade profile, and price lists.
For example, in Claims, Reference is not a mandatory field by default but if your business requires this field, you can create a mandatory rule to enforce this business requirement. An asterisk next to the field indicates that it is mandatory.
To create mandatory rules, log in to Oracle Trade Management with Oracle Trade Management User responsibility.
Navigation: Trade Management : Administration > Trade Management > Setup > Mandatory Rule.
Notes:
Object attribute: This is the side navigation menu for which this field appears.
Selected fields: The field names in the Selected Fields column will be mandatory.
Locking rules enable you to prevent users from updating data at certain statuses. In Oracle Channel Revenue Management modules that can use locking rules include Channel Rebate and Point-of-Sale, and Accounts Receivable Deductions Settlement.
To create a locking rule, log in to Oracle Trade Management with Trade Management User responsibility.
Navigation: Trade Management : Administration > Trade Management > Setup > Locking Rule.
Notes:
Parent object type: For each selection, different object selections become available in the Object Attribute and System Status drop-down lists.
Object attribute: This is the side navigational menu for which this field appears.
System status: Select New.
Selected fields: Move items from the Available Fields column to the Selected Fields column. The fields in the Selected Fields column will be locked.
Note: Certain fields are seeded in the mandatory rule and cannot be removed from the Selected Fields.
In Oracle Channel Revenue Management, every product can use approval rules. Approval rules determine what must be approved, by who, and at what status.
You can configure approval rules for budgets or budget requests by using multiple parameters such as amount, budget category, organization, and custom setup.
For internal approval of supplier ship and debit requests, you can configure approval rules for the new transaction type of OZF: Supplier Ship and Debit Request that you create with transaction type key of SUPPLIER_SHIP_DEBIT. To define approval rules for ship and debit, use the Approvals Management Administrator responsibility to create the new transaction type. Next, define item classes and attributes for this transaction type. Use the Approvals Management Business Analyst responsibility to create new attributes. For example, you can define an action type such as chain of approvers, create approver groups, and add members to a defined approver group.
If no approver is set up in Oracle Approval Management, Supplier Ship and Debit uses the approver you named for the OZF_SD_DEFAULT_APPROVER profile option. If no approver is found for the profile option, then either the person assigned this role on the request or the administrator approves the request.
When claim processors determine settlement methods for their claims, you can set up approval rules so that claims are settled only if they are approved by a manager.
If no approval rules are set up for a given transaction, notification is sent to users with the Marketing Default Approver role.
You can assign approvers by role, user, function or a combination of all three. You can use functions such as Object Owner, Parent Object Owner, Budget Owner, or Parent Budget Owner. These are similar to approval roles, but are dynamic based on each Object, and need not be assigned to a User. If you want the approval to go through a chain of approvers, set approvers in that particular order.
Approver attributes include:
Order: the order in which approvers are notified.
Roles: Marketing Default Approver role type.
Function: any customized program to search for approvers.
Warning: After setting up approval rules, carefully test each approval rule to ensure that the correct rule is used. This testing process identifies conflicting rules.
Example
Scenario: All claims under $100 are automatically approved. All claims over $100 with the reason Promotion go to Mary Smith, the Sales Administrator, for approval.
Solution: Set up two approval rules. The first one is for claim amounts $0 to $100. They are routed to a default dummy approver that has automatic approval set up in the workflow notification.
The second rule is for claim amounts over $100 with reason Promotion. These claims are routed to Mary Smith for approval.
Use the following procedure to set up approval rules:
In Oracle Channel Revenue Management, modules including budgets, offers, claims, price list, and budget sourcing can utilize user statuses. User statuses are meant for tracking and classification purposes only; system statuses drive system behavior. After you set up user statuses, Oracle Trade Management users can select user statuses for budgets, offers and claims.
You can create multiple user statuses to give a team of claim users who administer a claim the ability to review the performance details on the claim before they settle it:
| System Status | User Status |
|---|---|
| Pending Close | First Reviewer |
| Pending Close | Second Reviewer |
| Pending Close | Third Reviewer |
The first reviewer reviews the claim, and updates the status to “Pending Close - First Reviewer" user status. At this user status, because the underlying system status is Pending Close, the claim has all the behavior of a claim in the pending close status, and none of the fields on the claim can be updated. This user status also enables other claims users to know that the claim is under the first review. After reviewing the claim, the first reviewer can change the status to “Pending Close - Second Reviewer”, which enables everyone to know that the second reviewer is reviewing the claim.
Seeded user statuses are included in Oracle Channel Revenue Management. See the Oracle Accounts Receivable Deductions Settlement Implementation Guide for the list of seeded user statuses. Use the following procedure to create additional user statuses:
Log into Oracle Trade Management with Oracle Trade Management User responsibility.
Navigation: Trade Management: Administration > Trade Management > Setup > User Status.
Notes:
Default: Select this check box to set a user status as the default otherwise one of the seeded user statuses for budgets, claims or offers is used.
The required role types for approvals are:
Default Marketing Approver: Approver of any new marketing object requiring approval. This role type should be assigned to one person only.
Marketing Approver: Approvers specified by the approval rules.
To set up role types for approvals, log in to Oracle Forms and select the CRM Administrator responsibility.
Navigation: Resource Manager > Setup > Role Types.
Notes:
Role types: Verify that the following role types exist:
AMSAPPR: If the role type does not exist, then create one by clicking New.
Code column: Enter AMSAPPR.
Meaning and Description: Enter Default Marketing Approver.
Marketing approver: If the organization requires multiple approvers, then create a role type called Marketing Approver:
Role Type: MKTGAPPR. If it does not exist, continue with this procedure. Otherwise, proceed to the next section.
Menu: Select New.
Code: Enter MKTGAPPR.
Meaning and Description: Enter Marketing Approver.
Create the role of Default Marketing Approver and assign it to a user. The Default Marketing Approver receives approval notification for any budget, offer or claim not meeting the criteria specified in your approval rules.
Note: The Default Marketing Approver Role can only be assigned to one user. If more than one user receives this role, the approval process fails. Note that the system will not prevent you from assigning the role to more than one user. For information on Default Marketing Approver see the section titled Approval Process in the Oracle Marketing User Guide.
To set up approver roles, follow these steps:
Log on with CRM Resource Manager responsibility.
Navigate to Administration >Resources > Roles.
Query for the role AMS_DEFAULT_APPROVER or create it using the following steps.
Code column: enter AMS_DEFAULT_APPROVER..
Name: Default Marketing Approver.
Type: Use the LOV to select Default Marketing Approver or the description you gave the Default Marketing Approver Role Type.
Description: Enter Default Marketing Approver Role.
Check the Active and Manager boxes.
Save your work.
See the table below for system profiles and their values.
| Option | Required | Level | Setting | Effect/Limitation |
|---|---|---|---|---|
| AMS : Cut off percentage for Approvals | Yes | Site | Enter a value between 0 and 100 | This determines what percentage of the estimated budget amount an offer must secure in actual funding before the offer can go active. For example, if you enter 100, it means 100%. An offer's estimated budget amount is $10K, meaning that it is estimated that this offer must get budget approved for $10K before the offer can go active. |
| OZF : Source from Parent Object | Yes | Site | Yes/No | If set to Yes, then objects can source only from their parent objects. If set to No, then the schedule sources funds directly from a budget. |
The creation process involves first creating an approval rule and then assigning approvers to the rule.
The attributes of approval rules are weighted to determine which rules should be used in different situations. If there are multiple rules that may apply, then these weights determine which rule to use.
Business Unit = 6 (if the business unit matches the rule, this weight is assigned)
Organization = 5
Approval Object Type = 4 (budget)
Budget Category = 3
Custom Setup = 1
To create approval rules, log into Oracle Trade Management with the Oracle Trade Management User responsibility.
Navigation: Administration > Trade Management > Setup > Approval Rule.
You can assign approvers by role, user, function or a combination of all three. The functions in use are functions such as Object Owner, Parent Object Owner, or Budget Owner.
These are similar to approval roles but are different in the sense that they are dynamic based on each object (budget, claim, campaign, etc.) and do not have to be assigned to a User. Designate an order if the approval must be sent through a chain of approvers.
For example, you have a trade promotion budget that has three approvers for the Budget Line Approval. After creating the rule, add approvers to the rule in the order in which they should approve. Approver with Order [1] is the first approver, followed by Approver with Order [2] and so on.
Product templates enable users to configure product attributes. Configurable Product Options can be defined when Oracle Channel Revenue Management is installed. Product templates:
Determine the list of product attributes displayed in the inventory options side navigation menu for any responsibility
Enable you to customize a list of product attributes based on business needs and integration requirements
Oracle Channel Revenue Management provides a default template based on whether you are defining a product or a service. You can change the selection of product attributes to override the template. You can define the list of product attributes for each responsibility and you can also specify if the product attributes are editable in the inventory options page. This feature enables you to isolate product attributes and limit their access to the appropriate users in accordance with business and integration requirements.
Oracle Channel Revenue Management product options are different from inventory templates. The options created here are used only in Oracle Trade Management screens, which gives the user an option to configure the product attributes displayed in the inventory option side navigation menu.
To create product options:
Log into Oracle Trade Management with Oracle Trade Management User responsibility.
Navigate to Trade Management:Administration>Trade Management>Setup>Product Options.
To create and enable a new template, use the following procedures:
To create a new template, log in to Oracle Trade Management.
Navigation: Administration > Trade Management > Setup > Product Option > Create Product Template.
To set up a new template, open the new template.
Notes:
Responsibilities: Link a responsibility to the template. You can assign only one product template and one service template to a responsibility.
Attributes: Set the following parameters for each attribute:
Default: Select to make an attribute the default when a product is created.
Editable: Select to make an attribute updatable in the product screens. If Editable is selected, Hide is ignored.
Hide: Select to make hide the attribute in the product screens. This is overridden by a selected Editable parameter.
Select All: Select this flag to enable all the attributes.
Different Inventory attributes can be assigned to a product, depending on the type of product created-- Inventory or Service. If an Inventory product is created, then the attributes screen displays the specific Inventory and Order Management attributes; if the Service option is selected, then the specific Service default attributes are displayed. This section lists the seeded attributes for the following seeded product templates:
Product (Inventory) Template
Service Template
See the Oracle Marketing User's Guide for more information on seeded Templates for Products and Service Attributes.
The following sections describe customer setups:
To create customer classifications, see the Oracle Trading Community Architecture Administration Guide.
To define customer relationships, see the Oracle Trading Community Architecture Administration Guide.
Claims can be settled for the claiming customer account and all other related accounts. Claims always use customer accounts in TCA, and not parties. For example, if accruals are tracked at the account level, and the claim is from a bill-to account, payments can be made to related ship-to accounts.
For instructions on defining account relationships, see the section titled Creating Customer Account Relationships in the Oracle Receivables User Guide.
Customer trade profiles are used to perform the following tasks.
Store basic customer information such as customer name, account number, site and address.
Provide a link to vendor setups if applicable.
Define Autopay parameters for accrual reimbursements including payment frequency, threshold, and method.
Define parameters for claim payments including days due and write off thresholds for deductions and overpayments.
Define earning payment parameters for unearned offer accruals including various threshold settings.
Define indirect sales parameters including batch and line tolerances.
Define code mapping for customer reason, agreement, unit of measure (UOM), item, and end customer.
For instructions on how to create customer trade profiles, see Creating Customer Trade Profiles.
Buying groups enable companies to leverage high volume purchase discounts. Companies in the consumer goods sector and elsewhere can obtain high volume purchase discounts. You can create buying groups that aggregate the purchases from different organizations and their accounts so you can negotiate such discounts.
You can form buying groups in Oracle Marketing by linking various TCA parties together based on a predetermined party relationship.
Any account owned by a member organization can participate in the offer.
To create a buying group follow these steps.
Log into Trade Management with Oracle Trade Management User responsibility.
Navigate to Customer>Organization.
Drill down (click on) to the Organization that you want to set up as the Parent or Buying Group Organization.
Click on the Relationships cue card on the left-hand side.
On the Relationships page click the Add Relationship button.
On the ‘Add an Organization Relationship to’ select the Organization that you want to set up as the Child of the Buying Group.
Select relationship of type Buying Groups, make sure the status is set to Active and click Create.
A Confirmation page displays showing the related organization and relationship.
Once on the relationships summary page, add a new line for the Organization you just added.
Click on the Organization name just added, to display the child Organization details page. Click relationships cue card to validate if a new relationship type of buying group is generated for this child Org. This is done automatically by the system.
Log into Oracle Trade Management with Oracle Trade Management Administration forms responsibility.
Navigate to Concurrent Requests > Run.
Run the concurrent program Generate Party List for Market Qualifiers.
This will build the buying group and link all the Organizations so defined.
Certain Oracle CRM Application components are prerequisites for implementing any Oracle CRM module. They provide common infrastructure upon which all CRM applications are built. (Formerly CRM Technology Foundation)
By providing a set of application components, Oracle CRM ensures that all applications interact with key business objects in a consistent manner.
The following components are required for Oracle Trade Management:
Resource Manager
Notes
Territory Manager
Task Manager
Calendar (HTML and Forms-based)
To implement CRM Foundation for Oracle Marketing use the following procedures:
Resource Manager is a central repository for various types of resources, groups, teams, and roles can be created. It enables Oracle Trade Management and other applications to use resources regardless of where they are created.
You can import resources such as employees, suppliers, parties and partners that are created in other applications. After resources are imported into Resource Manager, they can be used by other applications.
Resource Manager enables:
Groups
Roles
Role Types
Employee Import
For instructions on setting up Resource Manager, see the Oracle Trading Community Architecture Administration Guide.
Oracle Channel Revenue Management uses territories for:
Budget Allocation: For fixed budget allocation and fully accrued budgets. Transaction Type = Offer in Territory Manager.
Quota Allocation: For allocating quotas to territory hierarchies.
Claim Owner Assignment: For transaction types analogous to the Claim in Territory Manager.
The concept of winning territory in other applications equates to budget and claim owner assignment in Oracle Trade Management. To implement Territory Manager for Oracle Trade Management, complete the following procedures in the order in the following order:
Setting up territory types is mandatory for Oracle Trade Management budgets, but optional for claim owner assignment. It is the first task you must perform when setting up Territory Manager for Oracle Trade Management. Territory types map to a specific level in a Trade Management budget. Each level in the territory hierarchy must have a unique territory type. For more details on Territory Manager, see the chapter titled Setting Up Territories in the Oracle Territory Manager Implementation Guide.
Territories are used in fixed budgets and fully accrued budgets in the following manner:
Fixed Budgets: Territories are used in fixed budgets for allocation purposes, thus enabling a company to allocate money to each sales territory. When the allocation is complete, a budget hierarchy similar to the territory hierarchy is created. The primary resource for each territory is the budget owner. Other territory resources become team members of the budget.
Fully Accrued Budgets: Territories are used in fully accrued budgets to create budget hierarchies. These budgets can be created based on a specific territory hierarchy. When approved, a budget hierarchy mapped to the selected territory hierarchy is created. Each child node (at the lowest level of the budget) is created by using an Advanced Pricing modifier. When an order that meets the defined criteria is placed, the total and utilized amount in the appropriate child budget is increased. The primary resource for each territory is the budget owner. Other territory resources become team members of the budget
For more details on Territory Manager, see the chapter titled Setting Up Territories in the Oracle Territory Manager Implementation Guide.
Claim owner assignment works similar to territories that are used in other applications. For example, you can set up a claim territory AZS , so that if the claiming customer is Business World, the claim is assigned to John. Other AZS territory resources are assigned as team members to the claim. Territory A is the “winning” territory.
For information on setting up territories refer to the chapter titled Setting Up Territories in the Oracle Territory Manager Implementation Guide.
Run the following concurrent programs each time you change a territory definition:
Generate Territory Package : Run the following programs In Territory Manager:
Import Territory Hierarchy and Generate Party List for Market Qualifiers
Run these programs in Oracle Channel Revenue Management.
When running the OZF-TM: Import Territory Hierarchy program, you are prompted for a Territory Hierarchy Start Node. This value can be any root territory defined under Oracle Channel Revenue Management in Territory Manager.
For more information on Territory Manager, see Oracle Territory Manager Implementation Guide.
Task Manager is optional for a basic implementation. Task Manager helps you to manage tasks by providing an effective mechanism for organizations to respond to customer needs in a timely manner. By using Task Manager you can create, assign, manage, sort, and prioritize a task.
To implement task transition rules, set the profile, Task Manager: Default Task Status, after defining a rule and assigning it an appropriate responsibility.
Note: If no rules are assigned to a responsibility, you do not need not set this profile because all statuses are displayed in the Status LOV.
For complete information on how to set up Task Manager, see the Oracle Trading Community Architecture Administration Guide.
| Option | Required | Level | Setting | Effect/Limitation |
|---|---|---|---|---|
| Task Manager: Default Task Status | Optional | Site, Application, Responsibility, User | User Defined | Required for implementing a task transition rule. Set this profile option to the initial status of the rule. |
| Task Manager: Owner type for a task | Optional | Site, Application, Responsibility, User | User Defined | Specifies the default task type when creating a task. |
| Task Manager: Default Priority | Optional | Site, Application, Responsibility, User | User Defined | Specifies the default task priority when creating a task. |
| Task Manager: Default assignee status | Optional | Site, Application, Responsibility, User | User Defined | Specifies the default assignee status when creating or assigning a task. |
The Task Manager: Default Task Status value must be set to the first status value defined in Task Status Transition Rule for Oracle Trade Management .
This status applies to the Oracle Trade Management Administrator.
For more information on Tasks, see the Oracle Trading Community Architecture Administration Guide..
Setting up note types is optional. Although Oracle Notes comes with a set of predefined note types, you can create customized note types. Predefined set of notes and the customized notes are available in Oracle Trade Management.
See the Oracle Trading Community Architecture Administration Guide for more information.
Navigation: Notes Setup> Note Type Setup.
Notes:
Code, Meaning, and Description: Carefully describe the Note Type meaning. This description is later used to map the Note Type to the Oracle Trade Management Object.
Tag: Enter Note.
Navigation: Notes Setups > Source and Note Type Mappings.
Notes:
Source object: Select the appropriate Oracle Trade Management object that you want to use this Note Type. For example, Campaign Schedule.
Note type: Select the new Note Type created. The Note Type LOV displays the text entered as the Note Type meaning.
Application: Select Trade Management.
Note: If a note type is not associated with a specific Oracle Trade Management object, it becomes available to all Oracle Trade Management objects.