Sage 100

Saw previous posts about forcing Due date by having it placed after the terms code when addressing AP invoice imports. This does not seem to work with PO invoice import.  The due date needs to be imported.  My work around so far is to export the header data for receipts in process and then import the fixed due date to the existing receipt.  Is there a better way?

------------------------------
alan niergarth
Velosio LLC
------------------------------

Have you tried moving the Due Date in the import definition to be the last header field set?
Are you setting the Invoice Date or letting the system default it for you?
If the latter, trying making sure to set the invoice date before the terms code, then set the due date.
There is probably another way but if you want to using the current date for the invoice date, set the field to calculated and use coSession'SystemDate$, coSession'ModuleDate$, or DTE(0:"%Y%Mz%Dz"). I seem to recall at one point something like <SystemDate> could be used but i'm not positive about that so i just use one of the above methods.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

I have experimented with moving the Due Date around in the order of import.  The invoice date is being imported.  If have tried using File Assigned terms and just setting terms at 00.  I have tried assigning the due date and importing the due date.

------------------------------
alan niergarth
Velosio LLC
------------------------------

Original Message:
Sent: 08-29-2019 00:29
From: David Speck II
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

Have you tried moving the Due Date in the import definition to be the last header field set?
Are you setting the Invoice Date or letting the system default it for you?
If the latter, trying making sure to set the invoice date before the terms code, then set the due date.
There is probably another way but if you want to using the current date for the invoice date, set the field to calculated and use coSession'SystemDate$, coSession'ModuleDate$, or DTE(0:"%Y%Mz%Dz"). I seem to recall at one point something like <SystemDate> could be used but i'm not positive about that so i just use one of the above methods.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

​Just a thought, which I have used in AP and PO I believe, since you have the Vendor, on the Terms Code Assign this to the Vendor's Term Code and leave Due Date off the import, by default and Business Logic it should auto populate. Otherwise I have had to also do a temp calc on Invoice date plus Terms, though that was in older versions.

------------------------------
Ron Peterson
DSD Business Systems
------------------------------

Original Message:
Sent: 08-29-2019 08:45
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

I have experimented with moving the Due Date around in the order of import.  The invoice date is being imported.  If have tried using File Assigned terms and just setting terms at 00.  I have tried assigning the due date and importing the due date.

------------------------------
alan niergarth
Velosio LLC
------------------------------


Original Message:
Sent: 08-29-2019 00:29
From: David Speck II
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

Have you tried moving the Due Date in the import definition to be the last header field set?
Are you setting the Invoice Date or letting the system default it for you?
If the latter, trying making sure to set the invoice date before the terms code, then set the due date.
There is probably another way but if you want to using the current date for the invoice date, set the field to calculated and use coSession'SystemDate$, coSession'ModuleDate$, or DTE(0:"%Y%Mz%Dz"). I seem to recall at one point something like <SystemDate> could be used but i'm not positive about that so i just use one of the above methods.

------------------------------
David Speck II
Tennessee Software Solutions

The job log after running the import shows the desired due date but DFDM shows the calculated date which overrides the desired due date.  At this point a second import job to 'fix" the receipt is working

------------------------------
alan niergarth
Velosio LLC
------------------------------

Original Message:
Sent: 08-29-2019 12:08
From: Ron Peterson
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

​Just a thought, which I have used in AP and PO I believe, since you have the Vendor, on the Terms Code Assign this to the Vendor's Term Code and leave Due Date off the import, by default and Business Logic it should auto populate. Otherwise I have had to also do a temp calc on Invoice date plus Terms, though that was in older versions.

------------------------------
Ron Peterson
DSD Business Systems
------------------------------


Original Message:
Sent: 08-29-2019 08:45
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

I have experimented with moving the Due Date around in the order of import.  The invoice date is being imported.  If have tried using File Assigned terms and just setting terms at 00.  I have tried assigning the due date and importing the due date.

------------------------------
alan niergarth
Velosio LLC


Original Message:
Sent: 08-29-2019 00:29
From: David Speck II
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

Have you tried moving the Due Date in the import definition to be the last header field set?
Are you setting the Invoice Date or letting the system default it for you?
If the latter, trying making sure to set the invoice date before the terms code, then set the due date.
There is probably another way but if you want to using the current date for the invoice date, set the field to calculated and use coSession'SystemDate$, coSession'ModuleDate$, or DTE(0:"%Y%Mz%Dz"). I seem to recall at one point something like <SystemDate> could be used but i'm not positive about that so i just use one of the above methods.

------------------------------
David Speck II
Tennessee Software Solutions

Are you positive your calculated date when setting the due date during the first pass is actually passing validation and not failing, thus causing it to be calculated by the business object based on the invoice date and terms?

Which date format are you using when setting the due date and which date mask are you telling the invoice due date to expect?


------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Original Message:
Sent: 08-29-2019 14:09
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

The job log after running the import shows the desired due date but DFDM shows the calculated date which overrides the desired due date.  At this point a second import job to 'fix" the receipt is working

------------------------------
alan niergarth
Velosio LLC
------------------------------


Original Message:
Sent: 08-29-2019 12:08
From: Ron Peterson
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

​Just a thought, which I have used in AP and PO I believe, since you have the Vendor, on the Terms Code Assign this to the Vendor's Term Code and leave Due Date off the import, by default and Business Logic it should auto populate. Otherwise I have had to also do a temp calc on Invoice date plus Terms, though that was in older versions.

------------------------------
Ron Peterson
DSD Business Systems


Original Message:
Sent: 08-29-2019 08:45
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

I have experimented with moving the Due Date around in the order of import.  The invoice date is being imported.  If have tried using File Assigned terms and just setting terms at 00.  I have tried assigning the due date and importing the due date.

------------------------------
alan niergarth
Velosio LLC


Original Message:
Sent: 08-29-2019 00:29
From: David Speck II
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

Have you tried moving the Due Date in the import definition to be the last header field set?
Are you setting the Invoice Date or letting the system default it for you?
If the latter, trying making sure to set the invoice date before the terms code, then set the due date.
There is probably another way but if you want to using the current date for the invoice date, set the field to calculated and use coSession'SystemDate$, coSession'ModuleDate$, or DTE(0:"%Y%Mz%Dz"). I seem to recall at one point something like <SystemDate> could be used but i'm not positive about that so i just use one of the above methods.

------------------------------
David Speck II
Tennessee Software Solutions

My raw data for the due date is a text string YYYYMMDD.  Same as my Import field selection. I've also tried runtime assigning the due date with same format. The due date value appears to be overwritten when the record is saved and being recalculated based on the terms and the invoice date.  Its a simple import job that works except for that value:


------------------------------
alan niergarth
Velosio LLC
------------------------------

Original Message:
Sent: 08-29-2019 14:14
From: David Speck II
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

Are you positive your calculated date when setting the due date during the first pass is actually passing validation and not failing, thus causing it to be calculated by the business object based on the invoice date and terms?

Which date format are you using when setting the due date and which date mask are you telling the invoice due date to expect?

If you are using the coSession'SystemDate$ property, then you should be using the "YYYYMMDD" mask.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------


Original Message:
Sent: 08-29-2019 14:09
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

The job log after running the import shows the desired due date but DFDM shows the calculated date which overrides the desired due date.  At this point a second import job to 'fix" the receipt is working

------------------------------
alan niergarth
Velosio LLC


Original Message:
Sent: 08-29-2019 12:08
From: Ron Peterson
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

​Just a thought, which I have used in AP and PO I believe, since you have the Vendor, on the Terms Code Assign this to the Vendor's Term Code and leave Due Date off the import, by default and Business Logic it should auto populate. Otherwise I have had to also do a temp calc on Invoice date plus Terms, though that was in older versions.

------------------------------
Ron Peterson
DSD Business Systems


Original Message:
Sent: 08-29-2019 08:45
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

I have experimented with moving the Due Date around in the order of import.  The invoice date is being imported.  If have tried using File Assigned terms and just setting terms at 00.  I have tried assigning the due date and importing the due date.

------------------------------
alan niergarth
Velosio LLC


Original Message:
Sent: 08-29-2019 00:29
From: David Speck II
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

Have you tried moving the Due Date in the import definition to be the last header field set?
Are you setting the Invoice Date or letting the system default it for you?
If the latter, trying making sure to set the invoice date before the terms code, then set the due date.
There is probably another way but if you want to using the current date for the invoice date, set the field to calculated and use coSession'SystemDate$, coSession'ModuleDate$, or DTE(0:"%Y%Mz%Dz"). I seem to recall at one point something like <SystemDate> could be used but i'm not positive about that so i just use one of the above methods.

------------------------------
David Speck II
Tennessee Software Solutions

Craziness! Since you have a working solution, I'm going to go ahead and close it to Sage 100. #Urgent​

------------------------------
Robert Wood
DDF Consulting Group, Inc.
Ocala FL
352-615-5898
------------------------------

Original Message:
Sent: 08-30-2019 08:40
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

My raw data for the due date is a text string YYYYMMDD.  Same as my Import field selection. I've also tried runtime assigning the due date with same format. The due date value appears to be overwritten when the record is saved and being recalculated based on the terms and the invoice date.  Its a simple import job that works except for that value:

------------------------------
alan niergarth
Velosio LLC
------------------------------


Original Message:
Sent: 08-29-2019 14:14
From: David Speck II
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

Are you positive your calculated date when setting the due date during the first pass is actually passing validation and not failing, thus causing it to be calculated by the business object based on the invoice date and terms?

Which date format are you using when setting the due date and which date mask are you telling the invoice due date to expect?

If you are using the coSession'SystemDate$ property, then you should be using the "YYYYMMDD" mask.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 08-29-2019 14:09
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

The job log after running the import shows the desired due date but DFDM shows the calculated date which overrides the desired due date.  At this point a second import job to 'fix" the receipt is working

------------------------------
alan niergarth
Velosio LLC


Original Message:
Sent: 08-29-2019 12:08
From: Ron Peterson
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

​Just a thought, which I have used in AP and PO I believe, since you have the Vendor, on the Terms Code Assign this to the Vendor's Term Code and leave Due Date off the import, by default and Business Logic it should auto populate. Otherwise I have had to also do a temp calc on Invoice date plus Terms, though that was in older versions.

------------------------------
Ron Peterson
DSD Business Systems


Original Message:
Sent: 08-29-2019 08:45
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

I have experimented with moving the Due Date around in the order of import.  The invoice date is being imported.  If have tried using File Assigned terms and just setting terms at 00.  I have tried assigning the due date and importing the due date.

------------------------------
alan niergarth
Velosio LLC


Original Message:
Sent: 08-29-2019 00:29
From: David Speck II
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

Have you tried moving the Due Date in the import definition to be the last header field set?
Are you setting the Invoice Date or letting the system default it for you?
If the latter, trying making sure to set the invoice date before the terms code, then set the due date.
There is probably another way but if you want to using the current date for the invoice date, set the field to calculated and use coSession'SystemDate$, coSession'ModuleDate$, or DTE(0:"%Y%Mz%Dz"). I seem to recall at one point something like <SystemDate> could be used but i'm not positive about that so i just use one of the above methods.

------------------------------
David Speck II
Tennessee Software Solutions

Import your date to a UDF, then script a pre-write update to the regular field when the module is VI? 
The date might be refreshed when doing PreTotals (?), and a PreWrite script could bypass if that is the problem.

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

Original Message:
Sent: 08-30-2019 08:40
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

My raw data for the due date is a text string YYYYMMDD.  Same as my Import field selection. I've also tried runtime assigning the due date with same format. The due date value appears to be overwritten when the record is saved and being recalculated based on the terms and the invoice date.  Its a simple import job that works except for that value:

------------------------------
alan niergarth
Velosio LLC
------------------------------


Original Message:
Sent: 08-29-2019 14:14
From: David Speck II
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

Are you positive your calculated date when setting the due date during the first pass is actually passing validation and not failing, thus causing it to be calculated by the business object based on the invoice date and terms?

Which date format are you using when setting the due date and which date mask are you telling the invoice due date to expect?

If you are using the coSession'SystemDate$ property, then you should be using the "YYYYMMDD" mask.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 08-29-2019 14:09
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

The job log after running the import shows the desired due date but DFDM shows the calculated date which overrides the desired due date.  At this point a second import job to 'fix" the receipt is working

------------------------------
alan niergarth
Velosio LLC


Original Message:
Sent: 08-29-2019 12:08
From: Ron Peterson
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

​Just a thought, which I have used in AP and PO I believe, since you have the Vendor, on the Terms Code Assign this to the Vendor's Term Code and leave Due Date off the import, by default and Business Logic it should auto populate. Otherwise I have had to also do a temp calc on Invoice date plus Terms, though that was in older versions.

------------------------------
Ron Peterson
DSD Business Systems


Original Message:
Sent: 08-29-2019 08:45
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

I have experimented with moving the Due Date around in the order of import.  The invoice date is being imported.  If have tried using File Assigned terms and just setting terms at 00.  I have tried assigning the due date and importing the due date.

------------------------------
alan niergarth
Velosio LLC


Original Message:
Sent: 08-29-2019 00:29
From: David Speck II
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

Have you tried moving the Due Date in the import definition to be the last header field set?
Are you setting the Invoice Date or letting the system default it for you?
If the latter, trying making sure to set the invoice date before the terms code, then set the due date.
There is probably another way but if you want to using the current date for the invoice date, set the field to calculated and use coSession'SystemDate$, coSession'ModuleDate$, or DTE(0:"%Y%Mz%Dz"). I seem to recall at one point something like <SystemDate> could be used but i'm not positive about that so i just use one of the above methods.

------------------------------
David Speck II
Tennessee Software Solutions

If it comes down to that, you should be able to use the following in a header pre-write perform logic. Just replace the [x] with the column number with your due date in "YYYYMMDD" format or replace "IMP$[x]" with whatever calculated date you come up with in "YYYYMMDD" format.

coBusiness'SetValue("InvoiceDueDate$",IMP$[x]) ! '​

FYI, not tested but in theory, it should work as long as you specify the date in the right format.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Original Message:
Sent: 09-03-2019 13:42
From: Kevin Moyes
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

Import your date to a UDF, then script a pre-write update to the regular field when the module is VI?
The date might be refreshed when doing PreTotals (?), and a PreWrite script could bypass if that is the problem.

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


Original Message:
Sent: 08-30-2019 08:40
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

My raw data for the due date is a text string YYYYMMDD.  Same as my Import field selection. I've also tried runtime assigning the due date with same format. The due date value appears to be overwritten when the record is saved and being recalculated based on the terms and the invoice date.  Its a simple import job that works except for that value:

------------------------------
alan niergarth
Velosio LLC


Original Message:
Sent: 08-29-2019 14:14
From: David Speck II
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

Are you positive your calculated date when setting the due date during the first pass is actually passing validation and not failing, thus causing it to be calculated by the business object based on the invoice date and terms?

Which date format are you using when setting the due date and which date mask are you telling the invoice due date to expect?

If you are using the coSession'SystemDate$ property, then you should be using the "YYYYMMDD" mask.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 08-29-2019 14:09
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

The job log after running the import shows the desired due date but DFDM shows the calculated date which overrides the desired due date.  At this point a second import job to 'fix" the receipt is working

------------------------------
alan niergarth
Velosio LLC


Original Message:
Sent: 08-29-2019 12:08
From: Ron Peterson
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

​Just a thought, which I have used in AP and PO I believe, since you have the Vendor, on the Terms Code Assign this to the Vendor's Term Code and leave Due Date off the import, by default and Business Logic it should auto populate. Otherwise I have had to also do a temp calc on Invoice date plus Terms, though that was in older versions.

------------------------------
Ron Peterson
DSD Business Systems


Original Message:
Sent: 08-29-2019 08:45
From: alan niergarth
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

I have experimented with moving the Due Date around in the order of import.  The invoice date is being imported.  If have tried using File Assigned terms and just setting terms at 00.  I have tried assigning the due date and importing the due date.

------------------------------
alan niergarth
Velosio LLC


Original Message:
Sent: 08-29-2019 00:29
From: David Speck II
Subject: Invoice Due Date - PO Receipt of Goods with Invoice

Have you tried moving the Due Date in the import definition to be the last header field set?
Are you setting the Invoice Date or letting the system default it for you?
If the latter, trying making sure to set the invoice date before the terms code, then set the due date.
There is probably another way but if you want to using the current date for the invoice date, set the field to calculated and use coSession'SystemDate$, coSession'ModuleDate$, or DTE(0:"%Y%Mz%Dz"). I seem to recall at one point something like <SystemDate> could be used but i'm not positive about that so i just use one of the above methods.

------------------------------
David Speck II
Tennessee Software Solutions