Error SG 105 when executing transaction KKAK

Hi,
When executing transaction KKAK (Results Analysis) for month end processing we get the following error for a especific sales order:
"E SG105 Enter rate CAD/USD rate type P for 01/01/2010 in the system settings"
My question will be: why is the system asking to enter that rate which we never use. We use rate M but not P. Is that really necessary?
We are using release 470, level 003, Support Package SAPKH47031.
Thanks for your help.

HI,
in the year-depending parameters of the controlling area version definition, the ex.rate type (P) and the valid-from-date is defined, thats why P is used.
Best regards, Christian

Similar Messages

  • SQL error 3113 occurred when executing EXEC SQL.

    Hi,
    We are facing one typical problem, One background is failing regularly with
    below dump. as we now got all notes giving information, if database  restarted
    taking backup, these type of failures occur, but our database is only down for backup once in a week, but it is failing with frequenly.
    in this two servers are located in different place, in this job tries to connect
    another server to get material statistics.
    It is giving some error message in sm21 with
    SQL error 3113 occurred when executing EXEC SQL.
    work procees in reconnect mode.
    all notes saying these types of dump occur when database restared, but this dump
    even though database is up.
    below is short dump, please can anyone help me from this problem.
    ABAP runtime errors    DBIF_DSQL2_SQL_ERROR
          Occurred on    08.01.2007 at 00:30:28
    >> Short dump has not been completely stored. It is too big.
    SQL error 3113 occurred when executing EXEC SQL.
    What happened?
    The error occurred in the current database connection "AZ1".
    What can you do?
    Note the actions and input that caused the error.
    Inform your SAP system administrator.
    You can print out this message by choosing "Print". Transaction ST22
    allows you to display and manage termination messages, including keeping
    them beyond their normal deletion date.
    Error analysis
    How to correct the error
    Database error text........: "ORA-03113: end-of-file on communication channel#"
    Triggering SQL statement...: "select mara.groes, mara.brgew, mara.ntgew,
    mara.gewei, mara.volum, mara.voleh, mara.mstae, mara.mstde, mara.prdha,
    marc.matnr, marc.werks, marc.mmsta, marc.mmstd from sapr3.mara, sapr3.m
    where sapr3.mara.mandt = sapr3.marc.mandt and sapr3.mara.matnr =
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).
    If the error occurred in a non-modified SAP program, you may be
    able to find a solution in the SAP note system.
    If you have access to the note system yourself, use the following
    search criteria:
    "DBIF_DSQL2_SQL_ERROR"
    "ZM2431216 " or "ZM2431216 "
    "EXTRACT_GENERAL_DATA"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
      To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
      To obtain this, call the system log with Transaction SM21
      and select the "Print" function to print out the relevant
      part.
    3. If the programs are your own programs or modified SAP programs,
      supply the source code.
      To do this, you can either use the "PRINT" command in th
      print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error o
      or which actions and input led to the error.
    System environment
    SAP Release.............. "46C"
    Application server....... "essceu3"
    Network address.......... "172.19.119.198"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C7ADBD4C00"
    Database server.......... "ukblx176"
    Database type............ "ORACLE"
    Database name............ "EU3"
    Database owner........... "SAPR3"
    Character set............ "es_ES.ISO8859-1"
    SAP kernel............... "46D"
    Created on............... "Jul 9 2006 20:26:33"
    Created in............... "AIX 1 5 00447C4A4C00"
    Database version......... "OCI_920__OCI_7_API "
    Patch level.............. "2257"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 8.0.5.., ORACLE 8.0.6.., ORACLE
    8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE 10.2.0.."
    SAP database version..... "46D"
    Operating system......... "AIX 1 4, AIX 2 4, AIX 3 4, AIX 1 5, AIX 2 5, AIX 3
    5, , System build information:,                                      , LCHN :
    841480"
    User, transaction...
    Client.............. 600
    User................ "MPZMMES"
    Language key........ "S"
    Transaction......... " "
    Program............. "ZM2431216 "
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where termination occurred
    The termination occurred in the ABAP/4 program "ZM2431216 " in
    "EXTRACT_GENERAL_DATA".
    The main program was "ZM2431216 ".
    The termination occurred in line 980
    of the source code of program "ZM2431216 " (when callin
    The program "ZM2431216 " was started as a background jo
    Source code extract
    009500              mara.ntgew,
    009510              mara.gewei,
    009520              mara.volum,
    009530              mara.voleh,
    009540              mara.mstae,
    009550              mara.mstde,
    009560              mara.prdha,
    009570              marc.matnr,
    009580              marc.werks,
    009590              marc.mmsta,
    009600              marc.mmstd
    009610        into :w_ops-groes,
    009620              :w_ops-brgew,
    009630              :w_ops-ntgew,
    009640              :w_ops-gewei,
    009650              :w_ops-volum,
    009660              :w_ops-voleh,
    009670              :w_ops-mstae,
    009680              :w_ops-mstde,
    009690              :w_ops-prdha,
    009700              :w_ops-matnr,
    009710              :w_ops-werks,
    009720              :w_ops-mmsta,
    009730              :w_ops-mmstd
    009740        from sapr3.mara, sapr3.marc
    009750        where sapr3.mara.mandt = sapr3.marc.mandt
    009760          and sapr3.mara.matnr = sapr3.marc.matnr
    009770          and sapr3.mara.mandt = :p_mandt
    009780          and sapr3.mara.matnr = :w_ebs-matnr
    009790          and sapr3.marc.werks = :p_owerks
        >    ENDEXEC.
    009810  endform.                    " extract_general_data
    009820  *&
    009830  *&      Form  append_i_ops
    009840  *&
    009850  *      Appends W_OPS to I_OPS
    009860  *
    009870  form append_i_ops.
    009880    append w_ops to i_ops.
    009890  endform.                    " append_i_ops
    009900  *&
    009910  *&      Form  extract_material_description
    009920  *&
    009930  *      Extracts a Material Description from the remote database an
    009940  *      modifies the current record in I_OPS.
    009950  *
    009960  *        >P_SPRAS  Language Key
    009970  *
    009980  form extract_material_description using    p_spras.
    009990    EXEC sql performing set_langauge.
    Contents of system fields
    SY field contents..................... SY field contents............
    SY-SUBRC 0                            SY-INDEX 0
    SY-TABIX 1                            SY-DBCNT 1
    SY-FDPOS 18                            SY-LSIND 0
    SY-PAGNO 0                            SY-LINNO 1
    SY-COLNO 1
    Chosen variables
    Name.......................... Contents.1........2........3....+..
    W_EBS-PRAT4
                                  2
                                  0
    W_OPS-GROES
                                  22222222222222222222222222222222
                                  00000000000000000000000000000000
    W_OPS-BRGEW                    #######
                                  0000000
                                  000000C
    W_OPS-NTGEW                    #######
                                  0000000
                                  000000C
    regards,
    krishnaiah.

    Hi,
    This is usually a SERVER SIDE DATABASE PROBLEM or SQLNET LISTENER (server side) PROBLEM.  The client side should initially be ignored and instead the server should be investigated. In rare cases, this can be caused by client
    side memory or other resource problem, or a DLL version mismatch, but this is
    unlikely.
    Enlist the assistance of your DBA.  Then reproduce the ORA-3113 error on your
    client application.  Ask your DBA to look at the database side Alert.log and
    trace files and look for ANY activity.  Any activity that coincides with your
    ORA-3113 will be a clue.
    REgards
    Vinod

  • Error in sxmb_moni when executing

    hi all,
    i get error in sxmb_moni  when executing (monitor for processed xml messages)
    the messages states that "system error occured during persist".how to clear this error message.

    Hi Allen
    Did you configure the right interface mapping in the interface determination? Did you activate your interface mapping? Plz have a look to transaction SXI_CACHE.
    this error is beacuse your mapping progrm might be wrong, just check the interface mapping test with mapping program ( it will be error) and with out mapping program ( no error will be there)
    cross check your mapping program any madt fields are you missing?
    Thanks!

  • When executing Transaction MRLH, it says "Function not currently possible"

    Hi All
    When executing Transaction MRLH, it says "Function not currently possible" which is the exact scenario discussed in Note 192664. But this note is valid only for 4.X where our system is ECC5. So if we try to implement this note it says "Note cannot be implemented".
    But still the error message is comming.
    Any ideas regarding what we can do to over come the scenario?
    BR
    Thanura

    Hi all,
    I am getting the exact same dump.
    And in my case, I am not providing any input.
    I have made a non-obligatory selection screen  parameter, and then appended that to a table type of the local structure of select options that i made.
    Then i am passing this to a fm as an importing parameter.
    And it is giving dump on the first query in the fm.
    If I don't use the fm, then in that case, it is working fine, and if the field is blank it fetches all records,
    but why it is not working now..., any ideas???

  • Error in BDC when executed in back ground

    Hi All,
    We are working on a BDC interface for Material Master Basic Data Add or Change using SAP 4.7. The interface is working fine with CALL TRANSACTION (N,A screen modes), BDC foreground and Display error modes.
    When the same session is executed in background mode it is not getting processed.
    The error is caused while calling screen 2031 which uses a  control. The diagnosis we received is given below
    Control Framework: Fatal error - GUI cannot be reached
    Message no. DC006
    Diagnosis
    When the Control Framework is started, the system checks whether the installed GUI supports frontend components such as controls. This check failed; the causes may be as follows:
    1.) The program is running in the background
    2.) A transaction was called using CALL TRANSACTION ... STARTING IN BACKGROUND TASK.
    Procedure
    Programs that run in the background cannot address controls on the frontend. In this case, the application must either include a fallback that does not depend on the user interface, or the program or transaction must detect for itself that is running in the background and terminate itself.
    Is there any alternate method available for running the session in background with the controls?
    Please help us in this regard.
    Thanks in advance.
    Kathirvel Balakrishnan

    Hi Kathirvel!
    In description of error: 'In this case, the application must either include a fallback that does not depend on the user interface, or the program or transaction must detect for itself that is running in the background and terminate itself.'
    Obviously in material master only second option was implemented - termination.
    Alternative: using IDOCs or BAPIs like BAPI_MATERIAL_SAVEDATA, BAPI_MATERIAL_MAINTAINDATA_RT.
    Regards,
    Christian

  • LE-TRM: Error message LTRM023 when executing LROUT

    Dear all,
    When executing the transaction LROUT, I get the error message LTRM023 "Site is not defined". I checked table LROUT and it is actually empty.
    However, I created appropriate settings in maintenance views V_T340DT, V_T347A, V_LLOCT and all other SPRO entries related to my TRM site. Futhermore, I implemented all OSS notes related to LROUT or TRM route.
    Then, I activated debug mode.
    > Issue 1:
    Main program SAPLLTRM
    Source code LLTRMU09
    Function LTRM_LLOCT_READ
    IF    ss_lloct IS INITIAL                        
       OR ss_lloct-locat <> i_locat.                 
      SELECT SINGLE * FROM lloct INTO ss_lloct       
        WHERE locat = i_locat.                       
    The issue is that settings of table LLOCT are not red. I had to manually set i_locat = "site" to process further.
    > Issue 2:
    Main program SAPLLTRS_SERVICES
    Source code LLTRS_SERVICESU08
    Function LTRS_LRSTY_READ
    SELECT * FROM lrsty INTO TABLE it_lrsty
           WHERE locat = i_locat.          
    IF sy-subrc <> 0.                      
      RAISE table_lrsty_not_maintained.    
    ENDIF.                                 
    But sy-subrc = 4..., so system raise error message table_lrsty_not_maintained. However, table LRSTY is maintened.
    Did you already have this issue? How did you solve it?
    In advance, thx a lot for your help.
    PS: I play with ECC 5.0, Release 500, SP SAPKGPAC05. With nearly equivalent settings in ECC 6.0, Release 604, SP SAPK-60402INEADFPS, I don't have any trouble running LROUT...

    Hi,
    Have you found the answer at your problem.
    I know you posted it one year ago but I am in the same case.
    So, if you have found the solution, I would be very pleased if you could help me.
    Edited by: FlorianFFF on Aug 26, 2011 3:03 PM

  • Workflow Triggering twice when executing transaction cj21n

    Hi Experts,
    when i am executing transaction cj21n my workflow is triggering twice but earlier  it was working fine ..
    please provide your input on the same
    Thanks
    Deepanker Dwivedi

    Hi,
    The 'event' which  mapped to workflow triggered twice or another event may added to the workflow
    1) Did you give additional event for the workflow in the Basic Data -> Start events, if yes remove that event and test it.
    2) If 'No', In the SPRO configurations some settings might have changed, Check with your Function Consultant ask  any changes they done in the SPRO settings related to the T.code cj21n.
    Regards,
    Surjith

  • HTTP Error: 401 unauthorized when executing a costcenter report.

    Hi.
    I get this HTTP error when executing an costcenter report.
    The steps I do is following.
    Call upp the report Y_D02_77000xxx
    Under the "kostenstellen:Selection I Fill in this values.
    Controlling area
    Fiscal Year
    From Period
    To     Period
    Plan version
    and finally i enter the "Cost Center group"
    Then i press "execute" and get the result for differrent Cost Element, i get 2 lines "*Total" and
    "**Over/underabsorption"
    Now i doubleclick Over/underabsorption and select report "Cost Centers: Actual Line Items"
    Now i Should get a new window woth results but instead i get a blank screen with the errormessage:
    "HTTP error: 401 unauthorized"
    This procedure worked fine until a couple of weeks ago.
    Anyone have any ideas about what could be the problem?
    Regards Johan

    You might want to check all of your connections in SM59. When you get the 401 error, this is sometimes due to a connection failure (bad password and so on) in the RFC connections (this can also happen if you are using the Content Manager).
    Hope that helps.
    J. Haynes

  • Oracle error message 1445 when executing a SAP query

    Hello experts,
    We are running a ECC6.0 DEV and ACC system on an Oracle database (release 10.2.0.2.0).
    When I execute a query in SQ01 on our acceptance system, a database error occurs (ORA-1445). However, when I execute the same query on our DEV system, this error does not occur.
    I managed to find that this error might be due to a bug in Oracle and that this bug occurs when executing a query with many joins (more than 6), which indeed I am doing. What I do not understand is that this query does run on DEV without errors but not on ACC.
    Does anyone have a suggestion?
    Thanks and regards,
    Alfio Esposito

    Check if note "1126517 - ORA-1445 or incorrect values with 10.2" applies and also check if you have the same patches on DEV + PRD installed (using opatch lsinventory)
    Markus

  • Error "Mutating table" when execute a trigger

    Hi all,
    I'm a newbie in oracle. Recently i do some database migration from sql server 2005 to oracle 11g. Some of my table are using trigger which is not running in oracle. It has error "mutating table" when i'm trying to update some table. According to some information i got from the internet this can be solve by creating 1 packages and 3 trigger, but i found this article http://www.oracle.com/technetwork/issue-archive/2008/08-sep/o58asktom-101055.html which confuse me much. It says that the trigger is not allowed to be used for multiple user, meanwhile my application was for multiple user. What should i do then ?
    *sorry for my bad english                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Hi,
    Sorry for my late reply, below is one of my trigger that causes error. This trigger was automatically created when im doing the migration.
    create or replace
    TRIGGER "DBO_ORACLE_240312".tgrRwyPktUpd
    -- =============================================
    -- Author:          Debora Farah Rasul
    -- Create date: 09.02.2012
    -- Description:     Update Riwayat Pangkat untuk data SKCPNS/SKPNS
    -- =============================================
    AFTER UPDATE
    ON RiwayatPangkat
    FOR EACH ROW
    DECLARE
    v_temp NUMBER(1, 0) := 0;
    BEGIN
    IF NULL/*TODO:TRIGGER_NESTLEVEL()*/ > 2 THEN
    RETURN;
    END IF;
    --SQL Server BEGIN TRANSACTION;
    BEGIN
    SELECT 1 INTO v_temp
    FROM DUAL
    WHERE ( ( SELECT :NEW.isTrigger
    FROM DUAL ) = -1 );
    EXCEPTION
    WHEN OTHERS THEN
    NULL;
    END;
    IF v_temp = 1 THEN
    BEGIN
    MERGE INTO SKCPNS
    USING (SELECT :NEW.PegawaiID AS PegawaiID, :NEW.NoNota AS NoNota, :NEW.NoSK AS NoSK, :NEW.TglSK AS TglSK, :NEW.TMTPangkat AS TMTPangkat, :NEW.PangkatID AS PangkatID
    FROM dual) src
    ON (SKCPNS.PegawaiID = src.PegawaiID )
    WHEN MATCHED THEN UPDATE SET NoNota = src.NoNota,
    NoSK = src.NoSK,
    TglSK = src.TglSK,
    TMTCPNS = src.TMTPangkat,
    PangkatID = src.PangkatID;
    END;
    ELSE
    BEGIN
    SELECT 1 INTO v_temp
    FROM DUAL
    WHERE ( ( SELECT :NEW.isTrigger
    FROM DUAL ) = -2 );
    EXCEPTION
    WHEN OTHERS THEN
    NULL;
    END;
    IF v_temp = 1 THEN
    BEGIN
    MERGE INTO SKPNS
    USING (SELECT :NEW.PegawaiID AS PegawaiID, :NEW.NoSK AS NoSK, :NEW.TglSK AS TglSK, :NEW.TMTPangkat AS TMTPangkat, :NEW.PangkatID AS PangkatID
    FROM dual) src
    ON ( SKPNS.PegawaiID = src.PegawaiID )
    WHEN MATCHED THEN UPDATE SET NoSK = src.NoSK,
    TglSK = src.TglSK,
    TMTPNS = src.TMTPangkat,
    PangkatID = src.PangkatID;
    END;
    END IF;
    END IF;
    MERGE INTO RiwayatGaji
    USING (SELECT :NEW.PegawaiID AS PegawaiID, :NEW.NoUrut AS NoUrut, :NEW.NoSK AS NoSK, :NEW.TglSK AS TglSK, :NEW.TMTPangkat AS TMTPangkat, :NEW.PejabatPenetap AS PejabatPenetap, :NEW.MasaKerjaTh AS MasaKerjaTh, :NEW.MasaKerjaBl AS MasaKerjaBl, :NEW.PangkatID AS PangkatID, :NEW.JenisKP AS JenisKP
    FROM dual) src
    ON ( RiwayatGaji.PegawaiID = :NEW.PegawaiID
    AND RiwayatGaji.isTrigger = :NEW.NoUrut)
    WHEN MATCHED THEN UPDATE SET NoSK = src.NoSK,
    TglSK = src.TglSK,
    TMTSK = src.TMTPangkat,
    PejabatPenetap = src.PejabatPenetap,
    MasaKerjaTh = src.MasaKerjaTh,
    MasaKerjaBl = src.MasaKerjaBl,
    PangkatID = src.PangkatID,
    JenisKenaikan = src.JenisKP;
    END;
    *Btw thank u for the reply :)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Oracle error -6508 returned when executing JSP

    The JSP program executes a stored procedure from a package. I've recompiled the package after some changes. The JSP returns -6508 error when it is executing the procedure. The error is returned only after recompiling the stored package. What could be the problem?

    Hi,
    ORA-6508 error is returned when the stored procedure cannot be found.
    ORA-06508 PL/SQL: could not find program unit being called
    Cause: An attempt was made to call a stored program that could not be found. The program may have been dropped or incompatibly modified, or have compiled with errors.
    Action: Check that all referenced programs, including their package bodies, exist and are compatible.
    Please check the package signature and the specifications.
    Thanks,
    Rashmi.

  • Error ORA-03113 when execute procedure via OEM

    Hi All,
    I got error messages
    ORA-03113: end-of-file on communication channel
    ERROR at line 1:
    ORA-03114: not connected to ORACLE
    when execute procedure via Oracle Enterprise Manager
    Who do you know what 's the problem and how can I resolves ?
    Thanks,
    Mcka

    Solution Description:
    =====================
    The ORA-3113 error is a general error reported by Oracle client tools,
    which signifies that they cannot communicate with the oracle shadow
    process. As it is such a general error more information must be collected
    to help determine what has happened.
    This short article describes what information to collect for an
    ORA-3113 error when the Oracle server is on a Unix platform.
    General Issues:
    ===============
    1) Is it only one tool that encounters the error or
    do you get an ORA-3113 from any tool doing a similar operation?
    If the problem reproduces in SQL*Plus, use this in all tests
    below.
    2) Check if the problem is just restricted to:
    [ ] One particular UNIX user,
    [ ] Any UNIX user
    or [ ] Any UNIX user EXCEPT as the Oracle user.
    3) Check if the problem is just restricted to:
    [ ] One particular ORACLE logon
    or [ ] Any ORACLE logon that has access to the
    relevant tables.
    4) If you have a client-server configuration does this occur from:
    [ ] Any client
    [ ] Just one particular client
    or [ ] Just one group of clients ?
    If so what do these clients have in common ?
    Eg: Software release .
    5) Do you have a second server or database version where the
    same operation works correctly?

  • Runtime error when executing transaction 'PPOME'

    Hi all,
    <br>
    <br>
    <br>I 'm new to SAP and would like to beg a helping hand.
    <br>I had tired the 'free search' function in PPOME.
    <br>and I m not sure what mistake I make. When I execute t-code PPOME again, it is getting the runtime error.
    <br>
    <br>the following are the descritpion of exception by T-code ST22.
    <br>the error is related to u201CSAP_IN_ITAB_ILLEGAL_OPTIONu201D and I read the its SAP NOTE(1256059).
    <br>However, I don't how to do so that fix this problem.
    <br>May anyone help me~
    <br>
    <br>----
    <br><b>Short text</b>                                                                        
    <br>Invalid value in OPTION field of value table for IN itab operator.                           
    <br>
    <br><b>What happened?</b>                                                                               
    <br>    Error in the ABAP Application Program                                                        
    <br>                                                                               
    <br>    The current ABAP program "%_T0DQG0" had to be terminated because it has                   
    <br>    come across a statement that unfortunately cannot be executed.
    <br>
    <br><b>Error analysis</b>                                                                               
    <br>    The current ABAP/4 program attempted to execute an ABAP/4 Open SQL                           
    <br>    statement in which the WHERE condition contains an IN itab operator.                         
    <br>                                                                               
    <br>    The IN itab operator is used with internal tables which                                      
    <br>    have the following structure:                                                                
    <br>                                                                               
    <br>       SIGN(1)   OPTION(2)   LOW LIKE db_field   HIGH LIKE db_field                              
    <br>                                                                               
    <br>    The OPTION column should contain only one of the following values:                           
    <br>                                                                               
    <br>       "EQ LE GE CP BT NE LT GT NP NB"                                                           
    <br>                                                                               
    <br>    The value " " is not allowed here.                                                           
    <br>
    <br><b>How to correct the error</b>                                                                        
    <br>    Use only one of the permitted values in the OPTION column.                                   
    <br>                                                                               
    <br>    If the error occures in a non-modified SAP program, you may be able to                       
    <br>    find an interim solution in an SAP Note.                                                     
    <br>    If you have access to SAP Notes, carry out a search with the following                       
    <br>    keywords:                                                                               
    <br>                                                                               
    <br>    "SAPSQL_IN_ITAB_ILLEGAL_OPTION" " "                                                          
    <br>    "%_T0DQG0" or "%_T0DQG0"                                                                     
    <br>    "GET_OBJECTS"                                                                               
    <br>                                                                               
    <br>    If you cannot solve the problem yourself and want to send an error                           
    <br>    notification to SAP, include the following information:                                      
    <br>                                                                               
    <br>    1. The description of the current problem (short dump)                                       
    <br>                                                                               
    <br>       To save the description, choose "System->List->Save->Local File                           
    <br>    (Unconverted)".                                                                               
    <br>                                                                               
    <br>    2. Corresponding system log                                                                  
    <br>                                                                               
    <br>       Display the system log by calling transaction SM21.                                       
    <br>       Restrict the time interval to 10 minutes before and five minutes                          
    <br>    after the short dump. Then choose "System->List->Save->Local File                            
    <br>    (Unconverted)".                                                                               
    <br>                                                                               
    <br>    3. If the problem occurs in a problem of your own or a modified SAP                          
    <br>    program: The source code of the program                                                      
    <br>       In the editor, choose "Utilities->More                                                    
    <br>    Utilities->Upload/Download->Download".                                                       
    <br>                                                                               
    <br>    4. Details about the conditions under which the error occurred or which                      
    <br>    actions and input led to the error.                                                          
    <br>
    <br><b>User and Transaction</b>                                                                            
    <br>                                                                               
    <br>    Client.............. 300                                                                     
    <br>    User................ "xxxxxxxx"                                                             
    <br>    Language key........ "E"                                                                     
    <br>    Transaction......... "PPOME "                                                                
    <br>    Transactions ID..... "26F031E14FDBF1E0BB3500155D7F2106"                                      
    <br>                                                                               
    <br>    Program............. "%_T0DQG0"                                                              
    <br>    Screen.............. "SAPMSSY0 1000"                                                         
    <br>    Screen line......... 6                                                                       
    <br>
    <br>
    <br><b>Information on where terminated</b>                                                                 
    <br>    The termination occurred in the temporary subroutine pool "%_T0DQG0" in                      
    <br>    "GET_OBJECTS".                                                                               
    <br>    The main program was "OM_START_NF ".                                                         
    <br>                                                                               
    <br>    The point of termination in the source code is in line 69 of                                 
    <br>    the temporary subroutine pool "%_T0DQG0".
    <br>
    <br>Edited by: jack22000011 on Dec 29, 2011 9:05 AM
    Edited by: jack22000011 on Dec 29, 2011 9:11 AM

    Hi all,
    I am getting the exact same dump.
    And in my case, I am not providing any input.
    I have made a non-obligatory selection screen  parameter, and then appended that to a table type of the local structure of select options that i made.
    Then i am passing this to a fm as an importing parameter.
    And it is giving dump on the first query in the fm.
    If I don't use the fm, then in that case, it is working fine, and if the field is blank it fetches all records,
    but why it is not working now..., any ideas???

  • When executing transactions FB50 or FB60 get an ABAP runtime error

    After applying the latest SAP Financial support stacks and OSS Notes we get the following:
                                                                                    Too many parameters specified with PERFORM.                                                                          
    In a subroutine call, there were more parameters than in the routine definition.                                                          
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLGLIN" had to be terminated because one of the statements could not be executed.                                                                             
    This is probably due to an error in the ABAP program.                                                                               
    An exception occurred. This exception is dealt with in more detail below               
    . The exception, which is assigned to the class                                        
    'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was neither                                         
    caught nor passed along using a RAISING clause, in the procedure "G_RWIN_CHECK"        
    "(FUNCTION)"                                                                          
    Since the caller of the procedure could not have expected this exception               
    to occur, the running program was terminated.                                         
    The reason for the exception is:                                                       
    A PERFORM was used to call the routine "G_RWIN_CHECK" of the program                   
    "SAPLGLIN".                                                                           
    This routine contains exactly 3 formal parameters, but the current                     
    call contains 4 actual parameters.                                                     
    parameters.                                                                            
    We   have suspended testing for this reason.  Please help.
    Thanks,
    Barbara

    hi barbara
    not sure if this is the right forum for this post and you may not get replies
    you could try the financials forum
    SAP ERP Financials
    or the ABAP and Basis forums which you can find from the list in /community [original link is broken]

  • Documnt not posted when executed transaction FBWD

    rHi,
    When I execute FBWD transaction for returned BoE, I am getting a msg as "Document Posted" and another msg as "1 item selected in addition".
    But actually, there is no dcument is getting posted. Please let me know if anyone faced this scenario and how to overcome this. There is no batch session also getting created.
    Even for other company code, where batch session created, when I run that batch from SM35, it is finishing posting the document showing with all screens, but finally no document getting generated and the same msg apearing in that batch session log as well "1 item selected in addition".
    Regards
    Suresh

    Hi,
    The IDOC is successfully coming from XI, but there is problem in R\3 end.
    Idoc status is 51 with "Application document not posted"
    This indicates that the logic for posting the application document is not coded properly in inbound function module. Verify the logic once again.
    Also you need to confirm that the data related or in application configuration is right. If the data values are not correct the above error get generated.
    refer blow link for the program
    http://help.sap.com/saphelp_nw04/helpdata/en/78/21760251ce11d189570000e829fbbd/frameset.htm
    Thanks
    Swarup
    Edited by: Swarup Sawant on Jan 28, 2008 11:13 AM

Maybe you are looking for

  • Storage location quantity ABAP report question

    hi experts, i want to write a report which can show all the quantitiy base on storage location and i have four questions .... 1 . has somebody can tell me where i can find the confirmed qty ? is it in VBEP-BMENG ? 2 . how to know one material in one

  • Cost of Goods sold value problem

    Dear all, In a Make To Stock, material use "Moving average" case. For example 1-Sep: Moving avg = $30 15-Sep: Sales & PGI (A) 30-Sep: Moving avg = $70 30-Sep: Sales & PGI (B) First of all, I expect the Cost of goods sold for Sales & PGI (A) should be

  • How do I backup my MacBook Pro when the disk image is grayed out?

    I have a MacBook Pro (15 inc. four years old) running OSX 10.6.8 and last night I got the color pinwheel of death.  I could not force quit anything and had to manually power down. When I powered back up I got the folder with the question mark.  I ran

  • Quantity Updation on quantity contract

    hi friends, I want to know the settings required for updating the quantity after release order in quantity contract. This is apart from seeing in the details in status overview screen. Regards Suman

  • Can you use any email account with iChat?

    It appears that iChat allows you to add other other email accounts other than AOL or MobileMe but can you chat using these accounts and can you screen share etc with non MobileMe users? Message was edited by: Peter O'Toole