‎2019 Oct 31 3:00 PM
I am trying to update table T024D MRP controllers.
Please let me know how you have done it.
‎2019 Oct 31 3:09 PM
Transaction SM30 enter T024d press button Find dialog ... it will find the corresponding view (V_T024D) and you could press Customizing to find where this view is manage in the customizing
And after you could play with SM30, LSMW, ecatt, Gui Scripting whatever you want
‎2019 Oct 31 6:09 PM
‎2019 Oct 31 8:18 PM
As said Frederic: "ecatt, Gui Scripting". And I add "batch input".
There's also the function module VIEW_MAINTENANCE_NO_DIALOG, but it's not intended to be used by customers, and I don't even know if it's really for the goal that its name let suppose.
‎2019 Nov 01 9:05 AM
VIEW_MAINTENANCE_SINGLE_ENTRY does not require but I have to submit save and return to the previous screen :(
‎2019 Nov 01 10:04 AM
if it is too complex do a simple batch input or a program that call the transaciton
you could record your bdc using SHDB transaction
‎2019 Nov 01 10:21 AM
the problem is not complexity ,the problem is 1.I have to remain in the same program 2.I have to catch the error also..if there is any
‎2019 Nov 01 10:30 AM
so use CALL TRANSACTION ... USING bdcdata ..
https://wiki.scn.sap.com/wiki/display/ABAP/Batch+Input+-+BDC
you could catch error, and you stay in your program
‎2019 Nov 01 10:35 AM
do you even read my comments?how do you catch the error if the records does not get updated?
‎2019 Nov 01 12:29 PM
‎2019 Nov 01 12:43 PM
‎2019 Nov 01 1:12 PM
Jonathan Blavatsky Okay, it was just a misunderstanding, Frederic probably supposed that you would read the whole wiki and documentation of CALL TRANSACTION. It's a little bit offensive to say that your comments are not read, though. It happens to anybody to not read enough, it's human, just repeat, possibly in a different way because maybe your first comment was read but not understood.
‎2019 Nov 01 12:47 PM
I assume you read the help
CALL TRANSACTION ta WITH|WITHOUT AUTHORITY-CHECK
USING bdc_tab { {[MODE mode] [UPDATE upd]}
| [OPTIONS FROM opt] }
[MESSAGES INTO itab]
Addition 4
... MESSAGES INTO itab
Effect
Using this addition, all the messages sent during batch input processing are saved to an internal table itab of the type BDCMSGCOLL from ABAP Dictionary.
‎2019 Nov 01 1:48 PM
‎2019 Nov 01 1:53 PM
Run your CALL TRANSACTION in mode 'E' means Error. When you will save the data, SAP will open a windows requesting the transport request. You will just have to specify it manually at this moment.
I think your initial question is now fully answered, and I think you should start to work in your side
Good luck
‎2019 Nov 01 2:02 PM
the transport request is a problem...I will wait for an alernative solution hopefully ,if not then this is not an option from my side.I have awarded your effort with an upvote.
‎2019 Nov 01 2:43 PM
Jonathan Blavatsky Why is it a problem? If the users want to maintain the table in the DEV system, they will have to assign the changes to a transport request and transport it to the production system. If the users want to maintain the table in production only, then you have the possibility to deactivate the transport in the production system by using the "current setting" flag (cf notes 523213 - Set maintenance view in production system to changeable, Note 135028 - Transfer IMG activity to current setting, 356483 - Customizing: Current settings in the test system, and eventually 351041 - Recording routine for table content to deactive the transport request also in DEV system...)