We provide a professional review of each incident report and accident investigation. 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:. Perform planning and budgeting of your trade promotions from the top down at the headquarter level or from the bottom up at the account level. Former Member replied February 26, at The functional areas include budget, quota, account manager dashboard, offer, claim, indirect sales, and common components.
Budget management gives organizations a comprehensive tool for planning as well as tracking actual spending, whether accrued or immediately incurred, of sales, marketing and partnering activities.
Companies using Trade Management generally write their own reports for specific reporting needs. Trade Management enables you to easily create these reports using the materialized views that collect budget utilization data. You can then use this data to create different reports. To strengthen support for integration with any third party system in any industry, Oracle Trade Management offers a public API.
You can use the Oracle Trade Management dashboard as a single entry point for the iterative selling process. In an iterative sales model sales representatives manage customer accounts and sell products on a continuous and repetitive basis. The features in the Oracle Trade Management Dashboard that address the iterative selling process include the following:.
Oracle Trade Management Offer provides comprehensive support for all types of promotional agreements. Sales users can create and monitor offers on the Account Manager Dashboard. Additionally, sales administrators, marketing managers, pricing managers and partner managers who have full exposure to set advanced pricing and eligibility rules can also create and monitor offers on the Account Manager Dashboard. Oracle Trade Management includes enhanced flexibility in creating volume offers and support for Indirect Sales in Volume Offers.
Volume offers, whether on an off invoice or accrual basis, are frequently used as incentives to customers, buying groups or partners, based on their cumulative purchase volume over a period of time. Oracle Trade Management includes enhanced flexibility in creating, maintaining, and monitoring volume offers and also features support for Indirect Sales in Volume Offers.
Tax classification codes are defined in Oracle E-Business Tax. The tax classification code values are based on whether a settlement method integrates with Accounts Receivable or Accounts Payable.
When you run settlement fetcher the payment details updated on the claim will carry the details of the payment including transaction type and number, date, amount, and status.
All the validations that are performed for check settlement method will also be performed for these three methods as well. Indirect sales is the process of using and managing external sale. Companies receive high volumes of data in different formats from different channels requiring time and resources to sort, cleanse and convert the data.
In addition, they need to validate the data against often complex pricing or promotion agreements that may involve multiple parties in a selling process, some of which the company may not even transact with directly.
Post-validation, companies need to create payments to partners or customers on a timely basis, as well as track the data in a way that can be useful for production planning, customer inventory analysis, sales compensation and revenue recognition.
Oracle Trade Management handles all payment requirements both directly or indirectly, based on Point of Sale data. Volume offers can apply on both direct and indirect sales or a combination of both.
Additionally, volume offer functions such as tracking total order volume, calculating the current discount rate, and making retroactive adjustments apply to both direct and indirect sales data. For supplier ship and debit, you submit a request to the supplier for approval on discounted prices at which you want to sell products to your customers.
After you make the sale, you submit a batch for supplier approval before you can debit the supplier for the difference in your acquisition and selling prices.
You define a trade profile for your supplier to capture supplier preferences and attributes for the approval and claim settlement processes. For example, if your supplier does not require you to submit a batch and seek approval for the claimed amount, you can select the auto debit function on the supplier trade profile.
Auto debit enables you to directly go to claims processing after you create a batch. On the supplier trade profile, you can define the frequency of batch creation, the quantity and amount limits on an offer, and claim computation and approval communication methods.
After the supplier approves price changes on a supplier ship and debit request, an accrual offer is created on the request. Similarly, accrual offers are created on internal ship and debit requests. Except for the distributor being the qualifier or beneficiary on such an offer, offer approval and creation follows the existing trade management functionality. An accrual offer is created on a request and sales orders booked for this offer.
Goods are then shipped to the retailer or end customer against these sales orders. After the sale is made, the claim can be created and settled. Distributors create requests for supplier approval of the new prices and upon approval, create batches for supplier approval of claim amounts.
A batch contains all the accrual lines for which the supplier is expected to make payment. A supplier debit claim is created for accrual lines in a batch that the supplier approves.
For rejected accrual lines, an internal ship and debit claim is created. The supplier claim is closed out on posting of a debit memo in Oracle Payables for the supplier for the total of all approved lines. Internal ship and debit requests have no supplier debits; accruals are settled by relieving liability and booking the expense to the appropriate distributor GL account.
Price protection enables distributors and retailers to streamline updates and processes when a vendor changes the price of a product. These updates are required to calculate the difference in inbound and outbound inventory costs that distributors and retailers can claim.
Because Oracle Trade Management integrates with other E-Business Suite applications such as Inventory and Order Management, price lists, purchasing systems, costing and financial systems need to reflect the new price. To ensure price protection integration with these applications and enable updates to these systems, you must enable the system profile options for price protection.
To enable accounting on price protection claims, you must set default accounts in the System Parameters page. These accounts are used for cost adjustment, accrual, and contra-liability.
If distributors and retailers are covered for losses on inventory by a price protection agreement, the retailer submits a credit claim to the distributor and the distributor submits a debit claim to the vendor. To capture preferences and attributes for the processing and settlement of price protection claims, you define trade profiles for the customer in the case of a credit claim and for the supplier in the case of a debit claim.
The price protection dashboard enables you to manage the creation and approval of transactions for updates to price lists and purchase orders. These transactions provide inventory details, price changes, and adjustments. You can create customer and supplier claims for active approved transactions and track approval and settlement of these claims from the price protection dashboard.
The following information describes some Common Component related features in Oracle Trade Management. Global Flag on Pricing Related Objects. This profile option defaults whether a global flag will be checked when the offer is passed to Advanced Pricing. Fully accrued budget in Oracle Trade Management also uses the above profile to determine whether the accrual parameters will apply on all sales orders or only those that belong to the same operating unit that created the budget.
Price protection transaction covered inventory details price protection transaction customer claims. Oracle Trade Management includes enhanced support for different organizational environments. An operating unit is a business entity with its own set of business rules. Oracle Trade Management customers generally set up entities for one or more of the following reasons:. 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. Support for different business or data model organization structures on an operating unit org-striped basis or a shared service basis.
Claim users with access to multiple operating units can view all claims across multiple operating units without switching responsibilities. 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. The sales rep logs onto this system and can view how many invoices have been received from the customer, they have a few selection parameters to view this list of invoices by e. Customer hierarchy, period, Document type, status, account manager, etc. For each of the invoices entered in the system the sales rep needs to add the proof a document - Nielson data that the promotion was carried out as agreed as approval to pay the amount and specify the rebate number to pay out the money from in R3.
We believe this is a statutory requirement, that they have to be able to show to the auditors the link between the invoice, the proof and the rebate number and this system allows this. The invoice may be for one rebate or multiple rebates. The clerk then reviews the list and for those which have the proof attached and rebate specified, they manually create a partial payment from the rebate in R3 to the customer. The documentation there explains the key types of Claims. Given your scenario, Invoice claims are what you are looking for.
Thanks in advance for your help. The process is a follows: Former Member February 26, at