SAP BW 7.3 Upgrade Issues and Solutions

• RSA1->InfoObjects->Search
  for 0CALMONTH->Change->In the ‘Master Data/texts’ tab, check ‘With
  texts’->Activate->Continue and accept all warnings.
• Perform
  above steps for each of the following time chars:
  • CALMONTH
  • 0CALMONTH2
  • 0CALQUARTER
  • 0FISCYEAR

• Amend
  the handling of the field TECHSTATUS as returned from the FM i.e.
• Replace
  the following code:

• T/C SICF
• For Service Name, enter “RSO_METADATA_REPOSITORY”
• F8 Select
  the service (child node in the displayed hierarchy)
• Select Service/Host from the main menu
• Select Activate
• Click Yes when
  prompted to confirm

• Change the “Set Quality Status to OK” flag for each InfoCube where this issue will occur. Identify the list of cubes as follows:
  • T/C
    SE16
  • Table
    name: RSDCUBE
  • Filters:
    OBJVERS = ‘A’, CUBETYPE=’B’, AUTOQUALOKFL=initial values.

• For every cube in the list ,do the following.
  • T/C RSA1 and select “InfoProvider”
  • Search for the cube and Select “Manage”
  • From the Main Menu, Select “Environment” and “Automatic Request Processing”
  • Check “Set Quality Status to OK (Confirm Quality of Data)” and select “Save”
  • When prompted to Write a transport request, select “No”

• T/C: MOD. Provide the componennt name  and
  select Deactivate on the toolbar
• Check Enhancements and select change
• Select the current enhancements and select Delete Row on the toolbar and select Save
• Add the enhancement (RSR00001) and select Components
• When prompted, select Save.
• In the list of Components, select Activate

• Local chains embedded in other chains fail if the local chain is inactive.
• Only a very small percentage of chains are “inactive” after the upgrade.

• Identify process chains to be re-activated. Re-activate the chain in each environment (the re-activated chains are therefore not transported)
• Identify the chains as follows: T/C: SE16->RSPCCHAINATTR
• OBJVERS = ‘A’
• ACTIVFL != ‘X’

• Apply manual changes to the update rules as per Note: 1713932
  • Goto RSA1. Navigate to infoprovider 0TCT_C22 and double click on the transfer rules
    for datasource 0TCT_DS22
  • Change to edit mode
  • Choose the field 0TCTTIMSTMP in the transfer rules and click on assignment button and
    select the radio button ‘Routine’ and click on ‘Create’ button.
  • Enter the transfer routine name as ‘Long timestamp -> short timestamp’.
  • Select the field ‘0TCTSTRTTST’ and enter.
  • Under FORM COMPUTE_TCTTIMSTMP, Please mention the below sentence RESULT = TRUNC(
    TRAN_STRUCTURE-TSTMP_START ).
  • Save the routine.

• execute access (Activity 16) for RFC = RSBAPI_IOBJ (Type = FUGR)
• execute access (Activity 16) for RFC = BAPI_IOBJ_GETDETAIL (type FUNC)
• execute access (Activity 16) for RFC = BDL5 (Type = FUGR)
• execute access (Activity 16) for RFC = BDL_GET_CENTRAL_TIMESTAMP (Type FUNC)
• execute access (Activity 16) for RFC = RSBAPI_IOBJ (Type = FUGR)
• execute access
  (Activity 16) for RFC = BAPI_IOBJ_GETDETAIL (Type = FUGR)

• Change the transfer  rule from iDoc to PSA
• Delete the modified version of the Hierarchy
• Reload the data

Implement SAP Note 1762200

Execute RS_PSA_PART_HIGH_VALUE_CHECK in repair mode

When performing an F4 (lookup) on Plant in BEx Analyser, the following error is displayed:

• Could not generate the data object; the type does not exist
• An exception with the type CX_SY_CREATE_DATA_ERROR
  occurred
• Brain 670

Program error in class SAPMSSY1 method :
UNCAUGHT_EXCEPTION

Metadata repository graphical display not available

• Complete solution is outstanding.
• Implement OSS note: 1706675???

This note was implemented but did not resolve the issues, and also produce new errors. Need a more extensive analysis, correction and test.