Outbound FM For CLFMAS01 Idoc Type

Hi Frnds,
My Requirement is Need to send classtype 001 details to CRM from ECC..using CLFMAS01 Idoc Type.
but i am unable to find out the Outbound Function Module..Please help to find that one.
Thanks,
Laxmi

Hi ,
As per ECC6 , the above FM is exist and also maintained in BD51 and WE57 for same message type.
Just recheck the same. If the FM Exist in the system them you can configure the same in BD51 and WE57 .
Thanks
Subhankar

Similar Messages

  • Receiver determination doesn't work for same IDoc type but in differentSWCV

    hi guys,
    we have an emergency now. Receiver determination doesn't work for same IDoc type but in different SWCV.Please check below for detail.
    1. The process flow is : R/3 IDoc -> XI -> Third party system
    2. In previous release R13, IDoc ORDERS05 was imported and used in XI and software component version is R13. And receiver determination was created.
    3. Now, in new release R17, IDoc ORDERS05 was imported from R/3 to XI again and software component version is R17. And in R17, the receiver determination created in R13 was used for both old interface(R13) and new interface in R17.
    Then we encountered the problem, both interfaces doesn't work now, even we deleted the receiver condition(In R13, IDoc ORDERS05 was sent to system A, and in R17 IDoc ORDERS05 was sent to system B, RCVPRN was used as an condition).
    Does anyone encounter this problem? really need and appreciate your help.
    -Eddie

    information from monitor:
    Status     Sender               Service Sender Namespace                         Sender Interface
    reschedul  XXXCLNT100     urn:sap-com:document:sap:idoc:messages   ORDRSP.ORDERS05
    columns for "Receiver Service","Receiver Namespace", "Receiver Interface" are blank
    And then double click records in monitor, go into detail information...
    Normally there's lots of setps existed, such as
    Inbound Message ( CENTRAL )
    Receiver Identification
    Interface Determination
    Receiver Grouping
    Message Branch According to Receiver List
    Technical Routing
    Call Adapter
    But now there's only one setp -
    "Inbound Message ( CENTRAL )" existed, no any another setp..., and payload in inbound message looks good.
    And in SMQ2, I checked the queue information, found there's an error - "An exception occurred that was not caught." No any other detail information for this error.

  • The meta data for the IDoc type "LOIPRO01" is unavailable

    Hello,
    i'm trying to send idocs via rfc from SAP ERP ECC 6.0 to SAP MII 12.06, but we always get errors like:
    The meta data for the IDOC type LOIPRO01 is unavailable
    I've checked the parameters on MII side of the IDOC Listener:
    Servername  MII_JCI33 
    server Properties 
    gwhost H33-I0.rz.k-plus-s.net 
    gwserv sapgw02 
    progid MII_JCI33 
    trace 1 
    params   
    snc_myname   
    snc_qop   
    snc_lib   
    unicode 1 
    max_startup_delay   
    Client Properties 
    client 303 
    user RFC-I33 
    alias_user   
    passwd   
    lang en 
    sysnr 02 
    ashost h33-i0.rz.k-plus-s.net 
    mshost H33-I0.rz.k-plus-s.net 
    gwhost H33-I0.rz.k-plus-s.net 
    gwserv sapgw02 
    r3name H33 
    group   
    tpname MII_JCI33 
    tphost H33-I0.rz.k-plus-s.net 
    type 3 
    trace 1 
    codepage 1 
    There is no saprouter between ERP and MII as in the thread from Christoph Mertins in November 2008. The user rfc-i33 on the ERP has SAP_ALL permissions.
    Has anyone an idea ?
    Kind Regards,
    Thomas Strecker

    Thomas,
    There is a link for a basic IDoc installation that may help.
    [IDocListener|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/manufacturing/how%20to%20send%20an%20idoc%20from%20sap%20ecc%20to%20the%20sap%20mii%20idoc%20listener.pdf]
    One other issue that has occurred to cause problems is registering the program in Visual Administrator.  If you registered the ProgID in Visual Administrator, there will now be two ProgIDs registered (MII does self registration with the RFC Destination upon starting the server).  Delete the registration in VA, if you did it.
    If there are other error messages available, please post them.
    Good luck,
    Mike
    I also just remembered, if you have two ProgIDs that are the same, running on two separate MII instances, you may run into a problem.  Not sure it will have the same symptoms or error messages, but something else to check with (especially when migrating from dev to prod).
    Edited by: Michael Appleby on Feb 10, 2009 5:02 PM

  • 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

  • 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

  • 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

  • Find program for an IDOC type

    Hello Gurus,
    I need to identify what program or transaction does a Particular IDOC type is associated to.
    How do I find Program related to IDOC type?
    How many ways to find such link?
    Regards,
    Abhishek.

    Hello Gurus,
    My scenario is to find the easiest way to search for the Link between and IDOC type (Outbound idoc) to a program.
    I have list of all the IDOC type now I need to find from where these IDOC´s are triggering from?
    Regards,
    Abhishek...

  • How to find the outbound program for standard IDoc

    Hi Folks,
    Can anyone tell me how to find the outbound program/tcode for a standard IDoc? For e.g. IDoc - MATMAS05 can be generated & distributed using tcode BD10. Similarly how do I find the outbound program/tcode for any standard IDoc? Is there any procedure to find the same.
    I have tried to search based on the package name, but unfortunately I didn't find the information for IDoc: COND_A04.
    Thanks in advance.
    Somu

    You can do following steps if the idoc is generated based on change pointer concept (for masters)
    - Identify the message type associated with idoc type (table EDIMSG).
    - Function module for generating the IDOC will be available in table TBDME (pass message type as input).
    Refer to the standard Outbound IDOC generation program RBDMIDOC for more details.
    If the idoc is generated based on the process code concept (transaction data), get the process code information from table TMSG1 (pass message type as input), get the function module associated process code from table TEDE1 (pass process code as input).
    Regards, Vinod
    P.S: There is no standard way to find out the associated program / Tcode for generating idoc. The above process will be helpful to find out the underlying function modules to generate the idoc.  For generating idocs based on change pointers the generic program RBDMIDOC can be used.
    Edited by: Vinod Kumar on Jul 13, 2011 2:15 PM

  • Find Idoc extension type for Basic Idoc type

    Hi all,
    Is there any way to find existing extesions for Idoc given by SAP? For example, for basic idoc DEBMAS05 for version 4.7 , Idoc extension is DEBMASEXT.
    In similar way I want to know what is Idoc extension for Idoc basic type PREQCR02 [Create Purchase Requisition].
    Thanks in advance.
    Madhura

    The reason is preqcr02 is a generated idoc type  and matmas05 and debmas05 are not generated idoc types .
    You can search in table EDBAS for this .  If you go for dynamic debuggin , message comes from form
    create_ext_structure  in include MSED5F02 
    data: l_edbas type edbas.
      select single * from edbas into l_edbas
         where idoctyp eq edi_iapi01-idoctyp.
    if l_edbas-generated eq 'X'.
       message e099(b1) with
          'Action is not possible for generated idoctypes'.
    endif.
    Edited by: anil sasidharan on Feb 25, 2009 12:51 PM
    Edited by: anil sasidharan on Feb 25, 2009 12:59 PM

  • When do we ceate custom messagae type apart for custom idocs type

    Hi all.
        Can u pls let me know when do we create custom message type in ALE/IDOCS. what I know is we can create a custom message when we create custom idoc type & when we have reduced idoc type.Pls let me what are other cases in which I need to create a custom message type.Thanks in advance.
    Kind regards,
    sami.

    I think these are the only cases where we need to create. Its basically when we dont have standard SAP message type available.

  • Process code or Fmodule  for Idoc type PREQCR101 and message type PREQCR1

    hi all,
           Iam unable to find the process code or function module for the idoc type PREQCR101 and message type PREQCR1 for inbound process.
    help from some one would be a lot appretiated.

    Hi,
    Go to transaction WE57 and you can find the processing FM and message type that are associcated to the IDOC type.
    For process code if it is Inbound check WE42 and outbound check WE41 transactions
    Regards
    Shiva

  • Creation of  New Message Type for Extended IDoc

    Dear Friends,
    I want to create New Message Type for MATMAS and want to Active Change Pointers accordingly. Thru this Message Type how can I able to use Extended IDoc which I have created for Basic Idoc Type MATMAS05.
    I am Sending Data from SAP to XI ; Any one can help me in this How can I create the Message Type with the IDoc Extn .
    for Change Pointers.
    Warm Regards,
    Naveen Mutyapu.

    Hi naveen mutyapu,
    see these links
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    http://www.allinterview.com/rss/interview-questions/new/SAP-ALE-IDocs.xml
    happy learning.
    thanks
    karthik

  • IDOC type for network?

    Any ideas for the IDOC type for network? (CN21 , CN22 transaction)

    Hi,
    Please check IDoc type PROJECT01 with message type PROJECT perhaps it may help.
    Regards,
    Ferry Lianto

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

Maybe you are looking for