Application Development 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: 

Outbound PO Idoc DUMP

Former Member
0 Kudos

We are sending PO via Idocs.

Idoc is created and sent successfully to Biztalk. We get the acknowledgement back. All is working good.

However everytime Idoc is sent, Runtime Errors         RAISE_EXCEPTION is seen.

It dumps.

=====

Error analysis
    A RAISE statement in the program "SAPLARFC" raised the exception
    condition "ERROR".
    Since the exception was not intercepted by a superior
    program, processing was terminated.

    Short description of exception condition:


    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    -

=======

Termination occurred in the ABAP program "SAPLARFC" - in "START_DEST".
The main program was "SAPMSSY1 ".

In the source code you have the termination point in line 977
of the (Include) program "LARFCU06".

>>>>>         call function 'ARFC_DEST_SHIP'

  978         destination state-arfcdest

  979            exporting

  980                 comment               = rfcdoc-rfcdoc1

  981                 sender_id             = sender_id

  982            tables

  983                 state                 = state

  984                 data                  = data

  985            exceptions

  986                 system_failure        = 1 message mess

  987                 communication_failure = 2 message mess.

  988       endif.

==========

Although the Idoc transmission is not an issue and all business process are running smoothly.

The ST22 is stacking up which is ugly.

Any idea why this dump is and how do we resolve would be greatly appreciated.

Thanks

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

Check TCODE SM58 for any transactonal RFCs that could not be carried out successfully.

Check this link for details. Second topic :

Checking the Status of Transactional Calls

http://help.sap.com/saphelp_nw04//helpdata/en/22/042585488911d189490000e829fbbd/content.htm

6 REPLIES 6

Former Member
0 Kudos

Any pointers guys?

0 Kudos

Hi,

   J_4A_IDOC_INPUT_ORDRSP is  to prevent a short dump

Former Member
0 Kudos

Hi,

Check TCODE SM58 for any transactonal RFCs that could not be carried out successfully.

Check this link for details. Second topic :

Checking the Status of Transactional Calls

http://help.sap.com/saphelp_nw04//helpdata/en/22/042585488911d189490000e829fbbd/content.htm

0 Kudos

Hello Shambhu,

Thanks for the reply.

SM58 has a big list and the status is Executing.

Shall I go ahead and delete these entries?

There are around 50 odd entries. I hope deletion does not lead to any inconsistency or loss of data.

Thanks again    

0 Kudos

You can also Debug LUW to see what is wrong!

0 Kudos

Execute 'ARFC_DEST_SHIP' in se37 and check.

Priya.