12. Construction of XML by drag and drop

Transform field data into structured ERP flows, without development

The construction of XML by drag and drop constitutes one of the pillars of the ERP integration module in SOOKSOOK.
It allows data from the field to be transformed into a structured format that is perfectly compatible with an ERP system such as SAP, Oracle or any other business software.

Unlike traditional approaches requiring specific development, SOOKSOOK offers a visual interface allowing you to simply define the correspondences between field data and the expected XML tags.

👉 The objective is clear:
allow a business user (and not a developer) to build a reliable, structured and automated ERP flow.

---

General principle

Each information produced in SOOKSOOK (publication, form, message, intervention, etc.) is associated with a specific XML tag.

The system therefore operates on a logic ofmapping :

👉 SOOKSOOK data = an XML tag = an ERP field

This mapping makes it possible to translate data readable by humans into data usable by a computer system.

---

XML mapping structure

The build interface is based on three fundamental elements:

• SOOKSOOK fields (data source)

• XML tags (ERP format)

• business logic (role of each piece of data)

Each configuration line represents a complete correspondence between these three dimensions.

---

Block 1: Identification and structuring of the flow

XML always begins with technical data allowing the flow to be identified and structured.

The tagSEQNUMcorresponds to a unique identifier of the flow.
It ensures traceability and avoids duplication on the ERP side.

The tagPLANTrepresents the site code (for example FOS).
It allows information to be linked to an industrial or organizational entity.

The tagNREPcorresponds to the SOOKSOOK report number or publication identifier.
It makes it possible to make the link between the ERP and the field source.

The tagMPOINTrepresents the technical station or equipment concerned.
It is a central element for maintenance, because it makes it possible to precisely target the impacted installation.

---

Block 2: Business content (core of information)

The heart of XML is made up of business data from the field.

The tagSTEXTmatches the short text.
This is a summary of the intervention or problem (e.g. “Cabin door fault”).

The tagLTEXTmatches long text.
It contains the detailed description, diagnosis and context.

The tagSOLUTIONallows you to indicate the action performed.
It formalizes the response to the problem (troubleshooting, repair, replacement, etc.).

👉 This trio (STEXT / LTEXT / SOLUTION) constitutes the operational heart of the ERP flow.

---

Block 3: Prioritization and impact

Certain tags allow you to add a dimension of criticality and analysis.

The tagPRIORsets the priority level.
It is often converted from a SOOKSOOK value (high / medium / low) to an ERP code.

The tagIMPACTENVmakes it possible to specify the environmental impact.
It may remain empty or contain information in the event of an incident.

👉 This data makes it possible to prioritize and qualify interventions.

---

Block 4: Compliance and regulatory monitoring

XML can incorporate compliance-related information.

The tagOCTRLcorresponds to the control office (eg: Veritas, Dekra).
It makes it possible to identify the organizations involved.

The tagSTATEcorresponds to the status of the object (open, in progress, closed).
It allows you to monitor progress in the ERP.

The tagREASONcorresponds to the cause or justification.
It makes it possible to identify the origin of the problem (wear, defect, incident, etc.).

👉 These elements are essential for audits and regulatory monitoring.

---

Block 5: Document management

XML can include references to documents.

The tagDOCUMENTS_IDallows you to list the associated files:

• PDF reports

• photos

• justificatifs

• technical documents

👉 This allows you to send not only data, but also evidence.

---

Block 6: Location

Location can be expressed in two forms.

The tagRENTAL (GPS)allows you to indicate a precise geographical position (latitude / longitude).

The tagRENTAL (text)allows you to indicate a descriptive location (e.g.: “HF1 level 22m”).

👉 This facilitates field analysis and data exploitation.

---

Block 7: User information

The XML may contain information about the author.

The tagNamecorresponds to the name of the technician or worker.
The tagEmailcorresponds to his email address.

The tagAuthor_idcorresponds to its internal technical identifier.

👉 This data ensures human traceability.

---

Block 8: Operational management

Certain tags make it possible to link the flow to the organization of work.

The tagOT numbercorresponds to the work order.
It allows you to link the intervention to an existing process in SAP.

The tagTypeAviscorresponds to the ERP notification type.
It allows information to be automatically classified (maintenance, security, work, etc.).

---

Block 9: ERP organization

XML can integrate organizational information.

The tagINGRPcorresponds to the planner group.
It helps guide treatment.

The tagARBPLcorresponds to the workstation or work center.
It allows you to structure the organization in the ERP.

---

Block 10: Typology of breakdowns

The system allows incidents to be classified.

The tagPFType failurecorresponds to an internal SOOKSOOK typology.

The tagFault type (code)corresponds to a standardized ERP code.

👉 This allows statistical analysis and better use of data.

---

Block 11: Time management

Timing information is essential.

The tags:

• StartDate(start date)

• StartTime(start time)

• EndDate(end date)

• EndTime(end time)

allow you to:

• measure the duration

• follow the interventions

• analyze performance

---

Overall system logic

The drag and drop system therefore allows you to:

• select useful fields

• define their XML correspondence

• organize the structure

• enrich the data

• automatically generate the feed

👉 All without writing code.

---

What this actually changes

Before :

• unstructured data

• manual re-entry

• common errors

After :

• structured data

• automatic integration

• high reliability

---

Conclusion of the chapter

Drag-and-drop XML construction completely transforms ERP flow management.

SOOKSOOK does not just collect information:

👉 he structures it
👉 he normalizes it
👉 it makes it usable
👉 it sends it automatically

---

👉 Result:

💥 a direct gateway between the field and the ERP, without technical complexity