3631640 - Removing the /CRYSTAL/ namespace from rise landscape

• Crystal Report Integration was flagged during ATC scan.
• Namespace: /CRYSTAL/
• Warnings related to Crystal Reports code.
• No usage of Crystal Reports functionality.

• SAP BW 7.2
• SAP BW 7.3
• SAP BW 7.4
• SAP BW 7.5
             
• SAP Crystal Reports 2008
• SAP Crystal Reports 2011
• SAP Crystal Reports 2013
• SAP Crystal Reports 2016
• SAP Crystal Reports 2020

1. Run ATC to identify custom code that needs to be adapted to function on RISE.
2. Observe that Crystal Report Integration is flagged.
3. Confirm that the namespace /CRYSTAL/ is present.

• The namespace /CRYSTAL/ was generated by the BW side and is created beforehand if Crystal Reports is installed on the machine/server.

1. There isn't a formal way to uninstall code from the SAP system. Custom code starting with Z can be deleted using SE80, but SAP standard code should not be deleted.
2. The /CRYSTAL/ package belongs to Basis components and SHOULD NOT BE DELETED.
3. If facing upgrade conflicts, import SAP IK transports before upgrading to reduce conflicts caused by missing tables.
4. Safely ignore errors related to /CRYSTAL/ namespace if Crystal functionality is not used.

• 1601518 - Error: '/CRYSTAL/MDX_GET_STREAM_DATA The obligatory parameter "TUPLE" had no value assigned to it'
• 2335385 - "CALL_FUNCTION_CONFLICT_TYPE" error appears in ST22 in BW when executing a report in SAP Crystal Reports

crystal reports, namespace, /CRYSTAL/, ATC scan, upgrade conflicts, SAP IK transports, SE80, Basis components, custom code, SAP standard code, delete package, ignore warnings , KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , Bug Filed