We are going to start forecasting at the store level using the 830 document we
already have in place (version 4010). In 4010, the X12 standards allow only 50
occurrences of the SDQ segment within the LIN/FST loop, meaning we can report
only up to 500 locations within each FST, since each SDQ contains up to 10
locations.
We have a need to report more than 500 locations when reporting at the store
level, so I see we will need to start a 2nd, 3rd, 4th, etc. FST loop within the
LIN. This SDQ limitation complicates the process of keeping the quantity in
FST01 (mandatory element) in sync with the total of the quantities in each
grouping of 50 SDQ segments (i.e., 500 locations).
Am I looking at this correctly, or am I missing something obvious, as far as
the best way to report more than 500 locations in the 830 document? I'm
wondering why, in this particular document, there is a limitation of the SDQ
segments, while in other documents (850 and 852, for example), there is a much
higher or unlimited number of SDQ occurrences allowed.
Right now I am working offsite and only have access to the X12 standards up to
version 4020, and version 4020 has the same SDQ limitation -- does anyone know
if later versions of the 830 standards allow more than 50 SDQ occurrences per
FST?
Your help is always appreciated!
Jayne
...
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Job postings are welcome, but for job postings or requests for work: <JOBS> IS
REQUIRED in the subject line as a prefix.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/EDI-L/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
