Difference between message type and idoc type

Hi
difference between message type and idoc type
Regards
Rama

Hi,
Message Type:
A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterises the data sent across systems and relates to the structure of the data called an IDOC type.
Diff. with IDOC type
An IDoc type specifies the structure of the data.
A message type specifies the meaning of the data
Diff. b/w IDOC type and IDOC
An IDoc type is the definition of a specific data structure.
An IDoc is an actual instance of data based on an IDoc type. Therefore, there can be many IDocs created from a single IDoc type.
Example:
MATMAS is the message type and MATMAS05 is IDoc type for Material Master.
Thanks,
Shankar

Similar Messages

Message type and idoc type

hi all,
i'm working on integration between sap and non sap.can anyone please tell me the message types and idoc types available for Funds Management and Project system modules.it will be of a great help,full points will be alloted imm.

What data you want to send / receive.
The site contains all message types which sap provides.
You can select your release and check in FI .
You can also check in tcode WE81 for available doc types .
Some of them I found are
GLCORE     Master data G/L accounts (CORE IDOC)
GLFETC     Request G/L accounts
GLM000     Test reduction GLMAST
GLMAST     Master data G/L accounts (master IDOC)
GLROLL     FI-GLX message type rollup
Your requirement is not clear as to what you want to send / receive with IDOCS.
Cheers

Message type and IDoc type to update a sales order

I can create sales order at WE19 by the message type SALESORDER_CREATEFROMDAT2 and IDoc type SALESORDER_CREATEFROMDAT202 . Can I use the same message type and IDoc type to update a sales document (sales order) and also how can I do (I mean, which structures should I use; at E1BPSDHD1X - UPDATEFLAG what should I enter? Put an X to update a document or etsc?)? I enter the "E1BPSDHD1X - UPDATEFLAG" as X, "E1BP_SENDER - LOG_SYSTEM", "E1BPSDITM - ITM_NUMBER", " E1BPSDITM - MATERIAL", "E1BPPARNR - PARTN_ROLE", "E1BPPARNR - PARTN_NUMB" and "E1BPSCHDL - REQ_QTY". The sales order quantity is at "E1BPSCHDL - REQ_QTY" and it is the field that I want to update. When I look at the transaction code BD87, I see the status text as "Enter a document number between 0005000000 and 0005999999". I cannot update the order. How can I update it? Canybody explain me in a detailed manner?
Thanks in advance....
Edited by: Hikmet Akcali on Oct 21, 2009 4:00 PM

At the IDoc type pop-up selection, there are 3 types. These are: ORD_ID01, ORDERS05 and /NFM/ORDERS05. SAP system component version is SAP ECC 6.0 . I choose ORD_ID01. There are structures EDI_Z1, EDI_Z3, EDI_Z5, EDI_Z9 and EDI_Z53. Where should I enter the number of the sales document to be updated? Also, which function module should I choose?
Edited by: Hikmet Akcali on Oct 21, 2009 5:34 PM

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

What is the difference between partner function and partner type

Hi Gurus,
What is the difference between partner function and partner type?
Thanks,
Paul

Hi John,
The partner types allow us to distinguish between different business partners such as customer, vendor, employee etc and the partner functions represent the functionality or role each partner plays within the business transaction.
For example under the partner type Customer, you will find - Sold to party, Ship to party, Bill to party, Payer.
The business partners that exist in the market place are represented with a partner type in the R/3 system. Examples of business partners are customer, vendor, employee and contact person.
The following partner types are defined in the partner processing for the sales & distribution module
a.     AP contact person (06)
b.     KU customer (07)
c.     LI vendor (08)
d.     PE employee/personnel (09)
Assigning the partner functions in the SAP system determines the functions of particular partner in the sales process. One partner may take on several functions also.
REWARD POINTS IF HELPFUL
Regards
Sai

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

Message type and IDoc type for PGI-GR?

hi all,
I have to send the PGI through ALE which have to create GR . So please mention the Message type , output type of message control and IDoc type?
Thanks
Vamshi

Hi,
The Idoc Types for Post Goods Issue are
MBGMCR01 / MBGMCR02.
Pls check the Message type in tcode WE82.
For output type GOTO transaction NACE-->Application V2.
hope this helps.
Regards,
Sharath
Edited by: sharath on Jun 24, 2008 7:16 PM

Difference between Message monitoring and end tot end monitoring.

Hi,
What exactly is the difference between message monitoring and end to end monitoring?
I read that message monitoring is used by end to end monitoring. Then why do we have two separate monitoring options?
Thanks
Hari.

End-to-End Monitoring
You use end-to-end monitoring in the following cases:
●      If you want to monitor message processing steps in a number of SAP components (to be configured).
●      If you want to monitor the path of individual messages through these SAP components, from start to end.
Message Monitoring
You use message monitoring in the following cases:
●      To track the status of messages
●      To find errors that have occurred and establish what caused them
for detail see this
Message Monitoring
http://help.sap.com/saphelp_nw04/helpdata/en/2f/4e313f8815d036e10000000a114084/frameset.htm
End-to-End Monitoring
http://help.sap.com/saphelp_nw04/helpdata/EN/82/9e8dfe9eadbd4b9194c433e646b84e/content.htm

What is the difference between Message Monitoring and End-to-End monitoring

Hi experts,what is the difference between Message Monitoring and End-to-End monitoring? and What is the difference between Value Mapping and Fix value?
Thanks,
Manoj

HII
You use message monitoring in the following cases:
● To track the status of messages
● To find errors that have occurred and establish what caused them
Check this help for further info:
http://help.sap.com/saphelp_nw04/helpdata/en/2f/4e313f8815d036e10000000a114084/content.htm
You use end-to-end monitoring in the following cases:
● If you want to monitor message processing steps in a number of SAP components (to be configured).
● If you want to monitor the path of individual messages through these SAP components, from start to end.
Check this help for further info:
http://help.sap.com/saphelp_nw04/helpdata/en/82/9e8dfe9eadbd4b9194c433e646b84e/content.htm
also refer this doc...gives more insight on various monitoring:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0b4580be-0601-0010-d3ad-bd6ce51ae916
... End-to-end monitoring in SAP XI provides a graphical overview of the different XI
components and the message flow between them. It is based on the Process Monitoring Infrastructure (PMI).
ans also
http://help.sap.com/saphelp_nw2004s/helpdata/en/7c/14b5765255e345a9e3f044f1e9bbbf/frameset.htm
You use message monitoring in the following cases:
1 To track the status of messages
2 To find errors that have occurred and establish what caused them
Check this help for further info:
http://help.sap.com/saphelp_nw04/helpdata/en/2f/4e313f8815d036e10000000a114084/content.htm
You use end-to-end monitoring in the following cases:
1 If you want to monitor message processing steps in a number of SAP components (to be configured).
2 If you want to monitor the path of individual messages through these SAP components, from start to end.
Check this help for further info:
http://help.sap.com/saphelp_nw04/helpdata/en/82/9e8dfe9eadbd4b9194c433e646b84e/content.htm
End-to-end monitoring includes message monitoring, adapter monitoring, BPE if BPM is involved.. so end-to-end monitoring tells you complete description of your scenario......but message monitoring is concerned only with source message coming to target message successfully generated.

Std Msg Type and Idoc Type to send multiple characteristics for equipment

Hello Experts,
I have the requirement to send all the assigned characteristics linked to an Equipment or linked to a Material, along with the all possible values BUT require only standard Message Type and Idoc Basic Type.
I found Message Type = CHRMAS and Idoc Type = CHRMAS04, BUT it contain information of ONLY one characteristic, not solve my objective (multiple characteristics in one Idoc)
Will you please provide me any standard Message Type and Idoc Basic Type that solve my above requirement?
Thanks in advance,
akg

Hello Experts,
Can you at least tell me, is there anything standrad that can fulfill my above requirement?
If not then I will proceed with custom developments; and in this case is there any complexity to transmit the custom Idoc?
Thanks in advance,
Thanks & Regards
akg

Difference between message processor and support team

Gurus ,
what is the difference between the "Message Processor" field and "support team" field available in support desk message .
we are defining a three level support . with thord level as SAP GLOBAL SUPPORT .
need i have to give first level in message processor and the other on the support team ?
(or)
what is the exact purpose and difference of those fields

HI Susin,
Let me tell you what i know about this issue
1) you create your organisation structure in ppoma_crm where Support Team BP is automatically created and you do not need to create explicitly.
2) Message processor is BP of type employee with object type US.
can be said member of Support team (BP) which you will be assigning in the ppoma_crm transaction.This user should also have an valid S User ID.
This support team configuration in transaction ppoma_crm has its direct link with transaction
crm_dno_monitor where you will filtering the messages belongs to various Support teams.
Regards,
Vijay.

Basic type and idoc type

hi iam having z-basic type how to find what is the standard idoc type(for ex MATMAS,Creamas) for that

Step1. Go to WE30 and give the extended IDoc name
Step2. Check the extension button and click on display
Step3. Click on header button (Top 3rd left button)
Step4. In Technical Attributes, you will get the name under "Linked Basic Type"
Hope it solves your query...
Regards,
Prasoon Sahay
Edited by: Prasoon Sahay on Sep 2, 2009 2:18 PM

Difference between Message View and Console Output view on JDeveloper 3.0

Hello,
My name is Vani Bansoodeb and I have just started learning Java.
I am using Oracle JDeveloper 3.0 as IDE.
I was trying the Synch.java(see below) program to learn how to
use the "synchronized" key word.
However, I got 2 diffent outputs, depending on the output medium.
With the MESSAGE VIEW, I got the following output:
[Hello
[Synch
[World
With the CONSOLE WINDOW (i.e.DOS Prompt), I got the following output:
[Hello]
[Synch]
[World]
Could anyone please tell me why the right square bracket is printing on
a new line in the first case?
Thanx,
Vani
------------Synch.java--------------------------------------------------
class Callme {
synchronized void call(String msg) {
System.out.print("[" + msg);
try{
Thread.sleep(1000);
}catch(InterruptedException e){
System.out.println("Interrupted");
System.out.println("]");
class Caller implements Runnable{
String msg;
Callme target;
Thread t;
public Caller(Callme targ, String s){
target = targ;
msg = s;
t = new Thread(this);
t.start();
public void run(){
target.call(msg);
class Synch{
public static void main(String args[]){
Callme target = new Callme();
Caller ob1 = new Caller(target, "Hello");
Caller ob2 = new Caller(target, "Synch");
Caller ob3 = new Caller(target, "World");
try{
ob1.t.join();
ob2.t.join();
ob3.t.join();
}catch(InterruptedException e){
System.out.println("Exception Interrupted");
}

Thanks for your feedback,
What I was wondering is: Why has the db to look for distinct values? There is a unique ocnstraint on this column so the DB should in advance know that there will be no dublicate.
It would be intressting to check in the Oracle Optimizer does it the same way on a 10g DB.

We57 link between logmessage and idoc type does not exist

in we57
i have fm idoc_input_pordcr
basic type pordcr101
message type pordcr
when i try to save
gives message link between log message pordcr and idoc type does not exist.
will not let me save
where do i go to link these up

Hi,
Transaction WE82, assign Idoc type to message type.
Regards
Vijaya

Diff ...between Bdoc's and Idoc's in XI integration !

Hi All
In XI integration what is the difference between Bdoc's and Idoc's ?
Both or same ? different ? how the integration will be done ?
Adv...thanx and regards
kiran LVS

Hi
An IDoc transfer is quicker in comparison to SOAP/XML because the IDoc document contains no metadata information (tags)unlike an XML document, and therefore, the size of document sent down the line is substantially smaller in comparison.
IDocs can be used to send messages to the SAP Exchange Infrastructure where an IDoc XML document will be established and mapped into other XML Schemata. The XML messages can be routed to other Business Systems. IDocs can be used to send messages to the Business Connector where an IDoc XML document will beestablished and mapped into other XML Schemata such as Rosetta Net, xCBL or customers ownschemata.IDocs can be used to send messages to a flat file.IDocs can be used to send messages to an ALE converter, where IDocs are mapped into standardizedmessage formats (EDI communication).IDocs can be used to send messages to an ALE Messaging System. In contrast to an ALE converter, the message handler will not perform any conversion or mapping but instead receives IDocs and sends
them to applications for processing. IDocs can be used to send messages to an EDI Sub-System. In contrast to an ALE converter, the EDISub-System does not use direct program-to-program communication for transferring IDocs.
A messaging BDoc consists of up to two parts:
Part 1: classical part
This part is mandatory.
The classical part consists of a BDoc header and segments, which may be arranged in a hierarchical fashion. The segments of the classical part are not mapped to database tables.
This part is to be modeled with the (CRM Server based) BDoc Modeler. Only the classical part is used to determine the receivers of mBDoc messages. Since there is no mapping to database tables (that is, no CDB), this part always needs to be filled completely by the application at runtime.
Part 2: Extension part
This part is optional.
The complex data type is modeled with the Data Repository Tools (SE11).
The extension does only exist for messaging BDocs.
The extension part is used to hold delta or extract data intended to pass into the CRM Server application (inbound case) or to send to remote systems (outbound case). The extension part cannot be used for receiver determination.
Bdocs are specific to CRM. They do not leave the CRM system, but perform their updates from it. They are much bigger because they contain the entire data-model of the object they are supposed to update. They can contain delta or creation information and can be processed by flow processes.
So they are data-containers that are used to update CRM & CRM dependent systems.
Idocs are data-containers as well, but they are structured for their purpose (not for the object they contain) and they can be transfered between systems.

Difference between message type and idoc type

Similar Messages

Maybe you are looking for