SAP SRM ECS: MASS Update the Purchase Order in SAP SRM to ECC

INTRODUCTION

In the Extended Classic Scenario of the SAP Supplier Relation Management module, we know that the Purchase Orders are created in the SRM system and is then replicated or copied back to the ECC system. In other words, in an extended classic scenario, the procurement process takes place in the SAP SRM system. The purchase order is created in the SAP SRM system and a read-only copy of the purchase order is replicated to the backend system.

Now suppose that the client’s SRM consultants want to have a custom program to update the Purchase Order(s) in the SAP SRM system in MASS, where one would pass the excel file as input to the program with the details like PO Number, line item number and the columns/fields which they intend to change through the program.

Handy CL_GUI_ALV_GRID wrapper

CL_SALV_TABLE or CL_GUI_ALV_GRID which class is better to use in 2021 ?

Probably old abapers remember that more than decades ago that there was shift from the “old-fashioned” CL_GUI_ALV_GRID class & ‘REUSE*’ function modules towards new up-to-date & OOP style class CL_SALV_TABLE. At 2020 I decided to move backwards to CL_GUI_ALV_GRID. At the small article below I try to explain why I made that decision. And it is not related to nostalgia.

One of the reasons to use CL_SALV_TABLE was small amount of code compared to CL_GUI_ALV_GRID. Also, there was no need to create new screen & containers to display a grid. But then new syntax 7.40 was introduced and passing parameters to any method via structures & tables simplified drastically. I decided to fill a gap and just add nested screens functionality for CL_GUI_ALV_GRID.