|
| 1 | +--- |
| 2 | +title: Order taker not auto-filled when creating purchase or sales orders |
| 3 | +description: Steps to troubleshoot when the Order taker or Sales orderer field is not automatically populated while creating purchase or sales orders in Microsoft Dynamics 365 Supply Chain Management. |
| 4 | +author: vermayashi |
| 5 | +ms.date: 09/12/2025 |
| 6 | +ms.search.form: PurchTable, PurchTablePart, PurchCreateOrder, SalesTable, SalesCreateOrder |
| 7 | +audience: Application User |
| 8 | +ms.reviewer: kamaybac |
| 9 | +ms.search.region: Global |
| 10 | +ms.author: vermayashi |
| 11 | +ms.search.validFrom: 2021-05-31 |
| 12 | +ms.dyn365.ops.version: 10.0.13 |
| 13 | +ms.custom: sap:Purchase order procurement and sourcing\Issues with order processing |
| 14 | +--- |
| 15 | +# Order taker not being auto-filled when creating purchase or sales orders |
| 16 | + |
| 17 | +## Symptoms |
| 18 | +When creating a purchase order (PO) or sales order (SO), the **Order taker** (or **Sales orderer**) field isn’t automatically populated. |
| 19 | + |
| 20 | +## Cause |
| 21 | +The issue occurs when the user account isn’t associated with a **PartyID** that has the **Worker role** in the current legal entity. |
| 22 | + |
| 23 | +- The system requires a Worker role to automatically populate the **Order taker / Sales orderer** field. |
| 24 | +- If a user has multiple PartyIDs, only the one with the Worker role for the current legal entity enables auto-fill. |
| 25 | +- If no Worker record exists for the person in this legal entity, the auto-fill won’t trigger. |
| 26 | + |
| 27 | +## Resolution |
| 28 | +To resolve this issue, associate the user with the PartyID that has the **Worker role** for the current legal entity. |
| 29 | + |
| 30 | +### Steps to fix |
| 31 | + |
| 32 | +1. **Confirm the issue** |
| 33 | + - In the target legal entity, create a new PO or SO and verify that the **Order taker / Sales orderer** field is blank. |
| 34 | + |
| 35 | +2. **Check the party record** |
| 36 | + - Go to **Organization administration > Global address book**. |
| 37 | + - Search for and open the relevant person/party record. |
| 38 | + - In the record, check the **Roles** (or role-specific pages) to confirm whether this PartyID has the **Worker role assigned for the current legal entity**. |
| 39 | + |
| 40 | +3. **If no Worker role exists** |
| 41 | + - Go to **Human resources > Workers > Workers**. |
| 42 | + - Select **New** to create a worker. |
| 43 | + - Enter the hire date and required details. |
| 44 | + - This action creates/associates the PartyID with the **Worker role** in the current legal entity. |
| 45 | + |
| 46 | +4. **Associate the user account** |
| 47 | + - Go to **System administration > Users > Users**. |
| 48 | + - Open the user account. |
| 49 | + - In the **Person** (or Contact) field, link the user to the party record that has the Worker role for the current legal entity. |
| 50 | + - If the Person field is locked due to an older association, use **Maintain versions** to remove the existing relation, then assign the correct Worker-linked party. |
| 51 | + |
| 52 | +5. **Validate the fix** |
| 53 | + - Save the user record. |
| 54 | + - Create a new PO and SO again. The **Order taker / Sales orderer** field should now be auto-filled correctly. |
| 55 | + |
| 56 | +## More information |
| 57 | +If the issue persists after confirming the Worker role association, check for duplicate PartyIDs, customizations that override defaults, or capture a trace for further support investigation. |
| 58 | + |
| 59 | +## Keywords |
| 60 | +Order taker blank, Sales orderer not auto-filled, Worker role missing, Purchase order, Sales order, Dynamics 365 SCM, PartyID association, User setup, Auto-fill not working |
| 61 | + |
| 62 | +## Related links |
| 63 | +- [Global address book overview](https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/organization-administration/overview-global-address-book) |
| 64 | +- [Manage users](https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/sysadmin/create-new-users) |
0 commit comments