krishnamraju

Local string &Where_Clause, &Prior_Condition_Exist; &Where_Clause = "WHERE "; &Prior_Condition_Exist = "N"; If All(CES_FA_CINB_WRK.EMPLID) Then    REM &Where_Clause = "WHERE EMPLID = " | "'" | CES_FA_CINB_WRK.EMPLID | "'";    &Where_Clause = &Where_Clause | " EMPLID = " | "'" | CES_FA_CINB_WRK.EMPLID | "'";    &Prior_Condition_Exist = "Y"; End-If; If All(CES_FA_CINB_WRK.SSN) Then    If &Prior_Condition_Exist = "Y" Then       &Where_Clause = &Where_Clause | " AND SSN = " | "'" | CES_FA_CINB_WRK.SSN | "'";    Else       &Where_Clause = &Where_Clause | "  SSN = " | "'" | CES_FA_CINB_WRK.SSN | "'";       &Prior_Condition_Exist = "Y";    End-If; End-If; If All(CES_FA_CINB_WRK.CES_FA_CSAC_ID) Then    If &...

STANDALONE ROWSET In PeopleCode a standalone rowset is an independent rowset object not associated with the component buffer. They allow you to work with data outside of the buffer by getting whatever additional data you need from the database. In this sense they replace the functionality of derived records which were once used as place holders to store data not directly associated with the component. Because a standalone rowset is standalone, there is no automatic action by the component processor on it. This means that if a standalone rowset is used to manipulate data (inserts/updates), code will need to be added to manually save the changes.   Code to create a standalone rowset object Local Rowset &rsExample;   &rsExample = CreateRowset (Record.REC1); Filling a standalone RowSet: The Fill method in the Rowset class is used to populate the rowset. This parameters to the fill method area Where clause and bind values. &rExample.Fill("where FIELD1 =...

REM **************************************************Modification Summary *******************************************************************; REM SL. No    Developer             Mod. No.     Date          Changes REM -----  -----------             --------- ----------  ------------------------------------------------------------ REM  01         Krishnam Raju Nadimpalli   AD0005       29/10/2015       Added the code to validate the Term and Description values REM*************************************************************************; Local Rowset &RS1, &RS2; Local number &i, &j; &RS1 = GetLevel0 () (1).GetRowset(Scro...

How to get a XML Publisher report from Connected Query with parameters from PeopleCode A connected query is a hierarchical object built with existing PeopleSoft queries. A parent query can nest  as many as levels of child queries and any child query can have  any number of sibling queries within a hierarchy. A connected query returns a hierarchical data set in which data returned by child queries is filtered by the results of its immediate parent query. Connected queries are used to analyze data, supply to other systems with PeopleSoft data using Web Services, and create BI Publisher reports that use connected query as a Data Source. To run connected query from PeopleCode we require to follow following steps – Create the connected query and run a sample of it to XML that you can save to file as sample data for your XML Publisher report. Create a Data source for your report, but instead of making in Connected Query, make it an XML File data ...

You can create a simple XMP Publisher report by answering these following questions: How to setup XML Publisher? How to create data sources? How to create report templates? How to define reports? For starters, you need to add the XMLP Report Developer to your User Role. That will give your user access/security to Report Category, Design Helper, Data Source, Report Definition, Content Library, Template Translations, Query Report Viewer, Query Report Scheduler, and Report Repository. You also need to download the template design helper which is located to Reporting Tools > XML Publisher > Setup > Design Helper Define report categories; this is for row level security of the data. Located to Reporting Tools > XML Publisher > Setup > Report Category. Now you must understand that XML Publisher retrieves data from different source (e.g. PS Query, RowSet, XML File, and XMLDoc Objects). In this article we will used the simplest form, the PS Quer...

Using the below XSL command you can <?for-each:SUMMER1[position()<6]?> Where 6 is the no of rows you want to display in each page, suppose your XML contain 30 rows,you wanted to display 6 rows in each page. you can do the for loop for 6 rows, then you can also add the command to page break when the position reaches 6 :) <?if:position() mod 3 =0?> <xsl:attribute name="break-before">page</xsl:attribute> <?end if?>

 %Execute()  UPDATE %Table(LAC_AB540_STG) B   SET B.FIRST_NAME = (  SELECT TRANSLATE(A.FIRST_NAME  ,'éêëèÉÈÊËðÐâàáãæàåÅÀÁÂÃÆäÄïîìíÌÍÎÏôòóõøÒÓÔÕØöÖûùúÙÚÛÜüñÑÇçýÿÝþÞ'  ,'eeeeEEEEDDaaaaaaaAAAAAAaAiiiiIIIIoooooOOOOOoOuuuUUUUunNCcyyYTt')   FROM PS_LAC_NAMES A  WHERE A.EMPLID = B.EMPLID    AND A.NAME_TYPE = 'PRI'    AND A.EFF_STATUS = 'A'    AND A.EFFDT = (  SELECT MAX(A_ED.EFFDT)   FROM PS_LAC_NAMES A_ED  WHERE A.EMPLID = A_ED.EMPLID    AND A.NAME_TYPE = A_ED.NAME_TYPE    AND A_ED.EFFDT <=%CurrentDateIn ))  WHERE B.PROCESS_INSTANCE = %ProcessInstance    AND EXISTS (  SELECT 1   FROM PS_LAC_NAMES A  WHERE A.EMPLID = B.EMPLID    AND A.NAME_TYPE = 'PRI'    AND A.EFF_STATUS = 'A'    AND A.EFFDT = (  SELECT MAX(A_ED.EFFDT)   FROM PS_LAC_NAMES A_ED  WHERE A.EMPLID = A_ED.EMPLID   ...