Friday, 20 July 2012

mapping-om-addresses-to-shipping-locations,bulk collect

Oracle Shipping Execution allows users to flexibly manage the shipment of products in a complex network of origins and destinations. Each origin or destination is modeled as a location in Oracle Applications. Because of the complex nature of shipping networks, and their relationship to other complex models such as organization structures of companies, the modeling of locations is complex. This paper explains how locations are set up and used in Oracle Shipping Execution.
Many types of locations are used in the shipping process. These include customer ship to addresses, warehouses, freight forwarders, consolidation points, distribution centers, etc. This paper will discuss setting up the most commonly used type of location – customer ship to addresses.
Customer ship to addresses are created in the customer standard form. Enter a new customer or select an existing customer. When you create a new address and assign a business purpose usage of “Ship To.” You may give the location a name if your system is set up so that locations are named manually. Otherwise, the system assigns a number to the location, and it is displayed on the form as soon as you save the business purpose usage record. This is the location name that is displayed in the sales order form when you select the ship to address for the customer’s order. It is associated with the business purpose.
Oracle Shipping Execution uses the location associated with the address record, instead of the location associated with the business purpose. This design is used because a single address may have many business purposes, possibly even across multiple customer records, but they should all be considered the same location in Shipping Execution. This location record is automatically created when you save the address in the customer standard form. The field is named Site Number, and it’s in the upper right hand corner of the screen. This location record will automatically be associated with any deliveries that are shipped to this address. The location record can be seen in the shipping transactions Mapping OM Addresses to Shipping Locations Page 2 form by going to the deliveries tab and opening the list of values for any of the address fields. The location name will be in the format “Site Number: Address 1 – City – State.” The list of values also shows the additional address lines, the country, and the postal code.
From the OM Super User menu, navigate to Customers -> Standard. Either find an existing customer or add a new customer. Go to the Addresses tab and enter the new customer ship to address. Save the record. Record the Site Number. This is the Site Number that is used in Shipping Execution. In this example, assume that the address you enter is 123 Main Street, Chicago, IL and the system generated Site Number is 55555.
Assign the Business Purpose Usage of “Ship to,” and (depending on your system setup) either enter a Location or record the system generated location. This is the Location that is used in the Sales Order form. Assume that you enter a Location of “Receiving.” The first time you enter an order for this ship to address, the shipping location is automatically created. You can find this location in any address field in the Shipping Transactions (Ship To, Deliver To, etc.) form by searching for the Site Number or part of the first line of the address. So, the location is displayed as 55555: 123 Main Street – Chicago – IL. You could find this location by entering 55555% or by entering %123 Main Street%.
This format for the Location is used consistently in Oracle Shipping Execution beginning in release 11.5.9.


Oracle Bulk Collect

One method of fetching data is an Oracle bulk collect. With Oracle bulk collect, the PL/SQL engine tells the SQL engine to collect many rows at once and place them in a collection. During an Oracle bulk collect, the SQL engine retrieves all the rows and loads them into the collection and switches back to the PL/SQL engine. When rows are retrieved using Oracle bulk collect, they are retrieved with only 2 context switches. The larger the number of rows you would like to collect with Oracle bulk collect, the more performance improvement you will see using an Oracle bulk collect.
Starting in Oracle10g, an Oracle bulk collect may be performed by the the PL/SQL engine for you. The PL/SQL engine may automatically use Oracle bulk collect to collect 100 rows at a time because of a cursor loop. This use of Oracle bulk collect allows your code to process rows without having to setup and execute the Oracle bulk collect operation. The result of this use of Oracle bulk collect is that bulk collecting 75 rows may not provide you with much of a benefit, but using Oracle bulk collect to collect large numbers of rows (many hundreds) will provid increased performance.
dfOracle Bulk collect is easy to use. First, define the collection or collections that will be collected using the Oracle bulk collect. Next, define the cursor to retrieve the data in the Oracle bulk collect. Finally, bulk collect the data into the collections.
A simple Oracle bulk collect exam
ple is shown below:

No comments:

Post a Comment