USE MODIFY STATEMENT FOR A MAINTENANCE TABLE

[Former Member]

Hello ,

I created a ABAP program. In this ABAP program, I use the statement MODIFY in this way :

MODIFY ZPMCAP_PERS FROM TABLE s_pern1

ZPMCAP_PERS is a maintenance table. In this table. I have 5 fields, 3 (pernr, namelas and namefir) are updated by the program (via the statement modify) and 2 fields (arbpl and arbpl_2) must be modify manually by the users.

The problem is once I execute my ABAP program, the 3 fields (pernr, namelas and namefir) are updated automatically as expected, but when the users cannot update manually the 2 others fields (arbpl and arbpl_2). The 2 others fields seems lock.

How can I do to solve this issue ??

Thanks for your help.

Cedric

[matt]

Please don't have your subject in all CAPITALS - it looks like shouting.

What is preventing the users from manually updating the other 2 fields? Are they blanked out, is there an error message when you try to save? "Seems" is not very explicit. Perhaps post a screen shot?

[Former Member]

Hello Mathew,

The 2 others fields are blanked out, as you can see in the picture below (The 4 others fields are populated automatically).

2018-07-02-12-45-23-modifier-vue-liste-des-effecti.png

When the users update values in the 2 fields, save the data and come back the table. The values added by the users are not saved (as you can see in the picture below

2018-07-02-12-49-09-modifier-vue-liste-des-effecti.png

2018-07-02-12-50-10-modifier-vue-liste-des-effecti.png

[matt]

Are the users able to create their own entries (as opposed to modifying entries created by your program)?

Have you tried debugging what happens when you save? Are there any events on the table maintenance definition?

[RaymondGiuseppi]

• What do you call a 'maintenance table'? (Is it actually a 'maintenance view')
• Is this a written program or a generated maintenance dialog, in second case did you change generated code or use some event(s)?
• Did you define any foreign key relation for arbpl? (without werks field, you should check transaction CR03, look also at Infotype 315)
• Did you handle sy-subrc after the MODIFY statement?
• Did you use a TABLES statement or explicit FIELDS statement to insure data communication between program and dynpro? (Debug is the key)
• Why didn't you define a custom Infotype for this kind of data?
• Did you copy some data from Infotype 0002 (names) into your table?
• Could you describe still more clearly your problem/requirement?