Your master scheduler combines all sources of demand, including the three forecasts and all sales orders, into a single statement of demand-the master demand schedule. Note that these forecasts are defined within a forecast set. You maintain and report on each forecast independently. In the above diagram, your master scheduler has created three forecast names: FC–WHOLESL, FC–RETAIL, and FC–MAILORDER. However, Oracle MRP considers all sources of forecasted and sales order demand together. You may wish to create a separate forecast name for each source and maintain each forecast independently. Each source has a different sales force you forecast independently. For example, suppose your company has three primary sources for sales orders: wholesale sales, retail sales, and mail order sales. You can use demand classes as a means of forecasting different sources of demand separately. You can segregate your subinventories and reserved inventory by demand class and selectively net them when launching the planning process. If you are planning a master production schedule that has an associated demand class, it only nets discrete jobs and repetitive schedules that have the same demand class. You can limit the netting of discrete jobs, repetitive schedules, flow schedules, reservations, and subinventories when planning a master production schedule. You can load a subset of the sales orders into your master schedule for a specific demand class. After consuming master schedules with the same demand class as the sales order or discrete job, Oracle MRP consumes master schedules with no demand class. When you ship a sales order or create a discrete job, that sales order or discrete job consumes the master schedules that are associated with the demand class of the sales order or discrete job. You can optionally associate a demand class to a master demand schedule or master production schedule when you define the master schedule name. If you place sales order demand that does not have an associated demand class, the forecast consumption process attempts to consume forecast entries associated with the organizational default demand class first, and then consume entries that have no demand class defined. If the forecast consumption process does not find a forecast, it consumes entries that have no demand class. When you place sales order demand, the forecast consumption process consumes the forecast with the same demand class. You can optionally associate a demand class to a forecast when you define the forecast name. Oracle MRP uses this demand class during forecast consumption, and shipment and production relief. You can assign a default demand class to your organization. Oracle Order Management automatically assigns a demand class to a sales order line using either the demand class associated to the customer ship to address or the order type. You can associate a demand class to a customer ship to address in Oracle Receivables and to an order type in Oracle Order Management. Associate Demand Classes to Customer Demand You can optionally define demand classes to group similar customers or sales orders. Demand classes may also represent different sources of demand, such as retail, mail order, and wholesale. A demand class may represent a particular grouping of customers, such as governmental and commercial customers, or it may represent sales channels or regions. 11/28 Demand Classes Overview of Demand Classesĭemand classes allow you to segregate scheduled demand and production into groups, allowing you to track and consume those groups independently.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |