RFC_ERROR_SYSTEM_FAILURE: Error in ASSIGN: Memory protection error.

HI,
I need an urgent help in this error. I am getting this error, while i am trying to access the R3 from portal. i.e While saving the employee info.
ESS -> PERSONAL INFO -> PROJECT EXP-> SAVE (dump)
error msg in portal
Error while saving: com.sap.mw.jco.JCO$Exception: (104)
RFC_ERROR_SYSTEM_FAILURE: Error in ASSIGN: Memory protection error.
Please contact administrator. 
  FIELD-SYMBOLS <KEY> STRUCTURE PAKEY DEFAULT INFTY_TAB.
  FIELD-SYMBOLS <CTRL> STRUCTURE PSHD1 DEFAULT INFTY_TAB.
LOOP AT INFTY_TAB.
ASSIGN INFTY_TAB+3 TO <KEY>.   " Skip MANDT-field <-- error while exe this statement
end loop.

Just try below Field-sumbiol statement might be it will solve ur problem.
FIELD-SYMBOLS <KEY> TYPE ANY.
FIELD-SYMBOLS <CTRL> TYPE ANY.
LOOP AT INFTY_TAB.
ASSIGN INFTY_TAB+3 TO <KEY>. " Skip MANDT-field <-- error while exe this statement
end loop.

Similar Messages

  • Adobe form Error "Memory protection fault in OLE container control"

    Hi,
       I am getting the error "Memory protection fault in OLE container control" while trying to open the layout tab of adobe forms.
      I am getting this error for all the adobe forms.Please let me know the solution.
    Thanks in advance.
    Thanks,
    Nuthan.

    I can reproduce this error consistently.. This is how: Install Microsoft SQL Server 2008.
    As soon as I remove SQL 2008 the error went away. Adobe LiveCycle Designer was invoked via OLE2 interface. Apparently SQL Server 2008 (as in my case or some other applications in your case) modified the way OLE2 behaves and therefore causes this error.

  • 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".

    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

  • RFC_ERROR_SYSTEM_FAILURE: Error in module RSQL of the database interface

    HI All,
    I am trying to execute an RFC through JCO connection and getting the error "RFC_ERROR_SYSTEM_FAILURE: Error in module RSQL of the database interface".
    While debugging I have found that the actual cause of dump is a SQL command written in this RFC. The SQL command is
    SELECT DISTINCT *
        INTO CORRESPONDING FIELDS OF TABLE lt_calcrule_hol
        FROM itc_calcrule_hol                              
        FOR ALL ENTRIES IN calc_rule
        WHERE rule_id = calc_rule-rule_id
        AND start_date <= sy-datum
        AND end_date >= sy-datum
        AND (lv_ident)
        AND ( (lv_orgs)
        OR location_type = '' ).
    Here the value of lv_ident is ======>>  ident IN ('US','B2'.........................)
    and value of lv_orgs is =========>>  location_type IN ('S1','S2',..............................)
    location_type and ident are columns in table itc_calcrule_hol .
    I have analysed that if I pass around 700 enteries in the lv_ident and lv_ogs then it is working fine.
    But if I have more than 900 enteries in these variables then it dumps.
    Can anybody let me know what is the issue with the query here.And what could be the solution.
    Thanks and Regards,
    Reena

    I'd recommend talking to an experienced basis admin or ABAP developer. First of all it would help to look at the short dump in SAP, to see if that gives any useful information. In case of a generic error like DBIF_RSQL_INVALID_RSQL, the developer trace of the work process (dev_w<n>) should contain further information (to get the number of the work process that handled your RFC call check the system log, which contains the reference along with a comment about the dump). So I'd check those first to see what actually caused the problem.
    Information on maximum SQL statement length can either be retrieved from the database vendor's documentation or alternatively by searching SAP [OSS notes|https://service.sap.com/notes]. For the latter you need a valid user ID for the SAP service market place.

  • How to disable memory protection

    hi
    i am using win 8.1 and ie 11 . i am administrator  on my system but i can not disable memory protection to mitigate online attacks and i tested all the ways in the answers but any of them worked. i have to disable it because of automation software.
    in my office i am using ie8 now. what i have to do to resolve this problem?

    Hi,
    The feature "Enable memory protection to help mitigate online attacks" is already replaced with "Enable Enhanced Protected Mode". You can disable it instead to realize your goals.
    For more infomation about this new feature, you can refer to the link below for more details:
    Enhanced Protected Mode:
    http://blogs.msdn.com/b/ie/archive/2012/03/14/enhanced-protected-mode.aspx
    Roger Lu
    TechNet Community Support

  • Assign memory to thread .......urgent...please...

    how can i assign memory to a perticular thread in my application.
    please help me !!!!!!

    Try
    java.lang.ThreadLocal

  • RFC_ERROR_SYSTEM_FAILURE error in Planning Sequence in RSPLAN

    Hi everyone,
    Whenever we run the Planning Modeler in RSPLAN and choose any Planning Sequence either for changing or executing, or just selecting it the system throws the following error:
    "An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE", and retrieve a short dump.
    This only occurs in all the planning sequences, which were working before without any issues, and this is only happening in BW development not in production.
    The short dump goes like this:
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_RSR_X_MESSAGE
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
          Name
       23 FUNCTION     SAPLRRMS                            LRRMSU13                               73
          RRMS_X_MESSAGE
       22 METHOD       CL_RS_BASE====================CP    CL_RS_BASE====================CM004     7
          CL_RS_BASE=>X_MESSAGE_S
       21 METHOD       CL_RSDRC_PROVRQ_SRVS==========CP    CL_RSDRC_PROVRQ_SRVS==========CM004   122
          CL_RSDRC_PROVRQ_SRVS=>GET_RQTS_BASIC
       20 METHOD       CL_RSD_DC_SUPPORT_INFOCUBE====CP    CL_RSD_DC_SUPPORT_INFOCUBE====CM006     6
          CL_RSD_DC_SUPPORT_INFOCUBE=>IF_RSD_DELTACACHE_SUPPORT~GET_RQTS
       19 METHOD       CL_RSD_CUBE===================CP    CL_RSD_CUBE===================CM02R    26
          CL_RSD_CUBE=>IF_RSD_DTA~GET_DATA_TIMESTMP
       18 METHOD       CL_RSD_DTA====================CP    CL_RSD_DTA====================CM01K     3
          CL_RSD_DTA=>IF_RSD_DTA~GET_DATA_TIMESTMP
       17 METHOD       CL_RSPLS_PLAN_BUFFER==========CP    CL_RSPLS_PLAN_BUFFER==========CM00H    35
          CL_RSPLS_PLAN_BUFFER=>IF_RSD_DELTACACHE_SUPPORT~GET_RQTS
       16 METHOD       CL_RSR_RRK0_RQTS==============CP    CL_RSR_RRK0_RQTS==============CM003   118
          CL_RSR_RRK0_RQTS=>APPEND_BUFFER
       15 FUNCTION     SAPLRRK0                            LRRK0U23                               33
          RRK_BUFFER_NOTIFY
       14 METHOD       CL_RSR_OLAP===================CP    CL_RSR_OLAP===================CM00X    44
          CL_RSR_OLAP=>CREATE_BUFFER
       13 METHOD       CL_RSR_OLAP===================CP    CL_RSR_OLAP===================CM002    65
          CL_RSR_OLAP=>OPEN_KHANDLE
       12 METHOD       CL_RSR_OLAP===================CP    CL_RSR_OLAP===================CM00M    15
          CL_RSR_OLAP=>IF_RSR_OLAP~GET_SELDR
       11 METHOD       CL_RSBOLAP_SELECTION_OBJECT===CP    CL_RSBOLAP_SELECTION_OBJECT===CM007    42
          CL_RSBOLAP_SELECTION_OBJECT=>LOAD_DEFINITION
       10 METHOD       CL_RSBOLAP_SELECTION_OBJECT===CP    CL_RSBOLAP_SELECTION_OBJECT===CM009    20
          CL_RSBOLAP_SELECTION_OBJECT=>SUBMITTED
          CL_RSBOLAP_SELECTION_OBJECT=>SUBMITTED
        9 METHOD       CL_RSR_OLAP_VAR===============CP    CL_RSR_OLAP_VAR===============CM003   283
          CL_RSR_OLAP_VAR=>IF_RSR_VAR_RUNTIME~SUBMIT
        8 METHOD       CL_RSR_VAR_RUNTIME============CP    CL_RSR_VAR_RUNTIME============CM00Q    11
          CL_RSR_VAR_RUNTIME=>IF_RSR_VAR_RUNTIME~SUBMIT
        7 METHOD       CL_RSPLFR_VAR_CONT============CP    CL_RSPLFR_VAR_CONT============CM003    24
          CL_RSPLFR_VAR_CONT=>SUBMIT_OLAP_VAR_CONT
        6 METHOD       CL_RSPLFR_VAR_CONT============CP    CL_RSPLFR_VAR_CONT============CM007   175
          CL_RSPLFR_VAR_CONT=>SCREEN_NECESSARY
        5 METHOD       CL_RSPLFR_CONTROLLER==========CP    CL_RSPLFR_CONTROLLER==========CM00T   158
          CL_RSPLFR_CONTROLLER=>CHECK_PLSEQ_SCREEN_NECESSARY
        4 FUNCTION     SAPLRSPLSSE                         LRSPLSSEU02                            46
          RSPLSSE_PLSEQ_EXECUTE
        3 FORM         SAPLRSPLSSE                         LRSPLSSEU02                             1
          RSPLSSE_PLSEQ_EXECUTE
        2 FORM         SAPMSSY1                            SAPMSSY1                               85
          REMOTE_FUNCTION_CALL
        1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
          %_RFC_START
    Does anyone have any idea what could be the issue here?
    Thanks,
    Diogo.

    Hi,
    Thanks for the response.
    I've already searched for that not but haven't installed it yet. I'm gonna try it to see if it solves it, but the weird thing is that in production the issue doesn't occur, only in development.
    Diogo.

  • Assigning memory on windows os crashing labview app

    Hi
    I must be doing something really stupid and very easily crashing my pc by writing only few functions in labview!
    I want to pre-allocate memory of 5GB at the start of application. So I used simple initialize function to create 2d array of NaN dB points as shown in the image.  I have 8GB of memory but the error popped up as shown in screen. And I only tried 1GB as shown in image. Could I not have this pre-allocation?
     

    k-waris wrote:
    Hi
    I must be doing something really stupid and very easily crashing my pc by writing only few functions in labview!
    I want to pre-allocate memory of 5GB at the start of application. So I used simple initialize function to create 2d array of NaN dB points as shown in the image.  I have 8GB of memory but the error popped up as shown in screen. And I only tried 1GB as shown in image. Could I not have this pre-allocation?
    Are you running LabVIEW 32-bit? You can't allocate that much memory with a 32-bit operating system or in LabVIEW 32-bit.

  • Short dump while filtering an ALV report

    Hi ,
    I have an ALV report which gives me short dump when I filter any of the 'P' type field. I tried to implement sap note 839839 in debug mode but in vain. Should I implement this note first and then check the chnage?
    the short dump error "..........
    Error in ASSIGN: Memory protection error.                                                                               
    The current program "SAPLSSEL " uses the ASSIGN statement.              
    However, the offset of the segment (20208) plus the length (69)         
    is greater than the length of the segment (20264).                      
    This is not allowed.                                                                               
    If the error is in one of your own ABAP programs or an SAP program that          
    you have modified, try to correct it.                                            
    Reduce the offset and/or length that you are using.                                                                               
    If the error occurred in a non-modified SAP program, you may be                  
    able to find a solution in the SAP note system.                                  
    If you have access to the note system yourself, use the following                
    search criteria:                                                                               
    "ASSIGN_OFFSET+LENGTH_TOOLARGE"                                   
    "SAPLSSEL " or "LSSELFDI "                                        
    "FILL_DYN_FROM_FIELD_SEL"               ........."
    I appreciate ur inputs.
    thanks in advance,
    regards,
    shan

    Hi Guys,
    I found the answer. I had to define all P type fields with eaxact length of 16 . Its working fine.
    thanks for all your help.
    regards,
    shan

  • Convert Float to Char

    Hi,
    I'm having problem when converting a float variable to char - it seems like the float value is automatically rounded into the char variable, but I don't want that.
    Does anybody know a wafunction or a way of avoiding this convertion round?
    Thanks,
    Nuno Afonso

    With the input parameters you gave me...
    Error in ASSIGN: Memory protection error
    The current program "SAPLSCFL " uses the ASSIGN statement. 
    However, the offset of the segment (536) plus the length (1)
    is greater than the length of the segment (536).           
    This is not allowed.                                       

  • BSP ASSIGNMENT ERROR WHEN SELECT A TAB IN TABSTRIP

    Hi all,
    I have a dump when select one of the four tabs, in which three working fine.
    Plese see the below dump and help as soon as possible.
    Runtime Errors         MOVE_TO_LIT_NOTALLOWED                          
    Exception              CX_SY_DYN_CALL_ILLEGAL_TYPE                     
           Occurred on     09/18/2006 at 20:51:05                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "CL_BSP_MODEL==================CP " had to be 
    terminated because one of the                                         
    statements could not be executed.                                      
    This is probably due to an error in the ABAP program.                  
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below       
    . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', 
    was neither                                                                   
    caught nor passed along using a RAISING clause, in the procedure               
    "IF_BSP_MODEL_UTIL~CONVERT_FROM_STRING" "(METHOD)"                            
    Since the caller of the procedure could not have expected this exception       
    to occur, the running program was terminated.                                 
    The reason for the exception is:                                               
    You attempted to overwrite the field "<L_FIELD>", although it is a             
    constant (i.e. a numeric literal or a string literal). This is not             
    allowed.                                                                       
    The following objects are protected:                                           
    - Character or numeric literals                                                
    - Constants (CONSTANTS)                                                        
    - Function module and method parameters with the type IMPORTING                
      REFERENCE                                                                    
    - Untyped field symbols that have not yet had a field assigned to them         
      using ASSIGN                                                                 
    - TABLES parameters, if the actual parameter is protected against              
      changes                                                                      
    - USING reference paraemters and CHANGING parameters in FORMs if the           
      actual parameter is protected against changes                                
    - Field symbols, if the field assigned to them using ASSIGN is protected       
      against changes (for example, key components of a SORTED or HASHED           
      TABLE)                                                                       
    - External write access to an attribute with the READ-ONLY attribute           
    I have the below error in webpage.
    500 SAP Internal Server Error
    Error message: Assignment error: A constant was meant to be overwritten. ( type of termination: RABAX_STATE
    if anybody have solution to this please help me.
    Thanks in advance.
    Saravanan.V

    Hi,
      Go through the sample bsp application <b>SBSPEXT_HTMLB-> TabStrip.bsp</b> and check where you are going wrong.
       Post the code to point out where you are going wrong.
    Regards,
    Azaz Ali.

  • Document Protection Error

    After checking out books from my library and 'loading' them to my kindle I have found that i can select the book on my kindle, but it says "this document is protected by Adobe Digital Rights Management (DRM) and is not currently authorized for use with you Adobe ID.  Please sign in with the authorized Adobe ID and try again."
    How can this be fixed?

    Hi,
    I too experienced similar problems recently -  used to get errors like SOFFICEINTEGRATION143, SOFFICEINTEGRATION141 & SOFFICEINTEGRATION101(Memory protection error for OLE Container) while accessing Layout of Interactive Forms.
    I got it resolved by uninstalling the NWDS (which uninstalls Adobe LiveCycle Designer (ALD) as well) and then reinstalling ALD and NWDS (Optional).
    With the NWDS installation, ALD is also bundled.
    If you need to install ALD separately, you may get the right ALD version from
    SAP Support Portal->Downloads-> Entry by Application Group->
    Support Packages and Patches-> SAP NetWeaver-> SAP NETWEAVER-> SAP NETWEAVER 7.0-> Entry by Component-> Frontend  =>> ADOBE LIVECYCLE DESIGNER 8.0 -> #OS independent.
    Hope this helps.
    George Mathew

  • Firefox has worked great up until today no I am getting the following "Application Error" "the instruction at "0x7b1077a9" refrenced memory at"0x7b1077a9". The memory could not be "written". Click on OK to terminatethe program

    I am getting the following: "Application Error" "the instruction at "0x7b1077a9" refrenced memory at"0x7b1077a9". The memory could not be "written". Click on OK to terminate the program
    == This happened ==
    Every time Firefox opened
    == This evening while I was browsing the internet ==
    == User Agent ==
    Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB6.5; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; OfficeLiveConnector.1.3; OfficeLivePatch.0.0; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)

    My OS is windows server 2003, I have searched for
    “Enable memory protection to help mitigate online attacks” at the
    following location I could not find the above statement. Can some one help me 
    "Local Administrators can control DEP/NX by running Internet Explorer as an Administrator and unchecking the Tools >
    Internet Options > Advanced > “Enable memory protection to help mitigate online attacks” option."
    Try: Computer Configuration > Policies > Administrator Templates >
    Windows Components > Internet Explorer > Security Features > Turn off Data Execution Prevention

  • RFC Call Error - from Portal End - For ESS Personal Information service

    Hi,
    I am getting "Syntax error in program SAPLHRXSS_PER_MAC                       ., error key: RFC_ERROR_SYSTEM_FAILURE  " error Message on the portal (ESS--->Personal Information Screen).
    When I did RFC trace analysis (using ST 22) this is what i get.
    Can you let me know what could be the issue.
    We are running HR Backend(Support Pack 15,ecc 5.0).
    Portal (EP 6.0 SP19, ESS 100 (SP 10)).
    Could you please let me know what could be the issue ?
    Syntax error in program "SAPLHRXSS_PER_MAC ".
         What happened?
              Error in ABAP application program.
              The current ABAP program "SAPMSSY1" had to be terminated because one of the
              statements could not be executed.
              This is probably due to an error in the ABAP program.
              In program "SAPLHRXSS_PER_MAC ", the following syntax error occurred
              in the Include "IF_HRPA_PERNR_INFTY_XSS=======IU " in line 114:
              "The type "HRXSS_PER_SUPPLD_SUBTY_INFO_T" is unknown."
              Author and last person to change the Include are:
              Author "SAP "
              Last changed by "C5069405 "
         What can you do?
              Please eliminate the error by performing a syntax check
              (or an extended program check) on the program "SAPLHRXSS_PER_MAC ".
              You can also perform the syntax check from the ABAP/4 Editor.
              If the problem persists, proceed as follows:
              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.
              is especially useful if you want to keep a particular message.
         Error analysis
              In program "SAPLHRXSS_PER_MAC ", the following syntax error occurred:
              "The type "HRXSS_PER_SUPPLD_SUBTY_INFO_T" is unknown."
         How to correct the error
              Probably the only way to eliminate the error is to correct the program.
              If you cannot solve the problem yourself and you wish to send
              an error message to SAP, include the following documents:
              1. A printout of the problem description (short dump)
                 To obtain this, select in the current display "System->List->
                 Save->Local File (unconverted)".
              2. A suitable printout of the system log
                 To obtain this, call the system log through transaction SM21.
                 Limit the time interval to 10 minutes before and 5 minutes
                 after the short dump. In the display, then select the function
                 "System->List->Save->Local File (unconverted)".
              3. If the programs are your own programs or modified SAP programs,
                 supply the source code.
                 To do this, select the Editor function "Further Utilities->
                 Upload/Download->Download".
              4. Details regarding the conditions under which the error occurred
                 or which actions and input led to the error.
         System environment
              SAP Release.............. "640"
              Application server....... "srv006"
              Network address.......... "167.116.230.56"
              Operating system......... "HP-UX"
              Release.................. "B.11.11"
              Hardware type............ "9000/800"
              Character length......... 8 Bits
              Pointer length........... 64 Bits
              Work process number...... 1
              Short dump setting....... "full"
              Database server.......... "srv006"
              Database type............ "ORACLE"
              Database name............ "H81"
              Database owner........... "SAPR3"
              Character set............ "en_US.iso88591"
              SAP kernel............... "640"
              Created on............... "May 21 2006 20:29:01"
              Created in............... "HP-UX B.11.00 A 9000/800"
              Database version......... "OCI_920 "
              Patch level.............. "129"
              Patch text............... " "
              Supported environment....
              Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
               10.2.0.."
              SAP database version..... "640"
              Operating system......... "HP-UX B.11"
              Memory usage.............
              Roll..................... 16128
              EM....................... 4189928
              Heap..................... 0
              Page..................... 0
              MM Used.................. 629192
              MM Free.................. 3558216
              SAP Release.............. "640"
         User and Transaction
         Information on where terminated
              The termination occurred in the ABAP program "SAPMSSY1" in
               "REMOTE_FUNCTION_CALL".
              The main program was "SAPMSSY1 ".
              The termination occurred in line 68 of the source code of the (Include)
               program "SAPMSSY1"
              of the source code of program "SAPMSSY1" (when calling the editor 680).
         Source Code Extract
         Line     SourceCde
            38     
            39     module %_rfcdia_call output.
            40         "Do not display screen !
            41         call 'DY_INVISIBLE_SCREEN'.
            42         perform remote_function_diacall.
            43     endmodule.
            44     
            45     module %_cpic_start.
            46       if sy-xprog(4) = '%RFC'.
            47         perform remote_function_call using rfctype_external_cpic.
            48       else.
            49         call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
            50         perform cpic_call using convid.
            51       endif.
            52     endmodule.
            53     
            54     
            55     form cpic_call using convid type c.
            56       communication send id convid buffer header.
            57       if sy-subrc eq 0.
            58         perform (sy-xform) in program (sy-xprog).
            59       else.
            60         message a800.
            61       endif.
            62     endform.
            63     
            64     form remote_function_call using value(type).
            65       do.
            66     *   test if sy-xprog and sy-xform are set
            67     *   sy-xform = 'quatsch'. sy-xprog = 'quatsch'.
         >>>>>         call 'RfcImport' id 'Type' field type.
            69         perform (sy-xform) in program (sy-xprog).
            70         rsyn >scont sysc 00011111 0.
            71       enddo.
            72     endform.
            73     
            74     form remote_function_diastart.
            75       do.
            76         call 'RfcImport' id 'Type' field rfctype_rfcdia.
            77         perform (sy-xform) in program (sy-xprog).
            78         "Parking position for next request
            79         rsyn >scont sysc 00011111 10.
            80         "ALternativ : Free mode
            81         "COMMIT WORK.
            82         "SYSTEM-CALL FREE MODE 0.
            83       enddo.
            84     endform.
            85     
            86     form remote_function_diacall.
            87         sy-xcode = '%_@no@'.
         Contents of system fields
         Name     Val.
         SY-SUBRC     0
         SY-INDEX     2
         SY-TABIX     0
         SY-DBCNT     0
         SY-FDPOS     0
         SY-LSIND     0
         SY-PAGNO     0
         SY-LINNO     1
         SY-COLNO     1
         SY-PFKEY     
         SY-UCOMM     
         SY-TITLE     CPIC and RFC Control
         SY-MSGTY     
         SY-MSGID     
         SY-MSGNO     000
         SY-MSGV1     
         SY-MSGV2     
         SY-MSGV3     
         SY-MSGV4     
         Active Calls/Events
         No.   Ty.          Program                             Include                             Line
               Name
             2 FORM         SAPMSSY1                            SAPMSSY1                               68
               REMOTE_FUNCTION_CALL
             1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
               %_RFC_START
         Chosen variables
         Name
             Val.
         No.          2     Ty.      FORM
         Name      REMOTE_FUNCTION_CALL
         %_DUMMY$$
                 2222
                 0000
         SY-REPID
              SAPMSSY1
                 5454555322222222222222222222222222222222
                 310D339100000000000000000000000000000000
         SYST-REPID
              SAPMSSY1
                 5454555322222222222222222222222222222222
                 310D339100000000000000000000000000000000
         %_ARCHIVE
                 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         TYPE
              3
                 0000
                 0003
         SY-XPROG
              SAPLSYST
                 5454555522222222222222222222222222222222
                 310C393400000000000000000000000000000000
         SY-XFORM
              HRXSS_PER_CLEANUP
                 455555545544444552222222222222
                 82833F052F3C51E500000000000000
         %_SPACE
                 2
                 0
         No.          1     Ty.      MODULE (PBO)
         Name      %_RFC_START
         %_PRINT
                  000                                                                                0 ##
                 2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         RFCTYPE_INTERNAL
              3
                 0000
                 0003
         Internal notes
              The termination occurred in the function "ab_genprog" of the SAP
              Basis System, specifically in line 1374 of the module
               "//bas/640_REL/src/krn/runt/abgen.c#10".
              The internal operation just processed is "CALY".
              The internal session was started at 20070502223335.
              Program name.........: "SAPLHRXSS_PER_MAC ".
              Error message........: "The type "HRXSS_PER_SUPPLD_SUBTY_INFO_T" is unknown.".
         Active Calls in SAP Kernel
         Lines of C Stack in Kernel (Structure Differs on Each Platform)
         ( 0)  0x40000000016d6a8c   CTrcStack2 + 0x2bc  [dw.sapH81_DVEBMGS33]
         ( 1)  0x40000000016d67c0   CTrcStack + 0x18  [dw.sapH81_DVEBMGS33]
         ( 2)  0x4000000001d41438   rabax_CStackSave__Fv + 0x100  [dw.sapH81_DVEBMGS33]
         ( 3)  0x4000000001d4dbf8   ab_rabax + 0x1f68  [dw.sapH81_DVEBMGS33]
         ( 4)  0x40000000018cc09c   ab_genprog__FPcPvUii + 0xdbc  [dw.sapH81_DVEBMGS33]
         ( 5)  0x4000000000d3b4cc   newload__FPcP13TmpSubpoolDirUi + 0x29c  [dw.sapH81_DVEBMGS33]
         ( 6)  0x40000000016a7324   ab_LoadProg__FPcUi + 0xec  [dw.sapH81_DVEBMGS33]
         ( 7)  0x40000000016831fc   ab_link + 0x334  [dw.sapH81_DVEBMGS33]
         ( 8)  0x40000000015694d4   ab_rfcimport + 0xccc  [dw.sapH81_DVEBMGS33]
         ( 9)  0x40000000018cff98   ab_jcaly__Fv + 0x598  [dw.sapH81_DVEBMGS33]
         (10)  0x4000000000f98df8   ab_extri__Fv + 0x17a0  [dw.sapH81_DVEBMGS33]
         (11)  0x40000000016ab2d8   ab_xevent__FPCc + 0x38  [dw.sapH81_DVEBMGS33]
         (12)  0x400000000189c9a8   ab_dstep + 0x120  [dw.sapH81_DVEBMGS33]
         (13)  0x4000000000ed4c00   dynpmcal + 0xd0  [dw.sapH81_DVEBMGS33]
         (14)  0x4000000000ed1554   dynppbo0 + 0x1e4  [dw.sapH81_DVEBMGS33]
         (15)  0x4000000000ed0af4   dynprctl + 0x43c  [dw.sapH81_DVEBMGS33]
         (16)  0x4000000000ecb7a0   dynpen00 + 0x2118  [dw.sapH81_DVEBMGS33]
         (17)  0x4000000000fa598c   Thdynpen00 + 0x6a4  [dw.sapH81_DVEBMGS33]
         (18)  0x4000000000fa49b8   TskhLoop + 0x50d8  [dw.sapH81_DVEBMGS33]
         (19)  0x4000000000f999f8   tskhstart + 0x1e0  [dw.sapH81_DVEBMGS33]
         (20)  0x4000000000d42194   DpMain + 0x484  [dw.sapH81_DVEBMGS33]
         (21)  0x400000000220d41c   nlsui_main + 0x14  [dw.sapH81_DVEBMGS33]
         (22)  0x4000000000992794   main + 0x14  [dw.sapH81_DVEBMGS33]
         (23)  0xc000000000020ab0   $START$ + 0xa0  [/usr/lib/pa20_64/dld.sl]
         List of ABAP programs affected
         Index     Ty.     Program     Group     Date     Time     Size     Lang.
              0     Prg     SAPMSSY1          0     06.11.2003     20:53:07         18432     E
              1     Prg     SAPLSYST          1     10.05.2006     09:57:38         30720     E
              2     Typ     SYST          0     04.12.2000     14:54:51         27648     
         Directory of Application Tables
         Name                                     Date       Time       Lngth
             Val.
         Program      SAPMSSY1
         SYST            .  .            :  :          00002404
         ABAP Control Blocks (CONT)
         Index     Name     Fl     PAR0     PAR1     PAR2     PAR3     PAR4     PAR5     PAR6     SourceCde
           118     CLEA     00     0035                                   SAPMSSY1
           119     CLEA     00     0036                                   SAPMSSY1
           120     CLEA     00     0037                                   SAPMSSY1
           121     MESS     00     001C                                   SAPMSSY1
           122     ENDF     00     0000                                   SAPMSSY1
           123     -
         00     0000                                   SAPMSSY1
           124     PERP     00     0001                                   SAPMSSY1
           125     PERP     02     0000                                   SAPMSSY1
           126     WHIL     00     0002     0000     0000     0000     0000     0000     0000     SAPMSSY1
           130     WHIL     00     0003     0000     0000     0000     0000     0000     0000     SAPMSSY1
           134     BRAN     05     000E                                   SAPMSSY1
           135     CALY     00     0003     0038     002A     0005     002B     0000     0000     SAPMSSY1
         >>>>>     CALY     02     0000     0039     8000     0000     0000     0000     0000     SAPMSSY1
           143     xper     02     0000     0010     0011                         SAPMSSY1
           145     PERP     80     0000                                   SAPMSSY1
           146     SYSC     1F     0000                                   SAPMSSY1
           147     BRAX     00     FFEF                                   SAPMSSY1
           148     WHIL     00     0004     0000     0000     0000     0000     0000     0000     SAPMSSY1
           152     ENDF     00     0000                                   SAPMSSY1
           153     -
         00     0000                                   SAPMSSY1

    Hi,
    The error is occuring in the program file SAPLHRXSS_PER_MAC.
    In program "SAPLHRXSS_PER_MAC ", the following syntax error occurred 
    in the Include "IF_HRPA_PERNR_INFTY_XSS=======IU " in line 114:      
    "The type "HRXSS_PER_SUPPLD_SUBTY_INFO_T" is unknown."    
    Information on where terminated                                              
        The termination occurred in the ABAP program "SAPMSSY1" in               
         "REMOTE_FUNCTION_CALL".                                                 
        The main program was "SAPMSSY1 ".
    This place  where it has terminated is highlighted in bold letters.                                       
    form remote_function_call using value(type).   
      do.                                          
      test if sy-xprog and sy-xform are set      
      sy-xform = 'quatsch'. sy-xprog = 'quatsch'.
    <b>    call 'RfcImport' id 'Type' field type.     </b>
        perform (sy-xform) in program (sy-xprog).  
        rsyn >scont sysc 00011111 0.               
      enddo.                                       
    endform.                                       
    Thanks,
    Manoj

  • MEMORY_NO_MORE_PAGING error

    Hi,
    We are using ECC 5.0 here. Our DB is Oracle 9.2.0.6 and OS is AIX.
    We have a problem here.
    Our Finance people run a report "S_ALR_87013542". It was working fine.
    But now it is giving an error with ABAP Dump. The error is MEMORY_NO_MORE_PAGING.
    I have increased the parameter "rdisp/PG_SHM" to the double value. Now the value is 16384. But it is still giving the same error.
    I increased it on a Dialog Instance (application server through which Finance people access SAP)
    I searched the notes, but could not find anything relevant about my error.
    I have tried to run the report in the night when there is no load on the server. But even then it gives the same error.
    My different Memory Paramters for the App server for finance people are listed below:-
    ztta/roll_area                              3000320   
    rdisp/ROLL_SHM                              16384     
    rdisp/ROLL_MAXFS                            32768     
    rdisp/PG_SHM                                16384     
    rdisp/PG_MAXFS                              32768     
    abap/heap_area_dia                          2000683008
    abap/heap_area_nondia                       2000683008
    abap/heap_area_total                        2000683008
    abap/heaplimit                              40894464  
    abap/swap_reserve                           20971520  
    ztta/roll_extension                         2000683008
    My ABAP dump gives this error:-
    Error analysis
        The ABAP/4 runtime system and the ABAP/4 compiler use a common
        interface to store different types of data in different parts of
        the SAP paging area. This data includes the
        ABAP/4 memory (EXPORT TO MEMORY), the SUBMIT REPORT parameters,
        CALL DIALOG and CALL TRANSACTION USING, as well as internally defined
        macros (specified with DEFINE).
                                                                                    To store further data in the SAP paging area, you attempted to
        allocate a new SAP paging block, but no more blocks were
        available.
                                                                                    When the SAP paging overflow occurred, the ABAP/4 memory contained
        entries for 55 of different IDs.
                                                                                    Please note:
        To facilitate error handling, the ABAP/4 memory was
        deleted.
    How to correct the error
        The amount of storage space (in bytes) filled at termination time was:
                                                                                    Roll area...................... 16128
        Extended memory (EM)........... 418992800
        Assigned memory (HEAP)......... 0
        Short area..................... " "
        Paging area.................... 40960
        Maximum address space.......... 4294967295
                                                                                    By calling Transaction SM04 and choosing 'Goto' -> 'Block list',
        you can display an overview of the current roll and paging memory
        levels resulting from active users and their transactions. Try to
        decide from this whether another program requires a lot of memory
        space (perhaps too much).
                                                                                    The system log contains more detailed information about the
        termination. Check for any unwanted recursion.
        Determine whether the error also occurs with small volumes of
        data. Check the profile (parameter "rdisp/PG_MAXFS", see
        Installation Guidelines).
        Is the disk or the file system that contains the paging file
        full to the extent that it cannot be increased, although it has
        not yet reached the size defined in the profile? Is the
        operating system configured to accommodate files of such a
        size?
                                                                                    The ABAP processor stores different types of data in the SAP paging area
        . These include:
                                                                                    (1) Data clusters (EXPORT ... TO MEMORY ...)
           (2) Parameters when calling programs (SUBMIT REPORT ...),
            dialog modues (CALL DIALOG ...) and transactions
            (CALL TRANSACTION USING ...)
        (3) Internally defined macros (DEFINE ...)
                                                                                    Accordingly, you should check the relevant statements in a program
    that results in an overflow of the SAP paging area.
                                                                                    The EXPORT statement is particularly critical - specifically when many
    internal tables, possibly with different IDs, are written to the
    memory.                                                                   
    Kindly help
    Regards,
    Tajinder

    Hello,
    Here the parameters for concern are
    1.rdisp/PG_SHM
    2.rdisp/PG_MAXFS
    1.rdisp/PG_SHM :
    The value specifies the size of the paging buffer in 8KB blocks.
    A paging buffer is no longer required for SAP Memory Managment,
    because internal tables and lists are not stored in SAP paging.
    Default : 0
    2.rdisp/PG_MAXFS :
    This value specifies the size of the SAP paging file in 8KB
    blocks.  The paging file is used to store extracts and for
    Export to Memory.
    Aim:
    The paging file must be sufficiently large. It is not a problem
    if it is set to too large a size.
    Dependencies:
    Sufficient disk space
    You can try
    1.Optimize the code, to use less memory.
    OR
    2.Increasing the parameter rdisp/PG_MAXFS as per the availability of disk space.
    Hope this solves your problem.
    Regards,
    Edited by: Satish P on Oct 21, 2008 2:01 PM

Maybe you are looking for