cancel
Showing results for 
Search instead for 
Did you mean: 

NODE FUNCTIONS

Former Member
0 Kudos

Hi all,

Can i get a detailed explanation on Node functions..

please not the general links....... I want simple clear examples to explain each of the below listed node functions in detail :

1.createIf,

2.removeContexts,

3.replaceValue,

4.Exists,

5.SplitByValue,

6.collapseContexts,

7.useOneAsMany,

8.sort,

9.sortByKey,

10.mapwithDefault,

11.formatByExample

please hurry up...

thanks in advance

Accepted Solutions (0)

Answers (5)

Answers (5)

former_member556603
Active Contributor
0 Kudos

Hello Deepika,

1.createIf,

2.removeContexts,

3.replaceValue,

4.Exists,

5.SplitByValue,

6.collapseContexts,

7.useOneAsMany,

8.sort,

9.sortByKey,

10.mapwithDefault,

11.formatByExample

Just u go throgh this link..

Standard Functions :

http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/content.htm

Function Category: Node Functions

Function

Use

createIf

If there are structuring elements in your target structure that do not exist in the source structure, insert them using this function. Using condition I you can control whether the element is inserted or not. You connect the element in the target structure using O.

removeContexts

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

replaceValue

Replaces the value I with a value that you can define in the dialog for the function properties.

exists

O = true, if the source field assigned to inbound channel I exists in the XML instance. Otherwise, false.

SplitByValue

Inserts a context change for an element.

collapseContexts

Deletes all values from all contexts from the inbound queue except for the first value. Empty contexts (= ResultList.SUPPRESS) are replaced by empty strings. Only one queue remains, which consists of contexts that contain just one value each. Finally, all internal context changes are deleted, so that all values belong to one and the same context.

useOneAsMany

Replicates a value of a field occurring once to pair it as a record with the values of a field occurring more than once.

sort

Sorts all values of the multiply-occurring inbound field I within the existing or set context. The sorting process is stable (the order of elements that are the same is not switched) and it sorts the values in O(n*log(n)) steps. Using the function properties, you can specify whether values are to be sorted numerically or lexicographically (case-sensitive or non case-sensitive) and in ascending or descending order.

sortByKey

Like sort, but with two inbound parameters to sort (key/value) pairs. The sort process can be compared to that of a table with two columns.

● Using the first parameter, you pass key values from the first column, which are used to sort the table. If you have classified the key values as numeric in the function properties, they must not be equal to the constant ResultList.SUPPRESS. See also: The ResultList Object

● Using the second parameter, you pass the values from the second column of the table.

If there is a discrepancy between the number of keys and values, the mapping runtime triggers an exception. The function returns a queue with the values sorted according to the keys.

mapWithDefault

Replaces empty contexts in the inbound queue with a default value, which you specify in the function properties.

Example:

If “Default” is the default value and

A|B1,B2| |C| |D

is the inbound queue,

mapWithDefault returns the following outbound queue:

A | B1,B2 | Default | C | Default |D.

The function corresponds to the following combination of standard functions:

If(

[]field,

exists([]field),

Constant([value=default]))

formatByExample

This function has two inbound queues, which must both have the same number of values. To generate the result queue, the function takes the values from the first queue and combines them with the context changes from the second queue.

Nice blogs..

/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii

/people/stefan.grube/blog/2005/12/29/new-functions-in-the-graphical-mapping-tool-xi-30-sp13

Hope this info is useful to you..

Thanks,

Satya..

Former Member
0 Kudos

These blog links are really worth.. Node functions explained with proper examples.... give a try for implementing these examples ....

Message Mapping Simplified – Part II

/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii

Replication of Nodes Using the Graphical Mapping Tool

/people/claus.wallacher/blog/2006/04/17/replication-of-nodes-using-the-graphical-mapping-tool

Message Splitting Using the Graphical Mapping Tool

/people/claus.wallacher/blog/2006/06/29/message-splitting-using-the-graphical-mapping-tool

Introduction to Context Handling in Message Mapping

/people/riyaz.sayyad/blog/2006/04/23/introduction-to-context-handling-in-message-mapping

Former Member
0 Kudos

Hi,

Please go through these links.

/people/stefan.grube/blog/2005/12/29/new-functions-in-the-graphical-mapping-tool-xi-30-sp13

Message Mapping Simplified - Part I

/people/sravya.talanki2/blog/2005/08/16/message-mapping-simplified--part-i

Message Mapping Simplified – Part II

/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9202d890-0201-0010-1588-adb...

These might be helpful for u.

Regards

radhika.

former_member8655
Active Participant
0 Kudos
Former Member
0 Kudos

Hi Deepika,

1. remove context:

You use removeContexts () to delete all the top contexts for an element. This removes all top hierarchy levels, so that all elements of the target queue are assigned to a root element of the source queue.

Advanced user-defined functions can import either just one context into the input arrays, or complete queues. Make your selection by selecting or deselecting the Save Entire Queue in Cache checkbox in the function editor.

2. split by value:

The SplitByValue() function is the counterpart to removeContexts(): Instead of deleting a context, you can insert a context change in the source value queue. You then receive this element for each inserted context change instead of a top node element. However, for this to be possible, the top node source field must be assigned a top node target field and minOccurs must be >0. You can insert a context change in the queue after each value, after each change to the value, or after each tag without a value.

3. collapse context:

Using collapseContexts() puts the first values of all contexts into a context. Empty contexts are replaced with an empty string:

This can be useful if an upper-level node is to be created each time a lower-level node exists, for example. The function is useful in combination with the SplitByValue function.

4. Use one as many

You require the function useOneAsMany() if a field that only occurs once needs to be replicated as often as another field occurs in the outbound message so that the fields can be written to the target structure in pairs as a record.

http://help.sap.com/saphelp_nw04/helpdata/en/2c/2d8c4024d26e1de10000000a1550b0/frameset.htm

5. Map with default

6.copyValue

You use CopyValue() for a frequently occurring element to copy the value of a position in the source structure and assign it to a target field. The value is copied each time the target field occurs in the target structure. However, it is copied a maximum of maxOccurs times

7.createIf

You use createIf() to create a tag in the target structure depending on a condition.

8.exists

You use this function to determine whether a particular source field exists in the XML instance to be processed. If it does, exists() returns the value true, otherwise it returns the value false.

9.Use

You use this function if you need to synchronize two queues of equal length with reference to their context change. The mapping runtime takes the values from the first queue, and the context change from the second queue. If the two inbound queues do not have the same number of values, the mapping runtime triggers an exception.

Regards,

Radhika.