Artmas idoc reduction

Hi All,
I am trying to do idoc reduction for artmas. Did all the settings as should be done in the following order:
1)created a reduced message type (ZARTMAS) using BD53 with refernce to standard message ARTMAS.
2)Activated the changed pointers for this message type.
3)Added this message type to the distribution model
4)created partner profiles and all...
when I change an article and process it through BD21 only it says "1 master IDocs set up for message type ZARTMAS" and "0 communication IDoc(s) generated for message type ZARTMAS".
Cant think of why the idoc is not getting created.
As message type artmas belongs to BAPI RetailMaterial.Clone: even tried to create an ALE interface for the ZARTMAS message type. Still the same message.
If I do the same process for MATMAS, it works fine. Can anyone please tell whats missing or what am I doing wrong.Why is the idoc not getting created for ZARTMAS.
Thanks in advance.

Hi Fouad,
Have you looked segment E1BPE1MARARTX?
You can check this fields.
- CREATED_ON
- CREATED_BY
- LAST_CHNGE
- CHANGED_BY
- DEL_FLAG
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Similar Messages

XSL mapping of ARTMAS IDoc - carriage returns and white space

Hi all. I have tried all sorts here and am completely stuck. I am mapping an article master ARTMAS IDoc using XSL mapping and an extra carriage return and white space characters are being added to the FIELD1 and FIELD2 fields of the E1BPE1MARAEXTRT segment and I don't know why! These fields contain all our bespoke field values joined together so they are 229 and 250 characters long respectively, which I think is related to the problem. The mapping program looks like this:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="xml" encoding="UTF-8" omit-xml-declaration="no" indent="yes"/>
<xsl:template match="/">
<ARTMAS04>
<IDOC>
<xsl:copy-of select="//ARTMAS04/IDOC/EDI_DC40"/>
<xsl:copy-of select="//ARTMAS04/IDOC/E1BPE1MATHEAD"/>
<xsl:copy-of select="//ARTMAS04/IDOC/E1BPE1MARART"/>
<xsl:copy-of select="//ARTMAS04/IDOC/E1BPE1MARAEXTRT"/>
<xsl:copy-of select="//ARTMAS04/IDOC/E1BPE1MAKTRT"/>
<xsl:for-each select="//ARTMAS04/IDOC/E1BPE1MARCRT">
 <xsl:if test="(PLANT='D100') or (PLANT='D200') or (PLANT='D300')">
 <xsl:copy-of select="."/>
 </xsl:if>
</xsl:for-each>
<xsl:copy-of select="//ARTMAS04/IDOC/E1BPE1MARMRT"/>
<xsl:copy-of select="//ARTMAS04/IDOC/E1BPE1MEANRT"/>
</IDOC>
</ARTMAS04>
</xsl:template>
</xsl:stylesheet>
I have a test IDoc going through this and the first 3 characters of the FIELD1 are "BIK". If I look at the source of the XML file, the problem area looks like this:
<E1BPE1MARAEXTRT SEGMENT="1">
 <FUNCTION>004</FUNCTION>
 <MATERIAL>000000000000895649</MATERIAL>
 <FIELD1>
 BIK 0 0.00 T 000000001CARRERA FURY 04 20" CARRERA FURY 04 20" 2005092420040622 X 00000000 20031104 00200406140000000000 0.00 0000000
 </FIELD1>
You can't really see it above, but there is a carriage return and 8 white spaces before the BIK. Where does this carriage return and white space come from?! Any help would be really appreciated - this is driving me crazy!
Many thanks,
Stuart Richards

Stuart,
I think I know the cause to your problem. I am not an XSLT programmer but based on searching this forum I found how I can acheive the carriage return at the end of my document. Your xsl statement is as follows:
<xsl:output method="xml" encoding="UTF-8" omit-xml-declaration="no" indent="yes"/>
Change the indent value from yes to no. This should remove the carraige return. Hope this works for you.
I actually need a carriage return and line feed on my document so I am still stuck. All I have acheived is the carraige return.
Thanks,
Jim

Huge size of ARTMAS IDOC

Hello gurus,
We are facing an issue in trasmiting generic articles(MARA-ATTYP = 01) along with all its variants via outbound ARTMAS IDOC(Transaction BD10). Some of the articles have around 40-50 variants. When such generic articles are transmitted via BD10, the size of IDOC is too huge for middleware to handle.
These IDOCs fail at the middleware end as the XML file is too huge for them to handle.
Do we have any standard functionality which wouldallow us to split the IDOC data into smaller chunks and transmit the same.
Any pointers to this issue would be a great help!
Thanks in advance.
Regards,
Mohini
Edited by: Mohini Shewale on Feb 12, 2009 1:30 PM

Hi Mohini,
what does it mean, the IDOC is too big ?
Which segments have the biggest numbers?
With a generic article you have
1 MARA segment for generic article
and 40 MARAs for the variants.
Which middleware is not able to handle this size?
Do you really need all the data in the IDOC? Maybe you can filter some segments like MBEW or MARD to make it smaller.
Or you reduce some fields per segment.
You can filter it in distribution model transaction BD64.
regards
Björn
Edited by: Björn Panter on Feb 12, 2009 2:22 PM

Huge size of ARTMAS IDOCs

Hello gurus,
We are facing an issue in trasmiting generic articles(MARA-ATTYP = 01) along with all its variants via outbound ARTMAS IDOC(Transaction BD10). Some of the articles have around 40-50 variants. When such generic articles are transmitted via BD10, the size of IDOC is too huge for middleware to handle.
These IDOCs fail at the middleware end as the XML file is too huge for them to handle.
Do we have any standard functionality which wouldallow us to split the IDOC data into smaller chunks and transmit the same.
Any pointers to this issue would be a great help!
Thanks in advance.
Regards,
Mohini

Hi
I think you should split the idoc to 2 separate idoc's
Please refer to this link to split the idoc's
Message split to 2 differenet IDOCs
Thanks
Viquar Iqbal

IDOC reduction for MSG type MATMAS

HI all,
i have a requirement where clients need only some standard segments and some particulars staructure.We are using MATMAS as a message type and MATMAS05 as a basic type.Basically it leads us for IDOC reduction. Can someone pls help me out for getting this requirement.
Rgds,
Raghav
Edited by: raghav on Jun 9, 2009 12:28 PM

Hi,
Launch the BD53 transaction (IDoc Reduction Maintenance: Initial Screen). In the Reduced message type field, type the value ZVISTAPM_REDUCED, then press the Create button. In the popup window which appears, type in the Message type reference field the value MATMAS.
Validate.
In the next popup window, type a short description for the new reduced message type.
Validate.
In the following window, select the segments and the fields needed for the new reduced message type.
Save.
KR Jaideep,

Idoc Reduction CREMAS

Hi,
Is there an alternative to this approach :
Problem: I create Vendor master idoc using basic type crema04 and message type cremas. Idoc reduction is present for this message type, so when the idoc is created only mandatory segment gets populated.
Solution I tried : Through BD53 , create a ZCREMAS reduction message type , select the segments to be populated , enable them and activate them . Use this message type for the generation of the idoc.
Question : Is there any alternative way to this method or this is the only way we can remove the idoc reduction for messag types?????
Thanks ,

Hi,
Perhaps you can use this custom exit '001' in include in include program LBD11F0Q to filter IDoc segment.
CALL CUSTOMER-FUNCTION '001'
 EXPORTING
 idoc_control_in = pxf_idoc_control
 target_idoc_type = target_idoctp
 target_cim_type = target_cimtyp
 IMPORTING
* idoc_control_out = pxf_idoc_control
 idoc_control_out = idoc_control_out
 TABLES
 idoc_data = pxt_idoc_data
 idoc_status = t_idoc_status.
This is being in FM MASTER_IDOC_DISTRIBUTE.
For SAP best practise, i would suggest to use reduce message type or segment filter.
Again, hope this will help.
Regards,
Ferry Lianto

FUNCTION elememt in ARTMAS IDOC?

Hi,
I m looking for the e;eaning of the FUNCTION elememt in ARTMAS IDOC! is it relation to creation / upadate data?
If it s true, how it s look this maching?
Thanks,
FF

hi,
values for Function element from WE60
'003' Delete: Message contains objects to be deleted
'004' Change: Message contains changes
'005' Replace: This message replaces previous messages
'009' Original: First message for process
'023' Wait/Adjust: Data should not be imported
'018' Resend
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Problem with ARTMAS idoc

Hi
I am working on an IS-Retail implementation and we deal with article master (similar to Material master). The idoc corresponding to this is ARTMAS.
The scenario is as explained below.
We have articles classified as 'generic' and 'variant'. One generic article can have many variants. eg. T-shirt can be a generic and its variants could be 'High neck', 'V-neck', 'round neck' etc.
The issue is : Whenever we make article master changes to the generic article and execute the tcode BD21 - idoc type for change pointers for ARTMAS, the articles whose info is changed triggers the outbound idoc which contains a segment ' E1BPE1MATHEAD' containing the details of generic and a number of segments 'E1BPE1AUSPRT' which contain the details of the variants associated with the generic,
When i changed any field in MM42 for a generic article, the idoc generated through BD21 contains the segments for variant articles also.
However, when the description field -MAKTX is changed for the generic article, the outbound idoc generated through BD21 does NOT contain the segment for the associated variants.
I need the outbound idoc to include the variant segments (E1BPE1AUSPRT) also when the Description of the Generic article is changed.
I have checked the table fields associated with ARTMAS and the field MARA-MAKTX is included in BD52.
Can someone throw some light on this.
Thanks in advance.

hi negender,
can u help me how u solved the issue,
thanx,
hari

IDOC reduction gets always MATMAS05 as basic type

Dear Gurus,
I am trying to create a reduced IDOC derived from MATMAS message. I get always an associated basic IDOC type MATMAS05 but I would like this concrete reduction to be derived from MATMAS03.
Can somebody tell me what can I do so the system will reduce from MATMAS03 instead of MATMAS05 ?
I am using release 470 for the application ERP and basis has release 620.
Thanks

Hi ,
When you are reducing the Idoc, system will consider latest version of the Basic type of mesage type MATMAS,
You can not reduce previous version, this is SAP standard,
You have to reduce MATMAS05 based on u r requirement and create new Message,
Revert back if u have any queries...
Regards
Suresh.,D

Idoc reduction

Hi all,
I want to reduce few segments of the basic idoc matmas05.
I have created a new reduced message type in transaction bd53.
I have selected the segments which are needed and then saved the reduced message type.
But I see no reduction in the Idoc.Could anyone guide me if I am missing any step.
thanks,
Keerthi.

hi i think it is better to create a new zidoc with the required fields ....in the tcode we30

IDOC reduction for ORDERS05

Hi,
Is it possible to reduce the idoc for ORDERS05? I used BD53 and gave a new message type ZORDERS and it is asking for with reference to message type...I am not able to see orders there.
Can anyone suggest how to proceed here?Is it something that only master idoc can be reduced?Pls suggest.
Regards,
Jeyananth

If you've just tried to enter ORDERS in there, you would've seen this message:
"There is no data maintained in the reduction pool for message type ORDERS
Message no. B1121
Diagnosis
This transaction is used for maintaining and displaying reduced message types. In the standard not all message types can be reduced.
There is no data in the reduction tool for message type ORDERS.
Procedure
Use the transaction WE30 for maintaining and displaying the associated intermediate document type, or use the transaction BD60 to maintain the data for the reduction tool."
But I wouldn't recommend reducing the IDoc - it's more trouble than it's worth IMHO.

Problem Sending ARTMAS IDoc

Hello,
we have following error.
ARTMAS04 IDOC contains a field like <2STEP_PICK>.
But a XML tag with a number in front isn't well-formed.
So i got an error on my XSLT Mapping.
Any Idea?
Reagards,
Robin

Hi Robin,
the field is called "_--32STEP_PICK". May be load metadata again in IDX2 or load IDoc again to Repository.
Regards,
Udo

Function element value in ARTMAS IDoc

Hi,
My scenario is IDoc->Xi->File, my mapping is based on Function element (if the IDoc contains changes or new data) but all time I got just 005 as Function witch mean new article.
Is there any set up to do in order to get 004 for changes and 005 for new data?
Thank you,

Hi,
You are doing an Idoc to File and the idoc is sent from your SAP system.
In real time, the functional team would have scheduled a report that will create the idoc and send it to XI. The Logic for creating the idoc would be with your functional team. So,. it would be best to ask the functional team for the clarification on this and ask them to send the appropriate data.
Regards,
Bhavesh

IDoc reduction with different system versions

Guys,
I'm having the following issue.
Two SAP system A and B. I want to send MATMAS Idocs from system A to system B. System A is 4.7 while System B is version 6.0
Further more I need only limited data to be sent from system A to sytem B therefor I'm trying to reduce the MATMAS IDoc type and this is where I'm having trouble:
When I run BD53 (Reduce IDoc) on system A, I type in the message type that I want to reduce (MATMAS) and it automaticaly defaults the basic type as MATMAS05 while doing the same on the target (B) system the basic type assigned to MATMAS is MATMASDI.
How can I use the same basic type on the both systems?
You help would be much appreciated.
Thanks a lot,
Viktor Varga

Oh, it's BD69, I got it.

IDOC REduction to !

Hello Experts my Questions are as follows...
I am planning to use basic Idoc type
MATMAS04
1. I want to reduce it Coz it has too many segments in it ( will i have to attach a new msg type to IDOC again or i just reduce it )
2. I want to update the short text STXL STXH tables too...or Say i want to update basic Data Text Which is about 2000 char long ( What will i have to do ) .
3 I want to save a file Address ( the file is a drawing of the material ) in the DRAW TABLE
4. Can i write certain routines to update other tables also...
Please suggest some approches to my problem ...( I am aware of the TCodes ....:) )
Edited by: Anup Deshmukh on Dec 28, 2009 11:33 AM

Hi Anup,
I am not export for matmas processing. But in general there are necessary segments, marked as "required" in the documentation WE60. They need to be added, all others can be ignored. BUT: If there is a child-segment below another one, you need to add the father-segment too.
Hope you will get answers to your other issue, too.
Regards,
Gerlinde

Artmas idoc reduction

Similar Messages

Maybe you are looking for