on 04-11-2013 9:44 PM
Hi All, I have a requirement where I need to process a 2 GB file through SAP PI with mapping transformations happening in PI and post it to SAP ECC system. This is the data coming from POS (Point of Sale) system. I recommended volume for PI interfaces is not more than 5MB.Is there anyone who explain me the approach for this in PI?
Please write a script at the OS level to split the file into multiple record sets as per your needs keeping the same name with an numeric extension At the file adapter level, execute OS command before processing and you won't run into any issues
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My File adapter is going to throw a timeout error if I am going to read a 2GB file with Recordset, 2000 records. Please suggest.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As per your responses, I need to chunk the file and split the file into pieces of 5 MB with one interface and pick the each file and process it in a new interface.
My other approach can be with File adapter with Recordset, "n" records getting processed for each Message ID. Which is best approach to follow?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raja,
If I am going with Recordsets per Message -- Is the adapter engine going to hold the file adapter till the processing is complete?....If there is any error in processing one of my message ID in the middle,is it going to stop the remaining messages to get processed?....Please suggest
Unfortunately, In my case the POSDM system is a legacy database system where they can only send text files. It cannot send XML files and we need to schedule the File adapter in PI system after the batch job is executed by legacy system to place the file.
As soon as Records are divided into independent messages, there will be no dependency. If one message fails, others will not get stopped. Now the concern is if Source wants to resend the failed Record after correction along with other successful records, it may cause duplicate records at Receiver side. You need to check with receiver system, whether they can handle duplicates or not.
Hi,
a file adapter can theoretically process 2 Gig. But any mapping would collapse. You need to chunk the file.
/Udo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Udo,
We can chunk the file and send it to SAP system with no mapping transformations in PI but SAP will not need a simple file transfer from legacy to SAP it needs the data in an IDOC format with mapping transformations happening in PI and posting the data.
If we use chunk mode and split the file into pieces and process these split files separately, but we don't know how the chunk mode splits the file as it may break the record unevenly and you may lose the data when it reaches the limit specified in the chunk mode (i.e for example as 5MB).
Hi Shyam
Refer the below link
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shyam,
As per SAP, PI can process up to 1 GB for PI File adapter. But I am still skeptical. I want to go with the suggestion of Baskar, split it. Also always perform Bulk load testing, for these type of interfaces.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
2GB file is larger size. If possible you can split the file data into smaller chunks and do multiple transaction. This is better approach.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.