Block serial nos. (scrap) vs. Output

Mula
Member Posts: 2
Hi all,
i am asking for your help with a "little" problem of mine.
i need to create serial nos. for traceability items in advance, when releasing an production order.
After creation, we print barcodes and attach those labels to the item during the manufacturing process.
This means, the once created serial nos. may not be deleted or reused for other items.
Currently, I am creating serial nos. automatically by calling the built-in functions as Reservation entries (T337)
also i do create entries in Table 6504 (serial no. informaton) automatically for each reservation entry.
Manual deletions or modifications in T6504 are not allowed.
This way i am able to check if there is a double serial no. (e.g. when someone is resetting the no.series).
Also, the serial no. could end as scrap. Users want to flag the serial no. as "blocked" in the serial no. information card.
And that's where my problem starts now...
Let's say we want to produce 10 items and therefore generate 10 serial nos. in advance as reservation entries.
and use the standard production journal for posting.
Then we end up with one item being scrap, so we need to post an output of 9 and scrap 1.
Changing the qty. will need a regulation of serial nos. in advance...
How can i adjust the item reservations without deleting the blocked serial nos.? they should not get posted of course, but
may not be deleted.
i am asking for your help with a "little" problem of mine.
i need to create serial nos. for traceability items in advance, when releasing an production order.
After creation, we print barcodes and attach those labels to the item during the manufacturing process.
This means, the once created serial nos. may not be deleted or reused for other items.
Currently, I am creating serial nos. automatically by calling the built-in functions as Reservation entries (T337)
also i do create entries in Table 6504 (serial no. informaton) automatically for each reservation entry.
Manual deletions or modifications in T6504 are not allowed.
This way i am able to check if there is a double serial no. (e.g. when someone is resetting the no.series).
Also, the serial no. could end as scrap. Users want to flag the serial no. as "blocked" in the serial no. information card.
And that's where my problem starts now...
Let's say we want to produce 10 items and therefore generate 10 serial nos. in advance as reservation entries.
and use the standard production journal for posting.
Then we end up with one item being scrap, so we need to post an output of 9 and scrap 1.
Changing the qty. will need a regulation of serial nos. in advance...
How can i adjust the item reservations without deleting the blocked serial nos.? they should not get posted of course, but
may not be deleted.
0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions