Overview:

Recently in a project, the SAP ECC and SAP CRM system is upgraded to higher product version in order to enable most areas of Existing ERP functions for SAP HANA to utilize the in-memory technology and to enable better performance of Business Applications. As part of this upgrade Activity, there are few implications to SAP BW extractors which are being listed out here for reference.

Technical Information:

S:NO

System name

Previous Version

Upgraded Version

1

SAP ISU

SAP ERP6.0 EHP5 with Utilities Add on

SAP ERP6.0 EHP7 with Utilities Add on

2

SAP CRM

SAPCRM7.0 EHP1

SAPCRM7.0 EHP3

3

Net weaver( For ISU & CRM )

SAP Net weaver  7.02

SAP Net weaver  7.40

4

BW

SAP BW 7.31 ( Support Package – SAPKW73106)

NA

Impacts to BW


As Part of this Upgrade, there were least expectations on the impacts from BW perspective. However while performing testing as part of upgrade, we were ought to face few issues. The scope of this document is to have an understanding on those issues and the resolution steps which could be referred in other requirements. I have classified the issues based on the system scope.

From ISU Perspective, we had faced the following issues .

Sales Stats (0UC_SALES_STATS_02) mass activity T-code was not accessible.

  • 0FC_SUBNO field was changed to 4 in the source system.
  • delta pointer issue
  • LIS extractors went to dump while running Delta

From CRM perspective, we had faced only one issue is

  • DB Cursor issue with the data source 0CRM_CAT_CATEGORY_ATTR

  was not accessible.

  • 0FC_SUBNO field was changed to 4 in the source system.
  • delta pointer issue
  • LIS extractors went to dump while running Delta

Fixes :

  • Sales Stats (0UC_SALES_STATS_02) which can be accessed via mass activity T-code ( EBW_DQ_SS) :

While tried to run the mass job , we got the error Code “ Table inconsistency. Group box 5503 not found”.

We found a recommendation from SAP through the note number “2036184” and after applying the note, the issue got resolved. PFA for more details on the SAP note.

  • 0FC_SUBNO field was changed to 4 in the source system.

.

The standard data source 0FC_PAY is used to extract the payment relevant data from ISU to BW for Analytical purpose. Under this data source there is a field “SUBNO” which is used to identify the payment sequence number and its length is changed from NUMC 3 to NUMC 4 as part of EHP7 upgrade. However the BW Business content was not activated in BW which resulted type conflict while loading data.

In order to overcome the above mentioned issue, SAP has suggested via an SAP note either to activate the business content delivered version as part of BI CONT version SAPK-74601INBICONT or to change the lengthof the info object 0FC_SUBNO manually.

We activated the business content in Dev and moved across other environments via CTS (Change and transport system).

While doing so the transport might go into error due to the existence of master data. We need to use SE14 (data base utility) to activate and adjust the /BI0/SFC_SUBNO table. The solution can be reffered via the SAP Note : 167225.

  • DB Cursor issue with the data source 0CRM_CAT_CATEGORY_ATTR

This Standard CRM data source is extracting data for Category attributes relevant for transactions raised in CRM. Transactions can be raised for various reasons like Work request, claim request, disconnection/reconnection request. After initial analysis, it was found that the commit statement after the open and fetch cursor was not happening properly. SAP suggested to go for the kernel upgrade as a permanent solution and also advised to increase the data transfer parameters at the source system as an intermediate solution.

Kernel Upgrade was carried out in CRM as per the advice from SAP taskhandler dispatcher department. Soution can be referred via the SAP Note No: 2093140.

  • Few other minor issues:

We faced few challenges while loading delta data to 2LIS_11_VAITM and 2LIS_18_I0NOTIF. Issues were faced only in the Test and pre-prod system.  We just deleted the initialization pointer and performed re-initialization. Please note this may not be applicable for other data sources as the functionalities varies

  ested to go for the kernel upgrade as a permanent solution and also advised to increase the data transfer parameters at the source system as an intermediate solution.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply