Basic type 'MATMAS01' is unknown in SM58
I try to send IDOC to XI , i have done all settings when i send IDOC from BD10 i get error like that "Basic type 'MATMAS01' is unknown" by selecting message type AIDMATMAS.
but i have imported IDOC type "AIDMATMAS.MATMAS01" in integration repository already.
when i look at status of IDoc in sender system's WE05, last status is 03, not 12..Namely it doesnt reach XI.
what can it be the error ?
Thanks a lot
Hi,
Follow below configuration it will work i think it is due to customized idoc, once again check with segment, idoc and message type configuration and check whether all are released or not.
1. Check whether segment, idoc and message type are released or not.
2. Define Logical system and assign logical system to sender system (r3)
3. Define RFC destination in R3 system.
4. Define port and partner profile, in partner profile outbound window configure idoc parameters properly
According to ur requirement ur r triggering IDOC through abap program, check with control record parameters, some times due to control record parameters will throw error.
Once r3 configuration is over configure settings in XI
1. Import IDOC from r3 in IR window, if u getting any problem for import it will throw error. Check with basis team for authorization.
2. Configure RFC destination for R3
3. Configure IDX1 and IDX2 ports properly.
4. Configure scenario according to your requirement in IR & ID window
It will work without fail.
Similar Messages
-
Tcode IDX2: Basic type 'MATMAS02' is unknown
Hi!
How to get the basis type such as MATMAS02, MATMAS05 as known basis type in tcode IDX2?
When I try to load metadata in tcode IDX2 I get the following error:
Basic type 'MATMAS02' is unknown
Message no. EA224
Thank you very much!
Holgerhi,
check the PORT is defined correctly in IDX1 in XI system.
Check SM58 in R/3 system..
check this blog as well page 9-10
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
Have you imported the IDOC into IR ?
Sachin -
Error: Basic type 'WVINVE03' is unknown
hi sdn frnds
I am doing File to Idoc scenario in that i am getting the error as
Error: Basic type 'WVINVE03' is unknown
can any one know about this and how to solve this problem
thanks in advance
VasuHi,
where do you try to find this idoc?
this IDOC should only be in the R3
(not in the XI)
if you want it in the XI you need
to download it's sigmature in <b>integration repository</b>
just like described here:
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a> -
Basis type MATMAS02 is unknown
Hi!
How to get the basis type such as MATMAS02 known basis type in tcode IDX2?
When I try to load metadata in tcode IDX2 I get the following error:
Basic type 'MATMAS02' is unknown
Message no. EA224
I already created Ports in tcode IDX1, defined the RFC connections, etc.
Thank you very much!
HolgerHi Holger,
What I don't understand is why you have created this thread that is identical to other one you
created this morning:
Tcode IDX2: Basic type 'MATMAS02' is unknown
And even you marked it as solved.......
Carlos -
Msg basic type idoc_type unknown ?
Hi,
i am workin on file 2 idoc scenario.
on XI created rfc destination using sm59
went to idx1 created port and assigned the rfc destin
In idx2 i was able to load one idoc but remaining
shows the message basic type <idoc_type> unknown.
Can any one help??
regards
farihaHi Kazi,
for File to IDOC no need for IDX2
Check my link at wiki for File to IDOC
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&
Sachin -
Basic IDoc type ORDLGT01 is unknown
Hi All,
When I test run to execute business object from BUS2032 from SWO1,
I got the following message: "Basic IDoc type ORDLGT01 is unknown".
Please let me know why its so happening.
Regards
BhaskarPLEASE SEARCH SDN before posting ([rules of engagement|https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement])
[SAP Note 607330 ALE: Basic type ORDLGT01 unknown|http://service.sap.com/sap/support/notes/607330] -
IDOC Segement Release vs IDOC Basic Type
Hi there,
we are in an upgrade project and are runing into a general question about idoc creation.
Here is our behavior:
1. We have an reduced IDOC Type in BD53 ZMATMAS based on Messagetype MATMASDI.
2. It has 2 Segements E1MARAM with fields MSGFN MATNR PSTAT and Subsegemnt E1MAKTM with fields MSGFN SPRAS MAKTX.
3. Done the things around (RFC, Partner Profile, distribution model, changepointer ..)
4. In Distribution Model in outbound parameters, added our ZMATMAS.
As parameters we have: Partner type: LS, Message Type: ZMATMAS, Basic Type MATMAS03! and Seg. release in IDOC Type 46B. The Partnersystem is an NoneSAP System.
We are using MATMAS03 because this interface exists since 46B.
Now we send an Material with BD10 and Message Type ZMATMAS.
The Master and Commuidoc are successfull created. In BD87 the commuidoc is an MATMAS03 and has the expected 2 segements E1MARAM and E1MAKTM.
But what we do not expect, if we look into the content of E1MARAM there are ALL Fields which exist for the E1MARAM in release 7.00. Not only our 3 fields MSGFN MATNR PSTAT, or as we second expect only the segemnts that had existed in the segemnt E1MARAM in release 46B of MATMAS03.
The additional fields were filled with the NODATA sign.
My question is: Is it correct that an IDOC with basic type MATMAS03 can have an segement E1MARAM which is formated like the segemntdefinition E2MARAM007 (Release 7.00 / 6.03)?
The difference is definatly the length of the field! 876 in 7.0 vs 757 in 4.6A.
Why is SAP using the highest available segemnt release regardles which basic type we choose?
Isnt this wrong?
Additional infos:
We know that it is not possible to have an IDOC with basic type MATMAS03 with an segement e.g. E1MARA1 which only exists in newer basic type MATMADI if segemnt release is set to 46B in our distribution model.
Failure is: Segment E1MARA1 is unknown in Release 46B/ (correct and expected behavior)
If we are using this scenario with not an reduced message type, we will only find the fields in E1MARAM which are filled with data. (Not all fields of the latest release with nodata)
I traced the MASTER_IDOC_CREATE_MATMAS and hit the function IDOC_REDUCTION_FIELD_REDUCE. As you can see in it, it first checks if the idoc is an reduced message type, and at the end, fills up all fields with the "empty_symbol" which have no data in it. Why is this only happening if it is an reduced message type?
Kind regards
ManuelAdditional Info:
In WE21 at the TRFC Port, it is possible to set this Option:
Send Only Fields of Selected Segment Version
The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
But if we are using an reduced message type, all fields of the newest release are in the segement.
The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
But it is never called when createing an material IDOC with BD10.
Bug or feature?
Kind regards
Manuel -
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 -
Enter a valid basic type - BW IDoc type RSSEND is not same as the SS IDOC
Hi,
I am connecting the ERP system to BW system, and am getting error:
CHECK(context menu source system):
@5C@ BW unknown in source system RSAR 8
@5C@ The BW IDoc type RSSEND is not the same as the source system IDoc type RSAR 371
RESTORE(context menu source system):
Information: Enter a valid basic type
Information help:
Enter a valid basic type
Message no. E0434
Diagnosis
An entry with the key /BD2CLNT100/LS//RSSEND//// is to be inserted in
table
EDP13.
The value 'RSBEND' is not valid for field IDOCTYP.
Procedure
Check whether basic type RSBEND exists.
help requiredHi,
Please find the below link may useful.
http://wiki.ittoolbox.com/index.php/Re-Connect_R/3_and_BW
Reg,
Venkat -
How to change the default IDOC basic type from CREMAS05 to CREMAS04.
Hi All,
How to change the default IDOC basic type from CREMAS05 to CREMAS04 when sending Vendor Master Data.
When I generate partner profile, the system will add the latest version of IDOC type which is CREMAS05 to the Outbound message. In my project, I'm asked to use CREMAS04.
I want to use BD14 to send master data directly, but the program will generate IDOC using CREMAS05. Is there a way that I can change it to CREMAS04? And also for using Change Pointers, I want to use the report RBDMIDOC, but i have the same problem.
Thanks
Sai Krishnaexecute WE20 and edit the outbound parameters
here is a pretty good example: http://documentation.softwareag.com/webmethods/sapr3_gateway/sap231/pages/sapdist.htm
Edited by: Jürgen L. on Sep 7, 2011 9:49 PM -
Error in idoc of basic type artmas05 - status 51 with Message no. MG537
Hi all,
I tried to upload the material master table through idoc creation of basic type artmas05. But when i'm trying to do that i'm getting status 51 with Message no. MG537. then I analysed the application log which displays the following
*The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required
field; it does not contain an entry
*The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
*The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
*You have not fully maintained the tax classifications
*The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
But i hv given values for all the above fields in their respective segments.So can any1 suggest me how to proceed further.
It would be helpful if someone could tel me the required fields in idoc to upload material master table through idoc.
Thanks in advance,
Revathi.Hi,
Anybody please tell me the reason for the following error, despite giving all the field values mentioned there. The same error occurs even if I run the BAPI (which the ARTMAS iDoc uses) directly by passing values.
The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required field; it does not contain an entry
The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
Regards,
Gowri.S -
Reg : The functionality of WMMBID02 Basic type in SAP.
Hi All,
Can anyone give me the functionality of WMMBID02 Basic type in SAP. Mean, not the structure of the Idocs i am talking about. But to which Module of SAP is it related to and what kind of inventory data it carries? what the significance of this data. which table get updated when this idocs gets posted successfully.
And also that, From table /GLB/RGTTPLANHED, we can get the trip status. So wat exactly this trip status indicates?... can anyone explain this in detail?The message typer for this is WMMBXY and its used for Goods movement between storage location. This would internally calls MB01 transaction and related to MM module.
-
How to populate custom fields in SAP standard Basic type DELFOR01(E1EDK09)
I've a requirement to include and populate 2 custom fields in SAP standard basic type DELFOR01 and Segment E1EDK09 (it is at hierarchy level 1 ) .
The requirement looks very simple but for this, as per my knowledge, I have to create a new Basic type with the copy of segment E1EDK09 and attach it to outbound process code and write my own function module to populate the segments.
It seems ok but the there are some existing codes in the user-exits for the SAP standard function module.These codes will not get triggered.(Or I've copy the user-exits code in my FM)
Can we do it any other way to handle this kind of situation?
Thanks in advance for your suggestions and help.Hi Phani,
You have done it correctly. ECC additional data to be moved to EWM, 1. you need to enhance the CIF for master data/ bapi to populate the data in the custom field in EWM. 2. Make your your are not enhancing only one structure. You need to do it in the CI includes so that the field is available in all the related tables/structures.
3. The BAPI/FM which updated these tables will take care automatically to update the custom field data if the field is correctly added in all the tables.
4. If the custom fields are added correctly and still the data is not getting saved , then need to check the mapping of the custom field and bepi extension.
Let me know if this helps. -
JMS sender adapter : message type null is unknown, payload cannot be read
Hello,
We are building a scenario Weblogic -> PI through a JMS adapter, but we are getting the following error in the adapter :
2009-09-29 12:09:58 Information New JMS message with JMS message ID ID:P<450046.1254218997063.0> received. The XI message ID for this message is e705a65f-3cf6-472a-3675-b04e9862ce45.
2009-09-29 12:09:58 Warning JMS message ID:P<450046.1254218997063.0>: message type null is unknown, payload cannot be read and will be empty!
2009-09-29 12:09:58 Warning JMS message ID:P<450046.1254218997063.0>: Payload empty or cannot be read.
2009-09-29 12:09:58 Information JMS Message was converted to XI message succesfully.
Despite the fact that the message is not readable, PI creates a message anyway but the payload is empty. It is the same issue as described in this thread :
How to read Java Object message from JMS Queue using JMS Adapter .
But there have been no answer there.
We have read many notes but none are relevant, any ideas ????
Many thanks,
GLHallo,
Have you seen this note:
[Note 837501 - J2EE JMSAdapter: Empty payloads, unknown JMS message types|https://service.sap.com/sap/support/notes/837501]?
Seems it can be either message
a) does not contain any payload and/or
or
b) is not of type TextMessage or BytesMessage
/Jakub -
Inbound IDOC basic type HRMD_A07: Why no validation available?
I am using a standard inbound IDOC basic type HRMD_A07 to update employee master data (IT0000 & IT0001). However, i found out that this IDOC just directly updates to the infotypes without any validation. For example, i provide an invalid company code (BUKRS) and personnel area (WERKS), the IDOC still updates into database without any proper validation.
Filled the following fields in the IDOC segments:
E1PLOGI
plvar=01, otype=P, objid=00000001, opera=I
E1PITYP
plvar=01, otype=P, objid=00000001, infty=0000, begda=20120101, endda=99991231
E1P0000
pernr=00000001, infty=0000, endda=99991231, begda=20120101, massn=01, massg=01, stat1=3, stat2=3
E1PITYP
plvar=01, otype=P, objid=00000001, infty=0001, begda=20120101, endda=99991231
E1P0001
pernr=00000001, infty=0001, endda=99991231, begda=20120101, bukrs=XXXX, werks=XXXX, persg=1, persk=EC, abkrs=99, plans=00000111, otype=S
Please help me out in case I am missing something. Thanks.Additional Info:
In WE21 at the TRFC Port, it is possible to set this Option:
Send Only Fields of Selected Segment Version
The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
But if we are using an reduced message type, all fields of the newest release are in the segement.
The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
But it is never called when createing an material IDOC with BD10.
Bug or feature?
Kind regards
Manuel
Maybe you are looking for
-
First DTP in Process chain giving Error "CX_RSB_WRITE_ERROR"
Hi All, I am facing a problem when I execute a process chain. I have a master process chain and 3 sub process chains. Each of these sub process chains are having some DTP in it in a sequential order. These DTP's are Independent of each other, so even
-
Query query = em.createQuery("select of from employees o where o.status : = status and o.lastName LIKE 'lastName%'"); query.setParameter("status", "A"); query.setParameter("lastName","Anne"); when i try to run the program with this code, I get the fo
-
Certificate Error when using pub services with IE7
everytime i try to use pub services admin console i get the following warning im using IE7 any idea how to stop this nag ? : There is a problem with this website's security certificate. The security certificate presented by this website was not issue
-
Cannot find/fix the error specified
My website is www.abilityaxis.com. I have a template that I use to create my pages. There seems to be an error on one of the pages regarding the template, but not the others. http://abilityaxis.com/2011calendar.html When I make a change to the templa
-
iCloud not allow login. It shows the password error but I am able to login to site using same Apple ID. I just update my software to Mountain Lion 10.8.2 I tried a lot... 1) I changed passwords few time. (through using forgot password options) 2) Cle