on 06-07-2011 1:05 PM
Dear All:
I wish to change field length for an AET generated ZZ field which was defined some time ago.
The surprise I got is in the field details, the field length is greyed.
Does anybody know how to proceed?
I saw thread , but this thread does not help me.
I searched OSS notes, but did not succeed to find any relevant information about it.
I checked programs and transactions in AXT_STRUCTURE package, but I was not able to find anything.
Thank you in advance.
Jordi
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jordi,
How did you resolve this?
Regards,
Priya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jordie / Priya,
This is very much painful task but I think can be achieved through little care.
Use the report AXT_EXT_ANALYZE give the Extension ID whichi is generated and run it.
This will tell you what append structures are created and what configurations are maintained.
If you change it that will solve your issue.
Regards,
Naresh
Also you can check the enhancement spots : AXT_FIELD_DEF_EXIT and AXT_FIELD_EXTENSION_EXIT
Edited by: Naresh Patel on Sep 20, 2011 12:03 PM
I document the procedure I built with my experience, and I close this thread.
1- Identify Extension ID of the AET field (Transaction AXTSHOW) .
2- Adapt Metadata: Change in Table AXT_EXT_PART_DTL (OBJ_PARAMETER LENGTH, set OBJ_PARAMVALUE to the desired length).
Include the entry in a transport order (Mandant intependent, Workbench order).
3- Adapt Metadata: Change in Table AXT_CAT_OBJ_DTL (OBJ_PARAMETER LENG, set OBJ_PARAMVALUE to the desired length).
Include the entry in a transport order (Mandant intependent, Workbench order).
4- Include in a transport order the Extension ID (Workbench order)
5- Run AXT_EXT_ANALYZE -> No inconsistencies found
6- Regenerate the extension (Transaction AXTSHOW)
7- Set the final width in the domain (SE11) (Workbench order).
Activate, the system adjusts dependent objects.
Activation gives error in BUT000 (normal, as expected)
8- Activate and adapt BUT000 (SE14), in Background, keeping data.
Process ended successfully.
6- Once adaptation is finished, build again the statistics of BUT000 (DB20)
Hope this helps.
Jordi
HI Jordi,
You can try my suggestion.
Create a new AET field with your desired length and hide the current field from the WEBUI, database still exists. In GET methods you may retrieve the data from Old to New. Any changes to data will get into the new one only.
Good luck..!
Cheers, Satish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I don think its not possibel to change the length after creating the filled through AET. just delete this field through AET and create a new one.
regards,
Gobi.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jordi,
You can do so by doing changes at the relevant data element level. When you activate this data element, the system will automatically adjust all the relevant tables, structures, view, etc..
I also faced this situation in the past where user changed the requirement. Modifying and activating the data element will not have any negative affects for sure.
Thanks
Vishal
Dear Vishal:
What you suggest is obvious. But take care, this is not enough!! .
There is a framework, which stores the metadata of every AET field. This has to be aligned with the data dictionary. I'm working now in this direction.
Take a look at AXT_STRUCTURE package (and subpackages), and you will understand what I mean.
I believe what you say, sure. Dictionary will be OK. But if AET metadata is not aligned, a problem could occur in the future (some upgrade, some additional enhancement...)
I opened an OSS question about this topic.
Best regards
Jordi.
User | Count |
---|---|
5 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.