TemSe files

Hi,
Our TemSe feature is set as follows.
D OBJKN,
IN0504     &temse=500
IN0501     &temse=500
     &temse=30
Any idea how can I find additional information about this feature? What is the unit for 500. 30....?
What are the different alternatives to delete the magentic files generated in the Tax Reporter run?
Thanks,
Ratna

Hello Ratna,
      OBJKN
US01      &TEMSE=50
US02       &TEMSE=100
CTRPUT      &TEMSE=200
CTRPUP      &TEMSE=300
     &TEMSE=30
The log for tax company US01 is kept for 50 days (at a minimum, after that it will be deleted when you do a routine clean up for TEMSE files)
The log for tax company US02 is kept for 100 days
The log for other tax companies is kept for 30 days.
The magnetic media generated in a production a run is kept for 300 days
The magnetic media generated in a test run is kept for 200 days.
Arti

Similar Messages

  • TAx Reporter Temse Files Download Automation

    Hi,
    I have a reuiqrement to download the Temse files generated in Tax Reporter. I have completed the code and it works fine if we run the program in foreground. But when I run the same program in background some Temse files downloaded have junk characters. If I download the same Temse file in foreground it works fine.
    There seems to be some issue with the FM when I run my progam in background.
    I have searched SDN and SAP Notes for any clues but did not get any.
    REPORT  ZPHOP_TEMSE  NO STANDARD PAGE HEADING
                      LINE-SIZE 1023
                      LINE-COUNT 65
                      MESSAGE-ID zz.
    DATA: BEGIN OF tape OCCURS 1,
             DATA(2000),
          END OF tape.
    DATA: force_ascii type c VALUE 'T'.
    DATA:  BEGIN OF int_msgs2 OCCURS 10,
             errnum(2) TYPE c,
             text1(8) TYPE c,
             text2(60) TYPE c,
           END OF int_msgs2.
    DATA: BEGIN OF g_int_temse OCCURS 0,
             dname    LIKE TST01-dname,
             dpart    LIKE TST01-dpart,
             dcretime LIKE TST01-DCRETIME,
             dcreater LIKE TST01-DCREATER,
          END OF g_int_temse.
    DATA: record_length  TYPE i VALUE 275,
           data_length    TYPE i,
           convert_to_ebcdic,
           filesize TYPE i,
           number_of_records TYPE i VALUE 1,
           filetype(3) VALUE 'BIN',
           conv TYPE REF TO cl_abap_conv_out_ce,
           dline TYPE REF TO data,
           dtab TYPE REF TO data,
           p_compid(4),
           p_pswd(8),
           g_str(2000),
           uc_filename TYPE string.
    DATA: l_nm_fixed_record.
    CONSTANTS: c_lpath TYPE pathintern VALUE 'ZOUT'.
    TABLES: TST01, ZPHOPFLS, ZTEMSE_LOG, V_5UXY_A.
    FIELD-SYMBOLS: <dtab> TYPE STANDARD TABLE,
                   <dline> TYPE ANY.
    INCLUDE: dbpnpcom.           " No logical database        Do not modify!
    INCLUDE: zphoptop,           " Top Include                Do not modify!
             zphopfil.           " File inlcude               Do not modify!
    SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE text-T01.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 1(30) text-001.
    SELECT-OPTIONS  s_temse FOR TST01-dname NO INTERVALS.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN END OF BLOCK B1.
    SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE text-T02.
    SELECT-OPTIONS  s_cai   FOR TST01-DCREATER NO INTERVALS.
    SELECT-OPTIONS  s_date  FOR sy-datum.
    SELECTION-SCREEN END OF BLOCK B2.
    SELECTION-SCREEN BEGIN OF BLOCK B3 WITH FRAME TITLE text-T03.
    PARAMETERS: p_ifid   LIKE t9aoa-if_id MODIF ID DIS ,
                p_fileid LIKE t9aoa-file_id MODIF ID DIS,
                p_unixf(60)  LOWER CASE MODIF ID DIS,
                p_uxdir  TYPE pathextern LOWER CASE MODIF ID DIS,
                p_dstfil(45) LOWER CASE MODIF ID DIS.
    SELECTION-SCREEN END OF BLOCK B3.
    PARAMETERS: p_skip AS CHECKBOX.
    DATA: ws_unixr LIKE p_unixf,
          ws_trans LIKE p_unixf.
    AT SELECTION-SCREEN OUTPUT.
      LOOP AT SCREEN.
        IF screen-group1 = 'DIS'.
          screen-output = '1'.
          screen-input  = '0'.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    INITIALIZATION.
      p_ifid = 'PAYFLS'.
      p_compid = 'HR00'.
      p_fileid = '01'.
      p_unixf = 'AFS'.
      p_pswd = 'chevr123'.
      p_skip = 'X'.
    -End of Initialization--
      PERFORM get_physical_path.
      FORMAT COLOR COL_HEADING.
      WRITE: /01 text-t04,
              10 sy-pagno,
              41 text-t05,
             110 text-t06,
             123 sy-datum.
      WRITE: /01 text-t08,
              14 sy-repid,
             110 text-t07,
             125 sy-uzeit.
      FORMAT COLOR OFF.
      SKIP.
      WRITE: /(20) text-T21       CENTERED COLOR COL_HEADING,
              (15) text-T22       CENTERED COLOR COL_HEADING,
              (20) text-T23       CENTERED COLOR COL_HEADING,
              (15) text-T24       CENTERED COLOR COL_HEADING,
              (40) text-T25       CENTERED COLOR COL_HEADING.
    START-OF-SELECTION.
    *Do not allow background processing
    *Check if the Temse file and CAI both are entered
    IF NOT S_TEMSE IS INITIAL AND NOT S_CAI IS INITIAL.
       MESSAGE W999 WITH TEXT-E01.
    ELSEIF S_TEMSE IS INITIAL AND S_CAI IS INITIAL.
       MESSAGE W999 WITH TEXT-E02.
    ENDIF.
    Collect all temse filenames from TST01 into an internal table.
    IF NOT s_temse IS INITIAL.
       SELECT dname dpart dcretime dcreater FROM TST01 INTO TABLE g_int_temse
              WHERE dname in s_temse
              AND   dpart EQ '1'.
    ELSE.
       SELECT * FROM TST01
              WHERE DCREATER in s_cai
              AND   DPART EQ '1'.
         IF TST01-DCRETIME(8) GE s_date-low
             AND TST01-DCRETIME(8) LE s_date-high.
            MOVE-CORRESPONDING TST01 TO g_int_temse.
            APPEND g_int_temse.
         ENDIF.
       ENDSELECT.
    ENDIF.
    SORT g_int_temse BY DNAME DPART DCRETIME.
    LOOP AT g_int_temse.
    Check if the temse file is already processed in ZTEMSE_LOG table.
      SELECT SINGLE * FROM ZTEMSE_LOG
             WHERE DNAME = g_int_temse-dname.
      IF sy-subrc EQ 0.
    error. Temse already processed
         CONTINUE.
      ENDIF.
    Check if the temse file bieng processed is the eligible temse file
      SELECT SINGLE * FROM V_5UXY_A
             WHERE TSOBJ = g_int_temse-dname.
      IF sy-subrc EQ 0.
         SELECT SINGLE * FROM ZPHOPFLS
             WHERE TAXAU = V_5UXY_A-TAXAU
             AND   TXFRM = V_5UXY_A-TXFRM.
         IF sy-subrc EQ 0.
    Generate the filename for the target destination
            CONCATENATE ZPHOPFLS-FILENAME '.' sy-datum '.' sy-uzeit INTO p_dstfil.
         ELSE.
    error. Script not maintained in ZPHOPFLS table
            CONTINUE.
         ENDIF.
      ELSE.
    error. Temse file is not the latest processed file.
         CONTINUE.
      ENDIF.
      CALL FUNCTION 'RP_TS_OPEN'
        EXPORTING
          tsobj = g_int_temse-dname
         versn = g_int_temse-dpart
          empfg = 'RPUTSVUM'.
      COMMIT WORK.
      REFRESH tape.
      CLEAR   tape.
    Einlesen von der TemSe
      CALL FUNCTION 'RSTS_READ'
        EXPORTING
           PARTS1BY1 = 'X'
        TABLES
          datatab = tape.
      CALL FUNCTION 'RSTS_CLOSE'.
    Read the 1st line which is supposed to contains info important for
    the downloading procedure. The syntax of the line is :
      SAPxxxnnnyyyy  - the 1st 3 char 'SAP' indicates this line contains
    download related info. xxx can either be 'ASC' (for ASCII) or 'EBC'
    (for EBCDIC). nnn is the length of each record, e.g. 128 for SSA disk
    format, 275 for SSA tape format etc. yyyy can either be 'CRLF' (each
    record is delimited by CRLF) or blank (no CRLF).
    After processing the 1st line, the line is deleted from the internal
    table. Downloading begins on the 2nd line.
      READ TABLE tape INDEX 1.
      IF tape-data(3) EQ 'SAP'.
        IF tape-data+3(3) EQ 'EBC'.
          convert_to_ebcdic = 'x'.
        ELSEIF tape-data+3(3) EQ 'ASC'
              AND force_ascii EQ 'T'.
          filetype = 'ASC'.
        ENDIF.
        IF tape-data+6(3) NA '*'.
          record_length = tape-data+6(3).
        ELSE.
          record_length = tape-data+13(4).
        ENDIF.
        IF tape-data+9(4) EQ 'CRLF'.
          data_length = record_length + 2.
        ELSE.
          data_length = record_length.
        ENDIF.
        DELETE tape INDEX 1.
      ELSE.
        data_length = record_length.
      ENDIF.
    Transfer the Temse file data to Unix file.
          PERFORM transfer_file.
    Update the Log table with the temse details.
          ZTEMSE_LOG-dname = g_int_temse-dname.
          ZTEMSE_LOG-txcmp = V_5UXY_A-taxau.
          ZTEMSE_LOG-txfrm = V_5UXY_A-txfrm.
          ZTEMSE_LOG-filename = ws_unixr.
          ZTEMSE_LOG-DCREATER = g_int_temse-dcreater.
          INSERT ZTEMSE_LOG.
        WRITE: /(20) ZTEMSE_LOG-dname,
                (15) ZTEMSE_LOG-txcmp,
                (20) ZTEMSE_LOG-txfrm,
                (15) ZTEMSE_LOG-dcreater,
                (40) ZTEMSE_LOG-filename.
    ENDLOOP.
    *&      Form  get_physical_path
          Get Physical directory name for the given logical path name
    FORM get_physical_path .
      CALL FUNCTION 'ZFILE_GET_PATH_NAME'
        EXPORTING
          LOGICAL_PATH               = c_lpath
        IMPORTING
          FILE_NAME_PATH             = p_uxdir
        EXCEPTIONS
          PATH_NOT_FOUND             = 1
          MISSING_PARAMETER          = 2
          OPERATING_SYSTEM_NOT_FOUND = 3
          FILE_SYSTEM_NOT_FOUND      = 4
          OTHERS                     = 5.
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " get_physical_path
    *&      Form  TRANSFER_FILE
    FORM transfer_file.
      p_unixf = 'AFS'.
    Concatenate Date with Unix File name
      CONCATENATE p_unixf '.' p_compid '.' p_ifid  '.' sy-datum '.' sy-uzeit INTO ws_unixr.
    Concatenate Unix Directory with Unix File for Outbound
      CONCATENATE p_uxdir ws_unixr INTO p_unixf.
      PERFORM open_files USING p_unixf.
    LOOP AT tape.
         g_str = tape-data(record_length).
        TRANSFER g_str TO p_unixf LENGTH record_length.
        IF sy-subrc <> 0.
          MESSAGE ID '00' TYPE 'E' NUMBER '398' WITH 'sy-subrc:' sy-subrc
           ' Error Transferring to: ' p_unixf.
        ENDIF.
    ENDLOOP.
      PERFORM close_files USING p_unixf.
    ENDFORM.                    " TRANSFER_FILE
    Can anyone please check and tell me what I need to overcome this problem.

    Hi Bhaskar,
    I also have the same requirement to upload TemSe files in to application server.
    In FDTA tcode after we enter company code and click on enter.
    In the second screen checking and line item and go to edit and click on download button.
    Here we see a popup with default file name, and when we say ok the file will get downloaded into C:\.....
    Here our req is to upload the file automatically pick up via batch job and place it in the in to the application server and from there it should be placed in the Netwrok server (UNIX).
    Pls provide me with suitable code so that i can finish it off.I tried a lot but did not work.
    Thanks.

  • Problem with Creation of TemSe file...

    HI Experts...
    Here im facing the problem with creation of # 3 rd Quarters
    Temse file.when ever i use the tcode pc00_m40_f24 and entering the details of quater 3 ...here im showing up the ABAP Runtime error."""Overflow for arthimitic operation Type P in program  HINCF240"".
    What could be done to overcome the problem.Please advice.
    Regards,
    V Sai.

    Hi experts/Sriram...
    Thanks for the reply.
    The -
    >showing the line....
            QS80_TAB-DEDMT=QS80_TAB-DEDMT+S80-DEDMT
    Where should we change to get rid of this runtime error.
    Here in my quality everthing is fine and we have uploaded patches in quality upto recent one sp80.But in prod. the patchlevel is sp71.Will it be the reason.
    Please advice me on this as i have to complete the issue of F16.
    Thanks and Regards,
    V Sai.

  • Reading TemSe files in unicode system showing greek letters

    Hi Gurus,
    I am facing issue with the newly converted unicode (cp 4102) spool files. I am using the standard functions RSTS_OPEN_RLC , RSTS_READ and RSTS_CLOSE to read TemSe files and create output files on application server using OPEN DATASET and TRANSFER.
    After conversion to unicode, these function calls are returning some greek characters with size of the itab doubled (and that is due to double-byte UTF-16 charcter set) .
    The program generates
    Runtime Error          CONVT_CODEPAGE
    Except.                CX_SY_CONVERSION_CODEPAGE
    " While a text was being converted from code page '4102' to '1100', on
    the following occurred:
    - an character was discovered that could not be represented in one o
    the two code pages;
    - the system established that this conversion is not supported."
    the statement
    TRANSFER TEMSE_DATA TO ACT_FILE
    generates this error.
    Can someone tell me what is missing ?
    TIA
    Wasim

    The extra characters are pasted below:
    ㄀  㤀㄀    ㈀㈀㄀㐀㄀ ㈀㜀㐀㐀㐀  㤀 ㈀ 㘀 㤀㈀ 圀 㤀㐀㄀ ㄀唀⸀匀⸀ 䈀䄀一䬀
    These kind of characters are also visible in SP11 contents for spool files.
    Again the question: which font to you use to display in your SAPGUI?
    The spool files are generated through language EN and should not show any non-english characters.
    That doesn´t tell anything. One advantage of Unicode is that you can enter, display and modify all languages/characters with an English logon.
    Another question: What technology is generating those spool files? Sapscript? Smartforms? Self written program?
    Markus

  • Issue with Temse File status

    Hi Expert,
    We built an interface using PU12 and we have an issue with the TEMSE file created.
    When we run the interface on background, the temse file has the status ''IS BEING WRITTEN'' instead of '' CLOSED'' and we are missing data on the file. The issue does not occurred on foreground.
    Please help.
    Thanks on advance.

    Hi Khaled,
    Do you still have the issue. If so, did you check the spool / steps of the background job. You may need to debug the subroutine close_dataset in the include program RPCIFM42.
    If you have solved the issue, please post the cause and the solution so that other users can benefit.
    Thanks & Regards.
    Kiran
    Edited by: Kiran NN on Jul 27, 2009 3:49 PM

  • Temse File name -- ACH payments

    SAPGurus,
    We are getting some error in DME file display (used in ACH payment, US) . Using Transaction code FDTA when we go for display of DME file the TSNAM is displayed incorrect (as we checked from debugging the program).
    What is this TSNAM (Temse File name). How is it updated? and which transaction codes are it used in.
    Please reply as soon as possible.
    Thanks and regards,
    Priyajit

    Hello,
    In table REGUT, field TSNAM field is available. Do check it may be useful to you.
    Also there are couple of Function modules that do use the above field. They are:
    FI_PAYM_FILENAME_CREATE
    FI_PAYM_FILE_DELETE
    FI_PAYM_FILE_OPEN
    FI_PAYM_FILE_READ
    FI_PAYM_FTA_DELETE
    FI_PAYM_FTA_OPEN
    FI_PAYM_FTA_READ
    FI_PAYM_OUTPUT_COLLECT
    FI_PAYM_XML_DELETE
    FI_PAYM_XML_OPEN
    FKK_BOL_FILE_NAME_CREATE
    FKK_BOL_OUTPUT_COLLECT
    FKK_DME_ADMINDATA_FILL
    FKK_DME_FILE_NAME_CREATE
    FKK_DME_OUTPUT_COLLECT
    Coming to your query where path is of the file can be found, you can check in FDTA.
    mention the Run date & identification .
    Select all check boxes available underneath like pymnt runs, proposals, Data medium...etc
    Press F8.
    You'd be displayed with files created. Double click on them.
    in Bank transaction tab strip, you can view the name of the folder in which file was generated<under file name>.
    Go to AL11 and view the file.
    Also you can search in data base tables PAY*
    Hope this helps
    Rgds
    Rajendra
    Pls assign points if useful.

  • Download Temse file-HR_F_MMREF_1_GA.

    Hello All,
    The Magnetic Media file that is generated during W2 processing for State of Georgia is named HR_F_MMREF_1_GA.  Starting this year, Georgia is requiring us to upload the file to their website.  We have attempted to do this but are receiving errors.   When we download from PU19, the downloaded file is 1024 characters in length with 2 records of 512 on each line of the file( using Notepad to review).   This is not acceptable at the State DOR website.   The file will not upload.
    I attempted to use PU12 to export the temse file.  This time there is one record per row of data (Notepad).  GA DOR has reviewed our file and determined that the record length on our file is 550 characters long and should be 512. 
    I have checked the layout of the Magnetic file in SPRO and each record type contained in the file is defined as 512 characters in length.   The header record states that it is 512.
    Is there a better way to download TemSe files and capture all of the data with the correct record length? 
    Thanks,
    Connie Durham

    I'm using the U.S. Tax Reporting Guide for SAP Payroll Customers Year End 2010 and I'm a little confused regarding the T5UX4 and T5UX5 table referred to on page 47 or topic Generic Solution for reporting multiple tax authorities on the same magnetic media.  I cloned HR_F_MMREF_1 to ZHR_F_MMREF_1_VT so I can report to the State of Vermont.  However I do not need to report to multiple localities.  Do I need to have entries in table T5UX4 and T5UX5?
    Regards,
    Helen

  • Temse files not deleted

    Hi all,
    After housekeeping of job logs via report RSBTCDEL2, the job logs are deleted in SAP but temse files in unix are not deleted.  Temse consistency check does not indicate any problem, what could be the cause?

    Hi,
    Please check this thread
    Missing job log
    Regards,
    Subodh

  • TemSe file in templates 110 and 111 (modelos 110 y 111) - (PY-ES)

    Hi experts,
    I have a question regarding spanish Employment Tax (IRPF) report, namely the 110 and 111 templates (modelos 110 y 111).
    I'm implementing spanish payrroll for the first time and, when I execute the RPC190E0 report for the 110 and 111 templates, the system displays the results correctly, but doesn't provide a TemSe file for download. This striked me as odd, since there is, for example, a TemSe file for template 190 (modelo 190).
    Is this standard behaviour, or is there a configuration that I am missing for templates 110 and 111?
    Thank you very much,
    Luí

    Hola Antoine,
    I talked with my cliente and they're ok with filling the modelo 111 manually. Thank you very much for your help.
    Since we're on this subject, could you help me in one more question? When I generate modelo 190, the resulting file comes with "Tipo de Registro 1" and "Tipo de registro 2", but doesn't generates "Tipo de registro 0". I looked it up and "Tipo de Registro 0" contains data from the Presentador, correct?
    Is there any table that I should fill to generate "Registro 0" in modelo 190? I searched SPRO under "Evaluaciones para Hacienda", but couldn't find anything.
    Once again, thank you for your help.
    Regards,

  • How to generate TEMSE file in form 16

    Hi Experts,
    How to generate TEMSE file in form 16.Here i am unbale to get the values in page3 of f16  ""DETAILS OF TAX DEDUCTED AND DEPOSITED INTO CENTRAL GOVERNMENT ACCOUNT''
    PLease advice.
    Regards,
    Sai.

    Hi Dev...
    Thanks for the reply.Here i can able to get form 16 except  the acknowldgement numbers in firstpage and Details of tax deducted and deposited into central govt. account in page no three.
    What should i do inorder to get all those details in f16.
    Here i have given the tcode pc00_m40_f24.From here onwards i was unable to go furthur.
    Please advice.Points are sure.
    regards,
    sai.

  • Temse File form PU12 in CSV Format

    Hi,
    I need to download Temse file in csv format. Normally Temse file contains data without any separator and it used to have layout based on the interface layout for example, first 10 digit employee no, next 2 digit year.
    Is there any standard FM which can read the Interface Layout and separated the data with some separator. Or any FM which can give the interface layout information and I can split the data based on the information.
    Br,
    Piyush

    Hi Piyush,
    Please let me know how you got a CSV file from PU12
    Regards,
    Manu

  • Temse File

    Hi,
    When i am trying to execute Temse data file for form24q it says no valid records found for selection
    is there any configuration needed for this
    Regards
    Nalla

    Check this tread might be useful....[Re: Challan mapping;
    Mohan

  • Temse io error while trying to print

    Whenever i try to print a document it gives " temse io "error.
    can any one help me know why this error and resolution .
    Regards,
    Sajith M.

    Hi,
    look  like inconsistency in temse object
    check
    Note 48400 - Reorganization of TemSe and Spool
    Note 16875 - TemSe objects do not match TemSe files
    regards,
    kaushal

  • MMREF Magnetic Media Files Download/Saved from Tax Reporter

    Often times when we go to download the MMREF Federal File and various state files that are generated in PU19, they are not in the correct format.  Please explain how these should be downloaded.  Is the process to take the temse file and just download via the download link in the screen?  If so, should they be saved in txt files to view?  Often times it looks like the data is wrapped.  Please help!  We seem to specifically be having a problem with AL at this time.

    Hi
    First you need to download the MMREF format in google. so that you will get an idea how it looks like and compare the same with the format you generated from tax reporter. you can download the same by hitting the disk icon and save it in your hard drive in .txt format. Pls open the downloaded txt file. you can able to read those....
    Thanks
    Muru

  • Txt format in a file created by the Payment Medium Program

    Hi,
    I need some help with a query from Payroll France.
    They use the transaction PC00_M06_FFOT (program RFFOF_V) to transfer payment data to banks.
    This program creates a txt file that is accessible to the payroll and accounting teams. This file is stored on local discs and as txt format it can be modified.
    The last audit pointed to this as a potential issue. The data in this file is very sensitive and shoud be secured against any modification.
    The program is SAP standard and the txt format is compliant with the system used by banks. That is why I am not sure if the file format can be modified. We were thinking perhaps a PDF fike would be an option. However, our Development do not want to touch at the change before we know if this will not be a problem for the banks' system.
    I've created a note for SAP about already but they say it is not really an error and in fact beyond their scope.
    Would appreciate some advice from you.
    Thanks,
    Monika.

    Monika :
    When running payment transfer to the bank (i.e. RFFOT or RFFOV), you have an option to either have the output file created (at application server) or a temse file created (which you would go to DME management to process downloading to a file (e.g. in your local PC machine).
    Having the ACH file created on application server site usually should be quite secure in my opition (first of, not many ee should have access to application servers; second, you can control not to allow non-authorized personnel to access to certain directories in application server; third, usually, when ACH file is created, it usually will be picked up by an automate process to send the file to the bank (rather than manual process)) .  Just my thought on your audit issue .
    Rgds.

Maybe you are looking for

  • CSV to XML problem in message mapping

    Hi,     I am trying for a CSV to XML scenario. But i am confused with the message mapping. Can anybody please help me by giving demo example of this???     Thank you. Regards, Atul

  • Oracle Table Storage Parameters - a nice reading

    bold Gony's reading excercise for 07/09/2009 bold - The below is from the web source http://www.praetoriate.com/t_%20tuning_storage_parameters.htm. Very good material.The notes refers to figures and diagrams which cannot be seen below. But the text b

  • ORA-02063: preceding line error while using dblink

    CREATE OR REPLACE PROCEDURE TEST AS BEGIN DECLARE v_circle VARCHAR(10); CURSOR c1 IS SELECT file_number,SUBSTR(file_name,INSTR(file_name,'.',1,2)+1,LENGTH(file_name)) AS ftm_id FROM TABLE1 WHERE trim(a.start_TIME) = trim(SYSDATE-1); BEGIN FOR r1 IN c

  • Monitoring  tools of Idoc interface

    Can anyone provide me the information on   " Monitoring  tools of Idoc interface"

  • QEMU boot fail

    I've setup a virtual drive in QEMU and have installed Arch, but when I boot it up, it comes up with this error: :: Checking Filesystems /dev/sda1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid