By using this website, you agree to our Terms of Use (click here)
Good morning. I've been watching the forums for awhile, but I think this is my first real question to the community. Thanks for all you do!
I have a client who needs to generate recurring sales orders to fulfill a quarterly magazine subscription. In an attempt at creating the most streamlined account setup workflow, I have proposed this solution:
1) Create Customer Template for Magazine Style (4 to chose from)
2) Store Subscription details in the Customer Attributes with details
Then trigger automated Sales Order Generation based off of Customer Attributes. However, this last part in the process has proven to be above my head.
My general concept was to create a GI that would pull customers that match this profile, then generate a sales order from 1 of 4 templates, using 1 variable from the Customer Attribute (qty of magazine line items per order).
Here is a screen shot of my attributes setup.
Build 19.205.0023
Any ideas on how to make this happen or another better idea that is more simple?
Do you have a Business Event that consumes the GI and passes the data to an Import Scenario?
Hi David,
I have done something similar that e-mails our clients a template on upcoming Managed Services invoicing for the month. As Tim said above, it requires three components: 1. The Generic Inquiry (GI) to get the data together, 2. the Business Event (BE) to trigger the e-mails and, 3. the Notification Template (NT) that the BE will use to send the information out.
Here is an example of a Customer with attributes set, the GI that picks is up and the BE and NT to send the e-mail. I also recommend adding in the NoteID from the Customer table, so you can write the Activity back to the Customer record.
Customer attributes:
Generic Inquiry setup:
This Condition ensures it only pulls out Customers where a Managed Services type has been chosen.
As a single Customer can have multiple Managed Services, we need to group them.
The results we want from the GI.
And Finally the results. This is basically the Customer information and all of the Attributes for that customer brought together in a single record line.
This set of data will now be piped through the BE, which is run on a schedule. Of note here are the BE is "Trigger by Schedule" and the Screen ID is the Generic Inquiry referenced earlier. Obviously we need the Notification Template to be able to link it, but I usually create the BE first, then go link it after it is created.
And finally the actual notification template, which is what the customer will see, based on the information provided by the GI. Fields of note here are highlighted. Obviously there is LOT that can be done with formatting. I eventually want to changes to a table, but just need to get the information going out.
The linked schedule. Again, this can be linked either from the BE to the NT, or from the NT to the BE.
Hopefully that gives you a bit of an idea on how you can use Attributes to produce schedule notifications to Customers, based on those attribute values.
Cheers!
@stewart-williams This is very helpful and is similar to what I have prototyped.
Originally I was going to do attributes that will be pulled by the GI into an Import Scenario that creates the Sales Orders. There were 2 major issues with this concept:
- There may be multiple subscriptions and there is no key value pair for identifying which qty of product goes with which subscription
- There was no way to identify which subscription issues were already processed
So, I've added a piece to the puzzle. The Attributes will be used as original planned for rapidly processing new customer orders and giving customer service a streamline method of subscription setup.
The initial automation will generate a Quote per subscription. The quote will have a line item for each of the magazines that is supposed to be delivered, with a delivery date.
In essence, this will work similar to a blanket Sales Order, but on any version of Acumatica.
A bonus benefit of this new setup is that they can easily modify or extend someone's subscription without having to regenerate a contract.
The project is not official yet, but it has been a good learning process.