File to Idoc - EOF issue.

Hi,
   I am working on file to IDoc scenario. But facing a problem...
   The source file contains ..EOF.. as a last line in the file. Actually, there is no need to map it to any of the field in IDOC. Just I have created a element in the source data type and ignoring it...
But I am getting this following error message...
    Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR consistency check in recordset structure validation (line no. 43: missing structure(s) in last recordset
Please help me to resolve this issue...
Thanks in advance!!!
Regards,
Vivek LR

Hi,
R u using content conversion in file adapter.Check ur content conversion parameter it is not able to convert the file to XML structure.
wat do u mean by "I have created a element in the source data type and ignoring it... " I think u r not mapping it in mapping right?
chirag

Similar Messages

File To IDOC Scenario issue

Hello Friends,
I am facing an issue during File To IDOC Scenario.
Sender side: Text file
It contains data:
name,surname,7894561230 i.e. phone no.
My sendor data type is also desined in same way.
I am facing given below wrror in SXMB_MONI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_mm_file_to_idoc_</SAP:P1>
<SAP:P2>java.lang.NullPointerException</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>java.lang.NullPointerException thrown during application mapping com/sap/xi/tf/_mm_file_to_idoc_:</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In sendor file adaptor I am using 'File' as message protocol.
Should I have to use 'File content Conversion'.
I tested message mapping. It is working fine.
Kindly suggest me for above error. How I can resolve it?
Regards,
Narendra

It contains data:
name,surname,7894561230 i.e. phone no.
java.lang.NullPointerException thrown during application mapping com/sap/xi/tf/_mm_file_to_idocc
In sendor file adaptor I am using 'File' as message protocol.
Should I have to use 'File content Conversion'
can you tell in what format is your source structure? I mean is it an XML or a CSV file?
If it is a CSV file then you need FCC....but then in this case the error should have been thrown by the channel itself and the message wont have come till mapping step....
If your source file is really in csv format then apply FCC....many blogs, references are readily available on SDN.
Regards,
Abhishek.

PI7.1 File to Idoc scenario issue.

Hi,
We recently had an upgrade from PI7 to PI7.1.
When testing File to Idoc scenario ,we had an issue as below
Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
<Trace level="1" type="T">Error during lookup - com.sap.aii.mapping.lookup.LookupException: Error when calling an adapter by using the communication channel GeneratedReceiverChannel_RFC (Party: , Service: ED2_200, Object ID: a8f14398a9993dccadbe983d401f693a) The channel with object ID a8f14398a9993dccadbe983d401f693a could not be found in the Integration Server Java Cache. Check if the channel exists in the Integration Builder Directory and execute a refresh of the Java Cache.</Trace>
<Trace level="1" type="T">Error when parsing RFC Response - null</Trace>
<Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
This was working fine before upggrade.
Any changes required to be done in scenario?
Pls let me know.
Thanks,
Srinivasa

do a CPA cache refresh
http://hostname:port/CPACache/refresh?mode=full
also check if the object is visible in tcode SXI_CACHE..
also refresh the SXI_CACHE

Big File to IDOC - performance issue

Hi All,
I am trying to create scenario where I have a file with aproximately 10 000 rows. From each row I am creating one IDOC and want to send it to R/3. Interface looks fine - it is working, but it is killing XI box for some time and u cant access it.
Full scenario look like this
File -> BPM (for 1:n) -> IDOC
I tried to find some solutions for doing the workload smaller by splitting file to less lines (500rows per file) but then file adapter picks up all file and processed them in parallel. So this is new scenario:
BigFile -> XI -> File -> BPM(1:n) -> IDOC
I tried to put second file sender communication channel as EOIO but looks like this does not work - or messages from queue are processed to fast. When one message starts BPM another file message start to be processed.
Do You have any ideas on how to make it more responsive and less performance impact?
thanks in advance.
Dawid

Hi ;
Since mappings are processed by the J2EE Engine, the maximum available Java heap may be a limit-ing factor for the maximum document size the XI mapping service is able to process. Tests have shown that processing of XSLT mappings consumes up to 20 times the source document size (using identity mapping). The maximum available Java heap for 32bit JVMs is platform-dependent. Using 64bit JVM platforms is an option here.
Current maximum heap sizes 32bit
OS
Maximum heap (GB)
Linux
2
Windows
1.2 1.4
The Java heap is limited by the heap limit of the process (may be limited by address space because operating system code or libraries may also be loaded within the same address space). Also, Java internal memory areas such as the permanent space for loading Java classes must fit into the same address space.
Java VM tuning is one of the most crucial tuning steps, especially for more complex scenarios. For information about setting baseline JVM parameters, see SAP Note 723909. You must also take plat-form-specific parameters into account (for example, JIT compiler settings). The impact of Garbage Collection (GC) behavior especially may become a critical issue. Overall GC times for the J2EE appli-cation should be well below 5%. For more information about GC behavior and settings, see also SAP Note 552522.
Specific to XI is the fact that you sometimes need to process large documents for mapping or when using signatures. This can lead to excessive memory usage on the Java side. Therefore, you must observe Garbage Collection and the available Java heap in order to evaluate performance and pre-vent OutOfMemory exceptions. Since XI mapping is processed by stateless session beans that are called using a JCo interface, this may lead to a reduction of parallel JCo server threads within the JCo RFC Provider service of a J2EE server node (you can compensate for this by adding J2EE server nodes).
Mudit

File - XI - Idoc : mapping issue

Hello gurus,
I have a mapping issue:
I have a mapping between FICABillingNotification to FKK_EBS_DOC_TREE
Some fields are mapped one to one, others a mapped to constants.
But for some reason i don't know, not all fields get the right value.
For example:
Working:
Constant 1 --> BEGIN
Constant LS --> RCVPRT (Receiver Partner Type)
Not working:
Constant FILE-->RCVPOR (Receiver Port)
I had an other value the first time i tried it, but now i changed it to FILE but this value is not used by the mapping.
Any help would be welcome
Thanks
Thomas
Edited by: Thomas Pary on May 28, 2008 3:36 PM

This was allready done (sorry i didn't answered that question).
But Ok now i see, that for this RCVPOR the value of the constant "FILE" is mapped, and i can see it in the payload in SXMB_MONI after the mapping. But it isn't populated to the IDoc field :-s
Another problem is, that like the one said above, some of my values are not mapped :
<FICAExternalBilling>
--<DocumentHeader> mapped to EF1KK_EBS_DOC_HEADER
<BillFromId>25001254</BillFromId> mapped to REF_DOC_NUMBER
<PostingDate>20080520</PostingDate> mapped to POST_DATE
<DocumentDate>20080520</DocumentDate> mapped to DOC_DATE
<OriginTypeId>IV</OriginTypeId> mapped to EXT_DOC_TYPE
<ObjectType/>
<ObjectKey/>
<PendingCommitmentGroupID/>
<InvoiceReferenceID/>
<DisputeDocumentReferenceID/>
--</DocumentHeader>
The value of OriginTypeId is not mapped, but the value of DocumentDate and PostingDate are mapped.

Flat file to idoc mapping issue

Hi Gurus,
i had a flat file format in sender side as below:
H_ID     TYP_CODE    line_elemet      Quantity
5896 STANDARD                       1.transmitter    1
5896                  STANDARD       2.xxxxxxxxx           1
5896                   STANDARD      3.yyyyyyyyy 2
6895                  STANDARD       1.aaaaaaaaa        1
9436                  STANDARD       1.bbbbbbbbb          4
9436                  STANDARD       2.ggggggggg          3
The above file need to be send to an Idoc.
for which same header_ID values should create only one header segment, under that many a line segments should create as many line items appear on that header_id value.
Here my query is how to suppress the repetetive header values to create onlyone header segment. And how to create as many line_item segments as the number of line items appear.
points obvoius for the response
Thanks in advance,
Sekhar.

About map problem I suggest youn to see the following link that are really helpful to improve knowledge about mapping:
/people/sravya.talanki2/blog/2005/08/16/message-mapping-simplified--part-i
/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii
I suggest you to see the following link to learn more about mapping:
Mapping functionality in XI
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9202d890-0201-0010-1588-adb5e89a6638
SAP Exchange Infrastructure - Graphical_Mapping
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6658bd90-0201-0010-fbb6-afe25fb398d3
SAP Exchange Infrastructure - Graphical Mapping Exercise
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/fd5ebd90-0201-0010-d697-91374d5b5190
SAP Exchange Infrastructure - Graphical Mapping - Advanced
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/be05e290-0201-0010-e997-b6e55f9548dd
SAP Exchange Infrastructure: Mapping Patterns - Understand Context Handling in Message Mapping - Webinar Powerpoint
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f59730fa-0901-0010-df97-c12f071f7d3b
SAP NetWeaver Exchange Infrastructure Mapping Troubleshooting - Webinar Powerpoint
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e01e9400-9e81-2910-20a5-a862945a5e98
Mapping Lookups a RFC API
Mapping lookups - RFC API
XI 3.0 New Mapping Features
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8a57d190-0201-0010-9e87-d8f327e1dba7
I hope these links will be usefull.
Regards,
Salvatore

IDOC creation issue at XI side - File to IDOC

Hi Everybody,
I am working on a File to IDOC scenario (XI 3.0).
We have to create Orders in the R/3 System using this Interface.
Mapping used is Java.
I am using 2 Classes : Group and SendIdoc one below the other in the Interface Mapping:
Firstly by using Group Class I am Grouping the Records in the file and then creating the IDOCs by using the next class(SendIdoc).
In the production environment if we drop like 20 files at a time in the source NFS folder the number of IDOCs created are wrong.
Say for example, for the first file dropped expected IDOCs are 10 but only 8 are created in SXMB_MONI .However in the input payload (in SXMB_MONI) the entire text file is read.
When we put the files sequentially say one after the other is processed, the number of IDOCs created are fine.
This is very strange problem.
I tried changing the polling interval of the channel but was of no help.
Any parameters we need to set in the channel or XI system to overcome this issue?
Can someone help me out on this?
Helpful answers will be rewarded points.
Thanks & Regards,
RK

Hi ,
When you placing files sequentially its working fine menas there is no problem with Java Code,one morething use synchronize methods or thread programming in Java maps is not advisable.
as per my knowledge File adapter picking up the recodrs when its giving inout to Java map some thing misisng....
for one file you need to create multiple IDocs try use QOS EOIO or if its not working then try to use record set per message one like that,let me know.
Regards,
Raj

File to IDOC - issue with partner profile

I have done File to IDOC scenario and tested it end to end successfully. For same have done all require configuration setting in R/3 like defining logical System and partner profile. And it sends new IDOC successfully in R/3 with status code 50 (IDoc added).
But when I create new logical system and partner profile in R/3 and when I use same logical system in my above mention scenario then my new generate IDOC in R/3 return status code 56 (EDI: Partner profile inbound not available). But same scenario work fine with my earlier partner profile. Here I have done all require changes at adapter level like adapter specific identification and same new logical system I have update in SLD with my business system Logical System Name.

Hi Bhavesh,
Thanks for your reply.
In control record, I checked with sender and receiver partner. In this sender partner is new partner profile which I have created with port details. Receiver partner has logical system name which I have mentioned in my SLD for my receiver business system. But in receiver partner dont have any port details.
But still it has same problem.
-Sunil

Mapping issue in FIle to IDoc

Hello friends,
In file to IDoc scenario,
Source structure is
1: header
n: itemdetails
For Item details, IDoc structure has got 2 sub segments under E1EDP01 segment. as below.
E1EDP01
--E1EDP02
--E1EDP26
When I try to post message with multiple line items, I am getting as below
E1EDP01
--E1EDP02
--E1EDP02
--E1EDP26
--E1EDP26
E1EDP01(no sub sement).
But the expected result is as below.
E1EDP01
--E1EDP02
--E1EDP26
E1EDP01
--E1EDP02
--E1EDP26
Please help me in this regard.
Many thanks
Sam
Edited by: Guest on Mar 18, 2008 7:41 PM
Edited by: Guest on Mar 18, 2008 7:43 PM

Hi,
just put a split by value in the mappings for E1EDP02 and E1EDP26:
field1>Split By Value\[Each Value\]>E1EDP02
field2>Split By Value\[Each Value\]>E1EDP26
Reward points if helpful.
Sankar Choudhury

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

File to IDoc scenario in SRM

Hello All,
I am executing a scenario involving File to IDoc using an XSLT interface mapping.
I am getting an error with error text "Tag ORDERHEADER found instead of tag IDOC BEGIN"
Here is the error message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>MSGGUID 1C28075F1E109C479C1A25BA068CC74D: Tag ORDERHEADER found instead of tag IDOC BEGIN=</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: MSGGUID 1C28075F1E109C479C1A25BA068CC74D: Tag ORDERHEADER found instead of tag IDOC BEGIN=</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I tested the XSLT mapping alone in Repository and it is working fine.
Please suggest on this issue.
Regards, Namadev

Hi Namdev,
//Tag ORDERHEADER found instead of tag IDOC BEGIN"
I think this error is due to a problem either in your source file or your mapping. When the IDOC is to be sent to the destination system, it expects the first tag to be <b><IDOC begin = ></b> , but I dont think that is happening in your mapping.
As you are doing XSLT mapping, I would suggest you test your mapping and check if the destination Message that is created matches with the IDOC structure.
Regards,
bhavesh

Regarding error in XI File to IDoc scenario

Hi,
when i was doing file 2 idoc scenario i got this error "Unable to convert sender service to an ALE logical system". please resolve my issue as early as possible.

Uday,
Please go through these threads:
Unable to convert the sender service to an ALE logical system
How to convert Sender Party/Service to a Logical System?
Unable to convert the sender service to an ALE logical system
BR,
Alok
Edited by: Alok Sharma on Jan 31, 2008 12:39 PM

Idoc sender issue

Hi,
I have an issue in Idoc sender scenario.
The flow is Idoc to BPM to Flat file.
Idoc is triggered from R/3 system via RFC port. It enters XI which is visible in Moni. But data is not there.
Which transaction to use to trace Idoc in XI?
I can see the Idoc successfully sent in we02 from R/3 system. But no data in Moni in main message or attachment.
Regards,
Anirudh.

Hi
Go through following ALE step, check whether you missed any of these steps:
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Regards
Sami

File to idoc scenario in pi 7.1

Hi All,
I am testing file to Idoc scenario.
I have few queries. I am using PI 7.1
1) in Message mapping - I import the receiver idoc metadata. and doing mapping.
So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
Please advice how to overcome
3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message.
"EDI: Partner profile inbound not available"
I checked all the relevent partner prfile configuration is already there"
I have already used all the forums , I did these scenario in past in PI 7.0 and never faced much issue . but doing first in PI 7.1 after a long time, so I might be possible, I am missing some thing. Please advice and help. thank
Ram

Hi Ram,
There is nothing new in PI7.1 which can cause these errors.. it is because the interface is configured wrongly
>>1) in Message mapping - I import the receiver idoc metadata. and doing mapping.So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
If you know the value the you can create the control record during mapping and the fields which you don;t required you can map it co constant. It is using this control record the partner profile entries are found and if there is a mismatch then the idoc will fail with the error which you mentioned in point 3
>>2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
No in 7.1 also we dont have to do anything like that. There is a blog on this error from Michael, please go through it and understand why and how this error occurs. May be in PI7.0 you were lucky enough for not getting this error
>>3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message. "EDI: Partner profile inbound not available"I checked all the relevent partner prfile configuration is already there"
Check the control record of the generated idoc and see whether you have a partner profile entry for the parameters mentioned in it. If not then you need to correct them in PI
Regards
Suraj

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,
<i>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?</i>
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 - EOF issue.

Similar Messages

Maybe you are looking for