| Production Planning (tisfc0110m000) Production Order In this session, you can only maintain the production
planning of the orders with one of the following statuses: - Created
- Printed
- Released
- Active
Planning Method If the Planning Method field is Forward, the delivery date is
planned forward based on the Production Start field. If the Planning Method field is Backward, the production
start date is planned backward based on the Planned Delivery field. You can only alter this field for: - Manually-entered
orders
- Orders
transferred from the Warehousing package.
Production Start Date and Time The date and time on which the order is planned to be taken
into production. The Production Start field is filled during production order creation. If the production planning
changes, this date can be automatically updated. The start date of the order can be copied from the
planned orders generated in the modules: - Warehouse Orders
- Inventory Planning
- Order Planning
Forward planning
If the planning method field has the value Forward,
the production start date can be used to calculate the delivery date. Backward planning If the planning method field has the
value Backward, the production
start date can be derived from the delivery date and the order lead time of the item.
The production start date is then calculated as follows: Production start date
= delivery date - order lead time of item This formula is used in the following
situations: - When you manually
enter a production order
- When you click the Plan button to recalculate the production start
date
- When a production
order for an item of type Manufactured has no
routing and is transferred to the Job Shop Control module.
Planned Delivery Date Allowed values If the
manufactured item is an RPT item a schedule period
must have been defined for the delivery date. Schedule periods can be defined
in the Calendars and Periods module and must be linked to a schedule in the Repetitive Manufacturing module. The delivery date of the order is copied from the
planned orders generated in the modules: - Inventory Planning
- Order Planning
Forward planning If the planning method field has the
value Forward, the delivery date can
be derived from the start date and the order lead time of the item.
The delivery date is then calculated as follows: Production start date =
delivery date + order lead time of item This formula is used in the following
situations: - When you manually
enter a production order
- When you click the Plan button to recalculate the production start
date
- When a production
order for an item of type Manufactured has no
routing and is transferred to the Job Shop Control module.
Requested Delivery Date The date that the customer has requested for the production
order. - If the planning
method is Forward, the Requested Delivery Date equals the Planned Delivery Date of the moment the production order is generated.
- If the planning
method is Backward, the Requested Delivery Date is the starting point for
planning.
Operation The sequence number of the operation, which is used for the
production of the manufactured subassembly or finished product, and which you
are planning in this session. Operation Status The current status of the operation which you are planning in this session. Start Operation If this check box is selected, there are no operations
before this operation. Blocking Reason If the operation has been blocked, the reason for
blocking. Operated Item The main item, or the phantom on which the operation is executed. If the Operated Item field does not contain the same item as
the Item field, the operated item is a phantom. In this
case, the routing of the phantom is connected to the routing of the main
item. If the operated item is not a phantom, the
main item and the operated item are the same. Initial Hidden Overlap View the percentage of overlap in the planning. Scrap Quantity Unusable material or rejects of intermediate products, for
example, because of faulty components, or products lost in cutting or sawing
operations. The gross material requirements and/or an operation's input
quantity must be increased to account for anticipated scrap. In the BOM, you can define scrap as a percentage of the net
material requirements, which is the scrap factor, and as a fixed quantity,
which is the scrap quantity. A scrap quantity is mostly used to define the
amount of material that is lost every time when you start producing, for
example, to test the equipment. For an operation, you can only define the scrap as a fixed
quantity. The quantity of material that will be lost during
production. The quantity is a fixed quantity that is independent to the
quantity produced. Recording a scrap quantity prevents shortages in
production. Scrap is an extra loss in addition to the loss caused by
the yield being less than
100%. If you generate the BOM from an engineering BOM, the
scrap factor and scrap quantity values will also be copied. However, these
values will only be copied if the sequence number is the only thing changed,
for example, wheel 10/1 to wheel 10/2. If a new item exist on the BOM line, for example, wheel
to spare wheel, the scrap data will not be copied, In this case scrap quantity
and scrap factor will be 0. Slack Time The time between the earliest finish date of the current
operation and the production start date of the following operation. Machine Occupation The number of machines needed to carry out the
operation. Subcontracting Document The type of document that is linked to the subcontracting
operation. Subcontracting Rate Factor The factor that is multiplied with the subcontracting base
rate to determine the cost of subcontracting. Subassembly An intermediary product in a production process that is not
stored or sold as an end product, but that is passed on to the next operation. For subcontracting purposes, a manufacturer can send a
subassembly to a subcontractor to carry out work on the subassembly. This
subassembly has its own item code defined in the Item Base Data. After work is finished, the subcontractor sends the
subassembly back to the manufacturer. Also this reworked subassembly has its
own item code defined in the Item Base Data. Subassembly Warehouse The warehouse from which the subassembly is sent or in which
the subassembly is received. Scrapped The quantity of the item produced by the production order
that was scrapped. This quantity can no longer be reworked or used for any
purpose. Completed If a quantity has already been completed, you can use this
field to report as additional completed quantities of the item. The quantity
that you can report as completed depends on the restrictions imposed by
previous operations, upcoming operations, and Quality. Note - Quantities can be entered as main item quantities or semifinished item quantities.
- If the operation has the status Blocked, you can modify
this field only if the blocking reason of the operation allows for it. This
restriction is explained in the Blocking operations topic.
Serialized items If the items on the operation are serialized, and the As-Built Status Handling field in the Production Order Parameters (tisfc0100s000) session is set to Manual, you
must first update the status of the items in the as-built header ( Serial End Item - As-Built Headers (timfc0110m000) session) before you can complete or reject the
items on the last operation of a production order. Click Serial Numbers to start the Serial End Item - As-Built Headers (timfc0110m000) session. Reason for Rejects The reason for the rejection. Use a reason with reason type Rejection of Production Result. Planning Related Next Operation The operation after the current operation. If this field is 0
(zero), this operation is the end operation. Task The task that is performed in the operation. If anything is reported on the operation,
you cannot change the task anymore. Work Center Note You can only change the work center if the operation
has one of the following statuses: - You cannot change the work center if some quantities
have already been reported completed.
- You cannot change another type of work station into a
line station or buffer.
- You can only change a subcontracting work station if no
purchase orders were generated or if already generated purchase orders can be
deleted or canceled.
Machine The machine on which the
operation is performed. This field is irrelevant in the case of a
non-machine task. You can modify this field. If, for
example, the machine is overloaded or must be repaired, it may be necessary to
move the operation to another machine. Lead Times and Start Date Start Date Transport Date To The date on which the item is transferred from the
sending warehouse of the previous operation. Queue Start Date Click the Automated Queue Time Compression option on the appropriate menu of the Production Planning (tisfc0110m000) session to start the session which you can use to
reduce the planned queue time. Setup+Run Start Date If you alter the date and/or time of
the Remainder Start Date field, LN recalculates the
value of the Setup+Run Start Date field. The start date of the operation is
copied from planned production orders, which are generated in Enterprise Planning, when
the orders are transferred from Enterprise Planning to Job Shop Control. If the production order is transferred
from the session in Production Order Advice (whina3100m000) in Warehousing, LN copies the start
date of the operation from that session. When you manually enter an order in
the Production Order (tisfc0101s000) session, LN calculates the value
of the Setup+Run Start Date field using the lead-time
elements of the operation that you specified in the Routing Operations (tirou1102m000) session. Remainder The date you want to start the operation, or if the
operation has already been started, the date when you want to resume the
operation. If you selected the Fixed Planning Dates check box, you can use this
field to change the date you plan to start or resume an operation. You can choose whether LN uses the remaining
order quantity or, the hours spent to calculate how much work has been carried
out, by changing the Calculation Method Remaining Production Time field in the Production Order Parameters (tisfc0100s000) session. Wait The date and time on which the setup and run time of the
operation are planned to finish, and the wait time is planned to start. for the production order. Note The wait start date is calculated in
the Job Shop Control module. Move The date and time on which the wait time is planned to
finish, and the move time is planned to start. Transport Date From Date on which the item is transferred from the receiving
warehouse, that is, the warehouse of the subcontracting work center. Transport Date To (Next Operation) Date on which the item is transferred from the sending
warehouse of the current operation. Queue Start(Next Operation) or Planned Delivery Date If this operation is followed by other operations, this
field displays the Queue Start(Next Operation) field. If this operation is
the last operation, this field displays the Planned Delivery Date field. These fields are defined as follows SU+Run (Next Oper.) or Requested Delivery Date If this operation is followed by other operations, this
field displays the SU+Run (Next Oper.) field. If this operation is
the last operation, this field displays the Requested Delivery Date field. These fields are defined as follows SU+Run (Next Oper.) The date and time on which the
queue time of the next operation is planned to finish, and the setup and run
time of the next operation is planned to start. If you selected the Transfer Batch Less Than Production Batch check box,
and defined a batch quantity in the Transfer Batch Qty field for the first operation, the
next operation can start before the first operation finished. In this case, the
date and time in the SU+Run (Next Oper.) field of the first operation
is equal to time and date in the Queue Start(Next Operation) field. Requested Delivery Date The date that the customer has
requested the production order. If a production order, originating
from a sales order, is transferred from Enterprise Planning, the
requested delivery date equals the sales order delivery date minus the
warehouse inbound, warehouse outbound, safety time and extra lead time. These
four lead times cause a difference between the sales order delivery date and
the planned delivery date. For more information, see To determine on order dates.
Fixed Duration If this check box is selected, the operation has a fixed duration, and its production time does not depend on the batch
size. If an operation has a fixed duration, LN applies the following
formula to calculate the run time: run time = cycle time If this check box is cleared, the
formula that LN uses to
calculate the run time is as follows: run time = (cycle time * quantity planned input) / routing quantity Transfer Batch Less Than Production Batch The quantity or percentage of items for which an operation must
be finished before you can start with the next operation. Even though an
operation is not yet finished for all items in a production order, you can
start the next operation for the items that are already finished. In a production environment where kanban is used, the
transfer batch quantity equals the kanban size (which is the standard
container, or the standard lot size). The transfer batch quantity replaces the previously used
concept of overlap percentage on operation. If this check box is selected, you
can start the next operation before the complete production batch is finished.
You must enter a value in the Transfer Batch Qty field, which indicates when the
next operation can be started. If this check box is cleared, the
next operation starts when the complete production batch is
finished. If the Transfer Batch Method field in the Routing Parameters (tirou0100m000) session is Quantity, you must type a quantity in the Transfer Batch Qty field. If the Transfer Batch Method field is Percentage, you must type a percentage. Transfer Batch Qty If the Transfer Batch Method field in the Routing Parameters (tirou0100m000) session is Quantity, you must type a quantity. If the Transfer Batch Method field is Percentage, you must type a percentage. Fixed Planning Dates If this check box is selected, LN uses fixed planning
dates, and the operation cannot be shifted due to changes in other
operations. Late Indicator that displays whether the move start date of
the operation falls after the requested delivery date of the production
order. Lead Times Time Unit The time unit in which the queue time is
expressed. Transport Time To The time required to transport the subassembly from the
sending warehouse to the warehouse at the subcontractor. In the manufacturer's
system, the warehouse at the subcontractor is defined as an external
warehouse. Default value The default value is calculated in Freight based on
the addresses of the warehouses. Note If the first operation of the routing
is subcontracted, this field is zero, because in that case no subassembly is
transported from the manufacturer to the subcontractor. Queue Time The queue time of the operation as you defined it in the Routing Operations (tirou1102m000) session. Click the Automated Queue Time Compression option on the appropriate menu of the Production Planning (tisfc0110m000) session to start the session which you can use to
reduce the planned queue time. Fixed Setup Time (SCS) The sequence independent time required to set up or
change over a machine in order to start running the machine. The fixed setup time is only used when Infor SCM Scheduler and Infor SCM Planner are installed. SetupTime(Avg) Note If Man Occup.for Setup = 0 and SetupTime(Avg) > 0, the following
applies: - The machine hours' required capacity calculated for
the order operation is not impacted and includes setup time.
- The setup time is not included in the man hours'
required capacity for the order operation and the required man hours for the
work center. This affects the man hours displayed on the work center
utilization reports and the resource order plan.
- The setup time is not included in the estimated man
hours and is not included in the calculation of operation costs for man
capacity work centers.
- The setup time is used in calculating operation
schedules.
Production Rate You can use a different production
rate for different orders. - If you change the value of this field, LN changes the value of
production time. That means that you can use this field as an alternative way
of entering the operation production time.
- If you click the Calculate Production Rate option on the appropriate menu, LN calculates the
production rate, using the cycle time of the operation. This is only possible if
the Use Production Rates check box in the Routing Parameters (tirou0100m000) session is selected.
Note Whether the production rate is
expressed in hours or minutes is shown in the next field. You can alter that in
the Production Rate Time Unit field in the Routing Parameters (tirou0100m000) session. Production Rate Time Unit The time units in which the production rate is
expressed. You can define this parameter in the Production Rate Time Unit field in the Routing Parameters (tirou0100m000) session. Cycle Time (min) LN uses the cycle time
to calculate the run time and the production time. Routing Unit The inventory unit in which the completed quantity of semi-finished products is
expressed. Remaining Production Time The remaining production lead time required to finish the
operation. Wait Time The wait time of the operation as you defined it in the Routing Operations (tirou1102m000) session, expressed in the time unit you specified in
that same session. Move Time The move time as you defined it in the Routing Operations (tirou1102m000) session, expressed in the time unit you specified in
that same session. Transport Time From Lead time of transport of the subassembly from the
warehouse at the subcontractor to the receiving warehouse. In the
manufacturer's system, the warehouse at the subcontractor is defined as an
external warehouse. Default value The default value is calculated in Freight based on
the addresses of the warehouses and work
centers. Slack Time Selecting the Transfer Batch Less Than Production Batch check box,
and specifying a quantity in the Transfer Batch Quantity field results in less slack time than the queue time of the next operation, or in a slack time value of
zero. For all the options you can select in the Moving Method Next Operations field, except for the Move All Operations option, LN can move the slack time. If you set the
field to When Overlap Occurs, the slack time can become longer if
you move an operation to an earlier point in time. In this situation, LN does not touch the
next operation, and, as a result the slack time on the moved operation
increases. You can compress the slack of all the
operations of an order automatically by reducing queue times. Refer to Queue time compression compression. Overlap View the percentage of overlap in the planning. Capacity / Subcontracting Capacity Data Man Occup.for Setup The number of persons that is needed to accomplish the
operation's setup. You must enter the number of persons that is needed to
accomplish the operation in the Man Occupation for Production field. Note If Man Occup.for Setup = 0 and SetupTime(Avg) > 0, the following
applies: - The machine hours' required capacity calculated for the
order operation is not impacted and includes setup time.
- The setup time is not included in the man hours'
required capacity for the order operation and the required man hours for the
work center. This affects the man hours displayed on the work center
utilization reports and the resource order plan.
- The setup time is not included in the estimated man
hours and is not included in the calculation of operation costs for man
capacity work centers.
- The setup time is used in calculating operation
schedules.
Man Hours The man hours required to carry out the operation. Man Occupation for Production In the Man Occupation for Setup field, you must enter the number of persons needed to
accomplish the operation's setup. Spent Production Time The total number of man hours and machine hours booked on
an operation until the current moment. The time is updated to the operation by People. If you selected the Backflush Hours check box, LN posts the hours
automatically. If you use the Hours and Expenses by Employee Overview (bptmm1100m000) session, the hours are posted to
the order/operation by that same session. Subcontracting Subcontractor The subcontractor where the work takes place if the
operation occurs in a subcontracting work center. Note LN treats
subcontractors as buy-from business partners. Purchase Document The purchase document number that corresponds to the
subcontracting order. Subcontracting Rate Factor LN uses this field and the subcontracting rate to
calculate subcontracting costs. You can define the subcontracting rate in the Subcontracting Rates (ticpr1160m000) session. This field only applies if you selected
the Operation Rate option in the Calculation Method for Subcontracting Costs field of
the Subcontracting Rates (ticpr1160m000) session for calculation of the subcontracting
costs. Qty Returned from Subcontracting The quantity received on the basis of a subcontracting
order. Subassembly An intermediary product in a production process that is not
stored or sold as an end product, but that is passed on to the next operation. For subcontracting purposes, a manufacturer can send a
subassembly to a subcontractor to carry out work on the subassembly. This
subassembly has its own item code defined in the Item Base Data. After work is finished, the subcontractor sends the
subassembly back to the manufacturer. Also this reworked subassembly has its
own item code defined in the Item Base Data. Quantity Planned Quantities Quantity Planned Input If you alter the scrap or yield values
in the Routing Operations (tirou1102m000) session, LN recalculates this
field to maintain the quantity planned output. Inventory Unit Main Item The inventory unit in which quantities of the main item are expressed. Yield Percentage The percentage of yield expected in the
operation. Scrap Quantity The quantity of scrap expected in the
operation. Count Point If this check box is selected, the operation is a count point. Default value The default for this check box is the Count Point check
box in the Routing Operations (tirou1102m000) session. For each operation it is determined if
it is a count point. This is incorporated as a default in the order
planning. You can modify this check box, until
the operation has been reported completed. Actual Quantities Quantity Completed The quantity of items reported as completed, or the
quantity on which the operation has been performed for the current
operation. LN cannot change the
corresponding value if the operation status is Blocked. Quantity Scrapped The quantity that does not reach quality standards for this
operation. LN cannot change the
corresponding value if the operation status is Blocked. Quantity Rejects The quantity that is planned to disappear in the operation
as a result of limited yield. LN needs the quantity
of planned rejects when an operation is reported completed, and it
automatically calculates the quantity completed. The quantity of the planned rejects depends on the
setting of the Yield Type field in the Routing Operations (tirou1102m000) session: - If you set the Yield Type field to Discrete,
the quantity of the planned rejects is 0 (zero) by default.
- If you set the Yield Type field to Continuous, LN applies the following
formula to calculate the quantity of the planned rejects:
Quantity planned rejects=(quantity completed+quantity rejected+quantity to inspect)*(100/yield percentage-1)+scrap quantity Quantity of Item by End Item If you define the operated item as a
phantom in the bill of material, LN uses this ratio to convert semifinished item
quantities that are reported completed to main item quantities. Scrapped Reason for Rejects The reason for the rejection. Use a reason with reason type Rejection of Production Result. Backflushing Backflush Hours If this check box is selected, hours are posted
automatically when an operation is completed. The quantity is based on the hours
estimated to be necessary to complete an operation rather than the actual
number of hours worked on the operation or the materials estimated for an
operation. Serialized items Serialized items can only be backflushed
if in the Items - Warehousing (whwmd4500m000) details session the Serials in Inventory check box is cleared, and the Register Serial Issue During As Built field is Yes. In all
other cases, serialized items cannot be backflushed. If the serialized item is
lot-controlled, the lot from which the items are backflushed is based on the
outbound method ( Last In First Out (LIFO), First In First Out (FIFO)) as is defined in the Items - Warehousing (whwmd4500m000) details session. Quantity to Backflush The quantity of items, whose components and/or hours still
have to be backflushed. If you backflush quantities, they are
posted automatically when an operation is completed. The quantity is based on
the hours estimated to be necessary to complete an operation rather than the
actual number of hours worked on the operation or the materials estimated for
an operation. Quantity Backflushed The quantity of end products included in the total order
quantity for which the components and/or hours have been posted using
backflushing. If you backflush quantities, they are
posted automatically when an operation is completed. The quantity is based on
the hours estimated to be necessary to complete an operation rather than the
actual number of hours worked on the operation or the materials estimated for
an operation. Inspection Data Quantity to Inspect The quantity that has been sent for inspection expressed in
main item quantities. Inspection Status The inspection status from the Order Inspections (qmptc1120m000) session. Miscellaneous Task The task on which the production
hours are posted in People.
In case of subcontracting, the task equals the task from production planning. Physical Location The actual location at which an operation is
executed. This location is useful information for
job shop planners, job shop supervisors, and mechanics in a job shop or
cellular manufacturing environment. Calendar The calendar that LN uses to plan the current operation. Time Zone The time zone LN takes into account for planning production orders. LN takes into account the time zone that you defined
for the address of the department of the involved work center in the Addresses (tccom4530m000) session. Actual Calendar Note - If a work center calendar is specified, the actual calendar
equals the work center calendar. If no work center calendar is specified, the
next applicable calendar is used such as that of the related production department.
- You can see the level at which the actual calendar is
defined in the Origin field.
Operation Text If this check box is selected, an operation text is
present. You can create an operation text in the Routing Operations (tirou1102m000) session. Costing Costing Work Center The costing work center that you linked to the planning work center in the Work Centers (tirou0101m000) session, and which LN uses for costing
purposes. Operation Set A group of operations carried out in the same costing work center which are grouped together for cost accounting
purposes. Within one operation set no WIP transfer takes place. If you cleared the Financial Transactions by Work Center check box in the Production Order (tisfc0101s000) session, operation sets are not
applicable. Container Data Container The container in which the
semi-finished item is carried to the next operation. You can only specify a
container in this field if you selected the KANBAN option in the Supply System field of the Item Data by Warehouse (whwmd2110s000) session for the warehouse in which the operated item
is stored. Containers are pulled to the next
work center / operation by labels. You can define containers in the Item Data by Warehouse (whwmd2110s000) session of Warehousing. Number of Containers The number of containers filled with items
required for the operation. If you want to increase the
replenishment rate between the operations, increase the value of this
field. Container Quantity The item quantity of the container. Container Method The code that represents an instruction how to handle the
items in the container. For example, "stack less than 10 high". | |