Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Material No format Validation

Former Member
0 Likes
760

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

5 REPLIES 5
Read only

Former Member
0 Likes
712

Hi

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

Read only

0 Likes
712

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

Read only

0 Likes
712

Hi

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

Max

Read only

0 Likes
712

Plz explain in detail ...

Read only

0 Likes
712

Plz explain in detail ...