Hi,
Non-standard characters can often be added (possibly depending on editor, but
it works here in SB Client), by holding down ALT and typing in the character
code on the numeric pad. In the case of @VM, that would be alt+253.
Adam
-Original Message-
From:
Late to this, but I use includes with code in two situations:
1. As standard library pieces managed through a pre-compiler, usually for
platform-dependent sections. For example, I have standard includes for
getting command line arguments, reading and writing from ini files and so
forth. The
I want to thank each contributor to this thread for the reasoned and
professional responses.
As always, very illuminating and instructive to be a part of this list.
Thank you each.
-Baker
This communication, its contents and any file attachments transmitted with it
are intended solely for
For those EDIers on the list.
Do any of you process drop shipments using EDI for 850's?
What method do you use?
We were thinking :
First N1 loop - N1 segment contains the BT and use the SAN (15 code)
Second N1 loop - N1 segment contains the ST but use phone# for identification
(12 code)
If you are using one ship to (drop ship) destination then what you suggest
below is fine. We often have a 'BT' (bill to) N1, N3 and N4 followed by a
'ST' (ship to) N1, N3 and N4.
Footnote: If you are going to have multiple destination in one PO, you will
need to look into the SDQ segment.
Didn't think about multiple destinationsI would hope that they separate
their 850's on the drop ships
So that each order is it's own destination.
I don't think they want to get too complicated either, so I think we can agree
on keeping it simple.
Thanks
George
-Original Message-
Are you setting up specifications or do you already have a set that
you're working from? You should be able to isolate the N1 loops from
each other within a dataset so that each loop is a functional subset.
Then, based on the BT/ST code determine what kind of information you
have and apply it
Aside from phone#, the other thought was just a straight text DROPSHIP, other
than
That, I wouldn't be relating the phone number to anything, other than a piece
of data
Isolating the loops isn't a problem. I have a subroutine that converts the EDI
To a dynamic array, and it knows that N1 is a
Without seeing your approach to handling your data, and more importantly
how you're feeding this data into your sales order system, I'm not real
sure what you're asking for. The only thing I really see in your
original question is about recognizing what the data in the N1 loop is.
That's what the
George, EDI is more people-oriented than technical. The X12
documents provide a structure, and trading partners can discuss
the content used to populate those structures to achieve their
business goals. There are few details about the 850, 856, 820,
997, 810, etc that can't be negotiated to
The universe compiler (-xref) option is pretty useful for tracking down
variable usage. Specifically, I'd like to eliminate assigned but unused
variables, so I'm looking for output that has single assignments only. It
looks like the raw compiler output from -X is from an intermediate file
Tony,
I can't agree more, as I've always said, EDI standards are the most
non-standard things I've ever seen.
Problem is I hadn't ever worked with drop shipments in EDI, and the trading
partner we are trying to
do this with has never done using EDI either, and I probably know more about
EDI
George,
May I suggest that you also post this question to the EDI-L group at:
ed...@yahoogroups.com?
They are all EDI specialists, much like most of us are U2/multivalue
specialists.
I'll look for your question on the EDI-L list and I look forward to the
responses you get.
Best regards,
13 matches
Mail list logo
