Abstract: A method for verifying a target attribute of a company profile record for a procurement application. 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.

Abstract: A method for verifying a target attribute of a company profile record for a procurement application. 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.

Abstract: A system and associated method for verifying an attribute in records for a procurement application. The procurement application employs a database having a company profile record, a user profile record, and a requisition object record, among which share a company_code attribute as a target attribute that is desired to be valid. The company profile record has a validity attribute, and the requisition object record has a validity flag, to indicate validities of the value for the target attribute in respective record. A company profile configuration module configures the company profile record. A user profile verification module prohibits a user without a valid user profile from accessing the procurement application. A user profile cleanup program removes invalid user profile records from the database. A requisition object verification module checks out valid values for the company_code attribute from the company profile records and blocks modification to invalid requisition objects.

Abstract: A purchasing method and system. The method includes purchasing method comprising generating by said computing system a database table. The database table comprises catalog purchase types for items available for purchase. An entity profile associated with an entity is generated. The entity profile is associated with entity allowable catalog purchase types selected from the available catalog purchase types in the database table. A catalog profile is generated. The catalog profile is associated with the entity profile. A user profile associated with the entity profile is generated. The user profile is associated with the entity allowable catalog purchase types. Specified catalogs are identified and presented to a user. The user profile is comprised of a default purchase type and additional user related details. The specified catalogs are associated with the default purchase type, the user profile, the entity profile, and the catalog profile.

Abstract: A system and method for keeping ledger accounts in synchronization between a back-end procurement system and a front-end requisition and catalog system. An extract utility extracts a file of general ledger (G/L) accounts, including account code, description, and company code, from a chart of accounts in the back-end and transfers it to the front-end, where it is updated by an update utility to include company group code from a company group table and then loaded into a data store of valid general ledger accounts. Maintenance of the front end data store of valid accounts includes pushing to all companies in a company group ledger code entered with respect to any one of the companies in that group.

Abstract: A system and associated method for verifying an attribute in records for a procurement application. The procurement application employs a database having a company profile record, a user profile record, and a requisition object record, among which share a company_code attribute as a target attribute that is desired to be valid. The company profile record has a validity attribute, and the requisition object record has a validity flag, to indicate validities of the value for the target attribute in respective record. A company profile configuration module configures the company profile record. A user profile verification module prohibits a user without a valid user profile from accessing the procurement application. A user profile cleanup program removes invalid user profile records from the database. A requisition object verification module checks out valid values for the company_code attribute from the company profile records and blocks modification to invalid requisition objects.

Abstract: A purchasing method and system. The method includes purchasing method comprising generating by said computing system a database table. The database table comprises catalog purchase types for items available for purchase. An entity profile associated with an entity is generated. The entity profile is associated with entity allowable catalog purchase types selected from the available catalog purchase types in the database table. A catalog profile is generated. The catalog profile is associated with the entity profile. A user profile associated with the entity profile is generated. The user profile is associated with the entity allowable catalog purchase types. Specified catalogs are identified and presented to a user. The user profile is comprised of a default purchase type and additional user related details. The specified catalogs are associated with the default purchase type, the user profile, the entity profile, and the catalog profile.

Abstract: A system and method for keeping ledger accounts in synchronization between a back-end procurement system and a front-end requisition and catalog system. An extract utility extracts a file of general ledger (G/L) accounts, including account code, description, and company code, from a chart of accounts in the back-end and transfers it to the front-end, where it is updated by an update utility to include company group code from a company group table and then loaded into a data store of valid general ledger accounts. Maintenance of the front end data store of valid accounts includes pushing to all companies in a company group ledger code entered with respect to any one of the companies in that group.

Abstract: A system and method for client/server communications, the method including the steps of loading to a client browser a frame set including a function frame and a content frame; loading application code to the function frame; and responsive to user interaction with the content frame, executing the application code. The frame set may also include navigation frame and a data accumulation frame. By using the frame set to store executable application code, collect and store data, and interact with a user, an application may be executed at a client browser substantially without client/server interaction beyond initializing the frames and communicating the end results.

Abstract: A system and method for organizing program code and database objects implemented within an enterprise server in support of the accounting and/or procurement systems of a plurality of customer companies. The customer companies are organized into groups of companies having the same accounting rules, and a company grouping code assigned to each company group. Responsive to input through a browser of a requisition request and user ID including a password, a user profile database is accessed to determine the user's company grouping code. Responsive to the company grouping code, a URL or other type of program call to company specific accounting rules is generated to apply appropriate accounting procedures and program logic. Responsive to the program logic and accounting rules accessed by, for example, that URL, the requisition request is applied and validated against company specific data in a common database.

Abstract: A system and method for sharing data from separate servers between browser frames. A first server opens a client browser frame set and loads data to a first frame. A second server is called from the first frame to open a window. Responsive to post command issued from the window, environment variables are passed from the second server to the first server and loaded data from the environment variables by the first server to a second frame of the frame set. Thereafter, data obtained from a second server, which is loaded in the second frame of the frame set, is available to the first frame.

Abstract: A method for making a printed circuit board with a flush surface land begins by forming a multi-layer printed circuit board with a recess in a surface dielectric layer. Then, a hole is drilled into or through the printed circuit board; the hole communicates with the recess. After the recess is formed, a conductive material is provided in the recess to form a surface land and provided on an inner surface of the hole to form a plated hole which is electrically connected to the surface land. The conductive material in the recess has a thickness substantially equal to a depth of the recess such that the surface land is flush with an adjacent surface of the dielectric surface layer.