One message type different IDoc Types

Hi All,
Can we use one message type and different data types based on the requirement in PI mapping.Basically I want to select mappings based on IDoc ...My requirement is to use different IDoc types for one message type in mapping ...will it work ?
Thanks ,
Vinay.

If you will be wanting to have 1 message producing different IDOCS types (to be meaning that not just multiple IDOCS of the same type) then this must be done via a BPM as the IDOC adapter will not be able to handle it by itself. Have a receiver determination step in the BPM for each IDOC type - you'll then be sending each via foreach block.

Similar Messages

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

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

Create a sequencial serial number for different Idoc Types

Hi,
we've got a legacy system which requires a serial number in a flat file for different Idoc types. The target filename for the three different Idoc types is exactly the same, lets say: InboundFile_nnnnn.xml (where nnnnn is the sequence number)
In the header of the file we will specify what type of file it is according to the Idoc that was received, but regardless of the idoc type, the sequence numbers for all three idoc types must be sequential. The files are placed on the target server using a receiver ftp adapter on the central adapter engine.
I would like to know if there is any way to store\maintain this sequence number in XI and use it accross different message mappings?
Your response is appreciated.
Thanks
Rudi
(and a merry christmas to you all

You can create a number range object in SNRO transaction abap stack in SAP XI and use that in the mapping by connecting through JCO in XI.RFC enable Number_Get_next.
check this for more info
/people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i

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

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 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

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

Multiple message types for IDoc types

Hi,
can we assign multiple message types to IDoc Types?
Is so How to make it
Thanks in Advance....
Regards
Sravya

Hi,
For an IDOC Basic Type is the structure which defines the skeleton of the data transfer like what all fields can be present, how many times a field can appear, is it mandatory etc.
A message type is a label used to identification.
Message type come into picture because we can use the same IDOC basic type for any number of applications. So it becomes necessary that we need some other tag to identify & distinguish between all these. Message Type helps in this cause.
Message type & Basic Type are linked in WE82.

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

Link between output type to Idoc type

Hi Gurus,
One basic question....How do we link sales document output type(eg BA00) to Idoc type/Message type.
I know from WE20 we do the partner profile setup and link the message type to idoc type and then we do the output determination,so now how does the system know for a particular output a specific idoc type has to trigger,is the link established when configuring thru we20 or is there any direct link to output type to Idoc type. I also checked WE82 but that dint help me either.
Thanks,
Vivek

Hi friend,
apart from the configuration of output type to idoc... etc.. the thing which triggers idoc is the message control along with partner profile.
the explanation can be more lengthy - but I just wanted to mention about message control.
Regards
sadhu kishore

Diff between IDOC TYPE & Basic IDOC TYPE ?

what is the Diff between IDOC TYPE & Basic IDOC TYPE ?

Hi,
IDoc type contains basic IDoc type and extension.
Extension is a sub-object which extends an existing basic IDoc type. Extension types are not delivered by SAP. They can be created by the customer.
Regards,
Ferry Lianto

Message type SHPCON, idoc type DELVRY01

Hi SAP Gurus,
I am using message type SHPCON and idoc type DELVRY01 with processing code DELV to post goods issue for a delivery note.
I tried to simulate the inbound entry via WE19. I was not able to proceed with the posting because I encountered error 51 in idoc.
Field EXIDV empty
Field VHILM empty
These fields are in E1EDL37 and E1EDL44 respectively, and referring to HU information in which we don't have.
What I have filled up are the fields:
E1EDL20-VBELN = DO num
E1EDL20-VSTEL = Plant
E1EDL18-QUALF = "PGI"
E1ADRM1-PARTNER_Q = "WE"
E1ADRM1-PARTNER_IQ = recv plant
E1EDTH13-QUALF = "015"
E1EDTH13-NTANF = date today
E1EDL24-POSNR = 000010
E1EDL24-MATNR = material num
E1EDL24-WERKS = delv plant
E1EDL24-LGORT = sloc
E1EDL24-LFIMG = quantity
E1EDL24-VRKME = unit
E1EDL24-LGMNG = quantity
E1EDL24-MEINS = unit
May I know how to avoid this or if I missed some fields that resulted to this error ? Or am I using the wrong message type?

Hari,
I can definitely use WE19 to reprocess it. However my problem is the source of this information. If we implement this process, we would not know where to get this information since we don't use handling units. To add to this, the field VHILM that the system is asking is "packaging material" which we don't use and don;t have.
How to get rid of these fields? In VL02N, there is no handling units when I click on the pack icon. Only the material and the quantity.
Thanks.

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

One Message, Call multiple IDOCS in PI 7.1

Hello SDN!!
We are trying to implement a scenario and curious if anyone has done this. We are looking to have one message exposed to another system, which will be mapped and sent to four different IDOCS on the same system. From some blogs it seems this really can't be done except by BPM. Is this the case, and if so, are there any good tips to do the most basic BPM to have this scenario complete? (Also all the documentation seems to be in 7.0)
Cheers
Devlin

Hello from the first response mapping without bpm it states it is not possible with IDOC
Messages that result from the split in a mapping-based message split are sent using one AE. So only adapters running on the AE are supported. In particular, this means that target IDOC message splits are not supported since the IDOC adapter is not part of the AE.
The other two blogs are nice, but wrong direction, instead of collecting IDOCs I was hoping to have one message split out to 4 IDOCS,
Cheers
Devlin

One message type different IDoc Types

Similar Messages

Maybe you are looking for