|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: Migrating Visual Maps to AI Maps in Gentran:Server U nix 6.0
Finally I was able to find out the way to get necessary values shown below
into delimited output file. It was not that easy like I in VM. But it
works. However I have some other questions to those who using Gentran:
Server for UNIX 6.0 (comparing to 5.3)
1. Check out / Check in procedure.
When checking out map it goes into working directory on client PC and into
host working directory. After I compile it, I always need to copy TPL file
into host working directory to be able to run translation. In 5.3 when you
compile map you had it in host working directory already. After that if I
want to check map back in master directory my PC just hang up in case if I
check in both files (*.map and *.TPL files). In this case TPL file goes
into master map directory, but *.map file goes nowhere and stays in working
directory. Then I need to kill Gentran process through Task Manager
(Gentran not responding at this time) and repeat all steps to check in file
with extension *.map.
Does anyone have this type of problem on UNIX platform?
2. Mapping Trailer record.
In Trailer Record I need to get number of all records created in output file
after translation. This is 850 transaction coming in. I created some
system variables and I increase the count by one in extended rule for each
record I write into output. I'm getting the correct number, but only for
last transaction (last PO) on the transmission. It seems like Gentran just
refreshing that count anytime it begin to read new transaction. Output file
looks fine if there is no TRL record - all header records and all item loop
records appear in output in correct sequence, but count is wrong.
Am I missing something here?
Vladimir
-----Original Message-----
From: Epshteyn, Vladimir [mailto:
Sent: Monday, April 05, 2004 9:50 AM
To:
Subject: RE: [EDI-L] Migrating Visual Maps to AI Maps in Gentran:Server U
nix 6.0
Hi Mark,
I'm having the same problem with conversion from Gentran: Server 5.3 to
Gentran: Server 6.0 SP2 (SunOS). I was using TP Code definition in many 850
maps as a key to convert it into appropriate Bill-To number and to create
some other fields.
My mapping instructions in VM looks like the following examples:
MAP trading partner & portion of text $ISA_Cntl starting at position 2 for 9
characters; & $SYS_Date TO D43
MAP generic synonym of source trading partner using the list named
'TP>BillTO' ; & '-' & portion of text S353 starting at position 3 for 4
characters; & '--' TO D8
Finally Sterling Commerce has helped me to make some changes in the set up
and insert ISA / GS envelope segments into Source definition, but
unfortunately all these steps are not in their documentation. With envelope
segments I think I can do something similar by using EDI ID. However I did
not have time to continue with this conversion and testing after that.
Vladimir
-----Original Message-----
From: Mark Lorenti [mailto: Behalf Of
Sent: Saturday, April 03, 2004 4:38 AM
To:
Subject: RE: ***[Possible UCE]*** [EDI-L] Migrating Visual Maps to AI Maps
in Gentran:Server Unix 6.0
Hi Brian,
You can use generic code lists in GIS (not in the map) to replace the
functionality of the generic synonym tables in G:S for UNIX. Just define
the code list to have blank sender and receiver ID's.
As for the TP Code ... there isn't really a TP Code (partner/transaction
unique id) anymore in GIS; you could use the transaction level envelope name
for that partner as a unique identifier. You would have to populate process
data with this value earlier in the process (e.g., via a lightweight JDBC
adapter), then it would be available for use in the map via a standard rule.
If you give me an idea of what your trying to accomplish with the TP Code, I
may have further ideas/suggestions.
Regards,
Mark Lorenti
Knack Technologies LLC
706-738-4102 office
208-730-0323 efax
-----Original Message-----
From: [mailto:
Sent: Thursday, April 01, 2004 12:31 PM
To:
Subject: ***[Possible UCE]*** [EDI-L] Migrating Visual Maps to AI Maps in
Gentran:Server Unix 6.0
According to Sterling Commerce, the Visual mapping tool used in
Gentran:Server for Unix up through version 5.2 will no longer be
updated/enhanced as of version 6.0. This has led me to investigate a
project for my company in which we will migrate our small list of
visual maps to the AI mapper. However, two things appear to be
missing from the AI mapper which were used extensively by my
predecessors in the Visual mapping tool, TPCode mapping and Generic
Synonym tables.
According to the FAQ, you cannot map the TPCode directly from the
Trading partner information to the application file. Anyone figure
out a way around this limitation other than by large extended rules
or hard coding in the specific maps?
The Generic Synonym tables can be replaced by code lists in
individual AI maps but other then copying maps to include the code
lists, can these be stored somehow to be accessed by any AI map?
My question is, has anyone undertaken this map conversion before in
the Unix environment? If so, did you deal with the TPCode and Generic
Synonym table issues? How did you handle these issues, more
importantly, best practice to move generic synonym tables to
equivalent in AI mapping?
Thank you,
Brian Leist
EDI Specialist
.
Please use the following Message Identifiers as your subject prefix:
<SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Yahoo! Groups Links
.
Please use the following Message Identifiers as your subject prefix:
<SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Yahoo! Groups Links
[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>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Yahoo! Groups Links
[Non-text portions of this message have been removed]
|
|
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
