> 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/configuracion.md). # Editran/SEPA configuration There are several Editran/SEPA parameters that can be configured, and this can be done in two ways: * Through the file `conf/Configuracion.properties`. * As Java virtual machine parameters. Example: ``` java –Dparam.lenguaje=A -cp "lib/*;lib/Win/*" com.indra.mmdd.editran.main.EDItranSepaXmlMain [Parameters] ``` The names of the different parameters that can be configured are: * **`param.lenguaje`** (Machine language): It can be `A` (ASCII) or `E` (EBCDIC). By default the Editran/SEPA converter determines it automatically. * **`param.alfabeto`** (Alphabet): This is the alphabet in which the plain file of the conversion is written or will be written. The possible values are those charsets allowed by Java (for example for Java 1.6 the allowed encodings are listed on its website). By default it uses the alphabet of the machine where it runs. * **`param.validar.xml`** (Validate XML): Used to indicate whether the XML should be validated against its schema, with possible values: * `S` (Always validated) * `P` (validated only in XML to Flat conversions) * `X` (validated only from Flat to XML) * `N` (Never validated) The default value is `S`. > **Attention:** disabling this validation, the resulting files could contain errors. * **`param.info.libre`** (Information in free fields): This parameter allows preserving certain information that would otherwise be lost after conversions, given the asymmetry between the standards of each format. The transferred information (see chapter [8 Use of the free zone of the records](#8-uso-de-la-zona-libre-de-los-registros)) is read from (flat to XML) or written to (XML to flat) free zones of the records in the flat format. It should be indicated `S` (Yes) to read/write or `N` (No) not to do so, the latter being the default value. * **`param.mantener.salida`** (Keep output file in case of error): In a conversion resulting in error the output file is deleted, since its form or content could be incorrect. This field allows modifying that behavior and keeping it in any case. The possible values are `S` to keep it and `N` to delete it, this being the default value. > **Attention:** In the integration with Editran, special care must be taken so that no incorrect output files remain in the Editran sending folder, since they would be transmitted. It is therefore advised not to activate this parameter except to debug an error in a file, remembering that afterward it must be removed from that directory. * **`param.resp.auto.nifpres`** (Automatic response message with the presenter NIF at the beginning of ``): The use of this parameter allows generating automatic response messages, according to `pain.002.001.03`, in XML to flat conversions, both for Debit Presentations files and Transfer Initiation files. The value of `` is composed of the Presenter NIF followed by the original message identifier. The code returned in `` indicates whether the conversion could be carried out (`ACTC`), or not (`RJCT`). The value of this parameter will be the full path of the response file. By writing at the beginning `param.fichero.entrada` the Converter will apply instead the input file name without the extension `.xml`, if it has one. For example, if the input file is `C:/fichero.xml` and we write `param.resp.auto=param.fichero.entrada.conf.xml`, the obtained response file will be `C:/fichero.conf.xml`. By default this file is not created. With this parameter enabled the following is ignored (`param.resp.auto`). * **`param.resp.auto`** (Automatic response message): The use of this parameter allows generating automatic response messages, according to `pain.002.001.03`, in XML to flat conversions, both for Debit Presentation files and Transfer Initiation files. The code returned in `` indicates whether the conversion could be carried out (`ACTC`), or not (`RJCT`). The value of this parameter will be the full path of the response file. By writing at the beginning `param.fichero.entrada` the Converter will apply instead the input file name without the extension `.xml`, if it has one. For example, if the input file is `C:/fichero.xml` and we write `param.resp.auto=param.fichero.entrada.conf.xml`, the obtained response file will be `C:/fichero.conf.xml`. By default this file is not created. If the previous parameter (`param.resp.auto.nifpres`) is enabled, this one is ignored. * **`param.quitar.validaciones`** (Remove validations): This parameter is used to bypass the validations of the XML standard usage rules imposed by SEPA Spain (these are restrictions and indications that are not included in the XSD schemas but in the published documents). The possible values are `S` to not validate and `N` to check compliance, the latter being its default value. To activate this parameter it is necessary to have a specific license. * **`param.juntar.xml`** (Join XML): This parameter allows defining the behavior of the converter in transformations of input files in flat format that include more than one logical file. There are two possibilities: * a) Whenever possible (they match in everything: creation date, ordering party/creditor identification, etc.), unify all the information from each input logical file into a single logical and physical XML output file. For this option the value `S`. * b) Obtain an output file with as many logical XML documents as logical flat-format files the original has. For this option the value `N`. The default value is `S`. > **Attention:** is indicated `N` to configure the parameter with value [it is essential to have the corresponding license (see section](#9-separador-ficheros-planos-y-xml) 9 Separator flat and XML files * **`param.cabecera`** (Transmission header): For XML to flat conversions of standard 34-14, this parameter indicates whether an additional header should be included at the beginning of the resulting file. The possible values of the parameter are: * `T` to write the header of the General Treasury of Social Security (see section [10 Adaptation for Telematic Payments of the TGSS](#10-adaptación-para-pagos-telemáticos-de-la-tgss) of this manual) * `N` to not do so, this being the default value. When this parameter has the value `T`, the converter ignores the parameter `param.resp.auto` for XML 34-14 files. *** --- # 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/configuracion.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.