Thank you in advance".
Likewise, you might set up the payroll department as a separate origin so that users can add only vouchers for employees.Image: Voucher Origin - Vouchering Options 1 page.Each voucher entered into PeopleSoft Payables must come from a valid origin.Selecting this option directs the system to the next higher level in the control hierarchy to obtain the value.An origin identifies a specific entry point for online or batch entry, such as a department, division, company, or specific user.You can also use these codes to identify departments or groups within the organization.This example illustrates the fields and controls on the Voucher Origin - Vouchering Options 1 page.Use the Voucher Origin - Vouchering Options 1 page (origin_vchr2) to specify voucher approval, match delay days, voucher currency, and document sequencing settings for the voucher origin.
While creating vouchers it is showing an message that "Origin missing on your operator profile.To define origin codes, use the Origin Codes component (PO_origin_codes).When you set up processing options in levels below the business units, the first option for most functions is default.This sharing enables the PeopleSoft Payables Voucher Build process to build vouchers from PeopleSoft Purchasing receipts, non-purchase order receipts, purchase orders, and contracts, regardless of the origin code default values.Origin codes enable you to group the transactions, and they provide an additional level from which information can appear by default in transactions.Origin is required in order to enter vouchers".Each PeopleSoft Payables user must be associated with an origin in order to process vouchers.In the Payables Options component, you define these options for the business unit; here, you define them for the voucher origin.Origin codes identify places in the system from which transactions originate.This section lists the page used to define origin codes.