IHPA table — PM Partner Assignment Table

One row in IHPA represents a single partner function assigned to a single PM or CS object. The object is not identified by equipment number or functional location code but by the generic object number (OBJNR) that SAP uses to link status management, classification and partner data across many application areas. A functional location might have one row for the 'ordered by' function, another for 'manufacturer', another for a responsible sales employee, each pointing to a different partner number. The same structure is reused for equipment, PM orders, notifications and maintenance plans, so the table is shared infrastructure rather than a PM-specific master data table in the usual sense. It does not store the partner's name or address itself, only the assignment and function.

IHPA is client-dependent and can be large across a landscape with many equipment and functional location records, each carrying several partner functions. Never select on it without first restricting OBJNR to a known set, because there is no direct equipment or functional location field to filter on. The normal path is to look up the object number in EQUI, IFLOT, AFIH or VIQMEL first, then query IHPA with that value or a range of values. Restricting by PARVW narrows results to a specific function, which is usually what the investigation actually needs rather than pulling every partner row for an object.

To confirm who is set as 'ordered by' on a piece of equipment, first read EQUI for the equipment number to get OBJNR, then select IHPA where OBJNR equals that value and PARVW equals the ordered-by function code from customizing. The PARNR returned is then looked up in the customer or vendor master depending on the partner function's category to get the actual name. An empty result set confirms no partner was ever assigned for that function, not that the assignment was deleted.

IHPA continues to exist as a transparent table in S/4HANA and is still the table PM and CS transactions write to when maintaining partner assignments on equipment, functional locations, orders and notifications. The underlying customer, vendor and personnel master data feeding PARNR has moved toward the unified Business Partner model in S/4HANA, but that consolidation happens in the master data layer, not in the structure of IHPA itself. No general replacement by a compatibility view is expected for this table in the way seen with some finance and sales tables.

Partner function customizing (which functions exist and what they represent) belongs to the PM configuration team. Day-to-day assignment of actual partners to equipment or functional locations is maintained by the maintenance planner or master data steward responsible for the technical object. Cross-object partner data quality issues that surface in reporting are usually a master data governance question, not a Basis or ABAP one.

IHPA is written whenever the partner tab is maintained on equipment through the equipment master transactions, on functional locations through the location master transactions, on orders through order maintenance, and on notifications through notification maintenance. The object-owning tables EQUI, IFLOT, AFIH and VIQMEL supply the OBJNR needed to query IHPA, and status table JEST shares the same object number key convention.