Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
This Blog gives you a brief overiew of CPI/HCI EDI Integration

SAP has released HCI EDI integrations for enterprise license account holders only

The technical procedure of HCI edi integration is almost like a see-burger or B2B ADD ON using splitter to split the messages and converter to convert edi to xml and there after mapping conversion


Step1: Download available schema (xsd) ex:850 PO from portal to local NFS





Step 2:-  Import the schema's to i-flow



Step 3:- Use EDI Splitter to split Interchange document and EDI to XML converter to convert EDI data to xml and mapping conversion to convert EDI XMl to IDOC XML




IFLOW - this needs to be modified as per requirements


Give all the required parameters mentioned in below help documents and maintain control number ranges and other inputs then execute checks for errors, deploy and test




Select 997 required or not required


Select if 997 control number needs to be created newly or use it from request EDI message


Select if you want to exclude or include optional AK3 and AK4 segments


EDI Splitter Configuration





NRO Configuration:-





Script to read NRO

import NumberRangeConfigException;
import java.util.HashMap;
def Message processData(Message message) {

def service = ITApiFactory.getApi(NumberRangeConfigurationService.class, null);
if( service != null)
def value = service.getNextValuefromNumberRange("NRO_NAME",null);
message.setHeader("NRO_NAME", value)
message.setProperty("Empty_String", '')
return message;



Control Segments


Set Control segments using run time values or constant


Example : Body of Control segments in Content modifier


<?xml version="1.0" encoding="UTF-8"?>
<n1:Interchange xsi:schemaLocation=" ASC-X12_810_004010.xsd" xmlns:xsi="" xmlns:n1="">
${header.ExtractedMessage}------------------> Note this is set in content modifier to capture incomming payload



Set Content modifier body by reading values using property

Example : Schema and Mapping





Additional Info

If you are importing map from PI/PO by default UDF will work at run time, you don't have to make any changes to UDF to convert to groovy or java script, however you will not be able to see the UDF code as you will get warning as shown below... here "shiftnegativevalue" is UDF imported from PI Map which works same as PI in runtime





Labels in this area