Aligned Solutions Consulting - Blog #EpicorAligned Solutions Consulting - Blog #Epicorhttps://getaligned.zohosites.com/blogs/tag/EpicorWed, 24 Dec 2025 07:04:57 -0800http://zoho.com/sites/<![CDATA[Change Issue Material From Whse/Bin Defaults To Use Backflush Hierarchy Logic]]>https://getaligned.zohosites.com/blogs/post/change-issue-material-from-whsebin-defaults-to-use-backflush-hierarchy-logic

Recently (Summer 2016) with the help of Craig Moore at Viridian Systems Consulting we were able to construct a BPM that would change the default From Warehouse and Bin when using the Issue Material program in Epicor 10.  Instead of defaulting to the Part's primary bin logic it made more sense to leverage the Epicor Backflush hierarchy to determine the default warehouse & bin when issuing materials.  I think this can give a greater sense of consistency for material handlers who in some cases were getting confused with where to transfer inventory since some materials were backflushed and others were not. I think it is very important for BPM's to be driven by dynamic data and not static values embedded in the BPM.  This gives end users more control over how a BPM behaves instead of fighting a static override.  By following the default Epicor backflush logic as well as providing a few other overrides options in Resource Group setup we were able to accomplish this dynamic and 'smart' behavior.  Here is how we did it.

Basic Requirements:

When the Issue Qty is updated in the Issue Material program, use the Epicor backflush logic, plus some Resource Group override logic to determine and set the From Warehouse & Bin.

Hierarchy Detail:

First Determine the Labor Reporting Resource.  This is the tricky step since an unscheduled job (which does happen) would not have a Resource defined.  This means we first need to check the Job Material's related Operation's "Production Labor Reporting Resource". This "Resource" (JobOprDtl) record has fields for both Resource Group and Resource, of which both are not required to be defined so we select whichever is more specific.  This means if the Resource is defined, we use that, if not, we must use the Resource Group.  This means that depending on which we use the processed hierarchy will change. If the Resource Group is used then 1, 4, 6, 7, 8 is processed.  If the Resource is used then 2, 3, 5, 6, 7 ,8 is processed.

1. Job Materials related Operation's Resource Group Input Warehouse & Bin, if adequate inventory.

2.  Job Operation's Resource Group Input Warehouse & Bin, no matter the inventory, IF Job Operation's Resource Get Default         Whse From Group (Resource.GetDefaultWhseFromGroup) = TRUE. (this field is hidden by default, but you can view it in         the list view with a personalization). This is the override step so if we need the Resource Group settings to be used no         matter which Resource is used we can, this is handy when multiple resources pull from the same whse/bin.

3.  Job Operation's Resource Input Warehouse & Bin, if adequate inventory.

4.  Job Operation's Resource Group Backflush Warehouse and Bin, if adequate inventory.

5.  Job Operation's Resource Backflush Warehouse and Bin, if adequate inventory.

6.  Job Material's Warehouse Primary Bin, if adequate inventory.

7.  Job Material's Warehouse First Bin, with adequate inventory.

8.  Job Material's Warehouse first bin no matter the inventory.

    BPM Construction:

    We identified the "IssueReturn.OnChangeTranQty" as the method to be used and we created a Post-Processing directive.  Since this object is used for both issue and return transactions, we first use a Query Condition widget to check the TranType to make sure it's "STK-MTL."  If it is, we call some C# code to determine the warehouse and bin:

    bool FoundIt = false; string FoundBin = string.Empty; string FoundWhse = string.Empty; string vResourceID = string.Empty; string vResourceGroupID = string.Empty; string vCompany = string.Empty; Erp.Tables.JobMtl JobMtl; Erp.Tables.JobOpDtl JobOpDtl; Erp.Tables.ResourceGroup ResourceGroup; Erp.Tables.Resource Resource; Erp.Tables.Resource Resource0; Erp.Tables.PartBin PartBin; Erp.Tables.PartBin PartBin2; Erp.Tables.PartBin PartBin3; Erp.Tables.PartBin PartBin4; Erp.Tables.PlantWhse PlantWhse; Erp.Tables.PartBin PartBin5; Erp.Tables.PartBin PartBin6; Erp.Tables.PartBin PartBin7; Erp.Tables.WhseBin WhseBin; Erp.Tables.Warehse Warehse; Erp.Tables.JobOper JobOper; vCompany = Session.CompanyID; foreach (var ttIssueReturn_xRow in ttIssueReturn) { var ttIssueReturnRow = ttIssueReturn_xRow; foreach (var JobMtl_iterator in (from JobMtl_Row in Db.JobMtl where JobMtl_Row.Company == ttIssueReturn_xRow.Company && JobMtl_Row.JobNum == ttIssueReturn_xRow.ToJobNum && JobMtl_Row.AssemblySeq == ttIssueReturn_xRow.ToAssemblySeq && JobMtl_Row.MtlSeq == ttIssueReturn_xRow.ToJobSeq select JobMtl_Row)) { JobMtl = JobMtl_iterator; foreach (var JobOper_iterator in (from JobOper_Row in Db.JobOper where string.Compare(JobOper_Row.Company, JobMtl.Company, true) == 0 && string.Compare(JobOper_Row.JobNum, JobMtl.JobNum, true) == 0 && JobOper_Row.AssemblySeq == JobMtl.AssemblySeq && JobOper_Row.OprSeq == JobMtl.RelatedOperation select JobOper_Row)) { //determine proper ResourceID and ResourceGroupID JobOper = JobOper_iterator; foreach (var JobOpDtl_iterator in (from JobOpDtl_Row in Db.JobOpDtl where string.Compare(JobOpDtl_Row.Company, JobOper.Company, true) == 0 && string.Compare(JobOpDtl_Row.JobNum, JobOper.JobNum, true) == 0 && JobOpDtl_Row.AssemblySeq == JobOper.AssemblySeq && JobOpDtl_Row.OprSeq == JobOper.OprSeq && JobOpDtl_Row.OpDtlSeq == JobOper.PrimaryProdOpDtl select JobOpDtl_Row)) { JobOpDtl = JobOpDtl_iterator; if (JobOpDtl.ResourceID == "") { vResourceGroupID = JobOpDtl.ResourceGrpID; } if (JobOpDtl.ResourceID != "") { vResourceID = JobOpDtl.ResourceID; foreach (var Resource_iterator in (from Resource_Row in Db.Resource where string.Compare(Resource_Row.Company, JobOpDtl.Company, true) == 0 && string.Compare(Resource_Row.ResourceID, JobOpDtl.ResourceID, true) == 0 && Resource_Row.GetDefaultWhseFromGroup == true select Resource_Row)) { Resource0 = Resource_iterator; vResourceGroupID = Resource0.ResourceGrpID; } } } //JobOpDtl //Checking Resource Group Input Bin foreach (var ResourceGroup_iterator in (from ResourceGroup_Row in Db.ResourceGroup where string.Compare(ResourceGroup_Row.Company, vCompany, true) == 0 && string.Compare(ResourceGroup_Row.ResourceGrpID, vResourceGroupID, true) == 0 select ResourceGroup_Row)) { ResourceGroup = ResourceGroup_iterator; foreach (var PartBin_iterator in (from PartBin_Row in Db.PartBin where string.Compare(PartBin_Row.Company, ResourceGroup.Company, true) == 0 && string.Compare(PartBin_Row.PartNum, JobMtl.PartNum, true) == 0 && string.Compare(PartBin_Row.WarehouseCode, ResourceGroup.InputWhse, true) == 0 && string.Compare(PartBin_Row.BinNum, ResourceGroup.InputBinNum, true) == 0 select PartBin_Row)) { PartBin = PartBin_iterator; if (ttIssueReturn_xRow.TranQty <= PartBin.OnhandQty) { FoundIt=true; FoundBin=PartBin.BinNum; FoundWhse=PartBin.WarehouseCode; } } // 1.5 per RB, use Resource Group input if Resource.GetDefaultWhseFromGroup=True, regardless of inventory foreach (var Resource_iterator in (from Resource_Row in Db.Resource where string.Compare(Resource_Row.Company, vCompany, true)== 0 && string.Compare(Resource_Row.ResourceID, vResourceID, true)== 0 && Resource_Row.GetDefaultWhseFromGroup== true select Resource_Row)) { if (ResourceGroup.InputBinNum !="" && ResourceGroup.InputWhse !="" ) { FoundIt=true; FoundBin=ResourceGroup.InputBinNum; FoundWhse=ResourceGroup.InputWhse; } } //Resource if GetDefault=true } //Res Group Input //Checking Resource Input Bin if (FoundIt== false) { foreach (var Resource_iterator in (from Resource_Row in Db.Resource where string.Compare(Resource_Row.Company, vCompany, true)== 0 && string.Compare(Resource_Row.ResourceID, vResourceID, true)== 0 select Resource_Row)) { Resource=Resource_iterator; foreach (var PartBin_iterator in (from PartBin_Row in Db.PartBin where string.Compare(PartBin_Row.Company, Resource.Company, true)== 0 && string.Compare(PartBin_Row.PartNum, JobMtl.PartNum, true)== 0 && string.Compare(PartBin_Row.WarehouseCode, Resource.InputWhse, true)== 0 && string.Compare(PartBin_Row.BinNum, Resource.InputBinNum, true)== 0 select PartBin_Row)) { PartBin2=PartBin_iterator; if (ttIssueReturn_xRow.TranQty<= PartBin2.OnhandQty) { FoundIt=true; FoundBin=PartBin2.BinNum; FoundWhse=PartBin2.WarehouseCode; } } } } //resource input //Checking Resource Group Backflush Bin if (FoundIt== false) { foreach (var ResourceGroup_iterator in (from ResourceGroup_Row in Db.ResourceGroup where string.Compare(ResourceGroup_Row.Company, vCompany, true)== 0 && string.Compare(ResourceGroup_Row.ResourceGrpID, vResourceGroupID, true)== 0 select ResourceGroup_Row)) { ResourceGroup=ResourceGroup_iterator; foreach (var PartBin_iterator in (from PartBin_Row in Db.PartBin where string.Compare(PartBin_Row.Company, ResourceGroup.Company, true)== 0 && string.Compare(PartBin_Row.PartNum, JobMtl.PartNum, true)== 0 && string.Compare(PartBin_Row.WarehouseCode, ResourceGroup.BackflushWhse, true)== 0 && string.Compare(PartBin_Row.BinNum, ResourceGroup.BackflushBinNum, true)== 0 select PartBin_Row)) { PartBin3=PartBin_iterator; if (ttIssueReturn_xRow.TranQty<= PartBin3.OnhandQty) { FoundIt=true; FoundBin=PartBin3.BinNum; FoundWhse=PartBin3.WarehouseCode; } } } } //Res Group backflush //Checking Resource Backflush Bin if (FoundIt== false) { foreach (var Resource_iterator in (from Resource_Row in Db.Resource where string.Compare(Resource_Row.Company, vCompany, true)== 0 && string.Compare(Resource_Row.ResourceID, vResourceID, true)== 0 select Resource_Row)) { Resource=Resource_iterator; foreach (var PartBin_iterator in (from PartBin_Row in Db.PartBin where string.Compare(PartBin_Row.Company, Resource.Company, true)== 0 && string.Compare(PartBin_Row.PartNum, JobMtl.PartNum, true)== 0 && string.Compare(PartBin_Row.WarehouseCode, Resource.BackflushWhse, true)== 0 && string.Compare(PartBin_Row.BinNum, Resource.BackflushBinNum, true)== 0 select PartBin_Row)) { PartBin4=PartBin_iterator; if (ttIssueReturn_xRow.TranQty<= PartBin4.OnhandQty) { FoundIt=true; FoundBin=PartBin4.BinNum; FoundWhse=PartBin4.WarehouseCode; } } } } //resource backflush } //JobOper //Checking Job Material's Warehouse Primary Bin if (FoundIt== false) { foreach (var PlantWhse_iterator in (from PlantWhse_Row in Db.PlantWhse where string.Compare(PlantWhse_Row.Company, JobMtl.Company, true)== 0 && string.Compare(PlantWhse_Row.PartNum, JobMtl.PartNum, true)== 0 && string.Compare(PlantWhse_Row.Plant, JobMtl.Plant, true)== 0 && string.Compare(PlantWhse_Row.WarehouseCode, JobMtl.WarehouseCode, true)== 0 select PlantWhse_Row)) { PlantWhse=PlantWhse_iterator; foreach (var PartBin_iterator in (from PartBin_Row in Db.PartBin where string.Compare(PartBin_Row.Company, PlantWhse.Company, true)== 0 && string.Compare(PartBin_Row.PartNum, PlantWhse.PartNum, true)== 0 && string.Compare(PartBin_Row.WarehouseCode, PlantWhse.WarehouseCode, true)== 0 && string.Compare(PartBin_Row.BinNum, PlantWhse.PrimBin, true)== 0 select PartBin_Row)) { PartBin5=PartBin_iterator; if (ttIssueReturn_xRow.TranQty<= PartBin5.OnhandQty) { FoundIt=true; FoundBin=PartBin5.BinNum; FoundWhse=PartBin5.WarehouseCode; } } } } // Job Mtl Prim Bin // Checking Job Mtl Whse Bin with enough if (FoundIt== false) { foreach (var PartBin_iterator in (from PartBin_Row in Db.PartBin where string.Compare(PartBin_Row.Company, JobMtl.Company, true)== 0 && string.Compare(PartBin_Row.PartNum, JobMtl.PartNum, true)== 0 && string.Compare(PartBin_Row.WarehouseCode, JobMtl.WarehouseCode, true)== 0 select PartBin_Row)) { PartBin6=PartBin_iterator; if (ttIssueReturn_xRow.TranQty<= PartBin6.OnhandQty && FoundIt== false) // looking for the first bin with enough inventory then ignoring the rest { FoundIt=true; FoundBin=PartBin6.BinNum; FoundWhse=PartBin6.WarehouseCode; } } } //Job Mtl Whse Bin with enough // Using First Job Mtl Whse Bin if (FoundIt== false) { PartBin7=(from PartBin_Row in Db.PartBin where string.Compare(PartBin_Row.Company, JobMtl.Company, true)== 0 && string.Compare(PartBin_Row.PartNum, JobMtl.PartNum, true)== 0 && string.Compare(PartBin_Row.WarehouseCode, JobMtl.WarehouseCode, true)== 0 select PartBin_Row).FirstOrDefault(); if (PartBin7 !=null) // no longer checking for sufficient inventory { FoundIt=true; FoundBin=PartBin7.BinNum; FoundWhse=PartBin7.WarehouseCode; } } //Job Mtl First Whse Bin } //JobMtl // Assigning found bin to transaction row if (FoundIt== true) { WhseBin=(from WhseBin_Row in Db.WhseBin where WhseBin_Row.Company== ttIssueReturnRow.Company && WhseBin_Row.WarehouseCode== FoundWhse && WhseBin_Row.BinNum== FoundBin select WhseBin_Row).FirstOrDefault(); if (WhseBin !=null) { ttIssueReturnRow.FromWarehouseCode=FoundWhse; ttIssueReturnRow.FromBinNum=FoundBin; ttIssueReturnRow.FromBinNumDescription=WhseBin.Description; Warehse=(from Warehse_Row in Db.Warehse where Warehse_Row.Company== ttIssueReturnRow.Company && Warehse_Row.WarehouseCode== FoundWhse select Warehse_Row).FirstOrDefault(); if (Warehse !=null) { ttIssueReturnRow.FromWarehouseCodeDescription=Warehse.Description; } } } } //ttIssueReturn

    We really had to fiddle with the code due to scope creep, so it may not be as efficient if we weren't dodging around learning how things work. This code is provided only as a guide and example and is not provided with any warranty, guarantee nor license, use at your own risk and always test heavily. Solution was deployed in an Epicor ERP 10.0.700.3 environment. C# code is courtesy of Viridian Systems Consulting. 

    If you found this post helpful, be sure to Like, Share & Comment! Need help with your Epicor solution?  Get in touch and let's find the best way to align your business with your software.
    ]]>    Fri, 02 Dec 2016 23:05:25 -0500    <![CDATA[Epicor 101: Grid/List View Tools]]>https://getaligned.zohosites.com/blogs/post/epicor-gridlist-view-tools
    Epicor provides per user (Personalizations) Grid/List View Tools to ease data readability and data analysis in Grid/List Views that are included in each program within the Epicor Application.  The following Grid/List View Tools are covered in this document:
    • Moving  & Adjusting Columns
    • Adding & Hiding Columns
    • Summary Options
    • Group By
    • Column Filters
    • Sorting
    • Split Grids
    • Copy To Excel
    • Save Layouts
    Moving & Adjusting Columns You can adjust the columns into the sequence you need. You can, for example, move the columns you want to see the most towards the left side of the column, so they automatically appear when you first view the grid.
    1. In any Epicor program select a List tab that displays the data in a grid.
    2. moving_columnsTo move any column, click on any column header and drag the column header between other column headers and release the mouse button to ‘drop’ the column in that location.  Arrows are displayed to assist with indicating where the column will be placed if released.
    3. adjusting_coulmnsTo adjust the width of any column:
      1. Click and drag on the column border of a column header you would like to adjust. A resize cursor is displayed to assist with adjusting the column width.
      2. To resize any column width to the maximum width of the data in the column, double click on the boarder of a column header. A resize cursor is displayed to assist with adjusting the column width.
    Add & Remove Columns You can also modify which columns are displayed in the List view.  To do this, you activate Personalization Mode from the Tools Menu. From the Control Properties windows you select the List control and select the columns you wish to show or hide from the Columns drop down.
    1. add_remove_columnsFrom the Tools menu, select Personalization. The Control Properties window displays.
    2. Navigate to the Grid view you wish to add or remove columns from and click on the Grid.  The Control Properties window now displays the properties for the selected grid.
    1. Click in the Columns field to display the Drop-Down Arrow button. The Column Properties window displays.
    2. Click on the Caption column header to sort the grid columns alphabetically.
    3. Using the ‘Hidden’ column select or deselect the columns you wish to hide.
    4. Click outside the Column Properties window to close it.
    5. Click OK. The Control Properties window closes. The grid now displays the personalization changes you made.
    Show Summaries By right-clicking ANYWHERE in the List/Grid View opens the List/Grid View Context Menu. From the List/Grid View Context menu you can enable many of the List/Grid Tools, such as Show Summaries.
    1. show_summariesRight Click ANYWHERE in a List/Grid View to open the List/Grid View Context Menu.
    2. Select ‘Show Summaries’ to enable Summaries.
    3. Now any NUMERICAL value will have a sigma sign; ∑ in the column header. Select the sigma to display and select the Summary function(s) to be performed on that column and select the ‘OK’ button. Summary options include:
    4. Average - This calculates the average value for each record.
      • Count - This displays the number of values that display within a column.
      • Maximum - This is the highest value listed in a column.
      • Minimum - This is the lowest value listed in a column.
      • Sum - This is the total amount of a column.
    5. Scroll to the bottom of the list.
    6. The summaries selected now display the summary values.
    7. The column width may need to be adjusted to view the entire value.
    Show Group By Most List/Grid Views offer Show Group By functionality that allows you to group the records in the list by a specific column.  If you are also using Summaries, each group will also be summarized.
    1. Right Click ANYWHERE in a List/Grid View to open the List/Grid View Context Menu.
    2. Select ‘Show Group By’.
    3. Now above the grid a light grey area appears that says ‘Drag a column header here to group by that column.’
    4. Click and drag the column to be grouped to the area above the grid view. Arrows are displayed to show where the column will be dropped.
    5. Now the rows have collapsed to groups with plus symbols next to each group (+). To view the detail rows of that group select the plus sign.
    6. Nested groups can be achieved by dragging and dropping other columns into the Group By area above the grid.show_group_by
    7. Remove any group by columns by dragging the column from the Group By area into the grid area, anywhere. The column will snap back to it’s original position.
    8. To disable the group by, right click anywhere in the List/Grid View and deselect ‘Show Group By.’
    Show Grid Filters By enabling Show Grid Filters you may then filter the list by any value in any column.  You may also specify a custom filter by selecting ‘(Custom)’
    1. show_grid_filtersRight Click ANYWHERE in a List/Grid View to open the List/Grid View Context Menu.
    2. Select ‘Show Grid Filters.
    3. Now each column header includes a filter symbol’
    4. By clicking on a column’s filter a drop down of all the values in the column.
    5. Select a value from the drop down list to filter the list to only display the rows with that value.
    6. Select ‘(All)’ to display all values for that column.
    7. Grid filters can be applied to multiple columns at the same time, which act as an AND logical operator.
    8. More complex filters can be applied to each column by selecting the ‘(Custom)’ option from the drop down.
    9. The ‘Custom Filter’ window is displayed and a complex filter can be built for each column.custom_filter
    10. To disable all grid filters, Right Click anywhere in the List/Grid view and deselect ‘Show Grid Filters’
    Sorting You may sort by any column by clicking on the column header.
    1. Click the column heading (field) by which you want to sort data.
    2. An up or down arrow displays in the column to indicate if the records are sorted in ascending (up) or descending (down) order. If the records are not sorted in the order you want, click the column heading again to change the sort order.
    3. At any time you may clear the Grid Filter by selecting ‘Clear Grid Filters’ from the Grid Context menu.
    Split Grids If there are numerous records in a grid, you can split the grid into separate grids to minimize scrolling.
    1. split_gridsTo set up a split grid, place your cursor near the top of the vertical scrollbar.
    2. When the cursor changes to a bold horizontal bar at the top of the grid, hold the mouse down and drag it down onto the grid to where you want to split the grid.
    3. At that spot, release the mouse, and the grid splits into two separate grids, each with its own scrollbar.
    4. To split the grid vertically, select the vertical scrollbar instead.
    5. To remove the split grid, drag & drop the grid split back to the original position.
    6. Grids can be split as many times as needed.
    Copy To Excelcopy_to_excelIf further data analysis is required you may copy any grid to Excel by selecting the ‘Copy To Excel’ option from the Grid Context Menu.
    1. Right-click ANYWHERE in the Grid and select ‘Copy To Excel.’
    2. In a few seconds Epicor will Open Excel with the grid data displayed in Excel.
    3. If any Sorts, Group By, Filters or Summaries were applied in the Epicor Grid, those attributes are also copied to Excel as well.
    Save Layouts After making the desired changes to any grid you may save the grid changes as a personalization by selecting ‘Save Layouts’ from the Grid Context Menu. It is recommended that after saving a Grid Layout that you navigate back to the tab you wish the form to open on by default and select ‘Save Layouts’ from the Tools menu.
    • The Grid Save Layout saves the grid layout.
    • The Tools Menu ‘Save Layout’ saves the form & tabs layout.
    1. Right-click ANYWHERE in the Grid and select ‘Save Layouts’
    2. The Grid Layout is now saved to your Epicor Account as a Personalization.
    ]]>    Fri, 03 Jun 2016 20:23:22 -0500    <![CDATA[Epicor Job Auto Receive Hierarchy]]>https://getaligned.zohosites.com/blogs/post/epicor-job-auto-receive-hierarchy
    Following is the hierarchy used for the Auto Receive Into Inventory function. Every part requires that a default warehouse (default comes from the company configuration but can be overridden or added to in the part master). In addition, every warehouse is required to have at least one bin associated with it. Thus, when you set up a part, at the very least it will have the default warehouse associated to it and the warehouse will have the default bin (from the warehouse master) associated to it. For the Job Auto Receive functionality to be triggered the following settings must be set:
    • Resource Group\Resource: The resources that are used as the primary resources on Auto Receive operations the Auto Move checkbox should be enabled. Otherwise when the Auto Receipt is triggered it will only create a Material Queue that would need to be processed by a Material Handler.
    • Job Operation\Method Operation : For the operation that should trigger the Auto Receive the Auto Receive checkbox should be enabled.  It also doesn't hurt to enable the Final Operation checkbox as well, which will tell the job to monitor that Operation's complete qty to determine the Job Complete Qty.
    For each Job that is created for Make To Stock the demand link is for a specified warehouse which is determined by the warehouse that is demanding the Part when MRP generated the Job. The following hierarchy is used for the Job's Part Warehouse from the Make To Stock Demand Link

    1. Part Warehouse Primary Bin

      If a primary bin is designated in the part master/warehouse file, the transaction will take that bin.

    2. Part Warehouse's Single Bin

      If a primary bin is not designated in the part master/warehouse file but one bin is associated to the warehouse for that part, the transaction will take that bin.

    3. Part Warehouse's First Alphanumeric Sorted Bin

      If a primary bin is not designated in the part master/warehouse file and more than one bin is associated to the warehouse for that part, the transaction will take the first one, alpha-numerically, based on the bin ID.

    4. Job Warehouses Bin

      If there are no bins associated to the part master/warehouse file, the transaction will take the first bin from the warehouse master. (with a list of multiple bins, the one at the top of the list is used.)
    If the primary warehouse and bin are changed in the warehouse after the job is created, the auto receive will still go to the original primary WH/Bin on the part since these were the items copied into the Manufacturing to Stock link on the Job Header. This must be updated manually on the job to reflect any changes made on the part master.

    References

    ]]>    Fri, 27 May 2016 16:55:34 -0500    <![CDATA[Epicor Backflush Hierarchy Logic]]>https://getaligned.zohosites.com/blogs/post/epicor-backflush-hierarchy-logic

    A reoccurring question I get often from Production Supervisors, Material Handlers, Inventory Managers & Cost Accountants is why Epicor backflushed from a certain location or pulled inventory negative.  Back in Vantage 8.03 and probably prior the Epicor Hierarchy Logic was a bit of a mystery since it was not documented in the embedded help, however since 9.04 the Backflush Hierarchy is included and can be found under: 


    Inventory Management > Working with Inventory Management > Material Backflushing Hierarchy


     It's a bit wordy so I have summed it up first and then I have included the actual help text:

    1.  Job Operation's Resource Group Input Warehouse & Bin, if adequate inventory.


    2.  Job Operation's Resource Input Warehouse & Bin, if adequate inventory.


    3.  Job Operation's Resource Group Backflush Warehouse & Bin, if adequate inventory.


    4.  Job Operation's Resource Backflush Warehouse & Bin, if adequate inventory.

    5.  Job Material's Warehouse Primary Bin, if adequate inventory.


    6.  Job Material's Warehouse first Bin, with adequate inventory.


    7.  Job Material's Warehouse first bin no matter the inventory.

    Backflush material quantities are reported complete at the job operation level. When the Epicor application performs material backflushing at the job operation level, it uses the following hierarchy to determine how the associated component materials should be backflushed:

    • If the available quantity on hand is greater than zero, it uses the input warehouse/bin (defined in the Input Warehouse and In Bin fields in the Resource Group Maintenance > Resources > Detail sheet) for the resource associated with the job operation.
    • If an inadequate available inventory balance exists in the input warehouse/bin defined in the Resource Group Maintenance > Resources > Detail sheet (or none has been defined), it uses the input warehouse/bin defined in the Input Warehouse and In Bin fields in Resource Group Maintenance for the resource group associated with the job operation (if the available quantity on hand is greater than zero).
    • If an inadequate available inventory balance exists in the input warehouse/bin defined in Resource Group Maintenance (or none has been defined), it uses the backflush warehouse/bin (defined in the Backflush Warehouse and Backflush Bin fields in the Resource Group Maintenance > Resources > Detail sheet) for the resource associated with the job operation (if the available quantity on hand is greater than zero).
    • If an inadequate available inventory balance exists in the backflush warehouse/bin defined the Resource Group Maintenance > Resources > Detail sheet (or none has been defined), it uses the backflush warehouse/bin (defined in the Backflush Warehouse and Backflush Bin fields in Resource Group Maintenance) for the resource group associated with the job operation (if the available quantity on hand is greater than zero).
    • If an inadequate available inventory balance exists in the backflush warehouse/bin defined in Resource Group Maintenance (or none has been defined), it uses the primary bin defined in the Primary Bin field in Warehouse Maintenance for the associated job material warehouse (if the available quantity on hand is greater than zero).
    • If an inadequate available inventory balance exists in the primary bin defined in Warehouse Maintenance (or none has been defined), it uses the first bin for the associated job material warehouse that contains a quantity for the Inventory unit of measure defined for the component part being backflushed (if the available quantity on hand is greater than zero).
    • If an inadequate available inventory balance exists in a warehouse bin for the Inventory unit of measure defined for the component part being backflushed, it uses the first bin in the job material warehouse that has an available quantity, regardless of unit of measure.

    If you found this post helpful, feel free to like, share and comment.

    ]]>    Fri, 20 May 2016 22:03:46 -0500    <![CDATA[Epicor 101: Hotkeys (Keyboard Shortcuts)]]>https://getaligned.zohosites.com/blogs/post/epicor-hotkeys-keyboard-shortcuts
    Epicor provides per user options to define Global and per Program Hot Keys assignment. Global Hot Keys consist of about 10 application wide commands. Program Hot Keys are program specific commands that are configured in each Epicor program. Both are configured via the Options dialog by selecting Options from the Tools menu in each Epicor program Global Hot Keys.

    1.  In any Epicor program select ‘Options’ from the Tools menu.

    •  You maybe prompted to ‘clear the form’ – Select ‘Yes’
    2.  Select the ‘Global Options’ tab and then the ‘Hot Keys’ sub tab.
    3. Select the Global Command from the drop down to view or assign a Hot Key.
    4. Select the Hot Key Short Cut you want to use for the command.
        • After selecting the Short Cut from the drop down the value is immediately saved and there is no need to close out of the Options windows and reopen to define another Hot Key.
    5. In the "Launch Hot Keys" section select the Hot Key for each of the options.
        • Launch Search: by pressing this hot key when in a ‘key’ field (Customer ID, Supplier ID, Part Number, Lot Number, etc) the Search for the key will launch.
        • Launch Enterprise Search: by pressing this hot key when in a "key" Enterprise field will launch an Enterprise Search on that value.
        • Launch Maint with by pressing this hot key when in a "key" field will launch the Maintenance Program for that value.
        •  Launch Info Zone: by pressing this hot key when in a "key" field that has an Info Zone configured will launch the info zone view for the value.
      Per Epicor Program Hot Keys: Most Hot Keys are specific to each Epicor Program.  Most of the commands that are available to define a Hot Key are any of the ‘New’ options and any Menu or toolbar options including the contents of the Actions menu.  This means you can assign almost any command that is normally used with the mouse, such as New Header, New Line, Print, View Call Logs, View Attachments, etc.  By leveraging Hot Keys data entry tasks can be performed quicker and more efficiently.
      1.  Open the Epicor Program that needs Hot Keys assigned.
      2.  From the Tools menu select "Options".
          • You maybe prompted to "clear the form" – Select "Yes".

      3.  Select the "Hot Keys" tab.

      5.  Select the Command from the drop down to view or assign a Hot Key.
      6.  If a Short Cut is already defined it will show up in the Short Cut field, if not the field will read "None".

      7. Select the Hot Key Short Cut to use for the selected command.

          • After selecting the Short Cut from the drop down the value is immediately saved and there is no need to close out of the Options windows and reopen to define another Hot Key.
      8.  Select another Command to be defined from the Command drop down and select its Short Cut. Continue until all desired Command Hot Keys are defined.
      ]]>      Fri, 06 May 2016 20:11:32 -0500      <![CDATA[Epicor 101: Using Searches]]>https://getaligned.zohosites.com/blogs/post/epicor-10-using-searches

      Search programs are available throughout the application. Use these programs to find and select the specific records to display within another program. In each search program, you can filter and organize search results through record specific criteria. You can then select a single record or a group of records. You launch a search window by clicking a Search button next to a key field. These buttons are found on sheets throughout the interface. The button label indicates what specific records this search program locates. There are several different types of searches available in the search interface:

      • Base Search
      • Quick Search
      • BAQ Search
      • Advance Search
      • Data Tags Search
      • Basic Search Features
      • Sort By: Select an option on this drop-down list to organize the search results by a specific field found in the record. The results display in descending order.
      • Starting At: Enter a character or characters to indicate where in the dataset you would like to begin your search.
      • Additional Filters: Many Basic searches offer addition types of filters to further specify the criteria
      • Combobox/Dropdown: Select from a predefined list of values.
      • Search: Click on the Search button to search for an additional filter.
      • Radio Button: Select a radio button that best matches what you are looking for.

      Quick Search: A Quick Search is a custom designed search based on a BAQ (query), that can be developed to provide custom searches that fit a specific workflow or business process.  After selecting the Quick Search from the list and clicking on ‘Search,’ then enter the Quick Search criteria and click ‘Search’ again to view the results.  See the IT Department if you have an idea for a Quick Search.

      BAQ Search: A BAQ search is a predetermined search based on a BAQ (query), that can be developed to provide custom searches that fit a specific workflow or business process.  After selecting the BAQ Search from the list and clicking on ‘Search,’ the results of the BAQ will be displayed.  BAQ searches do not require any criteria to be entered since the predetermined criteria was already provided.  See the IT Department if you have an idea for a Quick Search. 

      Advanced Search: An Advanced search uses a custom dashboard to search for the desired data.  After selecting the Advanced Search Dashboard from the list and clicking on ‘Search’ button, the dashboard will be loaded.  If applicable, enter the Dashboard search criteria and select ‘Search.’  See the IT Department if you have an idea for an Advanced Search. 

      Data Tags Search: Data tag searches allow you to search for records that are grouped by private or shared tags. The tags are unstructured text values that provide a way to associate otherwise unrelated records so that you or other users can search for them.  You may Tag any record by Right-Clicking on the data field and selecting ‘Tag Record’ from the context menu. You can add as many data tags as needed to a record, each separated by a space. Because the tags are space delimited, you cannot include a space as part of a data tag.

       Faster Searching: Epicor provides several tools that can get you to your data faster.

      Named Search: Use the Named Search program to create a series of pre-set search options.  You may create Named Searches for Basic, Quick & BAQ Searches.  Named Search Options also allow you to define a default Named Search, if the named search should Auto Execute, set the maximum rows returned and if a single value is returned if it should be auto selected.  You create Named Searches by selecting the ‘Named Search’ button in the Search dialog and setting up the named search criteria.  You may have as many named searches as you wish, and they are displayed in the Named Search drop down.  When selected the search criteria defaults are set on the appropriate search form.

      Options > Auto Populate

      No Action: The default and nothing will happen when you open the program.

      Auto Populate Data: Automatically executes and selects the data specified by the criteria of the Named Search specified.  If you do not select a Named Search, then all the records for the program in the database will be loaded into the program.  This is generally a bad idea.
      Auto Load Search: Automatically opens the Search window with the selected Named Search. If a named search is not select, then the Base Search form will be loaded when the program is opened.

      Enterprise Search: In the Main Menu, you can use Enterprise Search to search for common or basic business objects across the database. Other search programs within the Epicor application are limited to querying records for a specific record type, but Enterprise Search locates a search item throughout the database.  Enterprise Search can be customized to index specific Business Objects and by default all business objects are not indexed.  Many of the common business objects that are indexed include, Customer, Contacts, Ship To, Sales Orders, Shipments, Quotes, Purchase Orders, Parts, Invoices, Cases and Service Calls.  Users can enter the search criteria they are looking for and return results with links to open the business object in its native program.

      ]]>      Fri, 01 Apr 2016 20:04:25 -0500