johndanter
Legendary Poster
Hi list,
I have had an odd situation today with an EDI subsystem that creates POs in PY.
It's goal is to create PO with a next number from the DCT FY CO F00021 setup so all POs start 15nnnnnn (this year)
What I found was the subsystem was actually creating POs with 14nnnnn but manual runs of the exact same UBE would correctly produce 15nnnn DOCOs
I took a log of the manual UBE and then got CNC to relaunch the SBS with logging on. Sent in a signal and it worked! DOCO = 15nnnnn
So I have deduced that the SBS must be caching the FY pattern info somewhere?
How can I check this and is it a good idea to cache such sensitive info
Thanks
John
I have had an odd situation today with an EDI subsystem that creates POs in PY.
It's goal is to create PO with a next number from the DCT FY CO F00021 setup so all POs start 15nnnnnn (this year)
What I found was the subsystem was actually creating POs with 14nnnnn but manual runs of the exact same UBE would correctly produce 15nnnn DOCOs
I took a log of the manual UBE and then got CNC to relaunch the SBS with logging on. Sent in a signal and it worked! DOCO = 15nnnnn
So I have deduced that the SBS must be caching the FY pattern info somewhere?
How can I check this and is it a good idea to cache such sensitive info
Thanks
John