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

Custom Fields in ME51

Former Member
0 Likes
1,146

Hi all,

There is a requirement to include additional fields/columns in PR service specification level for additional data input.

<b>For example:</b>

Users want to enter separate descriptive text besides the service short text in the same line item (they do not want to use the long text feature).

Can anyone enlightened me on:

1. How do I add additional fields? Do I append to the current table?

2. How can I modify the line item view in all ME51,52 and 53 to rearrange and display input for the new fields?

3. Can this be achieved by enhancing the standard program or a new screen is needed?

Please advice.

Hi all,

There is a requirement to include additional fields/columns in PR service specification level for additional data input.

<b>For example:</b>

Users want to enter separate descriptive text besides the service short text in the same line item (they do not want to use the long text feature).

Can anyone enlightened me on:

1. How do I add additional fields? Do I append to the current table?

2. How can I modify the line item view in all ME51,52 and 53 to rearrange and display input for the new fields?

3. Can this be achieved by enhancing the standard program or a new screen is needed?

Please advice.

3 REPLIES 3
Read only

Former Member
0 Likes
700

Hi

You would have to add additiional sub screen to your transaction via a screen exit.

First you would create a sub screen with all fields you want to put including a PAI and PBO.

Then you find the appropriate screen exit for it. For ME51/52/53 the following exits apply...

AMPL0001 User subscreen for additional data on AMPL

LMEDR001 Enhancements to print program

LMELA002 Adopt batch no. from shipping notification when posting a GR

LMELA010 Inbound shipping notification: Transfer item data from IDOC

LMEQR001 User exit for source determination

LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt

LWSUS001 Customer-Specific Source Determination in Retail

M06B0001 Role determination for purchase requisition release

M06B0002 Changes to comm. structure for purchase requisition release

M06B0003 Number range and document number

M06B0004 Number range and document number

M06B0005 Changes to comm. structure for overall release of requisn.

M06E0004 Changes to communication structure for release purch. doc.

M06E0005 Role determination for release of purchasing documents

ME590001 Grouping of requsitions for PO split in ME59

MEETA001 Define schedule line type (backlog, immed. req., preview)

MEFLD004 Determine earliest delivery date f. check w. GR (only PO)

MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.

MEQUERY1 Enhancement to Document Overview ME21N/ME51N

MEVME001 WE default quantity calc. and over/ underdelivery tolerance

MM06E001 User exits for EDI inbound and outbound purchasing documents

MM06E003 Number range and document number

MM06E004 Control import data screens in purchase order

MM06E005 Customer fields in purchasing document

MM06E007 Change document for requisitions upon conversion into PO

MM06E008 Monitoring of contr. target value in case of release orders

MM06E009 Relevant texts for "Texts exist" indicator

MM06E010 Field selection for vendor address

MM06E011 Activate PReq Block

MMAL0001 ALE source list distribution: Outbound processing

MMAL0002 ALE source list distribution: Inbound processing

MMAL0003 ALE purcasing info record distribution: Outbound processing

MMAL0004 ALE purchasing info record distribution: Inbound processing

MMDA0001 Default delivery addresses

MMFAB001 User exit for generation of release order

MRFLB001 Control Items for Contract Release Order

You would have to check which applies to ur requirement and then code accordingly.

Hope this helps to solve ur problem....

<b>do reward if useful....</b>

regards

dinesh

Read only

Former Member
0 Likes
700

Hi,

You'll have to use MM06E005 Customer fields in purchasing document for ME51 transaction.

aprt from this below are some useful userexits for me51.

AMPL0001 User subscreen for additional data on AMPL

LMEDR001 Enhancements to print program

LMELA002 Adopt batch no. from shipping notification when posting

LMELA010 Inbound shipping notification: Transfer item data from

LMEQR001 User exit for source determination

LMEXF001 Conditions in Purchasing Documents Without Invoice Rece

LWSUS001 Customer-Specific Source Determination in Retail

M06B0001 Role determination for purchase requisition release

M06B0002 Changes to comm. structure for purchase requisition rel

M06B0003 Number range and document number

M06B0004 Number range and document number

M06B0005 Changes to comm. structure for overall release of requi

M06E0004 Changes to communication structure for release purch. d

M06E0005 Role determination for release of purchasing documents

ME590001 Grouping of requsitions for PO split in ME59

MEETA001 Define schedule line type (backlog, immed. req., previe

MEFLD004 Determine earliest delivery date f. check w. GR (only P

MELAB001 Gen. forecast delivery schedules: Transfer schedule imp

MEQUERY1 Enhancement to Document Overview ME21N/ME51N

MEVME001 WE default quantity calc. and over/ underdelivery toler

MM06E001 User exits for EDI inbound and outbound purchasing docu

MM06E003 Number range and document number

MM06E004 Control import data screens in purchase order

MM06E005 Customer fields in purchasing document

MM06E007 Change document for requisitions upon conversion into P

MM06E008 Monitoring of contr. target value in case of release or

MM06E009 Relevant texts for "Texts exist" indicator

MM06E010 Field selection for vendor address.

<b>Reward points</b>

Regards

Read only

Former Member
0 Likes
700

You can use MEREQ001 User exit to achive this

Thanks

Seshu