List IDoc message tpyes and description

I've been asked to provide a listing of all the IDOC message types and it's associated description.
Does anyone know what table holds this information or a t-code that will allow me to create a file listing the message tpyes and descriptions?

Use We81 --> Print -->Export

Similar Messages

Idoc Message type and Process Cosde for CJ01 transaction

Hi,
What is the Idoc message type and inbound Process code for CJ01 transdaction?
Is there Any standard procedure to find out Idoc Mesage type and process codes for particular application?
Thanks.

Hi,
All the sending and receiving programs(transaction) start with BD. e.g. if you want to send the material you can use the BD10 transaction and IDOC is available for the same.
Go to se93 and search for BD* and look for the description.
Regards,
Nilesh.

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

CRM Order Message number and description and Notes

Hi
   we have Error/warning messages and notes in CRMD_ORDER (ie in CRM sales order). I am looking to get the tables for message number and notes. The purpose for this is I need to give these details to BW team for extraction. The standard extractor doesnt have these fields (ie message number or notes)
Here is the research I have done till now
1) for Messages people are suggesting to use FM - CRM_MESSAGES_DISPLAY which gives Log handle and Message number. with this data call CRM_MESSAGES_GET_MSG_INFO and this will give the Application area and message number which can be queried in T100 table
2) for notes I was suggested to use the FM - READ_TEXT
The option I have is use a user exit (extractor) and populate these data in the extractor before sending it to BW
Can you please let me know if message number and notes in a order can be directly queried from tables (is there a link table that connects the order GUID to the message table (T100) ?

Hi Veena
     I tried this but it doesnt get me to the actual notes. I was able to query STXH which doesnt have the actual notes. So I further went into STXL table where there is a field called "Data" which looks like a big GUID but not sure if there is a another table I need to plug this to get the actual notes.
     What I heard from the ABAP team is that there is no way to get this data through direct or link tables. We have to use the READ_TEXT FM
Edited by: Vikas BhumiReddy on Jul 6, 2011 4:55 PM

Recently a new display area has been added (giving a lot of technical details) between the list of messages above and an opened message below. HOw can I remove

No further details.

Thank you very much Gnospen.
I have just changed the setting and, voila, the display is as I want it.

How can I display the IDOC message type descriptions

I've been asked to provide a listing of all the IDOC message types and it's associated description.
Does anyone know what table holds this information or a t-code that will allow me to create a file listing the message tpyes and descriptions?

Hi Timothy,
The correct table to get this information is from SAP table EDIMSGT. You can view/download the contents of this table via transaction SE16.
Hope this helps and please don't forget to reward points.
Cheers,
Sougata.

Message types and idoc types

hi,
     i need the list of message types and idoc types for edi.
      can any one of u pls send it.

Hi,
Check the OSS notes 104606.
The following list maps the logical messages and IDoc types to the corresponding ANSI X12 transaction sets.That is, the logical message can be copied to the transaction sets named.
204 Motor carrier shipment information
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
           The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880)
           The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
           The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
           For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
           For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
           The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELFOR the IDOC type DELFOR01.
832 Price catalog (also 879, 888, 889)
           The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
           The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
           The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
           The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04.Outbound processing is supported.
850 Purchase order or order (also 875)
           The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
           The logical message is PROACT, the IDoc type PROACT01.
855 Order confirmation (also 865)
           The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
           For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
           For the delivery in the SAP application, the logic message is DESADV, the IDoc types DESADV01 (to be discontinued), DELVRY01 and DELVRY02.
860 Ordering modification (also 876)
           The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
           The logical message is GSVERF, the IDoc type GSVERF01.
862 Delivery schedule (FAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDOC type DELFOR01.
864 Text message
           The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
           The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
           The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional acknowledgment
           This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
           "22" Shipping OK, acknowledgment has yet to come
           "16" Functional acknowledgment positive
           "17" Functional acknowledgment negative
           The status values "14" and "15" are available for the Interchange Acknowledgment accordingly. Source code corrections
Cheers
VJ

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

IDOC Message type for EDI 947- 'Warehouse Inventory Adjustment Advice'

Dear Guru's
I am in a EDI-IDOC project for my Client. Where a customer is treating my client as 3rd party warehouse. we have a scenario where I wanted to Trigger OutBond EDI 947 (Warehouse Inventory Adjustment Advice) from MIGO/MB1A/MB1B and MB1C. Can any one tell me what is the Standard IDOC message type and Basic type i can use.
You kind help on this will be great full to me.
With Regards,
M. Rajendran.

Hi Sridhar,
Thanks a lot for your reply. I need to try with the proposed message type. Hope it works fine.
With Best Regards,
M. Rajendran.

Question IDoc-Messages

Hi,
I send an IDoc-Message from R3 to XI. So, in the transaction "sxmb_moni", I see in the field "ACK. Status" following entry:
"Acknowledgement not possible"
Is it possible to disabled this entry, so that the field "ACK Status" has no entries?
Thanks.
Regards
Stefan

Hi,
idx_noale is not transaction,
Whatever version you are using , just run SE38 and give the program name IDX_NOALE and give the port and Idoc message type, and check the changes by seeing the table
IDXNOALE with the transaction SE16 - table name : IDXNOALE
you can check these info in the below link - 3.4 section
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
Regards
Chilla

IDoc Message Packages

All,
I went through Sravya's blog on "XI:Idoc Message Packages" and have a question.. probably a non-issue. The blog says you need to activate the IDoc message packages through transaction IDXPW. In that screen one of the value it asks is the message id (earlier message of the same IDoc type).
Does this mean that we need to activate it every time with a new message id? or is it just that the IDXPW needs this message id to get the other parameters like sender id / receiver id / job id?
Or is this done only once and message packaging will be done for all the messages of the same IDoc type?
Thanks.

Hi
Check the following help doc
http://help.sap.com/saphelp_nw04/helpdata/en/99/2653429392ab53e10000000a1550b0/frameset.htm
Looks like you need to activate everytime..
Regards
krishna
<i>Note: Reward points if helpful</i>

IDOC question on Message type and Basic Type - Partner Profile

Hi all,
I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
My question is about the setup of Partner Profile creation (WE20).
When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
Questions:
1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables. I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
Thanks.
tuff

Tuff,
Below are my thoughts,
There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order - ORDRSP.
And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
Regards,
Chen

LSMW with IDOC Message type COND_A and Basic type COND_A01

Hi Sap All.
in my project we using the LSMW with IDOC Message type COND_A and Basic type COND_A01 and now the requirement is to know the list of the tables which will be updated when i do the LSMW Migration with this IDOC Basic type.
i have tried to know the list of the tables updated by entering into the transaction we30 and looking at the segments E1KOMG,E1KONH, E1KONP,E1KONM,E1KONW and i found that the following below are the list of tables which gets updated when i populate the data into IDOC Message type COND_A and Basic type COND_A01.
KOMG,KONH,KONP,KONM,KONW.
please correct me if iam wrong.
regards.
Varma

Hi Varma,
The tables mentioned by you definitely get updated, i guess you can add KONV to the list too, but to be a 100% sure, enable SQL trace and process an IDOC. Then you can look for Insert/Modify/Update statements to get a list of the tables that get updated.
Regards,
Chen

DIFFERENCE BETWEEN iDOC MESSAGING AND bDOC MESSAGING

hI
gurus what is the diffrence between idoc messaging and bdoc messaging?
K. Mangalum

Hi Kumara,
BDOC:
Container of business data that belongs together, for example customer, contact person, order or activity. This means that it contains all required information for a business process. The technical representation of a BDoc type is completely independent. There are many possible representations for a BDoc type.
For example, a BDoc type can be represented as follows:
as a collection of internal ABAP table structures (on the CRM Server),
by ADO record sets (on mobile clients),
as an XML form (for non-SAP systems), or,
as an IDoc.
Therefore a BDoc type is a semantic collection of business data and not a syntactical description.
There are three classes of BDoc types:
BDoc types exclusively used for mobile applications
They consist of a hierarchical data segment structure with assignment to database tables.
BDoc types for synchronization between the consolidated database in the CRM Server and mobile applications
They consist of a hierarchical segment structure with assignment to database tables.
BDoc types exclusively used for non-mobile applications
They consist of:
a hierarchical segment structure with no assignment to database tables,
additional data (complex data type modeled in the ABAP Dictionary)
Standard BDoc types are provided by SAP. Additional BDoc types can be modeled by customers.
Idoc:
IDOC: An intermediate document, container for exchanging data between R/3 and other SAP and non-SAP applications. Structured collection of segments. Segments are structured collection of data elements.
General Structure
IDocs contain administration information for technical processing, as well as the actual application data, which is stored in segments. A segment comprises segment fields as the smallest unit of the IDoc - comparable with the data elements from the EDIFACT standard.
In the SAP System, the processing status ("what has happened to the IDoc before now?") is stored in the IDoc status information. The status information also contains details about errors and indicates the data in which the error occurred. This status information is not forwarded as part of the IDoc but separately using "status processing".
IDoc types (special structure)
An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). For example, segment E1EDPT1 (document item text identification) is a child segment of segment E1EDP01 (document item data, general) in IDoc type EXPINV01 (export billing) and a child segment of E1EDP07 (order data shipping notification) in IDoc type DESADV01 (shipping notification). The segment, therefore, is used in several contexts and is the "child" of several "parents".
CRM Bdoc and IDoc are both persisted data structures.
Idoc works on a particular technology called ALE and is used for data exchange between two R/3 systems
Regards,
Satish Mathala

What is inbound XML message type and idoc type in Purchase Order response

Hi ,
We are on SRM 7 ECS , support pack SAPKIBKV08.
We have a process in which vendor will send a Purchase Order response which will be
converted to XML format by a middleware. This XML message will come to
SRM and post a POR. I want to do the EDI mapping for this XML message,
but there is no message type and idoc type in SRM for Purchase Order
response. How do I map my message type in SRM to the vendor sent fields
in middleware .
Please advise
Rgds
Sumendra

Hi,
You can process with XML without IDoc.
Vendor-> (XML) -> PI -> (XML) -> SRM.
Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
http://esworkplace.sap.com
Regards,
Masa

List IDoc message tpyes and description

Similar Messages

Maybe you are looking for