Reduced message type - Idoc without conversion rules

Hi Friends,
Am facing a strange situation while converting the Material Master data from 4.7b to ECC using BD21 transaction with reduced custom message type. I have reduced the standard msg type MATMAS05 using BD53 for the required field mapping both systems and I written the code using the exit EXIT_SAPLMV01_002 based on client req.
The situation is that sometimes IDocs are failing and the error shows that some fields which I have not selected in E1MARAM segment of the reduced msg type are populated with some values(ex: zeroes-0, slash-/,spaces)
Note: Conversion rules are not needed for this scenario.
Please help me out how to get rid of this '/ ' or spaces which appear for unselected fields in outbound Idoc using reduced message type ?
Thanks
Saravanan

Hi,
Please check the documentation in WE60 tcode and see if the fields are required to be passed...
Regards,
Nagaraj

Similar Messages

Issue with the change pointer for the reduced message type ZMATMAS

Hi All,
I have created reduced message type ZMATMAS for the MATMAS to create a Idoc when change or insert material master data fields( MARA-LAENG, MARA-BREIT, MARA-HOEHE) . My Problem is that the Idoc is generated with the status (03) but the fields(LAENG, BREIT,HOEHE) are not getting fill with the values. They are always filling with the values '/'). I have done the following steps to create idoc for the change pointer. Please check whether i have missed some steps.
1.     Create reduction maintenance ZMATMAS (Tcode BD53)
keep the default selected segments E1MARAM, E1MAKTM
2.     Add following data to maintain table view for the message type ZMATMAS (Tcode BD52)
Object      Table Name     Field Name
MATERIAL       MARA      KEY
MATERIAL     MARA     LAENG
MATERIAL     MARA     BREIT
MATERIAL     MARA     HOEHE
3.     Activate particular change pointer in BD50
Message Type       Active
ZMATMAS         yes
4.     Activate change pointers u2013 Generally (Tcode BD61).
5.     Assign Segment fields to change document fields (Tcode BD66 )
Segment Type     Field Name     Object     Table Name     Field Name
E1MARAM     BREIT     MATERIAL     MARA     BREIT
E1MARAM     HOEHE     MATERIAL     MARA     HOEHE
E1MARAM     LAENG     MATERIAL     MARA     LAENG
6. I have done the distribution model settings (BD64) and the idoc configurations
1.     Logical System
2.     RFC destination
3.     Create port
4.     Create partner profile
7. I changed the fields in material master data(Tcode MM02) and I executed the Tcode BD21.
Idoc is generated but the fields are not getting fill with the values
(Note: some fields are filled with values e. g material number, material description)
I checked the Idoc data segment E1MARAM (WE02)
Fld name   Fld cont.
LAENG       /
BREIT       /
HOEHE      /
Can you please let me know the issue
Prad

Issue is solved when I select the segments and the fields in the segments (Tcode :BD53)
Prad

What's the difference between segment filtering and reduced message type

Hi gurus,
What's the difference between segment filtering and reduced message type? It seems they have the same functionality: Reduce the segment while idoc is generated.
Thanks in advance.

Hi,
BD53 is for IDoc Reduction.
this allows you to create a reduced message based upon a standard message type.If you want see mandatory fields. go to T-coe BD53 and give one standard messege type name and eg: matmas
there mandatory fields will be in Green color..
And BD56- This transaction is used to filter out segments of IDocs for combination of sender and receiver. This is usefull in scenarios where a standard IDoc with many segments is used but the receiving partner is only interested in some of the segments
the table related to this transation is TBD20
please go through below blog you have an idea abt that,
http://wiki.sdn.sap.com/wiki/display/ABAP/ReducedMessageTypes
http://saptotal.com/IDoc%20Segment%20Filtering.html
regards,
ganesh.

Need to ALE only 2 fields through a reduced message type copied from MATMAS

Hi,
Only the Authorization group fields MARA-BEGRU and MARC-QMATA need to be transferred through ALE from one system to another one. A new reduced message type has been created from MATMAS.
The fields BEGRU and QMATA have been selected through the BD53 transaction to be part of the segments.
Result: 3 segments are part of the new Message type: E1MARAM and its 2 children E1MAKTM and E1MARCM.
Problem: Even the BD53 (Reduced message type) transaction has been used, too many unnecessary fields are transferred through the ALE.
The following fields in the E1MARAM segment must not been updated (transferred) in the receiving system:
 - PSTAT,
 - LVORM
 - MTART
 - MBRSH,
 - MATKL,
 - MEINS,
 - GROES,
 - WRKST,
 - SPART,
 - VPSTA.
They should disappear from the segment.
The E1MAKTM segment must not been transferred to the receiving system because the user does not want to modifiy the Material description. But the BD53 (reduce message type) seems to consider that segment as mandatory.
Only few 1EMARCM segments with specific Plants (WERKS) should be sent on the receiving system. Not all the Plants. That segment should not include the PSTAT field. I have no control on which Plants to transfer.
Revision:
Only 2 segments must be ALE'd with only the following fields:
 1- E1MARAM:
 a) MATNR (Material number)
 b) BEGRU (Authorization group)
 2- E1MARCM:
 a) WERKS (Plant)
 b) QMATA (Material Authorization Group for Activities in QM).
What should I do to ALE only those 2 segments and only those specific fields?
Thanks a lot.
Diane.

Thanks Ferry for the previous answer,
I have a problem with the E1MARCM segment.
My sending and receiving systems do not have always the same Plant numbers.
If a Plant exists on the sending system and it does not on the receiving system, the Plant must not be created on the receiving system. But from the sending system, I do not know which Plants the receiving system has. This is why the IDoc contains all the Plants. But I added some logic in the inbound customer-function, EXIT_SAPLMV02_002, to ignore the Plants that do not exist on the receiving system in doing a SELECT on the MARC table in the receiving system.
But that customer-function is called from the IDOC_INPUT_MATMAS01 function module, in the " WHEN E1MARCM " section:
 PERFORM CHECK_USER_EXIT TABLES T_EDIDD
 USER_SEGMENTS
 USING CURRENT TABIX.
 LOOP AT USER_SEGMENTS.
 CALL CUSTOMER-FUNCTION '002'
 EXPORTING
 MESSAGE_TYPE = IDOC_CONTRL-MESTYP
 F_CUST_SEGMENT = USER_SEGMENTS
 ENDLOOP.
In the perform check_user_exit, no record is created in the user_segments table because all the segments in my IDoc start with ' E1 ' :
 LOOP AT IDOC_DATA INTO USER_SEGMENTS FROM CURRENT_TABIX.
 IF USER_SEGMENTS-SEGNAM(2) = ' E1 '.
 EXIT.
 ENDIF.
 APPEND USER_SEGMENTS.
 ENDLOOP.
The customer-function is called within the ' loop at user_segments '. This is why the customer-function is never executed and my code is ignored. So, all the IDocs in the receiving system are in the status 51 (red light).
Do you have any idea how to resolve my problem.
Thanks.
Diane.

Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 ,214

Hi friends,
Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 (Response to a Load Tender)., 214 (Shipment Status )
For shipement status i got trxstc01 for idoc type .. but its only before 4.6 version ..for 4.7 its not there .. please give the alternate for that ...
Thanks in Advance ....
If any one is provide exact answer i will give Max marks ..
Edited by: ajay KOLLA on Aug 6, 2009 8:04 AM

Hi,
Have you resolved this issue. If yes, can you please let me know. Im actually looking for same for EDI 867 (guess it is for summary report and need to know message type, Idoc type associated with this).
Rgds
Sudhanshu

Message type ,IDOC TYPE , PROCESS CODE for Edi 990

Hi ,
Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 (Response to a Load Tender).
Thanks in Advance.
Ajay Kolla

Hi
Pls check the below links
1. http://www.erpgenie.com/sap/sapedi/ansi.htm
2. http://www.erpgenie.com/sap-technical/ale-edi-b2b/master-data-message-types-idoc-types
Hope this may helps you.
Regards
Sirigiri

Any Idea Which Message type/Idoc Type should be used for FI Invoice

Hi Experts,
Any idea what message type/Idoc type should be used for FI invoice. We are going to send IDOC from R/3 to Non-SAP System using ALE. We are using T-codes FV60/FV65.
Thanks,
Sony

Hi Sony,
I never dealt with FI IDoc.
I think you need to setup EDI outgoing payment in IMG. Please take look this report RFFOALE1 - ALE Distribution of Payment Data and RFFOEDI1 and check also the program documentation.
Hope this will help.
Regards,
Ferry Lianto

What is Message Type & IDOC Type?

He Experts!,
What is Message Type & IDOC Type? What is the difference between them?
Thanks in advance.
Sekhar

Hi,
Please try these transaction codes.
WE82 - Message Type and IDoc Type
WE64 - Process Codes (Inbound and Outbound) for Message Type.
Message type. A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterizes the data sent across systems and relates to the structure of the data called an IDOC type (see below). For example, MATMAS is a message type for Material Master, and INVOIC is a message type for an Invoice (Billing Document). ALE supports over 200 message types in R/3 and about 200 application areas.
IDOC type and IDOC. An Intermediate Document (IDOC) type represents the structure of the data associated with a message type (DEBMAS02 for message type DEBMAS Customer Master, and WMMBID02 for message type WMMBXY Goods Movements), while an IDOC is an object containing the data of a particular message type. IDOCs are data containers with intelligence built in. Each IDOC contains one and only one business object. For example, an IDOC of type SHPMNT01, message type SHPMNT, will contain data only of one Shipment Document. Generally, the architecture of an IDOC is independent of the message type by virtue of ALEs ability to redefine it for any message type.
Use transaction BD64 or the following menu path to maintain the model: From the IMG (Implementation Guide), Cross-Application Components -> Distribution (ALE) (*) -> Distribution Customer Model -> Maintain Distribution Customer Model Directly -> Maintain Distribution Customer Model Directly.
Thanks,
Sankar M

How can I add an extention to a reduced message type?

We want to create change pointens for a subset of the HRMD messagetype.
So we created a reduced message type (based on HRMD_A07) and activated only those segment we need.
This works fine.
Now we need to add information of IT2006, this is not available in the HRMD. Therefore we made a Z segment and an extention to HRMD_A7. We added the extention to the partnerport and to the infotype (T777D).
The new segment is not send with PFAL, what do we need to do to make this work?

You need to make sure the new Z segments are populated with the data. You can check that by putting a break point in function module MASTER_IDOC_DISTRIBUTE and check the EDIDD parameter MASTER_IDOC_DATA. Check whether your Z segment is populated there. And check in parameter COMMUNICATION_IDOC, whether your extension is there. If your Z segment is not populated, you may have to check how that can be populated.
Regards,
Gokul

IDOC inbound conversion Rules

Hi to all,
I'm Implementing an Inbound Interface for Cost Centers using idoc message COSMAS and IDOC type COSMAS01.
I want to modify IDOC data changing the cost center code by another one stored locally in a param table (Z*).
I think the best way to do this is by creating a conversion rule in BD72 than maintain and assign to Message type. The problem is that i have to select data from the Z* Table i need two parameters from the IDOC(LogicalSystem and cost center). How can I create a custom conversion routine or something to get this data from the Z table into the IDOC field (KOSTL).
The conversion exits only have one import parameter and one export parameter.
Do anyone had one problem like this?
Thanks in advance to all.

Hi,
Please check the documentation in WE60 tcode and see if the fields are required to be passed...
Regards,
Nagaraj

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 are some of the message types (IDocs) related to HR in SAP?

Hello all,
Please tell me where can I get more details?
Thanks,
Charles.

Hi Charles,
Here is some material which i read some time ago, i think this will be helpul to you for IDOC, this may not give whole idea but atleast some basic ,
You need to get in touch with ABAP person for IDOC,
To create an Outbound interface from SAP HR to Other System.
*You have to know the process completely. I will give you the explanation here....*
*First of all you have to findout the Messgae type and IDOC type for the data.*
*Message Types:*
*Suppose if u want to transfer*
*Master and Organizational data----> HRMD_A*
*Personnel Actions -> HRSM_A*
*Time data---HRSM_C/HRSM_D*
*IDOC Types:*
*These stuff you can findout in WE30 Transaction code.*
*For HRMD_A----> HRMD_A01*
*HRSM_A----> HRSM_A01*
*If u go inside by selecting the IDOC type u can view all the segments.*
*For individual Segments you can go to the Transaction code WE31*
*Note: Suppose if the standard segments or IDOC type doesn't support your req..u can create the custom stuff in the same transaction code itself.*
*After completion of this,with the help of BASIS team you have to configure the ALE settings between the HR and Siebel system. And also make sure all the Outbound and Inbound parameters are defined correctly.*
*Then try to send the Master data using the Transaction code PFAL.*
*In this TCODE you can send the data based on Object type,Object ID,Infotype/Subtype etc...*
*If you are missing anydata from here try to customize the Inbound function module by the help of HR ABAPer.*
*(Normally we will go for standard FModule IDOC_INPUT_HRMD_A01....).* Bye let me know if you find this helpful
Regards
Pallavi

Message types(IDOC) in XI

Hi,
I am trying to maintain distribution model in XI, i could not found message types CREMAS, MATMAS and DEBMAS. can anyone help.
Actually i am sending IDOC's from R/3 to XI, i create RFC OUTBOUND in R/3 and maintained distribution model view.
Thanks in Advance
srinivas

hi,
>>>>I am trying to maintain distribution model in XI,
you do not do that in XI as it doesn't make any sense to use it there - XI does not store any master/transactional data
Regards,
michal

Message type idoc type problems

Hi,
I'm facing a problem in idocs. I'm sending idocs with message type ORDRSP and idoc type ORDERS05, but for some reason in SAP, the idoc is always picking up a different message type ORDERS and the partner profile part is failing because my partner profile is set up for ORDRSP message type. Is there any setting or transaction that sets a default message type for an idoc type in SAP.
Regards,
Vijay

Hi vihay,
yes for the message type ordrsp the basic type is orders05.
u r telling ur geeting problem in inbound idoc?
if that is the case then u have to use in we20 inbound parameters and give the processcode(ORDE) there instead of basictype .CHECK the same and get back to me if any quries
Regards,
Nagaraj

RC1_IDOC_SET_STATUS Program - Message Type & Idoc Number

Hi All,
Good Morning.
We use the SAP Standard Program RC1_IDOC_SET_STATUS to convert the status of Idocs. Recently, we had encountered a behavior which we havent come across before.
The selection screen has the IDOC number, the message type, the current status and the new status. There is an additional trial run checkbox as well.
(1) If the IDOC number alone is given then the status of that idoc alone will be changed. (And that works successfully)
(2) If the message type alone is given then the status of the Idocs for that message type are converted (And that works successfully)
(3) If the message type and the Idoc number is given, then the program converts the status of the all the idocs associated with the message type irrespective of the specification of IDOC numbers in the selection screen. (Now, this is where we faced the problem, the system converted all the Idocs with the mentioned message type ignoring the list of Idocs to be changed).
This resulted in change of the status of all Idocs of a particular message type.
Is there a way, we could track the Idocs which got changed and reverse them back to the old status? Is there an SAP note which addresses this issue?
Your Inputs on this would be highly appreciated.
Spandana

Hi,
With this report , specifying range won't work because the program loops at the select option and only takes the LOW variable of each record. So it is necessary that you pass all the idoc numbers for which you want to change the status for.
The solution is to give exact idoc numbers in the single values or copy this program to a 'Z' program and tweak it as per your requirement.
Br,
Advait

Reduced message type - Idoc without conversion rules

Similar Messages

Maybe you are looking for