Automated customer creation

After final approval, the workflow automatically creates the customer record in M3. through these , which are predefined services that create and update customer information.

This table shows the Application Programming Interfaces (APIs) used in the process:

Step M3 API Purpose
1 CRS610MI/Add Creates a preliminary customer record using the customer template specified in the Customer_Template variable.
Note: If the Customer_Template variable is empty, the workflow falls back to a manual task assigned to Customer Service to create the preliminary customer in M3. This fallback serves as a safety net when no template is configured.
2 CRS610MI/ChgBasicData Updates basic customer information, such as addresses, contact details, VAT information, and organization numbers.
3 CRS610MI/ChgFinancial Updates financial information when applicable.

Customer creation sub-workflow

After the customer is created in M3, the M3_CustomerCreationWorkflow_Enhancement sub-workflow starts to help you complete the remaining customer setup tasks.

This list describes what happens after the sub-workflow is initiated with the customer number and request details:

  1. Two tasks are assigned and run in parallel so these teams can finish their parts of the setup at the same time:
    • Customer Service

      Members of the M3CustomerCreationCustomerService group can update customer information such as shipping addresses and local exceptions. The task includes a drillback to CRS610/B. User clicks Done or Reject.

    • Accounts Receivable

      Members of the M3CustomerCreationAR group can update financial information such as credit limits, bank details, and invoice addresses. The task includes a drillback to CRS610/J. User clicks Done or Reject.

  2. Review the task results:
    • If both tasks are marked Done:
      • Customer status is updated to 20-Activated in M3.
      • Requester is notified that the customer is activated.
    • If either task is marked Reject:
      • Customer status is updated to 90-Deactivated in M3.
      • Requester is notified that the customer setup request is rejected.