Help me out Plz urgent, Gentran NT System Import Map

[R279]

Hi there EDI Guyz,

I started recently working on Gentran NT 4.0,

I need help regarding this system import map,

for an outbound transaction, I did the following steps

> created import map and compiled it

> created system import map based on steps given in Help
like created 1 segment with 5 elements partner_id,transaction set,version,standard,test/prod flag

like in help,used standard rules select for partner id and update for remaining elements.

So I dont understand what actually we are doing here like how do we relate the system import map and the normal import map,so do i need to use some elements from normal import map header record in this system import map.

Please some one can help me like how do we relate system and normal import map and how to create a system import map,what are the considerations to be done,anything on system import map.

Any suggestions would be really helpful and appreciate it.

Thanks

 

[hcalder]

Hi R279,
The System Import map is simply a method for Gentran to ascertain the Partner and the Transaction Set to be used for the data being imported into Gentran i.e. the partner relationship. When you have registered the compiled System Import map in the system you also need to set it up in the Configurator under the Imports tab with a path to the directory where the data file is to be found.
Your normal Import map, once registered, is available to be set up as an outbound relationship for any partner you choose. You will also need to set up the outbound interchange envelope details as part of each partner relationship.

Rgds,

Hugh.

 

[R279]

Hi Hugh,

First of all, Thnks for your help.

I do have some haunting questions.

Let me tell you an example,

this is an outbound transaction.

I am receiving an application file for two transactions like

810 and 856 combined, so i need to seperate them and use there respective normal import maps.

I created normal import maps,so as these transactions both come in same positional file, do i need to have same system import map or different.

If in the file I am receiving we have only one header record and one line record, so in the input side I created two records, header record contains info like translator code,comunication method, document std,document id, document type ...,but i am not linking the header record to anything on the output side,so do i need to use this header record in some way in system import map.

for creating sys import map like i said before just used the elements refered in HELP,and added in sys config , so that will do or i need to do anything else with sys import map.

So after creation of partner and outbound relation, do we need to relate the sys import map to that,or it gets automatically related.

In order to make it clear gave a long description, please suggest me.

Thanks,

Raj

 

[prospector55]

Good morning R279,

I am new to the Tek-Tips forum. Since this thread is an old one, I do not know if you still need the information. Below I have placed a description of the way that everything appears to tie together based on my personal testing long ago. I have not had the benefit of any of the classes from Sterling, so there may be some misconceptions. If so, I would appreciate any feedback. The bottom line is that it works.


The system import map should contain your header record. The fields of the header record will be associated with application field 1, application field2, transaction, test flag, etc. In the trading partner setup, after setting up the initial outbound information (name, version, std, etc), click on the translation button. This is where you specify the registered object that is going to be used to translate the data. There are 2 boxes there for application field 1 (application ID) and application field 2 (application alias value) information that are used to identify the correct translation object for a given document.


For example:

System_Import_Map1 contains only the header record as follows:

HDR1 810 X 004010 Test Customer1

In the system import map, the field for Customer1 is used in a standard rule – select – partner by alternate code. This will cause Gentran to select the appropriate trading partner from the list of partners. If you go to the partner editor and highlight the desired partner and click on Edit, the “Application code” is the value that will be checked as the alternate ID. The X is used in a standard rule – update- document record – Application Field 1. This will be checked against the value in the Application ID box in the window displayed by clicking on the Translation button. Similarly, the 810 is used in a standard rule – update – document record – Application Field 2. This will be checked against the value in the Alias Value box in the window displayed by clicking on the Translation button. The 2 fields matching up identifies this as the correct translation object to use to translate the document.

Note that the 2 fields that I used in this example to identify the correct translation object are not the only 2 that could have been used. As long as the combination is unique for that trading partner, it will work.

I hope that this helps you.
Prospector55