How to perform ‘File Transfer’ in R-Supply …

Background Knowledge:

What is ‘File Transfer’ in R-Supply? File Transfer in R-Supply is the process of moving or transferring file or files from/to NTCSS Server. Several R-Supply Batch Jobs requires input (i.e. Incoming Status for Supply/REQ/LOGREP, ASI Process, Monthly Change Notice, etc.). On the other hand, some R-Supply Batch Jobs produces electronic output and/or reports that need to be downloaded from the Server. File or files are uploaded to the NTCSS Server when processing incoming Supply Status, LOGREP, or Change Notices, etc. and files are downloaded from the Server to provide electronic copy of the output to the customer or send MILSTRIP through SALTS/DAAS or attaching electronic copy of the output to an email. File Transfer process is almost done in a daily basis.

Procedures:

To perform File Transfer (Upload or Download), follow the steps listed below:

A. Uploading File to Server… the most common process that File Transfer is performed is processing ‘Incoming Status for Supply (Batch Job JSS220)’. For demonstration purposes, we will use this process “Incoming Status for Supply/Referral/REQ/RQN/LOGREP” Batch Job JSS220.

Step #1: Prepare the File Input. Download supply status from SALTS or from email and save it into

CD or in the Hard Drive. Make sure to verify or preview the format of the transactions to ensure validity of the input.

Step #2: Logon to R-Supply. GoTo: File>Utilities>File Transfer>Batch File Transfer. In Batch File

Transfer Screen, Select ‘Transfer to Server’ radio button.

  Note: There is a checkbox ‘Append to existing file’ underneath the Transfer to Server radio button. This option is used when uploading additional transactions into an existing process input file… meaning that you have uploaded an input file for the process, however, you have not run or started the Batch Job (in this case, JSS220). Two hours passed, you downloaded additional supply status from SALTS and you want the additional supply status included in the Batch Job JSS220. In this situation, upload the additional transactions to same process (JSS220) by activating or selecting the ‘Append to existing file’ checkbox. The additional inputs will be appended to the previous transactions that have been previously uploaded to process JSS220.

Step #3: Click the ‘Process’ dropdown menu and select the process (In this case, JSS220).

Step #4: Enter the path and filename of the source file (File to be uploaded) on the ‘File Name’

data field or Click the ‘Browse’ button to look for the location of the source file (i.e. Drive E, then select the file). Select the Drive and filename of the file. (Notice when you select the file from the source Drive, the filename is displayed on the ‘File Name’ data field.

Step #5: Click ‘Open’ button. (Notice the data on the “Transfer to Server” block). On the ‘Process’

data field, the name of the Process appears (In this case, ‘Incoming Status for Supply/Referral/…) and the filename of your source file on the ‘File Name’ data field.

Step #6: Click ‘Apply’ icon to start the process of ‘File Transfer’. In a few seconds, you will see

an ‘Alert’ window to display the alert message saying ‘File Transfer, Completed Successfully /h/data/local/SUP1BT/tape_in/JSS220 created’. Click the ‘OK’ button and it will take you back to the ‘Batch File Transfer’ window.

  Note: It is highly recommended to check your input transactions to ensure all transactions have been uploaded for input to the selected process (Batch Job). You should count the number of input from the source file and compare that count to the uploaded file. To check your input, GoTo: File> Utilities>Batch Review then Select ‘Input Files’ radio button. The ‘Select Server File’ pop-up window displays the available batch process. Select the batch process or file and click ‘OK’ button or double click the file or process to display the input transactions. Count the number of transactions and compare this to the count from your source file. The count should match… if not, you may repeat the ‘File Transfer’ from start to finish. It will not hurt by doing so. For some reason, the program will sometimes drop some of your transactions during the file transfer process. Click ‘Cancel’ button to close the screen and proceed to start the Batch Job whatever process you are currently doing. Most of the R-Supply Batch Jobs that requires input are started from the “Predefined Parameters” located at: Site>Management>Site Internal>Batch Job Scheduling> Predefined Parameters. (See “How to submit and approve Batch Jobs...)

B. Downloading File from Server… the most common process that you must perform download file from the Server is processing ‘Release Outgoing Transactions’ (i.e. Requisitions, Outgoing Status, DLR Tracking Responses, DRA/DRB, MFCS/TIR, etc.). For demonstration purposes, we will use ‘Requisitions’ download (Batch Job JSL319).

After processing “Requisition Release (Batch Job JSL319)”, an electronic copy of the Requisitions (A0_) were created and written in directory: /h/data/local/SUP1BT/tape_out. The file must be downloaded for submission to Supply system via SALTS or other available means of transmission.

To perform file download, follow the steps listed below:

Step #1: Logon to R-Supply. GoTo: File>Utilities>File Transfer>Batch File Transfer. Select

‘Receive From Server’ radio button.

  Note: Notice the two or four checkboxes (Depending on R-Supply release) ‘MFCS Download’, ‘Stars Download’, ‘SWMS’ and ‘Archive Purge’ underneath the ‘Receive From Server’ radio button. The MFCS Download checkbox will be activated if you are downloading the daily MFCS TIR Report. Stars Download checkbox is activated if you are downloading your weekly Transmittal (Obligations) to DFAS. SWMS checkbox (Applicable to T-AKE type ship only) will be activated if you are downloading the output from the “Outgoing SWMS (Batch Job JSS320). Archive/Purge checkbox will be activated if you are downloading archive or purge files.

Step #2: Select ‘File’ radio button (Normally is the default).

Step #3: Type-in the Batch Job Number (In this case, JSL319-XXXX-XXX), the Batch Job

Number that created the file.

Step #4: Select the Drive radio button where you want the file to be written.

Step #5: Click ‘Apply’ icon to start the process.

  Note: An ‘Alert’ window will pop-up to display the message saying “File Transfer Successfully Completed…” It is highly recommended to verify the output and compare it to the downloaded file. To verify the output from the directory: /h/data/local/SUP1BT/tape_out, GoTo: File>Utilities>Batch Review and Select ‘Output Files’ radio button. Select the Batch Job Number and Click ‘OK’ button. The output file will be displayed. Count the transactions and compare this count to the downloaded transactions. It should match. If not, repeat the download process.

Step #6: Clean up the downloaded file. Normally, the Batch Job number will be written on the

first line. Also, at the end of the file you may find some strange data. You must remove these entries before transmitting or sending the transactions through SALTS or other means of transmission.

Step #7: Transmit data. It is highly recommended to monitor the return copy of the message after

transmission to ensure the message was actually transmitted out of the Ship or Activity.

For sample demonstration: Click here and follow the menu path given in procedures.

Any questions, feedback or comments, email Lonnie Auza.