HuskyBuy integration issues
Invoices failing sync to KFS due constraint on FP_DV_PAYEE_DTL_T for city/town character limit (45 characters). The error shown for this is a 500 message in the HB invoice history.
2. Invoice failure due to no Remit assigned to the fulfillment center, causing the invoice to fail. If no remit is assigned on the supplier fulfillment center, the supplier profile will assign the -0 remit to the -1,2,3 etc as a primary fallback. In this situation below, Business Services created the remit but failed to assign it to the fulfillment center.
3. Supplier sync failure due to Business Services modifying "Locations" or switching addresses between divisions. The HuskyBuy(HB) SQIN can cause issues if it's used across multiple divisions/fulfillment centers in HB. Switching addresses between fulfillment centers seems to cause issues in the integrations. If the supplier fails to sync due to the below error, creating the addresses from new should fix the issue.
-----Original Message-----
From: kfsbatch-noreply@uconn.edu <kfsbatch-noreply@uconn.edu>
Sent: Tuesday, May 17, 2022 3:55 PM
To: Patrylak, Nancy <nancy.patrylak@uconn.edu>; Klaben, Jim <james.klaben@uconn.edu>; Heinze,Garrett <heinze@uchc.edu>; Martin, Sean <sean.2.martin@uconn.edu>; Williams-Huang, Heather <heather.williams@uconn.edu>
Subject: KFS : Jaggaer supplier export error
There was an error processing the supplier sync data from Jaggaer.
While the KFS vendor passed business rules, it encountered an error during it's document routing.
The following suppliers were attempting to route:
Supplier name: Johns Hopkins University , Supplier number: 18460-5 Supplier name: Johns Hopkins University , Supplier number: 18460-3 Supplier name: Johns Hopkins University Supplier name: Johns Hopkins University , Supplier number: 18460-4
Errors:
document.newMaintainableObject.vendorHeader.vendorTaxNumber:The vendor parent of this vendor needs to be changed, please contact Purchasing Dept.
<<RE_ KFS _ Jaggaer supplier export error.msg>>
4. Generally, seeing "Primary Fallback" on any of the fulfillment centers is bad. This seems to cause issues. Sometimes simply removing the "Primary Fallback" from the supplier in HB can fix supplier integration errors. You can remove primary fallback by editing the assigned address, assign a new address, then save. You can now assign the original address and then saving again. This should remove the fallback label.
5. Occasionally, the ERP sync will get stuck and the integration is "paused". If there is an ERP number, we can fix this using a web service. If there is no ERP number, a ticket will need to be created with Jaggaer to fix the supplier.
6. The ultimate way to resolve integration issues where the KFS vs. HuskyBuy information does not match is to compare records in PUR_VNDR_ADDR_T for the VNDR_ADDR_GNRTD_ID, and see what VNDR_DTL_ASND_ID each address id belongs to. You can also further filter down this information by using a "Y" in DOB_MAINT_CD_ACTV_IND. By performing this exercise, you can confirm what address IDs are active in KFS, and what divisions they belong to. If something does not match up against HuskyBuy, then you can narrow down where the issue is from here. See spreadsheet for example comparison (this is what I did for 3. above).
<<18460-0.xlsx>>