IDOC : Message Function 003: Delete Object contains message to be deleted.

Hi,
I am trying to process a Customer master Icreation DOC (OILDEB06) which has a Message function 003: with the description Delete Object contains message to be deleted.
I am testing my IDOC, when should I be using this message function.
If you can detail with the example,
it does not mark the customer for deletion for sure. when it is recommended to use this message function.
Thanks
Regards

yes   your object was locked in the another session ... please close all the remaining sessions ...
and for cross check in SM12   tcode   ....see the lock list ...delete all the list ...
now you can delete the object from the list ..
it happens some times for all   ... when you work with multiple sessions.
reward points if is is usefull .
Girish

Similar Messages

Process code's function module required for the IDOC Message type PROACT

Hi,
I am trying to trigger an IDOC from ME32K transaction which will carry my Contract agreement details to XI. The IDOC I am using for this purpose is PROACT.PROACT01. But I couldn't find the outbound process code / Function module for the process code associated to this IDOC message type.
Pls help me out....
Thanks,
Ram Kalyan

I checked table EDIFCT for the message type and found this:
Function module Function type Basic type Message Type
IDOC_INPUT_PROACT F PROACT01 PROACT
Oops...I think you are looking for outbound..Ignore

IDOC Message type 'ORDCHG' - Sales Order Delete funcanility

Dear Guru's,
I have a requirement for a client where client is sending a EDI message to change & Delete a Sales order. I have mapped change option with IDOC message type 'ORDCHG' and basic message type 'ORDERS05'. Change option for the sales order is working fine.
Can any one tell me with message type 'ORDCHG'. how to delete a Sales Order. In EDI, client is passing only Header segments with Summary details.
Your reply will of greate help to me.
With Best Regards,
M. Rajendran.

Hi Ram,
Thanks a lot for sharing the link, but this dint solve my purpose. I have a different case all to geather.
My client is passing only Header segment and summary segment in the EDI. Thru ORDCHG i need to cancle/Delete entire sales order.
But i found that in standard IDOC Message type 'ORDCHG' only line item deletion/Cancle is availble but i wanted to delete/cancle entire sales document.
Any possibilites available in ORDCHG. Your reply will be much appreciated.
Thanks in Advance.
With Best Regards,
M. Rajendran.

Idoc message type which contains all data types & date format

Hello experts,
I have Two questions :
1.Need Idoc message type which has all sap data types (24 types).
2. I am getting output date in 31-05-1999, whereas am expecting 5/31/1999.
is there anything to be done at system level, since same Func Mod gives expected output in 4.7 verions, whereas in ecc 6.0 version it doesnt.
Thnx in advance

Hi Taj,
The date format usually depends upon the user settings in SAP. for this check your user settings... Go to menubar - > System - > user profile -> own data ->defaults tab -> change the date format in which you want.
Or else.......
There is a conversion exit to change the date in the format you wish to get.... use the Function Module FORMAT_DATE_4_OUTPUT and give the date and the format in which you want to print as input parameters.
Hope this helps.
Regards,
Ravikiran.

IDOC message type and message code and function?

Hai...
anyone can explain with example what is IDOC message type and message code and function? how it is used?
regards,
prabakaran

Hi
An IDoc type can be implemented for various "logical" messages; one message can also be assigned to different IDoc types (m:n relationship).
The message is defined by the values for message type (required), message code (optional) and message function (optional). These three fields belong to the key fields in the partner profiles, which are used, for example, to determine inbound processing. If the 'Message type' field is not maintained (e.g. in the case of a control record from Release 2.1, in which MESTYP did not exist), the IDoc Interface uses the value from STDMES (EDI message type).
If possible, the descriptions of the message type should be linked to the corresponding EDI message type.
The message ORDERS (= message type) identifies purchase orders (outbound) and sales orders (inbound).
Message code or Process Code for Inbound Processing
Code which identifies a process type.
The process type determines which process is used to convert an IDoc to an SAP document.
Process code for outbound processing
Code which identifies the type of data which is to be sent via the IDoc interface.
Using the process code, the IDoc interface finds the application selection module which converts the SAP document into an IDoc.
The process code is only used with applications which perform outbound processing via Message Control (NAST).
Thanks & Regards
Kishore

How can I output multiple IDOC messages in one dataflow in DS 3.2?

Hi, we are trying to load some business partner data into CRM through an IDOC. The specific IDOC we are attempting to use is CRMXIF_PARTNER_SAVE_M02. We successfully created a Data Services flow which takes input from a file and can write out an IDOC message which updates the record in CRM. The problem is that we can only manage to run this job for one record at a time - if the file we are using for input contains 2 or more records (2 or more business partners which we are trying to update), then the batch job fails with the error message:
IDoc Error: Message:      Adding this segment exceeds maximum allowed number of repetition E101CRMXIF_PARTNER_KEYS
I'm guessing from this error message that it is trying to shove both business partner records into one IDOC which is not supported by this IDOC. Instead what we want it to do is send 2 IDOC messages to the server, one per business partner.
Does anyone have any suggestions on how we can make this work?
Thanks
-Trevor

Hi Werner,
I am trying to load data into SAP for Functional Locations Domain using the 'FUNC_LOC_CHANGE' IDOC in Data Services and I am getting the following error.
8236
7776
R3C-244005
2013/02/27 4:52:36 PM
|Data flow DF_ChangeIDOC|Loader FUNC_LOC_CHANGE01
8236
7776
R3C-244005
2013/02/27 4:52:36 PM
IDoc target tried to generate IDoc <FUNC_LOC_CHANGE01> from NRDM data: <
8236
7776
R3C-244005
2013/02/27 4:52:36 PM
IDoc Error: Message:      CIDocIterator::Field: No datarecord available for this segment type
8236
7776
R3C-244005
2013/02/27 4:52:36 PM
IDoc Type:    FUNC_LOC_CHANGE01
8236
7776
R3C-244005
2013/02/27 4:52:36 PM
Release:      731
8236
7776
R3C-244005
2013/02/27 4:52:36 PM
IDoc Number: Not Applicable
8236
7776
R3C-244005
2013/02/27 4:52:36 PM
Segment Name:
8236
7776
R3C-244005
2013/02/27 4:52:36 PM
Segment Type:
8236
7776
R3C-244005
2013/02/27 4:52:36 PM
Field Name:   FUNCTLOCATION
8236
7776
R3C-244005
2013/02/27 4:52:36 PM
>. Check your input data.
6992
8284
R3C-244005
2013/02/27 4:52:46 PM
|Data flow DF_ChangeIDOC|Loader FUNC_LOC_CHANGE01
6992
8284
R3C-244005
2013/02/27 4:52:46 PM
IDoc target tried to generate IDoc <FUNC_LOC_CHANGE01> from NRDM data: <
6992
8284
R3C-244005
2013/02/27 4:52:46 PM
IDoc Error: Message:      CIDocIterator::Field: No datarecord available for this segment type
6992
8284
R3C-244005
2013/02/27 4:52:46 PM
IDoc Type:    FUNC_LOC_CHANGE01
6992
8284
R3C-244005
2013/02/27 4:52:46 PM
Release:      731
6992
8284
R3C-244005
2013/02/27 4:52:46 PM
IDoc Number: Not Applicable
6992
8284
R3C-244005
2013/02/27 4:52:46 PM
Segment Name:
6992
8284
R3C-244005
2013/02/27 4:52:46 PM
Segment Type:
6992
8284
R3C-244005
2013/02/27 4:52:46 PM
Field Name:   FUNCTLOCATION
6992
8284
R3C-244005
2013/02/27 4:52:46 PM
>. Check your input data.
I am trying to update the ABCIndicator from 2 to 3 and hence have set the Flag to X in the source table as well. I have updated the EDI_DC40 mandatory schema with the necessary values and mapped the values to the schemas in the IDOC
E1FUNC_LOC_CHANGE - from the source table
and sub schemas
E1BP_ITOB - some from the source table and other values to NULL
E1BP_ITOBX - FLAG X to the ABC Indicator from Source table and all others to NULL
E1BP_ITOB_FL_ONLY - NULL for Everything
E1BP_ITOB_FL_ONLYX - NUll for everything
I have tried to play around the FROM cluase in the query as well as UNnesting...all of them failed to resolve the issue...Can you please suggest me where I am going Wrong..
Thanks
Chan

Send IDOC Messages to SAP

I have a text file which contains lots of records. I have created a schema for that text file.Then I mapped this schema with IDOC (Acc_Document03)schema.Now I want to send this IDOC message to SAP.There is not shown any errors by BizTalk admin console.But
the message is not reached to SAP.But when I send this IDOC message to a location through File adapter instead of SAP adapter then it has reached there .Why this is happening ?
Please also tell me how to send multiple IDOC message to SAP ?

Hi Glenn.
I got the following error:
The adapter failed to transmit message going to send port "Interplx.SAP_SendPort" with URL "sap://CLIENT=130;LANG=EN;@A/10.151.97.51/00?RfcSdkTrace=False&AbapDebug=False&ListenerGwHost=10.151.97.51&ListenerGwServ=SAPGW00&ListenerProgramId=BTSIDOC_DEV-".
It will be retransmitted after the retry interval specified for this Send Port. Details:"System.Xml.XmlException: Start element 'ITEMNO_ACC' from namespace 'http://Microsoft.LobServices.Sap/2007/03/Types/Idoc/3/ACC_DOCUMENT03//701' expected. Found element
'ITEMNO_ACC' from namespace ''.
Server stack trace:
at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)".
Prakash

How to get the segment detials of IDoc message type.

Dear Friends,
I want to write function module , which takes the IDOC message type as an input and returns all the segment fields in response.
Basically I want to get the XML schema of a IDOC message type and need to expose these details toa 3rd party application to use.
Dear experts ,Please do give me some ideas how to achieve this .
like tables from where i can get these details or u feel any other goos way of doing the same.
thx,
jeevan

Hello experts,
Please participate .........
To redefine my objective I will say:--
I am trying to do some thing very similar that is there in XI .
You might have seen the way IDOCs are shown while mapping an idoc structure.
Its like you select a message type and u get all the list of Idoc Structure shown .
I am really relying on you people.
thx ,
jeevan

Notification of S1INVEXC (message Type) IDOC Message using Workflow

I have to build a Workflow for Notifying the IDOC details to a particular SAP user defined in the Partner Functions of SPEC2K. The Workflow should trigger as soon as the IDOC message of type S1INVEXC is recieved as Inbound process in the SAP.
How to go about, which Business object should be used? and what's the event which is invoked as the IDOC, is recieved.. Please give me brief details of starting this Workflow.
Can any one please give the Estimated duration for building this Workflow...
Message was edited by:
MANJUNATHA KS

Following steps would help you.
1. Create a new process code, and point the process code to the workflow using transaction WE42
2. Partner profile for the inbound message, use the new proces code.
hope it help.
regards
johnson zavier

Arbitration Mailbox is pointing to the Deleted Objects container

Recently completed a migration from Exchange 2010 to 2013. We are occationally receiving the following message. Could someone point me in the right direction? Thanks!
Process w3wp.exe (EWS) (PID=10092). Object [CN=_mailgroup,OU=Groups,DC=localdomain,DC=local]. Property [ArbitrationMailbox] is set to value [localdomain.local/Deleted Objects/SystemMailbox{1f05a927-b82d-41fe-b690-eb9b4350207a}
DEL:e43a17d1-7c97-4ae9-9bfb-17c730878662], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.

Hi,
Please run the Get-Mailbox -Arbitration cmdlet to check result. Make sure these system mailboxes are in existing Exchange server.
And please check if you can find the object "CN=_mailgroup,OU=Groups,DC=localdomain,DC=local", you can compare this object with another normal object to see if there is any defference on property settings.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Invoice posting is not triggering idoc message in EBP to FI backned ECC6

Hi ,
We are working on classic scenario with SRM 5 having EBP and SUS on separate clients on same srm system.
Now we are extending standlone scenario for selected product categories .
We have created product master ,product category & vendor master in SRM EBP client. Defined below settings
1.Define Sourcing for Product Categories -local
2.Define Objects in Backend System -EBP of type Local
3.Define G/L Account for Product Category and Account Assignmet
We are able to create Shpping cart ->purchase order( local)->confirm goods & invoice for local product
With central ccountant authorization employee user has created the invoice and resulted status of invoice as
"Currently Being Transferred" , expected   to post the invoice in ECC system but after invoice idoc is not getting generated in SRM in order to transferred to backend ?
I have tried and in debug mode found that ,Logical System of Logistics Backend is wrongly
attached to invoice ie instead of ECC logical system it is appearing SRM Local logical system . After changing the
backend value for invoice header -BE_LOG_SYSTEM from srm to ecc backend & executed
FM-BBP_PROCDOC_TRANSFER for particular invoice ,Idoc Basic type        BBPIV01 is generated and passed to ecc.
But not able to identify why wrong "Logistic backend " is appeared in invoice. we have below attributes maintained in
Employee
Accounting System for Vendor     VENDOR_ACS     DSRCLNT254(SRM local)
Company Code                                         BUK     100
Cost Center                                                               CNT     430900
System Alias                                                         SYS     LOGSYS250
System Alias for Accounting Systems                   ACS     DSRCLNT254
System Alias for Vendor                                      VENDOR_SYS     LOGSYS250
Vendor
Accounting System for Vendor     VENDOR_ACS     LOGSYS250(ECC)
Company Code                           BUK                            100
System Alias for Vendor                      VENDOR_SYS                            LOGSYS250(ECC)
Kindly help me to post the invoice to ECC backend ,

Thanks Sheetal,
We have classic scenario in place so ECC system (LOGSYS250 ) is defined as backend system of type- ERP_2.0   &
FIvalid- realtime backend validation .
We are using ECC is the accounting system defined in the configuration setting Define Backend Systems.
Note: More to add that Invocie idoc generated after backend logical system correction in invoice header data of SRM ,
it is posting invoice successfully in eCC backend . So data correction for logical system value is seems some problem with standlone scenario configuration .
We have validating this scenario for selectd product categories as with SRM 5 version in place, customer is intrested to use Invoice management system ie.   invoice should be validated with exceptions in SRM before posting to ECC.
We have EBP & SUS in different client on SRM system ,so in existing classical scenario   invoices created in SUS against ECC backned purchase orders is not flowing to IMS in EBP . Can you help me to validate the scenario ?
Regards,
Santosh
Edited by: Patil Santosh D on Oct 2, 2009 1:51 PM
Edited by: Patil Santosh D on Oct 5, 2009 11:37 AM
Edited by: Patil Santosh D on Oct 9, 2009 7:38 AM.
Issue is resolved . It is the System Alias for Accounting Systems setting in organization module .
Now with completion of workflow idoc message-BBPIV is generated in SRM and successfully posting in ECC.
Thanks a lot for your inputs .

IDOC Message coming from R/3 system to XI , but waits in Qeue

<b>IDOC Message coming from R/3 system to XI , but waits in Qeue</b>
XI doesn't send the message FTP receiver.In XI sxmb_moni the "c" column contains green flags that mean "message scheduled on outbound side".
In smq1 It writes "SYSFAIL" means "Password logon no longer possible - too many faile"
But I use "anonymus" in FTP adapter. Which password is this, which component is related with this error.
How can I do?
thanks

Hi Cemil,
it may be that the FTP server where you want to send your output file does not accept anonymous connections.........so just get the username and password of that FTP server, which has access to do FTP to that machine, for doing ftp to that machine, then your output msg will be FTP to your target FTP server........
Thanks,
Rajeev Gupta

XML message mapping considering idoc message variant

Dear Experts,
I am very new to PI. I am working on a scenario where I need to map VGON_OUT xml message from SNC system to ORDRSP.ORDERS05 inbound idoc of ECC 6.0 system.
The issue is :
In the inbound partner profile in ECC there are two ordersp message types. one with message variant SMI and another without any message variant.
Both of them are using different process codes for processing.
So my question is how to map the VGON_out xml message in PI?
Please note: the key difference is the idoc message variant.
There is no way to merge both of these message types as their function is serving two different purposes.
I have attached the xml file and the screenshot of the partner profile here.
Any suggestion or reference link or document would be deeply appreciated.
Thanks in advance.
Praty

Hi Pratyusa,
Did you try with different partner profiles for each ORDRSP?
Regards,
Krupa

Splitting multiple IDoc XML files into single IDoc messages for R/3

Hi all. I have a problem splitting IDoc XML files coming in to XI. I currently have an interface that takes in single store sale IDoc transactions (type WPUBON01) in an IDoc XML file. I then have some complex graphical mapping on the IDoc before sending to R/3 via the IDoc adapter. This works fine. However, we now wish to include multiple sales in one file i.e. many WPUBON01 IDocs. I could use message splitting to do this BUT the mapping is so complex, I do not wish to have to change it to enable the processing of many IDocs in one file instead of just one.
What I want to do: have one mapping splitting a multiple IDoc XML file into single IDoc messages and then another taking these single messages as before and performing the mapping. I cannot find a way to do this in one interface; the main problem I'm having is getting XI to split the multiple IDocs into many single IDoc messages within XI itself. I'd be very grateful for any advice on the best way to do this.
Thankyou.
Stuart Richards (Halfords, UK)

Bhavesh,
Thanks again for a clear explanation... I'm moving forwards but still struggling. I've been on this all afternoon today (after a break on other things) and just cannot get my message to split properly (though the SOAP adapter problem I had earlier is now fixed!). If my initial IDoc XML file contains this format:
<WPUBON01><IDOC>....</IDOC>
<IDOC>....</IDOC>
<IDOC>....</IDOC></WPUBON01>
.. I'm not sure what the cardinaility on the first message mapping and interface mapping should be. I'd have thought the source interface would be 1 and the target would be 0..unbounded but this isn't working. I'm trying different things but I get different errors each time. Currently, I have the above cardinality in my first interface and I'm passing in the following data:
<WPUBON01><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832292</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160633</VORGZEIT><BONNUMMER>1001</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1001</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832293</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1002</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1002</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832294</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1003</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1003</ZUONR></E1WPB06></E1WPB01></IDOC></WPUBON01>
In the message monitor, I get a chequered flag. Great. However, I get the dreaded error 500 in the SOAP receiver comm channel:
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Exception caught by adapter framework: SOAP Error
Delivery of the message to the application using connection AFW failed, due to: SOAP Error.
Any ideas as to what this might be?! I'm getting there.... if I get a solution out of this, I promise to write the blog myself!
Cheers
Stuart

Message monitor - IDOCs messages

Hi
I've created and sent IDOC messages from ERP to MII. However there is no single message found in MII. Any idea? The error message in MII is "Unknown error no messages" (something like that as I translated from German to English)
What I did checked
1. MII IDOC listener status - ok
2. ERP RFC connection -ok
But I saw error message under transaction SM58 "Error when opening an RFC connection"
Thanks for posting

Dear Seng,
I am working on MII12.1.5 build 91
I was also getting error in idoc receiving see below thread but now issue got resolved.
iDoc not received in MII
In my case iDoc sent successfully from SAP but not received in MII.
So i have created one more wrong RFC destination along with actual correct one.
then configured it in SAP NW as well as in SAP MII with same setting as i done for correct one it worked.
then i deleted the wrong RFC Destination and also deleted settings of wrong one in SAP NW and MII.
then my actual correct one is worked.
its strange but workes for me .
may i know on which MII version you are working.
Regards,
Manoj Bilthare

IDOC : Message Function 003: Delete Object contains message to be deleted.

Similar Messages

Maybe you are looking for