After receiving IDoc

Hi all,
I have configured the SAP system to receive a DEBMAS idoc from XI. The process code is DEB2.
i have check in WE05, the Idoc status is 50, Idoc added.
So where exactly is the Idoc added? where can i see the list DEBMAS in the system? is there a table for it?
appreciate any advice.

Hi,
Open the transaction BD87 and give your idoc number and execute.
You will get screen, where you can select your idoc status 50 entry and execute with Process button.
Regards,
Krishnaraju.

Similar Messages

Sender and Receiver IDOC config Settings

Guys I have just come up with this document as a quick reference guide to enable me to be able to configure IDOC scenarios quickly and efficiently. Couls you please let me know if this looks ok and all is in the correct order.
Quick Guide to Scenarios
Note A Ports only purpose is to allow either the SAP R/3 Backend system to establish an RFC connection with XI or allow the XI to establish an RFC Connection with the Receiver SAP R/3 system.
Note An RFC Destinations purpose is to: A) Communicate with the SAP system
B) Pull metadata from either the Sender/Receiver SAP R/3 System or another reference system that contains the same IDOC.
Sender IDOC Scenario
When configuring an IDOC Sender adapter there are a few things that you need to configure before you even start with the Config Directory itself.
Because IDOC Adapter resides on the ABAP stack no sender agreement or sender Comm Channel is necessary
Your main configuration is in R/3. You configure R/3 to send the IDOC to XI so hence you dont need an IDOC Adapter or Comm Channel.
1. You need to define an RFC destination to XI in the R/3 Backend system. (SM59). This RFC destination is used to retrieve the IDOC metadata from the sender system. The IDOC adapter needs these metadata to create the corresponding IDOC-XML message from the RFC stream.
2. Assign the destination to a Port in the R/3 Backend system (WE21)
3. Define your Partner Profiles for the IDOC you are trying to send and Reference that Port there as well (WE20)
Based on the above conditions, you do not need a Sender Comm Channel for IDOC or a Sender Agreement for the business scenario. Your only configuration in the Config Directory is to define R/3 as a Business System (no Comm Channel) and define the Receiver Business System along with the Receiver Determination, Interface Determination and Receiver agreement.
I'm not sure if this step is necessary in the sender IDOC scenario -
In XI box you must also define the ports in IDX1 which allows you to establish an RFC connection to pull the metadata in from the backend system, by specifying the RFC destination from where you want to get the info from. This system is defined by the sender port and the client in the IDOC control record. It is either the sender SAP system or an SAP reference system.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Receiver IDOC
When you receive an IDOC things are a little more complex. You do need a Sender agreement and Comm Channel defined. Again there is much to be done in XI and the R/3 Receiver system before you get to the configuration of the Config Directory.
1. In XI you must configure the RFC destination which enables XI to communicate with the Target System (SM59)
2. In XI you must then create the port which allows you to establish an RFC Connection. In this port you define the RFC destination you previously defined. (IDX1)
3. You then must also ensure that a Partner Profile has been established in the Target system which allows XI to send IDOCs to the Target system. (WE20)
Once the above is completed you can then continue to configure your IDOC scenario in the Config directory. In your Receiver Adapter you reference both the Port and RFC destination that you just established along with the Release which is to be the Target systems release. You must also specify an Interface version which again is the Target systems version.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Apart from the above the rest of the steps in the Config Directory are as normal.
Message was edited by:
 Alex Ong

Hi,
As per my knowledge you need to configure port in IDXI in XI to pull the metadata.
Its a mandatory step to pull the metadata whatever be scenario like whether you are sending an IDoc or receiving an IDoc.
So please configure RFC destination, IDX1 and IDX2 in XI side.
Only after pulling the IDoc metadata you can proceed with any of the IDoc scenario.
Whenever there a IDoc is changed you need to delete the previous metadata and pull it again. In such situations you can use the already existing port in IDX1.
Hope this helps you out.
Thanks and Regards,
Vineetha

Receiver IDOC adapter - RFC_NO_Authority

Scenario:
EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
Went thru receiver determination, Interface determination, message split, request message mapping, Technical routing and then got stuck at call Adapter stage. Below is the error:
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Runtime error RFC_NO_AUTHORITY has occurred</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: Runtime error RFC_NO_AUTHORITY has occurred</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Is there any step that I may have missed after I created the receiver IDOC Channel?
Could you please shed some light here?

Please, search SDN before posting....
check these link: Runtime error RFC_NO_AUTHORITY has occurred in SM58
What its error?

Receiving IDOC from Legacy

Hi guys,
I have requirement that POD will be send by the customer to the legacy system, where order processing is happening.
The legacy system will send the POD to the ECC system by using EDIFACT.
there is a integration layer where EDIFACT will be converted to IDOC.
Does the legacy sytem sends the IDOC automatically after conversion to ECC, or do we need to use any function module for this to receive IDOC in ECC.
If the Legacy system is sending the IDOC automatically in the ECC, where does it post to which table it has to update.
do we need to do any setting for this.

Hi,
There is no BAPI that will split the IDoc and post. You have to do it manually. One way is
1) Split the IDoc into two or more IDocs based on the maximum items you need. Later post these IDocs.
2) Post FI invoices as and when you reach max count(without actually creating new IDocs).
I guess first one would be better as you can tract which IDoc resulted in which FI document(Invoice).
I worked on this before. When we process an IDoc with more items, we flag that IDoc with a custom message with status 51. We have a scheduled job that picks the IDocs with this status and split the IDocs to 2 or more new IDocs.
These new IDocs are processed later.
Hope this helps
Vamsi

Problems while sending/receiving IDOCs

Hi,
I am trying to store IDOC data to MS access database. I created a scenario and able to activate that successfully, but after sending IDOC from SAP, in SXMB_MONI I can see status as "Message Processed succesfully" flag, and acknowledgement status as "Still awaiting acknowledgement" and data is not stored in database. Anybody having any idea about this problem.
Another problem what I am facing is, when sending an XML file from a file server to SAP(through XI), I am getting status as " Scheduled for outbound processing". Receiver determination, Interface determination, Sender & receiver agreements all are present and correct. Any help?

Hi,
Check what chris has said....Also in SXMB_MONI check the status of the message on the outbound side(by scrolling to the right)...This will say whether it has been transferred to the Adapter Engine....
For the second problem, pls check whether all your queues are registered. All queues can be registed from transaction SXMB_ADM...then doublwe click on "Manage Queues"...and choose the register queues and execute...
Thanks,
Renjith

Send/Receive IDOCs (XML) from/to SAP R/3 with XI-SOAP without XI!

Dear SAP specialists,
(BACKGROUND) We are using the Microsoft BizTalk Adapter for SAP 1.0, developed on top of the SAP DCOM Connector (we are using the version 6.20 Patch Nr. 177), with Microsoft BizTalk Server 2002 SP1 in order to send and receive IDOC via the tRFC transport protocol. We are using the Microsoft BizTalk Adapter for SAP 1.0 since February 2002, and today we are exchanging more than 25,000 IDOC/day with this architecture.
When we migrate our SAP R/3 system to the version 4.7 with WAS 6.20, I was very enthusiastic about the possibility of sending the IDOC in XML via the standard HTTP transport protocol, because it would considerably simplify my architecture, i.e. no need of any (expensive) adapter any more! But, I had to realise that the quality of service exactly once will not be there anymore with HTTP as it exists with tRFC. Then, we carry on using the tRFC transport protocol with the adapter.
(QUESTION) But recently, I followed the SAP Course TBIT40 XI Foundations and I learn that:
1. On one hand, the XI-SOAP protocol supports the quality of service exactly once by the usage of a message GUID within the XI-SOAP envelope;
2. On the other hand, all mySAP solutions using WAS 6.20 (or higher) carry a small Integration Engine (with XI-SOAP as the native transport protocol).
Then, my question is: << Is it possible to exchange IDOC (XML) directly with an SAP R/3 4.7 (WAS 6.20) via the XI-SOAP transport protocol using the small Integration Engine embedded into it, with the quality of service exactly once? >>
Many thanks in advance and best regards,
Patrice Krakow

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

How can I use aperture after receiving the full adobe suite? It won't allow me to use it.

How can I use aperture after receiving the full adobe suite? It won't allow me to use it. I receive a dialogue box which states previews are not allowed in aperture and the application is shut down.

Aperture is Apples version of Lightroom. This has nothing to do with Adobe. Ask on a Apple forum. You won't find many people here using this program.
Mylenium

Blue screen of death twice 2 days after receiving T510

Hi all,
I encounter the dreaded Blue Screen of Death 2 times in two days, with a brand new T510.
The first one came as such a surprise in a meeting that I couldn't catch what it was. The 2nd time happend just now and I decided to post and ask for advice. The error for this time is "bad_pool_header" - not sure what that is.
The 2nd time is not necessarily the same as the 1st time. It seems that the display driver is not very stable. There were various times that, when I open the lid while connecting to an external monitor, the whole image on the external screen flickered vigorously. Windows 7 complain the display driver had crashed and windows has recovered from the error. I suspect the first time Blue Screen may be related to this too.
Anyway, although I like this system a lot, two blue screens in two days after receiving the new machine on Wednesday is pretty frustrating to me. Would Lenovo please iron out some stable and high quality drivers with the Windows 7 "Enhanced" Experience? May be with the parts manufacturer please?
Thanks all!
Campion

I would start with installing the latest bios and video driver updates off of lenovo's site. (do not use the TVSU since that tends to be slower at propigating new updates). It is new hardware and there is the possiblity of drivers and/or bios being updated since the drive images Lenovo installs from where created.
Of course random BSOD's could also be bad ram. I would try running MemTest86 on the system and making sure it can successfully pass the tests, and make sure you call customer service and report this so that they know of the issue moving forward.
Best of luck!
lkpcampion wrote:
Hi all,
I encounter the dreaded Blue Screen of Death 2 times in two days, with a brand new T510.
The first one came as such a surprise in a meeting that I couldn't catch what it was. The 2nd time happend just now and I decided to post and ask for advice. The error for this time is "bad_pool_header" - not sure what that is.
The 2nd time is not necessarily the same as the 1st time. It seems that the display driver is not very stable. There were various times that, when I open the lid while connecting to an external monitor, the whole image on the external screen flickered vigorously. Windows 7 complain the display driver had crashed and windows has recovered from the error. I suspect the first time Blue Screen may be related to this too.
Anyway, although I like this system a lot, two blue screens in two days after receiving the new machine on Wednesday is pretty frustrating to me. Would Lenovo please iron out some stable and high quality drivers with the Windows 7 "Enhanced" Experience? May be with the parts manufacturer please?
Thanks all!
Campion
Thinkpad T500-2081 CTO | T9400 2.53GHz | 8 GB RAM | ATI HD3650 + Intel GM45 | 15.4" LED WXGA+ | Windows 8 | ATI Catalyst 13.1 (non-switchable)
Thinkpad 390x | PII 333 | 256mb ram | NeoMagic 256AV | SVGA LCD | OS/2 v4.52

How much $$$ will Verizon charge me if I don't return the Fascinate after receiving replacement?

How much $$$ will Verizon charge me if I don't return the Fascinate after receiving replacement?
I spoke with customer service and couldn't get a real number. She just said it "could be up to $500, or more"
to be determined after they don't receive it within the 5-day period.
Is there a way to find out for sure how much it's going to cost?
Thanks!
Here's the reason I'm asking:
I forgot to drop it off at FedEx on the way to the airport. My entire family is now on an overseas trip and won't
be back for 8 weeks. The Fascinate, packed in Verizon box with FedEx box, is now sitting in my car trunk at
the airport long-term parking lot. I was supposed to stop by the FedEx office at the airport cargo area to drop
it off, but forgot about it during the rush.... (yes, I do realize it's a stupid mistake that may end up costing a
lot of money)

Hi and good morning!
I would like to review your account with you and ensure I can help resolve any concerns you have about being charged for this device. Please PM me directly so we can discuss this together. Also, include your name and mobile number with your PM to me.
Thank you so much and have a safe overseas trip!

Help! Just did the Update (ML 10.8.4) after receiving a new HD since mine crashed last week, and now my Mac won't let me past the log in screen even with correct password.

Help! Just did the Update (ML 10.8.4) after receiving a new HD since mine crashed last week and the shop didn't update it back to Mavricks which I had previously done...and now my Mac won't let me past the log in screen even with correct password entered. It just spins like I'm logging in and then goes back to the user log in screen. I did the process where I restarted and pressed control S and created a new user and password, but once created same issue and can't get passed that screen.
Super frustrated and any help is appreciated!

I have decided to dedicate this thread to the wonderful errors of Lion OSX. Each time I find a huge problem with Lion I will make note of it here.
Today I discovered a new treasure of doggie poop in Lion. No Save As......
I repeat. No Save As. In text editor I couldn't save the file with a new extension. I finally accomplished this oh so majorly difficult task (because we all know how difficult it should be to save a file with a new extension) by pressing duplicate and then saving a copy of the file with a new extension. Yet then I had to delete the first copy and send it to trash. And of course then I have to secure empty trash because if I have to do this the rest of my mac's life I will be taking up a quarter of percentage of space with duplicate files. So this is the real reason they got rid of Save As: so that it would garble up some extra GB on the ole hard disk.
So about 20 minutes of my time were wasted while doing my homework and studying for an exam because I had to look up "how to save a file with a new extension in mac Lion" and then wasted time sitting here and ranting on this forum until someone over at Apple wakes up from their OSX-coma.
are you freaking kidding me Apple? I mean REALLY?!!!! who the heck designed this?!!! I want to know. I want his or her name and I want to sit down with them and have a long chat. and then I'd probably splash cold water on their face to wake them up.
I am starting to believe that Apple is Satan.

How to process the Received Idoc in SAP R/3 ? What to be done ?

Hi All
I am working for file to Idoc scenario.....
Idoc received into SAP R/3 but how to process the Idoc data ?
Such it will store in SAP R/3 DB.....
Clearly
How to Process the received idoc data into SAP R/3 ? (this is for inbound idoc)
I hope any one can help me on the processing steps ?
Waiting for valuable inputs form experts
Regards
Rakesh

rakesh
chec <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">Sample IDoc</a>
normally, based on the idoc types it will get processed. if it is an idoc with master record it will create appropriate master records or if it based for a transaction it will create one.
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098</a>

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

Problem with an Receiver Idoc adapter

Hi.
We have just went from XI 3.0 to PI.7.10.
The Receiver idoc adapter is set up in the same way as it was in XI.
The problem is when two different interfaces runs at the same time I got data into the DC40-record which not belongs too this idoc but from an another interface/idoc.
The idocs are different messagetypes.
In this case the field MESCOD which belongs to one of the idocs also appered in the idoc where the field MESCOD not should be used.
Any idea whats wrong ?
/Per-Arne

Thanks.
Checked sxmb_moni as you said.
In the OutboundBinding-node I can see the right idocadapter is used
where 'Apply Control Record Values from Payload' is enabled.
<SAP:ChannelName>IDOC_INBOUND_U01_110</SAP:ChannelName>
In the IdocOutbound-node I can see the message code 'EXT' which should'nt be there.
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>001</SAP:MANDT>
<SAP:DOCREL>710</SAP:DOCREL>
<SAP:DOCNUM>0000000000033474</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>OILLDD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>OILLDD</SAP:MESTYP>
<SAP:MESCOD>EXT</SAP:MESCOD>
Too be more specific about the interface.:
I got one file in from a file adapter and out of that file I produce two idocs into R3 whit
two different idocs-adapters.
I think you are right about that the configuration may be mixed up.
Any idea of what I can do?
It may be an PI 7.10 bug ?
Shall I delete all config objects and so set config up from scrach again ?
/Per-Arne

Can we show information messages after triggring IDOC's in background

Hi friends,
Iam executing one custom transaction for sales cycle in background, in that iam trigging IDOC's, user are getting the messages like
1. Idoc No: 0000014254 despatched to client -
2. 1Output were processed.
3. 1 IDOC's selected.
user has to enter 3 times while the transaction is running in background.
But requirement is "can i set all 3 information messages after trigging IDOC's to background.
any body suggest the solution.
regards,
vamsy krishna.

Nope nope, I don't work for Apple - I'm just a Level 3 Discussions pleb...! ;-))
I'd been in touch with the senior tiers of Apple Support on the phone to diagnose the chkdsk incidents of 2004-2005.
Following that, I also negotiated (part-)resolution to the Smart Playlist issue.
Since Updater 2006-01-10 (part-)fixed the Smart Playlist problem, but seemed to introduce some other issues for folks, I've been continuing to pass feedback from my Level 2 contact who is handling investigation of the latest problems. In turn, he is working with US Engineering to handle this issue.
So no, I'm not Apple, but I (and some others) pass commentary to and fro between Discussions and Level 2 Support, and by by-passing Front Line phone support, it helps us to get serious issues investigated and resolved more quickly. I find that such an approach for serious problems works well to help the Community.
I'm not sure if my message gives hope - but I do hope that having reported this on up to Level 2, and having been told that US Engineering have teams watching Discussions, that maybe we can expect some attention from Apple R&D on this matter. However, the official line is for individuals to contact Apple directly themselves via the phone and website feedback, so US Engineering have an idea of the number of people affected. The more people who report to Apple directly, the more likely the problem is to be noticed, and hence the priority for investigation and resolution increases. I can start an unofficial ball rolling, as I have done, but we cannot keep the momentum up unless users use these official routes to let Apple know they are affected.
Sorry it's all a bit foggy, but it's the best I've got! Hope this little explanation helps to clarify things a bit more. Feel free to post back if you'd like to discuss this further. Best for now.
Kind regards,
Gopha.

Receiving IDocs from non-SAP system ...

Hello guys,
I have problem with implementing IDoc-XI-IDoc scenario. The sender system is a subsystem (non-SAP system) sending IDocs but XI is not able to receive them. I thing the IDoc metadata can not be found.
Logical system name of the sender is IF6020DEV. I registered the system in SLD. In Integration Directory I imported the Bussines System IF6020DEV to my scenario and I created communication channel of type Sender IDoc Adapter in it.
In IDX2 I created new port called IF6020DEV and I copied needed metadata into the port. But it doesn't work. Probably I don't do it right because I'm beginner with SAP XI.
Could you give me any advice how to configure XI for receiving IDocs from non-SAP system?
Thank you in advance!
Regards
Zbynek

Thank you very much. The issue described in refered discussion is almost same issue what I'm solving. Unfortunetally the described solution dosn't work for me.
The sender system still returns following error. I know you probably won't understand it because you don't know the subsystem, but maybe you could get some idea what is wrong.
05/29/09 16:09:19.482 idoup2 Logon...
05/29/09 16:09:19.482 idoup2 RfcOpenEx (TRACE=1 CLIENT=110 USER=xxxxxx LANG=D LCHECK=1 GWHOST=xxxxxx GWSERV=3361 ASHOST=xxxxxxx SYSNR=61 PASSWD=<password>)
05/29/09 16:09:19.529 idoup2 Logon RfcOpenEx result=1
05/29/09 16:09:19.607 idoup2 Call to (IDOC_INBOUND_ASYNCHRONOUS) failed (3)
05/29/09 16:09:19.607 idoup2 Handle=1
05/29/09 16:09:19.607 idoup2 key............:
05/29/09 16:09:19.607 idoup2 status.........:
05/29/09 16:09:19.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:19.607 idoup2 internal status:
05/29/09 16:09:19.607 idoup2 idoc_upload failed with rc=(3), try(2)
05/29/09 16:09:20.607 idoup2 key............:IDoc-Adapter Eingang: Der Absend
05/29/09 16:09:20.607 idoup2 status.........:EXCEPTION SYSTEM_FAILURE RAISED
05/29/09 16:09:20.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:20.607 idoup2 internal status:
05/29/09 16:09:20.607 idoup2 idoc_upload failed with rc=(18), try(1)
05/29/09 16:09:21.607 idoup2 Logoff...

After receiving IDoc

Similar Messages

Maybe you are looking for