Professional Documents
Culture Documents
Microsoft Dynamics AX 2009 Lean Ordering Cumulative
Microsoft Dynamics AX 2009 Lean Ordering Cumulative
Microsoft Dynamics AX
®
http://www.microsoft.com/dynamics/ax
Table of Contents
Introduction ................................................................................................ 3
Assumptions ........................................................................................................................ 3
Purpose of the Lean ordering (Cumulative) feature ................................................................... 3
Process overview .................................................................................................................. 5
Prerequisites ........................................................................................................................ 5
Assumptions
It is assumed that the user has knowledge and experience in the following areas in Microsoft
Dynamics AX:
Lean kanbans
Accounts receivable
Production
Inventory management
Accounts payable
Prerequisites
Apart from the requirement to have items registered within lean ordering, the only
prerequisite is that the warehouse on the item corresponds with the warehouse that the
final assembly schedule will book production into.
Functionality description
Overview
The key elements of the feature are:
Lean ordering setup – This is where the structure of product groupings (families) and the associated
items are established together with the various parameters that are required by Lean ordering and the
resulting schedule.
Lean order schedule – This is the schedule identity number that is used to pull together all of the
entries on the schedule.
Work cell – This is the work cell identity for the final assembly area. When the schedule is linked to a
product family (and therefore all the items within the family), this is the cell that will undertake the
final assembly process.
Value stream – Used by Lean Accounting to associate a schedule with a value stream. The value
stream is a Microsoft Dynamics AX finance dimension. For additional information, see the Lean
Accounting user guide.
The Setup tab incorporates a large number of fields that are used only by Book-to-order schedules.
The following fields are those that are used by cumulative schedules.
Sales order (Status) – This is not used in Lean ordering Cumulative.
Lean order method – This parameter is only used for cumulative schedules (and is set to None for
Book to order). It controls how lean ordering interacts with scheduling the final assembly schedule.
Depending upon this parameter setting, the system may attempt to find production capacity for a new
order line automatically, provide the user with the option to find a production slot manually or inhibit
checking (ignoring capacity constraints) at the point of order entry.
If checking is inhibited at order entry, production leveling can be performed later by use of the
Heijunka process. If a production slot is selected at order entry, Heijunka is not used.
The values and outcomes are defined below
None – The schedule is assumed to be flexible, and the rate of output can increase or decrease,
for example, bringing workers to the cell. Heijunka scheduling will be permitted.
Always slot – When sales orders are entered, they will automatically find a slot for the whole
order.
Always Split – When sales orders are entered, they will be split (backward and forward) in time
consuming the drumbeat of the cell.
o Period start day – This is the start day of the week for the periods over which the
schedule will be viewed.
o Schedule period – Determines whether the schedule will contain periods (buckets) of
one day or one week duration.
o Schedule duration – Determines whether the schedule will be displayed in weeks or
months.
o Schedule duration length – Determines the schedule display period in terms of the
schedule duration.
Operational parameters
The following operational parameters apply to cumulatives.
Use lean warehousing – While the warehouse can be controlled by Lean warehousing and the Lean
warehousing dispatch forms used, it is assumed that standard Microsoft Dynamics AX will manage the
dispatch process. Setting this parameter populates the Warehouse field in the sales order line based
on Lean warehousing logic.
Use sales order BOM – The ability to read the BOM that is associated with the sales order is
standard functionality in Lean manufacturing. When selected, this parameter will cause the BOM on
the sales order to be used in the pull/assembly structure process.
Book to sales order – This check box will determine whether items on the schedule are pegged
directly to the originating sales order or allowed to be mixed within the schedule. Do not select this
check box when the Lean schedule is cumulative.
BOM version – If a specific BOM code is always used by the schedule and shared by members of a
product family, it can be selected here. It will be overridden by the Sales line BOM parameter on the
Setup tab.
10
Info tab
This tab is not used by cumulative schedules.
Structure setup
Family groups and the items within the family groups are loaded against a cell. It is assumed that only
one type of product will be loaded on a final assembly cell. The structure to establish this is defined as
follows:
Family groups
Lean manufacturing > Setup > Lean ordering > Lean ordering > Family grouping
The family group is defined and linked to the schedule that will be loaded on the final assembly cell. It
is possible to limit families to a proportion of the drumbeat capacity.
Family group – Use a code to define the group.
Description – A brief title for the group.
Lean order schedule – This field created the link between the family group and the schedule.
Maximum quantity – Where more than one family is associated with a schedule, a maximum
quantity, related to the capacity that is recorded against the Drumbeat per day field on the Setup
tab for the schedule, can be entered. It is important to ensure that the sum of these maximum values
does not exceed the overall capacity per day.
11
Lean manufacturing > Setup > Lean ordering > Lean ordering > Item grouping
The parts within the family are then defined:
Family group – The code that is used to define the group.
Group member item – The item code for the family group members.
BOM – If a specific bill of materials is to be used, it can be defined here.
Route number – If a specific routing is to be used, it can be defined here.
Ratio – This is not used by cumulative schedules.
Mandatory – This is not used by cumulative schedules.
Sales schedule – Used to link the item to both the cumulative schedule and, where applicable, a
sales schedule.
12
If the parameter is set to Always split, the available capacity will be consumed across available slots
until the requirement has been satisfied.
13
14
Clicking OK in the preceding form undertakes all of the necessary action to book the production into
the default warehouse for the item. If serial or batch numbers are required for the product to be
produced, then these should be generated by accessing the main table for the order and undertaking
the required action. This is standard for Microsoft Dynamics AX.
15
Post leveling
The results of the leveled can be viewed at this stage because they have not yet been confirmed.
When you click the Confirm button, the following form is displayed.
16
Leveling completes the process for Lean ordering where cumulatives are used. The inventory will be
present in the warehouse and normal sales order dispatch processes can be undertaken.
17
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the
date of publication. Because Microsoft must respond to changing market conditions, this document should not be interpreted to be a
commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of
publication.
This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS
TO THE INFORMATION IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of
this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means
(electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of
Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject
matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this
document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
18