Technical Interview Questions and Answers :: EDI
Map Editor enables you to create (save as a DDF) a DDF file (Data Definition Format File) so that you can use it as a starting place in other maps or as a means to update existing maps.
ISA is an Interchange segment ID, it is the 1st envelope Segment in the EDI Envelopes, check this post https://www.facebook.com/v4info/posts/466091393750709
GS*6 is the group control number which is unique for one GS in side one ISA segment.
Auto trim is the way to activate the EDI segment base on input file.
Instead of activating map components manually, you can use the Auto Trim function to modify the EDI side of the map according to a sample EDI file that you select.
The sample EDI file must be of the same standard, version, and transaction set (message) as the map for Auto Trim to match map components.
Delimiters for the EDI side of the map must be set to match the delimiters used in the sample EDI file.
Writeblock() : The writeblock function writes the data contained in the argument of a string variable to the output file. The readblock and writeblock functions are used together to pass a block of data from the input file to the output file without compliance checking or testing for proper EDI syntax.
Readblock(): The readblock function reads a block of data (segment or record) from the input file and places it into the argument of a string variable. The readblock and writeblock functions are used in conjunction with each other to pass a block of data from the input file to the output file without compliance checking or testing for proper EDI syntax. Together, these functions provide a more efficient alternative of using wildcard segments, which are typically implemented in build and break maps.
Unreadblock() : The unreadblock function provides a method of moving the input file-pointer back one block (a block of data is equivalent to one EDI segment or one positional record). This function "unreads" the block of data that was just processed by the readblock function.
Pre-session rules define variables that have global scope (can be accessed from any other extended rule in the map). Pre-session extended rules are processed before the translation object is processed, and apply to every extended rule defined in the map.
Post-session rules are run after the translation object is processed and thus have no permanent scope.
To write valid extended rules, you must understand how to use indexes. Without indexes, it is possible that a rule which moves data from one field to another may result in lost data.
An index is a number that is used within an extended rule only when referencing a field contained by a repeating record or group. This number is used to specify the exact occurrence (iteration) of the repeating group or record that you want the translator to access.
When you are mapping the data from one group of data to other group we have to use the indexing to map the correct sequence of data
First Input file will read, then it will apply for standard rule on source side then check for extended rule then linking, then it will go to target side and apply standard rule, then extended rule.
Pre and Post rule will applicable according.
The Promote function extracts one iteration (instance) of one of the following map components:
· Repeating record
· Repeating element
· repeating composite
Promote is a specialized version of the Split function. For example, if you have a group with 50 iterations and you select Promote, you then have two groups: one group with an iteration of 1 and a group that iterates 49 times.
This function enables you to map unique data from a document and to type a specialized definition. The translator specifies that only one-to-one (no loop) or many-to-many (loop) mapping relationships are valid. The Promote function is available only if a group or repeating record, element, or composite is selected.
Tag Delimiter ~
Segment Delimiter *
Element Delimiter *
Sub Element Delimiter
Repeating Element Delimiter