Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Function module not allowed: BAPI_IDOC_INPUT1 (Message Type: INCIDENT)

Former Member
0 Likes
5,054

During inbound IDOC processing of message INCIDENT, I receive the following error message: ‘Function module not allowed: BAPI_IDOC_INPUT1’, the IDOC status is set to status: 51 and cannot be processed.

I have checked the following settings;
a) Logical message INCIDENT is assigned to Process Code BAPI
b) IDOC assignment of FM BAPI_IDOC_INPUT1 to logical message: INCIDENT , Basic Type: INCIDENT01 and Object Type: BUS1240 (defined direction: inbound).
c) Table: TBDBE, entry for message INCIDENT exist.
d) Transaction BDBG, all recorsd already exist.


Functional area: SAP EH&S - Industrial Hygiene and Safety

  • Table TBDBE
    Message Type:             INCIDENT
    Object Type:                 BUS1240
    Method:                       SAVEREPLICAMULTIPLE
    Basic Type:                  INCIDENT01
    Function module:          CBIH_IAALE_IDOC_INPUT_IALDATA
    In Update Task:            X
    acket Processing:        X
  • Transaction BDBG
    Object:                        BUS1240
    Method:                       SAVEREPLICAMULTIPLE
    Result:                        For all records: ‘already exist’

  • WE57 record
    Function module:          BAPI_IDOC_INPUT1
    Function type:              Function module
    Basic type:                  INCIDENT01
    Extension
    Message Type:            INCIDENT
    Message Variant: 
    Mess. Function:
    Object Type:                BUS1240
    Direction:                     INBOUND


Which settings am I missing or are incorrect?

Thank you in advance.
Kind regards, Roy

1 ACCEPTED SOLUTION
Read only

JackGraus
Active Contributor
0 Likes
2,505

Hi R.,

When looking at your settings and also to the SAP coding of BAPI_IDOC_INPUT1 this should work. The error message is given when an entry is missing in TBDBE for the message type.

Next to that also table TBDBA could be used. TBDBA is used both for outbound as inbound IDOC's where TBDBE is just used for inbound.

Next to that you could also try function BAPI_IDOC_INPUTP.

Are you using transaction WE19 or is the IDOC triggered by a maping tool ?

Also check the inbound partner profile. There is an inbound process code for this message. Guess the process code is BAPI. When you double click the process code you should end in function BAPI_IDOC_INPUT1.

Regards Jack

2 REPLIES 2
Read only

JackGraus
Active Contributor
0 Likes
2,506

Hi R.,

When looking at your settings and also to the SAP coding of BAPI_IDOC_INPUT1 this should work. The error message is given when an entry is missing in TBDBE for the message type.

Next to that also table TBDBA could be used. TBDBA is used both for outbound as inbound IDOC's where TBDBE is just used for inbound.

Next to that you could also try function BAPI_IDOC_INPUTP.

Are you using transaction WE19 or is the IDOC triggered by a maping tool ?

Also check the inbound partner profile. There is an inbound process code for this message. Guess the process code is BAPI. When you double click the process code you should end in function BAPI_IDOC_INPUT1.

Regards Jack

Read only

Former Member
0 Likes
2,505

Hi Jack,

Indeed, with function BAPI_IDOC_INPUTP I'm able to process the message.

Thanks,

Roy