October 13, 2012

Workday Calendar

A workday calendar consists of a start date, and end date, and on and off days that follow one or more defined workday patterns. A workday calendar can also include shift information and exception dates, such as holidays or scheduled down time.

Use a workday calendar for forecasting and planning material requirements, use shift information for job scheduling, and capacity analysis.

Workday exceptions identify deviations to the workday calendar. Shift exceptions identify deviations for a shift.

Attention: Shift exceptions take precedence over workday exceptions. (This is only relevant if a workday exception and a shift exception overlap.)

To assign workday exceptions to a workday calendar or calendar shift, either select them intuitively from the Calendar Dates (or Shift Calendar Dates) window, or apply them from an existing template, calendar, or shift.

To create a workday calendar:

1. Navigate to the Workday Calendar window.

2. Enter a name for the workday calendar.

3. Select a quarterly calendar type:

4/4/5 Week Pattern: Two four-week periods followed by one five-week period.

5/4/4 Week Pattern: One five-week period followed by two four-week periods.

Calendar Months: Twelve periods per year based on calendar months.

13 Periods: Thirteen four-week periods per year.

Note: If you use Oracle Master Scheduling/MRP, choose the 4/4/5 Weekly Pattern or the 5/4/4 Weekly Pattern to report MRP information in weeks and months. Otherwise, if you choose the 13 Periods calendar or Calendar Months, you can only report MRP information in monthly buckets.

4. Enter a date range for the workday calendar. The default end date is four years from the start date.

Note: Days on and off are calculated based on the start date and the day of the week. For example, if you want a standard five day workweek to start on 01-JAN, you must enter the start date as the Monday before 01-JAN (unless 01-JAN falls on a Monday).

5. Continue creating the workday calendar by choosing one of the following buttons:

Workday Pattern: Set workdays on or off.

Shifts: Assign shifts to the workday calendar.

Dates: Review your work so far and its effect on the workday calendar. Do this before you build or rebuild the workday calendar you are now creating. (You can only do this after you have defined a workday pattern.)

Once you have created a workday pattern, assigned shifts, assigned workday and shift exceptions, and reviewed your work, you must build the calendar and assign it to an organization.

6. Save your work.

Once you have created the calendar, to make it active for using in other places, you need to build the calendar.

Defining Locations

In Oracle HRMS, you set up each physical site where your employees work as a separate location. Similarly, you enter the addresses of external organizations that you want to maintain in your system, such as employment agencies, tax authorities, and insurance or benefits carriers. When setting up internal or external organizations, you pick from a list of these locations.

Locations are shared across Business Groups in Oracle HRMS and with two other Oracle applications: Inventory and Purchasing. Oracle HRMS does not use some of the fields in the Location window. These fields are disabled for HRMS users.

To enter a work location and its address:

1. Enter the name of the location, and a description if required.

2. Select a national address style from the list.

A window opens with the address format for the country you select.

3. Enter address information in this window and choose the OK button.

Additional Information: Default address styles are predefined for many countries. You can add address styles for other countries, if required.

Locations once created, canot be deleted. But in need, it can be done Inactive mentioning the inactive date.

Header

Uncheck the Global check box if you want the location to only be available within the default Business Group of your current responsibility. Accept the default if you want the location to be a global location and therefore available to all Business Groups. If you are setting up a global location, the location name must be unique across all Business Groups. If you are setting up a location for one Business Group, the location name must be unique within that Business Group and all global locations, but does not have to be unique across all Business Groups.

Note: You cannot amend the Global check box once you have set up your location.

Address Details Tab

Select a national address style from the list. If a local address style exists for your country, it is displayed as the default. Otherwise, the international style is displayed.

Shipping Details

Selecting the check boxes means that you are making the location Name a valid location in the list of values on a Purchasing document. For example, selecting Ship–To Site makes the location name a valid choice in the list of values for the Ship–To field on a purchase order header. Note that if you define a default Ship–To or Bill–To Location in the Supplier–Purchasing region of the Financials Options window for your organization, which is the location that defaults onto your purchase orders. But if you wanted to change that default, the location name that you define here and enable as a Ship–To or Bill–To site is available in the list of values for you to choose from in the Ship–To or Bill–To fields.

Contact: Optional contact name for the location Name.

Ship–To Location: It’s the receiving dock. Usually the same as the location name. You could select a separate, previously defined Ship–To Location—for example, if you wanted to create a location Name, Office A, and specify Receiving Dock A as its Ship–To Location. Note, however, that once you specify a separate Ship–To Location, you can no longer enable the location Name as a Ship–To Site.

In this example, Receiving Dock A is the ship–to site for Office A; therefore, Office A itself cannot also be the ship–to site.

Ship–To Site: Is this location is a receiving dock. Select this option to make the location Name a valid ship–to organization on a purchase order or requisition.

Bill–To Site: Select this option to make the location Name a valid bill–to site. The Bill–To Site, which is used by Payables, is specified on a purchase order header.

Receiving Site: Select this option to make the location a valid receiving Location when creating a receipt or receiving transaction.

Office Site: Select this option to indicate that this location Name is an office site, such as a field office.

Internal Site: Select this option to make the location a valid internal ship–to location when creating an internal requisition.

Other Details

Inventory Organization: Select an inventory organization within which this location will be available in the list of values on a Purchasing document. By selecting no inventory organization, this location becomes available on purchasing documents in all organizations.

EDI Location: If you use Electronic Data Interchange (EDI) to receive Advance Shipment Notices (ASNs) or ASNs with billing information (ASBNs), enter a defined location. This location should match the ship-to location specified on an ASN or ASBN.

Enterprise Structure

You must plan how Oracle Inventory represents your company’s inventory sites and business units. This includes defining organizations, locations, subinventories, and locators depending on your company structure. You also must plan how to implement certain parameters and what level of the structure controls them.

Multi-org often refers to an Oracle Applications setup used to enable multiple business units in a single install. With multi-org, a business enterprise may set up multiple business units with differing sets of books, operating units, and legal entities all within a single instance. With multi-org, goods may be sold out of one operating unit or legal entity and shipped to another, and the system will process an intercompany sale to properly account for it.

Multi-org, however, should not be mistaken for installs with multiple inventory organizations. You do not have to use Oracle Applications multi-org to support multiple inventory organizations if all the inventory organizations share the same set of books, operating unit, and legal entity.

Location: A location is simply a name and address, and is assigned to an organization or used to indicate delivery information on a purchase order. You may define as many locations as you like, but only one location may be assigned to an inventory organization.

Business group is a group of companies that does business in different markets under common administrative or financial control whose members are linked by relations of interpersonal trust on the bases of similar personal ethnic or commercial background a business group.

Set of Books (SOB): The financial entity that represents the chart of accounts, fiscal calendar, and base currency. The SOB is set up in the General Ledger.

Legal Entity Organization: An entity used to represent a legal company. Fiscal and tax reporting are done at the Legal Entity level.
A legal employer is a legal entity that is responsible for employing people in a particular country. Therefore, if you employ people in a country, then you must have at least one organization classified as a legal entity and a legal employer.
The Configuration Workbench classifies an organization as a GRE/Legal Entity where your enterprise operates in a country, and classifies it as an Employer if you employ people in that country also. For example, you can have a legal entity in a country where you do business, but do not employ people in that country.

Operating Unit Organization: A business unit that shares a common Purchasing, Accounts Payable, Order Entry and Accounts Receivable setup. An operating unit may consist of multiple inventory organizations, with multiple manufacturing sites, distribution centers, and sales offices, but they share a common sales order and purchase order system. For example, a sales order may have lines shipping from different inventory organizations or a purchase order may have lines destined for different inventory organizations.

Inventory Organization: An entity used to represent a manufacturing or distribution site. Inventory organizations are where a user tracks on-hand balances, manufactures goods, and transacts the daily ins and outs of material movement. An inventory organization is the lowest level entity for costing goods, planning material requirements, and securing system access. Only a single address may be assigned to an Inventory Organization. An inventory organization is assigned a Set of Books which determines the chart of accounts, fiscal calendar, and base currency for all financial and value added activities that occur within the organization.

Inventory Organizations are also assigned to a Legal Entity Organization and an Operating Unit Organization.
A variation on the inventory organization is the master item organization. Generally, with Oracle Applications a single inventory organization is created and designated at the master organization. Items are defined first in the master organization, and then enabled in other inventory organizations as necessary. Some of the item attributes are set as controlled at the master organization and therefore the attribute values cannot be updated within individual inventory organizations. Category sets may also be designated as master organization level. Cross-references are also master level only or master level optional as well.

Subinventory: Physical or logical locations for storing inventory. Subinventories are generally defined to represent the main stores area as well as stocking points on the production floor. Additional subinventories may be used to specify supply closets or cabinets and the cage area for discrepant material. Subinventories are flagged as to availability for planning (nettable), reservations, and available to promise checks, thereby determining the availability of the material stored in the subinventory. Subinventories are assigned material asset account numbers. As goods move in and out of a subinventory a transaction posts to the asset account.

Stock Locator: A physical area within a stockroom. The stock locator is a key flexfield that is often defined as a multiple segment flexfield with the segments representing the physical layout of a stockroom. For example, a stockroom may be laid out in rows of shelves with bins on the shelves, each numbered so that a row/shelf/bin combination would direct someone to a particular material storage compartment. Such an implementation would define a locator flexfield as a 3 segment flexfield with segments for row, shelf, and bin.

Attachment of LE/OU/INV with BG
We never attach any LE/OU/INV with BG in front end...but its available in HR_ALL_ORGANIZATION_UNITS in column Business_Group_ID. So the question is from where it comes?
First we create a Business Group. Whenever we create a business group the system creates an organization with type businessgroup and attaches a business group ID 'N' which is same as the organization ID for that Business group.

After that we attach the business group to a responsibility through the profile option HR: Business Group.

Next we create whenever we create a new LE/OU/Inv with one responsibility the system will attach the Business Group which is attached with the HR: Business group for that particular responsibility.

Rules

· Available to Promise

· Forecast

· Picking

· Pick slip grouping

Available to Promise (ATP)

This rule helps us calculating the ATP details for an Order. Each rule is a combination of ATP computation options, time fence options, and supply and demand sources to use during an ATP inquiry. An ATP rule canot be deleted, but it can be renamed or redefined by updating the fields in an existing rule.

To define an available to promise rule:

1. Go to Inventory Superuser responsibility à Setup à Rule

2. Navigate to the ATP Rules window.

3. Enter a unique name for the rule.

4. Optionally, select a type of consumption. You can choose both.

1. Forward: Uses the available quantity from future periods to cover a period shortage.

2. Backward: Uses the available quantity from prior periods to cover a period shortage.

3. If you selected Backward consumption, indicate whether ATP information should be calculated by carrying available quantity from one period over to the next (Accumulation).

4. If you choose to accumulate available quantity, enter the number of days to define this window of time in the Accumulation Window field.

5. Enter the number of days to determine the past due demand and supply time fence dates. When calculating the ATP quantity of an item, Oracle Inventory does not consider any demand or supply source scheduled before these dates.

6. Select an Infinite Supply Option to determine the infinite supply time fence date.

7. When calculating the ATP quantity of an item, Oracle Inventory does not consider any supply source scheduled on or after this date. The infinite supply time fence date marks the end of the ATP horizon, after which Inventory assumes infinite supply is available to cover any scheduled demand.

Cumulative total lead time: Use the cumulative total lead time of the item.

Cumulative mfg lead time: Use the cumulative manufacturing lead time of the item.

Total lead time: Use the preprocessing, manufacturing, and postprocessing lead times of the item.

User-defined time fence: Use a lead time you specified when you defined the item

8. If you choose the User-defined time fence option, enter the number of lead time days in the Days field. This field is not available with other Infinite Supply options.

9. Indicate whether to calculate ATP based on defined demand classes. Demand classes allow you to segregate scheduled demand into user-defined groups.

10. If you choose to calculate ATP based on defined demand classes the following Supply Source options are not available: on-hand available, interorg transfers, purchase orders, internal and supplier requisitions.

11. Select Demand and Supply Sources to use in ATP calculations.

12. Save your work.

You can define multiple ATP rules to reflect the specific needs of your organization, and then use different rules to calculate availability for different items or groups of items. Each time you run an ATP check, the rule determines how existing supply and demand are matched.

You can choose one of the ATP rules you define as the default ATP rule for your organization. You can update the item attribute ATP Rule to specify a default ATP rule for each item.

Forecast

You can define forecast rules to use when loading forecasts. Defining forecast rules includes choosing forecast source options, entering statistical forecast parameters, and entering and adjusting initial seasonality indices.

To define a forecast rule:

1. Navigate to the Forecast Rules window.

2. Enter a unique name for the rule.

3. Indicate whether the bucket type is days, weeks, or periods.

4. Determine the transaction types to use as demand sources. The quantities associated with each source are used when calculating historical usage:

Sales Order Shipments: Includes sales order issue quantities.

Issues to WIP: Includes WIP issue quantities.

Miscellaneous Issues: Includes quantities issued with user-defined transaction sources, account numbers, and account aliases.

Inter-Org Transfers: Includes quantities issued to other organizations.

5. Indicate the forecast method to use:

Focus: Uses focus forecasting algorithms to forecast demand for the item. This procedure tests the selected items against a number of forecasting techniques and chooses the best one, based on history, as the technique to forecast future demand.

Statistical: Uses exponential smoothing, trend, and seasonality algorithms to forecast demand for the item.

If you choose statistical forecasting, continue with the following steps:

6. Enter the maximum number of past periods upon which to base the forecast

7. Enter the factor by which to smooth demand for each successive period in the forecast. This levels demand throughout the forecast, reducing dramatic upward or downward fluctuations.

You can enter values from 0 to 1. Values closer to 0 give more weight to past demand; values closer to 1 give more weight to current demand.

8. Indicate whether to base the forecast on a trend model.

Turning this option on performs smoothing on the upward or downward trend in demand.

9. Enter the factor by which to smooth the trend change in demand from period to period. This produces a more linear rise or fall in demand from period to period over the course of the forecast.

You can enter values from 0 to 1. Values closer to 1 give more weight to recent changes and trends. Values closer to 0 give more weight to historical trend.

10. Indicate whether to base the forecast on a seasonality model.

Turning this option on bases the forecast on a seasonal adjustment you define for the forecast rule.

11. Enter the factor by which to smooth the seasonality indices you define by period for this forecast rule. This produces a more even pattern of seasonal demand from period to period over the course of the forecast.

You can enter values from 0 to 1. Values closer to 0 give more weight to past seasonal indices; values closer to 1 give more weight to current seasonal indices.

12. Enter an index that describes the seasonal influence on the period. For example, 2 indicates that you expect the forecast to double in that period because of seasonal factors.

13. Save your work.

You can delete a forecast rule if there are no references to it.

Picking

When you define an item you choose a picking rule to determine the order in which revisions, lots, subinventories, and locators are picked for sales orders. Oracle Order Entry / Shipping submit requests to Oracle Inventory, which uses the information you enter in the Picking Rules window to generate pick lists for sales orders.

If you choose None for any of the criteria fields, Inventory ignores that criterion. For example, if you choose None for Revision, Inventory picks units of an item without regard to revision levels.

Oracle Inventory looks at the picking criteria in the order in which they appear in the Picking Rules window. Then, Inventory looks at the options (except for None options) for each criterion in the order in which they appear beneath each criterion.

To define a picking rule:

1. Navigate to the Picking Rules window.

2. Enter a unique name for the rule.

3. Select an option for revision order:

Revision: Pick most recent revision.

Effective Date: Pick earliest revision effective date.

None: Do not consider revision levels in the picking process.

4. Select an option for lot order:

Expiration Date: Pick earliest lot expiration date.

Receipt Date: Pick earliest lot receipt date, the date you received items into their current location.

Lot Number: Pick lowest lot number.

None: Do not consider lot numbers in the picking process.

5. Select an option for subinventory order:

Subinventory: Pick by order defined for each subinventory.

Receipt Date: Pick earliest subinventory receipt date.

None: Do not consider subinventories in the picking process.

6. Select an option for locator order:

Locator: Pick items according to the picking order defined for each locator.

Receipt Date: Pick items according to the earliest locator receipt date.

None: Do not consider locators in the picking process.

7. Save your work.

You can delete a picking rule if there are no references to it.

Learn Oracle