SAP TMG: Don’t bother Erasing and Recovering the Table Upkeep Generator after Expansion or Cancellation of New Key or Non-Key Fields in Tables.
Do you have any idea about how? SAP TMG?
Whenever we really 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 vast majority of the engineers keep a duplicate of the multitude of codes written in the Tables Occasions and related region like PBO/PAI. With the goal that after the new fields are added, they can erase the SAP 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.
FYI – We erase and regenarate the SAP TMG since, supposing that we don’t make it happen, the new fields doesn’t get reflected in SM30 T-Code.
Yet, consider the possibility that, another designer is in the task. He doesn’t realize that there is some custom rationale written in the occasions. Also, he adds new fields and erases existing SAP TMG and recovers the TMG without taking the reinforcement?
This has been a major 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 SAP TMG work for certain basic strides without erasing the current TMG.
How about we start.
This is the way 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, by and large, most experts (read ABAPers) follow one troublesome way of reviving the table support generator to make the new fields noticeable.
Erase the current TMG and making another one with recently added fields to the table. On the off chance that we have no occasions, we are fortunate, we have no issue. However, 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).
Have you been a survivor of TMG erasure? Have you at any point lost any code in view of TMG recovery?
Step 1: Added new fields to that table
Step 2: Adjust the table after addition of new fields in T-Code SE14.
Picked Enact and change information base button and Save information.
Step 3: Go back to the table (in change mode) and click on table maintenance generator from Utilities menu item.
Step 4: You would be able to see the change icon on the maintenance screen.
Click it.
Step 5: Popup will appear on clicking the change icon.
Step 6: Here comes the most important section, whether you want to change or delete the fields.
If you have any desire to add extra fields to the TMG, then select New field/sec. table in structure.
Click proceed.
You probably understood, if you need to erase the fields from a table, then you really want to choose Field/sec. table eliminated from the construction.
Click continue.
Step 7: For our exercise, continuing as adding new fields
So next screen would be:
Step 8: Here too, you have a very important decision to make. You want to add a key field or normal field?
Whether it is single screen or outline screen?
Here our situation is normal filed, with overview screen.
Click proceed.
Step 9: One more popup will appear after you press the continue button.
Basically click on Proceed.
Note: Some handling time will take to enact
Then click on SAVE.
Congrats you recovered the TMG effectively with no issue of erasing the TMG.
What are you sitting tight for? Proceed to actually take a look at your support (SM30).
Here you can see the outcome. Recently added fields are grinning and hanging tight for you to populate them.J
Follow the same procedure when you want 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 basic however trust us, numerous ABAPers don’t have a clue about this. Next time you change the construction of a Table, you know how to recover TMG with next to no cerebral pain.
YOU MAY BE INTERESTED IN
How to Convert JSON Data Structure to ABAP Structure without ABAP Code or SE11?
ABAP Evolution: From Monolithic Masterpieces to Agile Architects
A to Z of OLE Excel in ABAP 7.4
WhatsApp us