Temse

Hi All
I am trying to down load the error records of BDC session method from sm35 into a text file.
Please let me know how to proceed for that.
Let me know tha tables from where i can fetch these records or there any atandard function modules that i can use.
Thanks and regards
Satish

Hi Satish,
Correct me if I'm wrong but you want to execute a batch input and then store/write the error messages into a text file?
If so please look this tiny example (not full code):
data:  it_messages like bdcmsgcoll occurs 0 with header line.
call transaction 'VK11'
using bdcdata
mode 'E'
update 'S'
messages into it_messages.
* Messages
loop at it_messages
select single * from t100
where sprsl = sy-langu and
      arbgb = it_messages-msgid and
      msgnr = it_messages-msgnr.
* And here write what you want to do with each message
* Maybe put messages into a another iternal table then process it later to a text file?
endloop.
Hopefully this will give you an idea where to look for the messages.
Regards,
Ville

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.

  • What are data types that can be stored on TemSe?

    What are data types that can be stored on TemSe(Storage for Temporary Sequential Data)?
    Moderator message: please search for available information/documentation.
    [Rules of engagement|http://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement]
    [Asking Good Questions in the Forums to get Good Answers|/people/rob.burbank/blog/2010/05/12/asking-good-questions-in-the-forums-to-get-good-answers]
    Edited by: Thomas Zloch on Sep 18, 2011 10:04 PM

    Hi
    SAP Library: TemSe Data Store:
    There are the following TemSe objects, among others:
    ·        Spool requests (TemSe Name: Spool....)
    ·        Job logs (TemSe Name: JOBLG...)
    ·        Objects from other applications, such as Human Resources (TemSe Name: HR)
    ·        An object whose name begins with KONS; this is object is constantly used by report RSPO1043 and should never be deleted (SAP Note 98065)
    Sandra

  • Error while creating Temse Object (W2 form in PU19)

    Team,
    When i try to create the w2 in PU19, i am getting the error statingthat ERROR WHILE CREATING TEMSE OBJECT HRLUS01A100900109026.Please advise me in this.(We are maintaining the HRSP-42).It is veryurgent,Expecting your valuable Guidance.Points sure for the answers.
    Regards
    Priya.K

    Hi
    let me know weather r u using any reference object which contain the routinee.
    regards,
    chandra.

  • Smartform Printing : Error in spool C call: Error from TemSe

    Hi! everybody,
    I am stating my problem as follows : I have to print a bar-code sticker of size 10 X 7 cms. I have worked on bar-codes before this also. This time the output from a smartform is to be given to a ZEBRA TLP 2844 printer. I initially encountered problems in printing. The data does not fit on to the page.
    After a lot of searching I found that ZEBRA was a partner of SAP and that a special device type needs to be created for output from a ZEBRA printer. I did this two times. Each time my steps were as described under.
    To create the device type I did the following :
    1. I finally found the driver from the ZEBRA website from http://www.zebra.com/id/products/global/en/utilities/sap_device_types.UtilityFile.File.tmp/Zebra_SAP_Device_Types.zip From this I uploaded the driver for 203 DPI zebra printer with IBM code 850 font file name "YZB200.PRI" into the transaction SA38.
    2. Then I created a new device ZEB10 in SPAD after assigning my format to the device.
    Thereafter, I tried to print my sticker. During this procedure, on selection of the new device type, the fonts automatically changed to ARIAL in the print preview. When I give the print command (Spool request : Print immed = X, Delete after output = X & New spool request = X) it gives an error message Error in spool C call: Error from TemSe.
    Since the output had not been issued, I opened the spool request to view its TemSe characteristics. Here I found
    Spool Attributes
    Output Device    ZEB10
    Format           ZTT               Format
    Doc. Category    SMART
    Recipient
    Department
    Deleted On       19.01.2011
    Authorization
    Output Attributes
    No. of Copies   1
    Priority              5
    SAP Cover Page Do not print SAP cover page
    OS Cover Sheet  Print as set at printer
    Requested           0
    Processed           0   With Problem                             0
                            With Error (Not Printed)                 0
    Storage Mode Print
    TemSe Attributes
    Object name           SPOOL0000013836
    Data type             ????????????
    Character set         0 -
    > Character set of dev type = 1162
    Number of parts       0
    Record format
    Size in bytes         0
    Storage location
    On seeing SP01
          Spool no.              Type                 Date        Time   Status   Pages               Title
           13836      Smartforms(OTF) 11.01.2011  07:32       +          0      SMART LP01 USERID
    I hope this data helps you help me. Please ask for more data if you wish. Also, I have searched vastly for this error on the net  have already come across the link http://help.sap.com/saphelp_45b/helpdata/en/d9/4a8f9c51ea11d189570000e829fbbd/frameset.htm but to no use. On the SDN, I have not found a similar thread and that is why I decided to post this problem here, hoping to find a solution. Kindly help.
    Regards,
    Manas

    Hi Manas,
    I am facing the same issue for one of my clients.
    Can you please share the solution with me if you have come out with it.
    Regards,
    Nirmal.K

  • 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

  • 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.

  • 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

  • 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

  • Error in TemSe Management

    Hi All,
    I saw a few Error in TemSe Management in sm21. However, the symbols is green color. The detail of the error indicate "Error in the C coding of the spooler.
    Message is no longer output."
    Is that important ? What had caused it?
    Regards
    Lauran

    Hello Lauran,
    goto SP12 -> temse data storage -> consistency check
    check this note for details:
    Note 48400 - Reorganization of TemSe and Spool

  • 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.

  • Error in SP12 TemSe: Data Consistency Check

    Dear All,
    I am getting error in SP12 TemSe: Data Consistency Check. Please suggest. this are only few there are may in thousands. There is one thing more we have resent upgrade from ecc5 to eccc6.
    Please suggest how to solve it.
    Consistency check of table TST01 / TemSe objects
    System PRD 12.04.2010 12:22:02
    Clt TemSe object name Part Comments
    700 BDCLG001048620722636 1 Unable to access the related file
    700 BDCLG001336417070836 1 Unable to access the related file
    700 BDCLG366544424095583 2 Unable to access the related file
    700 BDCLG366544424095583 3 Unable to access the related file
    700 JOBLGX23303906X11768 1 Object reset
    0 JOBLGX_ZOMBIE_X00304 1 Object reset Length = 0
    0 JOBLGX_ZOMBIE_X00773 1 Object reset Length = 0
    0 JOBLGX_ZOMBIE_X01080 1 Object reset Length = 0
    0 JOBLGX_ZOMBIE_X02571 1 Object reset Length = 0
    Regards,
    Kumar

    hi
    what is the solution for this post?/
    please tell me i am also getting same error
    shell i delete all these things??
    regards
    krishna

  • Inconsistency TemSe -- Batch input logs

    Hi folks,
    in our system there is an inconsistency between the TST01 table and APQL table. APQL has a lot more entries than TST01.
    Now I tried to reorganize the batch input logs with reports RSBDC_REORG and RSBDCREO. Unfortunately both reports use function module BDC_PROTOCOL_DELETE which performs a rollback work in case an inconsistency in TemSe is detected. Seems like RSBDCREO used function module BDC_TEMSE_REMOVE in former times which doesn't do the rollback but not anymore.
    I also found report RSBDCTL3 but this one deletes all the batch input logs of the client. So this one is of no use for me.
    Do you have any other suggestions on how to clean my APQL table?
    Regards,
    Bastian

    This one checks table TST01 and has a rollback included in case of inconsistencies.....
    As already stated in my first posting.
    Other suggestions welcome.
    Edited by: Bastian Schneider on Mar 17, 2010 7:45 AM

  • Temse Error

    Hi,
    We are getting below below errors in our SAP system logs:
    Repost table TST01 (TemSe->XRTAB(3)->64; Flag: MDFF; Key [100]SPOOL0000174533 ,1)
    TemSe error repair: 16 (Module , location )
    Calling program reports invalid handle for TemSe object (magic==X'4f444f26')
    Calling program reports invalid handle for TemSe object (magic==X'4f444f26')
    Error in TemSe Management
    A record in the database table TST01, which was assumed to
    exist, could not be found. To interfere with the further editing as
    little as possible, it is entered (again) into the database.
    This problem was observed sporadically for background processing logs
    and could not be explained up to now.
    The database error occurred here is explained as follows:
    ...follow-up posting because TemSe->&B(&C)->&D; flags &A;key &a
                                          !  !    !         Processing mode
                                          !  !    Error number
                                          !  Function number
                                          Database access module
    Possible database access modules
    RTAB
    Direct access with entire or partial primary key
    XRTAB
    direct access with entire or partial primary key for all clients
    INCLUDE 'RSTS_RTAB_FUNCTIONS' OBJECT DOKU ID TX
    INCLUDE 'RSTS_RTAB_ERRORS' OBJECT DOKU ID TX
    INCLUDE 'RSTS_TABLES' OBJECT DOKU ID TX The table affected here is
    always TST01.
    Editing mode (flags) : 1st position: PROM
    I
    Editing only within an internal mode. (normal case)
    E
    Editing only within an external mode, however in all of its internal
    modes.
    W
    Editing only within a work process.
    Editing mode (flags) : 2nd position : STOTYP
    D
    Storage in the database (in table TST03).
    Please suggest to resolve the error.
    Shivam

    Please try :
    http://help.sap.com/saphelp_nw04/helpdata/en/fc/04ca3bb6f8c21de10000000a114084/content.htm
    Thanks
    Mithun Das

  • TemSe and spool

    Can anyone tell me about the purpose of TemSe and spool. in ABAP-HR

    hi,
    You may refer to this link
    http://help.sap.com/saphelp_nw04/helpdata/en/d9/4a8f9c51ea11d189570000e829fbbd/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/7e/36e4c4023411d399b70000e83dd9fc/content.htm

Maybe you are looking for