10 Replies Latest reply: Aug 19, 2013 11:47 AM by balaram reddy RSS

error in post processing report AGR_XPRA_REGENERATE_SAP_NEW

balaram reddy
Currently Being Moderated

Hi Friends,

 

can you please help me , how to correct below error


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR731XPRA90000124.EBS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2 EPU129      End of subsequent processing... "20130817200332"
3 ETP000
3 ETP000 **************************************************
3 ETP000
2 EPU115XReport "AGR_XPRA_REGENERATE_SAP_NEW" started: "20130817200332"
1AETR012XProgram terminated (job: "RDDEXECL", no.: "20033100")
1AEPU320 See job log"RDDEXECL""20033100""EBS"
1 ETP111 exit code           : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<

XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.

Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<

 

any one can you please help me, what are the possibilities  lock/unlock  during the upgrade.

 

Thanks & regards,

Balaram

  • Re: error in post processing report AGR_XPRA_REGENERATE_SAP_NEW
    Gaurav Kumar Pandey
    Currently Being Moderated

    Hello,

     

    2 EPU115XReport "AGR_XPRA_REGENERATE_SAP_NEW" started: "20130817200332"

    1AETR012XProgram terminated (job: "RDDEXECL", no.: "20033100")

    1AEPU320 See job log"RDDEXECL""20033100""EBS"

    1 ETP111 exit code           : "12"

     

    So the Job failed. Check the reason for the failure of the JOB. Check the Job log in the SM37 transaction.

    Generally it failes with the Syntax error. Provide the dump here.

     

    Reagrds,

    Gaurav

    • Re: error in post processing report AGR_XPRA_REGENERATE_SAP_NEW
      balaram reddy
      Currently Being Moderated

      Hi Gaurav,

       

      Yes , you are correct , i have informed to ABAP team about this.

       

      do we need to to take any action from our end??

       

      ABAP runtime error details:

       

      The current ABAP program "SAPLSUSB" had to be terminated because it has

      come across a statement that unfortunately cannot be executed.

       

      The following syntax error occurred in program "SAPLSUSD " in include

        "YUSER_COMMAND_USER============E " in

      line 46:

      "Field "GT_USERS_COMPLETE" is unknown. It is neither in one of the spec"

      "ified tables nor defined by a "DATA" statement. "DATA" statement."

      " "

      " "

       

      The include has been created and last changed by:

      Created by: "RSU.EXT "

      Last changed by: "JKR.IBS "

      Error in the ABAP Application Program

       

      The current ABAP program "SAPLSUSB" had to be terminated because it has

      come across a statement that unfortunately cannot be executed

       

      Right now system is locked during the upgrade , is there any possibilities to unlock the system , if the system unlocked , any disadvantages?

       

      i am able to login using  only with DDIC user , but we can't unlock the system using this user right?

      please help me.

       

      regards,

      Balaram

      • Re: error in post processing report AGR_XPRA_REGENERATE_SAP_NEW
        Rishi Abrol
        Currently Being Moderated

        Hi,

        Below note states the option to lock and unlock sap system during SAP upgrade.

         

        Note 1653003 - SNC 5.10:error in XPRAS_UPG during update to NW 7.31

         

         

        Why sap has the processes of locking the system so that no more changes can be done in sap system. The changes can be lost or cause inconsistency.

         

        Above note explain you how to lock and unlock the system.

         

        Which phase are you in the SUM tool.

         

        And have your developers customised sap standard? If yes dint you get any of this object in SPDD if you have crossed that phase.

         

        Did you try to continue and see what happens.

         

        How long was the job running which led to this dump.

         

        Thanks

        Rishi Abrol


        • Re: error in post processing report AGR_XPRA_REGENERATE_SAP_NEW
          balaram reddy
          Currently Being Moderated

          Hi Rishi,

           

          Thanks for your  valuble answer. we are getting different error also getting different run time error.

           

          please find the below detauils:

           

          SM37: Background job details:

           

          RDDEXECL                              DDIC          Canceled 17.08.2013 18:00:20

           

          Job log overview for job:    RDDEXECL / 18002000


          Date       Time     Message text

          17.08.2013 18:00:20 Job started
          17.08.2013 18:00:20 Step 001 started (program RDDEXECL, variant , user ID DDIC)
          17.08.2013 18:00:20 All DB buffers of application server ebs0v were synchronized
          17.08.2013 18:00:26 Internal session terminated with a runtime error SYNTAX_ERROR (see ST22)
          17.08.2013 18:00:26 Job cancelled

           

          ST22 - ABAP Runtime error:

           

          Category               ABAP Programming Error
          Runtime Errors         SYNTAX_ERROR
          ABAP Program           SAPLSUSD
          Application Component  BC-SEC-USR-IS
          Date and Time          17.08.2013 18:00:26

           

          Short text
               Syntax error in program "SAPLSUSD ".

           

          Error analysis

              The following syntax error was found in the program SAPLSUSD :

              "Field "GT_USERS_COMPLETE" is unknown. It is neither in one of the spec"

              "ified tables nor defined by a "DATA" statement. "DATA" statement."

              " "

              " "

          Information on where terminated
              Termination occurred in the ABAP program "SAPLSUSB" - in "UPD_USR10".
              The main program was "AGR_XPRA_REGENERATE_SAP_NEW ".

              In the source code you have the termination point in line 201
              of the (Include) program "MS01CD11_UPD_USR10".
              The program "SAPLSUSB" was started as a background job.
              Job Name....... "RDDEXECL"
              Job Initiator.. "DDIC"
              Job Number..... 18002000

           

          We have informed to ABAP team , they are working on this .. any actions need to take from our end??

           

          i have a question here , can we unlock the system in this phase ????  any side effects if we unlock the system??

          regards,

          balaram

      • Re: error in post processing report AGR_XPRA_REGENERATE_SAP_NEW
        Gaurav Kumar Pandey
        Currently Being Moderated

        Hello,

         

        XPRAS issues are mainly application issue so unless we have information from the applictaion team about their finding it hard to check it further from the basis side. Please let us know what your developers say.

         

        To unlock the system during the XPRAS_AIMMRG phase

         

        tp unlocksys command should be used. for the complete command please check the Upgrade Guide.

        Command for the shadow system will not work as there in no shadow system during this phase.

         

        Regarding the changes, it depends what changes are you making. I have seen people unlocking the system to apply the changes of a note (valid for their system) manually. But please dont make any other changes as it can cause further issues. Please check with your application+Basis team or SAP before making any changes.

         

        I hope it helps.

         

        Reagards,

        Gaurav

        • Re: error in post processing report AGR_XPRA_REGENERATE_SAP_NEW
          balaram reddy
          Currently Being Moderated

          Hi Gaurav,

           

          we have received below reply from application team..

           

          We have analyzed the code. The issue is due to an implicit enhancement YUSER_COMMAND_USER implemented in this include program LSUSDF01. This implicit enhancement is using a global variable which is currently not present in the latest version of the program. Currently we are unable to execute any of the relevant programs to analyze further. So to proceed further we have to undo the implementation YUSER_COMMAND_USER and execute the relevant report to understand the behavior of the latest code.

           

           

          regards,

          balaram

Actions