on 03-19-2013 7:16 AM
Hi,
Please try to patch your SPAM from your CI where EPS folder is available.
Don't try from the additional application server.
Thanks and Regards,
Vimal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Nainesh,
Goto link http://service.sap.com/spmanager from left menu choose SAP Support Packages in detail
download relevent version copy to catalog *EPS\in login to mandant 000 run tcode spam, from menu Support Package choose Import spam/saint update.
BR,
SAPFan
Category | ABAP Programming Error |
Runtime Errors | SYNTAX_ERROR |
ABAP Program | SAPLEPSF |
Application Component BC-CTS-TMS
Date and Time | 19.03.2013 14:25:18 |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Short text | | | |
| | Syntax error in program "SAPLEPSF ". | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened? | | | |
| | Error in the ABAP Application Program | | |
| | | | |
| | The current ABAP program "SAPMSPAM" had to be terminated because it has | | |
| | come across a statement that unfortunately cannot be executed. | | |
| | | | |
| | The following syntax error occurred in program "SAPLEPSF " in include "LEPSFU03 | | |
| | " in | | |
| | line 26: | | |
| | "Field "GT_OPEN_FILES" is unknown. It is not contained in one of the sp" | | |
| | "ecified tables nor is it defined by a "DATA" statement. "DATA" stateme" | | |
| | "nt." | | |
| | " " | | |
| | | | |
| | The include has been created and last changed by: | | |
| | Created by: "SAP " | | |
| | Last changed by: "SAP " | | |
| | Error in the ABAP Application Program | | |
| | | | |
| | The current ABAP program "SAPMSPAM" had to be terminated because it has | | |
| | come across a statement that unfortunately cannot be executed. | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What can you do? | | | |
| | Please eliminate the error by performing a syntax check | | |
| | (or an extended program check) on the program "SAPLEPSF ". | | |
| | You can also perform the syntax check from the ABAP Editor. | | |
| | | | |
| | If the problem persists, proceed as follows: | | |
| | Note down which actions and inputs caused the error. | | |
| | | | |
| | | | |
| | To process the problem further, contact you SAP system | | |
| | administrator. | | |
| | | | |
| | Using Transaction ST22 for ABAP Dump Analysis, you can look | | |
| | at and manage termination messages, and you can also | | |
| | keep them for a long time. | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Error analysis | | | |
| | The following syntax error was found in the program SAPLEPSF : | | |
| | "Field "GT_OPEN_FILES" is unknown. It is not contained in one of the sp" | | |
| | "ecified tables nor is it defined by a "DATA" statement. "DATA" stateme" | | |
| | "nt." | | |
| | " " | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|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 want to send an error | | |
| | notification to SAP, include the following information: | | |
| | | | |
| | 1. The description of the current problem (short dump) | | |
| | | | |
| | To save the description, choose "System->List->Save->Local File | | |
| | (Unconverted)". | | |
| | | | |
| | 2. Corresponding system log | | |
| | | | |
| | Display the system log by calling transaction SM21. | | |
| | Restrict the time interval to 10 minutes before and five minutes | | |
| | after the short dump. Then choose "System->List->Save->Local File | | |
| | (Unconverted)". | | |
| | | | |
| | 3. If the problem occurs in a problem of your own or a modified SAP | | |
| | program: The source code of the program | | |
| | In the editor, choose "Utilities->More | | |
| | Utilities->Upload/Download->Download". | | |
| | | | |
| | 4. Details about the conditions under which the error occurred or which | | |
| | actions and input led to the error. | | |
| | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|System environment | | | |
| | SAP Release..... 702 | | |
| | SAP Basis Level. 0007 | | |
| | | | |
| | Application server... "ailsaptest" | | |
| | Network address...... "172.17.11.40" | | |
| | Operating system..... "Windows NT" | | |
| | Release.............. "5.2" | | |
| | Hardware type........ "4x AMD64 Level" | | |
| | Character length.... 16 Bits | | |
| | Pointer length....... 64 Bits | | |
| | Work process number.. 1 | | |
| | Shortdump setting.... "full" | | |
| | | | |
| | Database server... "AILSAPTEST" | | |
| | Database type..... "ORACLE" | | |
| | Database name..... "ASL" | | |
| | Database user ID.. "SAPSR3" | | |
| | | | |
| | Terminal.......... "ailsaptest" | | |
| | | | |
| | Char.set.... "C" | | |
| | | | |
| | SAP kernel....... 720 | | |
| | created (date)... "Jan 16 2013 16:56:16" | | |
| | create on........ "NT 5.2 3790 S x86 MS VC++ 14.00" | | |
| | Database version. "OCI_10201_SHARE, 10.2.0.2.0 " | | |
| | | | |
| | Patch level. 401 | | |
| | Patch text.. " " | | |
| | | | |
| | Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" | | |
| | SAP database version. 720 | | |
| | Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows | | |
| | NT 6.0, Windows NT 6.1, Windows NT 6.2" | | |
| | | | |
| | Memory consumption | | |
| | Roll.... 0 | | |
| | EM...... 8379584 | | |
| | Heap.... 0 | | |
| | Page.... 57344 | | |
| | MM Used. 2212112 | | |
| | MM Free. 1975008 | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|User and Transaction | | | |
| | Client.............. 000 | | |
| | User................ "BASIS" | | |
| | Language key........ "E" | | |
| | Transaction......... "SPAM " | | |
| | Transaction ID...... "A27290E21E12F1B7861478E7D1D31CCC" | | |
| | | | |
| | EPP Whole Context ID.... "78E7D1D31CCC1ED2A48E4D0433724614" | | |
| | EPP Connection ID....... 00000000000000000000000000000000 | | |
| | EPP Caller Counter...... 0 | | |
| | | | |
| | Program............. "SAPMSPAM" | | |
| | Screen.............. "SAPMSPAM 0100" | | |
| | Screen Line......... 30 | | |
| | Debugger Active..... "none" | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Information on where terminated | | | |
| | Termination occurred in the ABAP program "SAPMSPAM" - in "PROMPT_UPLOAD". | | |
| | The main program was "SAPMSPAM ". | | |
| | | | |
| | In the source code you have the termination point in line 31 | | |
| | of the (Include) program "MSPAMF01". | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Source Code Extract | | |
----------------------------------------------------------------------------------------------------
|Line |SourceCde | | |
----------------------------------------------------------------------------------------------------
| | 1|*----------------------------------------------------------------------- | | | |
| | 2|* INCLUDE MSPAMF01. | | | |
| | 3|*----------------------------------------------------------------------- | | | |
| | 4|* | Contains all ABAP forms for module pool SAPMSPAM | | |
| | 5|* | (transaction SPAM). | | |
| | 6|*----------------------------------------------------------------------- | | | |
| | 7| | | | |
| | 8|*----------------------------------------------------------------------- | | | |
| | 9|* | Form PROMPT_UPLOAD | | |
| 10|*----------------------------------------------------------------------- | | | ||
| 11|* | Asks user to confirm the upload before proceeding. | | | |
| 12|* | | | ||
| 13|* | The following text elements are used: | | | |
| 14|* | - TEXT-007: Do you wish to upload the patches from the EPS | | | |
| 15|* | inbox? | | | |
| 16|* | - TEXT-008: EPS inbox path is & | | | |
| 17|* | - TEXT-009: SPAM: Confirm upload | | | |
| 18|*----------------------------------------------------------------------- | | | ||
| 19|* <-- P_ANSWER_YES | 'X' = yes | | | |
| 20|*----------------------------------------------------------------------- | | | ||
| 21|FORM prompt_upload CHANGING value(p_answer_yes). | | | ||
| 22| | | | ||
| 23|* (1) Local data definitions. | | | ||
| 24| CONSTANTS: lc_subdir LIKE epsf-epssubdir VALUE 'in'. | | | ||
| 25| | | | ||
| 26| DATA: lv_text(70) TYPE c, | | | ||
| 27| | lv_dir_name LIKE epsf-epsdirnam. | | | |
| 28| | | | ||
| 29|* (2) Determine path of EPS inbox. If it fails issue message: | | | ||
| 30|* "Failed to build patch for file &" | | | ||
|>>>>>| CALL FUNCTION 'EPS_GET_DIRECTORY_PATH' | | | ||
| 32| | EXPORTING | | | |
| 33| | eps_subdir | = lc_subdir | | |
| 34| | IMPORTING | | | |
| 35| | dir_name | = lv_dir_name | | |
| 36| | EXCEPTIONS | | | |
| 37| | invalid_eps_subdir | = 1 | | |
| 38| | sapgparam_failed | = 2 | | |
| 39| | build_directory_failed = 3. | | | |
| 40| | | | ||
| 41| IF syst-subrc <> 0. | | | ||
| 42| | MESSAGE i093 | | | |
| 43| | WITH 'usr/sap/trans/EPS/in'. | | | |
| 44| | EXIT. | | | |
| 45| ENDIF. | | | ||
| 46| | | | ||
| 47|* (3) Issue the confirmation popup. | | | ||
| 48| lv_text = text-008. | | | ||
| 49| REPLACE '&' WITH lv_dir_name INTO lv_text. | | | ||
| 50| | | |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Contents of system fields | | |
Hi Nainesh,
Thanks
Kishore Cherukumalla
Dear
When i give STMS It show Dump
Error in the ABAP Application Program
The current ABAP program "SAPLTMSM" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLSTCE " in include "LSTCEU35
" in
line 68:
"Different number of parameters in FORM and PERFORM (routine: FCHK_UNI_"
"DELIVERY, number of formal parameters: 6, number of actual parameters:"
" 5)."
" "
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLTMSM" had to be terminated because it has
it some part of Dump
nainesh
9376998808
Dear All
My problem is solved, sap give sap note 0001657891 Missing authorization checks in EPS
ones again thank for support to all
Nainesh
9376998808
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.