Need of datatype, message type and message interface

hai
can any one tell me..
why we need three level heirarchy for a message in XI
regards,
Madhav

Hi Madhav,
let us recall them by their name and identify their roll.
Data type : suppose that you want to form a message but that comprises of many different types of data . as in numeric, string, characters.So at bottom you will have to define datatype.
Message Type: having defined data type now you want to form a meaningful message and that message can be formed by combining many such different data types in to one message type.
Message interface : No you have created message type but now that you want to use it some where, then you will have to interface it. So you will hace to define a message interface.
Vishal
Please reward with points for useful Help

Similar Messages

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

Message type and datatype

Hi all,
what is the differnce between data type and message type?
regards,
keerthi

Hi,
Data type defines the structure of your xml message.Message type is the wrapper of data type.You will be using your message type while mapping and not the data type.Its the abstraction concept used in oops
A data type in a programming language is a set of data with values having predefined characteristics. Examples of data types are: integer, floating point unit number, character, string, and pointer.
The characteristic of columns and variables that defines what types of data values they can store. Examples include character, floating point and integer
Check out the details:
http://en.wikipedia.org/wiki/Data_type
A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
details:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/content.htm
2) Regarding the difference between XI 3.0 and PI 7.0, this threads will clear your doubts:
difference between XI 3.0 and P.I 7.0
Difference/ changes from XI 3.0 to PI 7.0
data types just define the abstract XSD structure . but since In XI we are using XML langauge. so We need a Root element in our message. that root element is added by Messagr type.
means data type is just an abstarct structure and message type add root element to data type.
and one message type corresponds to one data type only............
Thanks
swarup

Data Type, Message Type and Mapping for FTP

Thanks in advance for your replies.
As our first production XI scenario, we need to move several (at least 46) files from our SAP instance to a couple of different servers to support our legacy systems. Once all locations are on SAP this requirement should go away.
I only want to pick up the file from the one server and place it on the other and this leads me to some questions.
How do I define the Data Type and Message Type for each of the files? Do I need to consider the size of the record in each interface and create DT/MT with different sizes.
Do I need a mapping program that simply maps one structure to the other?

I recently completed a similar exercise.
It looks like this...
server1 ftp (Sender - delete file) - XI - Server2 ftp (receiver - create file). This will move the file from one server to another.
I used the same schema and mapped fields on a one to one basis.
The Size of the files I process are between 6kb and 500kb each, but the mapping/fields remain constant, just the numebr of items change.
Worked seemelessly for the last three weeks (since go-live)

EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

Hi All,
We are facing some issues regarding EDI 821 and EDI 823 file mappings.
We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
EDI 823 - Lock Box
Basic IDOC type - FINSTA01
Message type - FINSTA
Process Code - FINS
The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
EDI 821 -
Basic IDOC type - PEXR2002
Message type - PAYEXT OR REMADV
Process Code - PEXC OR REMA
We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
We are trying different combinations but nothing is working so far.
I need the following things to proceed furthur.
1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
2)If those are not correct, can you please let me know the correct entries
3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then I can re check it.
4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
thanks in advance for all your help.
Please let me know if my question is not clear.
Thanks,
Ramesh.

Hi Ramesh,
I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
Are you can give me the exact error and i can help you as well.
Thanks,
Mahesh.

BDoc: Related Data Type and Message Structure

Related Data Type and Message Structure are two attributes of a BDoc. Can anyone tell what they are used for?
Thanks in advance.
Regards,
Hui
BTW: Mush reward for good answers.

A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
· More than one message interface can use the same message type. For example, an asynchronous outbound message interface and an asynchronous inbound message interface can reference the same message type because the request message does not need to be mapped.
· When defining a message mapping you can directly reference message types to map messages from an outbound interface to messages from a receiver interface.
For technical reasons, a data type is not sufficient to describe the instance of a message. In XML schema, data types are defined as abstract types that are not yet fixed to an element. You can only describe an instance of a message when you have specified a data type as an element type. Therefore, a message type defines the root element of a message.
A message type does not define the direction of the message exchange, in other words, whether it is a request or a response. In exceptional cases you can use the same message type for both the request and the response message.

Port, Message type and Function Group

Hai,
Iam working on an inbound process for four different Partners.
Is there any need of Port for Inbound?
Shall i use the same message type and Idoc type?
And what about the function Group?
Thanks
Avi

Hello,
<b> If the functionality is same , you can use the same function Group.
If functionality is different , you want to use different Function Group.
Obvisouly, it is suggested to use different Message types .
If you are using same fields ,you can use the same idoc type.
depends on the scenior , the process code is needed. Generally no need.</b>
Thanks
Manju

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

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

Updating import declarations with duty types and message types

Hi All,
I am a GTS developer. There are configuration changes in the system . As a result, the import declarations and presentation documents created in 2014 and 2013 have to be updated with :
1.) Replace old duty types with new ones in the logistic costs tab.
2.) Replace old message types with new ones in the communication tab.
Any pointers on how to go about , regarding the table links between the duty types and declarations, message types and declarations , Function modules would be very helpful. Thanks much in advance.
Best Regards
Shankarnarayan.K.

Hi SK,
That's a strange request. Of course the configuration changes invalidate the old Declarations, but your attempt to re-write history isn't likely to achieve much.
Since the messaging cannot be repeated, it makes no sense to update the documents. And similarly, since the Declarations cannot be re-sent, updating the Duty Types will have no effect.
But if you must do it, here are some tips:
For the duty calculation, you need to update entries in table /SAPSLL/LEGCULC. Assuming the the Duty Types haven't been re-named, you should loop through the entries and use MOVE-CORRESPONDING to copy the values from the configuration tables /SAPSLL/TLC_ASC (key = LAUNR) and /SAPSLL/TLC_AAR (key = TLC_AAR, matching /SAPSLL/LEGCULC-TLC_AART). First check that all relevant fields have the same name, considering the Data Elements involved.
For the messages, you need to update entries in table /SAPSLL/LEGMES. However, I have no idea which fields your esteemed Application Consultant might have changed there, so can't immediately advise what should be copied.
In both cases, the link to the Customs Declarations is that GUID_MOBJ = /SAPSLL/CUHD-GUID_CUHD, and MOBJT = 'O' (that's the letter, not number zero).
Hope that helps.
Regards,
Dave

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

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 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 type, message type and process code for EDI 940 & 945

Hi,
We are implementing a scenario wherein we are required to send a Wharehouse Shipping Order to the warehouse (forwarding agent) using EDI 940. The output of the o/b is triggered from the Delivery (VA01) after creation of a Delivery in SAP. Once the warehouse ships the goods, it notifies us back by sending EDI 945 (Warehouse Shipping Advice). Using this inbound 945 we are required to update the existing delivery in SAP, i.e., it should do the Pick, Pack and PGI.
Can someone tell me which Idoc type, Message Type and Process code should be used for the above scenario.
Thanks in advance for the help.
Regards,
Gajendra

Hi Gajendra,
For EDI940, you can use message type SHPORD or WHSORD, IDOC type DELVRY01 and process code DELV.
For EDI945, you can use message type SHPCON or WHSCON, IDoc type DELVRY01 and process code DELV.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

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.

Need of datatype, message type and message interface

Similar Messages

Maybe you are looking for