infor.com
concierge
infor u
developer portal
Home
Groups
FACTS - Partner Community
Apply payroll changes to facts 7.5
dustin-ward
Are there any resellers that are trying to implement payroll changes into a facts 7.5 customer code base? I am running into problem with check update. Neither code base seems to fit exactly into 7.5.
I have fixed PRR211 for 7.5, but am stuck on problem. In the 77 version of PRR211 and PRR215, the programs reference a file 21 that I can't find being opened any where.
The information takes the place in the 6200 code to get fields H6$, I6$, J6$, K6$
file 21 is written in new routine 7100, which replaces previous routine 6100
If anyone knows what file 21 is please let me know.
Find more posts tagged with
Comments
peter
I believe what you are looking for is in PRR211 lines 790 and 795.
0790 let X=21,M$="SMSRT"
0795 call "prog/SM/SMC160",0,X,M$,Z8$; if Z8$>"" then goto 9900
0911060553270289.pdf
dustin-ward
Thanks very much for your help.
All the versions of PRR211 I looked at don't have lines 790-795.
Do you know what version of PRR211 you were looking at, or what is says on line 35?
peter
I reviewed both the 7.1 and 7.7 versions of the payroll changes. Lines 790 and 795 should be in both of them.
dustin-ward
I must have been looking in the wrong place
Does anyone know if the pr2011_77.zip installation will work seamlessly with facts 7.6?
Or are modifications needed, like for facts 7.5?
greimer
Review the Payroll change instructions. pr2011_71.zip is to be used for FACTS 7.1 [?] to FACTS 7.6. The pr2011_77.zip is for FACTS 7.7. Along with the 7.1 to 7.6 version is a UP program. I applied both _71 and _77 yesterday and clients used each of them shortly thereafter. No issues were brought to my attention.
jeff-christie
I took a call from a 7.7 customer who ran payroll following the changes. They run the Check Reg through Job Stream and we received an error in PRR211. I really wasn't involved in doing the payroll upgrade, but from what I gathered, there is a missing open line at 300 that is in PRR210, thus only JS hits this. I believe this was an issue with 7.7 originally and a temp fix to add line 300 was given, but PRR211 was replaced with this upgrade and the line was missing again (and now readded again)..
heike-tommack
We've run into an issue installing the changes on a 7.5 system. The PRR215 that is included in the 7.1 zip references SMCKHR in the 4400 block and SMLEDG in the 7000 block. Those files went away in 7.5 and the SMTRNH files were introduced. Can we drop the 7.7 version of PRR215 in place or pull the 4400 and 7000 block from the original 7.5 code?
[Updated on 1/11/2011 12:35 PM]
greimer
I applied PRR215 onto a 7.6 system with the same SMCKHR issue noted before. I think the resolution is to take the 7.5 [7.6] version and insert lines 370, 395, 2810, 3810, and 3880 from the new version. Then remove all 6200-6299 lines from the original and replace them with 6200-6299 of the new version.
birstSpaceMonitoring.html.zip
0906221039165974.pdf
Legacy Contributor
I follow up the steps for FACTS 7.5 to let the original 7.5 PRR215 and apply the changes from the upgrade (insert lines 370, 395,2810,3880), remove lines 6200-6299 from original and replace them 2ith lines 6200-6299 from new version but we are getting an error 23, in line 4405 in PRR215 . Any ideas??
Legacy Contributor
I suspect the problem is because the string template was never dimed out in PRR211. See if you got rid of the DIM_TEMPLATE procedure at 20200 in PRR211
Legacy Contributor
What changes do you apply to PRR211 to fixed for FACTS 7.5
Legacy Contributor
After reviwing the changes to PRR211 for payroll the new program does not include this line. May be the best to approach this will be to add th changes to the FACTS 7.5 version of PRR211
Wichtige_Lösungen_in_der_Wissensdatenbank_Juli_2012.pdf
Important Links
Community Hubs
Discussion Forums
Groups
Community News
Popular Tags
ION Connect
ION Workflow
ION API Gateway
Syteline Development
CPQ Discussion Ask a Colleague
Infor Data Fabric
Infor Document Management (IDM)
LN Development
FAQs, How-To, and Best Practices
API Usage