Default Values for Transport Types in ChaRM
By default both Workbench request and customizing requests are selected when a transport request is created in ChaRM. This documents explains the steps to change the defaults.
Background: In ChaRM when the status of a Change Document is “In Development” and a transport request is required to be created.
Both Workbench Request and Customizing Request are checked by default.
Requirement: Neither should be checked by default.
In some cases you we might want the user to choose what type of transport they want to create. We know that CHARM can create both transport
types and then remove the empty request when moved to test – however it consumes another transport number and potentially skews reporting on the number of open real changes in Development. We performed this enhancement by request for several customers on Solution Manager 7.1 SP08; will update SCN if we also perform on SP10.
Solution:
Press F2 on the Workbench Request to get the Technical Details of UI component and view to be enhanced.
Transaction: SM34
Transaction: SM30
Transaction: BSP_WD_CMPWB
Application: ZAIC_CM_TRANSCR
Enhance Component and View AIC_CM_TRANS_CR/TransportReqPage1
Redefine method
do_prepare_output of class ZL_AIC_CM_T_TRANSPORTREQP_IMPL to change the
values of fields ‘CUSTOMIZING_REQ’ & ‘TRFUNCTION’.
CALL METHOD super->do_prepare_output.
Data: lr_prop_cust type ref to if_bol_bo_property_access,
lr_prop_trans type ref to if_bol_bo_property_access.
constants: c_cust type name_komp value ‘CUSTOMIZING_REQ’,
c_trans type name_komp value ‘TRFUNCTION’.
lr_prop_cust ?= me->typed_context->BTAICREQTYPE->collection_wrapper->get_current( ).
if lr_prop_cust is bound.
lr_prop_cust->set_property( iv_attr_name = c_cust
iv_value = ‘ ‘ ).
endif.
lr_prop_trans ?= me->typed_context->BTTRANSREQ->collection_wrapper->get_current( ).
if lr_prop_trans is bound.
lr_prop_trans->set_property( iv_attr_name = c_trans
iv_value = ‘ ‘ ).
endif.
Dear Vanita Motwani Mody ,
thank you for this great document! We had an implementation on SM 7.2 (which was much more complicated), now we want to adapt it to SM 7.2. As it seems, SAP renamed "BTTRANSREQ" and "BTAICREQTYPE", do you have any hint how we can modify the coding so that it still works?
Best regards,
Daniel Lippmann
Any idea how we can implement the same in SOLMAN-7.2. As I see there is no relative tables had an entry in it.
Regards,
Vinayak Budapanahalli
Hi Friends ,
i am looking for similar solution , please do share your valuable inputs .
Thanks Siri