Cannot Insert NULL Error - "WMTN"."EDICONTROLNUMBER"."SENDERID"

Hariharan_m · January 31, 2012, 3:19pm

Hi,

The below error is encountered while trying to fetch the control number from EDIControlNumber table.

com.wm.app.b2b.server.ServiceException: java.sql.SQLIntegrityConstraintViolationException: [wm-cjdbc40-0034][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“WMTN”.“EDICONTROLNUMBER”.“SENDERID”)

The SenderID, ReceiverID etc are being passed in the input to the service fetching the control Number.
Also, the Partner IDs are set-up for Control Number generation on MWS.

Can any one please help identify the cause for this issue.

Thanks & Regards,
Hari

gupta_r.17495 · January 31, 2012, 8:05pm

Which service are you running and what are you trying to do with control numbers from UI or custom service thru?

HTH,
RMG

Hariharan_m · February 1, 2012, 12:58pm

The service executed is “wm.b2b.editn.batch:getControlNumber” to which the required inputs - TNsenderID, TNreceiverID, standard, type, update, prodMode and version - are being passed. The control number generated is used as the ICN# in the oubound EDI document generated. Please let me know if there is any other I can provide.

Thanks,
H

gupta_r.17495 · February 1, 2012, 8:47pm

Instead of via this service why don’t you configure in teh WmEDI homepage Manage Control Numbers section and have it configured desired?

Also the error indicates some constraint violating in the table may be dups with the sender/receiver combination…Did you check the table entries?

Hariharan_m · February 1, 2012, 10:04pm

The control number generation is configured in MWS as the feature in wM EDI module 8.0 is deprecated. The service is used to fetch the control number from the wmTN data base (EDICONTROLNUMBER table). Also, one thing as you mentioned, I noticed today is there were duplicate entries present for the given Sender/Receiver combination. However, was not sure if that could be cause for this issue. Will try deleting the duplicate set-ups tomorrow and testing the process again.

Thank you rmg.

Cheers!
H

gupta_r.17495 · February 1, 2012, 10:20pm

Yes you are right,even its deprecated via EDI home page you can still make it enable and edit it or use MWS itself to get more used…

Yes please check the dup entries and see how testing goes:

Please contact SAG tech support also if some fix available or make them aware of this issue:

HTH,
RMG

Salam_Marhoun · May 14, 2014, 2:27pm

Hi Hariharan_m *

I am facing same problem. Did you solve your problem? if yes, what was the solution?

anybody input in this is appreciated.

rmg · May 14, 2014, 3:32pm

Salam,

What was your exact problem with the Control Numbers generating from the TN DB or dup control numbers issue?

Also what is your IS/TN and EDI Module versions facing the issue?

HTH,
RMG

Salam_Marhoun · May 15, 2014, 6:45am

Version 8.2 but MWS is not enabled and I used wM EDI module 8.0 to add those control numbers.

I am not sure what is the problem but i am using service wm.b2b.editn.batch:getControlNumber and it through that error.

Salam_Marhoun · May 15, 2014, 7:44am

New update:

The service is working fine if I set parameter “update” to “false” which will not increment the control number in the table.

This led me to a conclusion that the problem is with the update process.

rmg · May 15, 2014, 3:15pm

Yes it make sense to adjust the field setting and glad to hear it resolved and not a bug

HTH,
RMG

Salam_Marhoun · May 18, 2014, 6:11am

The problem has not been solved yet… because the parameter should be true to increase the control number each time i send a documents.

waiting for any suggestion.

Malli_Venkateswarlu · April 7, 2015, 7:35pm

Hi Salam,

I also faced the same issue in WM9.0 and was able to fix by adding the configuration parameter EDIAllowCustomControlNumberSequences = strictCompatibility in the file properties.cnf. This file is located under WMEDI\Config folder. You may have to re-load the package after changing the property. Hope it will help you if your issue is still exists.

Thanks,
Venkat.

rmg · April 7, 2015, 7:41pm

Yes this should be the work around in 8.x and 9.x EDI module configuration and you can do this via MWS screens.

In 8.x it is set as “EDIAllowCustomControlNumberSequences=true”

HTH,
RMG

Deepika_Singh1 · July 17, 2018, 5:42pm

Hi,

The issue has been addressed in following KB article:

https://empower.softwareag.com/sl24sec/SecuredServices/KCFullTextASP/viewing/view.asp?prdfamily=webMethods&KEY=108351-14593233&DSN=PIVOTAL&DST=TCD

Description:
The following error occurs when running the IngEdiUtilities.edi:addICEnvelope Service in the WmEDI package:

“java.sql.SQLIntegrityConstraintViolationException: [SoftwareAG][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into (“WMTN”.“EDICONTROLNUMBER”.“SENDERID”)”

What could be causing this error, and how can it be resolved?
Resolution:
Follow the below steps to resolve this error:

Copy the sample-properties.cnf file from the
<IS_directory>\packages\WmEDI\config directory
to properties.cnf file in the same directory.
Edit the copied
<IS_directory>\packages\WmEDI\config\properties.cnf file, and add/modify this parameter as follows:

EDIAllowCustomControlNumberSequences = strictCompatibility

Re-load the WmEDI package.

rmg · July 17, 2018, 10:33pm

Deepika,

Thanks for updating this old thread!!

Appreciated!!

HTH,
-RMG