Hello Charles,
Thanks for the tips! FYI - ASNs can describe shipping info in different formats depending on how the material is packaged. The 'Shipment' is usually the parent and there can be 'X' number of children at various levels identified as Order/Tare/Pack/Item, hence the abbreviations: SOI=Shipment/Order/Item, SOPI=Shipment/Order/Packaging/item, etc.
1) I'd already been thru the manuals and the support portal and finally submitted a PMR, only to find that our maint on the Gentran product ran out earlier this year! My "IBM Entitlement & Reinstatement Specialist" is trying to find out which hoops to jump thru to reinstate. According to an email on Friday: "IBM does not invoice automatically--a quote is sent out to be reviewed and accepted by the customer. Once accepted, the support is invoiced." Which is all well & good as long as _someone_ get to review the quote in the first place!
2) As to the EDI doc itself - I just need to master the syntax...
JK
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Monday, November 11, 2013 8:47 AM
To: Midrange Systems Technical Discussion
Subject: Re: Legacy EDI - Gentran Server for iSeries - anyone using?
Jon,
I use Gentran Server for iSeries, though not that particular doc; nor am I familiar with the terms SOPI or SOI.
That being said, after taking a quick look at the 856 it looks pretty straightforward to me. The loop ID for HL is 1000, it wouldn't be affected by the fact the segments are nested. In the simplest scenario, you'd have a single detail file with a loop ID of 1000.
Assuming your HL data is split among multiple files, you'd probably want to make use of the sectioning functionality. AFAIK, each detail file would still have a loop ID of 1000. In fact, Gentran's online help mentions 856
specifically:
Sectioning Explanation
Sectioning allows the user to break the Detail portion of the document into smaller sections to better use the mapping buffers when large volumes of data are to be mapped.
ANSI 856 Advanced Shipment Notice. With sectioning, each HL level could be represented by a new area code and the buffer would be cleared more often. The HL level for Shipment ('S') would be set up at the 'D' area code. The HL level for Order ('O') would be area '1' and the item application shipment data to be read into the input buffer and be mapped to the correct HL loop.
If you're current on maintenance, you might consider asking support for help figuring out the map. (No guarantees...it's been I long time since I've contacted them :)
And just in case you hadn't found it, here's the docs:
http://www-01.ibm.com/support/docview.wss?uid=swg27023848#34
Feel free to PM me if you have to discuss further.
Charles
On Sat, Nov 9, 2013 at 1:22 AM, JK <johnking@xxxxxxx> wrote:
Hello all,
Is anyone out there still using the legacy Gentran Server for iSeries
to translate EDI docs? The product and its syntax are specific to the
iSeries and there's not much practical info in the manuals or the web.
Specifically, we need a map for inbound 856 ASN transactions and I'm
struggling to understand how to declare the nested HL segments in SOPI
and SOI formatted docs. It can't be difficult because this is a
widely-used transaction but I'm struggling to grasp the relationship
between the Loop_Ids on the 'Application Record' and the 'Transaction
Map'. Even a <print screen> of an existing map would help - does
anyone have expertise they'd be willing to share?
Much appreciated! - JK
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
