Skip to Content
0

How to change Field length once field is generated through AET?

Oct 13, 2017 at 01:11 PM

83

avatar image
Former Member

Hi,

I have a requirement where I need to change field length for an AET generated ZZ field.

I came across thread AET: How to change Field length once field is generated? and blog Steps to follow when changing data length for a generated AET Field.

But this thread did not clear my understandings.

Both of them mentioned we can acheive this by following below steps:

  1. Identify the Enhancement ID for the AET field through WebUI Configuration.
  2. Go to Table AXT_EXT_PART_DTL, Set the OBJ_PARAMVALUE parameter value to desired length by passing Enhancement ID and considering Parameter OBJ_PARAMETER as LENGTH. It will not ask for any Transport Entry but include the change in a Transport Request.
  3. Go to Table AXT_CAT_OBJ_DTL, set the OBJ_PARAMVALUE parameter value to desired length by passing Enhancement ID and considering Parameter OBJ_PARAMETER as LENGTH. It will not ask for any Transport Entry but include the change in a Transport Request.
  4. Regenerate the Enhancement ID (Tcode: AXTSHOW).
  5. If after regeneration, domain length did not change in corresponding table/tables, then follow step 8.
  6. Set the desired length in the Table->Data Element->Domain (SE11).
  7. Activate the table. Activation gives an error in table (Expected).
  8. Do a database adjustment for the required Table (SE14), in background, keeping data. It should activate the Table.
  9. Again Regenerate the Enhancement ID (Tcode: AXTSHOW).
  10. Once above steps are done, and then follow below 2 steps.
  11. Go to AET Object in WebUI ->Display Enhancements->Enhanced Objects->Enhancement ID and check the data length is matching with the database field length.
  12. Tcode: BSP_WD_CMPWB->Pass Required Component ->Corresponding View->Configuration TAB->Choose the correct configuration->select the required field -> check the data length if it is matching with Database field and AET object.

Can anyone please highlight and specify why we are performing Step 1 to step 5.

Actually i was just checking step 2 with OBJ_PARAMVALUE as old length value and for Step 3 I didn't get a single entry. Is this fine?

So if I create an entry in the tables as said in the blog, will that not create any inconsistency.

Please suggest any other way if we can achieve this?

Thanks,

Sameer

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Varun Agarwal
Oct 31, 2017 at 11:20 AM
0

Hi Sameer,

Changing the data type or data length for AET generated fields is not recommended or supported as there is a great chance of loosing all the data and making the extension corrupted.

The best way to deal with this situation would be to create a new field of your choice, then write a custom report to move the data from the existing field to the new one. Once that is successfully done and verified, you can remove the old field.

Please Note: If a custom field generated through AET is marked for BW Reporting, when deleting such a custom field, the BW related structure will also be updated. This update will surely help to adjust data to be loaded in future, but regarding the data which was already extracted to BW, it will not be removed because of this action. That is for example, after the AET field is created, there were some data created and stored into this field. The BW extraction happened and the data was moved to BW system. After this field deletion, the newly extracted data won't contain the data for this field, but for the already existing data in BW, it will require some manual actions from BW side to get it excluded when issuing BW report.

Best Regards,
Varun Agarwal

Share
10 |10000 characters needed characters left characters exceeded