RMA Supplier

Overview

RMA Supplier is the supplier’s window onto the returns that RMA Staff raised and RMA HQ approved. The supplier sees the approved items and accepts or rejects each one; rejected items are what the discrepancy note prints. Unlike the HQ and Staff rows, this is a separate bundle on its own route.

It is not the supplier RTV in the Internal RMA applet, which is a stock-moving INTERNAL_SUPPLIER_RTV document raised by your own staff.

The bundle rma-supplier-applet/prod/rma-supplier-applet-elements.js has no source repository in any organisation this documentation server can read (checked 2026-09-16). This page documents the registry row and the backend surfaces a supplier-side RMA screen can use — and no screen, field or setting, because none has been read.

Where it fits


Registry	`rma_supplier` · name RMA Supplier · type `TNT-APPLET` · ACTIVE · row created 2025-09-25
Route	`applet/tnt/wavelet/rma-supplier-applet`, custom element `rma-supplier-applet-elements-` — its own bundle, unlike the HQ / Staff pair
Upstream	Items HQ has approved (`rma_itm_hq_approval = RMA_ITM_HQ_APPROVED`)
Downstream	Accepted items travel under the RGPL; rejected ones (`rma_itm_supplier_acceptance = RMA_ITM_SUPPLIER_REJECTED`) print on the discrepancy note
Who opens it	A supplier — a login entity, not a tenant user. The backend’s supplier-facing endpoints are the `login-entity-ep` variants, which check `isUserLoginEntity` rather than a permission

Screens and menus

Not documented — no source read.

Configuration

Before you can use it

Prerequisite	Where it is set	Why it matters here
The supplier exists as an entity with a login	Supplier and the entity’s login	`login-entity-ep` endpoints serve only a signed-in entity
Items already approved by HQ	RMA HQ	There is nothing to accept before that
A Google Docs template for the discrepancy note	Wherever the tenant keeps its template document IDs	Printing takes the template ID on every call

Applet settings

No source read (bundle repository not found, 2026-09-16). Not documented.

Feature visibility / permissions

bl_applet_client_side_perm_dfn has no rows for rma_supplier. Server-side, a supplier login reaches generic documents through the login-entity-ep endpoints, which check that the caller is a login entity and that the document belongs to it, and reaches service-note requests through svc/issue-request-hdrs/login-entity-ep.

Fields

Not documented — no form model read. The supplier’s decision is the line-level extension row rma_itm_supplier_acceptance; the only value the backend looks for is RMA_ITM_SUPPLIER_REJECTED (the discrepancy print). The acceptance value is not named anywhere in blg-akaun-platform-java, so it is set and read only by the UI.

Lifecycle and effects

Accept / reject is a write to bl_fi_generic_doc_ext on the line. No backend validator constrains the value or checks that HQ approved the line first.
Nothing moves stock or posts. The RMA document types are 0 / 0 (see RMA HQ). The goods themselves come back to the supplier under whatever purchase-return document the tenant raises.
Discrepancy note. RmaDiscrepancyPrintService, called through the generic-document print-pdf endpoint (RMA HQ page, Printing), prints the lines whose rma_itm_supplier_acceptance is RMA_ITM_SUPPLIER_REJECTED into the template’s item table.
Supplier listing in the backend. GET …/svc/entity-rmas/SUPPLIER/backoffice-ep/query lists service notes with no service-document line yet, and for the supplier entity type it requires doc_hdr_guid — the call is rejected with “Kindly Provide an Appropriate doc_hdr_guid for Supplier” without one (RMAEntityUow.java:37). No UI this server can read calls it; it is listed because its name matches this family.
Automation. Tenant-specific job processors in the backend can mark HQ-approved items as accepted on the supplier’s behalf after a configured inactivity period. They are enabled per tenant through job-processor templates, not from this applet, and are not part of the product’s standard behaviour.

Related applets

RMA HQ and RMA Staff — the tenant-side builds this applet answers.
Rma Applet (Internal) — the service-note based applet with its own supplier RTV.
Supplier — the entity that signs in here.

Troubleshooting

Symptom	Cause	Fix
The supplier sees no items	Nothing has reached `RMA_ITM_HQ_APPROVED`, or the supplier is signed in as a tenant user rather than a login entity	Approve in RMA HQ; sign in with the entity login
Items show as accepted although the supplier did nothing	A tenant-specific auto-accept job processor is enabled	Check the tenant’s job-processor templates
The discrepancy note is empty	Only lines with `rma_itm_supplier_acceptance = RMA_ITM_SUPPLIER_REJECTED` print	Nothing was rejected, or the rejection was not saved