Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Reason Codes for Item Journal Entries?
kfons
Member Posts: 19
We are currently looking at way we can differentiate our scrap that is posted via the Item Journal.
We currently seperate some items using the General Posting Group, Department codes, and Area Code.
I am looking for simple reason codes to seperate transactions into standard categories like Obsolescense, Damaged in Production, Vendor Quality, Engineering Samples, etc.
We don't have access to the reason code field, not sure what granual this is part of, etc.
We could just create a custom field.
We will most likely either just copy and past monthly transactions using
filters and sorting from the item ledger entry table, or use SRS to write
some scrap reports to seperate out the categories.
I'm curious to hear what other people have done for this to make it quick
and easy without adding too much complexity.
We are on SQL version 4.1
Kevin
--
Kevin Fons - Materials Manager
Saris Cycling Group
Madison, WI 53711
We currently seperate some items using the General Posting Group, Department codes, and Area Code.
I am looking for simple reason codes to seperate transactions into standard categories like Obsolescense, Damaged in Production, Vendor Quality, Engineering Samples, etc.
We don't have access to the reason code field, not sure what granual this is part of, etc.
We could just create a custom field.
We will most likely either just copy and past monthly transactions using
filters and sorting from the item ledger entry table, or use SRS to write
some scrap reports to seperate out the categories.
I'm curious to hear what other people have done for this to make it quick
and easy without adding too much complexity.
We are on SQL version 4.1
Kevin
--
Kevin Fons - Materials Manager
Saris Cycling Group
Madison, WI 53711
Kevin Fons
Director of Business Systems
Saris Cycling Group - Madison, WI USA
Director of Business Systems
Saris Cycling Group - Madison, WI USA
0
Comments
No coding would be required and you could use the analysis view to see what you have in each.