This chapter covers the following topics:
This chapter provides information on creating supplier ship and debit users to set up profile options and supplier trade profiles, run concurrent programs, create ship and debit special price requests, and approve these requests. The way you set up a supplier trade profile determines how accruals are calculated, the type of communication used to obtain supplier approval on price requests and claim amounts, the frequency of claim generation, and supplier payment methods. Although you can create an individual special price request for one or more sale items, as the ship and debit administrator, you can also create multiple requests.
Descriptive flexfields (DFFs) allow you to extend Oracle applications to meet business requirements without the need for programming. You can use descriptive flexfields in the Oracle Channel Revenue Management UI to gather information, important and unique to your business that would not otherwise be captured.
You can customize a descriptive flexfield to capture just the information your organization needs. The flexfield structure can depend on the value of a context field and display only those fields (segments) that apply to the particular type of context. For example, if the asset category were "desk, wood", your descriptive flexfield could prompt for style, size and wood type. If the asset category were "computer, hardware", your flexfield could prompt for CPU chip and memory size. You can even add to the descriptive flexfield later as you acquire new categories of assets.
Oracle Supplier Ship and Debit uses the following flexfields.
Ship and debit request header and request line
Ship and debit batch header and batch line
If you created increase earned and decrease earned budget adjustment types in Oracle Channel Rebate and Point of Sales to decrement and increment supplier ship and debit accruals, you can select them as default budget adjustment types in the Supplier Ship and Debit section of the System Parameters page.
The Decrease Earned budget adjustment type is used to decrement accruals. For example, the distributor claims $100 but the supplier approves only $80, then the distributor can choose to adjust $ 20.
The Increase Earned budget adjustment type is used to increment accruals. For example, the distributor claims $100 and the supplier approves $120, distributor can choose to adjust the line adding $ 20 to the earnings.
In addition, you must select the appropriate budget adjustment type in both the System Parameters page and the Batch Details page to apply budget adjustments to the batch line for a Work in Progress Supplier Ship and Debit batch. For more information, see the Oracle Supplier Ship and Debit User Guide.
The Process Claim Amount for Partially Approved Lines parameter has three values: Yes, No, and blank. If you select the value as Yes, the parameter lets you claim the approved amount and split the rejected lines for further negotiations. If you select the value as No, the lines are not split, the partially approved amount is not processed, and the line is Rejected. If you select blank, the value behaves as No. The value set for this parameter on the Supplier Trade Profile page takes precedence over the value set on the System Parameters page.
For Supplier Ship and Debit, you must set up a supplier trade profile. This profile specifies supplier preferences for payment methods, approval, communication methods, claim frequency, computation, and acceptable threshold levels. Because claims are processed using AR Deductions and Settlement which recognizes only customer claims, you must map the supplier to a customer name and account in the supplier trade profile.
In summary, you use supplier trade profiles to:
Link suppliers to customer accounts.
Define parameters for accrual reimbursements including payment frequency, offer limits, and approval considerations.
Define preferences for approval communication methods.
Define thresholds for claim amounts including batch and line tolerances.
Define code mapping for automatic item code conversion of distributor item to supplier item for inbound and outbound transactions.
To set up trade profiles, log in to Oracle Channel Revenue Management. Navigation: Channel Revenue Management: Administration > Trade Management > Supplier Trade Profile > Create
To create a trade profile for your supplier, perform the following basic steps.
Select the operating unit for the supplier trade profile.
To settle claims, you must set up this supplier as a customer in TCA. In addition, perform the following steps to map supplier and customer information on the supplier trade profile.
Select the name of the supplier.
Select a supplier site. Supplier sites are not organization-specific and can be used across operating units.
Select the customer account that you want to map to the supplier site.
Select the bill-to site of the customer that you want to map to the supplier site.
The following supplier ship and debit options of a supplier trade profile influence the batch or claim process for the given supplier.
Enable Quantity Increase if the supplier does not wish to limit the offer quantity to that on the supplier request. If you enable this, enter the acceptable percentage increase.
Enter the number of days for which this request is open.
Enter the number of grace days after the request end date that the offer can stay open.
Select the supplier's preferred communication method for request approvals, if manual or through the XML Gateway
Select the supplier's preferred communication method for batch approvals, if through the XML Gateway or using Web ADI.
Select the unit of frequency and enter the frequency at which the batch or claim is generated.
Select the formula that ship and debit must use to calculate the cost of the item.
Select the supplier's preferred currency for receiving claims from the distributor.
Enter the minimum amount for a claim and the minimum amount for a line that is included in a claim. If you do not specify a line threshold amount for a supplier, then all lines are eligible for claim.
Enable AutoDebit if claim processing can begin without supplier approval on a batch. If you enable this, then the batch is automatically closed after it is created.
Enter the number of waiting days after the distributor submits the batch to the supplier for approval. If there is no response within this time, the Supplier Ship and Debit Batch Auto Claim concurrent program assumes that all lines on the batch are approved, initiates claim processing, and closes the batch.
Run the Supplier Ship and Debit Batch Auto Claim concurrent program to initiate claim processing and close the batch. For more information, see the Concurrent Programs chapter.
You can create an individual supplier request from the supplier ship and debit dashboard. Alternatively, you can import from a spreadsheet for example, all the information required to create a batch of supplier ship and debit requests. To do this, use the OZF_SDR_PUBLIC_API public API. Using the API enables you to integrate with external systems to bring in request data for bulk creation, update, and copy of requests.
For more information on this public API, use the Integrated SOA Gateway responsibility to access the Integration Repository application. In the Integration Repository, navigate to the Oracle Channel Revenue Management product from the Marketing and Sales Suite product family.
For information on creating requests from the supplier ship and debit dashboard, see Creating a Supplier Ship and Debit Request, Oracle Supplier Ship and Debit User Guide.
Access to requests is controlled based on user permissions and roles. You can assign Oracle Trade Management User permission to distributors. Distributors with this permission can create, view, update, and approve all supplier ship and debit requests and batches. In addition, distributors can view and track offers and claims.
The types of users for Supplier Ship and Debit and their responsibilities are listed below.
Sales User - Distributor users with the Oracle Trade Management User permission who can create and update supplier ship and debit requests.
Request Approver - Distributor users who are defined in Oracle Approvals Management, or on the OZF_SD_DEFAULT_APPROVER profile option, or on supplier ship and debit requests as assignee. These users can send request and batch details to suppliers for approval and receive supplier responses. In addition, they can create internal requests and create accounting for such requests after the sale.
Administrator User - Distributor users who can set up supplier trade profiles, supplier ship and debit profile options, and other users. They can also change the status of a request, implement WebADI and XML Gateway for supplier ship and debit, use the public API to create multiple requests, and run the supplier ship and debit concurrent programs.