topic Re: Data not saving in Application Development and Automation Discussions

Data not saving

Former Member — Tue, 21 Jan 2014 08:16:20 GMT

Hi,

In transaction 'me21n' i created a screen exit with some fields after completion of screen exit. i run transaction i comes but when i enter data to those fields and click on 'save' the data of those fields are not saving the table 'ekko'.how can i avoid it.

please help me urgent.

Re: Data not saving

FredericGirod — Tue, 21 Jan 2014 08:18:15 GMT

Hi,

does it works if you modify any others data of EKKO or EKPO ?

(standard fields)

regards

Fred

Re: Data not saving

nabheetscn — Tue, 21 Jan 2014 08:19:20 GMT

Hi Krishna

In the PAI of your subscreen did you pass back the data to the standard. If not please pass it their is an exit to pass back the data from custom field to standard.

Nabheet

Re: Data not saving

Former Member — Tue, 21 Jan 2014 09:10:58 GMT

Hi,

Give me one example how to pass.

Re: Data not saving

nabheetscn — Tue, 21 Jan 2014 09:16:53 GMT

Are you using MM06E005 if yes then you have to do it in EXIT_SAPMM06E_008

Re: Data not saving

Former Member — Tue, 21 Jan 2014 09:23:32 GMT

Hi Krishna,

transfer the data in the FMs EXIT_SAPMM06E_007 and/or EXIT_SAPMM06E_008 it its header and if its item please refer below , read the SAP documentation

Functional 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).

Header Screen:

- EXIT_SAPMM06E_006 - Export Data to Customer Subscreen for Purchasing Document Header (PBO)

- EXIT_SAPMM06E_007 - Export Data to Customer Subscreen for Purchasing Document Header (PAI)

- EXIT_SAPMM06E_008 - Import Data from Customer Subscreen for Header

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

Please look at documentation for further usage.

Happy Coding,

Santhosh Yadav

Re: Data not saving

Former Member — Tue, 21 Jan 2014 09:26:13 GMT

This message was moderated.

Re: Data not saving

muneshpatwari — Tue, 21 Jan 2014 09:28:09 GMT

This message was moderated.

Re: Data not saving

Former Member — Tue, 21 Jan 2014 09:43:20 GMT

Hi Krishna,

If you are using MM06E005 exit for customer fields in purchasing document ,then you have to do it in EXIT_SAPMM06E_008. in this u need to enable the "update".

for ex:

e_ci_ekko-zzpcardid = ekko_ci-zzpcardid.

e_ci_update = 'X'.

Note: u need to give Screen field as EKKO_CI-ZZPCARDID(custom field name).

Regards,

Lakshmi.

Re: Data not saving

Former Member — Tue, 21 Jan 2014 10:22:03 GMT

Hi,

After doing this also not saving the data.

Re: Data not saving

narendar_naidu — Tue, 21 Jan 2014 10:55:37 GMT

hi Krishna,

First let us know r u trying to save Custom fields data or standard fields.

if ur designing custom fields (or standard fields)to save in your EKKO table, create a Zstructure and append in EKKO and try saving them.

regards,

Re: Data not saving

Former Member — Tue, 21 Jan 2014 11:14:43 GMT

Hi Krishna ,

First to create zstr and append with standard table EKKO_CI and then after simply

assign field value and use

move corresponding ekko_ci to e_ci_ekko .

Regards

Vivek

Re: Data not saving

narendar_naidu — Tue, 21 Jan 2014 11:26:32 GMT

krishna let me know if your issue resolved or not.

Re: Data not saving

Former Member — Tue, 21 Jan 2014 11:36:20 GMT

Hi,

If u r not including the custom fields in include tables, we need to include . please observe the following screen.

Re: Data not saving

RaymondGiuseppi — Tue, 21 Jan 2014 12:40:07 GMT

Did you

Read SMOD MM06E005 documentation
Read 407975 - MM06E005: Collective note: Examples for implementation
Define your fields in includes CI_EKPODB or CI_EKKODB
Insert a TABLES statement for one of those structure or main table/structure EKKO, EKPO in include ZXM06TOP
Use those structure/table names in dynpro field definitions
Activate every object

Regards,

Raymond