Manage Channel Profile Options

Here you can view and manage profile options for Channel Revenue Management.

  1. In the Setup and Maintenance work area, go to:

    • Offering: Order Management/Procurement

    • Functional Area: Channel Revenue Management/Supplier Incentives

    • Task: Manage Channel Profile Options

  2. On the Manage Channel Profile Options page:

    • The Search Results: Profile Option section displays details of the profile option code, the profile display name, the application and its module that uses the profile option, the start and end dates, and the description of the profile option that you search for.

    • The Profile Option: Profile Values section displays the profile level set for the profile option.

List of Channel Profile Options

This table lists the profile options available for Channel Revenue Management.

Profile Display Name

Profile Option Code

Description

Channel Currency Conversion Type

CJM_CURRENCY_CONVERSION_TYPE

Use this option to specify the conversion rate type to be used during currency conversions at the site level.

Credit Method for Installments

ORA_CJM_AR_CR_MTHD_FOR_INSTL

For Deductions and Settlement

Use this option to specify how installments must be credited in Receivables for transactions with multiple installments, when settling with the settlement method Credit Memo - On Invoice. This option is for the site level. Values can be:

  • FIFO: First in First Out. Credits the first installment first.

  • LIFO: Last In First Out. Credits the last installment first.

  • Prorate: Credits the installments of the credited transactions and prorate them based on the amount remaining for each installment.

Credit Method for Accounting Rules

ORA_CJM_AR_CR_MTHD_FOR_RULE

For Deductions and Settlement

Use this option to specify how the accounting entries must be reversed in Receivables by the settlement method Credit Memo - On Invoice, if accounting rules are used. This option is for the site level. Values can be:

  • LIFO: Last In First Out. Starts from the last accounting period and reverses all prior periods till the credit memo is used up.

  • Prorate: Credits an equal percentage to all the account assignments for the invoice.

  • Unit: Reverses revenue for the number of units specified in the original invoice line.

Calendar Year Filter in Available Accruals Search ORA_CJM_AVAIL_ACCR_CAL_YEAR_FILTER Use this option to specify the calendar year filter used to search available accruals. This option can be used at the site or user levels. The default value is set at the site level.
Group by in Available Accruals Search ORA_CJM_AVAIL_ACCR_GROUP_BY Use this option to specify the association type used to group results in the available accruals search. This profile can be used at the site or user levels. The default value is set at the site level.

Minimum Number of Days of Receipt Data for Initial Load

ORA_CJM_MIN_DAYS_INITIAL_LOAD_RECEIPT

For Supplier Rebates

Use this option to specify the number of days of receipt data that must be processed in the initial (first) run of the Load Transactions process at the site level. When:

N = Minimum Number of Days of Receipt Data For Initial Load

D1 = Start date of the active program with the earliest start date.

D2 = D1 - N

  • If D2 <= Today's date, the initial start date for Load Transactions is D2.

  • If D2 > Today's date, the initial start date for Load Transactions is Today - N days.

  • If there are no active programs, the initial start date for Load Transactions is Today - N days.

  • Default value for Minimum Number of Days of Receipt Data For Initial Load is set as 30 days, if the profile value is cleared or a negative value is entered.

The profile option is used to determine how far back in days your implementation wants to collect receiving transactions from when you first execute the Load Transactions process. This profile is only used the first time you run the Load Transactions scheduled process. After the first run, the application tracks when the process was last performed. So from the next run onward, it collects only the new receiving transactions.

For example, if you're running the first Load Transactions process on Dec 14th and the implementation wants to bring in 1 month of transactions prior to a Jan 1st go-live date, then your initial load on Dec 14th should set Minimum Number of Days of Receipt Data from Initial Load to 14 days.