At the level of user organizations, the new e-TRAM greatly simplifies management: it allows self-management of the catalog of procedures and, above all, it streamlines management, since the procedures (with all their attachments) will be found by default in the entity's own registration tray, once the MUX DOWNLOAD is activated (according to the settings of your registration provider).
In any case, and if it is not there, you will also find all the documents attached to your organization's registration on the EACAT platform to consult it, and if necessary to download it and manually incorporate it into your entry record. More information in How the registration application works.
More services to control incidents. From the EACAT record to a dynamic CSV:
Although e-TRAM 2.0 is a more robust solution than its predecessor and also presents a better error communication policy, it is not infallible, so errors can occasionally be generated in the processing that must be identified.
In this sense, you may occasionally have some doubt in your registration due to some entry that does not have attachments. The first checkpoint we offer is the EACAT registration. As we mentioned previously, automatically if the processing has been carried out effectively, you will find the registration note and the attachments (which you can download). This may be interesting if your integration with MUX download is giving you problems as an alternative download point (while waiting for your provider to resolve the incident).
At the same time, we also provide a second tool: a URL where you will find a CSV published with all the procedures correctly entered into the solution in the organizations in the last 30 days: https://dadesobertes.seu-e.cat/csv/registres_valids_etram2.csv
Specifically, this CSV has all the procedures of the last 30 calendar days for all entities, with records updated 5 times a day (9am, 11am, 1pm, 3pm, and 5pm). It includes the following fields:
- Date of procedure, time of procedure, registration number, entity code .
To make the query, you will have to search based on the entity code (10-digit Municat code, also known as INE10), remembering that the list only includes those procedures that have been entered correctly into the platform.
Possible results:
- You have an entry in the registry (e-TRAM 2.0 procedure). You have not received the attached documentation and confirm that it does NOT appear in the list (CSV)
If you have an entry in your record (and therefore a record number) that does NOT appear in the CSV list, this is a procedure that was not created correctly , and therefore implies a processing error that you must be aware of.
- The main reason for this error is based on the process of obtaining the registration number. If the return by the organization plus the processing MUX takes a long time, an error is generated in the processing , and therefore despite the registration number , the procedure formally did not occur.
- In these cases, on the last screen of the e-TRAM 2.0 processing (citizenship part), an error message appears: “ an error has occurred while performing the entry” , and it is specified that the procedure must be tried again after a few moments.
- You have an entry in the registry (e-TRAM 2.0 procedure). You have not received the attached documentation and confirm that it does appear in the list (CSV)
If you have an entry in your registry (and therefore a registration number) that DOES appear in the CSV list, this is a procedure that has been created correctly , but is pending for your registry solution to "pull" the attached documentation through the MUX download.
In this case, you must first contact your registry provider to optimize the MUX download process. In this sense, you may have very high frequencies of predetermined times, or some specific error that does not allow you to have the documents (application, attachments, etc.) in your registry. In this sense, remember that it may also happen that the certificate associated with your file solution has expired and does not allow you to “pull” the documentation (via MUX_DESCARREGA).
If your provider's response does not resolve the problem, you can contact us through the support portal and provide us with more details so that we can analyze if there is any problem with the documentation download. Specifically, you will need to communicate to us the requests (and if possible responses) that your provider has made, including the identifiers of the MUX Download requests, so that we can perform the appropriate checks.
IMPORTANT: If you find yourself in this second case (and, therefore, the procedure has been generated correctly and you have seen it in the CSV), remember that until your provider resolves the incident, you can go to the EACAT registry and dispose of it manually. It is not the best option, but it will allow you to have all the information about the procedure immediately while the provider resolves the incident.
To do this, you must go to “REGISTER”, select e-TRAM and your organization's data will appear.
Select the procedure and you will be able to download the related documentation.