Regarding capturing VF01 ERROR logs in a background job

Hi ,
We are running a background job that calls transaction VF01 via BDC .
CALL TRANSACTION 'VF01' USING   bdcdata
                          MODE    S
                          UPDATE N
                          MESSAGES INTO gt_messtab.
In some cases billing documents will not be generated. In such cases systems will throw message "Check the log "
After which we can check the error messages via Menu Edit>logs.
This error messages (stored in XVBFS internal table) need to captured in the job log i.e custom programme.
Unfortunately i could not found any user exits/BADIs that can help me in capturing message.
Can you please help me how can i solve this issue?
Thanks in advance
Manoj
Edited by: Manoj J on Nov 16, 2011 9:42 AM
Moderator message : Duplicate post locked, continue with original thread [How to capture error logs of VF01 in a background job log   |Re: How to capture error logs of VF01 in a background job log].
Edited by: Vinod Kumar on Nov 16, 2011 3:34 PM

Hi Manoj,
I had a similar problem.
I solved it selecting from VBSK the last record of the user regarding elaboration of invoices, and then calling f.m. 'VBSK_ALV_DISPLAY'.
Otherwise you could call directly transaction "V.21"
Hope this could help you
Andrea

Similar Messages

Is there any FM to generate spool request for error log of a background job

Hi,
I am going to create a program to create deliveries and do PGI. This program will be assigned to periodic background job.Now whatever errors are generated in program i have to send the error log to spool request.Is there any FM for generating spool request with this error log or how can this be done? Kindly provide sample code if possible.
Thanks.
Nimish Dongare.

Hi Nimish,
How are you doing, This is Shreekant working as ABAP developer, I sow your post in sdn forum, I have a similar requirement like I am changing the delivery taking some data from a flat file which is coming from other system and do PGI. If any error occurs during this process I need to capture it and present it as a report or create log file.. whichever is easier.
Please can u help me how did u achieved this functionality for your requirement?.. pls. can u share some details.
If u don mind, can u give me ur email id to communicate.
Thanks,
Shreekant

Capturing Application Error log from SXMB_Moni

Hi,
I wanted to capture the error information from Application error log from ECC sxmb_moni and forward that as email alert.
We have already alert configuration in place with alert category using standard variables. Was wondering if I have to capture application error log from sxmb_moni what would be steps involved. Please let me know if anybody has worked on this and appreciate your help on this.
Sample Error message from sxmb_moni of ECC system
MT_Fault
Error in Application System
Detailed Information
Process Order invalid
Thanks
Selvam
Edited by: Selvam_muthu on Jun 23, 2011 5:40 PM

Hi Selvam,
As the exception is raised in ECC system, alert cannot be trigger, alert will get trigger when there is a error in PI system. To raise a email, write additional code in ECC to trigger the e-mail with proper error content

Error in batch processing: background job cannot be scheduled

Error in batch processing: background job cannot be scheduled in transaction code jpmg0. How to resolve the same?

Hello,
Check system log and also check work process trace, to know the error.
I feel that it could be Authorization issue, you don't have sufficient authorization to do.
Hope this helps.
Regards
venkata
Edited by: venkata emandi on Sep 12, 2011 8:13 AM

Error log in VL10a background mode

Hi,
We are using the BADI - LE_SHP_DELIVERY_PROC ->DELIVERY_FINAL_CHECK to populate messages in the log. The messages are populated in the CHANGING parameter (ct_finchdel ) of the method and once an error is inserted in this table, the delivery creation is blocked. The error message is populated in the following way:
ls_finchdel-vbeln    = wa_it_xlikp-vbeln. " This is the delivery number
ls_finchdel-pruefung = c_99.
ls_finchdel-msgty    = c_e.
ls_finchdel-msgid    = c_zsx_idc.
ls_finchdel-msgno    = c_208.
insert ls_finchdel into table ct_finchdel.
But there is an issue when we try to create ONE delivery by giving TWO sales orders.
Out of the two sales orders provided, if one of the sales orders goes into error; the delivery should still be created with the other SO. But if the above method is used, all the sales orders which was used to create that delivery will go into error.
Can someone please suggest a solution for this? Basically what we are looking for is a method to update the individual SO in the error log. if all slaes orders which combines into one deliveyr goes into eroor, the delvery creation should be blocked. In other caeses a partial dleivery should be created with appropriate logs.
Best regards,
Rajalakshmi

The scenario mentioned by you cannot be handled through the BADI. The method DELIVERY_FINAL_CHECK is triggered just before saving the delivery irrespective of single Order/multiple order as reference. If you want to handle this you should populate the error message log based on the custom validation of all reference orders.

Capture odi error log files

hi
how to capture an odi error log file for an odi package?
Kindly suggest me in this.

ODI execution log is stored in the repository, so you could query it to retrieve the needed information. Also you could use substitution api getPrevStepLog() to retrieve error log (code & message) for the certain step. And for OdiOSCommand you could capture error log in the specified Error file.

Error in Control Framework: Background job failed

Hi Experts,
One background job failed with job log: Error in Control Framework in ECC 6.0 system; the job is supposed to produce a XML report. Can anyone please give some idea on this why it could happen? One SAP note 893534 has described same kind of issue but in CRM system. That note even cant be implemeneted in ECC 6.0. Any workaround? Is it a BASIS issue here?
Thanks & Regards,
SKB

Hello,
please check the variant. We had this problem, and when checking the variant I got a shortdump because the variant did not fit to the program (there were problems with subscreens in the selection screen). After adjusting the variant with program RSVARDOC_610 the variant was ok.
I can not check if this solved the problem because the job runs weekly, and the next job is on Monday. But give it a try...
HTH,
Jens Hoetger

Error in MRP Run- Background Job.

Hi PP Gurus,
I defined scope of planning for two plants and defined counter too. And set background job through Transaction code MDBT taking 24Hrs as Schedule selection parameter.
When I'm accessing MDBT after 24Hrs system is throwing following messages in Scheduling log:
1. Please check the destination for Parallel MRP (message no. MD251)
Diagnosis of Message:
No destination have been entered in Customizing or none of the destinations (application server) entered are active. In Customizing for MRP, you define the logical destinations (servers) to be used for parallel processing.
2. Job cancelled after system exception ERROR_MESSAGE (Message no. 00564)
Though I tried to enter to Customization through Message no. 1 but system is not allowing for it.
What could be the problem. No help is available through any OSS note also.
Please suggest the required solution in terms of Configuration or any other changes?
Thanks & Regards,
Abu Arbab

Hi,
Two more queries:
1. If I don't want to go for Parallel Processing MRP, I don't have to select 'Parallel Processing' in Transaction code MDBT variant. But when I'm trying to change it system is not allowing me. It's not allowing me to go further without selection of it. What could be the reason behind it? Either Customization problem or any other?
2. If set 'Parallel Processing destination' through Customization, system is giving only Development server as available destination and also Customization Request is getting generated. But the request is going to be transported to Production server. Since Parallel Processing destination was selected 'Development server' earlier and now MRP will run on 'Production server', it has to be changed to 'Production server'. But as already mentioned Customization Request will be getting generated and further it is freeze for Customization. How could get rid of these issues?
Please come back with prompt comments.
Thanks & Regards,
Abu Arbab

SQL error "-911" while running background job

Hi Experts,
We are getting the below runtime error while a background job is run.
SQL error "-911" when accessing table "DD02L".
Error Text of the Database: "SQL0911N The current transaction has been rolled
back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001 row=1"
The error is happening at a delete statement.
Please let me know what might be the reason of this error and how this can be resolved.
Thanks,
Jissa.

Hi,
The system is taking very long for processing delete statement.
can u send me ur code, so based on that i will give u some idea.
Ram.

Find errors logged from oracle batch job...

Hi,
I have a batch job that calls a procedure.. code is as under
begin
sys.dbms_job.submit(job => :job,
                      what => 'begin
                                   delete_stale_data;
                                    end;',
                      next_date => to_date('29-06-2006 05:33:28', 'dd-mm-yyyy h24:mi:ss'),
                      interval => 'sysdate+(30/1440)');
commit;
end;Now, how can i get to view the error messages if
1) procedure runs into an exception and hence job is not executed
2) if job runs into some problem due to which it is not completed..
Thanks,
JP

"Viewing errors" is the wrong term to use - it assumes that there are devices like STDERR and STDOUT in Oracle that is written to when an error occurs.
There are no such devices in Oracle. Oracle itself will record system related errors (and messages) to the alert log of the database instance. Custom PL/SQL code can also write to the alert log using an undocumented call - but it is a very poor idea as the alert log is for the DBA to deal with system errors. Not with someone's application errors.
The correct method is to implement an application logging PL/SQL interface (package) that allows applications to log errors and warnings and messages (including debug stuff). The basic method of this API implementation is to create a log table and write messages (from applications) to this table using autonomous transactions. The API call can also record the system date/time, the current PL/SQL stack trace, client session details, etc.
Using such an API, you would schedule the job as follows:
Method 1:
The job becomes broken after 16 repeated failures (the exception is re-raised in order for DBMS_JOB to deal with it).
sys.dbms_job.submit(job => :job,
what => 'begin
delete_stale_data;
exception when OTHERS then
APPLOG.CriticalError( 'Error occured running DELETE_STALE_DATA', SQLCODE );
raise;
end;',
next_date => to_date('29-06-2006 05:33:28', 'dd-mm-yyyy h24:mi:ss'),
interval => 'sysdate+(30/1440)');
Method 2:
The job will never break. The exception is supressed and DBMS_JOB will not know that any errors occurred:
sys.dbms_job.submit(job => :job,
what => 'begin
delete_stale_data;
exception when OTHERS then
APPLOG.CriticalError( 'Error occured running DELETE_STALE_DATA', SQLCODE );
end;',
next_date => to_date('29-06-2006 05:33:28', 'dd-mm-yyyy h24:mi:ss'),
interval => 'sysdate+(30/1440)');

Write the Error log from background Job to the Spool request

Hi ,
I have a situation where in i need to capture the error log of a Z program which runs as a background job and write that log into the spool request. My Z program calls runs RSEINB00 program using the SUBMIT statement. When this Job fails the error log can be seen in SM37. But i need this error log to be sent in to a spool.
I can read the error log using the BP_JOBLOG_READ FM and can also create a spool using the RSPO_SPOOL_OPEN FM.
The problem is, when the Submit statement executes, due to internal valdation in the RSEINB00 program the program terminates. Due to this it is not able to perform the SY-SUBRC Check and thus doesn't read the log.
Can anybody suggest me how to overcome this problem. I am attaching the code for your refernece.
SUBMIT RSEINB00
       USING SELECTION-SET 'TEST2'
                       TO SAP-SPOOL
                       LIST NAME 'LOCL'
                       IMMEDIATELY space
                       KEEP IN SPOOL 'X'
       AND RETURN.
<b>If sy-subrc <> 0.</b>
             CALL FUNCTION 'BP_JOBLOG_READ'
              EXPORTING
                CLIENT                      = SY-MANDT
                JOBCOUNT                    = i_tbtco-jobcount
                JOBLOG                      = i_tbtco-joblog
                JOBNAME                     = i_tbtco-jobname
               TABLES
                 JOBLOGTBL                   = l_joblog
             IF SY-SUBRC <> 0.
             else.
                message i002 with l_joblog-msgv1.
             ENDIF.
<b>
ENDIF.</b>
Rgds,
Kewal
P.S. : any other approach to solve this problem will be appreciated too and the points will be rewarded suitably.

If I select a job in SM37 and I click on "spool" I get a list with separate spool entries for each of the steps, e. g.
Programmname/Kommand   Programmtyp   Spoolliste
Z_MM_STAT_UPDATE_WERK ABAP             1707445
ZSLEEP                 Ext. Kommando
Z_MM_STAT_UPDATE_WERK ABAP             1707459
ZSLEEP                 Ext. Kommando
Z_MM_STAT_UPDATE_MARA ABAP             1721423
ZSLEEP                 Ext. Kommando
Z_MM_STAT_UPDATE_WERK ABAP             1721437
Z_MM_STAT_UPDATE_MARA ABAP             1721446
Z_MM_STAT_UPDATE_WERK ABAP             1721447
Z_MM_STAT_UPDATE_VKORG ABAP             1721471
ZSLEEP                 Ext. Kommando
Z_MM_STAT_UPDATE_VKORG ABAP             1721521
ZSLEEP                 Ext. Kommando
Z_MM_STAT_UPDATE_VKORG ABAP             1721816
It's in German but I'm sure you get the idea. For each Z_MM_STAT_UPDATE and variant I have a separate spool list that I can display.
Markus

Error logs in job releases forecast from DP to SNP-"Matl does not exist"

Hi Everyone,
I am facing error logs in the batch job which releases forecast from DP to SNP
Forecast release job - Weekly - Through background job
Forecast category - FA
Error 1: - Characteristic combination appears on batch job log with an error that
"GMC does not exist " Even though it exist in R/3 and APO
All products with error message "Product does not exist" from do exist and have Forecast in Product View
Error 2: - Deleted KCC keep showing up on the Demand Forecast release job log as errors even though they are invalid KCC and were deleted previously. How do they get removed from error log so they don't get created again
Material does not exist on the APO Product Master, in R3 there is a delete flag and the MRP type is set to X1 ,it does not exist in the APO Product Master and does not exist in R3.
Request you to kindly provide any way forward which may be causing error logs of the job
Thanks in advance,
Mrigendra Sharma

Hi Mrigendra,
Please re-initialize the SNP planning area (program : /SAPAPO/TS_PAREA_INITIALIZE) and then check the consistency by executing the program: /SAPAPO/TS_LCM_CONS_CHECK. If you observe any inconsistency in the log/spool, then re-run the program: /SAPAPO/TS_LCM_CONS_CHECK to observe all green.
It is recommended to run the consistency program after any master data change. The initialization program should be run at least weekly.
Try transfering the data again from DP to SNP to see if the error reappear.
Hope this helps.
Regards,
Nawanit

DML Error logging for Update statement

Hello,
I am facing a problem with regard to DML Error logging with Update statement .
oracle : 10.2
I am executing following DML update:
BEGIN
UPDATE
table_1 a
SET a.Exp_DATE =a.EFF_DATE
WHERE a.col_a1 != (SELECT b.colb1
                     FROM table_2 b
                     WHERE a.msisdn =b.msisdn )
LOG ERRORS INTO table_1_ERR REJECT LIMIT UNLIMITED;
END ;    I was expecting that "ORA-01427: single-row subquery returns more than one row" would be captured in LOG error table "table_1_err"
but instead I got run time error and whole dml was rolled back.
Please let me know whether this exception is not captured by DML error logging.
Thanks,
Abhishek

*Oracle logs the following errors during DML operations:** Column values that are too large.
* Constraint violations (NOT NULL, unique, referential, and check constraints).
* Errors raised during trigger execution.
* Errors resulting from type conversion between a column in a subquery and the corresponding column of the table.
* Partition mapping errors.
>
http://download.oracle.com/docs/cd/B19306_01/server.102/b14223/transform.htm#sthref777

HI All Capturing the error records in an internal table

Hi All,
         I am retrieving the data from application server .
        My requirement is to :
     Check if the Measurement Point Id provided in the file is a valid one or not. Query the table EUITRANS by passing the Measurement point Id in the EXT_UI field. If the query is successful, then proceed to next step. If not, log it in the error log with error message DM-001 and proceed with the next Measurement point id.
so i nee the code for capturing the error log with error message.
pls provide me ASAP.
Thanks&Regards,
Bharat

Hi,
if you like do display all messages online have a look at FM:
'MESSAGES_INITIALIZE'
'MESSAGE_STORE'
'MESSAGES_SHOW'
If you want to write application log look at function group SBAL modules BAL_LOG*. There is also a good documentation in SAPDOCU..
Kind regards,
HP

Background job SWFSLSDLEX cannot be scheduled (error )"

Hi All ,
i got the following error ,
when i try to customize the SWU3 " Schedule background job for dead line monitoring ".
The error is :
"Work item -: Background job SWFSLSDLEX cannot be scheduled (error )"
And the Error log says :
Refer to your workflow system administrator.
The specified error number should indicate possible reasons for the error. It is possible that the system is in an inconsistent state. The scheduled start of the specified background job must be compared with the minimum date/time of all work items in table SWWDHMIN. It may be necessary to delete the scheduled background job by hand and reschedule it by calling report RSWWDHEX.
Apparently i dont see any table SWWDHMIN.
Thanks!
Richard A

The issue is solved by adding start profile and instance profile to operation modes.
Many thanks to my BASIS Guys for solving it !
Richard A

Regarding capturing VF01 ERROR logs in a background job

Similar Messages

Maybe you are looking for