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>

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

  • 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.

  • How to rectify the error "basic type z_idocname could not be converted"

    hi,
    I am trying to create a partner profile for a outbound process. In the transaction we20 i gave a new partner number, attached the message type and the idoc and the port no, when i tried saving its showing basic type z_idocname could not be converted how to rectify this error.

    Have you made the corresponding entries in WE81 and WE82?

  • Error : The type 'TPLIC_RVAL_TAB' is unknown.

    Hi all,
    I added a field in z table and regenerated the maintenance object through transaction SE54. Then I run SM31 to insert some records into table. But when I run the SM31 I'm getting 'The type 'TPLIC_RVAL_TAB' is unknown. ' error.  I don't have any idea about this error.
    Any help will be appreciated.

    Hi,
        There is no type with the given name : 'TPLIC_RVAL_TAB' ..
        I think you need to declare the below statement or is commented out
        TYPE-POOL tplic .
    Regards,
    Srini.

  • 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

  • The Type TP_TH_LISTNER is unknown

    Hi All ,
        We are in SP15 and When we try to implement a note we got this error ' the Type TP_TH_LISTNER is unknown ' . We are getting this error in Class interface (SE24)  - CL_RRMS_APPL_LOG .
    I think people who are in support pack 16 can help .
    Regards
    Santosh

    Please check, following OSS note is applicable or not in your case.
    Note 1020323 - Input-ready query: characteristic relationship, mem consump.

  • 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

  • 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

  • IDoc basic type FIDCCH01 with error F5866

    Iu2019m trying to create an iDoc with basic type FIDCCH01 and message type FIDCCH type.  Iu2019m getting error F5866 u201CWhen calling up the interface to financial accounting, no entry was made in the transfer parameter "Application key" when I process the idoc.  I do not see an idoc value by this name.  What am I missing in my config?
    Thanks,
    Stan

    Stan,
    First, I'd like to mention that you determine where the error message F5866 is used by entering this message in transaction SE91 and pressing the where-used function.  This won't show you any of the dynamic message calls, but it does indicate that function modules FI_DOCUMENT_CHANGE and FI_DOCUMENT_CHECK_CHANGE are both possible origins for the message you received.  These function modules are part of the FI Interface which I am assuming is called during the processing of your IDoc. 
    ACCHD-AWREF is one of the values passed to the FI Interface function modules, and message F5866 is returned when that field is blank.  This is why I assume that the IDoc in question is missing a value for the AWREF field.
    Based on that assumption, I checked the definition for the IDoc type that you mentioned, FIDCCH01, via area menu WEDI.  This IDoc type contains a segment E1FIREF with field AWREF.  You can use transaction WE02 to display the IDoc causing the error and check to see if the actual data for E1FIREF-AWREF is blank (ultimately leading to the blank ACCHD-AWREF value and error F5866).
    Cheers,
    Jamie

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

  • Error Cancelling Release of Basic Type

    Hi,
    Im using WE30 to make changes to a BASIC type. So in the menu EDIT->Cancel Release an error prompted these messages:
    The release of the basis types cannot be reset
    Message no. EA506
    Diagnosis
    The release can only be reset if the basis type has been released in the current Release. Basis type ZPADET01 has already been released in Release 46C, so this release can no longer be removed.
    Procedure
    Create a successor to basis type ZPADET01 so this new basis type can be further developed.
    I usually modify BASIC type with WE30 successfully. But this error message I'm at a lost.
    Please Help,
    Sid

    i wouldn't go about and delete it. just create a new one, let's say YPADET01. when you clicked the button 'create' there comes a pop-up where you can decide how to proceed. it is there where you can decide whether you want the new one to be a successor of ZPADET01.
    actually, i have been doing some reading on the subject and found about that release-thing:
    http://help.sap.com/saphelp_erp2004/helpdata/DE/dc/6b832543d711d1893e0000e8323c4f/frameset.htm
    start there and dig a bit around, so you can get a better clue on how to go on.
    sorry, that was the german link, here you go in english:
    http://help.sap.com/saphelp_erp2004/helpdata/EN/dc/6b832543d711d1893e0000e8323c4f/frameset.htm
    Edited by: Mylene Euridice Dorias on Aug 11, 2009 8:13 AM

  • 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

  • Error :- No authorization for basic types

    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,
    analyze the missing authorization with transaction SU53 immediately when the error appeared.
    Ask your system/authorization administrator to grant you the missing authorization.
    Regards
    Rainer

  • Data Services IDOC Errors when working with a newl Basic Type

    Hello,
    Just wondering if anyone else has encountered an issue similar to the one I am dealing with. We are trying to create business partners in SAP CRM from Data Services via IDOC. We are not using the standard IDOC, but instead we are using a new IDOC type.
    This IDOC type is generated by SAP CRM automatically through a transaction BDFG. This transaction creates a new basic type for an standard IDOC with the additional fields that we have added through the easy enhancement workbench (EEWB).
    The issue that we are having is that when we import the IDOC type into data services and we look at the schema many fields and sub-structures of the IDOC are duplicated. This means that we receive hundreds of errors when we try to validate our data flow. I can delete the duplicated sub structures in my query transformation but then the query transformation and the output schema and the idoc input schema are no longer identical.
    I have searched all over oss and different web forums for a solution but no one else it seems has even encountered this error. If anyone else has had a similar issue and can offer help it would be greatly appreciated.
    Bill

    Issue is resolved.
    After importing the meta data for the IDOC into data services I then proceeded to edit out all of the duplicate structures and fields from the IDOC.
    After making the IDOC structure in data services identical to the structure of the IDOC  in SAP I then proceeded to test this IDOC and it executed successfully.

Maybe you are looking for