Program terminating after spool is generated

Hello Experts..
                        I wrote a print program for smartform, and i converted that form from OTF to PDF using RSTXPDF4 program.
Everything is going well but ,
                       After saving PDF file, If we press Back then control not coming to program it is terminating abnormally(Showing SAP Easy access Screen)..
What should i do  to get back the control to the program to handle remaining things..
Thanks in adv....
Edited by: Murthy.SAP on Nov 12, 2010 8:21 AM

Yes  I got Solution ..............

Similar Messages

  • Run program in background spool is generated with zero page

    Dear all,
    I am new in abap. I change existing program and add SED column if I give the input and run that program in foreground I will see ALV output but when in same input same program I run in background spool is generated with zero page report is too heavy that is why I want to run it in background but I canu2019t.
    regards
    shahid

    shahid,
    goto SM37, select your job, then in command bar type JDBG, press Enter. it will debug the back ground job, and you can check why you didnot get an output.

  • ABNORMAL PROGRAM TERMINATION error

    I get an error every time I try to install an add-on on a specific client (only one!).
    The error message is:
    "VISUAL C++ Runtime Library“
    “Runtime Error Program C:\Program Files\SAP\SAP Business One\SAP Business One.exe”
    “abnormal program termination”
    After this message SBO crashes
    SAP version: 2005 SP1 P18
    I've already installed .Net Framework 1.1 and 2.0, windows installer 3.0 and 3.1
    I've tried to uninstall and reinstall sap client and add-on
    This happens with SAP add-ons and also with custom add-ons
    Did I forget something in basic installation?
    Did I have to open a call?
    Thanks in advance

    Dario,
    You may want to post a message with SAP Support on this as based on your description, you are not getting this issue accross the board "only on one workstation".  The forum you have posted your question in is for questions related to the Business One SDK and at least from your description, it does not sound SDK related.
    Eddy

  • Program terminated error after entering sold to party no. in sales order

    hello friends,
                      can any help me, i was doing the topic of user exit for pre-defined sold to party using v45a0002 in cmod and i wrote a program for include 'if sy-uname= 'sapuser'.
    message e000(0) with ' you are not authorised to create so'
    endif
    while activating i got error msg 'The last statement is not complete (period missing)."  & i have saved inspite error
    after i tried create a order
    program terminated error after entering sold to party no. in sales order
    so i have deactivated the project created in cmod & deleted the project inspite i am getting the program terminated error
    i am sending total error plz reply quickly urgent friends
    Runtime Errors         SYNTAX_ERROR
    Date and Time          19.04.2008 17:51:58
    ShrtText
    Syntax error in program "SAPLXVVA ".
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLVKMP" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    In program "SAPLXVVA ", the following syntax error occurred
    in the Include "ZXVVAU04 " in line 5:
    "The last statement is not complete (period missing)."
    Author and last person to change the Include are:
    Author "SAPUSER "
    Last changed by "SAPUSER "
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "SAPLXVVA ".
    You can also perform the syntax check from the ABAP/4 Editor.
    If the problem persists, proceed as follows:
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    In program "SAPLXVVA ", the following syntax error occurred:
    "The last statement is not complete (period missing)."
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    System environment
    SAP Release.............. "640"
    Application server....... "mtpl7"
    Network address.......... "192.100.10.1"
    Operating system......... "Windows NT"
    Release.................. "5.1"
    Hardware type............ "2x Intel 801586"
    Character length......... 8 Bits
    Pointer length........... 32 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "MTPL7"
    Database type............ "ORACLE"
    Database name............ "ERP"
    Database owner........... "SAPERP"
    Character set............ "English_United State"
    SAP kernel............... "640"
    Created on............... "Nov 4 2004 23:26:03"
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "OCI_920_SHARE "
    Patch level.............. "43"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory usage.............
    Roll..................... 8112
    EM....................... 8362368
    Heap..................... 0
    Page..................... 122880
    MM Used.................. 4229224
    MM Free.................. 995472
    SAP Release.............. "640"
    User and Transaction
    Client.............. 800
    User................ "SAPUSER"
    Language key........ "E"
    Transaction......... "VA01 "
    Program............. "SAPLVKMP"
    Screen.............. "SAPMV45A 4701"
    Screen line......... 16
    Information on where terminated
    The termination occurred in the ABAP program "SAPLVKMP" in
    "SD_DETERMINE_KKBER".
    The main program was "SAPMV45A ".
    The termination occurred in line 0 of the source code of the (Include)
    program " "
    of the source code of program " " (when calling the editor 00).
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    4
    SY-LSIND
    0
    SY-PAGNO
    1
    SY-LINNO
    8
    SY-COLNO
    1
    SY-PFKEY
    U
    SY-UCOMM
    SY-TITLE
    Create Standard Order kb: Overview
    SY-MSGTY
    E
    SY-MSGID
    VP
    SY-MSGNO
    106
    SY-MSGV1
    BUS2032
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    13 FUNCTION     SAPLVKMP                            LVKMPU41                               91
    SD_DETERMINE_KKBER
    12 FUNCTION     SAPLVKMP                            LVKMPU41                               91
    SD_DETERMINE_KKBER
    11 FUNCTION     SAPLV09B                            LV09BU30                              148
    SD_PCHECK_PAYER_IN_CREDITAREA
    10 FUNCTION     SAPLV09B                            LV09BU26                              296
    SD_PARTNER_EXECUTE_CHECKS
    9 FUNCTION     SAPLV09B                            LV09BU25                               57
    SD_PARTNER_CHECK_BEFORE
    8 FUNCTION     SAPLV09A                            LV09AU26                              342
    SD_PARTNER_SINGLE_MODIFY
    7 FORM         SAPLV09A                            LV09AF39                              176
    PARTNER_SELECTION
    6 FUNCTION     SAPLV09A                            LV09AU29                              820
    SD_PARTNER_DETERMINATION
    5 FUNCTION     SAPLV05E                            LV05EU01                              654
    VIEW_KUAGV
    4 FORM         SAPMV45A                            MV45AF0K_KUAGV_SELECT                  40
    KUAGV_SELECT
    3 FORM         SAPMV45A                            MV45AF0A_AUFTRAGGEBER_PRUEFEN          46
    AUFTRAGGEBER_PRUEFEN
    2 FORM         SAPMV45A                            MV45AF0K_KUNDEN_PRUEFEN               454
    KUNDEN_PRUEFEN
    1 MODULE (PAI) SAPMV45A                            MV45AI0K_KUNDEN_PRUEFEN                15
    KUNDEN_PRUEFEN
    Chosen variables
    Name
    Val.
    No.      13 Ty.          FUNCTION
    Name  SD_DETERMINE_KKBER
    I_KKBER_KNVV
    2222
    0000
    I_KKBER_T001
    8888
    3333
    8888
    I_KKBER_TVTA
    2222
    0000
    I_KUNNR
    7000000000
    3333333333
    7000000000
    I_SPART
    SM
    54
    3D
    I_VKORG
    T000
    5333
    4000
    I_VTWEG
    S4
    53
    34
    XVBAK
    00000000000000            000000000000000000000000         00000000
    2222222222222333333333333332222222222223333333333333333333333332222222223333333322222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    E_KNVV_FLG
    2
    0
    RC
    0
    0000
    0000
    XVBKD[]
    Table[initial]
    XVBPA[]
    Table IT_1743[2x542]
    FUNCTION=SD_PCHECK_PAYER_IN_CREDITAREADATA=LVT_CREDIT_XVBPA
    Table reference: 275
    TABH+  0(20) = 70A2883B388BC43B0000000013010000CF060000
    TABH+ 20(20) = 020000001E020000FFFFFFFF04910100D82F0000
    TABH+ 40( 8) = 02000000C1248400
    store        = 0x70A2883B
    ext1         = 0x388BC43B
    shmId        = 0     (0x00000000)
    id           = 275   (0x13010000)
    label        = 1743  (0xCF060000)
    fill         = 2     (0x02000000)
    leng         = 542   (0x1E020000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000209
    occu         = 2     (0x02000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x28C1883B
    pghook       = 0x00000000
    idxPtr       = 0x00000000
    refCount     = 1     (0x01000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 2     (0x02000000)
    lineAlloc    = 2     (0x02000000)
    store_id     = 690   (0xB2020000)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    hsdir        = 0x00000000
    ext2         = 0x28A4883B
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x109C883B
    delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    I_KKBER
    2222
    0000
    FCODE_KOMM_LIEF_MENGE_SICH
    MOD2
    44432222222222222222
    DF420000000000000000
    SYST-REPID
    SAPLVKMP
    5454544522222222222222222222222222222222
    310C6BD000000000000000000000000000000000
    %_SPACE
    2
    0
    FCODE_KONFIGURATION1
    POKO
    54442222222222222222
    0FBF0000000000000000
    CREDIT_CHECK
    2222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000
    SY-REPID
    SAPLVKMP
    5454544522222222222222222222222222222222
    310C6BD000000000000000000000000000000000
    SAV_BUKRS
    SS00
    5533
    3300
    CHAR_
    2
    0
    %_DUMMY$$
    2222
    0000
    AUTOMO_VOLVO
    08
    33
    08
    SPACE
    2
    0
    FCODE_ABRUF_GENERIEREN
    PABG
    54442222222222222222
    01270000000000000000
    XVBRK
    00000000          0000000
    2222222222222222222222222222222222222222222222223333333322222222223333333222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    KOPGR_LIEFERPLAN
    LL
    4422
    CC00
    FCODE_ZUSAETZE_FAB
    PFZU
    54552222222222222222
    06A50000000000000000
    FCODE_REPARATUR
    PREP
    55452222222222222222
    02500000000000000000
    XVBKD
    000000                                                 #####0000000000       ####
    2222222222222333333222222222222222222222222222222222222222222222222200000333333333322222220000
    000000000000000000000000000000000000000000000000000000000000000000000000C000000000000000000000
    FCODE_GEFAHRGUT
    KGGP
    44452222222222222222
    B7700000000000000000
    I_KKBER_HELP
    2222
    0000
    T001
    800SS00SRIYA TEXTILES           HYDERABAD                IN INR  EINT 10K41      0000050495DE1
    3335533554542545544452222222222245445444422222222222222224424452244452334332222223333333333443
    800330032991045849C530000000000089452121400000000000000009E09E20059E4010B410000000000050495451
    FCODE_STOFFBERICHTE
    IEHS
    44452222222222222222
    95830000000000000000
    T001-BUKRS
    SS00
    5533
    3300
    No.      12 Ty.          FUNCTION
    Name  SD_DETERMINE_KKBER
    I_KKBER_KNVV
    2222
    0000
    I_KKBER_T001
    8888
    3333
    8888
    I_KKBER_TVTA
    2222
    0000
    I_KUNNR
    7000000000
    3333333333
    7000000000
    I_SPART
    SM
    54
    3D
    I_VKORG
    T000
    5333
    4000
    I_VTWEG
    S4
    53
    34
    XVBAK
    00000000000000            000000000000000000000000         00000000
    2222222222222333333333333332222222222223333333333333333333333332222222223333333322222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    E_KNVV_FLG
    2
    0
    RC
    0
    0000
    0000
    XVBKD[]
    Table[initial]
    XVBPA[]
    Table IT_1743[2x542]
    I_KKBER
    2222
    0000
    XVBKD
    000000                                                 #####0000000000       ####
    2222222222222333333222222222222222222222222222222222222222222222222200000333333333322222220000
    000000000000000000000000000000000000000000000000000000000000000000000000C000000000000000000000
    I_KKBER_HELP
    2222
    0000
    No.      11 Ty.          FUNCTION
    Name  SD_PCHECK_PAYER_IN_CREDITAREA
    FIC_OBJECTKEY
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    FIC_OBJECTTYPE
    BUS2032
    4553333222
    2532032000
    FIF_CHECKTYPE
    I
    4
    9
    FIF_MSGTYPE
    E
    4
    5
    FIF_NRART
    KU
    45
    B5
    FIF_PARGR
    TA
    5422
    4100
    FIF_PARNR
    7000000000
    3333333333
    7000000000
    FIF_PARVW
    RG
    5422
    2700
    FIF_POSNR
    000000
    333333
    000000
    FIF_RTYPE
    0003
    3333
    0003
    FIS_SDORGDATA
    T000S4SMZSOR
    533353545545222222
    4000343DA3F2000000
    FRF_MESSAGES
    0
    0000
    0000
    FRF_MESSAGE_COUNT
    0
    0000
    0000
    LVF_KKBER2
    2222
    0000
    LVF_KUNNR
    7000000000
    3333333333
    7000000000
    SYST-REPID
    SAPLV09B
    5454533422222222222222222222222222222222
    310C609200000000000000000000000000000000
    LVF_KURGV2
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    FIS_SDORGDATA-SPART
    SM
    54
    3D
    FIS_SDORGDATA-VKORG
    T000
    5333
    4000
    FIS_SDORGDATA-VTWEG
    S4
    53
    34
    %_O_SD_PARTNER_CONTEXT-HEX_0004
    1
    0
    LVT_CREDIT_XVBPA
    Table IT_1743[2x542]
    LVF_KKBER1
    2222
    0000
    GCS_HERTAB
    ABCDEFG
    24444444
    01234567
    %_DUMMY$$
    2222
    0000
    SY-SUBRC
    0
    0000
    0000
    LVF_BEFORE_PARVW
    2222
    0000
    No.      10 Ty.          FUNCTION
    Name  SD_PARTNER_EXECUTE_CHECKS
    FIC_OBJECTKEY
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    FIC_OBJECTTYPE
    BUS2032
    4553333222
    2532032000
    FIF_BEFORE
    2
    0
    FIF_CHECKTYPE
    I
    4
    9
    FIF_DIALOG
    2
    0
    FIF_MSGTYPE_TO_EXEC
    E
    4222
    5000
    FIF_NRART
    KU
    45
    B5
    FIF_PARGR
    TA
    5422
    4100
    FIF_PARNR
    7000000000
    3333333333
    7000000000
    FIF_PARVW
    RG
    5422
    2700
    FIF_POSNR
    000000
    333333
    000000
    FIF_RTYPE
    0003
    3333
    0003
    FIS_SDORGDATA
    T000S4SMZSOR
    533353545545222222
    4000343DA3F2000000
    FRF_MESSAGES
    0
    0000
    0000
    FRF_MESSAGE_COUNT
    0
    0000
    0000
    LVF_ALL_PREDECESSORS_SUCCEEDED
    X
    5
    8
    FALSE
    2
    0
    GS_MARKED_PARTNERS
    222222222222
    000000000000
    LVT_CHECKCALLSTACK
    Table IT_1515[21x52]
    FUNCTION=SD_PARTNER_EXECUTE_CHECKSDATA=LVT_CHECKCALLSTACK
    Table reference: 219
    TABH+  0(20) = E8C3863B0000000000000000DB000000EB050000
    TABH+ 20(20) = 1500000034000000F00000000491010058090000
    TABH+ 40( 8) = 15000000C1248000
    store        = 0xE8C3863B
    ext1         = 0x00000000
    shmId        = 0     (0x00000000)
    id           = 219   (0xDB000000)
    label        = 1515  (0xEB050000)
    fill         = 21    (0x15000000)
    leng         = 52    (0x34000000)
    loop         = 240   (0xF0000000)
    xtyp         = TYPE#000033
    occu         = 21    (0x15000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x90BF863B
    pghook       = 0x00000000
    idxPtr       = 0x00000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 21    (0x15000000)
    lineAlloc    = 21    (0x15000000)
    store_id     = 595   (0x53020000)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    LVS_CHECKCALLSTACK_WA
    80000018BUS2030   SD_PCHECK_PAYER_IN_CREDITAREA   XX
    3333333345533332225455444445545455445454445454422255
    80000018253203000034F03853BF01952F9EF325494125100088
    GT_MARKED_FOR_DEL_PARTNERS
    Table[initial]
    LVS_CHECKCALLSTACK_WA-FUNCNAME
    SD_PCHECK_PAYER_IN_CREDITAREA
    545544444554545544545444545442
    34F03853BF01952F9EF32549412510
    GC_NO_ACTION
    2
    0
    GC_NEW_PARTNER
    I
    4
    9
    GVC_PARTNER_CONTEXT
    CONTEXT_X_SD_PARTNER_CONTEXT            fò####################################################
    44454555555455455445544454552222222222226F0000000000000000000000000000000000000000000000000000
    3FE4584F8F34F0124E52F3FE4584000000000000620000000000000000000000000000000000000000000000000000
    GC_ERROR
    E
    4
    5
    GC_PROCESSMODE_DIALOG
    D
    4
    4
    LVF_MSGTYP
    E
    4
    5
    BUFFER_FULL_FILLED
    F
    4
    6
    POS_NUL
    000000
    333333
    000000
    BUFFER_PARTITIAL_FILLED
    P
    5
    0
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GCS_PARTNER_ROLETYPES
    0001000200030004000500060007000800090010001100120013NONE
    33333333333333333333333333333333333333333333333333334444
    0001000200030004000500060007000800090010001100120013EFE5
    GCS_PARTNER_TYPE
    KUAPLIPE
    45454454
    B510C905
    LVF_RTYPE
    0003
    3333
    0003
    GCS_PARTNER_CALL_BACK_EVENTS
    CHANGE    DELETE    NEW
    444444222244445422224452222222
    381E75000045C5450000E570000000
    %_PRINT
    000                                                                                0 ##
    2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GCF_INITIAL_PARTNER
    0
    32
    00
    GCF_CALLER_TRANSPORT
    T
    5
    4
    TPACHECKRELATION
    0000000000
    2223333333333
    0000000000000
    GC_APPL_LOG
    SDBFPD
    54445422222222222222
    34260400000000000000
    SY-REPID
    SAPLV09B
    5454533422222222222222222222222222222222
    310C609200000000000000000000000000000000
    GVC_PARTNER_CONTEXT-B0007-PARVW
    RG
    54
    27
    No.       9 Ty.          FUNCTION
    Name  SD_PARTNER_CHECK_BEFORE
    FIC_OBJECTKEY
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    FIC_OBJECTTYPE
    BUS2032
    4553333222
    2532032000
    FIF_BEFORE
    2
    0
    FIF_CHECKTYPE
    I
    4
    9
    FIF_DIALOG
    2
    0
    FIF_NRART
    KU
    45
    B5
    FIF_PARGR
    TA
    5422
    4100
    FIF_PARNR
    7000000000
    3333333333
    7000000000
    FIF_PARVW
    RG
    5422
    2700
    FIF_POSNR
    000000
    333333
    000000
    FIF_RTYPE
    0003
    3333
    0003
    FIS_SDORGDATA
    T000S4SMZSOR
    533353545545222222
    4000343DA3F2000000
    FRF_MESSAGES
    0
    0000
    0000
    FRF_MESSAGE_COUNT
    0
    0000
    0000
    LS_STATISTICS
    ########################4   ################
    00000000000000000000000032220000000000000000
    00000000000000000000000040000000000000000000
    No.       8 Ty.          FUNCTION
    Name  SD_PARTNER_SINGLE_MODIFY
    FIC_OBJECTKEY
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    FIC_OBJECTTYPE
    BUS2032
    4553333222
    2532032000
    FIF_BOKRE
    2
    0
    FIF_CLEAR_APPL_LOG
    X
    5
    8
    FIF_DIALOG
    2
    0
    FIF_HARD_DELETION
    2
    0
    FIF_HISTUNR
    00
    33
    00
    FIF_HZUOR
    00
    33
    00
    FIF_INITIAL_VALUE
    X
    5
    8
    FIF_KNREF_PARNR
    2222222222
    0000000000
    FIF_KUNNR_NEW
    7000000000
    3333333333
    7000000000
    FIF_KUNNR_OLD
    2222222222
    0000000000
    FIF_LISTPROCESSING
    2
    0
    FIF_MANUAL_ADDRESS
    2222222222
    0000000000
    FIF_MANUAL_ADDRESS_ORIGIN
    2
    0
    FIF_NO_CPD_DIALOG
    2
    0
    FIF_NO_DIALOG
    2
    0
    FIF_NO_MESSAGES
    2
    0
    FIF_PARGR
    TA
    5422
    4100
    FIF_PARTIAL_NEW_DETERMINATION
    2
    0
    FIF_PARVW
    RG
    5422
    2700
    FIF_POSNR
    000000
    333333
    000000
    FIF_PRFRE
    2
    0
    FIF_VKORG
    2222
    0000
    FIS_SDORGDATA
    T000S4SMZSOR
    533353545545222222
    4000343DA3F2000000
    FEV_ACTION_DONE
    I
    4
    9
    FRF_LOG_COUNT
    0
    0000
    0000
    SYST-REPID
    SAPLV09A
    5454533422222222222222222222222222222222
    310C609100000000000000000000000000000000
    GVT_LOCAL_CALL_BACK_MEMORY[]
    Table[initial]
    %_SPACE
    2
    0
    SY-REPID
    SAPLV09A
    5454533422222222222222222222222222222222
    310C609100000000000000000000000000000000
    LVF_ACTION_TODO
    I
    4
    9
    GC_UPD_PARTNER
    U
    5
    5
    %_VIASELSCR
    0
    4
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GCS_PARTNER_ROLETYPES-SHIP_TO
    0002
    3333
    0002
    LVF_NRART
    KU
    45
    B5
    LVF_KUNNR_NEW
    7000000000
    3333333333
    7000000000
    GCS_ADDRESS_GROUP
    SD01CA01
    54334433
    34013101
    GCF_APPL_TABLE_SD
    VBUK
    5454222222
    625B000000
    LVF_ROLETYPE
    0003
    3333
    0003
    RSJOBINFO
    00000000000000                                  ####
    222222222222222222222222222222223333333333333322222222222222222222222222222222220000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LVF_MESSAGE_COUNT
    0
    0000
    0000
    %_DUMMY$$
    2222
    0000
    GCF_ADDRESS_TYPE_CONT_PERSON
    3
    3
    3
    No.       7 Ty.          FORM
    Name  PARTNER_SELECTION
    TVTA
    000
    222222222222222222222222222222222333222222222222222
    000000000000000000000000000000000000000000000000000
    TPAER
    00
    22222222222222332222
    00000000000000000000
    LVS_XVBPA
    000000RG7000000000          0000000000000000000000050510
    2222222222222333333543333333333222222222233333333333333333333333333332222222222222222222222222
    0000000000000000000277000000000000000000000000000000000000000000505100000000000000000000000000
    LVF_PARNR
    7000000000
    3333333333
    7000000000
    PIC_OBJECTKEY
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    PIC_OBJECTTYPE
    BUS2032
    4553333222
    2532032000
    PIF_NO_DIALOG
    2
    0
    PIF_PARGR
    TA
    5422
    4100
    LVF_PARVW
    RG
    5422
    2700
    PIF_POSNR

    Hi Kartik,
    Could you please be more clearer as to how do you want me to proceed so that this syntax error stops bothering me while creating a standard order thru TCode VA01.Also what do you mean by "well comment the code in the include and activate the include"
    I created a projet in CMOD and than added the enhancement  V45A0002.The components shown as EXIT_SAPMV45A_002(Predefined sold to party when making the standard order),i double click on the exit and entered into the function module.After that i double clicked on the include ZXVVZU04 and entered in and wrote E_KUNNR=100171
    While activating i got error msg 'The last statement is not complete (period missing)." & i have saved inspite the error .After that i tried to create a order and program terminated error came after entering sold to party no. in sales order
    so now i have deactivated the project which i created in CMOD & deleted the project also inspite of this i am getting the program terminated error while making the order
    I would be great ful if somebody helps me *** out of this syntax error.
    Thanks
    Rishi

  • How do I open a word document after a popup says "abnormal program termination"?

    When I try to open an attachment, the document appears for a nano-second, then a message appears in front of the document that says "abnormal program termination" and I cannot get rid of it and cannot scroll down to read the document.

    What have you tried that doesn't work? What else can you tell us about it? Which Pages version are you using?
    There are several ways to open a document on a computer.
    1. Double click and it'll open in its own applications if it is installed on the computer or to an assigned application for that format. You can assign an application in the Get info window (cmd + I)
    2. Drag and drop on the application of chocise. It the application can open the format of the document it it will.
    3. In the application of choice go file > open and find the document and click on the Open button
    4. Right click on the document asn choose an application

  • "Program terminated in remote system NONE: Logon failed" when adding a new table

    Hello,
    I set up a replication flow from a SAP ERP 6.0 EHP7 with SAP ASE 16.0 source to SAP HANA 1.0 rev 82 target
    I am using a standalone SLT system NetWeaver 7.0 with DMIS 2011_1_731 (with SP 1 to 7).
    I have 100 tables to replicate.
    I succeeded to set up replication for 57 tables. These tables are replicating properly.
    Whenever I try to add a new one (with LTRC transaction, Data Provisioning -> Start Replication), the new table is marked as 'Failed' after a little while.
    When I press 'Show Error Log' button I got an obscure error message:
    "Program terminated in remote system NONE: Logon failed "
    I do not understand this message. I checked both on SAP ASE source and SAP HANA target. I am still able to connect against both source and target.
    Can you please tell how to troubleshoot this error.
    Thanks in advance,
    Christian

    First thank you for answering my questions. I really appreciate your answers.
    I rechecked the documentation.
    "Application Operations Guide SAP Landscape Transformation Replication Server Document Version: 2.3 – 2014-07-08"
    Page 29 - 30
    3.5.2.2 Data Transfer Jobs
    This section explains the relationship between the number of data transfer jobs and the number of available background work process.
    Data transfer and data transformation processing on SLT server system is accomplished by the background work processes of the underlying SAP NetWeaver ABAP application server. Each job occupies 1 background work process in the SAP LT Replication Server system. For each configuration, the parameter Data Transfer Jobs restricts the maximum number of data load job for each mass transfer ID (MT_ID). In total, a mass transfer ID (MT_ID) requires at least 4 background jobs to be available:
     One monitoring job (master job)
     One master controller job
     At least one data load job
     One additional job either for the migration objects definition, access plan calculation or to change configuration settings in the Configuration & Monitoring Dashboard
    Example
    If you set the parameter Data Transfer Jobs to 04 in a configuration “SCHEMA1”, a mass transfer ID 001 is assigned. As a result, the following jobs should be in the system:
    1 Master controller job: /1LT/IUC_REP_CNTR_001
     At most 4 parallel jobs for MT_ID 001: /1LT/IUC_LOAD_MT_001_001/~002/~003/~004
    When configuring your data load or replication scenario, consider the following:
     Do not define more data transfer jobs than the number of available application server background work processes. If all available background work processes are already occupied by jobs, any other job will have to wait until a free work process becomes available. This can lead to long wait times until a new activity (for example creating triggers) can start, and can also result in significantly increased latency times for data replication.
     The number of dialog work processes in the source system corresponds 1:1 with the number of data transfer jobs in the SAP LT Replication Server system.
     Besides the work processes allocated by the data transfer jobs you need to provide additional available work processes for controller and monitoring jobs, the migration objects definition, access plan calculation or to perform configuration changes, and so on.
    Sizing for SAP LT Replication Server involves determining how many work processes are required to perform the initial load of data into the target system within an acceptable timeframe, and accomplish the change capturing and the transfer of data changes to the target system within expected latency times.
    Ensure that you add enough additional work processes to allow other required SAP LT Replication Server jobs to run.
    Finally, you map the number of required application server work processes to their system resource consumption (CPU, memory, disc space) using the formulas provided by the SLT Sizing Guide.
    With the simple formula below, you can calculate the number of required application server work processes (WPs) on the SLT Server for each active SLT configuration.
    The number of required work processes can be determined by adding
     The Number of required data transfer jobs ,
     plus one background work process for Central Master (Monitoring) Job (only one per system!),
     plus one background work process for Master Controller Job,
     plus 3-5 additional empty background work processes (recommended per configuration),
     plus approx. 3 dialog work processes (recommended for each configuration).
    Note: A lack of available free application server work processes can negatively affect the data load or data replication processes.
    To summarize everything, the number of 'Data Transfer Jobs' must be set depending of the number of source tables, it is not the actual number of tables.
    Assume that for my 100 tables I use 10 'Data Transfer Jobs' :
    - The number of work processes on the SLT server would be 20. I took the simple formula of the documentation:
    10 data transfer jobs ,
    + 1 background work process for Central Master (Monitoring) Job (only one per system!),
    + 1 background work process for Master Controller Job,
    + 5 additional empty background work processes (recommended per configuration),
    + 3 dialog work processes (recommended for each configuration).
    - The number of dialog processes on the source server would be 10 ( equal to the number of 'Data Transfer Jobs')
    Am I correct ?
    Regards,
    Christian

  • Fax from computer to photosmart 7525 gets cancelled after spooling

    I can fax directly from printer, but when I use the HP software or print function on the computer to set up fax and send, the progress goes from spooling to cancelled without any error notices. I have a Dell XPS 8500 running 8.1 and Photosmart 7525 connected by USB and wirelessly. They communicate just fine with the scan and print functions. Both are current on updates using the check for updates utility. I have a dedicated Voip phone line from Comcast and ther most current modem that I have slowed through the fax settings. I've spent hours reading forums on HP and Microsoft searching for exactly this issue. Please help

    Hi @xskilledtrades
    The truth is, I don't know what is causing the fax from computer function to fail. I understand from your description that the fax is cancelling after spooling, but that you can print and scan just fine as well as fax directly from the printer. I suspect the issue has something to do with the driver, thus I suggest we remove the driver and reload it.
    Please use the following steps to delete the printer/fax from device and printers, and the driver from the server properties.
    1. In the ‘Devices and Printers’ folder
    2. Choose ‘Print server properties’.
    Win XP – With no printer selected, click ‘File’ then ‘Server Properties’.
    Windows Vista – With no printer selected, press ‘Alt’ then click ‘File’ then ‘Server Properties’.
    Windows 7/8 and 8.1 – Select any printer in the ‘Devices and Printers’ folder and click ‘Print Server properties’ above.
    3. Click on the ‘Drivers’ tab at the top of ‘Print server properties’ window
    4. Choose the printer you want to uninstall and click ‘Remove’
    5. Choose 'Remove driver only'
    6. The next screen will give a warning, letting you know that deleting the driver package will remove it from the system. Click ‘Yes’ to say that you are sure you want to do this.
    If documents are stuck in the print spooler, you may see an error, cancel any documents pending in the print queue, or try restarting the print spooler, then try to remove the driver from ‘Print server properties’ again. If it still won’t remove the package, restarting the computer and the printer should resolve this ‘in use’ error and allow the driver to be removed.
    If the you continue to get an 'in use' message follow the steps in the document here; The Specified Printer Driver is Currently in Use
    After the driver is removed, open Start > All Programs > HP folder > Printer folder > HP Setup and Software (or the printer icon).
    The Setup and software screen will open and you can click on Connect a new printer.
    Thanks, I look forward to hearing back from you.
    Please click the Thumbs up icon below to thank me for responding.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
    Sunshyn2005 - I work on behalf of HP

  • Spool not generated in some condition

    Requirement :Developing a data transfer program. Approach used is Call Transaction in S mode.
    In some cases(if Receiving Storage Location is PKGX) I need to load only MB11 and other cases I need to load 3 transaction sequentially – MB11 creates Mat. Doc. No. which in turn passed to the LT06 to create TO(Transfer Order) and the TO passed to LT12 to confirm TO.
    Problem – When I run it in background(it generates report in foreground), job finished successfully, data is loaded into system and spool status shown as error ONLY IF ALL THE 3 TRANSACTIONS CALLED AND LOADED.
    I debugged the Batch Job(using t-code JDBG) line by line output,contents are writen to output but at the end spool goes into error and report is not visible.
    In all other cases like messages/outputs due to record not correct or/and only MB11 is to be processed, spool is generated with status Waiting and report is visible.
    Statement at top –
    REPORT ZL6C_LOAD_INVENTORY_WM_SLOC
    NO STANDARD PAGE HEADING
    MESSAGE-ID ZOLSC_AS
    LINE-COUNT 65
    LINE-SIZE 148.
    It works if I set line-size as 132 .
    To overcome this I used FM GET_PRINT_PARAMETER with various cominations of parameter passed but it doesn’t work –
    CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
    COPIES = L_C_ONE
    DEPARTMENT = L_C_SYSTEM
    DESTINATION = L_C_LOCL
    EXPIRATION = L_C_2
    LAYOUT = L_C_X_65_255
    LINE_COUNT = L_C_65
    LINE_SIZE = L_C_255
    LIST_NAME = L_LIST_NAME
    LIST_TEXT = L_LIST_TEXT
    MODE = 'BATCH'
    NEW_LIST_ID = G_C_X
    NO_DIALOG = G_C_X
    RECEIVER = L_C_SAP
    RELEASE = G_C_X
    SAP_COVER_PAGE = G_C_X
    REPORT = SY-REPID
    USER = SY-UNAME
    IMPORTING
    OUT_PARAMETERS = L_PARAMS
    EXCEPTIONS
    ARCHIVE_INFO_NOT_FOUND = 1
    INVALID_PRINT_PARAMS = 2
    INVALID_ARCHIVE_PARAMS = 3
    OTHERS = 4
    IF SY-SUBRC = 0 AND NOT L_PARAMS IS INITIAL.
    NEW-PAGE PRINT ON PARAMETERS L_PARAMS NO DIALOG NEW-SECTION.
    G_SPOOL = 'X'.
    ENDIF.
    Also when I use this FM under INITIALIZATION then it generates the spool but content written at TOP_OF_PAGE not displayed. When I use it under START-OF-SELECTION, problem still remain same.
    Please Suggest
    thanks
    Sonal

    Hello All,
    I checked in SM58. It showed an error.
    I checked my function module attributes. It was normal. Changed it to Remote enabled.
    Now spool is generated.
    Regards,
    Kausthub

  • Spool request generated twice

    Dear all,
    I'm facing a very strange behavior while printing sales order confirmation from va01
    in SAP ECC5.0.
    I've got access sequences and condition records in order to print out immediately the form at saving, based on sales org/doc type.
    Among 3 different doc type, only one is wrongly output twice when saving, without any explanations : no messages number set up in communication no TDCOPIES , output type set up ok and so on...
    I really check around the whole things to find out a potential reason of this but without success.
    Other doc type call same smartforms and print program but correctly issue only one output.
    Where else could I look on to?
    Please advice.
    Regards.

    i know the table for spool request :  TSP01
    But how should i link it to background job name ?
    i want the link between background job name and spool request generated by it......
    TBTCPV is the view but it stores only one spool request.....rather than multiple spoolreq generated by background job..

  • Debug Error! Abnormal program termination

    I have a client that is using Adobe LiveCycle Designer ES2. She is able to open up the document but when she clicks on the Preview PDF tab she's getting a Microsoft Visual C++ Debug Library dialogue box that has the following information:
    Debug Error!
    Program: ...rogram Files\Adobe\Acrobat 10.0\Designer 9.0\FormsDesigner.exe
    abnormal program termination
    (press Retry to debug the application)
    Abort     Retry     Ignore
    - Ran a repair to Adobe Acrobat and this didn't help.
    - Checked the revision level and from what I can tell she's got SP2 installed.
    - Happens on any documents she wants to Preview PDF's in.
    Running on Windows XP Pro SP3
    Adobe Acrobat Pro X
    Any suggestions??

    Thanks for the quick response...unfortunately getting the same error message after renaming the "Designer" folder under her profile.
    Tried doing the same function of Previewing the form under my profile, that has local admin privilages and same error.
    Removed the  LifeCycle Designer from the Adobe install and then reinstalled it and go figure it works. :-)
    Thanks
    thread can be closed and helpful points awarded to 'radzmar'

  • Program terminated: Time limit exceeded, ABAP performance, max_wprun_time

    Hi,
    I am running an ABAP program, and I get the following short dump:
    Time limit exceeded. The program has exceeded the maximum permitted runtime and has therefore been terminated. After a certain time, the program terminates to free the work processfor other users who are waiting. This is to stop work processes being blocked for too long by
    - Endless loops (DO, WHILE, ...),
    - Database acceses with large result sets,
    - Database accesses without an apporpriate index (full table scan)
    - database accesses producing an excessively large result set,
    The maximum runtime of a program is set by the profile parameter "rdisp/max_wprun_time". The current setting is 10000 seconds. After this, the system gives the program a second chance. During the first half (>= 10000 seconds), a call that is blocking the work process (such as a long-running SQLstatement) can occur. While the statement is being processed, the database layer will not allow it to be interrupted. However, to stop the program terminating immediately after the statement has been successfully processed, the system gives it another 10000 seconds. Hence the maximum runtime of a program is at least twice the value of the system profile parameter "rdisp/max_wprun_time".
    Last error logged in SAP kernel
    Component............ "NI (network interface)"
    Place................ "SAP-Dispatcher ok1a11cs_P06_00 on host ok1a11e0"
    Version.............. 34
    Error code........... "-6"
    Error text........... "connection to partner broken"
    Description.......... "NiPRead"
    System call.......... "recv"
    Module............... "niuxi.c"
    Line................. 1186
    Long-running programs should be started as background jobs. If this is not possible, you can increase the value of the system profile parameter "rdisp/max_wprun_time".
    Program cannot be started as a background job. We have now identified two options to solve the problem:
    - Increase the value of the system profile parameter "rdisp/max_wprun_time"
    - Improve the performance of the following SELECT statement in the program:
    SELECT ps_psp_pnr ebeln ebelp zekkn sakto FROM ekkn
    INTO CORRESPONDING FIELDS OF TABLE i_ekkn
    FOR ALL ENTRIES IN p_lt_proj
    WHERE ps_psp_pnr = p_lt_proj-pspnr
    AND ps_psp_pnr > 0.
    In EKKN we have 200 000 entries.
    Is there any other options we could try?
    Regards,
    Jarmo

    Thanks for your help, this problem seems to be quite challenging...
    In EKKN we have 200 000 entries. 199 999 entries have value of 00000000 in column ps_psp_pnr, and only one has a value which identifies a WBS element.
    I believe the problem is that there isn't any WBS element in PRPS which has the value of 00000000. I guess that is the reason why EKKN is read sequantially.
    I also tried this one, but it doesn't help at all. Before the SELECT statement is executed, there are 594 entries in internal table p_lt_proj_sel:
      DATA p_lt_proj_sel LIKE p_lt_proj OCCURS 0 WITH HEADER LINE.
      p_lt_proj_sel[] = p_lt_proj[].
      DELETE p_lt_proj_sel WHERE pspnr = 0.
      SORT p_lt_proj_sel by pspnr.
      SELECT ps_psp_pnr ebeln ebelp zekkn sakto FROM ekkn
      INTO CORRESPONDING FIELDS OF TABLE i_ekkn
      FOR ALL ENTRIES IN p_lt_proj_sel
      WHERE ps_psp_pnr = p_lt_proj_sel-pspnr.
    I also checked that the index P in EKKN is active.
    Can I somehow force the optimizer to use the index?
    Regards,
    Jarmo

  • Job finished successfully but Spool not generated(no spool icon)

    I am generating a report which . When the program in scheduled, the job completed successfully but spool icon is not available. Could any one suggest us the reason why spool has not generated. Thanks in advance!

    Hi,
    When executing report, Spool gets generated only when an Output is generated. Please check if output exits for the selection criteria.
    Also check any special mechanisms are used that diverse the ouput when executed in background.

  • Spool Not Generated Conditionally

    <b>Requirement :</b>Developing a data transfer program. Approach used is Call Transaction in S mode.
    In some cases(if Receiving Storage Location is PKGX) I need to load only MB11 and other cases I need to load 3 transaction sequentially – MB11 creates Mat. Doc. No. which in turn passed to the LT06 to create TO(Transfer Order) and the TO passed to LT12 to confirm TO.
    <b>Problem –</b> When I run it in background(it generates report in foreground), job finished successfully, data is loaded into system and spool status shown as error ONLY IF ALL THE 3 TRANSACTIONS CALLED AND LOADED.
    <u>I debugged the Batch Job(using t-code JDBG) line by line output,contents are writen to output but at the end spool goes into error and report is not visible</u>.
    In all other cases like messages/outputs due to record not correct or/and only MB11 is to be processed, spool is generated with status Waiting and report is visible.
    <b>Statement at top –</b> REPORT ZL6C_LOAD_INVENTORY_WM_SLOC
    NO STANDARD PAGE HEADING
    MESSAGE-ID ZOLSC_AS
    LINE-COUNT 65
    LINE-SIZE 148.
    <u><b>It works if I set line-size as 132 .</b></u>
    To overcome this I used FM GET_PRINT_PARAMETER with various cominations of parameter passed but it doesn’t work –
    CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
    COPIES = L_C_ONE
    DEPARTMENT = L_C_SYSTEM
    DESTINATION = L_C_LOCL
    EXPIRATION = L_C_2
    LAYOUT = L_C_X_65_255
    LINE_COUNT = L_C_65
    LINE_SIZE = L_C_255
    LIST_NAME = L_LIST_NAME
    LIST_TEXT = L_LIST_TEXT
    MODE = 'BATCH'
    NEW_LIST_ID = G_C_X
    NO_DIALOG = G_C_X
    RECEIVER = L_C_SAP
    RELEASE = G_C_X
    SAP_COVER_PAGE = G_C_X
    REPORT = SY-REPID
    USER = SY-UNAME
    IMPORTING
    OUT_PARAMETERS = L_PARAMS
    EXCEPTIONS
    ARCHIVE_INFO_NOT_FOUND = 1
    INVALID_PRINT_PARAMS = 2
    INVALID_ARCHIVE_PARAMS = 3
    OTHERS = 4
    IF SY-SUBRC = 0 AND NOT L_PARAMS IS INITIAL.
    NEW-PAGE PRINT ON PARAMETERS L_PARAMS NO DIALOG NEW-SECTION.
    G_SPOOL = 'X'.
    ENDIF.
    Also when I use this FM under INITIALIZATION then it generates the spool but content written at TOP_OF_PAGE not displayed. When I use it under START-OF-SELECTION, problem still remain same.
    Please Suggest
    thanks
    Sonal

    Use FM  : RSPO_OUTPUT_SPOOL_REQUEST
    Reward Points if it is helpful
    Thanks
    Seshu

  • Spool not generated for some conditions

    <b>Requirement :</b>Developing a data transfer program. Approach used is Call Transaction in S mode.
    In some cases(if Receiving Storage Location is PKGX) I need to load only MB11 and other cases I need to load 3 transaction sequentially – MB11 creates Mat. Doc. No.  which in turn passed to the LT06 to create TO(Transfer Order) and the TO passed to LT12 to confirm TO.
    <b>Problem –</b> When I run it in background(it generates report in foreground), job finished successfully, data is loaded into system and spool status shown as error ONLY IF ALL THE 3 TRANSACTIONS CALLED AND LOADED.
    <u>I debugged the Batch Job(using t-code JDBG) line by line output,contents are writen to output but at the end spool goes into error and report is not visible.</u>
    In all other cases like messages/outputs due to record not correct  or/and  only MB11 is to be processed, spool is generated with status Waiting and report is visible.
    <b>Statement at top –</b>
    REPORT  ZL6C_LOAD_INVENTORY_WM_SLOC
            NO STANDARD PAGE HEADING
            MESSAGE-ID ZOLSC_AS
            LINE-COUNT 65
            LINE-SIZE  148.
    <u>It works if I set line-size as 132 .</u>
    To overcome this I used FM GET_PRINT_PARAMETER with various cominations of parameter passed but it doesn’t work –
    CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
    COPIES                 = L_C_ONE
           DEPARTMENT             = L_C_SYSTEM
           DESTINATION            = L_C_LOCL
           EXPIRATION             = L_C_2
           LAYOUT                 = L_C_X_65_255
           LINE_COUNT             = L_C_65
           LINE_SIZE              = L_C_255
           LIST_NAME              = L_LIST_NAME
           LIST_TEXT              = L_LIST_TEXT
           MODE                   = 'BATCH'
           NEW_LIST_ID            = G_C_X
           NO_DIALOG              = G_C_X
           RECEIVER               = L_C_SAP
           RELEASE                = G_C_X
           SAP_COVER_PAGE         = G_C_X
           REPORT                 = SY-REPID
           USER                   = SY-UNAME
    IMPORTING
           OUT_PARAMETERS         = L_PARAMS
    EXCEPTIONS
           ARCHIVE_INFO_NOT_FOUND = 1
           INVALID_PRINT_PARAMS   = 2
           INVALID_ARCHIVE_PARAMS = 3
           OTHERS                 = 4
       IF SY-SUBRC = 0 AND NOT L_PARAMS IS INITIAL.
         NEW-PAGE PRINT ON PARAMETERS L_PARAMS  NO DIALOG NEW-SECTION.
         G_SPOOL = 'X'.
       ENDIF.
    Also when I use this FM under INITIALIZATION then it generates the spool but content written at TOP_OF_PAGE not displayed. When I use it under START-OF-SELECTION, problem still remain same.
    Please Suggest
    thanks
    Sonal

    Hi,
      All spool requests will be stored in TSP01 table
    TSP01 - Spool Requests
    field name for Spool request number is RQIDENT
    Hi,
    Take a look at OSS Note 422136 which states:
    "2. You can only store one spool request even if a step generates several spool requests during processing. The application is responsible for a "spool overview" in this case. If a step generates several spool requests during processing, only one request can be stored. In this case, the application report should issue the number with a message when writing a spool request so that it is then displayed in the job log."
    Also take a look at OSS Note 519059 which further supports the case that you must capture the individual spool numbers as they are being created (i.e. within the job step's program). The note contains the following:
    8] Question: How are the spool requests assigned?
    Answer: The step information is stored in table TBTCP. This has space for exactly one spool request (field LISTIDENT). If a step generates several spool requests during the processing, only one can be stored. In this case the application is responsible for a "spool overview
    <b>Reward points</b>
    Regards

  • Kgefec:fatal error0; OCI-21503:program terminated by fatal error; OCI-04030

    Hi expert,
    I've hit the following errors when I tried to start my application using the corbaloc call:- Would appreciate your expertise adv and helps, please~!
    dlys_storage_prep_srvr -ename INT -pname DLYS_PREP_SRVR -ORBInitRef NameService=corbaloc:iiop:uxkulaix01:19001/NameService -ORBInitRef ImplRepoService=corbaloc:iiop:uxkulaix01:19002/ImplRepoService -ORBInitRef LoadManager=corbaloc:iiop:uxkulaix01:19007/LoadManager -ORBUseIMR 1 -instance DLYS_PREP_SRVR_2 -phaseID 1 -jobID 2109 -requestID 0 -scheduleUser SYSTEM
    kgefec: fatal error 0
    kgefec: fatal error 0
    kgefec: fatal error 0
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 512 bytes (Alloc statemen,pref col alloc)
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 224 bytes (Alloc statemen,pref col alloc)
    kgefec: fatal error 0
    kgefec: fatal error 0
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 272 bytes (Alloc statemen,pref col alloc)
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 176 bytes (Alloc statemen,pref col alloc)
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 392 bytes (Alloc statemen,pref col alloc)
    Errors in file :
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 272 bytes (Alloc statemen,pref col alloc)
    kgefec: fatal error 0
    Errors in file :
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 176 bytes (Alloc statemen,pref col alloc)
    Errors in file :
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 392 bytes (Alloc statemen,pref col alloc)
    ----- Call Stack Trace -----
    Errors in file :
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 512 bytes (Alloc statemen,pref col alloc)
    ----- Call Stack Trace -----
    Errors in file :
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 224 bytes (Alloc statemen,pref col alloc)
    calling call entry argument values in hex
    ----- Call Stack Trace -----
    location type point (? means dubious value)
    calling call entry argument values in hex
    calling call entry argument values in hex
    location type point (? means dubious value)
    location type point (? means dubious value)
    ----- Call Stack Trace -----
    kgefec: fatal error 0
    ----- Call Stack Trace -----
    calling call entry argument values in hex
    calling call entry argument values in hex
    location type point (? means dubious value)
    location type point (? means dubious value)
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 536 bytes (Alloc statemen,pref col alloc)
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 656 bytes (Alloc statemen,pref col alloc)
    Errors in file :
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 536 bytes (Alloc statemen,pref col alloc)
    ----- Call Stack Trace -----
    Errors in file :
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 656 bytes (Alloc statemen,pref col alloc)
    calling call entry argument values in hex
    location type point (? means dubious value)
    ----- Call Stack Trace -----
    calling call entry argument values in hex
    location type point (? means dubious value)
    kgefec: fatal error 0
    OCI-21503: program terminated by fatal error
    OCI-04030: out of process memory when trying to allocate 296 bytes (Alloc statemen,pref col alloc)
    SQL> SQL> select * from v$pgastat;
    NAME VALUE UNIT
    aggregate PGA target parameter 314572800 bytes
    aggregate PGA auto target 243984384 bytes
    global memory bound 62914560 bytes
    total PGA inuse 43478016 bytes
    total PGA allocated 85145600 bytes
    maximum PGA allocated 85963776 bytes
    total freeable PGA memory 15204352 bytes
    process count 50
    max processes count 51
    PGA memory freed back to OS 10616832 bytes
    total PGA used for auto workareas 0 bytes
    NAME VALUE UNIT
    maximum PGA used for auto workareas 155648 bytes
    total PGA used for manual workareas 0 bytes
    maximum PGA used for manual workareas 0 bytes
    over allocation count 0
    bytes processed 30577664 bytes
    extra bytes read/written 0 bytes
    cache hit percentage 100 percent
    recompute count (total) 516
    19 rows selected.
    # Instance Identification
    instance_name=ICTINT
    # Database Identification
    db_domain=""
    db_name=ICTINT
    # Cache and I/O
    db_block_size=8192
    db_cache_advice=ON
    db_keep_cache_size=0
    #db_file_multiblock_read_count=32
    #db_writer_processes=4
    db_files=200
    disk_asynch_io=FALSE
    filesystemio_options=NONE
    # Optimizer Settings
    optimizer_index_caching=50
    optimizer_index_cost_adj=50
    optimizer_mode=FIRST_ROWS_1000
    query_rewrite_enabled=TRUE
    star_transformation_enabled=FALSE
    # Cursors and Library Cache
    open_cursors=1500
    cursor_sharing=FORCE
    cursor_space_for_time=TRUE
    # Diagnostics and Statistics
    background_dump_dest=/emcoracle/admin/ICTINT/bdump
    core_dump_dest=/emcoracle/admin/ICTINT/cdump
    user_dump_dest=/emcoracle/admin/ICTINT/udump
    timed_statistics=TRUE
    # File Configuration
    control_files=("/oradata/ICTINT/data/control/control_01.ctl",
    "/oradata/ICTINT/index/control/control_02.ctl")
    # Job Queues
    job_queue_processes=10
    # Miscellaneous
    aq_tm_processes=1
    compatible=10.2.0
    log_checkpoints_to_alert=TRUE
    recyclebin=OFF
    # Pools
    #java_pool_size=0
    #large_pool_size=16777216
    #shared_pool_size=524288000
    sga_max_size=2G
    sga_target=2G
    # Processes and Sessions
    processes=250
    # Redo Log and Recovery
    fast_start_mttr_target=300
    # Security and Auditing
    remote_login_passwordfile=EXCLUSIVE
    audit_file_dest=/emcoracle/admin/ICTINT/audit
    #audit_trail=true
    # Sort, Hash Joins, Bitmap Indexes
    pga_aggregate_target=100M
    workarea_size_policy=AUTO
    # System Managed Undo and Rollback Segments
    undo_management=AUTO
    undo_retention=900
    undo_tablespace=UNDOTBS1
    # Archiving
    #log_archive_start=TRUE
    #log_archive_dest_1='location=${ARCHIVELOG}'
    log_archive_format=ICT_%d_ARC_%t_%s_%r.arc

    That error means that Oracle is not allowed to allocate the memory by the operating system.
    This is not a bug of Oracle; the problem must be somewhere else.
    - How much memory has the process allocated when it produces this error?
    - Did you set the per-process memory limits of the operating system high enough?
    - Did you start the Java Virtual Machine with a sufficient maximal stack size?
    If the problem only occurs after a longer runtime, you might also consider the
    possibility that your code has a memory leak.
    Yours,
    Laurenz Albe

Maybe you are looking for