SAP Community - SAP Process Integration

B2B/TPM on SAP BTP Integration Suite migration (SAP PO, Boomi, EDI Providers and home-grown apps)

2023-12-12T11:54:48+01:00

Summary

SAP BTP Integration Suite has matured in the B2B/EDI space over the years and a much broader adoption is currently happening but what to consider for this type of migration? In this article I will try to answer why does it make sense to move to SAP BTP Integration Suite B2B functionality, when to take this step, what is it made of and how to do it without disrupting the most important integration flows for many companies, responsible for selling, buying, and shipping most of the products.

Figure - SAP PO, Boomi, EDI provider (OpenText) migration to SAP BTP Integration Suite TPM/B2B.

WHY - why move your EDI integration to SAP BTP Integration Suite B2B/TPM?

There are two aspects of that question. The first one is related to the fact why move at all if the old system is working and without any doubts it will be a challenging process. Because the cost of doing nothing can be very high and maybe it’s time to think about it:

How many CR (change requests) were not implemented or implemented with a big delay on the current landscape?

How much does it cost to run the EDI on-premise?

Where there any scalability issues that required additional cost?

Was there any downtime caused by the old integration platform?

Is the current integration platform ready for new EDI types of connections?

Is the company bound to use a single Service Integrator (SI) or vendor resources as no one else can operate the current EDI solution?

What is the employee productivity with the current integration platform?

Is there any technical debt related to using the current integration platform?

"In the realm of innovation preparations, one must question how does the cost of inaction can be confidently calculated - Michal Krawczyk"

Once you answer the first question on the cost of doing nothing then you might get into some more detailed questions depending on the type of your current EDI/B2B integration solution:

SAP Process Orchestration B2B addon (SAP PO)

Does it make sense to stay on the on-premises solution with an end of life in 2027?

How quickly can you do the changes without the Integration Advisor?

Boomi, other iPaaS solutions

Does it make sense to use nonSAP solution in case all your business processed using EDI are running on SAP?

Is the topic of skill consolidation important at your company or do you prepare to have different teams/vendors for each part of your internal business processes?

EDI providers like OpenText

What is more important for you at the current stage of your SAP program: EDI/B2B integration delivery speed and accountability of the whole process or cost of EDI transactions?

Are you fine with outsourcing parts of the most important processes of your company (selling, buying, shipping) to a middleman?

Home grown applications

Do you have and will continue to have a very strong internal development team who will always be there to support you?

What is the cost of adding new functions to the home grown application?

Is the topic of skill consolidation important at your company or do you prepare to have different teams/vendors for each part of your internal business processes?

WHEN – when is the time to plan and the move to SAP BTP Integration Suite?

Best way to find out when is to have a look at the Roadmap explorer and put in the “B2B Integration” phrase but the number of new B2B features is overwhelming.

Figure - B2B integration feature roadmap in SAP BTP Integration Suite

HOW – how to simplify the move to SAP BTP Integration Suite?

First thing first - learn!

You need to learn how to work with SAP BTP Integration Suite and the best way to do it is to use SAP community knowledge:

openSAP course “Manage B2B Scenarios Effectively with SAP Integration Suite”

An amazing blog series by Bhavesh Kantilal (link in the reference section)

Automate testing

Testing is 65% of your EDI migration project. If you want to move to SAP BTP Integration Suite, it may be worth making sure your EDI/B2B flows will continue working after the migration so it might be useful to run automated testing for this program. Int4 Shield is not only recommended solution by SAP for this type of programs, but it’s also used by SAP for RiseWithSAP service called “SAP BTP Integration Suite testing” and used by SAP consulting for SAP BTP Integration Suite EDI/B2B migration projects. With Int4 Shield you can easily model the whole EDI message exchange (made of multiple iflows – sender, transformation, and receiver) in a single testable unit and run it as often as you wish as shown in the figures below:

Figure - Combine all iflows of a typical B2B/EDI scenario (sender, transformation and receiver) in one test using Int4 Shield

Figure - results of a EDI file comparison using Int4 Shield

Simulate EDI partners

Do you want to engage your EDI partners a lot for this migration program and literally make the project stop or would you like to simulate your EDI partners and have complete control of the program? If you want to control the speed of this migration project I’d advice to have a look at Unit 2: Simulating EDI partners based on historical transactions and Unit 3: How to virtualize messages from B2B partners and external applications of openSAP course “Avoid SAP S/4HANA Project Delays with Third-Party Systems Service Virtualization”.

Figure - Simulate EDI partners with Int4 Shield

Last but not least - what about the new mappings?

What to do if you migrate from non-SAP system to SAP BTP Integration Suite and you cannot reuse the mappings? Why not automatically generate them from historical messages? Have a look a this video explaining the concept of how generative Test Driven Development can help you generate the mappings automatically with Int4 Shield as per the video from SAP Devtoberfest 2023 below:

Wish you all the best with your SAP BTP Integration Suite B2B migrations!

References

Frequently Asked Questions (FAQ) on Edge Integration Cell

2023-12-14T21:21:29+01:00

Background
With so much anticipation after the release of Edge Integration Cell in SAP Integration Suite, I realise that there are many questions that needs to be addressed specifically. Hence giving it a shot to create this Frequently Asked Questions for Edge Integration Cell, hoping that it answers most of the burning questions.

What is Edge Integration Cell?
“Edge Integration Cell” is the new flexible hybrid integration runtime, offered as an optional extension to SAP Integration Suite, enabling customers to manage APIs and run their integration scenarios within customer-managed private landscapes.

What are the key features of Edge Integration Cell?

Flexible deployment option in customer managed private kubernetes environments (Azure AKS, Amazon EKS, SUSE Rancher)

Design, configure and monitor integrations and APIs in the cloud but run them within your private landscape

Configure and manage multiple Edge Integration Cells with an SAP Integration Suite cloud tenant

Offers a migration path for PI/PO customers, to move to SAP Integration Suite, and still be able to run scenarios within their private landscape

What are the main use cases and when should I use Edge Integration Cell?

Supports data compliance and governance by processing data locally

Elevate the transformation journey for SAP PI/PO customers

Suitable for on-premise to on-premise integrations

Leverage it for API-led and event-driven integrations in your private landscape

Business continuity during temporary connectivity loss (part of 2024 roadmap)

High Availability setup for backup with multiple Edge Integration Cells in different clusters

Which Kubernetes containerised platforms are currently supported and which other containerised platforms support is planned?
As of now, the supported Kubernetes platforms are Microsoft Azure AKS, Amazon EKS and SUSE Rancher. We plan to support RedHat OpenShift as additional K8s platform as part of the roadmap.

How do I install and set it up?
You can find the detailed steps to setup and install Edge Integration Cell in this blog.

Why there is no "Runtime" tab under Settings even though I have the SAP Integration Suite license which is eligible for Edge Integration Cell?
You need to configure entitlements in the SAP BTP cockpit and then you will see this available in your SAP Integration Suite tenant. Please check this blog on setup and installation for more details.

What is the licensing model?

Every SAP Integration Suite licensed tenant (via standard edition, premium edition, CPEA and PAYG) gets one entitlement of Edge Integration Cell included.

Additional Edge Integration Cell entitlements can be acquired through a separate add-on SKU.

Messages flowing through Edge Integration Cell(s) will be metered but only 50% of them are chargeable.

How much does the additional Edge Integration Cell cost?
You can find the pricing details here in the SAP Discovery Center.

Can I buy Edge Integration Cell with SAP Integration Suite Basic Edition?
No, Edge Integration Cell is available only with these SAP Integration Suite licenses (standard edition, premium edition, CPEA and PAYG).

If a message flow from an integration flow deployed on Edge Integration Cell to another integration flow deployed on SAP Integration Suite, will it still be considered as one message or two?
Depends. If the message is flowing through unmodified SAP to SAP standard content in both the runtimes, then the message count will be 0. But if the message is flowing through modified standard content or custom content in both runtimes, then 1.5, since according to the licensing model of Edge Integration Cell only 50% messages are chargeable.

Does it have all the features of Cloud Integration supported?
Not yet. We plan to provide feature parity between Edge Integration Cell and Cloud Integration. You can check the currently supported features and limitations in the runtime scope. Then later in addition, we plan to offer additional on-premise specific features and adapters. You can follow the progress of these feature deliveries via the roadmap explorer.

How do we size Edge Integration Cell?
We have published a sizing guide for Edge Integration Cell as a recommendation.

Is there a way to have both runtime and design time deployed within a private landscape?
No, this is not possible. Edge Integration Cell is a runtime, which can be deployed in your private landscape. It uses the design time and monitoring of SAP Integration Suite in the cloud for designing, deploying and monitoring integrations and APIs but have the flexibility to run them on Edge Integration Cell.

What will be the frequency of updates to Edge Integration Cell and how will it be applied?
Edge Integration Cell will also receive updates at "cloud" speed, that is, every 4 weeks, like we ship updates for SAP Integration Suite. Customers can check the Operate -> Status Information to check the version details.

Or check if there is a the "warning" icon in Edge Lifecycle Management cockpit, which means that the software version is outdated and a newer version is available. Then click on the three dots next to Edge Integration Cell solution to upgrade to the latest version.

Will there be support for older versions of Edge Integration Cell and for how many past versions?
Like mentioned above, there will be updates for Edge Integration Cell every 4 weeks. We recommend you to apply these updates as soon as they are available. But customers will have an option to delay the software update of Edge Integration Cell for additional 4 weeks from the time the update is available. So that means, that SAP will support the latest version (n) and one older version (n-1) than the latest version. We also plan to restrict deployment of new content to any older version of Edge Integration Cell beyond n-1 version. This is to ensure that you are on the latest version of the software and are consuming the latest innovations.

How long does the update of Edge Integration Cell solution take?
Depends upon the network connectivity but it is usually quite fast.

How is the responsibilities split between SAP and customer for Edge Integration Cell?
Here you can check out the roles and responsibilities of the customer split across 3 main personas - System Admin, Tenant Admin and Integration / API Developer.

Similar information is presented in a different perspective as the Operating Model for Edge Integration Cell in the documentation.

Will the monitoring data or payload get pulled to the cloud from Edge Integration Cell?
All the message processing and payload data is persisted on the Edge Integration Cell into the external database within the customers private landscape. The monitoring UI in the cloud pulls only the monitoring metadata using the APIs and displays this information to the end-user. But the payload data can move to the cloud only if "trace" log level is switched on in the monitoring.

Is there a plan to support monitoring of Edge Integration Cell in SAP Cloud ALM?
Yes. The plan is to provide remote OData APIs for monitoring and operations of Edge Integration Cell and with this you will be able to integrate it to SAP Cloud ALM or SAP Focussed Run or any other 3rd party monitoring tools.

Are there plans to support access policies at integration flow level for Edge Integration Cell?
Yes, this is planned and part of the roadmap.

Are there plans to support offline mode for Edge Integration Cell?
Yes, we do plan to support offline mode for Edge Integration Cell, to ensure business continuity during temporary connectivity loss (for up to 4 hours).

Will Edge Integration Cell have the features that are currently offered in SAP PI/PO?
SAP Integration Suite is the logical successor of SAP PI/PO. We have the Migration Assessment, Migration Tooling, Regression Test Tools from partners, and now Edge Integration Cell, to support this transformation journey from SAP PI/PO to SAP Integration Suite. Edge Integration Cell plays an important role in this whole journey, as it gives the customers an option to continue running specific scenarios on-prem or within their private landscape. There are also plans to provide on-prem specific adapters like RFC Sender, File, OFTP2, and X400 adapter on Edge Integration Cell.

Is Edge Integration Cell available as part of RISE with SAP?
RISE with SAP comes with SAP BTP/CPEA entitlements which can be used to subscribe to SAP Integration Suite and this gives you entitlement to use Edge Integration Cell. You can install and setup Edge Integration Cell in your private landscape on one of the supported K8s platforms. But Edge Integration Cell is not available as a service hosted and managed by SAP within the RISE context.

How many Edge Integration Cells can be managed by one SAP Integration Suite tenant?
You can assign up to 20 Edge Integration Cells to a Keystore and hence manage the same number of Edge Integration Cells with one SAP Integration Suite tenant.

Which all regions is Edge Integration Cell available? If not available in a particular region, how can we request for it?
You can check for the available and planned regions for Edge Integration Cell in the SAP note. Some regions are available on demand and can be enabled based on customer request.

How to setup High Availability for Edge Integration Cell?
You can check the recommendations on HA setup for Edge Integration Cell in the documentation.

Can I use the internal persistence (PostgreSQL & Redis) of Edge Integration Cell for productive scenarios?
No, the internal persistence of Edge Integration Cell can be used only for test and demo purposes as these built-in services aren't highly available, nor scalable as required for a production environment. For a production environment, you need to use an external PostgreSQL database and a Redis data store outside the Edge Integration Cell deployment.

Can the Cloud Connector which is part of Edge Lifecycle Management be used for other applications other than Edge Integration Cell?
The Cloud Connector as part of Edge Lifecycle Management is inbuilt and cannot be used separately for any other applications. Refer to the technical landscape of Edge Integration Cell for more details.

Can the Kubernetes Cluster be shared with other applications?
It is strongly recommended to use dedicated K8s cluster for Edge Integration Cell and not share it with any other applications which has higher resource requirements.

Can one Kubernetes cluster host multiple Edge Integration Cell deployments?
The Edge Integration Cell deployment uses a fixed K8s namespace (edge-icell). Therefore, multiple deployments in the same cluster is not possible.

Conclusion
Hope this blog helped you get most of your questions answered. If you still have questions, feel free to add them in the comments section and we will respond to them.

Enabling Pagination in SAP PO

2023-12-19T02:39:12+01:00

How to enable pagination in SAP PO

We have a requirement where we need to call the api’s to get the data but there is a limitation where we can retrieve only 50 records per one call, hence we need to come up with an approach where we can do multiple calls and get all the open items. API is providing an offset parameter that can help us to control the pagination part.

Approach

Configure REST Polling option on the REST adapter and configure the GET call

Once the data is retrieved, we can have 2 Routing rules in ICO which would send the data to SAP and other to get the next 50 records from the API URL.

When calling the API to get the next 50 we have made the offset parameter dynamic and that value is controlled from message mapping level.

Here is the tricky part where we need to delegate the response of the GET call to another ICO through the virtual receiver concept.

We need to configure a series of standard adapter modules that would help us to trigger the second virtual ICO which would have the identical mappings of the main ICO. This virtual ICO will be executed multiple times until all the records are retrieved from API.

Here DynamicConfigurationBean is used to pass the offset value to the virtual ICO to ensure duplicate calls are not made, this will ensure offset values are properly propagated .

RequestResponseBean and ResponseOnewayBean are used to ensure data is directed to the appropriate virtual ICO.

Through this approach we could see that we are able to efficiently handle the pagination part, another approach would be where SAP could be the trigger point and ABAP proxy can control the offset variable and execute the looping of the service interface so multiple calls are made to the API.

SAP PO Message Download tool

2023-12-26T23:34:57+01:00

Introduction

Integration support activities often require communication with support team for third-party systems. If there are any problems with inbound or outbound messages it is most useful to obtain message payloads for futher inspection. This inspection may be done internally or forwarded to a third party. This means exporting some messages directly from SAP PO Message Monitor (Java stack). Downloading 5, 10, 20 or even 50 messages may be manageable. However when number of messages does higher than 100 it is not possible to proceed without a tool.

In order to download and package messages efficiently I have developed a specialized tool -- SAP PO Message Download tool. This command-line tool allows you to download messages directly from SAP PO system given a list of message IDs (stored in one text file). Files are downloaded and put into ZIP archive file for easy handling. Tool supports multi-threading, message grouping and saving raw data as returned by SAP PO.

Example use case

Minimal required options are as follows:

(-ids <file.txt>) — text file containing list of message IDs to download

(-connection <file.txt>) — text file containing connection data for SAP PO

Below is an example run of the tool:

PO message are sucessfully downloaded

Folder structure inside created ZIP archive

Message payloads

I would recommand also specifying -log option and -stage options. They allow to specify which LOG and STAGE versions respectively must be saved.

All available options (can be accessed by running downloader --help)

Usage of downloader.exe:

  -connection string

        Required. Path to connection file (contains systems address, username and password)

  -groupby string

        Group payloads by message ID, message version or both (default "version")

  -ids string

        Required. Path to a list of message IDs to download, one message per line.

  -log string

        Comma-separated list of log versions which must be exported. Supports standard version names (BI, MS, etc) and special values (all, none, json, jsonsend, jsonrecv). See details in documentation.  (default "all")

  -nocomment

        If specified, no text comment will be added to ZIP file (applies to -zip all).

  -opendir

        Open destination folder in Explorer when download process ends

  -output string

        Destination folder to save exported payloads (default "./export/")

  -raw

        If specified, raw contents (multipart message format) be saved as payload

  -stage string

        Comma-separated list of staging version numbers (0, 1, 2, ...) which must be exported. Special values (all, last, none) are acceptable. See details in documentation. (default "all")

  -statsonly

        If specified, only statistics on available message versions will be displayed. No actual download will happen.

  -threads int

        Number of parallel HTTP download threads (default 2)

  -xiheader

        If specified, XI header will be saved as payload

  -zip string

        Mode of compression for exported payloads. Available options are: (n)one, (f)ile, (a)ll (default "all")

Please refer to full documentation for detailed description of each option.

Useful resources

Full documentation with all avialable command-line options is available at Github repository

Released binaries are available at Github repository releases.

Any comments and suggestions are welcome here and at Github repository.

Thank you

Test Scenerio - ProcessDirect

2024-01-02T09:06:07+01:00

Scenerio:

Customer Order data is coming from sender using SOAP adaptor. CPI should generate order_no acc. to the given format. After generating order_no we need to add a field company_name. After this we need to check the action is Pending/Not_Available/Delivered.

If its pending then its end the flow, if its delivered then it direct to another IFlow using Process Direct in which we are generating TransactionId according to the given format. One its generated it should send the mail to the customer and the company admin mail, if its Not_Available it should end and send the mail to the customer and admin that your order is not available.

Order_no: random alphanumeric string of length 6 and concat it with quantity and Item as below.



Example: Item:- xyz, Quantity: 1 => Order_no = AB12CDxyz1



TransactionId:- Random alpha character string of length 10 and concat it with the Order_no.



Example: ABCDEFGHIJAB12CD1xyz

Steps:

Create an IFlow connect with sender using SOAP 1x adaptor as it is one way communication.

Add message mapping pallete and add source and target xsd as per the data.

Source XSD:

<?xml version="1.0" encoding="utf-8"?>



<!-- Created with Liquid Technologies Online Tools 1.0 (https://www.liquid-technologies.com) -->



<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">



  <xs:element name="Order_root">



    <xs:complexType>



      <xs:sequence>



        <xs:element maxOccurs="unbounded" name="Order">



          <xs:complexType>



            <xs:sequence>



              <xs:element name="Orderno" />



              <xs:element name="Cust_Name" type="xs:string" />



              <xs:element name="Cust_Add" type="xs:string" />



              <xs:element name="Item" type="xs:string" />



              <xs:element name="Action" type="xs:string" />



              <xs:element name="Quantity" type="xs:unsignedByte" />



              <xs:element name="Email" type="xs:string" />



            </xs:sequence>



          </xs:complexType>



        </xs:element>



      </xs:sequence>



    </xs:complexType>



  </xs:element>



</xs:schema>

Target XSD:

<?xml version="1.0" encoding="utf-8"?>



<!-- Created with Liquid Technologies Online Tools 1.0 (https://www.liquid-technologies.com) -->



<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">



  <xs:element name="Order_root">



    <xs:complexType>



      <xs:sequence>



        <xs:element maxOccurs="unbounded" name="Order">



          <xs:complexType>



            <xs:sequence>



              <xs:element name="Orderno" />



              <xs:element name="Cust_Name" type="xs:string" />



              <xs:element name="Cust_Add" type="xs:string" />



              <xs:element name="Item" type="xs:string" />



              <xs:element name="Action" type="xs:string" />



              <xs:element name="Quantity" type="xs:unsignedByte" />



              <xs:element name="Company" type="xs:string" />



              <xs:element name="Email" type="xs:string" />



            </xs:sequence>



          </xs:complexType>



        </xs:element>



      </xs:sequence>



    </xs:complexType>



  </xs:element>



</xs:schema>

Configure Message Mapping.

Custom Function Script:

import com.sap.it.api.mapping.*;

def String customFunc(String arg1){

  def chars = "ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789";

  def random = new Random();

  def sb = new StringBuilder(6);

  for (int i = 0; i < 6; i++) {

    sb.append(chars.charAt(random.nextInt(chars.length())));

  }

  return sb.toString();

}

Add Splitter to split the XML record and send to router.

Route 2 is ending as it is for Action Pending.

Route 3 is connecting to receiver using process direct adaptor.

Route 4 is connecting content modifier as we need customer mail id from the respective data.

Route 5 is default if the action not defined it should end the flow.

Configuring route 4 as below.

Configure Process-Direct.

Save and deploy this IFlow and create another IFlow for processdirect.

Configure Process Direct, give the same address as you give in previous flow.

Add mapping pallete and source and target xsd.

Source xsd should be same as the previous IFLOW Target xsd.

<?xml version="1.0" encoding="utf-8"?>



<!-- Created with Liquid Technologies Online Tools 1.0 (https://www.liquid-technologies.com) -->



<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">



  <xs:element name="Order_root">



    <xs:complexType>



      <xs:sequence>



        <xs:element maxOccurs="unbounded" name="Order">



          <xs:complexType>



            <xs:sequence>



              <xs:element name="Orderno" />



              <xs:element name="Cust_Name" type="xs:string" />



              <xs:element name="Cust_Add" type="xs:string" />



              <xs:element name="Item" type="xs:string" />



              <xs:element name="Action" type="xs:string" />



              <xs:element name="Quantity" type="xs:unsignedByte" />



              <xs:element name="Company" type="xs:string" />



              <xs:element name="Email" type="xs:string" />



            </xs:sequence>



          </xs:complexType>



        </xs:element>



      </xs:sequence>



    </xs:complexType>



  </xs:element>



</xs:schema>

Target XSD:

<?xml version="1.0" encoding="utf-8"?>



<!-- Created with Liquid Technologies Online Tools 1.0 (https://www.liquid-technologies.com) -->



<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">



  <xs:element name="Order_root">



    <xs:complexType>



      <xs:sequence>



        <xs:element maxOccurs="unbounded" name="Order">



          <xs:complexType>



            <xs:sequence>



              <xs:element name="Orderno" type="xs:string" />



              <xs:element name="Cust_Name" type="xs:string" />



              <xs:element name="Cust_Add" type="xs:string" />



              <xs:element name="Item" type="xs:string" />



              <xs:element name="Action" type="xs:string" />



              <xs:element name="Quantity" type="xs:unsignedByte" />



              <xs:element name="Company" type="xs:string" />



              <xs:element name="Transition_ID" type="xs:string" />



              <xs:element name="Email" type="xs:string" />



            </xs:sequence>



          </xs:complexType>



        </xs:element>



      </xs:sequence>



    </xs:complexType>



  </xs:element>



</xs:schema>

Configure Mapping.

Custom Function Groovy:

import com.sap.it.api.mapping.*;

def String customFunc(String arg1){

  def chars = "ABCDEFGHIJKLMNOPQRSTUVWXYZ";

  def random = new Random();

  def sb = new StringBuilder(10);

  sb.append(arg1);

  for (int i = 0; i < 8; i++) {

    sb.append(chars.charAt(random.nextInt(chars.length())));

  }

  return sb.toString();

}

Add Content modifier to store the customer email.

Configure XML to CSV convertor.

Configure Mail Adaptor.

Save and deploy the IFlow. Change the log of both IFlow to trace in monitoring.

Open SOAP UI to trigger the data.

Refer below blog to use SOAP UI
https://blogs.sap.com/2023/09/21/sending-xml-data-using-soap-adaptor-to-mail-using-message-mapping/

Add sample data.

<Order_root>



<Order>



<Orderno></Orderno>



<Cust_Name>Sahil</Cust_Name>



<Cust_Add>xyz</Cust_Add>



<Item>Pen</Item>



<Action>Pending</Action>



<Quantity>1</Quantity>



<Email>abc@gmail.com</Email>



</Order>



<Order>



<Orderno></Orderno>



<Cust_Name>Dushyant</Cust_Name>



<Cust_Add>xyz</Cust_Add>



<Item>Notebook</Item>



<Action>Delivered</Action>



<Quantity>4</Quantity>



<Email>efg@gmail.com</Email>



</Order>



<Order>



<Orderno></Orderno>



<Cust_Name>Aman</Cust_Name>



<Cust_Add>xyz</Cust_Add>



<Item>Pencil</Item>



<Action>Not Available</Action>



<Quantity>2</Quantity>



<Email>ijk@gmail.com</Email>



</Order>



</Order_root>

Check the customer mail.I hope this blog helps you, if you have any concern or doubt, drop in the comment section.

Thanks

Dushyant

Self-subcribe to specific integration scenarios to receive push notification directly to device

2024-02-10T13:19:19.028000+01:00

Introduction

We usually use either SOLMAN, CALM, or in certain situations, even third-party solutions to notify responders of different error scenarios. The most common method of notifications is emails, the creation of work tickets, or direct posting to MS Teams channels. All these methods rely on the owners of these applications to configure the responder emails.

In this blog, we showcase the capacity of push notification that directly gives power to the end-users to subscribe themselves to either the completion or failure of integration scenarios - circumventing the entire approval and delegation process. Push notifications are also non-invasive in nature as they do not flood the inbox with emails. This tool also facilitates subscribers to view the error that has simply occurred in the transactions.

The intention of this tool is obviously not to replace CALM/SOLMAN, but rather complimenting those products with another added flexibility (of self-subcription).

Advantage of push-notification:

There are several advantages of push notifications over emails (under obvious specific conditions). Some of them are:

Push notification are easy to subscribe.
Push notification add urgency to the message.
Triggering mechanism can be fully customized.
Non-invasive (no spamming).
Mandatory interaction required - cannot be ignored.
Empowering the end-user to receive information outside the conventional delegation process.

Tools used to create application: SAP CAP and SAP UI5.

Architecture

Comparison of this tool (notification feature only) with SOLMAN, CALM.

As we can see above, this tool empowers business users to receive notifications directly to their devices when integration scenarios of interest are completed or fail. They can also view the logs of the message processing to view more details of the execution. However, this tool is not completely devoid of administration - the admin of this tool can view all the subscription that exists, and can also delete user subscriptions if required.

Above is the HLL architecture of the tool. This can be easily deployed to cloud foundry in BTP which has HANA cloud. Following are the salient features of the application:

User can self-subscribe to any integration flow and will get notified in case of completion or errors.
User can self-subscribe different scenarios to different device.
Administrator can delete the subscription of any user.

Demo

Conclusion

SAP BTP is all about delivering innovation for the clients. This app coupled with SOLMAN and CALM will further enhance the notification experience for the customers who wants to be informed in the occurence of important events in mission critical interfaces. Now never miss an event.

DM Deepankar Bhowmick to discuss more interesting ideas around integrations and implementation of highly customized solutions.

Integration Advisor: Using the Pre-Transformation feature within a Mapping Guideline (MAG)

2024-02-15T17:09:35.581000+01:00

Introduction

Hello dear SAP Integration community,

In this Blog I want to show how to use one of the powerful features in Integration Advisor - the "Pre-Transformation". This feature allows to transform the source Message Implementation Guideline (MIG) structure which significantly simplifies the logic between source and target within the Mapping Guideline (MAG).

In this case a shipment based advanced shipping notification which is a key document in collaboration between suppliers and customers is exchanged. A SOAP message is send from SAP S/4HANA which must be transformed to UN/EDIFACT and send to the specific Trading Partner.

Please note that the scope of this blog does not describe how to create and qualify MIGs. As a starting point you can refer to this blog: Create a customized interface using MIG editor

Real world challenge

The shipment on the source side consists of multiple item segments, one with the gross details, multiple with package details and multiple with product details. They are all on the same segment level.
However, one package can contain multiple products. And that is how the target side is expecting the content.

Ideally, we should transform the source message in such a way that we group all products together which belong to one package.

Solution

Looking at the source payload, for each PRD item an additional segment <HierarchyRelationship> is created pointing to the relevant PKG:

And that is the information we need to do the Pre-Transformation.

In this case we have following relationship:

PKG ID	PRD ID
10	150, 200, 160, 220, 230
70	170
90	180
110	190
130	210

So 5 Packages and 9 Products whereas one of the packages contain 5 products.

Let's jump into the MAG:

What do we want to do exactly?
We want to copy the item segments qualified with PRD into the item segment qualified with PKG where the IDs are matching.
Which can be achieved by the following:

Simulation

Let's see what the result looks like.

Here on the right side (After Pre-Transformation) we can see that inside Item (Package) another node has been created - Item_gq_PRD_Copy. The first package with ID=10 has 5 Item_gq_PRD_Copy elements (see the yellow highlighted area). Inside the first package the first product has the ID=150. Now let's look at the second product:

Here we can see that it has the ID=200. And this matches with the table above.

Conclusion

In this blog article we showed the powerful and easy to use feature of the Pre-Transformation, where we transformed the source structure in such a way that it matches the structure of the target which expects to group all products belonging to one package.
Especially in this case, the Pre-Transformation helps to avoid building complex mapping logics which is also an essential aspect and which will be beneficial for operations.

Catalyst for Efficiency: Revolutionizing SAP Integration Suite with AI and Automation

2024-02-18T08:38:49.249000+01:00

I) Introduction:

While there are already many blogs online about message monitoring reports in the SAP Integration Suite, I want to add my own perspective and share some useful files for developers. In today's world, Artificial Intelligence models (such as Gemini and ChatGPT) and automation are becoming important everywhere, even in SAP.

Have you ever found yourself in need of checking a daily transactional report at your enterprise business? With the SAP Integration Suite, there's a handy tool called message monitoring for just that. However, here's the snag: after a while, the transaction seems to disappear. Many companies desire these reports emailed (for logs) and seek suggestions for failed messages, especially in cases of failed transactions.

Picture this: you rely on these reports, but they mysteriously vanish. Frustrating, isn't it? Well, fear not! Artificial Intelligence (AI) and Integration Suite (IS)-API have the solution. They detect transaction issues and offer solutions, alleviating your time and stress burdens.

In this blog, we'll explore how we can revolutionize SAP Integration Suite reports, making your job simpler and more efficient. Let's dive in!

II) Agenda:

Cost Background: Explaining the Financial Aspect
Overview: Exploring the Background Story
Technical Architecture Diagram: Visualizing the System Design
Technical Implementation: Step-by-Step Integration Details
Conclusion: Reflecting on the Key Takeaways and Future Directions
Additional Resources: Providing Research Material Links for Further Exploration

III) Cost Background: Explaining the Financial Aspect

While SAP offers a multitude of features including HANADB with Fiori screen report, ALM, SAC, and analytic tools, it's important to note that the solution discussed here is a zero-cost option for accessing reports via email. The only scenario where additional expenses may arise is if AI suggestions are required for productive use. Apart from that, the daily report functionality is completely free of charge when utilizing the solution outlined below.

IV) Overview: Exploring the Background Story

Imagine Tamil Selvan, a newly hired SAP Analyst at XYZ organization. One of Tamil's primary responsibilities is to compile and send a daily report of failed transactions to the relevant teams. Each morning at 8 AM, Tamil diligently logs into the SAP Integration Suite to review the list of failed and escalated messages. He then meticulously copies these details into Excel tables, which he shares with the technical team for investigation. Concurrently, the Application Management Services (AMS) team logs a ticket for further action.

This daily routine consumes a significant amount of Tamil's time, typically ranging from 1 to 1.5 hours. Extrapolating this across a week, Tamil spends approximately 7 to 10.5 hours dedicated solely to this task. Over the course of a year, this translates to a staggering 336 to 504 hours invested in creating these reports.

TimeFrame	TimeSpentPerDay	TimeSpentPerWeek	TimeSpentPerYear
Daily	1 - 1.5 hours
Weekly		7 - 10.5 hours
Yearly			336 - 504 hours

Considering the broader perspective, Tamil's annual commitment to generating these reports amounts to nearly two months of full-time work for individual client. Additionally, this is merely the initial step in addressing the identified issues. Following the report creation, the support team invests another 30+ days in diagnosing the problems and implementing solutions, often requiring additional iterations.

This inefficiency is striking; Tamil alone dedicates nearly 48 days per year solely to report creation, not including the subsequent resolution efforts by the support team. It's evident that the current process is time-consuming and resource-intensive, highlighting the urgent need for optimization.

The forthcoming blog aims to revolutionize these workflows, promising to enhance efficiency by over 98%. By implementing the proposed improvements for automation iFlow, the number of days spent on these tasks will be drastically reduced to Zero days, providing much-needed support to consultants, and expediting issue resolution processes.

V) Technical Architecture Diagram: Visualizing the System Design

VI) Technical Implementation: Step-by-Step Integration Details

Before proceeding, please ensure the following prerequisites are met:

Obtain the API key by registering on the ChatGPT website. Please purchase credit for production use.
Enable the Integration Suite API plan within the SAP BTP entitlement.
Obtain the mail server credentials from the respective domains. For educational purposes, Gmail is used in this example.

Step 1: Establishing an Integration Package with Proper Naming Conventions, Followed by iFlow Creation within the Artifacts.

Step 2:

Step two has been divided into three sections, each detailed below:

Section-A: Setting the Parameters, Creating the Queries, and Calling the APIs
Section-B: Establishing Conditions to Determine the Response Route
Section-C: Iterating Through the Responses

Section-A: Setting the Parameters, Creating the Queries, and Calling the APIs

Configure the parameters mentioned above in the content modifier. These parameters serve as the initial declarations for the iFlow properties, which will be utilized in later stages within the Groovy scripts.

The Groovy script above enhances the query to filter statuses such as failed or escalated. Additionally, it incorporates a manual flag check. For instance, if the manual flag is set to true, the configured value in the iFlow will be used. Conversely, if the manual load flag is set to false, the script will utilize the last successful runtime to retrieve results from the Integration Suite API.

Utilize the message processing log API to retrieve the pertinent response from the Integration Suite for escalated and failed messages. Refer this link: https://api.sap.com/api/MessageProcessingLogs/resource/Logs

Section-B: Establishing Conditions to Determine the Response Route

Verify whether the inbound response contains valid records. If the record count is valid, proceed with further actions. Otherwise, transition it to a completed state with a marker indicating zero records.

Section-C: Iterating Through the Responses

One of the notable features in the SAP Integration Suite is the Iteration Splitter (IS), which allows us to iterate through messages and obtain their respective IDs. These IDs can then be used to query additional APIs within the Integration Suite using exchange parameters and the XPATH mechanism. Below is an example where we capture the messageGuid to fetch more details from subsequent APIs within the Integration Suite.

Step-3:

Step three is divided into three sections, outlined as follows:

Section-D: Utilizing the messageGUID to retrieve the relevant message details.
Section-E: Employing the messageGUID to retrieve the relevant error message from another API.
Section-F: Leveraging Artificial Intelligence (AI) to receive suggestions for errors.

Section-D: Utilizing the messageGUID to retrieve the relevant message details.

Utilizing the OData protocol to retrieve pertinent details from the Integration Suite server involves accessing artifact information and transaction status. This includes identifying the iFlow name and message GUID, aiding developers in locating transactions within the message monitoring dashboard.

Operation: Read (GET)
Resource Path: MessageProcessingLogs(MessageGuid='${property.MessageGuid}')
Query Option: $select=MessageGuid,CorrelationId,IntegrationFlowName,Status,TransactionId,LogStart,LogEnd,Sender,Receiver,CustomStatus,LogLevel,PreviousComponentName,LocalComponentName,OriginComponentName,IntegrationArtifact,ApplicationMessageId,ApplicationMessageType

Section-E: Employing the messageGUID to retrieve the relevant error message from another API.

Ensure to utilize the HTTP protocol when accessing error message details through the SAP API, as it currently supports the HTTP protocol for this purpose. While it's possible that this method may transition to being embedded within OData entities in the future, for now, HTTP remains the preferred protocol.

Address: https://<HOST>.it-cpi004.cfapps.ap11.hana.ondemand.com/api/v1/MessageProcessingLogs('${property.MessageGuid}')/ErrorInformation/$value

Store the returned message in the "error" property, as indicated above. The subsequent step involves utilizing this property value in the AI models to generate the response.

Section-F: Leveraging Artificial Intelligence (AI) to receive suggestions for errors.

In this section, we leverage the openAI models to provide suggestions for the errors encountered in the systems.

Address: https://api.openai.com/v1/chat/completions
Protocol: Http

Utilize the provided script to capture the AI-suggested response and store it in a property named "openAIResponse."

Store the AI response in the “AISuggessionForError” property in the content modifier. And set the below XML format in the Content modified body

The XML payload resulting from message processing will be merged with the original payload, facilitating the creation of a consolidated report. This report, presented in a table format, enhances the readability and presentation of the details for email recipients.

Step-4:

Step four is subdivided into two sections, each outlined as follows:

Section G: Gather the response, and execute message mapping.
Section H: Generate HTML content for report creation and initiate email dispatch.

Section G: Gather the response, and execute message mapping.

In this section, we are gathering the responses from the respective sources. Since we are utilizing iteration splitter and multicasting, we have collected and halted the loop by employing a gather functionality.

During this gathering process, additional components may be added, which may not be suitable for message mapping. Therefore, we are using a Groovy Script to remove the unwanted headers using Groovy to remove multi tag script.

With the message mapping described above, the consolidated report has been formatted in a manner suitable for HTML. This formatted report includes tables, headers, and relevant information, providing a detailed and beautified result set.

Section H: Generate HTML content for report creation and initiate email dispatch.

Creating an HTML table response with Groovy to include transaction errors, iFlow names, AI suggestions, and job details.

The HTML content is delivered via the mail adapter from the Integration Suite, providing automated daily reports for failed and escalated transactions, along with Artificial Intelligence (AI) suggestions.

Step-5:

The program automatically generates an email containing details of the report, including failed and escalated transactions. Additionally, it provides solutions for the failed transactions within the report, facilitated by AI.

If you find this information helpful, please consider clicking the "Like" button on this blog and sharing your thoughts in the comments section below. You can also connect with the author on their LinkedIn profile: [Author's LinkedIn Profile]

VII) Conclusion: Reflecting on the Key Takeaways and Future Directions

Embracing Core Concepts of the Integration Suite
Grasping the Fundamentals of AI and Automation within SAP Integration Suite
Simplifying Error Handling Reports and Utilizing AI for Issue Identification and Resolution
Prioritizing Understanding of Business Problems, Root Cause Analysis, and Storytelling for Accessibility to All, Regardless of Technical Background

VIII) Additional Resources: Providing Research Material Links for Further Exploration

Duplication of Target Nodes in Integration Advisor (Group Nodes)

2024-02-20T09:28:19.740000+01:00

Introduction

Recently, we have introduced a new feature in Integration Advisor for the duplication of target nodes. This feature allows the duplication of leaf as well as group nodes of a target Message Implementation Guideline (MIG) in the Message Guideline (MAG) editor. This feature helps in special mapping situations where you have two sources which must be mapped to (multiple instances of) the same target node.

In this blog post, I will show a scenario which illustrates some of the benefits of this new feature when applying it to the duplication of group nodes. In a follow up article, a scenario with leaf nodes will be presented.

Scenario

As an example we use the following scenario: Assume you have a source MIG based on UN/EDIFACT message ORDERS (version D.21B S3, e.g.) which shall be mapped to an SAP IDoc ORDERS.ORDERS05. Furthermore, you agreed with your partner, which sends the UN/EDIFACT ORDERS message, that they can either use the DTM segment in the header to specify the expected delivery date for all items or the DTM segment of each item separately. However, on your own side you want to have the expected delivery date in segment E1EDP03 of each item independent of the decision of your partner.

Challenge

Now start the mapping design in the following way: You map the child DTM segment of segment group SG29 to E1EDP03. This would give the expected result when your partner sends the DTM segment with each item:

But what happens if the information is contained in the header? Then E1EDP03 will remain empty. Somehow you would like to map the header's DTM segment to E1EDP03 as well, but that was not possible so far.

Solution

Now, our new feature kicks in: You can duplicate the E1EDP03 group node at the target side and map both DTM segments to different duplicates. This looks as follows:

Now, you can map the header's DTM segment to the new duplicate and you are done. On message level both duplicates look the same, there are only distinguished in the MAG editor:

How to do it on your own?

Create a MIG based on UN/EDIFACT message ORDERS version D.21B S3 as source MIG (see Creating a New Message Implementation Guideline). Then select segment group SG29, the child DTM of SG29, and the 2380 fields of both DTM segments (header and line item). As last step you qualify both DTM segments with qualifier 2005 and value 2 (Delivery date/time, requested), see also Qualifying Nodes.This should look similar to the source MIG shown in the screenshots above. Then create a second MIG based on SAP IDoc ORDERS.ORDERS05 (version 1809_FPS02) as target MIG. Select nodes E1EDP01 and E1EDP03 and all child nodes of E1EDP03. Similar to the source MIG qualify the E1EDP03 node with qualifier IDDAT and value 002 (Requested delivery date (customer)). The resulting MIG shall look like the target MIG in the screenshots above.

Now you can create a MAG using both MIGs (see Creating a New Mapping Guideline). Before you can draw the mapping lines you can now duplicate the node E1EDP03 of your target MIG: In Edit mode hover over the E1EDP03 node, press the overflow button, and select "Duplicate":

In the duplicate editor add one duplicate by pressing the "Add" button and give the new duplicate a speaking name so that you can recognize it later:

After pressing the "Apply" button you can use the new duplicate and design your mapping:

Note that we also used the date time mapping feature of Integration Advisor in this example (see Date Time Conversion). Now you can simulate the mapping with the attached example payloads:

Summary

In this blog article we showed how we can use the new duplicate target nodes feature for solving a mapping challenge which previously was not possible. In a follow up article we will present another use case where in contrast to this example leaf nodes instead of group nodes are involved. We also would be happy to know more about your use cases for this new feature.
Please, share your ideas and feedback in a comment. Furthermore, you can follow the SAP Integration Suite topic page to get to know more about Integration Suite in general, or read other posts on Integration Advisor. You can also follow my profile if you want to read similar content in the future.

Appendix

In case you agreed with your partner that they can use the DTM segment in the header to specify the expected delivery date as default for all items but can override that date via the DTM segment of single items, the situation becomes a little bit more complex but can still be solved with Integration Advisor: Just use the conditional mapping, delete the mapping line between the groups DTM [2005 = 2] in the header (source) and E1EDP03 [IDDAT = 002] [1] (duplicated target node), and add a new mapping line between the groups SG29 (source) and E1EDP03 [IDDAT = 002] [1] (target). Then you can use the field 2005 of the line item as a conditional node for the new group-to-group mapping by drawing a line from it to the same target node E1EDP03 [IDDAT = 002] [1]:

Finally, enter

not(boolean($nodes_in/D_2005))

as a condition. This will create the target node instance only if the DTM segment of the line item is not available in the corresponding line item. I attached a sample payload also for this case.

PGP Encryption/Decryption using Java code inside payload

2024-03-01T10:51:37.554000+01:00

In this blog, I will retrace the steps that I have used to encrypt and decrypt payload coming inside message tags using PGP encryption/decryption. After many searches and tries, I was able to find a blog by Sandeep using Bouncy Castle,
https://community.sap.com/t5/additional-blogs-by-members/pgp-encryption-decryption-using-java-code/ba-p/12912768
This is an update to the same blog where I have worked around the mentioned trick without using Bouncy Castle to add the encrypted payload within the messages.

For OpenPGP encryption and decryption, the requirement that I had was to convert the generated message through BCM(Bank Communication Management) by first encrypting with PGP encryption and then converting to base64 while having this within the payload.

INBOUND flow

Download the necessary libraries required.
bcpg-lw-jdk15on-1.70.jar
bcprov-lw-jdk15on-1.70.jar
pgplib-3.2.3.jar
com.sap.xi.mapping.tool.lib_api.jar
com.sap.xpi.ib.mapping.lib.jar

You can get the first 3 libraries from the below link
https://didisoft.com/java-openpgp/
The other 2 libraries are sap standard libraries used in Java mapping or any UDF concerned, if required I will also try to attach the same on edit.
Next step, you have to generate your keys, I have used GPG4WIN 3.1.9 to generate keys

Post your keys generation, you will have 3 keys, one public key from the bank and 2 keys generated at your end, one public and one private.
You have to store the keys in the OS folder such that your Java code can access the keys, I have mentioned the path in which I have stored them for your reference. You have to use SKR for private keys and PKR extension for public keys.
```
/usr/sap/XXX/X00/<your_custom_folder>/privatekey.skr
```
I have used Eclipse for my Java code development, as currently NWDS is not available. Below is the reference path of the package I have used, I have inserted keys within the package and reference libraries which I have uploaded.
package content
reference libraries
Below is the encryption Java code that I have used, I have used many "getTrace" code which is for my reference, you can remove them or add additional ones based on what you prefer during testing.

package z001;

import java.io.InputStream;
import java.io.OutputStream;
import com.sap.aii.mapping.api.*;
import java.io.*;
import java.util.Base64;
import com.didisoft.pgp.PGPLib;
public class encrypt extends AbstractTransformation {
	 @Override

	    public void transform(TransformationInput transformationInput, TransformationOutput transformationOutput) throws StreamTransformationException {
		 try{     
		       
			    PGPLib pgp = new PGPLib();
			     String privateKeyFile = "/usr/sap/XXX/X00/<your_custom_folder>/privatekey.skr";
			     String privateKeyPassword = "<your_key_password>";

			     String publicEncryptionKeyFile = "/usr/sap/XXX/X00/<your_custom_folder>/bankkey.pkr";        
			     
		        InputStream inputStream = transformationInput.getInputPayload().getInputStream();
		        
		        BufferedReader inpxml = new BufferedReader(new InputStreamReader(inputStream));
		        getTrace().addInfo("input received");
		        StringBuffer buffer = new StringBuffer();
				   String line="";
				   while ((line = inpxml.readLine()) != null)
				   {
				   buffer.append(line);
				   }
				   String org_msg=buffer.toString();
				
				   OutputStream outputstream = transformationOutput.getOutputPayload().getOutputStream();
				   
				   getTrace().addInfo("encrypt");
				   
				   String signedAndEncryptedString = 
					          pgp.signAndEncryptString(org_msg,
					                                   privateKeyFile, 
					                                   privateKeyPassword, 
					                                   publicEncryptionKeyFile);
				   
				   getTrace().addInfo("encode");
				   
				   byte[] bytes = signedAndEncryptedString.getBytes(); 
				   String encodedString = Base64.getEncoder().encodeToString(bytes);
//					   int msg_length = org_msg.length();
				   getTrace().addInfo("finalstructure");
				   String target_msg = "<?xml version=\"1.0\" encoding=\"UTF-8\"?>"+"<ns0:MT_bank_Pay_Request xmlns:ns0=\"http://x.com/bank_Payment\">"+"<paymentBase64>"+encodedString+"</paymentBase64>"+"</ns0:MT_bank_Pay_Request>";
				   outputstream.write(target_msg.getBytes());
//this is to get the final target message that we have converted
				   getTrace().addInfo("finalstructure"+target_msg);
		 }
		   catch (Exception ie) {
		  }
		      
	    } 
}

This will convert the final message below

<?xml version="1.0" encoding="UTF-8">
<ns0:MT_bank_Pay_Request xmlns:ns0="http://x.com/bank_Payment">

<paymentBase64>"your encoded and encrypted string"</paymentBase64>

</ns0:MT_bank_Pay_Request>

OUTBOUND flow
This is the response from the bank side that I was receiving, here in responsebase64 I had the original file content response, which needed to be decoded and decrypted.

<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Vendor_Pay_Response xmlns:ns0="http://x.com/bank_Payment">
   <referenceId>1</referenceId>
   <profileId>2</profileId>
   <statusCode>3</statusCode>
   <statusDesc>5</statusDesc>
   <responseBase64>6</responseBase64>
</ns0:MT_Vendor_Pay_Response>

For decryption, in the below Java code, you can see the original content (which is encrypted and encoded) is within the responsebase64 tag, if blank I am generating a different XML response, but if non-blank I will be consuming the payload within SAP PO. Integration response will be generally provided by the bank side, you can add the dummy payload as same as the response you are having from the bank.

package z001;

import com.sap.aii.mapping.api.*;
import java.io.*;
import java.util.Base64;
import com.didisoft.pgp.PGPLib;

public class decrypt extends AbstractTransformation {
	@Override
	public void transform(TransformationInput transformationInput, TransformationOutput transformationOutput)
			throws StreamTransformationException {
		try {
			PGPLib pgp = new PGPLib();
			String privateKeyFile = "/usr/sap/XXX/X00/<your_custom_folder>/privatekey.skr";
			String privateKeyPassword = "<your_key_password>";

			InputStream inputStream = transformationInput.getInputPayload().getInputStream();
			OutputStream outputstream = transformationOutput.getOutputPayload().getOutputStream();

			BufferedReader inpxml = new BufferedReader(new InputStreamReader(inputStream));
			getTrace().addInfo("input received");
			String originalFileName = "";
			StringBuffer buffer = new StringBuffer();
			String line = "";
			while ((line = inpxml.readLine()) != null) {
				buffer.append(line);
			}
			String org_msg = buffer.toString();
			String s3 = org_msg;
			String isFound = "";
			String headerstatus = "";
			String headerdesc = "";
			String responsebase64 ;
			headerstatus = s3;
			headerdesc = s3;
			responsebase64 = s3;
//I have used index here as my response was having status code and message
//which i have capture in local variable.
			headerstatus = headerstatus.substring(headerstatus.indexOf("<statusCode>") + 12);
			headerstatus = headerstatus.substring(0, headerstatus.indexOf("</statusCode>"));
			getTrace().addInfo(headerstatus);

			headerdesc = headerdesc.substring(headerdesc.indexOf("<statusDesc>") + 12);
			headerdesc = headerdesc.substring(0, headerdesc.indexOf("</statusDesc>"));
			getTrace().addInfo(headerdesc);
//orginal response was coming after <responseBase64> tag which is capture here
			responsebase64 = responsebase64.substring(responsebase64.indexOf("<responseBase64>") + 16);
			
			getTrace().addInfo(responsebase64);
			
//I am checking here if response is there or not, if not i am making a custom xml
			if ( responsebase64.indexOf("</responseBase64>") == 0)
			{

				isFound = "N";
			}
			else
			{
				responsebase64 = responsebase64.substring(0, responsebase64.indexOf("</responseBase64>"));
				isFound = "Y";
			}
				
				
			getTrace().addInfo("truecheck" + isFound + responsebase64);
			if ( isFound == "Y" ) 
			{
				getTrace().addInfo("ifcheck");
				org_msg = org_msg.substring(org_msg.indexOf("<responseBase64>") + 16);
				org_msg = org_msg.substring(0, org_msg.indexOf("</responseBase64>"));
				getTrace().addInfo("beforedecoding" + org_msg);
				byte[] decodedBytes = Base64.getDecoder().decode(org_msg);
				getTrace().addInfo("decoded");
				String decodedString = null;
				// Get the string of decoded byte array
				String s = new String(decodedBytes);
//		  String encrypted = "";
				decodedString = s;

				getTrace().addInfo("beforedecryption");
//this is the decryption code, you can use it based on ur use case
				originalFileName = pgp.decryptString(decodedString, privateKeyFile, privateKeyPassword);
//end of decryption code
				getTrace().addInfo("decrypted" + originalFileName);
			}
			
			else 
			
			{
				getTrace().addInfo("elsecheck");
				String so = originalFileName;	
				if (so == "") {
///if the code is blank					
					originalFileName = "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\r\n"
							+ "<ns0:Document xmlns:ns0=\"urn:http://x.com\">\r\n" + "<paymentresponseBase64>"+"FAILED"+"</paymentresponseBase64>"

+ "</ns0:Document>";
				}
			}
			String target_msg = originalFileName;
			getTrace().addInfo("finalstructure" + target_msg);
			outputstream.write(target_msg.getBytes());

		}

		catch (Exception ie) {
		}
	}
}

Note:
I have used the above code based on my use case, you can play around with the Didisoft libraries and choose what fits best. For the adapter level, many modules and blogs are available that can be used to do the encryption and decryption.
Keep track of the expiry of keys, would be helpful for you as a change in year-end activity.

Move SAP Cloud Integration (CPI) Artifact/app content through SAP Cloud Transport Management

2024-03-03T09:20:43.232000+01:00

Overview-

SAP Cloud Transport Management is a multi-tenant-aware application that guarantees tenant separation while streamlining the management of application-specific content and development artifacts. This means that you can use SAP BTP to effectively manage software deliverables across accounts in different environments (such Neo and Cloud Foundry), safely transferring them across different runtimes while keeping tenants unique from one another.

Pre-requisites-

Subaccount -

Integration Suite Subaccount (Alias DEV, QAS and PRD/ DEV and PRD) respectively

1. Enable Cloud Foundry environment

2. Entitlement Access:

a. Integration Suite

b. Process Integration Runtime

Cloud Transport Management Subaccount

3. Entitlement Access:

a. Cloud Transport Management

b. Content Agent Service

Set-up details-

Navigate to the option Transport Node-

Check transport node description and set-up-

Navigate to the transport route-

Navigate it to Landscape visualization-

Steps to move Artifact:

Go to cloud integration-

To transport the desired package, click on button Transport –

Fill in the comment in the space and click on Transport-

If the export of the package content is successful, then the below message will be popped up-

To import the transport in PRD, Login into the Cloud transport tenant Click on Transport Node.

Select the PRD Node, then select the transport Request and click on button Import Selected.

Status of the transport can be verify from column status.

Conclusion-

We discussed how to transport/move the artifacts via CTMS and set-up details.

Related informations-

https://help.sap.com/docs/cloud-transport-management

https://help.sap.com/docs/cloud-transport-management/sap-cloud-transport-management/what-is-sap-cloud-transport-management

Please share your feedback and your thoughts. Write back to me for questions and queries.

Thank you.

Analyze Your SAP PI/PO System Before a Migration to Integration Suite

2024-03-05T14:30:56.817000+01:00

Before you can create any SAP PI/PO migration you need to plan and budget for a migration project. It is not an easy to do task and there are a lot of factors you should consider.

SAP has their migration assessment tool, that you can trigger to fetch data about your current system and landscape. I strongly encourage you to run it and get the details from it. The more perspectives you have on your integration, the better.

At Figaf we also have our report over your landscape. It does not come with any timeline on how long it should take to process each migration. It is something that is up to you to process with your landscape.

How Figaf collects data

Once you install Figaf and it connect to your SAP PI/PO system it collects a local version of all objects. Then it links all objects to so we got a tree of the objects. This is the same as SAPs tool does.

You can use our free migration edition, which will also help you test the migration and allow you to try our migration tool. You can install Figaf on a laptop for a PoC or on BTP for productive usage.

Figaf report

Once data is collected, you can generate a report like the following with all data.

You will need to go through and find:

The different types of adapters used. It is mainly the first time you connect with an adapter that it will cost you time.

Number of different modules you need to support and how critical it is

Number of EDI interfaces

Find problems that cannot be migrated

Once you have gone thru the list it becomes easier for you to estimate how many interfaces you need to migrate.

The small differences

With the projects we have been working with we have found that it is small details that makes or breaks if a migration will work. Some of the recent challenges we have come up with are:

Local function in a message mapping that are using Imported Archives

Message mapping that links to an Imported Message. Something we have only seen in old mappings.

And you will probably find a lot of other cases

In our latest release (2402) of Figaf we have created a option to callow you to create your own rules via Xpath or Regex. Then it will find all objects in your ESR or Directory that matches this. On a call we should the team in about 5 minutes how to create a new rule to cover checking for the second case. Then we could see less than 10 mappings were affected so no need to automate a workaround. If it was 20-50 we may have considered improving to fix this case.

For 1. Figaf allows you to extract the UDF to a groovy script as we do for Function Libraries. This gives you a way to edit and manage the content much more accessible.

To create a new rule check the following guide

I hope this will be a part of your migration toolbox.

Pilot project

The assessment is not something that can stand alone. Running a pilot project where you migrate some integrations with the different options SAPs, Figafs or manual migration will give you much more data about how to get started.

Also consider the effort of moving it into production and all the steps involved, like testing and go live considerations.

What’s New for SAP Integration Suite – February 2024

2024-03-12T09:22:05.281000+01:00

Before going into the highlights of our innovations, we are thrilled to inform you that SAP Integration Suite has been recognized as a Leader in the latest Gartner Magic Quadrant for Integration Platform-as-a-Service (iPaaS) for the fourth consecutive time. We are convinced that we have been received this recognition for our commitments to deliver a top-tier customer-centric integration solution, the ability to accelerate business outcomes through prebuilt content, ongoing innovation, the global geographic strategy, and readiness for the future. And a big thanks also goes to you in supporting us with all your great feedback. For more details checkout the blogpost and the SAP News article.

SAP Integration Suite highlights are:

JMS receiver adapter: property to identify sending integration flow
Inspect resource consumption through SAP Cloud ALM/SAP Focused Run
Call to action: Upgrade to new version of third-party connectors
Duplicate nodes on target side in a MAG
Definition of more complex code value mapping scenarios
Add metadata for OData-based API artifacts deployed on Edge Integration Cell
Enhancement of security standards in API Management
Policy templates in API Management
Distributed tracing in advanced event mesh
Direct consumption of SAP S/4HANA Cloud events in advanced event mesh

Cloud Integration

JMS receiver adapter: property to identify sending integration flow

We have extended the JMS receiver adapter by storing a new SAP_IntegrationFlowID property. It contains the ID of the integration flow that has sent the message through the JMS receiver adapter. The JMS consumer can use this property to define steps depending on the sending integration flow ID. Refer the documentation.

Inspect resource consumption through SAP Cloud ALM/SAP Focused Run

Inspection of your resource consumption has been available since the middle of last year. Now you may analyze the utilization of database and system resources through the health monitoring application of SAP Cloud ALM and SAP Focused Run. For troubleshooting bottlenecks caused by integration flows you may jump directly to the Inspect section of the Cloud Integration monitor.

Call to action: Upgrade to new version of third-party connectors

As per SAP note 3001980 the following previous adapter versions are deprecated since end of 2020: Salesforce, Amazon Web Services, Microsoft Dynamics, SugarCRM. There haven't been any new features or enhancements for these previous adapter versions. After the upcoming Apache Camel upgrade, the adapter versions will no longer run.

Action is required from the customer's side. Check all your tenants to see whether you have any kind of the above adapters still deployed. Please undeploy and delete the adapters. In case of question reach out to annemarie.kiefer@sap.com.

B2B Integration

We have extended the mapping functionality of the Integration Advisor capability to offer you more flexibility.

Duplicate nodes on target side in a MAG

When designing B2B integration scenarios you may have situations where certain information within the source structure needs to be mapped to only one node in the target structure. Now the mapping guidelines editor of the Integration Advisor capability enables you to duplicate group or leave nodes and map each source alternative to one of the reproductions. Refer to the documentation.

Definition of more complex code value mapping scenarios

You are now able to define local or global mappings of multiple code values at the source side to one code value at the target side. The value function now supports N:1 cardinality code value mapping ease e.g., situations where you have to map multiple partners or currencies.

API Management

Add metadata for OData-based API artifacts deployed on Edge Integration Cell

You can now supply an EDMX specification for API artifacts (API-led integration flows for deployment on Edge Integration Cell), that are based on OData APIs. This allows you to easily specify additional integration steps based on the resources of this API. See the detailed documentation.

Enhancement of security standards

As always, our intention is to offer the highest security standards to avoid attack vulnerabilities. Therefore, we encourage you to use strong certificates, and will no longer accept uploads to the Trust Store of weak customer-owned self-signed certificates or certificate chains used for mTLS handshakes. Consequently, the OpenSSL security level has been increased to level 2. See a comprehensive definition of security level 2 published on the OpenSLL site. For additional details please see note -3418201.

Policy templates

We have filled a small gap when applying policy templates to an API proxy. Default fault rules or post-client flows available within a policy template will now also be appended to the API proxy. Refer to the documentation.

Event-driven Integration

We have news regarding SAP Integration Suite, advanced event mesh our offering for distributed network of event brokers and sophisticated features.

Distributed tracing

We have extended SAP Integration Suite, advanced event mesh with a distributed tracing capability. Now you are able to trace the the lifecycle of events through OpenTelemetry, from the producing application across one or multiple event brokers to the receiving application.

Direct consumption of SAP S/4HANA Cloud events

We have an update regarding the event sources. We have enabled the direct consumption of SAP S/4HANA Cloud events into SAP Integration Suite, advanced event mesh without any intermediate hops. SAP S/4HANA Cloud customers may leverage SAP Integration Suite, advanced event mesh for very large projects, where performance is crucial. Read the documentation.

How to stay tuned to recent and upcoming innovations?

The SAP Road Map Explorer is your one-stop shop for all SAP Integration Suite innovations. You can easily check out the latest innovations and follow what is planned for the following quarters. All recent innovations also cover under the tab Features further links to blogposts or documentation.

We also refer to the complete list of new releases in our documentation: What’s New in SAP Integration Suite.

And if you have not heard of our monthly webinars, I suggest you sign up to get an invitation to the upcoming ones. Our team of Product Management experts host these webinars to showcase the latest and greatest updates regarding all SAP Integration Suite capabilities. The webinars are hosted on the last Tuesday of every month and the next one is already scheduled for February 27th.

In case you have missed our last monthly webinar, don’t worry. Visit 2024 Learning Sessions for SAP User Groups on SAP Integration Suite for all recordings, presentations, and Q&As.

Are you aware of the Release Navigator for SAP BTP? It consolidates release information across SAP BTP products and services easing you the way to find product release related notes, blogposts, and webpages. For your convenience use the direct link to the SAP Integration Suite section of the Release Navigator.

Benefit From The New 'Process Hierarchy Assignments' App in SAP Cloud ALM for Implementation

2024-03-19T16:33:41.013000+01:00

'Process Hierarchy' enables users to define common process landscape which is used across SAP Cloud ALM tenant.

This blog outlines how to manage and track your process hierarchy assignments in SAP Cloud ALM, with a spotlight on introduction to the new analytics application called 'Process Hierarchy Assignments'. This application provides a unified overview of process hierarchy and its assignments across your implementation projects. Before delving into the details of new application, let's briefly recap for managing process hierarchies in SAP Cloud ALM.

Defining Process Hierarchy

A process hierarchy is a structured representation of processes within an organization or system. You can break down complex processes of your organization into smaller components to create multiple levels or layers of nodes. Each level of process hierarchy nodes represents different stages or components of a process. To learn more about Process Hierarchy, you can visit Help Portal.

To create or edit process hierarchy in SAP Cloud ALM, admins can assign the role 'Process Hierarchy Author' to themselves or other team members in user management app.

Once you have the role authorizations, you can create the Process Hierarchy structure in the 'Process' app or simply upload via Excel. More information about how to upload process hierarchies via spreadsheet can be found in this Blog Post..

Assigning Project Elements

Once the process hierarchy structure is created, the assignment of hierarchy nodes is possible in various applications. You can assign hierarchy nodes to your Solution Processes, Requirements, Tasks and Documents in their respective applications. Assigning these entities to process hierarchy will enable clarity, accountability, and efficient tracking at the hierarchy level in your implementation.

Tracking in 'Process Hierarchy Assignments'

Process Hierarchy Assignments is a cross-project report that offers granular structure of process hierarchy nodes, along with the status of its assigned elements allowing for deeper insights into relationships.

Process Hierarchy Assignments can be launched from the 'Cross-Project Overview' page.

Where to find Process Hierarchy Assignment Apps

Here you can analyze assignments of your Solution Processes, Requirements, Tasks and Documents that may belong to different implementation projects, to specific process hierarchy node. The first column present the tree structure of your defined process hierarchy nodes and the next columns display number and status of assigned elements.

You can also utilize the expand or collapse functionality on individual node to adjust the view based on the granularity of levels of hierarchy you need or simply use 'Expand All' / 'Collapse All' icons on top right to adjust the view.

Process Hierarchy Assignments App

Use the settings to personalize the displayed columns. You can choose the entities you wish to include in the columns and their order as well.

Use 'Settings' to personalize the columns

To delve deeper, for instance, into a specific node, you can activate the side panel by clicking on the arrow. The side panel will then display the list of assigned elements grouped by projects. You can then navigate through different tabs to view the entity list.

For further drill down, the app also provides forward navigation. For instance, in the requirements tab, if you wish to explore requirements in the realization status and check their testing status, you can simply select the requirements and navigate to requirements traceability.

View details in the side panel to forward naviagte

Here are the upcoming enhancements planned for Process Hierarchy Assignments app. Stay tuned for further updates!

Adding filters to narrow down results for specific Projects, Scopes, and Process Hierarchy Nodes.
Adding filters to display hierarchy nodes with assigned Solution Processes, Requirements, Documents, and Tasks in specific statuses.
Adding filters to display hierarchy nodes with specific Document types and Task types assigned.
Introducing anomaly detection, such as identifying nodes with no assigned project elements.

First run of SAPs Pipelines for Integration Suite

2024-04-02T11:40:52.518000+02:00

I saw the pipeline concept for SAP Integration Suite and wanted to explore it.

It did look fairly complicated to get started with as I saw it but I had to dig in to learn and understand. Hopefully this guide will help you so you can explore it faster.

There are a lot of positives with the setup and the ability to control systems in such a way. It allows a simpler setup for handling the processing of messages and restarts. Separating mapping logic from retry processing making it easier to build solid integration.

It adds some complexity to the process and challenges monitoring and handling changes in the setup. You can do it via API calls, which is not ideal. I’m sure it can be automated in some way.

Once you have processed a message that is being split, you will see the following messages being processed.

You can follow the guide below to see the vide of the concept.

How to get started

Note: You can run the following example without installing Figaf. But if you are working on a migration project our migration edition will bring a lot of value to your project.

It is a bit difficult to get started with the platform. You need some flows that can work and handle your scenario. So, hopefully, this guide will simplify the setup so that you can run it on your own system.

1) In your Integration Suite, go to Discovery and search for Process Integration Pipeline – Generic Integration Flows & Templates.

Copy and add it to your tenant.

2) Deploy Script collection and iflow 2-6 no configuration is needed for it

3) Download the sample package from Figaf here upload and deploy it

It contains a

HTTP endpoint to test with.
Dummy Endpoint a process Direct flow that mocks as an endpoint. You can configure how often it should create errors. You can change how often it should fail.
Two iflows have been migrated via the Figaf tool. Usually Figaf would migrate it with a receiver split but we have instead generated it as two separate iflows and added Process Direct to it. There is still routing in it, which should have been moving to the Receiver or Interface determination.

They should all be deployed.

4) Get the Bruno to use for HTTP testing

5) Get our collection here.

Unzip it, and import it into Bruno

6) Configure the environment with service keys for both API and for Messaging(run) the key for Message Run must have run enabled otherwise you need to change the setup.

Enter them in the environments page

7) Run the PD(partner directory) login

😎Run the PDInit to initialize the directory with some content

9) Send messages with the Send Message to see how the flow works

Hopefully, you should now see all the messages being processed on the monitor. If not then you have some time to process the different steps and learn where the processing fails.

Note: You can use the 03_PDClean to remove the object created in the process. Check if something is missing.

XSLT

We have just created some fixed XSLT for the mapping to the receiver and interface. For now there are now queries in it but it should be simple to add such conditions.

Receiver XSLT

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="3.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <xsl:template match="/">
    <ns0:Receivers xmlns:ns0="http://sap.com/xi/XI/System">
     <ReceiverNotDetermined>
       <Type>Default</Type>
       <DefaultReceiver>
         <Service>RL_Receiver_1</Service>
       </DefaultReceiver>
    </ReceiverNotDetermined>
    <Receiver>
        <Service>AsyncPartner</Service>
      </Receiver>
      <Receiver>
        <Service>ERP</Service>
      </Receiver>
    </ns0:Receivers>
  </xsl:template>
</xsl:stylesheet>

Interface XSLT

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="3.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <xsl:template match="/">
    <ns0:Interfaces xmlns:ns0="http://sap.com/xi/XI/System">
      <Interface>
        <Index>1</Index>
        <Service>/pip/Asyncpartner_line</Service>
      </Interface>
    </ns0:Interfaces>
  </xsl:template>
</xsl:stylesheet>

Note: This was orginal posted at figaf.com

SAP PI/PO migration? Why you should move to the Cloud with SAP Integration Suite!

2024-04-02T11:57:06.272000+02:00

Are you among the thousands SAP customers using SAP Process Integration / SAP Process Orchestration?

If yes, you’re aware that this product is impacted by SAP NetWeaver 7.5 maintenance strategy, as explained in this blog post: indeed, the maintenance of SAP Process Integration and SAP Process Orchestration will be extended in accordance with SAP NetWeaver 7.5, with mainstream maintenance until end of 2027 with option of extended maintenance until end of 2030.

Let’s consider that it typically takes a year to get business case approvals and then it takes time to convince stakeholders and cooperate in development and productive cycles: you should start your move to SAP Integration Suite in 2024 to be sure to have the migration completed by 2027. That’s why I’m happy to guide you on the path that will let you adopt SAP Integration Suite, the modern way of integrating your SAP and non-SAP systems for the best business outcomes.

What is SAP Integration Suite?

SAP Integration Suite is an integration platform-as-a-service – iPaaS – that helps you quickly integrate on-premises and cloud-based processes, services, applications, events, and data. With SAP Integration Suite, you accelerate innovation, automate more processes, and realize a faster time to value.

SAP Integration Suite helps you quickly connect systems, automate business processes, and harmonize experiences across the extended enterprise. It comes with:

Prebuilt integrations managed and updated by SAP and by our valued partners
Harmonized access to popular third-party cloud applications
Tools for designing, publishing, and managing APIs
AI-assisted development and integration optimization
Tools-based, guided approach to define, document, and govern you>integration strategy

To get an overview, watch our 4 minutes video What is SAP Integration Suite

To delve deeper into SAP Integration Suite, read our 44 pages Feature Scope Description.

With SAP Integration Suite comes SAP Integration Solution Advisory Methodology, which defines your proven path toward integration excellence to successfully move from SAP Process Integration / SAP Process Orchestration.

What is SAP Integration Solution Advisory Methodology

SAP Integration Solution Advisory Methodology has been created by our experts to provide a standardized approach to integration. With SAP ISA-M, you can accelerate your digital transformation and become an integrated intelligent enterprise.

Our methodology offers a comprehensive framework that helps accelerate hybrid integration platform design, safeguard integration projects based on SAP best practices, and enable an agile integration practice across your organization. As you answer the assessment questions, you’ll learn more about the five levels of maturity and gain insight into where your business stands – and what to do next.

With SAP ISA-M you raise your organization's integration maturity level, moving from ad hoc integration to a systematic approach based on well-defined integration standards:

You will find all the links to resources related to this methodology in Katrin von Ahsen’s blog post.

What is Event Driven Architecture?

Event Driven Architecture is more and more popular simply because the world is more and more real-time.

Let me share just 2 business examples of this

Inventories must be updated as soon as sales happen
Maintenance teams need to know of breakdown as soon as possible

Let me go back to the very basics to quickly introduce Event Driven Architecture aka EDA:

An event is a significant change in the state of a system.
Notification events or data events can be sent from the event source to inform other counterparts of the change.
A message holding the event description in an encoded format is sent through an event broker, in charge of properly distributing the events.
Event consumers have registered with the event broker and are informed of the event, so they can appropriately react to it.

From a business perspective, with EDA you take advantage of

Improved reaction time and lower costs through full automation of real-time business processes

Smarter business decisions based on up-to-date information
Open ecosystem across vendor boundaries
Organizational empowerment through social-media communication style

From a technology perspective, you benefit of

Loose coupling for flexibility and scalability
Improved fault tolerance using suitable patterns
Incremental growth and higher-quality operations through step-by-step addition of event consumers and event sources
Real-time technical integrations and extensions

In SAP event-driven ecosystem as it is today, Event Sources can be

SAP S/4HANA
SAP S/4HANA Cloud
SAP ERP
SAP SuccessFactors solutions
SAP Marketing Cloud
SAP Data Intelligence
SAP CPQ
other SAP solutions
third-party solutions

and Event Consumers can be

SAP Integration Suite
SAP Build
SAP BTP services and apps
SAP S/4HANA
SAP S/4HANA Cloud
SAP ECC using add-on
SAP BTP, Kyma runtime
SAP Data Intelligence
other SAP solutions
third-party solutions

And as the most powerful and reliable event broker, we bring Advanced Event Mesh.;/p>

What is Advanced Event Mesh?

Advanced Event Mesh for SAP Integration Suite is a complete event streaming, event management, and monitoring platform that makes software event brokers available as a service. With advanced event mesh you can create event broker services in minutes, build a model of your event mesh to design and help implement it, and monitor your services and event mesh to ensure everything runs smoothly.

Learn more on Advanced Event Mesh technical concepts in this blog post from Luiz Guilherme Cerqueira Campos.

This cloud platform incorporates best practices, expertise, and technology for event-driven architecture (EDA) on a single platform. As a SaaS solution, it provides:

everything you need to accelerate your organization’s EDA adoption, allowing you to fulfill modern use cases that demand real-time, intelligent event streaming
an intuitive, unified interface to design, deploy, manage, monitor, and govern your event streaming infrastructure (including the events that flow over it) in the most secure manner.

To delve deeper on Advanced Event Mesh, browse our Help Portal content on SAP Integration Suite, Advanced Event Mesh and learn with the missions available in SAP Discovery Center.

What about Edge Integration Cell?

Edge Integration Cell is an optional hybrid integration runtime offered as part of SAP Integration Suite, which enables you to manage APIs and run integration scenarios within your private landscape.

The hybrid deployment model of Edge Integration Cell enables you to:

Design and monitor your integration content in the cloud.
Deploy and run your integration content in your private landscape.

To learn more about how hybrid deployment works using Edge Integration Cell, see Hybrid Deployment Using Edge Integration Cell.

To compare hybrid deployment with the standard deployment model of SAP Integration Suite, see Standard Deployment in the Cloud.

Edge Integration Cell supports the following use cases:

Security or compliance use cases

In many enterprises, sensitive data must be managed and controlled inside the enterprise's firewall. In addition, there could be strict architectural restrictions and you want to keep your data within your private landscape.

Getting a migration path for SAP Process Integration / SAP Process Orchestration customers

SAP Process Integration / SAP Process Orchestration is used by many customers for ground-to-ground integration scenarios. Edge Integration Cell allows these customers to benefit from the newest innovations that come with SAP Integration Suite, with the option to design and monitor integration content in the cloud, and deploy and run their scenarios exclusively in their private landscapes.

In both cases, we recommend using a hybrid integration approach for enterprise-wide connectivity.

For more information about the supported features and limitations of Edge Integration Cell, see Edge Integration Cell Runtime Scope. Read more from Piyush Gakhar, in his blog post “Announcement: Hybrid Integrations with Integration Suite”. Read also Finny Babu’s “Next-gen hybrid integration with SAP Integration Suite & Edge Integration Cell – Introduction & Setup” and Ashutosh Kumar Singh’s “Edge Integration Cell: Design, deploy and manage APIs”.

How to move?

To get the latest information on the migration from SAP Process Integration / SAP Process Orchestration to SAP Integration Suite, we prepared a dedicated web page. You will learn about SAP Integration Suite capabilities, and evaluate top business challenges to streamline processes, enhance productivity, and simplify the way people, data, and systems work together. You will also discover pre-built integrations available on SAP Business Accelerator Hub: indeed, you can connect and integrate applications and business partners with thousands of pre-built integrations, connectors, APIs and more.

For more information on the new tools and the established services you can also check out this blog post from our expert Arti Gopalan.

And to facilitate this move, we bring you a comprehensive Migration Guide for SAP Process Orchestration.

This online document describes what you need to know when you want to migrate from SAP Process Orchestration to SAP Integration Suite. It covers a variety of topics related to the migration process:

Introduction to SAP Integration Suite: Before you start your migration, get to know SAP Integration Suite, learn about its advantages, and get an overview of the migration process from SAP Process Orchestration to SAP Integration Suite.
Landscape: Assess your existing integration landscape and plan your target landscape.
Connectivity: Learn how to move your connectivity options to the connectors and adapters of the SAP Integration Suite.
Security: Get an overview of the security aspects you must consider while migrating and how to manage them in SAP Integration Suite.
Error Handling and Logging Strategy: Learn about cloud-based error handling and logging strategies and understand the different approaches available to you.
Interface Governance: Understand how interfaces are governed in the cloud and how to manage them across multiple landscapes.
Interface Migration: Discover the different aspects involved in moving interfaces from SAP Process Integration and SAP Process Orchestration to SAP Integration Suite, as well as scenario and object assessment and how testing can be automated.

We also provide you with

12 months free regression test tool
SAP Migration Factory with 2-3 weeks of free service
SAP Services and Support offered in our Preferred Success and MaxAttention programs

And our valued partners are bringing powerful migration tools such as FIGAF and INT4.

Keep in touch!

Now, you should have access to all the information you need to consider your migration from SAP Process Integration / SAP Process Orchestration toward SAP Integration Suite.

To stay updated throughout the year, regularly browse our public roadmap for SAP Integration Suite and… feel free to follow me here and/or on LinkedIn to be notified of my next blog posts! 😉

SAP PO- Remove Double Quotes From Sent Request

2024-04-29T13:14:50.771000+02:00

Introduction:

In this blog, we have a scenario where data sent from SAP to an external system is in the form of Proxy To REST. An external system provides us with a REST API. We will send a request to this API using the POST method. In the request sent according to the API of the external system, there are integer values corresponding to the IDs field. These values, after passing through the XML type at the mapping step and transitioning to the converter step in the adapter, have double quotes added to them by the adapter. Consequently, the service returns a 400 bad request response.

Typically, these fields within the array correspond to an IDs field. In other words:

[
"IDs":6913,
"IDs":6915
]

In contrast, during triggering, they are sending all integer values within an array with commas between them, like so;

[6913,6915...]

As a result, the adapter incorrectly interprets them as separate key-value pairs with the key "IDs", leading to the addition of double quotes during JSON conversion.

Firstly, defining the IDs field as an integer in the adapter did not work because the PO (Process Orchestration) converts this request to a string due to the commas between the values in the sent request.

When we inspect the logs, we observe that in the step where the adapter converts to JSON, it adds double quotes as follows:

Step 1. XSLT

I decided not to perform the conversion operation in the adapter because I believe the error stems from that conversion process. By default, the structure outputted from the mapping step is in XML format. If we convert this structure to JSON in the mapping step and specify that this structure is an array, the issue will be resolved. To achieve this, I have written an XSLT.

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
	<xsl:output method="text" encoding="UTF-8"/>
	<xsl:template match="/">
		<xsl:text>[</xsl:text>
		<xsl:apply-templates/>
		<xsl:text>]</xsl:text>
	</xsl:template>
	<!-- Process the IDs element -->
	<xsl:template match="IDs">
		<!-- Convert XML content directly to JSON -->
		<xsl:value-of select="."/>
	</xsl:template>
	<!-- Match the delimiters to add commas -->
	<xsl:template match="IDs[position() &gt; 1]">
		<xsl:text>,</xsl:text>
		<xsl:value-of select="."/>
	</xsl:template>
</xsl:stylesheet>

Step 2. XSLT Import in PO

Afterward, I imported this XSLT file into PO as an imported archive.

Step 3. XSLT Mapping

Then, in the operation mapping step, I provided the imported XSLT file to the request mapping.

Step 4. REST Receiver Adapter

In a default proxy to REST scenario, XML is expected to be output from the after mapping step, so we usually check the option "Convert XML payload to JSON" in the adapter. However, in our scenario, we are sending a JSON structure from the mapping step to the adapter. Therefore, we will not check this option. Instead, we will simply select JSON as the Data Format to indicate that our request is in JSON format.

Step 5. Testing

After completing all the PO steps, our service is now ready for testing. We can send a payload from the "Send Message" step to proceed.

Adding Custom Fields to Migration Objects in SAP S/4HANA Cloud Public Edition

2024-05-03T07:51:35.354000+02:00

Introduction

SAP S/4HANA Cloud Public Edition is a cloud-based Enterprise Resource Planning (ERP) system that is built on the SAP HANA in-memory database platform. It is designed to provide businesses of all sizes with a comprehensive suite of enterprise management applications for their core business processes, such as finance, procurement, manufacturing, sales, and supply chain management, among others.

The need of custom fields in Data Migration

SAP S/4HANA Cloud Public Edition offers powerful tools for data migration, enabling businesses to seamlessly transition their data to the cloud. However, organizations often require additional custom fields to capture unique information critical to their operations. In this blog post, we'll explore the process of adding custom fields to data migration in S/4HANA Cloud Public Edition. From understanding the data model to configuring custom fields in the migration templates, we'll provide insights and best practices to streamline the migration process and ensure that your business's specific requirements are met. With the flexibility of custom fields, businesses can unlock the full potential of S/4HANA Cloud Public Edition and drive innovation in their digital transformation journey.

One of our key priorities within the PSA is to empower partners with proficiency in new technologies. As part of this initiative, we provide a training program known as the Go Live Experience (GLX). This training simulates a rapid implementation scenario for a distribution company. It encompasses various aspects including configuration settings, data migration, and testing scenarios, focusing on critical areas such as procurement, sales, and finance.

During recent GLX training sessions, participants frequently inquired about managing custom fields within standard migration objects during SAP implementation projects. In response to this demand, I have created this blog to offer a detailed, step-by-step solution. It is our hope that this resource will help you achieve your migration objectives.

Business Case

This simulated scenario requires to add a custom field to the sales order. This field will be included as part of the sales order header, is required to appeared in reporting, will be needed also in the sales order confirmation printout form as well as appear in the billing document. there might be the need to use this field in a potential integration so it will be also available for API usage while working with sales orders.

For more details see images below:

Sales order analytics enabled

Sales order API enabled

Sales order confirmation print form enabled

The custom field is enabled for billing documents

Once these changes are published into SAP S/4HANA Cloud Public Edition the field is created and extended into the corresponding places. Now we go into the UI Adaptation mode to select my available field and capture it during the execution of the business transaction. e.g. in this case the sales order creation.

As a result the field appears in the main screen

The expectation is to migrate existing sales orders; we proceed to create a migration project using local staging tables

To avoid mistakes during migration you need to "Check for Custom Fields" once this operation is run the system will add the custom field to the standard migration template.

You can see under the History Tab the executed actions/status; as well as the predecessors if any.

Proceed to Download this fresh template. Under the title Key user Extensibility Fields you will find the recently created field, in this case ZCustom_Field_DLEON

Continue with the standard steps to Upload File, Review Data, Mapping Tasks, Simulation and Migration.

See the migrated info for a particular order if you to the sales document header and then look into the Custom Fields tab.

We hope this is useful for your implementation. Please leave your feedback below

Thanks,

David Leon

Partner Solution Adoption

SAP Pipeline Concept and B2B TPM testing

2024-05-06T07:30:00.023000+02:00

Abstract

With the introduction of the SAP Pipeline Concept we now have a second large use case apart from B2B-TPM which allows processing different types of messages with a set of predefined generic iflows. This blog will show a few ways how automated testing of such scenarios can be set up of the box with Int4 Shield - SAP Integration Suite testing platform and how SAP Integration Suite customers already use it for such scenarios.

SAP Pipeline Concept and B2B TPM - multiple iflows

In the pipeline concept, each step corresponds to an integration flow (generic integration flows and scenario-specific integration flows). The generic integration flows are used across all integration scenarios and must only be deployed once while scenario-specific integration flows handle the scenario-specific message conversions and mappings.

File Source: https://community.sap.com/t5/technology-blogs-by-sap/introducing-the-new-pipeline-concept-in-cloud-integration/ba-p/13639651

Similarly the B2B-TPM the exchange is divided into sender communication iflows, interchange processing and receiver iflows.

File source: https://community.sap.com/t5/technology-blogs-by-sap/use-tpm-ia-ci-to-efficiently-manage-and-run-complex-b2b-transactions/ba-p/13565068

Cloud integration is very flexible in terms of modeling and running your integration scenarios allowing the design of a rich variety of integration patterns on the other hand for some types of scenarios we may want to use a more "formal" way or processing and this is there SAP Pipeline Concept and B2B-TPM scenarios come in handy with some of it's common advantages:

a) Provide commonly used restart capabilities
b) Simplifies operations by separating errors into different generic queues
c) Require lower number of JMS queues to take into account the resource limits
d) Simplify monitoring operations
e) Allow reusability of artifacts across multiple flows by using generic (Pipeline or TPM) iflow concept

SAP Pipeline Concept and B2B TPM - testing

Since those two frameworks are going to be used more and more and they involve several iflows to be tested
is there any way to automate the testing of such integration processes? With Int4 Shield - SAP Integration Suite testing platform, there out of the box we have several ways to implement automated testing of the SAP Pipeline Concept and B2B TPM. Let me explain, how they work.

Step 1

In both SAP Pipeline Concept and B2B TPM we're working with multiple iflows so we may want to inject the test messages into a specific iflow. This can be the first iflows but does not have to be as we may want to skip testing the initial iflow in some cases.

Figure - Int4 Shield inject test message options

Step 2

Now we need to decide what do we want to test. What are the options? Basically two:

a) we can either test the whole framework (SAP Pipeline Concept and B2B TPM ) from start to finish

b) we may want to test specific iflows of the whole framework (SAP Pipeline Concept and B2B TPM)

For this purpose Int4 Shield automatically enables Trace monitoring level on tested iFlows to be able to introspect processing inside of these steps.
Thanks to this Int4 Shield can validate payload content at any single execution block of the processing steps.

Figure - Int4 Shield inject test message and trace start with validation options

Step 3

Scenario 1 (single automation object) - for simple black box testing, Int4 Shield injects the message in the initial step and awaits for logs and payload to arrive at the final processing step, capturing the output payload, as it would be sent to a target system. Single test case and single automation object is sufficient for test and validation.

Figure - Int4 Shield validation option with a single automation object

Scenario 2 (combination of automation objects - API workflows testing) - thorough testing is made possible with more test cases that execute more validation steps. In a typical scenario there is separate validation of Step 2 - to check if payload input was properly processed by Step 1 logic, and for Step 3 - to validate the output payload after mapping is correct and routed to the expected channel.

Figure - Int4 Shield validation option with a a combination of automation objects - API workflow testing

SAP Pipeline Concept and B2B TPM - framework support

Int4 Shied testing concept for SAP Pipeline Concept and B2B TPM supports:

a) Multiple adapter types : SFTP, JMS, HTTP, IDOC, ProcessDirect, SOAP
b) Enabling unit testing of specific flow components
c) Testing business flows with Inputs and Outputs from different iFlows
d) Test complete SAP Pipeline Concept and B2B TPM execution with one test case
e) Capture and test intermediate results from specific iFlow steps
f) Test complete SAP Pipeline Concept and B2B TPM execution, validating document flow through the iFlows
g) Massive and automated test case creation
h) Test case loader - mass load of test files
i) Robotic crawler - automatic capture of historical data from another integration platform
j) Test scenario builder - linking multiple test cases into test scenarios automatically based on message content (e.g. document numbers)

Additional resources

B2B/TPM on SAP BTP Integration Suite migration (SAP PO, Boomi, EDI Providers and home-grown apps)

Int4 Suite for SAP BTP Integration Suite testing fully integrated with SAP Cloud ALM

4 big waves for API led strategies and SAP BTP Integration Suite explosive growth

There is no AI without API - Integration is the backbone of digital transformations

How do we adapt the PATCH method in SAP PO

2024-05-13T12:54:11.101000+02:00

Hello everyone,

I will explain how to adapt a REST service called with the PATCH method for use in SAP PO.

In an integration scenario triggered from SAP, if we have a REST link on the receiver side and this link is called with the PATCH method in Postman, we can easily adapt it in PO. This is because not all methods may be available in every PO system. If the PATCH method is not available in your PO system, you can follow the steps below.

1- When configuring, first, we create a Rest receiver adapter.

If there is no authorization in our Rest link, we do not select Basic Authentication. However, if our service authenticates with a username and password, we must specify it in this section.

2- We use our link in the Target URL section in the REST URL tab.

3- We should select POST as the Static Value for our Rest Operation.

To send a service from SAP using the PATCH method through the adapter, we need to add two module configurations in the Module section of the adapter.

4- Module Configuration:

overrideHttpMethod - PATCH

useSAPHttpLibrary - apache

After adding these modules, we can complete the Integrated Configuration steps of the service and trigger it from SAP.

We can easily adapt a REST service triggered as PATCH in Postman to be used in the adapter with the POST method in SAP PO.