Error in limit utilization

Hi Experts
I am getting error while utilizing limt as mentioned in screen shot
Where i have mentioned the interest rate for yield curve 9001

Hi Bajaj,
You need to remove the yield curve 9001 in MRA as you are not using the NPV calculations

Similar Messages

Credit Risk Analyzer- Limit utilization error

Hi All,
For the money market, we defined different Limit types in Credit Risk Analyzer. And for each business partner and currency used, we defined seperate limits. When we enter a credit, if the end date of the credit isnu2019t equal to the Valid to (external) date of the related limit, in Limit utilization details it gives the error :
Error while determining attributable amounts
    Message no. K-152
Diagnosis
    A serious error occurred during calculation of the attributable amounts that caused the system to terminate calculations.
Procedure
    Pay attention to further error messages.
As a warning:
Transaction 2000000000068, company code 1000, object category T5 could not be valued
    Message no. K-249
What are your suggestions?
Thanks in advance,
Regards,

Hi Danisman,
I am facing the same problem, did you find a solution for this issue?
Thank you,
Luis Marquez

Credit Limit utilization error

Dear experts,
For the money market, we defined different Limit types in Credit Market Analyzer. And for each business partner and currency used, we defined seperate limits. When we enter a credit, if the end date isnu2019t equal to the Valid to (external) date in the related limit, in Limit utilization details it gives the error :
Error while determining attributable amounts
    Message no. K-152
Diagnosis
    A serious error occurred during calculation of the attributable amounts that caused the system to terminate calculations.
Procedure
    Pay attention to further error messages.
And it gives this warning:
Transaction 2000000000068, company code 1000, object category T5 could not be valued
    Message no. K-249
How can we solve this problem?
Thanks for your help,

Hi Danisman,
same error im also facing.
Did you manage to solve above error .
Thanks

Runtime error(Time limit exceeds)after executing select query

Dear experts, whenever i executing the select query in this zprogram i am getting runtime error that time limit exceeds.i am using inner join and into table.after that also i am geetting error. how can i resolve it??
SELECT LIKP~VBELN LIKP~WADAT_IST LIKP~VEHICLE_NO LIKP~TRNAME
          LIKP~VEHI_TYPE LIKP~LR_NO LIKP~ANZPK LIKP~W_BILL_NO
          LIKP~SEALNO1                                       " Seal NO1
          LIKP~SEALNO2                                       " Seal NO2
          LIPS~LFIMG
          VBRP~VBELN VBRP~VGBEL VBRP~MATNR VBRP~AUBEL VBRP~FKIMG
          VBAK~AUART
          VBRK~FKART VBRK~KNUMV VBRK~FKSTO
          FROM LIKP INNER JOIN LIPS ON LIKP~VBELN EQ LIPS~VBELN
                    INNER JOIN VBRP ON LIKP~VBELN EQ VBRP~VGBEL
                    INNER JOIN VBAK ON VBRP~AUBEL EQ VBAK~VBELN
                    INNER JOIN VBRK ON VBRP~VBELN EQ VBRK~VBELN
          INTO TABLE I_FINAL_TEMP
          WHERE LIKP~VSTEL = '5100' AND
             LIKP~WADAT_IST IN S_WADAT AND
                VBRP~AUBEL IN S_AUBEL AND
                VBAK~AUART IN ('ZJOB','ZOR') AND
                VBRK~FKART IN S_FKART AND
*               VBRK~FKART IN ('ZF8','ZF2','ZS1') AND
                VBRK~FKSTO NE 'X'.
When I am debugging the select query.the cursor will not go to next step.after 15-20 minutes i am getting runtime error(time limit exceeds).
how can i resolve it for that scenario??

Looks like whole SD flow you trying to fetch in single query
First you check the database statistic of these table are upto date in system ( Check with basis team )
if this query was working fine earlier.
Most of table involved are huge volume tables which queried with any primary key
Any secondary index on created for LIKP on VSTEL WADET ?
My suggestion would be split the selection queries and make use of primary or existing secondary index to fetch the desired result if possible. For testing purpose split the queries and find which is taking more time and which needs index by taking squel trace in ST05.
Also take ST05 trace of this query in debugger ( New debugger -> special tool -> trace > ST05/SE30)

APO jobs cancelled due to error- Time limit Exceed.

Dear All,
Three jobs are scheduled daily to transfer data from R/3 to APO,
These are cancelled due to error -"Time limit exceed".

Hi Pankaj,
There is a specific time allocated for each queue to clear and to get transferred across the system. the probable reasons are.
1. The queue itself is taking more than the allocated time to clear due to system load. Each queue requires specific free memory from server , in case of overload system is unable to allocate desired memory hence the error might appear.
2. If in a queue the very first entry is stuck due to x,y,z reason the queues following automatically go into "timeout" and then "system fail"
Proposed solution.
1. Analyze the first entry functionally. If Ok then ask the basis team to clear that particular entry.
2. after time out the queue will go to "SYSFAIL". Double clicking on this will reveal the reason. Based on the technical reason I can suggest the relevant OSS notes to be applied.
For detailed technical analysis check t-code CFG1.
Regards,
Ankur
Edited by: Ankur Shrivastava on Dec 19, 2007 5:58 AM

Error in LIME Query-Authorization object C_Lime_Loc cannot be checked..

hi,
I am very new to SAP Basis. i am facing the subject mentioned error in one of the user in a client when i run MM03 T.code.Su53 is showing Successful.
Temporaily ,I have provided the user with Profile SAP_ALL along with roles specified for the user and things are working fine.
i have tried assigning this object to all the Roles in the user but still in vain. Request some guidance to resolve this problem and thus removing the SAP_ALL profile to the concern user.Thanks in advance.
Edited by: Selva kannan on May 5, 2008 2:13 PM

Hi,
Heartly thanks for your feedback.
Actally the error reads: Error in Lime Query:Authrization object C_Lime_Loc cannot be checked.
SU53 is displaying last authorization is successful.
i have already added the object C_LIME_Loc to all the roles and checked the T.code MM03 without SAP_ALL profile.but failed.
I had compared the t.code su24 output in the user once with SAP_ALL profile and once without SAP_ALL and found both has same(identical) checked value. need help as i can feel that there is some authrization in SAP_ALL which is missing in my roles. how do i detect this....how do i check the objects in SAP_ALL related to this error.

JSP Error: Include limit reached

Hi All,
I am developing on iAS 6.0 SP1 on WinNT. I have my initial index.jsp
which uses
<%@ include file=xx.jsp %> to layout the main page depending on a set of
session values.
At the moment I have about 31 such includes. But I get the following
error with that jsp.
I remember there was a limitation of 20 includes in NAS 4.0.
I feel that same limitation is with iAS.
If so is there a way to overcome this limitation?
TIA
Dhaninda Weerasinghe
plate: /cat/index.jsp, JSP Error: Include limit reached
Exception Stack Trace:
java.lang.Exception: JSP Error: Include limit reached
at com.netscape.jsp.JSP.parseAt(Unknown Source)
at com.netscape.jsp.JSP.parseNext(Unknown Source)
at com.netscape.jsp.JSP.parseBlock(Unknown Source) . . .

Hi,
CALCLIMITFORMULARECURSION configuration setting is not valid for ASO cubes and only applies to BSO cubes. The equivalent configuration setting for ASO cubes is MDXLIMITFORMULARECURSION.
Syntax
MDXLIMITFORMULARECURSION TRUE | FALSE
TRUE - Imposes a limit of 31 on the number of MDX formula execution levels. The default setting is TRUE.
FALSE - Imposes no limit on the number of MDX formula execution levels.
Description
MDXLIMITFORMULARECURSION limits the number of execution levels of MDX calculated members or formulas. MDX calculated member or formula execution may be recursive (for example, a formula can refer to itself, or a calculated member can refer to itself). By default, Essbase limits the number of MDX formula execution levels, because formulas with excessive execution levels may lead to stack overflow errors and crash the server. However, setting MDXLIMITFORMULARECURSION to FALSE prevents Essbase from imposing the limitation. You can use this setting when you know that a recursive execution in a formula/calculated member will eventually terminate, and you wish to have a recursion depth greater than 31.
If an MDX formula reaches 31 execution levels and MDXLIMITFORMULARECURSION is not set, or is set to TRUE, Essbase stops processing that formula and writes
error messages in the application log. If a formula reaches 31 execution levels and MDXLIMITFORMULARECURSION is set to FALSE, Essbase continues processing that formula.
CAUTION: before setting MDXLIMITFORMULARECURSION to FALSE, be sure that the MDX formulas in the outline are not infinitely recursive; for example, be sure that formulas do not depend on each other. Infinite formula recursion may crash the server.
This is a known issue and is fixed in version 11.1.1.3.500 and you may consider upgrading Essbase.
KosuruS

Error pass limit

Cisco phone shows " Error Pass Limit".
Product Type:
Cisco 7941
Phone has 2 Lines.

This can also be caused by excessive number of unused DN’s in CUCM. See more in this url, http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080875c69.shtml
Roger

Error Pass Limit 7940 series phone

Hi all,
I have a 7940 that's displaying an "Error Pass Limit" error on the screen. It receives no dial tone but can browse the corporate directory and the switch works fine. Things like call fwd doesn't work and view missed calls do not display even though they did a few days ago.
I'm using a CAT6 patch cable. It configures and gets its IP fine.
If you like, I can post info about its Rx or Tx packets displayed on its Port Information page.Let me know which one to show and I can get the info for you.
THANKS in advance! I really need to get it back in working condition.

Hi Erik,
This bug is rated as a severity level 4. Here is the description of a level 4 (not being worked on);
4 - Minor - Things fail under very unusual circumstances, but operation essentially recovers without intervention. Users don't need to install any workarounds, and performance impact is tolerable.
This bug is only found on CCM 4.0(1), is that what you are running? If so,you probably want to upgrade to at least 4.0(2)a (but more likely to 4.1(3)sr3b). Here is a link to the number of resolved caveats between 4.0(1) and 4.0(2) which is a massive list.
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_0/rel_note/402cmrn.htm#wp1723292
Hope this helps!
Rob
Please remember to rate helpful posts....

Error Contract limit exceeded

Hello All,
We got an error "Contract limit exceeded" When tried to create a PO.
I checked in the contract header limit.But it seems not useful.Pl provide me any Table name where i can check the Release values of each line item of the contract in various Purchase orders.
OR provide a path where can i check the contract used limit.
Thanks in advance to all
Kalyani
Hyderabad

It seems Contract Limit is Exceeded. Go to ME33K and Select Item Then Click on Release Documentation (Ctrl Shift F12) then it will Show the Number of release pos created on Contract.
Also Check the Contract Limit in Header Details.
Regards,
Ashok

Query0;Runtime error time limit exceeded,with parallel processing via RFC

Dear experts,
I have created a report on 0cca_c11 cube and while running my report when i give cost center group which contains many cost centers , my report executes for long time and at last gives message
"Error while reading data;navigation is possible" and
"Query0;Runtime error time limit exceeded,with parallel processing via RFC"
please tell me what is the problem and how can i solve this
Regards
Shweta

hI,
Execute the Query in RSRT with Execute and Debug option.
Select SQL statements toknow where exactly it's taking time.
Let us know the details once you done.
Reg
Pra

Error Pass Limit on 7912

Hi i have a problem with 7912s registered to a callmanager v 4.1(3)sr3a. I changed the maximum allowed calls in the directory number but nothing happened, do you think that Cisco release a service release to solve this problem? I don't know what else to do, any suggestion?
Thanks in advanced,
Pepe

We receive 5 new phones (7912) when i registered them the error pass limit appeared on 4 of them. After that, i searched for the error on the web and tried put the maximum calls on 6 and the trigger on 4 on the DN of the phone, but nothing happened. I tried this with all the values allowed but nothing happened. After that i tried to register the phone with other number but the problem was still there.
To discard a software problem on the phone i registered it on my callmanager and its function was normally.

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

TRFC error "time limit exceeded"

Hi Prashant,
No reply to my below thread...
Hi Prashant,
We are facing this issue quite often as i stated in my previous threads.
As you mentioned some steps i have already followed all the steps so that i can furnish the jog log and tRFC details for reference long back.
This issue i have posted one month back with full details and what we temporarily follow to execute this element successfully.
Number of times i have stated that i need to know the root cause and permanent solution to resolve this issue as the log clearly states that it is due to struck LUWs(Source system).
Even after executing the LUWs manually the status is same (Request still running and the status is in yellow color).
I have no idea why this is happening to this element particularly as we have sufficient background jobs.
we need change some settings like increasing or decreasing data package size or something else to resolve the issue permanently?
For u i am giving the details once again
Data flow:Standard DS-->PSA--->Data Target(DSO)
In process monitor screen the request is in yellow color. NO clear error message s defined here.under update 0 record updated and missing message with yellow color except this the status against each log is green.
Job log:Job is finished TRFCSSTATE=SYSFAIL message
Trfcs:time limit exceeded
What i follow to resolve the issue:Make the request green and manually update from PSA to Data target and the job gets completed successfully.
Can you please tell me how to follow in this scenario to resolve the issue as i waiting for the same for long time now.
And till now i didn't get any clue and what ever i have investigated i am getting replies till that point and no further update beyond this
with regards,
musai

Hi,
You have mentioned that already you have checked for LUWs, so the problem is not there now.
In source system, go to we02 and check for idoc of type RSRQST & RSINFO. If any of them are in yellow status, take them to BD87 and process them. If the idoc processed is of RSRQST type, it would now create the job in source system for carrying out dataload. If it was of RSINFO type, it would finish the dataload in SAP BI side as well.
If any in red, then check the reason.

ASO Error - Recursion Limit reached

Hi,
I'm getting Recurrsion limit error in ASO while trying to access the data in Excel Addin. I set CALCLIMITFORMULARECURSION FALSE in essbase.cfg but still facing the same error. Any help would be appreciated...
Essbase Version 11.1.13
"Error executing formula for [MemeberName] (line 0): Recursion Limit [31] Reached"
Thanks
Edited by: MoFa on Jul 26, 2012 4:48 PM

Hi,
CALCLIMITFORMULARECURSION configuration setting is not valid for ASO cubes and only applies to BSO cubes. The equivalent configuration setting for ASO cubes is MDXLIMITFORMULARECURSION.
Syntax
MDXLIMITFORMULARECURSION TRUE | FALSE
TRUE - Imposes a limit of 31 on the number of MDX formula execution levels. The default setting is TRUE.
FALSE - Imposes no limit on the number of MDX formula execution levels.
Description
MDXLIMITFORMULARECURSION limits the number of execution levels of MDX calculated members or formulas. MDX calculated member or formula execution may be recursive (for example, a formula can refer to itself, or a calculated member can refer to itself). By default, Essbase limits the number of MDX formula execution levels, because formulas with excessive execution levels may lead to stack overflow errors and crash the server. However, setting MDXLIMITFORMULARECURSION to FALSE prevents Essbase from imposing the limitation. You can use this setting when you know that a recursive execution in a formula/calculated member will eventually terminate, and you wish to have a recursion depth greater than 31.
If an MDX formula reaches 31 execution levels and MDXLIMITFORMULARECURSION is not set, or is set to TRUE, Essbase stops processing that formula and writes
error messages in the application log. If a formula reaches 31 execution levels and MDXLIMITFORMULARECURSION is set to FALSE, Essbase continues processing that formula.
CAUTION: before setting MDXLIMITFORMULARECURSION to FALSE, be sure that the MDX formulas in the outline are not infinitely recursive; for example, be sure that formulas do not depend on each other. Infinite formula recursion may crash the server.
This is a known issue and is fixed in version 11.1.1.3.500 and you may consider upgrading Essbase.
KosuruS

Error in limit utilization

Similar Messages

Maybe you are looking for