ABAP Report Errors in Production

[Former Member]

Hi All,

After checking everything moved the ABAP report to the production , in production if you get any errors or if reports goes for dump, what we have to do.

As per my knowledge we have to move back to the development system and we have to rectifying errorsand again moved to the production.if i am wrong please correct me.

Note: This is not a interview question

Thanks,

GAL

[Former Member]

Hi All,

After checking everything moved the ABAP report to the production , in production if you get any errors or if reports goes for dump, what we have to do.

As per my knowledge we have to move back to the development system and we have to rectifying errorsand again moved to the production.if i am wrong please correct me.

Note: This is not a interview question

Thanks,

GAL

[Former Member]

Yep Correct the program and move it again.

Thanks,

Sai

[Former Member]

hi,

After Transporting the object also, The object is available in Development Server, so no need to moved

back any Object from production to Development.

we release only the transport request.

After done the modifications in the production server while saving it will ask the request again. so new request will generate. we need to transport this request.

[Former Member]

Hi Gal

Due to bulk data selecting in the production server.You may get dump error.At this time yous wants to change your logic according to the data.

In T.Code ST05 - Performance Analysis .

By Using these t.code we can analysis the process time of the report.

By

Pari

[Former Member]

Hi All thanks for quick reply

Do we have any other options like rectifying errors in Production Itself , instead of moving back and forth

[Former Member]

It may be possible depending on the production system settings, but is not advisable. You shouldn't be transporting directly from DEV to PRD anyway. You should be testing in QA first.

Rob

[Former Member]

In some cases, like when a report is run for a large set of data, it might go for a time out dump. For such cases, the profile parameters can be altered in Production itself, for the report to continue execution. In case there are issues with the coding (processing logic, incorrect validations, etc.,) you will have to rectify it in DEV and move it to QA for further testing. Only after that it is advised to move the object to production system.

[Former Member]

Hi,

Rob is correct. Check it in the QAS and then move it to PRD. If you have any errors in the program, Correct the program in DEV put it in a new TR and move the TR to QAS and then PRD.

Thanks,

Sai

[vijy_mukunthan]

hi GAL

If you have authorization then check st22 to find the error. As every one suggested in the development create new request for the program move to quality and check what type of input is given by the client give the same input in the quality also if your getting dump in the qulity itslef you have reprogram the logic.

Regards

vijay

[Former Member]

check your internal table data, how many records are coming to your internal table , may be ur using standard internal table ..., if data is very huge its goin to dump....