Archive for September, 2010

GAAP – Accounting Framework

Generally Accepted Accounting Principles (GAAP)  is a term used to refer to the standard framework of guidelines for financial accounting  used in any given jurisdiction which are generally known as Accounting Standards . GAAP includes the standards, conventions, and rules accountants follow in recording and summarizing transactions, and in the preparation of financial statements

Financial Accounting is information that must be assembled and reported objectively. Third-parties who must rely on such information have a right to be assured that the data are free from bias and inconsistency, whether deliberate or not. For this reason, financial accounting relies on certain standards or guides that are called "Generally Accepted Accounting Principles" (GAAP).

Principles derive from tradition, such as the concept of matching. In any report of financial statements (audit, compilation, review, etc.), the preparer/auditor must indicate to the reader whether or not the information contained within the statements complies with GAAP.

International Accounting Standards and Rules

Many countries use or are converging on the International Financial Reporting Standards  (IFRS), established and maintained by the International Accounting Standards Board . In some countries, local accounting principles are applied for regular companies but listed or large companies must conforms to IFRS, so statutory reporting is comparable internationally, across jurisdictions.

* Source : WIKI

Below are some FSCM  functions which cover most of the Business Processes related to modules.

Row Class

Row Class

A row object, instantiated from the Row class, is a single row of data that consists of one to n records of data. A single row in a component scroll is a row.
A row object is always associated with a rowset object, that is, you cannot instantiate a row object without first either explicitly or implicitly instantiating a rowset object. A row may have one to n child rowsets. For example, a row in a level two scroll may have n level three child rowsets.






ChildCount     [R]
DeleteEnabled  [R/W]
IsChanged     [R]
IsDeleted     [R]
IsEditError     [R]
IsNew          [R]
ParentRowset     [R]
RecordCount     [R]
RowNumber     [R]
Selected     [R]
Style          [R/W]
Visible          [R/W]

Application Engine

Application Engine

State Records
Required Process_instance as only Key-Name should end with _AET
Thought of as in Program memory – Data is saved to databases at commit to enable restart
%bind(recordname.fieldname) (for non default records only)

select oprid,run_cntl_id,’L’ From ps_aeruncontrol where process_instance = %bind(process_instance)



Temporary Tables
Should have Process Instance as key Name should end with _TAO
Use with Meta SQL for correct Table name
Use for Set Processing

Control Tables
PS_AE_RUN_CONTROL – Keyed by Operator ID and Run Control ID
PS_AERUNCONTROL – Keyed by Process Instance, Operator ID and Run Control ID
This is the "memory" of where a program is stopped

PeopleSoft tools Tables

PSAEAPPLDEFN – AE Definition Record
PSAEAPPLSTATE – Lists all State Records for an AE Program
PSAEAPPLTEMPTBL – Lists all Temp Records for an AE Program
PSAESECTDEFN – Lists all Sections within an AE Probram
PSAESECTDTLDEFN – Detail Section Information
PSAESTEPDEFN – Detail Step Information
PSAESTEPMSGDEFN – Message Step Information
PSAESTMTDEFN – SQL within the Step

RowSet Class

RowSet Class

A rowset object, instantiated from a Rowset class, is a collection of rows associated with buffer data. A component scroll is a rowset. We can also have a level zero rowset.


CreateRowset(Record.Name [,&Rowset}])




ActiveRowCount      [R/W]
ChangeOnInit             [R/W]
DataAreaCollapsed         [R/W]
DBRecordName      [R]
DeleteEnabled [R], InsertEnabled [R/W]
EffDt [R],EffSeq          [R]
ParentRow [R],  ParentRowset [R],  TopRowNumber [R/W],RowCont [R]
IsEditError           [R]
Level               [R]
Name                [R]

* We would be having Row ,Record and Field Classes in coming PeopleCode Tips. Keep watching.

PeopleSoft Benefits Administration – Features List

Complete Benefits

    • Establish and manage multiple employee benefits programs, including flexible spending accounts, as well as leave accruals for sick, vacation, or personal time off (PTO) plans.
    • Define your providers, rates, and beneficiaries, including spouses, domestic partners, and dependents, and calculate coverages and premiums for employees who have multiple jobs.
    • Establish and administer plans for FMLA (Family Medical Leave Act), COBRA (Consolidated Omnibus Budget Reconciliation Act), health and life insurance, savings (including 401(k) and 403(b) plans), Section 129 dependent care reimbursement, and Section 457 savings plans.

Automatic Event Maintenance, Enrollment, and Billing  

    • Automatically enroll participants and dependents in a variety of benefit options.
    • Determine and track employee eligibility based on 18 delivered fields.
    • Use passive event processing to trigger events automatically.
    • Generate and process billings, payments, and adjustments for individuals and groups.
    • Automatically identify eligible employees and calculate and process retroactive benefits and deductions.

Manage and Administer Flexible Spending Accounts  

    • Administer health care and dependent care FSA claims.
    • Record pledges.
    • Process claims.
    • Print checks.
    • Account for funds.
    • Enter and validate claims online.

Comprehensive Reporting and Analysis  

    • Generate reports for frequently requested information and create your own customized, ad hoc reports for agency-specific requirements.
    • Analyze trends in your workforce and study the enterprise-wide impact of your programs and policies, including various benefits-expense ratios.

Complete Functionalities for U.S. Federal Government Employers  

    • Establish and administer benefits that meet applicable federal standards.
    • Gain advanced capabilities for processing federal leaves.
    • Automate benefits enrollment and gain event-maintenance functionalities for federal benefits programs                    
Component Interface Introduction

Component Interface is an Integration Tool in PeopleSoft, its  a way for external applications, internal message handling, and other application environments to access PeopleSoft logic and data.

SQL Class in PeopleSoft

You can create SQL definitions in PeopleSoft Application Designer. These can be entire SQL programs, or just fragments of SQL statements that you want to re-use. PeopleCode provides the SQL class for accessing these SQL definitions in your PeopleCode program at runtime.

The SQL class provides capability beyond that offered by SQLExec. Unlike SQLExec, which fetches just the first SELECTed row, operations for the SQL class allow iteration over all rows fetched. This can dramatically improve performance if you’re doing a million operations and you’ve set the BulkMode property to True.


  1. CreateSQL(&Sql,&var1,&var2)
  2. FetchSQL(SQL.Name,&dbtype,&Effdt)
  3. GetSQL(SQL.Name,&var1,&var2)
  4. StoreSQL(&Sql,SQL.Name,&dbtype,&Effdt)


  1. Close()
  2. Execute(&var1,&var2)
  3. Fetch(&var1,&var2)
  4. Open(SQL.Name,&var1,&var2)


  1. BulkMode         [R/W]
  2. IsOpen             [R]
  3. Ltrim                [R/W] %SQLStatus_OK
  4. ReuseCursor    [R/W]  0   No Errors
  5. RowsAffected   [R] %SQLStatus_NotFound
  6. Status             [R]   1       Record Not Found
  7. TraceName      [R/W] %SQLStatus_Duplicate
  8. Value              [R]   2       Duplicate Record Found

Code Example : SQL

Below example shows how to use SQL:


While &SQL.Fetch(&Custid,&Billid)

          /*More Processing*/