BCD_OVERFLOW CX_SY_CONVERSION_OVERFLOW /VIRSA/ZVFATBAK

Hi guys,
I have my FF user executing transaction SE38 and upon the execution, the background job /VIRSA/VFATBAK ended in status "Canceled". In the log, its shows the below description for the background job cancallation.
Short text
Overflow during an arithmetic operation (type P) in program "/VIRSA/ZVFATBAK".
What happened?
Error in the ABAP Application Program.
The current ABAP program "/VIRSA/ZVFATBAK" had to be terminated because it has come across a statement that unfortunately cannot be executed. A value is too long for a calculation field.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not caught in
procedure "GET_SE38_CHANGES" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated. The reason for the exception is:
In the current arithmetic operation with operands of type P an overflow has been detected. Possible causes are:
1. The result field of type P is too small to store the result.
2. The result or an intermediate result has more than 31 decimal places.
How to correct the error
Maybe the result field - if still possible - must be defined larger.
Maybe the current process can be divided into separate units in a way that only smaller values occur.
Anyone shares this experience before and if you have resolve it via the proposed way to coorect the error?
If you have successfully executed the corrections, can you pls share on the steps to be taken?
Thanks.
Raymond

An calculation causes an exception because the result variable is too short to store the result.
You can 2 things to solve the problem :
- Add an error handling mechanisme CATCH or TRY to get the exception and act on it (message or something else)
- change the result variable so that it can store the resulting value
regards,
hans

Similar Messages

ABAP report /VIRSA/ZVFATBAK run very long on backend

Hello experts,
For ABAP report /VIRSA/ZVFATBAK which runs in the backend system, normally how long would it take to finish? Because now the duration for the report is already 2k++ seconds and its still running in our test system, while the report scheduled in our development system only uses 1 or 2 secs to finish.
Any idea why is it taking that long in a test system?
Appreciate the replies, thank you in advance.

Thank you for the note sabita! Its really helpful.
One question regarding the sapnote, it mentioned STAT collector job, is this a standard job?
If yes, below are the standard collector jobs which is scheduled in the system, which would it be?
SAP_COLLECTOR_FOR_JOBSTATISTIC
SAP_COLLECTOR_FOR_NONE_R3_STAT
SAP_COLLECTOR_FOR_PERFMONITOR

Run VIRSA/ZVFATBAK to generate missed log

Hello experts, we had an upgrade a couple weeks ago and we had to put the VIRSA/ZVFATBAK job on hold. Because of this we have a couple of FF logons missing data. We have the "BACKGROUND JOB WAS NOT SCHEDULED/LOG & FILE NOT YET GENERATED" error. Usually I can run job immediately after the upgrade and gather this missed data, however this time we forgot and now trying to go back 3 weeks ago.
I thought since I can still see the data in STAD (ST03) I should be able to get VIRSA/ZVFATBAK to run and find the data. This is not the case this time. Can anyone confirm its too late to generate these missed logs?
Thanks
Dave Wood

Hi David,
If you see that logs are missing for certain date and time then you can run the report /VIRSA/ZVFATBAK with date and time for which logs where missing, see sap note - 1142312 (read this to understand what start & read time should be given to run the report)
Please be informed that the report will fetch data from STAT and CDHDR, CDPOS only if the data exists in these for the given date and time. If the data has been purged from STAT for that period then its not possible to get the logs.
Also note this point - As per design, manual FF log update considers only the firefighter ids
assigned to the user who is triggering the update through the firefighter dashboard. Whereas the scheduled background job considers all the FFIDs for a particular time period.
Best Regards,
Sirish Gullapalli.

Fire Fighter job /VIRSA/ZVFATBAK is finishing in zero sec

Hello Everyone,
In my Solution Manager Production system FF job /VIRSA/ZVFATBAK is finishing in zero sec.
Log:
Date       Time     Message text                                                                        Message class Message no. Message type
01.04.2014 02:30:33 Job started                                                                              00           516          S
01.04.2014 02:30:33 Step 001 started (program /VIRSA/ZVFATBAK, variant &0000000000002, user ID DE15386)      00           550          S
01.04.2014 02:30:33 Job finished                                                                             00           517          S
Please suggest what could be thepossible reason.
I am not able to get FF logs. So is this job the reason for no logs?
Thanks,
Ashish Gaurav

Hi Tang,
Did you check the configuration settings for both the FF IDs.
Also, as a trail and error, to isolate the issue, can you check using only the 2nd FF ID for which the log was not sent. Ensure that the 1st FF ID is not used. This way you can identify whether the issue is with the FF ID or the configuration.
Regards,
Raghu

/VIRSA/ZVFATBAK stopped after upgrade

Hi,
We are currently running the GRC compliance report to view log of Fire-fighter users and the transactions they have been using. This report is sent out to the FF owners every month.
We upgraded our system from 4.7c to ECC6 in early May and since then the /VIRSA/ZVFATBAK job has not been running and collecting the log data.
The /VIRSA/ZVFATBAK is now setup correctly again but we were hoping to run the job so it would collect the data from the previous month, up to the 9th of June.
I have been trying various techniques and selection parameters but have been unsuccessful.
Can anyone tell me any way of running the /VIRSA/ZVFATBAK job so that when I run report next week it will have all the data as far back as the 9th of June?
Any help is much appreciated,
Colm

Hi Michael,
Thanks for the reply. I will talk to the basis team about this but I probably should mention that on Thursday evening I was able to run the job for the 6th and 5th of July successfully. I had to go to a meeting then and when I came in on Friday morning the job was no longer working.
I wonder is it something to do with my selection screen?
If I want to gather all the data for the 2nd of July I am running it with a Start Date of 02.07.2010, a start time of 23:59:59 and a read time of 23:59:58.
As I said this worked for the 5th and the 6th but no longer works for me and there were FF enteries on the 2nd.
Many Thanks,
Colm

/virsa/ZVFATBAK background job

Hello,
SAP 4.6c.
/virsa/ZVFATBAK is running currently in the system at specific periods.
Should this job be running on each application server of the system?
Or just a one time schedule in SM36 for the entire system is good.
Kindly advise.
Thanks.
Prasanna

Hello,
Thanks for the reply.
Recently, the frequency of the job was switched from hourly to once every 4 hours.
The firefighter logs are not getting generated.
I dont see anyother changes that have been made.
1039144-Is this note the solution?
thanks.
Prasanna

Log storage time of /VIRSA/ZVFATBAK

Hi Guys,
Can any one let me know how many days firefighter stores the logs generated by the background job /VIRSA/ZVFATBAK.
I have given the user Firefighter ID from june 12th to june 19th. can I generate a firefighter log on june 28th.
Kindly respond.

Hello Rahul,
The Data which is retrieved by the /VIRSA/ZVFATBAK program is stored in Firefighter tables. If the problem was able to retrieve the data for that particular date successfully from SAP System then it will be available in the logs for review as long as it is in Firefighter tables.
Regards, Varun

Job cycle for Prog. /VIRSA/ZVFATBAK for GRC

Hi Experts,
I want to know JOB cycle for Prog. /VIRSA/ZVFATBAK for GRC.
Please advice the matter.
Regards,
Gaito

Hi,
This job scheduled every hour.
Check SAP Note 1039144 - Superuser job is not completing or is not retrieving data
Thanks
Sunny

/virsa/vfatbak and the report it generates

The /virsa/vfatbak report runs regularly. The controllers are telling me that they used to receive a detailed log report in their email, but they've stopped receiving this report. When I go into firefighter and look at the log, there is sufficient detail, and yet the email to the controller only shows that someone logged into their firefighter ID.
I looked and didn't find any setting that was misconfigured/not configured. I was wondering if you could point me in the right direction.
Thanks,
Santosh

UPDATE
While trying to get this report to send emails as I need it to, I found that my /virsa/zvfatbak began to cancel spontaneously. So now, every hour, a bunch of emails get sent out by DDIC saying that the job has failed.
On further investigation, I found the following short dump:
Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time          08.09.2010 15:49:42
Short dump has not been completely stored (too big)
Short text
     No more storage space available for extending an internal table.
What happened?
     You attempted to extend an internal table, but the required space was
     not available.
I found a note numbered 1039144, but that is in regard to this job never terminating. Clearly, this job is now running out of space, as can be inferred from this error.
I had BASIS run this job on a different app server, and it finished, and then it continued to run successfully for an additional 4 hours, after which it began to fail.
Please let me know your thoughts.
Thanks,
Santosh

Problem with Firefighter logs after upgrade to 5.3 from 5.2

Hello Gurus ,
just for 2 weeks we are running GRC 5.3 , which we updated from the 5.2 version .
Unfortunately i could not make all the possible tests in one day and after i didnt check the FF reports .
So after 10 days..after solving some issues from the upgrade i realized that in SPM (Superuser Priviliege Management ) we have a problem as well .
We cant perform anymore reason / activity reports because the data are empty.By empty i mean all the entries users made dissapeard. I searched the two tables that normally should have the data (/virsa/zffcdhdr and the STXH ) but with no luck .
The other problem is..that after the upgrade to 5.3 from 5.2 the grcservice user that is responsible for the job /VIRSA/ZVFATBAK didnt had enough authorization to complete the job , thing that before worked fine .
So for 10 days the job didnt run and when i run the log report i see for every FFID the message "BACKGROUND JOB WAS NOT SCHEDULED/LOG & FILE NOT YET GENERATED"
When i look directly in the tables CDHDR and CDPOS i can see the data that the log needs.
But how can i reconstruct the FF log with this data ? Because when the auditor comes i would like to have the complete logs.
thank you all for the support
Cheerz ,
david

Hi David,
Please go through the SAP Note [1143639|https://service.sap.com/sap/support/notes/1143639] (and subsequent Notes). I hope it is of help, at least partially.
Best regatds,
Feri
Edited by: Ferenc Orosz on Apr 2, 2009 2:43 PM

Can I generate backdated FF logs?

Hi Experts,
We have issue, because of system maintenance hourly run /VIRSA/ZVFATBAK job didn't run on perticular date and time. Now when we pulling FF log it gives message "Background Job was not scheduled/log & file not yet generated" is there in any case can we regenerate FF log for that perticular date by externally running /VIRSA/ZVFATBAK job? Is there any solution for this situation?
Thanks in advance for reply,
Yash

Hi Yashwin,
Kindly refer to Notes "1563226"for info on how to recover the backlog data.
The Most Important thing being the STAD data should be still available in the System. In Production systems there is a periodic Basis Background job that deletes data older than a set period this can range normally from a fortnight to a month. Kindly check with basis team and recover the data.
All the Best.
Rgds
Ganesh.S
P.S: Incase your query is resolved, kindly mark this thread as 'Answered' and award points to the 'Contributors'

SPM Reporting - Log reports display on front end

Hi,
We have implemented GRC 5.3 and have an issue on the SPM reporting through the front end.
We have done config in dev and have the following jobs running in the background every 1 hour:
1. /VIRSA/ZVFATBAK
2. /VIRSA/ZVFAT_LOG_REPORT
3. /VIRSA/ZVFAT_V01
4. /VIRSA/ZVFAT_V03
The log on the back-end displays all activity of FF user, but when going to the front end I seem not to get any reports to display.
We have created the connectors via the config page, but when trying to drill through the selection criteria we found that the FF user does not come up as a selection variable. We see the system defined though.
Any suggestions how to get the reporting to display on the front-end?
Kind Regards, Melvin

Santosh,
You should only need the /virsa/zvfatbak job running in the background. However, if the emails are not triggered for the log reports, you may wish to schedule the /virsa/zvfat_log_report program to run after completion of /virsa/zvfatbak as that is the program which actually sends the notifications.
Regarding the RFC user, check the authorisations held in the Firefighter Administrator role as those will not be too far away!
Simon

Firefighter Configuration

Hi Experts,
For Firefighter configuration, do we need to define all the paramters with YES or NO value OR we can leave the one which we dont require, e.g "Assign FF Roles Instead of FF IDs" - we dont need this, so still do we need to make an entry for this paramater with value NO.
What is we define both the paramters "Send Log Report Execution Notification" and "Send Log Report Execution Notification Immediately" ?
FF reads CDHDR table for the changes, how can we find out which all changes would be covered in that - i mean does the RFC connection creation, deletion and change will be recorded ?
Thanks
Davinder

Hello Davinder,
For the particular parameter you mentioned in this post "Assign FF Roles Instead of FF IDs" the default value is NO.
By default the table logging is ON for most of the tables but not all. For those tables for which table logging is not ON the data will not be captured in STAD and thus will not be fetched by firefighter.
You can contact your basis admin to check if table logging is ON for a particular table or not. If the operation you performed did not get captured in STAD then the table logging for that table might not
be active.
Regarding the 2 parameters "Send Log Report Execution Notification" and "Send Log Report Execution Notification Immediately" you can refer to the information available in the configuration guide of
AC5.3. Here is what these are all about:
1. Send Log Report Execution Notification - This parameter specifies whether log reports that contain information about Firefighter activity are emailed to controllers. If you set this to YES, then the report will be
                                                                sent to controller otherwise if you set this one to NO then the report will not be sent at all.
2. Send Log Report Execution Notification Immediately - This option specifies whether the log reports are sent to the controllers as soon as the background job (/VIRSA/ZVFATBAK) is executed or at
a predefined date and time. To send log report email notifications to the controller inboxes as soon as the /VIRSA/ZVFATBAK job runs, set
this parameter to Yes. If you plan to receive the job at regular intervals, schedule the job /VIRSA/ZVFAT_LOG_REPORT at regular intervals,
and set this parameter to No.
Regards,
Varun

FF log issue.

Hi Experts,
Our FF log job /VIRSA/ZVFATBAK runs hourly, without varient and with same timezone of A/P server batch user ID as per SAP recommendation. It generets FF logs perfectly. Inbetween due to maintenance of our batch Job scheduler software it was stopperd for 6 hours and job didn't run. Now for that duration when I am taking FF logs it gives me message "BACKGROUND JOB NOT SCHEDULED/FILE NOT YET GENERATED...". Is there any way can I generate/capture FF logs from STAT for that duration? I tried to run /VIRSA/ZVFATBAK externaly using SA38 doesn't works, although I can see data using SM20N for that duration.
Thanks,
Yashwin

Hello,
This maybe can help you...
GRC 5.3 SPM Log Report
Good luck!

Best SAP Security Practices Print,file,job schedule, archiving

Hello All, i would like to know in your experience which will be the best practices for Security for this list below:
- Printer security (especially check printing)
- File path security for export/import
- Best Practice for Job Schedule and Spool file
- Archiving process (I can't think of any specific to security, other than Security Audit Logs)
Are there any special transactions/system settings/parameters that must be on place in order to hard SAP Systems?
Do you have any documentation related?
I mean for example Job, spool i think user must just only run heir own jobs,and se their own works for printing, is there a paremeter to athenticate Prints/user, etc.
Please let me know your comments about those related issues.
I appreciate your help.
Thanks a lot.
Ahmed

Hi,
PFCG_TIME_DEPENDENCY
This is best to run once a day mostly after 12.01 am as it removes the roles which are invalid for current date. As role assignment is on date basis there is no advantage of running it hourly.
/VIRSA/ZVFATBAK
This is for GRC 5.3, and this job is to collect FFID logs from backend to GRC repository, so if you have frequent FFID usage you can schedule it hourly or for every 30 min too, if you have enough bandwidth in your server to get the latest log report. or else you can have it scheduled for twice a day too, so it is purely based on your need.
Hope this helps.
BR,
Mangesh

BCD_OVERFLOW CX_SY_CONVERSION_OVERFLOW /VIRSA/ZVFATBAK

Similar Messages

Maybe you are looking for