Check if A/R summary has exceeded time limit:exceeded by days/hours 42 14 ?

When I place an sale order with VA01, there is a warnning:
Check if A/R summary has exceeded time limit:exceeded by days/hours 42 14
What does it mean?

Hi
Check wheather you have done credit management or not. So check in OVA8 wheather you have maintained data or not. Also check in FD32 wheather you have maintained A/R summary for that customer.or not .
Regards
Srinath

Similar Messages

PI 7.0: IDOCs struck in IDX5 with error "Time Limit Exceeded".

Hi All,
We have a File to IDOC scenario in PI 7.0. After mapping the IDOCs are posted from PI to ECC System.
On a normal day this interface works good, yesterday we received a huge file which resulted in the creation of about 25000 IDOCs from one single file. The mapping went fine, however the IDOCs created were not posted into ECC System. When we monitor the IDOCs using transaction code IDX5 in PI system, we found the error message as "Time limit exceeded", the user shown was "PIAFUSER". To overcome this error, we increased the time limit of PIAFUSER from default to about 1500 seconds.
Now, I want to push these IDOCs from PI into ECC System. Could you please let us know, how to push these IDOCs sitting in PI system to ECC?
We do not want to reprocess the file from the beginning. Please let us know if it is possible to push the IDOCs without processing the file? If yes, how to reprocess?
Thanks in advance.
Regards,
Manohar Dubbaka.

Hi,
the help documentation is as follows:
Check the tRFC Status
Use
tRFC calls which transfer IDocs use the function module IDOC_INBOUND_ASYNCHRONOUS at reception (before release 4.0: INBOUND_IDOC_PROCESS).
If an IDoc in the sending system has been passed to tRFC (IDoc status "03"), but has not yet been input in the receiving system, this means that the tRFC call has not yet been executed.
Activities
To check the status of the tRFC calls, choose Tools ® IDoc Interface/ALE ® Administration ® Monitoring ® Troubleshooting ® RFC Queue (SM58) and specify any additional selection criteria.
The program RSARFCEX restarts unsuccessful tRFC calls.
You cannot choose the option is being executed in background processing.
Best Regards,
Erik Hubers

Program terminated: Time limit exceeded, ABAP performance, max_wprun_time

Hi,
I am running an ABAP program, and I get the following short dump:
Time limit exceeded. The program has exceeded the maximum permitted runtime and has therefore been terminated. After a certain time, the program terminates to free the work processfor other users who are waiting. This is to stop work processes being blocked for too long by
- Endless loops (DO, WHILE, ...),
- Database acceses with large result sets,
- Database accesses without an apporpriate index (full table scan)
- database accesses producing an excessively large result set,
The maximum runtime of a program is set by the profile parameter "rdisp/max_wprun_time". The current setting is 10000 seconds. After this, the system gives the program a second chance. During the first half (>= 10000 seconds), a call that is blocking the work process (such as a long-running SQLstatement) can occur. While the statement is being processed, the database layer will not allow it to be interrupted. However, to stop the program terminating immediately after the statement has been successfully processed, the system gives it another 10000 seconds. Hence the maximum runtime of a program is at least twice the value of the system profile parameter "rdisp/max_wprun_time".
Last error logged in SAP kernel
Component............ "NI (network interface)"
Place................ "SAP-Dispatcher ok1a11cs_P06_00 on host ok1a11e0"
Version.............. 34
Error code........... "-6"
Error text........... "connection to partner broken"
Description.......... "NiPRead"
System call.......... "recv"
Module............... "niuxi.c"
Line................. 1186
Long-running programs should be started as background jobs. If this is not possible, you can increase the value of the system profile parameter "rdisp/max_wprun_time".
Program cannot be started as a background job. We have now identified two options to solve the problem:
- Increase the value of the system profile parameter "rdisp/max_wprun_time"
- Improve the performance of the following SELECT statement in the program:
SELECT ps_psp_pnr ebeln ebelp zekkn sakto FROM ekkn
INTO CORRESPONDING FIELDS OF TABLE i_ekkn
FOR ALL ENTRIES IN p_lt_proj
WHERE ps_psp_pnr = p_lt_proj-pspnr
AND ps_psp_pnr > 0.
In EKKN we have 200 000 entries.
Is there any other options we could try?
Regards,
Jarmo

Thanks for your help, this problem seems to be quite challenging...
In EKKN we have 200 000 entries. 199 999 entries have value of 00000000 in column ps_psp_pnr, and only one has a value which identifies a WBS element.
I believe the problem is that there isn't any WBS element in PRPS which has the value of 00000000. I guess that is the reason why EKKN is read sequantially.
I also tried this one, but it doesn't help at all. Before the SELECT statement is executed, there are 594 entries in internal table p_lt_proj_sel:
DATA p_lt_proj_sel LIKE p_lt_proj OCCURS 0 WITH HEADER LINE.
p_lt_proj_sel[] = p_lt_proj[].
DELETE p_lt_proj_sel WHERE pspnr = 0.
SORT p_lt_proj_sel by pspnr.
SELECT ps_psp_pnr ebeln ebelp zekkn sakto FROM ekkn
INTO CORRESPONDING FIELDS OF TABLE i_ekkn
FOR ALL ENTRIES IN p_lt_proj_sel
WHERE ps_psp_pnr = p_lt_proj_sel-pspnr.
I also checked that the index P in EKKN is active.
Can I somehow force the optimizer to use the index?
Regards,
Jarmo

TRFC Time limit exceeded issue

We have issue about the TFC time limit exceeded. We have a third partner application which will call a HTTP service to our SAP, let's call the HTTP service as Z_submit_request, in Z_submit_request, we call RFC Z_process_request in IN BACKGROUND TASK, but we received a Time limit exceeded issue in SM58. Could anyone help to answer why we get this issue?
Thanks a lot!

RFC's are executed in dialog tasks, which have an upper limit for the allowed runtime. This can be set for profile parameter rdisp/max_wprun_time. You might want to check the profile parameter (or ask the basis folks) if it has the default value (or another reasonable value). Most likely though I'd say you should look into the actual RFC and see if you can improve the performance of Z_PROCESS_REQUEST, so that the timeout doesn't occur.

Short dump "Time limit exceeded" when searching for Business Transactions

Hello Experts,
We migrated from SAP CRM 5.2 to SAP CRM 7.0. After migration, our business transaction search (quotation, sales order, service order, contract etc) ends with the short dump "Time limit exceeded" in class CL_CRM_REPORT_ACC_DYNAMIC, method DATABASE_ACCESS. The select query is triggered from line 5 of this method.
Number of Records:
CRMD_ORDERADM_H: 5,115,675
CRMD_ORDER_INDEX: 74,615,914
We have done these so far, but the performance is still either poor or times out.
1. DB team checked the ORACLE parameters and confirmed they are fine. They also checked the health of indices in table CRMD_ORDER_INDEX and indices are healthy
2. Created additional indices on CRMD_ORDERADM_H and CRMD_ORDER_INDEX. After the creation of indices, some of the searches(without any criteria) work. But it takes more than a minute to fetch 1 or 2 records
3. An ST05 trace confirmed that the selection on CRMD_ORDER_INDEX takes the most time. It takes about 103 seconds to fetch 2 records (max hits + 1)
4. If we specify search parameters, say for example a date or status, then again we get a short dump with the message "Time limit exceeded".
5. Observed that only if a matching index is available for the WHERE clause, the results are returned (albeit slowly). In the absence of an index, we get the dump.
6. Searched for notes and there are no notes that could help us.
Any idea what is causing this issue and what we can do to resolve this?
Regards,
Bala

Hi Michael,
Thanks. Yes we considered the note 1527039. None of the three scenarios mentioned in the note helped us. But we ran CRM_INDEX_REBUILD to check if the table CRMD_ORDER_INDEX had a problem. That did not help us either.
The business users told us that they mostly search using the date fields or Object ID. We did not have any problem with search by Object ID. So we created additional indices to support search using the date fields.
Regards,
Bala

Time limit exceeded error

Hello All,
I am trying to execute a custom program with a variant, but I receive the Time limit exceeded error [TIME_OUT].
I am now trying to analyse why this error has occurred as I am a beginner. Any help shall be greatly appreciated.
Regards,
Arpita.
Moderator message: Welcome to SCN!
Moderator message: Please Read before Posting in the Performance and Tuning Forum
Edited by: Thomas Zloch on Oct 20, 2011 2:01 PM

Hi Ramya,
Your prog running in the back ground, so the time limit of the prog is exceded. Go to sm37 see the prog running time if exceded correct the time.
Regards
Srinu

Time Limit exceeded error in R & R queue

Hi,
We are getting Time limit exceeded error in the R & R queue when we try to extract the data for a site.
The error is happening with the message SALESDOCGEN_O_W. It is observed that whenever, the timelimit error is encountered, the possible solution is to run the job in the background. But in this case, is there any possibility to run the particular subscription for sales document in the background.
Any pointers on this would be of great help.
Thanks in advance,
Regards,
Rasmi.

Hi Rasmi
I suppose that the usual answer would be to increase the timeout for the R&R queue.
We have increased the timeout on ours to 60 mins and that takes care of just about everything.
The other thing to check would be the volume of data that is going to each site for SALESDOCGEN_O_W. These are pretty big BDOCs and the sales force will not thank you for huge contranns time
If you have a subscription for sales documents by business patrner, then it is worth seeing if the business partner subscription could be made more intelligent to fit your needs
Regards
James

Time Limit exceeded error in ALV report

I am gettting error "Time Limit Exceeded" when i execute ALV report. Can i run the program in background and how to do that?. I had already optimized my query in the program but even then i am facing the same issue.

You can process the alv in background by pressing F9...I guess that the output would be available as a spool in SP01.
You may need to re-check your query...And also, review the alv catalog and any events you are using....
Greetings,
Blag.

Time Limit Exceeded in File - java- IDOC

Hello,
I have an interface which reads a text file in XI and uses a java mapping to produce IDOCs in an R3 system synchronously, the interface was running fine for more than 2 years . Since the text file is larger than 20 MB, we are splitting into small text files (2mb each) for easier processing. While processing, each file will hold the outbound queue (SMQ2) until it gets completed. after 2 years of using this interface, it started giving errors in the queue (Time Limit Exceeded) for files larger than 1mb.
Any hint ??

Swarup,
increasing the RFC adapter time out from the visual admin has solve the problem,
thank you for that.
but what I was looking for is a way to find out what could be the root cause, since it was running 2 years with (300000 ms time out) without a problem. Now I must increase this time out which mean my system is not performing well!
Agasthuri,
as I mentioned, it was running fine with 2mb, now even 1mb cannot be proccessed,
Thanks again.

SMQ2 Time limit exceeded

Hi Experts,
IDOC to IDOC Scenarion--There are some entries in SMQ2 are showing "time limit exceeded". i tried to unlok the Queue every time i get the error and after that queue is going into Running status for some time and again it is giving the same error and status is "SYSFAIL". Queue registration is also done.we are facing this problem in production.
All other interfaces messages are processing fine except for one interface. some IDocs are processed even for the same interface. I assumed that the size of the message is large. so it is not processing, mapping step is not executed.
see the example below for one message which is not processed from XI
<SAP:MessageSizePayload>467228</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>479041</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>467228</SAP:PayloadSizeRequest>
We have restarted the complete XI server after Kernal upgrade and after that we are getting this problem, can any body give me the suggestion how can we solve the problem.

Hi
The size of the messages also not huge, we have tested it testing system and it is taking less than one minute to process the message. And we have checked at the Gate way & JCO connections are working fine. The problem is still there as i explained in my first post.
Every time it is giving time limit exceeded after unlocking the Queue.
Is there any other suggestions to resolve this issue.
Thanks in Advance
Neeru
Edited by: neeru on Mar 3, 2010 2:57 PM

Time limit exceeded in inbound qRfc

Hi all!
Please I need your help with this timeout issue. I have the following scenario:
FTP --> XI (Java mapping) --> R3 (Idoc)
Where from that Java mapping I do some RFC's to R3 in order to make conversions and validations.
When I test this interface in development environment with a 1Mb flat file, it took 5 minutes to process. However, i did the same test in QA environment, it took pretty much more than 5 minutes and I got this "time limit exceeded" in the qRfc inbound queue (sxmb_moni t-code).
I was told that the hardware beneath development and QA are different but theorically, the later should be faster.
Anyone has any suggestion to resolve this? I will really appreciate it.
Best regards!
Vanesa.

Hi,
have a look on this doc called "HowTou2026 Investigate Timeouts in Synchronous XI/PI Scenario"
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747
You will certainly find your answer.
Regards.
Mickael

IDoc on outbound side from XI - time limit exceeded error

Hi,
I have a FIle to IDoc scenario and I'm creating there a lot of idocs (20000) in a single push. I'm getting an error "time limit exceeded" on outbound side with red flag in SXMB_MONI. How to increase this limit parameter? Where to do it? - PI? or R/3?
Thank you,
Olian

Hi,
Check thios below thread..
Re: XI timeout error
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Regards,
Srini

Time limit Exceeded problem

Hi ,
I have a file to idoc scenario .
I have a file which generates many idocs (size atmost 5 mb)
I am aware sap recommends to limit the message the file size to atmost 5mb.
Do they mean file size of the payload ...because size increases in xi also .
I just want to process such a file quickly .
For that I am employing queue priortization at both sender and reciever .
and would idoc packaging help at the receiver .
Besides I am getting 'time limit exceeded in sm58' although I am seeing my idocs in idx5.
Here are some of the things I have checked ..
1) Parameters in SXMB_ADM - Integration Eningine configuration ---Specific configuration ...tried various tuning parameters ...but it didn't work..
2) In partner profile in recieving CRM system made chagend the setting from trigger immediately ..to background Task ...
(I am not certain how far that is relevant .
If it is a problem with CRM system's ability to accept mass idocs (because a small number is acceptible ...under 1mb file size ) then seetings should in crm so that large number idocs get succesfully posted .
I have posted this issue several times ...Kindlyhelp
KIndly what parameters i should tweak in xi or that matter recieving crm system to take care of this problem.
Kindly help

HI,
Large size of file processing
In general, an extra sizing for XI memory consumption is not required. The total memory of the SAP Web Application Server
should be sufficient except in the case of large messages (>1MB).
To determine the memory consumption for processing large messages, you can use the following rules of thumb:
Allocate 3 MB per process (for example, the number of parallel messages per second may be an indicator)
Allocate 4 kB per 1kB of message size in the asynchronous case or 9 kB per 1kB message size in the synchronous case
Example: asynchronous concurrent processing of 10 messages with a size of 1MB requires 70 MB of memory
(3MB + 4 * 1MB) * 10 = 70 MB With mapping or content-based routing where an internal representation of the message payload
may be necessary, the memory requirements can be much higher (possibly exceeding 20 kBytes per 1kByte
message, depending on the type of mapping).
The size of the largest message thus depends mainly on the size of the available main memory. On a normal 32Bit operating system, there is an upper boundary of approximately 1.5 to 2 GByte per process, limiting the respective largest message size.
please check these links..
/community [original link is broken]:///people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Input Flat File Size Determination
/people/shabarish.vijayakumar/blog/2006/04/03/xi-in-the-role-of-a-ftp
data packet size - load from flat file
How to upload a file of very huge size on to server.
Regards
Chilla

Time Limit Exceeded. JDBC Adapter

Hello guys,
we have problem in an interface in production.
The interface is asynchronous and is File -> PI -> JDBC
Some messages have sometimes an error in PI monitorization, and we can see the next error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SYSTEM_DUMP</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>XXXX : XXXX___0000 : Time limit exceeded.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
It seems there is an error when sending to the JDBC adapter? The concurrency of the adpter is set to 1 and we send 7 messages to the same adapter and the messages are executed more or less at the same time.
Could we have to do some PI configuration about queues? or maybe is about the concurrency of the adapter?
Many thanks in advance.
Regards,
Xavier.

You might need to increase MAXIMUM CONCURRENCY > 1 and set poolWaitingTime > 0 as per SAP Note 831162. By doing this will alow JDBC Receiver to process concurrency the request from Integration Engine.
or you also can try to increase "Recv.maxConsumers" for JDBC Adapter. The current value is 5
In addition above, since more messages are concurrently happening more or less at the same time, I would recommend also to use this parameter setting.... Go to advanced tab in the jdbc receiver channel.
check the option "Disconnect from Database After Processing Each message". This would help if the connection is not immediately return to the other thread after serving the first thread. Plus it is a best practice to follow up.

Time limit Exceeded in SM58

Hi ,
I have a file to ido scenario.The file size is suppose to be big (atmost 5mb).I am getting the following error in SM58
Time limit Exceeded .
I am able to see my idocs in idx5.
Kindly help

HI,
Check the below links may be useful
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/43e3b690-0201-0010-c582-deedc80fa6bb
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694
Regards
Chilla

Check if A/R summary has exceeded time limit:exceeded by days/hours 42 14 ?

Similar Messages

Maybe you are looking for