Process Flow for Customer Order Creation

  1. The RPA verifies the Type (Email or Folder) user parameter.
  2. The required directories are created in the path specified in the ProjectData_folderpath.
  3. The email account is accessed based on the value specified in the emailaccount.
  4. Search for the required emailfolder and download the unread PDF or email.
    Note: 
    • You must provide the email account details.
    • The emails are retrieved based on the value specified in the numberOfEmails field.
  5. Access the Purchase Order files based on the value specified in the Type.
  6. The contents of the file are extracted using the document processor (IDP and GENAI).
    Note: The excel files are extracted:
    • If the files are available in .xlsx format.
    • If the files are available in .csv format and the sheet name is Order Form.
  7. The RPA verifies if the file is a purchase order or a non-purchase order file. If the file is not a purchase order, the record is displayed in the Failure tab of the Review Center and the customer order is not created.
  8. If the file contains multiple purchase orders, the RPA splits the file into multiple purchase orders. Every purchase order is processed as a new input document.
  9. The RPA processes the purchase order only if the purchase order is available in a single page. If the purchase order is available in multiple pages of the file, the RPA does not process the purchase order, the record is displayed in the Failure tab of the Review Center and the customer order is not created.
  10. The RPA verifies if a Customer Order is already available for the Purchase Order. If the customer order already exists for the purchase order, the record is displayed in the Failure tab of the Review Center and a new customer order is not created.
  11. The price of the items available in the purchase order is verified with the price specified in the application. If the price of the item does not match with the price specified in the application, the record is displayed in the Needs Action tab of the Review Center and a new customer order is not created.
  12. The extracted purchase order is classified into Blanket or Regular purchase order.
  13. If mandatory values such as Customer, Item, or PO Number are missing, the record is displayed in the Missing Information tab of the Review Center and a new customer order is not created.
  14. The downloaded attachments are stored in the IDM.
  15. After the Customer Order document is processed, a notification is sent to the user defined in the userIdentifier.