Background job SAP_PERIODIC_ORACLE_SNAPSHOT got cancelled.

Hi All,
Background job SAP_PERIODIC_ORACLE_SNAPSHOT got cancelled.
Im SM37 the log shows that the job has been cancelled because 'No Vendor Specified'
Is that any variant needs to be specified.
Please help me on this.
Thanks & Regards,
Gopi L.

Hi,
Please check the SM21 log and the corresponding work process trace (dev_wX - X refers to the work process number used by the job, can be seen from SM21) for errors.
Best regards,
Warren

Similar Messages

SAP_COLLECTOR_FOR_PERFMONITOR background job cancelled in SM37

Dear all ,
One of the scheduled background job has been cancelled .
Kindly check the below loga and Background job details .
Job name        SAP_COLLECTOR_FOR_PERFMONITOR
Job class       C
Status          Canceled
(ABAP Program
Name           RSCOLL00
Variant
Language       EN)
Job Log :
30.05.2010 06:20:32 Job started
30.05.2010 06:20:32 Step 001 started (program RSCOLL00, variant , user ID DDIC)
30.05.2010 06:20:37 Clean_Plan:Cleanup of DB13 Plannings
30.05.2010 06:20:37 Clean_Plan:started by RSDBPREV                       on server PRDCIXI
30.05.2010 06:20:38 Clean_Plan:Cleaning up jobs of system IRP
30.05.2010 06:20:39 Clean_Plan:finished
30.05.2010 06:20:43 ABAP/4 processor: DBIF_RTAB_SQL_ERROR
30.05.2010 06:20:43 Job cancelled
Kindly suggest

Dear all ,
Kindly check the ST22 error logs .
Short text SQL error occurred in the database when accessing a table. What happened? The database system detected a deadlock and avoided it by rolling back your transaction. What can you do? If possible (and necessary), repeat the last database transaction in the hope that locking the object will not result in another deadlock. Note which actions and input led to the error. For further help in handling the problem, contact your SAP administrator . You can use the ABAP dump analysis transaction ST22 to view and manage termination messages, in particular for long term reference. Error analysis The database system recognized that your last operation on the database would have led to a deadlock. Therefore, your transaction was rolled back to avoid this. ORACLE always terminates any transaction that would result in deadlock. The other transactions involved in this potential deadlock are not affected by the termination. Last error logged in SAP kernel Component............ "SAP-Gateway" Place................ "SAP-Gateway on host PRDCIXI / sapgw01" Version.............. 2 Error code........... 679 Error text........... "program prodoradb.sapccmsr.99 not registered" Description.......... "TP prodoradb.sapccmsr.99 not registered" How to correct the error Database error text........: "ORA-00060: deadlock detected while waiting for resource" Internal call code.........: "[RTAB/UPD /MONI ]" Please check the entries in the system log (Transaction SM21). If the error occures in a non-modified SAP program, you may be able to find an interim solution in an SAP Note. If you have access to SAP Notes, carry out a search with the following keywords: "DBIF_RTAB_SQL_ERROR" " " "RSHOST3M" or "RSHOST3M" "PUT_LOGBOOK" If you cannot solve the problem yourself and want to send an error notification to SAP, include the following information: 1. The description of the current problem (short dump) To save the description, choose "System->List->Save->Local File (Unconverted)". 2. Corresponding system log Display the system log by calling transaction SM21. Restrict the time interval to 10 minutes before and five minutes after the short dump. Then choose "System->List->Save->Local File (Unconverted)". 3. If the problem occurs in a problem of your own or a modified SAP System call.......... " " Module............... "gwr3cpic.c" Line................. 1835 The error reported by the operating system is: Error number..... " " Error text....... " "
for detail log.
System environment
SAP-Release 700
Application server... "PRDCIXI"
Network address...... "10.54.145.32"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "000184CAD400"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 8
Shortdump setting.... "full"
Database server... "PRODORADB"
Database type..... "ORACLE"
Database name..... "IRP"
Database user ID.. "SAPSR3"
Terminal................. " "
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 7 2010 21:00:49"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 246
Patch text.. " "
Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 1217248
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 1050520
MM Free. 146024
and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "4BFF227871E00187E10080000A369120"
In the source code you have the termination point in line 521
of the (Include) program "RSHOST3M".
The program "RSHOST3M" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 02033500
In the source code you have the termination point in line 521
of the (Include) program "RSHOST3M".
The program "RSHOST3M" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 02033500
Program............. "RSHOST3M"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
rmation on where terminated
Termination occurred in the ABAP program "RSHOST3M" - in "PUT_LOGBOOK".
The main program was "RSHOST3M ".

Background Job cancelling with error Data does not match the job definition

Dear Team,
Background Job is getting cancelled when I run a Job on periodically but the same Job is executing perfectly when I run it manually(repeat scheduling) .
Let me describe the problem clearly.
We have a program which picks up files from an FTP server and posts the documents into SAP. We are scheduling this program as a background Job daily. This Job is running perfectly if the files contain no data. But if the file contains data the JOb is getting cancelled with the following messages.
And also the same Job is getting executed perfectly when repeat scheduling is done ( even for files with data).
Time     Message text                                                                       Message class Message no. Message type
03:46:08 Job PREPAID_OCT_APPS2_11: Data does not match the job definition; job terminated        BD           078          E
03:46:08 Job cancelled after system exception ERROR_MESSAGE                                      00           564          A
Please help me in resolving this issue.
Thanks in advance,
Sai.

hi,
If you have any GUI function modules used in the program of job
you cannot run it in background mode.

Custom Background Job Cancelling

Hi Folks,
I'm working on a custom development and I'm experiencing some trouble - I would greatly appreciate any help / effort from anyone in providing me with some ideas as to what the cause may be.
Basically my development is made up of two parts - Part 1) A custom RFC used to trigger a custom program in the background - here i'm using job_open / submit program / job_close. This works fine and a job is successfully created to run the custom program
Part 2) - The custom program, running in the background job tries to create a background job to trigger standard program (f.05) with a variant. Again using job_open / submit program / job_close. However on this occassion when the second background job starts it cancels immediately - stating "Make an entry in all required fields". . However the variant is fine and all the parameters for the standard program are filled. I can even trigger this program and variant seperately and it works.
Are there conflicts in creating a background job from a background job ? I'm confused as to why this is not working and i would appreciate any help or ideas anyone could give me on this.
Thanks alot for your time.
Regards
DK
Overview
RFC -> Create Background Job # 1 -> Background Job # 1 created successfully - Custom program running in Background Job # 1 tries to run standard program in backgroun - Background Job # 2 created successfully but immediately cancels - Job log message - "Make an entry in all required fields". Job cancelled after system exception ERROR_MESSAGE.

Hi Guys,
Thanks for your answers. The job log does say "Make an entry in all required fields" - but all the required fields are specified under the variant. I can even run this program with the same variant with no problems. I'm wondering what would affect the submit to program to prevent it passing the variant correctly - here is my submit
    SUBMIT sapf100 VIA JOB l_jobnam NUMBER l_jobcnt
    USING SELECTION-SET l_vari
    AND RETURN.
l_vari = Variant Name
l_jobname = job name
l_jobcnt = job count
here is the message from the job log. your help is appreciated - thanks
10.09.2009 14:22:18 Job started
10.09.2009 14:22:18 Step 001 started (program SAPF100, variant &0000000000018, user ID XXXX)
10.09.2009 14:22:18 Make an entry in all required fields
10.09.2009 14:22:18 Job cancelled after system exception ERROR_MESSAGE

Background Job cancellation-Alert config in Solman

Team,
We would like to send an alert to the distribution list or the user whenever a particular background job is getting cancelled.
Could you please let me know the steps how it can be done in solution manager.
Regds,
Satyanarayana N

Hello,
I recommend to setup the Job Monitoring of Business Process Montoring from a Job Documentation. The alerts can either generate notifications (E-Mail, SMS) or workflow documents (messages in Support Desk).
This is demonstrated in a RKT tutorial:
http://service.sap.com/~sapidb/011000358700001911422008E.sim
The process is also documented:
http://help.sap.com/saphelp_smehp1/helpdata/en/8e/3ad6f807e147669036d2a6aed597aa/frameset.htm
Please also visit our Service Markteplace representation: http://service.sap.com/jsm
Kind regards,
Martin

Background Job assigment with variant in SM37 , for Textfile uploading

Dear all,
Im using the BAPI_PO_CHANGE to update the existing schedule dates in Purchase Orders,
for this the po's , item, schedules, delivery dates(Need to update) from a Textfile into the internal table
and passing that data to bapi function module, it works fi9 in foreground and the output is a classical report
with Corresponding messages through RETURN.
i need the same to run in background with a variant, but after assigning the background job in SM36,
i found that the job assigned got CANCELLED in SM37.
I hope everything is clear, so kindly revert back with solution.
Regards,
Niranjan.G

Hi,
You should understand that background job will be executed in application server and there will be no gui or access to presentation server available.
You should upload your file to application server through tcode CG3Z.
See F1 help for OPEN DATASET / Search SCN for sample codes for OPEN DATASET.
You should change the code so that it can be run in both modes using the system variable SY-BATCH.
If it is space use GUI_UPLOAD, if it is X use OPEN DATASET.
Regards
Karthik D

ABAP report to monitor Background Jobs (SM37)

Hi,
I need an ABAP report to monitor Background Jobs (SM37) which can monitor following things:
1) All jobs which got cancelled based upon the hours field specified in the customizing table.
2)All jobs which are active till the current date.
Hope to receive your precious response!
Thanks
Mehar
Moderator message : Spec dumping not allowed, search for available information. Thread locked.
Edited by: Vinod Kumar on Nov 22, 2011 3:36 PM

Hi,
I need an ABAP report to monitor Background Jobs (SM37) which can monitor following things:
1) All jobs which got cancelled based upon the hours field specified in the customizing table.
2)All jobs which are active till the current date.
Hope to receive your precious response!
Thanks
Mehar
Moderator message : Spec dumping not allowed, search for available information. Thread locked.
Edited by: Vinod Kumar on Nov 22, 2011 3:36 PM

Background Job: SWEQSRV - system_cancelled

Hello gurus.
We are on ECC6 and recently upgraded our system to Unicode.
Now there are irregular dumps in ST22 with information of the background job (SWEQSRV) being cancelled by the system. "SYSTEM_CANCELLED".
Error analysis
The current program has been terminated from another mode, e.g. with
Transaction SM50.
This usually happens during 'system off-peak periods' e.g. during the night or early in the morning when there is minimun system usage.
Does any one know what could be cause for this?
Regards.
Wandai

Hello Wandai,
maybe noone answered this question because you spelled "cancelled" correctly. The dump message spells SYSTEM_CANCELED.
I have the same question. We are on ERP 6.04 but have not migrated to Unicode yet.
The SWEQSRV jobs (several of them) run very often. The dumps occur only once or twice a day. Since the joblogs are automatically purged there is not much you have to analyze the cause.
Regards
Andreas

Error in background job of downloading data to PC

Hi Gurus,
   I hv created a report for downloading data to PC using
GUI_DOWNLOAD FM when scheduling job in background
job is getting canceled...................
give me some solution....

thnaks friend.i hv used DATASET as u said...............
But I M getting dump
FILE IS NOT OPEN
this is my code
TYPES:BEGIN OF T_MARD,
        MATNR LIKE MARD-MATNR,
        WERKS LIKE MARD-WERKS,
        LGORT LIKE MARD-LGORT,
        LABST LIKE MARD-LABST,
        MAKTX LIKE MAKT-MAKTX,
     END OF T_MARD.
***********WORK AREAS**********
DATA: WA_MARD TYPE T_MARD,
      WA_MARD1 TYPE T_MARD.
DATA:BEGIN OF IT_MARD1 OCCURS 0,
        MATNR(18),
        WERKS(4),
        LGORT(4),
        LABST(13),
        MAKTX(40),
     END OF IT_MARD1.
TYPES : BEGIN OF TY_BAT,
          LINE(100) TYPE C,
        END OF TY_BAT.
*********INTERNAL TABLES*******
DATA:IT_MARD TYPE STANDARD TABLE OF T_MARD INITIAL SIZE 0 WITH HEADER LINE .
types: BEGIN OF ITAB1,
            FIELD(100),
      END   OF ITAB1.
DATA : IT_BAT TYPE TABLE OF TY_BAT,
       WA_BAT TYPE TY_BAT,
       wa_itab1 type itab1.
data : it_tab type table of ALSMEX_TABLINE with header line.
*DATA: FILENAME1 TYPE STRING valu.
*DATA: FILENAME1(500).
DATA: FILENAME1 TYPE RLGRAP-FILENAME .
LOOP AT IT_MARD1.
      CONCATENATE IT_MARD1-MATNR IT_MARD1-LABST IT_MARD1-MAKTX
                  INTO wa_ITAB1    SEPARATED BY ' '.
      APPEND wa_itab1 to IT_tab.
      CLEAR wa_ITAB1.
    CLEAR WA_MARD.
ENDLOOP.
CONCATENATE 'D:\STOCKINH\' SY-DATUM '.TXT' INTO FILENAME1.
open dataset filename1 for output in binary mode." ENCODING DEFAULT.
IF sy-subrc = 0.
EXIT.
ENDIF.
LOOP AT it_tab into wa_itab1.
TRANSFER wa_itab1 TO filename1.
CLEAR wa_itab1.
ENDLOOP.
close dataset filename1.
MESSAGE S001(38) WITH 'Files Generated'.
WA_BAT = 'ftp -s:d:\ftp\ftp_upload.txt'.
APPEND WA_BAT TO IT_BAT.
CLEAR FILENAME1.
   FILENAME1 = 'D:\STOCKINH\ftp_upload.BAT'.
open dataset filename1 for output in binary mode." ENCODING DEFAULT.
IF sy-subrc = 0.
EXIT.
ENDIF.
LOOP AT it_bat INTO wa_bat.
TRANSFER wa_bat TO filename1.
CLEAR wa_bat.
ENDLOOP.
close dataset filename1.
CLEAR: IT_BAT.
REFRESH IT_BAT.
WA_BAT-LINE = 'open 10.100.103.199'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'epossync'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'sync@1234'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'lcd D:\STOCKINH\20080201.TXT'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'cd /home/epossync/AMIT'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'binary'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'hash'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'put D:\STOCKINH\20080201.txt'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = ' '.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'bye'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
CLEAR FILENAME1.
FILENAME1 = 'D:\STOCKINH\ftp_upload.txt'.
open dataset filename1 for output in binary mode." ENCODING DEFAULT.
IF sy-subrc = 0.
EXIT.
ENDIF.
LOOP AT it_bat INTO wa_bat.
TRANSFER wa_bat TO filename1.
CLEAR wa_bat.
ENDLOOP.
close dataset filename1.

Background job error No appropriate entry found in table ADRT

Hi,
I have developed a report to sent mail in background. My background job is getting cancelled in background. but it runs in foreground.I have used leave to transaction statement in my report.
In my development server job cancellation occurs.but mails are being sent.whereas in production server job cancellation ocurrs but mails are not sent.
It shows the below error also...
27.12.2010 17:00:00 Job started
27.12.2010 17:00:00 Step 001 started (program YSD_OUTSANDING, variant &0000000000094, user ID ABAPER)
27.12.2010 17:00:01 No appropriate entry found in table ADRT
27.12.2010 17:00:01 Job cancelled after system exception ERROR_MESSAGE
please help me to overcome this error...
Thanks & Regards,
A. Jenifer

I don't see how either of those replies are helpful...
To the OP, you haven't given much information. That's a custom program but the failure is being triggered most likely by your attempt to generate the email by the standard code. You need to get the error message ID and number from the log and find the codepoint (from a where-used analysis or debug) and analyze the condition that's triggering the message. Most likely, it's a simple fix - there appears to be a missing remakrk entry but sometimes those messages are misleading and the message issued isn't actually the problem.

Assign Server to Background Job

Hi all,
I need a help in Background Job,
we got two servers i need to assigning one of the server to my background job running through report using 1)JOB_OPEN 2) Submit Report and 3) JOB_CLOSE.
Thank you all in Advance,
Jagan.

You can do this easily via SM36 by filling the Exec. Target while creating the Job.. But if you would like to set the SERVER name vai your Program.... try this
after the function call JOB_OPEN & before the SUBMIT statement, update the field EXECSERVER of the TBTCS dbTable with the server name. ( SInce it is your own Job & all you are doing is trying to force it to a server, a direct db UPDATE should not be an issue)
~Suresh

Cancleling a background job through ABAP code

hi
in my report i have a condition like this
if s_erdat > sy-datum.
xxxxxxxx
xxxxxxxxxxx
xxxxxxxxx
xxxxxxxx
endif.
if my selection screen date is grater than the system date i dont need to run the report at all
when i am running this report in back ground and i have given the erdat date greater than the system date my job status is finished.
but i dont want the job to be finished i want the job to be cancled. in this case how i need to modify the code

if s_erdat > sy-datum.
xxxxxxxx
xxxxxxxxxxx
xxxxxxxxx
xxxxxxxx
else.
message e001 text-001. "date is lower than the current date.
endif.
if you raise a error message background job will be cancelled with the text 001 in job spool..
Edited by: Jackandjay on Apr 22, 2008 12:57 AM

Submitting background jobs using an excecutable program

Hi all
Would anyone give an example program to submit jobs in background using job_open, job_submit, job_close F.M's,
please dont give complex coded program, easily understandable code with some useful comments will be apprecieated.
Thanks

Create a job using job_open
Create your job with JOB_OPEN. The module returns a unique job
number. Together with the jobname, this number identifies the
job. Other parameters are available, but are not required.
JOBNAME = 'Freely selectable name for the job(s) you create'.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
JOBNAME = JOBNAME
IMPORTING
JOBCOUNT = JOBNUMBER
EXCEPTIONS
CANT_CREATE_JOB = 01
INVALID_JOB_DATA = 02
JOBNAME_MISSING = 03
OTHERS = 99.
IF SY-SUBRC > 0.
<Error processing>
ENDIF.
Adding job step
Add a job step: ABAP program
CALL FUNCTION 'JOB_SUBMIT'
EXPORTING
AUTHCKNAM = SY-UNAME " Runtime authorizations
" user
JOBCOUNT = JOBNUMBER " Value from JOB_OPEN
JOBNAME = JOBNAME " Value from JOB_OPEN
REPORT = 'REPORT' " Report to be run
VARIANT = 'VARIANT' " Variant to use with
" report
PRIPARAMS = USER_PRINT_PARAMS " User printing options
ARCPARAMS = USER_ARC_PARAMS " User archiving options
" Both sets of options
" come from
" GET_PRINT_PARAMETERS
EXCEPTIONS
BAD_PRIPARAMS = 01
INVALID_JOBDATA = 02
JOBNAME_MISSING = 03
JOB_NOTEX = 04
JOB_SUBMIT_FAILED = 05
LOCK_FAILED = 06
PROGRAM_MISSING = 07
PROG_ABAP_AND_EXTPG_SET = 08
OTHERS = 99.
IF SY-SUBRC > 0.
<Error processing>
ENDIF.
**Closing job
Submit job for processing: immediate start
CALL FUNCTION 'JOB_CLOSE'
EXPORTING
JOBCOUNT = JOBNUMBER " Job identification: number
JOBNAME = JOBNAME " and name.
STRTIMMED = 'X' " Schedules the job for
" immediate start. The job
" is started immediately
" only if the user has the
" RELE authorization to
" release a job to run.
IMPORTING
JOB_WAS_RELEASED = JOB_RELEASED " If user has authorization
" to release jobs to run, job
" is automatically released
" when it is scheduled. This
" field is set to 'x' if the
" job has been released.
" Otherwise, the job is sche-
" duled but must be released
" by an administrator before
" it can be started.
EXCEPTIONS
CANT_START_IMMEDIATE No longer used. Replaced by IMPORTING
parameter JOB_WAS_RELEASED.
INVALID_STARTDATE = 01
JOBNAME_MISSING = 02
JOB_CLOSE_FAILED = 03
JOB_NOSTEPS = 04
JOB_NOTEX = 05
LOCK_FAILED = 06
OTHERS = 99.
IF SY-SUBRC > 0.
<Error processing>
ENDIF.
*Please note it's not my original code..I have done what you could do!! Just visited help.sap.com and typed Background jobs and got sample codes..

Background job got cancelled for the user ----- Isolation and resolution

Hi Experts,
One background job got cancelled for the user I have the Jobname and User...
Able to view the log information in SM37.
I am not sure what is the next step to do and how to resolve this issue.
Could any one please provide me the step by step Isolating the issue and resolving it.
That would be really greatfull.
Thank you in advance.
Regards,
Prem.

Hi,
What the error it was stating in that SM37 job log?
Pls post that error log, not completely just mention the error here we'll try to help you.
rgds,

BWREMOTE background job canceled in sap r/3 system

Hi my friends,
Thanks for your help ahead.
Today I checked the background job in SAP R/3 created by BWREMOTE via SM37. It showed me some jobs had been canceled.
I displayed its log, the detail message is:
==========================================
Step 001 started (program SBIE0001, variant &0000000083494, user name BWREMOTE)
DATASOURCE = ZQM_NOT_SHFGRP
Call up of customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 1,593 records
Result of customer enhancement: 1,593 records
Call up of customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 1,593 records
ABAP/4 processor: SAPSQL_INVALID_FIELDNAME
Job cancelled
==========================================
Then I displayed the "Long Text" of the job log. It is
One of the field names in the SELECT clause was not recognized.
Error analysis
The SELECT clause was specified in an internal table at runtime.
It contains the field name "TPR00", but this does not occur in any of
the database tables listed in the FROM clause.
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPLXRSA " in
"EXIT_SAPLRSAP_001".
The main program was "SBIE0001 ".
Source code extract
008840 concatenate 'TPR'
008850 day_temp+6(2)
008860 ' = '
008870 ' ''' zshift '''' into
008880 cond .
008890 append cond to itab .
008900 select schkz into i_not_shfgrp-zzschkz from t552a
008910 where zeity = '2'
008920 and mofid = 'CN'
008930 and mosid = '28'
008940 and ( schkz = 'SFTA' or
008950 schkz = 'SFTB' or
008960 schkz = 'SFTC' or
008970 schkz = 'SFTD' )
008980 and kjahr = day_temp+0(4)
008990 and monat = day_temp+4(2)
> and (itab) .
009010 endselect.
I guess that there is not a field named TPR00 in table t552a.
Next, I opened the 'project management of sap enhancement' via CMOD, entering the project name and chosing 'Display'.
Then Double click the Components 'EXIT_SAPLRSAP_001', we can see the function module 'EXIT_SAPLRSAP_001'. In the source codes, there is an include program, it is 'INCLUDE ZXRSAU01.'.
Then, I double clicked the Include program and find the position program terminated. The source codes are:
ZQM_NOT_SHFGRP *
when 'ZQM_NOT_SHFGRP'.
loop at c_t_data into i_not_shfgrp .
l_tabix = sy-tabix .
clear :mbatch ,zshift,cond ,zfield, zcharg, day_temp .
refresh itab.
if i_not_shfgrp-ausvn is initial.
else.
aa = '080000'.
bb = '160000'.
cc = '235959'.
day_temp = i_not_shfgrp-ausvn.
if i_not_shfgrp-auztv ge aa and
i_not_shfgrp-auztv lt bb .
zshift = 'MSHF' .
elseif i_not_shfgrp-auztv ge bb and
i_not_shfgrp-auztv le cc .
zshift = 'LSHF'.
else .
zshift = 'NSHF'.
day_temp = i_not_shfgrp-ausvn - 1.
endif.
concatenate 'TPR'
day_temp+6(2)
' = '
' ''' zshift '''' into
cond .
append cond to itab .
select schkz into i_not_shfgrp-zzschkz from t552a
where zeity = '2'
and mofid = 'CN'
and mosid = '28'
and ( schkz = 'SFTA' or
schkz = 'SFTB' or
schkz = 'SFTC' or
schkz = 'SFTD' )
and kjahr = day_temp+0(4)
and monat = day_temp+4(2)
and (itab) .
endselect.
endif.
I found that we got a TPR00 during concatenation. In other words, day_temp+6(2) = 00. But I think it is impossible. I can not explain this.
Any ideas, my friends. Many thanks.

select schkz into i_not_shfgrp-zzschkz from t552a
where zeity = '2'
and mofid = 'CN'
and mosid = '28'
and ( schkz = 'SFTA' or
schkz = 'SFTB' or
schkz = 'SFTC' or
schkz = 'SFTD' )
and kjahr = day_temp+0(4)
and monat = day_temp+4(2)
and (itab) . => doesn't make sense?!
endselect.
endif.
it seems something got deleted between 'and' and '(itab)'... so, you'll have to recheck the requirements for your select to fill the 'and' statement further.
so, it should look like
and monat = day_temp+4(2)
and <some kind of condition that needs to be fulfilled>.
endselect.
<some logic to fill a line in your internal table>.
append cond to itab.
endif.
obviously <some kind of condition that needs to be fulfilled> needs to be replaced by a real condition
and <some logic to fill a line in your internal table> needs to be replaced by some kind of formula
I assume something like (otherwise it would be really weird to select that field):
cond = i_not_shfgrp-zzschkz.
or a formula using the i_not_shfgrp-zzschkz field.
It would also be a lot better to replace your select ... endselect by a select single as you'll be selecting 1 record only anyways.
Message was edited by:
RafB

Background job SAP_PERIODIC_ORACLE_SNAPSHOT got cancelled.

Similar Messages

Maybe you are looking for