File to idoc scenario with file size 16 MB

Hi experts
We are developing a file to idoc scenario.The file is a 16 mb CSV txt file.Is it feasible to poll a 16 mb file at a single shot or any mechanism can be followed which would split the 16 mb file into manageable size files so that it can be polled from the adapter engine side.Will there be any performance bottleneck fr polling 16 mb file .Plz provide help in this regard

Hi Sabyasachi,
There would be absolutely no problem , you need not worry. I myself am using a 16 MB master record file.
The problem only arises when you need to open this 16 MB file for into some errors or some other changes then invariably what happens is that my desktop hangs.
Regards
joel

Similar Messages

FILE TO IDOC SCENARIO WITH SCREEN SHOTS

can u please send me FILE TO IDOC SCENARIO WITH SCREEN SHOTS and do the needful for me

/people/ravikumar.allampallam/blog/2005/03/03/creating-purchase-order-idoc-through-xi
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Also have a look at these forum threads...
IDOC TO FILE SCENARIO
idoc to file scenario
I hope this answers your query.
regards
Sreeram.G.Reddy
Message was edited by:
Sreeram Reddy

File to idoc scenario with controls

I am working on file to idic scenario.
file has four types of lines :
Begin of file.
header.
items.
end of file.
each line has a element Record type and some other elements.for header record type is A , for item its B , for Begin of file its C and for end of file its D.
we have to check for every line that it should have record type as one of these four and if not so we have to send a mail through alert functionality.we have to send a mail which has all errors by checking the whole file for record types.we have to ignore these lines in the file and proceed with the rest.
how can we implement this?
regards,
rohit

Hi,
Please go through these links
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Thanks
Vikranth Khimavath

Reg File to IDOC scenario with Acknowledgment

Hi Experts!
In a File to IDOC scenario , how to get the acknowledgment back to PI after posting the IDOC to SAP system and send the acknowledgment to the sender system.
What setting needs to be done in Sap and PI? Is it better if we have a BPM or is it good to have another interface to pass the acknowledgment IDOC back to the file sender.
Regards,
Srini

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

IDocs not created in file to IDoc scenario

Hi all
I am trying this file to IDoc scenario.
File picked up successfully and sent to R/3 BackendBut Idoc is not postedthe status records
In /n we05 in R/3 Backend shows that EDI: Partner profile inbound not available
I created/tested all basics like RFC dest, port etc.
File service that I am using is a business service hence I am specifying a Logical system name in
Adapter specific Identifiers of the file service.
I disabled EDI_DC40 control tag record as IDoc adapter
takes care of it.
So at first I tried the configuration of IDoc comm. Channel by checking the Apply control record values from payload
But SXMB monitor gave an error regarding this control record tagI guess as we have disabled it so there wont be any values
for control record in payload (correct me if I am wrong).
So I unchecked the checkbox Apply control record values from payload and monitor showed up as successfully processed.
But in the backend I am getting this error regarding partner profile.
I also tried to use an existing profile (LS type) by modifying its inbound parameters to accept CREMAS Idoc.
But the error is as persistent as me
Pls help
Sudhir

Hi
Sender --> LEGACY, maintained in SLD (Logical system).
Receiver--> ENI maintained in SLD with logical sys name M700.
Partner Profile LEGACY maintained in R3.
Following is the IDocOutbound in SXMB monitor in XI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000001013</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPAXI</SAP:SNDPOR>
<SAP:SNDPRN>LEGACY</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPENI</SAP:RCVPOR>
<SAP:RCVPRN>M700</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS />
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY>DF57A2C0532811D9AD84000F206A031B</SAP:ARCKEY>
</SAP:IDocOutbound>
Control record of IDoc in R3
Tab: Typeinfo
 Basic type-->CREMAS03
 Message Type-->CREMAS
Tab: Partner
 Recipient
 Port -->SAPENI
 Partner Number--> M700
 Partner Type-->LS
 Sender
 Port -->SAPAXI
 Partner Number--> LEGACY
 Partner Type-->LS
Pls help
Regards
Sudhir

Lookup issue for File to Idoc scenario-- Urgent Pls.

Hi All,
Iam doing File to IDoc scenario with one file --> any of 3 R/3 systems.
Routing has to be done dynamically using a lookup file, based on the incoming GLN code and last character of the Order Reference number.
The last character of the Order ref Num will have A,B or C.
Where, ' A' for R/3 152 Client
             ' B' for R/3 142 Client
             'C' for R/3 132 Client.
1. PlantGLN_Routing lookup file :
DestinationSystem,   Plant GLNCode,       Partner Number,
A,                            5000243000473,         GDKDVRC152,
B,                            5000243000473,         GDKDVRC142,
C,                            5000243000473,         GDKDVRC132,
A                                 500034000487           GDKDVRC152,
B                                 500034000487           GDKDVRC142,
C                                 500034000487           GDKDVRC132,
By Using DestinationSystem and Plant GLN Code as lookup key --> I need to get the value of partner system.
2. IdocCtrlLookup
Purpose: To read the IdocCtrlLookup file to populate the Idoc control segment
Now based on the partner system from previous table --> I need to get the details of Sender Port , Sender Partner Type , Sender Partner Function , Sender Partner Number , Rx Port , Rx Partner Type , Rx Partner Function , Rx Partner Number.
Please help me how can acheive this scenario with the help of lookups.
Its very urgent.
Regards
Krupakar.

HI,
Here you would have to use one mapping for dynamic routing , based on this create IM and use it in receiver determination.
the another mapping is general to file to idoc.
see the dynamic routing link here
Dynamic Configuration of Some Communication Channel Parameters using Message Mapping -
/people/william.li/blog/2006/04/18/dynamic-configuration-of-some-communication-channel-parameters-using-message-mapping
Also if you know the field name the context object can be defined for partner no that can be used in receiver determination in condition. to particular partner no in receiver determination.
Regards
Chilla

How can I include the Header Information....for a File to IDOC Scenario

Hi,
I made a File to IDOC Scenario with DEBMDM06 for MDM>XI>SAP R/3. The Header Information in the XML File which is at the XI end is Missing. For that reason In Tcode SXMB_MONI we are getting an Error that "HEADER Information Missing: Message should Start with EDI_DC40" i.e the Header Information.
My Question is that whether we can do some changes in the Message mapping Step in the Integration Repository. I HardCoded the Few mandatory Fields that were there but it Again gave me the Same Error as above.
Can you please Suggest some Solution for this. Since the data is Coming in from MDM part the Header information is not there but It actually Important as it has got all the Port Information.
Kindly Inform me some Solutions.
Thanks & Regards
Somnath

Hi Suraj,
Thanks for ur Reply, but Since we are Doing a File to IDOC Scenario the IDOC DEBMDM is on the Right Side in Message Mapping and as U know it is Mandatory to Map an IDOC on the Right Part. EDI_DC40 is coming as it is there in the IDOC but our XML File Does not have that. If we Don't Map then it Becomes RED, which is an Error.
Furthermore in the Receiver Agreement we have put the Necessary Details such as Sender Service and Receiver Service along with the IDOC Communication Channels.
Can U give as a Better Insight on this Note how to check the Header Part as it is mandatory to MAP.We also tried to HARDCODE it by putting those Values and Mapping them to a Constant but it is Giving the Same Error.
Thanks and Regards
Somnath

File to IDoc Scenario: Idoc Status 50

Hello,
I have a problem in doing a File to IDoc Scenario with a simple XML file mapped to IDoc "CREMAS.CREMAS03". In the beginning, I got a status 56:"IDoc with errors added". Then I added a logical system (LS name of my sender)manually in "Display IMG";however, it didn't work. So I simply changed the logical system name of my sender to XI_00_800 which already exists in R/3. I tried the scenario again, then I got the status 50:"IDoc added". Looked like the IDoc still hadn't been correctly inserted as a record. May I ask what other steps or configurations do I need to do to get this scenario to work? Thank you.

Steve,
Moreover, I didn't create any partner profile. The "XI_00_800" partner profile is in the system all along. Should I create a whole new partner profile and point that to my sender business system?
You need not create it once again as it already exists. Normally , ALE configurations on an R3 system are the responsibiltis of the Functional Team. For instance , on our projects we are never given access to the End r3 systems and the Partner profile are created by the F'nal team itself.
Like I mentioned, ask your F'nal team why you are getting this issue. From XI side , there is nothing more you need to do.
Regards,
Bhavesh

File to IDoc Scenario exception handling

I have configured Time bound File to IDoc scenario with processing mode in Sender adapter as 'Delete'. And it is running perfectly. I am trying to add additional functionality to the scenario, i.e.,if a file does not exist on the ftp server, a mail should be sent to a recipient.
May be using Java proxy is not appropriate, as poll interval does not be accounted in Java Proxy and file server should be having Java runtime.
Please can any one suggest, how this can be acheived?
Regards,
Suraj Kumar

Hi Bhavesh,
What you have understood is correct?
Any way, I will come out in more detail.
My Ftp server: //yhsap/xi
File: xi_for_upload.txt
Sender Adapter: File Adapter using content conversion with processing mode as 'Delete' and poll interval is 600sec.
Simple Mapping is achieved.
Receiver Adapter: IDoc Adapter.
So, if file is not available in Source system, send mail to [email protected]
Can you suggest a suitable solution?
VasanthaKumar: After adding wait step in BPM, can you please illustrate me how to ping the ftp server and how to read whether file is there? Can you please explain in more detail.
Thanks & Regards,
Suraj Kumar

How to start an File- XI- IDOC -Scenario manually?

Hi,
we have a File->XI->IDOC -Scenario with a polling time of 60 minutes.
Now it should be possible, that the enduser can start this scenario manually (by report or something else), because sometimes the user has to edit the file and then he/she cannot wait till the loop restarts.
How can we manage it?
Regards
Wolfgang

Hi,
Wow - that's great!
BUT.... it's working only in XI/2004 >=SPS17. We have PI 700/2004s SPS7
Do you know the corresponding SPS for this feature in PI 700?
I wanna ask my admin to upgrade - it's a feature the enduser (special endusers) really needs.
Thanks a lot!
Regards
Wolfgang

IDOC is posting with Errors in File to IDOC scenario

Hi,
I did the File to IDOC scenario for CREMAS . IDOC is posting with Errors .. i.e. in the status record it was showing 56- EDI: Partner profile inbound not available ..
If I manually process that IDOC in WE19 , then it was processing successfully.. and in the we19 it was showing Inbound Processing : Port Not Maintained but even though manually it was posting fine...
any ideas regarding this will be appriciated.....
Regards
Babu

Please check whether you had done the following assuming your doing File to Idoc
Settings in your Business service for the receiving system
Please specify the RFC detination, SAP System and Client of the Receiving System in the adapter specific detials.
Settings in R/3
WE20 - Add the partner profile for the particular message type cremas and process code.
Your statement
" and that same logical system name had given as Message Specific Attributes in the Sender Business Sevice parameters in I.D "
Please do mention R/3 Details in the receiver business service or system.
Thnz

File to IDOC scenario : Error with mapping due to Context handling

Hi Experts.
I have a file to IDOC scenario which need your advice.
Source File structure as follows:
Control_Header <1:1>
Invoice_Header <1:unbounded)
Invoice_Line <1:unbounded)
Trailer <1:1>
Payload as follows capture from SXMB_MONI
- <Control_Header>
 <Key>999</Key>
 <TransactionID>RCTV</TransactionID>
</Control_Header>
- <Invoice_Header>
 <Key>000</Key>
 <BusinessUnit>HDB05</BusinessUnit>
 <InvoiceNo>64471</InvoiceNo>
</Invoice_Header>
- <Invoice_Line>
 <Key>001</Key>
 <UnitPrice>7.00000</UnitPrice>
 <Quantity>1.0000</Quantity>
 <GSTAmount>0.49</GSTAmount>
 <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Invoice_Line>
 <Key>001</Key>
 <UnitPrice>8.00000</UnitPrice>
 <Quantity>1.0000</Quantity>
 <GSTAmount>0.56</GSTAmount>
 <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Invoice_Header>
 <Key>000</Key>
 <BusinessUnit>HDB21</BusinessUnit>
 <InvoiceNo>6Y0575</InvoiceNo>
</Invoice_Header>
- <Invoice_Line>
 <Key>001</Key>
 <UnitPrice>49.50000</UnitPrice>
 <Quantity>1.0000</Quantity>
 <GSTAmount>3.47</GSTAmount>
 <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Trailer>
 <Key>TRL</Key>
 <TransactionID>RCTV</TransactionID>
 <TotalFeedLine>96</TotalFeedLine>
 <HashTotalValue>212.00</HashTotalValue>
</Trailer>
</ns:MT_EINVOICE>
Mapping as follow:
 IDOC
<Control_Header> -> <Control_Header>
<Invoice_Header> --> <Header_Invoice>
<Invoice_Line> ---> removeContext --> <Line_Invoice> this is the child node of <Header_Invoice>
<Trailer> -
> <Trailer>
The result of the using the above Payload get the following result which not wht I seek
<Control_Header>
<Header_Invoice>
 <Line_Invoice>
 <Line_Invoice>
 <Line_Invoice> *** This belong to the Invoice_Line of the second <Header_Invoice> at the payload
<Header_Invoice>
 <Line_Invoice> *** THis segment is empty
<Trailer>
I required the Line_Invoice to belong to the child of the second <Header_Invoice>, I have tried using
removecontext with splitVaue and collaspeContext but to no avail.
May I know what is my mistake on the mapping of the Invoice_Line to Line_Invoice>
Rgds
FNG

Hello,
There should be something that could correlate the Invoice_Header/Key and Invoice_Line/Key. In your example, both are the same for the first and data set. If the sample looks like the one below, it is possible to sort things by correlating the Invoice_Header key and Invoice_Line key
<Invoice_Header>
<Key>000<Key>
</Invoice_Header>
<Invoice_Line>
<Key>000<Key>
</Invoice_Line>
<Invoice_Line>
<Key>000<Key>
</Invoice_Line>
<Invoice_Header>
<Key>001<Key>
</Invoice_Header>
<Invoice_Line>
<Key>001<Key>
</Invoice_Line>
An example mapping could look like this
For Header
Invoice_Header --> Header_Invoice
For Line
/InvoiceLine/Key --> removeContext --> splitByValue:valueChanged --> Invoice_Line
The subfields of the invoice line would also follow a similar logic, you just need to use formatByExample --> splitByValue:eachValue so that the context levels are the same.
Hope this helps,
Mark

Problem with Sender service in File to IDOC scenario

Hello All,
Am doing a file to IDOC scenario.
I have configured the sending system as a party and added a business component, to the BC attached the service interface and also configured the sender Communication channel(CC) as file.
On the receiving end configured the R/3 system from SLD as the business system and configured the receiver CCl. Can see the R/3 logical system in the Adapter specific identifiers at business system.
Pushing the file get an error "Unable to convert the sender service to an ALE Logical System". But choosing "Take sender from Payload" in the receiver CC is resolving the problem, however the sender partner number remains the same as what I have mapped to the control record in message mapping (which is like hard coding).
My questions are:
1. Am I doing the correct config in terms of the scenario. (like using "Take sender from Payload")
2. I tried using identifiers at the party level to convert the sending system, but nothing seems to work. But sending system remains the same as the constant from mapping.
Suggestions would be very much helpful..
--Prashanth
PS: Have gone through many blogs and posts on the forums, but may be I did not see the correct thread. Apologies if I am asking this again.

Hi Prashanth,
refer the below discussion i think it will solve your problem.
File To Idoc scenario
Thanks

Idocs with errors added status-56 in file to idoc scenario- how to rectify

hi ,
in file to idoc scenario when i m sending the file from ftp server to IS Retail, file is successfully getting processed but the idoc is showing error ,when we see using WE05 tcode or BD87 , pl sugggest how to rectify it to make the status 53

Hi,
Have you configured the partner profile details? check these steps..
1. In the receiver system you must configure the partner profile for your sender system in WE20.
2. Add the IDoc message type to inbound parameters of the partner profile and configure the appropriate process code.
2. Fill the Logical system name for your senderservice-->Adapter Specific identifiers in ID.
<a href="/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi File-to-IDOC Scenario</a> By Venugopalarao
<a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> By Ravikumar Allampalam
Regards
San

Error while doing a File to IDOC scenario

Hi Experts,
I have created a File to IDOC scenario where in i have sent a file which has to pass data to ABSEN1 IDOC.I could see the IDOC reaching R/3 ,but with the status 56: "EDI: Partner profile inbound not available"
I have checked with all the configurations and couldnt find where it went wrong.
Kindly help me in this regard.
Thanks.

Hi
Check the inbound parameter and the process code.
To find Process code for IDoc use Tcode WE42.
ALE idoc trouble shooting use
Troubleshooting of ALE Process
look also this configuration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34

File to idoc scenario with file size 16 MB

Similar Messages

Maybe you are looking for