Sage 100

I have a customer trying to better manage sales order backorders.

Their business problem: 

Customer orders item ABC which is not in stock. They assign a promise date on the sales order line of 12/31/2021
There is a purchase order is out for item ABC and shows we expect it 12/31/2021

Subsequently the purchase order for that item ABC changes and we now expect the item to arrive 3/15/2022

1. We want to update the customer via email with the new expected arrival date 
2. We want to change the sales order line to change the promise date to the new date we expect the PO to arrive

Unless I've missed something - there doesn't seem to be an easy way to update the sales order line promise date based on a change to the purchase order required date.

It seems like a workflow similar to this should work: 

If the PO req date changes - search for all open SO ( open qty and backorder qty ) with promise dates for that item and change all the promise dates to the new PO req data changes ( plus a two week cushion )

And then fire off an alert to the customer to say that the promise date on the SO line has changed


Has anyone tackled this in a different way? 
I feel like a lot of this could be done by reports however the customer also wants to notify customers of an updated sales order promise date

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------

This prior thread is similar to what I think an ultimate solution might look like. 

Either VI or a script to update the SO Line promise date with the new PO line required date

Caveats would be needed that if there are multiple POs referencing the same item with different required dates that this doesn't work cleanly

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------

A simple-minded approach would be a weekly report flagging SOs tied to POs that have expected receipt dates beyond the SO Promise dates. The company then manually handles the consequences. 

As you point out, some sort of scripting could probably get it most of the way there. This approach also has other drawbacks, including maintenance as the company's needs change.

Another approach is to explore a workflow tool. This could be KnowlegeSync; I did a similar project way back when, but I'm now bummed by their apparent lack of responsiveness. A more promising tool is Fisher Technology's BPA Platform (fka Taskcentre). Their business focus these days is ecomm integrating with ERP, but they do have Sage 100 connectors, and this sort of problem is right down their alley. Once a customer solves a problem like this, they are likely to think of other tasks/problems to use the tool on.

This can be structured as a Value Priced project in two stages. The first is to help them decide which approach is best for them, as all 3 have pros and cons. The second would be to implement the chosen approach for this problem.

------------------------------
Jerry Norman
At-Large BOD Member, 90 Minds
Smartbridge Partners
512.419.1444 x112
------------------------------

Original Message:
Sent: 12-07-2021 11:12
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

This prior thread is similar to what I think an ultimate solution might look like.

Either VI or a script to update the SO Line promise date with the new PO line required date

Caveats would be needed that if there are multiple POs referencing the same item with different required dates that this doesn't work cleanly

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------

Thanks. This is looking like it's beyond the capabilities of Sage 100.
I checked DSD and they don't seem to have anything 

Just to close the loop on this for future searchers - what I'm planning to do is suggesting the customer walk before they run. 

First, create some type of report that shows this info and see whether having a report is enough.
Then, if the report isn't working I will take what I've learned from reporting and propose a software solution - this probably would be a scripting project however I'm not sure if scripting could totally resolve the issue. It might also be a VI job that runs overnight to update the promise dates. I have a healthy skepticism that updating the promise dates is the way to go because in some cases a customer may have specifically requested a LATER promise date and if we'd just overwriting whatever is in promise date we are now changing the intent of whoever took the order and manually created a future promise date ( customer will always say that will ' never ' happen until it does and they call you 36 months later when neither of you can remember the original design specification of what they asked...

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------

Original Message:
Sent: 12-07-2021 12:33
From: Jerry Norman
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

A simple-minded approach would be a weekly report flagging SOs tied to POs that have expected receipt dates beyond the SO Promise dates. The company then manually handles the consequences.

As you point out, some sort of scripting could probably get it most of the way there. This approach also has other drawbacks, including maintenance as the company's needs change.

Another approach is to explore a workflow tool. This could be KnowlegeSync; I did a similar project way back when, but I'm now bummed by their apparent lack of responsiveness. A more promising tool is Fisher Technology's BPA Platform (fka Taskcentre). Their business focus these days is ecomm integrating with ERP, but they do have Sage 100 connectors, and this sort of problem is right down their alley. Once a customer solves a problem like this, they are likely to think of other tasks/problems to use the tool on.

This can be structured as a Value Priced project in two stages. The first is to help them decide which approach is best for them, as all 3 have pros and cons. The second would be to implement the chosen approach for this problem.

------------------------------
Jerry Norman
At-Large BOD Member, 90 Minds
Smartbridge Partners
512.419.1444 x112
------------------------------


Original Message:
Sent: 12-07-2021 11:12
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

This prior thread is similar to what I think an ultimate solution might look like.

Either VI or a script to update the SO Line promise date with the new PO line required date

Caveats would be needed that if there are multiple POs referencing the same item with different required dates that this doesn't work cleanly

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990

I was thinking of something like this:

• Automated report to show them when there are date issues.
• Button script in SO Entry to update Promise Dates for that order based on the current PO data (with whatever conditional logic you want...).
• Then they can resend the updated SO normally.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 12-08-2021 10:23
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Thanks. This is looking like it's beyond the capabilities of Sage 100.
I checked DSD and they don't seem to have anything

Just to close the loop on this for future searchers - what I'm planning to do is suggesting the customer walk before they run.

First, create some type of report that shows this info and see whether having a report is enough.
Then, if the report isn't working I will take what I've learned from reporting and propose a software solution - this probably would be a scripting project however I'm not sure if scripting could totally resolve the issue. It might also be a VI job that runs overnight to update the promise dates. I have a healthy skepticism that updating the promise dates is the way to go because in some cases a customer may have specifically requested a LATER promise date and if we'd just overwriting whatever is in promise date we are now changing the intent of whoever took the order and manually created a future promise date ( customer will always say that will ' never ' happen until it does and they call you 36 months later when neither of you can remember the original design specification of what they asked...

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------


Original Message:
Sent: 12-07-2021 12:33
From: Jerry Norman
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

A simple-minded approach would be a weekly report flagging SOs tied to POs that have expected receipt dates beyond the SO Promise dates. The company then manually handles the consequences.

As you point out, some sort of scripting could probably get it most of the way there. This approach also has other drawbacks, including maintenance as the company's needs change.

Another approach is to explore a workflow tool. This could be KnowlegeSync; I did a similar project way back when, but I'm now bummed by their apparent lack of responsiveness. A more promising tool is Fisher Technology's BPA Platform (fka Taskcentre). Their business focus these days is ecomm integrating with ERP, but they do have Sage 100 connectors, and this sort of problem is right down their alley. Once a customer solves a problem like this, they are likely to think of other tasks/problems to use the tool on.

This can be structured as a Value Priced project in two stages. The first is to help them decide which approach is best for them, as all 3 have pros and cons. The second would be to implement the chosen approach for this problem.

------------------------------
Jerry Norman
At-Large BOD Member, 90 Minds
Smartbridge Partners
512.419.1444 x112


Original Message:
Sent: 12-07-2021 11:12
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

This prior thread is similar to what I think an ultimate solution might look like.

Either VI or a script to update the SO Line promise date with the new PO line required date

Caveats would be needed that if there are multiple POs referencing the same item with different required dates that this doesn't work cleanly

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990

I like this idea. 
It's sort of a hybrid and requires someone to approve the updated order being sent by email which I think at least initially is a good idea so that customers aren't getting bombarded with emails if a PO date changes frequently.

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------

Original Message:
Sent: 12-08-2021 10:29
From: Kevin Moyes
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

I was thinking of something like this:

• Automated report to show them when there are date issues.
• Button script in SO Entry to update Promise Dates for that order based on the current PO data (with whatever conditional logic you want...).
• Then they can resend the updated SO normally.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 12-08-2021 10:23
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Thanks. This is looking like it's beyond the capabilities of Sage 100.
I checked DSD and they don't seem to have anything

Just to close the loop on this for future searchers - what I'm planning to do is suggesting the customer walk before they run.

First, create some type of report that shows this info and see whether having a report is enough.
Then, if the report isn't working I will take what I've learned from reporting and propose a software solution - this probably would be a scripting project however I'm not sure if scripting could totally resolve the issue. It might also be a VI job that runs overnight to update the promise dates. I have a healthy skepticism that updating the promise dates is the way to go because in some cases a customer may have specifically requested a LATER promise date and if we'd just overwriting whatever is in promise date we are now changing the intent of whoever took the order and manually created a future promise date ( customer will always say that will ' never ' happen until it does and they call you 36 months later when neither of you can remember the original design specification of what they asked...

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990


Original Message:
Sent: 12-07-2021 12:33
From: Jerry Norman
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

A simple-minded approach would be a weekly report flagging SOs tied to POs that have expected receipt dates beyond the SO Promise dates. The company then manually handles the consequences.

As you point out, some sort of scripting could probably get it most of the way there. This approach also has other drawbacks, including maintenance as the company's needs change.

Another approach is to explore a workflow tool. This could be KnowlegeSync; I did a similar project way back when, but I'm now bummed by their apparent lack of responsiveness. A more promising tool is Fisher Technology's BPA Platform (fka Taskcentre). Their business focus these days is ecomm integrating with ERP, but they do have Sage 100 connectors, and this sort of problem is right down their alley. Once a customer solves a problem like this, they are likely to think of other tasks/problems to use the tool on.

This can be structured as a Value Priced project in two stages. The first is to help them decide which approach is best for them, as all 3 have pros and cons. The second would be to implement the chosen approach for this problem.

------------------------------
Jerry Norman
At-Large BOD Member, 90 Minds
Smartbridge Partners
512.419.1444 x112


Original Message:
Sent: 12-07-2021 11:12
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

This prior thread is similar to what I think an ultimate solution might look like.

Either VI or a script to update the SO Line promise date with the new PO line required date

Caveats would be needed that if there are multiple POs referencing the same item with different required dates that this doesn't work cleanly

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990

Good. I would be interested in hearing the results of your Value Conversation with them. What elements of this are worth $$? Customer retention? Penalty fees? Diversion of employee attention and such? This symptom might be part of a larger issue they are trying to deal with, perhaps in inventory or warehouse management.

------------------------------
Jerry Norman
At-Large BOD Member, 90 Minds
Smartbridge Partners
512.419.1444 x112
------------------------------

Original Message:
Sent: 12-08-2021 10:51
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

I like this idea.
It's sort of a hybrid and requires someone to approve the updated order being sent by email which I think at least initially is a good idea so that customers aren't getting bombarded with emails if a PO date changes frequently.

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------


Original Message:
Sent: 12-08-2021 10:29
From: Kevin Moyes
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

I was thinking of something like this:

• Automated report to show them when there are date issues.
• Button script in SO Entry to update Promise Dates for that order based on the current PO data (with whatever conditional logic you want...).
• Then they can resend the updated SO normally.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 12-08-2021 10:23
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Thanks. This is looking like it's beyond the capabilities of Sage 100.
I checked DSD and they don't seem to have anything

Just to close the loop on this for future searchers - what I'm planning to do is suggesting the customer walk before they run.

First, create some type of report that shows this info and see whether having a report is enough.
Then, if the report isn't working I will take what I've learned from reporting and propose a software solution - this probably would be a scripting project however I'm not sure if scripting could totally resolve the issue. It might also be a VI job that runs overnight to update the promise dates. I have a healthy skepticism that updating the promise dates is the way to go because in some cases a customer may have specifically requested a LATER promise date and if we'd just overwriting whatever is in promise date we are now changing the intent of whoever took the order and manually created a future promise date ( customer will always say that will ' never ' happen until it does and they call you 36 months later when neither of you can remember the original design specification of what they asked...

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990


Original Message:
Sent: 12-07-2021 12:33
From: Jerry Norman
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

A simple-minded approach would be a weekly report flagging SOs tied to POs that have expected receipt dates beyond the SO Promise dates. The company then manually handles the consequences.

As you point out, some sort of scripting could probably get it most of the way there. This approach also has other drawbacks, including maintenance as the company's needs change.

Another approach is to explore a workflow tool. This could be KnowlegeSync; I did a similar project way back when, but I'm now bummed by their apparent lack of responsiveness. A more promising tool is Fisher Technology's BPA Platform (fka Taskcentre). Their business focus these days is ecomm integrating with ERP, but they do have Sage 100 connectors, and this sort of problem is right down their alley. Once a customer solves a problem like this, they are likely to think of other tasks/problems to use the tool on.

This can be structured as a Value Priced project in two stages. The first is to help them decide which approach is best for them, as all 3 have pros and cons. The second would be to implement the chosen approach for this problem.

------------------------------
Jerry Norman
At-Large BOD Member, 90 Minds
Smartbridge Partners
512.419.1444 x112


Original Message:
Sent: 12-07-2021 11:12
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

This prior thread is similar to what I think an ultimate solution might look like.

Either VI or a script to update the SO Line promise date with the new PO line required date

Caveats would be needed that if there are multiple POs referencing the same item with different required dates that this doesn't work cleanly

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990

Supply chain issues are hitting everyone right now, and they probably just need a way to manage customer expectations while PO receipts are delayed.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 12-08-2021 11:05
From: Jerry Norman
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Good. I would be interested in hearing the results of your Value Conversation with them. What elements of this are worth $$? Customer retention? Penalty fees? Diversion of employee attention and such? This symptom might be part of a larger issue they are trying to deal with, perhaps in inventory or warehouse management.

------------------------------
Jerry Norman
At-Large BOD Member, 90 Minds
Smartbridge Partners
512.419.1444 x112
------------------------------


Original Message:
Sent: 12-08-2021 10:51
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

I like this idea.
It's sort of a hybrid and requires someone to approve the updated order being sent by email which I think at least initially is a good idea so that customers aren't getting bombarded with emails if a PO date changes frequently.

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990


Original Message:
Sent: 12-08-2021 10:29
From: Kevin Moyes
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

I was thinking of something like this:

• Automated report to show them when there are date issues.
• Button script in SO Entry to update Promise Dates for that order based on the current PO data (with whatever conditional logic you want...).
• Then they can resend the updated SO normally.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 12-08-2021 10:23
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Thanks. This is looking like it's beyond the capabilities of Sage 100.
I checked DSD and they don't seem to have anything

Just to close the loop on this for future searchers - what I'm planning to do is suggesting the customer walk before they run.

First, create some type of report that shows this info and see whether having a report is enough.
Then, if the report isn't working I will take what I've learned from reporting and propose a software solution - this probably would be a scripting project however I'm not sure if scripting could totally resolve the issue. It might also be a VI job that runs overnight to update the promise dates. I have a healthy skepticism that updating the promise dates is the way to go because in some cases a customer may have specifically requested a LATER promise date and if we'd just overwriting whatever is in promise date we are now changing the intent of whoever took the order and manually created a future promise date ( customer will always say that will ' never ' happen until it does and they call you 36 months later when neither of you can remember the original design specification of what they asked...

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990


Original Message:
Sent: 12-07-2021 12:33
From: Jerry Norman
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

A simple-minded approach would be a weekly report flagging SOs tied to POs that have expected receipt dates beyond the SO Promise dates. The company then manually handles the consequences.

As you point out, some sort of scripting could probably get it most of the way there. This approach also has other drawbacks, including maintenance as the company's needs change.

Another approach is to explore a workflow tool. This could be KnowlegeSync; I did a similar project way back when, but I'm now bummed by their apparent lack of responsiveness. A more promising tool is Fisher Technology's BPA Platform (fka Taskcentre). Their business focus these days is ecomm integrating with ERP, but they do have Sage 100 connectors, and this sort of problem is right down their alley. Once a customer solves a problem like this, they are likely to think of other tasks/problems to use the tool on.

This can be structured as a Value Priced project in two stages. The first is to help them decide which approach is best for them, as all 3 have pros and cons. The second would be to implement the chosen approach for this problem.

------------------------------
Jerry Norman
At-Large BOD Member, 90 Minds
Smartbridge Partners
512.419.1444 x112


Original Message:
Sent: 12-07-2021 11:12
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

This prior thread is similar to what I think an ultimate solution might look like.

Either VI or a script to update the SO Line promise date with the new PO line required date

Caveats would be needed that if there are multiple POs referencing the same item with different required dates that this doesn't work cleanly

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990

Yes, that's the case here though I believe the issue has always existed to some extent and this was more clean up work for them. They also create automated inventory feeds nightly using Crystal and Windows Task Scheduler which bypasses a need for a more expensive EDI

I'm on a fixed fee annual agreement with them so this is not something I am proposing separately but is a part of my annual work.

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------

Original Message:
Sent: 12-08-2021 12:14
From: Kevin Moyes
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Supply chain issues are hitting everyone right now, and they probably just need a way to manage customer expectations while PO receipts are delayed.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 12-08-2021 11:05
From: Jerry Norman
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Good. I would be interested in hearing the results of your Value Conversation with them. What elements of this are worth $$? Customer retention? Penalty fees? Diversion of employee attention and such? This symptom might be part of a larger issue they are trying to deal with, perhaps in inventory or warehouse management.

------------------------------
Jerry Norman
At-Large BOD Member, 90 Minds
Smartbridge Partners
512.419.1444 x112


Original Message:
Sent: 12-08-2021 10:51
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

I like this idea.
It's sort of a hybrid and requires someone to approve the updated order being sent by email which I think at least initially is a good idea so that customers aren't getting bombarded with emails if a PO date changes frequently.

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990


Original Message:
Sent: 12-08-2021 10:29
From: Kevin Moyes
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

I was thinking of something like this:

• Automated report to show them when there are date issues.
• Button script in SO Entry to update Promise Dates for that order based on the current PO data (with whatever conditional logic you want...).
• Then they can resend the updated SO normally.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 12-08-2021 10:23
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Thanks. This is looking like it's beyond the capabilities of Sage 100.
I checked DSD and they don't seem to have anything

Just to close the loop on this for future searchers - what I'm planning to do is suggesting the customer walk before they run.

First, create some type of report that shows this info and see whether having a report is enough.
Then, if the report isn't working I will take what I've learned from reporting and propose a software solution - this probably would be a scripting project however I'm not sure if scripting could totally resolve the issue. It might also be a VI job that runs overnight to update the promise dates. I have a healthy skepticism that updating the promise dates is the way to go because in some cases a customer may have specifically requested a LATER promise date and if we'd just overwriting whatever is in promise date we are now changing the intent of whoever took the order and manually created a future promise date ( customer will always say that will ' never ' happen until it does and they call you 36 months later when neither of you can remember the original design specification of what they asked...

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990


Original Message:
Sent: 12-07-2021 12:33
From: Jerry Norman
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

A simple-minded approach would be a weekly report flagging SOs tied to POs that have expected receipt dates beyond the SO Promise dates. The company then manually handles the consequences.

As you point out, some sort of scripting could probably get it most of the way there. This approach also has other drawbacks, including maintenance as the company's needs change.

Another approach is to explore a workflow tool. This could be KnowlegeSync; I did a similar project way back when, but I'm now bummed by their apparent lack of responsiveness. A more promising tool is Fisher Technology's BPA Platform (fka Taskcentre). Their business focus these days is ecomm integrating with ERP, but they do have Sage 100 connectors, and this sort of problem is right down their alley. Once a customer solves a problem like this, they are likely to think of other tasks/problems to use the tool on.

This can be structured as a Value Priced project in two stages. The first is to help them decide which approach is best for them, as all 3 have pros and cons. The second would be to implement the chosen approach for this problem.

------------------------------
Jerry Norman
At-Large BOD Member, 90 Minds
Smartbridge Partners
512.419.1444 x112


Original Message:
Sent: 12-07-2021 11:12
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

This prior thread is similar to what I think an ultimate solution might look like.

Either VI or a script to update the SO Line promise date with the new PO line required date

Caveats would be needed that if there are multiple POs referencing the same item with different required dates that this doesn't work cleanly

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990

Wayne

Based on what you outlined below I think you could automate this. The nice part with below is you can implement in steps using Sage Alerts so customer can ease into this in regards to whether something is really working for what they need.

1. Use sage alerts to monitor purchase orders where the dates changed and only for POs that are directly linked to sales orders. You may have some specific requirements on what needs to be checked but sounds like date changed would be one.

2. Use this query in Sage alerts to grab the sales order numbers/Purchase Orders/Items you need to fix and make that be used to select against the sales order table. Note - for this step- you may want to use a combined key field in Sage Alerts so you get a hit. I would also suggest using a crystal report in sage alerts for this one since you need to get data from the PO table (new date) and send it to sales order. You are using the event in step 1 to figure out what POs where touched to pass it to this report. This part can email your customer to give them a list of what changed so if nothing else, they have that part.

4. This second query/report. in step 2 generates a csv file that can be imported into sage to change the dates on the sales order.

5. You write an alert to change the ship to date by running a VI job to import the file in step4

6. Now - for the alert to the customer - you could do the alert to monitor whenever the Sales Order line date is changed. Note - we always have fun getting these change fields to work in Sage Alerts so many times we go around this other ways - but if you can get it to work, it can send an alert to the customer to let them know that the line on their sales order has changed.

We use Sage Alerts to do all of this “automation” all the time when the customer doesn’t want to pay to have scripting done.

Disclaimer - I am outlining the above on only one cup of coffee so there might be something I missed but this is just to get the lay of the land on how to do it.

Sent from my iPhone

Thanks, Tara. I'm definitely considering Sage Alerts to manage some of this.
First I want the customer to look a the process completely manually with reports so they can spot any weaknesses or unexpected issues.
I think there are a few things this customer hasn't thought about and won't be clear until they see a report in front of them.

The new normal for customers seems to be that they want an Amazon.com type system with zero thought as to business rules.

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------

Original Message:
Sent: 12-15-2021 07:11
From: Tara Schinkel
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Wayne

Based on what you outlined below I think you could automate this. The nice part with below is you can implement in steps using Sage Alerts so customer can ease into this in regards to whether something is really working for what they need.

1. Use sage alerts to monitor purchase orders where the dates changed and only for POs that are directly linked to sales orders. You may have some specific requirements on what needs to be checked but sounds like date changed would be one.

2. Use this query in Sage alerts to grab the sales order numbers/Purchase Orders/Items you need to fix and make that be used to select against the sales order table. Note - for this step- you may want to use a combined key field in Sage Alerts so you get a hit. I would also suggest using a crystal report in sage alerts for this one since you need to get data from the PO table (new date) and send it to sales order. You are using the event in step 1 to figure out what POs where touched to pass it to this report. This part can email your customer to give them a list of what changed so if nothing else, they have that part.

4. This second query/report. in step 2 generates a csv file that can be imported into sage to change the dates on the sales order.

5. You write an alert to change the ship to date by running a VI job to import the file in step4

6. Now - for the alert to the customer - you could do the alert to monitor whenever the Sales Order line date is changed. Note - we always have fun getting these change fields to work in Sage Alerts so many times we go around this other ways - but if you can get it to work, it can send an alert to the customer to let them know that the line on their sales order has changed.

We use Sage Alerts to do all of this "automation" all the time when the customer doesn't want to pay to have scripting done.

Disclaimer - I am outlining the above on only one cup of coffee so there might be something I missed but this is just to get the lay of the land on how to do it.

Sent from my iPhone

"The new normal for customers seems to be that they want an Amazon.com type system with zero thought as to business rules."  @Wayne Schulz  This reminds me of a customer that I was discussing a new web portal with a few years ago.  He said "Ernie (the company president) wants the portal to look just like Amazon!".    I replied, please tell Ernie that he's going to have to increase the budget a tad above $25K if he wants it to look just like Amazon.  LOL!!  Make it $100M and we'll see what we can do.
​

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

Original Message:
Sent: 12-15-2021 09:12
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Thanks, Tara. I'm definitely considering Sage Alerts to manage some of this.
First I want the customer to look a the process completely manually with reports so they can spot any weaknesses or unexpected issues.
I think there are a few things this customer hasn't thought about and won't be clear until they see a report in front of them.

The new normal for customers seems to be that they want an Amazon.com type system with zero thought as to business rules.

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------


Original Message:
Sent: 12-15-2021 07:11
From: Tara Schinkel
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Wayne

Based on what you outlined below I think you could automate this. The nice part with below is you can implement in steps using Sage Alerts so customer can ease into this in regards to whether something is really working for what they need.

1. Use sage alerts to monitor purchase orders where the dates changed and only for POs that are directly linked to sales orders. You may have some specific requirements on what needs to be checked but sounds like date changed would be one.

2. Use this query in Sage alerts to grab the sales order numbers/Purchase Orders/Items you need to fix and make that be used to select against the sales order table. Note - for this step- you may want to use a combined key field in Sage Alerts so you get a hit. I would also suggest using a crystal report in sage alerts for this one since you need to get data from the PO table (new date) and send it to sales order. You are using the event in step 1 to figure out what POs where touched to pass it to this report. This part can email your customer to give them a list of what changed so if nothing else, they have that part.

4. This second query/report. in step 2 generates a csv file that can be imported into sage to change the dates on the sales order.

5. You write an alert to change the ship to date by running a VI job to import the file in step4

6. Now - for the alert to the customer - you could do the alert to monitor whenever the Sales Order line date is changed. Note - we always have fun getting these change fields to work in Sage Alerts so many times we go around this other ways - but if you can get it to work, it can send an alert to the customer to let them know that the line on their sales order has changed.

We use Sage Alerts to do all of this "automation" all the time when the customer doesn't want to pay to have scripting done.

Disclaimer - I am outlining the above on only one cup of coffee so there might be something I missed but this is just to get the lay of the land on how to do it.

Sent from my iPhone

Tara - Thanks for putting this solution architecture for members to learn from! Very appropriate.

Wayne - your customer management strategy is something I hope more 90 Minders adopt. We consultants all too often overestimate our customers' understanding of the complexities involved with addressing their challenges. Automation, especially, is far to easy to visualize the result and be completely blind to the really hard work it takes to produce it. (This really irked me about Sage's Steve Kelly in his Summit demos ...)

------------------------------
Jerry Norman
At-Large BOD Member, 90 Minds
Smartbridge Partners
512.419.1444 x112
------------------------------

Original Message:
Sent: 12-15-2021 09:12
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Thanks, Tara. I'm definitely considering Sage Alerts to manage some of this.
First I want the customer to look a the process completely manually with reports so they can spot any weaknesses or unexpected issues.
I think there are a few things this customer hasn't thought about and won't be clear until they see a report in front of them.

The new normal for customers seems to be that they want an Amazon.com type system with zero thought as to business rules.

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------


Original Message:
Sent: 12-15-2021 07:11
From: Tara Schinkel
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Wayne

Based on what you outlined below I think you could automate this. The nice part with below is you can implement in steps using Sage Alerts so customer can ease into this in regards to whether something is really working for what they need.

1. Use sage alerts to monitor purchase orders where the dates changed and only for POs that are directly linked to sales orders. You may have some specific requirements on what needs to be checked but sounds like date changed would be one.

2. Use this query in Sage alerts to grab the sales order numbers/Purchase Orders/Items you need to fix and make that be used to select against the sales order table. Note - for this step- you may want to use a combined key field in Sage Alerts so you get a hit. I would also suggest using a crystal report in sage alerts for this one since you need to get data from the PO table (new date) and send it to sales order. You are using the event in step 1 to figure out what POs where touched to pass it to this report. This part can email your customer to give them a list of what changed so if nothing else, they have that part.

4. This second query/report. in step 2 generates a csv file that can be imported into sage to change the dates on the sales order.

5. You write an alert to change the ship to date by running a VI job to import the file in step4

6. Now - for the alert to the customer - you could do the alert to monitor whenever the Sales Order line date is changed. Note - we always have fun getting these change fields to work in Sage Alerts so many times we go around this other ways - but if you can get it to work, it can send an alert to the customer to let them know that the line on their sales order has changed.

We use Sage Alerts to do all of this "automation" all the time when the customer doesn't want to pay to have scripting done.

Disclaimer - I am outlining the above on only one cup of coffee so there might be something I missed but this is just to get the lay of the land on how to do it.

Sent from my iPhone

Yes, we try to push running complicated processes manually for a while before enabling automation.  At the very least, it increases the impression of value for what we configure, but you can also learn about considerations not covered in the initial design discussions.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 12-15-2021 11:06
From: Jerry Norman
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Tara - Thanks for putting this solution architecture for members to learn from! Very appropriate.

Wayne - your customer management strategy is something I hope more 90 Minders adopt. We consultants all too often overestimate our customers' understanding of the complexities involved with addressing their challenges. Automation, especially, is far to easy to visualize the result and be completely blind to the really hard work it takes to produce it. (This really irked me about Sage's Steve Kelly in his Summit demos ...)

------------------------------
Jerry Norman
At-Large BOD Member, 90 Minds
Smartbridge Partners
512.419.1444 x112
------------------------------


Original Message:
Sent: 12-15-2021 09:12
From: Wayne Schulz
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Thanks, Tara. I'm definitely considering Sage Alerts to manage some of this.
First I want the customer to look a the process completely manually with reports so they can spot any weaknesses or unexpected issues.
I think there are a few things this customer hasn't thought about and won't be clear until they see a report in front of them.

The new normal for customers seems to be that they want an Amazon.com type system with zero thought as to business rules.

------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990


Original Message:
Sent: 12-15-2021 07:11
From: Tara Schinkel
Subject: Proactive Backorder Promise Date Management Based on Purchase Order Required Date Changes

Wayne

Based on what you outlined below I think you could automate this. The nice part with below is you can implement in steps using Sage Alerts so customer can ease into this in regards to whether something is really working for what they need.

1. Use sage alerts to monitor purchase orders where the dates changed and only for POs that are directly linked to sales orders. You may have some specific requirements on what needs to be checked but sounds like date changed would be one.

2. Use this query in Sage alerts to grab the sales order numbers/Purchase Orders/Items you need to fix and make that be used to select against the sales order table. Note - for this step- you may want to use a combined key field in Sage Alerts so you get a hit. I would also suggest using a crystal report in sage alerts for this one since you need to get data from the PO table (new date) and send it to sales order. You are using the event in step 1 to figure out what POs where touched to pass it to this report. This part can email your customer to give them a list of what changed so if nothing else, they have that part.

4. This second query/report. in step 2 generates a csv file that can be imported into sage to change the dates on the sales order.

5. You write an alert to change the ship to date by running a VI job to import the file in step4

6. Now - for the alert to the customer - you could do the alert to monitor whenever the Sales Order line date is changed. Note - we always have fun getting these change fields to work in Sage Alerts so many times we go around this other ways - but if you can get it to work, it can send an alert to the customer to let them know that the line on their sales order has changed.

We use Sage Alerts to do all of this "automation" all the time when the customer doesn't want to pay to have scripting done.

Disclaimer - I am outlining the above on only one cup of coffee so there might be something I missed but this is just to get the lay of the land on how to do it.

Sent from my iPhone

Update - I met with the customer today and this is how they have initially decided to proceed: 

Monitor the Purchase Order Header for a change in the required date.

We talked about Sage Alerts and they are hesitant to spend the money and instead proposed adding a PO header UDF checkbox "Required Date Change".

The person making the change on the PO would be tasked with adding this checkmark.

Then overnight they want to print a report of all the open POs where there is a required date change flag ( UDF is checked ).
Along with the report they want a subreport showing he open sales orders and the line item promise date for any items that were on the above PO.

Once this report is printed  we will use VI to reset all the PO Header "Required Date Change" flags back to "N" which essentially gets them ready for the next day. This customer already has Logicity ( similar to Visual Cut ) so we will use that to create a CSV of all the PO numbers with Required Date Change = "Y" and then use an unattended VI to import those back to PO Header and change flag from Y to N on the "Required Data Change" UDF.

They swear there's only one vendor PO that is issued for a specific item. I think this will likely uncover one or two other things they haven't considered. This is a very small office with one person doing purchase orders and one person doing sales orders. Clearly this type of semi-manual automation probably wouldn't scale in a bigger company.


------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------