Procurement Attribute Verification via Segmented Modules
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional procurement applications require significant time and cost to redesign when new attributes need to be verified, as existing attributes may only be developed after deployment, making it inefficient to support emerging verification needs.
Innovation Solution
A method and system for verifying a target attribute of a company profile record in a procurement application, involving configuring validity attributes, authenticating users, and prohibiting modifications to invalid requisition objects, using modules such as company profile configuration, user profile verification, and requisition object verification, to enhance the software without full redesign.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the procurement application is redesigned to support verification of a new attribute, then the application can verify the new attribute, but the redesign demands a lot of time and is very costly
Solution Approach 1:
The patent segments the verification functionality from the core procurement application by introducing separate verification modules (company profile verification module, user profile verification module, requisition object verification module) that operate independently. These modules verify attributes without requiring redesign of the main application, thus resolving the contradiction between adding verification capability and avoiding redesign time costs.
Solution Approach 2:
The patent introduces verification modules as intermediary components between the user and the procurement application. These modules act as mediators that handle attribute verification independently, allowing the core application to remain unchanged while still providing verification functionality, thereby eliminating the need for time-consuming redesign.
2Reliability
If the procurement application is redesigned to support verification of a new attribute, then the application can verify the new attribute, but the redesign is very costly
Solution Approach 1:
By segmenting verification functionality into separate modules, the patent avoids the high cost of redesigning the entire procurement application. Each verification module is an independent, manageable component that can be developed and maintained separately, significantly reducing development costs compared to full application redesign.
Solution Approach 2:
The verification modules are designed to be universal and can verify multiple different attributes (company profile attributes, user profile attributes, requisition object attributes) using the same underlying mechanism. This multi-functionality eliminates the need for separate development efforts for each attribute type, thereby reducing overall development costs.
3Productivity
If attributes are developed only after the procurement application is deployed, then the application can be deployed quickly, but the application cannot verify new attributes without full redesign
Solution Approach 1:
The patent implements preliminary action by pre-configuring verification rules and validity criteria in the verification modules before actual verification is needed. The modules are pre-established with the capability to verify various attributes, allowing the system to quickly adapt to new verification requirements without redesign, thus maintaining both fast deployment and high adaptability.
Solution Approach 2:
The verification modules are designed to be dynamic and configurable, allowing verification rules and attributes to be modified without changing the core application structure. This dynamic capability enables the system to quickly adapt to new verification needs while maintaining rapid deployment speed, resolving the contradiction between deployment speed and adaptability.
Data Source
AI summary
A method and system. It is ascertained that a database stores the company profile record including the target attribute and a validity attribute associated with the target attribute. The validity attribute has a VALID or INVALID value respectively indicating that the target attribute in the company profile record has a valid or invalid value within the database. It is insured that the database stores a first and second user profile record, that a first user of a requisition transaction corresponds to the first user profile record, that the first user profile record includes the target attribute having a value identical to a value of the target attribute of a first company profile record associated with a first company represented by the first user, and that the validity attribute of the first company profile record has the VALID value. A requisition object record corresponding to the requisition transaction is verified.