Application Development 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: 

Mapp custom field in MM06E005: ME21N, ME22N and ME23N.

Fabio777-hub
Explorer
0 Kudos

Good morning,

via enhancement MM06E005 I have implemented my custom tab. CUSTSCR1 SAPLXM06-0111.

Everithings works ok: I am able to see my tab end custom fields (added in CI_EKPODB), and also I manage fine values and save data.

Now via EXIT_SAPMM06E_012 I'm able to check custom fields (added in CI_EKPODB) showed in tab. CUSTSCR1 SAPLXM06-0111 but I would like to link my error message to my cutom field. Can I mapp mmmfd_cust_01 with my custom field or I can only do it if I have created tab SAPLXM06-0111 with BADI and not with user-exit?

many thanks

Fabio.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi Fabio,

Good day,

Type group for ME21n,ME22n,ME23n is MMMFD.

In this we have the following custom fields.

mmmfd_cust_01          TYPE mmpur_metafield VALUE 90000000,

mmmfd_cust_02          TYPE mmpur_metafield VALUE 90000001,

mmmfd_cust_03          TYPE mmpur_metafield VALUE 90000002,

mmmfd_cust_04          TYPE mmpur_metafield VALUE 90000003,

mmmfd_cust_05          TYPE mmpur_metafield VALUE 90000004,

mmmfd_cust_06          TYPE mmpur_metafield VALUE 90000005,

mmmfd_cust_07          TYPE mmpur_metafield VALUE 90000006,

mmmfd_cust_08          TYPE mmpur_metafield VALUE 90000007,

mmmfd_cust_09          TYPE mmpur_metafield VALUE 90000008,

mmmfd_cust_10          TYPE mmpur_metafield VALUE 90000009.

So you can use these fields in your custom screen and validation can be done.

Please revert if any queries.

Thanks,

Seshadri.

3 REPLIES 3

Former Member
0 Kudos

Hi Fabio,

Good day,

Type group for ME21n,ME22n,ME23n is MMMFD.

In this we have the following custom fields.

mmmfd_cust_01          TYPE mmpur_metafield VALUE 90000000,

mmmfd_cust_02          TYPE mmpur_metafield VALUE 90000001,

mmmfd_cust_03          TYPE mmpur_metafield VALUE 90000002,

mmmfd_cust_04          TYPE mmpur_metafield VALUE 90000003,

mmmfd_cust_05          TYPE mmpur_metafield VALUE 90000004,

mmmfd_cust_06          TYPE mmpur_metafield VALUE 90000005,

mmmfd_cust_07          TYPE mmpur_metafield VALUE 90000006,

mmmfd_cust_08          TYPE mmpur_metafield VALUE 90000007,

mmmfd_cust_09          TYPE mmpur_metafield VALUE 90000008,

mmmfd_cust_10          TYPE mmpur_metafield VALUE 90000009.

So you can use these fields in your custom screen and validation can be done.

Please revert if any queries.

Thanks,

Seshadri.

0 Kudos

Ciao Seshadri,

I changed my name custom fields into mmmfd_cust_0-10 in dynpro 0111 and in EXIT_SAPMM06E_012

and also I have tryed via BADI ME_PROCESS_PO_CUST method CHECK wit macro

mmpur_business_obj_id w_item-id.

mmpur_metafield mmmfd mmmfd_cust_0              and so on...

but this is not sufficient to link my error message.

any way many thanks for your reply.

Fabio

0 Kudos

Hi Luca,

Few points in the documentation provided in example class CL_EXM_IM_ME_GUI_PO_CUST for ME_GUI_PO_CUST.

1.Mapping to metafields which are used for field selection purposes and error handling can be attained by standard definitions in type pool MMMFD.


So by these point my assumption is the Error handling can be done by through BADI only and not by user exit.


Please read the whole documentation of the example class and if u have any issues plz revert me.


Thanks,

Seshadri.