vault backup: 2025-09-25 18:51:36

This commit is contained in:
Alex Kogutkiewicz
2025-09-25 18:51:36 -05:00
parent f78d5800ac
commit 220b12583f
92 changed files with 3227 additions and 62 deletions

View File

@@ -0,0 +1,50 @@
JDMEX-4514316192
* Sending part number in PO1 segment
* Part number sent on outbound in IT1 segment
* Sales order part: FG3582B w/ cross reference TA40412
JDMEX-4514541897
* Sending part number in PO1 segment (TR147312)
* Part number included on outbound IT1 segment
* Sales order part: QPA3440CEX w/o cross reference
JDNAA-4514623393
* Sending part in PID segment (TR150730)
* No invoice yet
* Sales order part: FG4096C w/ cross reference TR150730
JDNAA-4514660499
* Sending tooling (non-part) in PID segment
* FSEC (generic inspection fixture part) used on sales order
* Only PO line was mentioned on invoice
JDWWL-PNW00317945
* Send with part number on PO1 line (but with a T at the end)
* FSEC used on sales order for both lines
* Invoice was submitted through another means
JOHDE-4514443907
* Part number sent in PO1 segment (QT521828A)
* Sales order part: QPA3758C w/o cross reference
JOHDE-4514455124
* Tooling description in PID segment (non-part)
* Invoice references only PO line
* Sales order has FSEC part, addition line charges
JOHDE-4514602090
* A bunch of MIOEM (programming charges)
* FSEC charge
* Inspection description sent in PID segment (non-part)
* No invoice yet
Questions:
- Right now, for the John Deere 856 and 810, is there any data being sourced that wouldnt be available on a manually entered order?
Ideas:
* Reader-report for the 850
* We will leave 856s alone - will send those as normal
* For 810, if a certain value (undetermined) is set to something, send
* If I submit 3 lines with the same PO number, can the map combine those into a single line