After the ECM+ Impact Agent returns an impact summary, use a progressive drill-down conversation to explore the affected documents in detail. The agent keeps the context of the engineering change or PLM staging journal that you are discussing, so you can refine your questions across multiple turns without repeating the change identifier. Use this task to inspect the header and line details of a specific document and to narrow the results to the customers, suppliers, or document types that matter to you.
Prerequisites
You have run an impact analysis for an ECO or a PLM staging journal in the current conversation.
The documents that you want to inspect are linked to the engineering change.
Steps
In the same Copilot chat conversation, ask the agent for details about a specific document. For example, enter "Tell me about sales order SO01256?".
Review the header and line summary that the agent returns. For a sales order, the summary includes the delivery address, requested ship date, customer references, discount, status fields, and each order line with its item, quantity, unit price, delivery type, and warehouse.
To see line-specific details, ask a follow-up question, such as "What are the line-specific details for the first line?". The agent returns general information, intercompany settings, and status fields for that line.
To narrow the results, refine your query in natural language. For example:
"Show only Boeing orders."
"What about suppliers?"
"Show only VIP customer orders."
Continue asking follow-up questions to move between document types, such as purchase orders, production orders, inventory, inventory journals, purchase requisitions, and purchase quotations, while the agent maintains the conversation context.
Results
You gain a clear understanding of each affected document and how it relates to the engineering change.
The agent displays only the documents that the engineering change affects, and it retains the context across the conversation so that you can refine your questions.
Note
The agent maintains context across long, multi-turn conversations, so you can keep refining your questions without losing track of the engineering change or PLM staging journal in discussion.
If the document does not exist or the engineering change does not affect it, the agent returns a message that the document was not found or is not impacted.