Skip to Content

One should understand the fact that it’s a lot easier to add fields via EEWB than removing the added fields. Hence EEWB should be used with caution for adding the fields. However, in the project scenarios, one can not be fully cautious and a situation may arise where the fields added via EEWB needs to be deleted from the custom screen.

Context:

In the diagram shown below, the BDT screens, sections and views are marked for reference.

Context

Some facts about BDT Screens, Sections and Views: 

  1. One screen can have maximum of 10 sections and one section can have maximum of 10 views. 
  2. For each new extension created, EEW creates one or more sections depending on the number of fields/views. Also, if the limit of sections is reached then a new screen is created.

Scenario: In this blog, we are discussing an example of BP extension by EEWB where some custom fields are added to BP and there existed some custom fields previously. Now for some reason, the newly added fields need to be deleted andCustom screen entries in V_TBZ3A for that purpose, the new project/extension is deleted in EEWB then it may or may not cause issues as explained below –

  1. If the previously created project / extension exist in the system then there would be no adverse repercussions of deleting the new extension/project.
  2. If the previously created project/extension does not exist in the system (Reason explained below) then, on deletion, EEWB will treat the new extension as the first extension of the application and thus will delete the existing custom screen entry and hence all the screen to section mapping as well in TBZ3* tables (details mentioned below) along with deletion of new fields.

Reason: One of the possible scenario can be in the case where 2 different SAP landscapes are used – lets say one for the Upgrade/Implementation purposes (say ‘A’) and the other for Production Support purposes (say ‘B’). In this case if the previous extension was created in landscape ‘A’ and then system ‘B’ was upgraded from system ‘A’ then the EEWB project/extension (created in ‘A’) will not exist in landscape ‘B’ as the EEWB project/extension are not migrated in Transport Requests. Hence in this case, the custom fields created in the previous extension would exist in system ‘B’ but the EEWB project would not exist and the scenario 2 mentioned above will become true and any deletion of EEWB project/extension could create issues as mentioned above in scenario 2.

Result: For the scenario 2 mentioned above, due to the missing BDT screen the ‘BP’ transaction will start throwing dump with the error ‘No Active Tabs’. The tables impacted would be –

Table         Description

TBZ3A        BDT Screens

TBZ3K        Assign BDT Screen Sequence -> BDT Screen

TBZ3I        Assign BDT Screen -> BDT Sections

Resolution:

  • Maintain the view V_TBZ3A (shown below) in transaction SM30 for the entries in TBZ3A table. The missing BDT custom screen entry (e.g. ZG0000 in this case) would need to be added. Refer to the data in table TBZ3A in any unimpacted environment for the correct data. ‘Screen Number’, ‘Description’ and ‘Screen title’ are the fields required to be maintained. 

View V_TBZ3A

 

  • View ‘V_TBZ3K’ or Transaction ‘BUS6’ (snapshot shown below) can be used to maintain the table TBZ3K. The custom screen entry would need to be added in the screen sequence (e.g. Screen ‘ZG0000’ in Screen Sequence ‘BUP001’ in the snapshot below). Refer to the data in table TBZ3K in unimpacted environment for the correct data. The ‘Screen Number’ would be the same as entered in TBZ3A above (e.g. ‘ZG0000’ in this case). The other two fields ‘Description’ and ‘Screen title’ would be auto-populated from table TBZ3A.

View V_TBZ3K 

 

  • View V_TBZ3I (snapshot shown below) can be used to maintain the table TBZ3I. The mapping of screen and sections would need to be added. Refer to the data in table TBZ3I in unimpacted environment for the correct data to be maintained. Note – In case there is no unimpacted environment to refer to then table TBZ3C can be referred for ‘Sections’ data. As data in table TBZ3C is not impacted by the deletion of extension so cross check all the custom sections (for application impacted e.g. BUPA in this case) in the table TBZ3C with the mapping data in TBZ3I. Identify the custom sections in TBZ3C that doesn’t have mapping to the custom screen in TBZ3I table.

 

View V_TBZ3I

 

 

** Note – The tables maintenance required will be for the tables as listed above. However, the data shown above is just an example and users should refer to the other environments (unaffected from the EEWB changes e.g. QA/Prod) for the correct table entries required to be maintained.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply