Enhancement Statement in ECC 6.0

Hey guys,
I have question regarding this ENHANCEMENT statement...
What does it actually do?
Does it affect the flow of the program?

[http://help.sap.com/saphelp_nw2004s/helpdata/en/a0/47e94086087e7fe10000000a1550b0/frameset.htm|http://help.sap.com/saphelp_nw2004s/helpdata/en/a0/47e94086087e7fe10000000a1550b0/frameset.htm]

Similar Messages

Creating Enhancement Implementation for the Enhancement spot in ECC 6.0

Hi All,
I have an urgent requirement of creating an Enhancement implementation for the existing Enhancement Spot in ECC 6.0 ..
I never worked on enhancement in ECC 6.0.
There is an existing enhancement spot called "ES_SAPLIQS0" in the package " IWOC". which has got three existing implementations
1. DI_ROT_SAPLIQS0
2. ISU_SAPLIQS0
3. DIMP_GENERAL_SAPLIQS0
I need to create another implementation for the same enhancement spot.. Please let me know the detailed procedure to create the enhancement implementation for the same spot..
Thanks-
Shrikant
useful answers will be rewarded.

First of all find out the include program where you want to write the logic.. Click the spiral button to go to enhancement mode.. then click on Edit > Enhancement operations> Show implicit enhancement points.
This will hightlight all the enhancement points in your include program. Right click on exact enhancement point and select Enhancement Implementations --> Create,, It should give you the same Enhancement spot you are talking about. select that and write the code.. This code will be automatically appear in the same enhancement spot. You can see one more Enhancement implementation in the same Enhancement spot from the transaction code se19.
Hope my explanation is clear, if you have any doubts, send me a mail at [email protected]
All the best.
Shrikant

PROBELM WITH TYPE X VALUE '20' IN CONCATENATE STATEMENT in ECC version

Hi EXPERTS,
 I am working in ECC 6.0 version.
 PROBELM WITH TYPE X VALUE '20' IN CONCATENATE STATEMENT in ECC version
 C_DEL TYPE X VALUE '09' having solution --C_DEL TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB,
 If C_DEL TYPE X VALUE '20' what was the solution in ECC version.
 Please let me know. I am awaiting for ur answers
<REMOVED BY MODERATOR>
Message was edited by:
 Alvaro Tejada Galindo

Hi
welcome to SDN forum
move that X field to a char field and use in concatenation
CONCATENATE works only with CHAR fields
Regards
Anji

Position the cursor on an ENHANCEMENT statement .ED301

Hello Folks ,
I am changing an ENHANCEMENT and did a syntax check. the syntax check failed.
Editting is now locked out and when I place the cursor on the Enhancement statement and go to Edit > Enhancement Operations > Change Enhancement.
the "Position the cursor on an ENHANCEMENT statement" error statement appears even though the cursor was there.
I tried to "UNDO" the Enhancement So that I could put the correct code in. But,the same syntax error appears even though the bad code is not on the screen.
Has anyone else encountered this problem?

Hi Harel Gilor,
In that case you can delete/change that enhancement point by going to node Enhancements under your package name in SE80>Package>Enhacements.
Thanks & Regards,
Faheem.

Obsolete statements in ECC with respect to 4.5b

Hi Gurus,
This is really very urgent.i need an information on Obsolete Statements in ECC 6.0 with respect to 4.5B R/3 Version.please help me..
Full marks would be rewarded 100%
regards
Sahil

Hi
check the table PRGN_CORR2 which gives the list of transactions that were changed from different versions from 3.1G to 4.70 and also above versions
Pls check this
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
Reward if useful
Regards
Raghav T

Enhancement spot in ECC 6.0

Hi all,
can anyone please make it clear on what enhancement spot is in ECC 6.0.
All Useful answers will be rewarded..
Thanks & Regards,
Saroja.

Hi
ENHANCEMENT-POINT
ENHANCEMENT-POINT can either be static (for example, additional data declaration) or dynamic (for example, additional coding).
http://help.sap.com/saphelp_nw2004s/helpdata/en/56/ee9441026aae5fe10000000a1550b0/content.htm
Refer the very useful links below:
Enhancement-Point is a part of the new enhancement framework. He is some lite reading.
http://help.sap.com/saphelp_nw2004s/helpdata/en/94/9cdc40132a8531e10000000a1550b0/frameset.htm
Please check this blogs and wiki as well.
/people/thomas.weiss/blog/2006/05/03/source-code-enhancements--part-5-of-the-series-on-the-new-enhancement-framework
/people/thomas.weiss/blog/2006/03/15/the-new-enhancement-framework-part-2--what-else-you-need-to-know-before-building-an-enhancement
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/thenewEnhancementFrameworkandthenewkernel-basedBAdI&
Please check these weblog for more information and sample codes.
/people/thomas.weiss/blog/2006/01/24/what-the-new-enhancement-framework-is-for-150-its-basic-structure-and-elements-for-beginners
/people/thomas.weiss/blog/2006/03/15/the-new-enhancement-framework-part-2--what-else-you-need-to-know-before-building-an-enhancement
/people/thomas.weiss/blog/2006/04/03/how-to-define-a-new-badi-within-the-enhancement-framework--part-3-of-the-series
/people/thomas.weiss/blog/2006/04/18/how-to-implement-a-badi-and-how-to-use-a-filter--part-4-of-the-series-on-the-new-enhancement-framework
/people/thomas.weiss/blog/2006/05/03/source-code-enhancements--part-5-of-the-series-on-the-new-enhancement-framework
Look at this articles:
New Enhancement Framework
Enhancement Framework
Enhancement Framework - The New Way to Enhance Your ABAP Systems
Switch Framework Demo
Introduction to the Enhancement Framework
To now more about BADi Implementation see:
How To Define a New BAdI Within the Enhancement Framework
How to implement a BAdI And How to Use a Filter
Enhancement-Point is a part of the new enhancement framework. He is some lite reading.
http://help.sap.com/saphelp_nw2004s/helpdata/en/94/9cdc40132a8531e10000000a1550b0/frameset.htm
Please check this blogs .
/people/thomas.weiss/blog/2006/05/03/source-code-enhancements--part-5-of-the-series-on-the-new-enhancement-framework
/people/thomas.weiss/blog/2006/03/15/the-new-enhancement-framework-part-2--what-else-you-need-to-know-before-building-an-enhancement
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/thenewEnhancementFrameworkandthenewkernel-basedBAdI&
Enhancement frame work is the new concept using which SAP allows you to change the existing programs
See the following blogs that talk about the same in detail
/people/thomas.weiss/blog/2006/04/03/how-to-define-a-new-badi-within-the-enhancement-framework--part-3-of-the-series
/people/thomas.weiss/blog/2006/04/18/how-to-implement-a-badi-and-how-to-use-a-filter--part-4-of-the-series-on-the-new-enhancement-framework
/people/thomas.weiss/blog/2006/05/03/source-code-enhancements--part-5-of-the-series-on-the-new-enhancement-framework
Defines a position in an ABAP program as an enhancement option, at which one or more source code plug-ins can be inserted.
Syntax
ENHANCEMENT-POINT enh_id SPOTS spot1 spot2 ...
[STATIC]
[INCLUDE BOUND].
Extras:
1. ... STATIC
2. ... INCLUDE BOUND
Effect
: This statement defines an explicit enhancement option at the current position in the program at which a source code enhancement can be made. In program generation, the source code plug-ins of the assigned enhancement implementation that are available in the current system and have a switch in the status stand-by or on, are inserted at this position.
If the addition STATIC is not specified, the source code enhancement is dynamic. This means that in program execution, only those source code plug-ins are executed whose switch has the status on. If a source code plug-in does not have a switch assigned to it, it is handled in the same way as a plug-in with a switch in the status on.
With enh_id, an ID must be specified directly for the enhancement option, which is unique in the current compilation unit without the addition INCLUDE BOUND, and with this addition, is unique in current Include program. At least one enhancement spot must be assigned to the enhancement option using the specification simple enhancement spots spot1, spot2, and so on.
Within enhancements, one or more source code plug-ins can be created for one enhancement option. A source code plug-in is created by the assignment of an enhancement implementation in the Enhancement Builder. This automatically generates an empty source code plug-in with a unique ID, which is displayed underneath ENHANCEMENT-POINT in the Editor, where the actual enhancement can be implemented between ENHANCEMENT and ENDENHANCEMENT.
A source code plug-in is assigned to only one enhancement option. Multiple source code plug-ins of one enhancement implementation and the source code plug-ins of multiple enhancement implementations can be assigned to one enhancement point.
Notes
: In the terminology of the enhancement concept, the statement ENHANCEMENT-POINT includes both the enhancement spot element definition and the enhancement spot invocation of the enhancement option.
The statement ENHANCEMENT-POINT can either be entered directly or created by choosing Edit ? Enhancement operations ? Create enhancement in the Enhancement Builder. After the program has been saved or created using Edit ? Enhancement operations ? Create enhancement, the statement can only be deleted by choosing Edit ? Enhancement operations ? Delete enhancement.
In addition to the enhancement options explicitly specified by ENHANCEMENT-POINT, ABAP programs also contain implicit enhancement points, which can also be enhanced using source code plug-ins.
Addition 1
... STATIC
Effect
: The addition STATIC is used to define a static source code enhancement. In a static source code enhancement, all incorporated source code plug-ins are taken into account when the program is executed, including those whose switch is in the status stand-by.
Note
: The STATIC addition is intended for the enhancement of data declarations, while the statement ENHANCEMENT-POINT without the STATIC addition is designed for the enhancement of executable coding. When the statement is executed using Enhancements ? Create enhancement, the addition is set according to this selection.
Addition 2
... INCLUDE BOUND
Effect
: This addition can be entered in Include programs. It links the source code enhancement to the current Include program. Each program that incorporates an Include program only includes the source code enhancements that are defined with this addition. Source code enhancements created using the INCLUDE BOUND addition have their own namespace in each Include program. This ensures that if several Include programs are integrated into one compilation unit, no namespace conflicts arise, either between Include programs, or with the source code enhancements of the compilation unit.
Without the addition INCLUDE BOUND, a source code enhancement is assigned to only one compilation unit. If the statement ENHANCEMENT-POINT is executed in an Include program without this addition, a compilation unit must be assigned to it in the Enhancement Builder.
Note
: In an Include program, Include-bound and non-Include-bound source code enhancements can not be defined at the same time. This also applies if an Include program incorporates other Include programs.
Enhancement points are points provided by sap in standard programs to modify the source code. Go to any standard program, Locate the spiral button on the toolbar. Then press it and then navigate to edit->enhancement operations->display enhancement point menu. Then a no of yellow lines would appear, which are the available en points. You would have to change it and write the applicable source code.
Regards
Anji

Replacement of SEARCH ITAB statement in ECC 6.0

Hello Experts,
Can anybody tell me, which statement i can use to replace an obsolete statement i.e. SEARCH ITAB in ECC 6.0?
Thanks in advance!!
Best Regards,
Bhupinder

Hello,
While using FIND statement, i am getting bellow syntax error
As line type of the table "ITAB" in the CHAR MODE a indication-like and/or in the BYTE MODE a byte-like field was expected.
My statement is
FIND FIRST OCCURRENCE OF 'WHERE'
IN TABLE ITAB
What should i do to resolve this sytax error?
Best Regards,
Bhupinder

PROBLEM IN MOVE STATEMENT IN ECC 6.0

hi EXPERTS,
THE FOLLOWING CODE WORKS FINE IN 4.6C BUT IN ECC 6.0 THE MOVE STATEMENT AT THE END THROWS ERROR.
""INNNN" and "I0008" are not mutually convertible. In Unicode systems, "INNNN" must have the same structure layout (fragment view) as"I0008", regardless of the length of the Unicode character."
DATA: i0001 LIKE p0001 OCCURS 0 WITH HEADER LINE,
 i0008 LIKE p0008 ,
 innnn like PRELP.
SELECT * INTO CORRESPONDING FIELDS OF TABLE i0001
 FROM pa0001
 WHERE begda <= 20061201
 AND endda >= 20061201
 AND pernr = 00014442 .
READ TABLE i0001 INDEX 1.
 i0008-trfgr = i0001-persk.
 CASE i0001-persg.
 WHEN '4'.
 i0008-trfst = i0001-persg.
 WHEN '7'.
 i0008-trfst = i0001-persg.
 WHEN '8'.
 i0008-trfst = i0001-persg.
 WHEN OTHERS.
 i0008-trfst = '1' .
 ENDCASE.
 MOVE i0008 TO innnn.
I'VE ALSO CHECKED THE SAME PROGRAM IN DEBUGGER IN 4.6C.
I'VE FOUND THAT THE VALUES FOR i0008-trfgr i0008-trfst ARE TOGETHER STORED IN THE FIELD DATA1 OF INNNN. BUT THIS DOES NOT HAPPEN IN ECC 6.0.
PLEASE HELP.
ITS URGENT.

Hi priya,
DATA: i0001 LIKE p0001 OCCURS 0 WITH HEADER LINE,
i0008 LIKE p0008 ,
declare innnn like this and check
innnn like p008.
regards,
Nagaraj

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

READ TABLE statement in ECC 6.0

hi,
in 4.6, my statement was
READ TABLE S_XVTTS WHERE TKNUM = S_XVTTK-TKNUM
AND NOT S_XVTTS-VSTEL IS INITIAL.
This wont work in ECC 6.0, hence I need to modify this. so i write like
READ TABLE S_XVTTS INTO wa_vttsvb WITH KEY TKNUM = S_XVTTK-TKNUM ..................................
how to accomodate the check for NOT initial of S_XVTTS-VSTEL .. how will my statement look like ? thks

Hi Sdnuser1,
Try to use LOOP statement as follow.
"// This LOOP read only one line of table s_xvtt exactly as READ TABLE do.
LOOP AT s_xvtts INTO wa_vttsv WHERE tknum EQ s_xvttk-tknum AND s_xvtts-vstel IS NOT INITIAL.
EXIT.
ENDLOOP.
IF sy-subrc IS INITIAL.
"// You can use wa_vttsv
ELSE.
"// Do something
ENDIF.
I hope it helps yous.
Greetings.
Marcelo Ramos

Perform statement in ECC 6.0

hi,
So is it the best practice that we have to avoid creating FORM-ENDFORM in ECC 6.0 and also avoid using PERFORM statement ? what will be the alternative for this ?
I have a couple of includes where there are lots of FORMS.
thks

Use METHODS instead of creating FORM-PERFORM. ECC is all about Object Oriented Concepts.

How to Check Enhancement Pack of ECC system

Hi Experts,
I want to check enhancement pack of My SAP R/3 ECC 6.0 system.
Where can i find this information can you please help.
In System --> Status --> in component version i can see "SAP ECC 6.0".
On click of the button provided below this component version , i can see following details:
SAP_ABA             700                     0011     SAPKA70011     Cross-Application Component
SAP_BASIS     700                     0011     SAPKB70011     SAP Basis Component
ST-PI             2005_1_700     0005     SAPKITLQI5     SAP Solution Tools Plug-In
PI_BASIS             2005_1_700     0011     SAPKIPYJ7B     PI_BASIS 2005_1_700
SAP_BW             700                     0011     SAPKW70011     SAP NetWeaver BI 7.0
SAP_AP             700                     0007     SAPKNA7007     SAP Application Platform
LCAPPS     2005_700                     0003     SAPKIBHD03     LC Applications (LCAPPS) 2005_700
SAP_APPL     600                     0006     SAPKH60006     Logistics and Accounting
from this information can you please help me identify my SAp R/3 ECC 6.0 system's enhancement pack version?
Regards,
Ashish Shah

SAP_APPL 600 No EHP
SAP_APPL 601 EHP1
SAP_APPL 602 EHP2
SAP_APPL 603 EHP3
SAP_APPL 604 EHP4
SAP_APPL 605 EHP5
SAP_APPL 616 EHP6
SAP_APPL 617 EHP7
Sorry if i am wrong....thats how i find it...i am an ABAPer.
Regards,
Vishnu

How to use Enhancement Framework in ECC 5.0 and 6.0

hi
is there any good tutorials on enhancement framework? i have gone through the help but its not very clear. if anyone has stepby step guide will be useful.
~Suresh

This is an old question... but i think it is very useful for the developers if anyone search it and find my answer relevant like it with immediate effect.....
What is Enhancement Framework?????????
Enhancement Framework is the new paradigm to bring all enhancement techniques under one roof. It can also be switched using Switch Framework. The following are different enhancement technologies available under this framework.
• Source Code Enhancement
• Function Group Enhancement
• Class Enhancement
• Kernel-BADI Enhancement
Semantically related enhancement options are grouped under a ‘Simple Enhancement Spot’. ‘Composite Enhancement Spot’ contains one or more of Simple and other Composite Enhancement Spots. On the other hand (implementation side), various related implementation elements are grouped under a ‘Simple Enhancement Implementation’. A ‘Composite Enhancement Implementation’ can contain one or more of Simple and other Complex Enhancement Implementations.
1.Source Code enhancement
Whenever enhancement needs to be incorporated directly into the ABAP source code, this technology shall be provided. Implementing this technology is also called as Source Code Plug-In. There are two types of Source Code enhancements possible.
• Implicit enhancement option
• Explicit enhancement option
>>>Implicit enhancement option
Throughout the ABAP system, enhancement options are automatically available at certain pre-defined places. Some of the implicit options are:
• At the end of all the programs (Includes, Reports, Function pool, Module pool, etc.), after the last statement
• At the beginning and end of all FORM subroutines
• At the end of all Function Modules
• At the end of all visibility areas (public, protected and private) of local class
******Note that, in order to implement any of these Source code enhancements, you need to be in the ‘Change Enhancement mode’ (the spiral icon available in the editor). Technically the source code plug-in implementations are stored in a separate include program and not as part of the original source program.***********
>>>>Explicit enhancement option
The Implicit enhancement options are provided at specific source code places explicitly by SAP (Note that these enhancement definitions can also be created by partners and customers in their code).
There are two types of Explicit Enhancement options available. One which can be provided at a specific place - called Enhancement Point, and another which can be used to replace a set of statements – called Enhancement Section. For this, we now have two new ABAP statements, viz.
• ENHANCEMENT-POINT
• ENHANCEMENT-SECTION
When the Enhancement-Section is implemented, only the implementation gets executed and the original code doesn’t get executed. This is a new technique, which didn’t exist previously in any of the old ways of enhancing, to exclude any standard SAP code from execution. Because of this, there can be only one active implementation of an Enhancement-Section. On the other hand, there can be multiple active implementations of an Enhancement-Point, in which case all the implementations will be executed with no guarantee in the order of execution.
we mainly use above framework .......if nybody need further and more information let me knw...

Idoc in processing state in ECC

Hi All,
I have JMS to Idoc scenario.
The data is being successfully posted from PI. I have checked sxi_monitor and RWB both.
The Idocs reach ECC but are in Processing state. Status 64.
I checked we20 Partner profile it is set to trigger immediately.
Please suggest what could be possible error.
Thanks.

Hey,
>Can this be the reason: Username used to create the Partner profile does not have authorizations.
No,
Did you checked Queue Processing check Box ? & what is the Package value you mentioned ( Try with value - 1 ),
Cheers
Agasthuri

Syntax Error with EXPORT statement in ECC 6

Hi All,
I have one issue with EXPORT statement syntax.
I have declared data like below:
DATA: BEGIN OF mem_id,
          mandt LIKE sy-mandt,
          uname LIKE sy-uname,
          modno LIKE sy-modno,
        END OF mem_id.
export the memory id
    EXPORT E_VBKOK XANZPK TEXTTAB XBOLNR TO MEMORY ID MEM_ID.
When I am checking the syntax error i am getting like "MEM_ID" must be a character-type field (data type C, N, D or T). by "INTERFACE". by "INTERFACE". "INTERFACE". by "INTERFACE". by "INTERFACE".
I know this statement would be like IMPORT ITAB TO JTAB FROM MEMORY ID 'table'. So I have written like below
EXPORT E_VBKOK XANZPK TEXTTAB XBOLNR TO MEMORY ID 'MEM_ID'. But still it is throwing an error.
Can you please let me know how can I resolve this?
Regards,
Jyothi CH.

Hi Jyothi,
data: l_var type string.
concatenate '6' '8' into l_var separated by space.
export l_var to memory id 'BB'.
Here we have to declare the type(structure) for l_var not for BB
and in another program
data:l_var type string.
import l_var from memory id 'BB'.
write : l_var.

Enhancement Statement in ECC 6.0

Similar Messages

Maybe you are looking for