Preview of Transformed EDI Data

> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/setup/document-types/edi-data-transformation-process.md). # EDI 数据转换流程 {% embed url="" %}

#### 第 1 步：结构描述符 * **格式**：JSON * **用途**：此步骤用于定义 EDI 数据的结构，包括指定 `SAC`、`N1` 和 `PO1` 等段，并详细说明每个段包含的字段。对于包含嵌套结构的段，会定义循环以妥善组织数据层级。 ```json { "SAC": {"fields": ["SAC", "DTM", "TX1", "TD5"]}, "N1": {"fields": ["N1", "N2", "N3", "N4", "PER"]}, "PO1": { "fields": ["PO1", "REF"], "loops": { "SAC": {"fields": ["SAC", "TX1", "DTM"]} } } } ``` #### 第 2 步：使用 XSLT 进行转换 * **格式**：XSLT * **用途**：此步骤用于将结构化 JSON 数据转换为结构化 XML 格式，并根据后续处理或集成的要求定制输出。此转换有助于提取确认类型、订单详情以及根据特定值确定的条件元素等精确信息。 ```xml

With detail, no change With detail and change Unknown ``` #### 第 3 步：预览（HTML 转换） * **格式**：XSLT（输出 HTML） * **用途**：将第 2 步生成的 XML 数据转换为 HTML 格式，以便以清晰且直观的方式预览转换后的数据。HTML 布局包含用于展示的样式，并将采购订单、供应商详情和订单条款等数据进行结构化，便于查看。 ```xml Preview of Transformed EDI Data

``` #### 第 4 步：提取路径 * **格式**：JSON * **用途**：指定用于从第 2 步生成的 XML 数据中提取关键值的 JSON 路径。这些路径用于检索采购订单和货币等特定数据点，这些数据对于后续处理以及集成到其他系统至关重要。 ```json { "fields": { "purchase_order": "//ORDER_CONFIRMATION/PURCHASE_ORDER/text()", "currency": "//ORDER_CONFIRMATION/CURRENCY/text()", ... }, "tables": [ { "name": "ORDER_CONFIRMATION_TABLE", "row_path": "//ORDER_CONFIRMATION/ORDER_LINES/ORDER_LINE", "columns": [ {"name": "POSITION", "path": "POSITION/text()"}, ... ] } ] } ``` 这一更新后的流程确保了完整的处理过程：使用 JSON 对原始 EDI 数据进行结构化，使用 XSLT 进行转换并生成 HTML 预览，随后通过 JSON 路径提取数据并进行集成，最终将其转换为结构化且可操作的信息。 --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.docbits.com/chinese/guan-li-yu-she-zhi/setup/document-types/edi-data-transformation-process.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.