Customs procedure code 29 is not defined in any customs code list

[Isabelle]

Hi GTS specialists!

I'm creating export transit declarations by sending the invoice from ECC to GTS.

Normally this works fine, and in this case the export declaration is created but the transit declaration is not....

The document is stuck in the transfer log for billing document - Export/transit in GTS, with the following log:

Customs procedure code 29 is not defined in any customs code list

Message no. /SAPSLL/API_INBOUND030

I have tried to check in customizing, for custom code lists, but didn't find the key solution yet..

Any suggestions how to fix this?

I suppose some mapping between export procedure 29 (= export in Foreign Trade Data - item) and GTS customs code list is missing..?

thanks!!!

Isabelle

[Former Member · Accepted solution]

Hello Isabelle,

In Feeder system the customs procedure codes are stored in table T616.

You can access this in ERP SPRO -> Sales & Distribution -> Foreign trade/ Customs -> Basic data for Foreign trade -> Define procedures and Default value.

For export in all EU the standard code is "1000" ( Final export without previous custom approved procedure )

This error does not prevent us in our environment from creating declaration however, it only makes the user enter the value manually on the declaration.

If you have problems with creation of Transit declaration try checking also "Determination Procedure for Activity Sequence" - in GTS SPRO.

Best Regards,

Brano Petricek

[former_member381293]

Hello Isabelle!

We use only one invoice to create one GTS document at one time. I'm not sure if GTS doesn't get problems to determine the legal regulation, if you try to create two GTS documents out of one invoice?

Anyway can you check please, if you have customized correctly the assignment of the documenttyp? (IMG --> GTS --> Customs Management --> General Settings --> Document Structure --> Assignment of Document Types from Feeder Systems --> Assign Document Type at Feeder System (Group??) Level )

If that does not work, it could be necessary to create a second (pro forma?) invoice dokument from that the transit document is build.

We use the BADI for translating some company specific textual packing informations into offical custom-valid codes.

kind regards

Sabine

[Isabelle]

Dear all,

for information purposes, this issue has been solved, some default data was missing for field: confirmation of presentation (eg D re export after CWH).

Thanks for your input,

Isabelle

[former_member381293]

Hello Isabelle!

Yes we assign the export procedure from ECC to a customs code list, but we are using a BADI between.

May I ask you some more questions?

Is the whole transit document not created, or is "only" the export procedure number missing?

And are you using one invoice for creating the export and the transit process, or are you using a seperate invoice for each?

kind regards

Sabine

[Isabelle]

Hi! Thanks for the help...

Indeed, my transit document is not created at all.

1 billing document should trigger 1 export + 1 transit declaration. The export declaration is created...

But my transit declaration is not...

Only error log that is linked with this says that there is a problem with the customs procedure 29 which is not defined in any customs code list...

why are you using a BADI in between? and to which customs code list field is it exactly linked?

can I do this without the BADI?

Thanks!

[former_member381293]

Hello Isabelle!

Therefor I am from Austria I don't know specific requirements for the Belgium export procedure numbers. In Austria we don't use any export procedure numbers at the transit process.

Sorry for my foolish question, but are you sure, that you need procedure numbers for transit? The transit process NCTS should be standardized throughout the EU. Or is BE not using the NCTS system?

Sabine

[Isabelle]

Hi Sabine, no foolish questions here

Yes Belgium is using the NCTS and indeed I would expect it to be standardized...

But in ECC for intrastat we are using export procedure 29 (which is shown in the invoice < item < foreign trade < origin...

As this is automatically filled in for any export invoice, the invoice is then transferred to GTS, the export customs document is created correctly, but not the transit document....

In the transfer log of export/transit billing documents in GTS it is indicating that there is a problem with procedure 29 which is not mentioned in any customs code list..

Do you assign the export procedures from ECC to any customs code list?

thanks,

have a lovely weekend,

[former_member381293]

Hi!

You said that the Transfer from ECC to GTS did not work for Transit, but it did work for Export.

The Customs Code List for Export uses the Legal Regulation CUSBE, but the Transit Process uses the Customs Code List for the Legal Regulation TRSBE.

Have you maintained the Customs Code List for the Legall Regulation TRSBE too?

kind regards

Sabine

[Isabelle]

Hi Sabine,

Thanks for your answer, but indeed yes I have maintained the custom code lists from CUSBE and TRSBE,

but possibly something is missing in this TRSBE, do you know of any specific requirement for the export procedure number (29 in my case)?

thanks,

[former_member215181]

Hi Isabelle,

There is no mapping between the Customs Procedure codes in ERP and those in GTS. Instead, the code must exist in GTS in order to be transferred. That's to say; you must configure the same code list in ERP and GTS.

Usually it's better not to propose ANY Customs Procedure Codes in ERP, and instead use the Data Proposal in GTS. But if you have particular dependencies already set up in ERP, then you just need to make sure that the codes are valid for your Legal Regulation. Code '29' seems an unlikely one for Belgium. Right across the EU, the CPCs are structured in the same way - 4 digits for the main code, and 3 further characters for the additional code, if applicable. For Export, you should expect to be using (mostly) code 1000.

But in any case, the code discrepancy is not the reason that your transaction is stuck. The message is only information for the transfer log, and there must be some other reason why your billing document is not transferred to GTS.

I hope that helps.

Kind regards,

Dave

[Isabelle]

Hi, Thanks for the responses...

But I'm not getting to the solution just yet..

Indeed 29 is my export code in ECC for Belgium, and this is not linked in ECC..

My billing document is transferred from ECC to GTS but only for export, not for transit, because in the transfer log it says : customs procedure code 29 is not defined in any customs code list...

I have already tried all kinds of types in the customs code lists but still it does not work....

Any other suggestions, please?

Thanks!