Playing around with existing implementations I can see that, BADI_SD_TAB_CUST_H, can definitely enhance the Sales order

header with additional tab strip screens . Similarly BADI_SD_TAB_CUST_I can be used to enhance Sales order item screens. Here is what I understand from the coding of an existing implementation ACTIVATE_TAB_PAGE - takes a module pool program name and a subscreen that you cr eated and adds it as a additional tab page to sales order header screen. You nee d to pass back f_program and f_dynpro with your program and screen number that y ou painted TRANSFER_DATA_TO_SUBSCREEN - can be used to read and pass data to the fields on the subscreen you created TRANSFER_DATA_FROM_SUBSCREEN - can be used to pass back whatever changes done by user to the respective Z variables in VBAK PASS_FCODE_TO_SUBSCREEN - Pass the fcode the user selected to your subscreen. I would suggest that you create a function group and create screens, functions e tc within that and use those in these methods. Refer existing implementations.