How to migrate Function Libraries

How to migrate Function Libraries

What to use for your migration of message mappings from SAP PI/PO to Cloud Integration?

That's a great question and there are two options for handling linked Function Libraries (FL):

  • Use the new FL object in Cloud Integration

  • Convert the FL into Groovy and use it in the mapping

 

Important note: For each FL you need to consider if it can be migrated and then perform the steps.

Figaf can handle both options depending on how they are handled.

Here is a table of the differences as of August 2023 between the functions

 

Groovy

Function Lib

Simple  function

X

X

Queue function

X

X

Parameters

X

p

Using Container

-

X

All values of queue

-

p

Missing input on a function

p

p

Init method

-

X

Imported archives

 

p

Changed syntax

X

 

Access PI data

-

-

 

I would expect that all items marked with "p" will be possible to resolve by SAP for the FL object. When they will be resolved is the question. And that Figaf can resolve the missing input on a function, in a short period if requested by customer. The other items will not be possible to resolve because the Groovy functions cannot be extended.

The biggest disadvantage with Groovy is that the Groovy syntax is a bit different in some cases. For instance, a "100$" in java is seen as a string in Groovy the $ is seen as the beginning of a variable. In Figaf we escape automatically this but there are other syntax changes that can be more challenging.

When you migrate with Figaf you can select how each of your FL should be migrated.

 

If you change you format the message mappings should use the Overwrite the shared artifact.

For the Groovy you will see warnings about how the FL is migrated and if there are things like container that is not supported.

No matter how you handle the migration, remember to test. 
    • Related Articles

    • Implement RFC Lookup in a migrated mapping

      If you have a Message Mapping with an RFC lookup then the migration will create a Groovy script with a mock function like the following. import com.sap.it.api.mapping.*; import com.sap.conn.jco.JCoDestination; import ...
    • Testing SAP PI to CPI Migrations

      In this article, you will see how you can test how the migration of your SAP CPI migration went.  We have recorded a video about how to create the testing ​ Create SAP PI Test case Find the ICO to select the recording from Create a Recording request ...
    • How to install Figaf to handle SAP PI to CPI migrations

      This guide shows you how to install the Figaf Suite, and enables you to create your first SAP PI to CPI migration.  It is recommended that you follow along in the video.  ​ Install the Tool Registered for the Trial on Figaf  and you will get the ...
    • FAQ: What kinds of problem will I face with my SAP PI/PO to Cloud Integration migration with your tool

      We are still improving the Figaf Tool to make SAP PI/PO to Integration Suite/CPI better. We often get asked what is not supported.  Many of the problems comes from the fact that it is two different environments that we try to convert artifacts ...
    • Transporting your migrated SAP CPI iFlows to production

      See how to handle the transport of your iFlow to production ​​ Here you will see how to transport your migrated and tested iflow into production. Create a landscape for the transport. It is possible to use only one system for the setup to see the ...