5/15/2023 0 Comments Quick invoice creation![]() ![]() The subprocess copies purchase order and receiver fields to voucher lines and creates distribution lines, based on either Must be created by the voucher edit subprocess using the PeopleSoft Payables control hierarchy defaults. For all other source transaction types, the payment records Staging tables enable the entry of payment schedule information. ![]() Quick invoices and voucher data that is staged to the voucher Message is entered through the source transaction component. The pre-edit subprocess can create payment schedule records only if payment schedule information such as the bank or a payment If applicable, the subprocess creates control groups, builds miscellaneous charge records if absent (based on business unit The subprocess verifies that voucher headers have voucher lines and that voucher lines have distribution lines. The invoice data from some source transactions receive additional error checks. ![]() It performs header error processing by checking for a valid business unit, invoice ID, invoice date, vendor ID, vendor location,Īddress sequence number, and voucher origin. See Tables That Are Accessed by the Voucher Build Process. Vouchers from prior Voucher Build process instances that have been staged for review and released for processing, as wellĪs vouchers with corrected pre-edit errors, can also be selected for reprocessing and are inserted into the temporary tables The specific source tables and data that the subprocess retrieves depends on the run control selection criteria that you specify It accesses and retrieves invoice data from the source transaction tables or staging tables, and it uses the data to populate The pre-edit subprocess works in the following way: See Understanding Financial Sanctions Validation. You cannot pay these vouchers until the financial sanctions status of the vendor is set to Cleared or Valid. However, the Pay Cycle Application Engine process (AP_APY2015) does not select vouchers for a vendor that has a financial Therefore, you can build vouchers for any vendor with a financial sanctions status of Review or Blocked. The vendor, nor does it validate the vendor against any financial sanctions lists (for example, the Specially Designated Nationals ![]() If financial sanctions validation is enabled, the Voucher Build process does not consider the financial sanctions status of Voucher record sets successfully, it calls the voucher edit subprocess to complete these record sets. Summary Invoice Entry component (VCHR_SUMM_PNL), or that it retrieves from other sources. Record sets from limited information that you enter online using the Quick Invoice Entry component (VCHR_QUICK_PNL) or the The pre-edit subprocess builds skeleton voucher The Voucher Build process comprises two subprocesses, pre-edit and voucher edit. Tables that are accessed by the Voucher Build process. Also, you must modify non-accounts payable voucher source transactions, for example, procurement card invoicesĪnd XML invoices, to account for the new field. Warning! If you add voucher fields to the staging or quick invoice tables, you must add the associated logic to the Voucher Build processĬode line. Therefore, not all voucher fields are part of the staging and quick invoice tables. Transactions originating from third-party systems.ĭue to the scope of the voucher build functionality, PeopleSoft Payables does not deliver all online voucher entry functionalityĪs part of the Voucher Build process. PeopleSoft Payables provides the Voucher Build process to build vouchers in batch from various source transactions, including Run the Voucher Build Application Engine process (AP_VCHRBLD) and review messages. This chapter provides overviews of voucher build processing and voucher build source transactions, lists prerequisites, and ![]()
0 Comments
Leave a Reply. |