Let’s get on SAP TMG – No Need to Delete & Regenrate After Change of Table Structure. At the point when we want to add another vital field or non-key field to a current table which as of now has a TMG (Table Support Generator), the majority of the engineers keep a duplicate of the multitude of codes written in the Tables Occasions and related region like PBO/PAI. So after the new fields are added, they can erase the TMG and recover. When the TMG is recovered, every one of the past codes are lost and the ABAPer needs to retrofit the code back to the occasions from his back up. SAP TMG – No Need to Delete & Regenrate After Change of Table Structure.
FYI – We erase and regenarate the TMG since, in such a case that we don’t make it happen, the new fields doesn’t get reflected in SM30 T-Code.
However, consider the possibility that, another designer is in the venture. He doesn’t realize that there is some custom rationale written in the occasions. Furthermore, he adds new fields and erases existing TMG and recovers the TMG without taking the reinforcement?
This has been an undeniable irritation in any event, for prepared ABAPers with over many years of involved insight. Today, we would demonstrate the way that you can add new fields and furthermore make the current TMG work for certain straightforward strides without erasing the current TMG. SAP TMG – No Need to Delete & Regenrate After Change of Table Structure.
How about we start.
This is the manner by which the table looks before we add new fields:
(Accept we have a few Occasions made for this table, ex: occasion 05, occasion 06 and so on… )
Step 1: I have created a custom table with maintenance with some fields.
(Maintenance screen before adding the additional fields)
(Maintenance table)
Subsequent to adding the new fields to the current table, as a rule, most specialists (read ABAPers) follow one troublesome way of reviving the table upkeep generator to make the new fields noticeable.
Erase the current TMG and making another one with recently added fields to the table. Assuming that we have no occasions, we are fortunate, we have no issue. Yet, on the off chance that there were occasions, erasing the TMG would blur off all the rationale in short order. When you erased you can’t get the code back (however, there are ways of getting it back)
Step 1: Added new fields to that table
Step 2: Change the table after expansion of new fields in T-Code SE14.
Picked Actuate and change data set button and Save information.
Step 3: Return to the table (in change mode) and snap on table upkeep generator from Utilities menu thing.
Step 4: You would have the option to see the change symbol on the upkeep screen.
Click it.
Step 5: Popup will show up on tapping the change symbol.
Step 6: Here comes the main segment, whether you need to change or erase the fields.
If you have any desire to add extra fields to the TMG, then, at that point, select New field/sec. table in structure.
Click proceed.
You probably understood, if you need to erase the fields from a table, then you want to choose Field/sec. table eliminated from the design.
Click continue.
Step 7: For our activity, going on as adding new fields
So next screen would be:
Step 8: Here as well, you have a vital choice to make. You need to add a vital field or typical field?
Whether it is single screen or outline screen?
Here our circumstance is ordinary documented, with outline screen.
Click continue.
Step 9: One more popup will show up after you press the proceed with button.
Just snap on Proceed.
Note: Some handling time will take to actuate
Then, at that point, click on SAVE.
Congrats you recovered the TMG effectively with practically no problem of erasing the TMG.
What are you sitting tight for? Proceed to actually look at your upkeep (SM30).
Here you can see the outcome. Recently added fields are grinning and sitting tight for you to populate them.
Follow a similar method when you need to:
- Add new Key fields to the table
- Delete the fields (key/non-key) from the table
Trust you loved this stunt. It could look straightforward however trust us, numerous ABAPers don’t have the foggiest idea about this. Next time you change the construction of a Table, you know how to recover TMG with no cerebral pain.
YOU MAY BE INTERESTED IN
A Comprehensive Guide to SAP ABAP Training Online
Best Practices for SAP ABAP Development: A Comprehensive Guide
WhatsApp us