### Description of the bug: Das Metadatenschema von FIT-Connect schreibt für das Geschäftszeichen vor, dass der String kleiner oder gleich 10 Zeichen sein darf. Die Schnittstellenbeschreibung von Elster-Transfer erlaubt bis zu 60 Zeichen. ### Current behavior: Die Definition und Dokumentation des Metadatenschemas begrenzt die Anzahl der Zeichen für das Geschäftszeichen auf maximal 10 Zeichen. ### Expected behavior: Die Schnittstellenbeschreibung von Elster-Transfer erlaubt eine maximale Länge des Geschäftszeichens von 60 Zeichen. {width=900 height=140} **Es werden neue Metadatenversionen 1.6.0 und 2.1.0 bereitgestellt.** SSP und SDKs müssen diese zulassen. ### Environments: DEV, TEST, STAGE, PROD ### Additional Information: Schnittstellenbeschreibung Elster-Transfer 25.07 vom 12.08.2025 [Schnittstellen_von_ELSTER-Transfer_-_ETR_25.07.pdf](/uploads/f83ed98ecb2ac7cd210dd768cf8a32d0/Schnittstellen_von_ELSTER-Transfer_-_ETR_25.07.pdf) ### Dependency / relationship to other issues: <!-- Write down here what kind of relationship it is and a brief explanation of it. --> ### Responsible person / team: <!-- Insert here the name of the person or team responsible for processing the bug. --> ## Transfer history to different teams <!-- Stories are sometimes assigned to different teams for processing. In this context, it has been found that a history of why the ticket was assigned to a particular team can be very helpful. --> ### Contact persons including contact details: <!-- Indication of contact persons such as the person who reported the error, how to reach them. --> ### Screenshots / Logs / Requests: <!-- Insert screenshots or other (visual) aids here if necessary to clarify the bug. --> ### Checklist: - [ ] Add Severity label - [ ] Add team label - [ ] Related/affected issues/stories/epics linked and explained in the bug issue - [ ] Creation of an automated test - [ ] Bugfix deployed on DEV - [ ] Bugfix tested on DEV - [ ] Bugfix deployed on TEST - [ ] Bugfix tested on TEST (possibly also by the connection project itself) - [ ] Successful fix reported to Team Operations (Teams channel) - [ ] Bugfix deployed on STAGE - [ ] Bugfix tested on STAGE if necessary - [ ] Bugfix deployed on PROD - [ ] Bugfix tested on PROD (possibly also by the connection project itself) - [ ] Final communication by Team Operations if necessary - [ ] Internal documentation was checked and updated if necessary - [ ] External documentation has been checked and updated if necessary - [ ] Updated changelog if necessary ### Approach/Solution: <!-- Other comments or notes can be added here, e.g. what has been tried so far to solve the problem. --> ### Release version of the artifact: