HR Payroll plugin for iDempiere

[redhuan d. oon]

I am now focusing on this and invite any functional review comments of Libero HR as expanded by ADempiere LVE at this forum thread http://red1.org/adempiere/viewtopic.php?f=29&t=1729. It is due to be completed by end of February.

[Orlando Curieles]

Hi, Red1 thanks for the how to make a IDempiere plugin, schedule today's meeting with my team and we advise you.

Thanks again

Enviado desde mi iPhone

[redhuan d. oon]

I am expanding it to include LCO first as this is a pre requisite of HR Payroll. http://red1.org/adempiere/viewtopic.php?f=29&t=1729&p=8290#p8289
So this means other countries concerned with Withholding Tax must make their ideas known to consolidate the work to be reusable across their locales.
Also for Language importing, we will make LCO Spanish as a reference guide, where its 2Pack script is reusable.

[redhuan d. oon]

Hola,
I already done with LCO Retenciones plugin, and now have to finish this up as promised. I am following the readme. I want to do it without the Language translation, just HR Payroll. I need to know which scripts to run and not to run. For example LVE361/customization.sql.
There is a LoginPanel, and other common code, do i need them?

[Edickson Martinez]

Amigo Redhuan, saludos!

1- We recommend you first remove all menu items payroll

2- Only be imported packages located in /migration_LVE_361/package/nomina/

     LVE_TalentoHumanoHigiene_1.zip

     LVE_TalentoHumanoNomina_2.zip

     LVE_TalentoHumanoRRHH_3.zip

     LVE_Empleado_4.zip

     LVE_CatalogoConceptos_5.zip

     LVE_HR_Loan_Type_6.zip

3- Run the scripts in order located in migration_LVE_361/LVE_361/361/nomina/ (These scripts import necessary data to parameterize the payroll for Venezuela)

    first: script1_.sql

    last: script20_Create IsOption11 In HR_concept.sql

However we have a database in the 361 final version with all the payroll menu, even in this database we have corrected some issues. What do you think? if I pass this database and you export the package (Packout) from this.

Edickson Martinez

2013/1/17 redhuan d. oon <red...@gmail.com>

[redhuan d. oon]

Yes it be a good idea to start and just pass me a completed Database as all i need is to upgrade to iDempiere and Pack Out its models.
You also have to list to me besides the Menu items, what other windows or tables are added with LVE Payroll columns.

[Alex Yang]

Hi Red,

What's current status now for the HR & Payroll module? Does it work? I would like to test it if any progress.

Thanks,

Alex

[redhuan d. oon]

Now it's converted as a basic plugin and awaiting a user manual which i hope to commence soon. We already understood how the concept works with attributes to post movements via processing of rules. Then u try to follow and test it.

[Alex Yang]

Amazing! Thanks Redhuan!

I have spent a lot of time reading Libero HR & Payroll source code in last year and also gotten a basic understanding of concepts, attribute, payroll prcess, movement and payroll selection.

Hope this plugin move forward quickly. Then I can help on testing.

Thanks,

Alex

[Alex Yang]

Hi Red1,

Is the manual ready for your LiVE_HR plugin? I see you are moving to liberoHR on bitbucket. Does it mean you want hold on current work on LVE_HR?

Thanks,

Alex

[redhuan d. oon]

Thanks for following closely and thus u are in a position to help test better.

You probably read from my forum why i am doing this LiberoHR as a first base as the LiVE is more complex with 250 records in AD_Rule and mostly in Spanish! I have understood roughly how some of them work but like to use LiberoHR to configure some basic rules to have a fully minimal working model first. So you can basically take from my bitbucket and try to introduce some basic rule and give me back in migration script for me to review and incorporate it as a sample contribution from you.

Also when Edwin Ang went through it with me in Jakarta 2 weeks ago, he found code methods that we do not know how it really works, so he disable them. Thus i better abort the LiVE as i described in my forum and wait to separate LiVE from Libero as a fragment plugin rather than a bulky standalone plugin.

I will update the huge Spanish AD_Rule data into a 2Pack which u can PackIn into your iDempiere to browse through them (Download: HR_Rule.zip). Alternatively you can DB_Restore the ExpDat.dmp from ExpDatLiVE.jar (Download: ExpDatLiVE.jar) that has the whole Venezuelean data including that AD_Rule, HR_Concepts, Attributes, etc so you can correlate how they do it. If you really understand them then please teach me in English :) 

The general link for the above files are at http://sourceforge.net/projects/red1/files/p2/LiVE_HR/

[Alex Yang]

Hi Red1,

Thanks for the long update.

A quick question: is your plugin of LiVE_Base and LiVE_ including all code of Venezuela's enhancement? I launched it LiVE_ in iDempiere. But seems less menu than Venezuela's Spanish's manual.

I am going to import full data into iDempiere to understand Venezuela's localization features. So I may need a workable plugin firstly.

Thanks,

Alex

[redhuan d. oon]

Yes it does. You have to start the bundle to get the menu packed in. Then u have to login into Venezuela Admin role and do a role access update and then relogin. You should see the whole  menu tree.

On Tuesday, 26 March 2013 11:58:31 UTC+8, Alex Yang wrote:

[redhuan d. oon]

Or like I said, just use the ExpDatLiVE.jar (jar -xvf to get the ExpDat.dmp) which has the whole original Venezuela DB.

[redhuan d. oon]

I would still recommend using the LiberoHR which i am focussing on now as that is the core engine. 

Please raise tickets like this one http://sourceforge.net/p/red1/tickets/11/

and i will resolve them right away. But in 2 weeks time i will have to move on to another plugin and thus may not give maximum attention on this.

[Alex Yang]

Hi Red1,

I am moving to your bitbucket repository. When I complete the Payroll Process. The eclipse error message as below. It seems related to Doc_HRProcess.

BTW I can't find a place to create ticket on your sourceforge site.

java.lang.IllegalAccessError: tried to access method org.compiere.acct.Doc.<init>(Lorg/compiere/model/MAcctSchema;Ljava/lang/Class;Ljava/sql/ResultSet;Ljava/lang/String;Ljava/lang/String;)V from class org.compiere.acct.Doc_HRProcess

at org.compiere.acct.Doc_HRProcess.<init>(Doc_HRProcess.java:61)

at org.idempiere.component.DocFactoryHRProcess.getDocument(DocFactoryHRProcess.java:66)

at org.compiere.acct.DocManager.getDocument(DocManager.java:196)

at org.compiere.acct.Doc.get(Doc.java:215)

at org.compiere.acct.DocManager.postDocument(DocManager.java:295)

at org.compiere.acct.DocManager.postDocument(DocManager.java:246)

at org.compiere.acct.Doc.postImmediate(Doc.java:230)

at org.compiere.process.DocumentEngine.postImmediate(DocumentEngine.java:1253)

at org.compiere.process.DocumentEngine.postIt(DocumentEngine.java:491)

at org.compiere.process.DocumentEngine.processIt(DocumentEngine.java:319)

at org.compiere.process.DocumentEngine.processIt(DocumentEngine.java:255)

at org.eevolution.model.MHRProcess.processIt(MHRProcess.java:179)

at org.compiere.wf.MWFActivity.performWork(MWFActivity.java:987)

at org.compiere.wf.MWFActivity.run(MWFActivity.java:874)

at org.compiere.wf.MWFProcess.startNext(MWFProcess.java:371)

at org.compiere.wf.MWFProcess.checkActivities(MWFProcess.java:281)

at org.compiere.wf.MWFActivity.setWFState(MWFActivity.java:277)

at org.compiere.wf.MWFActivity.run(MWFActivity.java:891)

at org.compiere.wf.MWFProcess.startNext(MWFProcess.java:371)

at org.compiere.wf.MWFProcess.checkActivities(MWFProcess.java:281)

at org.compiere.wf.MWFActivity.setWFState(MWFActivity.java:277)

at org.compiere.wf.MWFActivity.run(MWFActivity.java:891)

at org.compiere.wf.MWFProcess.startWork(MWFProcess.java:503)

at org.compiere.wf.MWorkflow.start(MWorkflow.java:702)

at org.adempiere.util.ProcessUtil.startWorkFlow(ProcessUtil.java:310)

at org.compiere.apps.AbstractProcessCtl.startWorkflow(AbstractProcessCtl.java:373)

at org.compiere.apps.AbstractProcessCtl.run(AbstractProcessCtl.java:207)

at org.adempiere.webui.apps.WProcessCtl.process(WProcessCtl.java:158)

at org.adempiere.webui.apps.ProcessModalDialog$ProcessDialogRunnable.doRun(ProcessModalDialog.java:506)

at org.adempiere.util.ContextRunnable.run(ContextRunnable.java:38)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:138)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)

at java.lang.Thread.run(Thread.java:662)

Thanks,

Alex

[Alex Yang]

Hi Red1,

one more question: where is the original place for Carlos's GeneratePayrollInvoices.java.

I can't find it in https://bitbucket.org/CarlosRuiz_globalqss/globalqss-adempiere-hr

Thanks,

Alex

[Hiep Lq]

I play with HR module from DSC.

by compare code, I see it near same plug-in of red1.

Because I report some problem I think it error. please correct me if I wrong.

1. about HRCreatePeriods.

1.a enddate of first period is wrong in some case  (only DSC plug-in)

please see attach for detail.

I fix at: https://bitbucket.org/hieplq/liberohr_ve/commits/5bbecf5e65158f705f6d265f67741bfa3603c742

1.b before make period line I think should clear all period of this year.

1.c block code below  is not necessary:

               year.setProcessed(false); 

       year.save();

1.d current I can make multi year with same year value. 

1.e after run HRCreatePeriods, user can edit period, because i think make a new process to validate all period.

2. when run “Create concept for payroll” only concept has isPay = “N” and not concepted is use to make payrollConcept.

but when make payrollConcept in tab "Payroll Concept" nothing condition is filter. 

3. what is diff between of run process "payroll processing" and do complete document in "payroll process" window?

[Hiep Lq]

sorry. I miss attach file.

other problem I see.

4. window "Payroll Process"

4.1 in state drapt many field is can't change. event field don't enter. 

(Account Date, Payroll, Payroll Period)

4.2 period is mandatory field, but not mark that.

[Hiep Lq]

about "4.2 period is mandatory field, but not mark that."

When read more code. I know "period is mandatory field" is wrong.

but when don't choose a period a NPE is raise when execute "org.compiere.util.TimeUtil.getDaysBetween(period.getStartDate(),period.getEndDate())"

assume fix above issue.

Current code use new install of HRPeriod with startdate and endate = null. more processing will encounter

5. createMovementFromConcept

in this function. when concept.isEmployee()

In gui i don't see any window make a link of HR_employer and hr_attribute

because clause HR_Employee_ID = ? is necessary?

[Hiep Lq]

6. isEmployee

In guideline and source, I see isEmployee is active case. but in gui. I don't see any logic for display this field

i try by install from code and install form p2 directory of red1. 

isEmployee will remove?

[Tom Ssemwogerere]

Hi Gays.
I am happy that you are doing a good job. But I would like to request you to develop a a plugin for Agriculture production to capture field Operations.

Tom

[redhuan d. oon]

Hi Tom,
Thank you for your suggestion. Can you post at a new thread about your requirements? Than i can see how it can be adapted from any other plugin.

[Tom Ssemwogerere]

Attached are the requirements for idempiere plugin for Agriculture production to capture field Operations.

--
You received this message because you are subscribed to a topic in the Google Groups "iDempiere" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/idempiere/cYj10T3O8KM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to idempiere+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/15ee61e3-1982-4660-8568-11467b2beb7f%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Sherif Abou-Klila]

I did not find attendance sheet ,  and it's very important to any HR module, does it exist, if not what is your plan to handle it in the current plugin?  

[redhuan d. oon]

No, there is no attendance sheet.

[Saher Edris]

Hi everyone i could not create periods from year in payroll definition windows using "HRPayroll Create Periods" i'm getting

 "Failed to create new process instance for org.eevolution.process.HRCreatePeriods"

any idea's ?

thanks

[Vladimir]

A) Do I understand correctly that this pug-in is no longer supported and is not usable?

Just a few issues I came across that made it of a zero use:
1) sql example file does not work on the new iDempiere version
2) periods generation process results in Java error
3) Payroll Process run results in Java error.

B) Can anyone indicate any working solution for HR module in iDempiere?

[redhuan d. oon]

I have updated the plugin jar to iDempiere 4.1. (http://sourceforge.net/projects/red1/files/LiberoPayroll/) It can run and pack in. However the migration scripts was not properly done by me last time as it does not use centralised IDs. Otherwise you have to manually create the data.
I will try to fix that and update this thread again. As i have to test those processes and fix any bugs they have.

[redhuan d. oon]

Forgot to mention that if you follow my PDF manual carefully you may be able to test everything to confirm it anything is broken. I just moved a copy of LiberoHR.pdf to the same above here.

[Vladimir]

redhuan,
thanks  lot for the prompt reply and the intend to support the plug-in -- it is really a must-be feature for the iDempiere.
I commit to test the newly published update vs. the pdf guide. With the previous update I have done the step-by-step payroll process and this is what were the biggest catches:
1) Not all the steps are captures in the guide as it assumes the data are already in the system via sql. E.g. the set-up of the second employee should be guessed from the sql script code.
2) Concept Accounting tab of the Payroll Concept Catalog Window pre-fills the "Payroll concept" fild not as "CC_SALARY_Monthly Salary" as in the screenshot but as "-1_Monthly Salary" -- same as you have in the following screenshots in the pdf.
3) the "employee" check-box is not available in the "Concept" tab of the Payroll Concept Catalog Window -- it has to be loaded in the fields order of the this window set-up. W/o this box checked you cn not proceed with the business partner assignment.
4) Payroll definition window does not create the payroll periods for the year chosen. If done directly in sql base the periods are created OK.
5) When a new Process is created in the Payroll Process Window the "Document Type" field is defaulted to "Purchase Order" and can not be altered.
6) When run the Payroll Process results in an error.

Hope this list may be of a help for fixing the plug-in.
Thank you,
Vladimir

понедельник, 27 марта 2017 г., 14:19:49 UTC+3 пользователь redhuan d. oon написал:

[Vladimir]

redhuan,
Just tested the new update of the Plug-in (4.1.0.201703271712): the create periods process still results in error:

"Failed to create new process instance for org.eevolution.process.HRCreatePeriods"

Payroll Process stil results in error:

"Persistent Object not DocAction - org.eevolution.model.X_HR_Process - AD_Table_ID=53092, Record_ID=100000"

Thanks for digging into the issue.

Vladimir

[redhuan d. oon]

I have uploaded to same link the data_migration.sql for PG database. It will setup sample data and populate a 2013 year in Payroll Definition. Copy that to 2017 and run Create Periods does work for me.
Make sure your plugin is 'Active' in the OSGi console.

[redhuan d. oon]

You have to start fresh again in iDempiere DB or this new data will be in conflict. After applying the data_migration_pg.sql, login as SystemAdmin and run Sequence Check. Then in GardenWorld do as advised my previous post.

[Vladimir]

redhuan,
I will give it a try in line with your guidance. One asking though:
Can you, please, point me to the right step-by-step guide for copying data from one year to the other?

Thank you,
Vladimir

[Vladimir]

redhuan,
I tried to load the data from SQL file via the PostreSQL pgAdmin 4 but failed -- I must be doing something wrong :(. Here are my steps:
1) Dropped the iDempiere DB
2) run the RunImportIdempiere.bat from utils
3) Open the pgAdmin 4
4) Select PostgerSQL\Databases\idempiere\Schemas\adempiere
5) Run tools->Query Tool
6) In the Query: Open data_migration_pg.sql
7) click Execute/Refresh button.

Output shows an error:
ERROR:  relation "hr_contract" does not exist
LINE 3: INSERT INTO HR_Contract (HR_Contract_ID,NetDays,ValidFrom,De..

From my experience this apparently means that the database name HR_Contract is not specified for scheme choice. The change to adempiere.HR_Contract would work.

Can you, please, advise how could I your the sql data loader via pgAdmin?

Thank you,
Vladimir

[Mellina Videv]

Hi Vladimir

Why not you try this repository on https://bitbucket.org/ingeint/payroll_idempiere powered by ingeint it's more updated and maintained

regards

[Vladimir]

Thanks, Melina.
There are only 2 reasons for not using the plug-in:
1) It did not start (installed as plugin but could not get activated).
2) I could not find any guidance/tutorial on installing and using this plugin.

I am surely ready to try if you could help me with the p2 that would allow me to move further than p1.

Thank you,
Vladmir


среда, 29 марта 2017 г., 13:54:43 UTC+3 пользователь Mellina Videv написал:

[redhuan d. oon]

Vladmir,
You miss one step - 2.1) run idempiere-server with LiberoHR plugin installed and active.
That will pack in the basic menu structure and data model first.
Then the migration script inserts the data sample into the data model.

About your earlier question on copying data from year to year or do you mean creating new year periods?

[Vladimir]

"You miss one step - 2.1) run idempiere-server with LiberoHR plugin installed and active."

Thanks, I'll try.

"About your earlier question on copying data from year to year or do you mean creating new year periods?"

I refer to your earlier guidance:

"It will setup sample data and populate a 2013 year in Payroll Definition. Copy that to 2017 and run Create Periods does work for me."

What did you mean by "Copy that to 2017"?

Thanks

[redhuan d. oon]

At the 2003 year record, you click on the copy icon. Then change 2003 tp 2017. ..

[Vladimir]

You miss one step - 2.1) run idempiere-server with LiberoHR plugin installed and active.

I have repeated the attempt ensuring that 2.1 is done.
Still the same error when trying to load the .sql query.
I attach the screenshot if helpful.

Any ideal on how to fix the load?

Vladimir

[redhuan d. oon]

2.1 ... active <-- is it?

[redhuan d. oon]

OK, from your screenshot, it seems there is error in executing script properly. Have you done any other scripts successfully before?

[Vladimir]

I have run the iBudget....sql -- seems like successfully: there was no response message but AD_Message table was properly populated.
LiberoHR....sql I was able to almost fully execute line-by-line when replaced each [table_name] with [adempiere.table_name].

[Vladimir]

redhuan,
Meanwhile, I have done the following on a fresh Idempiere DB, with LiberoHR installed and active (PG 9.6, iDempiere 4.1.0):

Under System login
1) Created new Client (ADempiere 3.4 ERP Solutions, Bayu Cahya Pamungkas, p 70-72)
2) Loaded AccountingUS.csv COA (ADempiere 3.4 ERP Solutions, Bayu Cahya Pamungkas, p 80-83)
3) Made visible Employee check-box in  Payroll Concept Catalog via "Window, Tab & Fields" setup

Under admin login
4) Created new Payroll Contract in Payroll Contract Window (LiberoHR.pdf p16)
5) Created a new Concept in Payroll Concept Catalog Window/Concept tab (p19 )
6) Defined new Payroll in Payroll Definition/Payroll tab (p22, see the screenshot)
7) Defined new Year (2017 from drop-down list) in Payroll Definition/Year tab (p23, see the screenshot)
8) Run the HRPayroll Create Periods process in Payroll Definition/Year tab

RESULT: An Error. See screenshot attached

Could you repeat these simple steps to see if the error is replicated?
How can I get you more information for troubleshooting?

Vladimir

[redhuan d. oon]

Please test according to my original advice above. So that the cause of error is eliminated before proceeding to involve new steps. Else i cannot assist.

[Vladimir]

redhuan,
I test according to your original advice.
Test result: test fails at the step "applying the data_migration_pg.sql" with the error mentioned above.

What can I do to proceed with the test?
Vladimir

[redhuan d. oon]

OK, repeating my same response to the same failure. This time i also give a screenshot to show that it works here.
Sometimes database has other issues and i always struggled with them. I would have to research why a particular line does not work.

[Vladimir]

Quick update:
the error when running the script is caused by a wrong "search_path" variable used by pgAdmin.

Troubleshoot details:
PostgreSQL 9.6 requires the queries to use full address of a table in the form "[schema_name].[Table_name]".
To simplify query the Postgres uses a "search_path" variable. Any table within a schema, included into the list of search_path allows simplified reference [Table_name]. By default it is set to "$user",public . Therefore the "adempiere" schema is out of search.
Role "adempiere" created by the RUN_ImportIdempiere.bat contains a parameter "search_path" set to "adempiere,pg_catalog". Therefore "adempiere" schema is included in search if a user s logged with the "adempiere" role.
I am somehow logged into the "PostgreSQL 9.6" server under a role different from "adempiere" (and I have no clue how to change the role logged). This causes an error when running any script with a simplified table reference.

Solution:
To change the search_path the SET command should be used: SET search_path TO myschema,public; (http://postgresql.ru.net/manual/ddl-schemas.html#DDL-SCHEMAS-PATH)

To run the data_migration_pg.sql I've done the following steps:

1) Start PostgreSQL ('pg_ctl start -D C:\postgresql\data' in Widows Command prompt)
2) Start iDempiere server ('idempiere-server' in Widows Command prompt)
3) Run pgAdmin 4
4) Select idempiere Database
5) Run Query tool (Tolls -> Query tool)
6) Open data_migration_pg.sql
7) Add as a 1st line the command 'SET search_path TO adempiere;'
8) Execute the query.

The query runs with no errors.

May it be that the errors in the LiberoHR module is caused by a wrong role used to start PostgreSQL?

I'll continue the testing/troubleshooting.
Vladimir

[Vladimir]

redhuan,
Proceeding to test according to your original advice.
Environment
iDempiere server run, LiberoHR Active, data_migration_pg.sql executed

Test

After applying the data_migration_pg.sql, login as SystemAdmin and run Sequence Check

Done
1) Log into iDempiere as System
2) Run Sequence Check Process.
Result: List of entries generated
Done
3) Rerun Sequence Check Process.
Result: No Errors, No List of entries

Test

setup sample data and populate a 2013 year in Payroll Definition. Copy that to 2017 and run Create Periods

Done
1) Log into iDempiere as GardenAdmin
2) In Payroll Definition/Year
1. Duplicate 2013 entry
2. Change Year to 2017
3. Change Start Date to 01/01/2017
4. Save
5. run Create Periods

Result: Error: Failed to create new process instance for org.eevolution.process.HRCreatePeriods

Can you, please, advise on how to proceed?

Thank you,
Vladimir

[redhuan d. oon]

Yes, SET SEARCH_PATH TO ADEMPIERE; is the right pre-step when dealing in Postgresql Database where there exists more database schemas. As i stated the LiberoHR plugin works well. Other errors have to be confirmed as not pertaining to outside factors such as OS, AppServices, clients and databases.

[redhuan d. oon]

Since you do not give error stacks as the practice i have to assume your idempiere cannot load external plugin processes. Then eliminate that possibility by testing a more simpler plugin in the Available Plugins page.

[Vladimir]

"Then eliminate that possibility by testing a more simpler plugin in the Available Plugins page."

Thanks,
Can you, please, advise what be the right plugin to choose -- simplest yet still meaningful for test purpose.

Thank you,
Vladimir

[redhuan d. oon]

OK, you can try http://wiki.idempiere.org/en/Plugin:_QuickEntry.
There is a YouTube movie link there to see how to use it. If the process doesn't work then its not any plugin fault, but has to be the iDempiere stack in general. 

[Vladimir]

redhuan,
I have tried the QuickEntry plug-in. It works step-by-step as in the tutorial video -- no errors.
How can I identify the root-cause of the HR Plugin error?

Thank you,
Vladimir

понедельник, 3 апреля 2017 г., 2:41:36 UTC+3 пользователь redhuan d. oon написал:

[redhuan d. oon]

OK, let me take a look at the HR plugin in a day or so. Busy finishing up the WMS first release at the moment.

[Orlando Curieles]

Hi, I Updated our Payroll plugin to iDempiere 4.1, please check on this url.

https://bitbucket.org/ingeint/payroll_idempiere

Regards

--
You received this message because you are subscribed to the Google Groups "iDempiere" group.
To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/93b39b30-7523-4be1-af19-4a32298dddd8%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[redhuan d. oon]

Now back testing, and i noticed i upgraded the binary to iDempiere 4.1 dated March 29th. (Only now i also committed this change to https://bitbucket.org/red1/liberohr)

Now i could run data_migraton_pg.sql but i forgot to run the tickets script. However i still could go into the HR Payroll Definition, create new Year 2017 and RUN Process - HRPayroll Create Periods. It complained of duplicate periods, so i deleted 2013 periods and resume it worked. See attached screenshot. If you still have errors try getting someone else who can troubleshoot your PG DB.

On Sunday, 21 May 2017 01:46:57 UTC+8, Vladimir wrote:

[redhuan d. oon]

I forgot to run Sequence Check. That solved the error i had myself just now.

[Vladimir]

Orlando,
thanks for your attention to this issue.
Unfortunately your plug-in did not work for me: I have installed it via the Felix Web Console (it appeared in the list as installed) but when I tried to activate (pushed the "play" button) this did not work -- status remained "installed".

Vladimir

вторник, 23 мая 2017 г., 16:21:31 UTC+3 пользователь Orlando Curieles написал:

[Vladimir]

Thanks, Redhuan.
I am using the plug-in "LiberoHR_4.1.0.201703271712".

What I found out:
When I install the plug-in, activate it and load Idempiere (Web UI) -- there is no guarantee that the plug-in is still active. When I refresh the Web Console, I see the plug-in missing as if it was not installed.
In cases when I refresh the Console (in a parallel window) and the plug-in still shows status "active", the periods are processed with no error.

My conclusion would be that the issue is not specific plug-in functionality but it's stability within the Idempiere in general. Any advise on how I can make the plug-in "sticking" will be appreciated.

Thank you,
Vladimir

понедельник, 29 мая 2017 г., 5:51:26 UTC+3 пользователь redhuan d. oon написал:

[Orlando Curieles]

Hi, i think you have another problem, I have installed this plugin on a clean database and work perfectly, please attach your log to see the error.

Regard

[Vladimir]

Surely, Orlando,
there is some issue in my specific installation of PG-Idempiere-plugin.

If you could advise how to collect the log, I'll try to test again.

Thank you,
Vladimir

понедельник, 29 мая 2017 г., 14:19:34 UTC+3 пользователь Orlando Curieles написал:

[tobias.t...@gmail.com]

Hi Everyone,

I managed to get the Libero HR and Payroll Plugin running with idempiere 5.1, by installing the most recent .jar via Eclipse's OSGI console and activating it (as described in the manual).
https://netcologne.dl.sourceforge.net/project/red1/LiberoManufacturing/org.lib.mfg4_4.1.0.201706070027.jar
https://10gbps-io.dl.sourceforge.net/project/red1/LiberoPayroll/LiberoHR.pdf

Everything works quite fine except for one issue: I can't setup the "Payroll Employee->Attributes" because I cannot select a "Payroll Concept" even though it definitely exists. Is this a bug, or am I missing something. Does some of you guys have a hint or a workaround?

Help appreciated, thank you very much in advance.

Regards,

Tobias

[tobias.t...@gmail.com]

Sorry for double-posting, but I found the issue, there were in fact two problems:
- The employee-marker in "Payroll Employee->Business Partner" was set to be shown in column 5 of the window, which caused it to not being shown.
- The dynamic validation rule of the "Payroll Concept"-field in "Payroll Employee->Attributes" prevented all payroll concepts from being shown. After deactivating it in the respective record of "Table and Columns", the concepts were shown.

But now, when I keep following the Manual from Reduan, which is pretty good btw, I encounter another problem when trying to porcess my payrolls:
- The processing of the payroll doesn't seem to create the according transactions/movements for the affected business partners. Other accounting processes seem to work, I checked it with processing of a Purchase Order/Invoice, which creates the respective transactions.

Help appreciated! Best regards,

Tobias

[redhuan d. oon]

Thank you for following my documentation manual carefully. It should solve everything including the accts posting. You can point to me which part/page you are reading and not able to understand. I may have to explain in further detail. It is been some time since i look into it, so giving reference from my manual help me to trace and see if it is obvious right away your omission if any.

[Derek Lew]

Hi all,

i have tried this plugin, but there isn't a Employee checkbox in Payroll Concept Catalog window.  And it seems from the code, the IsEmployee field is always set to false.  

How do I enable IsEmployee to true?

Best regards,

Derek

On Thursday, January 10, 2013 at 6:48:53 PM UTC+8, redhuan d. oon wrote:

I am now focusing on this and invite any functional review comments of Libero HR as expanded by ADempiere LVE at this forum thread http://red1.org/adempiere/viewtopic.php?f=29&t=1729. It is due to be completed by end of February.

[Derek Lew]

Ok, found out, just run this sql.

update adempiere.ad_field set IsDisplayed = 'Y', IsDisplayedGrid = 'Y', seqno = 150, seqnogrid = 150 WHERE ad_tab_id = 53111 and ad_column_id = 54827;

[Derek Lew]

After Completed the Payroll Process, there is nothing shown in the Account Viewer, what could have been wrong?

[Derek Lew]

The Hr_movement was generated.

[Alejandro Guerra]

hi Derek,

You configured the accounting of the concepts?

[Derek Lew]

Yes, I had.

[Alejandro Guerra]

hi Derek,

Can you check if the moves have?

Regards,

[Derek Lew]

Yes.

[Derek Lew]

And i am seeing lots of this error.

MLookup.doRun: AD_Field.AD_Field_ID: Loader - Too many records, Column=AD_Field_ID, Table=AD_Field_Trl [448]

[Derek Lew]

I found the issue, I did not set Account Sign.

[Satish Vijayan]

Hi All - is there a write up on how to configure libero payroll?

On Monday, April 9, 2018 at 12:18:21 PM UTC+5:30, Derek Lew wrote:

[redhuan d. oon]

Have you tried reading LiberoHR.pdf? https://sourceforge.net/projects/red1/files/LiberoPayroll/LiberoHR.pdf/download

[Satish Vijayan]

I finally go around to this. I get a pack-in error now.

org.adempiere.exceptions.AdempiereException: org.adempiere.exceptions.DBException: org.postgresql.util.PSQLException: ERROR: insert or update on table "hr_concept_acct" violates foreign key constraint "hrconcept_hrconceptacct"

  Detail: Key (hr_concept_id)=(1000000) is not present in table "hr_concept".

[Satish Vijayan]

@ red - I get a pack-in error when adding the module. It looks like some base data has to be added before I pack-in. Where would this be available?

[redhuan d. oon]

Hi, you have to furnish me the error part. I just tried it and it has none (see screenshot). I am testing on my latest source https://bitbucket.org/red1/liberohr

[redhuan d. oon]

OK, i see your error. Perhaps you already packed in an older LiberoHR? You have to try again on a fresh iDempiere then.