PRMAN-Technical Overview

This diagram illustrates a comprehensive product inventory management system with multiple interconnected components. Here's a breakdown of the architecture:

System Architecture

roduct Relationship Manager Rest API activity diagram.

Side Effects

The Product Relationship Manager (PRMAN) is primarily concerned with computational processes rather than data storage.

At present, the PRMAN REST API exposes a single endpoint, with two additional endpoints planned for implementation in the near future.

The POST /offer-qualifications endpoint accepts a JSON payload containing a SAART L3 customer identifier. PRMAN subsequently retrieves relevant promotions from the Common Catalog and associated products from the Product Inventory Management system for the specified SAART L3 customer. Each promotion includes a PromotionPattern comprising evaluation criteria, which PRMAN assesses against the customer's product data. For each promotion where the customer satisfies the criteria, the promotion ID is included in the HTTP response within the `responseData.offerQualifications` field.

Dependencies:

Product Inventory Management (PINV/C360) The eligibility criteria for all four promotions currently supported by PRMAN are encoded to evaluate the products associated with a customer (TMF637). For these promotions, only the product CRU needs to be onboarded to Product Inventory Management (PINV/C360). Without the product being fully onboarded to Product Inventory Management, it is not possible to accurately assess promotion eligibility, as incomplete or ambiguous information—such as a customer potentially possessing the CRU without it being loaded into PINV/C360 prevents reliable evaluation.
Common Catalog The Common Catalog capability serves as the authoritative source for available promotions (TMF671). Each promotion includes a PromotionPattern that defines the eligibility criteria for that promotion.