FOLIO not sending ACK to remote storage (dematic)

Description

Overview: FOLIO is not acknowledging an IR when a barcode is missing

Steps to Reproduce:

We had another incident yesterday with an item that caused a problem about a month ago.

Image
This EMS record has no barcode. We are working with Dematic to get it deleted from the EMS database as it continues to cause issues. However, Dematic responded:

1:10 AM EDT - I reviewed the system documentation. The IR message is ItemReturned according to the appa_innovative millenium.doc It says This message notifies the LCS that an item has been returned without the LCS requesting the return. There are plenty of examples of IR messages being sent OK but they have codes in them like these for example

hs1.06: prcDate )VALUES (2259688,'SENT','',0,'IR','040-109653937 000','00000','hs','2024/04/04 21:27:19.00','0000/00/00
hs1.06: prcDate )VALUES (2259689,'SENT','',0,'IR','040-106817204 000','00000','hs','2024/04/04 21:29:45.00','0000/00/00
hs1.06: prcDate )VALUES (2259690,'SENT','',0,'IR','040-106817204 000','00000','hs','2024/04/04 21:35:38.00','0000/00/00
hs1.06: prcDate )VALUES (2259691,'SENT','',0,'IR','040-111130696 000','00000','hs','2024/04/04 21:39:12.00','0000/00/00

this one

..............prcDate )VALUES (2261001,'SENT','',0,'IR',' 000','00000','hs','2024/04/08 14:47:21.00','0000/00/00

is different in that it has no barcode. It should not matter that the message without a barcode makes little sense to the receiver. Standard practice dictates that readable messages should always be ACKed. The recommendation is that the Host system should ACK the message and ignore it.

Is it possible for FOLIO to send an ACK back to EMS for messages like this?

Expected Results: The message is acknowledged

Actual Results: The message is not acknowledged

Additional Information: This Dematic EMS system connects to FOLIO via StagingDirector's TCP/IP integration points
URL:

Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

Activity

Show:

Tetiana Gusar August 29, 2024 at 10:16 AM

As discussed in slack this issue can be done after

Stephanie Buck July 31, 2024 at 1:37 PM

Hi . I’m working on getting logs to you.

Regarding the 004 message, it means that the Item is missing. Folio needs to respond to the 004 message as if it was a 000 message and then ignore it internally. It should log the error and then consider the request complete.

cc:

Gurleen Kaur1 July 30, 2024 at 12:41 AM
Edited

Hi ,

Unfortunately I really can't make out much from that message. In edge-dematic logs the payload will be printed which will have the string like ----- Status channel handler income: <payload>

Therefore, can the payload without barcode be fetched from the logs ? Or please provide us the log dumps for edge-dematic when the barcode is not present.

https://github.com/folio-org/edge-dematic/blob/a4d59f846ded3b90761c4f823e5dcf555bd5b939/src/main/java/org/folio/ed/handler/StatusChannelHandler.java#L27

Please also confirm what does the error code 004 means ? The same can be added in the StagingDriectorErrorCode Enum file ? What is the folio application suppose to do in case of 004 error code should it just return a TR message ?

Stephanie Buck July 29, 2024 at 4:29 PM

Hi . In the initial email from UMKC, the IR message without a barcode looked like this: ...prcDate )VALUES (2261001,'SENT','',0,'IR',' 000','00000','hs','2024/04/08 14:47:21.00','0000/00/00.

cc:

Gurleen Kaur1 July 29, 2024 at 9:31 AM
Edited

Hi

Can you please provide some IR messages without a barcode? For example, with a barcode, the message payload is: IR0000120200101121212697685458679 000. The barcode in this case is 697685458679. According to this Jira, the barcode will not be present. What will the message look like then?

Will it be like this: IR0000120200101121212000000000000 000, where the barcode value is transformed to all zeros? As i believe the IR message length has to cater to the length specifications as of the current code that specifies as 36

CC: ,

Details

Assignee

Reporter

Priority

Development Team

Volaris

Release

Not Scheduled

RCA Group

TBD

Affected releases

Orchid (R1 2023)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created April 19, 2024 at 5:12 PM
Updated August 29, 2024 at 10:16 AM
TestRail: Cases
TestRail: Runs