Making Documentation mandatory in Transport Request

[Former Member]

Hi......

I've got a requirement were in i need to include documentation(like for what purpose we've created this and its explanation are included it the concern documentation field of every transport request........we get this field while we double click on the request id in SE09).

Now when we release the task under the request and then later the request id to QAS or to PRD we should get a pop message(an error or information message) mentioning that the documentation is empty....Making documentation as mandatory.......while transporting the request.................Any one has got any idea...of how we need to work on this.........

Points would be rewarded for the sure..........

[Former Member]

Hi......

I've got a requirement were in i need to include documentation(like for what purpose we've created this and its explanation are included it the concern documentation field of every transport request........we get this field while we double click on the request id in SE09).

Now when we release the task under the request and then later the request id to QAS or to PRD we should get a pop message(an error or information message) mentioning that the documentation is empty....Making documentation as mandatory.......while transporting the request.................Any one has got any idea...of how we need to work on this.........

Points would be rewarded for the sure..........

[Former Member]

Hi,

I dont think you can make it mandatory. The only alternative is to ask the team to follow it regularly and the team lead needs to review the same before releasing the transport.

Best regards,

Vasanth

[Former Member]

Hi Vasanth,

Thx for the reply....Now how can a team lead do this......as you know when we transport the request onces from dev to qas....the documentation or any other stufff cant be added......any how the pushing of request is done from our end and we do make mistakes and dont check them while pushing it to QAS.So once its done to qas we cant handle it any more right........any standard programming can be changed or help from OSS??????

[former_member404244]

Hi,

The solution given by vasanth is perfect...we cannot make it mandatory,so the other option is the entrie team should follow it and the people who reviews the object,should also review the documentation part of the request....this is how it should be....it should be put in ur clients standards ,so that evry one can follow..even if any one misses it its the duty of the reviewer to intimate the same to the devloper.....

Regards,

nagaraj