Information Systems:Bank EDI - Revision history

Norwinu: /* EFT file not generated */

2019-09-04T21:34:54Z

EFT file not generated

Norwinu: /* EFT file not generated */

2019-09-04T21:31:39Z

EFT file not generated

Norwinu at 21:31, 4 September 2019

2019-09-04T21:31:27Z

Norwinu at 21:10, 4 September 2019

2019-09-04T21:10:05Z

Norwinu: /* Issues */

2019-09-04T19:02:25Z

Issues

Sheilav at 22:12, 24 January 2017

2017-01-24T22:12:56Z

Sheilav at 22:07, 24 January 2017

2017-01-24T22:07:46Z

Sheilav at 21:55, 24 January 2017

2017-01-24T21:55:27Z

Sheilav: /* Credit and Debit Card Transactions */

2016-11-30T20:23:51Z

Credit and Debit Card Transactions

Sheilav: /* Bank EDI Does Not Post */

2016-11-30T20:19:30Z

Bank EDI Does Not Post

@@ Line 173: / Line 173: @@
 * On a command line, type CPYTOIMPF and F4-prompt.
 * In the "From file" field, enter <code>/QSYS.LIB/UWDASWPRDD.LIB/EFEFTSP.FILE/'''XYZ'''</code>, where XYZ is the file member determined in the previous step.
-* In the "To file" field, enter a directory on the IFS. Usually, I output this to my home directory i.e. <code>/home/NORWINU></code>. You could also try the actual folder it's supposed to go to (EFT/), but I'm more cautious.
+* In the "To file" field, enter a directory on the IFS. Usually, I output this to my home directory i.e. <code>/home/NORWINU</code>. You could also try the actual folder it's supposed to go to (EFT/), but I'm more cautious.
 * Change '''Stream file option''' to '''*REPLACE''' and '''Stream file code page''' to '''*PCASCII'''.
 * Hit Enter.

← Older revision		Revision as of 21:31, 4 September 2019
Line 161:		Line 161:

	===EFT file not generated===		===EFT file not generated===
−	Exercise caution when attempting this "fix".

	When the "EC" menu option/function is run during the AR payments process, a text file is generated for upload to CIBC and automatically placed in the IFS. This file represents payments (AR credits) to customers. There have been several instances where the file does not get generated i.e. Accounting will report it missing from the EFT/ folder on the IFS. Because file generation is only one step in the EFT process, it is not feasible to re-run EC (in fact, it is not even possible, because the job status will have changed to prevent a duplicate run). Therefore the system command used to create the file (CPYTOSTMF) must be executed manually:		When the "EC" menu option/function is run during the AR payments process, a text file is generated for upload to CIBC and automatically placed in the IFS. This file represents payments (AR credits) to customers. There have been several instances where the file does not get generated i.e. Accounting will report it missing from the EFT/ folder on the IFS. Because file generation is only one step in the EFT process, it is not feasible to re-run EC (in fact, it is not even possible, because the job status will have changed to prevent a duplicate run). Therefore the system command used to create the file (CPYTOSTMF) must be executed manually:

@@ Line 163: / Line 163: @@
  Exercise caution when attempting this "fix".
-When the "EC" menu option/function is run during the AR payments process, a file is generated for upload to CIBC. This file represents payments (AR credits) to customers. There have been several instances where the file does not get generated i.e. Accounting will report it missing from the EFT/ folder on the IFS. Because file generation is only one step in the EFT process, it is not feasible to re-run EC (in fact, it is not even possible if the rest of the function completes, because the job status will have changed to prevent a duplicate run). Therefore the system command used to create the file (CPYTOSTMF) must be executed manually:
+When the "EC" menu option/function is run during the AR payments process, a text file is generated for upload to CIBC and automatically placed in the IFS. This file represents payments (AR credits) to customers. There have been several instances where the file does not get generated i.e. Accounting will report it missing from the EFT/ folder on the IFS. Because file generation is only one step in the EFT process, it is not feasible to re-run EC (in fact, it is not even possible, because the job status will have changed to prevent a duplicate run). Therefore the system command used to create the file (CPYTOSTMF) must be executed manually:
-* First verify that the rest of the process ("E1") completed sucessfully:
+* First verify that the rest of the process (EC/E1) completed sucessfully:
 :* Check the status of the statement run. It should be at C1.
 :* Check that a printout of the G/L postings printed. Spot check a transaction listed on the printout in G/L 120000 (A/R).
@@ Line 171: / Line 171: @@
 :* WRKMBRPDM for file UWDASWPRDD/EFEFTSP.
 :* Find the desired member, and view it to verify that it is the correct member for which you would like to generate a file.

← Older revision		Revision as of 21:10, 4 September 2019
Line 163:		Line 163:
	Exercise caution when attempting this "fix".		Exercise caution when attempting this "fix".

−	When the "EC" menu option/function is run during the AR payments process, a file is generated for upload to CIBC. This file represents payments (AR credits) to customers. There have been several instances where the file does not get generated i.e. is missing from the EFT/ folder on the IFS. Because file generation is only one step in the ~~series~~ of ~~steps~~ ~~run~~ by ~~executing~~ "EC"), it ~~cannot~~ be ~~easily~~ ~~redone~~.	+	When the "EC" menu option/function is run during the AR payments process, a file is generated for upload to CIBC. This file represents payments (AR credits) to customers. There have been several instances where the file does not get generated i.e. Accounting will report it missing from the EFT/ folder on the IFS. Because file generation is only one step in the EFT process, it is not feasible to re-run EC (in fact, it is not even possible if the rest of the function completes, because the job status will have changed to prevent a duplicate run). Therefore the system command used to create the file (CPYTOSTMF) must be executed manually:
		+
		+	* First verify that the rest of the process ("E1") completed sucessfully:
		+	:* Check the status of the statement run. It should be at C1.
		+	:* Check that a printout of the G/L postings printed. Spot check a transaction listed on the printout in G/L 120000 (A/R).
		+	* Obtain the file member name that needs to output to a file:
		+	:* WRKMBRPDM for file UWDASWPRDD/EFEFTSP.
		+	:* Find the desired member, and view it to verify that it is the correct member for which you would like to generate a file.
		+

← Older revision		Revision as of 19:02, 4 September 2019
Line 159:		Line 159:

	Even though the import process will allow you to import a file with a duplicate name, it is best not to do it.		Even though the import process will allow you to import a file with a duplicate name, it is best not to do it.
		+
		+	===EFT file not generated===
		+	Exercise caution when attempting this "fix".
		+
		+	When the "EC" menu option/function is run during the AR payments process, a file is generated for upload to CIBC. This file represents payments (AR credits) to customers. There have been several instances where the file does not get generated i.e. is missing from the EFT/ folder on the IFS. Because file generation is only one step in the series of steps run by executing "EC"), it cannot be easily redone.

@@ Line 143: / Line 143: @@
 ===Duplicate File Name===
-If you try to import file with the same name as one that has already been imported, you will get a message.  You should cancel the process, and investigate it.  Using the 'RD' (raw data) option, look at the file that has already been uploaded.  A file with no transactions will have two records; a batch header and batch trailer (record types 10 and 99).
+If you try to import a file with the same name as one that has already been imported, you will get a message.  You should cancel the process, and investigate it.  Using the 'RD' (raw data) option, look at the file that has already been uploaded.  A file with no transactions will have two records; a batch header and batch trailer (record types 10 and 99).
   Columns . . . :    1 121                    Browse                              UWDASWPRDD/BECPRDP
@@ Line 154: / Line 154: @@
          ****************** End of data ************************************************************
-If the new file to import also looks like this, it can go straight to the archive (to keep a record of the fact it was received twice).  Change the name by, for example, adding a letter to end to make it clear it was a duplicate file.
+If the new file to import has the same records as the original file, it can go straight to the archive (to keep a record of the fact it was received twice).  Change the name by, for example, adding 'dup' to end to make it clear it was a duplicate file.
-If the two files are different, I would question the bank - there is only supposed to be one file per day, and the date is part of the file name.  If the second file should also be uploaded, the file name should be changed; but using a different method than above.  The files are imported with the name 'C', six digit date, then the file suffix; which is the Julian day.  To import a second file for the same date, change the file suffix to make the name unique.
+If the two files are different, I would question the bank - there is only supposed to be one file per day, and the date is part of the file name.  If the second file should also be uploaded, the file name should be changed; but using a different method than above.  The files are imported with the name 'C', six digit date (from the file name), then the file suffix; which is the Julian day.  To import a second file for the same date, change the file suffix to make the name unique.
 Even though the import process will allow you to import a file with a duplicate name, it is best not to do it.
 [[Category: Extensions]]

@@ Line 151: / Line 151: @@
 .00 1001191711440310946585  TRN
 .00 990000000020000000000000000000000000000000000000000000000000000TRN
-.00 �
+.00
          ****************** End of data ************************************************************
 If the new file to import also looks like this, it can go straight to the archive (to keep a record of the fact it was received twice).  Change the name by, for example, adding a letter to end to make it clear it was a duplicate file.
-If the two files are different, I would question the bank - there is only supposed to be one file per day, and the date is part of the file name.  If the second file should also be uploaded, the file name should be changed; but using a different method.
+If the two files are different, I would question the bank - there is only supposed to be one file per day, and the date is part of the file name.  If the second file should also be uploaded, the file name should be changed; but using a different method than above.  The files are imported with the name 'C', six digit date, then the file suffix; which is the Julian day.  To import a second file for the same date, change the file suffix to make the name unique.

@@ Line 140: / Line 140: @@
 Document type / identity is AMX / AX, DBT / DB, DS / DS, MC / MC, VIS/ VI.
 This will post to A/R and 730200.  Entries to move from 730200 to the correct bank accounts will not post, but will still be in SROIBT.  The next time bank EDI is posted, they will be included.  However one entry will be missing, so the journal will not be balanced.  See ‘Problems / Finance / Journal in Error / Out of Balance – Debit/Credit Card Transactions’ for an explanation and how to fix it.
 [[Category: Extensions]]

← Older revision		Revision as of 20:23, 30 November 2016
Line 42:		Line 42:

	Transactions are summarized by card type, and put them into accounts receivable for the shareholder. They will show on the next statement. If they make their account go into credit, we put the amount into their bank account via EFT.		Transactions are summarized by card type, and put them into accounts receivable for the shareholder. They will show on the next statement. If they make their account go into credit, we put the amount into their bank account via EFT.
		+
		+	Because this application was originally written for TD, Chase transactions must be translated to use the same transaction types and card types. If Chase sends a record with a new, unmapped type, it will have to be added to tables UX BEDICPCRDT or UX BEDICPTRNT.

	As well as these A/R transactions, entries to the G/L are also made; ie. credit A/R and debit cash.		As well as these A/R transactions, entries to the G/L are also made; ie. credit A/R and debit cash.

@@ Line 96: / Line 96: @@
 Only one A/R batch payment process can be run at a time.  Base ASW makes sure this doesn't happen.  Several extensions process payments without checking first to make sure another isn't currently running.  Originally this was okay, because QBATCH only ran one job at a time.  We changed it to allow two.
-When more than one card type is in a batch, this process submitted to QBATCH for each type.  As each may take a moment to run, the next must wait to be submitted.  The user will see this screen -
+When more than one card type is in a batch, this process is submitted to QBATCH for each type.  As each may take a moment to run, the next must wait to be submitted.  The user will see this screen -
  *PL/480B*  A/R batch payment update                 11/30/16 11:53:49 FKR05101