AI Agent: Order Exception Assistant

Use the Order Exception Assistant to examine the Groovy code in your order management extensions and identify exceptions that your code might be causing on sales orders. It can also guide you on how to fix data that builds up in tables that don't contain transaction data:.

• Improve your Groovy extension code's performance.
• Keep your system optimal. Avoid a buildup of tracking and message data.

Try It

Go to Home > Order Management > Show More > Sales Orders (New), click the dots until you're on the Order Exception Assistant, then click Ask Oracle:

Click Show Exceptions:

Reply with 1:

Examine the summary and suggestions:

The agent can help improve your code. It will:

• Monitor how long your extension runs when you create a sales order and identify the ones that run for more than two seconds.
• Display the 5 sales orders that take the longest to finish when you have a large number of orders.
• Review your code and suggest improvements that you can make.
• Provide a summary of recommended changes and link to the relevant set up page where you can make them.
• Remove an extension that you have fixed from the report.

Examine the recommendations and benefits:

The agent can also help you remove excessive and unnecessary data and improve performance. It can automatically run scheduled processes to delete records that don't contain transaction data or to close orders that aren't closed even though Order Management fulfilled them. As an alternative, it can recommend parameter values for you and you can manually run the scheduled processes yourself. See Delete Records That Don't Contain Transaction Data.

Steps to Enable

1. Make sure you have the ORA_DR_FAI_GENERATIVE_AI_AGENT_SCM_ADMINISTRATOR_DUTY role.
2. Make sure you have the FAI_VIEW_AI_AGENT_WORKFLOW_DATA and
   FAI_MANAGE_AI_AGENT_WORKFLOW_DATA roles so you can access the templates.
3. Go to Home > Setup and Maintenance > Tasks > Search > Manage Administrator Profile Values, then set the Enable VBCS Progressive Web Application User Interface (ORA_HCM_VBCS_PWA_ENABLED) profile to Y at the site level.
4. Go to Home Page > Tools > AI Agent Studio, set the Family to SCM, the Product to Order Management, search for Order Exception Assistant, then click Copy Template on Order Exception Assistant:
   
5. Enter the number 1 for the suffix, then click Continue. We recommend that you use the suffix to indicate versions, such as 1, 2, 3:
   
6. Click . . . > Edit:
   
7. Use the predefined values on the Details tab or modify them to meet your needs:
   
8. Click LLM, then examine the predefined prompt. If necessary, you can modify it, then click Update:
   
9. Click Publish:
   
10. Click Agent Teams, search for and open Order Exception Assistant 1, then verify the status is Published:
    

Add to Guided Journey and Test

1. Go to Home Page > My Client Groups > Show More > ctrl+f, search for, then click Guided Journey.
2. On the Guided Journey page, click Create, set these values, then click Create Draft:

   Attribute	Value
   Name	Order Exception Assistant
   Code	ORDER_EXCEPTION_ASSISTANT
   Allow Access for External Users	Yes

3. Add this task, then click Save > Activate:

   Attribute	Value
   Task Name	Order Exception Assistant
   Task Description	-
   Task Type	Agent
   Agent Type	Workflow Agent
   Workflow Agent	Order Exception Assistant 1

   The Order Management work area will display the Task Name and Task Description on the journey's banner. We recommend that you use headline capitalization so it's consistent with the work area's style.
4. Go to Home Page > Order Management > Show More > Sales Orders (New).
5. Click Settings and Actions > Edit Page in Visual Builder Studio.
6. Set the JourneyCode property to ORDER_EXCEPTION_ASSISTANT, then click Publish.
7. Go to the Order Management work area and test your set up.

Tips And Considerations

• You can also use this agent to help delete records that don't contain transaction data. Just enter Delete Nontransactional Entities from Closed Sales Orders and Fulfillment Lines in the agent's prompt, then follow the instructions. For background, see Delete Records That Don't Contain Transaction Data.
• The agent can identify problems with your extension and make recommendations, but these suggestions are only guidelines. You must review and analyze your Groovy code before you make changes.
• You must test your changes in a test environment and make sure your extension works correctly before you make them in your production environment.
• You can't change a sales order after the Update or Close Sales Orders scheduled process closes it. Make sure you set the parameters for that process so it doesn't close sales orders that you might need to change. See Update or Close Sales Orders.

Key Resources

• Overview of Creating Order Management Extensions

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

Administrator:

• Order Manager or Order Administrator duty role.
• Manage Orchestration Process Definition (DOO_MANAGE_ORCHESTRATION_PROCESS_DEFINITION_PRIV)
• Plan Orchestration Processes (DOO_PLAN_ORCHESTRATION_PROCESSES_PRIV)
• Manage Orchestration Order Modification (DOO_MANAGE_ORCHESTRATION_ORDER_MODIFICATION_PRIV)
• FOM_MANAGE_ORDER_MANAGEMENT_EXTENSIONS

Person using the agent in the Order Management work area:

• View Orders (FOM_VIEW_ORDERS_PRIV)
• ORA_DOO_ORDER_MANAGER_JOB or ORA_DOO_ORCHESTRATION_ORDER_MANAGEMENT_DUTY or ORA_DOO_ORDER_ADMINISTRATOR_JOB 

These privileges were available before this update.