PubdatacurrentDate issue returning 00 hour

When we call currentDate passing it a pattern of HHmm we get the hour of 24 when we expect 00. In other words, when the time is after midnight and before 1:00am, the hour of 24 is returned. 12:30am is displayed as 2430 which should be displayed as 0030.

Has anyone else run into this?

I saw that with the kkmm pattern (24:01). Changing the pattern to HHmm solved it (00:01).
Interesting let us know the cause.

We also had the same issue. Pattern kkmm need to be changed to HHmm in several places(eg: WmEDI services addGroupEnvelope, addICEnvelope etc.,).

Upon further investigation we found that a few webMethods EDI services need to be updated since they have a pattern of kkmm instead of HHmm.

  1. wm.b2b.edi.util:addGroupEnvelope
  2. wm.b2b.edi.util:addICEnvelope
  3. wm.b2b.edi.util:addICEnvelopeEDIFACT

Ray,

Interestingly I reported this and the GS06 problem to Tech support in 4.6 and found that they still existed in 6.01. The other issue with addGroupEnvelope is that the GS06 is still treated as a alphanumeric with leading zeros where the Standard dictates that it numeric. Your Partners will drop the leading zeros and the FA’s won’t reconcile.

HTH

FYI
WmEDI_6-0-1_Fix7 solves the above mentioned problem. It only refers to addICEnvelopeEDIFACT and not just addICEnvelope.
Wonder what that means?

Article ID: 1610880442 What is this?
Quick Access URL: [url=“http://advantage.webmethods.com/article/?id=1610880442”]http://advantage.webmethods.com/article/?id=1610880442[/url]
Release Date: 16-May-2003
Description Fixes the time pattern from “kkmm” to “HHmm” for addICEnvelopeEDIFACT service.

Fixes AK2 segment overwrite problem for generateFA service.

Hey,

Is there any fix for this in 4.0.2.

Thanks,
Madhu M.