12.07.2015 Views

Using Accounts Payable

Using Accounts Payable

Using Accounts Payable

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Vouchers: Transferring Voucher Items to Fixed AssetsThe ITM.FXA.TRANSFER.STATUS field uses one of three validation codes:• R – Ready for Transfer• I – In Use• T – TransferredTechnical Tip: The ITM.FXA.TRANSFER.STATUS validation codesare stored in the FXA.TRANSFER.STATUSES record of theCF.VALCODES file, and cannot be modified.Colleague updates the ITM.FXA.TRANSFER.STATUS field of the ITEMSfile with the appropriate validation code throughout the AP-to-FX transferprocess.Step 2: Run the Fixed Assets Transfer Report(FXTR)The FXTR process creates an ITEMS.ID saved list of selected voucher lineitems whose ITM.FXA.TRANSFER.STATUS is “R” (Ready for Transfer).Step 3: Run the Fixed Assets - AP Interface (FXAP)ProcessThe FXAP process uses the ITEMS.ID saved list to create one or morebatches, and stores these batches in the FXA.BATCH file. Colleague updatesthe ITM.FXA.TRANSFER.STATUS field for each batched item record to “T”(Transferred). The FXAP process also creates a record in the FXA.ITEMS filefor each fixed asset line item that is displayed on the FX-AP Interface List(FAIL) form.Note: Each batch can store a maximum of 300 line items. If youtransfer more than 300 line items at one time, Colleague creates asmany batches as necessary to accommodate the additional line items.Step 4: Run the FX - AP Interface List (FAIL) ProcessAccess a batch of line items through the FAIL form. You can create or modifyan asset record for a line item or delete a line item on the FAIL form.Colleague removes the item record from the FXA.ITEMS file (thus alsoremoving it from the FXA.BATCH file) when the asset transfer is complete orit is removed.294 <strong>Using</strong> <strong>Accounts</strong> <strong>Payable</strong>, June 19, 2009© 2009 Datatel, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!