FM CONVERSION_EXIT_ZMAT1_INPUT

[Former Member]

Hello All,

Due to a dump occurred I have found the SAP Note 1790031. In this Note it is suggested to use the FM CONVERSION_EXIT_ZMAT1_INPUT.

I have tried to find this FM on BW and R/3 Systems but without success. I suppose that the "Z" character, included in the name of the FM, means that this FM must be created.

I have found the standard FM CONVERSION_EXIT_MATN1_INPUT that, in my opinion, has the same behavior.

Is it possible to know a possible reason about this?

Any suggestion will be greatly appreciated.

Thanks in advance for your kind support.

Regards,

    Giovanni

[Former Member]

Hello All,

Due to a dump occurred I have found the SAP Note 1790031. In this Note it is suggested to use the FM CONVERSION_EXIT_ZMAT1_INPUT.

I have tried to find this FM on BW and R/3 Systems but without success. I suppose that the "Z" character, included in the name of the FM, means that this FM must be created.

I have found the standard FM CONVERSION_EXIT_MATN1_INPUT that, in my opinion, has the same behavior.

Is it possible to know a possible reason about this?

Any suggestion will be greatly appreciated.

Thanks in advance for your kind support.

Regards,

    Giovanni

[roberto_vacca2]

Hi.

Dump is caused by the Internal->External->Internal conversion from DataSource.

You have the option to receive data in internal format or to implement this enhancement in sap.

To create a custom code inside MAT1 routine conversion you have 2 options:

1 - enhance  MGA00003 from SMOD (function EXIT_SAPLOMCV_001)

2 - implement BADI_MATN1.

These 2 exits are visible from CONVERSION_EXIT_MATN1_INPUT code when you see:

CALL CUSTOMER-FUNCTION '001' ;

CALL METHOD G_BADI_MATN1->MATN1_INPUT_001

The MATN1 conversion exit raises every time you check MATNR field in SAP transactions and MATNR domain.

So pay attention to all the side-effects of a custom modification.

Hope to help

Bye

[Former Member]

Just a thought...

Before you look into BADIs, enhancements or custom functions, I'd investigate the reason for the dump. Was it one messed up material record? Then fix the data. Or do you have a real requirement to do something non-standard? MATNR has been around so long that I would bet on a data issue. Fix the source, not the symptom - or you'll have to add patch after patch later.

Also, exits are assigned at the domain. Be aware that materials have more than one domain (across several tables) and they may not all use the same conversion exit.

Not saying that you shouldn't do it, but think twice (or ten times) before you go down that route.

Wolfgang

[RaymondGiuseppi]

Don't use the conversion exits mentionned in the document, those are only illustrative (from PROJ to ZMAT1)

What the document suggests, is that if data is exported in external format in Datasource, you have to either

• Use a transformation routine that call the INPUT conversion exit of the domain
• Adjust datasource (*)

Regards,

Raymond

(*) e.g. Enhancement (SMOD) RSAP0001 or Business Transaction Event (BTE) BW204010-40