Idocs multiple message types

Hi all,
I created one custom idoc type with six segments. I heard that one idoc type can have any number of message types
if it is so pls tell me how to assign these two message types for my idoc .
i want to create multiple message types because i want to send same idoc type to diff legacy systems.
My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?
Edited by: kunal kakkar on May 16, 2011 10:21 AM
Moderator message: duplicate post locked.
Edited by: Thomas Zloch on May 16, 2011 12:39 PM

COND_A01 is the IDoc to distribute the condition master data. Sales order (ORDERS05) is transactional data. It is not feasible to generate a master data IDoc from a sales document. Even if it was feasible, what would be the purpose? The master data hasn't changed, why would anyone want to send it again with every order?

Similar Messages

Multiple message types for an idoc type

Hi all,
I created one custom idoc type with six segments. I heard that one idoc type can have any number of message types
if it is so pls tell me how to assign these two message types for my idoc .
i want to create multiple message types because i want to send same idoc type to diff legacy systems.
My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?

Hi Kunal,
Below are my thoughts from a design perspective,
My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
Before you look upon the no. of message types you need, i guess you need to look at the business requirement. Per your requirement you want to send send two sub sets of data. The first subset in the first 3 segments and other three segments for the second subset of data.
Is the structure of the first subset of data similar to the second subset If not, better to create two IDOC Types. If they are similar, then create one IDOC Type with three segments and have two message types for each subset of data.
For Ex: ORDERS05 is the IDOC type for Orders, this IDOC type provides capability to carry data related to any type of orders
but the action on the data is facilitated by the message type like ORDERS for create, ORDCHG for change, ORDRSP for Order response etc.
OR
Are these two subsets of data related to each other, if yes understand the relation? If not related at all then you might be better of creating two separate IDOC Types.
Like in the above example A purchase order is related to a sales order so you can use the same IDOC type, but in case of a order response and ASN that data sent is different and hence you will need different IDOC types (even though a SO is related to a DN).
how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?
The above again depends on the how tightly/loosely coupled are the data sets, you can have just one program and have a simple case statement on the message types or have two different programs.
You will also have to consider points like, if any of the subsets is more prone to more change in terms of the structure and associated business logic. If yes, then you might want to keep the programs separate to reduce work on regression testing etc.
I am sure you will receive more inputs from the experts on the forum and the list of points to look for will get longer , so understand the requirement, dependencies and if you have any specific questions you could post it on the forum.
Regards,
Chen

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.

Error while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

Creation of IDOC with message type INVOIC01

Hi All,
I am trying to create a new IDOC with message type INVOIC01.
When I see transaction WE81, I observe that the required message type INVOIC is available. Also in WE82 the basic types INVOIC01, INVOIC02 and INV_ID01 are attached to the message type INVOIC.
However, while trying to create an IDOC in WE19 using a message type, I get options to create against INVOIC02 or INV_ID01. The basic type INVOIC01 is not getting populated because of which all the IDOC that I create are of basic type INVOIC02.
The client wants me to create IDOCs with basic type INVOIC01.
Can anyone please help?
Thanks in advance.
regards
Nagarajan

Hi Nagaraj!
I've looked at the documentation and did not find information, which would help me. Should I use in my case z-segment to put extra lines or there is some qualifier in segment E1EDP02 (Document Item Reference Data), which triggers to another referencing (not PO or delivery note)?
Thank You,
Natalija

Diff bet IDOC and Message Types.

What are the difference between IDOC and Message types.
Diff between MATMAS01 ,MATMAS02 and MATMAS03

IDOCs:
- IDOC is an Intermediate Document. It is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data.
An IDOC is created as a result of executing an Outbound ALE or EDI process.
In an inbound ALE or EDI process, an IDOC serves as input to create an application document. When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.IDOC will wait until the Remote System is Active.
Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
basic IDOC type or a customer developed basic IDOC type.
- A basic IDOC type has the following characteristics:
Name : A basic Idoc type can be assigned upto a thirty character name.
List of permitted segments: The segments make up the IDOC structure.
Hierarchy of segments : The hierarchy of segments specifies the physical sequence and any parent - child relationship in the segments.
Mandatory Vs Optional Segments : When used in the IDOC type, each segment has an attribute that defines whether the segment is option or mandatory. Minimum/Maximum range for each segment: It defines the maximum and minimum number of timesa data record corresponding to a segment cn exist in an IDOC.
-Segments : A segment defines the format and structure of a data record. Segments are reusable componets. A segment consists of various fields that represent data in data record.
IDOC Record Types:
1. Control Record : The control record contains all of the control information about an IDOC, this information basically includes the IDOC number, sender and receiver information, and information such as the message type it represents and the IDOC type.
- there is only one control record per IDOC.
- The stucture of the control record is the same for all the IDOCs and is defined by SAP.
- The structure of the control record is defined by the data dictionary structure EDI_DC40. The control record is stored in the EDIDC table.
2. Data Record : Data records contain the application data. A data record has two sections
Administrative Section and a Data section.
- The Administrative section cotain the segment name, client, IDOC number, segment number, hierarchy level information.
- The Data section of a data record is a stram of 1000 bytes where the actual data resides.
- The data record is defined by the data dictionary structure EDI_DD40.
- Data records for IDOCs stored in the EDID4 table.
3. Status Record : Status records are attaced to an IDOC throughout the process as the IDOC achieves different milestones or encounters an error. At every milestone a statu code, date and time are assigned.
- Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for inbound processes.
IDOC TYPE IS AN INSTANCE OF IDOC
Message Type: Identifies what type of information transformed between logical systems or partners.Message type is not a local object type , it is transportable.
For different applicatons we have different MESSAGETYPE.
example:
APPLICATION MESSAGETYPE
MATERIAL MASTER MATMAS
VENDOR MASTER CREMAS
CUSTOMER MASTER DEBMAS
MATMAS01, MATMAS02, MATMAS03, MATMAS04, MATMAS05 are all MESSAGETYPES ... FOR NEW VERSIONS LIKE SAP 4.7EE, SAP ECC5.0....we have to use MATMAS05 message type. for older versions like SAP R/3 we have to use MATMAS01.
REWARD ME IF THIS IS HELPFUL

RFC error "No authorization to send IDOCs with message type ..."

Hi all,
I have now tried just about everything I could think of, applied all the notes mentioned on this forum but still no luck. Can anyone please help ...
I have got a file to idoc scenario, the status in the sxmb_moni is successful, but the outbound processing logs an error. When I go to transaction SM58 I get an error for the user XIAFUSER with the message "No authorization to send IDOCs with message type WPUUMS".
I have tried giving this user SA_ALL access and still got the same error thus concluding that this is not an authorisation error.
Any suggestions?
Regards,
Liesel

Hi Liesel,
The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
Please check if the user id/Password that you have given has all the authorization.
Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
Regards,
Abhy Thomas

Batches not getting updated by incoming idoc DELVRY03 (message type SHPCON)

Hi
    I am using incoming idoc DELVRY03 (message type SHPCON) to update delivery document.I am using field E1EDL24-CHARG to pass batch data.
      However batch number is not getting updated in delivery document. I have verified aspects like batch number is valid etc.
     While updating batch number thru incoming idoc, do I need to supply some other data?
Please help.
TIA
Koustav

Hi Biswas,
I think batches are determined automatically in the deliveries while creation and thats the reason it is not getting the batch number in the delivery, if there is no automatic batch dertermination then it will update the valid batch number
also please check the batch determination procedure and the batch master in MSC2N and availability of materials for that particular batch
regards,
Santsoh

Error : No authorization to send IDocs with message type MATMAS

Hi All,
My scenario is FILE-XI-IDOC.
I am getting chequered flag in SXMB_MONI,but in that under outbound status I am getting red flag.
When I check in SM58 I am getting message as "No authorization to send IDocs with message type MATMAS".
Do I need to give any authorizations on XI side or on R/3 side?
If so, what is the authorization required?
I could not find the note :837595.

You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
Solution
In transaction PFCG, extend the role of the logon user by adding the following authorizations:
Authorization object S_RFC
 Field name RFC_TYPE value FUGR
 Field name RFC_NAME value EDIMEXT, SDTX
 Field name ACTVT value 16
Authorization object S_IDOCDEFT
 Field name ACTVT value 03
 Field name EDI_CIM value ' '
 Field name EDI_DOC value TXTRAW01
 Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
 Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
 Field name ACTVT value 03
 Field name DICBERCLS value
from the note mentioned above.
Regards
Bhavesh

Workflow Ends in Error " No auth to send IDocs with message type ORDRSP"

Hello All,
I have created an RFC user with limited Authoprizations including WE* tciodes and a few ME* transactons for an ALE Set up. I want to make sure i would not be giving more authorizations (extensive) to this RFC user and assign Just required authorizations. So i started testing testing and the inbound IDOC ended in error with a message " No auth to send IDocs with message type ORDRSP" Message no. SR053. Is there any way to find out what is the missing authorization object for the User. Any inputs would be really apprecaited.
Br,
Sri

Hi !
Becaus alle this happens in beckgound, things are a bit difficult but solvable....
What you should do is a "Authority trace" ... as follows....:
- Go to the ST01
- Mark "Authorisation Check"
- Swich the trace on for your Workflow user
- Execute the Workflow until the error uccurs
- Go back to the ST01
- Press the "Analyze" button and see what error occurs
Dont forget to swicht the trace off... otherwise the tracefiles become realle BIG !
Regards
rainer
Some Reward poins would be nice if that helped....

IDOC of message type EUPEXR

hi all,
When I run RFFOEDI to gereate IDOCS, IDOCS of message type EUPEXR and PAYEXT are generated.
I need to pass a value in a field in the control record for the IDOC of message type EUPEXR but in FM : FI_EDI_EUPEXR_IDCREF01_OUT ( which is uesd to generate this IDOC ), control record is filled and before passing this control record to MASTER_IDOC_DISTRIBUTE, I could not find any exit to change its control record.
Please help.
Thanks and Regards
Gurpreet Singh

Hi Ferry,
System checks for the IDOC version and then calls the EXIT if the versions are different .Following is the code snippet that ensures the above thing in include LBD11F0T :
Change IDOC version if target <> current version.
IF F_EXCEPTION-MSGTY IS INITIAL
 AND ( F_IDOC_CONTROL-IDOCTP <> TARGET_IDOCTP
 OR F_IDOC_CONTROL-CIMTYP <> TARGET_CIMTYP ).
 PERFORM CHANGE_IDOC_VERSION TABLES T_IDOC_DATA
 USING TARGET_IDOCTP
 TARGET_CIMTYP
 CHANGING F_IDOC_CONTROL
 CHANGED_FLAG
 F_EXCEPTION.
ENDIF. "End of if subrc = 0
Have you tested it ? Pls suggest if I am wrong somewhere.
Thanks and Regards
Gurpreet Singh

How do I execute IDOC for message type LOIPRO

How is it possible to execute IDOC using message type LOIPRO which I have configured with change pointers? Change pointers are using object ORDER.
I am looking to only generate IDOC for production order changes / updates that meets the criteria set by the change pointers. If something in the order changes, but that field is not being looked at by change pointers, I don't need IDOC to pick up that order.
I don't want to have to run RCCLTRAN or RCCLORD on a scheduled job. Only need to have activity if change pointers are activated. Am I going down the wrong road using LOIPRO ?

Hi Bob,
Could you please guide me through the process of creating/triggering a change pointer based LOIPRO? Your help much appreciated.
Tabraiz

IDOC of message type COMCMT

Hi,
Does anybody know how to generate a IDOC of message type CODCMT do you have some doc about it?
Thanks alot
Regards,
Zheng
Edited by: zhengliu on Jun 16, 2009 12:09 PM
Edited by: zhengliu on Jun 16, 2009 12:10 PM

Thank you.
In fact, I have already read that doc, but after the definition of these datas, what i must do?
For example, are there some data are obligatory?
Is this IDOC an IDOC outgoing?
Regards,
Zheng
Edited by: zhengliu on Jun 16, 2009 1:21 PM

Problem In IDOCS of Message Type ORDERS05

I am Trying to place Sales Order as soon as i recieve an idoc of Message Type ORDERS05. But It gives following error when it recieves the idoc of a Purchase Order.
VKORG, VTWEG, SPART cannot be determined for customer 0000003000, vend 0000005595.
I am not Getting This Problem.
Please Help.

Hi,
Please see the link below for some information.
ABAP Development
If you find the info useful please reward with points.
regards
Aveek

Function Module to transfer IDOC of message type ADRMAS!!!!!!!!!!!

Hi
process code is assigned to partner profile which is the best suited Function Module to transfer IDOC of message type ADRMAS

Hi,
     You can find the FMs, specfic to Msg types in Table TBDME.
    Regards
      Kiran

Idocs multiple message types

Similar Messages

Maybe you are looking for