IDOC ABAP-PI Port Function Module not called

HI all,
i am using a scenario where i am sending (outbound) idocs via abap proxy to PI.
I have assigned the function module to the abap-pi port.
when i am trying to send a test idoc via we19, i get the message "IDoc '0000000000198029' transferred to ABAP-PSS port".
but the function module (a copy of own_function) doesn't get called. if i am testing the function module from se80 with the above mentioned idoc number '0000000000198029' everything is fine.
in the partner profile i have added the corresponding idoc message type and selected to send idocs immediately. have i forgotten something in order to trigger the call of the function module ?
br,
martin

Hello,
I think it is not so easy to send IDoc to XI with ABAP-PSS-Port.
I would try to create the IDoc and send it to XI-Port (Transactional RFC).
This is SAP-Standard for IDoc-Scenario (SAP-R3 to XI).
Best Regards, Dirk

Similar Messages

Program making a RFC call to Function Module not working in background

Hi All,
I have an ABAP Program which is used to do a reconciliation check between the R/3 and BI system for Invoice Data. Please find below the details of the program flow:
1.     Program counts the number of records in the DSO table and aggregates the Net_Value based on the date range (passed as parameters)
2.     Program calls a Function Module (RFC Call) which counts the number of records in the R/3 table and aggregates the Net_Value for the same date range
3.     Function Module Passes back the count values and aggregated Net_Value to the program
4.     Program compares the count and aggregated Net_Value from EDWH and MSP systems and sends an email mentioning whether the counts match or not
However we are facing an issue.
Whenever, we execute the program in dialog mode, it works fine and fetches results within 5-6 minutes. However if we schedule the program to run in background (parameters through a variant), it gives no results even after running for over 3-4 hours. We tried figuring it out yesterday but could not come to any conclusion. Since there is a RFC call being to the function module, we were wondering if we need to specify some other parameter as well.
Thanks & Regards
Dharmendra

RFC Call is a procedure for executing remote enables function modules. It is done via the 'Remote Enabled' radio button on the function module's attribute screen.

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

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

Status : 51- Incorrect function module IDOC_INPUT_MATMAS01 called up

Hello,
File - IDOC
in MONI, checkered flag is shown up and when I go the R3 server, WE05, I get error message
Status : 51
Incorrect function module IDOC_INPUT_MATMAS01 called up
I am using MATMAS04 without extension and updated the same in WE57. also checked in WE42 (MATM)
now, how do I proceed furthur related the above error message?
Regards,
Nikhil.

can very much
check your partner profiles PROPERLY. If u have the same IDoc type in 2 different partner profiles, check the 2nd one for it's process code. Isn't it the one, which is called after your Idoc is received? Processing code in partner profile is not based only on Idoc Type, but also on Message Type, Message Code and Extension. If the 2nd profile contains the process code, which is called, then check your incoming idoc for header values. May be this is causing your problem.
Peter

ABAP Object or function module?

Hello all!
I have to create a reusable routine. This routine should be select data from Z table for to get data with a parameter ID. I will pass a ID and expect result a internal table with some parameter values.
So, my question is: What i use for to do that? ABAP Object or function module?
I think that so easy to use function module. Why i should to use ABAP objects? What is positive points in use object and not function module?
For me, both do the same thing... i don't see any difference. Just object is more complicated.
Please, tell me why should i use object??
Edited by: Rodrigo Kenji Matsunaga on Dec 10, 2009 5:51 PM

I would go with Class.
Read through this discussion:
Needing Evidence on the Advantages of ABAP OO
Class would provide you a flexibility of inheritance. E.g. if you want to use the same data selection with little modification in your other applications, you can inherit some other class form this class. Redefine the method, call the Super's method and change the output before sending back to the caller.
Regards,
Naimesh Patel

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

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

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

ABAP Program or Function Module to activate infospoke/openhub table

Hi,
Post migration to production, when i am trying to load the data in open hub table, its showing OH table is not active. i had tried to all aspect but i am unable to load the data.
is there any ABAP Program or Function Module to activate infospoke/openhub table
Thanks & Regards,
Pankaj Bansal

Hello Pankaj,
Please check whether you have access to TCode SE14 . If Yes , You can use this TCode to activate the Tables.
There are lot of Posts talk about the procedure for activation through SE14. please refer the same
Thanks & regards,
Prasath

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: 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 ABAP-PI Port Function Module not called

Similar Messages

Maybe you are looking for