Process flow

This sequence outlines the process flow when you run the solution:
  1. Emails with supplier purchase agreements in attachments are received in a specified email account folder. Alternatively, the supplier purchase agreements are also received in a specified local folder.
    Note: You can configure the RPA bot to run in attended mode. The mailbox of the specified email account is monitored by the RPA bot.
  2. In RPA, these key values are extracted from the document using Optical Character Recognition in IDP:
    • Supplier name
    • Supplier code
    • Supplier address
    • Item numbers
    • Alias numbers
    • New prices
    • Agreement date
    • Valid from date
    • Currency and units
  3. RPA uses AI and ML to identify the Active Supplier Code in M3 through the supplier details extracted from the document.
  4. RPA identifies the item codes from the retrieved Item and Alias codes in the document.
  5. RPA uses a custom API (CMS100MI) to validate if an active supplier purchase agreement exists in M3 with the extracted supplier and item combination.
    RPA uses these M3 APIs to handle supplier purchase agreements and item pricing lines based on agreement status:
    • If an active agreement does not exist, RPA uses PPS100MI.AddAgrHead to create the agreement header and PPS100MI.AddAgrLine to add item pricing lines.
    • If an active agreement exists, RPA uses PPS100MI.UpddAgrLine to set the Valid To date of the agreement to one day before the new agreement date. RPA uses PPS100MI.AddAgrLine to add item pricing lines as a new line under the same active agreement number.
  6. RPA uploads the document to IDM and sends a notification to a designated user or group.
  7. After the RPA process is completed, you can review and approve the created agreement in PPS100.