topic Re: Material No format Validation in Application Development and Automation Discussions

Material No format Validation

Former Member — Fri, 02 Dec 2011 16:08:43 GMT

Hello,

We have external material number format, example : X-XXX-XXX-XXX, so any material created should have the said format.

So we used user exit in "conversion exits of matnr: CONVERSION_EXIT_MATN1_INPUT ' to validate material no & throw error message .

These conversion exits are called whenever material is created thru tcode: MM01, changed in MM02.

But when any material created using BAPI / Idoc, these conversion exits are not called.

Please let me know the solution such that material number format is validated when created thru all means.

Thanks,

Sridhar

Re: Material No format Validation

Former Member — Fri, 02 Dec 2011 16:14:44 GMT

CONVERSION_EXIT_MATN1_INPUT (and CONVERSION_EXIT_MATN1_OUTPUT) are called only for input/output convertion, so it means only when a material is displayed in a abap list or in a screen.

This exit is not triggered internally a program, that mean you need to call it by yourself, so you should call it to convert material numbaer before calling the BAPI or IDOC

Max

Re: Material No format Validation

Former Member — Sat, 03 Dec 2011 13:08:20 GMT

Hello Max,

Thanks for your reply.

I do agree, but some external systems are using BAPI_MATERIAL_SAVEDATA to create material.

They create material with wrong format...

Some how need to restrict / validate material no format before created thru any method(MM01/Idoc/BAPI etc)...

Plz share your knowledge.

Thanks,

Sridhar

Re: Material No format Validation

Former Member — Sat, 03 Dec 2011 13:21:46 GMT

The material code should be transfered as Material External Code in oreder to convert it as internal one

Max

Re: Material No format Validation

Former Member — Sun, 04 Dec 2011 17:09:13 GMT

Plz explain in detail ...

Re: Material No format Validation

Former Member — Mon, 05 Dec 2011 11:58:49 GMT

Plz explain in detail ...