[EDI-L Mailing List Archive Home] [Message List] [Reply To This Message]

Re: 856 Standard vs Pick and Pack Structure

From: "lgstcs_boy" <khurst@...>
Date: Tue Oct 7, 2003  4:43 pm
Subject: Re: 856 Standard vs Pick and Pack Structure
did someone say 856? a subject near and dear to my heart.

There are a couple very simple ways to use either a qualifier or the
heirarchial structure in the 856 itself to determine how the data
relates to the real world.

For the qualifier, just use the BSN05 to designate the heirarchy in
the message, or in the HL loops, you can use the numbering &
child/parent information in HL01 and HL02 to tell you how things are
built.

dB-wise, you need to create a structure that allows for the
definition of the data structures being sent so that when you pipe
the information down to your end user you give them the right
information.

I hope that helps. Feel free to ping me with any specific questions.

Cheers,

Kyle
Amazon.com



--- In "edipro1212" <gooldedi@a...> wrote:
> Good Monday morning all,
> I'll try to make this as short as possible...
> All of our customers want their 856's in Pick and Pack Structure
> (SOPI). We have a new customer who wants their 856 in Standard
> Structure (SOIP). It is my understanding that shipping
> software/systems (I don't know exactly what to call it) are set up
to
> do either P&P or Standard--not both. At other jobs, we have had to
> programmatically re-sort the P&P data and write a new physical file
> for the data in Standard format. I'm trying to explain this to our
> programmer, be he insists that a new logical file over the Pick and
> Pack physical will work if we use different keys. This just
doesn't
> seem to make sense to me--how can one file have both one item to
many
> packs AND one pack to many items, no matter how you sort it? Am I
> crazy? I'm relatively new at this job, so I have not built up
enough
> credibility for anyone to believe what I'm saying. I have a
meeting
> with him in an hour, so any quick second (third, fourth) opinion is
> very welcome.
>
> Thank you!
> Tracy
>
> AS400, BPCS ERP, Varsity shipping software, SSA modified version of
> Harbiner 3.2 translator




 
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify EDI Data Integration with Stylus Studio XML Enterprise Suite - Free Download!
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2007 All Rights Reserved.