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: 

Enhancement

Former Member
0 Kudos

Hi frnds,

i need to add one filed in PO Header. actually that field is available in item level. can u pls tell me how to do this. i know the field at item level.

Regards

Balu

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

Goto Transaction SMOD.

Give the Enhancement Name : <b>MM06E005</b>

Select the <b>Components</b> Radio Button.

and <b>"Click"</b> Display.

<b>Use the following FMs</b>:

The Function module Exit "<b>EXIT_SAPMM06E_006</b>" is for Export Data to Customer Subscreen for Purchasing Document Header.

The Function module Exit "<b>EXIT_SAPMM06E_008</b>" is for

Import Data from Customer Subscreen for Purchasing Document

Subscreen Program "<b>SAPMM06E</b>" and the Screen Number "<b>0101</b>"

for Subscreen: PO header.

And in the bottom,

u can use

<b>CI_EKKODB</b> include two append 2 fileds.

these things for ur requirement.

Then goto Transaction CMOD create a project for this requirement.

Use the enhancement, subscreen and Includes.

Hope this will help you.

9 REPLIES 9

former_member181962
Active Contributor
0 Kudos

Add the field to the EKKO table using Append structure method.

Then you can use the enhancement MM06E005.

REad the documentation for the user exit.

If you do not have it, her it is from the sap documentation:

<b>With the enhancement, you can

o Maintain/supply your own customer fields in the headers and items of

all purchasing documents except purchase requisitions

o Update your own customer-specific tables

You cannot:

o Change standard fields

o Change data that depends on the document header in the items

o Change data that depends on an item in the document header

INCLUDES

You incorporate your customer fields for the document header in the

INCLUDE CI_EKKODB (in table EKKO).

You incorporate your customer fields for the document item in the

INCLUDE CI_EKPODB (in table EKPO).

Dynpro areas

If you use the enhancement, you must create and generate the following

dynpros (even if the dynpros are not going to be used):

o SAPLXM06 0101 Subscreen header purchase order

o SAPLXM06 0201 Subscreen header outline agreement

o SAPLXM06 0301 Subscreen header RFQ

o SAPLXM06 0111 Subscreen item purchase order

o SAPLXM06 0211 Subscreen item outline agreement

o SAPLXM06 0311 Subscreen item RFQ

You must identify all dynpros as subscreens. It is not necessary that

they contain fields, but it is essential that they exist in order that

no program abend occurs.

Function exits

The dynpros are linked to the standard program via function modules.

There are function modules that provide your subscreen with data

(export) and function modules that fetch data from your subscreens

(import).

o Header screens:

- EXIT_SAPMM06E_006 Export data to customer subscreen for header

(PBO)

- EXIT_SAPMM06E_007 Export data to customer subscreen for header

(PAI)

- EXIT_SAPMM06E_008 Import data from customer subscreen for

header

o Item screens:

- EXIT_SAPMM06E_016 Export data to customer subscreen for item

(PBO)

- EXIT_SAPMM06E_017 Export data to customer subscreen for item

(PAI)

- EXIT_SAPMM06E_018 Import data from customer subscreen for item

You can set or supply your own data fields in the PBO function modules.

You receive the current (possibly changed viz a viz the PBO call) data

of the standard program in the PAI function module.

You can return your fields to the standard program in the import

function modules.

There is also sufficient data available to supply the customer fields

from the material master record, info record, reference documents, RFQs,

contracts, or vendor master record. This is sufficient to fill customer

fields in normal dialog transactions.

The same function modules are also invoked when purchase orders are

created via function modules (function group EINC) (recognizable by the

import parameter I_NO_SCREEN, which is then set to 'X').

If you wish to update your own tables, you can invoke function module

EXIT_SAPMM06E_013. This is invoked directly prior to "commit work" with

all available data. You can carry out further checks prior to saving via

the function module EXIT_SAPMM06E_012. This is processed in the case of

the functions "Check document" and "Save".

If you wish to read your own tables as well, you should use function

module EXIT_SAPMM06E_014. This is invoked when the purchasing document

is read from the database.

To re-initialize your own data, it is essential that you also use

function module EXIT_SAPMM06E_009. This function module is always

invoked when the next purchasing document is processed (when POs are

created via function module).

In the header modules, you obtain the SAP transaction category via the

parameter I_TRTYP:

o A Display

o V Change

o H Create

You obtain the relevant transaction/event from the SAP transaction table

(e.g. quotation, scheduling agreement delivery schedule) via the

parameter I_VORGA. The possible values are not stored as fixed domain

values.

In the item modules, you obtain the activity category via the parameter

I_AKTYP:

o A Display

o V Change

o H Create </b>

Regards,

ravi

0 Kudos

hi Ravi,

i need to add that field in me21n screen. not in the table. is it possible to add in the screen with out adding that field in Header tabel EKKO.

0 Kudos

Hi KBS,

Assuming that you have it on the screen and not in the table.

Then what happens when the user saves the PO?

Where will you store that particular field?

Regards,

Ravi

Former Member
0 Kudos

Hi,

Goto Transaction SMOD.

Give the Enhancement Name : <b>MM06E005</b>

Select the <b>Components</b> Radio Button.

and <b>"Click"</b> Display.

<b>Use the following FMs</b>:

The Function module Exit "<b>EXIT_SAPMM06E_006</b>" is for Export Data to Customer Subscreen for Purchasing Document Header.

The Function module Exit "<b>EXIT_SAPMM06E_008</b>" is for

Import Data from Customer Subscreen for Purchasing Document

Subscreen Program "<b>SAPMM06E</b>" and the Screen Number "<b>0101</b>"

for Subscreen: PO header.

And in the bottom,

u can use

<b>CI_EKKODB</b> include two append 2 fileds.

these things for ur requirement.

Then goto Transaction CMOD create a project for this requirement.

Use the enhancement, subscreen and Includes.

Hope this will help you.

Former Member
0 Kudos

hi,

i added the field in append structure CI_EKKODB and i press syntax check. it was giving some worning errors. again i pressed activate button. it was showing like "PARTLY ACTIVE". is it give any problem in future?

now this field is appearing in EKKO table. is it right?

now if i want to add this field in ME21N header part. what to do?

give me your valuable suggestions.

regards

balu

0 Kudos

Hi,

To activate the table after introducing two fields as append structure fields, use SE14 OR goto Utilities> Database utility> and choose activate & adjust database,

To add the custom fields, go to the relevant screen, and edit the screen and add two fields, it is nothing but the screen painter and you can add fields in the screen, once the fields are added, activate the screen & flow logic,

Hope this helps,

Rgds,

0 Kudos

Look at the BADI ME_GUI_PO_CUST (Customer's Own Screens in Enjoy Purchase Order) to add custom elements to the PO screen.

The Business Add-In (BAdI) ME_GUI_PO_CUST enables you to integrate your own subscreens into the Enjoy purchase order at both eader and item levels.

-Kiran

*Please mark useful answers

Former Member
0 Kudos

Hi,

i have added the field in PO header for subscreen. here when i press F4, input possible values are coming, but when i select any one entry, it was saying that the value is not available in the check table. when i checked the check table it was there. pls any one give your solution or ideas for this.

regards

KBS Reddy

Former Member
0 Kudos

Hi,

Go the Include program. In that u declare the Tbale EKKO in the Global definition.

like TABLES: EKKO.