cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Issue with BAdI /SAPSLL/BADI_EXT_UI_PRD

pastrzig
Explorer
0 Likes
817

Hi,

I enhanced table /SAPSLL/PR with additional columns and want to display and edit their values in the product view (transaction /SAPSLL/PRODUCT_0X). To do this, I use the BAdI /SAPSLL/BADI_EXT_UI_PRD. The BAdI has the interface /SAPSLL/IF_BADI_EXT_UI_PRD. The interface implements the methods PAI_CALL and PBO_CALL. PAI_CALL has a changing structure CS_PRD_CUST whose values are displayed on the dynpro. PBO_CALL provides the importing structure IS_PROD_OBJ, which (among other things) contains the corresponding fields for the output on the dynpro.

This brings me to my problem: If you transfer changes with CS_PRD_CUST via the PAI_CALL method and switch from edit mode to display mode, a popup is displayed to the user asking whether the data should be saved or not. If the user clicks No (do not save), the program switches to display mode. However, the PBO_CALL method returns the values that should not be saved. The correct values are not displayed until the user exits and calls the transaction again.

Does anyone use this BAdI? Is there a way to fix this issue?

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member215181
Active Contributor

Hi Tobias,

I think you should probably create an OSS Incident for this issue. From what you've found, it seems like the original data is not being re-loaded with the change from "Edit" to "Display" mode.

Regards,
Dave