EDI number assignment: Cannot determine customs number

[dean_hinson2]

Hello All,

I have been trying to output an XML file.  I thought I had everything configured correctly, the Port, the Partner, the Customs Office and the Trader Identificatin Numbers.  The message shows correctly in the Communications tab of the Customs Declaration but when I try to execute the message, I get a popup error...

EDI number assignment: Cannot determine customs number.

What did I miss?

[dean_hinson2 · Accepted solution]

Hello All,

I have found the issue.... trader id numbers for the representative/broker.  I maintained for the 'dummy' customs office but not the representative/broker.

The error is raised in the include /SAPSLL/LLEG_ECC_IPF02 in the EDINR_NUMBER_GET routine. Check out the code after comment *------- TIN des Nachrichtenübermittlers aus Partnertab ermitteln.

FYI, I am on GTS 10.0 patch 12.

Thank you for all your help.

[former_member215181 · Accepted solution]

Hi Dean,

Ah yes, the Message was delivered in SP12, for ATLAS processing.  The systems I was looking at were only at SP9.

Glad that you found the problem.

Regards,

Dave

[former_member215181]

Hi Dean,

Could you please confirm the message number (click on the "question mark" to bring up the message long text).  I'm struggling to find the message text that you quoted.  So far I've only found these:

/SAPSLL/CUS_ECC 288 Cannot determine customs number of message transmitter

/SAPSLL/CUS_ECC 050 EDI number assignment not maintained for number range &1

As you can see, neither quite match your text.  If you can provide the Class and Number, we should be able to find out what's happening in your situation.

Thanks & regards,

Dave

[dean_hinson2]

Hello Dave,

The error message is :

EDI number assignment: Cannot determine customs number

Message no. /SAPSLL/CUS_ECC049

I tried using the where-used from SE91 but found nothing. If I could find the code where this error is raised, I could have figured it out (hopefully). 

Any suggestions?

[mouaz_benredjeb]

Hi Dean,

I have seen that the message /SAPSLL/CUS_ECC049 is used in at least the following programs. But I cannot guarantee that it is used only in these programs, it could be that the message is used elsewhere too:

Program /SAPSLL/LLEG_ECC_IPF20 / FORM ccm_edinr_number_get

Program /SAPSLL/LLEG_ECC_IPF02 / FORM edinr_number_get

Program /SAPSLL/LLEG_ECC_IPF02 / FORM ped_edinr_number_get

If you feel comfortable with debugging, try to set a break point in the above programs/routines and check what is happening in debug mode.

Hope this helps.

Regards.

Mouaz BEN REDJB

[former_member215181]

Hi Dean,

That message number doesn't exist (in my systems).  Which GTS version are you using?

Regards,

Dave

[mouaz_benredjeb]

Hello,

Have you maintained number ranges for EDI messages ?

Regards.

Mouaz BEN REDJEB

[dean_hinson2]

Hello Mouaz,

Yes, I did.  I should have included that bit of information in the original discussion text.

Thank you for your quick reply.

[mouaz_benredjeb]

OK.

In your declaration, do you have a Declarant partner function ?

[dean_hinson2]

No, I do not. We are triggering this file generation by using a carrier partner type and default data.  We want to send data in electronic form to a carrier to expedite paperwork.  So, we have created a fake customs office to utilize standard AES functions.

[mouaz_benredjeb]

Could you please give me the technical name of the carrier partner type you are using ?

(e.g. CUSANM for Declarant, etc...)

[dean_hinson2]

The technical type is CUSSTP Representative/Broker.