Function module not genrating a output when executing

Hello
I am using this function module to calculate the difference between the number of days using factory calendar. The function module is working fine but it is not giving the output. It is not generating the result. here is the code for the function module
please can you check and let me know what can be the reason
DATA:
    DURATION_F       TYPE F.
IF START_DATE IS INITIAL
AND END_DATE IS INITIAL.
    MESSAGE E032 RAISING PARAMETERS_NOT_VALID.
Bitte geben Sie ein gültiges Start- und Enddatum an
ENDIF.
IF FLG_UNITS IS INITIAL.
    PERFORM TIME_UNITS.
    FLG_UNITS = 'X'.
ENDIF.
IF UNIT = SPACE.
    UNIT = UNIT_DAY.
ENDIF.
PERFORM DURATION_COMPUTE
     USING
          START_DATE
          START_TIME
          END_DATE
          END_TIME
          FACTORY_CALENDAR
          UNIT
     CHANGING
          DURATION_F
          START_DATE
          END_DATE
          START_TIME
          END_TIME.
DURATION = DURATION_F.
ENDFUNCTION.

when calling the function module get the duration field as output
write that output on the list

Similar Messages

Smartforms.. Function Module not found.. fm_name when tried in the SE38

Hi all,
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 declared the data types, but when I called the function module fm_name, the system is saying that fm does not exits..My program looks like this in short:
data fm_name type rs38l_fnam.
parameter: p_form   type tdsfname   default 'zashok01'.
where Zashok01 is the form name.
print data
call function 'SSF_FUNCTION_MODULE_NAME'
       exporting formname           = p_form
                variant            = ' '
                direct_call        = ' '
       importing fm_name            = fm_name
       exceptions no_form            = 1
                  no_function_module = 2
                  others             = 3.
now after this, when I am calling the function module fm_name to get the generated FM for the form, the system gives a note that FM does not exits..
Can anyone find me the result.. Do I need to create a new FM or what??? or is there anything wrong with my codes to assign the name of FM.
Waiting for your replies..
Regards,
   -Ashok Hansraj

hi,
correct the following things
1. parameter: p_form type tdsfname default 'ZASHOK01'.
2. check fm name in Smartform - > Environment - > function module name
3. copy name of the function module and call from the program like
CALL FUNCTION '/1BCDWB/SF00000003'
IMPORTING
DOCUMENT_OUTPUT_INFO       =
JOB_OUTPUT_INFO            =
JOB_OUTPUT_OPTIONS         =
then replace '/1BCDWB/SF00000003' to fm_name like below
CALL FUNCTION fm_name
IMPORTING
DOCUMENT_OUTPUT_INFO       =
JOB_OUTPUT_INFO            =
JOB_OUTPUT_OPTIONS         =
cheers,
sasi

Function module not working

Hi All,
I have created a function module it is working fine by executing it self,when I am calling it into any program it is not working it means it is not fetching data from table I passed correct parameters I don't know what was the problem any one can help me in this.
Thanks&regds,
Sree.

There is no leading zeros here I am giving my funtion module code.
*function zmm_vendor.
""Local Interface:
*" IMPORTING
*"     REFERENCE(P_VENDOR) TYPE LFA1-LIFNR
*" TABLES
*"      P_VENDOR_DATA STRUCTURE ZVENDOR_DATA
tables : lfa1,lfm1.
data flag(1) type c.
types : begin of ty_lfm1,
        lifnr like lfm1-lifnr,
        "ekorg LIKE lfm1-ekorg,
        "erdat LIKE lfm1-erdat,
        ernam like lfm1-ernam,
        lfabc like lfm1-lfabc,
        waers like lfm1-waers,
        minbw like lfm1-minbw,
        webre like lfm1-webre,
        kalsk like lfm1-kalsk,
        ekgrp like lfm1-ekgrp,
        lipre like lfm1-lipre,
        end of ty_lfm1.
types : begin of ty_lfa1,
        lifnr like lfa1-lifnr,
        name1 like lfa1-name1,
        ort01 like lfa1-ort01,
        ort02 like lfa1-ort02,
        adrnr like lfa1-adrnr,
        end of ty_lfa1.
types : begin of ty_adr6,
        addrnumber like adr6-addrnumber,
        smtp_addr like adr6-smtp_addr,
        end of ty_adr6.
types : begin of ty_lfb1,
        akont like lfb1-akont,
        zwels like lfb1-zwels,
        zterm like lfb1-zterm,
        fdgrv like lfb1-fdgrv,
        reprf like lfb1-reprf,
         end of ty_lfb1.
types : begin of ty_display,
        sel,
        lifnr like lfm1-lifnr,
        ekorg like lfm1-ekorg,
        erdat like lfm1-erdat,
        ernam like lfm1-ernam,
        lfabc like lfm1-lfabc,
        smtp_addr like adr6-smtp_addr,
        waers like lfm1-waers,
        minbw like lfm1-minbw,
        webre like lfm1-webre,
        kalsk like lfm1-kalsk,
        ekgrp like lfm1-ekgrp,
        lipre like lfm1-lipre,
        name1 like lfa1-name1,
        ort01 like lfa1-ort01,
        ort02 like lfa1-ort02,
        akont like lfb1-akont,
        zwels like lfb1-zwels,
        zterm like lfb1-zterm,
        fdgrv like lfb1-fdgrv,
        reprf like lfb1-reprf,
        end of ty_display.
         INTERNAL TABLES DECLARATION
data: t_lfm1 type standard table of ty_lfm1 with header line,
      t_lfa1 type standard table of ty_lfa1 with header line,
      t_display type standard table of ty_display with header line,
       t_lfb1 type standard table of ty_lfb1 with header line,
       t_adr6 type standard table of ty_adr6 with header line.
         WORK AREAS DECLARATION
data: wa_lfm1 type ty_lfm1,
      wa_lfa1 type ty_lfa1,
      wa_adr6 type ty_adr6,
      wa_lfb1 type ty_lfb1,
      wa_display type ty_display.
select lifnr
         ekorg
         erdat
         ernam
         lfabc
         waers
         minbw
         webre
         kalsk
         ekgrp
         lipre from lfm1
         into corresponding fields of table t_lfm1
         where lifnr = p_vendor.
    if t_lfm1[] is not initial.
select lifnr
         name1
         ort01
         ort02
         adrnr from lfa1
         into corresponding fields of table t_lfa1
         for all entries in t_lfm1
         where lifnr = t_lfm1-lifnr.
     endif.
    if t_lfm1[] is not initial.
    select addrnumber smtp_addr from adr6
           into table t_adr6
           for all entries in t_lfa1
           where addrnumber = t_lfa1-adrnr.
      endif.
      if t_lfm1[] is not initial.
    select akont
           zwels
           zterm
           fdgrv
           reprf from lfb1
           into table t_lfb1
           for all entries in t_lfm1
           where lifnr = t_lfm1-lifnr.
      endif.
loop at t_lfm1 into wa_lfm1.
    move wa_lfm1-lifnr to t_display-lifnr.
     "move   wa_lfm1-ekorg to wa_display-ekorg.
    " move   wa_lfm1-erdat to wa_display-erdat.
     move   wa_lfm1-lfabc to t_display-lfabc.
     move   wa_lfm1-waers to t_display-waers.
     move   wa_lfm1-minbw to t_display-minbw.
     move   wa_lfm1-webre to t_display-webre.
     move   wa_lfm1-kalsk to t_display-kalsk.
     move   wa_lfm1-ekgrp to t_display-ekgrp.
     move   wa_lfm1-lipre to t_display-lipre.
     "append wa_display to t_display.
read table t_lfa1 into wa_lfa1 index 1 .
if sy-subrc = 0.
    move wa_lfa1-name1 to t_display-name1.
    move wa_lfa1-ort01 to t_display-ort01.
    move wa_lfa1-ort02 to t_display-ort02.
   endif.
read table t_adr6 into wa_adr6 index 1 .
if sy-subrc = 0.
    move wa_adr6-smtp_addr to t_display-smtp_addr.
endif.
read table t_lfb1 into wa_lfb1 index 1 .
if sy-subrc = 0.
    move wa_lfb1-akont to t_display-akont.
    move wa_lfb1-zwels to t_display-zwels.
    move wa_lfb1-zterm to t_display-zterm.
    move wa_lfb1-fdgrv to t_display-fdgrv.
    move wa_lfb1-reprf to t_display-reprf.
endif.
append   t_display.
exit.
"clear wa_display.
"clear t_display.
endloop.
delete adjacent duplicates from t_display comparing lifnr.
     move t_display-lifnr to p_vendor_data-lifnr.
     "move   t_display-ekorg to P_VENDOR_DATA-ekorg.
    " move   t_display-erdat to P_VENDOR_DATA-erdat.
     move   t_display-lfabc to p_vendor_data-lfabc.
     move   t_display-waers to p_vendor_data-waers.
     move   t_display-minbw to p_vendor_data-minbw.
     move   t_display-webre to p_vendor_data-webre.
     move   t_display-kalsk to p_vendor_data-kalsk.
     move   t_display-ekgrp to p_vendor_data-ekgrp.
     move   t_display-lipre to p_vendor_data-lipre.
     move   t_display-name1 to p_vendor_data-name1.
     move   t_display-ort01 to p_vendor_data-ort01.
     move   t_display-ort02 to p_vendor_data-ort02.
     move   t_display-smtp_addr to p_vendor_data-smtp_addr.
     move   t_display-akont to p_vendor_data-akont.
     move   t_display-zwels to p_vendor_data-zwels.
     move   t_display-zterm to p_vendor_data-zterm.
     move   t_display-fdgrv to p_vendor_data-fdgrv.
     move   t_display-reprf to p_vendor_data-reprf.
     append p_vendor_data.
endfunction.*
but after calling this into my program it is not working here is my program.
report ZTEST.
parameters : zvendor like lfm1-lifnr.
data : begin of ty_display occurs 0,
       lifnr like lfm1-lifnr,
       ekorg like lfm1-ekorg,
       erdat like lfm1-erdat,
       ernam like lfm1-ernam,
       lfabc like lfm1-lfabc,
       smtp_addr like adr6-smtp_addr,
waers like lfm1-waers,
       minbw like lfm1-minbw,
       webre like lfm1-webre,
       kalsk like lfm1-kalsk,
       ekgrp like lfm1-ekgrp,
       lipre like lfm1-lipre,
       name1 like lfa1-name1,
       ort01 like lfa1-ort01,
       ort02 like lfa1-ort02,
       akont like lfb1-akont,
      zwels like lfb1-zwels,
      zterm like lfb1-zterm,
      fdgrv like lfb1-fdgrv,
      reprf like lfb1-reprf,
      end of ty_display.
CALL FUNCTION 'ZMM_VENDOR'
EXPORTING
p_vendor            = zvendor
tables
p_vendor_data       = ty_display
loop at ty_display.
write : / ty_display-ort01.
endloop.
Thanks and Regds,
Sree.

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 .

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_NAMEand 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.***

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

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!

SMQ2 SYSFAIL - Function Module not found

Hi All,
When i am trying to push data to cdb i got sysfail - Function module not found error in the smq2. But data inserted in the cdb, the probelm we found was the data object having the dependency cause this error.
The data was there in the cdb, but no distribution entries found.
Please help me to resolve the same.
Regards,
Ramkumar

Hi,
Clear the queue first (delete it), then implement the NOTE 1552255 - 'Parallel load problem for partial association shadow'. Run the report mentioned in the NOTE and do a delta generation.
Then on doin a delta load the queues should run successfully.
regards,
Anil

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.

Function Module not working for old Role

Dears
Function Module not working for old Role
Function Module: /VIRSA/BAPI_AE_USERS_FOR_ROLES
Before EHP4 upgrade this functional module working fine, but after updated users are not visible.
We have chekced if the users are assigned directly users are visible but indirect (Position Based) assignment users are not apprearing.
Pl check the fucntion module with given roles below and identify the root cause,
EP_TRVL_ALL_CAB - Old Role
EP_TRN_TRVL_DRGC_V2 - New Role
Regards
Krishna Mohan CH
9704500717

Krishna,
I do not think this BAPI is meant to be called by anyone but the application using it, and its functionality may therefore change without notice.
What are you trying to achieve? Maybe there's a better way to do that...
Frank.

MRP_ATP_PUB.Call_ATP api not retrieving requested_date_quantity value when executed in custom schema but when executed in apps its working fine, can anyone help on this..

The MRP_ATP_PUB.Call_ATP api not retrieving requested_date_quantity value when executed in custom schema but when executed in apps its working fine, can anyone help on this..
We are passing the required values to the ATP API.
1) The x_return_status is showing as 'S' i.e. success but x_atp_rec.Requested_Date_Quantity is not returning any value.
2) If there is a grant issue how to identify it.
Regards,
Vinod Annukaran

Pl do not post duplicates -0 MRP_ATP_PUB.Call_ATP api not retrieving requested_date_quantity value when executed in custom schema but when executed in apps its working fine, can anyone help on this..

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

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

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 genrating a output when executing

Similar Messages

Maybe you are looking for