Not sure why you can't do a x12 to x12 mapping, but whatever reason it
seems you cannot. Another approach could be to look at the inbound
"x12" as a delimited flat-file. Then you would basically be creating
one map... an delimited-flat-file (which looks like a x12-4010) to
x12-5010.
--- In [email protected], "vijaychandrak07" <vijaychandrak07@...>
wrote:
>
> Hi All,
>
> Has anyone worked on X12 to X12 mapping? I have this requirement for
mapping Health Care Claim transaction (837) from 4010 to 5010. My
platform is IBM Sterling Integrator5.2 .
>
> My client needs to get it done by outbound process only. I am clueless
on how to run an outbound process for x12-x12 transactions. I'm quite
aware of outbound for positional to X12 / XML to X12 using header maps
where I write select/update statements to recognize the correct
partnerID's. Can we use the same process of header maps for X12-X12
outbound mapping too?
> Asking this because when I tried to create a header map for the X12
elements' standard rules, I couldn't find select and update. Please
advice.
>
> Regards,
> Chandra
>
[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/
