Skip to Content

Continuing from my last blog Caboodle – Part 4 – The BOBJ4 Post Install

Now we have an SAP NetWeaver (NSP) and a BOBJ4 System, I’m going to split the NSP into an ERP System and a BW System.

Having this scenario will “spoof” the two types of systems which BOBJ commonly integrates with, thus broaden the Caboodle environment functionality.

I now consider the NSP Client “001” as the ERP (OLTP) System, and use it to perform a Client “002” copy, which I configure as the BW (OLAP) System.

Follow the steps below, exactly. Do not deviate. It begins a little texty, but soon enters screen shots. It is certainly not exhaustively tested, so I would only recommend this done here.

So, to begin …

Logon to NSP 001 (ERP) with user “bcuser”

RZ10 – Add an Instance Profile Parameter and value

login/no_automatic_user_sapstar = 0

BD54 – Create a new Logical System “NSPCLNT002”

SCC4 – Create the new Client Definition (for lack of a better description). For this I simply copied Client 001, renamed it, and gave it the Logcal System created above – “NSPCLNT002”

SU01 – Create remote access user for the BW System. User name “BW_REMOTE”, User Type “System”, Profile “S_BI-WX_RFC”, and of course, give it a password

Re-start the SAP System for the Instance Profile Parameter to operate

Logon to NSP 002 (BW) with user “sap*” and password “pass”

SCCL – Perform Client Copy using Profile “SAP_ALL” as Source Client. Schedule as background job. 30 mins

Log out

Logon back to (BW) with user “bcuser”

SU01 – Delete unecessary user “BW_REMOTE”

SE16 – Edit table RSADMINA, one and only record “BW”, set field BWMANDT to “002”. This will enable transaction RSA1 – BW Workbench.

SPRO – Create remote access user for the ERP Source System. IMG->SAP NetWeaver->Business Intelligence->Automated Processes->Create User for Background Processes  – “ERP_REMOTE”

SPRO – Tell BW the ERP access User name. IMG->SAP NetWeaver->Business Intelligence-> Links to Other Source Systems-> Connection Between SAP Systems and BI System-> Maintain proposal for users in the source system (ALE communication) – “BW_REMOTE”

SM59 – Create ERP ABAP Connection RFC. Client “001”, User “BW_REMOTE”. Save & test “Remote Logon”. If it looks like nothing happened, all is well, as the “BW_REMOTE” user is a System user. There should not be a log on screen. If there is, then it is likely that the password wrong.

Logon to NSP 001 (ERP) with user “bcuser”

 SM59 – Create BW ABAP Connection RFC. Client “002”, User “ERP_REMOTE”. Save & test “Remote Logon”. If it looks like nothing happened, all is well, as the “ERP_REMOTE” user is a System user. There should not be a log on screen. If there is, then it is likely that the password wrong.

Logon to NSP 002 (BW) with user “bcuser”

WE20 – Delete Logical System (LS) partner “NSPCLNT002”

BDLS – Convert Logical System name (Not 100% sure if this is actually required).

  • Old Logical System Name = “NSPCLNT001”
  • New Logical System Name = “NSPCLNT002”

 

Logon to NSP 001 (ERP) with user “bcuser”

SE37 DO NOT PERFORM THIS STEP IN BW – Remove bad configuration from BW System with Function Module “RSAP_BIW_DISCONNECT”.

  • I_BIW_LOGSYS = NSPCLNT002
  • I_OLTP_LOGSYS = NSPCLNT002
  • I_FORCE_DELETE = X

Performing the Client Copy put an invalid entry in table RSBASIDOC. Table “RSBASIDOC” on the BW System should be empty.

SE37 – Add good configuration with Function Module “RSAP_BIW_CONNECT”.  With the following parameters

  • I_LANGU = EN
  • I_SLOGSYS = NSPCLNT001
  • I_LOGSYS = NSPCLNT002
  • I_STEXT = NSPCLNT002
  • I_BASIC_IDOC = ZSBA001
  • I_TSPREFIX = BA
  • I_PREFIXE = AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
  • I_SAPRL = 702
  • I_RESTORE = X

 

This should have created a valid record in the BW table “RSBASIDOC”

 

Logon to NSP 002 (BW) with user “bcuser”

RSA1 – Enter the BW Workbench, select “Only Activate”

Navigate to Modelling->Source Systems

Should see this

 

Right click the “SAP” entry, then “Restore” from the context menu

 

Supply the appropriate passwords

 

Validate who you are, by login on as an administrator

 

Use user “BCUSER”

 

As the “Source System Connection” has already been configured (done earlier)

 

“Continue”

As the “RFC Destination” already exists (created earlier)

 

“Use”

As the “Connection” cannot be used

 

“Delete”

Around we go again. Log on as an administrator

 

Use user “BCUSER”

 

As the “Source System Connection” has already been configured (done earlier)

 

“Continue”

As the “RFC Destination” already exists (created earlier)

 

“Use”

 

“Only Activate”

Navigate to Tools->Manage Source System

 

Check all

 

Execute

 

Now both Systems are good.

As I said earlier, this process is not supported anywhere, but it is reliable and works.

We can now perform some data extractions from our “ERP” System to the new “BW” System and even configure the BW Publishing functionality.

 Sweet !

Continue on to my next blog, Caboodle – Part 6 – BOBJ4 Client Tools Install

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