So here is a simple way to communicate between an external system and SAP BW.
The business scenario where we used this:
Our planning application from Cognos is running on SQL Server. Once the publish and the planning process is completed, we need to load budget data to BW.
Currently this is done on a fixed time and can either cause delays in the update or when the publish process isn’t finished causing the load to fail.
The goal is once Cognos is finished publishing the data and ready to be uploaded to BW have it automatically trigger a process chain in BW
Here is the approach that we followed to communicate between Cognos and BW (or any other external application you might have)
On BW side:
– First we need an Event (ZBU_LOAD) in SAP BW. Can be created with T-Code SM64.
– Use this Event now to trigger your process chain that will load the data from your external system.
On your external Application:
– Next we need is to trigger this event. For this we need PsExec that can be download from http://technet.microsoft.com/de-de/sysinternals/bb897553.aspx.
We added this syntax line after the batch file step finished publishing the data. You can put it anywhere in processes on your external system.
\\BWSERVER\sapmnt\sapevt\sapevt.exe ZBU_LOAD =BWSERVER pf=”Default Profile Path in BW”.
The full syntax line then looks like this:
Most likely your SAP basis team need to help you finding the exact path of sapevt.exe and Default profile.
Make sure the user connecting to your BW system has access right to the folder and is able to execute the sapevt.exe!
This will now trigger the load of your process chain via Event. We just need to call this command from external system… And this will trigger process chain in BW system. You can add this command easily in a batch file.