202501 bt code 191 #422
Open
202501 bt code 191 #422
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
end_to_end_id auf alle sepa export items angewandt
... waren es auch nie wirklich (macht es nur komplizierter)
…kommt Ich hab exakt einen Mandanten gefunden, der folgende Transaktionscodes gespeichert hat: select distinct transaction_code from bank_transactions; transaction_code ------------------ 116 TRF 105 MSC 835 191 159 51 DDT 166 STO 303 117 SEC CHG CHK Der Code 191 befindet sich in 10 von 6800 Bankbewegungen, dennoch wird bei jeder Verbuchungsabfrage über alle offene SEPA Exporte iteriert, um diesen Fall auf Verdacht zu berechnen. Damit ist jetzt Schluss! Die aktuelle Bankbewegungen lassen sich sehr simpel mit einer Zeile vorher analysieren, ob sich die gesamte Aktion überhaupt lohnt.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Falls jmd. aus dem Hause ukd reviewen mag ...