Skip to Content
author's profile photo Former Member
Former Member

RFC_ERROR_SYSTEM_FAILURE error while updating the sick leave in MSS

Hi Guru ,

We are getting RFC_ERROR_SYSTEM_FAILURE error while updating the Sick leave for team member from portal .

Please tell how to resolve this .

Dump part :

Runtime Errors MESSAGE_TYPE_X

Error analysis

Short text of error message:

System error

Long text of error message:

Technical information about the message:

Message class....... "HRTIM00BUFMSG"

Number.............. 001

Variable 1.......... " "

Variable 2.......... " "

Variable 3.......... " "

Variable 4.......... " "

Information on where terminated

Termination occurred in the ABAP program "SAPLHRTIM00_TMWBUFFER" - in

"INITIALIZE".

The main program was "SAPMSSY1 ".

In the source code you have the termination point in line 55

of the (Include) program "LHRTIM00_TMWBUFFERCB5".

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on May 13, 2010 at 03:09 PM

    When an RFC fails from the portal to an SAP Backend, probably ECC 6.0 in your case, there are a few options that I use to troubleshoot:

    1. Ensure that all your jco's are set up ok, passwords, ect. JCOs do not appear to be the problem here

    2. Have an ABAP programmer review where the RFC is failing on the Backend System

    3. Set up an External Breakpoint in the backend RFC. Step to do this:

    a. Get the Backend UserID of a test portal user that is having this issue.

    b. Ensure that test user has "Debug Display" access in the Backend System

    c. Log into the Backend system, go to SE 37 and display your RFC

    d. Go to Utilities --> Settings --> Debugging in the top menu and add the Test User ID to the "Users" field.

    e. Set an external breakpoint any where you want in the RFC.

    f. Run the Leave request as the test user.

    g. a new SAP GUI screen will popup once it hits the breakpoint. The portal browser will stay frozen until you step thru the ABAP program.

    Option 3 may sound like alot at first if you never used it, but if you are responsible for troubleshooting portal issues like this one, it is a skill you must have. You can also have an ABAP resource responsible for external debugging when you come accross issues like these. It helps you see exactly what data is being passed in from the portal and what is happening to cause the error.

    Regards,

    Tom

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 13, 2010 at 03:32 PM

    Hi Tom ,

    Thanks for information .

    After checking the dump in Backend system , Found the code line where error is getting raised .

    • test if dates are valid ,

    afromdate = fromdate + 1.

    afromdate = afromdate - 1.

    atodate = todate - 1.

    atodate = atodate + 1.

    IF afromdate NE fromdate OR

    atodate NE todate.

    >>>> MESSAGE x001(hrtim00bufmsg).

    ENDIF.

    Values of Chosen variables at the time of termination are as follows :-

    FROMDATE : 20100421

    TODATE : 00000000

    ME->AFROMDATE : 20100421

    ME->ATODATE : 00010102

    As user is trying to update the sick leave which is of open leave type , Some problem is there with date calculations .

    Please can you give some details about this code .

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 13, 2010 at 03:43 PM

    The TODATE variable at the bottom of you page is either being passed from the Portal via the RFC as blank or it is getting set to blank somewhere in the code.

    Try to back track and see where the TODATE is coming from. Pass me back the RFC name and I'll take a look at it a little later.

    Did you do any customizations to the Leave Request Web Dynpro?

    Regards,

    Tom

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.