An ERP is business software application or series of applications, which facilitate the daily operations of business. An ERP an be commercial-off-the-shelf (COTS) applications (which may or may not be customized) or custom built (home grown) by the business and/or assemblages of different vendor applications and/or models. ERP applications dules from a variety of vendors.
Common ERP Major Functions
ERP application software typically support these major business operations:
Financials Management system (FMS)
FMS supports accounting, consolidation, planning, and procurement.
Customer Relationship Management (CRM)
CRM facilitates customer interactions and data throughout the customer lifecycle, with the goal of improving business relationships with customers, assisting in customer retention and sales growth.
Converting a timestamp to date in PeopleSoft Query seems to be a common item, which I have helped others with, to the point that I kept a personal note on the coding logic. So, I thought I would post this quick note in case it may be useful to someone. This item would seem to be straight forward, however, PS query tries to help you with the process, so, some experimentation is usually involved to get the code to out just right.
Here is a sample expression I use for the timestamp to date conversion in PS Query.
Create an expression with an Expression Type of “Number”
While PeopleSoft PeopleTools Application Designer is the best way to validate query migrations, sometimes a few SQL scripts can be helpful when verifying that queries and associated tree exist in an environment with the necessary nodes. This SQL can be run in the appropriate SQL editor and was written against an Oracle RDBMS.
A frequent problem during migrations of PeopleSoft record definitions is the omission of a record build, even though the record exists in the PeopleTools project Meta Data. An easily way to solve this issue is to run a SQL script to test the new record exist and/or that altered record field(s) exist. A simple count script can provide the necessary answers and save lost project time and reduce testing defect research and resolution activities up front. Here a couple of quick samples, which can be assembled into a script and run in Oracle SQL Developer as a script.
Verify that a new PeopleSoft record exists in Oracle
SELECT COUNT(*) AS CNT_<<RecordName>>
Verify that a new field exists on an existing PeopleSoft record in Oracle
SELECT COUNT(<<FieldName>>) As CNT_<<RecordName_FieldName>>
Note: This SQL can also, be used to see if a field was dropped, only it should produce an error for the removed field.
In PeopleSoft (PS) query, it is possible to add the user name of the person who ran the query as a column. To do so create an expression, substring the %Operator global variable, and use the expression as a field.
I’ve had this SQL snippet laying around for a while, so, before I lose it, I thought I would post it for future reference. Below is SQL to lookup a XLAT values, in case you don’t want to or cannot go through PeopleSoft Application Designer.