A Practical Guide to Formatting in SAP PI: Learn by Example

Format by Example in SAP PI is a concept that allows users to define message mappings using examples rather than complex coding. This approach simplifies the development process and reduces the need for technical expertise, making it easier for non-technical users to create mappings. By providing sample input and output messages, users can generate mapping rules automatically based on these examples. This article explores how Format by Example works in SAP PI and discusses its benefits in terms of efficiency and ease of use.

SAP Versions used in the illustration:

SAP S4 HANA Fashion 1709 and SAP PO 7.5 are both software versions used in the field of SAP technology.

UseOneAsMany Node Function: Input and Output Format in SAP PI

UseOneAsMany has 3 inputs or arguments. The output of UseOneAsMany function is derived from these three inputs.

• Input 1 : Value from source message which should be repeated at target.
• Input 2 : Number of times first argument ‘Input 1′ should be repeated at the target.
• Input 3 : Context Change of the target or output.

Understanding the Concepts of Removing Context and Collapsing Context

– Removes suppressed and empty values within the same context.

– removeContexts: Deletes all top contexts for an element.

Using UseOneAsMany Inputs: Guidelines to Follow in SAP PI

Input 1 represents the specific value from the original message that we aim to replicate in the destination. Consequently, each instance of Input 1 should contain only one value.

Here are a few instances of how to allocate the initial parameter of the UseOneAsMany function.

Input 1 is accurately assigned without any duplicate values in a specific context. Input 1 has been correctly allocated with a single value, ensuring that there are no repetitions within the given context.

In both instances mentioned earlier, each context contains only one value. There is no repetition of values.

Incorrect allocation of parameters. Numerous values within the identical setting.

In this scenario, the values are duplicated. Both values exist within the same context. This type of value assignment is not valid for argument 1 of this node function.

Rule 2: Ensure Input 1 and Input 2 Have an Equal Number of Context Changes

The count of context changes for Input 1 and Input 2 should be the same.

Below are a few instances that demonstrate both accurate and inaccurate allocation of Input 1 and Input 2 for the node function.

The number of context changes in Input 1 and Input 2 is the same. There are a total of two context changes. The context changes for both Input 1 and Input 2 are equal, resulting in three context changes. However, if there is an incorrect assignment of Input 1 and Input 2 in UseOneAsMany, the context changes will not be equal.

Rule 3: Ensure Equal Total Number of Values in Input 2 and Input 3

The count of values in the queues for Input 2 and Input 3 must be the same.

For instance, both sets of arguments contain 4 values each.

Proper utilization of the second and third arguments in the node function UseOneAsMany is essential. Ensure that you understand how to correctly employ these arguments for optimal results.

By adhering to these guidelines while assigning the inputs, you can avoid encountering any Queue Exceptions.

Node functions in SAP PI: An overview

The given list of actions includes various functions that can be performed. These functions are createIf, removeContexts, replaceValue, Exists, SplitByValue, collapseContexts, useOneAsMany, sort and More items. Each function serves a different purpose and can be utilized in different scenarios to achieve specific outcomes.

For example, the createIf function allows you to create something based on certain conditions or criteria. This can be useful when you want to generate new data or elements only if certain requirements are met. For instance, in a shopping app, you could use this function to create a discount coupon for customers who have spent a certain amount of money.

On the other hand, the removeContexts function enables you to eliminate unnecessary contexts or factors from your data or system. This can help streamline processes and improve efficiency by removing any irrelevant information that might hinder decision-making or analysis.

The replaceValue function allows you to substitute one value with another within your data set or system. This is particularly handy when you need to update information across multiple instances without having to manually change each occurrence individually. For instance, if there is a change in pricing for products on an e-commerce website due to tax regulations changing in India; using this function would allow updating all affected prices at once.

– The createIf function generates new elements based on specified conditions.

– The removeContexts action eliminates unnecessary factors from your data/system.

– The replaceValue feature substitutes one value with another throughout your dataset/system.

– The Exists functionality determines whether something exists within your dataset/system

Using Examples to Demonstrate Format by Example in SAP PI

Now, we will examine the scenarios in which the UseOneAsMany node function is utilized by presenting a few examples.

Example 1: Repeat Purchase Order Number Using UseOneAsMany

The PONumber in the Purchase Order should be duplicated at the destination for every line item.

The purchase order number needs to be included in every line item.

UseOneAsMany Mapping:

The first input is the Purchase Order Number in the context of an order. The second argument is obtained from the Line Item, while the third argument is obtained from the Item Number segment.

SAP PI: Exploring the UseOneAsMany Arguments

Input 1 does not contain any duplicate values. Each context has only one purchase order number assigned to it. The first purchase order number, PO1, appears three times, while the second purchase order number, PO2, appears once.

Input 3 of the function defines the context changes of the target element. Notice that the total number of values in the Input 2 is equal to the total number of values in Input 3.

Example 2: Repeat Product ID at Target Message using UseOneAsMany

Here we have a source message with product header detail. A product can have multiple names. Target message should be created with each product name and corresponding product ID (ProductID).

Using OneAsMany Graphical Mapping for ProductID in SAP PI

The first input is the ProductID, while the second and third inputs are both ProductName. However, the third argument utilizes the SplitByValue function to obtain the appropriate context.

SAP PI: Exploring Format By Example

Product-1 needs to be duplicated twice, whereas Product-2 only has a single product name. As for Product-3, it possesses three distinct names and thus should be assigned three times at the target destination.

In Input 3, the SplitByValue node function is utilized to specify the required modifications in context.

It is important to observe that we have followed the guidelines 1, 2, and 3 of the UseOneAsMany function. There are no duplicate values in argument 1, which represents the queue of Product IDs.

Argument 2 specifies the desired repetition of Product ID. Input 2 and 3 have an equal number of context changes in the queue.

SAP PI: An Alternative Approach to Mapping Product ID Using Example 3

Let’s take the same source and target messages as in example 2, but use UseOneAsMany node function differently.

Alternative Node Function Argument Assignment

I want to emphasize the significance of argument (Input) 3 in this particular instance. In this case, Rule 3 is fulfilled because the number of values in Input 2 and input 3 are equal. To ensure a smooth transition at the target, we employ SplitByValue after using UseOneAsMany.

To summarize, we can apply UseOneAsMany node function to repeat values in graphical mapping. There are three input arguments and one output in this function. Assign the input arguments to the function based on the three rules. Hope this article on the different aspects of UseOneasMany node function is helpful to you!

You can refer to my earlier article regarding the functions of RemoveContext and CollapseContext nodes.

If you have any queries regarding the UseOneAsMany node function, please feel free to leave a comment below.

Hello, my name is Isuru Fernando and I have a decade of experience as a Senior SAP Integration Consultant, specializing in full-cycle implementation and support projects.

Since my early days, I have had a strong interest in coding, software development, and all things related to technology. Initially starting as an ABAP developer, I discovered my passion for system integration when I learned SAP XI 3.0 back in 2008. Throughout my career, I have taken on various roles such as an offshore technical consultant (ABAP, PI/PO, BW, BOBJ) and eventually became a technical lead overseeing consultants from different countries. This journey has provided me with extensive experience in implementing SAP projects throughout their lifecycle.

During my experience working on SAP implementation projects in various regions such as the USA, EU, and Asia, I gained valuable knowledge about global business processes in areas like Sales and Distribution (SD), Material Management, Retail, Customer Relationship Management (CRM), and Finance and Controlling (FICO).

In this blog, I aim to share my extensive knowledge in various SAP technical domains like SAP ABAP, PI/PO, AIF, and Basis. Additionally, I strive to create a space where individuals with similar aspirations can showcase their expertise in SAP technology to a wider audience.

Using one as many in SAP PI: What is its purpose?

If you need to replicate a field that appears only once in an outbound message as many times as another field occurs, the useOneAsMany() function is necessary. This allows the fields to be written in pairs as a record and transferred to the target structure.

The useOneAsMany() function acts as a bridge between different structures within SAP PI by replicating one field (Field B) multiple times based on how many occurrences of another field (Field A) are present in the outbound message. This ensures that both fields can be processed together and written into their respective positions within the target structure.

Overall, understanding how to utilize functions like useOneAsMany() plays a crucial role in ensuring accurate data transformation and mapping within SAP PI scenarios involving format-by-example requirements. By leveraging this functionality effectively, developers can streamline integration processes and ensure seamless communication between systems while adhering to specific formatting needs dictated by business requirements

Collapse context in SAP CPI: What does it mean?

The collapseContexts() function in SAP PI allows for the consolidation of values from multiple contexts into a single context. In cases where certain contexts are empty, they will be replaced with an empty string. This functionality proves beneficial when there is a need to create an upper-level node whenever a lower-level node exists. The collapseContexts() function can be effectively used in conjunction with the SplitByValue() function to achieve desired results.

When using the collapseContexts() function in SAP PI, it enables the merging of values from various contexts into one specific context. If any of these contexts happen to be empty, they will simply be substituted with an empty string during this process. This feature becomes particularly useful when there is a requirement to generate an upper-level node each time a lower-level node is present within the system. By combining this functionality with that of the SplitByValue() function, users can attain their intended outcomes efficiently.

SAP PI offers users the ability to employ the collapseContexts() feature as part of its format by example methodology. With this functionality, data originating from diverse contexts can be merged and consolidated into one specific context within the system framework effortlessly. When encountering instances where particular contexts lack any values or information, such occurrences are automatically substituted with an empty string during this consolidation procedure itself. This aspect becomes especially valuable when there arises a need to establish superior-tier nodes every time subordinate-tier nodes are present. By skillfully combining the collapseContexts() function with other relevant functions like SplitByValue(), users can effectively accomplish their desired objectives in a streamlined manner.

What does removing context mean?

Imagine a photograph capturing two football teams in action. In this analogy, each team represents a specific context within the overall picture. If you were to point at one of the teams and remove all other visual cues, only that particular team would be visible. Similarly, if you zoomed in on an individual player within that team and eliminated any surrounding elements, only that player would remain in focus.

In SAP PI (Process Integration), Format by Example plays a crucial role in transforming data from one format to another based on predefined rules or patterns. Just like pointing at different aspects of a photograph alters what is shown, Format by Example allows users to define specific formatting rules for their data transformations.

By providing examples of input and output messages or documents, users can instruct SAP PI on how they want their data formatted. This approach simplifies the process as it eliminates the need for complex coding or scripting languages. Instead, users can rely on intuitive graphical interfaces provided by SAP PI tools.

P.S: With Format by Example functionality in SAP PI, businesses operating in India can streamline their integration processes while ensuring accurate and consistent data formatting according to their specific requirements.

What does removing context mean in SAP PI?

context are used while handling/processing Queues of the fields in the XML structure. Remove Context: this function is used to remove context changes, it removes the CC from the Queue of the field in question.

Katy