Error-file to Idoc

Hi,
I have created file to idoc scenario.
I have done all the Design and Configuration parts.
But when executed the same scenario by placing input file on input folder.
Its not picking the file and in sxmb_moni also it wont give any messages?!!
What would be the problem....Can you help me out??!!
Cheers.,
Stallin

Hi Stallin,
Do you see any channels in the Adapter monitoring?
It's look to me like a cache problem,
Do you see the channel in SXI_CACHE?
Have you try to perform CPA CACHE REFRESH?
Try to read the following guide "How to Handle Caches in SAP XI 3.0" https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290
I think that one of the cache refresh in http://SERVER:PORT/rep -> Administartion will solve yor problem
Best Regards
Guza

Similar Messages

No suitable sender agreement error (File -- XI -- IDOC R/3)

Hi All,
I am completeing teh 'File --> XI -->IDOC to R/3' scenario.
Have manged to complete teh IR and ID config as per the various threads in SDN.
I am using FCC in the Sender File adapter (which I assume will read the file data and convert to XML data). When this channel is activated, it gives me the error 'No suitable sender agreement found'.
As per various posts in sdn, this scenaruio may not need sender agreement as XI is finally using IDOC adapter to send data to R/3.
Am I correct in assuming that ??
Could you help point any potential missing config.
For your reference:
The comm Channel used to read file data is using File adapter (marked as SENDER/NFS/FCC/Integration server)
Appreciate your feedback.
Thanks
Shirin

Hi,
chk for ALE settings....
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)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Step 6)
     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 7)
     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.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
reward points if helpful...
Prashant

ATTRIBUTE_IDOC_METADEATA Error: File to IDOC Java Mapping

I have done a Java Mapping from File to Idoc and I get the following error in sxmb_moni:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Fehler: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The Idoc structure that I generate in my mapping makes no fullfil of the IDOC tags.
For example:
<IDOC BEGIN="1">
               <EDI_DC40 SEGMENT="1">
                    <TABNAM/>
                    <MANDT/>
                    <DOCNUM/>
                    <DOCREL/>
                    <STATUS/>
                    <DIRECT/>
                    <OUTMOD/>
                    <EXPRSS/>
                    <TEST/>
                    <IDCOTYP/>
                    <CIMTYP/>
                    <MESTYP/>
                    <MESCOD/>
                    <MESFCT/>
                    <STD/>
                    <STDVRS/>
                    <STDMES/>
                    <SNDPOR/>
                    <SNDPRT/>
                    <SNDPFC/>
                    <SNDPRN/>
                    <SNDSAD/>
                    <SNDLAD/>
                    <RCVPOR/>
                    <RCVPRT/>
                    <RCVPFC/>
                    <RCVPRN/>
                    <RCVSAD/>
                    <RCVLAD/>
                    <CREDAT/>
                    <CRETIM/>
                    <REFINT/>
                    <REFGRP/>
                    <REFMES/>
                    <ARCKEY/>
                    <SERIAL/>
               </EDI_DC40>
Should I complete these values in my mapping program?
Which values should I complete?
Thank You.

Antonio,
you can ignore whole EDIDC Segement make disabled in our mapping still it works . but the problem is not with this is our meta data chekc in IDX2 t/c code of XI box.
      it has some problem the strcuture you generate and R/3 accepts are not same their is mismatch in structure
Regards
Sreeram.G.Reddy
Message was edited by:
        Sreeram Reddy

Bulk file upload error: File to IDoc

Dear all,
I have a File -> XI -> IDoc scenario.
The scenario is working fine for files with filesize 2 MB.
But, when I upload a bulk file with filesize 23 MB, it is Struck in XI
In the SXMB_MONI, I see the error flag in the "Outbound Status"
The error message is "Message has error status on Outbound side".
In the R/3 side, the IDoc segments have number of occurrences from 1 to 9999999999
Is there any restriction in the size of the file we upload in SAP XI?
Could anyone tell me the reason for the error and the possible solutions?
Thanks in advance
Kind regards,
Thangesh

Is there any restriction in the size of the file we upload in SAP XI?
There is no theoretical limitation. Bcoz the size more depends upon th hardware configuration and tuning in XI.
The 23MB file can easily be handled in XI.
Could anyone tell me the reason for the error and the possible solutions?
A probable reason would be the hardware configuration. U may check the XI tuning guide.
Regards,
Prateek

Communication Channel Error : File to IDOC scenario

Hi all,
I am getting the below error in my CC monitoring for the channel, previously its good. Now its not getting process due to this error.
Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting document line no. 1 according to structure 'DTL':java.lang.Exception: Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this
Below are the Conversion Parameters:
DTL.fieldNames : REC_CD,SYS_SOURCE_CD,ACC_DT,JE_NO,JE_SRL_NO,BUS_UNIT_CD,GEO,DEPT_ID,OPER_UNIT,PJT_ID,WRK_REQST_NO,OPEN_ITEM,PROCESS_CD,NATURAL_ACCT,FERC_ACCT,PRODUCT,AFFIL_BUS_UNIT_CD,RES_TYPE,REC_CATEGORY,DOLLAR_AMT_SIGN,DOLLAR_AMT,QTY_1,QTY,DESC,SECOND_DESC,BASE_CST_AMT_SIGN,BASE_CST_AMT,TRANS_DATE,EXH_NO,PO_NO,VENDOR_NO_7,STRS_REF_NO,STK_NO,STRM_NO,INV_TYPE,INV_NO,CUST_CD,PLAT_JE_REF_NO,VCH_NO,VCH_LINE_ITEM,AP_REF_NO,PO_LINE_NO,BILL_CTL_RPT_NO,VEH_NO,PAYT_RECVR_CODE,GLEX_SEQ_NO,PAYMT_TYPE_CODE,CHECK_NO,FILLER
fixedLength: 1,3,10,4,5,5,2,10,8,15,15,15,4,10,6,6,5,5,5,1,19,1,15,30,30,1,18,10,10,10,10,5,6,3,8,6,8,13,8,4,1,4,17,10,1,4,1,18,13
keyFieldValue: D
Please help me in this..
Regards,
Srikanth.

>
srikanth vadlamani wrote:
> Hi experts,
> Communication Channel itself shows this error, still I did not placed the file in the FTP to process.
> The error is not from RWB/MONI, it is from Communication channel monitoring, there I can see the red flag. If I am can process the file then its ok I can check with the data or my business people, but channel itself shows this error, need to fix, tomorrow they might place the file, it should process.Pls. help me how can I resolve this issue.
>
> regards,
> Sri..
In this case check SAP Note 830238.

Error/Doubts in Idoc-XI-File scenario

Dear All,
I am doing one scenario in which DELIVERY idoc is posted from R/3 to XI and then from XI that idoc is to be sent as flat file to one local folder.
For this scenario, I have done all ALE settings and I am able to see the idoc in XI in cXML format.Now I want to sent it as flat file.
Now, for doing this I created 2 BS & 2 TS. 1 BS & TS of type Third Party for receiver & 1 BS & TS are of type Web as ABAP for sender. Then I have created one namespace in IR. I have not created any DT, MT, MI, MM becoz the structure of source and target file are same. Now, I created one IM in which I specified specified Type as "ABAP Class" & Mapping program name as one of the Z function module as specified in one of the SAP Guides.
Then in ID, I created 2 Parties ie. one for Sender & one for receiver. Sender is having a communication channel of type Idoc & receiver is having communication channel of type File. And thn further Receiver Agreement, Inetrface Determination, Sender Agreement & Receiver Agreement are configured.
In my system there is one scenario already configured which is using Delivery idoc so I have used party in my scenario for both sender & receiver.
Now, when I am sending the idoc from R/3, I am able to see cXML in SXMB_MONI but it is taking receiver as the one which is defined for the already existing scenario but not the receiver defined by me.
Can anybody guide if I have followed the correct steps & where I am doing the error.
Warm Regards,
N.Jain

Hi ,
Plese refer the following blogs ,
IDoc to File
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
You have to do all this settings mentioned in the docuemnt:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Also can you check this weblogs on the same:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Thanks ,
Suvarna
Award pts if it helps .

Message has error status at outbound side File To Idoc Scenario

hi ,
In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
Please suggest what may be the problem ?
Regards,
Rohit

1. First check the RFC destination name used in receiver Idoc adapter communication channel.
2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
Regards,
Prateek

Error in File to IDOC Scenario

Hi,
I have File to IDOC scenario.
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Despite of this error in sender channel I am receiving the message in XI.
But in XI also it throws error :
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
Any help on this ?
Thanks,
Vikas

Hello Vikas,
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e. keyFieldValue.
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
regarding the above error refer this
https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
Regards,
Prasanna

Error in file to idoc scenerio

hi
in file to idoc scenario
i got error in sxmb_moni
in status it is showing recording,
in Q.status it is showing stop symbol.
waiting for suggestions.

Hi Sandeep,
Have a look at queue problms here
/people/prashanth.azharuddin/blog/2006/11/24/some-errors-in-an-xi-production-environment
Some additional help
Q.Status is "Queue stopped"
queue status is stopped
Regards,
Prateek

File-to-Idoc error (using business sender service)

Hello,
My scenario is Flat file to IDoc. I am using a business service as my sender system. I did put in a logical system name in the business service and I have added the logical system in SALE.
The error I am getting is <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>MSGGUID 526719BA7E874E3906EEF45B43806D5C: Tag CULL_GR_RECORD found instead of tag IDOC BEGIN=</SAP:P1>
This is confusing to me because the CULL_GR_RECORD is the name of my data record of the file that is converted into an idoc within XI.
Can someone please help me with this? I would really appreciate it. I need to solve this tonight.
Thank you.

Hi,
>><i> I am using a business service as my sender system.</i>
This is fine as ur sender is file.
I suggest deleting the matadata in IDX2 and then rerun the entire interface.
Make sure ur IDoc is imported properly to the IR. If yes, test ur mapping locally once.
Regards,
Divija.

Error in File 2 Idoc

Getting following error while doing Simple File to Idoc scnerio
Leaf node with min occurence>0 and with out mapping.
please Help

Hello,
You try to send an idoc that require a filled node without filling it.
For example, the node B must to be fill :
<A><B>toto</B></A>
If you don't fill it you have an error.
Regards,
Chris

Error in File-PI-Idoc scenario

Dear All,
While working on File-PI-Idoc scenario, I am getting the error as
<?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>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have checked various other posts on the same error but still I am not able to resolve this.
Please help me in resolving this error.
reg,
nj

Nishu,
Please check whether you have assigned the following roles to the particular user you are using for data communication.
Roles:
SAP_XI_IS_SERV_USER,
SAP_XI_APPL_SERV_USER
Regards,
Sugata

File to idoc error

i am testing File to idoc scenario..
everything went smooth in XI...51 status error at ECC.
when i went into details..it says..Fill in all required entry fields
i tried checking those ..but its fine
what should be the error

Hey
When you execute the function module in foreground,you will see errors(if any) in red color along with the field which is giving this error(with explanation).fix that error and try to post IDOC's again.
to me it looks like the configuration is not in place to receive your IDOC,you might be passing some value which is not valid for proper configuration.
Like in my case i was giving wrong ship to party,this ship to party was not configured in R/3 hence IDOC was not posted correctly.
Thanx
Aamir

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

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-file to Idoc

Similar Messages

Maybe you are looking for