Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Cha Cha,
The Field exit mentioned by David will achieve your requirement. We use this to enforce a naming standard similar to the one you have suggested. Our format is <project>:<functional area>:<call number>:<general description>.
This, in turn, allows us to use workflow and the stms QA system so that transports can be approved by an appropriate person according to functional area and project. We also store the call number associated with the transport in the transport description for audit purposes.
Judy.
| | | ---------------Original Message---------------
From: geunrisse
Sent: Wednesday, October 13, 2010 5:19 AM
Subject: Restrict the naming of a Transport Request
Hello all,
Good day!
i would like to inquire if there is a possible way to restrict or control the naming of a transport request? We plan to to implement a naming convention regarding the creation of transport requests. Standard naming convention is a necessity so that we can identify quickly the ones that needs to be transported, or the ones that needs to be deleted during clean up activities. This should be strictly followed by users, instructors, trainees and developers. This is especially for the Cross-Client Objects, to differentiate objects to be migrated from those that are garbage objects. This naming convention needs to be strictly followed by developers to avoid their asset objects to be deleted in the system.
For example, if the changes made were related to configuration, the TR should be named TRN_BC_DEV: Basis Custom Table Deployment
where
TRN: object indicator which means that the TR is Training related.
BC: functional module; BC is for Basis. incase the TR is ABAP related, then it should be AB.
DEV: Change type; this indicates that the TR involves Cross-Client Objects.
Basis Custom Table Deployment: this is the description of the purpose for which the TR was made for.
we want to restrict this. so if the end-user named the TR with anything else that does not follow the naming convention we have established, the end-user should encounter an error stating the he/she must change the name of the TR and follow our naming convention before he/she could proceed.
is there a way to implement this?
thank you very much in advance for your inputs.
regards,
charisse |
| __.____._ Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| | Related Content Most Popular White Papers
In the Spotlight  _.____.__ |
Mark as helpful
