Determination of QOS for IDOC messages

Hi,
sending IDOC from SAP to XI, and then to an external system using a JDBC adapter, the QOS for messages is automatically set to EO: anyone knows if it's possible to change this parameter (I need EOIO)? Where can I find documentation about setting/changing QOS?
Thanks for any suggestion.
Simona

I had the same scenario as Simona and at the end it turned out to be pretty simple (if WAS >= 6.40). On the sender system (SAP ERP) in partner profiles -> in the outbound parameters for the message type, you need to check Queue Processing parameter. When you do this an aditionalfield will apear: Rule name. This determines which rule will be used as QueueID. Rules are customized in WE85 where you can assign your own function modules to custom rule names.
Once I assigned appropriate rule (for test I used FIRST_16_OF_MESTYP) xml message was automaticaly set to
<SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService>
and the message got the QueueID XBQO* (in SXMB_ADMIN).
Again, if WAS is WAS >= 6.40 you don't need to set up IDXQUEUE table.
Regards,
Elvis

Similar Messages

QoS for IDOC adapter

Hi all ,
what are the QOS available for idoc adapter
Regards,
Tarang

Hi,
Check on this:
<i>The quality of service EOIO (Exactly Once In Order) must be specified in the message header.
The receiver system or the sender system must be based on SAP Web Application Server 6.40 or higher.
If this is not the case, the quality of service is automatically changed to EO for compatibility reasons and the message is processed accordingly.</i>
http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
Regards
Vijaya

IDoc Error: No recipient found for IDoc message type in the ALE model...

Hello Experts,
I just created an IDoc for purchase orders and when I try to test it after releasing
the PO, an error is shown in the processing log saying that there are no recipients
found for my message type of the IDoc. I refrenced it against a working IDoc but I might be
missing something.
Hope you can help me guys. Thank you and take care!

hi,
in bd64 ,goto change mode select ur distribution model and click add message type define ur logical systems and message type and save.
thn goto environment - partner profiles - f 8.it will show whether model is created or any errors.
then go back edit - model view - distribute.
reward points if hlpful.

Table for Idoc messages

Hi,
Where I will get the bd87 idoc messages
what the name of the table contain these messages.
Thanks!!

Hi Ramesh,
if you are tracing the idocs through BD87 (idocs in outbound side) , then u can find the corrresponding inbound idocs in the reciever system,use transaction we02 give the outbound idoc numbers and execute , the u can see the idoc numbers along with thier inbound status (for eg 51, 53 0r 64).
Also in bd87 itself u can trace the idocs by mentioning the time and date on which u created idocs.
The status through which ab idoc has passed are stored in EDIDS.
Regards...

Configure retries for IDOC message in BPM?

Hello!
I have a BPM in where I am posting an Idoc to a SAP system. If posting this Idoc goes wrong, I would like to have some retries before I eventually send an alert message. Is this possible to configure somewhere in the BPM? If not, can I configure this somewhere else?
Thanks!
regards Pavel

hi,
> I mean if XI for some reason cannot post the Idoc to SAP
depends on what reason
you can reschedule restarts of queues (smq1/smq2)
you can restart SM58
you can restart XI messages
so depending on the error there are many ways to restart automatically
Regards,
Michal KRawczyk

EOIO QOS for IDOC- PI- Proxy communication

Hi,
We have a scenario where IDOC communication is being used for sending the data to PI and PI does the mapping and routes it to ABAP proxy of the reciever.
In this scenario, we want to ensure the EOIO for one IDOC which means we want all the XML messsages of a particular interface need to be executed in the same queue.
Sender Uses IDOC to send information to PI
PI does the mapping and routes to reciever using XI adapter.
Reciver uses ABAP proxy to execute the XML
THanks,
Prashanth

you need IDoc serialization.
/people/sap.user72/blog/2005/01/28/setting-up-inbound-qrfc-queues-for-serializing-idocs-using-the-idoc-adapter & http://help.sap.com/saphelp_erp2004/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm will help you

Workflow notification is not tiggered for IDoc of message type 'WPUWBW'

Hi All,
        I would like to know the setting up of workflow notification for IDoc message type 'WPUWBW' (idoc of different message type is getting notified). Please provide pointers and also the steps for the above issue.
Regards,
PSS

Hi Ferry,
System checks for the IDOC version and then calls the EXIT if the versions are different .Following is the code snippet that ensures the above thing in include LBD11F0T :
Change IDOC version if target <> current version.
IF F_EXCEPTION-MSGTY IS INITIAL
    AND (    F_IDOC_CONTROL-IDOCTP <> TARGET_IDOCTP
          OR F_IDOC_CONTROL-CIMTYP <> TARGET_CIMTYP ).
    PERFORM CHANGE_IDOC_VERSION TABLES   T_IDOC_DATA
                                USING    TARGET_IDOCTP
                                         TARGET_CIMTYP
                                CHANGING F_IDOC_CONTROL
                                         CHANGED_FLAG
                                         F_EXCEPTION.
ENDIF.                               "End of if subrc = 0
Have you tested it ? Pls suggest if I am wrong somewhere.
Thanks and Regards
Gurpreet Singh

Enhanced Interface Determination for IDOCs

Hi All,
I've a query on the usage of Enhanced Interface Determination for IDocs.
I've to create IDocs based on the condition in the Message Mapping i.e. say if recordtype in the source is A then IDoc1 should be created and if recordtype is B then IDoc2 should be created.
Is it possible to use Enhanced Interface Determination to achieve this??.. Because I was told by someone that Enhanced Interface Determination can't be used for IDoc based scenarios though am using External Definitions for the mapping purpose. Please clarify.
Thanks in advance
Regards,
Joe.

Hi Sridhar/ Bhavesh,
Thanks for your prompt reply. I think I wasn't clear in my previous post.
The scenario is the input file has three different record types (3 different structures) and the IDocs should be created based on the record type. I don't think I can use the condition based scenario as the record types are totally different. Please suggest.
Thanks,
Joe.

Multiple customers for same message type "invoic" and idoc type "invoic02"

Dear Experts,
I have SAP ALE process configured for single customer u2018Au2019 where I send invoic02 idoc (message type invoic) to the customer via PI server. Now I need to add one more customer u2018Bu2019 which require recepient determination. I am not sure whether this resolution of customer address at PI level or config is required at R3 itself.
I tried to maintain partner profile type as KU but it generates the error "No partner profile is maintained". For existing customer u2018Au2019 I am keeping the partner profile type LS.
I want to know the following:
a.Whether the recipient determination at R3 (config of partner profile we20)- if so what are the essential steps. Do I really need to shift partner profile type as KU?
b.Whether config is required at PI level itself- if so is there any pre-requisite config in R3 to support that in PI.
I hope my question is clear since this is my maiden attempt to seek solution from expert group.
Regards & Thanks

Hi ,
if you want to trigger the idoc two times for basic type& Extension..
1 ) you need to maintain WE20 Partner Profiles (This is good already you did)
--> But the Output type for Bsic type & extension type is same so output type is triggered Once so idoc is created One.
2) try to create another Output type in T-code NACE for extension then two Idocs is created one for Basic and another for Extension.
Regards,
Prabhudas

IDOC message type for "Site" in SAP Retail module?

Hi All,
We have the need to transfer master data (through master data change pointers) of Retail Sites within the SAP Retail module (transaction: WB01, WB02). Does anyone know if there's an IDOC message/type already associated with this? Thanks in advance for your help!
Cheers,
Matt

Hi,
please read SAP notes 892103 and 551035.
The correct IDOC type should be FIDCC1 / FIDCC2.
Best regards,
Andreas

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

IDOC Segment missing for MATMASS Message type

Through change pointer program for the message type YAUIHUBMATMAS IDOC is triggered.
1) Change pointers are defined in system for the message type T Code u2013 BD52.
2) If respective field is changed in material master , this data is stored in change pointers table BDCP.
3) Background jobs are scheduled every day, which searches for the changes pointer table and triggers the idoc.
In our case IDOC is getting generated but with one segment missing.
We have analysed the succesful and failed IDOC and found desrepency is field updation of BDCP table.
Succesful case contain material number in object value of ZZMDST field where as failed contain some other value.
Can anyone please help us to guide how the BDCP table is updated and the values are mapped in it or any other suggestion to find why the segment is missing in it.
Regards,
Roshni.

Jürgen L. wrote:
> I have never seen a YAUIHUBMATMAS IDOC, nor a ZZMDST field .
> This seems to be home made.
>
> You are expecting that standard SAP programs are generating change pointers for your z-fields?
> Do you see a change history in material master for your z-field?
>
>
> follow the slution from this thread:
>
Yes ,This is a Z -field.
Change pointer is triggering the idoc fo this Z-field but in some cases one segment is missing .
This is z-field in the basic data view of material master.
Yes , we have checked the change history in material master for this field it is getting updated there in BDCP table as well but in BDCP table if this field is flagged then object value is not contain material number instead it contain some other number .
But in case of succesful IDOC the object value is same as material number.
Regards,
Roshni

Equivalent Idoc message type for EDIFACT BANSTA

Hi Experts,
I am trying to find out the equivalent IDOC message type for EDIFACT BANSTA. The purpose of the message is to show the item level statuses for a particular payment batch. There are lot of references about FINSTA01, however, this is for account level status response.
If anybody know the equivalent idoc message type for EDIFACT BANSTA, kindly let me know.
Thanks in advance.
Regards,
Ravi

Thanks raja shekar. I posted this thread in ABAP development forum.

Error monitoring through workflow for idoc with message type ORDRSP

Hi All,
Through WE19 I am trying to post a failed idoc ie idoc in 51 status for message type ORDRSP to check whether the event IDOCORDRSP-INPUTERROROCCURED event is triggering or not. Though the idoc is going into 51 status and partner profile is maintained I cannot find this event in SWEL. I checked in fm IDOC_INPUT_ORDRSP fm and found that workflow_result is 99999.
Can anybody tell me why the event is not getting triggered for the message type ORDRSP or where do I debug to find out what is going wrong. IDOC_INPUT_ORDRSP fm is getting called from BUS2012 'S method confirmfromORDRSP which is very strange.So I am not getting where do I debug.
Regards
Suchandra

Hi All,
Solved it by my self.. To trigger the event we need to populate the EDIDC control record in WE19 and press standard inbound button 'not test by inbound fm) and then the inputerroroccured event will trigger...
Regards
Suchandra

MB1B transfer posting Idoc/Message type for outbound and inbound

Hello All
Can anyone tell me the idoc/message type for movement type 313 outbound and 315 inbound to SAP. This is for MB1B Enter Transfer Positing.
Thanks
Ricky

Its WMMBXY

Determination of QOS for IDOC messages

Similar Messages

Maybe you are looking for