Technical Details on Correction Instructions

Format

Correction instructions describe changes that need to be made to repository objects in the ABAP Workbench, most commonly to the ABAP source code, in order to correct errors.

Correction instructions can also be manual activities that have to be performed alongside the implementation of automatic correction instructions.

Changes to the Source Code

Each change specifies the object (include, function module, and so on) and the modularization unit (such as the FORM routine). To identify the code that needs to be changed, you first need to specify the number of unchanged lines preceding it (context block). These lines are followed by the ones that need to be deleted (delete block) and then the new lines (insert block).

Correction instructions can consist of multiple context, delete and insert blocks.

Whenever the system implements correction instructions automatically, it searches for the context blocks in the function module or include, checks whether the delete blocks follow and then replaces them with the insert block.

If the function module or include has been modified by the customer, the system sometimes cannot find the context blocks or delete blocks specified in the correction instructions, and it cannot implement all the corrections. If this is the case, you can use the split-screen editor to adjust the corrections from the SAP Note to your modifications.

Changes to Other Repository Objects

Repository objects or parts of them that are not of the source code type are stored in database tables. Correction instructions contain information about which table entries have to be deleted, inserted or changed to correct an error. The system displays this information in the form of the content of a set of correction instructions. However, this display is primarily designed with experts in mind, for the purpose of problem analysis. You are advised not to implement correction instructions manually using this information. Use automatic implementation only.

Manual Activities

For objects that cannot be implemented using automatic correction instructions, manual activities can be created in text form. You generally need to perform these activities manually either before implementing automatic correction instructions (manual pre-implementation steps) or afterwards (manual post-implementation steps). Note Assistant displays manual activities in the Correction Instructions Queue. You can only continue implementing the Note once you have confirmed that the manual activity has been performed.

For each manual activity, the system indicates whether or not its results are transportable, that is, whether performance of the activity can be recorded in a change request. If a manual activity is not transportable, you need to perform it individually in every system in your system landscape where you import the SAP Note to. You can then restart the Note implementation process and confirm that the manual activities have been performed. If you do not do this, the Note will not be completely implemented in the follow-on systems.

Validity

All correction instructions specify the releases and Support Package levels in which you can implement them. These release and Support Package levels are known as the validity range of the correction instructions.

For example, if Support Package 5 corrects an error in Release 4.6C, the validity range of the correction instructions is 4.6C Support Packages 1 - 4.

An SAP Note can also stipulate that correction instructions cannot be implemented if a certain software component (an add-on, for example) is installed in the system. This could happen, for example, if a correction would change a program part that is actually required by another software component in its present (unchanged) form.

If an exception criterion like this has been defined, it is displayed in the header area of the correction instructions, under Invalid for <software component, release, Support Package level>.

Note Assistant automatically checks the validity, and only implements correction instructions if the system status is within the specified validity range.

Objects that can be changed using correction instructions

The following objects can be described and automatically implemented in correction instructions:

Valid for SAP Web AS 6.20, from Basis Support Package 55, SAP Web AS 6.40 from Basis Support Package 13 and higher :

• ABAP programs (REPS): ABAP source text and properties

• Screens (DYNP): ABAP source text, properties and element list

• Function modules (FUNC): ABAP source texts, properties, interface parameters and exceptions

• Classes (CLAS):

  • Class definitions (CLSD)

  • Local class definitions (CINC): For local definitions, local class implementations, and macros

  • Private sections (CPRI)

  • Protected sections (CPRO)

  • Public sections (CPUB)

• Interfaces (INTF): Interface section

• Type groups (TYPD): ABAP source text and properties

• Methods (METH): ABAP source text, properties, parameters, and exceptions

• Pages/controller for a BSP application (WAPP): ABAP source text, properties, layout, event handler, page attributes, and type definitions

Valid for SAP Web AS 6.40 from Basis Support Package 13 and higher :

• ITS objects (Internet Transaction Server):

  • Non language-specific binary data of an IAC (Internet Application Component) (IAMU)

  • Non language-specific IAC templates (IATU)

  • Parameters of an IAC service (IASP)

  • Parameters of an IAC language resource (IARP)

• Info objects from the MIME repository (SMIM)

Valid for SAP NetWeaver AS 7.0 in Basis Support Package 4 and higher :

• Enhancement Framework objects:

  • Enhancement implementations (ENHO): ABAP source code enhancements

  • Enhancement spots (ENHS): ABAP source code definitions

  • Composite enhancement implementations (ENHC)

  • Composite enhancement spots (ENSC)

Valid for SAP NetWeaver AS 7.0 in Basis Support Package 9 and higher:

• Web Dynpro comp./intf. (WDYN):

  • Web Dynpro definition (WDYD)

  • Web Dynpro controller (WDYC)

  • Web Dynpro view and windows (WDYV)

  Note Assistant also displays object type WDCV. This is an object type created especially for Note Assistant, combining object types WDYC and WDYV. Type WDCV is used only for internal processing of Web Dynpro objects. It is not included in your system.

Applies to SAP NetWeaver 7.0 as of Basis Support Package 22, SAP enhancement package 1 of SAP NetWeaver 7.0 as of Basis Support Package 7, SAP enhancement package 2 of SAP NetWeaver 7.0 as of Basis Support Package 3, SAP NetWeaver 7.1 as of Basis Support Package 10, SAP enhancement package 1 of SAP NetWeaver 7.1 as of Basis Support Package 5, SAP NetWeaver 7.2 as of Basis Support Package 2, SAP NetWeaver 7.3 and higher releases:

• Enterprise Services:

  • Enterprise Services Proxies (SPRX)

  • Enterprise Services Virtual Endpoints (WEBI)

Applies to SAP NetWeaver 7.0 as of SAP enhancement package 2, SAP NetWeaver 7.3 and higher releases:

• Web Dynpro configurations

  • Web Dynpro component configurations (WDCC)

  Note

  The Note Assistance does not support Web Dynpro application configurations (WDCA).

Applies to SAP Business Suite Foundation (SAP_BS_FND) 7.02 SP3 and 7.03 and higher releases:

• Business Object Processing Framework (BOPF):

  • Business Object Models (BOBF)

  • Business Object Model Enhancements (BOBX)

• Visual Business:

  • Visual Business Applications (VBAP)