"Postal code does not exist" - bypass error message in CREMAS

[Former Member]

Hi.

I am on a client implementing ALE between HR+Travel and FI/CO.

Vendors are created in HR and send to FI/CO with the IDoc CREMAS.

They don't want to validate the Postal Codes and Cities in the Vendors' Master Data.

But the IDoc ends with the status 51 and the message:

R5(510): "Postal code &1 in country &2 does not exist".

Do you know a way to bypass the validation in this Inbound Idoc in FI/CO?

Is it possible to customize this message to be a warning instead of an error in the IDoc, like it is on the manual entry screen?

Thank you for your help.

Edited by: MDuarte on Jan 9, 2012 11:32 AM

[former_member131723 · Accepted solution]

Hi there

I did some checks on this error and in fact found some support issues fixed in BC-SRV-ADR component (but for transaction XK01 directly) however for tcode PRAA there are some additional BADi's and user exits you can check in note 570023 - User exits for the generation of vendors with RPRAPA00, If the address editing in the vendor master record does not suit

your requirements, it can also be changed. For this purpose you have the user exit routine 'set_address_by_user'.

However specifically in XK01, this was alleviated by removing the flag CITY FILE ACTIVE for the relevant country.

If CITY FILE ACTIVE is disabled, it will disable regional structure checks, similarly POSTAL CODE CHECK will disable postal code checks. (See the F1 help)

[Former Member]

Hi,

Just to add : This can be done in tcode OY17.

[Former Member]

Hi Sally.

Deactivating "City file active" solved the problem.

Thank you so much.

Edited by: MDuarte on Jan 11, 2012 3:26 PM