计划订单 (cprrp1600m000)
使用此进程以维护计划订单。
在实际应用中,大多数计划订单都只有一个订单行,而为其定义了各种不同有效单元的计划订单具有多个订单行。
- Details Session Repeating
-
- 方案
-
整体计划解决方案的标识。
每种方案都代表一个整体计划解决方案,包括物料和资源计划的特定设置。可以使用方案来分析和比较各种计划选项,并找到最佳计划解决方案。例如,可以变化需求预测或供应源分配策略。
其中一个方案将成为实际方案,它符合实际计划情况。只能将来自实际方案的计划订单和生产计划转移至 LN 的执行层。
If the scenario's plan status is 已结, 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.
- 订单类型
-
选择 LN 必须显示指定方案的计划订单的订单类型。
允许值
- 生产订单
-
生产订单的功能概览
- 不适用
-
当前上下文中未使用。
- 预测
- CTP 预留
- 销售报价单
-
销售报价单
- 采购合同
-
采购合同
- 销售合同
-
销售合同
- 仓单
-
仓单
- 服务订单
-
服务订单
- PRP 采购订单
- PRP 仓单
- 采购订单
-
采购订单
- 仓储装配订单
-
仓储装配订单
- 仓库转移
-
仓库转移
- 生产批
- 销售订单
-
销售订单
- 计划分销订单
- 装配件需求
- 生产订单(人工)
-
生产订单的功能概览
- 采购订单(人工)
-
采购订单
- 销售订单(人工)
-
销售订单
- 服务订单(人工)
-
服务订单
- 仓库转移(人工)
-
仓库转移
- 维修销售订单
-
维护销售订单
- 维修工作单
-
维护订单
- 维修销售订单(人工)
-
维护销售订单
- 计划生产订单
- 征求报价单
-
征求报价单 (RFQ)
- 销售计划预测
- 维修工作单(人工)
-
维护订单
- 货运
-
货运单
- 库存
- 安全库存
-
安全库存
- 装配订单(人工)
- 请购单
-
请购单
- 生产计划
-
企业计划子系统中的生产计划
- 计划采购订单
- 采购计划
- 周期盘点单
-
周期盘点单
- 调整订单
-
调整订单
- 重估订单
-
重估
- 生产计划
- 生产看板
- 项目
- 项目(人工)
- 采购计划
-
采购进度计划
- 仓库转移(分销)
-
转移订单
- PCS 项目
- 分配更改单
-
分配更改单
- 销售计划
-
销售进度计划
- 库存所有权更改单
-
库存所有权更改单
- 预期供应
- 已确认供应
- 自客户的预测
- 至供应商的预测
- 卖方业务伙伴转移(采购)
- 采购订单通知
-
采购订单建议
- 卖方业务伙伴转移(计划)
- 买方业务伙伴转移(销售)
- 买方业务伙伴转移(计划)
- 买方业务伙伴转移(人工仓储)
- 买方业务伙伴转移(人工)
- 装配订单
- 买方业务伙伴转移(仓库分销)
- 计划的成本挂钩转移
- 成本挂钩转移
- 项目合同
- 客户索赔
- 供应商索赔
- 计划活动服务
-
计划活动
- 隔离库存
-
隔离库存
- 计划订单
-
The order number of the planned order.
Note:If the order type is planned distribution order, this field displays the order code at the receiving company.
- 计划物料
-
The ordered plan item.
- General
-
- Planned Order
-
- Order Quantity
-
The sum of the order quantities of the planned order's order lines.
- Inventory Unit
-
The inventory unit in which the quantity is expressed.
- 方案状态
-
The order status of the production order.
允许值
/baanerp/cp/domains/rrp.osta
- 订单下达
-
Determines whether this planned order is ready for transfer to the execution level.
-
待下达
The order is ready for transfer to the execution level. -
暂不下达
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.
-
- 地点
-
企业的经营位置。企业可在此位置维护自己的物流数据。它包括同一位置的仓库、部门和装配线的集合。地点用于在多地点环境中为供应链建模。
以下限制适用于地点:
- 地点不能跨国家/地区。地点的仓库和部门必须与地点位于相同的国家/地区。
- 地点链接到一个计划群。因此,一个地点的所有仓库和工作中心都必须属于同一计划群。
- 地点链接到一个物流公司。
可以将地点链接到企业单元或将企业单元链接到地点。
如果将企业单元链接到地点,则地点的实体属于企业单元。反之,如果将地点链接到企业单元,则企业单元的实体属于地点。
- 订购仓库
-
The warehouse where the goods are expected to be received.
默认值
The value of the 订购仓库 field in the 物料计划数据 (cprpd1100m000) session.
If you transfer the planned order, this information is passed on to the 作业车间控制模块 module and the 采购控制模块 module.
- 物料清单
-
用于制造计划订单的产品的产品模型 ID 和修订。
- 物料工艺流程
-
The item's routing.
An item' s default routing is defined in the 物料工艺流程 (tirou1101m000) session. The default routing also depends on the value of the 数量 field.
- 工艺流程
-
/baanerp/ti/bom/tibom3100m000#tibom300.rouc
- Planning
-
- 计划编制方法
-
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 the following 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:
-
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)
-
Backward
LN computes the start date based on:
- A given finish date
- A lead time derived from the routing, or a fixed lead time (depending on the fixed lead-time horizon)
-
- 计划需求日期
-
LN 标识物料需求的日期。
如果该日期的预期库存小于需求数量,计划引擎会生成计划订单或紧急重排进度计划例外消息。
人工输入计划订单的计划需求日期等于计划订单的结束日期。
- 计划起始日期
-
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.
- 计划结束日期
-
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.
- Details
-
- Roles
-
- 计划员
-
负责计划物料的生产、采购和分配的员工或部门。 计划员会考虑库存级别、材料可用性和资源能力,并对 LN 生成的重排进度计划信息等信号做出响应。
The employee that planned the order.
- 计划订单组
-
The planned order's order group.
- 工艺流程组
-
In this field you can assign routing groups to the item.
Routing groups are used in the 作业车间控制模块 module of 制造管理 to manage the workload.
- 采购员
-
贵公司负责与相关卖方业务伙伴进行联系的员工。 采购员也称为采购代理。
Note:When the 允许在计划采购订单中分派采购员 parameter is checked this field can be edited.
- 车间计划员
-
负责打印、(重新)制定生产订单进度计划并下达生产订单及管理工作量的人员。
The employee that is responsible for the item in Job Shop Control (JSC).
The shop floor planner is also a selection criterion that determines which orders are included in an order group in the 创建计划订单的订单组 (cppat3250m000) session, and which orders are transferred in the 转换计划订单 (cppat1210m000) session.
- Properties
-
- 项目 (PCS)
-
A collection of manufacturing and purchasing actions that are performed for a particular customer order. A project is initiated to plan and coordinate the production of the to be manufactured items.
For a standard-to-order production, the project is only used to link the item with the customer order. A project can also include these:
- Customized item data (BOMs and routings)
- Project planning (activity planning)
- 模块
-
A planning unit for a customized, manufactured, or purchased part, for which the logistical planning is related directly to the project network planning. A module may be a more or less complex compound part or a single part, such as a long delivery time part.
- 事务处理日期
-
The date when the planned order was created or modified.
- 订单分配
-
/baanerp/ti/sfc/tisfc0120s000#tisfc001.odpr
- 工序分包
-
如果选中此复选框, one or more operations of the planned order are subcontracted.
- 由 Infor Planning 计划
-
如果选中此复选框, all planning for the order is done by the Infor Planning.
- 计划订单文本
-
如果选中此复选框, a text is present for the planned order.
- Initial Peg
-
- 挂钩公司
-
The receiving company that generated the demand for which this planned order produces the supply.
- 挂钩订单
-
The order that caused the demand for which this planned order produces the supply.
Note:If the production order supplies multiple sales orders, only the first will be referenced by the initial order peg. If changes are made to the order, the order peg is not updated. Pegs displayed in this session may be out of sync with the date displayed in the 浏览订单挂钩 (cprrp0740m000) session.
- 挂钩位置
-
The position number of the order line that generated the demand for which this planned order produces the supply.
- 挂钩序号
-
The sequence number of the order line that generated the demand for which this planned order produces the supply.
- Purchase
-
- Purchase
-
- 物料采购价格
-
If the item is a purchased item, this field displays the purchase price, as defined in the 物料采购数据 (tdipu0101m000) session.
- 供应商
-
您从其订购货物或服务的业务伙伴;这通常是供应商的销售部门。其定义包括了默认价格和折扣协议、采购订单默认值、交货条款及相关的运输方和发票开具方业务伙伴。
The supplier designated to the planned purchase order.
- 供货方业务伙伴
-
将订购的货物装运给您公司的业务伙伴。这通常指供应商的分销中心或仓库。其定义包括了要对货物进行检验时接收货物的默认仓库、负责货物运输的承运人及相关的卖方业务伙伴。
- 承运人
-
提供运输服务的组织。您可以将默认承运人链接到进货方和供货方业务伙伴。此外,您可以将销售和采购订单按照承运人排序打印到装箱清单上。
在下订单和开发票时,您必须将承运人定义为业务伙伴。
- 请求者
-
完成生产订单所需的估计小时数,包括计划的排队时间。
- Miscellaneous Data
-
- 分包采购订单
-
如果选中此复选框, the order or parts of the order are being subcontracted.
- 分包商发料日期
-
The date on with the order was subcontracted.
- Target Price
-
- 目标价格
-
The target price retrieved from the purchase order line.
- 价目表
-
The price book used.
- 业务对象类型
-
The type of order to which the planned order was hard pegged, such as, 销售订单, or 服务订单.
Note:The following fields are always used in combination; together, they identify the relevant order or order line:
- 业务对象类型
- 业务对象
- 业务对象参考
允许值
- 服务(人工)
- 维修销售订单
-
维修销售订单
- 维修销售(人工)
- 维修工作单
-
维修订单
- 维修工作单(人工)
- 销售订单
-
销售订单
- 销售计划
-
销售进度计划
- 不适用
- 销售(人工)
- 服务订单
-
服务订单
- 业务对象
-
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:
- 业务对象类型
- 业务对象
- 业务对象参考
- 参考
-
A reference code to which the planned order was demand pegged.
LN uses this characteristic to match supply and demand.
LN can use this field in two ways:
- If the 业务伙伴 field is filled, LN uses the 参考 field to record a reference code defined by a customer.
- If the 业务伙伴 field is empty, LN uses the 参考 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.
- 业务伙伴
-
The sold-to business partner to which the planned order was hard pegged.
LN uses this characteristic to match supply and demand.
- Miscellaneous Data
-
- 分包采购订单
-
如果选中此复选框, one or more operations of the planned order are subcontracted.
- 分包商发料日期
-
The date on with the order was subcontracted.
- Supply
-
- 公司
-
通过多公司分销结构从中交付计划物料的公司。
- 方案
-
The supplying scenario ID.
- 计划物料
-
If this planned order is a planned distribution order, this field displays the supplying item.
- 订购仓库
-
The warehouse from which the item is supplied.
- 货运单
-
运输特定数量货物的委托书。 货运单包含一个订单页眉及一个或多个订单行。
货运单页眉包含一些常规信息,如交货日期及接收货运单上所列货物的客户的名称和地址。
货运单行包含要运输的物料及一些有关该物料的详细资料,如数量和尺寸。
- Customer Furnished
-
- 由客户提供的材料
- 包含由客户提供的材料