Solution: To address these challenges, we implemented Automation Anywhere 360 to automate the lease renewal process. Our Robotic Process Automation (RPA) bot was designed to perform the following steps:

1. YARDI Portal Access: The bot seamlessly logged into the YARDI portal, the platform used for lease management, ensuring efficient access to the required data and functionalities.
2. Lease ID Integration: The bot selected the appropriate submenu in the portal to provide the lease ID for renewal. This ensured accuracy and streamlined the process for each lease.
3. API Integration and Workload Management: Using an API and a workload management tool, the bot integrated the lease ID from the portal into the Automation Anywhere 360 queues. This allowed for efficient workload distribution and management.
4. Data Retrieval: The bot retrieved the tenant codes from the queues in Automation Anywhere 360, corresponding to each lease ID. It then navigated to a different page in the portal to update the relevant data for lease renewal.
5. Portal Updates: Within the portal, the bot entered the necessary data, saved the information, and created a renewal schedule. This automation eliminated manual data entry and reduced errors.
6. Service Portal Interaction: The bot accessed a service portal, filtering the tenant code to determine if the lease was renewed for that specific code. If renewed, the bot clicked “complete”; otherwise, it flagged an exception.
7. Transaction Log and Notifications: The bot saved transaction logs and screenshots in a shared folder, ensuring traceability and accountability. It also sent notifications to the business users, providing them with lease renewal data and highlighting any business exceptions.
8. Daily Automation: Our bot performed this automated task daily, ensuring timely and accurate lease renewals.

Solution: To address these challenges, we implemented Automation Anywhere 360 to automate our client’s CAM invoicing process. Our Robotic Process Automation (RPA) bot was designed to perform the following steps:

1. Farvision Portal Access: The bot seamlessly logged into the Farvision portal, which served as the platform for CAM invoicing, enabling efficient access to essential data and functionalities.
2. Business Unit Selection: The bot extracted a list of business units (BUs) from a master configuration file for which CAM bills needed to be generated, ensuring comprehensive coverage and accuracy.
3. Data Retrieval: The bot automatically downloaded relevant files, such as the booking register and invoice register, for the specified quarter and BU, eliminating the need for manual retrieval and reducing human errors.
4. Excel Macro Utilization: Employing Excel macros, the bot generated a price list file that was uploaded into the Farvision system to create invoices in bulk. This automation eliminated manual calculations, ensuring accurate and efficient invoicing.
5. Bulk Invoice Submission: To handle the significant volume of invoices, the bot divided the price list file into multiple chunks and uploaded them into the Farvision system. The bot then submitted all the invoices in a swift and automated manner, streamlining the overall process.
6. Quality Control and Validation: The bot downloaded invoice PDFs for each unit and prepared a quality control (QC) file, containing detailed invoice information. The QC file was shared with a business user for validation, ensuring accuracy and adherence to business rules.
7. Approval and Notification: Based on the validation status, the bot approved or rejected invoices, sending emails containing approved invoices to respective unit holders. This automated communication facilitated prompt delivery and enhanced customer satisfaction.
8. Automated Quarterly Execution: Our bot performed this automated task at the start of every quarter, ensuring consistent and timely CAM invoicing for the given period.

Solution: To overcome these challenges, we implemented Automation Anywhere 360 in combination with Dot net to automate the bank statement reconciliation process. Our RPA bot was designed to perform the following steps:

1. SFTP Connection: The bot utilized Dot net DLL to securely connect to the SFTP server, ensuring a seamless and controlled data retrieval process.
2. Statement Download: Our bot automatically downloaded MT940 statements from various bank accounts, eliminating the need for manual retrieval and ensuring efficient data collection.
3. Encryption Decryption: The bot decrypted the encrypted bank statements, enabling seamless processing and preparation for reconciliation.
4. Oracle Fusion Upload: Our RPA bot uploaded the decrypted statements into Oracle Fusion, enabling automated reconciliation for all bank statement entries. This integration eliminated the need for manual data entry and reduced the risk of human errors.
5. Transaction Log and Screenshots: The bot generated a transaction log and captured screenshots at relevant steps in the process, providing a comprehensive audit trail for future reference and compliance purposes.
6. Notification and Business Exceptions: Our bot sent a notification to the relevant stakeholders, including the business team, containing the transaction log and any identified business exceptions. This facilitated prompt action and issue resolution.
7. Daily Automation: The bot performed this automated task every day, ensuring the consistent and timely reconciliation of bank statements.

Solution: To address these challenges, we leveraged Automation Anywhere 360 to automate the bank statement download, merge, and cash position report generation processes. Our RPA bot was designed to perform the following steps:

1. Bank Account Access: The bot autonomously accessed each bank account, ensuring secure and controlled access to sensitive financial information.
2. Statement Download: The bot downloaded statements for each account, retrieving the required data for every date.
3. Business Requirement Modifications: Using VB macros, the bot made necessary changes to the downloaded statements as per our business requirements, ensuring data accuracy and consistency.
4. Statement Merge: The bot merged all modified files into a single master statement, simplifying the consolidation process and saving valuable time.
5. CPR Report Generation: Our RPA bot generated Cash Position Reports (CPR) for each bank account in the required format, facilitating comprehensive analysis and decision-making.
6. Iteration and Notification: The bot iterated through the process for all bank accounts mentioned in the Config File, ensuring thorough coverage. It also sent a transaction log and business exceptions notification to the relevant stakeholders, enabling prompt action and issue resolution.
7. Daily Automation: Our bot performed this automated task every day, ensuring consistent and timely delivery of accurate cash position reports.

Solution: To address the challenges faced by our client, we implemented a conversational bot using Kore.ai to automate the process of answering HR-related frequently asked questions (FAQs). Our solution aimed to reduce the number of tickets, provide quick turnaround times for basic questions, and enhance overall employee satisfaction.

Process: The RPA bot executed the following steps to automate the handling of HR-related FAQs:

1. FAQ Document Management: The bot securely saved all the FAQ documents on a cloud platform. This ensured easy access to the knowledge base and facilitated efficient retrieval of relevant information.
2. Natural Language Processing (NLP): Leveraging the NLP capabilities of the conversational bot, the agent was designed to understand queries and questions from employees in natural language, even accommodating slang or informal language.
3. Query Analysis: When an employee posed a question, the virtual agent analyzed the query to determine its nature and intent. It compared the query against the stored FAQ documents to identify the most relevant knowledge article.
4. Knowledge Article Presentation: If the virtual agent found a matching knowledge article, it presented excerpts from the article to the user. The agent also provided a “read more” link for the user to access the complete document and obtain detailed information.
5. Ticket Creation: If the virtual agent couldn’t find a relevant knowledge article, it created an incident ticket on behalf of the user. The ticket was then assigned to the appropriate HR personnel for further investigation and resolution.
6. Reporting and Metrics: The bot generated reports and metrics on a weekly basis, providing insights into the number of queries addressed, as well as the tickets created. These reports helped in monitoring the effectiveness of the virtual agent and identifying areas for improvement.
7. Information Sharing: The bot saved the generated reports and metrics in a shared folder for easy access and reference. It also sent notifications to the relevant stakeholders, including the HR team and business, providing updates on the reports and metrics.
8. Daily Task Execution: The bot performed these automated tasks on a daily basis, ensuring that employees received prompt responses to their queries and that the incident tickets were efficiently managed.

Solution: To address the challenge of validating education claims, we implemented Automation Anywhere 360 to automate the entire process. Our solution aimed to streamline the verification process, reduce manual errors, and enhance the overall user experience.

Process: The RPA bot executed the following steps to automate the verification of education claims PDFs:

1. Oracle Fusion ERP Login: The bot logged into the Oracle Fusion ERP system, gaining access to the necessary modules and functionalities.
2. Pending Requests: The bot retrieved the list of pending education claims requests from the ERP system. It created a transactions file containing the details of these requests and loaded the information into the database.
3. Receipt Download: The bot downloaded the PDF receipts associated with each request from the ERP system. These receipts were obtained from education institutions and submitted by employees for reimbursement.
4. Data Analysis using Chat GPT: The bot utilized Chat GPT, an AI model, to analyze the data extracted from the uploaded receipts. It extracted key details such as the name of the educational institution, the program/course name, and the duration of the program. This analysis helped in verifying the authenticity of the claims.
5. Claim Approval or Rejection: Based on predefined conditions stored in a master configuration file, the bot made decisions regarding claim approval or rejection. If the receipts were deemed valid and met the predefined criteria, the bot approved the claim. Otherwise, it rejected the claim and provided a reason for rejection.
6. Process Completion: The bot repeated the above steps for all pending education claims requests. It saved the final transaction file containing the updated status of each request, along with transaction logs and screenshots, in a shared folder. Additionally, the bot sent a notification to the relevant stakeholders, providing the final transaction file, transaction logs, and any business exceptions that required attention.
7. Daily Execution: The bot performed this automated task daily, ensuring that the verification of education claims PDFs was conducted promptly and efficiently.

Process: The RPA bot executed the following steps to automate the Wholesale Demand Planning process:

1. Filter Selection: The bot picked up a list of filters provided by the planners that needed to match the order quantities. These filters determined the specific items and parameters for the forecast adjustment.
2. Login to Blue Yonder: The bot logged into the Blue Yonder application, providing secure access to the necessary features and functionalities.
3. Unlock Styles: Before adjusting the forecast, the bot applied the specified filters to unlock all the styles in the system. This ensured that the planners had complete flexibility to modify the forecast.
4. Forecast Adjustment: The bot navigated to the reporting screen within Blue Yonder and adjusted the forecast quantities to match the planners’ future order quantities. This step involved updating the quantities based on the provided filters and business requirements.
5. Lock Styles: After completing the forecast adjustment, the bot applied the filters again to lock all the styles. This ensured that the forecast remained accurate and prevented any unintended modifications.
6. Logging and Notification: The bot maintained a transaction log and captured screenshots throughout the process. It saved this information in a shared folder for future reference. Additionally, the bot sent a notification to the relevant stakeholders, including business exceptions or any noteworthy observations during the process.
7. Daily Execution: The bot performed this automated task daily, ensuring that the Match-to-Order process was executed regularly and efficiently.

Solution: To address the challenge of updating comments in SAP, we implemented Automation Anywhere 360 to automate the complete process, providing a more efficient and error-free solution. Our automation solution focused on bulk updating of shipping/general comments, ensuring a streamlined approach to keep records up to date.

Process: The RPA bot performed the following steps to automate the bulk update of shipping/general comments in SAP:

1. Input File Processing: The Account Service Representatives (ASRs) placed the input file containing the comments in a shared folder. The bot retrieved the file and processed it one at a time.
2. Login to SAP and Navigation: The bot logged into the SAP system and navigated to the respective transaction code (Tcode) based on the type of comment (sales order or contract).
3. Search and Comment Determination: The bot searched for the given sales order or contract and determined the comment section within SAP. It identified the comment type and the required comment action (replace or append).
4. Comment Update: Based on the comment action, the bot either replaced or appended the comment in the designated section of the order or contract. It then saved the changes and proceeded to the next order or contract in the input file.
5. SQL Table Update: The bot updated the SQL table with the status of each order or contract after the comment update. This ensured accurate tracking and record-keeping.
6. Processed File Creation: For each input file, the bot created a processed file with the status of each order or contract, providing a comprehensive record of the comment updates.
7. Shared Folder Management: The processed files were stored in a shared folder, allowing easy access and reference for the ASRs.

Solution: To overcome the challenges faced by our client, we implemented Automation Anywhere 360 to automate the process of updating comments and managing traffic routing requests on web/E-commerce portals. Our Robotic Process Automation (RPA) bot was designed to perform the following steps:

1. SAP Login and Data Retrieval: The bot logged into SAP and fetched the load numbers for which shipments needed to be created. It segregated the loads based on the portals they were associated with and inserted the data into an SQL table for further processing.
2. Shipment Details Calculation: The bot calculated the weight, dimensions, and other shipment details required for the routing requests. It accessed different web portals, filled in the shipment forms with the necessary information, and captured a confirmation screenshot after submission.
3. Database Update: The bot updated the status and other relevant information in the database related to each shipment, ensuring accurate tracking and record-keeping.
4. Shared Folder Management: The processed files and screenshots were copied to a shared folder, providing easy access and documentation of the completed tasks.
5. Shipment Confirmation Email: The bot generated and sent a shipment confirmation email to the appropriate stakeholders, providing them with the necessary information and ensuring seamless communication.

Solution: To address these challenges, we implemented Automation Anywhere 360 to automate the complete process of updating sales orders and line items. Our Robotic Process Automation (RPA) bot was designed to perform the following steps:

1. Input File Processing: The RPA bot monitored a shared folder for input files containing sales order revision requests. It processed one file at a time, extracting the order line items and storing them in a SQL database for further processing.
2. SAP Login and Navigation: The bot logged into SAP and navigated to the respective transaction code (Tcode) for sales order revisions.
3. Order Details Retrieval: Using the order number provided in the input file, the bot searched for the specific sales order in SAP and accessed the order details screen.
4. Line Item Modification: The bot identified the requested line item changes, such as quantity reduction, order cancellation, or cancel date modification. It updated the line items in chunks of 100 to optimize efficiency and performance.
5. SQL Transactional Table Update: After making the necessary changes in SAP, the bot updated the status of the line items in a SQL transactional table, ensuring accurate tracking of the revised orders.
6. Repeat for All Line Items: The bot repeated the steps for all line items within the sales order, ensuring comprehensive updates to each individual line item.
7. Processed File Creation: Once all line items were processed, the bot generated a processed file for each input file, indicating the status of the update process.
8. Shared Folder Management: The processed files were saved in a shared folder, providing easy access to the updated sales order data.