Implementing ME21N / ME22N screen exit (Enhancement MM06E005)

[Former Member]

I've just implemented enhancement MM06E005 and have extended a new field to CI_EKKODB. The subscreen is in place and the project has been activated without issues. I can populate the DB via the new field in 'customer data' tab. The only problem I have is I don't see my new value after saving the PO and re-accessing it in change mode ME22N. The new field is blank. I can see the record's new field has the value in SE16N and I see the value when debugging EXIT_SAPMM06E_006. My assignment statement in EXIT_SAPMM06E_006 for the new field is similar to: i_ci_ekko-zzvbeln = i_ekko-zzvbeln. What have I missed?

Edited by: Steve Fenske on Oct 13, 2009 11:45 PM

[Former Member]

Please check out the link

[Former Member]

Hi Steve.

If you observe the enhancement "MM06E005", in addition to the first exit - "EXIT_SAPMM06E_006".

You need to write the same back to the "EXIT_SAPMM06E_008" as this will pass the data back from the sub-screen to the customer screen. Hence, it will update.

Code in this exit and activate.

EXIT_SAPMM06E_008

  if sy-tcode = 'ME21' or
    sy-tcode = 'ME22'.
    e_ci_ekko-zzvbeln = ekko_ci-zzvbeln.
 endif. 

In addition to your earlier code in EXIT_SAPMM06E_006,

 if sy-tcode = 'ME22'
or sy-tcode = 'ME23'.
  i_ekko-zzvbeln = ekko_ci-zzvbeln.
endif. 

I am sure it will work.

Best regards,

Harsh Dave

[sujeet2918]

Hello Steve,

One good site for you where you will find already developed screen exit for ME22N.

website saptechnical

Have a Nice Day

regards,

Sujeet

Edited by: Sujeet Mishra on Oct 14, 2009 11:01 AM

Edited by: Sujeet Mishra on Oct 14, 2009 11:02 AM

[Former Member]

Hi steve ,

In addition to the function exit u r doing , u have to code the bellow exit also .

See the documentation of this exit , it explains u clearly in the document.

EXIT_SAPMM06E_006 Export Data to Customer Subscreen for Purchasing Document Head

EXIT_SAPMM06E_008 Import Data from Customer Subscreen for Purchasing Document

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

Rajendra

[Former Member]

Thank-you for your quick response(s). To be clear, the updating functionality in EXIT_SAPMM06E_008 always worked. To anyone reading this link, donu2019t forget to assign an u2018Xu2019 to the e_ci_update indicator. I just couldn't figure out how to refresh the screen with my updated values after returning to the PO in ME22N. Turns out I hadn't coded the appropriate PBO logic in module STATUS_0101 to assign the ekko_ci value to ekko between iterations.