SAP Note 1601120 - Extended check for access sequences in customizing

Reason and Prerequisites
Extended checks for access sequences of pricing and pricing related usages during customizing download. For details please check note 1600482.

Solution
The solution can be implemented by the following steps:
1. Implement the manual preparation steps valid for your release.
2. Implement the attached coding changes.


------------------------------------------------------------------------
|Manual Pre-Implement. |
------------------------------------------------------------------------
|VALID FOR |
|Software Component BBPCRM BBP / CRM |
| Release 400 From SAPKU40001 |
------------------------------------------------------------------------
1. Step to transaction SE91.

2. Choose message class CND_MAP

3. Select number 208 and hit the 'Change' button.

a) Create the following short text for the message:
'Data exchange was canceled due to a fatal error'
b) Save the message.
c) Deselect the check box 'self explainatory' and maintain the following longtext for the message:

Diagnosis
The data exchange was canceled due to a fatal error. The exchanged data was only partly posted in the system. The pricing customizing is inconsistent.


Procedure
Clean up the fatal error that triggered the cancellation, and then
startthe data exchange again for the corresponding exchange object.
<zh>Until the exchange for the corresponding exchange object is successfully completed, the pricing can lead to incorrect results.</>
d) Activate the longtext and save.

4. Select number 209 and hit the 'Change' button.
a) Create the following short text for the message:
'The access type A is not available (access seq. &1, access &2,
field &3)'
b) Save the message.
c) Deselect the check box 'self explainaty' and maintain the following
longtext for the message:
Diagnosis
The access type A (hierarchical access functionality) is not
available.
The error was triggered by access sequence &V1&, access number
&V2&, field &V3&.
Procedure
For details, see SAP note 1600482.
d) Activate the longtext and save.

------------------------------------------------------------------------
|Manual Activity |
------------------------------------------------------------------------
|VALID FOR |
|Software Component BBPCRM BBP / CRM |
| Release 500 Until SAPKU50019 |
| Release 520 All Support Package Levels |
| Release 700 SAPKU70001 - SAPKU70010 |
| Release 600 SAPKU60001 - SAPKU60010 |
| Release 701 SAPKU70103 - SAPKU70106 |
------------------------------------------------------------------------
1. Step to transaction SE91.
2. Choose message class CND_MAP
3. Select number 209 and hit the 'Change' button.

a) Create the following short text for the message:
'The access type A is not available (access seq. &1, access &2,
field &3)'
b) Save the message.
c) Deselect the check box 'self explainatory' and maintain the
following longtext for the message:

Diagnosis
The access type A (hierarchical access functionality) is not available.
The error was triggered by access sequence &V1&, access number &V2&, field &V3&.
Procedure
For details, see SAP note 1600482.
d) Activate the longtext and save.

Read Complete Note @ Market Place

SAP Note 1601052 - Extended checks for customizing of condition access sequence

Reason and Prerequisites
Extended checks in the customizing view for condition access sequences.
For details please check note 1600482.

Solution
The solution can be implemented by the following steps:
1. Implement the manual preparation steps valid for your release (new messages). This is only necessary before 4.6C.
2. Implement the automatic correction instruction (coding changes).
3. Apply the manual post-processing steps valid for your release.


------------------------------------------------------------------------
|Manual Post-Implement. |
------------------------------------------------------------------------
|VALID FOR |
|Software Component SAP_APPL SAP Application |
| Release 45B All Support Package Levels |
| Release 46B All Support Package Levels |
| Release 46C Until SAPKH46C62 |
| Release 470 Until SAPKH47036 |
| Release 500 SAPKH50001 - SAPKH50025 |
| Release 600 SAPKH60001 - SAPKH60020 |
| Release 602 Until SAPKH60210 |
| Release 603 Until SAPKH60309 |
| Release 604 SAPKH60401 - SAPKH60410 |
| Release 605 Until SAPKH60507 |
------------------------------------------------------------------------


This note introduces a consistency check routine in the customizing view cluster for maintenance of access sequences.

After the coding changes have been implemented, the check routine has to be added and activated in the view cluster and its variants. This can be achieved by downloading and running the attached report
ZZ_VVC_UPDATE_NOTE_1601052.

The report has to be executed manually in the development system. The report adds routine V_T682_SAVE_CHECK to the save event of certain view cluster variants.


It is rarely possible that error messages arise (e.g. view cluster variants are locked by another user). In such a case the report has to be executed again after the situation that led to the error has been resolved (e.g.
user has unlocked the view cluster variants).
With this run all view cluster variants that were not updated due to the error situation should be updated.

IMPORTANT:
1. The report records the performed changes to a transport request. These changes should be transported together with the automatic coding changes from note 1601052. The report doesn't have to be
executed in the target (productive) systems.
2. It is not necessary to transport report ZZ_VVC_UPDATE_NOTE_1601052 to other systems than the development system.

In detail, report ZZ_VVC_UPDATE_NOTE_1601052 does the following:


a) The list of view cluster variants relevant for your release is determined.

b) The following view cluster variants are updated:
- V_T682
- VVC_T682_MA
Starting from release 4.6B furthermore:
- VVC_T682_VA
Starting from release 4.6C furthermore:
- VVC_T682_CQ
- VVC_T682_FA
- VVC_T682_KA
- VVC_T682_KE
- VVC_T682_MS
- VVC_T682_TP
- VVC_T682_TX
In case the check routine V_T682_SAVE_CHECK is already active for a certain view cluster variant, the view cluster variant is not updated.

c) All changed objects are recorded to a transport request. When you are asked by the report, you have to enter a transport request.

d) After the report was successfully run without any error message, the transport request contains two objects for every updated view cluster variant, e.g.:
R3TR VCLS VVC_T682_MA
R3TR TOBJ VVC_T682_MAC

SAP Note 1600091 - Deactivation of hierarchical access functionality

Reason and Prerequisites
Extended checks during runtime for pricing and pricing related usages and during customizing of access sequences.
For details check note 1600482.

Solution
The correction consists of a Java correction as well as an ABAP correction.
These corrections are included in SAP AP 7.00 Support Package 26.
The application of these corrections is only possible with an installation of SAP_AP 7.00 Support Package 26 or a higher support package.
If it should not be possible to install a support package of SAP_AP 7.00, then please apply note 1798794 for ERP-systems or note 1776338 for CRM, SRM and GTS.



For Complete information please read the note @ Market Place

SAP Note 1599403 - Deactivation of hierarchical access functionality

Reason and Prerequisites
Extended checks during runtime for pricing and pricing related usages.
For details check note 1600482.

Solution
Implement the manual pre-implementation and the attached changes in the
source code.
------------------------------------------------------------------------
|Manual Pre-Implement. |
------------------------------------------------------------------------
|VALID FOR |
|Software Component SAP_APPL SAP Application |
| Release 45B All Support Package Levels |
| Release 46B All Support Package Levels |
| Release 46C Until SAPKH46C63 |
| Release 470 Until SAPKH47036 |
| Release 500 SAPKH50001 - SAPKH50025 |
| Release 600 SAPKH60001 - SAPKH60020 |
| Release 602 Until SAPKH60210 |
| Release 603 Until SAPKH60309 |
| Release 604 SAPKH60401 - SAPKH60410 |
| Release 605 Until SAPKH60507 |
------------------------------------------------------------------------

1. Step to transaction SE91.
2. Choose message class VT
3. Select number 664 and hit the 'Change' button.

a) Create the following short text for the message:
'Hierarchical access not possible (access seq. &1, access &2, field &3)'

b) Select the check box 'self explainaty' and save.
The following steps c) and d) are optional.

c) Deselect the check box 'self explainaty' and maintain the following long text for the message:

Diagnosis
The functionality of the hierarchical access is not possible.
The error was triggered by access sequence &V1&, access number
&V2&, field &V3&.

Procedure
Adjust the access type and continue processing.
For details, see SAP note 1600482.

d) Activate the longtext and save.

SAP Note 1600482 - Hierarchical access functionality

Summary

Symptom

IMPORTANT: This and the related SAP Notes implement a change to the

functionality of the hierarchical access feature for use in pricing and

pricing-related functionality. Because of a court order in a patent

litigation involving SAP, application of these changes is mandatory for all

U.S. customers, all customers with U.S. installations, and all customers

with U.S. users. These changes are already included in Business Suite 2011

(including ECC 6.0 EHP6) and in SP26 of the SAP AP 7.00 software component.

Application of the related SAP Notes 1599403, 1600091, 1601052, 1601120

1643194, 1645515, 1645516 is required, either manually or via installation

of the relevant Support Packages.

Please see the attachment of this note to determine which notes are

relevant for your product versions.

The changes contained in these Notes are included in the Support Packages

for affected products as listed below:

Product Version  Required Support Package Stack

R/3 4.6C SP17

Enterprise 4.7 x1.0 SP37

Enterprise 4.7 x2.0 SP37

ERP 2004 SP26

ECC 6.0 SP21

ECC 6.0 EHP2 SP11

ECC 6.0 EHP3 SP10

ECC 6.0 EHP4 SP11

ECC 6.0 EHP5 SP08

CRM 5.0 = CRM 2005 SP20

CRM 2007 SP11

CRM 7.0 SP11

CRM 7.0 EHP1 SP07

SRM 5.0/SRM 2005 SP20

SRM 7.0 SP12

SRM 7.0 EHP1 SP07

GTS 7.1 SP25

GTS 7.2 SP23

GTS 8.0 SP19

GTS 10.0 SP09

As detailed below, customers who do not use hierarchical access for pricing

or pricing-related usages will not be affected by the application of this

SAP Note. Nevertheless, if you are not using hierarchical access

functionality in pricing or pricing-related functionalities and are not

planning to use it, application of the notes relevant for your product

version is still mandatory. No further action beyond the application of

these notes is necessary, as application of these notes will not affect

your use of the SAP solution.

If you are not sure whether you are using this specific functionality, we

strongly recommend that you run the check report included in the related

SAP Notes 1600090 and 1601021 before you install a Support Package as

listed above. The check reports allow you to easily check whether this

specific pricing functionality is being used in your system(s).

When you install or upgrade to a new product version of an ERP, CRM, SRM or

GTS system, you will be required to implement at least the Required Support

Package level for that product version listed above. Until the Required

Support Package level is applied to your upgraded system, pricing and

condition technique will abort with the run-time error "support package

level not sufficient". Please review the information in this Note and

contact us by creating a support ticket under the XX-PROJ-IMS-HA component

if you have additional questions about these changes or what you can expect

when you install a new product version.

Please read the following information carefully before applying these SAP

Notes.

Reason and Prerequisites

Translated version of this note being for convenience but not legally

binding.

Solution

Application of these Notes is mandatory for all U.S. customers, all

customers with U.S. installations, and all customers with U.S. users. This

and the related SAP Notes disable the hierarchical access feature (access

type = "A") in pricing and pricing-related functionalities, including

general pricing, rebate calculation, free goods, tax determination,

campaign determination, product determination, product substitution,

generic "data determination," GTIN (Global Trade Item Number) mapping, and

commodity pricing. Hierarchical access differs from a standard access

sequence.

Only the hierarchical access functionality is affected by this Note. The

use of standard access sequences to access condition records associated

with a hierarchy, such as a product hierarchy or customer hierarchy, is not

affected by this Note. The use of standard access sequences is not

affected by this Note.

Following the application of this SAP Note, pricing must use the standard

form of access sequence without access type "A". As detailed below,

customers who do not use hierarchical access will be unaffected by the

application of this SAP Note. Uses of hierarchical access outside of

pricing and pricing-related functionalities are also unaffected.

If you are not sure whether or not you are using this specific

functionality, we strongly recommend that you run the check report included

in the related SAP Notes 1600090 and 1601021 before you install a Support

Package as listed above. The check reports allow you to easily check

whether this specific pricing functionality is being used in your

system(s).

If you are not using hierarchical access functionality in pricing or

pricing-related functionalities and are not planning to use it, no further

action beyond the application of these notes is necessary, as application

of these SAP Notes will not affect your use of the SAP solution.

If you are already actively using or planning to use this functionality, we

request that you contact us by creating a support ticket under the

XX-PROJ-IMS-HA component so that we can work together to ensure that your

SAP solution continues to satisfy your needs in the future.

Overview: Impact of Installation of this SAP Note

1. Customers who do not use hierarchical access in pricing or

pricing-related functionality.

Customers will experience no change in their operation of the SAP

system.

2. Customers who use hierarchical access in pricing or pricing-related

functionality.

The SAP system will function differently, as described below, after

the application of this SAP Note.

a) Existing access sequences of the type "Hierarchical Access"

(created before the installation of this SAP Note) in pricing or

pricing-related functionality will no longer function as before.

Pricing will abort with a run-time error if an access sequence of

the type "Hierarchical Access" is used for searching price data.

These access sequences may be converted to the standard form of

access sequence. SAP can assist you with this process to ensure

that your SAP solution continues to satisfy your needs.

b) It will no longer be possible to create a new access sequence of

the type "Hierarchical Access" in pricing or pricing-related

functionality. The new access sequence cannot be saved. For

pricing and pricing-related functionality, use the standard form of

access sequence.

If you have any questions regarding this Note, you can contact us by

creating a support ticket under the XX-PROJ-IMS-HA component identified

above.

The Note is release-independent