This chapter covers the following topics:
Oracle Marketing is a component of the integrated Oracle E-Business Suite. Because of this, you will need to verify that Oracle E-Business Suite dependencies are installed and set up properly for Oracle Marketing. The verification and setup of Oracle E-Business Suite prerequisites is necessary to ensure that supporting functionality and applications infrastructure is in place prior to beginning the Oracle Marketing implementation.
In addition, you can leverage other applications and modules within the Oracle E-Business Suite to provide additional functionality to your Oracle Marketing implementation. For example, if your business requirements mandate that your marketing campaign results be translated into leads, then you can license and implement Oracle Leads Management along with Oracle Marketing. This combined implementation would allow you to analyze and track sales leads as a follow up to your marketing initiatives.
This implementation guide categorizes Oracle E-Business Suite dependencies as follows:
Mandatory Dependencies: Oracle applications and modules that provide underlying infrastructure and support to Oracle Marketing. Implementing these dependencies is required and must be complete before beginning an Oracle Marketing implementation.
For example, the Oracle Trading Community Architecture (TCA) provides a repository for customer and partner information. All customer and partner information used by Oracle Marketing is stored in the TCA tables. Because this information is critical for Oracle Marketing, TCA is a mandatory dependency, and must be setup properly.
Conditional Dependencies: Oracle applications and modules that extend or enhance Oracle Marketing functionality via integration. Implementing these dependencies is conditional based on business requirements and practices, functionality desired, and licensing.
Applications and modules defined as mandatory must be setup prior to implementing Oracle Marketing. The setups, however, are generally partial and limited to basic functions that are specifically needed for Oracle Marketing.
For example, Oracle Inventory is a mandatory dependency for Oracle Marketing's product functionality. However, to enable products for marketing purposes, you do not need a full Oracle Inventory implementation.
See the following sections for more information on setting up mandatory dependencies:
Oracle CRM Application Foundation provides a common infrastructure upon which all Oracle CRM applications are built. By providing a set of application components, CRM Application Foundation ensures that all applications interact with key business objects in a consistent manner.
Resource Manager is mandatory for an Oracle Marketing implementation. This component enables you to use application resources regardless of where they are created. Acting as a central repository, Resource Manager enables the creation of various types of resources, groups, teams, and roles.
You can import resources such as employees, suppliers, parties, or partners, created in other applications. Once imported, the resource becomes available for other applications to use.
Resource Manager enables:
Groups
Roles
Role Types
Employee Import
Task Manager is mandatory for an Oracle Marketing implementation. It provides a mechanism for your application to respond to customer needs in a timely manner. Using Task Manager you can create, assign, manage, sort, and prioritize tasks. To assign a task to a specific user, or logged in user, you need to set the profile Task Manager: Default Task Owner at the user level, and the profile value should be the resource name associated with the logged in user. For example, if the resource name is Johnson, then Johnson should be set as the profile value.
After defining a rule and assigning it an appropriate responsibility, if you wish to implement task transition rules, set the profile Task Manager: Default Task Status at the user level. You need not set this profile if rules are not assigned to any responsibility. In this case, the status LOV displays all the statuses.
Interaction History is mandatory for an Oracle Marketing implementation. It provides a common framework for capturing and accessing all interaction data associated with customer contact. Acting as a central repository, it provides a consistent API for tracking all customer interactions within the Oracle E-Business Suite.
For example, if using the tracking mechanism within Web marketing, each response (each time a customer responds to a Web ad) is tracked in Interaction History.
If using email, fax, print schedules, email notifications (or if using the features of email notifications on fulfillment rules) Oracle One-to-One Fulfillment is a mandatory setup. The fulfillment engine supports high volume electronic fulfillment of documents.
When implementing Oracle One-to-One Fulfillment, the following conditions must be met:
Fulfillment Server is created: A Fulfillment Server is an instance of the request processing software.
Fulfillment Group is created: Fulfillment group is used to group agents (users) together.
JFT Fulfillment Admin role is assigned to the Implementor: This role gives access to the Fulfillment administration console for setting up fulfillment, creating master documents and viewing request history. This role and responsibility only needs to be assigned to a Marketing user only if he/she will also be administering the Fulfillment activities (for example, setting up Fulfillment servers, agents, etc.). Typically, only a Marketing Administrator is involved in these activities.
AMS: Enable Fulfillment is set to Yes
Consult Oracle One-to-One Fulfillment documentation for more information.
Oracle Applications Object Library (AOL) 12.0 enables a multiple language and currency setup for the Oracle Marketing implementation. After being enabled, you can determine the set of languages and currencies to be used.
For more information see Oracle Applications Concepts and Oracle Applications System Administrator's Documentation Set.
Basic accounting information for Oracle Marketing is provided by Oracle General Ledger (GL). Because Oracle Inventory requires at least one organization and associated set of books, at least one business unit must be created in GL.
To implement GL for Oracle Marketing, you must setup the following:
Accounting Calendar Types
Accounting Calendar
Currencies
Currency Conversion Rates
Currency Conversion Rate Types
Set of Books
The Marketing Calendar defined by this task becomes a value in the LOVs for the profile AMS: Marketing Calendar.
To define the Marketing Calendar, log in to Oracle Forms with System Administrator responsibility.
Navigation: Profile > System
Notes
Application: Specify the application for which you want to define the Calendar.
Profile: Search and select the AMS: Marketing Calendar profile.
Site Level: You can view available AMS: Marketing Calendar options. Select the appropriate Accounting Calendar.
For information about creating the Marketing Calendar, see Setting Up the Marketing Calendar.
The Oracle Human Resources Management System (HRMS) stores information related to your organization. For detailed Oracle HRMS information, consult Using Oracle HRMS - The Fundamentals.
For an Oracle Marketing implementation, see the following sections for information on the HRMS setups that must be performed:
The responsibilities and navigation paths for performing HRMS tasks is different depending on the terms of your license (shared vs. full).
Shared HRMS lisence: Create employees using CRM Foundation.
Responsibility: CRM Administrator
Navigation Path: CRM Foundation > Resource Manager > Maintain Employees > Employees
Full HRMS lisence: Create employees using HRMS.
Responsibility: HRMS Manager
Navigation Path: People > Enter and Maintain
In this step you are creating sub organization types. For example, if the organization is divided into business groups, then create an organization type called Business Group.
This procedure adds values for a specific lookup “Organization Types (ORG_TYPE)”. If the organization is divided into subsidiaries, create an organization type called Subsidiary.
In Oracle HRMS, you will set up each physical site where your employees work as a separate location. You can set up:
Global locations: Available in all Business Groups.
Business Group locations: Available in one Business Group.
Similarly, you enter the addresses of external organizations that you want to maintain in your system, such as employment agencies, tax authorities, and insurance or benefits carriers. When setting up internal or external organizations, you select from a list of these locations.
The business group is the largest organizational unit representing the enterprise. A Business Group may correspond to a company or corporation, or in large enterprises, a holding or parent company. It can be an organization with a physical location, or it may be an abstract representation of a legal entity that employs people assigned to work in organizations beneath it.
A default business organization has been set up for you, therefore this step is not required for Oracle Marketing to be fully operational. However, you must set up an organization if you plan to use any financial ERP applications in the future.
The first organization to set up is the Business Group and all other organizations will belong to it. Below the Business Group, you represent the groupings in which employees work, such as branches, departments or sections, by means of internal organizations. To enable the assignment of employees to an internal organization, you classify it as an HR Organization.
In this step, you will be defining the security level for specific Marketing Responsibilities. To do this, use the profile HR: Security Profile. This profile enables access (based on responsibility) to a single business group.
Notes
HR: Security Profile, Site level: The organization selected is the business group that users will have access to. They will have access only to records within this business group.
Validate that the setting for HR: Business Group is the same organization as the HR: Security profile.
To perform the HRMS task of creating a Legal Entity, Operating Unit, Organization use the following information:
Prerequisites: Appropriate HRMS Manager responsibility
For more information on determining this, see Determining the HRMS Navigation Path.
Adding a Legal Entity Notes
Organization Classification Name: Enable GRE / Legal Entity and select a Set of Books
Adding an Operating Unit Notes
Classification: Is used to determine the purpose and use of the Operating Unit
Adding an HR Organization Notes
HR Organization: The organization to which employees are assigned
A business unit is an organization such as a plant, warehouse, division, department, and so on.
Notes
Organization Classification: Is used to determine the purpose and use of the organization
Oracle Marketing requires the implementation of a Multiple Organization Structure. Please refer to Oracle Applications Multiple Organizations Implementation Guide for additional information.
You will assign Multi Org responsibilities to a selected Oracle Marketing responsibility. This displays the appropriate Business Unit when using that responsibility.
Oracle Inventory serves as the repository for items that can be used in Oracle Marketing. Items stored in Oracle Inventory reside in the MTL_SYSTEM_ITEMS table.
Oracle Inventory requires one inventory organization to be identified. Typically this is the Master Inventory Organization. If you need to separate products (sold from each operating unit) into different inventory organizations, create a separate inventory organization for each operating unit.
Implement Oracle Inventory as described in the Oracle Inventory Implementation Guide.
Oracle Marketing derives its product data using the product catalog provided by Product Lifecycle Management (PLM). PLM provides a product hierarchy located in the OLTP schemas. This hierarchy is maintained by the user in a product catalog and is expanded to a de-normalized table (designed for efficient traversal) by the Oracle Sales and Marketing applications.
For more information about implementing PLM for Marketing see Implementing Oracle Product Lifecycle Management.
Oracle Content Manager (OCM) is the content management system for Oracle Marketing. OCM has a central repository that manages the content types using folders, versions, and translations. You can work with outbound collateral content for non-direct marketing activities such as advertising, in-store and press activities. You can set up, define, and attach media clips, print ads, and other offline media for use in the Campaign activities. And for leads generated on such advertising activities, you can preview the Outbound Collateral for efficient lead follow up. By providing content management building blocks, Oracle Marketing stores the following content in OCM:
Attachments: Stored in the default folder set up in OCM. When a user adds attachments to a cover letter, by default they are created in this folder. The user can change the folder to store attachments in the user interface. Attachments for emails are stored in the folder 'Attachments'.
Marketing Cover Letters: Stores Fulfillment Cover Letters (also referred to as Templates) used in Oracle Marketing in the default folder created in OCM. When a user creates a cover letter, he or she has an option to change this location. The appropriate option in this drop-down is: OMO Directory and all its subdirectories excluding Requests subdirectory.
Queries: Stores all the fulfillment Queries defined in Oracle Marketing in the default folder created in OCM. When a user creates a custom fulfillment query using the Oracle Marketing Admin screens, by default the content is stored in this directory. The user can change this folder if required.
Deliverables: Stores all deliverable e-mail content in the default folder created for it in OCM. When a user creates e-mail content for the marketing deliverable object, by default it is created in this directory.
Print Advertisement: Stores all web advertisements defined in Oracle Marketing in the default folder created in OCM. The user can change this location during the print advertisement creation flow.
Media: Media related files such as .wav files and billboard content are stored in the default folder created in OCM. This is used for non-direct marketing activities such as television spots and radio commercials.
For more information on how OCM is integrated with Oracle Marketing for direct marketing fulfillment, see Fulfillment Setup in Implementing and Administering Direct Marketing Fulfillment.
Each user (or type of user) has a specific collection of responsibilities. Before assigning responsibilities to a user, the employee must be created in the HRMS. After the employee has been created, you can create the user and assign responsibilities and a default application ID.
To create marketing users:
Create the employee
Define a User by adding responsibilities
Set the default application and responsibility
Import the employee
Grant access to Audience and Administration tabs
Update group access
The first step in creating a user is creating the employee in HRMS.
Prerequisites: HRMS Manager Responsibility
Navigation: People > Enter & Maintain
Notes
Social Security #: The information entered here will be checked against existing social security information
Assignment Region Notes
Update: Use to create a new record
Correction: Use to revise existing data
After creating the employee in HRMS, you can add responsibilities to it.
Based on your functional requirements, add one or more responsibilities to your user.
Navigation: Security > User > Define
For more information about creating Marketing users see:
The Campaign Dashboard allows you to review key marketing initiatives, such as activities, campaigns, and lists. It allows managers to review the performance of the current or past initiatives, and displays the campaign performance data. For daily operations, this page also provides easy access to the recent campaigns and activities and allows navigation to all other marketing functions that a user can access based on the responsibility you assign.
The dashboard allows the user to access initiatives through tabs such as Short Cuts, Quick Actions, and Related Links. Alternatively, it also allows search options such as New Search, Saved Search, and Quick Find.
You can search for the following initiatives:
Activity: Retrieves campaign activities including events.
Campaign: Retrieves a campaign.
List: Retrieves a list.
Model: Retrieves predictive models for a campaign.
Program: Retrieves all the programs in a campaign.
Scoring Run: Retrieves the scoring run of a campaign.
Source Code: Retrieves the source code of a searched initiative.
Note: Scoring run and Source Code are retrieved only through the New Search option.
When a user logs into the Campaign Workbench and creates a new campaign, the campaign is in the New Status. This campaign contains basic campaign attributes that the user may update based on the locking rules set by a Marketing Administrator. The same holds true for activity creation. However, a few basic attributes are hidden by default, depending on the user responsibility. You need to log in as the Marketing Administrator and enable these attributes for the users to see them. For more information on Locking Rules, see Implementing Locking Rules.
The following attributes are hidden in the Dashboard:
Purpose
Start and End Dates
Inherit the Source Code from Parent
Triggered by Monitor
This activity attribute is hidden only if the activity is triggered based on a monitor. For more information on Monitors, see Implementing Monitors.
The Campaign Workbench consists of sections or bins with operational data for the user. This data contains past or present program and/or campaign performances and enables the user to track the progress of campaigns and activities. It helps the user navigate the Workbench better.
The table below lists the sections.
| Bin Name | Description |
| Campaign Gantt Chart | Enables the user to review the time-line for the Campaigns retrieved based on the view selected by the user. The user can expand the Gantt chart for the Campaign Activities of each Campaign listed in the bin. The Gantt chart is hidden by default. You need to log in as the Administrator and enable this bin for a specific site and place it as the first bin in the Dashboard if required. |
| Open Tasks | Enables the logged in user to see the open tasks associated with a campaign and activity that he or she owns or the team has access to. |
| Triggered Monitors | Displays the monitors in the Triggered status. The user can check the condition of the initiatives associated with the triggered monitors. |
| Campaigns | Displays the campaigns retrieved based on the view selected by the user. The user can personalize this bin and search for specific campaigns and campaign attributes to review. |
| Trend Chart | Displays the marketing trend for a selected Metric of the top five campaigns listed in the Campaigns Bin view. |
| Activities | Displays the activities retrieved based on the view selected by the user. The user can personalize this bin and search for specific activities and activity attributes to review. |
| Recently Updated Campaigns | Displays the campaigns recently updated by the logged in user. |
| Recently Updated Activities | Displays the activities recently updated by the logged in user. |
| Shortcuts | The user can access the marketing functions on the Dashboard by clicking the shortcuts links. |
The Campaign Workbench provides personalization options for each section or bin. The user can navigate to the standard OA Personalization Page where he or she can create personalized views to search for and select Campaigns and/or Activities. The personalization options are available as links in each bin. For example, for the bin 'Active Activities', a link 'Personalize Activities Bin' is available.
The Shortcuts links on the right side of the dashboard enable users to easily navigate to their desired initiatives. However, the following links are hidden by default depending on the user responsibility:
Create Program
Create Campaign
Daily Business Intelligence
To enable the Create Program and Create Campaign links, you need to edit the JRAD XML file CampDashNavigationv2RN.xml from the webui directory in the following path: oracle/apps/ams/mds/campaign. The 'rendered' attributes for these two links should be set to 'True' instead of 'False'.
To enable the DBI link, ensure that the user sets up the function BIM_I_MKTG_MGMT in the menu hierarchy.
You can assign a default application and default responsibility to the Implementation user.
Notes
In the Find System Profile Values Form, at the User Level, search for the user who will be assigned to this application and responsibility.
Profile: enter JFT%DEFAULT%.
JTF_PROFILE_DEFAULT_APPLICATION: Set this to 530
JFT_PROFILE_DEFAULT_RESPONSIBILITY: Set this to 21706 (Oracle Marketing Super User)
Log in to Oracle Forms with CRM Administrator responsibility. Locate and import the employee as a Resource. Accept the default values. Remember to record the transaction number.
Navigation: Resource Manager > Maintain Resources > Import Resources
Run the Concurrent Program AMS: Group Access Refresh to complete the process of creating the Implementation user.
Marketing departments have global and regional operations at their respective levels. But they are not always synchronized with their financial structure. They use their resources such as audience, budgets, and campaign activities, without being able to share the resources globally. Despite a need to share resources between corporate and regional marketing entities, there is also a need to control the access of marketing objects between these departments to avoid misuse. Multi Org Access Control (MOAC) helps the Marketing departments achieve this goal.
Oracle Marketing does not use the MOAC functionality to implement access control, or create financial transactions in any of the financial applications. However, it is aware of MOAC and stores Organization IDs for marketing objects, which are used to set the Default Operating Unit for a marketing object while creating a budget for that object. The current profile MO: Operating Unit is replaced with two new profiles: the Security Group Profile and the Default Operating Unit profile. The Oracle Marketing Administrator must derive the operating unit from the Default Operating Unit profile for the user.
Sales Campaigns help sales managers generate sales growth and equips them to explore their install base and historical customer data, and to mine that data for cross-sell and up-sell opportunities. Sales managers can quickly create and execute campaigns to push these opportunities out to their territories, along with a coordinated sales methodology. These opportunities are considered for marketing purposes such as list generation, queries, and creating data sources for Audience management.
Organizations can create sales methodologies that match their requirements for different product lines, sales channels, organization units, or marketing campaigns. You can access these sales methodologies when you create and manage leads and opportunities. Each stage of the methodology has a sales wizard, called the coach, which comprises a series of questions regarding that sales stage, or provide you with sales stage information. The sales coach assists you by reminding you of points and issues to consider and procedures to follow during the sales effort. Additionally, you can export summaries of the sales coach data into printable worksheets that can be used during review meetings and training sessions. For more information on sales methodologies, refer to the Oracle Sales User Guide.
Oracle Marketing's conditional dependencies can be categorized as follows:
Optional Marketing and Partnering Enhancements: Additional modules that are implemented along with Oracle Marketing that are part of the Oracle Marketing and Partnering product family.
For example, you can purchase Oracle Trade Management (which is part of the Oracle Marketing and Partnering family of applications) to implement along with Oracle Marketing. This is an optional component that enables advanced budgeting, claims, claims settlement, and trade planning.
Optional Integrations: Applications implemented in addition to Oracle Marketing. Any application that is not part of the Oracle Marketing and Partnering product family.
For example, Oracle iStore can be implemented along with Oracle Marketing. Used in conjunction with Oracle Marketing, iStore provides a Web storefront for online Web advertisement and execution. This functionality is optional, is not required for Oracle Marketing to function properly, and is therefore considered an optional integration.
When implementing basic Oracle Marketing, you can optionally implement additional Marketing and Partnering applications.
The following can be implemented with Oracle Marketing:
Designed for the consumer goods sector, Oracle Trade Management provides additional B2B functionality used to:
Control costs related to promotions
Track deals made with retailers, distributors or partners
Process claims and deductions
Automate and track funds management and promotional spending
Note: Oracle Trade Management must be purchased separately.
For Oracle Trade Management implementation details, see the Oracle Trade Management Implementation Guide.
Oracle Partner Management assists an organization in maintaining, tracking, managing, and communicating with its partners. When implemented with the rest of the Oracle E-Business Suite, you can manage leads, track and share opportunities with partners, forecast sales, manage partner and customer information, send outbound information, and calendar activities, tasks and notes.
Note: Oracle Partner Management must be purchased separately.
For Oracle Partner Management implementation details, see the Oracle Partner Management Implementation and Administration Guide.
Oracle Leads Management enables you to automate and optimize prospect-to-sales conversion across the enterprise. Leads Management provides a staging area for all prospect leads for data quality processing, prioritization and distribution, enterprise review, and conversion. When implemented in conjunctions with the rest of the Oracle E-Business Suite, Oracle Leads Management enables you to effectively convert prospects into sales by tracking lead activity, aging, and closure.
Note: Oracle Leads Management must be purchased separately.
For more information see the Oracle Leads Management Implementation and Administration Guide.
Implementing Oracle Territory Manager is optional. It provides an infrastructure to define territories based on flexible criteria, such as geography, zip code, area code. This engine creates automatic assignment of transactions across the entire CRM suite. For example, leads and opportunities are routed through this engine to the appropriate sales professionals.
See Oracle Territory Manager Implementation Guide for more information.
Web Applications Desktop Integrator (Web ADI) brings Oracle E-Business Suite functionality to a spreadsheet, where familiar data entry and modeling techniques can be used to complete Oracle E-Business Suite tasks. You can create formatted spreadsheets on your desktop that allow you to download, view, edit, and create Oracle E-Business Suite data. Data entry shortcuts (such as copying and pasting or dragging and dropping ranges of cells) or even using formulas to calculate amounts, can all be used to save time. You can combine speed and accuracy by invoking lists of values for fields within the spreadsheet. After editing the spreadsheet, you can use Web ADI’s validation functionality to validate the data before uploading it to the Oracle E-Business Suite. Refer Oracle Web Applications Desktop Integrator Implementation and Administration Guide for information on Web ADI implementation.
Oracle Marketing integrates with Web ADI to provide marketers with a spreadsheet interface to create and update campaign activity data. For more information on implementing Web ADI for Marketing, see Implementing and Administering Web ADI Integration.
Oracle Marketing uses Oracle Receivables to record customer information. Customer registration information is maintained in the Trading Community Architecture (TCA). TCA stores all customer, partner, prospect, and other customer related information in a single repository. This enables consistent message delivery across all channels.
Setting up Oracle Receivables is optional, and customers can set it up for tax options and address validation, as described in the Oracle Receivables User Guide.
Optionally, Oracle Marketing can be integrated with a variety of other applications to extend its functionality. The following is a list of common integration points for Oracle Marketing:
Data Mining is an analytic feature providing a complete enterprise view of the Oracle Marketing business flows. Using extensive analytical and reporting capabilities, all personnel within and organization can monitor the status of marketing activities in real time. Data Mining functionality is included in an Oracle Marketing license. However, the decision to implement fully is optional.
Oracle Sales Online (OSO) is an application designed for field sales representatives, sales managers, and executives. The application provides a complete set of tools that enables sales teams to manage the sales cycle from beginning to end. OSO supports the key functions of the sales cycle, with features such as:
Lead and opportunity management
Forecasting
Quote generation
Order placement
Sales methodologies
When integrated with Oracle Marketing, the critical link in the Campaign to Cash business flow is fulfilled, providing the information to analyze the success of company campaigns. The system enables campaign to cash flow tracking as the source code can be tracked from campaigns to orders.
When integrated, you can also create Sales campaigns as a Sales tool to quickly create and execute cross sell/up sell campaigns that target existing customers.
For more information about implementing and using Oracle Sales Online, see Oracle Sales Implementation Guide.
Oracle Telesales (OTS) is an application designed for inside sales professionals, inbound telesales agents, or outbound telemarketing agents. OTS offers a multi-channel selling solution that manages leads, opportunities and forecasts across all sales channels: over the phone, the Web or through mobile devices. It provides a set of tools to help the inside sales team manage the sales cycle from prospecting for customers to booking the order.
When integrating Oracle Marketing and Oracle Telesales, marketers can use the Oracle Marketing List Import feature to assign lists to TeleSales Agents. A TeleSales agent can then use the Universal Work Queue to access the list of customers assigned to them by the marketing team. For implementation details see Implementing List Import for Universal Work Queue.
Oracle Interaction Center is an integrated series of products designed for consistent and effective handling of customer interactions. It provides sophisticated routing, media queuing and enhanced screen pops integration. Interaction center reduces the cost, complexity and risk associated with deploying applications. Interaction Center consists of the following modules:
Advanced Inbound
Advanced Outbound
Email Center
Interaction Center Intelligence
Scripting
Universal Work Queue
Oracle Scripting is a set of tools to facilitate the process of gathering of information through guided decision flows, consisting of text, questions, and answers. Oracle Scripting is composed of several components: the Script Author, the Scripting Engine, the Scripting Administration console, and the Survey Administration console.
When Oracle Marketing and Oracle iStore are integrated, you can use the eMerchandising module of Oracle Marketing to personalize Web advertisements for Oracle iStore. Using this functionality, a marketer can make recommendations for customers. Store personalization and customer-specific recommendations are accomplished through specialty store Web postings from eMerchandising and store Event capture.
Web Application Desktop Integrator or Web ADI is a tool that brings Oracle E-Business Suite functionality to a spreadsheet, where familiar data entry and modeling techniques can be used to complete Oracle E-Business Suite tasks. For Oracle Marketing, the worksheet provides a quick and simple means to create and update multiple campaign activities from the Campaign Workbench, within and across campaigns.
Use the following sections to implement and administer Web ADI for Marketing use:
Implementing Web ADI Integration
Administering Web ADI Integration
To implement the Web ADI integration, you need to run the following concurrent programs:
AMS : Schedules Import: this is used to import new schedules
AMS: Media Planner Loader: this is used to map metrics data from the interface table to schedule metrics. If metrics already exist for the schedule, the metric values are updated. If the metrics do not exist, new metrics are created for the schedule.
To administer Web ADI for Oracle Marketing, see the following sections:
Web ADI Templates
Customizing Web ADI Templates
Security Requirements for Web ADI
A Web ADI template is a combination of a spreadsheet interface consisting of a set of columns, the mapping of attributes from each of these columns to the appropriate column in the underlying data store, and the logic to create or update the data with the necessary validations.
As an administrator, you can customize Web ADI templates for marketing use. See Customizing Web ADI Templates.
The seeded Web ADI templates include:
Media Planner
This template can be used for working with metrics for a large number of Campaign activities.
Schedule Metadata Mass Update Worksheet
This template can be used for mass update of basic identifying schedule attributes. Sample scenarios where this template may be used:
The marketing manager needs to adjust the dates of the Campaign Activities for a specific Campaign for which the dates have changed
The marketing administrator needs to mass update the ownership of campaign activities when the current owner leaves the marketing department
The marketing manager needs to cancel a set of campaign activities
To customize a Web ADI template, you can copy a seeded Web ADI template, make the necessary changes to it, and save it as a new Marketing usage specific layout.
Oracle Discoverer is a business intelligence/analytics application that is often implemented with Oracle Marketing for list management purposes. Oracle Marketing supports Discoverer 10.1.2.
When implemented, a Discoverer end user layer (containing Oracle Marketing business areas) can be launched from within the Oracle Marketing application. Using this interface, a list manager can create and manage workbooks and worksheets needed for list management purposes.
You can create a list of person and organizational contacts -- and the organization information can be part of the attribute in organization contact list. When creating a list from Discoverer, you will need to select a mandatory identifier, which is a constant key. The other fields including "include organization", "include email", etc. are optional depending on what kind of list you want to generate.
To implement Oracle Discoverer for Oracle Marketing purposes, use the procedures below. After performing these procedure, Oracle Discoverer launches with a single sign-on from within Oracle Marketing.
Set the following profile options.
| Option | Required | Level | Setting | Effect/Limitation |
|---|---|---|---|---|
| ICX: Discoverer End User Layer | Yes | Site | User Defined | EUL prefix for Discoverer, usually EUL4. |
| ICX: Discoverer Launcher | Yes | Site | User Defined | URL to launch Discoverer Web version. |
| ICX: Discoverer Viewer Launcher | Yes | Site | User Defined | URL to launch Discoverer viewer. |
| ICX: Discoverer Use Viewer | Optional | Site | Yes/No | Whether to use viewer instead Web Discoverer. Defaulted to No. |
This procedure will populate the LOV for the List functionality.
| Key | Type | Seeded Values | Meanings |
|---|---|---|---|
| AMS_LIST_ ACT_TYPE | User | Employee List List |
Target group list selection type. |
| AMS_LIST_ DEDUP_ TYPE | User | List Import Consumers Import Organizations |
Type of Deduplication Rules to be applied. |
| AMS_LIST_GENERATION_TYPE | System | Full Refresh Append New Records Update Attributes Only |
Full refresh of all the entries. New entries meeting the criteria added. Only the attributes of the entries updated. |
| AMS_LIST_ ROW_ SELECT_ TYPE | System | Nth Record Random Standard |
How to select rows during list generation. Standard is top down selection. |
| AMS_LIST_ SEGMENT_ STATUS | User | Archived Available Cancelled Draft Expired |
Archived Available Cancelled Draft Expired |
| AMS_LIST_ SEGMENT_ TYPE | System | Workbook SQL |
Two types of segments supported. Based on a Discoverer workbook or an SQL statement. |
| AMS_LIST_ SELECTION_ ACTION | System | Include Exclude Intersect |
How each selection is added to the list. Exclude means that all entries that exist in the excluded list are removed from the current list. Intersect causes the current list to become a list of only those entries which are on the intersected list and the current list. |
| AMS_LIST_ SELECTION_ TYPE | System | Segment Workbook Import List List SQL |
Segment Workbook Import List List SQL |
| AMS_LIST_ STATUS | System | Archived Available Cancelled Draft Executed Executing Generating Locked New Pending Reserved Scheduled Validated Validating |
Archived Available Cancelled Draft Executed Executing Generating Locked New Pending Reserved Scheduled Validated Validating |
| AMS_LIST_ TYPE | System | Manual List Standard List Suppression List Target Group |
List of possible list types. Note where these appear in the program. |
Run the following Concurrent Programs for Lists:
| Concurrent Manager | Required | Description |
|---|---|---|
| AMS : Refresh Party Market Segments | Optional | Generates a list of parties in the segment. This program also updates the size information for all segments so a history of segment sizes may be maintained. |
| AMS : Generate Suppression list | Optional | Updates and maintains organization defined suppression lists. This is in addition to seeded suppression lists. |
| AMS : Purge Target Group | Optional | After a target group has been generated and used, this program lets a user purge the list entries. |
| AMS : Purge Imported List | Optional | During the import process, the user may specify an expiration date or number of uses for a list. This program removes those entries whose expiration date has passed or number of uses reached. Optional Parameter: force_purge_flag. This parameter indicates whether to purge a record regardless of the associated campaign status. The default value is No. |
| Workflow Background Process | Required | The System Administrator must run this program. It populates List generation and target Group Generation data. Parameters: Item Type: AMS List Generation Process Deferred: Yes Process Timeout : yes Process Stuck: yes Ignore Minimum and Maximum Thresholds |
To create the Discoverer End User Layer (EUL), you must create a database user and give the appropriate Applications (APPS) grants to that user. This sets the Discoverer End User Layer (EUL) for all APPS.
For specific information about Installing Oracle Discoverer, see Oracle Discoverer Implementation Guide .
To create the Oracle Marketing EUL for Discoverer, Oracle Marketing and Oracle Discoverer must be installed. Use the following steps to create an EUL.
Open a DOS prompt.
Navigate to the directory where Oracle Discoverer Admin edition is installed. For example, if Oracle Discoverer Admin is installed in D:\orant\discvr4, type:
a) d:
b) cd\orant\discvr4
If the database schema has not previously been created, run the following:
dis4adm.exe
/CREATE_EUL
/APPS_MODE
/CONNECT system/manager@tst115rw (enter in your password and TNS Name entry in place of “manager” and “tst115rw” respectively).
/PASSWORD eul
/DEFAULT_TABLESPACE user_data (enter your tablespace names in place of “user_data”)
/TEMPORARY_TABLESPACE temp (enter your tablespace name in place of “temp”)
/SET_EUL_LANGUAGE US
/APPS_GRANT_DETAILS apps/apps (enter your Oracle Applications Foundation username and password for "apps" and “apps” respectively).
/SHOW PROGRESS
If the database schema has previously been created, run the following:
dis4adm.exe
/CREATE_EUL
/APPS_MODE
/CONNECT eul_us/eul_us/eul@tst115rw (The “eul_us” should be the name of the database schema previously created.)
/APPS_GRANT_DETAILS apps/apps (username and password)
/SHOW_PROGRESS
The Oracle Discoverer End User Layer (EUL) contains the Oracle Marketing Business Areas. By importing the Discoverer EUL, these business areas become available for List Management. Alternatively, you may manually import the EEX files from the Oracle Discoverer Admin interface. Before you import the EUL, ensure that the MKS Toolkit is implemented.
Use the following steps to import the Discoverer EUL:
Start the Korn Shell (MKS Toolkit).
From the NT box where Discoverer Admin is installed map the $AU_TOP/discover directory or copy the eex files to the NT box and specify this directory as 'topdir' directory when running the utility.
APPS User/Responsibility must be specified for import. The imported workbooks will be saved under the specified APPS User.
On the new EUL make sure the APPS User does have full access privileges to use Discoverer Admin Edition.
Use the parameter file so that you don't have to specify all values on the command line.
sh adupdeul.sh
connect=<username/password{@<two_task>}
connect=<username/password{@<two_task>}
resp=<APPS responsibility name>
gwyuid=<APPS GWYUID>
fndnam=<APPS FNDNAM>
secgroup=<APPS responsibilty security group>
topdir=<top level directory where discoverer
files are available>
eulprefix=<EUL prefix (for ex EUL4 for EUL4_US)>
language=<NLS language code>
eultype=<OLTP|EDW> default OLTP
{ parfile=<name of parameter file> }
{ mode=<COMPLETE or DRIVER> default DRIVER> }
{ driver=<list of driver files to be loaded
separated by a "," (comma)> }
{ exedir=<directory where discoverer executables are located>}
{ logfile=<log file name, default adupdeul.log> }
Example
Copy the directory $AU_TOP/discover/US to C\bblock\import\au_top\discover\US.
With Admin Edition connect as EUL owner EUL4_US/EUL@mydb and grant privileges for Admin Edition to apps user SYSTEST.
In Korn Shell CD C\bblock\import
Specify parameter values in a parameter file, for example:
parfile.lst eulprefix=EUL4 exedir=D/orant/discvr4 mode=COMPLETE topdir=C/bblock/import/au_top/discover eultype=OLTP fndnam=APPS gwyuid=APPLSYSPUB/PUB resp="Business Views Setup" secgroup="Standard"
Start the full import, all eex files in the topdir.
sh adupdeul.sh connect = systest/welcome98@mydb parfile = parfile.lst language = US logfile = imp_010314_EUL4_US_mydb.log
Or start the import for just the files of specified ARU copy file drivers.
sh adupdeul.sh connect = systest/welcome98@mydb parfile = parfile.lst language = US mode = DRIVER driver = c1641981.drv logfile = imp_010314_EUL4_US_mydb.log
For the first time to import, it is recommended to use mode=COMPLETE.
Set the following ICX profiles in Oracle Applications at the responsibility level:
ICX _PROFILE ICX_DISCOVERER_LAUNCHER
URL that points to the Web Discoverer Server
Example
http://machinename.domain/diswb4/html/discolaunch.htm?Connect=[APPS_SECURE]
ICX _PROFILE ICX_DISCOVERER_VIEWER_LAUNCHER
URL that points to the Discoverer Viewer
Example
http//machinename.domain/discoverer4i/viewer?cs=[APPS_SECURE]
ICX_PROFILE ICX_DEFAULT_EUL
This in combination with the language code make up the EUL owner at runtime. Example EUL4 (not EUL4_US)