ALE: reduced IDOC type

I have 4 systems, i.e.: PLM and R3-1, R3-2, R3-3
I want to send a reduced IDOC for material master (MATMAS) from the R3 instances to PLM
I created a reduced IDOC type for MATMAS and created a transport request of ALE tables of reduced message type in PLM.
However, I am unable to import the transport request from PLM to the R3 instance, because PLM is unicode and R3 is non-unicode.
As a workaround until I resolve the unicode issue, I re-create the reduced IDOC in the R3 instance and I am able to send the material master data correctly.
Is there a simpler workaround than re-creating the reduced idoc in each R3 instance?
Also, when I send material master data from R3 using BD10, it does not send associated material class even though, I specify 'send material in full'. Where does that association take place?
Any thoughts?

The table is maintained with BD69 - Assignment of message type to IDOC type.
In my case I added one line with values:
Message type: {my reduced message type}
Basic type: HRMD_A06
Extension: {my HRMD_A06 extension}
Also it looks like there is another (better?) way of making the assignment. It is done with WE82, described in sap help here http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b7db043d711d1893e0000e8323c4f/frameset.htm and also discussed in this topic.
SAP ERP Human Capital Management (SAP ERP HCM)

Similar Messages

ALE: setting up reduced IDoc type for use in 4.7 and ERP 2005 problem

I need to set up a reduced HRMD_A message type and then use it to send HR data from a 4.7 system to an ERP 2005 system.
To define the reduced type in both systems I use transaction BD53 (Idoc reduction maintenance).
The problem is that the transaction offers HRMD_A06 as the basic type on a 4.7 system and HRMD_A07 on ERP 2005. Thus i cannot set up identical definitions.
I suppose I should 'step back' to A06 at the ERP 2005 system somehow, but where to look for?..
Thank you in advance!

The table is maintained with BD69 - Assignment of message type to IDOC type.
In my case I added one line with values:
Message type: {my reduced message type}
Basic type: HRMD_A06
Extension: {my HRMD_A06 extension}
Also it looks like there is another (better?) way of making the assignment. It is done with WE82, described in sap help here http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b7db043d711d1893e0000e8323c4f/frameset.htm and also discussed in this topic.
SAP ERP Human Capital Management (SAP ERP HCM)

How to reduce idoc type HRMD_A?

Dear All,
We need to reduce the HRMD_A idoc. We have taken the following steps:
1- created message type ZHRMD_A using transaction BD53 (Idoc reduction maintenance) wit reference to HRMD_A message type
2- Activated the segments and fields of the required segments
3- Activated change pointers using the Active Change Pointers push button on the initial screen of BD53
We can see that our ZHRMD_A message type is active in table TBDA2 (using transaction BD50. Message type HRMD_A is still active in the same table.
When we run transaction BD21 (to evaluate change pointers) with message type ZHRMD_A, we do not get any idocs created. However BD21 will generate idocs when run with HRMD_A message type.
Are we missing a step in our configuration?
We are on ERP 2005 (WAS 7:00) SPS 6
Thx/Farshad

Fatin,
Have you activated Change Pointers - Generally? If no then in Customizing for Distribution (ALE), choose Modeling and Implementing Business Processes -> Master Data Distribution -> Replication of Modified Data -> Activate Change Pointers - Generally. Set the change pointer status to Active, and save this setting.
Choose Modeling and Implementing Business Processes ® Master Data Distribution -> Replication of Modified Data -> Activate Change Pointers for Message Types. Set the change pointer status to Active for the appropriate message type (which is ZHRMD_A in this example), and save this setting.
Also do not forget to maintained Distribution model ( TC : BD64) & partner profile(WE20) for message type ZHRMD_A.
Cheers,
Nilesh

When do we ceate custom messagae type apart for custom idocs type

Hi all.
Can u pls let me know when do we create custom message type in ALE/IDOCS. what I know is we can create a custom message when we create custom idoc type & when we have reduced idoc type.Pls let me what are other cases in which I need to create a custom message type.Thanks in advance.
Kind regards,
sami.

I think these are the only cases where we need to create. Its basically when we dont have standard SAP message type available.

Sending reduced IDOC from XI to R/3 with nodata markers

Hi !
I need to update a VERY FEW Vendor fields data in R/3 from XI (FILE-XI-IDOC). I'm using the standard IDOC type CREMAS04 (I need to update fields of the E1LFBWM segment...withholding tax fields).
The problem is, that if I disable the not needed IDOC fields in the XI message mapping, when the IDOC reaches R/3, it blanks all the fields that were empty as result of the mapping...I verified it using XI and using the IDOC test tool (we19). For example, if the vendor had data in fields such as "salutation", "phone number", etc. after the IDOC processing, those fields change to BLANK.
One solution is to send the NODATA marker ("/") in those not needed fields, and that works!!!!...BUT, there are hundreds of IDOC fields.
I made a reduced IDOC type, based on CREMAS, enabling only the segments and fields needed, but tnx-WE19 and XI keep sending blank data in the not needed fields instead of the NODATA marker.
How could I send by default, the NODATA marker ("/") to all the fields NOT mapped or disabled, without having to map each field manually ?!?!?
Should XI send those fields as "/", or the R/3 should detect that the incoming IDOC is a reduced IDOC type, and complete all the not existing fields with NODATA ??
The goal is to update some data, and not overwrite with blanks, those fields that should remain untouched.
Thanks !!
Matias.

Matias
Is ur intention /equirement to send the NODATA for the rest of the IDOC elements or just send the reduced IDOC for the required sender elements..
if it is only for sender file elements, as sravya said Note 709400 describes
The integration repository provides a new function: "export reduced XSD" to reduce the XML schema of an IDoc.
To use this function in the mapping tool, proceed as follows:
1) Open the relevant IDoc in the object editor of the XI Repository.
2) In the menu "Tools", select the menu option "Export reduced XSD".
3) Assign a file name in the subsequent dialog box and save the data on the hard disk of your local PC.
4) Use this exported file in the message mapping instead of the IDoc by using the function "Import XML or XSD" in the mapping tool to select the source or target message. So you must use this function to import the reduced XML schema stored under
3) of the IDoc in question, and use this XML schema instead of the complete IDoc.
Note: The XML schema generated using the function "export reduced XSD" does not contain the full information in the repository on the IDoc and should only be used for the mapping.
option2: if you want to send the NO DATA, you got to develop UDF in Java or XSLT..
Here is a sample Java code:
obj = inputModuleData.getPrincipalData();
msg = (Message)obj;
XMLPayload xmlpayload = msg.getDocument();
DocumentBuilderFactory factory;
factory =DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
// parse the XML Payload
Document document = builder.parse((InputStream)
xmlpayload.getInputStream());
var x=document.getElementsByTagName("<rootnode>");
for(i=0;i<x.length;i++)
//the attlist variable will hold a NamedNodeMap
var attlist=x.item(i).attributes;
if (attllist.getvalue.equals("") { //pseudo
attlist.setvalue("/"); //pseudo
document.write(att.value + " ");
Good luck
Thanks-Gopal
Message was edited by:
gopal srinivasan

Entending a IDOC type

Hi,Experts!
I try to entend IDOC type "ZCRMXIF_ORDER_SAVE_M02" using WE30. However an Error occured: Action is not possible for generated idoctypes.
And I can't create extended IDOC.
Why this error occured? If you have information about extending IDOC,plese tell me how to create a extended IDOC.
Regards.

Hi,
These are the steps for idoc extension.
Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.

Reg. IDoc errors in Mat Mas conversion using ALE/IDocs & reduced msg type

Hi Friends,
Am facing a strange situation while converting the Material Master data from 4.6b to ECC using BD10 transaction with reduced custom message type. I have reduced the standard msg type MATMAS03 using BD53 for the required field mapping both in 4.6b and ECC systems and I written the code using the exit EXIT_SAPLMV01_002 based on client req.
The situation is that in receiving system(ECC) 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)
(Error Msg -Blank spaces in change number 0 / are not supported). And all these coversions are scheduled as Batch jobs and by ALE setup. But when I try to send these errored out material numbers using BD10 tcode(without Batch job), they are posted successfully and the IDoc does not show the additonal fields which I have not selected. I tried to debug the errored parts conversion, but they always post successfully.
FYI, the additonal fields which are populating does not exist in the message type MATMAS03 of the sending system(100 flds) but exists in receiving system ECC(118 flds).
Please help me out..if you have any clue.. and pls let me know if you need more info about this scenario.
Thanks

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

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.

Incorrect IDoc type ZSWA003 in the ALE defintion of the source system.

Hi !
When I triggering the load from BW it is giving me an error Incorrect IDoc type ZSWA003 in the ALE defintion of the source system.
When I am checking the connection in source system with R3 system , it is giving me this error and asked me to Enter IDoc type ZSWA011 .
Please tell me how to do this.

Hi,
I assume that the source system has been copied fom production onto quality-system (or somothin likely).
To solve that, plase refer to the oss-note 886102.
https://websmp130.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=886102
https://service.sap.com/sap/support/notes/886102
Hope that helps.
cheers
Sven
Edited by: Sven Muntermann on Mar 26, 2009 6:21 PM

Incorrect IDoc type ZSBB010 in the ALE defintion of the source system.

Hi,
We have done client copy of BW production system into BW test system.
I am getting following error while checking Test R/3 system in BW Administrator workbench.
Diagnosis
Incorrect IDoc type ZSBB010 in the ALE defintion of the source system.
System response
Error when sending data to BW.
Procedure
Enter IDoc type ZSBB017 .
Ring any bell.. Thank you for Ur time..
Cheers
Senthil

Hello Senthil,
Please check WE20 transaction and look for idoc type there.Most likely you need to make some corrections in there. Also check BD64.
Regards.
Ruchit.

Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR

Hi Experts,
Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR 373 error is coming .
Some one suggested note no 886102 but i went inside i did not find correction or code for implementing please any body suggeste for rectifying this error.
Please tell correct aproach for solving the issue.

Hi,
there is some problem with your RFC connection
just go to WE20 T code and expand partner type LS
here search your r/3 system and click on that here you can find the details of idoc
if you are not able to correct yourself you can contact basis team for that.
just go to RSA1--> using the conxt menu doa check of Source system you will get the error message
just send the screen shot of the same to Basis team they will take care of the same.
Br
santosh

Incorrect IDoc type ZSBC052 in the ALE definition of the source system

hi guyz,
i am getting the following error while checking the source system in bi.
Incorrect IDoc type ZSBC052 in the ALE definition of the source system RSAR 373
please guide through your expertise.
regards,
raps.

Hi,
Check the below given thread,
[Source System Check Problem;
[Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR;
Regards,
Durgesh.

Incorrect Idoc Type in ALE Definition of Source System

hi,
I have defined a R/3 Source System in BW client. This source system points to another R/3 Server in our system landscape. When I right click on the source system and click on the "check" option, getting the following error - "Incorrect Idoc type ZSKB013 in the ALE definition of the source system".
Where can I change this setting and will this be done on BW side or R/3?
regards,
SK

Hi,
there is some problem with your RFC connection
just go to WE20 T code and expand partner type LS
here search your r/3 system and click on that here you can find the details of idoc
if you are not able to correct yourself you can contact basis team for that.
just go to RSA1--> using the conxt menu doa check of Source system you will get the error message
just send the screen shot of the same to Basis team they will take care of the same.
Br
santosh

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

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

ALE: reduced IDOC type

Similar Messages

Maybe you are looking for