Require specific fields on inbound documents and lines before auto-processing accepts them.
Centara Inbound e-Document Validation Setup
BC page: Centara Inbound e-Document Validation Setup (List) · Search: “Centara Inbound e-Document Validation Setup” Source:
RSMSTAValidationSetup.Page.al
The Validation Setup lets you declare “these fields must not be empty on an inbound document before auto-process is allowed to handle it”. When the validator runs over a new inbound document, any row in this table that points to a blank field puts the document into Error with a clear message — instead of letting the auto-process pipeline fail later with a less obvious symptom.
Common use cases: require an Accounting Cost on every header, require a Buyer Reference on every line, etc.
Columns
| Column | What it controls |
|---|---|
| TableName | The Centara table the validation applies to. Use the lookup to pick between RSMSTA IntegrationPeppolHeader (header-level fields) and RSMSTA IntegrationPeppolLines (line-level fields). Mandatory |
| FieldName | The specific field that must be filled. Use the lookup to pick from the fields available on the selected table. Mandatory |
How validation runs
The validator is invoked by RSMSTAAutoProcessPO (the auto-process engine) before it tries to match an inbound document against a Purchase Order. If any rule fails, the document moves to Error with a message naming the missing field. The user can then either edit the inbound document or fix the source before the next pipeline run.
For a wider view of the auto-process pipeline see Auto Processing.
See also
- Auto Processing — where validation fits in the pipeline
- Documents to Review — failed documents that ended up in Error