Modules:Advanced Warehouse Operations Manufacturing

Introduction

This module Advanced Warehouse Operations for Manufacturing, abreviated as AWO-MFG, is a submodule of Advanced Warehouse Operations focussed on operational improvements for manufacturing. Aside the operational improvements it also contains the link, through webservices, to allow an external planning software to generate Work Requirements with the resulting Work Efforts, Production Runs and Material List.

License:

• Commercial
• Category: Module

Group of Inventory- and Supply Chain Management functionalities

The AWO module has been created in order to enhance Openbravo with the ability to do advanced warehouse operations by configurable warehouse areas and dynamic bin- and inventory determination but all to a simple and effective User Interface.

It is an important part of a set of functionalities that all together bring first class inventory and supply chain capabilities. The complete set is:

• Enhancements in the Supply Chain concerning PLANNING & EXECUTION of INCOMING INVENTORY:
  • (17Q3) Distribution Orders. Integration aspects (configuration & operation) with Advanced Warehouse Operations are covered in this Wiki.
  • FairShare and Push-Planning

• Enhancements in the Supply Chain concerning MANAGEMENT of IN-HOUSE INVENTORY:
  • (16Q4) Advanced Warehouse Operations for Manufacturing
  • (17Q1) Unit of Measure Conversions. Integration aspects (configuration & operation) with Advanced Warehouse Operations are covered in this Wiki.
  • (17Q3) Inventory Status. Integration aspects (configuration & operation) with Advanced Warehouse Operations are covered in this Wiki.
  • (17Q4) Advanced Warehouse Operations, including mobile inventory procedures.
  • (18Q2) Referenced Inventory. Integration aspects (configuration & operation) with Advanced Warehouse Operations are covered in this Wiki.
  • (18Q2) Controlled Attribute Change.

• Enhancements in the Supply Chain concerning PLANNING & EXECUTION of OUTGOING INVENTORY:
  • (17Q3) Distribution Orders. Integration aspects (configuration & operation) with Advanced Warehouse Operations are covered in this Wiki.
  • Vehicle and Transport management

Additional Configuration

Basic setup must be done for produced products as per this wiki.

All configuration is identical and has to follow the same structure as the configuration explained in the wiki for Advanced Warehouse Operations. Given that all configuration related to the warehouse spaces is/should already be covered by the configuration of AWO, here the documentation limits to the exceptions/additions related to manufacturing.

Issue- and Receipts for Work Efforts

The generation and processing of Advanced Warehouse Tasks for the Inventory Transaction Types ISS-WO and RCT-WO is on the Roadmap and can be accelerated if demanded.

Picking for Work Effort

The ITT for this transaction is the "PIK-WE" and should be configured in the Warehopuse Definition window in the back-end with Internal Routings and Algorithms, just like the other ITT.

Specific algorithms use the IssueBin to determine to To-Locator and can be set in the Manufacturing Cost Center as per the image below.

The Issue bin can be predefined in the Manufacturing Cost Center.

The Receipt bin is set in the Production Run.

Global Use

Products that are defined as Global Use in the work effort do not generate AWO picking tasks since these products are supposed to be 'general available' and dont need picking. The purpose of the inclusion of these products is mainly for costing.

Generate Work Requirements through WebServices

Advanced Warehouse Operations for Manufacturing (AWO-MFG) include the possibility to have a third-party software create the Work Requirements (WR) and -optionally- process it and generate the Work Effort (WE), Production Run (PR) and Material List (ML) by the use of WebServices.

The optional Processing of the WR (and subsecuent generation of the WE, PR and ML) is activated by passing a header parameter, called "DoProcess", with true or false.

The webservice returns a response with the number of successfull work requirements created and processed or, in case of errors, each work requirement with the identifier and the error.

Find below the instructions and an example of the message-content: The WebService URL is: http://localhost:8080/openbravo/ws/org.openbravo.warehouse.advancedwarehouseoperations.manufacturing.AddWorkRequirementsWS

• Replace <localhost:8080> by the right server
• Method: PUT
• Parameter in header: DoProcess (not mandatory). It affects every work requirement included.
• Data: XML with a list of work requirements (1 or more)
• Result: Success/Error message with the details.
  • Error processing Work Requirement 10000030 - 13-09-2016: Advanced Warehouse Operations flow is not actived for this organization.
  • Work Requirements created successfully

Bear in mind that all the referenced ID's like the Organization, Client, Processplan, etc, must exist on Openbravo.

The header parameter that will process the WR and generate WE, PE and ML.

Below an example to process 2 work requirements, one of them will generate an error).

Header: DoProcess: true

Data:

• <ob:Openbravo xmlns:ob="http://www.openbravo.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  • <ManufacturingWorkRequirement>
    • <client id="DC97D3D6CB314FEB9F998019F671A63B"/>
    • <organization id="17C777183DAD4DDAA212D176A90DAE7C" entity-name="Organization" identifier="USA East"/>
    • <active>true</active>
    • <creationDate transient="true">2016-09-26T12:44:23.561Z</creationDate>
    • <createdBy transient="true" id="100" entity-name="ADUser" identifier="Openbravo"/>
    • <updated transient="true">2016-09-26T12:44:23.561Z</updated>
    • <updatedBy transient="true" id="100" entity-name="ADUser" identifier="Openbravo"/>
    • <name xsi:nil="true"/>
    • <processPlan id="55BF140AAD8A47BEBA7EE32C25CE96C9" entity-name="ManufacturingProcessPlan" identifier="MTR"/>
    • <quantity>1</quantity>
    • <wRCreationDate>2016-09-26T00:00:00.0Z</wRCreationDate>
    • <startingDate>2016-09-13T00:00:00.0Z</startingDate>
    • <endingDate>2016-09-27T00:00:00.0Z</endingDate>
    • <closed>false</closed>
    • <documentNo>10000031</documentNo>
    • <insertProductsAndorPhases>false</insertProductsAndorPhases>
    • <processed>false</processed>
    • <includePhasesWhenInserting>true</includePhasesWhenInserting>
    • <processQuantity>0</processQuantity>
    • <processUnit xsi:nil="true"/>
    • <conversionRate xsi:nil="true"/>
    • <estimatedTime>0</estimatedTime>
    • <runTime>0</runTime>
    • <documentType xsi:nil="true"/>
    • <createworkrequirement>false</createworkrequirement>
    • <closedStat>false</closedStat>
    • <manufacturingWorkRequirementOperationList/>
  • </ManufacturingWorkRequirement>
  • <ManufacturingWorkRequirement>
    • <client id="DC97D3D6CB314FEB9F998019F671A63B"/>
    • <organization id="498D09231B83485B98E53976B1C81D2A" entity-name="Organization" identifier="USA East"/>
    • <active>true</active>
    • <creationDate transient="true">2016-09-26T12:44:23.561Z</creationDate>
    • <createdBy transient="true" id="100" entity-name="ADUser" ***identifier="Openbravo"/>
    • <updated transient="true">2016-09-26T12:44:23.561Z</updated>
    • <updatedBy transient="true" id="100" entity-name="ADUser" identifier="Openbravo"/>
    • <name xsi:nil="true"/>
    • <processPlan id="55BF140AAD8A47BEBA7EE32C25CE96C9" entity-name="ManufacturingProcessPlan" identifier="MTR"/>
    • <quantity>1</quantity>
    • <wRCreationDate>2016-09-26T00:00:00.0Z</wRCreationDate>
    • <startingDate>2016-09-13T00:00:00.0Z</startingDate>
    • <endingDate>2016-09-27T00:00:00.0Z</endingDate>
    • <closed>false</closed>
    • <documentNo>10000031</documentNo>
    • <insertProductsAndorPhases>false</insertProductsAndorPhases>
    • <processed>false</processed>
    • <includePhasesWhenInserting>true</includePhasesWhenInserting>
    • <processQuantity>0</processQuantity>
    • <processUnit xsi:nil="true"/>
    • <conversionRate xsi:nil="true"/>
    • <estimatedTime>0</estimatedTime>
    • <runTime>0</runTime>
    • <documentType xsi:nil="true"/>
    • <createworkrequirement>false</createworkrequirement>
    • <closedStat>false</closedStat>
    • <manufacturingWorkRequirementOperationList/>
  • </ManufacturingWorkRequirement>
• </ob:Openbravo>

Result:

• Error processing Work Requirement 10000031 - 13-09-2016: The Organization Information for USA West is not found. Please define it at Organization | Information window.
• 1 Work Requirement(s) created successfully

Operations

The typical life-cycle of the Work Effort is the following:

1. Window Create Work Requirement
   1. Button Process Work Requirement will set it ready.
   2. Button Generate Work Effort will apply the standard Manufacturing Process / BOM and create the Work Effort and Production Run for a specified date.
2. Window Production Run
   1. Button Reservation Tasks will create the material list and generate Tasks for any not previously reserved quantity of the Material List and given availability of stock.
   2. Button Picking Tasks will convert reservation tasks to picking tasks and create additional picking tasks for any not previously reserved/picked quantity of the Material List and given availability of stock.
   3. Button Create Products will create the content of the tab "Products" with input from the material list in order to prefill the (mandatory) attributes of the P+
   4. Button Backflush will issue the P- components and receive the P+ finished product.

Production Reference

The field Production Reference is a free-format field that can be used to identify the work efforts and production runs. It is editeed on the Work Effort and visible on the Production Run. It is also used to search from the Front-End the proper Production Run to pick or receive (backflush).

The Production Reference can be used to easily identity the works.

Window Production Run

The window for Production Run has been enhanced to serve as the centre of operations. From this window it is possible to initiate processes and view the status and progress of the reservations and pickings.

The Production Run window with the enhanced capabilities as centre of manufacturing operations.

Monitor Picking progress in the Back-End

Both (calculated) fields are part of the AWO-for-Manufacturing functionality.

• PR-header (Production Run) "Incomplete Pickings": This flag counts the number of Material-List lines that are not fully picked, so those with Incomplete Quantity > 0.
• PR-details (Material-List) "Incomplete Quantity": This flag indicates the quantity that is not yet picked for this specific material-list line.

Both columns show incompleteness: Either consolidated for incomplete Material List lines, or for incomplete quantity within the Material List line.

Picking for WE from the Back-end

Multiple Production Runs can be selected at the same time and, if they are not processed and not fully picked, will generate tasks. The tasks can have two different status, depending the button that was prssed:

• TaskStatus "Available" if the button Picking Tasks was pressed. These tasks can be assigned to an operator and confirmed. If there are Tasks of Status "Reserved" for this Production Run then these will be converted to Tasks with status "Available".
• TaskStatus "Reserved" if the button Reservation Tasks was pressed. These tasks cannot be assigned to an operator and cannot be confirmed. These tasks have the purpose to reserve specific Storage details with specific attribute set values.

Initiating the reservation or picking for the selected Production Run(s) will generate Tasks for all components (P-) previously not reserved/picked.

Picking for WE from the Front-end

Production Runs that are not processed and have still quantity open to pick can be selected from the front-end. They can also be searched using the Production Reference field.

Searching the Production Run that can be picked by using the Production Reference as search key.

Receipts (and Backflush) for WE from the Front-end

The purpose of having the Receipt transaction on the Front-end is to facilitate easy and straight-forward operations. For that reason, the Receipt from the front-end will execute the backflush (the issue of components (P-)) and the receipt of the finished product (P+). Prior to this, the P+ has to receive the attribute values and that can only be done in the Product tab of the Production Run in the back-end. If the P+ does not require a mandatory attribute, the Receipt can be fully done from the Front-end.

Searching the Production Run that can be received by using the Production Reference as search key.