972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Master data

DMSTAT Data maintenance status report/query

The UN/EDIFACT message that transfers, or queries, the status of data maintenance requests among parties in the directory process.

Sent by
Standards working group or submitter
Received by
Submitter or other process parties
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT DMSTAT message?

DMSTAT is the UN/EDIFACT data maintenance status report/query message. The directory defines it as a message that transfers the status of any data maintenance request (DMR) action among the parties involved in preparing, processing, assessing and resolving requests and producing directories. It can also be used to query that status.

Each change request passes through stages such as received, under assessment, approved, rejected and published. DMSTAT lets submitters and working groups follow requests without manual correspondence. Implementers can use status reports to anticipate changes in upcoming directory releases.

How the EDIFACT DMSTAT message worksDiagram of the UN/EDIFACT DMSTAT Data maintenance status report/query message. Standards working group or submitter sends it to submitter or other process parties. It usually follows DMRDEF. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG1 loop with PNA (Party identification) and the required SG2 loop with HYN (Hierarchy information). 2 conditional segment groups are listed by their trigger segment.How the EDIFACT DMSTAT message worksData maintenance status report/query: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSDMRDEFData maintenancerequest definitionDMSTATSENDERStandards workinggroup or submitterRECEIVERSubmitter or otherprocess partiesCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage DMSTATUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats up to 9PNAParty identificationMandatory group SG2 · repeats many timesHYNHierarchy information+ 2 conditional groups, starting with:STSIRQBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for DMSTAT. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT DMSTAT message worksDiagram of the UN/EDIFACT DMSTAT Data maintenance status report/query message. Standards working group or submitter sends it to submitter or other process parties. It usually follows DMRDEF. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG1 loop with PNA (Party identification) and the required SG2 loop with HYN (Hierarchy information). 2 conditional segment groups are listed by their trigger segment.How the EDIFACT DMSTATmessage worksData maintenance status report/query: whosends it, where it fits and what the directorymarks mandatory1 WHERE IT FITSUSUALLY FOLLOWSDMRDEFData maintenance request definitionDMSTATSENDERStandardsworking groupor submitterRECEIVERSubmitter orother processpartiesCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message DMSTAT (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 9PNAParty identificationMandatory group SG2 · repeatsmany timesHYNHierarchy information+ 2 conditional groups, starting with:STSIRQBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for DMSTAT.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends DMSTAT, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around DMSTAT and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Reporting the status of change requests
  • Querying the status of a submitted request
  • Coordinating requests between working groups

Where it fits in the message flow

Usually follows DMRDEF Data maintenance request definition
This message DMSTAT Data maintenance status report/query

Structure

Mandatory segments in DMSTAT (directory D.21A)

In UN/EDIFACT directory D.21A, the DMSTAT message has 17 segment positions arranged in 4 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • DTM
  • SG1 (PNA)
  • SG2 (HYN)
  • UNT

Practical example

DMSTAT in practice

An industry representative wants to know whether a submitted code request will be in the next directory. Its system sends a DMSTAT query for the request number. The answer shows the request was approved with a modified description and is scheduled for the next release.

Implementation

Implementation considerations for DMSTAT

  • Reference data maintenance request numbers exactly.
  • Follow UN/CEFACT procedures and status definitions.
  • Communicate approved changes to affected implementers.
  • Plan implementation around directory release dates.

How ECOM helps

Automate DMSTAT with ECOM

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Service

Mapping and Translation

Map development and maintenance for X12, EDIFACT, XML, JSON, flat files and ERP formats.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related master data messages

All 11 master data messages

Need help with DMSTAT?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us