Regarding Runtime Analyzer in ECC 6.0

Hi All,
Please tell me what is the use of "In parallel session " and "Scheduling" in Runtime Analyzer (SE30) ? Please tell me how to use these things and where i can see the results ?
Thanks ,
Sabu.

Follow Below link
http://www.sapdevelopment.co.uk/perform/perform_pcursor.htm
http://help.sap.com/saphelp_nw70/helpdata/en/22/0425c6488911d189490000e829fbbd/content.htm
Parallel Processing
Regards,
Midhun Abraham

Similar Messages

Regarding types statement in ECC 6.0...plz reply..urgent

Hi,
I am copying a program which is in 4.7 to ECC 6.0,i am facing error regarding structures with types...
The following code in 4.7
DATA:BEGIN OF W_BMM00.
 INCLUDE STRUCTURE BMM00.
DATA:END OF W_BMM00.
DATA:BEGIN OF W_BMMH1.
 INCLUDE STRUCTURE BMMH1.
DATA:END OF W_BMMH1.
DATA:BEGIN OF W_BMMH7.
 INCLUDE STRUCTURE BMMH7.
DATA:END OF W_BMMH7.
DATA : BEGIN OF TAB_TLINE OCCURS 0.
 INCLUDE STRUCTURE TLINE.
DATA : END OF TAB_TLINE.
i have written the same in ECC6.0 as below
TYPES:BEGIN OF tw_bmm00.
 INCLUDE STRUCTURE bmm00.
TYPES:END OF tw_bmm00 ,
 tt_bmm00 TYPE STANDARD TABLE OF tw_bmm00.
TYPES:BEGIN OF tw_bmmh1.
 INCLUDE STRUCTURE bmmh1.
TYPES:END OF tw_bmmh1 ,
 tt_bmmh1 TYPE STANDARD TABLE OF tw_bmmh1.
TYPES:BEGIN OF tw_bmmh7.
 INCLUDE STRUCTURE bmmh7.
TYPES:END OF tw_bmmh7 ,
 tt_bmmh7 TYPE STANDARD TABLE OF tw_bmmh7.
TYPES:BEGIN OF tw_TAB_TLINE.
 INCLUDE STRUCTURE TLINE.
TYPES:END OF tw_TAB_TLINE,
 tt_tab_tline TYPE STANDARD TABLE OF tw_tab_tline.
lw_bmm00 TYPE tw_bmm00,
 lt_bmm00 TYPE tt_bmm00,
 lw_bmmh1 TYPE tw_bmmh1,
 lt_bmmh1 TYPE tt_bmmh1,
 lw_bmmh7 TYPE tw_bmmh7,
 lt_bmmh7 TYPE tt_bmmh7,
 lw_tab_thead TYPE tw_tab_thead,
 lt_tab_thead TYPE tt_tab_thead,....
when i check SLIN errors i am getting the following errors...plz resolve..
The current ABAP command is obsolete
Within classes and interfaces, you can only use "TYPE" to refer to ABAP Dictionary
types (not "LIKE" or "STRUCTURE").


include strture not allowed.
rules.
ABAP Development under Unicode
Prior to Unicode the length of a character was exactly one byte, allowing implicit typecasts or memory-layout oriented programming. With Unicode this situation has changed: One character is no longer one byte, so that additional specifications have to be added to define the unit of measure for implicit or explicit references to (the length of) characters.
Character-like data in ABAP are always represented with the UTF-16 - standard (also used in Java or other development tools like Microsoft's Visual Basic); but this format is not related to the encoding of the underlying database.
A Unicode-enabled ABAP program (UP) is a program in which all Unicode checks are effective. Such a program returns the same results in a non-Unicode system (NUS) as in a Unicode system (US). In order to perform the relevant syntax checks, you must activate the Unicode flag in the screens of the program and class attributes.
In a US, you can only execute programs for which the Unicode flag is set. In future, the Unicode flag must be set for all SAP programs to enable them to run on a US. If the Unicode flag is set for a program, the syntax is checked and the program executed according to the rules described in this document, regardless of whether the system is a US or a NUS. From now on, the Unicode flag must be set for all new programs and classes that are created.
If the Unicode flag is not set, a program can only be executed in an NUS. The syntactical and semantic changes described below do not apply to such programs. However, you can use all language extensions that have been introduced in the process of the conversion to Unicode.
As a result of the modifications and restrictions associated with the Unicode flag, programs are executed in both Unicode and non-Unicode systems with the same semantics to a large degree. In rare cases, however, differences may occur. Programs that are designed to run on both systems therefore need to be tested on both platforms.
Other Changes
1. Bit Statements
2. Adding Field Sequences
3. Loops with VARY and VARYING
4. Creating Subroutines
5. Saving Programs
6. Assigning Types for GET/SET PARAMETER
7. Unreachable Statements
8. Function Modules with Incorrect Parameter Names
1. Bit Statements
Previously, the system checked for the bit statements SET BIT i OF f [TO g] and GET BIT i OF f [INTO g]whether the field f is character-type; X fields, X strings, and flat structures are usually regarded as character-type. For Unicode programs this is no longer useful, because the types X and XSTRING no longer count as character-type and the bit by bit access to character-type fields or structures is no longer platform-independent. Therefore, with these operations in Unicode programs, the field f must be type X or XSTRING.
For the bit mask operations f O x, f Z x, and f M x you could previously use all number-type and hence all character-type types for the left operand f. In Unicode programs, the f operand must now be type X or XSTRING.
2. Adding Field Sequences
When adding field sequences, restrictions apply to the following statements in Unicode:
ADD n1 THEN n2 UNTIL nz [ ACCORDING TO sel ] GIVING m ...
ADD n1 THEN n2 UNTIL nz TO m [ RANGE str ].
1. The operands n1, n2, and nz must be type-compatible with one another.
2. The distance between nz and n1 must be an integral multiple of the distance between n2 and n1.
3. A syntax or runtime error occurs if the fields n1, n2, and nz are not in a structure. This structure must be recognizable statically or its valid area must be marked explicitly using the RANGE addition.
4. At runtime, the system ensures that the RANGE area is not left.
ADD n1 FROM i1 GIVING m [ RANGE str ].
1. Field n1 must be within the structure. The structure must be explicitly defined using the RANGE addition if it is not recognizable statically.
2. For this variant, the system also checks at runtime whether n1 and the addressed values are within the structure.
3. Loops
Loops with the VARY or VARYING addition are also problematic in Unicode, since a type-a access to memory contents cannot be ensured and memory can be overwritten inadvertently.
DO ... VARYING f FROM f1 NEXT f2.
For this statement, the fields f, f1, and f2 must be type-compatible with each other. To prevent memory contents being overwritten, a RANGE for valid accesses is introduced implicitly or explicitly for the following statements:
DO ... TIMES VARYING f FROM f1 NEXT f2 [ RANGE f3 ].
WHILE ... VARY f FROM f1 NEXT f2 [ RANGE f3 ].
A syntax or runtime error is caused if f1 or f2 are not included in f3. If the RANGE addition is missing, it is defined implicitly from FROM f1 NEXT f2 as follows:
1. If both f1 and f2 are statically recognizable components of the same structure, the valid RANGE area is defined from the smallest structure that comprises f1 and f2.
2. A syntax error is triggered if it is recognizable statically that f1 and f2 are not part of the same structure.
3. A valid area must be defined explicitly using the RANGE addition if the connection between f1 and f2 is not recognizable statically.
If you specify a deep structure as the RANGE addition, the system checks for every loop pass that there are no field references, object references, tables, or strings in the area read.
4. Creating Subroutines
When automatically generating subroutines using the statement GENERATE SUBROUTINE POOL itab NAME name, the generated program inherits the content of the Unicode flag of the generating program.
5. Saving Programs
When automatically generating programs using the statement INSERT REPORT prog FROM itab, default values are set for the TRDIR entry as before. Amongst other things, this statement has the new addition UNICODE ENABLING uc, with which the Unicode flag of the inserted report receives the value of uc. If this addition is missing, the following applies:
1. A Unicode program creates a Unicode program.
2. A non-Unicode program in turn creates a non-Unicode program.
3. A non-Unicode program becomes a Unicode program if it is overwritten by a Unicode program.
4. A Unicode program remains a Unicode program if it is overwritten by a non-Unicode program.
6. Assigning Types for GET/SET PARAMETER
For the statements GET PARAMETER ID pid FIELD f and GET PARAMETER ID pid FIELD f, f must be character-type. You can use the EXPORT and IMPORT statements for storing non-character-type fields and structures.
7. Unreachable Statements
In Unicode programs, unreachable statements cause a syntax error. In non-Unicode programs, there was previously only a syntax warning.
8. Function Modules with Incorrect Parameter Names
In Unicode programs, calling a function module, whose parameter names are specified statically as a literal or constant, causes an exception that can be handled if an incorrect parameter name was specified. This only applies to function modules that are not called via Remote Function Call. In non-Unicode programs, an incorrect name was previously ignored.
http://service.sap.com/instguides
--> SAP Business Suite Applications
--> SAP ERP
--> mySAP ERP 2005
--> Upgrade
--> Upgrade Documentation - mySAP ERP 2005 SR2
There choose your database and operating system.
If you're looking for functional details check
http://service.sap.com/releasenotes

Regarding runtime error DBIF_RSQL_SQL_ERROR and exception CX_SY_OPEN_SQL_DB

Hi All,
I am loading a COPA cube from a DSO.
There are about 15million records to be loaded. every time i try loading the data, 1 or 2 Data packages gets stuck and finally it leads to a runtime error DBIF_RSQL_SQL_ERROR with exception CX_SY_OPEN_SQL_DB.
When i checked in SM21 transaction code, i got the following message
10:41:52 BTC 018 500 AMRUKV                     BY O Deadlock occurred
10:41:53 BTC 018 500 AMRUKV                     BY 4 Database error 60 at INS access to table /BIC/FCSDV
10:41:53 BTC 018 500 AMRUKV                     BY 0 > ORA-00060: deadlock detected while waiting for resource
10:41:54 BTC 018 500 AMRUKV                     AB 0 Run-time error "DBIF_RSQL_SQL_ERROR" occurred
10:41:58 BTC 018 500 AMRUKV                     AB 1 > Short dump "080818 104154 s0173bel PB100 " generated
10:41:58 BTC 018 500 AMRUKV                     D0 1 Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20080818104154s0173bel_PB1_00 AMRUKV 500 )
In transaction code ST22 i got the following message:
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          18.08.2008 10:41:54
Short text
     SQL error in the database when accessing a table.
What happened?
     The database system detected a deadlock and avoided it by rolling back
     your transaction.
What can you do?
     If possible (and necessary), repeat the last database transaction in the
      hope that locking the object will not result in another deadlock.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
      in procedure "WRITE_ICFACT" "(FORM)", nor was it propagated by a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     The database system recognized that your last operation on the database
     would have led to a deadlock.
     Therefore, your transaction was rolled back
     to avoid this.
     ORACLE always terminates any transaction that would result in deadlock.
     The other transactions involved in this potential deadlock
     are not affected by the termination.
How to correct the error
    Database error text........: "ORA-00060: deadlock detected while waiting for
     resource"
    Internal call code.........: "[RSQL/INSR//BIC/FCSDVD_C02 ]"
    Please check the entries in the system log (Transaction SM21).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "GPD3UMZD6V4YAKZAIWAOCYLV07Y" or "GPD3UMZD6V4YAKZAIWAOCYLV07Y"
    "WRITE_ICFACT"
    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.
    The exception must either be prevented, caught within proedure
    "WRITE_ICFACT" "(FORM)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
Can anybody suggest on what can be done?
Thanks in Advance,
Regards
A.T

Hi ,
This is a table space issue....
u will be getting a Dump...as DBIF_RSQL_SQL_ERROR check in ST22. in this DUMP if u scroll down u will find the table for which this is failing. Actually this is like some of the table related to the DSO is not having sufficient space to cary out the transaction. hence it is failing.
U can also see in DB02--> Deadlock....u will see that there is a deadlock for this table. So find the table from ST22 and ask ur basis team to increase the space for this table....
This can be solved only by increasing the space of the table...no other solution....ask help from ur basis team.
Thanks
Sandeep

Regarding Bigger SGA in ECC 6.0

Hi All,
When installing SAP ECC 6.0/Oracle 10g on AIX 5.3, if i am modifing instance memory then installation giving me following error in catproc.sql running phase.
============ ERROR==== ========= ========= ========= =======
ERROR 2006-12-20 09:44:38
FCO-00011 The step runCatprocSql with step key
|NW_Onehost| ind|ind|ind| ind|0|0|NW_ Onehost_System| ind|ind|ind| ind|1|0|NW_ CreateDBandLoad| ind|ind|ind| ind|9|0|NW_ CreateDB| ind|ind|ind| ind|0|0|NW_ OraDBCheck| ind|ind|ind| ind|0|0|NW_ OraDBMain| ind|ind|ind| ind|0|0|NW_ OraDBStd| ind|ind|ind| ind|3|0|NW_ OraDbBuild| ind|ind|ind| ind|5|0|runCatpr ocSql
was executed with status ERROR .
ERROR 2006-12-20 09:44:38
CJS-00084 SQL statement or script
failed. DIAGNOSI S: Error message: ORA-29809: cannot
drop an operator with dependent objects
============ ========= ========= ========= ========= =======
if i am not modifing the instance RAM(if using default value) then installation is working fine,
My Server RAM is 9 GB
When i am installing SAP/Oracle occpy 50% of total RAM, if i am modifing 6 GB RAM then it is not working and giving me error at catproc.sql phase.
My intention is that i want to create little bit bigger SGA greather then 1.7 GB.
I have following doubts, kindly provide guidance.
(1) Why should i cannot create more then 1.7 GB RAM?
(2) If i want to Create more then 1.7 GB RAM's SGA
then what should i have to do during installation?
(3) Which SAP Parameters i have to change to utilise maximum Memroy.
Waiting for your kind response.
Thanks and Regards
K R Singh

Hi Karmesh,
As a role of thumb, Oracle does not support any extended shared memory segments on IBM AIX. Please take a look OSS notes #105429, 123366.
Additionally, I would like to suggest that you use dynamic SGA that has been mentioned in OSS note #105429.
What kind of memory, you are talking about, in your last question? Oracle memory tuning or SAP memory tuning?
Regards,
Orkun Gedik
Senior SAP R/3 Basis and Development Consultant
ASTRON

Urgent: Regarding Runtime Error in FM

hi,
i had made a Function Module which will reterive the production order,but when i use it in the program it gives runtime error.Plzz help me how to solve this problem.
1st i am pasting the code which i had written:-
FUNCTION ZFIND_PRDORD.
""Local Interface:
*" IMPORTING
*"     VALUE(QP_CHARG) LIKE CHVW-CHARG OPTIONAL
*"     VALUE(P_AUFNR) LIKE CHVW-AUFNR OPTIONAL
*" EXPORTING
*"     VALUE(P_RETVAL) LIKE CHVW-AUFNR
DATA : BEGIN OF T_CHVW OCCURS 0,
              XZUGA LIKE CHVW-XZUGA,
              WERKS LIKE CHVW-WERKS,
              MATNR LIKE CHVW-MATNR,
              CHARG LIKE CHVW-CHARG,
              AUFNR LIKE CHVW-AUFNR,
              EBELN LIKE CHVW-EBELN,
              MBLNR LIKE CHVW-MBLNR,
              ZEILE LIKE CHVW-ZEILE,
              BUDAT LIKE CHVW-BUDAT,
              SHKZG LIKE CHVW-SHKZG,
              BWART LIKE CHVW-BWART,
              MENGE LIKE CHVW-MENGE,
              MEINS LIKE CHVW-MEINS,
              KZBEW LIKE CHVW-KZBEW,
          END OF T_CHVW.
SELECT XZUGA WERKS MATNR CHARG AUFNR EBELN
MBLNR ZEILE BUDAT SHKZG BWART MENGE MEINS KZBEW
FROM CHVW INTO TABLE T_CHVW
WHERE CHARG EQ QP_CHARG
and XZUGA = ' '
AND BWART = '101'
and aufnr eq p_aufnr
AND KZBEW = 'F' .
P_RETVAL = T_CHVW-AUFNR.
ENDFUNCTION.
Now i am displaying the program for testing this FM which gives the runtime error:-
TABLES : CHVW.
SELECT-OPTIONS : P_CHARG FOR CHVW-CHARG,
                 P_AUFNR FOR CHVW-AUFNR .
CALL FUNCTION 'ZFIND_PRDORD'
EXPORTING
   QP_CHARG       = P_CHARG
   P_AUFNR        = P_AUFNR
IMPORTING
   P_RETVAL      = P_AUFNR.
WRITE : / 'SDSQDA' .
Plzz help me out as how to solve this problem as i have to use it in
the main program.
regards,
ric.s

HI SANTOSH,
I had changed according what u said and it is not giving runtime error .
but it is not giving the value as if i send the value of batch and the prd orderr. plz tell me how do it get the output.
i had written the code of program like this:-
TABLES : CHVW.
Parameters : P_CHARG like CHVW-CHARG,
             P_AUFNR like CHVW-AUFNR.
DATA: PRD LIKE CHVW-AUFNR.
CALL FUNCTION 'ZFIND_PRDORD'
EXPORTING
QP_CHARG = P_CHARG
P_AUFNR = P_AUFNR
IMPORTING
P_RETVAL = PRD.
WRITE : / PRD .
PLZ HELPMEOUT HOW TO DO THIS.

Regarding obselete statements in ECC 6.0 ...plz help uregent

Hi guys...
I am importing a program from 4.7 to ECC 6.0.
When i am checking SLIN errors i am getting followin error..
The current ABAP command is obsolete
Field groups cannot be created in the OO context.
Internal Message Code: FIELD-GROUPS 000
The 4.7 program uses the follwing code where i am getting the error
FIELD-GROUPS: HEADER, ITEMS.So plz find a solution for this...
thank u.
madhavi

Hi Madhavi,
There is no other solution than rewriting the program, e.q. by creating internal tables for the fields now defined with FIELD-GROUPS in HEADER and ITEMS and looping over these tables.
Regards,
John.

Regarding form routines IN ECC 6.0

Hi Abapers,
                   I am currently working in ECC 6.0. I have come through an error as
se old_entry_xxx as a form routine if you use an own print program
I have a form routine in my include program as follows...
FORM ENTRY_NEU USING ENT_RETCO ENT_SCREEN.
XSCREEN = ENT_SCREEN.
IF NAST-AENDE EQ SPACE.
    XDRUVO = '1'.
ELSE.
    XDRUVO = '2'.
ENDIF.
CLEAR: XFZ, XOFFEN, XLMAHN, XLPET.
CLEAR ENT_RETCO.
PERFORM LESEN USING NAST.
MOVE RETCO TO ENT_RETCO.
ENDFORM.
Can anyone give any hints regarding how to come out of this error, i guess its a unicode error but not sure.
Frnds looking for ur help.
thanks
& regards,
kamal

Hi ,
       I have'nt come up with any solutions yet. But wht i consider is the perform doesnt exist for that form routine.I m wondering , Is that a form routine has any "perform". Frnds if anyone is having any clues plzz provide.
Its basically a Upgrade task.
thanking u all.
regards,
kamal

Regarding 4.6c to ECC 6.0

Hi,
We are starting the upgradition from 4.6C to ECC6.0,as a ABAP er what changes i need to do could you explain me with transaction codes
what is unicode and what is the neccessity of unicode for upgradtion
Regards
Raghava

Hi,
When an upgrade has been carried on a system, large number of data dictionary & repository objects get affected in the newer version.
1. You have to start with identifying the objects which have undergone a change. So run the transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system. Following links contains necesary documentation on SPDD.
http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/6d66617d9011d396b60000e82de14a/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/6d66647d9011d396b60000e82de14a/content.htm
2. After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified. This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
Check the below link. It elaborates on adjusting repository objects.
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/61ec66e33611d1954b0000e82de14a/content.htm
3. Also check whether the custom programs have been copied properly. Remove any obsolete statements. Also replace the obsolete function modules. Function modules like WS_UPLOAD & DOWNLOAD have become obsolete in ECC 6.0.
4. In case of BDC, compare the screen with the older version. There is a possibility that few fields would have missed out. You may have to do some tweking in the program too. Same is the case with sap scripts.
5. Also make sure that the objects are unicode compatible.
Check out the below links for a detailed explanation in Unicode.
http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/content.htm
http://www.sapdb.org/7.4/htmhelp/db/74d038d35e11d5994400508b6b8b11/content.htm
Hope this helps you.
(If your question is answered, please mark the thread as answered)
Regards
Sayee

Regarding kernel upgrade in ECC 6.0

Hi,
We want to perform a kernel upgrade for our ECC 6.0 system landscape.
Currently we are on kernel 133 and the present kernel level is 179 in service market place.
In our landscape,we have 7 dialog instances along with the central instance.If I upgrade the exe folder(Solaris) in Central instance, would the kernel be upgraded in all the application servers associated with it?
Or do we need replace all the executables(After unzipping the uncar files of SAPEXE & SAPEXEDB)in dialog instances as well, apart from central instances.If so,in what sequence do we need to replace.(Central Instance,Dialog instance1,DI2,DI3....)
Anyone please clarify and help.
-Sudheer.

Hi Sudheer,
If your landscape(CI & DI) running in heterogenus operating system then you have to perform kernel upgrade manually in CI and DI because SAP provides SAR files according to operating system and Database with unicode and Non-unicode systems.
Please check in the link https://websmp205.sap-ag.de/patches
Regards
Krishna Vanga

Best performance in runtime analyzer

Hi All,
While doing the runtime analysis (using SE30) of a ABAP program , what is the best performance analysis report , means more percentage of time consumed by , ABAP program , Database or System ?
Thanks & Regards ,
Sabu.

Best Case :
No one shold be in red color in analysis is the best runtime.
All should be in Green.
or
OK Case :
Database level - Red is not acceptable
ABAP Level - Red can be accepted and can be a good runtime.
System Level - Red is not acceptable.
Worst Case:
All are in Red Color

Regarding enterprise services in ECC

Hi ,
In reference to whether using standard idocs or standard ES available in ECC box ,in case we are not using CE ( so no composite applications) and only using SAP PI to integrate could someone point out any best practices that are available. The majority of services for example for Order to Cash scenarios like Sales Order create are synchronous in mode. From performance and reprocessing perspective using an asynchronous mode would be preferable - so do we use enterprise services for straight forward scenarios like order creation in ecc from sender legacy application or we use it only when we have business process orchestration in mind for later.
Regards

Hi Ravi,
It may be that you just need a delta cache refresh but I would start by checking the SLD configuration.
First strt with SAP Note: 1169869
- I think that you might need to try changing the vendor (sap.com) that's assigned to the Software Component Version.
- If you were seeing the SWCV before it should be installed on your system anyway but you can double check using the steps I've specified here: [Can't find ESA ECC-SE 603 SWCV;
- You might also want to check if the SWC is correctly assigned to the relevant business system/s in the SLD.
Regards, Trevor

Regarding runtime error

Hi Gurus,
I am facing error while creating sales order.I am working on excise( TAXINN).while creating standard sales order there is no runtime error.But when i change customer pricing procedure relevant to tax it shows runtime error.there is no such error in TAXINJ.
ii have given following link for details.
http://www.4shared.com/file/63968817/42eae8b2/Runtime_error.html
please guide me.
Regards
Hemant

i was wrong in confiruration.

Regarding Runtime error in ALV List Display.

am using following to display data in ALV List.
but after executing of program am getting runtime error called 'Field Symbol has Not been assigned' .
please tell me how to correct the error.
Very urgent
Suitable answers rewarded with Maximum Ponits...
REPORT zmatrix.
TYPE-POOLS: slis.
TABLES: agr_define, sza5_d0700.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-006.
SELECT-OPTIONS: s_role FOR agr_define-agr_name OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b1.
 D A T A *
TYPES: BEGIN OF ty_agr_1251_inf,
 agr_name TYPE agr_1251-agr_name,
 object TYPE agr_1251-object,
 field TYPE agr_1251-field,
 low(20) TYPE c,
 high TYPE agr_1251-high,
 infty TYPE t582s-infty,
 itext TYPE t582s-itext,
 END OF ty_agr_1251_inf.
TYPES: BEGIN OF ty_agr_1251_tcode,
 agr_name TYPE agr_1251-agr_name,
 object TYPE agr_1251-object,
 field TYPE agr_1251-field,
 low(20) TYPE c,
 high TYPE agr_1251-high,
 tcode TYPE tstct-tcode,
 ttext TYPE tstct-ttext,
 END OF ty_agr_1251_tcode.
TYPES: BEGIN OF ty_t582s,
 infty TYPE agval,
 itext TYPE t582s-itext,
 END OF ty_t582s.
TYPES: BEGIN OF ty_code,
 tcode TYPE tstct-tcode,
 ttext TYPE ttext_stct,
END OF ty_code.
TYPES: BEGIN OF ty_inf,
 infty TYPE t582s-infty,
 itext TYPE t582s-itext,
 END OF ty_inf.
TYPES: BEGIN OF ty_role,
 agr_name TYPE agr_1251-agr_name,
 END OF ty_role.
TYPES: BEGIN OF tys_role_dtls,
 agr_name TYPE agr_name,
 value TYPE c,
 property TYPE c,
 END OF tys_role_dtls.
TYPES: BEGIN OF tys_infotype_final,
 text(60),
 text1(60),
 value(4),
 END OF tys_infotype_final.
 I N T E R N A L T A B L E S *
DATA: wa_infotyp_final TYPE tys_infotype_final.
DATA: t_infotyp_final TYPE TABLE OF tys_infotype_final.
DATA: BEGIN OF wa_infotyp_dtls,
 infty TYPE infty,
 itext TYPE intxt,
 role_dtls TYPE TABLE OF tys_role_dtls,
 END OF wa_infotyp_dtls.
DATA: BEGIN OF wa_tcode_dtls,
 tcode TYPE tcode,
 ttext TYPE ttext_stct,
 role_dtls TYPE TABLE OF tys_role_dtls,
 END OF wa_tcode_dtls.
DATA: t_infotyp_dtls LIKE TABLE OF wa_infotyp_dtls,
 t_tcode_dtls LIKE TABLE OF wa_tcode_dtls,
 t_role_dtls TYPE TABLE OF tys_role_dtls,
 wa_role_dtls TYPE tys_role_dtls.
DATA: wa_inf TYPE ty_inf,
 t_inf TYPE STANDARD TABLE OF ty_inf.
DATA: wa_role TYPE ty_role,
 t_role TYPE STANDARD TABLE OF ty_role.
DATA: wa_tcode TYPE ty_code,
 t_tcode TYPE TABLE OF ty_code.
DATA: wa_agr_1251_inf TYPE ty_agr_1251_inf.
DATA: wa_agr_1251_tcode TYPE ty_agr_1251_tcode.
DATA: t_agr_1251_inf TYPE STANDARD TABLE OF ty_agr_1251_inf.
DATA: t_agr_1251_tc TYPE STANDARD TABLE OF ty_agr_1251_tcode.
DATA: wa_582s TYPE ty_t582s.
DATA: t_582s TYPE STANDARD TABLE OF ty_t582s.
DATA: t_range_tcode TYPE RANGE OF tcode.
DATA: t_range_inf TYPE RANGE OF infotyp.
DATA: wa_range_inf LIKE LINE OF t_range_inf.
DATA: wa_range_tcode LIKE LINE OF t_range_tcode.
DATA: wa_field TYPE slis_fieldcat_alv.
DATA: t_field TYPE slis_t_fieldcat_alv.
 VARIABLES FOR OLE *
DATA: text(20),
 count(20).
DATA: text1(30).
DATA: agr_name TYPE agr_1251-agr_name.
DATA: flag TYPE i VALUE '0'.
DATA: string1 TYPE string.
DATA: str TYPE string VALUE 'SAP%'.
DATA: count1 TYPE i VALUE '0'.
*& Event START-OF-SELECTION
START-OF-SELECTION.
PERFORM f100_get_inf_data.
PERFORM f200_process_inf_data.
count1 = 1.
PERFORM f300_prepare_field_catalog.
PERFORM f110_main_data.
PERFORM f400_display_data.
PERFORM f100_get_trans_data.
*& Form f110_main_data
 text
FORM f110_main_data.
wa_infotyp_final-text = 'Access to Infotypes'.
APPEND wa_infotyp_final TO t_infotyp_final.
wa_infotyp_final-text = 'Infotype'.
wa_infotyp_final-text1 = 'Description'.
APPEND wa_infotyp_final TO t_infotyp_final.
wa_infotyp_final-text = '*'.
wa_infotyp_final-text1 = 'Acess to all Infotypes'.
LOOP AT t_role INTO wa_role WHERE agr_name <> ' '.
 READ TABLE t_agr_1251_inf INTO wa_agr_1251_inf
 WITH KEY agr_name = wa_role-agr_name field = 'INFTY' low = '*'.
 IF syst-subrc = 0.
 wa_infotyp_final-value = 'X'.
 ENDIF.
ENDLOOP.
APPEND wa_infotyp_final TO t_infotyp_final.
LOOP AT t_inf INTO wa_inf WHERE infty <> ' '.
 wa_infotyp_final-text = wa_inf-infty.
 wa_infotyp_final-text1 = wa_inf-itext.
 LOOP AT t_role INTO wa_role WHERE agr_name <> ' '.
 Role Name
 CLEAR wa_role_dtls.
 flag = 1.
 wa_role_dtls-agr_name = wa_role-agr_name.
 For Value D & F
 READ TABLE t_agr_1251_inf INTO wa_agr_1251_inf
 WITH KEY agr_name = wa_role-agr_name field = 'AUTHC'..
 IF syst-subrc EQ 0.
 IF wa_agr_1251_inf-low = 'R'.
 wa_infotyp_final-value = 'D'.
 ELSE.
 wa_infotyp_final-value = 'F'.
 ENDIF.
 ENDIF.
 APPEND wa_role_dtls TO t_role_dtls.
 APPEND wa_infotyp_final TO t_infotyp_final.
 ENDLOOP.
ENDLOOP.
ENDFORM. "f110_main_data
*& Form f100_get_inf_data
 text
FORM f100_get_inf_data.
 Logic for Infotypes *
SELECT aagr_name aobject
 afield alow a~high
 INTO TABLE t_agr_1251_inf
 FROM agr_1251 AS a INNER JOIN agr_define AS b
 ON aagr_name EQ bagr_name
WHERE ( ( aobject EQ 'P_ORGIN' OR aobject EQ 'P_PERNR' )
AND ( aagr_name IN s_role ) AND ( bagr_name NOT LIKE str ) ).
ENDFORM. "f100_get_inf_data
*& Form f200_get_inf_process_data
 text
FORM f200_process_inf_data.
LOOP AT t_agr_1251_inf INTO wa_agr_1251_inf.
 IF wa_agr_1251_inf-high IS INITIAL.
 CLEAR wa_range_inf.
 wa_range_inf-sign = 'I'.
 wa_range_inf-option = 'EQ'.
 wa_range_inf-low = wa_agr_1251_inf-low.
 APPEND wa_range_inf TO t_range_inf.
 ELSE.
 CLEAR wa_range_inf.
 wa_range_inf-sign = 'I'.
 wa_range_inf-option = 'BT'.
 wa_range_inf-low = wa_agr_1251_inf-low.
 wa_range_inf-high = wa_agr_1251_inf-high.
 APPEND wa_range_inf TO t_range_inf.
 ENDIF.
ENDLOOP.
SORT t_range_inf.
DELETE ADJACENT DUPLICATES FROM t_range_inf.
IF t_range_inf IS NOT INITIAL.
 SELECT infty itext FROM t582s
 INTO TABLE t_582s
 WHERE sprsl = 'EN' AND infty IN t_range_inf.
 IF syst-subrc EQ 0.
 ENDIF.
ENDIF.
LOOP AT t_agr_1251_inf INTO wa_agr_1251_inf.
 IF wa_agr_1251_inf-high IS INITIAL.
 READ TABLE t_582s INTO wa_582s
 WITH KEY infty = wa_agr_1251_inf-low.
 IF syst-subrc EQ 0.
 wa_agr_1251_inf-infty = wa_582s-infty.
 wa_agr_1251_inf-itext = wa_582s-itext.
 MODIFY t_agr_1251_inf FROM wa_agr_1251_inf
 TRANSPORTING infty itext.
 IF syst-subrc EQ 0.
 ENDIF.
 ENDIF.
 ELSE.
 CLEAR count.
 LOOP AT t_582s INTO wa_582s
 WHERE infty GE wa_agr_1251_inf-low
 AND infty LE wa_agr_1251_inf-high.
 IF count LE 1.
 wa_agr_1251_inf-high = space.
 wa_agr_1251_inf-infty = wa_582s-infty.
 wa_agr_1251_inf-itext = wa_582s-itext.
 MODIFY t_agr_1251_inf FROM wa_agr_1251_inf
 TRANSPORTING infty itext.
 IF syst-subrc EQ 0.
 CLEAR wa_582s.
 ENDIF.
 ELSE.
 wa_agr_1251_inf-high = space.
 wa_agr_1251_inf-infty = wa_582s-infty.
 wa_agr_1251_inf-itext = wa_582s-itext.
 APPEND wa_agr_1251_inf TO t_agr_1251_inf.
 ENDIF.
 CLEAR wa_agr_1251_inf.
 count = count + 1.
 ENDLOOP.
 ENDIF.
ENDLOOP.
wa_role-agr_name = ' '.
APPEND wa_role TO t_role.
wa_role-agr_name = ' '.
APPEND wa_role TO t_role.
LOOP AT t_agr_1251_inf INTO wa_agr_1251_inf.
 IF wa_agr_1251_inf IS NOT INITIAL.
 wa_role-agr_name = wa_agr_1251_inf-agr_name.
 wa_inf-infty = wa_agr_1251_inf-infty.
 wa_inf-itext = wa_agr_1251_inf-itext.
 APPEND wa_role TO t_role.
 APPEND wa_inf TO t_inf.
 ENDIF.
ENDLOOP.
SORT t_role BY agr_name.
DELETE ADJACENT DUPLICATES FROM t_role.
SORT t_inf BY infty.
DELETE ADJACENT DUPLICATES FROM t_inf.
ENDFORM. "f200_get_process_inf_data
*& Form f100_get_trans_data
 text
FORM f100_get_trans_data.
 Logic for Transaction Codes *
SELECT aagr_name aobject
 afield alow a~high
 INTO CORRESPONDING FIELDS OF TABLE t_agr_1251_tc
 FROM agr_1251 AS a
 INNER JOIN agr_define AS b ON aagr_name EQ bagr_name
 WHERE a~agr_name IN s_role
 AND a~object EQ 'S_TCODE'.
ENDFORM. "f100_get_trans_data
*& Form f200_process_trans_data
 text
FORM f200_process_trans_data.
LOOP AT t_agr_1251_tc INTO wa_agr_1251_tcode.
 IF wa_agr_1251_tcode-high IS INITIAL.
 CLEAR wa_range_tcode.
 wa_range_tcode-sign = 'I'.
 wa_range_tcode-option = 'EQ'.
 wa_range_tcode-low = wa_agr_1251_tcode-low.
 APPEND wa_range_tcode TO t_range_tcode.
 ELSE.
 CLEAR wa_range_tcode.
 wa_range_tcode-sign = 'I'.
 wa_range_tcode-option = 'BT'.
 wa_range_tcode-low = wa_agr_1251_tcode-low.
 wa_range_tcode-high = wa_agr_1251_tcode-high.
 APPEND wa_range_tcode TO t_range_tcode.
 ENDIF.
ENDLOOP.
SORT t_range_tcode.
DELETE ADJACENT DUPLICATES FROM t_range_tcode.
IF t_range_tcode IS NOT INITIAL.
 SELECT tcode
 ttext
 FROM tstct
 INTO TABLE t_tcode
 WHERE sprsl EQ 'E'
 AND tcode IN t_range_tcode.
 IF sy-subrc EQ 0.
 ENDIF.
ENDIF.
SORT t_agr_1251_tc BY agr_name.
LOOP AT t_agr_1251_tc INTO wa_agr_1251_tcode.
 IF wa_agr_1251_tcode-high IS INITIAL.
 READ TABLE t_tcode INTO wa_tcode
 WITH KEY tcode = wa_agr_1251_tcode-low.
 IF syst-subrc EQ 0.
 wa_agr_1251_tcode-tcode = wa_tcode-tcode.
 wa_agr_1251_tcode-ttext = wa_tcode-ttext.
 MODIFY t_agr_1251_tc FROM wa_agr_1251_tcode
 TRANSPORTING tcode ttext.
 IF syst-subrc EQ 0.
 ENDIF.
 ENDIF.
 ELSE.
 CLEAR count.
 LOOP AT t_tcode INTO wa_tcode
 WHERE tcode GE wa_agr_1251_tcode-low
 AND tcode LE wa_agr_1251_tcode-high.
 IF count LE 1.
 agr_name = wa_agr_1251_tcode-agr_name.
 wa_agr_1251_tcode-high = space.
 wa_agr_1251_tcode-tcode = wa_tcode-tcode.
 wa_agr_1251_tcode-ttext = wa_tcode-ttext.
 MODIFY t_agr_1251_tc FROM wa_agr_1251_tcode
 TRANSPORTING tcode ttext high.
 IF syst-subrc EQ 0.
 CLEAR wa_tcode.
 ENDIF.
 count = 1.
 ELSE.
 wa_agr_1251_tcode-high = space.
 wa_agr_1251_tcode-agr_name = agr_name.
 wa_agr_1251_tcode-low = wa_tcode-tcode.
 wa_agr_1251_tcode-tcode = wa_tcode-tcode.
 wa_agr_1251_tcode-ttext = wa_tcode-ttext.
 APPEND wa_agr_1251_tcode TO t_agr_1251_tc.
 ENDIF.
 CLEAR wa_agr_1251_tcode.
 count = count + 1.
 ENDLOOP.
 ENDIF.
ENDLOOP.
LOOP AT t_agr_1251_tc INTO wa_agr_1251_tcode.
 wa_role-agr_name = wa_agr_1251_tcode-agr_name.
 APPEND wa_role TO t_role.
ENDLOOP.
SORT t_role BY agr_name.
DELETE ADJACENT DUPLICATES FROM t_role.
SORT t_tcode BY tcode.
DELETE ADJACENT DUPLICATES FROM t_tcode.
ENDFORM. "f200_process_trans_data
*& Form f100_prepare_field_catalog
 text
FORM f300_prepare_field_catalog.
LOOP AT t_role INTO wa_role.
 wa_field-col_pos = count1.
 wa_field-fieldname = wa_role-agr_name.
 APPEND wa_field TO t_field.
 count1 = count1 + 1.
ENDLOOP.
ENDFORM. "f100_prepare_field_catalog
*& Form f100_display_data
 text
FORM f400_display_data.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
 EXPORTING
 I_INTERFACE_CHECK = ' '
 I_BYPASSING_BUFFER =
 I_BUFFER_ACTIVE = ' '
 i_callback_program = sy-cprog
 I_CALLBACK_PF_STATUS_SET = ' '
 I_CALLBACK_USER_COMMAND = ' '
 I_STRUCTURE_NAME =
 IS_LAYOUT =
 it_fieldcat = t_field[]
 IT_EXCLUDING =
 IT_SPECIAL_GROUPS =
 IT_SORT =
 IT_FILTER =
 IS_SEL_HIDE =
 I_DEFAULT = 'X'
 I_SAVE = ' '
 IS_VARIANT =
 IT_EVENTS =
 IT_EVENT_EXIT =
 IS_PRINT =
 IS_REPREP_ID =
 I_SCREEN_START_COLUMN = 0
 I_SCREEN_START_LINE = 0
 I_SCREEN_END_COLUMN = 0
 I_SCREEN_END_LINE = 0
 IR_SALV_LIST_ADAPTER =
 IT_EXCEPT_QINFO =
 I_SUPPRESS_EMPTY_DATA = ABAP_FALSE
 IMPORTING
 E_EXIT_CAUSED_BY_CALLER =
 ES_EXIT_CAUSED_BY_USER =
 TABLES
 t_outtab = t_infotyp_final[]
 EXCEPTIONS
 program_error = 1
 OTHERS = 2
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM. "f100_display_data

this are the wasy u can build a field catalog...
1.----
FORM fill_fieldcat .
DATA: fld(30),
idx(2) TYPE n.
DEFINE no_output.
fieldcatalog-fieldname = &1.
fieldcatalog-no_out = 'X'.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
END-OF-DEFINITION.
DEFINE catalog.
fieldcatalog-fieldname = &1.
fieldcatalog-seltext_s = &2.
if not &3 is initial.
fieldcatalog-seltext_m = &3.
else.
fieldcatalog-seltext_m = fieldcatalog-seltext_s.
endif.
if not &4 is initial.
fieldcatalog-seltext_l = &4.
else.
fieldcatalog-seltext_l = fieldcatalog-seltext_m.
endif.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
END-OF-DEFINITION.
catalog 'AVAIL_BASE'
'Base Qty.'
'Base Qty. Available'
'Base Quantity Available'.
catalog 'AVAIL_SALES'
'Sales Qty.'
'Sales Qty. Available'
'Sales Quantity Available'.
LOOP AT t_char_data.
idx = sy-tabix.
CONCATENATE 'CHR' idx INTO fld.
catalog fld
t_char_data-atbez
t_char_data-atbez
t_char_data-atbez.
ENDLOOP.
ADD 1 TO idx.
WHILE idx LE 15.
CONCATENATE 'CHR' idx INTO fld.
no_output fld.
ADD 1 TO idx.
ENDWHILE..
fieldcatalog-fieldname = 'EXACT'.
fieldcatalog-checkbox = 'X'.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
2.----
FORM fieldcatalog.
REFRESH fc. CLEAR fc.
fc-tabname = 'HEADER'.
fc-fieldname = 'KUNNR'.
fc-ref_tabname = 'MSKU'.
APPEND fc. CLEAR fc.
fc-tabname = 'HEADER'.
fc-fieldname = 'NAME1_K'.
fc-ref_tabname = 'KNA1'.
fc-ref_fieldname = 'NAME1'.
APPEND fc. CLEAR fc.
fc-tabname = 'HEADER'.
fc-fieldname = 'TOTAL'.
fc-ref_tabname = 'MBEW'.
fc-ref_fieldname = 'SALK3'.
APPEND fc. CLEAR fc.
fc-tabname = 'LIST'.
fc-fieldname = 'MATNR'.
fc-ref_tabname = 'MSKU'.
APPEND fc. CLEAR fc.
fc-tabname = 'LIST'.
fc-fieldname = 'MAKTX'.
fc-ref_tabname = 'MAKT'.
fc-no_out = 'X'.
APPEND fc. CLEAR fc.
fc-tabname = 'LIST'.
fc-fieldname = 'CHARG'.
fc-ref_tabname = 'MSKU'.
APPEND fc. CLEAR fc.
fc-tabname = 'LIST'.
fc-fieldname = 'WERKS'.
fc-ref_tabname = 'MSKU'.
fc-no_out = 'X'.
APPEND fc. CLEAR fc.
fc-tabname = 'LIST'.
fc-fieldname = 'NAME1_W'.
fc-ref_tabname = 'T001W'.
fc-ref_fieldname = 'NAME1'.
fc-no_out = 'X'.
APPEND fc. CLEAR fc.

Regarding Shift Activation In ECC 6.0

Hi, We are implementating ECC6.0 in our company. We have downloaded the Ecc6.0 enchnacement pacakages from service markets and applied it but still the shift is bnot being actives in confirmation screen
Please helps us in tghis regards
Bhupendra singh

Hi,
You have to execute following stpes to reflect shift in co11n
01 SPRO : OPK4 select freely definable screen number & put shift in pushbutton. This will only display shift on conn screen ( No input values)
02 ABAP Activity; Create new append structure in table AFRU ,include components & allowed values( shift 1,2,3),activate user exit confpp07 ,activate function group for screen 900.
03. Change screen layout as per requirement in se51.
this will make entry of shift possible in co11n as well as saving in table for reports.
Regards,
Milind.

Regarding Runtime error with MB_MIGO_BADI

Hi,
I have implemented badi MB_MIGO_BADI for MIGO transaction for GR. I have added 3 fields to the header level. If i save it it is saving(i Have created a Ztable to store it.).
If i give the material document number its showing the contents of the fields i have added.
But we can display the same GR through ME23N also. In ME23N transaction if i click on GR document, Its going for dump. The problem with field symbol.
Code is:
field-symbols <fs2> type MSEG.
 assign ('(SAPLMIGO)mseg') to <fs2>.
 <fs2>-zzoctno = WA_OCT_DET-OCT_NOTE.
 <fs2>-zzoctdate = WA_OCT_DET-OCT_DATE.
 <fs2>-zzmatdate = WA_OCT_DET-MAT_RECP_DATE.
its not asssiging ('(SAPLMIGO)mseg') to <fs2> .....when coming through ME23N.
The same statement is working fine through MIGO code.
Please let me know the solution
thanks,
kishore

Hello,
Change this
field-symbols <fs2> type TABLE. "CHeck here
Regards,
Vasanth

Regarding Runtime Analyzer in ECC 6.0

Similar Messages

Maybe you are looking for