Re: 255 Character Limit Puzzle

["Bhowmik, Bhaskar" <Bhaskar.Bhowmik@STAPLES.COM>]

    This is a PeopleTools limitation. The Application designer does not let
you define
    CHAR fields greater than 254 bytes.
    (Corresponding definition in Oracle would look like VARCHAR2(254))

    The following example depicts a similar problem:
    Module: Variable Compensation

    It so happened that the field (IC_WHERE_CLAUSE) in IC_GRP_DEFN being
limited
    to 254 bytes. Whenever a group's selection criteria ( Where Clause )
exceeded 254
    bytes, the SQR would bomb when it tried to insert the where clause.

    Prior to 7.5, we worked around the problem by altering the table in
Oracle to
    increase the field size to VARCHAR2(2000). We had to maintain
documentation for
    future reference because the field definition in PeopleTools Tables
would still be
    CHAR(254).

    In 7.5, PeopleSoft has worked around this PeopleTools limitation by
adding a new
    table to store the where clause (IC_GRP_BLD_SQL). The logic in the Group
Build SQR
    breaks the Where Clause into multiple Rows if it happens to exceed 254
bytes.

    The Group Populate SQR concatenates the data in multiple rows to build
the Where Clause
    and populates the Group.


    ~BB

-----Original Message-----
From: Zubin Shroff [mailto:zshroff@DTTUS.COM]
Sent: August 17, 1999 11:43 AM
To: Multiple recipients of list SQR-USERS
Subject: 255 Character Limit Puzzle


     I was getting an 'Over the 255 character limit...' error when running
     an SQR (PS 7.5, 95/DB2-AS400). I solved this by remapping some of my
     SQR search paths to shorten them. Yesterday, an SQR was run without
     the remapping, resulting in a parm list of approx 280 characters. The
     SQR ran fine. There seemed to be no difference in how and where the 2
     SQRs were run. Why is this? What exactly is included in the total
     count?

     Thanks.