Skip to Content
author's profile photo Former Member
Former Member

Legacy-PI intergration

Hi All,

I have to integrate Legacy system to ECC using PI. So the flow will be Legacy ->PI -> SAP system.

The flow seems to be simple the file comes in PI and the same will get uploaded in ECC system. But here comes the catch, suppose there are some filed level changes in the XML file and now we only want to process the changed records and update the same in SAP.

The sender system want us to compare the last extract with the currrent one and then only send the changes to SAP system.

For example:

File1: Will be processed with all the 3 records

Name Age Hobbies

A 30 Golf

B 31 Tennis

C 32 TT

File2: in this only first 2 records needs to be send to SAP system becoz hobbies filed data is changed

Name Age Hobbies

A 30 Cricket

B 31 Football

C 32 TT

Request you to let me know how i can achieve the same requirement.


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    Posted on Jun 05, 2012 at 07:18 PM


    You also have option 3 that I would personally recommend: to implement the comparing logic in the receiver system. It should help you achieve better performance, since you do not use RFC Lookups (less connections between systems) and should be easier to implement. Once the data reach the receiver system, you can easily compare the data already saved with the ones you just received.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 05, 2012 at 06:53 PM

    Very simple.


    Legacy(File)----->PI(RFC Lookup)------>SAP.

    You need help from ABAP team to buld one RFC fucntion module which can evaluate the new record with old data(very much possible).



    Legacy(File)----->PI(RFC Lookup)------>SAP, but RFC look up returns old data based on key then perform validation at PI level.

    But i would recommend to use option1.

    Best Regards,


    Add a comment
    10|10000 characters needed characters exceeded

    • Yeah correct.

      Other approach is why dont you handle valdiation logic in ECC only because ABAP team can have more flexiblity to perform validation in Porxy program level before updating data in SAP Tables.

      I prefer this approach because it avoids RFC look up and you can avoid validtaion logic also.

      Your interface going to File to Proxy.

  • Posted on Jun 05, 2012 at 07:10 PM

    Raja already explained the ways... Every time you send record to ECC, validate with the backend system via RFC graphical lookup or some UDF to check whether that record exists or not. If not, then insert. This lookup logic should exist in the message mapping. Only downside is you need to check every individual record and if the file size is too big then this would slow down the processing time.

    Plus if you have any primary key or similar id in the table then you can retrieve all the existing records and make a single call to RFC instead of multiple calls... Use shabarish blog for this. Thsi would help improving the performance

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 05, 2012 at 07:38 PM

    >So we are looking for PI to handle this and send only the changed data.

    If you want to handle via PI then you have to do RFC lookup for validating the data. So you might want to see Shabarish blog mentioned above to retrieve multiple values using single lookup to avoid mulitple calls to RFC.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.