Reduced IDoc

Hello evryone,
I created reduced Idoc in BD53 of message type PORDCR. PORDCR05 idoc is assigned to it.
when i open the reduced message type in WE19, it is still showing all the segments.
After creating reduced idoc in BD53 and activating, is there any other steps left?
Why it is showing all the segments in WE19, not the only selected segments and selected fields?
Regards,
manish

Hi,
The mandatory segments cannot be reduced.The Fields present in the Idoc with reduced message type can be viewed in BD52. And please see the below links, it might be useful to you.
http://help.sap.com/saphelp_46c/helpdata/en/66/1c4b6e5733d1118b3f0060b03ca329/content.htm
https://wiki.sdn.sap.com/wiki/display/ABAP/ReducedMessageTypes
Regards,
P.Rajesh

Similar Messages

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

Reducing IDOC HRMD_A

I want to reduce IDOC HRMD_A.
I have
1) created a copy ZHRMD_A & marked the fileds that I want to send in the IDOC via tocde BD53
2) activated the change pointers for ZHRMD_A
3) updated the partner profile & distribution model.
But when the IDOC is created it still has all the fields without any reduction.
Any help would be greatly appreciated.
Thanks

Hi,
I have the same problem! Does anybody know how to solve it?
Regards,
André Avilla

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)

Need to reduce idoc for PO

Hi all,
we have a requirement to send PO details when new po is crated in SAP,
but we need to send only 13 fields from PO , so how to reduce the fields and how map the fields,
the below are the fields needs to send to legacy system.
EBELN
WERKS
LGORT
AEDAT
BSART
EBELP
MATNR
MENGE
MEINS
BANFN
EINDT
MENGE
REVNO
ERDAT
which idoc needs to use , there are 3 idocs are available in SAP( PORDCR04, IMPINV01, ORDERS05)
we are using ECC 6.0
Regards,
Suresh

HI,
there are a lot of ways.
IF you are using ORDERS05 (ORDERS).
Implement Exit "EXIT_SAPLEINM_002" and remove all unanted value in the Segments.
Note: Each Segment is used by that exit.
another way.
Wait if the ORDERS is complete.
Implement BADI "IDOC_DATA_MAPPER" and use Method "PROCESS" to get rid of all unwanted data.
Note: this badi is called after IDOC_OUTPUT_ORDERS.
Note: take care of using this Badi cause every created IDoc is running through that function ? You have to restrict for each IDoc Type and maybe Partner.
example.
Case CONTROL-IDOCTP or RCVPRN or ....
when 'ORDERS05' ...
endcase.
Regards,
Gordon

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

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)

Reducing IDOC size

Hi,
I would like to reduce the size of the IDOC. Can we restrict the maximum segments per IDOC. How can we modify IDOC basic type ( Eg: HRMD_A06)?

Check the documents below:
http://www.dataxstream.com/doclib/ALEOptimization.pdf
http://www.supinfo-projects.com/cn/2005/idocs_en/3/
http://help.sap.com/saphelp_45b/helpdata/en/1a/0e350a539911d1898b0000e8322d00/content.htm
Please give me reward points...

Reduce idoc with extension

I've created an extended idoc based on HRMD_A06 (the extension segment is for IT0220 which is not included in the standard HRMD_A06)
I also want to reduce the idoc so that it will only produce E1P0014 and my custom segment.
Is this possible and how ??
Much appreciated ..
John

You can probably do the segment filtering at the Distribution model itself, so that when the IDOC is being generated it will generate specific segments.
Here is the SAP help for the same.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
regards,
Ravi
Note : Please mark all the helpful answers

Need info regarding reducing Idocs

Hi,
Iam exteding ORDERS05 to ZORDERS05.
I need to remove segment E1EDS01 from this ZORDERS05.
i tried to reduce using BD53 tcode but it asks for reference message type and throws message saying not available in reduction pool.
pls sugest

ACLs, like Accounts, are optional security setting which may add on some extra functionality to mandatory security groups. Likewise, the resulting permission is taken as an intersection of SG and ACLs.
But in the second part the number of set of users is huge (approx say 600)I don't get this completely. Does this mean that those "sets of users" (users who see the same data) are distinct and that there is 600 of such groups?
If you read thoroughly the manual I sent earlier, there is a recommendation that there should be maximum 50 security groups, and you should use accounts, should this number be exceeded. This means you could have all the documents in one security group (and have one common role with Read permission), but combine it with accounts. ACLs are not a good choice here - their performance and manageability is much worse than of accounts. ACLs are primarily used if you expect security settings to change during the lifetime (e.g. a project manager adds temporarily rights to access an item to another user, and revokes it when the user finishes his or her work).
Note that accounts as well as permissions of users within accounts can also be mapped externally (from LDAP/AD) and it usually follows some kind of org chart.
I'd feel more comfortable not to speak about users, security groups, roles, etc., but about some real-life objects and scenarios.

Idoc sent with status 03 but not arrive to destination

Hi experts,
I am working on idoc scenario on ECC6.0.I am pushing the idoc from R/3 system to Cast Iron Midleware (non SAP aplication).I have done all the prerequisites involved to pushing idoc-----
maintain Rfc destinations,maintain port,partner profile,distribution model....
But when i am pushing the reduced idoc from sender it's showing the status 03.when i am running RBDMOIND, some Idocs change status to 12 and others not, still in 03.
I always sent the same Idoc to the customer. The strange thing here is that sometimes the same Idoc arrives destination without any problem and sometimes the exactly same idoc not arrives. That´s doesn´t make any sense..
When I enter to SM58 I can see this message: Commit fault: java.lang.RuntimeException: java.lang.NullPointerException. Message no. SR053
If I execute LUW the following message appears: Function module does not exist or EXCEPTION raised. Message no. SY359.
Please tell me what I need to do or check. This problem is about to explote.
Thanks a lot!

Dear Federico,
How you resolved this issue? I am getting the same, please find below log -
RfcException: [ABC.com|ESB]
 message: check TID fault: java.lang.NullPointerException
 Return code: RFC_FAILURE(1)
 error group: 104
 key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by ABC.com|ESB
>>> RfcAbort [7] >Fri Apr 04 12:16:54,346< ...
>>>> RfcAbort called by external program ...
 handle = 7
 text = check TID fault: java.lang.NullPointerException

Unable top convert the status of idoc from 03 to 12

Hi experts,
I am working on idoc scenario on ECC6.0.I am pushing the idoc from R/3 system to PI7.0.I have done all the prerequisites involved to pushing idoc-----
maintain Rfc destinations,maintain port,partner profile,distribution model....
But when i am pushing the reduced idoc from sender it's showing the status 03.when i am running RBDMOIND in se38 still it is not getting converted into 12.
kindly help me how can I convert the status from 03 to 12.
Thanks in advance.
Regards,
Naresh.K

Hi Naresh
you have to create the service. Create first the technical system and the business system in the SLD. Look for the right "Logical System" (Transation SALE in R3).
In the Integration Builder Directory go to "Environment/Clear SLD Data" and create the service by "Objects/Service without party/Business System/Assign Business System".
Hope this will solve your Querry
Thanks !!
Questions are welcome here!!
Also mark helpful answers by rewarding points 
Regards
Abhishek Agrahari

IDOC HRMD_A + Change pointers + Infotypes change objects doesnt exist???

Hi guys,
I Have to send master data from infotypes 0002, 0006, 0032 and 0105 from HR to SAP PI. I've configured BD61, BD50 and BD53 to reduce Idoc HRMD_A. Then in BD52 I've tried to put this fields to activate change pointers when data from this infotypes is changed.
But in BD52 doesnt exist infotypes 0002, 0006, 0032 and 0105. I tried with object HR_IT1002, table HRP1002 and fields BEGDA and ENDDA, then run program RBDMIDOC and the Idoc is sent, but is possible with infotypes metioned????
Regards,
Pablo

Pablo,
are you able to see entries getting created in BDCP* tables
did you activate change pointers in BD53
Thanks
Bala Duvvuri
Edited by: Bala Duvvuri on Jul 29, 2010 10:35 AM

IDOC: Material master data views

I create a material with an IDOC. The IDOC only contains basic data (i.e: segments E1MARAM and E1MAKTM).
However when I look at the material in MM03, I see all the data views.
Is this do to missing config in SPRO -> Material master configuration
I just want views that have data from IDOC

Hi,
You can check the partner profile for that partner.As my understanding in your case reduced idoc is created and that is used in the partner profile.May be that reduced idoc contains only the basic data segment only.
Thanks and regards,
shyla

The XI does not send messages with correct IDOC structure

SAP XI 3.0 sends to ECC IDOC HRMD_A07
The XI does not send messages with correct IDOC structure.
In XI Design, Software Component RHEVOLU, Ive imported the Objects
HRMD_A.HRMD_A07 from SAP ECC; In Tools -> Export Reduced XSD, I saved
HRMD_A.HRMD_A07.xsd in Namespace http://suezambiental.com.br/HR . At
Message Mapping -> mmAdmissao, in Imported Message -> Import XML or
XSD, I imported the reduced Idoc file generated above, mapping source
fields to target fields.
The IDOC sent from XI to ECC has this structure (template: 22122)
E1PLOGI
E1PORIG
E1PITYP
E1P0000
E1P0001
E1P0002
Status 53 -HR: ALE inbound processing for HR master data
But does not update HR Master data.
The structure expected in ECC side (template: 20376) is:
E1PLOGI
E1PORIG
E1PITYP
E1P0000
E1PITYP
E1P0001
E1PITYP
E1P0002
Status 53 -HR: ALE inbound processing for HR master data
By using WE19 transaction, this structure was changed manually; so, the
HR Master data was updated.
Witch kind of customizing or correction could be made in XI, to send
the correct structure to ECC?
Best Regards
Claudio

Hi Claudio,
In your case, there are perhaps two causes:
1. perhaps when you have import the idoc, for a strange reason, a bad metadata was created by XI. You can clean this one in tcode IDX2 (Idoc metadata cache).
2. but it's also probably an error in your Message Mapping. Have you correctly manage segment E1PITYP?
Regards
Mickael

Reduced IDoc

Similar Messages

Maybe you are looking for