Further notes and activities in NW 7.5 system for custom code check

So this week we had to implement note 2241080 in the NW 7.5 system and execute report  SYCM_UPLOAD_SIMPLIFIC_INFO in SE38 to implement the ZIP file downloaded from the note. 

This is part of the activities in generating the custom code reports.

Interesting times ahead............:-)

Interesting session for custom code inspection for HANA prerequisites

Had an interesting session this morning , during the custom code inspection that requires scheduling a couple of background jobs (from a NW7.5 system) to collect the data in the source system which will be converted to HANA.

Its not clear to me why the reports have to be executed from a NW7.5 system and not directly on the source system . So put in mind you need to have a 7.5 system in your landscape during a HANA upgrade/conversion project! (with RFC's to the source systems).

Some analysis reports used

/SDF/UPL_CONTROL (run in se38)
/n/SDF/CD_CCA   (transaction) 

Notes
Implement note 2011106 ,2485231 & 2270689
Details on additional notes in SAP notes 2436688 and 2364916

In source system
Execute ABAP program RS_ABAP_INIT_ANALYSIS

in NW 7.52 system
transaction SCI create
FUNCTIONAL_DB (later FUNCTIONAL_DB_ADDITION) and schedule in background
FUNCTIONAL_DB
generated CI check using program SYCM_CREATE_CI_CHECK_VARIANT) and schedule in background.

I have a detailed document for this procedure .....email if interested

CHECK_DUPRECS_IN_TAB and MESSAGE TYPE X dump in ST22

We faced an issue which just developed one Monday from nowhere , suddenly users in the Finance department could not post loans in certain company codes.

The solution as given by SAP was

Note 1977680 will resolve this issue.

But this note leads to a follow up issue, which is corrected by note 2109893.

Please apply note 1977680 and afterwards note 2109893 including execution of correction report.

HANA migration Transactions/Tables/Programs for Pre-Check

As I prepare for the migration to SAP HANA from ECC6 on AIX , i would like to share some key activities and steps done so far.

Two key notes to implement in the source system are NOTE

0002270689 Remote Analysis (for source system) : Manual Steps are required)

0002190065 ATC/CI: Remote Code Analysis - Object Provider Stub
Update sapnote 2186164 on Solman
SAP Readines check, execution of sapnote 2290622

Other Activities include. 

Activity	T.Code / Table / Program	Pre-Requisite Notes	Output / Result
Consistency Check for AA	RASFIN_MIGR_PRECHECK	2333236 or 1939592 & 1958020
Customizing Pre-Check	FINS_MIG_PRECHECK_CUST_SETTNGS	2129306 & 2240666
GL – AA Reconciliation	RAABST02
GL Ledger Comparison	SAPF190 / TFC_COMPARE_VZ
Compare G/L Accounts in FI with Profit Center Accounting	RCOPCA44
FI-MM Reconciliation	RM07MBST / ABST2
FI-MM Reconciliation	RM07MMFI
Compares the totals records of any two ledgers	RGUCOMP4
GL Vs. New GL	GLT0 / FAGLFLEXT / FAGLFLEXA
FI-AA	ASKB AFAR
Classic GL Vs. New GL	Table - FAGL_ACTIVEC If Transactions viz., FB01L, FAGLL03, FAGLB03 are available in system		Field FAGL_GLFLEX_ACTIVE if active/checked then customer is on New GL
Classic AA Vs. New AA	SFW5 - FIN_AA_PARALLEL_VAL		If the Business Function FIN_AA_PARALLEL_VAL is active then NEW AA is active

Headache from Hell due to failed JDBC installation using JSPM

Last couple of days were tough .. trying to install sql drivers in SAP PI 7.3 system. Started off using JSPM which had worked in the DEV and QA system but was failing in production why? you will get to know in a bit :-) .

So JSPM indicates successful deployment of the com.sap.aii.lib.sda (after a tedious preparation of the file using winzip ref to this good link https://archive.sap.com/kmuuid2/8000cffc-6b92-2d10-3493-f2ac1399242f/Deploying%20JDBC%20Drivers%20in%20PI%207.1x%20Systems ) but when you check the logs there is an error! indicating an issue with port 50004.

This led to numerous parameter changes i.e. checking the port configuration in config tool, adding parameters in the default profile , checking if SAP processes are running on that port . Some of the useful information came from the following commands , notes and urls

sapcontrol -nr 00 -function GetAccessPointList

./STARTUP confighostagent <SID>

http://www.sapbasis1solution.com/HOW_To_Launch_NEW_SUM_SP_14_15_16_17_Upgrade.htm

set in profile parameter icm/server_port_1 = PORT=5$(SAPSYSTEM)04,PROT=P4

We also had to define *.* to port 50004 in hosts file as the server had a virtual host name since it was previously a cluster set up.