Dynamics AX Manufacturing R&D Team blog https://docs.microsoft.com/archive/blogs/axmfg/feed.xml The blog contains contributions from the AX R&D team on manufacturing covering topics like MRP, discrete, lean, & process manufacturing Thu, 14 Mar 2019 14:48:27 GMT en-US hourly 1 Demand Forecasting: Performance influencers https://docs.microsoft.com/archive/blogs/axmfg/demand-forecasting-performance-influencers Thu, 12 Jul 2018 10:35:51 GMT https://blogs.msdn.microsoft.com/axmfg/?p=2665 Forecast generation in Azure Machine Learning timed out

Number of enabled forecasting dimensions

The Forecasting dimensions are accessible via Demand forecasting parameters form under the Master planning menu, as illustrated below: Enable only the must have forecasting dimensions. If you experience a timeout in the Azure Machine Learning when generating the statistical baseline forecast, one of the first things to consider is, if any of the enabled forecasting dimensions can be disabled.

Number of items in Item allocation keys

The Item allocation key form is accessible under the Master planning menu, as illustrated below:      Each allocation key will currently be executed in isolation on the Azure Machine Learning web service, this implies that the number of items in each allocation key, will have a direct impact on the performance of processing each allocation key. Typically, which items are assigned to which item allocation key is a business decision, however to the extent possible try to keep number of items in each group below 1 thousand or at least in the low thousands.

Historical Horizon

The historical horizon is assigned before running the generation of the statistical baseline forecast.

The size of the historical horizon has a direct impact on the performance of the generation of the statistical forecast. It is worth considering if historical data is representative of what is expected in the future. For example, 3 years of historical data may be available, but in some cases it can be better (result in a more accurate forecast) to use just last year's historical data. It requires insight into the historical data to make this decision but is something that should be considered.

Selecting a single forecast model

As a last resort a single forecast model can be selected, the options are:
  • STL
  • ARIMA
  • ETS
]]> Product Configuration: What's new in 2018 https://docs.microsoft.com/archive/blogs/axmfg/product-configuration-whats-new-in-2018 Wed, 11 Jul 2018 14:49:49 GMT https://blogs.msdn.microsoft.com/axmfg/?p=2565 Performance The Z3 Solver strategy is now available in  Microsoft Dynamics 365 for Finance & Operations. For details on the Z3 Sovler strategy read the dedicated blog post here: LINK

Usability

The configuration dialog can now be configured to have a multi column layout. For details on the multi column layout read the dedicated blog post here: LINK

     ]]> Product Configuration: Performance with Z3 https://docs.microsoft.com/archive/blogs/axmfg/product-configuration-performance-with-z3 Wed, 11 Jul 2018 14:42:51 GMT https://blogs.msdn.microsoft.com/axmfg/?p=2575 Introduction In the spring release of 2018 for Microsoft Dynamics 365 for Finance & Operations a significant investment in improving performance of the constraint evaluation has been made. The result of this investment is the introduction of the Z3 sovler strategy. Z3 is a theorem prover from Microsoft Research, that has won several awards and has an active open source community. The Microsoft Dynamics 365 for Finance & Operations team, teamed up with the Microsoft researches to develop new algorithms targeted at the Product configuration scenarios for Microsoft Dynamics 365 for Finance & Operations.
Microsoft Dynamics AX 2012 R3
The Z3 solver strategy is also available for Microsoft Dynamics AX 2012 R3 with the following KB article numbers: 
  • 4341629 - Additional performance improvement of loading models
  • 4046549 - Performance improvement of loading models
  • 4034024 - Fix to support customization related to system defined table constraints
  • 4012892 - Introduction of the Z3 Solver strategy

Usage

The applied solver strategy for a product configuration model is selected by accessing the Model properties form. From the Model properties form the Z3 solver strategy can be selected as illustrated below: The Z3 solver strategy will currently not have a functional impact, the impact will be on performance.      ]]> Product Configuration: Multi-column dialog layout https://docs.microsoft.com/archive/blogs/axmfg/product-configuration-multi-column-dialog-layout Wed, 11 Jul 2018 14:11:05 GMT https://blogs.msdn.microsoft.com/axmfg/?p=2585 Model properties form. In the Model properties form, there is now a new field Maximum number of columns. This field allows you to specify how many columns should be used display the attribute groups of each component of the selected product configuration model. Now, when the model is loaded in the configuration dialog in Test or via any of the order forms (Sales, Purchase etc.) it will look like this: With this feature more of the user interface real estate is being put to use, to providing a better overview of the attributes of the selected component.   I hope you find this useful    ]]> New Flushing principle https://docs.microsoft.com/archive/blogs/axmfg/new-flushing-principle Tue, 17 Oct 2017 10:56:59 GMT https://blogs.msdn.microsoft.com/axmfg/?p=2525 This blog post describes a new flushing principle Available at location that was introduced in Dynamics 365 for finance and operations, Enterprise edition for the spring release 2017.

The flushing principles reflect different consumption strategies for raw materials that are used in production processes. Consumption is the process that deducts material from the on-hand inventory and sets the value of the consumed materials to Work in progress (WIP) for production orders and batch orders. Raw materials are usually consumed from a location that is configured for the process that consumes the material. This location is known as the production input location. Material consumption for production and batch orders is accounted for in the Production picking list journal.

Flushing principle available at location

The Available at location flushing principle indicates that the material will be automatically consumed when it's registered as picked for production. The material is registered as picked from location when work for the raw material picking is completed, or when material is available on the production input location and the material line is released to the warehouse. The picking list that is generated during the process is posted in a batch job. This principle is relevant if, for example, you have many picking activities against one production order. In this case, you don't have to update the picking list manually, and you can get a current view of the WIP balance. Let's walk through some simple scenarios that shows how the new flushing principle works. In the following example we will be using product L0101 from the USMF demo data.
  1. Go to the BOM version for L0101 and remove product L0100 and M9204, so the resulting bill of material looks like below.
2. Go to the details for the line item for M9203 and change the flushing principle to “Available at location” 3. Create a production order for L0101 with the default quantity 20. 4. Estimate and Release the production order a. Verify that work has been created for M9203 5. Start the production order with the below setting Note: When starting the production order, no picking list was created. This is because no material has yet been made available on the production input location by completion of warehouse work. 6. Process the warehouse work with the help of the hand-held device 7. After completing the work, go to the picking list of the production order Note: Because the bom line has the flushing principle Available at location the picking list journal was automatically created when the pick work was completed. The posting of the picking list is inserted into a batch job, and that is why it can appear as not posted when opened just after the work is completed. After a couple of minutes after work completion the picking list will be posted by the batch job. 8. Create a new production order for L0101 9. Estimate and Release the order Note: No work was created, because M9203 is available at the production input location, because we staged the full quantity of the license plate (200 pcs) when we processed the work for the first production order and we only consumed 20 pcs, so 180 pcs are remaining. 10. Start the production order with Auto BOM Consumption = Flushing principle Note: A production picking list was created and posted. When material is already available at the production input location, the flushing principle “Available at location” has the same behavior as the flushing principle “Start”.]]> System requirements and Sales solution setup for Prospect to Cash Integration between Microsoft Dynamics 365 for Sales and for Finance and Operations, Enterprise Edition https://docs.microsoft.com/archive/blogs/axmfg/prospecttocashintegrationrequirements Thu, 03 Aug 2017 13:46:47 GMT https://blogs.msdn.microsoft.com/axmfg/?p=2466
  • Information about Data integrator
  • Information about Prospect to cash templates
    •   Prospect to cash integration - System requirements:

    Dynamics 365 for Finance and Operations, Enterprise Edition

    Dynamics 365 for Sales, Enterprise Edition

    • Solution was developed for Microsoft Dynamics 365 for Sales Version 1612 (8.2.1.207) (DB 8.2.1.207) online
    • Use Prospect to Cash Solution for Sales, version 1.14.0.0 or later
    Install the Prospect to Cash Solution for Sales
    • Download the P2C CRM Solution Package Deployer zip - DOWNLOAD: from CustomerSource
    • Make sure that the zip file is unblocked (right click on zip file > properties > Unblocked) - otherwise you might get the error 'No import packages were found.' when running the PackageDeployer.
    • Unzip and run PackageDeployer.exe
    • Install the Prospect to Cash Integration Solution into your own Sales instance.
    1. Choose Deployment type: Office 365
    2. Choose Show advanced
    3. Select the region (fast) or select Don’t know (it will search in all regions – takes a little longer)
    4. Enter User name and Password for an admin user with privilege to install solution on the target Sales instance.
      Christian Rytt]]>         Using the Withdrawal kanban for raw material replenishment https://docs.microsoft.com/archive/blogs/axmfg/using-the-withdrawal-kanban-for-raw-material-replenishment Tue, 11 Jul 2017 14:10:50 GMT https://blogs.msdn.microsoft.com/axmfg/?p=2205
  • Enable the user to configure warehouse processes for raw material picking for the withdrawal Kanban with the help of work templates and location directives.
  • Enable the user to process work for raw material picking for the withdrawal Kanban with the hand-held device
  • Enable the user to process an Empty Kanban signal with the hand-held device
  • Provide the user a status of wave and work in the Picking list section in the Kanban transfer board.
  • Enable the user to configure the Kanban transfer activity of the withdrawal Kanban to be automatic completed, when the Kanban pick work is completed.
    • In the following section, it is described in detail how a withdrawal Kanban is set up for material replenishment, for material that is managed on a warehouse for advanced warehouse processes. Scenario A withdrawal Kanban is set up to transfer material L0100 between locations in warehouse 51 to a production input location 001 in warehouse 61. When a new Kanban is created, the Kanban is automatically released to a wave in warehouse 51. When the wave is processed, warehouse work for Kanban picking is generated, directing the warehouse worker to pick L0100 on a location in warehouse 51 and put it to the TrFrom51 location. The Withdrawal Kanban is now ready to be completed. In the Complete step the material is transferred from location TrFrom51 in warehouse 51 to the production input location 001 in warehouse 61. Prepare the demo Use company USMF Create production input location PIL-01 in warehouse 61. Add on-hand inventory for item L0100 in warehouse 51. Create a new Lean production flow for transferring L0100 from warehouse 51 to warehouse 61.   Define transfer activity (Click: Activities -> Create a new activity plan -> Follow the wizzard)   Activate the flow (Click: Activate) Create a Kanban rule for L0100
    • Type: Withdrawal
    • Replenishment strategy: Fixed
    • First plan activity: Transfer 51 to 61
    • Product: L0100
    • Default quantity: 1
    • Fixed Kanban quantity: 2
    Check location directive for Kanban picking Note: The two types of kanbans Manufacturing Kanban and Withdrawal Kanban shares the same location directive and work template. If separate processes for the two types of kanbans is required, then the configuration can be separated in the queries for work templates and location directive by filtering on the Kanban activity type (Transfer or process). Demo From the Kanban rule create two new Withdrawal kanbans for L0100 Note: After the Kanban’s are created, you can see from the message details that the Kanban’s have been released to a wave and warehouse work has been created. Go to the Kanban board for transfer jobs to see the details for the two Withdrawal kanbans. Filter on the production flow created for this scenario Look in the Work details (Tab: Transfer-> Group: Warehouse -> Work details) Work of type Kanban picking has been generated to transfer from the bulk location to the transfer location TrFrom51. Tak a note of the Work-ID that you should use later, when you process the pick work on the hand-held device. Go to the Picking list section in the Kanban board for transfer jobs Note: In the picking list section, you can see from the Item pegging status, that Work has been created but not yet processed. Use the hand-held device to process the pick work for one of the Kanban’s Go back to the Kanban board and look at the item pegging status in the Pick list section Note: The status has changed from Work created to Inventory. From the Kanban board complete the Kanban by selecting the Complete button L0100 is now transferred to the production input location and is ready to be consumed. Kanban empty signal The signal to replenish L0100 can now be given with an empty scan. The empty scan indicates that a Kanban has been consumed at the production location and is now empty. The empty signal can be configured to happen either automatically when a Kanban is completed or as a manual registration. This is set up in the field Register as empty in the Kanban rule (Section: Kanban rule -> Group: Material handling unit -> Register empty). Make sure the Manual (includes scanning empty) option is selected on the Kanban rule for L0100. The Manual empty signal can be done from the Kanban transfer board, but there is also an option to make the make the empty signal on the mobile device. Here is how to configure the empty signal for the hand-held device. First create a new Mobile device menu item with the below settings: Add the new menu item to a mobile menu, for example the menu for Production. As the material L0100 is now in warehouse 61, we need to change warehouse to 61 on the mobile device. This is done by granting the warehouse worker in warehouse 51 access to also work in warehouse 61 in the Work users page Select Warehouses in the action pane Go to the mobile menu and select Change Warehouse Select the Empty scan option in the mobile menu     Going back to the Kanban board for transfer job, you can see the new Kanban that was created by the empty signal Option to auto-complete the Withdrawal Kanban when completing pick work There is also an option to setup the transfer activity for the withdrawal Kanban to auto-complete when the put transaction for the Kanban pick work is completed. This option can for example be used if the warehouse worker, who picks the material in warehouse 51, also delivers the material to the production input location on warehouse 61. With this option the hand-held work flow for Kanban picking is first directing the worker to pick-up the material from the pick location in warehouse 51 and then directing him to deliver the material to the put location in warehouse 61. The warehouse worker will not notice that the Withdrawal kanban is automatically completed, when the put transaction is completed. Go to the definition of the transfer activity in the production flow and select the Auto complete by put option. Go to the Kanban board for transfer job and find one of the un-processed Kanban's Open the Work details and note the Work-id Process the work from the hand-held device (user should be in warehouse 51) Note: From this flow you can see how the user is directed to put L0100 to warehouse 61 on location PIL-01. Go to the Kanban board for transfer jobs and verify that the Kanban is completed ]]>         Cross docking from production orders to transfer orders https://docs.microsoft.com/archive/blogs/axmfg/cross-docking-from-production-orders-to-transfer-orders Mon, 13 Feb 2017 22:58:19 GMT https://blogs.msdn.microsoft.com/axmfg/?p=1475 Finished goods put away type is usually created to guide the warehouse worker to pick the goods from the production output location and put to a location that is determined by the location directive for Finished goods put away. This feature enables a process where, during the process of reporting goods as finished, the system looks for an opportunity to cross-dock the goods to the bay door locations where there is transfer order demand. From a system perspective, the cross-docking opportunity is a transfer order that is released to the warehouse. This transfer order represents the transportation between the manufacturing plant and a distribution center. If a released transfer order exists, the system generates work of the Transfer issue type instead of the Finished goods put away type. This work suggests that the warehouse worker pick from the production output location and put to a location that is determined by the Transfer issue location directive for the Put work order type. The following illustration shows this process. scenario In the preceding illustration, the truck driver picks up the pallet at the end of the production line. If a released transfer order exists, the system directs the forklift driver to the bay door location. If there is no demand at the bay door, the system directs the truck driver to a location in the warehouse. How to configure cross docking You configure the cross-docking process in work policies. A work policy includes a work order type, a location, and a product. In the following example, cross-docking is configured for product X and location Y. Work order types
    • Work order type: Finished goods put way
    • Work creation method: Cross docking
    • Cross docking policy name: Transfer orders
    Inventory locations
    • Warehouse: 51
    • Location: Y
    Products
    • Item number: X
    Currently, cross-docking can be configured for only two work order types:
    • Finished goods put away
    • Co-product and by-product put away
    In the cross-docking policy, you define which document types are applicable for cross-docking. Currently, the only document type that is supported is Transfer orders . The following example shows the configuration of a cross-docking policy. Cross docking policy name: Transfer order
    • Sequence number: 10
    • Work order type: Transfer issue
    • Cross docking demand requires location: False
    • Cross docking strategy: Date and time
    The sequence number indicates the priority of the document type. Currently, Transfer issue is the only type that is supported. Therefore, the sequence number will become relevant only when more work order types are supported. The cross-docking policy also sets the policy for the prioritization of transfer order demand. For example, if multiple transfer orders exist for the same product, the scheduled date and time that are set on the load and associated with the transfer order determine the prioritization between the orders. The scheduled date and time can be set directly on the load, or they can be set on an appointment schedule that is associated with the load. The prioritization is determined by the cross-docking strategy. Currently, there is only one strategy: Date and time. In the cross-docking policy, you can set up a criterion to require that transfer orders have an assigned location in order to be eligible for cross-docking. This criterion is set in the Cross docking demand requires location field. In this case, the location on the appointment schedule that is associated with the load is used as the final location for the goods that are being cross-docked. If the Cross docking demand requires location field isn’t set, the transfer order can be eligible for cross-docking even if a location isn’t set on the appointment schedule. In this case, the final location for the goods that are being cross-docked is determined by the location directive for Transfer issue for the Put work order type. You might find it useful to set the Cross docking demand requires location field in a scenario where the finished goods should be cross-docked only if a trailer is assigned to a bay door. In this scenario, the goods are moved directly from the production line into the trailer. When a trailer is assigned to the bay door, a user will assign the location to the appointment schedule and will therefore make the location applicable for cross-docking. The following sections walk you through two examples. Scenario 1 – Cross-docking to bay door locations Finished good L0101 is reported as finished to production output location PRODRECV in warehouse 51. Transfer orders for L0101 are set up to manage transportation between location BAYDOOR in warehouse 51 and a receipt location in warehouse 61. If a released transfer order for L0101 exists, the product should be cross-docked to the BAYDOOR location when the product is reported as finished. Scenario 2- Cross-docking to a bay door location assigned a trailer Finished good L0101 is reported as finished to production output location PRODRECV in warehouse 51. Transfer orders for L0101 are set up to manage transportation between location BAYDOOR in warehouse 51 and a receipt location in warehouse 61. If a released transfer order exists for L0101, the product should be cross-docked to the BAYDOOR location when the product is reported as finished.

    Scenario 1 – Cross docking to bay door locations

    Use company USMF. 2. Enable a new number sequence for cross-docking Go to the Number sequences page, and select the Generate button. A wizard will guide you through the process. wizzard 2. Create a Cross docking policy Go to the Cross docking policy page, and create a new policy that is named Cross docking to transfer order. crossdockpolicy Note that the only work order type that you can select is Transfer issue, and the only cross-docking strategy that is available is Date and time. 3. Create a Work policy Go to the Work policies page, and create a new work policy that is named Cross Dock L0101. workpolicy 4. Set up loads so that they are created automatically for transfer orders. In the warehouse parameters, set up loads so that they are created automatically when transfer orders are created. A load is a prerequisite for making the transfer order eligible for cross-docking. warehouse-parameter-auto-load 5. Set up the item load mapping. Go to the Item load mapping page, and set up a standard load template for the CarAudio item group. This mapping will automatically insert the load template on the load when the transfer order is created. itemloadmapping 6. Create a transfer order Create a Transfer order for item number L0101 transferorder2 7. Release the transfer order from the Load planning workbench On the Ship tab, select the menu item for the Load planning workbench. releaseload1 Release the transfer order from the load by selecting Release to warehouse on the Release menu on the load line. releasemenu1 releaseinfo1 An open wave line of type Transfer issue now exists for the transfer order. 8. Create a production order Go to the production order list page, and create a production order for product L0101. prodorder2 Estimate and start the production order by using the settings in the following screenshot. Note that the Post picking list now field remains set to No. start1 9. Report as finished from the mobile device Go to the mobile device portal and select menu item: Report as finished and put away. Now report as finished L0101 from the hand held device. raf_flow1 Note that the put location is BAYDOOR. This location is found from the Transfer issue location directive for the Put work order type. locdirective Also notice that work of type Transfer issue has been created and completed. Go to the transfer order Work details to verify the work. workdetails Now try to start 20 pieces more on the production order start2 Now try to report 20 ea as finished by using the handheld device. raf_flow2 This time, location LP-001 is suggested as the put location. This location is found from the location directive for Finished goods put away. This location directive is being used, because no opportunity for cross-docking exists. The transfer order for LP-001 was completely fulfilled by the first cross-docking activity. Work of type Finished goods put away was created and processed rafwork

    Scenario 2- Cross-docking to a bay door location assigned a trailer

    Use company USMF. 1. Change Cross-docking policy Change the cross-docking policy that you created in scenario 1 by selecting the Cross docking demand requires location check box. crossdockpolicy2 2. Create a new transfer order Create a transfer order, and go to the Load planning workbench. transferorder3 Open the Load planning workbench. loadplanworkbench2 3. Create an Appointment schedule. From the Load planning workbench, go to the Loads section, and select Appointment schedule on the Transportation menu. Create a new appointment schedule. Note that the appointment schedule has a reference to the transfer order in the Order number field. In the Planned start date/time at location field, you can set the date and time for the appointment. This date and time will be used when cross-docking demand is prioritized during the cross-docking process. The date and time that you set in this field will update the Scheduled load shipping date and time field on the corresponding load. The location on the Shipping details FastTab determines the location that the transfer order is shipped on. appointmentschedule Back on the Load planning workbench release to the warehouse releaseload2 4. Create a production order Create a production order for item number L0101, and set it in status Started, as you did in scenario 1. createprod2 5. Report as finished from the mobile device Go to the mobile device portal, and select the Report as finished and put away menu item. Now report item L0101 as finished from the handheld device. raf_flow3 Note that the put location is now BAYDOOR 2. This location is found from the appointment schedule instead of the Transfer receipt location directive. Flow diagram The flow is explained in below flow chart diagram: flow-diagram Additional information
    • The cross docking scenario is supported for batch and serial controlled items, both with the batch and serial number dimensions defined above and below location, in the reservation hierarchy.
    • The quantity that is being reported as finished cannot be split to a transfer order demand that is lower. If, for example, 20 pieces is being reported as finished and a transfer order exist for 5 pieces, then the transfer order will not be found applicable for cross docking.
    ]]>         Using the handheld device for reporting serial numbers as finished in production  https://docs.microsoft.com/archive/blogs/axmfg/using-the-handheld-device-for-reporting-serial-numbers-as-finished-in-production Tue, 29 Nov 2016 08:22:42 GMT https://blogs.msdn.microsoft.com/axmfg/?p=1715 Introduction A new flow for the handheld device has been released with KB article: 3148600. This flow enables the user to register the finished good serial number when reporting as finished in production. This flow is targeting a process where the finished good serial number is generated under the following conditions:
    • It is assigned by the system at the time when the production or batch order is created.
    • It is configured to be unique per one single unit of the production order. If, for example, a production order of five pieces is created, five unique serial numbers are created.

    Configuration of the flow

    This section provides information about how the flow is configured. Create a new Mobile device menu item, and name it, for example, Register serial number. In the field Work creation process select Register report as finished by serial number. mobile-device The menu item can be added to a menu, for example, the Production menu, as shown below. mobile-menu

    Use the flow in production

    This section provides information about how the new flow can be used in production.

    Create a finished good

    Create a new finished good that is controlled by serial number. createfg As this is an item enabled for the new warehouse processes, make sure the Number sequence group ID is added the product. Note: This flow is only applicable for a product that is enabled for a managed warehouse. Associate a Serial number group, with this setup, with the released product. numgroup With this setting, a serial number per quantity of the finished good will be created, when the production or batch order is created.

    Create a production order

    Create a production order for the finished product. createprod When the production order is created, open the Transactions form and notice each of five transactions has a serial number assigned.

    transactions

    Estimate and start the production order

    startstate Open the menu for the handheld device and register report as finished for the serial number: 000006. rafflow1 Open the Transactions form again and notice that the serial number has been reported as finished to the inventory. transactions2 Open the Work details form and notice that work of type Finished goods put away has been created. workdetails  ]]>         Using the Work Policy for warehouse processes in production https://docs.microsoft.com/archive/blogs/axmfg/using-the-work-policy-for-warehouse-processes-in-production Wed, 21 Sep 2016 12:05:40 GMT https://blogs.msdn.microsoft.com/axmfg/?p=1346 Scenario In this scenario, we have two production orders; one for painting Comp-1 and one for the assembly of Fg-1. The production order for Comp-1 is reported as finished to the location 001. The production order for Fg-1 is later consuming Comp-1 and Rm-1 from location 001. When the production order for Fg-1 is released, warehouse work for raw material picking is generated to move Rm-1 from the Bulk locations to 001. For this scenario, we can set up following requirements for the warehouse processes:
    • No warehouse work for Finished goods put away should be created when reporting as finished Comp-1 to location 001 because Comp-1 is later consumed on the same location by the Assembly operation.
    • No Work for Raw Material Picking should be generated for Comp-1 when releasing the Assembly operation to the warehouse.
    • Work for Raw material picking should be generated for Rm-1 when releasing the production order for the Assembly operation to the warehouse.
    • It should be possible to define location 001 as non-license plate controlled, as it acts both as a production input location and a production output location (so far it has not been possible to define the production output location as non-license plate controlled).
    The following walkthrough shows how these requirements are supported by the Work Policy. First we will set up a Work policy named NoPickPutAway-001-FG1 as shown below work policy As it can be seen from the figure, the Work policy uses the following three criteria to define work creation:
    • The Work Order Type
    • The Location
    • The Product (selected or all products)
    Above policy will prevent Finished good put away work to be generated when Reporting as finished product Comp-1 to location 001 in warehouse 51. The policy will also prevent Work for raw material picking to be generated when releasing a production order that is consuming product Comp-1 from production input location 001. Location 001 is defined as a non-license plate controlled location. It is pre requisite for defining a non-license plate output location, that a work policy exists for the location that prevents work for Finished goods put-away from being created. Let’s take a closer look at the setup of the products and then how the work policy works in this scenario. Product Comp-1 has a Painting operation which is associated a resource group with output location 001 Resource group The Assembly operation for the production order for FG-1 is consuming the products Comp-1 and RM-1 from the input location 001. The input location is setup on the resource requirements for the Assembly operation resource The active bill of material version for Fg-1 is setup for materials Comp-1 and Rm-1 bom version Now we create a production order for Comp-1 for 20 pieces CreateProdComp-1 The production order is Started ProdStart The production order is Reported as finished from the hand-held device in the below flow RafFlow In this case Comp-1 was reported as finished directly to location 001 and no put-away work was generated because of the Work policy. Now we create a production order for FG-1 ProdCreateFG1 The production order is Estimated and Released ProdRelease Work for raw material picking has been generated for Rm-1, because the Work policy is only preventing work for raw material picking for product Comp-1 to be generated from location 001 WareHouseWork In the first release of the Work policy only the following three Work order types for production are supported
    • Raw material picking
    • Finished goods put away
    • Co-product and by-product put away
    ]]>