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>toto</A>
If you don't fill it you have an error.
Regards,
Chris

Similar Messages

ATTRIBUTE_IDOC_RUNTIME error in File-IDOC Scenario

Hi,
I got this error in FIle-IDOC scenario.
ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPMMX, client , RFC destination contain errors
There are many threads on same issue. Almost in all threads, the suggestion given was, we need to check the Channel Definition(Port should be SAP<SYSID> and not SAP<SYSID>_<CLIENT>)
I have given the proper values for RFC desitnation and port. Even then, I m getting this error.
Is there any other suggestions?

Hi aarthi,
I suggest u chk all d settings dat u hav done..
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...
MenoN

File-IDOC, idoc interface error

Hi,
Scenario: File-IDOC (Multiple records in source file to be mapped to multiple CREMAS IDOCs) without BPM.
Modified the occurance(maxOccurs = 'unbounded') in XSD structure of IDOC(CREMAS) and saved it as external definition.
I have used this external definition in message mapping and interface mapping.
In configuration, i have used the same message interface (corresponding to external definition) as inbound interface.
Now, I get the following error.
- <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_WRONG_INTF</SAP:Code>
<SAP:P1>MI_Cremas04_multi_external</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_Cremas04_multi_external</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please help.

Hi,
>>I have used this external definition in message mapping and interface mapping.
In interface mapping you need to use Imported IDOC not External definition
This solves your problem.
let me know if you have any issues still.
Cheers,
Jag

Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number

Hi,
I'm attempting to create a simple interface which converts cutomer data from a flat file and loads it into a SAP enterprise system as an DEBMAS06 IDoc type. I am getting the error message Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number in the XI message monitor.
Has anyone come accross this error before and if so, what is the resolution???
Thanks, in advance,
Pete

Hi Peter,
did you fixed it?
How did you?
got the same problem
Kind regards,
Michael

SP14 Multi-mapping - error in receiver idoc adapter

Hi,
I have a scenario where a business service should send some XML to SAP CRM. I get the file via a sender JMS adapter and try to post it to CRM via a receiver IDOC adapter.
I have created a multimapping (1:N - 1 XML file to many Idocs) as should in the repository.
In the configuration under Interface Determination, I have chosen 'RB_SPLIT' and selected the interface multimapping.
It should be pointed out, that when testing both interface and message mapping i get no error. All idocs seem to be created as they should.
When testing the setup 'real life' the message fails. The error message in the monitor says:
- 
- <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_WRONG_INTF</SAP:Code>
<SAP:P1>InterfaceCollection</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface InterfaceCollection</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Notice that the above error is when trying to send only 1 record, which in turn then should result in only 1 idoc.
If trying to send multiple XML records, i get the following error:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>A system error occurred in the outbound binding</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the monitor in the payload of 'Request message mapping' I see as many Maindocument, Submaindocument pairs as should be Idocs.
Now i really don't know how to interpret the error messages in both cases, so I'm a little lost here...
It should be pointed out that the idoc being used everywhere in this scenario, has not been modified - from all places it is being used (and only exists) in the 'Imported objects | Idocs' place.
Also the Idoc is also being used as Inbound interface - so no mistakes here either.
I really hope someone can help me here, as I'm otherwise pretty stuck in this case.
Best regards,
Daniel

Hi Daniel,
I have exactly the same type of scenario (under SPS14 and now also SPS15), sending an XML message over JMS to XI and trying a multi-mapping to many IDocs (actually a list of orders in XML is mapped to n ORDERS Idocs).
I also face problems doing so, when I use the IDoc Adapter as outbound in the Receiver Agreement. I receive the following error:
CO_TXT_MMF_ENGINETYPE
Messages in multi message format can be sent to one adapter engine only
However, I tested the same scenario by just changing the Receiver Agreement to a File Communication Channel and - surprise, surprise - it works. One file per IDoc is created.
Of course, this is not what we want to accomplish, but when I checked this piece of documentation (sorry another link
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
the IDoc adapter is not listed in the list of Adapters that are supported. Does that mean, that this feature is not supported for generating IDocs? Maybe that's a question for a SAP OSS Message?
I hope that helped you a little further - if you find out more I'd be happy to learn about it.
regards,
Peter

File-idoc Unable to convert the sender service to an ALE logical syste

Hi experts
iam working on file-idoc scenario ,iam getting the below error in sxmb_moni and RWB
"Unable to convert the sender service to an ALE logical system"
i checked the partnetr profile, RFC(sm59) and IDX1 t codes.
the connection is ok. but still i could figureout the problem.
please suggest me
Thanks
vasavi

Hi,
Have u checked the logical system is added in the Sender Business service in the Integration Directory?
Open the Buiness Service/System --> EDIT-ADAPTER SPECIFIC IDENTIFIERS
then specify the logical system name.
Go throgh the following link
Troubleshooting File-to-IDOC Scenario in XI.
Regards
Sridhar Goli

Error in file cc attemp to process file due java.lang.NullPointerException

there is an error in file communication channel with error information
*Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException
.*please post ur views what might be reason for this type of errors.

Thanks all for your valuable and quick responses.
MY concern is that why it created 1 file 3 times.
i checked the ICF that is green.
THe interface works like this
*the idoc is sent from the SAP system.
*and is received by a BPM in XI
BPM sends the file to a file receiver channel.
*Encryption program picks the file and encryption is done
*Again the file is sent by file sender channel to receiver.
the receiver is supposed to get 3 files but it is getting 9 files.
one file 3 times.
Moreover file receiver channel shows error jave lang null pointer
please send in your views so that the problem can be sorted out ........
Thanks.

FILE-IDOC, no message no IDOC

Hi experts..
iam working in FILE-IDOC scenario. when the scenario is excuted , the file is picking and archiving in the given directory. but when i check in SXMB_MONI the message is not cretaed and finally the the IDOC is
not created in destination system.
i cheked in RWB --adapter monitaring --the adapetr in sucess status.
please tell me what could be the reason?
Regards
vasavir.

Hii
Place a file in the specified source location.
once the scenario is configured correctly then the adapter picks the file based on the time specified in the pollinterval and process the file.and based on IDX1 IDX2 settings the file is posted to SAP R3.and in R3 check the idoc in WE05 or WE02.
there you can find the status of the idoc.
these links will help u for checking ur scenario and error handling :
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Error handling in File ---IDOC Scenario
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
Regards

File-IDOC Scenario

Hi,
My scenrio is File -IDOC.
I had done Design & Configuration part.
I am getting following error
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_RCV_SERV</SAP:Code>
Kindly help me;.

Hello Srikant,
Refer the following weblog in section 5 Troubleshooting File-to-IDOC Scenario in XI.
You have to define logical system name for sender system.Do the steps which are specified in weblog you can able to overcome this error.
Cheers
Veera

File-IDOC

Hi All,
I am trying a file-IDOC scenario. When I execute the scenario, I get an erro msg in SXMB_MONI. The error msg I get is "Receiver service cannot be converted into an ALE logical system".
Any inputs on this would be of great help.
Thanks & Regards,
Jai Shankar.

Hi Jai,
Please check the following:
1. Give an ALE name for the sender system (file adapter) also.
- Go to Integration Directory - > double click on your business system (for file system) -> services -> Adapter-Specific Identifiers..... Here if there is no logical system, Please do give the ALE Logical System name that is maintained in the SLD. if you are giving the Logical system name, do save and then activate the changes made.
2. When you create a business service, goto the menu option Service->Adapter-specific Identifiers and mention the ALE configuration information details.
3. At first we should check if our Logical System Name is correctly maintained in the SLD:
- go to the SLD - Technical system -> Client number -> Logical System Name and make sure your business system name is there .
4. Then we have import the LS name to the XI Directory:
- go to your Business System -> Service -> Adapter Specific Identifiers.
- import the business system name from the SLD using the "Compare with SLD" button
- Activate the changes and you can check your if your configuration works.
5. If none of the above is the cause... then probably you'll need to refresh the cache and still if it doesnt work you need to implement OSS note: 791181 (which deals with an error caused by a header mapping)
Also Check the following blog.
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
I hope it helps......
Regards,
Abhy
Message was edited by: Abhy Thomas

Exceptions in file-idoc scenario

Hi Folks,
I am developing a file-idoc scenario. What are the different exceptions I would be needed to handle apart from the following two identified?
1. Mapping issue
2. Problem in posting the idoc (SAP system may be down and others)
Thank you

Hi Raja,
The errors an happen at following steps:
1. Error while picking the file:File adapter error
2. Error in mapping: error due to incorrect data, incorrect format, corrupt file etc.
3. While posting Idoc: due to Incorrect userId password, due to structure not matching, destination system being down.
Hope this helps.
Regards
Vijaya

Error in posting IDOC ORDERS.ORDERS05

hi,
dear all,
i am getting error in posting IDOC ORDERS05.
IDOC has arrived on system but with status 51,
it says:
VKORG, VTWEG, SPART cannot be determined for customer , vendor
can you please tell me how to map above specified fields.They are under which segment.
I am sending XML file with fields thru XI.
Thanks.

hey rajeev,
thanks very much for your patience to deal with this basic questions expected from me who is just new to XI
really thanks.
but RAJEEV, as you said we have to add the same IDOC to inbound to R3 if R3 is receiving that IDOC and in OUTBOUND if R3 is sending right?
hi, sorry to interrupt you more :
take my scenario of IDOC ->XI->FILE.
i added that IDOC type in receiving LS that is FILE LS in OUTBOUND side,
and i do not add anything in OUTBOUND parameters of my sending LS that is R3 system.
i am using we19 to send IDOC.
Before Sending IDOC i am filling EDIDC segment with these parameters is it right?
Sender Information:
Partner number: SAPLS
Port: Port defined on XI pointing to R3.
Partner type :LS
Receiver Information:
Partner Number : FILELS
Port: Port defined on R3 pointing to XI.
SO, Provided that i entered following values in EDIDC segment and i do not add anything IDOC type in outbound parameters in R3(sending system),
i add that IDOc in outbound parameters under LS defined for File system,it worked.
You got my point?
sorry for writing such a long thread? but please resolve it RAJEEV.
Thanks.

Re : How to Error Handling In Idoc /ALE.

Hi This is Arief ,
I tranfer the Data Through ALE from One Client To Other Client some of Data not Posted ......how check other client wither Data Posted or not ....
How to error Handling In IDocs.....pls Help me.......
Kind Regards
Arief .S

Hi
The exception handling for idocs
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm
Exception handling in File to IDoc Scenario
For RFCs
Re: Passing SAP Exceptions to a sync SOAP Call
Error Handling when using RFC
Exception Handling while Calling RFC - BPM
handle exceptions in remote function modules

Web-Disk on OSX 10.9 Give me this error: "Finder got an error: Network file permission error."

Previously I was using OSX 10.8 and Web Disk was working great.
Since I upgraded to OSX 10.9 Web Disk Dont Attach to my compputer and give me this ERROR:
FInder got an error: Network file permission error.
When I got this ERROR first time I searched GOOGLE and found this link: http://cammodude.blogspot.no/
And I did:
To force all connections to be SMB1:
Open A terminal window
paste in the following line followed by the return key(should be all on one line):
echo "[default]" >> ~/Library/Preferences/nsmb.conf; echo "smb_neg=smb1_only" >> ~/Library/Preferences/nsmb.conf
What the command does:
Creates a file called nsmb.conf in your home directory at the path ~/Library/Preferences/nsmb.conf.
Adds directives to force SMB connections to use the SMB1 protocol. This is slower but stable.
Then I could use Web Disk on OSX 10.9 after executing this command in Terminal.
But now I restarted my Macbook and now Im NOT able to connect to Web Disk and get the same ERROR.
FInder got an error: Network file permission error
After trying 100 times it attaches 1 time but then show this ERROR:
Can't get <<class cdis>> "my.server.com/2078" of application "Finder".
If this happen then I can see the files in Finder and see the Contents and Size of files but if I open a PHP file in BBEdit then it shows BLANK.. But actually it is NOT blank.
Now Im stuck How can I solve this? All help is highly appericated..
Thank you so much...

Hi,
Make sure to chmod the app, something like this :
chmod -Rf 777 secure_site_WebDisk.app
(in my case the CPanel provided the app for my OSx version.)

[Solved] Error : The file or folder path /Probl?me 1 does not exist

Hello,
I encountered this error
The file or folder <path>/Probl?me 2 does not exist
while I was trying to open a directory already extracted from a zip file containing directories with special characters. In this case, it is a "è" that was misinterpreted as a "?".
I searched the forums and on google, the solutions proposed do not work for me. Although, I have to deal with these files written in french, I would like to have my locale in english (US), with a system wide support for special characters.
Attempt 1: Adding the option : iocharset=utf8 into the fstab, like this :
fstab :
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
/dev/fd0 /media/fl auto user,noauto 0 0
/dev/disk/by-uuid/24ba75ac-e52d-40eb-a599-83b394b500b2 /boot ext2 defaults 0 2
/dev/disk/by-uuid/c797f409-00bc-479a-b4d6-ab49943f644b / ext4 defaults 0 1
/dev/disk/by-uuid/668427a8-5f51-42bd-a316-fc7984bf5f4f /var ext4 defaults 0 2
/dev/sda7 swap swap defaults 0 0
/dev/disk/by-uuid/417cd1b7-8f06-414b-84d5-e8714d9646ab /home ext4 defaults 0 2
/dev/disk/by-uuid/ef9aa00e-0515-4d7b-aa23-8096e787250d /usr ext4 defaults 0 2
/dev/disk/by-uuid/17d401b7-2fc7-4d9f-8e17-657d86926d2e /tmp ext4 defaults,iocharset=utf8 0 0 <<<<<<<<<<<<<<
/dev/disk/by-uuid/71e543b6-e06c-4b0e-b1e3-3b491ff1fefe /var/cache/pacman/repos ext4 defaults 0 2
#/dev/sda12 /mnt/archive ext4 defaults 0 2
#.host:/ /mnt/hgfs vmhgfs defaults 0 0
This solution does not work, because after adding iocharset=utf8, in front or after a "defaults", after a reboot, while mounting the filesystem, there is the following error message:
Mounting Locale Filesystem :
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
$ dmesg | tail
phy0: Selected rate control algorithm 'iwl-agn-rs'
EXT4-fs (sda5): re-mounted. Opts: (null)
EXT4-fs (sda5): re-mounted. Opts: (null)
EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (sda10): Unrecognized mount option "iocharset=utf8" or missing value <<<<<<<<<<<<<<
EXT4-fs (sda11): mounted filesystem with ordered data mode. Opts: (null)
Adding 2104476k swap on /dev/sda7. Priority:-1 extents:1 across:2104476k
tg3 0000:07:00.0: irq 44 for MSI/MSI-X
Attempt 2: Changing all the locale features in KDE and in /etc/rc.conf as well.
$ vim /etc/rc.conf
LOCALE="fr_CA.utf8"
HARDWARECLOCK=""
TIMEZONE="America/Montreal"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
It is complicated to remove these directories. I had to use the inum to get precisely these directories before removing them.
$ ls -il
total 8
1577566 drwxr-xr-x 2 [username] [username] 4096 28 jan 07:09 Probl?me 1
1577573 drwxr-xr-x 2 [username] [username] 4096 28 jan 07:09 Probl?me 2
$ find . -inum 1577566 -exec rm -i {} \;
rm: impossible de supprimer « ./Probl\212me 1 »: est un dossier
Note that the hypothetical character 'è' is represented has a '\212', a 'È' if seen as a extended ASCII character.
These directories cannot be deleted this way :
$ rm -r Problème\ 1
rm: cannot remove `Problème 1': No such file or directory
or
$ rm -r ProblÈme\ 1
rm: cannot remove `ProblÈme 1': No such file or directory
What should I do to be make the operating system recognize those special character, and interpret them correctly ?
Last edited by ramboman (2011-01-29 21:45:50)

I found a working solution, but better solution are also welcome
I had to have fr_CA not only in utf8 but also in iso88591. I had to modify the /etc/rc.conf this way :
LOCALE="fr_CA" <<<<<<<<<<<<<<
HARDWARECLOCK=""
TIMEZONE="America/Montreal"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
To preserve the english US language system wide, I had to add the following line in the /etc/profile :
# Allow french special character while in en_US
export LANG=en_US
The character misinterpreted by a "?" is now seen :
as a "è" in dolphin
as a "?" in the console
It is now possible to access the folders.

My LR 4 suddenly no longer recognized my memory cards. I am using the same cards and cameras but consisitently get the error message:"files not imported because the files could not be read. they are jpg and nef files...I am stuck without my workhorse! Any

My LR 4 suddenly no longer recognized my memory cards. I am using the same cards and cameras but consisitently get the error message:"files not imported because the files could not be read. they are jpg and nef files...I am stuck without my workhorse! Any advice is helpful. This has never happened in 6 years

answered in your other thread LR 4 suddenly no longer recognizes files.

Error in File 2 Idoc

Similar Messages

Maybe you are looking for