Matmas05

Hi, How to see the details (logic etc) in R/3 System for standard idoc MATMAS05 to prepare a FS to interface with external system. Please advise what should i mention in FS in this regard. thank you.

closed as no respone recieved for long time

Similar Messages

Error: ****** is not a unit of length - MATMAS05

Hi,
I am sending material master data from a file to ECC thru SAP PI using MATMAS05, I see the idoc in status 51 and get the below error in SAP
" ****** is not a unit of length", I tried passing "(double quotes) , INCH in MEABM field but it does not take, please advice
Thank you

in MATMAS05 IDOCs you have to enter the ISOcode of a unit
execute CUNI, select Length and find the INCH unit, go into its detail and see what ISOcode it has

Getting error while try to send data to matmas05 idoc

hello frnds,
i m working on a scenario in which i m sending data from xml file to matmas05 idoc of R/3. here i have done all the required XI settings. at sender side i have used file adapter and at reciever side IDOC Adapter. while i m executing my schenario at that time i m getting green flag into the sxmb_moni transaction but m not able to see any idoc generated at the receiver R/3.
can anybody tell me that what might be the problem? is it the problem with R/3 receiver or it is the problem with XI configuration itself..
Regards,
Hetal

hi,
if the flag is green you can check in SMQ1, SMQ2
for any waiting entries
I hope you've activated the queues in SXMB_ADM
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Create Material using MATMAS05 IDOC

Hi Gurus,
Please tell me what are the mandatory fields and tables for those fields to create a Material using MATMAS05 standard IDOC.

Hi,
Fields are never mandatory while sending the idocs. Its the segment which is mandatory.
If you see the definition of MATMAS05 idoc in transaction WE30 you will find E1MARAM and E1MAKTM, as a mandatory segment. It means that you can't send an Idoc without this segment. If you go in segment details than even if you populate a single field in the segment E1MARAM and E1MAKTM then you can send the idocs.
KR Jaideep,

Flat file to idoc MATMAS05 - mapping

Hi,
I want to create 2 Idocs from one recordset.
Can any one tell me how do I map this Recordset to an Idoc?
Example source and target IDOC structures:
Source:-
 <Recordset>
 <SA010>
 <IDENTS>1234</IDENTS>
 <BEZ>Dummytxt</BEZ>
 </SA010>
 <SA088>
 <IDENTS>1234</IDENTS>
 <MARC1>010</ MARC1>
 <MARC2>020</MARC2>
 </SA088>
 </Recordset>
Target:-
 <MATMAS05>
 <IDOC BEGIN="1">
 <E1MARAM SEGMENT="1">
 <MATNR>1234</MATNR>
 <E1MARCM SEGMENT="2">
 <WERKS>010</WERKS>
 </E1MARCM>
 </E1MARAM>
 </IDOC>
 </MATMAS05>
 <MATMAS05>
 <IDOC BEGIN="1">
 <E1MARAM SEGMENT="1">
 <MATNR>1234</MATNR>
 <E1MARCM SEGMENT="2">
 <WERKS>020</WERKS>
 </E1MARCM>
 </E1MARAM>
 </IDOC>
 </MATMAS05>
Thanks and Regards,
Eren

Hello Varun,
My flat structure:
<Recordset>
<SA010>
<IDENTS>1234</IDENTS>
<BEZ>Dummytxt</BEZ>
</SA010>
<SA088>
<IDENTS>1234</IDENTS>
<MARC1>010<>
<MARC2>020</MARC2>
</SA088>
</Recordset>
The MATNR field is <IDENTS>. I can pick the value from node <SA010> or <SA088>.
Thanks

MATMAS05 Idoc to Flat File : Multiple material into same file

Hi ,
I am struck in simple scenario .Sending Materail Master data to flat file using idoc MATMAS05. I made following changes to MATMAS05.xml file.
I added MaxOccurs -=Unbounded and imported it in the interface mapping.
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:element name="MATMAS05"><xsd:complexType><xsd:sequence><xsd:element name="IDOC" type="MATMAS.MATMAS05" maxOccurs="unbounded"
I am able to get multiple materials extracted in same file .However the XML fails to open the file completely saying there is error.
Can anybody send me an xml file of Material Master having 2 matrials so I can compare it?
Regards
Prashanta

Hello Prasanta,
If I understand correctly you are sending MATMAS from SAP to File.
And you want to split the Matmas into multiple files .
If this is the case then do not change the Idoc field occurance on the target side. In the Message mapping , messages tab change the occurance of the target to unbounded.
And use enhanced interface determination for the same.
Cheers,
Himadri

IDoc MATMAS05 does not update MARA-AENAM

Dear colleagues,
I am using IDoc for maintenance of material master records. It's basic type is standard MATMAS05. When I trigger IDoc that needs to change material master record, this material master record is updated correctly, except AENAM field (Name of accounting clark who changed record). In my IDoc structure I have field which defines AENAM. This field is filled with proper information, but after IDoc running ERP MARA-AENAM is filled with logon user defined in RFC Destination settings and not with value from IDoc's AENAM.
Could you help me to solve this issue and have proper data in MARA-AENAM (from IDoc AENAM field)?
Regards,
Harry

the coding is undoubtedly taking the last change date and user from the SY structure:
IF neuflag = space
   and ( not rmmg2-new_inst is initial or
         not rmmg2-new_inst_v is initial or
         not rmmg2-new_inst_a is initial ).
    mara-laeda = sy-datum.
    IF user IS INITIAL.
      mara-aenam = sy-uname.
    ELSE.
      mara-aenam = user.
    ENDIF.
ENDIF.
And this sounds logical to me, as if this would not be the case, then you could change data with an IDOC and let it look as if this change was done by someone else.

Material Master IDOC MATMAS05 and unit of measure

Hi
We are using SAP standard material master IDOC type MATMAS05 to trigger IDOC. Our material master is having base unit of measure as "G". We are not using ISO unit of measurement. But Material master IDOC, segment E1MARM is populating base unit of meaurement (MEINS) as "GRM".
Any idea why IDOC is picking ISO unit of measurement instead of material master base unit of measurement.
Any idea how to send base unit of measurememt as "G" instead of "GRM" in DOC segment.
Thanks
Nilesh

Thats the way it works. In any interfacie to or from external sys. , it uses the ISO code from CUNI instead of the UOM .

Message Mapping of IDOC "MATMAS.MATMAS05"

Hi!
I would like to execute the following message mapping for IDoc
MATMAS05 <--> MATMAS05.
What are the recommended fields to map?
Is the a button to automatically map the fields with the same names?
Thank you very much!
regards
Thom

Hi,
you could use the button "Map Selected Fields and Substructures if Names Are Identical"
it's explained here:
http://help.sap.com/saphelp_nw04/helpdata/en/49/1ebc6111ea2f45a9946c702b685299/frameset.htm
Or if you do it without a mapping:
simple IDoc to IDoc scenario with SAP PI
Regards
Patrick

Sending MATMAS05 IDOC via XML-HTTP Interface (without XI)

Dear all,
I have to send the MATMAS05 IDOC via XML-SOAP-HTTP Interface to a subsystem. Sending works (the sub-system receives the SOAP-Request with the MATMAS05 as Body). So far so good. Now the SAP System is waiting for an answer (synchronous communication). How should this answer look like?
We receive the Error EA390 "Problem with SOAP Class" - execute_processing: entry result table
Can anybody give me a hint how the response should look like.
Many thanks and best regards
Roman

Hello Sven,
we find a solution. As far as I remember, there is a flag to send without waiting for answer (or technical better to not rely on SOAP standard).
Look in WE21 and the XML_HTTP Port you use. Uncheck the "SOAP Protocol" flag. Then it should work.
HTH and Best regards
Roman

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

I can create material using inbound Idoc of type MATMAS01, but not MATMAS05

I can create material using inbound Idoc of type MATMAS01 in WE19, but MATMAS05 failed. In fact I used same data ( different material number), and same inbound function, but got different result.
What is different between MATMAS01 and MATMAS05? Is there some configuation need for MATMAS05?
My system is ECC5.0. Thanks.

Hi, nagaraj
this is inbound IDoc, not outbound IDoc, so we can't assign Basic type in WE20, only can assign Message type.
In WE82, there are 5 records about Messagetype MATMAS:
     Message type   Basic type     Release
      MATMAS         MATMAS01        30A
      MATMAS         MATMAS02        30D
      MATMAS         MATMAS03        40A
      MATMAS         MATMAS04        46C
      MATMAS         MATMAS05        470
   I think it should be ok.
In WE57, there 2 records are exist:
   FM_name                 BasicType       MessageType
IDOC_INPUT_MATMAS01       MATMAS01         MATMAS
IDOC_INPUT_MATMAS01       MATMAS05         MATMAS
so I think all configurations should be ok.
Message was edited by:
        liu bin

File to IDOC(MATMAS05)

I'm trying simple scenario for File to MATMAS05 IDOC. I filled in the required fields it specified by Red in the message mapping, but still I get the following error when I try to test the mapping
Structure with min!=max without mapping
I dont understand what exactly this means..did anyone get this before? how to fix this error?
Thanks,
Kalpana

hi
Below one is for Cremas
u just follow the same procedure for u r Idoc with u r fields..
I think it is helpful for u upto some Extend...
2.11.4     Map the fields of the source document to the equivalent fields in the IDoc. This can be achieved easily by locating the target field in the IDoc structure and then drag-and-drop from the source field to target field. Please refer to the table below for the mapping rules (segments and fields are sorted according to their order of appearance in the IDoc).
Source field in Vendor     Target field in CREMAS03
VendorNumber     E1LFA1M à LIFNR
Address à Country     E1LFA1M à LAND1
LastName     E1LFA1M à NAME1
Address à City     E1LFA1M à ORT01
Address à Zip     E1LFA1M à PSTLZ
SearchTerm     E1LFA1M à SORTL
Address à Street     E1LFA1M à STRAS
VendorNumber     E1LFA1M à E1LFB1M à LIFNR
VendorNumber     E1LFA1M à E1LFM1M à LIFNR
Currency     E1LFA1M à E1LFM1M à WAERS
2.11.5     Now we have to assign constants to certain fields and attributes in the IDoc (for segment qualifiers, hardcoded values and XML attributes). This can be achieved by following the procedure below. Refer to the table below for more details on the mapping rules.
2.11.5.1     Double-click on the target field in the IDoc.
2.11.5.2     At the bottom of the screen, select Constants from the drop-down list for function type.
2.11.5.3     Click on the function Constant. Now the empty constant appears in the screen.
2.11.5.4     Double-click on the empty constant and assign a specific value.
2.11.5.5     Connect the constant to the target field.
Constant     Target field in CREMAS
1     CREMAS03 à IDOC à BEGIN
1     E1LFA1M à SEGMENT
009     E1LFA1M à MSGFN
COMPANY     E1LFA1M à ANRED
LIEF     E1LFA1M à KTOKK
1     E1LFA1M à E1LFB1M à SEGMENT
009     E1LFA1M à E1LFB1M à MSGFN
3000     E1LFA1M à E1LFB1M à BUKRS
31000     E1LFA1M à E1LFB1M à AKONT
A1     E1LFA1M à E1LFB1M à FDGRV
1     E1LFA1M à E1LFM1M à SEGMENT
009     E1LFA1M à E1LFM1M à MSGFN
3000     E1LFA1M à E1LFM1M à EKORG
2.11.6     For the segments E1LFB1M and E1LFM1M please assign an empty constant. This is necessary because these segments are optional in the IDoc. Although some underlying fields have already been mapped, If the parent node is not explicitely used as the target of a mapping, the segment will not be instantiated at all.
2.11.7     Finally, right-click on the segment EDI_DC40 and disable it (this segment is mandatory but will be filled out automatically by the IDoc adapter. Save your mapping.

The meta data for the IDoc type "MATMAS05" is unavailable

Dear Gurus:
I need help in completing small test that I am doing to send MATMAS IDOC to xMII.
I have done:
1. RFC connection SM69 and tested ok
2. xMII IDOC Listner config with my SAP client
3. Connection appears in smgw ok (in logon client screen)
4. Completed Distribution channel and we20,we21
All above looks in place when I send one IDOC (BD10) it remains in 03 even after I run RBDMOIND. Besides IDOC is not appearing in C:\Lighthammer\JCO\Output.
On tRFC I see error The meta data for the IDoc type "MATMAS05" is unavailable.
Note that
a) I am NOT using transaction on routing tab
b) xMII version 11.5
c) I used "How to send IDOC ...." Version 2 PDF that is available on web (thanks to Bimal)
d) I looked at other two posts which has to do with LOIPRO message type and with JCO issue
Please help.
Thanks
Jay

Jay,
What version of ERP are you using, perhaps this note will help: 770239
Also the SAP Help has some suggestions as well...<a href="http://help.sap.com/saphelp_nw04/helpdata/en/8a/b8b13bb3ace769e10000000a11402f/content.htm">Click Here</a>
-Sam
null

LSMW IDOC MATMAS05 Material Master

Hi Experts,
Actually ,Iam using IDOC method in LSMW for Material Master Upload.
For that Iam using the IDOC type MATMAS05 .
So in the input file when Iam not the giving the Material Number IDOC is getting failed
with status 51 and giving the errors that "NO MATERIAL NUMBER
TRANSFERED".
And
if Iam giving a material number in the test file it is again getting failed
giving the error " The material does not exist ".
I am not able to understand what iam missing here.
Other than this Iam passing all the mandatory fields required .
Also in the each segment iam passing the MSGFN = '009'. i.e. to create.
Pls help.
Thanks in Advance.
Regards,
Mithun

Hi Chuin,
This forum doesn't provide specific info on LSMW. You may check https://service.sap.com/lsmw for more info.
Regards,
Markus

MATMAS05 IDOC adding Quality Management view to Material when posted

Matmas05 IDoc when posted is appending Quality Management(QM) view to material.
Initially Material doesnt have a QM view . However whil e postion matmas05 , MAra-VPSTA & PSTAT fields are getting updated with the letter Q(which is QM). I'm not passing any fields relevant to quality management. I donot want any views to be added.
Thanks
Sunil R

I can see the IDOC data passing in through WE02 and can control which data I can pass in to MATMAS05 IDOC. However need to know why the idoc is appending a view to the material. I tried to Debug the IDOC_Input_MAtmas01 Function module which is used to process this incoming IDOC to SAP, coudnt get too far on that.
Where can i see the actual updating of tables like mara &marc in the above Function module at debug time?
Thnaks
SUnil R

Matmas05

Similar Messages

Maybe you are looking for