In this case I agree with the notion that there is no right or wrong. It should be done according to business rules and the actual usage of the PO Number value.
However, validating the structure defined in a trading partners mapping spec is not an unreasonable thing to do in the mapping tool of your translator. Some trading partners simply send a dummy sequential value and some send a PO Number value that is somewhat sophisticated. This example is from the Target 850 Mapping specs: The Basic PO Number format is: SSSS-PPPPPPP-LLLL SSSS = Source Code (e.g. department number) PPPPPPP = Purchase Order Number LLLL = Location ID (Always the Bill To Location) Sample BEG segment for Target BEG*00*SA*0093-2465211-0551**20041018*D The ANSI X12 standard allows for 22 characters in the BEG03 data element 324. Target is using the element according to standard but is also defining their structural format use for the element. My point is that it would not be unreasonable on the input side of the map to create a mask AAAA-AAAAAAA-AAAA with A being an alphanumeric string value. This would be useful especially if your application will use the values in the PO Number. Sergey Sudakov EDI Project Manager Beacon EDI, Inc [email protected] 4445 Eastgate Mall Suite 200 San Diego, CA 92121 800-334-6127 x2 https://beaconedi.com/ EDI Blog: https://beaconedi.com/edi-blog On Wed, May 22, 2013 at 9:02 AM, need2know711 <[email protected]>wrote: > ** > > > Hello group. > > I have questions about tight application validation. We are consolidating > one of our division into our national translator. It turns out the division > is performing validation on the format PO NUMBER within the EDI map. So if > the format is not right, it will reject the PO, even if it is valid EDI > data according to the standards. On our national translator we allow the > valid numbers to enter into the application and depend on the application > to validate the actual format. > > What are the thoughts as to what is the "right" way to handle formatting > issues? > > > [Non-text portions of this message have been removed] ------------------------------------ ... 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: [email protected] [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/
