Information Systems:Periodic-Calendar Year - Revision history

Jeremym: /* T5 - Statement of Investment Income */

2023-02-01T00:17:52Z

T5 - Statement of Investment Income

Jeremym: /* T5 - Statement of Investment Income */

2023-02-01T00:17:23Z

T5 - Statement of Investment Income

Jeremym: /* T5 - Statement of Investment Income */

2022-02-07T18:54:37Z

T5 - Statement of Investment Income

Jeremym: /* T5 - Statement of Investment Income */

2022-02-07T18:49:46Z

T5 - Statement of Investment Income

Jeremym: /* T5 - Statement of Investment Income */

2022-02-07T18:49:10Z

T5 - Statement of Investment Income

Jeremym: /* T5 - Statement of Investment Income */

2022-02-07T18:48:37Z

T5 - Statement of Investment Income

Norwinu at 20:37, 17 January 2019

2019-01-17T20:37:16Z

Norwinu at 20:36, 17 January 2019

2019-01-17T20:36:50Z

Darrenf: /* T5 - Statement of Investment Income */

2017-01-26T18:29:24Z

T5 - Statement of Investment Income

Norwinu at 17:17, 15 July 2016

2016-07-15T17:17:17Z

New page

=Calendar Year=

==Set up Courier Schedule for the Year==

From the warehouse manager, get the list of days that the warehouse will not be open. Enter these days into file ATLDATEP. Program PLZIU511 (PLZ -- build shipment file for Atlas) will not run if the current date is in this file.

whse menu / configuration / stat holidays no pickups

Press page down to see how the data is entered, then F10 to add.

==Change Atlas Transmission Times When Friday is a Statutory Holiday==

Atlas does a late pickup on Fridays, to take to their depot, and distribute to the drivers on Saturday morning (for Saturday delivery). If the warehouse is closed on Friday, this late pickup will have to be done on Thursday. Which means we will have to do a late transmission as well.

We cannot change the transmission schedule ahead of time, so put reminders in your calendar.

Key in the command WRKJOBSCDE and press enter.

Work with Job Schedule Entries BART
10/14/15 16:53:30

Type options, press Enter.
2=Change 3=Hold 4=Remove 5=Display details 6=Release
8=Work with last submission 10=Submit immediately

Next
-----Schedule------ Recovery Submit
Opt Job Status Date Time Frequency Action Date
_ ATLAS01 SCD USER DEF 06:15:00 *WEEKLY *NOSBM 10/15/15
_ ATLAS02 SCD USER DEF 13:15:00 *WEEKLY *NOSBM 10/15/15
_ ATLAS03 SCD USER DEF 13:35:00 *WEEKLY *NOSBM 10/15/15
2 ATLAS04 SCD *FRI 19:15:00 *WEEKLY *NOSBM 10/16/15
_ DHLINV SCD USER DEF 22:00:00 *WEEKLY *NOSBM 10/14/15
_ ECUREGULAR SCD *THU 21:30:00 *WEEKLY *NOSBM 10/15/15
_ EDI_PO SCD *ALL 07:00:00 *WEEKLY *SBMRLS 10/15/15
More...
Parameters or command
===>
F3=Exit F4=Prompt F5=Refresh F6=Add F9=Retrieve
F11=Display job queue data F12=Cancel F17=Top F18=Bottom

Use option 2 to change job ATLAS04.

Change Job Schedule Entry (CHGJOBSCDE)

Type choices, press Enter.

Job name . . . . . . . . . . . . > ATLAS04 Name
Entry number . . . . . . . . . . > 309408 000001-999999, *ONLY
Command to run . . . . . . . . . CALL PGM(PLCIU511) PARM('AM')

Frequency . . . . . . . . . . . *WEEKLY *SAME, *ONCE, *WEEKLY...
Schedule date . . . . . . . . . *NONE Date, *SAME, *CURRENT...
Schedule day . . . . . . . . . . *FRI *SAME, *NONE, *ALL, *MON...
+ for more values
Schedule time . . . . . . . . . '19:15:00' Time, *SAME, *CURRENT

F3=Exit F4=Prompt F5=Refresh F10=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

Change the schedule day from *FRI to *THU, and press enter. Don't forget the change this back for the following week.

==Copy of Warehouse Balance File==

When program EOMASW runs on January first for December, it creates a copy of SROSRO, and names it SROSROyyyy where yyyy is the calendar year just ending. It also builds the logical file SRBSROyyyy. This allows us to run reports for the auditors.

Confirm that this has been done.

==Check ECU (Electronic Catalogue Update) Calendar==

Every Thursday, a scheduled job builds item files to send to the POS vendors.

Unity / Start uniPharm Extensions / VA Company / UWD Extensions / ECU Catalog Update / Show Calendar

Change 'Display Order' to DATED - date descending.

10/15/15 09:54:01 uniPHARM -- PRODUCTION ECRIQ010/LISTCTL
ECU RUNNING ECU - Show Calendar Master File PRODUCTION 1.00
Display Order Field Test Values
DATED DATE DESCENDING
Date Range Week Status AND
ST 00 00 00 00 AND
Period
RH=Run History WK
MA=Main TR=Transmissions BA=Base File CH=Changes PR=Promo

Reference Week St Start/End Dates SCHED DATE PRICE DATE ADDED DATE
APR08 2022 1580 NP APR 9 22 APR 15 22 APR 08 22 APR 08 22 NOV 07 14
APR01 2022 1579 NP APR 2 22 APR 8 22 APR 01 22 APR 01 22 NOV 07 14
MAR25 2022 1578 NP MAR 26 22 APR 1 22 MAR 25 22 MAR 25 22 NOV 07 14
MAR18 2022 1577 NP MAR 19 22 MAR 25 22 MAR 18 22 MAR 18 22 NOV 07 14
MAR11 2022 1576 NP MAR 12 22 MAR 18 22 MAR 11 22 MAR 11 22 NOV 07 14
MAR04 2022 1575 NP MAR 5 22 MAR 11 22 MAR 04 22 MAR 04 22 NOV 07 14
FEB25 2022 1574 NP FEB 26 22 MAR 4 22 FEB 25 22 FEB 25 22 NOV 07 14
FEB18 2022 1573 NP FEB 19 22 FEB 25 22 FEB 18 22 FEB 18 22 NOV 07 14
FEB11 2022 1572 NP FEB 12 22 FEB 18 22 FEB 11 22 FEB 11 22 NOV 07 14
FEB04 2022 1571 NP FEB 5 22 FEB 11 22 FEB 04 22 FEB 04 22 NOV 07 14 +
F21=Scrn Reset
F3=Exit F5=Refresh . F12=Previous F24=Scrn Save

Make sure the latest date on this file will cover the following year. If not, add more.

Key in GENECUCAL and press F4 to prompt. Start with the week AFTER the last one on the file.

GENERATE ECUCALP FILE (GENECUCAL)

Type choices, press Enter.

STARTING WEEK # . . . . . . . . 1581 Number
# OF WEEKS TO GENERATE . . . . . 300 Number
SCHEDULE DATE - CE . . . . . . . 20 Number
SCHEDULE DATE - YR . . . . . . . 22 Number
SCHEDULE DATE - MO . . . . . . . 04 Number
SCHEDULE DATE - DY . . . . . . . 22 Number

==T5 - Statement of Investment Income==

Finance creates an Excel file, then saves as T5file.csv

Move this to bart / uwd staging / T5 /

Make a copy, and rename it to T5file.csv (after deleting file from last year).

'''Upload to i and build files'''

Start ASW to setup your library list.
On a command line, key in CALL T5PRODCSV and press Enter.
This CL uses program T5PROD to build files T5619P (T619 header file), T5SHRP (T5 shareholder recipient file), and T5UWDP (T5 UWD summary file).

'''Print T5 forms'''

Call program T5PRINT. This will include the form, so prints on regular paper.
It will be directed to your default printer; probably QPRINT. To change it, key in WRKSPLF and press Enter. Find the file TPRINTP, and use option 2 to change it. Press page down, and key ELAHO into the ‘Output queue’. (Maybe STEIN.)
As this is sensitive information, go to the printer and wait for the T5’s.

'''Use WebSmart to build XML file'''

Sign on to infonet.unipharm.com to get a valid log in.
In URL, change ‘in_home’ to ‘t5619list’ (this program is not on a menu).

1. Click the XML icon in the Action column (rightmost icon) next to the T5619P record you would like to generate the return for. This will present a prompt with default IFS location and file name.

2. Click the 'Build XML' button. This calls a program that will build the XML file and save it to the specified IFS location. (this is not the file you need, so continue with these instructions.)

3. The list program will then present a summary indicating the IFS location and file name. Use the 'View File' button to open the XML document in the browser.

4. Use the File menu in the browser to save the document to your local drive, a network drive or you can use the back button to return to the summary. The file currently saved on the IFS is in EBCDIC (I think), so you must save it from here in order to convert it to ASCII and use it.

5. Use the back error to get back to the program, and click on Log Out.

'''Validate the XML file'''

* I think that we only need to do this if either CRA or we, make a change.

XMLMind – Professional edition $300usd ($330usd in Jan 2013)

You can download upgrades for 1 year after purchase. This means, if you purchase on Jan 30, 2013 you can download the upgrade, and process next year’s T5s up to Jan 29, 2014 – without having to pay again!

Original email from them –

Please keep a record of this number for later reference,
since you will need it to download the software.

xe-usr-5.5 distribution includes the following files:

http://www.xmlmind.com/store_download/xe-usr-5.5/xxe-pro-5_5_0-setup-nojvm.exe
(Jan 21 2013 08:30:20 GMT, 51489184 bytes)
Windows auto-installable binary distribution. (Requires a publicly installed Java 1.6+ runtime.)

http://www.xmlmind.com/store_download/xe-usr-5.5/xxe-pro-5_5_0-setup.exe
(Jan 21 2013 08:30:20 GMT, 72841280 bytes)
Windows auto-installable binary distribution, bundled with a private Java 1.6.0_38 runtime.

http://www.xmlmind.com/store_download/xe-usr-5.5/xxe-pro-5_5_0.dmg
(Jan 21 2013 08:30:19 GMT, 54611291 bytes)
Mac OS X native binary distribution. Requires Mac OS X 10.6 (Snow Leopard) or 10.7 (Lion) or 10.8 (Mountain Lion) and latest Apple Java 1.6.

http://www.xmlmind.com/store_download/xe-usr-5.5/xxe-pro-5_5_0.tar.gz
(Jan 21 2013 08:30:20 GMT, 51406214 bytes)
Distribution compressed with tar+gzip.

http://www.xmlmind.com/store_download/xe-usr-5.5/xxe-pro-5_5_0.zip
(Jan 21 2013 08:30:20 GMT, 54769987 bytes)
Distribution compressed with zip.

In order to be able to download these files,
when prompted by your Web browser, please enter:

sheilav@unipharm.com

as the requested username and enter:

YoNyTqD

as the requested password.

Your license grants you free access to new versions of the product
until January 30, 2014.
See <http://www.xmlmind.com/xmleditor/upgrade.html>
for the upgrade procedure.

For technical support on this product post a message to
<xmleditor-client@xmlmind.com>. Please keep a record of this address
since it is reserved for registered licensees and is not
advertised anywhere.

To pay for and download a new version –

http://www.xmlmind.com/xmleditor/buy.html

If you download a new version, make sure all the schemas (is that the plural of schema, or is it already plural?) (.xsd) are in bin folder.

On Pat’s computer, the W3C XML Schema is in –

C:\Documents and Settings\patp\My Documents\T5\XML Mind Editor Professional

It is also in –

Superserver\tech\common\iSeries\T5\ XML Mind Editor Professional

To validate –
- Copy the XML to be validated into the folder containing the XL schema.
- Run XMLmind XML Editor
- Click on ‘File’, ‘Open’, the XML file in the schema folder (from above), and then on ‘Open’
- The window will contain a list of errors if there are any, or the XML. If
there are no errors, the bottom line will show “Z:\Common\iSeries\T5\XML
Mind Editor Professional\T5619LIST.xml is valid”

'''Send to CRA website'''

Nancy does this step.

Go to https://apps.cra-arc.gc.ca/ebci/leb0/upload/T05iDisclaimerRender-e
and click on ‘I agree’.

Key in Account number and Web Access Code to complete the identification section.

Find the location of your electronic information return and attach .

Submit your electronic information return (XML format).

Keep the submission number provided on the confirmation of receipt page.

'''More Info on Printing T5’s'''

The T5 form is in an overlay, which is then included in the printer file. The form and the content is then printed together. If the form changes, the overlay will have to be changed.

Download pdf of T5 from CRA web site (in this example, it is t5-flat-10b in H:\Software Library \ T5 forms)

See IBM Document Number 5184341 Creating AFP Resources Using the IBM AFP Printer Drivers

Create a printer that prints to a file (T5 AFP)
Print pdf to the T5 printer (produces t5-flat-10b.prn or t5-flat-10b-p1.prn)

'''Upload an overlay to the System i'''

- iSeries Navigator / AFP Manager / bottom right, “Import an overlay”

- T5OVL should not exist before the upload, as it will be created

[[File:T5-1.jpg]]

'''Test overlay on System I'''

OVRPRTF FILE(QPDCDEVA) DEVTYPE(*AFPDS) FRONTOVL(UWDASWPRDD/T5OVL) HOLD(*YES) SAVE(*YES) OVRSCOPE(*CALLLVL)
prtdevadr ctl01

wrksplf, 8=Attributes – to look at splf QPDCDEVA

OVRPRTF FILE(T5PRINTP) DEVTYPE(*AFPDS) CPI(15) FRONTOVL(T5OVL) HOLD(*YES) SAVE(*YES) OVRSCOPE(*CALLLVL)

can specify FONT in the ovrprtf

then call print program, send output to elaho

'''If overlay cannot be created -'''

Print form (pdf from CRA website).

Recompile T5PRINTP without the overlay.

Run T5PRINT, and print. Output will be content only; without the form.

Put pages back into printer, and photocopy form over top of the printed output (will have to figure out in what orientation to load the pages).

@@ Line 297: / Line 297: @@
 The Revenue Canada T5 spec file has changed again for 2022.  As a result the following changes must be made to the file in order for it to pass validation:
  <sbrn_root></sbrn_root> has the trust number showing, which is Box 22 on the T5 slip and known as the Recipient Identification Number.  This needs to be changed to: <rcpnt_tr_acct_nbr></rcpnt_tr_acct_nbr>
  <rcpnt_tr_acct_nbr></rcpnt_tr_acct_nbr> is represented by a T00000000 which needs to be changed to: <slp_rcpnt_bn></slp_rcpnt_bn>

← Older revision		Revision as of 00:17, 1 February 2023
Line 295:		Line 295:
	What has been changed is the <sbrn_root>, which is shown on every slip needs to be changed to <rcpnt_tr_acct_nbr>.		What has been changed is the <sbrn_root>, which is shown on every slip needs to be changed to <rcpnt_tr_acct_nbr>.

		+	The Revenue Canada T5 spec file has changed again for 2022. As a result the following changes must be made to the file in order for it to pass validation:
		+	<sbrn_root></sbrn_root> has the trust number showing, which is Box 22 on the T5 slip and known as the Recipient Identification Number. This needs to be changed to: <rcpnt_tr_acct_nbr></rcpnt_tr_acct_nbr>
		+	<rcpnt_tr_acct_nbr></rcpnt_tr_acct_nbr> is represented by a T00000000 which needs to be changed to: <slp_rcpnt_bn></slp_rcpnt_bn>

@@ Line 287: / Line 287: @@
 '''More Info on Validating XML Files'''
-The Revenue Canada T5 spec was changed for 2020.  As a result, the XML file that is produced by the InfoNet program will not pass validation and will need to be modified before it will be accepted by Revenue Canada.  I have been unable to use Notepad++ to perform proper validation on the XML file.  It does not seem to be able to pick up the errors properly.  XML Mind, as discussed above, I'm unable to install for whatever reason.  I was able to install XML Language Support by Red Hat on Visual Studio Code and this seems to catch the errors when I open the XML file.  It's important to note that the file must be copied into the .xsd schema folder that you download and unzip from Revenue Canada for this to work.   The schema uses multiple files so they must all be present in the same directory for the validation process to work.
+The Revenue Canada T5 spec was changed for 2020.  As a result, the XML file that is produced by the InfoNet program will not pass validation and will need to be modified before it will be accepted by Revenue Canada.  I have been unable to use Notepad++ to perform proper validation on the XML file.  It does not seem to be able to pick up the errors properly.  XML Mind, as discussed above, I'm unable to install for whatever reason.
 What has been changed is the <sbrn_root>, which is shown on every slip needs to be changed to <rcpnt_tr_acct_nbr>.

← Older revision		Revision as of 18:49, 7 February 2022
Line 286:		Line 286:

	'''More Info on Validating XML Files'''		'''More Info on Validating XML Files'''
		+
	The Revenue Canada T5 spec was changed for 2020. As a result, the XML file that is produced by the InfoNet program will not pass validation and will need to be modified before it will be accepted by Revenue Canada. I have been unable to use Notepad++ to perform proper validation on the XML file. It does not seem to be able to pick up the errors properly. XML Mind, as discussed above, I'm unable to install for whatever reason. I was able to install XML Language Support by Red Hat on Visual Studio Code and this seems to catch the errors when I open the XML file. It's important to note that the file must be copied into the .xsd schema folder that you download and unzip from Revenue Canada for this to work. The schema uses multiple files so they must all be present in the same directory for the validation process to work.		The Revenue Canada T5 spec was changed for 2020. As a result, the XML file that is produced by the InfoNet program will not pass validation and will need to be modified before it will be accepted by Revenue Canada. I have been unable to use Notepad++ to perform proper validation on the XML file. It does not seem to be able to pick up the errors properly. XML Mind, as discussed above, I'm unable to install for whatever reason. I was able to install XML Language Support by Red Hat on Visual Studio Code and this seems to catch the errors when I open the XML file. It's important to note that the file must be copied into the .xsd schema folder that you download and unzip from Revenue Canada for this to work. The schema uses multiple files so they must all be present in the same directory for the validation process to work.

@@ Line 283: / Line 283: @@
 Put pages back into printer, and photocopy form over top of the printed output (will have to figure out in what orientation to load the pages).
 '''More Info on Validating XML Files'''
@@ Line 288: / Line 289: @@
 What has been changed is the <sbrn_root>, which is shown on every slip needs to be changed to <rcpnt_tr_acct_nbr>.

← Older revision		Revision as of 18:48, 7 February 2022
Line 283:		Line 283:

	Put pages back into printer, and photocopy form over top of the printed output (will have to figure out in what orientation to load the pages).		Put pages back into printer, and photocopy form over top of the printed output (will have to figure out in what orientation to load the pages).
		+
		+	'''More Info on Validating XML Files'''
		+	The Revenue Canada T5 spec was changed for 2020. As a result, the XML file that is produced by the InfoNet program will not pass validation and will need to be modified before it will be accepted by Revenue Canada. I have been unable to use Notepad++ to perform proper validation on the XML file. It does not seem to be able to pick up the errors properly. XML Mind, as discussed above, I'm unable to install for whatever reason. I was able to install XML Language Support by Red Hat on Visual Studio Code and this seems to catch the errors when I open the XML file. It's important to note that the file must be copied into the .xsd schema folder that you download and unzip from Revenue Canada for this to work. The schema uses multiple files so they must all be present in the same directory for the validation process to work.
		+
		+	What has been changed is the <sbrn_root>, which is shown on every slip needs to be changed to <rcpnt_tr_acct_nbr>.
		+

	[[Category: I.T. Periodic Tasks]]		[[Category: I.T. Periodic Tasks]]

← Older revision		Revision as of 20:37, 17 January 2019
Line 285:		Line 285:

	[[Category: I.T. Periodic Tasks]]		[[Category: I.T. Periodic Tasks]]
		+	[[Category: Unlisted Infonet Programs]]

← Older revision		Revision as of 20:36, 17 January 2019
Line 283:		Line 283:

	Put pages back into printer, and photocopy form over top of the printed output (will have to figure out in what orientation to load the pages).		Put pages back into printer, and photocopy form over top of the printed output (will have to figure out in what orientation to load the pages).
		+
		+	[[Category: I.T. Periodic Tasks]]

← Older revision		Revision as of 18:29, 26 January 2017
Line 147:		Line 147:
	4. Use the File menu in the browser to save the document to your local drive, a network drive or you can use the back button to return to the summary. The file currently saved on the IFS is in EBCDIC (I think), so you must save it from here in order to convert it to ASCII and use it.		4. Use the File menu in the browser to save the document to your local drive, a network drive or you can use the back button to return to the summary. The file currently saved on the IFS is in EBCDIC (I think), so you must save it from here in order to convert it to ASCII and use it.

		+	5. Use the back error to get back to the program, and click on Log Out. At this point give the paper T5 forms to Nancy and verify that the XML file has the correct summary which is located at the very bottom of the file. Nancy should open the XML file and scroll all the way to the bottom and compare the dollar amounts to what she has in her source spreadsheet. If good then she can continue. If the numbers don't match then the numbers on the source spreadsheet need to be formatted as text instead of numbers with 2 decimal places, then resaved as a new CSV and the process started again to generate the XML and paper forms.
−	5. Use the back error to get back to the program, and click on Log Out.

	'''Validate the XML file'''		'''Validate the XML file'''