How does GFEBS prevent duplicate Purchase Requisitions?

The correct answer illustrates that GFEBS employs validation checks for existing requisitions as a means to prevent duplicates. This process works by systematically reviewing entered requisitions against those already in the system, ensuring that if a requisition with the same details (such as vendor, items requested, or total amount) already exists, the system will flag it. This proactive approach is efficient because it helps maintain the integrity of the purchasing process, minimizing redundancy and potential confusion that can arise from having multiple requisitions requesting the same items or services.

The other methods mentioned, such as changing requisition IDs automatically or limiting the number of requisitions a user can create, do not directly address the issue of duplicates in the same manner. Automatic ID changes might lead to complications in tracking requisitions accurately over time. Similarly, capping the number of requisitions a user can create does not inherently prevent duplicate entries from being attempted; it merely restricts the volume of submissions. Manager oversight on all submissions might help catch duplicates at a later stage but is not as effective as real-time validation checks in preventing them from occurring in the first place. Thus, the validation checks are the most directly applicable mechanism for preventing duplicate purchase requisitions in the system.