In continuation from Invoke Synchronous RFC in ECC using NW BPM 7.40 – Part1 http://scn.sap.com/docs/DOC-70160)
Assign administrator to the pool for BAPIBPM
Click on the Pool in BAPIBPM and select “Administrators” tab. click choose.
Make sure that the user name which you select as administrator should have the following two roles assigned to it.
- Create a role “ZSPML_READ_ROLE” in Identify management in NWA.
- Assign this role to the user which you want to use as an administrator for the BAPIBPM
Complete snapshot of the BAPIBPM
Build and Deploy the Process Development Component
Right click on the development component and select deploy. This will build and deploy the process component in the Process Server.
You can view the deploy log from the “Deploy View Console” by navigating to Window –> Show View –> Deploy view console.
The status of the deployment should be successful. For any errors, resolve and re-deploy the component.
Assign Provider system to the Process Component
Go to NWA –> SOA –> Application and Scenario Communication –> Application Communication
Select the Process Development Component soa/sg.
Click on “Consumed Service Groups” and in the “Provider System” column, select “XXX_ECC” which is the provider ECC system which we have configured earlier in (Part1).
Start and Test the BAPIBPM Process
Go to NWA –> Configuration –> Processes and Tasks –> Process Repository
Select the BAPIBPM process and start the process.
Once you start the process, you will be taken to the test page of the BPM process startup.
Click on “Add Component”. Input the following values.
IP_CARRID = AA
IP_CONNID = 888
Click on Start Process.
You will see a message that Process BAPIBPM started with Process Instance ID xxxxxxx”. Click on details. This will take you to “Manage Processes: Process Instances” page.
Click on Context data tab and select DO_BPI_Req. The data values which you have input above should be visible as shown below.
Now, select DO_BPI_Res from the “Context data” to verify that the BPM has successfully received the response from the RFC YBAPI_PITEST in ECC.
The status of the process is set as “OK Completed”.
This ensures successful implementation of NW BPM calling synchronous RFC in ECC.