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!
Holger

hi,
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

Similar Messages

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!
Holger

Hi 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

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.

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
Vasu

Hi,
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>

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
fariha

Hi 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
Bhaskar

PLEASE 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]

Basic type CREMAS03 does not exist

Hi all.
We have SRM 7 Classic Scenario with ECC 6.4
My problem is in scenario MM-SUS. When we try to replicate a vendor data from MM to SUS the idoc MM is processed correctly, but in (SUS) has an error in trx WE05: Basic type CREMAS03 does not exist.
I review the settings and I can not find the cause.
any idea about that?
Regards

Hi,
I am not clear with your issue. Why are you checking for idoc status in SUS system?
IDOC is sent from the ERP system and check what the status of IDOC is in ERP. Next check whats the xml status in PI system and if its successful in PI then check xml in SUS system/. You can check xml status using tcode: sxi_monitor.
Regards
Sam

Basic type for product hierarchy v/76

Hi all,
I have another task that need to configure once a product hierarchy is created in Tcode v/76, it will trigger an outbound IDOC and send out.
Can anyone explain to me what basic type or message type should be used in this case?
Thanks for help.
Best Regards,
JL

Hi,
I am having the same issue, to send prod-Hier via Idoc.
Please let me know if you get the solution for the same,
BR,
Udit

Idoc processing - determine Basic Type in Program

Hi Forums,
I would like to determine the Basic type that is being processed by at the time of my Idoc creation.
the function module I am using is being called by shipping document as well as delivery documents.
I would like my code only to be executed when it is a basic type of DELVRY05

Hi,
1) Goto Tcode - we57:
Assign function module to IDoc type
Module: Function module
Basic type:
Message type:
Direction: 2 (inbound)
This will differentiate between Shipping and Delivery.
2) Creating Inbound process code - we42
For Outbound Process Code -- WE41.
For further plz refer following link.
https://wiki.sdn.sap.com/wiki/display/ABAP/ALE%2CIDOC
Thanks and Regards,
ShreeMohan

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
Manuel

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

BASIC TYPE VS MESSAGE TYPE

Hi all,
Can i know wats the difference between Basic type and Message type??
wat s the use of having both this types????

hi
Message Type:
A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterises the data sent across systems and relates to the structure of the data called an IDOC type.
Diff. with IDOC type
An IDoc type specifies the structure of the data.
A message type specifies the meaning of the data
Diff. b/w IDOC type and IDOC
An IDoc type is the definition of a specific data structure.
An IDoc is an actual instance of data based on an IDoc type. Therefore, there can be many IDocs created from a single IDoc type.
Every idoc type will have Message Type.
It mean Idoc will be recognised By message type.
For ex : MATMAS03 is idoc type, and its message type MATAMS.
There are different message type for every master data. suppose for vendor master CREMAS is the message type, for customer mast DEBMAS like these there many message type for other type of master data.
To recognise the particular idoc, we use message types.
We82 is the TCode where IDoC type is attached to Mesage tYpe.
Refer to this related thread
difference between message type and idoc type
Check these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Regards
Anji

How can I delete the IDOC basic type and extension?

Hi,Expert:
There are some idoc basic types and extension which are not used any more in our system.Now we want to delete them.but when I delete them using tcode:WE30, system said that the basic type or extension has been released and they can not be deleted.
How should we do to delete these idoc types?
Thanks

From the top menu > edit> cancel release then try to delete
a®s

Error :- No authorization for basic types (activity 01)

Hi Experts,
While trying something at the BW server i suddenly got the below error
I am getting the error when i am accessing the T-CODE RSA1.
Error :- You have no authorization for basic types (activity 01)
I checked the ids of my colleagues all are getting the same messages...
Regards,
RG

Hi,
1. Check in SU53 tcode
2. You are having RSECADMIN/PFCG tcode access?? If yes you can give authorisation for the same.
3. You dont have S_RS_ADMWB - authorisation
4. for your user id give this above authorisation
5. If you are unable to do the same, ask your basis team to give you the authorisation
refer this link- 1.http://help.sap.com/saphelp_nw70ehp1/helpdata/en/f3/291542e4b4df2ce10000000a1550b0/frameset.htm
2.http://help.sap.com/saphelp_nw70ehp1/helpdata/en/a4/1be541f321c717e10000000a155106/frameset.htm
Edited by: Asish Sahu on Apr 28, 2009 10:34 AM

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 required

Hi,
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 Krishna

execute 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

Tcode IDX2: Basic type 'MATMAS02' is unknown

Similar Messages

Maybe you are looking for