SupplierAcknowledgement (PUT) | GEP TECH DOCUMENTATION

Overview

Clients use the Supplier Acknowledgement API to confirm the receipt of modified supplier data and indicate whether the ERP system has accepted the modification.
• If isInterfaced is set to false or true and sourceSystemName is empty, the API will search for a profile where the source system is not interfaced.
• If a specific sourceSystemName (e.g., "Oracle", "SAP", "Client Supplier Code") is provided, the API will check against the corresponding source system and return results based on the isInterfaced flag.

URL Format:
https://<Instance>/leov2-supplier-composite-microservice/api/v1/PlsOutbound/AcknowledgeSupplier

Request

{
    "clientPartnerCode": "string",
    "status": "string",
    "comments": "string",
    "sourceSystemName": "string",
    "sourceSystemId": "string"
  }

Response

{
  "statusCode": int,
  "successDetails": [
    {
      "key": "string"
    }
  ],
  "errorDetails": [
    "string"
  ]
}

Data Elements

Property	Required?	Data Type	Description	Validations / Exceptions
clientPartnerCode	Yes	String	Unique code provided by the client's ERP system to identify the partner.	Must be a non-empty string, alphanumeric, and adhere to predefined format.
status	Yes	String	Status of the partner or process (e.g., "Active", "Inactive").	Must be a valid status value defined by the system.
comments	No	String	Additional comments or notes related to the request.	Optional; maximum length of 255 characters.
sourceSystemName	No	String	Name of the source system from which the request originated.	Must be a valid system name, alphanumeric, and adhere to naming standards.
sourceSystemId	No	String	Unique identifier for the source system sending the request.	Must be a valid string format if applicable.

Property	Required?	Data Type	Description	Validations / Exceptions
statusCode		Integer	HTTP status code representing the result of the request.	Must be a valid HTTP status code (e.g., 200, 400).
successDetails		Array	Array of objects containing details of successful operations.	Optional; each object must contain a key field with a valid string.
successDetails.key		String	Key representing a specific success detail, such as an identifier or additional information.	Must be a non-empty string.
errorDetails		Array	Array of strings containing error messages or details about failed operations.	Optional; each element must be a valid string describing the error.