Here you can find EDI Mapping Interview Questions and Answers.
In this EDI Mapping Interview Questions and Answers section you can learn and practice EDI Mapping Interview Questions and Answers to improve your skills in order to face technical inerview by IT companies. By Practicing these interview questions, you can easily crack any EDI Mapping interview.
AllIndiaExams provides you lots EDI Mapping Interview Questions and Answers with proper explanation. Fully solved examples with detailed answer description. All students, freshers can download EDI Mapping Interview Questions and Answers as PDF files and eBooks.
You no need to worry, we have given lots of EDI Mapping Interview Questions and Answers and also we have provided lots of FAQ's to quickly answer the questions in the EDI Mapping technical interview.
What are the rules available in map editor?
1. Pre session rule: In pre session rule we can declare and initialize the variables and also we can write the conditions as per the business rules. It will get executed at the beginning of the map translation. The variables we declare in the pre session rule are having global scope. 2.Loop extended rule: Loop extend rule is applied to the record or segment level. We have on begin and on end rules in loop extended rule. For looping records or groups on begin rule executed once for each occurrence of the loop at the beginning of each loop. For looping records or groups on end rule executed once for each occurrence of the loop at the end of each loop. 3. Extended rule: In extended rule we can write the business rules using functions available in the SI map editor and we can declare the variables. The variables we declare in the extended rule are having local scope. 4.Standard rule: We can apply standard rules to the field level using predefined functions available in the standard rule. Those predefined functions are 1.Select 2.Update 3.Use system variable, it enables you to set a variable that maps current date and time to the selected field. The selected map component must have a data type of Date Time. 4.Use constant, it enables you to move a constant value to the specified field. 5.Use accumulator, it gives access to a set of numeric variables that you can manipulate using numeric operations and then transfer to fields. 6.Loop count, it enables to count number of times a loop is repeated if the field is the part of the loop. 7.Use code. It enables to use code lists to validate the content of a field and use as a reference to look up an associated description for a field. 5. Post session rules: It is same as pre sessions but only difference is pre session rules will get executed at the beginning of the translation but post session rules will get executed after the translation.
Explain the execution of a map in SI map editor?
In map editor, what are all the conditions and variables listed in the pre session rule that will execute first because presession rules will get execute at the beginning of the translation. And then it will check the group or record if is there any on begin rule that will execute next. Then it goes in to fields in the record, if is there any Standard rule/ Extended rule we apply for the field that will execute Extended rule for the field will be executed. At the end of the record, on end rule will be executed if we write any conditions there.
Explain the process in migration map development?
We will analyse the business rules on the mapping for the customer in the production system then we will create the specification. We will test the map by taking existing production system input file and run that in SI then compare existing production system to corresponding output file. At last SI generates output.
When to use temporary records and fields ?
Use temporary records and fields When you cannot use a simple link or if you must extract only specific occurrences of a record from your data file. If you must map from a repeating map component to a single map component, or vice versa. If the Input hierarchical level in a map does not match the Output hierarchical level. If you only want to populate an Output field with data if a specified qualifier is used or if specific criteria is met. If you must use extended rules in addition to creating temporary records and fields.
Where to use temporary records and fields ?
You can add temporary records and fields at any hierarchical level in a map. However, when you use temporary records and fields, you must locate them after the map component that contains the necessary data. You must use a record tag that you would never receive in your Input file, and the recommended default is $$$. If you are creating a temporary record for an XML file, use the tag XXX, because $$$ is not permitted as a tag in XML. The translator does not run standard or extended rules on temporary records.
Explain about Split function ?
The Split function can be used to split the following objects into two groups: Group Repeating record Repeating element Repeating composite After the split operation is performed, the individual iterations of the two groups that were created by splitting a group add up to the original number of iterations of the group before the split. The Split function is available only if a group or repeating record, element, or composite is selected. Use the Split function when you need more than one instance of a map component that occurs multiple times.
Explain about Promote function ?
The Promote function extracts one iteration (instance) of one of the following map components : Group 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. The Promote function is available only if a group or repeating record, element, or composite is selected. Promote function enables you to map unique data from a document and to type a specialized definition.
Explain about Select standard rule ?
The Select standard rule: associate a field with a TP code list, a section in process data, a document envelope, and use the transaction register function.Document envelope: support TRADACOMS enveloping to enable the map to extract values from the envelope definition and use them in the map. Trading partner code list: list of codes that are dynamic, related to trading partners, and stored in the Application database. Process data: service-independent XML DOM associated with a BP that holds data associated with the BP, which you interact with using XPath. Transaction register: specify a field for which you want to see if it contains duplicate data (using the Update standard rule Transaction Register function) and then invoke it (using the Select standard rule Transaction Register function) to verify whether the field contains duplicate data.
Explain about Update standard rule ?
The Update standard rule: move data from a field in the map into process data, to update process data so that the data can be used elsewhere in the BP, to record document- specific parameters during translation, and to check for duplicate data. Document extraction: load values into the Sender ID, Application Sender ID, Receiver ID, Application Receiver ID, and Accepter Lookup Alias field values in the Document Extraction table, so that the Document Extraction service can put these values in process data, along with an associated output document. process data: service-independent XML DOM associated with a BP that holds data associated with the BP, which you interact with using XPath. correlation data: record document-specific correlation parameters during translation. Transaction register: specify a field for which you want to check for duplicate data (using the Update standard rule Transaction Register function) and then invoke it (using the Select standard rule Transaction Register function) to verify whether the field contains duplicate data. Transaction XREF: cross-reference the application data to generated transaction.
What are various types of extended rules ?
Pre-Session extended rules: These rules define variables that have global scope and can be accessed from any other extended rule in the map. They are processed before the translation object is processed. Post-Session standard rules: These rules run after the translation object is processed and have no permanent scope. On-Begin extended rules: The On-Begin rules are processed before the start of the group iterations and before any variables in the group are instantiated. On-End extended rules: The On-End rules are processed after the end of the group.