Error: Metadata EDISDEF for port SAPEC1, IDoc typ

I am getting following error in my File-2-IDOC scenario.
Could anyone please help me out?
<b>Error: Metadata EDISDEF for port SAPEC1, IDoc typ
CREMAS04 and CIM type  not maintained</b>
I defined RFC Destination and Port properly..
Did I miss out anything.
Thanks in advance for the help.
Venu

Hi,
A few checks to be done,
1. GO to the RFC destination 9in SM59 and see if the Remote Log on and Test COnnectiivyt to the R# system works.
2. Go to IDX2 and deleted the exisitng Metadata and import the same meta data manually. IS the import succesful?
3. Check if you have entered valid POrt value and RFC destintion in IDOC adapter.
Regards,
Bhavesh

Similar Messages

  • Metadata EDISDEF for port SAPPF5, IDoc type ZIDOC_PARTNER_NOM and CIM type

    Hi all,
    I simply migrated a scenario for an XI 3.0 server to the new PI 7.0 server it will run on. When I do the IDX2 to pull in the metadata I get
    "Segment Version could not be read", but it still shows the metadata.
    then when I run the IDOC I get the above error in the subject line. Everything is the exact same in the two XI systems but one works and one does not. Please give direction!
    Chris

    Hi,
    Could you verify connection in port configuration. Transaction IDX1. Maybe RFC destination which you used is wrong.
    You can also use this report in PI:
    IDX_CHECK_METADATA - check IDOC adapter metadata  inside XI against source systems
    /wg
    Edited by: Wojciech Gasiorowski on Feb 27, 2008 8:34 PM

  • ERROR IN CREATING SALES ORDER,USING IDOC TYPE ORDERS05

    I am using exit to write my code for creating sales order of IDOC Type ORDERS05 and order type ZDRX.
    IF I proceess the Idoc in background each time error message comes
    FIELD kuwev-kunnr(ship to party)is not an input field.
    but if i run in foreground in debugging mode,sales order is getting created..
    please suggest something.

    If thats not working..
    try BAPI_SALESORDER_CREATEFROMDAT2
    If BAPI is not working. try creating a bdc for the same if there's not error on trying from VA01

  • User exit / BADI for the MATQM01 IDOC type?

    Hello,
       I am working on a Material Master conversion that will need to include the Material Inspection Setup. Using BD10 to send the material 'In Full' generates these MATQM01 IDOCs successfully. As part of this conversion I need to map some old plants to new plants.
    Is there a user exit or BADI within the MATQM process that I can use to accomplish this?
    The BADI/Exits for BD10 do not access the MATQM data. There are no exits listed for QL11 which is the standalone code for creating MATQM idocs.
    Any help would be appreciated!
    John

    Thank you guys for the replies. I will try the Rules and Filters approach to implement the logic I require. If the logic is too complex then I will go with the z-copy of QL11.
    Thanks!

  • IDoc Error in LSMW for MB1C - Special stock type is E

    When we use MB1C for GR to enter initial entry of stock balance into unrestricted stock for special stock type is E.
    The document is Posted.
    But, when we use LSMW for the above Transaction, the document is not posted.
    In the Inbound processing of IDOC  has the status "Application document not posted".
    In the IDoc Status record gives
       current status : 51 ("SD Document XXXXXXXXX is not in the database or has been archived"
    Pl explain how this problem can be addressed.

    Hi,
    It seems that the stock indicator in E demands for a sales order in the MB1C transaction. The sales order provided by you in the flat file is getting validated by SAP and that sales order is not available in the system or might have been archived.
    It is better to provide a live Sales order to book the stock to that particular sales order. If in case if the Sales order mentioned by you is closed or not required, in such as case the material can be stored under unrestricted stock and not under the sales order stock
    Thanks and Regards,
    Dilli Babu R

  • Segment E1IDBW1 is missing for the inbound idoc type PAYEXT

    Hello,
    the above segment is missing in the inbound idoc - basic type pexr2002.
    I have checked in TC-we30 and its available there.
    but still the idoc is getting generated without this segment.
    can someone suggest.
    thanks
    Arun

    Hi All,
    I have a similar query to that of Penny. We are able to get the standard IDOC to generate with segment E1IDBW1. It contains the standard fields INPWEEMP, INPWTXT1, INPWTXT2. However, we have a requirement to manipulate the standard contents of these fields. We wanted to use user exit EXIT_SAPLIEDP_002 to do this.
    I have maintained user exit EXIT_SAPLIEDP_002 but when we enter this on creation of the IDOC the segment E1IDBW1 does not seem to be available in table EDIDD_TABLE for manipulation. Can you advise please if (1) you were able to get E1IDBW1 available to edit in exit EXIT_SAPLIEDP_002  and (2) were you able to manipulate the contents of INPWTXT1, INPWTXT2 etc?
    We have done the following steps:
    - BTE 2441 is available on our release
    - house bank has been setup as an In House Cash Center which allows E1IDBW1 to be generated
    - entry has been maintained in table FEDICUS with Message Type = PAYEXT, BasicType = PEXR2002, Extension = Blank, Seg Type = E1IDBW1
    - code maintained in ZXF08U04
    The system enters ZXF08U04 but E1IDBW1 is not available there for manipulation.
    Can you advise what we might be missing please?
    Thanks and regards
    Mike

  • Error:storage location for material's valuation type does not exit

    create physical inventory document for material , it has a error message "Storage location X105 for material 0004AA00 plant 1151 valuation type **** does not exist", MMSC is ok, so i don't know what question?

    Hi Yan,
    If no previous goods movements have been posted yet for the combination  of the relevant material, plant, storage location and valuation type  the physical inventory cannot be done.                                                                               
    The table MCHB is used for both batch managed materials and materials  with split valuation. You can only create a physical inventory document for a material with   split valuation when both, a MARD and a MCHB segment are available.              
    When you create a valuation type in the material master, only the table  MBEW is updated - an entry is not created in the table MCHB. This is needed however to perform a physical inventory for this material.                
    This MCHB segment is created when you perform a goods receipt for the material, but (like with batches) a physical inventory posting cannot   create this entry in the table.                                                                               
    You will need to create a material posting for these materials if you wish to create a physical inventory for them. On the other hand, please,    consider that it is not necessary to create a physical inventory for those materials which have not suffered any goods movement at all.                                                                               
    If you want to make a physical inventory for a material valuated separately, you have to proceed as follows:                                                                               
    - make a goods receipt (561)==> then the stock segment will be created           
    - make the reversal of the goods receipt                                         
    - make the inventory.      
    Hope this can help
    Regards,
    Mauro

  • User Exit available for basic inbound idoc type MBGMCR01 in SAP R/3

    HI,
    We are looking for the User Exit for BsicIdoc MBGMCR01.
    When we create confirmation in EBP, this idoc gets triggered from EBP to R/3 to create goods receipt material document.
    Regards,
    Nikhil.B

    Hi
    <b>Please go through the following links, for all the required details -> </b>
    GRN IDOC Transfer to ERP  - MBGMCR01 ( 2 IDOCS created)
    Re: GR IDOC Number
    Re: Confirmation screen field to be mapped to backend field
    Re: Delete goods confirmation in SRM3.0
    Re: Not able to change confirmation date
    Confirmation against Backend PO for SRM@ERP2005
    Re: SRM Confirmation # in R/3
    Re: Goods Confirmation not transferred to backend!!
    Hope this will definitely help.
    Regards
    - Atul

  • Metadata EDISDEF not maintained  - Idoc adapter error

    hi,
    In our scenario, SenderParty->XI->R/3, we are using custom idoc to post into R/3. The idoc adapter throws an error, Metadata EDISDEF for port SAPXXX, IDoc type ZKAGXXX and CIM type not maintained, but when i use standard idoc, i don't get this error. We even applied oss note 837595 to fix authorization issue, but it didn't help.
    Any ideas or suggestions.
    Thanks
    Pandari

    One LAST suggestion.  Looking at Note 837595, it doesn't seem to specify a value for authorization group (DICBERCLS).  Try authorization group 'SS' (without quotes).  So:
    Object: S_TABU_DIS
    Activity: 03
    Auth. Group: SS
    I recall now that a customer recently had this issue and (for them), this helped.
    Jin

  • IDX2 Communication Error - Problem with only 1 IDoc Type

    Trying to import metadata via IDX2.  All IDoc types have imported succesfully, except DELVRY03. 
    I get a message saying "Communication Error" Message #: IDOC_METADATA407.
    I have tried DELVRY01 and it imports fine.  But, DELVRY02 and DELVRY03 both give the "Communication Error" messages.
    Any ideas why this one particular type will not import?  Settings/logon have not changed.
    Thanks

    FYI, Update... I think I may be on to something here...
    All checks in WE30 return okay.
    I debugged the IDX2 program, error is occuring in the 'IDOCTYPE_READ_COMPLETE' function call.  It is returning with message: 'Structure of segment E1EDD10 is unknown'.  Did search on this in OSS and found note #491264 -- Output of IDoc DELVRY02/DELVRY03 does not work
    Symptom
    You want to display IDoc DELVRYnn (nn = 02,03), SHPMNTnn (nn = 03,04,05), or PLNSHPnn (nn = 01) via the IDoc documentation transactions. The sys
    Comment: This relates only to the display of the IDOC structure. The IDocs work for the data exchange.
    Still working through the note to see if this will fix the issue, but I just tried to import in SHPMNT03 and I get the same error.
    Thanks.

  • Idoc segment for shpmnt notification for idoc type shpmnt02

    Hi gurus,
               I have to find the idoc segment for shipment notification,idoc  type which we are going to use is shpmnt02 or shpmnt01,Can any one of you please tell me the idoc segments for this idoc type with fields and table name?.Thanks in  advance.

    Hi Nagarathinam
    You can use transaction WE60 for documentation on IDOCs
    Best regards,
    Chris

  • Inbound Idoc type for posting Non-PO Invoice

    Hi,
    I am looking for an inbound Idoc type to post Non-PO Invoice.  The Idoc types INVOIC01 and INVOIC02 helps me to post the invoice with reference to PO.  But I am looking for the Idoc type to post the invoices without reference to PO i.e., For example to post the transaction FB60 (Enter vendor invoice without ref to purchase order).
    with regards,
    suresh

    Hello Deep,
    I know it might be quite late for you for this answer, nevertheless I will write that, because there are lots of question like yours. bapi_incominginvoice_park is also a suitable bapi for you. All you need to do is call it this way:
    data: headerdata like bapi_incinv_create_header value is initial,
            table_item type table of bapi_incinv_create_item,
            gl_account like bapi_incinv_create_gl_account,
            table_gl type table of bapi_incinv_create_gl_account.
    * fill headerdata and table_gl, leaving table_item empty
    CALL FUNCTION 'BAPI_INCOMINGINVOICE_PARK'
        EXPORTING
          HEADERDATA                = HEADERDATA
    *   ADDRESSDATA               =
        IMPORTING
          INVOICEDOCNUMBER          = lv_docnr
          FISCALYEAR                = lv_year
        TABLES
          ITEMDATA                  = table_item
    *      ACCOUNTINGDATA            = table_acc
          GLACCOUNTDATA             = table_gl
    *   MATERIALDATA              =
    *      TAXDATA                   = table_tax
    *   WITHTAXDATA               =
    *   VENDORITEMSPLITDATA       =
          RETURN                    = lt_return.
    This works perfectly for me, creating a mir7 document without refering to a PO. The trick here is to fulfill the glaccountingdata importing table while leaving itemdata empty.

  • Multiple message types for an idoc type

    Hi all,
    I created one custom idoc type with six segments. I heard that one idoc type can have any number of message types
    if it is so pls tell me how to assign these two message types for my idoc .
    i want to create multiple message types because i want to send same idoc type to diff legacy systems.
    My requirement is message type one is only for first three segments and message type two is for another three segments .
    The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
    how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?

    Hi Kunal,
    Below are my thoughts from a design perspective,
    My requirement is message type one is only for first three segments and message type two is for another three segments .
    The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
    Before you look upon the no. of message types you need, i guess you need to look at the business requirement. Per your requirement you want to send send two sub sets of data. The first subset in the first 3 segments and other three segments for the second subset of data.
    Is the structure of the first subset of data similar to the second subset If not, better to create two IDOC Types. If they are similar, then create one IDOC Type with three segments and have two message types for each subset of data.
    For Ex: ORDERS05 is the IDOC type for Orders, this IDOC type provides capability to carry data related to any type of orders
    but the action on the data is facilitated by the message type like ORDERS for create, ORDCHG for change, ORDRSP for Order response etc.
    OR
    Are these two subsets of data related to each other, if yes understand the relation? If not related at all then you might be better of creating two separate IDOC Types.
    Like in the above example A purchase order is related to a sales order so you can use the same IDOC type, but in case of a order response and ASN that data sent is different and hence you will need different IDOC types (even though a SO is related to a DN).
    how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?
    The above again depends on the how tightly/loosely coupled are the data sets, you can have just one program and have a simple case statement on the message types or have two different programs.
    You will also have to consider points like, if any of the subsets is more prone to more change in terms of the structure and associated business logic. If yes, then you might want to keep the programs separate to reduce work on regression testing etc.
    I am sure you will receive more inputs from the experts on the forum and the list of points to look for will get longer , so understand the requirement, dependencies and if you have any specific questions you could post it on the forum.
    Regards,
    Chen

  • Process codes for Idoc types

    Hi All,
    Can you please send me the process codes for the following IDOC types as I could not find them in WE64. Also let me know how did you found out.
    IDOC types are:
    1) INTERNAL_ORDER_CREATE01
    2) PROFITCENTER_CREATE01
    3) COSTCENTERGROUP_CREATE01
    Urgent help is really appreciated.
    Regards,
    Shahu

    Hi,
    1) INTERNAL_ORDER_CREATE01
               Please clarify for which order you are using this.
    2) PROFITCENTER_CREATE01 -
               PRCM (PRCMAS)
    3) COSTCENTERGROUP_CREATE01
               COSM (COSMAS)
    Reward points if useful.
    Regards,
    Atish

  • Create a sequencial serial number for different Idoc Types

    Hi,
    we've got a legacy system which requires a serial number in a flat file for different Idoc types.  The target filename for the three different Idoc types is exactly the same, lets say: InboundFile_nnnnn.xml (where nnnnn is the sequence number)
    In the header of the file we will specify what type of file it is according to the Idoc that was received, but regardless of the idoc type, the sequence numbers for all three idoc types must be sequential.  The files are placed on the target server using a receiver ftp adapter on the central adapter engine.
    I would like to know if there is any way to store\maintain this sequence number in XI and use it accross different message mappings?
    Your response is appreciated.
    Thanks
    Rudi
    (and a merry christmas to you all

    You can create a number range object in SNRO transaction abap stack in SAP XI and use that in the mapping by connecting through JCO in XI.RFC enable Number_Get_next.
    check this for more info
    /people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i

Maybe you are looking for