Preface: This is for Gentran:Basic for Z-series only. No comments
please about how it's done in other mapping tools, this is an immediate
need and I'm drawing a blank. Please only comment if you know
Gentran:Basic.
The situation is that I have a customer who sometimes sends an N1 shipto
segment (N1*BY) and sometimes does not. However, SAP needs to encounter
a valid header level ship-to in order to go through the order creation
process; no "spreadsheet orders" yet allowed. (Meaning SDQ segments
only.) We are working on the changes within SAP to do this, but in the
meantime, as I said, I have this need.
Here's a sample of the two types of transactions we get.
This one we can process, because it has the N1*BY and has NO SDQ
segments - it's a regular single destination map.
BEG*00*SA*PONUMBER**20101220~
REF*IA*VENDORCODE~
SAC*A*E750*******ZZ*0~
DTM*001*20110121~
DTM*010*20101223~
N1*BY*STORE*92*1234~
PO1...~
PO1...~
This one we can't process.
BEG*00*SA*PONUMBER**20101220~
REF*IA*VENDORCODE~
DTM*001*20110121~
DTM*010*20101223~
PO1**115*EA*100.32**UP*UPCNUMBER*VA*VENDCODE~
SDQ*EA*92*0003*1*0004*1*0005*1*0006*1*0007*1*0008*1~
PO1**115*EA*100.32**UP*UPCNUMBER*VA*VENDCODE~
SDQ*EA*92*0003*1*0004*1*0005*1*0006*1*0007*1*0008*1~
I need to, in effect, stuff an N1 header shipto if none is found. It
doesn't matter what it is, because once it gets past the shipto, it will
hit the SDQ explosion process and create one sales order for each SDQ
destination that it sees and ignore the header level shipto. I am
going to have to - wait for it - hardcode a shipto in this map for this
customer. (Yes, it's a custom map. Yes, I hate this solution, but it's
temporary.)
Gentran:Basic (as well as other translators I'm sure) does not map an
outbound value if no segment exists in the interchange. So I'm hanging
my hat on the REF segment that they send.
So my logic wants to look like this:
If the REF*IA equals VENDORCODE, map the hardcoded output value that
I've defined in the extended mapping instructions.
However, if the map later encounters an N1*BY, I would expect that this
value be overwritten; except that it's not.
The hardcoded value keeps showing up again over and over for all the
interesting REF*IA segments even if the customer sends a N1*BY.
Remember, I can't do this AT the N1*BY because that logic simply won't
fire if the segment doesn't exist.
And I can't do it after the N1 because now I've switched from header to
detail level and I have crossed the "section" boundary.
Has anyone encountered a similar situation?
Rich Hurd
IT Technical Lead, Global Services
908-874-1523 Fax 800-538-1593 JJDial 8-340-1523
Furious activity is no substitute for understanding. -- H.H. Williams
[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/
