Scenario:

A business Partner(BP) fetched from S4Hana on-premise system. Then BP Tax no will change in BTP App . Then Approver will Approve or Reject. If Approver approved, then BP Tax no will update in backend.

Systems:

In this topic we used below Technologies and Systems.

1. SAP Build Apps
2. SAP Process Automation
3. SAP S4Hana On-Premise as backend

Steps:

1. API from S4HANA system should be exposed to get consumed.

2. Then build a App in BTP.

3. Get the Entity from Backend destination and bind it to Data of the App.

4. Build the App with 2 pages. First page will show the BP Header data in List format.

Second Page with Input field.

5. Create an Action to post the changes using API.

6. Create a Workflow using Business Process Automation in BTP.

In this simple workflow it will be trigger first from APP after Save button. Then it will go to the approver . If Approver approve, update will happen in BP.

7. Deploy the app in SAP Build Work Zone.

Test results:

1. Open the App from SAP Build App preview or SAP Build Work zone. The BP no and Tax Id fetched from backend on the first page.

2. After click on respective line, 2nd page will display. Give the Tax no for update.

3. After Save , Workflow will be trigger.

4. It will shown in the My Inbox App of approvers with updated Tax id.

5. If User approve, Update will be triggered from Workflow. Workflow will be completed.

6. BP will be updated with new Tax no.

This document has been prepared only a summary to showcase the side by side extensibility. There ae some configurations need to be done in both SAP Build Apps, BTP and SAP Build work zone.

The post Implement side-by-side extensibility with SAP Build Apps and SAP Process Automation in BTP onPremise appeared first on ERP Q&A.

Ever since the advent of Launch Wizard, we have been waiting for this feature in Launch Wizard service as we see many customers running their SAP applications on SAP ASE such as SAP NetWeaver, SAP Process Orchestration (PO) and Solution Manager. This new feature will help customer and implementation partners to speed up SAP deployments on SAP ASE database during their implementation projects.

In this blog post, we will walk you through essential steps that are required to deploy SAP application based on SAP ASE database using the automation capabilities of AWS Launch Wizard for SAP.AWS

AWS Launch Wizard for SAP:

AWS Launch Wizard for SAP is a service that helps in deployment of SAP workload based on SAP HANA and SAP ASE database in AWS cloud using a guided wizard-based experience & APIs for programmatic deployments. Users will have to provide inputs related to their SAP workload like SAP application and database versions, landscape settings, deployment details etc. Launch Wizard identifies the appropriate AWS resources to deploy and run your SAP application.

Launch Wizard for SAP not only automates the SAP deployments, but also helps in EC2 instance selection and configuration, resource selections, cost estimation, installation of Data Provider for SAP etc… For the complete list of features refer to Launch Wizard User Guide.

Prerequisites:

Before getting started, ensure that you have the following in place:

• Key Considerations: Current Launch for SAP supports deployment of SAP ASE version 16 SP4 PL4. Also, only single instance deployment is supported as of today.
• AWS Account: Make sure you have an active AWS account with the necessary permissions to access AWS Launch Wizard.
• SAP System: Have an SAP build sheet ready with all the information on SID, instance number and file system layout and so on.
• Launch Wizard Access: Ensure you have access to AWS Launch Wizard and that it’s available in your AWS region and supported by AWS.
• Download SAP packages: We can follow the guide below to download SAP packages and pay special attention to SAP ASE software.
• Upload SAP software to Amazon S3.

Testing Steps:

1. Launching AWS Launch Wizard:

• Log in to the AWS Management Console and navigate to the AWS Launch Wizard service.
  
• Select the SAP workload type.
  
• Define Infrastructure.

2. Network Configuration:

• Define the network architecture for your SAP deployment, including VPC settings, subnet configurations, and security groups.

3. Selecting SAP ASE as the database:

• Select SAP Application Type (we choose Netweaver stack on SAP ASE) and Application (we choose Netweaver ABAP). One can also choose Application as Netweaver Java (single stack) or Solution Manager (dual stack)
  
• Configure SAP system parameters.
  
• Ensure that the selected parameters align with the requirements of your SAP landscape.

• Configure storage settings, specifying the type, size, and configuration of storage volumes for your SAP system and SAP ASE database.
  
• Choose the appropriate Amazon EC2 instance type for your SAP workload, considering performance requirements and resource utilization.

4. Review and Launch:

• Review all the configured settings to ensure accuracy.
  
• Click on the ‘Deploy’ button to initiate the deployment process.

5. Monitor and Validate:

• Monitor the deployment progress through the AWS Launch Wizard console.
  
• Once deployed, validate the SAP system’s functionality and SAP ASE database connection.

Conclusion:

In this blog you have seen how easy it is to deploy SAP workload based on SAP ASE database in AWS cloud. AWS Launch wizard for SAP takes away heavy lifting from project consultants & makes it easy and quick for customers and partners to deploy their SAP workloads. Hence reducing the errors in the deployment cycles and overall reduction in project implementation timelines. Launch Wizard for SAP already supports SAP deployment based on SAP HANA and now with the SAP ASE deployment support, it’s convenient for the customers to use single service to meet the majority of SAP workload deployment needs for their SAP landscape in AWS cloud.

The post Automate SAP Application Provisioning on SAP ASE database with AWS Launch Wizard for SAP appeared first on ERP Q&A.

Enterprise Automation

Integrating, analyzing, and automating end-to-end business processes is critical in today’s digital landscape. To help customers stay ahead of the competition, SAP offers enterprise automation, a solution that combines the value of SAP Integration Suite, SAP Signavio, and SAP Build. Enterprise Automation allow customers to identify, model, integrate and automate processes end to end across heterogeneous landscapes. This helps companies grappling with disconnected processes and ensures they are automating processes that need it the most.

Ecosystem

The enterprise automation solutions from SAP connect to everything in your environment

• 80+ standard adapters: SAP Applications, mail, various protocols (such as Odata), HTTPS, FTP, RFC and more
• 170+ non-SAP connectors: Gmail, Dropbox, Evernote, etc, which are specific to Integration Suite
• Own adapter development with an Adapter Development Kit
• Open connectors (SAP Integration Suite)

SAP commitment to deeper partnerships to serve customers across different tools

• Process Composability with 3rd party automation tools: UiPath, Automation Anywhere, Microsoft
• Customers can continue using existing and familiar automation tools without disruption
• Flexibility and customization with the right tools to cater to specific automation project requirements

Partners contribute actively to our store and pre-built content

• Unified Store & Marketplace for SAP, partners and customers. Includes pre-built industry & LoBcontent, integration packages, and more
• Discover industry-specific content for existing SAP systems, like SAP SuccessFactors, SAP Ariba, SAP S/4HANA, etc
• Content updates delivered by SAP partners with industry expertise and knowledge

Automation Anywhere Integration

This section provides information about setting up the SAP Business Technology Platform account to consume the SAP Build Process Automation Update Opportunity Stage template as well as the Create Lead template.

The templates mentioned above are intended to simplify the integration of automated business processes from SAP with Salesforce data. The Opportunity Update template automates the steps required to change the pipeline stage of any opportunity within Salesforce to which the defined user within the automation has the ability to edit. The Lead Creation template automates the steps required to create a new Lead record within Salesforce, allowing you to pass in all required attributes for the new Lead.

Both of the automations mentioned above follow a similar flow given the actions provided within each and both are intended to be fully customizable to meet the needs of your business and the customizations you may have applied to your own Salesforce instances. As can be seen from the diagram below, a Form is provided within the SBPA template which captures input data to the process. That data is then encapsulated and sent to the target Automation Anywhere Control Room which will will deploy the task automation to complete the work wihtin Salesforce. The outcome of the automation is pulled from the Automaiton Anywhere Control Room and can be viewed in the monitoring output which SBPA provides.

The Actions included in the templates above deploy the following API’s which are published into the SAP Build Store as a part of the template project to make it simple for any developer to quickly configure against your own target systems for execution via SBPA:

Automation Anywhere Authentication V1

• POST – /v1/authentication
• Requires a valid user account into Automation Anywhere Control Room
• Optional: User should be assigned “Generate API-Key” permission if choosing to utilize API Keys over Passwords

Automation Anywhere Bot Execution Orchestrator V3

• GET – /v3/activity/execution/{id}
• POST – /v3/activity/list
• Ensure user has been assigned the “View my activity” permission

Automation Anywhere Bot Deploy V4

• POST – /v4/automations/deploy
• Ensure the user has been granted the following Control Room permissions
• View my bots
• Run my bots
• View Content permission on the folders containing the bots
• Run permission on the folders containing the bots

The user should belong to a role which has access to Bot Runners and optionally is also a consumer of a Device Pool if looking to deploy the automations to the first available device in a pre-configured pool of devices.

Prerequisites

The automation templates for Update Opportunity Stage and Create Lead provide a set of actions that can be incorporated into any SBPA Process Flow and requires the following services to be available to successfully run:

• SAP Build Process Automation to orchestrate the process.
• Salesforce CRM
• Automation Anywhere A360 Control Room on version A.30+

Configuration

To call these process actions, a HTTP destination is required in the SAP BTP account where the SAP Build Process Automation is subscribed.

Update Opportunity Stage and Create Lead templates require SAP Build Process Automation subscription or CPEA contract. Follow the setup and configuration section.

Setup SAP Business Technology Platform Cockpit

Destination Configuration

Configure SAP Build Process Automation HTTP Destination:

Add the following Additional Properties to your destination configuration:

Setup Automation Anywhere Content

Both of the scenarios in this template, Update Opportunity Stage as well as Create Lead, are dependent on Automation Anywhere bots to perform the automations against Salesforce. An exported package of automations has been provided for you and can be downloaded directly from the SAP Build Store listing page from which you deployed the template. Follow the directions below to configure and deploy the Automation Anywhere bots.

1. Download the ZIP file to your local device
2. Log into Automation Anywhere Control Room with a user that has the following permissions:

a. View my bots

b. Import bots

c. Check in permissions to Public folder

3. Navigate to the Automation menu item
4. Select Import located on the top right of the page
5. Click the Browse button to navigate to the folder containing the downloaded ZIP file
6. Leave the password field blank
7. Under Import bot to, select Private Tab
8. Leave the default option selected for “During import if a file already exists”. This option allows you to specify how the system should behave if it encounters a matching file and folder
9. Click the Import bots button located on the top right of the page
10. The import process may take 1-2 minutes to complete. You can refresh the folder listing under your Private tab to check if the artifacts have been successfully generated. You should see the following folder structure created:

• Bots
  • SAP Build Process Automation
    • Create New Lead
      • Config
    • Update Opportunity Stage
      • Config

11. Once the automations have been fully imported, you’ll need to make some updates. Both task automations have been designed to utilize Control Room Credential Vault to read Salesforce login attributes at runtime. See documentation here on setting up Credential Vault lockers and credentials.
12. Once you’ve set up your credentials, you can update the Salesforce Authentication steps in both the Create Salesforce Lead automation and the Update Opportunity Stage automations

13. Both automations have been designed to read re-usable environment values from the Config.xml file located in their respective Config folders. You can open and edit these files directly from within Control Room. Make edits to the values under the appropriate section which indicates where the automations have been deployed to; Development, UAT or Production.

14. Navigate to the Global Values menu item

15. Create a new Global Value called Environment

16. Assign a value to the variable of either Development, UAT or Production, depending on which of these best represents the purpose of the Control Room in your development lifecycle.

17. Update either automation with additional customizations as needed to support your use case or your customizations within your own Salesforce instance. For example, the Create Salesforce Lead automation only utilizes standard Lead fields to create the target Lead record. Add additional input variables and update the Dictionary as required to support your customizations.

18. Check your automation into the Public folder when ready

19. Once your automations have been checked in, open them from Public and make note of the ID contained in the URL.

Eg: /#/bots/repository/public/taskbots/7289/view

The 7289 above is the ID of the automation in the Public folder and this value will be used when deploying the automation from SBPA in the following steps

SAP Build Process Automation

In this section, you’ll find detailed information on the required or optional customizations for components within the Update Opportunity Stage and Create Lead Process Automations.

Update Opportunity Stage

Configure Process

Automation Anywhere is currently planning and developing the required authentication flows to support SAP OAuth within Destinations. As a result, the currently supported authentication method in the Authenticate User action relies on providing a the username as well as either a password or an API Key for the user which will be used to log into the Control Room via API to deploy the automation. Additional input parameters include the Bot ID as well as the Unattended Bot Runner ID which will be used to deploy the bot. Both of these values can be captured from the Automation Anywhere Control Room. These values can be passed in at runtime of the process, leaving only the configuration of the HTTP Destination before running the process.

As the content package is designed to be reusable, you will need to define a Destination which will allow the actions to determine which Control Room end point they need to communicate with for each respective call out. To configure HTTP Destinations in your environment, review the SAP Documentation by clicking here.

*Ignore this step if you already configured an HTTP destination to your Control Room as defined in the pre-requisite configurations above

Configure Forms

While no updates or modifications are required on the Input Form for the Update Opportunity Stage process automation, the form does allow for flexibility in how the Opportunity is located in Salesforce. If choosing to use the Opportunity ID field, ensure that you pass in the Salesforce record ID of the opportunity which can be found in the URL of the opportunity record page.

If you are not able to locate the record ID, you can skip directly to the middle section of the form on which you can instead provide the Account Name as well as the Opportunity Name exactly as they have been defined in Salesforce. Where the automation is able to find a unique match on these values, the opportunity stage update will be performed.

The last required attribute on the form is the pipeline stage name you would like to update the opportunity to. A value must be selected in order to run the process.

Create Lead

Configure Process

Automation Anywhere is currently planning and developing the required authentication flows to support SAP OAuth within Destinations. As a result, the currently supported authentication method in the Authenticate User action relies on providing a the username as well as either a password or an API Key for the user which will be used to log into the Control Room via API to deploy the automation. Additional input parameters include the Bot ID as well as the Unattended Bot Runner ID which will be used to deploy the bot. Both of these values can be captured from the Automation Anywhere Control Room. These values can be passed in at runtime of the process, leaving only the configuration of the HTTP Destination before running the process.

As the content package is designed to be reusable, you will need to define a Destination which will allow the actions to determine which Control Room end point they need to communicate with for each respective call out. To configure HTTP Destinations in your environment, review the SAP Documentation by clicking here.

*Ignore this step if you already configured an HTTP destination to your Control Room as defined in the pre-requisite configurations above

Configure Forms

The Create Lead Input Form does not require any updates or modifications to use. The form has been designed to work with all Salesforce Standard fields for a Lead record, allowing you to pass in a combination of required as well as optional values which will be used to create the new Lead record in Salesforce. The required fields must be provided a value in order to execute the process.

Automation Anywhere SBPA Command Package

Automation Anywhere Command Packages provide a collection of actions that you can configure and use to build automations. To make integration with SAP SBPA even simpler, Automation Anywhere has built a command package that can be downloaded from the Automation Anywhere Bot Store marketplace which provides the following benefits:

• Easy integration between Automation Anywhere A360 and SAP Build Process Automation
• Start processes in SAP Build Process Automation
• Get Process Context
• Get Process Status

The key use cases the command package can help unlock include:

• Start a process in SAP Build Process Automation
• Check the status of a process instance
• Get the process context

The post Enterprise Automation with SAP Build Process Automation and Automation Anywhere appeared first on ERP Q&A.

Scenario:

The scenario is as follows: We have SAP Build Process Automation running on the SAP Business Technology Platform (BTP), while the on-premises systems expose their endpoints. In order to establish the connection, we will configure the Cloud Connector, create a destination, create a Build Actions project, and test it in a Build Business Process.

Let’s dive into the steps required to set up this integration and leverage the power of SAP Build Process Automation in conjunction with the SAP Cloud Connector.

Prerequisite

Before proceeding with the steps outlined in this guide, it is essential to have an instance of the SAP Cloud Connector installed. While it is possible to install the Cloud Connector on a server, for the purposes of this demonstration, we will be using a Windows machine.

Second requirement is a BTP subaccount with a SAP Build Process Automation instance. To this subaccount we will connect the Cloud Connector.

1. Cloud Connector Configuration

The first step is to create a configuration in the Cloud Connector that connects to our subaccount and exposes the HTTP resource. For the purpose of this demonstration, I ran a small Node.js server on my Windows machine that outputs “Hello World”.

To create the configuration, navigate to the admin interface of the Cloud Connector and create a “Cloud to On-Premise” configuration.

In the provided screenshot, you will notice that I have exposed the internal host “localhost” on port 3333 using a virtual host named “internalhost”. This virtual host will be used for making requests from the BTP side. Currently, I have configured an unrestricted access policy, allowing access to all paths. However, in production scenarios, it is recommended to define access policies with more granular control.

Please note that it is crucial to ensure that you have exposed the necessary resources in your configuration. This ensures that the required endpoints are accessible and allows for successful communication between the cloud and on-premises environments.

The type of system in this case is Non-SAP System with the protocol HTTP. Notice – the internalhost is the virtual host that is mapping to the accessible host in the on-premises environment. To verify its reachability, you can utilize the “Check availability of internal host” button. This step is crucial as it helps ensure the correctness of your setup and validates the connectivity between the cloud and on-premises environments.

On the BTP end, we can check the cockpit and the connected Cloud Connectors in the respective menu tab. If you cannot see this tab, you may be missing some roles. In the image, you see my registered Cloud Connector and the backend system internalhost:3333 available.

2. Create Destination

After successfully registering the Cloud Connector, the next step is to create a destination. A destination serves as a means for services to access an API by handling the authentication and networking aspects.

By configuring a destination, you can simplify the process of accessing APIs by abstracting the underlying technical details. The destination takes care of handling authentication, network communication, and other necessary configurations, allowing services to focus on consuming the API and performing business logic without worrying about the underlying implementation.

Creating a destination provides a convenient way to encapsulate the necessary information, such as the API endpoint URL, authentication credentials, and other relevant settings. This abstraction helps streamline the integration process and facilitates secure and reliable communication between your services and the targeted API.

When creating the destination, there are several important details to specify. These include the name of the destination, the URL you want to access, and the type of destination. In this case, we will specify the URL as the virtual host “http://internalhost:3333”. To utilize the Cloud Connector, we set the proxy type to on-premise.

Additionally, when working with Build Process Automation, we require two additional properties to ensure the destination can be accessed from the Build Actions end:

1. sap.processautomation.enabled – Set this property to true.
   
2. sap.applicationdevelopment.actions.enabled – Set this property to true as well.

Once the destination configuration is complete, it is crucial to use the “Check Connection” button to verify that everything is configured correctly and the connection can be established successfully. This step ensures that the destination is functioning as expected and is ready to be utilized in your automation processes.

In the ideal case you get the green checkmark! But there are some common errors we need to discuss:

The “Backend not available” error occurs when the connectivity service is unable to locate the host you are trying to access. This could be due to the host not being exposed in the Cloud Connector configuration or a potential misspelling in the URL. To resolve this issue, it is important to revisit the URL and ensure that you are using the correct virtual host specified in the Cloud Connector configuration. Verify that the URL is accurate and matches the virtual host configuration to establish the necessary connectivity.

The second common issue that may arise is the “Resource not accessible” error. This occurs when the connectivity service successfully locates the backend you intend to connect to, but the specific resource (such as the subpath “/hello”) either does not exist or is not allowed to be accessed based on the rules defined in the configuration. To resolve this, ensure that you have included the correct path in the Cloud Connector’s resource configuration.

3. Create Actions Project

Now, let’s dive into SAP Build Process Automation and create an Actions project. In this case, since my API is not a standard one, I will create a custom API Specification. However, if you are working with a target system like S/4HANA, you can leverage the pre-defined API Specifications available in the SAP Business Accelerator Hub.

To proceed, navigate to “Build an Automated Process” > “Actions” > “Upload API Specification”.

{
  "openapi": "3.0.0",
  "info": {
    "description": "Demonstration Hello World",
    "title": "helloworld",
    "version": "1.0.0"
  },
  "servers": [
    {
      "url": "empty"
    }
  ],
  "paths": {
    "/hello": {
      "get": {
        "summary": "get hello",
        "description": "get a hello world message",
        "operationId": "get.hello",
        "responses": {
          "200": {
            "description": "Successful response",
            "content": {
              "application/json": {
                "schema": {
                  "type": "object",
                  "title": "Message Object",
                  "properties": {
                    "message": {
                      "type": "string"
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}

The provided code snippet represents the API Specification, where I define the necessary details. In this case, the servers section is left empty as the URL will be retrieved from the destination configuration at a later stage. Additionally, I specify the available path as “/hello”.

It’s important to note that the path mentioned in the API specification will be preceded by the destination’s URL. Therefore, in our scenario, the complete URL for the request will be “http://internalhost:3333/hello”.

Another crucial aspect for the functionality within the low-code environment is defining the expected response structure. In this case, the response payload will consist of a plain object with the key “message”. To build and test specifications, you can utilize the website https://editor.swagger.io/. Be aware, that the response structure must match the specification; if, for example, fields are missing, you will be prompted with a schema error.

Once you have finalized the specification, save the file as a .json format and proceed to upload it to the Actions project.

Within the Actions Project, you will be prompted to add the desired actions, which you can proceed to do. Now, let’s move on to testing:

Within the selected Action, navigate to the “Test” tab. Here, you have the option to select the destination that serves as the basis for the request. For this demonstration, I will choose the ON_PREM_HELLO_WORLD destination that I created earlier. Once the test is executed, you will find the response payload displayed at the bottom. In this particular case, the test is successful, and I receive the expected message from my on-premises server.

If you encounter an error during the process, make sure to check the “View API” Section for any response body that might provide insights into the cause of the issue.

In the final step, we need to release and publish the Action to ensure its availability for consumption in an Automation Project. To accomplish this, locate the buttons located at the top right-hand side of the Actions editor. Click on these buttons and ensure that the status indicates “published.”

4. Add Action to Process

Lets create a Build Business Process Project and invoke the Action. Do so by adding a step in the Process on the + symbol.

We add a Action to the Process, configure its Destination field by creating a new Destination Variable we call in this case the same name as our real destination. To prove that we can now also use the data from the API, I created another Form and put its subject to the message variable from the payload. Go through the regular process to release and deploy this project.

In the Build Lobby we need to add this destination before we can also use it finally in the deployment.

Now when executing the start form, the process will trigger the API call and we should recieve a new Form in the Inbox (Can be found in the Build Lobby). We can see that the Result Forms has our message from the On-Premises HTTP Server as subject. Nice!

The post Accessing On-Premises HTTP APIs with SAP Build Process Automation and SAP Cloud Connector appeared first on ERP Q&A.

Why would you want to do this?

Creating a quick “Hello World” project is a great way to check that everything is properly configured with your agent while familiarizing yourself with the process building experience.

Requirements to follow this guide

• SAP Build Process Automation
  
• Desktop Agent

Note: Free tier does come with some limitations, but this project can be created with a free tier account. If you would like to create a free tier account you can follow this guide.

1. Open the SAP Build Lobby and click “Create” to start a new project

2. Select “Build an Automated Process” and then “Task Automation”

3. Name your project “Hello World” and add a description then click “Create” to launch the process builder

4. Select your agent version from the list and click “Confirm”. You should see “Local” as a tag for your version. This helps to ensure that everything you create is compatible with that agent version.

5. Give your automation a name and description then click “Create”

Note: The identifier will be automatically created based on the name you provide

6. Before we add any activities to this automation we will need to capture our web page. To start this capture, click on the Create icon on the left side of the screen, then select “Application”

7. Similar to creating the automation, we will now give the application a name and description then click “Create”

8. Open a new browser window and navigate to a website of your choice, for this example I will use google.com

Note: To capture a page it must be open in a separate window as the active tab

9. Return to your project in SAP Build Process Automation and select your web page from the “Web” section of the application capture tool then click “Next”

10. Select “Manual Capture” then click “Capture”

11. Click “Go to Application”

Now that we have captured the page we will capture the search field as an element

12. Click on the search field on the screenshot to select the element then set the name to “Search Field”

13. The capture tool has automatically selected recognition criteria, but we will enhance this by selecting another tag from the “Available Criteria” section on the right side of the window. Select “aria-label: ‘Search’” to add it to the recognition criteria then click “Declare Element”

14. Click “Save” to save this captured application, then return to the automation we created in step 5 by clicking on its tab within the project

15. Select “Screens” to open the list of captured screens then drag the “Google” screen from the right side list into the center of the automation canvas

16. Click on the screen in the canvas then click “Define Screen Activities”

17. Search for “start web page” on the right side then drag the “Start Web Page” activity from the right side onto the screenshot of your captured page

18. Click on the “Start Web Page” activity and then select “Chrome” as the browser in the list of input parameters

19. Click on the search field element within the screenshot then search for “set”

Note: Selecting an element like this will apply contextual filtering to the list of activities so that you only see relevant activities for that element

20. Drag the “Set Element” activity and drop it on the search field highlighted in green

21. Click on the “Set Element” activity then enter “Hello World” in the “value” field in the list of input parameters

22. Click on the search field element within the screenshot then search for “key”

23. Drag the “Keystroke Element” activity and drop it on the search field highlighted in green

24. Click on the “Keystroke Element” activity and open the expression editor for the command field by clicking the pencil icon next to that input parameter

25. Copy and Paste or type “irpa_core.enums.key.Enter” into the expression editor and click “Save Expression”

26. Click “Save” and we are ready to test! To begin the test, click the Play icon in the top left corner

27. Click “Test” and the project will initialize then run

28. Once the automation runs you will see Chrome open to “google.com” and search for “Hello World”

The post How to create a “Hello World” project in SAP Build Process Automation appeared first on ERP Q&A.

Bot opens the excel file in order to get the data and then Bot is opening SAP system and then it opens VA01 transaction (creation of sales order) for data entry and then bot enters the data into the system from excel and saving data.

This blog post will make your manual work easy and will automatically create sales orders. This is very useful in business purpose.

What BOT is doing:

The Structure of a Sales Order:

• An inquiry from a customer consists of one or more items that contains the quantity of a material or service entered in the order. The quantity in a sales order is further divided into business lines and comprises of various subsets and delivering dates. All the valid conditions on these items are mentioned in item conditions. These conditions for an item can be derived via a full condition and can be valid for the entire sales order.
  
• T-Code − VA01 Create a Sales Order

• A new window will open, then you can enter the below details −
  
• Enter the Order Type, below order types are available. Enter the sales organization, distribution channel and division.

• It will open a new window. Enter the following details −
  
  1. Enter Ship-To-Party, Purchase Order and Date.
     
  2. Enter the Required Delivery Date.
     
  3. Enter the item details.

• After this you can click on the save icon at the top. You will get a confirmation message −

INTEGRATING EXCEL WITH SAP:

First thing is fetching all the data from excel and creating Sales order.

secondly, we create our and IRPA Bot in Cloud studio by capturing screens, creating workflows, generating scripts and defining context variables as per requirement and finally it should look like below :

SAP Intelligent RPA Bot Details:

In this application we are capturing all the screens which all are needed for this automation.

WORKFLOW:

How BOT is fetching data from excel:

In the below workflow from Activity 1 to Activity 14.

Open Excel Instance – Mandatory activity to drop when using MS Excel : opens an instance of MS EXCEL. Once you open an Excel Instance, you can use other MS Excel activities.

Open Workbook – Open a workbook referenced by a workbook path. Once opened, use the Activate workbook activity for further usage.

Activate Worksheet – Set the ACTIVE worksheet of the ACTIVE workbook. Once activated, further operations might be possible such as Get Values or Set Values which require an active workbook defined.

Get Values cell – Return(read) the values of a specified cell range in the ACTIVE worksheet.

Range Definition: You need to define the range of a cell from the excel Like A1, A2 etc.

From Activity 4 to Activity 14 you need to define cell range from the Excel.

Custom Script: In Activity 15 we are using custom script it Inserts a step defined by custom JavaScript Code. We are adding custom script for opening SAP by giving the credentials.

JavaScript Code for defining the Input Parameters:

irpa_core.core.shellexec(‘sapshcut.exe’, ‘-system=’ + System + ‘ -client=’ + Client + ‘ -user=’ + UserName + ‘ -pw=’ + Password);

WAIT: Activity 16 It is used for a given delay (expressed in ms) between two activities for example for example. It can be useful if some User Interface elements cannot be detected or if some User Interface interactions are too fast . By adding wait , the overall automation duration may increase.

From Activity 17 to Activity 19:

In this we are defining the screen activities by capturing all the screens from SAP application .

Maximize Window (GUI Frame): In Activity 17 we are defining maximize a frame window in the background.

Set Element: In Activity 18 Set the value of a User Interface Element

Click: In Activity 19 execute a ‘click’ action on a button.

From Activity 20 to Activity 25:

Wait(Screen): In Activity 20 we are using wait screen wait until a screen is present and then call a callback. If the screen already exists, the callback is called immediately.

From Activity 21 to Activity 24–

We are setting the element of a User Interface Element from the excel by using this expression Step4.returnedValues (From Step 4 we need the data from excel). Same we are doing for other set elements

Activity 25: We are using ‘CLICK’ activity.

Activity 26 to Activity 33:

In Activity 26 we are using Wait(Screen) and then we are Setting elements from Activity 27 to 33 accordingly from the Excel and then we are using click (defined activity in the application) as SAVE.

Activity 35: In this Pop up screen of SAP we are using CLICK as an Activity.

Activity 36: In this pop up screen we are using again CLICK activity to save the document.

Close workbook – In Activity 37 we are using Close Workbook (Closing the active workbook).

Release Excel Instance – In Activity 38 we are using this activity release an instance without closing an application.

The post Sales Order Creation with SAP Intelligent RPA| Integrating SAP with Excel appeared first on ERP Q&A.

The goal is to cover all the steps necessary to consume Actions in a Process, not to proivde a real Process use case.

Create BTP Destination

In the SAP BTP Cockpit, create a destination that will be used in the Action Editor to test the Action and in the Process execution.

Configure Destination for SAP Process Automation

To allow the usage of the BTP destination, you have to add the Destination in SAP Process Automation.

• In the Settings or SAP Process Automation, select Destinations

• Click New Destination

select the Destination from the list and press Add

• The destination is now added to the lst and can be used in SAP Process Automation

Create Action Project

In this sample we will create a simple Action Project for a REST API.
We will not change input/output parameters or customize the action.

Important: You need an Open API specification for your API to create Actions

• For this example, just copy the definition from here to a local text file called ToDoAPI.json and save the file. We will use the file to create the Action Project with one Action.

{ "openapi": "3.0.0",
    "info": {
        "description": "This is a fake API of todo list",
        "title": "fake.todo",
        "version": "1.0.0"
    },
    "servers": [ { "url": "https://jsonplaceholder.typicode.com/" } ],
    "paths": {
        "/todos": {
            "get": {
                "summary": "get list of todos",
                "description": "get list of todos",
                "operationId": "get.todos",
                "responses": {
                    "200": {
                        "description": "Successful response",
                        "content": { 
                            "application/json": {
                                "schema": {
                                    "type": "array",
                                    "items": {
                                        "properties": {
                                            "userId": { "type": "number" },
                                            "id": { "type": "number" },
                                            "title": { "type": "string" },
                                            "completed": { "type": "boolean" }
} } } } } } } } } } }

• In the Lobby of SAP Process Automation, create an Action Project.

• Specify the name ToDo Actions and upload the API spec ToDoAPI.json, click Create

• Select the actions from the list, click Add

• Your Action Project will contain one action

Test an Action

You can test the execution of your action in the Action Editor. Lets test the Action ‘get list of todos’.

• Select ‘get list of todos’ from the list, the action has no input parameters

• Select Tab Output, shows the fields returned when the action is executed

• Select Tab Test, you can see the different options available to test an action.
  Connectivity Host allows you to test with an destination or Manual, you can enter the system details here.

• Select the destination Demo, click Test
  The Response Preview will show the results

Release and Publish to Library

To be able to use the Action in a Process, we have to release and publish the Action Project.

• Click Release

• Provide release information, click Release

• Click Publish to Library

• On Publish Project, click Publish

Consumption in Process

Create Business Process and use an Action

• From the Lobby select Create Process
  
• Enter the Project Name, e.g. Demo Process and select Create
  
• On the Create Process Dialog, enter the Process Name myActionProcess and select Create
  your canvas should look like here

• Select the + to add a step to your process

• Select Browse library, you will see all actions
  here I have used a filter to show only Actions from ToDo Actions project

• Lets use ‘get list of todos’ action, click Add

• As a last step we have to define a Destination variable

This variable will be later used in the Execution to assign a destination created in BTP and configured in SAP Process Automation

• Select Create Destination Variable, set system as Identifier and select Create

• An Environment variable was created and your process should not display an error anymore
  
• Now Save your process

Release and Deploy the Process

To test the action in the process, we will release and deploy the project.

• clik Release

• Enter a Version comment, click Release

• click Deploy

• On the Deploy a project dialog, select the Destination Demo, click Confirm

• The Deploy button gets activated, click Deploy
  
• Your project is deployed and the deployed version is shown

Test the Process which is using the Action

• In the Monitor or SAP Process Automation, select Manage –> Process and Workflow Definitions
  you can use filter myActionProcess

• select the myActionProcess from the list, click Start New Instance

• On the Start New Instance you can specify input parameters, we have no input so we can use {}, click Start New Instance and Close

• The instance will be started
  
• Select Monitor -> Process and Workflow Instances
  
• Reset the Filters to show all instances

• in the Search, enter myActionProcess
  
• Select myActionProcess from the list to show the instance results

The post SAP Process Automation – Your first simple Action Project: End to End appeared first on ERP Q&A.

1. SAP Process Automation
2. SAP Conversational AI
3. SAP WorkZone
4. SAP AI Business Services

Problem:

With the growing demand of investors to understand a company’s performance in non-financial data, a deep understanding of a company’s commercial, ecological and social impacts, caused by routine business operations & endeavors is needed. However, in many developed economies this led to the penetration of several sustainability reporting instruments some being voluntary and some mandatory leading to non-comparable sustainability performance reporting. Also, capital market regulators had less direct information from the listed companies where a materiality assessment is performed, and an audited quantitative measure was shared by the legal entity enabling to create a sustainability index which is comparable across different market segments.

With different corporates at different maturity level in their sustainability journey a common scoring model independent of the company’s current stage in sustainability journey was lacking.

The Securities and Exchange Board of India (SEBI) has enhanced the existing Business Responsibility Report (BRR) to cover the new dimensions around sustainability and this has led to the new reporting namely Business Responsibility and Sustainability Reporting. BRSR would be applicable for top 1000 listed entities by market capitalization in India, the BRSR lite is for the unlisted companies.

In order to have a quantitative measurement the BRSR standard raises several data points which are broadly classified under 9 principles of the National Guidelines on Responsible Business Conduct (NGRBC). Now the challenge lies in the systematic data collection needed under each principle of NGRBC to prepare a final report which can then be fed to the Ministry of Corporate Affairs MCA21 portal for a standard scoring and evaluation.

In this SAP Community challenge, we would like to address the problem of systematic process automation to ensure the new BRSR reporting can be done by existing ESG department in a company with minimal IT support as large part of the quantified measures collected in the BRSR report lies distributed in the disparate IT silos of a company

Solution:

For this community challenge, we have picked a small part of the BRSR reporting covering Section B and Principle 2 and Principle 6 of Section C. The solution covers process automation with simple forms being generated for covering some generic questions that require a human actor input(a ESG Manager for example) and using SAP ERP data and SAP Environment Health, Safety and Emission Management data. The idea is to supplement the process automation in places where the standard SAP processes do not cover the data collection in its core business processes.

Solution Deep Dive:

Persona:

1. Head of Sustainability: Having a dedicated “head” is necessary to ensure there is focus on driving sustainability strategy and advancing the company’s program—it can also signal the company’s commitment. A majority of top global corporations with which BSR works have dedicated sustainability leaders with varying levels and titles, like Chief Sustainability Officer. These people can be the internal and external “face” for sustainability for the company.​

2. Sustainability Teams: Having a core team can help coordinate daily activities and implement companywide initiatives. While a dedicated team is very common, it’s important for it is not siloed, but rather integrated and engaged with business units and functions. 

• ESG Lead part of Sustainability Core team reporting to Head of Sustainability/CSO

3. Sustainability Supporting Structures:  Working groups or committees, which may have a dotted-line reporting relationship to the head of sustainability, can assist integration of strategy and goals by supporting and even substituting sustainability teams. Individuals in these support structures may be the “owners” of priority sustainability topics and are responsible for implementing strategies, tracking performance, and engaging employees. Representatives may come from real estate and facilities, communications, human resources, risk management, supply chain, and other groups.

• ESG Procurement Manager
• ESG Admin & Facility Manager

For this prototype, we have assumed an organizational structure as above where a BRSR report which is sub dived by different sections and principles would require a lot of back and forth collaboration between different departments in the reporting company.

A pain point of data collection also lies in the ownership and responsibility in the company for precise ESG information which is spread across multiple people. Hence this justifies structured process automation to streamline this report preparation.

Process Flow

For this prototype, we have started with Section B where the ESG lead part of the sustainability core team initiates overall management and process disclosure across the 9 principles. Based on the principles which are relevant for the reporting company there are different process steps initiated for the sustainability support structures that are embedded in a different line of business departments in the company. We have shown in the prototype how the below principles related to climate action can be covered with the support of SAP Process Automation and other SAP systems as backends ( SAP ERP, SAP Environment Health Safety and Environment Management, SAP Responsible Design & Production, SAP Product Compliance, SAP Product Footprint Management, etc.)

• Principle 2 – BUSINESSES SHOULD PROVIDE GOODS AND SERVICES IN A MANNER THAT IS SUSTAINABLE AND SAFE
  
• Principle 6 – BUSINESSES SHOULD RESPECT AND MAKE EFFORTS TO PROTECT AND RESTORE THE ENVIRONMENT

Implementation:

1. SAP Conversational AI

Chatbot 3 basic skills.

1. Greetings
   
2. Sustainability
   
3. brsr

When the chatbot is greeted with a greetings message following options are provided for further selection.

As it is a sustainability topic user clicks on the sustainability and the following skills are triggered.

Users choose BRSR reports and respective Business Process forms are triggered which is automated with SAP Process Automation.

2. Integrate SAP Conversational AI and SAP Workzone.

Integrate SAP Conversational AI and SAP Workzone using SAP Jam Collaboration

3. Workzone Configurations.

Open the Chatbot configuration and enter a name.

Register an OAUTH Client

Enable API access

Enable push notification.

3. Microsoft Teams Integration with SAP Work Zone

Microsoft Teams Integration.

Choose External Integrations and Microsoft Teams and download the ZIP.

4. SAP Process Automation.

Create a Business Process as below:

1. Section B form:

2. Determining Working Group

Role collection created in BTP Cockpit

3. BOT would automate the below process of

• Calculating the Electricity Consumption and Fuel Consumption for the entire year with Dox capabilities of SAP AI Business Services
  
• Greenhouse gas emissions are retrieved from S/4 HANA EHSM Module and PFM Module

4. Section C -Principle 6 Form which is auto-filled with values retrieved Form the BOT(read-only fields) and other editable fields.

5. Section C -Principle 6 Approval Form which has to be approved by Sustainability Lead

The post Business Responsibility and Sustainability Reporting(BRSR) enabled by SAP Process Automation and SAP Conversational AI appeared first on ERP Q&A.