Stuck Outbound Queues in CRM system

[Former Member]

Hi Guys,

In CRM system the out bound queuse for the Sales Orders got stuck with the following error "Too many recursive subroutine calls"

The Sales Orders are not getting replicated from the CRM system to R/3.

The business partners associated with the sales orders are getting replicated to the From CRM to the R/3 system.

anyone has clue regarding the issue.

[hongyan_shao · Accepted solution]

Hi,

Are there any short dump in st22 as

RPERF_TOO_MANY_CALLS?

what is the program it points to?

Hongyan

[Former Member · Accepted solution]

Hi,

There are no short dumps in the ST22 transaction.

It doesnt refer to any programs.

The corrresponding business partners got replicated but the sales orders got stuck without being replicated.

Thanks,

Vijay

[hongyan_shao · Accepted solution]

Hi Vijay,

Sorry, I run out of idea.

How about create a message to contact SAP support for this?

I believe a logon into the system and check is necessary.

Excuse me.

Hongyan

[Former Member · Accepted solution]

upon debuggin we found the follwoing nformation

In debugging the program it states the following:

Too many recursive subroutine calls.

What happened?

Error in ABAP application program.

The current ABAP program "SAPLCC01" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

What can you do?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

Error analysis

An ABAP/4 subroutine was called recursively too often.

This is probably due to a conversion exit or a user exit

triggering the same exit again and again.

These exits are implemented by function modules with the names

CONVERSION_EXIT_xxxxx_INPUT/OUTPUT or USER_EXIT_xxxxx_INPUT.

-

You can find out which ABAP/4 subroutine is affected in the

section "Active Calls / Events".

Conversion exits are triggered during screen field transports or

WRITE statements, field exits during field transports from the

screen to the ABAP/4 program, so they are not called directly by

an ABAP/4 program. Most likely, this is due to the implementation

of a conversion exit which contains a WRITE statement for a field

to which the same conversion exit is assigned in its Dictionary

domain. As A result, the exit is triggered

recursively.

You can make up to 50 ABAP/4 subroutine calls.

-

How to correct the error

Probably the only way to eliminate the error is to correct the program.

-

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-

---

"RPERF_TOO_MANY_CALLS" C

"SAPLCC01" or "LCC01U05"

"PCA_CHECK_LUHN_MOD_TEN"

-

---

If you cannot solve the problem yourself, please send the

following documents to SAP:

[hongyan_shao · Accepted solution]

Hi,

Yeah, that is the short dump I am interested in.

There are limitation on 50 subroutine calls in ABAP program.

There is chances that in your system, it exceeds this limitation.

In the short dump file you should be able to see the full list of the call stack, could under

Active Calls / Events

section.

Then you may judge whether any user exit programs are involved. If they are all related to SAP standard program, then we need to create a message and call help from SAP support.

Hongyan

[Former Member · Accepted solution]

Thanks hongyan shao.

We identified that an user exit regaridng credit card authorization which has been recently chnaged is causing the problem.

Thanks for your time.

The issue is closed .