You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
2
+
title: Order Taker Not Auto-Filled When Creating Purchase or Sales Orders
3
+
description: Learn how to troubleshooting issues preventing the orderer or sales orderer field from being automatically populated when creating a purchase or sales order in Microsoft Dynamics 365 Supply Chain Management.
ms.custom: sap:Purchase order procurement and sourcing\Issues with Purchase order or sales order auto-fill
14
+
ms.topic: troubleshooting-problem-resolution
15
+
16
+
#customer intent: As a developer or system administrator, I want to fix an issue with the order taker not being autofilled when creating a purchase or sales order so that the order taker field doesn't need to be entered manually.
14
17
---
15
-
# Order taker not being auto-filled when creating purchase or sales orders
18
+
# Order taker field not autofilled when creating purchase or sales orders
19
+
20
+
When you [create a purchase order](/dynamics365/supply-chain/procurement/tasks/create-purchase-order) (PO) or sales order (SO) in Microsoft Dynamics 365 Supply Chain Management, the *order taker* (referred to as the **Orderer** in a PO and the **Sales orderer** in an SO) might fail to automatically populate when expected to. This article provides guidance for troubleshooting the required configurations to enable autofill.
21
+
22
+
## Symptoms
23
+
24
+
The **Orderer** or **Sales orderer** field is blank when creating a new PO or SO, even though it should be autofilled.
25
+
26
+
## Cause
27
+
28
+
The **Orderer** or **Sales orderer** field are autofilled only if the current user account is associated with a **Party ID** that has the [Worker role](/dynamics365/fin-ops-core/dev-itpro/organization-administration/overview-global-address-book#party-roles) in the current legal entity.
29
+
30
+
> [!NOTE]
31
+
> If a user has multiple **Party IDs**, only the one with the **Worker** role in the current legal entity enables autofill.
32
+
33
+
## Solution
34
+
35
+
To enable autofill, associate the user account with a **Party ID** that has the **Worker** role in the current legal entity. Follow these steps:
36
+
37
+
### Step 1: Confirm the issue
16
38
17
-
## Symptoms
18
-
When creating a purchase order (PO) or sales order (SO), the **Order taker** (or **Sales orderer**) field isn’t automatically populated.
39
+
In the target legal entity, create a new PO or SO and verify that the **Orderer** / **Sales orderer** field isn't autofilled.
19
40
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.
41
+
### Step 2: Check the party record
22
42
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.
43
+
1. Navigate to **Organization administration** > **Global address book**.
44
+
1. Search for and open the relevant person or party record.
45
+
1. In the record, check the **Roles** section (or role-specific pages) to confirm if this **Party ID** has the **Worker** role assigned for the current legal entity.
46
+
1. If the **Worker** role isn't assigned to the **Party ID** proceed to [step 3](#step-3-associate-party-id-with-the-worker-role-if-not-assigned), otherwise skip to [step 4](#step-4-associate-the-user-account-with-the-party-record).
26
47
27
-
## Resolution
28
-
To resolve this issue, associate the user with the PartyID that has the **Worker role** for the current legal entity.
48
+
### Step 3: Associate the Party ID with the Worker role
29
49
30
-
### Steps to fix
50
+
1. Navigate to **Human resources** > **Workers** > **Workers**.
51
+
1. Select **New** to create a worker record.
52
+
1. Enter the hire date and any required details.
31
53
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.
54
+
This step creates or associates the **Party ID** with the **Worker** role in the current legal entity.
34
55
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**.
56
+
### Step 4: Associate the user account with the party record
39
57
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.
58
+
1. Go to **System administration** > **Users** > **Users**.
59
+
1. Open the relevant user account.
60
+
1. In the **Person** (or **Contact**) field, link the user account to the party record that has the **Worker** role for the current legal entity.
61
+
1. If the **Person** field is locked due to a previous association, use the **Maintain versions** option to remove the existing relation. Then assign the correct worker-linked party.
45
62
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.
63
+
### Step 5: Validate the fix
51
64
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.
65
+
1. Save the user record
66
+
1. Create a new PO or SO and validate that the **Orderer** / **Sales orderer** field is autofilled.
55
67
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.
68
+
If the issue persists after confirming the **Worker** role association, try the following:
58
69
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
70
+
1. Check for duplicate **Party IDs** that might be causing conflicts.
71
+
1. Investigate potential customizations or extensions that could override default behavior.
72
+
1. Capture a trace for further analysis if needed. This trace can help identify any underlying issues requiring technical support.
61
73
62
-
## Related links
63
-
-[Global address book overview](/dynamics365/fin-ops-core/dev-itpro/organization-administration/overview-global-address-book)
0 commit comments