Skip to Content
Author's profile photo Former Member

Do you need a custom adapter in PI?

One of my responsibilities at SAP is to help our PI customer find solutions which are not readily apparent.  Some of the solutions may involve special mapping usages or adapter user-modules or how to access non-standard external applications/systems using standard adapters delivered with PI. 

However, there were times when the solution can only be met by a custom adapter which is not available with PI or from any of our partners.  Developing an adapter is not a trivial task, especially for first-timers.  The learning curve is quite high.  Based on some customer experiences, the total cost may exceed $500K from concept to production.  This is not something a customer can readily justify from the business-case perspective.  Only companies who plan to resell the adapter can justify the cost and recoup that kind of investment.

Then, through various colleagues, I found that SAP consulting actually offers such a service.  Yes, SAP consulting can develop custom adapters for customers.  This service is now a viable option for customers to explore.  Why?

  1. SAP consulting has been doing this for customers already.  The high learning curve is no longer there.  This means considerable savings.
  2. As an option, SAP consulting can perform the task remotely.  This can mean additional savings.
  3. SAP consulting has access to developers and application groups when additional technical information is needed.
  4. SAP consulting also has deep PI experiences and knowledge.  This is different from many of the companies that just develop adapters.  This allows them to understand your end-to-end process within PI and may even propose features and suggestions not thought of before and how to better leverage existing PI capabilities.

One of the adapters SAP consulting has done is the EBICS adapter for banking.  You can get more information on this via this blog:

Another adapter they have done is not blogged any place.  But, I was very much aware of it through a proof-of-concept project, and it has since been put into production.  It is a “splitter” adapter.  The adapter can process an arbitrarily large XML message, which can be in the GB range.  As an example, the adapter will split an XML message, which contains one header and many detail records, into multiple detail messages each contains the same header record.  This is not possible for the structure conversion of the File adapter, because the same header, which there is only one, must be repeated in all the messages.

If you have a need for a custom adapter, please do not hesitate to contact Lars Ulrich at .

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Hi Bill,

      We have a situation where we need to split a Big File into multiple files based on the content. Say for example, it has many line items for many distributors and I have to group these and split based on the distributors. We cannot do it in the Message Mapping as the message fails as it is big.

      We are using File adapter with Content Conversion. When we use the Content Conversion, the adapter will convert the payload to XML and so the payload increases 5-6 times. This is OK, but we are not able to process the file without increasing the HEAP memory.

      Ideally, A 100 MB file has 20 distributors, after splitting, it will be 5 MB per Distributor files for processing. we need to split the file as we can save the HEAP memory.

      One solution is to use a Custom Adapter Module to split the file in the Sender Adapter before Content Conversion so that One file can be sent as multiple messages.

      So is there any similar request made by anyone else? How do we deal with the situations like the above?

      Thanks for your help and time.

      Author's profile photo Former Member
      Former Member
      Blog Post Author


      Sounds like you may need a special adapter.  You can contact the person mentioned in the blog,, for more info.  Lars may have other suggestions.



      Author's profile photo Daniel Graversen
      Daniel Graversen


      You can use smaller tag names so instead of using <COMPANYCODENAME> you would use <T12> that will shrink the size of the file.

      You can also sent the file as text file and use a java mapping to split it. Then you would juse the soap adapter to sent the message to PI it self. that will save you some time in creating an adapter