Sie sind auf Seite 1von 26

createIf

Description:” I have criteria for existing”. It is used when you want to create target node or element based on some condition.

createIf Description:” I have criteria for existing”. It is used when you want to create target

Fig.1

Figure depicts createIf node functionality. ID is mapped to MT_Reciever_Minor using createIf function.

Fig.2 Figure depicts result of mapping in Fig.1.As, the value of ID is less than 25,

Fig.2

Figure depicts result of mapping in Fig.1.As, the value of ID is less than 25, MT_Reciever_Minor node is created in target side.

Fig.3 Figure depicts createIf node functionality. ID is mapped to MT_Reciever_Major using createIf function.

Fig.3

Figure depicts createIf node functionality. ID is mapped to MT_Reciever_Major using createIf function.

Fig.4 Figure depicts result of mapping in Fig.3.As, the value of ID is greater than 25,

Fig.4

Figure depicts result of mapping in Fig.3.As, the value of ID is greater than 25, MT_Reciever_Major node is created in target side.

removeContext

Description: Removes all immediate level contexts of a source field. In this way, you can delete all hierarchy levels and generate a list.

Fig.5 Figure depicts removeContexts functionality.

Fig.5

Figure depicts removeContexts functionality.

Fig.6 Figure depicts result of mapping in Fig.5.By applying removeContexts, all the Cust_NAME fields came in

Fig.6

Figure depicts result of mapping in Fig.5.By applying removeContexts, all the Cust_NAME fields came in one context.

replaceValue

Description: Replaces the value of element with a value that you can define in the dialog for the function properties.

Fig.7 Figure depicts replaceValue functionality.

Fig.7

Figure depicts replaceValue functionality.

Fig.8 replaceValue will replace the value of Cust_NAME element with the value defined i.e.20Name. splitByValue Description:

Fig.8

replaceValue will replace the value of Cust_NAME element with the value defined i.e.20Name.

splitByValue

Description: splitByValue() is the counterpart to removeContexts(): Instead of deleting a context, you can insert a context change in the source value queue.

You can insert a context change in the queue after each value or after each change to the value, or after each tag without a value.

splitByValue can be achieved in following three ways:

1. EACH VALUE

Fig.12 Figure depicts the splitByValue(Each Value) functionality.

Fig.12

Figure depicts the splitByValue(Each Value) functionality.

Fig.13 Figure depicts the splitByValue (Each Value) mapping result. 2. VALUE CHANGE

Fig.13

Figure depicts the splitByValue (Each Value) mapping result.

2. VALUE CHANGE

Fig.14 Figure depicts the splitByValue (Value Change) functionality.

Fig.14

Figure depicts the splitByValue (Value Change) functionality.

Fig.15 Figure depicts the splitByValue (Value Change) mapping result. 3. EMPTY VALUE

Fig.15

Figure depicts the splitByValue (Value Change) mapping result.

3. EMPTY VALUE

Fig.16 Figure depicts the splitByValue (Empty Value) functionality.

Fig.16

Figure depicts the splitByValue (Empty Value) functionality.

Fig.17 Figure depicts the splitByValue (Empty Value) mapping result. collapseContext Description: It takes the first value

Fig.17

Figure depicts the splitByValue (Empty Value) mapping result.

collapseContext

Description: It takes the first value from all the contexts and put them into a context on the target side, So that all values come under one context.

Empty contexts are replaced by empty strings.

Fig.18 Figure depicts the collapseContexts functionality.

Fig.18

Figure depicts the collapseContexts functionality.

Fig.19 Figure depicts the collapseContexts mapping result. useOneAsMany Description: As shown in the figure below the

Fig.19

Figure depicts the collapseContexts mapping result.

useOneAsMany

Description: As shown in the figure below the maximum occurrence of the header node in the source is 1 and the target is unbounded. So we have only one occurrence of MatNo & MatDesc, which has to be replicated for every line Item.

Fig.20 Above figure depicts, both source & target structures.

Fig.20

Above figure depicts, both source & target structures.

Fig.21 Above fig depicts, mapping of usOneAsMany function In the above figure , useOneAsMany takes three

Fig.21

Above fig depicts, mapping of usOneAsMany function

In the above figure, useOneAsMany takes three arguments.

  • 1. First argument “what should be repeated”.

  • 2. Second argument “how many times, first argument should repeat”.

  • 3. Third argument “Should have same context of Item (Second argument)”.It maintains the context.

MatDesc field will also be mapped in similar way like MatNo.

Fig.22 Number of time Item node appears (repeats), same number of time Header node will appear

Fig.22

Number of time Item node appears (repeats), same number of time Header node will appear in target side. So, source Item node is mapped to Target Header node.

Fig.23 In above fig, Item node is duplicated.

Fig.23

In above fig, Item node is duplicated.

Fig.24 In above fig, Item node is duplicated twice in the source structure. Accordingly, Header is

Fig.24

In above fig, Item node is duplicated twice in the source structure. Accordingly, Header is repeating twice in the target side i.e. MatNo & MatDesc.

sort & sortByKey

Description: The element Cust_Name shall be sorted the same way as the element Cust_ID. but with two inbound parameters to sort (key/value) pairs. The sort process can be compared to that of a table with two columns

Sort and sortByKey: Have 3 options.

1)

Lexicographically 2) Lexicographically (Case Insensitive) and 3) Numeric.

Fig.25 Figure depicts the sort functionality. As the functions sort and sortByKey only sort the elements

Fig.25

Figure depicts the sort functionality.

As the functions sort and sortByKey only sort the elements within the same context, we have to use the function removeContexts before sort. After sort we have to restore the original contexts. We do this with the node function splitByValue

Fig.26 Figure depicts the sortByKey functionality. In the above fig The Cust_Name is sorted based on

Fig.26

Figure depicts the sortByKey functionality.

In the above fig The Cust_Name is sorted based on the Cust_ID.

sortByKey: take two arguments, first argument acts as key for sorting the second argument.

Fig.27 In the above fig Cust_Name is sorted based on Cust_ID. mapWithDefault Description: This function provides

Fig.27

In the above fig Cust_Name is sorted based on Cust_ID.

mapWithDefault

Description: This function provides a default value, whenever the source element is not available.

Fig.28 Figure depicts the mapWithDefault functionality.

Fig.28

Figure depicts the mapWithDefault functionality.

Fig.29 Figure depicts the mapWithDefault mapping result.

Fig.29

Figure depicts the mapWithDefault mapping result.