IDOC Error - Function module not allowed: IDOC_INPUT_HRMD

Hello Gurus,
I have an issue with the IDOC Transfer. I am using the program RSEINB00 to read the file and convert the data into IDOCs with status 64.
But all my Idocs are getting created with status 51 and the error is getting populated as " Function module not allowed: IDOC_INPUT_HRMD ".
Please do let me know whats needs to be done for this to be rectified.
Thanks,
Naveen.

You are not using the right process code.
In partner profile - in message type
u will see the process code to which a function module is attached,
for ur message type, this is not the right function module.
Regards
Manu

Similar Messages

  • ALE-IDOC Error -Function module not allowed: ZIDOC_INPUT_MATCLASS

    Hello all,
    I am having a requirement to enhace bd10  to suit for material master.For that i have written a Z-function module to at inbound side.
    Function module has coading for extended segments and z processing code is created for the same.
    The issue is that i am getting error-Function module not allowed: ZIDOC_INPUT_MATCLASS.Please help to resolve the issue.
    Thank you.

    I have checked as per your suggestion in detail the error reported as-
    Function module not allowed: ZIDOC_INPUT_MATCLASS
    Message no. B1252
    Diagnosis
    The function module ZIDOC_INPUT_MATCLASS and the application object type which were determined are not valid for this IDoc.
    Procedure
    1. Please check that the process code in the inbound partner profile is correct.
    2. If this is the case, you should check the ALE inbound methods ALE inbound methods for the process code and see whether the specified function module and application object type are correct.
    3. If this is also the case, then the function module and the application object type are not permitted for the logical message type, message variant, message function and basis type that are contained in the IDoc control record. You should check whether the correct values have been assigned to these fields in the control record. If they do have the correct values, then the assignment to the function module and the application object type needs to be maintained.
    I am done with all the procedure.
    I am currently using-BUS1001006.I really dont know if this is the one for extended idocs and z function module for material master.Please guide me if this is the issue. And i f so please guide right buziness object.
    Thanks.
    Edited by: sanjivrd on Sep 22, 2009 1:27 PM

  • ALE  error Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT.

    Hi Gurus,
    By ALE config I am trying to send material from one client to another  ( MATMAS )
    I have created two logical systems and assigned them to corresponding clients.
    Created a RFC destination and assigned logical systems.
    Created Distribution model in sending client.
    Created partner profile in both clients.
    Created Material and send to receiving system using BD10 tcode.
    I checked Idoc status in Sending system, Idoc status is 03-Data is passed to port OK, status 30-Idoc ready for dispatch and status 01- Idoc generated.
    But in receving system (Inbound Idoc)- I got status- 51-Application document not posted and Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT.
    I also checked partner profiles in both systmes- both r same.
    IAny help in this regard is appreciated.
    Thanks,
    Bluesh

    On receiver system...
    1 - goto WE20
    2 - locate the sender logical system (partner)
    3 - in Inbound grid select message type MATMAS (double click)
    4 - change "Process code" AFSA to MATM (probably AFSA is the actual code)
    5 - save and reprocess the IDocs using BD87
    Note: Process code AFSA is deafult but the scenarios need a spefic code that is MATM
    Best Regards,
    Josieudes Claudio
    Edited by: Josieudes de Sousa Cláudio on Jul 12, 2011 9:06 PM

  • Function module not allowed: RSAR_DATA_RECEIVED B1 252

    Hi Friends,
    I have a Data load problem when loading hierarchi data loads i.e. 0material,0prod_hier etc.
    I am getting the following error:
    Error when updating Idocs in Business Information Warehouse
    Diagnosis
    Errors have been reported in Business Information Warehouse during IDoc update:
    Function module not allowed: &
    System Response
    Some IDocs have error status.
    Procedure
    Check the IDocs in Business Information Warehouse . You do this using the extraction monitor.
    Error handling:
    How you resolve the errors depends on the error message you get.
    Under Error Analysis:
    Function module not allowed: RSAR_DATA_RECEIVED B1 252.
    We are getting this problem after refreshing the R/3 source system with production R/3 system.
    the loads went fine before the refresh.
    Data load is taking long time and finally getting failed without pulling any data into BW.
    Looking for valuable suggessions.
    Thanks in advance.
    Laxman

    Cannot load Hierarchies after refresh
    More information in SAP Note 216671.

  • IDOC error 51- Function module not allowed:

    Hi,
    I am getting following error in IDOC inbouond.I verifyed all parameters mentioned in error.
    Issue still not resolved.
    When debugged from WE19 this issue dosnt arise.
    Kindly guide.
    Function module not allowed: ZIDOC_INPUT_MATCLASS
    Message no. B1252
    Diagnosis
    The function module ZIDOC_INPUT_MATCLASS and the application object type BUS1001 which were determined are not valid for this IDoc.
    Procedure
    1. Please check that the process code in the inbound partner profile is correct.
    2. If this is the case, you should check the ALE inbound methods ALE inbound methods for the process code and see whether the specified function module and application object type are correct.
    3. If this is also the case, then the function module and the application object type are not permitted for the logical message type, message variant, message function and basis type that are contained in the IDoc control record. You should check whether the correct values have been assigned to these fields in the control record. If they do have the correct values, then the assignment to the function module and the application object type needs to be maintained.

    Hi,
    Check in WE42, for the process code, you have assigned this function module and given the correct process code in the partner profile.
    Sujay

  • Idoc error 51 - "Function module not allowed - APPL_IDOC_INPUT1'

    Hello everyone,
    We are uploading GL balances from legacy to SAP using the LSMW Bapi
    object - bus6035
    method - post
    message type - ACC_DOCUMENT
    Basic type - ACC_DOCUMENT03
    When we run the lsmw, idoc is created, however with an error 51 saying
    "Function module not allowed - APPL_IDOC_INPUT1'
    The partner no. is the logical system (the system on which the lsmw is executed)
    In the partner profile, we have defined this as LS. In the inbound parameters, we have defined message type = ACC_DOCUMENT, the process code is APL1 and the corresponding function module is - APPL_IDOC_INPUT1
    Please let me know if we are missing something or doing anything wrong ?
    Since the data in the LSMW will be read frmo a file on the presentation server, do we need to have a port configuration for the same ?
    Thanks,
    Sushil Joshi`

    Hello Sushil
    The long text of message B1(252) is quite informative for error analysis:
    NA B1252
    Short Text
         Function module not allowed: &
    Diagnosis
         The function module  and the application object type  which were
         determined are not valid for this IDoc.
    Procedure
         1.  Please check that the process code in the  inbound partner profile
             is correct.
         2.  If this is the case, you should check the ALE inbound methods ALE
             inbound methods for the process code and see whether the specified
             function module and application object type are correct.
         3.  If this is also the case, then the function module and the
             application object type are not permitted for the logical message
             type, message variant, message function and basis type that are
             contained in the IDoc control record. You should check whether the
             correct values have been assigned to these fields in the control
             record. If they do have the correct values, then the assignment to
             the function module and the application object type needs to be
             maintained.
    On ECC 6.0 this long text contains 3 transactions for analysis:
    - WE20
    - BD67
    - WE57
    Regards
      Uwe

  • "Function module not allowed" error message

    Hi,
    We created a special FM to be processed when the INVOIC is in inbound processing. We link the FM to the process code and the process code to the partner functions. We get the error message; "Function module not allowed: & name of our FM". However, when we reprocess the idoc via WE19, it goes through.
    Did somebody ever face that situation?
    Thanks
    Martin

    Hi
    is it for MRM  .  If it is ,I faced the same Problem Martin .go to EDIFCT table give ur basic type and execute and check for entries .if there no issue other wise goto we57 and maintain the entry for basic type .

  • Function module not allowed: IDOC_INPUT_INVOIC_MRM in 4.6C

    Hi All,
    I am working on SAP 4.6C, I am trying to post an idoc through WE19 and using message type INVOIC and basic type - INVOIC02. Also, we are using the process code - INVL which using the function IDOC_INPUT_INVOIC_MRM.
    While trying to post an MM Invoice after entering all the parameters in WE19, the IDoc in status 51.
    Also, the error message states that "Function module not allowed: IDOC_INPUT_INVOIC_MRM". Since it is a standard function module, I donu2019t know how to get to solve the problem.
    Thanks in advance.
    Regards,
    Nagarajan

    Hi Nagaraju ,
    Make Entries in WE57 . To make entries in this Take help of WE42-Inbound process code INVL .If u did not have the entries then it causes  this error .After logging ur entry Check in  table EDIFCT.
    Hope this helps .
    Rgds
    Sree . M

  • Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT.

    Dear Expert,
       I have a problem when I use ALE. I found error message of inbound in target system have a error status 51. Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT.
    message type is MATMAS. and i want to distribute Material master from 1 system to another system.
    Process code: AFSA
    This below is my config.
    Process code                         AFSA
    My process code Identification.
    Function module : AFS_RETAIL_ARTMAS_IDOC_INPUT
    Maximum number of repeats 0
    Object type                         IDOCARTMAS
    End event                           MASSINPUTFINISHED
    Object type                         IDOCARTMAS
    Start event                         INPUTERROROCCURRED
    End event                           INPUTFINISHED
    How to do this?
    thanks,
    Sak
    Edited by: Pongsak Ruangsongkhram on Dec 24, 2007 8:59 AM

    Pls make sure the following config in we42.
    Process code                         MATM                                                                               
    Function module                     IDOC_INPUT_MATMAS01 IDOC_INPUT_MA      
    Maximum number of repeats                                                                               
    Object type                         IDPKMATMAS                             
    End event                           MASSINPUTFINISHED                                                                               
    Object type                         IDOCMATMAS                             
    Start event                         INPUTERROROCCURRED                     
    End event                           INPUTFINISHED                                                                               
    Object type                         BUS1001                                
    Start event                                                                               
    Cheers!

  • FRM-41009 error - function key not allowed ?

    Folks,
    I don't know what object or item in my form is causing the "FRM-41009" error - "function key not allowed".
    I have a simple button which (when pressed) inserts records into a table, then does a commit. That insert statement is NOT the problem because an older version of my application does not give me this error.
    Does this mean that I have a trigger somewhere that's reacting on a COMMIT ??? Any ideas...sorry so vague on this one, but I can't pinpoint the problem.
    Thanks,
    Bob

    It's definitely my COMMIT statement that's causing the error in my form.
    When I do a simple Insert statment with the commit, it returns the error. Without the commit, there's no error (and of course no data in my table).
    Why does my commit work in a previously version of my form ?
    Bob

  • Error Function module " " not found in Smartforms

    Hi all,
    Please help me out….
    I created the form using the smartforms, check it and activated it. I can see the unique function module is assigned to the form. I wrote the ABAP program and use function module ‘SSF_FUNCTION_MODULE_NAME’and also define data types.
    when I called the function module fm_name for passing values and tables from program to smartform. This is working perfectly in development server but in production it giving error like Function module " " not found.
    Below I m pasting my code.
    *& Report  ZCASHJOURNAL                                                *
    REPORT  zcashjournal                            .
    TABLES: bseg.
    DATA: FM_NAME TYPE rs38l_fnam.
    DATA:BEGIN OF it_bseg OCCURS 0.
            INCLUDE STRUCTURE bseg.
    DATA:END OF it_bseg.
    DATA:BEGIN OF it_bseg1 OCCURS 0.
            INCLUDE STRUCTURE bseg.
    DATA:END OF it_bseg1.
    DATA: gv_amt_in_words TYPE spell,
          gv_word TYPE spell-word,
          gv_decword TYPE spell-decword.
    DATA:BEGIN OF gt_bkpf OCCURS 0.
            INCLUDE STRUCTURE bkpf.
    DATA:END OF gt_bkpf.
    DATA:bktxt TYPE bktxt.
    DATA:waers TYPE waers.
    DATA:belnr TYPE belnr_d.
    DATA:werks TYPE bukrs.
    DATA:desc  TYPE butxt.
    DATA:awkey TYPE awkey.
    DATA:docno TYPE matnr.
    DATA:cajo  TYPE awkey.
    DATA:desc1 TYPE butxt.
    DATA:dmbtr TYPE dmbtr.
    SELECTION-SCREEN BEGIN OF BLOCK b2.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT (15) FOR FIELD s_belnr.
    SELECTION-SCREEN POSITION 28 .
      PARAMETERS : s_belnr TYPE bseg-belnr .
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT (15) FOR FIELD s_werks.
        SELECTION-SCREEN POSITION 28 .
          PARAMETERS: s_werks TYPE werks.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN END OF BLOCK b2.
    SELECT * FROM bkpf
               INTO CORRESPONDING FIELDS OF TABLE gt_bkpf
              WHERE belnr LIKE s_belnr
              AND   bukrs LIKE s_werks.
    IF NOT gt_bkpf[] IS INITIAL.
      SELECT * FROM bseg
          INTO CORRESPONDING FIELDS OF TABLE it_bseg
          FOR ALL ENTRIES IN gt_bkpf
          WHERE bukrs EQ gt_bkpf-bukrs
          AND   belnr EQ gt_bkpf-belnr
          AND   shkzg EQ 'S'.
    ENDIF.
    LOOP AT gt_bkpf.
      bktxt = gt_bkpf-bktxt.
      waers = gt_bkpf-waers.
      belnr = gt_bkpf-belnr.
      werks = gt_bkpf-bukrs.
      awkey = gt_bkpf-awkey.
      docno = awkey+0(10).
      cajo = awkey+10(4).
    ENDLOOP.
    LOOP AT it_bseg.
      dmbtr = it_bseg-dmbtr.
    ENDLOOP.
    IF s_werks EQ '65'.
      desc = 'JCBML - Heavy Equipments'.
    ENDIF.
    IF cajo EQ '0001'.
      desc1 = 'PETTY CASH PLANT II'.
    ENDIF.
    CALL FUNCTION 'SPELL_AMOUNT'
      EXPORTING
        amount    = dmbtr
        currency  = waers
        filler    = space
        language  = sy-langu
      IMPORTING
        in_words  = gv_amt_in_words
      EXCEPTIONS
        not_found = 1
        too_large = 2
        OTHERS    = 3.
    IF sy-subrc EQ 0.
      MOVE : gv_amt_in_words-word TO gv_word,
             gv_amt_in_words-decword TO gv_decword.
    ENDIF.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
      EXPORTING
        formname                 = 'ZCASHRECPT'
    IMPORTING
       FM_NAME                  = FM_NAME
    EXCEPTIONS
       NO_FORM                  = 1
       NO_FUNCTION_MODULE       = 2
       OTHERS                   = 3
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    *CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
            EXPORTING  formname           = 'ZCASHRECPT'
                    variant            = ' '
                    direct_call        = ' '
            IMPORTING  fm_name            = lf_fm_name
            EXCEPTIONS no_form            = 1
                       no_function_module = 2.
    *v_vbeln = S_VBELN-low.
    CALL FUNCTION FM_NAME
      EXPORTING
        bktxt            = bktxt
        waers            = waers
        belnr            = belnr
        werks            = werks
        desc             = desc
        docno            = docno
        cajo             = cajo
        desc1            = desc1
        dmbtr            = dmbtr
        gv_word          = gv_word
      TABLES
        T_ZDEB           = it_bseg
      EXCEPTIONS
        formatting_error = 1
        internal_error   = 2
        send_error       = 3
        user_canceled    = 4
        OTHERS           = 5.
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.

    Hi Rakesh,
    Check two things
    1. Program tranpsorted to production without any error in request log.
    2. Smartform tranpsorted to production without any error in request log and without renaming / misspelling it.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING
    formname = 'ZCASHRECPT'
    IMPORTING
    FM_NAME = FM_NAME
    EXCEPTIONS
    NO_FORM = 1
    NO_FUNCTION_MODULE = 2
    OTHERS = 3
    IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Also try to uncomment the Message id part and it will show some meaningful message.
    And to check whether actaually fucntion module is generated or not goto smartforms ->Smartform name -> Display -> Environment->Fucntion module name . if this is blank try to retransport smartform.
    Hope that helps.
    Regards
    Kapadia
    ***Assigning points is the way to say thanks in SDN.***

  • Error "Function module  not found."

    Hi,
    I am calling RFC_GET_MATERIAL_DATA but I got this error "Function module "RFC_GET_MATERIAL_DATA" not found". What does it mean? How I can solve this error?
    Thank you in advance,
    Sunny

    Well I think it simply means that the Function Module does not exist in the system where it needs to get executed.
    First check if you are calling this FM remotely ( with a DESTINATION specification ). Then ensure that the FM exist in the DEST system (SE37).
    if you are not calling it remotely, then check if the FM exist in your local system.Just check in SE37.
    Reason it might not be available in the system is because of the version , or say product type ( R/3, CRM, EBP, BW... ).
    Thanks,
    Ram

  • ALE: Function module not allowed: IDOC_INPUT_MATMAS01

    Hi,
    I have extrended IDoc MATMAS05.It is passed on to recepient system. But not posted. I am getting this error. But using WE19 I am able to post. Any solution?
    Regards,
    Madhu

    Hi,
    Check whether the Partner profile name,port, logical system all of with the same name, when all are with the same i dont think you face such kind of problem also check the customization of MM01 in both the client r they same?(for example - Some fields may be mandatory in receiver but optional in sending).
    Regards:-
    <b>Santosh.D</b>
    P.S. Mark Usefull answers.

  • Error while creating Notification: Partner Function is Not Allowed in Partner Determination Profile Q2

    During Notification Creation I get the error --Partner Function is Not Allowed in Partner Determination Profile Q2
    As I enter Purchase Document Number in the transaction QM01 and press Enter. I get the above error and donot go further.
    Can anyone help me here.

    Hello Prashant,
    You are missing some configuration for the partner function;
    Go- to
    SPRO>IMG>QM>Quality Notifications>Notification Creation>Partners>Define partner Determination Procedure>
    Again Select "Define Partner Determination Procedure".
    Select Quality management> Change Partner
    Now Select Q2.
    Compare settings with Partner Determination Procedure on any other client. Also check Partner functions on the same screen.
    Amol.

  • Error 'Function module "IAOM_ACCOUNT_MANAGER" not found' in RPM_FIN02.

    Hi,
    When I am trying to run report RPM_FIN02 in ERP system, I am getting error ''Function module "IAOM_ACCOUNT_MANAGER" not found'.
    Please note i have done required configration in both systems i.e. cProject and ERP.
    Can somebody help me on this?
    Regards,
    Manoj

    Thanks for your input.
    This note is already implemented in our system.
    Anyway my problem is solved.The problem was in our configration.
    Regards,
    Manoj

Maybe you are looking for

  • New Phone

    My husband used my iCloud account before I had an iPhone. Now that I have one, I am still finding information from when my husband used the account. I try to backup my iCloud account and it says I do not have enough space, but I know I still 3.9GB le

  • Cisco E4200 and VPN and Vontage Phone service.

     I have a E4200 Router. I would like to  subscribe to a VPN service and possiby flash the router with DD-WRT so I can take advantge of of the VPN across my network and allow my various clents ( Roku, Boxee Box, etc ) to have access to the VPN.  My qu

  • How to reset USB port after too much power draw message

    Hi everyone, I have the brand new MBA which I use for work and I tried connecting a USB hub yesterday to it.  Once I did the computer immediately shut itself off and after doing some HW troubleshooting for a bit, I unplugged, got back running and saw

  • AP_INVOICE_DISTRIBUTIONS_ALL.LAST_UPDATE_DATE was not updated

    Hi, I would like to raise one question on AP_INVOICE_DISTRIBUTIONS_ALL.LAST_UPDATE_DATE of EBS 11.5.10 which is related to OBI Application 7.9.6.1 One customer mentioned that AP_INVOICE_DISTRIBUTIONS_ALL.LAST_UPDATE_DATE was not updated whenever AP_I

  • I am not able to download new nor update old apps

    How can this be fixed?