> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/documentacion-editran-editran-sepa-v3-open-en/modo-de-uso/integracion/uso-en-transmisiones-de-emision.md).

# Use in outbound transmissions

When the SEPA converter is used together with Editran, in addition to implementing the processes before sending and after receiving as described in the previous sections, the Editran/G profile of the sending files must also be configured appropriately. The configuration differs depending on the type of file obtained with the conversion. The procedure to follow in each case is detailed below.

* **XML → flat**: if the initial file is XML, when passing through the SEPA converter a flat-format file is obtained, which is the one that will be sent. Therefore, "Fixed" will be defined in the "File format" field, 600 as record length and no delimiter. The alphabet will be ASCII. ASCII/EBCDIC translation will be necessary if the remote side wants to receive the flat file in EBCDIC format.

![Photo](https://620397458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYRsCBWELAyzw5mj5JFUW%2Fuploads%2Fgit-blob-e37ea27385ff1e7b42434d9a921ab7b21ad3f96d%2Fimage.avif?alt=media)

Unix configuration example:

![Photo](https://620397458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYRsCBWELAyzw5mj5JFUW%2Fuploads%2Fgit-blob-60e0fea8a04b8b2b3744071bac82aa2584965362%2Fimage.avif2.avif?alt=media)

* **Flat → XML**: if the initial file is flat, when passing through the SEPA converter an XML file is obtained that must necessarily be encoded in UTF-8. So this type of file will be sent in binary format, with alphabet and delimiter "NONE".

Windows configuration example:

![Photo](https://620397458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYRsCBWELAyzw5mj5JFUW%2Fuploads%2Fgit-blob-98b6b1ea003eb2bafaee1d70ec97252d00c237d6%2Fimage.avif3.avif?alt=media)

Unix configuration example:

![Photo](https://620397458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYRsCBWELAyzw5mj5JFUW%2Fuploads%2Fgit-blob-f613f5bcf694f31155d22bbb83e7d6d007090186%2Fimage.avif4.avif?alt=media)

It is possible to send files of both types, flat and XML, through the same Editran presentation. To do this, it will be enough to define, from Files in the G Menu, the two types of sending files as described.

In the following Editran Windows example, different folders are used to store the two types of files that will be converted and subsequently sent. All documents found in the "flat" directory will be transformed to XML and sent in binary. For their part, all those in the "XML" directory will be transformed to flat and then sent in fixed format with length 600, without delimiter and in ASCII language.

Windows configuration example:

![Photo](https://620397458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYRsCBWELAyzw5mj5JFUW%2Fuploads%2Fgit-blob-8b62b58d103595def3c2a57dc8a1fc93148d4917%2Fimage.avif5.avif?alt=media)

Unix configuration example: ![Foto](https://620397458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYRsCBWELAyzw5mj5JFUW%2Fuploads%2Fgit-blob-d6b28777175e9c03cdddee1b27f5454950763eec%2Fimage.avif6.avif?alt=media)


---

# 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.editran.onesait.com/documentacion-editran/documentacion-editran-editran-sepa-v3-open-en/modo-de-uso/integracion/uso-en-transmisiones-de-emision.md?ask=<question>&goal=<user_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.