Introduction
Production control in Microsoft Dynamics AX 2012 consists of many aspects of the production environment. This includes creation, estimation, scheduling, consumption, feedback, and cost accounting for production orders.
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-1
In this chapter, you will review the following major components of the Production control module. Bill of materials: A list of all parts, components, and raw materials needed to produce a product. Routes: The path that the item takes from operation to operation throughout the production life cycle. Production orders: A source document that defines what is to be produced, how much (quantity), and a planned finished date. Scheduling: An iterative activity where the system tries to find a set of resources that can deliver the product on or before the requested date. Planned production orders: A special type of "pre" production orders that is used to generate firmed production orders that is based on demand and other factors. Lean, Kanban, and Production flow: Introduce industry best practices for pull based production. Process Industries: Review of how Microsoft Dynamics AX 2012 can support process manufacturing principles.
10-2
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
Bill of Materials
A bill of materials (BOM) is a complete list of all the components, parts, raw materials, assemblies and their quantities that are required to make a finished product. BOMs define the relationship between the components and the finished product or sub-assembly. The item number that represents the BOM is often referred to as the finished product, and the components that make up the finished good are referred to as raw materials. In some cases the item number that represents a BOM is not a finished good and is instead referred to as a sub-assembly which is used in another BOM to create a finished product or another sub-assembly. A clear definition of this relationship is important for the following. Allocation of materials Scheduling of operations or jobs Creation of production orders Costing of the BOM and production order
Every item that must be physically accounted for in a finished product or subassembly product or financially accounted for in the costing phase must be included in the BOM. Although BOMs define the components and their relationships, they do not define the sequence of steps to produce or assemble the finished item. BOMs are made up of product types, versions, configurations, sites, levels, lines, and information used for cost calculations. In the following sections, these components and the data model for BOMs are reviewed to illustrate the relationship between the tables.
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-3
BOM Version
A BOM can have multiple versions. When you create a BOM, you must have at least one version. In order to use the BOM it must be approved and activated. Later, if the BOM is no longer required, the activation and approval can be removed. The BOM version is used to define which finished product item numbers are linked to the BOM. You can also specify information about the date of validity, site, quantity ranges, whether the version is active, and who approved it. Zero or more BOM versions can be valid or active for any item at any given point in time. However, only one version can be applied. The applied version is selected based on time, site, and quantity. The BOM version is useful in these cases. Two products that consist of the same raw materials but different production processes will be able to use the same BOM but different routes. For example, the same product is produced in two different sites by using different equipment. When changing the raw materials of a product over time, different BOMs can be attached as of a specific date. In the example of the personalized coffee mug, the paint that is used for the mug was originally paint X, and now they are going to use paint Y to make the mugs. This change can be reflected in a new BOM version as of the date that the change occurs.
BOM Configuration
For planning, calculation, and consumption purposes, each BOM line must specify whether the item has any configurations. A configuration is a standard component combination, such as a satellite speaker and a sub-woofer that can be specified for a BOM item during the ordering process. For example, the user might select the size and color of speaker to be included in the home theater system.
10-4
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-5
BOM Costing
Bills of material calculations use data from several sources to calculate the rolled-up or total costs of a manufactured item. The sources include information about items routing details, indirect cost calculation formulas, and the costing version. The purchased item information that is used in a standard cost BOM calculation includes cost, cost group, and warning conditions. The manufactured item information that is used in a standard cost BOM calculation includes standard order quantity for inventory and warning conditions that are embedded in the item's BOM calculation group. The bill of material information that is used in a standard cost BOM calculation depends on the following. BOM version BOM line item quantity BOM line item scrap BOM line item valid dates The default order type of the BOM line item Parameters for the cost calculation Sub-route for a manufactured component Effect of operation scrap percentages
10-6
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
The BOMTable is the primary table of the construct. Contained within is the setup for a Bill of Material, including Approved, BOMId, Name, Version, and SiteId. This is best described as the header information that you must define for the BOM. For example this is an Eight inch woofer speaker assembly. The BOM is the line items associated with the primary table. You can have many line items that are related to each BOMTable. Each BOM record is related to one InventTable record to create the link for the components to the raw materials items and services. For example, the woofer speaker assembly might include the speakers, cabinet, and cross over assembly needed to construct the speaker. For the speaker assemblies, they can be used for other cabinets or other configurations. The BOMVersion is the final table needed for the basic BOM set up. The relationship between the BOMTable and BOMVersion is one or more versions for each BOM. Each BOMVersion record is related to one InventTable record to create the link to the finished product item number. For example, one version could be used for one site and a different version for another site. Frequently BOMs are phased out, with new components that are included in the latest version.
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-7
Routes
Routes are the path or sequence that the product takes from operation to operation, starting with the beginning of the production process and continuing to the end. It is a set of sequential operations, or tasks, that are required to produce a product. The route operations describe the requirements for the resources that are required for performing each operation. Each route includes the following: Operations to be performed. Operations relations. Sequence of the operations. Resources requirements involved in completing the operations. Standard times for the set up and run of the production.
One or more routes can be mapped for each product, depending on the product and the process. You can create a completely new route, or you can base a new route on existing route information, and then adjust or update the information to match the new production process. The same route can also be used for multiple products. In the following section, you will review how to use routes and operations and the data model associated with them.
10-8
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
The use of the operation relation is limited in the way it is attached to items and routes. Each relation is attached to an item, an item group, or all items. At the same time, each relation is attached to either a route or all routes. This means that one operation could include different information on times, cost categories, properties, and so on, specified in separate relations. Therefore, the same operation can be used in several routes by creating a relation for each route.
Sequence of Operations
Operations in a route must be attached to each other in a logical way to reflect the production process. Depending on the complexity of the production, this can result in a route network. For simple routes, where the operations are executed one after the other, a route network is not required. However, complex networks are frequently needed to reflect the production environment. If this is the case, you can construct routes that contain several operation branches that can be started independently. Another network operation is concurrent operations. In this case, prerequisites are run first, and then several operations run in parallel, ending in a completion operation. Each operation in a route can have multiple predecessors, but only one successor. As a consequence, a route may have multiple starting points, but only one end-point. Therefore, only a subset of all possible networks may be modeled as routes.
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-9
10-10
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
Also important for this model, is the relationship between Routes, ReqRoute, and ProdRoute tables. For example, a regular route includes how the task or activity is completed, the order and operation priority, and the requirements for the resources that will perform them. The ReqRoute table is primarily populated during master planning to record which operations are used for a production order, and when the planned order is firmed. This data is then combined with the operation relation to make up the production route in the ProdRoute table. This makes sure that the route does not change mid-process and still allows planners and schedulers to be able to update the Route table. The route on a specific production order can be modified; much like a BOM can be, without affecting the original route.
Production Orders
The production order contains information about what is to be produced, how much (quantity), and the planned finish date. The system assigns an order status to each step in the life cycle of the order. The status shows where the item is in the production process. The following sections include an overview of production orders, orders statuses, the data model, the journal framework, and three production order classes.
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-11
10-12
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
Step 4 Released In this step, the system releases the production order when the schedule is realistic. At this point, you can print production order documents such as the job card and the route card. Now, the status of the production order changes to Released and indicates that the production can start.
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-13
10-14
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
The ProdTable is the primary production order table, which contains the header information about all of the production orders. Each production order contains is related to at least one InventTransOrigin and InventTrans table record. Each production order can be connected to a planned production order, a sales order or a project. When a production order is created from master planning, the planned production order is stored in the ReqPO table. The ProdTableProj table contains information about production orders that belong to projects. Such a production order is connected to a real production order stored in the ProdTable table and to a project stored in the ProjTable table. The ProdBOM table contains a productions bill of materials. This information is copied from the BOM and BOMTable.
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-15
When a production journal posts, all transactions are automatically transferred to the General ledger. The General ledger is the centralized location for financial information in Microsoft Dynamics AX 2012. Information posted from various journals in the system is used in the General ledger when companywide financial transactions are calculated. Production journals consist of two main partsthe journal header and the journal lines, or actual journal records. Journal lines reflect the actual records or entries present in the journal. These records can include a list of production materials ready for release, the time consumed, the number of good and defective items, and so on.
ProdMulti
You can update production orders one at a time or update multiple orders one time. You can use the RunBaseMultiParm structure to run different parameter (parm) tables that use the same structure. The ProdMulti class is the base class that you can use to update production orders. It is based on the RunBaseMultiParm class. A user interface (UI) should be implemented for derived classes.
10-16
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
} else { } }
RunBaseMultiParm::runSpecial(_args);
ProdMultiCostEstimation is instantiated, and then passed into the static method RunBaseMultiParm::initFromForm(), together with args. 2. View the RunBaseMultiParm::initFromFormInternal() method:
/// <summary> /// Initializes an instance of the <c>RunBaseMultiParm</c> class by using a container of packed records. /// </summary> /// <param name="_includeRecords"> /// A Boolean parameter that indicates whether records are included. /// </param>
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-17
parmBuffer is a table map that is mapped to the different parm tables. RunBaseMultiParm.defaultParmBuffer() is overridden in the sub-classes and returns the appropriate parm table. RunBaseMultiParm::initParm() retrieves saved data (from sysLastValue by calling getLast()) and sets the ParmId used in the update.
static server void initParm(RunBaseMultiParm runBaseMultiParm) { runBaseMultiParm.getLast(); runBaseMultiParm.initParmId(); }
All selected records in the form data source are added to the appropriate parm table. If the update is called from the main menu, there is no data source and no records are found.
10-18
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
} else { } }
RunBaseMultiParm::runSpecial(_args);
The prompt displays the form where the user can change the settings to update the order. There is also a Select button on the form that the user can click to modify the query and select more records. When the form is opened from the main menu (Production control > Periodic > Production orders), the query is empty and the user must click this button to select the records for update. The run() method is then called. 4. View the ProdMultiCostEstimation.run() method:
... while (curParmCostEstimation) { try { prodTable = this.initProdTable(curParmCostEstimation.ProdId); prodTable.status().runCostEstimation(curParmCostEstimation, false,prodPurch,this); } catch (Exception::Deadlock) { retry; } ...
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-19
All records in the parm table are looped over. The ProdStatusType sub-class is instantiated by using the status of the prodTable record, then the update is called.
ProdStatusType
Production order updates are controlled by using the ProdStatusType class and subclasses. Each stage of the update process must occur. If the current status of an order is Estimated, and you try to update it to Report as Finished, then it must be Scheduled, Released, and Started before it can be reported as Finished. The required status and status sequences are configured in the Production control parameters form. Before each update is run, the system checks to determine whether the previous status is already processed. If the update is not installed, then the system runs that update. It also handles which updates can occur with a production order. For example, a production order with the status Finished, cannot be Estimated.
10-20
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
ask is set to true only when the method is called to ask whether the update is allowed, not to run the update. ProdUpdReportFinished::RunPreviousJob runs the update to the status Started. 3. View ProdUpdReportFinished::RunPreviousJob.
static void runPreviousJob( ProdParmReportFinished prodParmReportFinished, RunbaseRecsMapable _multi = null) { ProdParmStartUp prodParmStartUp = ProdUpdStartUp::initParmBufferFromRepFin(prodParmReportFini shed); prodParmStartUp.insert(); ProdTable::find(prodParmStartUp.ProdId).status().runStartUp ( prodParmStartUp,
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-21
A record in ProdParmStartUp is created by using the ProdParmReportFinished record that is used for the update to Report as Finished. The ProdStatusType_Released sub-class is instantiated by using the status of the production order and calls ProdStatusType.runStartUp(). 4. View the ProdStatusType.runStartUp() method.
if (!_ask) { if (this.shouldRunPreviousJob(ProdStatus::StartedUp)) { ProdUpdStartUp::runPreviousJob( _prodParmStartUp, } prodTable.type().runStartUp( _prodParmStartUp, } return true; _prodPurch, _multi);
_multi);
Because the previous status to Started is released, and because this order is already released, it is not necessary to run the previous job. As soon as the update to the status Started occurs, it returns to ProdStatusType.runReportFinished(), then runs the update to Report as Finished.
10-22
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
The ProdUpd class is an abstract class, and you cannot make an instance out of it. You can only inherit this class from other production update classes. To update production order stage, the following classes are used: ProdUpdBOMCalc ProdUpdCostEstimation ProdUpdScheduling o o ProdUpdScheduling_Operation ProdUpdScheduling_Job
To decrease production order status, the following classes are used: ProdUpdStatusDecrease o o o o o ProdUpdStatusDecrease_CostEstimate ProdUpdStatusDecrease_Finished ProdUpdStatusDecrease_Release ProdUpdStatusDecrease_Schedule ProdUpdStatusDecrease_StartUp
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-23
ProdStatusType.RunStartUp() runs the update to the Startup status. The following steps demonstrate the use of ProdUpd. 1. View the ProdStatusType.RunStartUp() method. This method was reviewed earlier in the "ProdStatusType" topic. ProdUpdStartUp is instantiated by using the parm table, and then run. 2. View the ProdUpdStartUp.run() method.
void run() { #OCCRetryCount RecordViewCache
viewCacheProdRoute;
viewCacheProdRoute = null; viewCacheProdRoute = ProdRoute::viewCacheProdId(prodTable.ProdId,true); this.updateProduction(); this.updateBOMConsumption(); prodTable.status().startUpUpdateRouteJobs(this); this.updateRouteConsumption(); this.startupReferences(); this.updateJobJournal(ParmJobStatus::Executed); TransactionLog::create(TransactionLogType::ProdStartUp, strfmt("@SYS76498",
10-24
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
} ...
ProdUpdStartUp.setParameters() retrieves ProdTable and initializes BomCalc. It is called when component dimensions are used in the calculation of item consumption. viewCacheProdRoute activates cache on all prodRoute records for the current production order. 3. ProdUpdStartUp.updateProduction updates the prodTable.Status, prodTable.StartedUpQty, and prodTable.StUpDate.
void updateProduction() { if (prodParmStartUp.StartUpProduction) { prodTable.QtyStUp += prodParmStartUp.StartUpQty; } prodTable.ProdStatus = prodTable.status().isBefore(ProdStatus::StartedUp) ? ProdStatus::StartedUp : prodTable.ProdStatus; prodTable.StUpDate = prodParmStartUp.PostDate ? prodParmStartUp.PostDate : systemdateget(); prodTable.update(); this.addUpdateRec(prodTable); }
4. ProdUpdStartUp.updateBOMConsumption() creates the picking list journal. If the update is set to post the BOM consumption, it also posts the journal. 5. The production route is updated and the route journal is created and posted. (This sample comes from the ProdUpdStartUp.run method reviewed earlier.)
this.startupReferences(); this.updateJobJournal(ParmJobStatus::Executed); TransactionLog::create(TransactionLogType::ProdStartUp, strfmt("@SYS76498", prodTable.ProdId, "@SYS77138")); ttscommit;
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-25
Scheduling
Scheduling is an iterative activity where the system tries to find a set of resources that can deliver the product on or before the requested date. In the following sections, you will review the main production scheduling concepts that provide an overview of scheduling, resources, the resources data model, and jobs.
Scheduling Overview
The scheduling engine is aligned with the new resource model in Microsoft Dynamics AX 2012. This introduces capabilities and priorities, and replaces work centers and work center groups by using resources and resource groups. You can run scheduling after the production order is created and estimated. Production dates and other information important to the production process are established at this point. The role of the scheduling system is to plan the actual production process so that each operation in the production route is assigned a starting and ending date and time, and that the materials needed for production are available when the operation starts. Another important role of the scheduling system is to assign jobs and operations to a resource or resource groups. This depends on whether job scheduling or operation scheduling is used. Running scheduling raises the production status to Scheduled.
Resources Overview
Microsoft Dynamics AX 2012 introduces resources that are assigned to jobs and operations. Resources can be different types including machines, tools, human resources, vendors or locations. The scheduling engine aligns with the new resource model and can schedule resources based on their capabilities. Resources and capabilities replace work centers and task groups to provide for more flexibility in setup and maintenance. In Microsoft Dynamics AX 2012, resources can be allocated to jobs and operations by matching the capabilities of the resources with the requirements of the operation. Alternative resources with the same capabilities are considered, unless there are requirements for a specific resource or resource group. This applies whether you select to run job scheduling or operations scheduling. The selection process consists of matching the requirements of the operation with the capabilities of the resources. Other requirements, such as location, resource working time, and resource type are also considered when planning the production. Microsoft Dynamics AX 2012 has changed the following to the Operations Resource Model.
10-26
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
In the following section, you will review resources and recourse capabilities.
Resources
Resources are used throughout the production or project processes. They can be machines, tools, people, vendors or locations that contribute to the production of an item. After an operations resource is created, you can assign it to a resource group and specific productions. Resource groups have fixed location. You can move resources to another location by reassigning them to a different resource group. However, a resource can only be assigned to one resource group at a time. The Effective and Expiration date fields on the Resource groups tab represent when the resource in question can be used for production. With this setup you can share a resource across many sites. When a resource becomes a member of the resource group that has a different location, it represents the physical move from one site to another. You can also copy resources to make the setup of resources easier. During the scheduling process, the capacity of a resource group is calculated as the sum of the capacity of its resources. Resources are used in the detailed planning of capacity requirements and in job scheduling. When job scheduling is run, the operations in each resource are scheduled into individual tasks or "jobs." Five types of resources are available. Vendor: Select this type when the resource is an external operations resource, for example, with a subcontractor. Human resources: Select this type when the operations resource is a worker. Typically, you schedule the human resources type if the personnel capacity is limited. Machine: Select this type if the resource is considered a production machine. Tool: Select this type if the resource is considered a tool. If you want to schedule for tools, machines, or personnel at the same time, select a primary operations resource that determines the capacity available. Location: Select this type if the resource is considered a location.
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-27
10-28
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
Resource Requirements
When defining the requirements for a production route, you can also specify skills, courses, certifications or title as requirements in addition to capabilities. This does not require a relation to a worker. These values are set up in the Human resource module and are not defined in the Capabilities form. When defining skills, courses, certifications or title as requirements, you must have the Human resources module enabled. You can define capabilities in the Capabilities form that resemble or duplicate those from the Human resources module. However, the Capabilities form does not contain the functionality that is required to maintain skills, courses, certifications or titles. Skills: You can use the Skills form to create and manage competencies that are specified for employees or jobs. An operation can require a human resource with a specific skill, and the scheduling engine will find resources with the specific skills. It does this by searching for the skill information on the worker to which the resource is linked. This is only applicable for job scheduling, and not operation scheduling. Courses: You can create and maintain the courses your employees have attended. An operation can require a human resource with a specific course, and the scheduling engine can find resources with specific courses. It does this by searching for the course information on the worker to which the resource is linked. This is only applicable for job scheduling. Certificate: You can add certificates to a user in human resources and use this to track all employee certificates. An operation can require a human resource with a specific certificate, and the scheduling engine can find resources with specific certificates. It does this by searching for the certificate information on the worker to which the resource is linked. This is only applicable for job scheduling. Title: The title an employee has can also be a requirement for a job. An operation can require a human resource with a specific title, and the scheduling engine can find resources with specific titles. It does this by searching for the title information on the worker to which the resource is linked. This is only applicable for job scheduling.
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-29
10-30
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
These requirements types are important to many companies. EXAMPLE: Food and drug companies because their modern production facilities must be in compliance with the United States Food and Drug Administration (FDA), Code of Federal Regulation, (CFR) Title 21, Part 11, requirements that involve the validation and control of safe practices. The system is designed to make sure that workers are educated in their respective positions and can validate they are current on all training, certifications, and have sufficient authority (through title) to complete operations.
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-31
When the requirements are not met by the current inventory, a planned production order can be issued that specifies what is needed and when. Then the planner knows what is missing and he or she can make decisions about how to meet these requirements. NOTE: Master planning can generate several types of planned orders such as planned transfer, planned purchases, or kanbans, not just planned production orders. The following figure shows the steps for the Master planning module that must be completed to run and generate the planned production orders.
10-32
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
LEAN Manufacturing
Lean manufacturing is a both a process philosophy and workable process methodology. It introduces best practice material handling and best in class manufacturing methods that are now standard across industries. The core concepts for lean manufacturing provide a base level understanding of the system functionality within Microsoft Dynamics AX 2012. In the following section, you will review the Lean production principles, the overview and rules for Kanban, and production flow processes.
Kanban Overview
In Microsoft Dynamics AX 2012, the Lean manufacturing module introduces kanbans as a pull-based just-in-time production system. Kanbans relate to a sequence of kanban jobs. Each kanban job has a status that indicates its current stage in the production or transfer process. Each kanban also has a status, the socalled handling unit status that indicates the overall state of a kanban and the related handling unit.
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-33
Kanbans are created based on kanban rules. Kanban rules operate on a production flow or on part of a production flow. There are two types of kanbans: Withdrawal kanbans Manufacturing kanbans
Similarly, there are two types of kanban jobs: Process jobs Transfer jobs
10-34
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
Scheduled Kanbans
Master planning creates scheduled Kanbans automatically for planned Kanban orders to cover the requirements within the firm horizon of the production forecast. Scheduled Kanbans can also be manually created.
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-35
Production Flow
Typically, a Lean manufacturing scenario is more than an accumulation of unrelated Kanban rules or material supply policies. The flow of material and products throughout work cells and locations for a specific production or supply scenario is described as a sequence or small network of process or transfer activities, which is known as a production flow. Microsoft Dynamics AX 2012 introduces the activity based production flows to establish a production and cost context for various Kanban scenarios. All Kanban rules are directly connected to this predefined structure. The activity based model is used to set up a wider range of scenarios than those supported by earlier versions of Lean manufacturing in Microsoft Dynamics AX. Additionally, it is now easier for shop floor workers to use because all scenarios use the same activity based user interface.
To better support continuous improvement, the production flows are implemented in time-effective versions. You can copy an existing production flow versionincluding all related Kanban rulesto a future version of the production flow, and model the future-state production flow before validating and activating it for production. Existing Kanbans from old production flow versions are automatically related to the new version to make sure a seamless material flow on the transition date and beyond.
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
NOTE: An operating unit can be configured to be used as a financial dimension. A production group.
NOTE: The production group defines the set of accounts that are used for the financial postings that are related to the production flow. The most important accounts are the WIP and Offset accounts. These are the basis of the variance calculation for the production flow. The setting of the financial dimension for the production flow is optional. TIP: For more information about lean manufacturing, refer to the following two whitepapers. Lean manufacturing - kanban and pull-based manufacturing (http://go.microsoft.com/fwlink/?LinkId=238243) Lean Manufacturing Production flows and activities (http://go.microsoft.com/fwlink/?LinkId=238244) Additionally, you can refer to the Lean Manufacturing for Microsoft Dynamics AX 2012 course.
Process Industries
Process Manufacturing for Microsoft Dynamics AX 2012 supports a range of manufacturing processes. This includes make to order, make to stock, and mixed mode. Mixed mode is a hybrid environment that enables discrete, lean, and process requirements to coexist. You can integrate production processes to build a flexible solution that meets your needs.
Overview
Process industry requirements are reflected in the following Microsoft Dynamics AX 2012 functionalities. Integration with the Manufacturing execution system Integration with Warehouse Management Systems II (WMSII)
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-37
Some features can be used with any license of Microsoft Dynamics AX2012, while other features can be used only with a Process Manufacturing installation. The two installations for Process Manufacturing include the following. Process Manufacturing Logistics: The Process Manufacturing Logistics installation contains all production and manufacturing functionality. Process Manufacturing Distribution: The Process Manufacturing Distribution installation contains all inventory distribution functionality.
If your organization wants to use the Process Manufacturing solution, you must implement one or both of the Process Manufacturing installations.
10-38
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
Challenge Yourself!
Use the following tables, maps, and forms to create a new field for Victor to track returnable items at the BOM line level. BOM table ProdBOM table ProdBOM form BOMConsistOf form BOMMap
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-39
Step by Step
1. Open the Development Workspace. 2. In the AOT window, expand the Data Dictionary node and then right-click the Extended Data Types node and select New > Enum. 3. Set the following properties. a. Name = IsReturnable b. Label = Is returnable c. Help text = Item can be returned to the vendor d. Enum Type = NoYes 4. Save the extended data type. If you are prompted to synchronize the database, select Yes. 5. Create a project (View > Project or Ctrl+Shift+P ). 6. Right-click the Shared space, New > Project. 7. Name the project. 8. Open the project. 9. Drag the new IsReturnable extended data type to the project. 10. Find the BOM table in the AOT. 11. Drag BOM table to the project. 12. Expand to the Fields node. 13. Find the ProdBOM table in the AOT. 14. Drag the ProdBOM table to the project. 15. Expand the Fields node. 16. Right-click IsReturnable(usr) and select Open New Window. 17. From the new window drag IsReturnable to the BOM fields and the ProdBOM tables. 18. Close the AOT window with the IsReturn(usr) extended data type. 19. Save the project. 20. In the AOT window, expand the Forms node and locate BOMConsistOf and ProdBom. 21. Drag the forms to the project. 22. Right-click the project and select Restore. 23. Expand the BOMConsistOf form to Data Sources > BOM > Fields > IsReturnable, and then right-click and select Open New Window. 24. Expand the BOMConsistOf form to Designs > Design > [Group:GroupBOM] > [Tab:Tab] > [TabPage:Overview] > [Grid:GridBOM]. 25. Drag IsReturnable to the [Grid:GridBOM].
10-40
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-41
Summary
A bill of material is a complete list of all the components, parts, raw materials, assemblies and their quantities that are required to make a finished product. The BOM Version identifies which BOM to use for producing an item under specific circumstances. Routes and operations are the path that the item takes from operation to operation, starting with the beginning of the production process and continuing to the end. It is a set of sequential operations, or tasks, that are required to produce an item. Production orders are used to track information about what is to be produced, how much (quantity), and the planned finish date. The system assigns an order status to each step in the life cycle of the order. The status shows where the item is in the production process. Scheduling assigns resources and attempts to schedule the operations on possible dates and times so that the requested date can be met. Planned production orders are created by master planning when requirements are not met by current inventory. A planned production order is issued that specifies what is needed and when. Then the planner knows what is missing and he or she can make decisions about how to meet these requirements. This interacts with the journals for each step for both real time information and auditing purposes. Lean is a both a process philosophy and a workable process methodology. It introduces best practice material handling and best in class manufacturing methods that are now a standard across industries. Microsoft Dynamics AX 2012 integrates the concept of Kanbans and their effect on the production process. You can integrate production processes in Microsoft Dynamics AX 2012 to build a flexible solution that meets your needs by using process industries functionality.
10-42
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-43
2.
3.
10-44
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
Solutions
Test Your Knowledge
1. Which of the following are items that are found on a BOM? (Select all that apply) () Components () Parts () Assemblies () Raw materials 2. Which of the following is not a BOM line type? ( ) Phantom ( ) Pegged ( ) Vendor () Shortest route 3. The applicable resources of an operation in Microsoft Dynamics AX 2012 can be restricted by which new feature? ( ) Operations to perform () Capabilities ( ) Sequence of operations ( ) Customer value 4. Which of the follow is true about Production Orders? Select all that apply. () Meeting sales demand when inventory is insufficient () Creating safety stock based on possible demand ( ) Developing templates for receiving control () Supply the BOM as sub-assemblies to other items in demand
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement
10-45
10-46
Microsoft Official Training Materials for Microsoft Dynamics Your use of this content is subject to your current services agreement