This procedure could be useful for the organizations who has requirement of web enabling some of reports or building web application for SAP transactions using BSP but they are still on version 4.6C or less and can not migrate R3 to 4.7 immediatly.
As per this procedure BSP application can be written on saperate WAS server and later when R3 is migrated to 4.7 the BSP application can be migrated to R3 4.7.
Also using this procedure you can enjoy other features of SAP WAS server like SMTP connection instead of SAP Exchange Server can be configured to SAP WAS and will connect to R3 system for process.
Step1: Installing WAS server 6.40: First you have to install a saperate instance of SAP WAS 6.40, which could be simple installation (without any SAP Modules).
Step2: Setup RFC Connection between WAS & R3 System: After finishing the necessary BASIS activities of SAP WAS you have to setup an RFC connection between SAP WAS server and SAP R3 system in transaction SM59.
Step3: SSO – Setup Trusted Relationship Between WAS/R3: For accessing SAP R3 (4.6C) RFCs you need to setup trusted relationship between R3 and WAS severver in which R3 server should be configured as Trusting System and WAS sever as Trusted System.
Once the trusted relationship has been defined between the two systems the user logs into WAS server using BSP can perform his transaction in R3 without any access issue. This is required because in normal RFC connection setup you can supply (hardcode) only one user id and password which leads to executing all R3 BAPI/transactions with that user id.
Step4: Replicating the Users of R3 to SAP WAS: As WAS server will be substitute of SAP R3 4.7 to use BSP and other latest feature till you migrate your R3 to 4.7 all the users in your R3 systems should be replicated in WAS server.
Step5: Replicating R3 Data structure/Table Structure: If your WAS server is not fully R3 Server some of your transaction data structure / table structure will not exists in WAS, you need to migrate them from existing R3 system so that it can be used in your BSP application.
Step6: Writing BSP Application: Now you can write your BSP application using HTMLB to represent the frontend and you can call the FM of R3 system by giving the RFC detination name as its on the same server.
Step7: SSO between SAP Portal / WAS / R3: If you wish to connect your BSP application to EP, you can setup the SSO between EP and WAS server and WAS server & R3 are already setup for trusted relationship which enables the complete SSO for whole landscape. User will not know how many systems are invloved. SAP EP –SSO–> SAP WAS –Trusted Rel–> SAP R3.
Step8: Process after upgrading you SAP R3: In the future when you plan for upgrading your SAP R3 server to 4.7 or higher you will have BSP engine inbuilt into the R3 system. Now you can plan to discontiue your WAS server and load all BSP application directly to the R3 server.
Here you need to check for your destination name for RFC connection because in your BSP application you would have coded the R3 destination name while calling RFM / BAPI, now either you need to parameterize this entry so that you can change it at one place to access the R3 system itself as target system.
Or if you are not able to perform the above step you can try removing the destination name code from BSP pages
Or you can setup the trusted relationship between the R3 server with itself in one RFC destination and you can use the BSP application just by transporting it to new R3 Server.
Platform independent content for Portal: By using the above method you will develop the contents which will not have any impact on your upgrade or migration of systems. The content developed on BSP will have no effect when you migrate your EP5 to EP6 and above process also tells that when you move to R3 4.7 or higher it will have no or negligible effect for transporting the contents.