GRPG_PO_COMPONENT is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Grouping/Pegging: purchase order object components" Information within sap ABAP programs. This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately. i.e. DATA: wa_GRPG_PO_COMPONENT TYPE GRPG_PO_COMPONENT.
The GRPG_PO_COMPONENT table consists of various fields, each holding specific information or linking keys about Grouping/Pegging: purchase order object components data available in SAP. These include EBELP (Item Number of Purchasing Document), ZEKKN (Sequential Number of Account Assignment), PSPNR (Grouping WBS element), REPOBJ (Object number of replenishment elem. used for static pegging)... See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .