This chapter provides the information you need to set up the Oracle Supplier Ship and Debit product of the Oracle Channel Revenue Management suite. Before you can set up Oracle Supplier Ship and Debit, you must perform basic Oracle Channel Revenue Management setups such as setting up calendars and rates, creating users and user profiles, setting up customer profiles and accounts, and defining the default accounting structure in the System Parameters page. For more information, see the Oracle Channel Revenue Management Implementation and Administration Guide. For information on the Supplier Ship and Debit process, see the Oracle Supplier Ship and Debit User Guide.
In addition, Supplier Ship and Debit integrates with other products in the Channel Revenue Management family, as well as those in Financials, Supply Chain, Procurement, and Applications Technology Group.
Based on your requirements, you can then set up the necessary profile options for Oracle Supplier Ship and Debit, and implement the required communication channels between distributors and suppliers.
Supplier Ship and Debit enables distributors to sell goods at lower prices to customers to move onhand inventory or gain advantage over competitors. To sell these goods at the new prices and debit the supplier for the difference in acquisition and resale prices, distributors using Oracle Supplier Ship and Debit integrate with several E-Business Suite applications.
Oracle Supplier Ship and Debit integrates with this product to create, validate, and settle claims on approved ship and debit batch lines. After a sale is completed at the new, lower price, the distributor can submit a claim to collect payment. When submitting a claim, the claim must be for the same organization as the one for which the request was approved. With the claim, you can submit sales data as a proof of performance.
Oracle Supplier Ship and Debit integrates with this product and transfers the supplier approved discounted price offers as modifiers that must be manually or automatically applied to sales orders of ship and debit customers. These modifiers can have built in conditions for when they can be applied such as promotions on specific products or product lines, discounts on customer types, additional charges on international shipments, etc. In addition to creating modifiers in Advanced Pricing, you can create qualifiers to reference specific attributes of a sales order, product, customer, etc. and help determine if the modifier qualifies for the sales transaction.
Oracle Supplier Ship and Debit integrates with this product to create approval rules. These rules determine who can approve supplier ship and debit requests.
Oracle Supplier Ship and Debit integrates with this product to:
Create a default budget for supplier ship and debit requests. If a default budget exists, the system generates a budget request for the requested amount when you submit a request. You can configure the Budget tab for display. If you choose to have this tab displayed, internal approvers for supplier requests can change the budget sourcing options. If approvers do not change the sourcing option, the system automatically adjusts the budget amount based on the approved amount.
Generate accrual offers on approved ship and debit requests with defined qualifiers and market eligibility, activate and execute the offer, and calculate accrual.
Before you can implement Oracle Supplier Ship and Debit, you must implement supplier trade profiles and system parameters in Oracle Channel Revenue Management. Supplier trade profiles define supplier preferences for payments and methods for exchanging information between suppliers and distributors. System parameters help set up the default accounting structures.
Oracle Supplier Ship and Debit integrates with this product to create accounting entries for the new discounted prices rejected by suppliers. Accounting is necessary if distributors nevertheless decide to go ahead with the new prices and absorb the loss themselves.
Oracle Supplier Ship and Debit integrates with this product for product and product category definitions on ship and debit requests and batches.
Oracle Supplier Ship and Debit integrates with this product to create sales orders for customers based on the new lower prices on approved supplier ship and debit requests. Order information such as product number, units, quantity, value and discount, as well as the offer details come from the ship and debit requests.
Oracle Supplier Ship and Debit integrates with this product to pay claimed amounts to distributors on approved ship and debit batch lines by raising debit memos against the supplier.
Oracle Supplier Ship and Debit integrates with this product to communicate with the supplier when seeking approval of claim amounts on ship and debit batches.
Oracle Supplier Ship and Debit integrates with this product to communicate with the supplier when seeking approval of supplier ship and debit price requests and batch lines for claim amounts.
This section describes profile options for the Supplier Ship and Debit category, OZF_SD_SETUP. These profile options affect the processing of supplier ship and debit requests from approval through to generation of claims.
You must set a value for a required profile option. Optional profile options provide default values, so you need to provide a value only if you want to change the default value. Your System Administrator needs to set up Supplier Ship and Debit profile options in the System Profile Values Window. See: Setting User Profile Options, Oracle Applications System Administrator's Guide.
| Profile Name | Required | Level | Setting | Default | Effect/Limitation |
|---|---|---|---|---|---|
| OZF: Default Ship & Debit Request Approver | No | Site Appl Resp User |
List of active, internal employees | Valid employee name | If no approver is set up in Oracle Approval Management, this profile option determines the default approver for supplier ship and debit requests. |
| OZF: Request Based Ship and Debit | No | Site Appl Resp User |
Yes/No | No | This profile option determines if the offer on a supplier ship and debit request is automatically applied to the sales order or is manually applied by the Order Management user. Setting the profile to Yes selects the Request Only check box on the Ship and Debit Create/Update page. You can change this setting. |
| OZF: Ship and Debit Budget | Yes | Site Appl Resp User |
List of active fixed budgets | Valid Trade Management budget | This profile option determines the budget that supplier ship and debit uses for the offer. |
| OZF: Supplier Ship & Debit Claims group lines by SDR & Product | No | Site Appl Resp User | Yes/No | Yes | This profile option determines if a claim is to be created for each approved batch line or for approved batch lines grouped by supplier ship and debit request and product. |
Related Topics
Personal Profile Values Window, Oracle Applications User's Guide
Overview of Setting User Profiles, Oracle Applications System Administrator's Guide
Common User Profile Option, Oracle Applications User's Guide
Based on supplier preferences on the communication method to be used, you can set up the XML Gateway for Supplier Ship and Debit and use it to communicate with the supplier for approval of supplier ship and debit requests and batches. Oracle XML Gateway is a set of services that allows easy integration with the Oracle E-Business Suite to support XML messaging. The XML Gateway Execution Engine interfaces with the Oracle E-Business Suite via business events and event subscriptions to retrieve data from or populate data into the Oracle e-Business Suite tables. For more information, see the Oracle XML Gateway User's Guide.
Alternatively, if your supplier prefers that you use use the Oracle Web Applications Desktop Integrator or Web ADI to communicate, you must set up the Web ADI for Supplier Ship and Debit. Web ADI enables you to use the spreadsheet format of Microsoft Excel on your desktop to export and import Ship and Debit data to your supplier. WebADI has an integrator that can create, update and download ship and debit data from the Oracle database tables to an interface table or viewer such as Microsoft Excel on your desktop. You can extract the data into an MS Excel spreadsheet and upload into the database from the spreadsheet using the upload menu option.
You can customize the fields that appear in the spreadsheet, their positions, and their default values using Web ADI's Layout functionality. All data in the spreadsheet can be validated against Oracle E-Business Suite business rules before it is uploaded into the Oracle database. For more information see the Oracle Web Applications Desktop Integrator Implementation and Administration Guide.
Based on the communication preferences you defined on the supplier trade profile, you can use the Oracle Web Applications Desktop Integrator or Web ADI to communicate with your supplier for approval on the batch that you created.
To send batch information to the supplier for approval by the method you specified on the supplier trade profile, click Batch Export on the Batch Details page. Before you can send batch information to the supplier, you must define a layout for your spreadsheet, map spreadsheet columns to interface columns, and create data in the spreadsheet document. Perform the following set of steps to create spreadsheet content for supplier approval.
Perform the following steps to specify the position of the fields for the layout of your spreadsheet.
Login into Oracle Applications using the Web ADI responsibility.
Select Define Layout.
Select the Ship and Debit Batch Integrator.
Enter Batch Details as the layout name and the number of headers as two.
Select the columns and specify the placement of the fields, if header or line. You can also assign default values using SQL or environment variables
Save your work.
Next, use the following steps to map interface columns with spreadsheet columns.
Using the Web ADI responsibility, select Define Mapping.
Select the Ship and Debit Batch Integrator.
Click on Define Mapping.
In the Mapping window, select OZF_SD_BFEED_MAP as the map name and the mapping key, and 193 as the number of source spreadsheet columns that you are mapping to target interface columns.
Save your work.
Use these last steps to create the MS Excel worksheet that you must send to the supplier for approval.
Using the Oracle Trade Management User responsibility, navigate to the Batch Details page from the supplier ship and debit dashboard and click Export Batch.
Select Excel as the viewer and reporting as No. Selecting No for reporting ensures that the Oracle > Upload menu is available in the downloaded worksheet to enable you to upload data during the inbound transaction.
Select the required layout if there is more than one layout defined for the integrator.
Select Download as the content.
Enter OZF_SD_BFEED_MAP as the mapping file name and give value to the parameter.
On the Document Creation Review page, click Create Document to populate the worksheet with data.
Save the worksheet.
After you receive the supplier's response, open the MS Excel worksheet sent by the supplier and click Oracle > Upload in the Web ADI Excel viewer. The internal APIs validate the data before the data is uploaded. If any errors occur during data validation, no data is uploaded to the database. You must correct the errors and upload the corrected data.
If the supplier rejected lines on the batch, all rejected lines are removed from the current batch during the upload. A new batch is created for the rejected lines and standard industry rejection reasons or dispute codes provided for each rejected line. You can view the rejection reasons, make changes to the claim amounts and resubmit this new batch for supplier approval.
Based on the communication preferences you defined on the supplier trade profile, you can use the XML Gateway to communicate with the supplier on requests and batches. Supplier Ship and Debit uses the standard Rosettanet format for its communication transactions. Changing the status of a supplier request to Pending for Supplier Approval raises the XML gateway business event. This business event populates the XML document with valid data from the e-Business tables. You can click Export Batch on the Batch Details page to transmit this data.
To implement and use the XML Gateway, you must define the transaction subtypes for each predefined supplier ship and debit transaction. To do this, perform the following steps.
Use the XML Gateway responsibility to log into Oracle Applications.
Navigate to Define Transactions.
Select Supplier as the party type.
Enter OZF as the transaction type.
Select from the following transaction subtypes
SDRO for outbound supplier request for vendor approval
SDRI for inbound request for vendor approval
SDBO for outbound batch for vendor approval
SDBI for inbound batch for vendor approval.
For each transactions subtype, select OZFSD as the external transaction type.
Based on the transaction subtype that you selected, select from the following appropriate external transaction subtype
REQI for external transactions subtype of SDRI
REQO for external transactions subtype of SDRO
BATO for external transactions subtype of SDBI
BATI for external transactions subtype of SDBO
Save your work and close the window.
After you define transactions, you must map XML file and database columns for each transaction subtype. For this mapping, use the XML message designer. See the XML Gateway Implementation Guide. After you have defined maps, you must set up your trading partner or supplier in XML Gateway. To do this, use the following steps.
Log into Oracle Applications with the XML Gateway responsibility.
Navigate to Trading Partner Setup.
Select the operating unit of the supplier ship and debit transactions.
Select Supplier as the trading partner type.
Search and select the name of the supplier or trading partner.
Search and select the trading partner site.
Enter the company e-mail address of the administrator who receives confirmation on message transmissions.
To enter trading partner select from the following supplier ship and debit transaction subtypes for the OZF transaction type.
SDRI - for inbound request transactions
SDRO - for outbound request transactions
SDBI - for inbound batch transactions
SDBO - for outbound batch transactions
Based on the transaction subtype you selected, select from the following maps available for supplier ship and debit.
OZF_SD_BATCH_IN - Select this if you selected the SDBI transaction subtype.
OZF_SD_BATCH_OUT - Select this if you selected the SDBO transaction subtype.
OZF_SD_REQ_IN - Select this if you selected the SDRI transaction subtype.
OZF_SD_REQ_OUT - Select this if you selected the SDRO transaction subtype.
For inbound transactions, enter the party site ID or the location code of the trading partner that is the source of the transaction. If you select an HTTP or SMTP hub, select hub username and enter destination trading partner location code.
For outbound transactions, enter the party site ID or the location code of the trading partner that is the destination for the transaction. If the transaction is routed through a hub, select the hub, the protocol type for the hub, and the hub user. If you are transmitting directly, select Direct as the hub. If you select a connection type of SMTP for this hub, enter the e-mail address of the person receiving the transmitted message as the protocol address.
Note: To find the value for the party site ID, click in the Trading Partner Site field and navigate to the Examine Field and Variable Values window. To navigate to this window, click Help > Diagnostics > Examine in the menu. Find and select the PARTY_SITE_ID field to retrieve its value.
Select the type of confirmation that the trading partner wants to receive for all inbound or outbound messages of the selected transaction subtype.
0: Never send a confirmation
1: Send notification about transmission error, if any
2: Always send a confirmation
Click User Setup to set up users by their user name for the specified supplier site and hub. Save your work and close the Trading Partner User Setup window.
Click Code Conversion to set up the DUNS number for the specified supplier site. Dun & Bradstreet (D&B) provides a unique nine-digit identification DUNS number, for each physical location of your business. You enter this DUNS number as the unique number for the supplier in Oracle Trade Management. Enter the Oracle value of OZFSDDUNS as the runtime value for the field, for the DUNS category. The runtime value determines the set of mapped values that are used in the communication transaction.
Save your work and close the Trading Partner Setup window.
For additional information, please refer to the Oracle XML Gateway User's Guide. To set up XML Gateway messages, set the ICX profile option and the profile options for Application Framework and Apps Servlet Agents, see Profile Options for Indirect Sales, Oracle Channel Rebate and Point-of-Sale Management Implementation Guide.