Yes, it is possible to link the Project Group from the Project screen to the Approval Mapping for invoices and memos, but it will require a bit of customization to extend Acumatica's built-in approval process.

Acumatica's approval workflows are generally designed to be flexible and customizable. However, the out-of-the-box approval mapping is typically based on standard fields such as attributes or specific conditions related to the document type. Since Project Group isn't directly available for approval mapping by default, you'll need to make some modifications.

Here’s how you can approach it:

1. Customizing Approval Mapping

To link the Project Group field to the approval workflow, follow these steps:

a. Create a Custom Field in the Approval Map Conditions:

• You can create a custom field in the Approval Map conditions that allows you to select the Project Group from the project.
• This custom field will allow you to select and apply the Project Group in the approval conditions for invoices and memos.

b. Link Project Group to the Document:

• Ensure that the Project Group is included in the Invoice and Memo records. This might require modifying the DAC (Data Access Class) for AR or AP invoices/memos to pull in the associated Project Group from the project.
• You may need to write custom code in the graph extension of the invoice/memo screen to pull the Project Group from the linked project and store it in a custom field within the invoice/memo.

c. Modify Approval Workflow:

• Modify the Approval Workflow to include a condition that checks the custom Project Group field in invoices and memos.
• Use the Conditions tab of the Approval Mapping screen to add a condition that triggers approvals when the Project Group matches the desired value.

2. Use Custom Attributes:

If you want to avoid deep customization, an alternative approach could be:

• Add a custom attribute to the project (if you're already using attributes). You can create an attribute that replicates the Project Group functionality and can be used in the Approval Mapping directly.
• This would allow you to manage approvals based on custom attributes, which are easier to work with in approval mapping conditions.

3. Leveraging Existing Fields (if Customization Isn't an Option):

• If customization is limited, consider using Project Type or Attributes as part of the approval mapping process. If you can't directly link Project Group, you might still be able to map based on these other project-level fields.
• You could potentially create a conditional approval step that triggers based on Project Type combined with another attribute that serves as a proxy for the Project Group.

Example Scenario:

Let’s say you have a Project Group called "Annual Projects." You could set up an approval workflow that checks for the Project Group and triggers specific approvals for invoices tied to these projects.

1. Create a Custom Field in the invoice/memo to store the Project Group.
2. Pull in the Project Group from the related project when the invoice/memo is created.
3. Set up an approval map that includes the condition: “When Project Group = ‘Annual Projects’,” trigger approval for specific approvers.

Conclusion:

While linking Project Group directly to the approval workflow isn’t natively supported, it is achievable with customization. By adding a custom field for Project Group and incorporating it into the approval mapping conditions, you can create the specific approval workflow you need. Alternatively, attributes or project types can be used for simpler configurations if customization is not an option.

Thanks!! Will definitely try this approach!