| | Planned Orders (cprrp1100m000)If you select one of the sort options on the View menu, LN can display the orders
by order type, by item, by requirement date, or by planner or buyer. Double-click a planned order to go to the Planned Order (cprrp1600m000) session, to view and modify the order lines of planned
orders. Note In practice, most planned orders have only
one order line. Planned orders for which you defined various effectivity units, have multiple order lines. Select a planned order and click Details on the appropriate menu to go to
the Planned Orders (cprrp1100m000) details session, where you can view and maintain the
order details. Select the Generate Order Planning (Item) command to zoom to the Generate Order Planning (Item) (cprrp1220m000) session. Select a planned order and choose Lead-Time Analysis from the appropriate menu to zoom to
the Lead-Time Analysis (cprrp1150m000) session, to see of which lead time components
the order lead time consists. In addition, you can select one of the other
options on the appropriate menu to view order related data about demand, supply, inventory, capacity
and/or material requirements. Note When LN generates supply for purchase schedule
items, the resulting purchase volumes are not translated into planned purchase
orders, but are directly transferred to the Purchase Control module
in Order Management. Scenario The identification of an overall planning solution. Each scenario represents one overall planning solution, and
involves particular settings for the planning of items and resources. You can
use scenarios to analyze and compare various planning options and to find the
best planning solution. For example, you can vary demand forecasts or sourcing
strategies. One of the scenarios is the actual scenario, which
corresponds with the actual planning situation. You can only transfer planned
orders and production plans from the actual scenario to the execution level of LN. If the scenario's plan status is Closed, you can no longer
modify the data related to this scenario. Actual scenario This read-only field indicates whether the selected scenario is
the actual scenario. Order Type Select the order type for which LN must display the
planned orders for the specified scenario. Order Information Planning Method The calculation method for the planned start date and/or the
planned finish date. For a planned order generated during an order
simulation, this field can have these values: -
Backward The computed start date is based on: - A given finish date
- A lead time derived from the routing
-
Backward, Lead Time The computed start date is based on: - A given finish date
- A fixed lead time
-
Manually planned orders If you (re)plan an order manually, you can choose
between the following values: - Backward, Lead Time
- Forward, Lead Time
-
Forward LN computes the finish date based on: - A given start date
- A lead time derived from the routing, or a fixed lead
time (depending on the fixed lead-time horizon)
-
Forward, Lead Time LN computes the start date based on: - A given start date
- A lead time derived from the routing, or a fixed lead
time (depending on the fixed lead-time horizon)
Item Routing The item's routing. To set the value of this field to the
item's default routing, click Default Routing. An item's default routing is
defined in the Item - Routings (tirou1101m000) session. The default routing also depends on
the value of the Order Quantity field. Order Release Determines whether this planned order is ready for transfer
to the execution level. To be released The order is ready for transfer to the execution level. Not to be released The order is not yet ready for transfer to the execution
level. This value can only occur if the replenishment method differs from the
planning method.
Planner The employee or department responsible for planning the
production, purchase and distribution of items. The planner takes into account
the inventory levels, availability of materials, and capacities of resources,
and reacts on signals such as rescheduling messages that LN generates. The employee that planned the order. Buyer The employee of your company who is the contact to the
concerned buy-from business partner. The buyer is also known as the purchasing
agent. Routing Group In this field you can assign routing groups to the item. Routing groups are used in the Shop Floor Control module
of Manufacturing to manage
the workload. Destination Warehouse The warehouse where the
goods are expected to be received. Default value The value of the Default Warehouse field in the Items - Planning (cprpd1100m000) session. If you transfer the planned order, this
information is passed on to the Shop Floor Control module and the Purchase Control module. Transaction Date The date when the planned order was created or modified. Planned Start Date The date on which the order is planned to be started. Note The planned start date equals the start
date of the earliest order line. Planned Finish Date The date on which the order is planned to be finished. Note The planned order's finish date equals
the last order line finish date. Required Date The date for which LN identifies a material requirement. If the projected inventory at that date is less than the
required quantity, the planning engine generates a planned order or a
reschedule-in exception message. The planned requirement date of a manually entered planned
order is equal to the planned order's finish date. Order Quantity The sum of the order quantities of the planned order's order
lines. Freight Order A commission to transport a particular number of goods. A
freight order includes an order header and one or more order lines. A freight order header includes some general information,
such as the delivery date and the name and address of the customer who is to
receive the goods listed on the freight order. A freight order line includes an item to be transported and
some details about the item, such as the quantity and the dimensions. Planned Order Text If this check box is selected, a text is present for
the planned order. Purchase/Supply Item - Purchase Price If the item is a purchased item, this field displays the purchase price, as defined in the Item - Purchase (tdipu0101m000) session. Supplying Site The site from which a plan item is delivered through the
multisite distribution structure. Supplying Warehouse The warehouse from which the item is supplied. Pegging Info Pegged Order Type The order type of the origin of the demand for which this
planned order produces the supply. Pegged Order Number The order that caused the demand for which this planned order
produces the supply. Pegged Position Number The position number of the order line that generated the
demand for which this planned order produces the supply. Pegged Sequence Number The sequence number of the order line that generated the
demand for which this planned order produces the supply. Pegged Operation The operation for which the item that this planned order
supplies is required as a component. Pegged Site The receiving site that generated the demand for which this
planned order produces the supply. Specification Specification If this check box is selected, a specification is present. To display the specification, in the appropriate menu, click Specification. Use Unallocated Inventory If this check box is selected, Enterprise Planning can use
unallocated inventory to supply the demand. Enterprise Planning uses
allocated inventory first. If there is not enough allocated inventory, Enterprise Planning also
uses unallocated inventory. If this check box is cleared, Enterprise Planning can use
only allocated inventory to fill the demand. Hard Pegged To Business Object Type The type of order to which the planned order was hard pegged, such as, Sales Order,
or Service Order. Note The following fields are always used in combination;
together, they identify the relevant order or order line: - Business Object Type
- Business Object
- Business Object Reference
Business Object The order,
or order line, to which the planned order was hard pegged. LN uses this
characteristic to match supply and demand. Note The following fields are always used in combination;
together, they identify the relevant order or order line: - Business Object Type
- Business Object
- Business Object Reference
Reference A reference code to which the planned order was hard pegged. LN uses this
characteristic to match supply and demand. LN can use this field in two ways: - If the Business Partner field is filled, LN uses the Reference field to record a reference code defined by
a customer.
- If the Business Partner field is empty, LN uses the Reference field to record an internal
reference.
You can use a reference code to keep a
collection of parts linked together, even if they follow different routings,
for example, if some of the parts are transported to a subcontractor to be returned later. | |