linear_scale How To

Create and Upload Feeder Journals

Certain organizations that have a high volume of iJournal transactions are authorized to do feeder journals.

  1. Open iJournals Upload Template in Excel
  2. Read the Instructions included in the file 
  3. Print a copy for future reference

  1. Delete rows 43-166 and rows 1-37
  2. Enter Feeder Date (DD-MMM-YYYY) in cell B1
  3. Enter Period (MMM-YYYY) in cell C1
  4. Enter "Feeder" as the Category in cell D1
  5. Enter Short Title in cell E1
  6. Enter Debit Total in cell F1
  7. Enter Feeder ID in G1
  8. Enter feeder purpose in cell B2 (EXPL)

  1. Enter the first Project in cell B3
  2. Enter the Task in cell C3
  3. Enter the Fund/Award in cell D3
  4. Enter the Exp. Type/Object Code in cell E3
  5. Enter the Exp. Item Dt in cell F3
  6. Enter Employee ID (if applicable) in cell G3
  7. Leave column H blank
  8. Enter Line Description in cell I3
    Line description is displayed on the Expenditure Detail Report.
  9. If the line is a debit, enter Debit Amount in cell J3
  10. If the line is a credit, enter Credit Amount in cell K3
  11. Insert new DETL rows as needed and repeat until all of the debits and credits have been entered
  12. The last two cells of the file must contain END and EOF (refer to the template in Step 1)

  • PC: Save the upload spreadsheet as a tab-delimited text file.
  • MAC: Save the upload spreadsheet as a Text (Windows) file.

  1. Enter ofweb.stanford.edu in the browser
  2. Click Login
  3. As prompted, log in using SUNet ID and password

  1. Select SU iJournals Specialist or SU iJournals Central 
  2. Select iJournals Home 

  1. Select Feeder/Upload on the left side of the Home page to begin the process
  2. Select Browse and locate the file to be uploaded on the Upload a File page
  3. Select Upload
  4. Select Home tab to return to the Feeders Requiring Action section

  1. Select the Excel icon next to the feeder file name
  2. Verify the data
  3. Close spreadsheet when finished reviewing data

  1. Verify that the Feeder is in Validated status in the Feeders Requiring Action section
  2. Select Submit
    • A workflow notification will be sent to the business owner and feeder owners for approval.

Approval of feeders requiring specific timing for posting (PSOFT, UASRV, PYR01, PYMON, EFAO, EGFSS, EGFSM, EGFSN and ESFS) will generate a workflow notification to Systems and Reporting Operations (S&RO) for control of posting time. 

The Status value in the Feeders Requiring Action section reflects one of the following:

  • Processing – System is validating feeder lines
  • Validated – Feeder has been validated and queued for submittal
  • Invalid – Invalid feeder lines must be forced using the Force PTA option, or feeder file must be purged and resubmitted

Feeders with a Status of Validated or Invalid contain a live link. Selecting the link will allow you to take action on the selected feeder. If you wish to take action on multiple feeders, refine your Status search to Validated or Invalid. Refer to How To: Search Feeder Journals.

Validated Status – Submit Feeder for Approval

The daily upload, validate and approval deadline for same-night posting is 6:30 p.m.

  1. Select Validated under Status column
    You will be redirected to the Feeder Inquiry tab > Feeder Management section.
  2. Select the checkbox for the appropriate feeder
  3. Select Submit to route for approval
    • Feeder originator cannot approve his/her own uploaded feeders.
    • In Feeder Management – if the Submit button is not available for selection, this is an indicator that the period provided for the selected feeder is not in the current open month, you have a feeder with an invalid status and/or the daily feeder posting window has closed.
    • Approval of feeders requiring specific timing for posting (PSOFT, UASRV, PYR01, PYMON, EFAO, EGFSS, EGFSM, EGFSN, and ESFS) will generate a workflow notification to Systems and Reporting Operations (S&RO) for control of posting time.
  4. Select OK in the confirmation pop-up window
Validated Status – Purge a Feeder

Examples why a user may consider (or need to) purge a Valid feeder:

  • Format issues with the file
  • Data issues with the file
  • Force button is not available for the Feeder ID
  1. Select Validated under Status column
    • You will be redirected to the Feeder Inquiry tab > Feeder Management section.
  2. Select the checkbox
  3. Select Purge 
  4. Select OK in the confirmation pop-up window
    Purged feeders will no longer be retrievable.
Invalid Status – Purge a Feeder

Examples why a user may consider (or need to) purge an Invalid feeder:

  • The GL Period used in the uploaded feeder is no longer open, thus, the only option at this point is to purge the feeder and re-upload with the current open GL Period.
  • Feeder was erroneously uploaded multiple times.
  • User notices information that should not be included in the file.
  1. Select Invalid under Status column
    • You will be redirected to the Feeder Inquiry tab > Feeder Management section.
  2. Select the checkbox
  3. Select Purge 
  4. Select OK in the confirmation pop-up window
    Purged feeders will no longer be retrievable.
Invalid Status – Force a Feeder

The Force button is available and enabled for a Feeder ID that has been set up with an alternate PTA.

  1. Select Invalid under Status column
    You will be redirected to the Feeder Inquiry tab > Feeder Management section.
  2. Select the checkbox
  3. Select Force 
  4. Select OK in the confirmation pop-up window
    The validation process will restart, and upon completion, the Feeder status will change to Validated or Invalid.
Rejected Status – Purge a Feeder

Feeder was rejected by the approver.

  1. Select Rejected under Status column
    • You will be redirected to the Feeder Inquiry tab > Feeder Management section.
  2. Select the checkbox
  3. Select Purge 
  4. Select OK in the confirmation pop-up window
    Purged feeders will no longer be retrievable.

  1. Click Return to Portal
  2. Click Logout
What Happens Next?
Last Updated: Aug 28, 2020

Questions?

S&RO (Systems and Reporting Operations)
arrow_upward
Back to Top