Same message type and two different IDOCS need to be triggered

Hi,
I have two idocs with same message type,the partner profile is same.
Please tell if there is any way to handle this situation without changing the message type.
Please do the needful.
Thanks,
Nivedita

Hi
We can have same message type for different idoc types.
ex:MATMAS.MATMAS01
MATMAS.MATMAS02
MATMAS.MATMAS03
In the above example MATMAS is the same message type for different idoc types.
Thanks

Similar Messages

Same message type in Diffrent Interface IDoc-HRMD_A

Hi All.
i am using standard message type HRMD_A iin one IDoc and have done coding in one of the Function Exit ..EXIT_SAPLRHA0_001
now if some other interface is also running using same satndard message type then how can i restritct my EXIT code to run for the 1st one only..like 1st one is running for country say Alaska and 2nd one for Ohio then how to make a check to diffrentiate between these two...as there is no Control data is populated before triggering this Function exit.i have done filteration in the exit like it will pass the data for the Alaska country only rest will be filtered out.but for the Ohio i want some other filyteration.Please assist.
Mona singh.

Hi Mona,
One question, just to see if I understood, the filter you want to use is by Company Code? or which is the field you want to use as a filter? You want some information to be sent to the destination and the other don't ?
Or you just want that the internal code in that Exit is to be executed for especific filter?
I ask, because there is a way to filter by company code the whole IDOC.
Regards
Edith

Same Message interface in two different namespace

Hi,
can we have same MI in two different namespaces(Sofwate componnent also different)?
Thanks
Ruban

The design objects is uniquely identified by combination of Object Name, Namespace, and SWC.
So in your case, it is not a problem.
Liang

Same message type

Hi,
is it possible to use the same message types in two different BPEL processes ?
If yes, could you show me an example ?
thank you & bye

Yes of course, just make sure the xsd's match. You can make sure the xsd's are the same in those BPEL processes by:
a) copy the .xsd's yourselves in each BPEL process (this violates the Edsger W. Dijkstra's design principle 'Avoid duplication of volatile information')
b) use a seperate BPEL process for storing all the common xsd's (unfortuately this requires that this process is deployed to the server before you can compile the other BPEL projects).
c) use svn:externals or a custom copy script that will make sure that there is only one source for the XSD's
The IT-eye article on Generate facade classes for multiple Oracle BPEL usertask payload structures at once might be usefull.
Regards,
PieterB

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

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

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

IDoc processing for same message type but diff extensions

Hi
I want to send idoc when a material is changed. Everything is in place and have also done a test scenario. In partner profile i had the message type linked to basic type and tested which is fine. Now i wanted to have one more idoc created for another extension having the same basic type and linked to the same message type. Have maintained the same in WE20 but when i executed BD10 i could only see one idoc been generated but i need to see two idoc (one for basic type and another for the extended) not sure where i'm missing. any pointers on it pls?

Hi ,
if you want to trigger the idoc two times for basic type& Extension..
1 ) you need to maintain WE20 Partner Profiles (This is good already you did)
--> But the Output type for Bsic type & extension type is same so output type is triggered Once so idoc is created One.
2) try to create another Output type in T-code NACE for extension then two Idocs is created one for Basic and another for Extension.
Regards,
Prabhudas

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

IDOC - same message type

hello,
I have two idoc types named MATMAS04, MATMAS05.
(to MATMAS05 i have created an extension)
they are both in the same message type MATMAS.
i need to send the two idocs to the same system.
but, in transaction WE20 when i link the message type to the system i can create only one record of the message type. in all the administration tables for IDOCs i can see that i can send to idoc types under the same essage type but WE20 prevents it.
I don't want to create a new message type.
is there a way that i can use the same message type for different idoc types?
Regards,
Roi Grosfeld

Hi Roy,
This link might help u in idoc programming
http://help.sap.com/saphelp_erp2005/helpdata/en/78/21758d51ce11d189570000e829fbbd/frameset.htm
Hope this helps,
Regards,
Nagarajan.

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

Can two people share the same Apple ID on two different iPhones and maintain different passwords? Yes, there is more to the story.

I have an iMac, and iPhone. I've had my Apple ID for a few years.
My wife got an iPhone 4S a few months back and the salesperson at Verizon set her Apple ID the same as mine, but gave her a different password. I don't know if this was ok, but that is what happened.
So, yesterday, we both upgraded to IOS6 and I had no problem logging in to my iPhone with my Apple ID. When my wife went to log in, she was told that she was entering the wrong password. We entered the password over and over again and still was wrong.
The question is... can two people share the same Apple ID on two different iPhones and maintain different passwords? (I have the feeling her iPhone is thinking that since it's my Apple ID, it wants my password.)
If not, can I still set up a new Apple ID for her even through she's had the iPhone for a few months?
Thanks.

Hi
You shold follow your feelings, its probably right most of the time.
You can have 5 different devices hucked upp to one Apple ID. What I have done is that my wife and I have one Apple ID, when I bye a new app on my phone, She gets it to. Thats nice.
You can allways set upp a new Apple ID for your wife.

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

Same message type and two different IDOCS need to be triggered

Similar Messages

Maybe you are looking for