Oracle business partner program

BenefitDescription string The text describing the benefits. CorpCurrencyCode string The corporate currency code associated with the record. CreatedBy string The user who created the record.

CurcyConvRateType string The currency conversion rate associated with the record. CurrencyCode string The currency code. DeleteFlag boolean Indicates whether the record can be deleted or not. EligibilityDescription string The text describing the eligibility criteria to enroll into program. EnrollmentApproverUser string An approver of the program enrollments. FeesAgreementDescription string Text describing the agreement criteria.

LastUpdatedBy string The user who last updated the record. MeasureDescription string The text to describe objectives listed for this program. ObjectVersionNumber int The number used to implement locking. Primary Key. Contained by. Handled by. The approval comments. The text describing the benefits. The user who created the record. The date when the record was created. The currency code. Indicates whether the record can be deleted or not.

The text describing the eligibility criteria to enroll into program. The date after which the record becomes inactive. The inventory LOV uses certain attributes to identify an inventory item as a potential partner program.

The following values must be provided when creating a partner program as an inventory item:. When automatic creation of inventory items is disabled, because the partner program pricing is associated with the partner program inventory item, the program pricing must be set up in the Oracle Advanced Pricing application.

When automatic creation is disabled, you can associate a partner program with an inventory item even without pricing set, but you cannot activate it until pricing is set up for the associated inventory item. In previous releases, an inventory item was created automatically for each partner program. However, if a partner program does not have a fee, creating the inventory item is unnecessary, because the item is not orderable.

If a partner program is active and has enrollments, you cannot change the association between the inventory item and the partner program. In order for a partner to successfully enroll in a program with a fee, the following must be performed:. If your enterprise has more than one operating unit, be sure that when you create an inventory item for a partner program, you make it available for all inventory organizations.

Oracle Partner Management uses the AMS: Item Validation Master Organization profile option to determine the master inventory organization in which partner programs will be stored as items.

The profile setting should be the name of the organization and set at the Site level. If this profile is not set, then the user will see an error when accessing the inventory LOV if automatic creation of inventory item is disabled or when creating a program with fee if automatic creation of inventory item is enabled. This ensures that the unit of measure matches up with your inventory application.

You should not change the UOM after implementation, because the UOM identifies the inventory item as a part of a partner program. You must set the default UOM whether the inventory items are created automatically or manually.

The PV: Default UOM Code profile options is not shipped with any value, but you must set it to any UOM currently available in your inventory program or the application will create an error message. Inventory items are added using a key flex field. This information creates a partner program inventory item when automatic creation of inventory item is enabled.

Oracle Inventory uses one of the segments in the flexfield to uniquely identify each inventory item; each Oracle application that sets up inventory items must populate this segment with information that uniquely identifies its items.

Other segments in the flexfield are used to provide additional information about the item such as company name or business unit. What values must be specified in the segments that precede or follow the segment that uniquely identifies the inventory item. When you set the profile option, you specify appropriate values for the preceding or following segments and enter the code for the program. This segment will be populated with a unique value to make the concatenation of segments unique for each inventory item that gets created.

For example, suppose that the vendor organization's Inventory key flexfield uses four segments to specify an inventory item, and uses ". For a program called Distributors Gold Program, the inventory flexfield would be populated as follows:. Partners might be charged to enroll into a partner program.

Thus, a price needs to be defined for program inventory items in one ore more price lists, which then can be used to determine the appropriate program price for each partner. When the channel manager creates a partner program, he selects which price list or price lists will be used for the program. If the pricing setup can result in finding duplicate prices for a program inventory item, the channel manager must define precedence so that the price with the lowest precedence is selected.

The channel administrator specifies which application is used by setting the profile option QP: Source System Code. This profile is set at the Application level; when the profile is set, the value provided is the name of the pricing application to be used. A variety of payment methods can be set up to help partners pay program enrollment fees conveniently. Payment methods can include cash, credit, check, purchase order, wire transfer, or invoice.

Payment methods are set up based on geographical regions, which allows the vendor to set up different payment options for partners located in different countries or regions, if necessary.

The geographic regions used to specify payment options are set up in Oracle Marketing. Geographic information may already be set up for your implementation. However, if it is not, it can be set up by a user with Oracle Marketing administration access. Use this procedure to add a payment rule to specify available payment methods by geographic regions from the Payment Option Details page.

Note : This setup is not mandatory. Geography Level: Indicates the level at which the payment option applies, for example, country or state. Geographic Region: Further defines the geographic information. The regions options are determined by the Geography Level selected previously. For example, if you select Country as the Geography Level, the Lookup for Geographic Region lists all countries stored in the Oracle Marketing application. This lookup is shipped with all the payment types enabled.

For wire transfer, you must set the Allow Multiple Payments system parameter to Yes in Oracle Order Management for each operating unit that is associated with a partner responsibility. A benefit is a feature of a program that provides value to a partner, for example:. A benefit can be associated with one or more partner programs.

Benefits are associated with partner programs, and are granted to a partner organization through partner program enrollment. The channel administrator sets up benefits from the Benefit Administration page.

When setting up a benefit, the administrator selects the type of benefit to be created from the list of available benefits, which include deal registration, soft fund, referral, and other. Numerous benefits of the same type can be set up; for example, the vendor might want to offer different soft fund benefits to different types of partners. Setting up a soft fund also referred to as a partner fund , deal registration, or referral benefit involves specifying additional steps, such as assigning a budget to the benefit or associating products with it.

Additional information about creating a deal registration benefit, partner fund benefit, and referral benefit is presented in each benefit's specific chapter. Opportunity management and special pricing functionality are also made available to partners through benefit creation.

To set up these types of benefits as well as benefits such as access to mailing lists or Oracle iStore , the channel manager creates a benefit of type Other.

Refer to the chapters on Special Pricing and Opportunity Management for more information. A locking rule locks a partner program field to further editing. More specifically a locking rule specifies that a field can not be edited when the partner program is in a certain status.

For example, you might want to lock some fields after a program becomes Active. Object Attribute: Select the flow for which you are creating the locking rule. The list of available fields is updated to reflect the fields contained in the flow selected. System Status: Select the program status that will cause selected fields to become locked. Certain fields are seeded in the locking rule and cannot be removed from the Selected Fields area. Mandatory rules allow you to specify fields that are required for program creation.

You can create mandatory rules for each feature or flow that you set up for a partner program. Object Attribute: Select the feature or flow for which you are creating the mandatory rule. The list of available fields is updated to reflect the fields contained in the object attribute selected. Certain fields are seeded in the mandatory rule and cannot be removed from the Selected Fields area.

A vendor can associate legal terms and conditions with membership in a partner program. Terms and conditions are listed in a contract template, which is presented to a partner user who is enrolling into the program. If the partner agrees to the terms, the partner user can electronically accept the terms and conditions or submit the signed contract to the vendor via fax or regular mail based on available contact response options to the partner's geography.

Oracle Partner Management integrates with the Oracle Contract Management, which allows the vendor to create and manage contract templates. A contract template can be attached to a program based on geography and member type. Member type can be used to present global partners with contracts that differ from contracts presented to standard or subsidiary partners. In Oracle Partner Management, the contract template is displayed and not the actual contract.

The program manager selects the type of contract templates or contracts that he wants to associate with a program and attaches it to a partner program. For a contract template to be available in Oracle Partner Management, the program manager or a user with access to Oracle Contract Management must create contract templates with the document type as Partner Program.

Contract templates are created and stored in the Oracle Contract Management Core application. The legal terms that a vendor organization wants partners to agree to might differ based on a partner's geographic location, partner member type or partner user's language. Thus, numerous partner program contract templates may need to be set up in Oracle Contract Management. The channel manager then selects the contract templates that he wants to associate with a specific partner program based on geographic and partner member type criteria.

Oracle Partner Management integrates with Oracle Contracts to provide the terms and conditions that can be associated with membership in a partner program. For example, if you want it to run every five days, you would select days.

This means the data load is configured to be activated after 10 minutes and to run every four days until the following month.

The imported records will appear in the Eligibility Partners list after the data load has run. Before you can do this, you must have the Business Intelligence reports set up and configured properly. Figure 25 shows the partner program load data flowchart. It has an input property called MaxErrors. Default value for this parameter is 1. If there is an error during data load, the job is terminated. It is possible to change this input property on the workflow. If the value is increased to , then 99 data load errors are ignored.

For information on creating a refresh schedule, see Creating a Refresh Schedule. The following is the workflow for using the Analytics Report. The workflow's status changes from In Progress to Completed.

This address should be the full path name. You do not need to restart the Siebel Server for this change to be effective. It is important that the Oracle Business Intelligence report setup is completed and configured properly before you use it to create an eligibility list. Use the following procedure to create an Oracle Business Intelligence report.

The Marketing Account List catalog displays in the left panel. You can use other Channel Partner integration component keys or create a new one. Make sure the key uniquely identifies the record before using it. Channel Partner.