How to "restrict" what Branches can be used with Projects - Everything Else

RE: How to "restrict" what Branches can be used with Projects

Tim Rodman — Thu, 24 Sep 2020 02:19:36 +0000

Hi @dawnmms,

You might want to repost this Discussion Topic in the Construction forum on the new official Acumatica Community website:
https://community.acumatica.com/construction-120

Here on AUGForums.com, most of the forums will now focus on reporting, with the exception of general topics in the Everything Else (click here) forum and the AUGForums.com Real Talk Podcast (click here) where we'll continue to focus on real Acumatica customer stories (click here if you'd like to participate).

For more info about how AUGForums.com compares to the new official Acumatica Community, checkout this post:
https://www.augforums.com/augforums-com-vs-the-official-acumatica-community

RE: How to "restrict" what Branches can be used with Projects

dawnmms — Mon, 03 Aug 2020 16:33:20 +0000

Nope...didn't work. LOL! Oh well...I tried.

RE: How to "restrict" what Branches can be used with Projects

dawnmms — Mon, 03 Aug 2020 16:28:53 +0000

@johnymt hmmmm....all the bills are paid thru Branch 100 but expensed to applicable "branches". Depending on what the project is will usually determine what "branch" should be used. I will need to recommend that all bills go thru an approval process before release so that errors can be caught before it is released...Just would be such a cool feature that when putting in the wrong branch, a warning would pop up that it is incompatible with the project selected. I am going to test an idea of perhaps having the project entered first and see if the "Default" branch populates the Branch.

RE: How to "restrict" what Branches can be used with Projects

johnymt — Mon, 03 Aug 2020 00:27:03 +0000

@dawnmms I have somewhat similar situation. There are company A and B. But in my case Company A owns all the projects. So I am thinking of adding an approval workflow that kicks in if the and X >. That way if the user enter a project related bill while in Company B, the bill cannot be released directly. Will this help you?

RE: How to "restrict" what Branches can be used with Projects

dawnmms — Mon, 20 Jul 2020 16:09:09 +0000

@johnymt The answer to your question is "Yes" the AP Clerk has access to both branches. The question I have is "Is there a way to NOTIFY the user entering the bills that the BRANCH is not valid with the "Project" entered" so that we don't have to "clean" up later if inadvertently entered incorrectly. (Generally discovered when we get ready to do month end close and numbers are not matching from the GL TB Detail with the Project Reports.

RE: How to "restrict" what Branches can be used with Projects

dawnmms — Mon, 29 Jun 2020 15:36:23 +0000

Yes.

RE: How to "restrict" what Branches can be used with Projects

johnymt — Mon, 29 Jun 2020 15:19:30 +0000

Does the AP clerk has access to both branches?

How to "restrict" what Branches can be used with Projects

dawnmms — Wed, 20 May 2020 20:23:52 +0000

Is there an ability to restrict or at least warn that the branch entered in whatever type of transaction is NOT consistent with the Default Branch recorded in the Project record? Example: Branch 200 is the Default Branch for Project 1022000 and should always be recorded as a Branch 200 transaction. The AP Clerk enters a bill and records the transaction to Branch 100 Project 1022000, is it possible that either a "warning" or "error" notifies the AP Clerk that the transactions cannot be saved because of issue with the Branch/Project configuration and prompts a correction prior to Release and Posting of transaction. To be applicable across all modules (i.e. Finance, Banking, Time & Billing, Payables, Receivables)