Why message type if idoc type or idoc is already there.

Experts.
this has been posted several times and i gone through so many threads but stil some confusion . So anyone can tell in simple terms what is the difference and why sap has given this two instead of one.
Diff. with IDOC type
An IDoc type specifies the structure of the data.
A message type specifies the meaning of the data
*****from the above statements , by seeing the name of the idoc type ex matmas01 also we ca n say that it is used for material data, then why message type matmas needed?

Hi,
Idoc type means combination of segements
Message type means Combination of idoc type
or
Message type mean combination of Idoc type + Extension idoc type( Custom segments added to idoc type)..
Example:-
If you want to fill the data to custom segment which is available at exension idoc ...
then first check the message type then check basic idoc type then check it contains exetension idoc type ..then fill the segment
Generally the communication occurs between system through message type...
Prabhudas

Similar Messages

Want to add multiple idoc type with single message type.

Hi Gurus,
I have a problem. I want to add multiple idoc type with single message type in WE20.
How we can do this in WE20 or is there any other way to do that?
Please help me.
Thanks in advance.
Srimanta.

hi,
basically in partner profile i.e. in we20 , we add details to the receiver / sender port that we have created using we21.
so what exactly we do in that is that we first use the message type for those idocs that we have created.
now based on those message type we create a process code. now this is the reason why you cannot apply several message types with the same name in we20... as process code is unque for each message type.
so thats why you can only assign the same message name to several idocs in we82 and then in we20 define the process code for that message type.
it will solve your problem.
hope this will help you!!!
Thanks & regards,
punit raval.

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

Basic type, Idoc type, Message type

hi,
can anyone please explain me the exact difference between basic type, idoc type and message type...
Thanks in advance,
Krish

Hi,
Idoc Types and the Basic Types are the same which is provided by SAP Standard Idoc Names.This will have the releases like 01, 02 ,03
And the Message type names will be the same as Idoc type name with out releases
The combination of the message type & Idoc type will be------CREMAS.CREMAS03( Message type.Idoc type)
Check this Screen for better clarity , and we added some extra Segments to the standard Idoc also, so thats why it has the Extension also
http://img182.imageshack.us/img182/3749/64960008jl7.jpg
Regards
Seshagiri
Edited by: N V Seshagiri on Aug 20, 2008 8:51 AM

Message type for Scheduling Agreement - Outbound IDoc

Hi All,
I have to create an Idoc for Scheduling Agreement through a Z program based on some conditions. I have bit confusion, whether i can use Idoc type for Orders(e.g ORDERS01..05) & Message type ORDERS / ORDCHG to generate Outbound Idoc.
Already there is process code for for ORDCHG mappig IDOC_OUTPUT_ORDCHG & ORDERS mappig IDOC_OUTPUT_ORDERS. Whether there will be any impact on this.
Appreciate your help.
Regards,
Anbalagan.

Hi Anji,
Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
But I have to send Outbound Idoc for a Schedule Agreement.
Whether the same Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
Please Advice.
Regards,
Anbalagan

Message type, Idoc type and process code in ALE/Idoc

Each Idoc version(creams01 or cremas03) will have seperate process codes in Inbound process?
Whether Message type triggers the process code or the Idoctype/idoc triggers the process code in Inbound process?
regards
Message was edited by: henry

Hi Henry,
About your question as how should you assign seperate process code for the same message type ( with different IDoc Type )-
In We42, the message type can be assigned to the processing code. But here you will find that along with message type there are two more fields - Message Code & Message Function.
You can use any one these to serve your purpose.
e.g. you can assign
-process code P1 to message type M with Message code 1
-process code P2 to message type M with Message code 2
Further these process types can be configured to call separate FMs.
Now depending on IDOC types your external system should populate the message type as well as Message code so that accordingly process code will be determined at the time of inbound processing.
I hope it's clear & correct
Thanks,
Ram

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

Urgent - Idoc type and the Message type

Hello
Its very urgent. I want to know the basic idoc type and the message type used for EDI 894 transmission (Delivery / Return Base Record). Please respond at the earliest.
Thanks in advance

HI
Pratibha
How are you ?
Please check the below links:
http://scn.sap.com/thread/990524
http://www.erpgreat.com/pm003.htm
http://scn.sap.com/thread/1386811
http://scn.sap.com/thread/1078741http://www.erpgreat.com/plant/what-is-equipment-master.htm
http://benxbrain.com/en/index.do?onInputProcessing%28brai_object_thread%29&001_threadid=0000835100&001_boardtype=01&sysid=PI1&pgmid=R3TR&object=TABL&obj_name=EQBS&child_param=
Mutti

IDOC type & Message type for posting GR against PO

Hi Experts
I want to Post Goods Receipt against Purchase Order using Idoc in Material Management & AFS ( Apparel Fashion & Footwear Solutions) module. so I want to know what is the Idoc type/ mesaage type for this?
& how to trigger the idoc & what are the settings need to be done for this?
Appreciate you quick responses.
Thanks
Rgds
Ramesh

Hi Ramesh,
is it not an abused thread (a litle)... as by using google or sdn search button, in 2min you have your answer of all your questions.
Tips: to find an IDoc type, in SAP, in WE60 or WE02, or BD87 or ..., use the search help button (F4) of field "message type" by giving the description "goodreceipt*".
For the triggering to outbound Idoc, think to "change pointer", or eventually "change document", table CDHDR, CDPOS.
Good search.
Regards
Mickael

Message Split: File to Multiple IDOC Types

Hi,
I'm attempting to perform a multi-mapping using BPM where I have File -> XI -> IDOC.
The result will be 3 DIFFERENT IDOC types, but depending on the payload of the file, not all will be created. I have followed the steps in this weblog: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2748. [original link is broken] [original link is broken] [original link is broken] [original link is broken]
This works fine as long as all 3 messages are being created, however if only 2 of 3 IDOCs are to be created, I receive an error in the PE.
I have set the occurances of the target messages as 0...1 in the Message and Interface Mappings.
Any ideas would be greatly appreciated.

><i>This works fine as long as all 3 messages are being created, however if only 2 of 3 IDOCs are to be created, I receive an error in the PE.</i>
Just noticed this
The reason is when you have a 1:N mapping inside the BPM, all messages need to be compulsorily be created. If you have 3 messages in the target side all 3 messages / idoc's need to be created as the output of your multimapping.
As a workaround, if the condition which you want to check does not exist and you do not want the idoc to be created, in the mappingcreate the idoc, use some dummy flag and then use a switch in the BPm to decide if the idoc is to be sent to the target system or not.
Regards
Bhavesh

EDI ANSI X12 and relavent IDOC types and messages...

Hi ,
    Is there any place where we can get the relevant Idoc types and messages for EDI Transacitons below:
210 -Motor Carrier Freight Details and Invoice
240 -Motor Carrier Package Status
753 -Request for Routing Instructions
754 -Routing Instructions
816-ORGANIZATIONAL RELATIONSHIPS
828-Debit Authorization
846- Inventory Inquiry/Advice
870-Order Status Report
Could you please help me?
Thanks and regards,
gowri

EDI ANSI X12 and relavent IDOC types and messages...
Posted: May 25, 2006 8:44 PM        Reply      E-mail this post
Hi Ravi,
     Thanks a lot for the reply. I have already checked this. In the ittoolbox.com is having some info about 214 but not about 210 and 240. I have already gone through the sapgenie.com but could able to get the relevant info on below transactions.I am basically looking for relevant idoc types and messages in SAP for the below ansix12 transactions .
Is there any place where we can get the relevant Idoc types and messages for EDI Transacitons below:
210 -Motor Carrier Freight Details and Invoice
240 -Motor Carrier Package Status
753 -Request for Routing Instructions
754 -Routing Instructions
816-ORGANIZATIONAL RELATIONSHIPS
828-Debit Authorization
846- Inventory Inquiry/Advice
870-Order Status Report

IDOC Types and their equivalent messages in EDIFACT and ANSI X12

Hi all, since I only have a list of messages in EDIFACT and ANSI X12 for release 4.6 B, I need to update the list from 6.0 version, but I don't have online support system to get it (OSS), it's note 104606 in OSS.
Can somebody give me a link to the full new updated list? Will surely give points with your helpful answers
Regards,

Hi,
Please check these perhaps they may help.
Mapping ANSI X12 to SAP Message Type and IDoc Type:
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), EDI - Inbound INVOIC posting configuration
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 logical message is DELINS (from the EDI standard ODETTE) or DELFOR, the IDoc type is 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 Ordering or order response (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 delivery in the SAP application, the logical message is DESADV, the IDoc types are DESADV01 (expires) or DELVRY01 and DELVRY02.
860 Ordering or order 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 logical message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDoc type is 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.
Regards,
Ferry Lianto

Idoc types and message types we use in IS-Retail

hi gurus,
can anyone tell me what are the idoc types and their message types that we use in SAP IS-Retail .
Thanks in advance
regards
gopal

Hello, these are the main idoc types used in sap retail:
'WPDBBY01' POS outbound: bonus buy conditions
'WPDCUR01' POS interface: Download exchange rates
'WPDNAC01' POS interface: Download products
'WPDSET01' POS interface: Download set assignments
'WPDTAX01' POS interface: Download tax rates
'WPDWGR01' POS interface: Download material group master
'WPUBON01' POS interface: Upload sales docs (trnsctns), non-aggregated
'WPUERR01' POS interface: Upload messages SRS/POS/SCS
'WPUFIB01' POS interface: Upload Fin.Acc. interface SRS/POS
'WPUKSR01' POS Interface: Inbound processing cashier data for POS stats
'WPUTAB01' POS interface: Upload day-end closing POS
'WPUUMS01' POS interface: Upload sales data (compressed)
'WPUWBW01' POS interface: Upload goods movements
'WP_EAN01' POS interface: Upload/Download EAN assignments
'WP_PER01' POS interface: Upload/Download person data
'WP_PLU01' POS interface: Upload/Download article master
'WP_PLU02' POS interface: material and condition (inbound and outb.)
'WTADDI01' Additionals
'WVINVE01' Store phy.inv.: phy.inv. docs outbound; count data inbound
'WVINVE02' Store phy.inv.: phy.inv. docs outbound; count data inbound
'W_WGRP01' Distribution of material groups
Regards,
Juan Carlos

Idoc types and message types

Hi ,
Anyone can send what are all the std idoc types and message types are there in SAP?
Coz i dnt have SAP.
Please let me know

The IDoc type indicates the SAP format that is to be used to interpret the data of a business transaction.
An IDoc type consists of the following components:
·       a control record
This is identical for each IDoc type.
·       several data records
One data record consists of a fixed key part and a variable data part. The data part is interpreted using segments, which differ depending on the IDoc type selected.
·       several status records
These are identical for each IDoc type and describe the statuses an IDoc has already passed through or the status an IDoc has attained.
You find various IDOC / Message types in SAP -
http://www.erpgenie.com/sapedi/message_types_masterdata.htm
IDoc Types - Message Types -Accounting Business Processes
IDoc Types - Message Types - HR Business Processes
IDoc Types - Message Types - Logistics Business Processes
Eg.
General       Message types / IDoc types / BAPI
Vendor        CREMAS / CREMAS02
Customer      DEBMAS / DEBMAS03
Accounting   Message types / IDoc types / BAPI
G/L account   GLMAST / GLMAST01
Cost center     COSMAS / COSMAS01
Cost element COELEM / COELEM01

Idoc types & message types

hi friends, please can somebody post different kinds of Idoc types and message types used in sd , from sd's point of view. and also explain giving examples if you could. thanks
points will be awarded for sure . thanks
seema roy

Dear Seema,
concerning EDI concept in SD: the EDI concept is intended to realize the sales and distribution process completely automatically with the help of electronical documents. These documents are sent from one customer to another, are processed mostly on the background and give a possibility to realize the sales process extremely efficiently.
If MM-customer would like to purchase the goods then he creates the IDOC of type ORDERS and send it to SD-customer. On the SD-side the IDOC is processed via the function module IDOC_INPUT_ORDERS and creates the sales order. As confirmation the SD-side can send to MM-side the Order-Response IDOC (function IDOC_OUTPUT_ORDERS). The MM-customer can every thime send a change to the existiong order, then on SD side the ORDCHG IDOC will be processed. It can change the order like in VA02. The creation of the invoice can be made via IDOC of message type INVOIC (function IDOC_OUTPUT_INVOIC).
So, the process can be realized completely automatically between SD and MM partners with the help of IDOCs: ORDERS, ORDCHG, ORDRSP, INVOIC.
That's all concerning the SD-EDI.
Additional processes in SD, where EDI are used:
1) application of delivery schedules to the scheduling agreement: IDOC of type DELINS
2) creation of a delivery order to the scheduling agreement: IDOC of type DELORD
3) creation of external agent service delivery to scheduling agreement: IDOC of type EDLNOT
4) creation of credit advice / credit memo in the frames of self-billing: IDOCs of type GSVERF, SBWAP and for external invoice creation SBINV.
It is all processes which are realized in the SD module via EDI.
There is not so much Customizing for EDI. The most entries are required by EDI for the scheduling agreement processing (DELINS, EDLNOT, SBINV). The Customizing of these processes is located in the Customizing of scheduling agreements: SPRO => Sales and Distribution => Sales => Sales Documents => Scheduling agreements with delivery schedules => Control EDI Inbound processing.
General EDI Customizing in SD is available under: SPRO => Sales and Distribution => Electronic Data Interchange => EDI messages => ...
I hope this info helps.
Kind regards,
Akmal Vakhidov
Development Support SAP, Walldorf/Germany

Why message type if idoc type or idoc is already there.

Similar Messages

Maybe you are looking for