Applied Concepts HR/Payroll Knowledge Base

Custom to resolve a limitation of ESS PayStubs and CheckHistory. There is a limitation of 20 pay or deduction codes. This most often appears, as a problem, when rates are displayed on the pay stub. The custom has been submitted with a request to be included in the standard product.

Administrator — Thu, 04 Dec 2008 03:58:00 GMT

Abstract:

Issue: A client recently uncovered a limitation of ESS PayStubs and CheckHistory. Specifically no more than 20 deductions or 20 pays will be displayed on the pages.

Solution: A custom was created and implemented which resolved this issue be allowing an unlimited number of deductions or pays to be displayed. The custom has been submitted with a request that it be included in the standard product.

Detail: Following is some detail on the subject:

(1) The Pay Stub with EssPayStub Rates system parameter set to no.

The area outlined in blue will not appear on the paystub after the Rates system paramater is set to yes.

(2) The Pay Stub with EssPayStub Rates system parameter set to yes.

Note that the pays, outlined in blue on point (1), do not appear on the pay stub in point(2).

(3) The custom solution involves modifications to the PayStubDetails and CheckHistoryDetails C# programs.

(4) Specifically the following logic was placed in each location where a datatable was built for display on the pay stub or check history:

// --> custom by Denton
int pdsCount = 40;
try
{
pdsCount = payPds.DataArray.GetUpperBound(0);
}
catch {}
dt.DataChunkSize = pdsCount + 1;
// --^ end of custom

(5) Using the above logic the number of pays included in the datatable is set equal to the number of pays available in the page data set. Prior to this custom the limit was 20 pays.

(6) Because the above custom was applied only to Pay Stubs and Check History the r

ESS/MSS - A user asked for screen shots of employee and manager self service. This article explains how these screens can be viewed in the emPath application clients already own.

Administrator — Thu, 04 Dec 2008 03:57:00 GMT

Abstract:

Request: A client asked "Can anyone provide me a screenshot of ESS and MSS pages? I am trying to give my leadership team an idea of what ESS and MSS pages look like. Any help would be appreciated."

Response:

although you have to license ESS and MSS to use the features you can look at the screens in your existing emPath implementation.

Following are the steps involved:

(1) I recommend you work in your test environment.

(2) Find valid ESS/MSS user ids by selecting (admin > security > users).

(2.1) Hover over the edit icon and select find. Enter EMPLOYEE in the user class and click search. Select an employee then note the login id and the employee id.

(2.2) Hover over the edit i

401(k) balancing - A detail explanation of how to combine percentages and YTD values from the EDF (Employee Deduction table) with current payroll deductions from the DDS (Deduction Detail Summary) reports.

Administrator — Wed, 22 Oct 2008 11:52:00 GMT

Abstract:

Request: A client recently asked for assistance in balancing their 401(k) deductions. The challenge is they needed information from the EDF (employee deduction) table and the DDS (deduction detail) reports. Specifically they wanted to pull percentages and YTD amounts from the EDF table and current payroll deduction amounts from the DDS report. They needed to do this for 19 deduction codes. Given the complexity of the balancing routine they needed this information to be presented in Excel spreadsheets for analysis. And they needed this done in a timely manner during the payroll calculate before the payroll update occurred.

Following is a diagram depicting the clients request:

Solution: The solution is fairly detailed and will be presented in summary here with links to the detail in subsequent articles.

One challenge was how to report the DDS information given that during the payroll process the information has not yet updated a database table which can easily be reported against. We looked a creating a view to read the raw columns on the PCF tables. We quickly looked at alternatives and settled on a VB script which parsed the DDS report and created SQL necessary to update a temporary table.

A job was created which did the following:

(1) Creates a temporary PYT file requesting a DDS report be ran for the deduction codes requested.

(2) Runs the delivered emPath DDS program (pr852) with no modifications.

(3) Runs a VB script to parse the DDS reports.

(4) Runs a SQL script to create a temporary table (temp_ddx).

emPath Custom Command Procedures

Administrator — Wed, 22 Oct 2008 11:52:00 GMT

Abstract:

Please find attached a compiled HTML document which contains numerous custom command procedure examples along with explanations for each.

Note, that if you receive the mesage "This program cannot display the webpage" after you download the attached document then you will need to unblock the compiled HTML. Unblock as follows:

Right click on the downloaded document
Select properties
Click the unblocked button.
Click the apply button
Click the ok button.

Basic Concepts:

Custom batch jobs can easily be added to emPath through the “Report” setup windows (ReportAdd., ReportDetails, ReportElementAdd, and ReportElementDetails). Once these custom reports have been added and security has been updated then end users may submit the custom reports for processing. However until you create a custom command procedure the custom reports will not accomplish anything.

The custom reports will prompt for the report elements you have added as part of the setup. These report elements along with the report id and program id are written by emPath to the PYT (Batch Report Transaction) file. EmPath will then trigger a command procedure, with the name you have setup, to process. As a result one of the first things your custom command procedure will need to do is read the PYT to determine what report elements have been passed to the command procedure.

Detail on how to create a Visual Basic script (VBS) which parses the Deduction Detail Summary (DDS) report creating SQL statements to insert detail, from the DDS report, into a temporary table. The benefit of such a VBS is that the deduction detail can then be joined with YTD information and percentages maintained on the Employee Deduction (EDF) table. By joining this information it is possible to balance complex deduction formulas which are dependent on one another.

Administrator — Wed, 22 Oct 2008 11:51:00 GMT

Abstract:

Request: A client recently asked for assistance in balancing their 401(k) deductions. See article Q10023 for a summary explanation of the request and solution. The specific portion of that request, which this article details, relates to Runs a VB script to parse the DDS reports and running of SQL statements to update a temporary (temp_dds) table. The specific request was for 19 deduction codes. The client asked that they submit a single emPath report request which triggered the DDS report to run for 19 deduction codes.

Solution: Use a Visual Basic Script to parse the DDS reports creating SQL statements which insert and/or update a temporary table on the emPath database.

Following is a diagram which depicts this process:

The VBS script used is attached to this article in a zip file. The script is very small however I attached it as a zip in case there are client filters which prevent my readers from downloading a VB script.

(1) The command procedure statements to run the DDS_parse are as follows:

:sub070_DDS_parse
@echo ******************************************************
@echo *** run DDS parse
time /t
(%datadrive%:)
(cd %hrdatbow%)
(if exist dds_update_temp_ddx_table.sql del dds_update_temp_ddx_table.sql)
(cscript %bow_cmn_wsh%\DDS_parse.vbs %dd_RPT_PR852% dds_update_temp_ddx_table.sql //B)
(goto :eof)

Note that cscript was used to execute the vbs. In this manner if a file is not found or any other error occurs then an error will be written to the log. If the vbs is executed directly or using wscript then errors appear as prompts in an

Applicant tracking - Consider leveraging the integration of emPath''s applicant tracking feature with an interface to a best of bread recruitment management system such as PeopleClick.

Administrator — Wed, 22 Oct 2008 11:51:00 GMT

Abstract:

Issue: The subject of Applicant Tracking comes up over and over. I have heard clients ask about it at user groups, on the list server, in RFP's, and in direct communication. In my opinion emPath has a very powerful applicant tracking feature which is integrated and works wonderfully when applicants are hired. Also, in my opinion there are best of bread Recruitment Management systems which offer features emPath does not.

Recommendation: Consider leveraging the integration of emPath's applicant tracking feature with an interface to a best of bread recruitment management system such as PeopleClick. One client I work with saw significant benefit from just such an interface. Following are some details:

(1) They used PeopleClick's features to support Candidate Relationship Management.

(2) They used emPath's Applicant import feature to interface applicant information collected in PeopleClick.

(3) The applicant information is then available to use the powerful emPath integration features such as hiring applicants on the new hire page.

(4) Using emPath's mass import feature it is possible to import additional information about applicants such as eduction, licenses, and skills.

How to use a Visual Basic Script to send an email in a custom command procedure. This example uses the CDO message feature from Microsoft to send the email.

Administrator — Mon, 15 Sep 2008 16:17:00 GMT

Abstract:

Question: It is common to need an email sent as part of a custom command procedure. The solution presented here is the result of a need to replace MapiSend which Outlook security changes have made obsolete.

Solution: The Visual Basic Script attached can be used to send emails from a custom command procedure.

Following is an example of how the VB script is executed:

(call :sub070_email_reports) >> %joblog% 2>&1 || %x%

:sub070_email_reports
@echo ****************************************************************
@echo sub070_email_reports
@echo
time /t
(%AppDrive%:)
(call %AciDis%\%cmdproc%_dis.bat)
(set fa=%emailAdmin%)
(set mr=%distribution%)
(set ms="%cmdProc% reports")
(set mm="See attached files")
(set mt="NA")
(set ma1="%LoadRptfile%")
(set ma2="%AciTranslatorSummary%")
(set ma3="%AciTranslatorErrors%")
(set ma4="%AciUpdateEmPathReportfile%")
(set smtp=mail.yourdomain.com)
(cscript %aciwsh%\aciSendMail.vbs %fa% %mr% %ms% %mm% %mt% %ma1% %ma2% %ma3% %ma4% %smtp% //B)
(goto :eof)

Note that the example shown uses several environment variables defined as follows:

fa = From Address for example denton@AppliedConceptsHrPayroll.com
mr = recipient(s) (multiples must be separated by ';' and
must not be ambiguous in default address book.)
ms = subject line
mm = message to be placed in the email body
mt = specifies text file for contents of the mail message

An emPath user asked how long they should plan for the testing of release 6.4. This article contains some suggestions about testing which should occur. Specifically testing of the increased number of tax codes and pay/deduction codes on the tax group records.

Administrator — Fri, 01 Aug 2008 05:05:00 GMT

Abstract:

Question: An emPath user asked:

"I am trying to gather information on how long it took you to test 6.4? We want to move to 6.4 but I want to know how much time I should plan to allocate to testing so that I have a better idea on what kind of commitment I have for other projects"

Resonse: A list server response from another emPath user indicated the following which I agree with:

"For us it is about 8 weeks. That is time for IS to install the system and do some limited testing. (We (IS) test to make sure the batch jobs, still run, not worrying about the outputs validity.) Both HR and Payroll do their testing of the windows, adding employees, moving employees from one location to other locations, changes in benefits, etc. The last big item is to run the current system and the new system in parallel for two payroll cycles, and to fully test out the new system."
"This is what we do. How long and how much effort you and your team puts into testing 6.4 is up to you and your team."

article 10007 which provides several command procedure examples.

Execute MicroFocus sort:

The following example shows the execute from a command procedure which uses MicroFocus sort.

register for the webinar or if the date has passed listen and view the recorded webinar.

(1) Question: Do we compile on the Business Server or just move files over ( Source, executable, etc).

Response: What I have used and seen at several clients is the following approach. Each developer has a copy of NetExpress / Microfocus COBOL on their personal PC. The programs are developed and compiled on their personal PC. Only the executable (exe) is moved to the emPath business tier. The source is normally maintained in a common Visual SourceSafe (VSS).

The command procedures, sort specifications, SQL statements, etc are also normally maintained on VSS and copied to the emPath business tier.

(2) Question: For testing do we have to automatically add to the emPath Menu as an Item to the right or can the program be easily added as part of the list for Batch Reports Menu Item.

Response: Most batch custom development should be added as a batch reports menu item. Adding menu items outside of the batch reports area is normally done for online customs.

Note that while it is possible to create a menu item, outside of the batch reports area, which involks a command procedure it is important to note that this method of invoking a command procedure resul

An example of how users can control the re-run of custom reports. This example uses the batch reporting capabilities delivered with emPath.

Denton Harryman — Wed, 02 Apr 2008 09:36:00 GMT
Abstract:
Issue: A client recently asked for ideas on how to restart part way through a custom command procedure. Specifically the client has a customized process which runs after the payroll/processing/update menu item. This process contains several program executables which produce various reports and will be submitted to run after the payroll update has completed.
In case of a program failure, the client does not want to re-run reports which have already ran. The clients wants to fix whatever the problem was, then re-submit the process, and have it start automatically where it failed previously.
Resolution: The are several alternative resolutions. This article presents a custom solution which allows customers to control the re-run process. The solution uses the batch reporting process delivered with emPath. Following is some overview detail. The attached example contains additional detail.
(1) Following is an example screen print which allows user control over the process:
(2) The example command procedure attached to this article uses subroutines for each custom report. There is also a mainline section with if statements which test the values entered in the screen shown above. Following is the mainline section and the if statements mentioned:
(if /i "%runrpt001%" equ "Y" call :sub050_run_rpt_001) >> %joblog% 2>&1 || %x%
(if /i "%runrpt002%" equ "Y" call :sub060_run_rpt_002) >> %joblog% 2>&1 || %x%
(if /i "%runrpt003%" equ "Y" call :sub070_run_rpt_003) >> %joblog% 2>&1 || %x%

Detail on how to create a view which combines employee deduction (EDF) information with results from the Deduction Detail Summary (DDS) report. This approach helps with balancing of 401(k) and other complex deductions using multiple deduction formulas.

Denton Harryman — Wed, 27 Feb 2008 12:40:00 GMT
Abstract:
Request: A client recently asked for assistance in balancing their 401(k) deductions. See article Q10023 for a summary explanation of the request and solution. The specific portion of that request, which this article details, relates to running SQL scripts to create two views which combine information from EDF and DDS. The goal is to be able to create a spreadsheet with combines specific information from EDF and DDS in a columniar format.
Solution: Use SQL to create two views which combine information from the EDF table and the parsed results from the DDS reports. See articles the related articles, attached to the document, for detail on how the DDS report was parsed. For the purposes of this article accept that the DDS results now exists in a temporary table.
(1) The goal is to allow the user to create a spreadsheet similar to the following. Note that the following is a simplified example. There acutal request involved 19 deduction codes and multiple spreadsheets.
(2) Create views for the EDF information and the DDS parsed table. The sql scripts are attached.
(3) Use Business Objects or Crystal to combine the two views created in step 2.
Note: A simplified SQL statement, used to create a spooled file which was pulled into Excel to create the above spreadsheet, is as follows:
select
edfv.EM_EMPLOYEE_ID,
DEFSAVR_PERCENT,
NDSAVR_PERCENT,
DEFSAVR_YTD,
NDSAVR_YTD,
DEFSAVR_DDS,
NDSAVR_DDS
from view_401k_edf_info edfv, view_401k_dds_info dds
where NDSAVR_YTD <&g

SQL performance tip - When joining char and varchar columns using the RPAD feature instead of the TRIM will improve performance when if columns are part of an index.

Denton Harryman — Mon, 25 Feb 2008 10:29:00 GMT
Abstract:
Issue: A client was experencing slow response from a SQL script ran against the emPath employee benefit (BN3) table and a custom table.
Research: The slow response was directly related to the custom table using VARCHAR field types while the BN3 table used CHAR field types. The workaround on the field type issue was to trim each column when referenced in the where clause. That workaround, along with the fact that columns in the where clause were part of an index, caused very slow response.
Resolution: The resolution is to use RPAD instead of TRIM. This results in a significant performance improvement.
Original where clause:
where trim(bn3.em_employee_id) = trim(es.em_employee_id)
and trim(bn3.bn_benefit) = trim(es.bn_benefit)
and trim(bn3.bn_coverage) = trim(es.bn_coverage)
Performance improving where clause:
where bn3.em_employee_id = rpad(es.em_employee_id,9)
and bn3.bn_benefit = rpad(es.bn_benefit,8)
and bn3.bn_coverage = rpad(es.bn_coverage,4)

Detail on how to create a temporary PYT file requesting a DDS (Deduction Detail Summary) report be ran for multiple deduction codes. This example demonstrates the power of custom programs PYTparse and PYTinsert.

Denton Harryman — Fri, 08 Feb 2008 11:58:00 GMT
Abstract:
Request: A client recently asked for assistance in balancing their 401(k) deductions. See article Q10023 for a summary explanation of the request and solution. The specific portion of that request, which this article details, relates to the clients need to run a DDS report for multiple deduction codes at the same time. The specific request was for 19 deduction codes. The client asked that they submit a single emPath report request which triggered the DDS report to run for 19 deduction codes.
Solution: Use emPath to prompt the user for a date range. Then create a temporary PYT file requesting that the DDS report be ran for multiple deduction codes. Additional articles will be referenced in this article detailing how the resulting DDS report is parsed and SQL is generated to create tables. Then those tables are joined with other tables in a view which can be used by Business Objects or Crystal to generate balancing spreadsheets.
The other benefit of this article is to demonstrate the power of using custom programs PYTparse and PYTinsert.
(1) The delivered PYT process is depicted in the following diagram:
(2) The power of custom program PYTparse is depicted in the following diagram:
(3) The possibilities of custom program PYTparse and PYTinsert are shown in the following diagram and description of how they were used in one specific request:
(3.1)

Resolving pay/deduction overflow issues on the ETF table after running the CTXG (adjust emp taxes by tax group) job.

Denton Harryman — Fri, 01 Feb 2008 11:01:00 GMT
Abstract:
Question: A client recently asked for assistance in resolving a problem where they were receiving pay/deduction overflow massages on the ETF table when they ran the CTXG report.
The challenge is that with emPath 6.3 there is a limitation of 42 pays and deductions on the employee tax (ETF / ETF2) tables. Making the challenge even harder is that there is a limit of 12 pay and deduction codes on the tax group (TGF) table. The code on the TGF can be wild carded which often causes multiple pays and deductions to be added to the ETF which are not needed.
The best solution to this issue is to upgrade to emPath 6.4 where these limitations have been relaxed. However, if you are using emPath 6.3 the following steps will help in resolving the problem.
(1) Identify the employees and tax groups impacted. Following is a SQL statement which will identify those employees with a value of 42 in pay/deduction occurances column.
select em_employee_id, etf_tax_group
from etf
where etf_pay_ded_data_occurs_count = 42;
(2) Review the tax groups identified in step 1 vs the pays and deductions paid in the year as reported on the E-H-R report. When running the E-H-R report enter "T" in the sort by column such

How to make data corrections, in emPath tables, when a manual check is created in a new quarter before the previous quarter has been rolled. This resolves out of balances situations between Earning History Register (EHR) and QTD/YTD register (QYR).

Denton Harryman — Fri, 01 Feb 2008 03:56:00 GMT
Abstract:
Question: A client recently asked for help in correcting data, in emPath tables, to resolve a problem caused by the creation of manual checks in a new quarter before quarter end was rolled.
The problem is caused when a manual check is created, in a new quarter, before the accumulators on the employee tax tables have been rolled. The problem is manifest by an out of balance situation between the Earning History Register (EHR) and QTD/YTD register (QYR).
Answer: The problem can be resolved using SQL updates if the number of employees is limited.
If you have not already rolled the calender then do so.
Use the EXCP, E-H-R, and QYR reports to identify the employees involved and the total tax and taxable amounts by tax code. Also, determine the amount by pay code which appears on the QYR report.
Run SQL scripts to subtract the tax and taxable amounts from the last quarter accumulators. Then add the tax and taxable amounts to the current quarter accumulators.
Run E-H-R and QYR reports after the correction to verify the correction was successful.
Note that there is an example set of SQL statements attached. Please remember the attached SQL is an example and would have to be modified to address the data circumstance you are challenged with.
Note that, in emPath 6.3, there are eight tax code on the ETF table and four tax codes on the ETF2 table. The sequence in which the codes are assigned varies by tax group.
Note that, in emPath 6.4, the number of tax codes are greatly increased.

Creating a custom validation table and a drop down selection box. Example using the instructor field on the (training > setup > sessions) page. Custom accomplished using the site_ComponentMetaData and a minor XML change.

Denton Harryman — Thu, 31 Jan 2008 16:08:00 GMT
Abstract:
Question: I need to create a validation table with a list of our training instructors. The validation table needs to be linked to the “Instructor” field in the set-upèSessionsèDetails page. Any information you can share with me is greatly appreciated.
Solution: This can be accomplished using the emPath site_ComponentMetaData feature in combination with a minor XML change. The result is a dropdown box tied to a custom validation table. Following is an example using the (training è set-upèSessionsèDetails) page.

Custom to insure W-4 page has no editable fields. This is necessary because while setting emPath security for the W4 to Inquiry does remove modify and the OK button, it still leaves a few fields which are editable.

Denton Harryman — Wed, 19 Dec 2007 16:53:00 GMT
Abstract:
Custom to insure W-4 page has no editable fields. This is necessary because while setting emPath security for the W4 to Inquiry does remove modify and the OK button, it still leaves a few fields which are editable.
The objective, of this custom, is to have read only fields on the W-4 page as shown in the following screen prints. Without a custom the fields circled in blue appear as editable even is change is removed from the security page.

. . .
The custom is to:
(1) modify the EssW4Details xml file as follows
(1.1) Set disabled true on W4Allowances, AdditionalAmount, ExemptFromTax. See attached example XML.
(1.2) Delete the c:\Nsl63\emPath\Cache\en_US\ESS\EssW4Details file.
(1.3) End the W3-SP process on the webtier supporting IIS.
Note that this article has a related article about the functional effort to change the menu title and the help text controlled by metadata.

The EssAllowAccess system parameter impacts the message "Access to this page has not been approved".

Denton Harryman — Wed, 19 Dec 2007 16:51:00 GMT
Abstract: The reason an employee might receive the following message restricting access to ESS is because their (admin > security > user) record has a value in the "inactivation date" field. When the inactivation date is removed ESS access is allowed.

The program logic loads the inactivation date any time an employees status is changed to DE, LY, RT, or TR.

Note that if there is a System Parameter created called EssAllowAccess and the parm value is set to Y. Then the inactivation date is not set for status code changes to LY.

Following is an example of the EssAllowAccess system parameter.

Use delivered configuration feature to place an instructional message on the HR/Payroll (emPath) login page. Especially useful for Employee Self Service.

Denton Harryman — Wed, 19 Dec 2007 16:50:00 GMT
Abstract:
A delivered configuration feature is especially helpful for Employee Self Service because clients are given control of a message which appears on the login page. Following is an example:
The configuration, necessary to control the login message, is in the query string on the URL which an employee clicks on to link to the login page. Therefore it works best if the client has a link, to ESS, on their Intranet site or if the client has a front end menu or portal for ESS.
Following is an example of the url which created the message shown above.
http://ess.yourdomain.com/empath63/HrLogin.aspx?msg=Please%20enter%20employee%20number%20as%20your%20user%20id.%20%20After%20keying%20your%20password,%20please%20select%20the%20environment%20which%20describes%20your%20location.%20%20If%20you%20have%20problems%20please%20contact%20the%20HR%20Service%20Center%20at%201-800-ess-help

Use front end menus for emPath staff and employee self service (ESS) usage. Creating front end menus are very beneficial for ESS usage such that when the server is down for maintenance you can easily notify thousands of users. Also, by placing the front end menu on a different server you are insured the employees will see a friendly message instead of an unfriendly error.

Denton Harryman — Wed, 19 Dec 2007 16:48:00 GMT
Abstract:
Following is an example of a staff front end menu:
Note the potential for links to different servers (production, QA testing, and development)
Note the potential to link to documentation.
Note that the potential to use the center of the page to share information in a collapsible list.
Note that the potential exists to convey planned outage with a red arrow pointing at the message.
Following is an example of an Employee Self Service (ESS) front end menu
Note the potential to display welcome and instructional messages in multiple languages.
Note the potential to display planned system outage information.
Note the potential to display instructions in multiple languages
Note the potential to place an instructional message on the login page using multiple languages via the MSG value in the URL query string. See the related article below for full details.
Please note that these front end menus are very easy to develop and if you are interested can be developed as a custom from Applied Concepts HR/Payroll. If a client is interested in these as a custom we will consider generalizing them such that a product offering is available.
Contact us if you have questions.

Change an ESS menu title and the help text.

Denton Harryman — Wed, 19 Dec 2007 16:47:00 GMT
Abstract:
Details on how to change an ESS menu title and the help text. This specific example was performed for an client who wanted to release W-4 to ESS users but as inquiry only.
The goal of this article is to show the detail on how the menu item for "W-4 change" was changed to "W-4". Also to show how the help text at the top of the page was modified to let users know that changes should be made with the assistance of their HR Service Center.
All clients will not need these changes however those that do the following detail may help.
(1) Change the menu item title on the security items detail page
(1.1) Select (admin > security > items) from the menu
(1.2) Hover over the edit icon then select find from the edit menu
(1.3) Enter EssW4Details as the item then click on the search button
(1.4) Click on the W-4 Change Request item
(1.5) Hover over the edit icon then select modify
(1.6) Change the item description from "W-4 Change Request" to "W-4"
(1.7) Change the Navigation Title from "w-4 change" to "w-4".
(1.8) Click on the OK button.

(2) Change the security screen to inquiry only
(2.1) While on the security item screen, referenced above, insure "allow inquire" is check marked while add, change, and delete are not check marked.
Note that the above security change will remove the modify option and the OK key, however the page opens in edit mode with a few fields editable. To resolve this a minor XML custom is required. See the related article listed below for details.
(3) To change the help text do the following.
(

Resolving RPC (remote procedure call) problems. After an install or a change in the server architecture it is possible to have a red X on the top of emPath screen indicating the RPC could not be started. One possible cause is that the "Supplemental UI Library for Visual J# .Net v1.1" (vjssupuilib) is not installed. The symptom, of this problem, is a gem_server dmp file in the Gembase log files. The gem_server dmp file will indicate there has been an EXCEPTION_ACCESS_VIOLATION.

Denton Harryman — Wed, 19 Dec 2007 16:46:00 GMT
Abstract:
Resolving RPC (remote procedure call) problems. After an install or a change in the server architecture it is possible to have a red X on the top of emPath screen indicating the RPC could not be started. One possible cause is that the "Supplemental UI Library for Visual J# .Net v1.1" (vjssupuilib) is not installed. The symptom, of this problem, is a gem_server dmp file in the Gembase log files. The gem_server dmp file will indicate there has been an EXCEPTION_ACCESS_VIOLATION.

VARCHAR2 vs CHAR - can data type VARCHAR2 be used in customs to emPath

Denton Harryman — Wed, 19 Dec 2007 16:43:00 GMT
Abstract:
Question:
We are adding fields to existing base table and creating new tables. I noticed that all the tables use CHAR and not VARCHAR2. I wanted to know if I have no choice but to define my new fields with CHAR or I can use VARCHAR2. I did notice that VARCHAR2 is being used in some of the fields but for large comment, description fields. What is the reasone behind using CHAR for all fields.
Answer:
Yes, you may use datatype VARCHAR2 on customs to the emPath application. I have used VARCHAR2 in my online csharp (C#) customs, batch COBOL, and SQL scripts. There are a lot of advantages to using VARCHAR and only a few issues you need to be aware of:
(1) When working with Oracle you should use the trim function to insure your comparision to CHAR datatypes will perform accurately. Following is an example from one of my C# customs.
select
BN3.BN_BENEFIT AS BN3_BN_BENEFIT,
BN3.BN_COVERAGE AS BN3_BN_COVERAGE,
BN3_START_DATE
From
CUSTOM_ENROLL_AVAILABLE_BENEFITS AB, EMF, BN3
where
EMF.EM_EMPLOYEE_ID = ?
and EMF.EM_BENEFIT_STATUS <> 'NO'
and AB.BENEFIT_CLASS = ?
and AB.BENEFIT_CATEGORY = ?
and AB.PERIOD_START_DATE >= ?
and AB.PERIOD_STOP_DATE <= ?
and AB.BN_BENEFIT = TRIM(BN3.BN_BENEFIT)
and AB.BN_COVERAGE = TRIM(BN3.BN_COVERAGE)
and BN3.EM_EMPLOYEE_ID = EMF.EM_EMPLOYEE_ID
and BN3_INVERSE_DATE LIKE ' %'
(2) When working w

Null values can cause SQLstate 22002 - indicator variable required but not supplied

Denton Harryman — Wed, 19 Dec 2007 16:37:00 GMT
Abstract:
It is possible to create customs which allow null values. When nulls are present they can cause a NetExpress (Microfocus COBOL) program to error out with a SQLstate 22002 error. The error message "indicator variable required but not supplied" is less than helpful. There is however a Microsoft knowledge base article which explains the error in more detail.
To workaround this issue in Oracle you can use the decode function in the select statement such that nulls are changed to spaces as shown below:
SELECT
EM_EMPLOYEE_ID,
decode(RATE_TABLE_GRADE,NULL,' ',
RATE_TABLE_GRADE) as rateGrade
. . .

Who can use the AppliedConceptsHrPayroll knowledge database.

Denton Harryman — Tue, 25 Sep 2007 18:29:00 GMT
Abstract:
Please note that this knowledge database is restricted to customers of Applied Concepts Software and Consulting, Inc. To become a customer you may contact us at (888) 731-3026 x-1 or send an email to Denton@Harryman.com
The content of the knowledge database is specific to integration, customization, and support of the NOW Solutions emPath (HR/Payroll) application.