Upgrading to FACTS 9.0.2 results in SOCRSL records without SOCRSH records

We recently upgraded a customer from FACTS 7.3 to FACTS 9.0.2. After the upgrade, we found that SOCRSL (Customer Returns Document Lines) had records without corresponding SOCRSH (header) records. This happened to multiple customers of ours that we upgraded to FACTS 9.0.2.

Infor has asked that I reach out to the partner community to see if this has happened to anyone else. If it has, please respond - thanks!

Brad Kraft

Aktion Associates

Find more posts tagged with

Comments

kevenh

We recently upgraded a customer from 7.7 to 9.0.2, who uses CRS quite a bit. I just checked their files and they are fine. I'm surprised you would have SOCRSL records without a corresponding SOCRSH record since UPSOCRSL specifically checks for this in the UP7800 section:

0690 read (socrsh,key=crs_a0$+crs_a5$,kno=0,dom=*next)*,*,crs_a2$,crs_h8$,crs_c5$,crs_d5$,*,crs_w1$; auth=crs_c5$(1,1)="A"; goto 0705

0695 skip_rec=1; goto *return ! header not found, don't bring this CRS line forward

Have these lines maybe been changed or missing from your UPSOCRSL?

salbritton

Keven, those lines are there. What we found was that lines 1045 and 1050 in UP0700 needed to be swapped. The reason is that UPSOPCRH is increasing the size of the key field from 6 to 10 before the SOCRSH adjustment to the key size is made. Any records in SOPCRH that have the identical 2 characters in the (old) 6 character document get overwritten by subsequent write to SOCRSH. Either UPSOCRSH needs to be run before UPSOPCRH or UPSOPCRH needs to leave the key field alone and allow UPSOCRSH handle it.

As I said, I wasn't the only tech in our company to come across this issue. Infor now has the original data files from the customer and is looking at this further.

Copyright © 2025 Infor. All rights reserved.