Monday, April 6, 2020
Wednesday, April 1, 2020
Dynamics NAV/BC Columbus Foods - Production Planning Process
Before doing any planning
Regular Production
- Ensure item replenishment areas are setup for all manufactured items
- Ensure items with pre-processes are setup to auto-plan if component
Regular Production
- Create Formula BOMs
- Create Packaging BOMs
- Quick Planner - Run for FG (or per level of package BOM)
- Run Quick Planner again if second level is also a package bom
- Batch Planner - Run at end to generate batch planned Production Orders with batch numbering and formula int
- If an item does not show up in the batch planning list,
- the production grouping item has not been set for that family of bom items
- Go to the item card and define the production grouping item for all items in the chain
- Filter by Quantity Required > 0
- If you get "attempted to divide by zero"
- It means the intermediate below this item's item type is not set to "Intermediate" on the item card
- Either your intermediate item should be set as an intermediate
- OR Run quick planner to generate orders for this level of production
- Select Item>Plan
- If you get another "attempted to divide by zero" when packing out
- The package bom should not have multiple equipment
- Generate Pre-Process Activities
- Run Prod. Repl. Move List for each replenishment area
- If bin is marked to break containers, ADC will not be able to transfer containers into the bin
- ADC Bin to Bin raw materials to Preprocess Bins, no destination containers
- After time passes,
- Update pre-process > Register pre-process to move stock into Replenishment Bin
- ADC Bin to Bin raw materials to Replenishment Bins, no destination containers
- Execute Production
- Post Batch Reporting
- Final packout (Bread only, or second level packout of FG)
- Release Planned Production Order
- Line>Component>Production Journal
- Enter consumption and output
- Post production journal
- ADC Bin to Bin finished goods to final destination
Co-Buy Production
- Setup Std cost by products
- Setup regular primary products
- Create co-Buy Bom
- Run Supply Driven Planning
Thursday, March 26, 2020
Wednesday, March 25, 2020
Devops - Future iterations aren't showing in the Delivery Plans function
- Cause
- You used the Project Configuration to define new sprints, but did not actually create new sprints in the Backlog
- Resolution
- From Backlogs>Planning Create new sprints
- It will use the predefined sprints from the project configuration if they were defined
- Otherwise, you can define new sprints
- These will now display in the delivery plan
Dynamics NAV / Business Central - Payment Application View
SELECT INV.timestamp, INV.[Entry No_], INV.[Vendor Ledger Entry No_], INV.[Entry Type] AS InvType, INV.[Posting Date], INV.[Document Type], INV.[Document No_], INV.Amount, INV.[Amount (LCY)], INV.[Vendor No_],
INV.[Transaction No_], INV.[Debit Amount], INV.[Credit Amount], INV.[Debit Amount (LCY)], INV.[Credit Amount (LCY)], INV.[Applied Vend_ Ledger Entry No_], INV.Unapplied, INV.[Unapplied by Entry No_],
INV.[Application No_], PAY.[Entry Type] AS PayType, VLEPAY.[Document Date] AS PaymentDate, VLEPAY.[External Document No_] AS PayExtDoc, VLEINV.[Document No_] AS INVDocNo,
VLEINV.[Document Date] AS INVDocDate, VLEINV.[External Document No_] AS INVExtDoc
FROM dbo.[Pennywise$Detailed Vendor Ledg_ Entry] AS INV INNER JOIN
dbo.[Pennywise$Detailed Vendor Ledg_ Entry] AS PAY ON INV.[Vendor Ledger Entry No_] = PAY.[Vendor Ledger Entry No_] INNER JOIN
dbo.[Pennywise$Vendor Ledger Entry] AS VLEPAY ON PAY.[Document No_] = VLEPAY.[Document No_] INNER JOIN
dbo.[Pennywise$Vendor Ledger Entry] AS VLEINV ON INV.[Vendor Ledger Entry No_] = VLEINV.[Entry No_]
WHERE (INV.[Entry Type] IN (2, 4)) AND (PAY.[Entry Type] = 1) AND (INV.[Debit Amount] > 0)
INV.[Transaction No_], INV.[Debit Amount], INV.[Credit Amount], INV.[Debit Amount (LCY)], INV.[Credit Amount (LCY)], INV.[Applied Vend_ Ledger Entry No_], INV.Unapplied, INV.[Unapplied by Entry No_],
INV.[Application No_], PAY.[Entry Type] AS PayType, VLEPAY.[Document Date] AS PaymentDate, VLEPAY.[External Document No_] AS PayExtDoc, VLEINV.[Document No_] AS INVDocNo,
VLEINV.[Document Date] AS INVDocDate, VLEINV.[External Document No_] AS INVExtDoc
FROM dbo.[Pennywise$Detailed Vendor Ledg_ Entry] AS INV INNER JOIN
dbo.[Pennywise$Detailed Vendor Ledg_ Entry] AS PAY ON INV.[Vendor Ledger Entry No_] = PAY.[Vendor Ledger Entry No_] INNER JOIN
dbo.[Pennywise$Vendor Ledger Entry] AS VLEPAY ON PAY.[Document No_] = VLEPAY.[Document No_] INNER JOIN
dbo.[Pennywise$Vendor Ledger Entry] AS VLEINV ON INV.[Vendor Ledger Entry No_] = VLEINV.[Entry No_]
WHERE (INV.[Entry Type] IN (2, 4)) AND (PAY.[Entry Type] = 1) AND (INV.[Debit Amount] > 0)
Monday, March 23, 2020
Dynamics NAV, business Central - Web client - "Working On it" timeout error
Problem:
Solution:
- This happens on sales return order>get documents to reverse
Solution:
- Use a different Browser
- Chrome or Edge do not suffer from this issue.
- Explorer does.
Friday, March 13, 2020
Business Central - Demo Install, cannot login to web client - Add nav user
The user account you are currently using cannot login to Business Central.
Add another user account with super permission.
Error: You are not setup as a valid user
https://docs.microsoft.com/en-us/previous-versions/dynamicsnav-2013r2/jj672890(v=nav.71)
If you are restoring from an external database, Add your windows account to the database using SSMS to ensure the powershell can even interact with the db.
Give it db_owner to the db and master
From powershell or administration shell, run as administrator
New-NAVServerUser MicrosoftDynamicsNavServer -WindowsAccount Cronus\Chris
New-NAVServerUserPermissionSet DynamicsNAV71 –WindowsAccount cronus\chris -PermissionSetId BASIC
New-NAVServerUserPermissionSet CRONUS –WindowsAccount cronus\Joe -PermissionSetId SUPER
eg.
New-NAVServerUser BC150 -WindowsAccount mypc\test New-NAVServerUserPermissionSet BC150 –WindowsAccount mypc\test -PermissionSetId SUPER
Add another user account with super permission.
Error: You are not setup as a valid user
https://docs.microsoft.com/en-us/previous-versions/dynamicsnav-2013r2/jj672890(v=nav.71)
If you are restoring from an external database, Add your windows account to the database using SSMS to ensure the powershell can even interact with the db.
Give it db_owner to the db and master
From powershell or administration shell, run as administrator
New-NAVServerUser MicrosoftDynamicsNavServer -WindowsAccount Cronus\Chris
New-NAVServerUserPermissionSet DynamicsNAV71 –WindowsAccount cronus\chris -PermissionSetId BASIC
New-NAVServerUserPermissionSet CRONUS –WindowsAccount cronus\Joe -PermissionSetId SUPER
eg.
New-NAVServerUser BC150 -WindowsAccount mypc\test New-NAVServerUserPermissionSet BC150 –WindowsAccount mypc\test -PermissionSetId SUPER
Subscribe to:
Posts (Atom)