Hello,
what about the table LFBK - vendor master (bank details)?
Greetings
Britta Heimann
what about the table LFBK - vendor master (bank details)?
Greetings
Britta Heimann
Reply: 16
Auto translated
Display vendor master data including IBAN as report
Hello
with the transaction SQVI I wanted to create a report, where I can then look at certain fields of company code data and also A segment data of vendors.
In this report I also wanted to display the IBAN, which is stored in the table TIBAN.
So a report which shows A segments B segments including IBAN data which are stored in TIBAN table.
The stupid thing is that in the table TIBAN, which is of course in the A segment, there is no reasonable link to the vendor number. I have tried everything, outer join inner join.... Nothing works anymore.
Does anyone have experience with this? Does anyone know a good self-made SE 38 report?
with the transaction SQVI I wanted to create a report, where I can then look at certain fields of company code data and also A segment data of vendors.
In this report I also wanted to display the IBAN, which is stored in the table TIBAN.
So a report which shows A segments B segments including IBAN data which are stored in TIBAN table.
The stupid thing is that in the table TIBAN, which is of course in the A segment, there is no reasonable link to the vendor number. I have tried everything, outer join inner join.... Nothing works anymore.
Does anyone have experience with this? Does anyone know a good self-made SE 38 report?
CommercialTRUST.EXCELLENCE.PEOPLEErfahren und agil. Nicht auf dem Sprung, sondern verlässlich an Ihrer Seite.!!
You must be logged in to post a reply.
16 Answers
- The LFBK does not contain the IBAN, therefore this is useless.... IBAN is completely independent in table TIBAN...
- Hello,
unfortunately I am not so familiar with Query.
With Microsoft Access I would create an additional field so that I convert the field Key of the origin table from TIBAN to the vendor. Here the vendor is 10 digits with leading zeros.
In the table LFA! or FLBK the vendor is 8 digits. I would update the new field with right(left(key...;10);8). This would make the JOIN identical and a link would be possible.
Greetings
Johannes - Hello
I had the same idea, even if it is awkward, it seems to be the only chance.
Nevertheless many thanks again - Hello,
under Demo FICO there is a video:
Quickviewer and Join with multiple tables.
Have a look at it.
mfg
Johannes - Wonderful. This fits perfectly !
Thank you very much ! - Hello
have it here now again represented.
http://fico-forum.de/demo/Query_join.php
If you look at the very end in the creditor 1002 and 1003 on the video you realize that these suppliers have a different account number with the same
same bank code, so same house bank, but in the additional field same IBAN comes up.
This is not ok .
So this SQVI is probably not ok.Last edited 21.08.12 10:15
- In the table TIBAN there is e.g. the field
TABNAME filled for vendors with LFBK
So you would have to create this list in XLS from SAP and then link the number from the LFBK in addition to the SQVI in the video.
The LFBK contains the number of the supplier.
e.g. 0001467804
This corresponds to what you said above. Seems to me to be the only chance. - Hello,
the topic is a little older, however I was also desperately looking for a systemic solution.
I have solved the problem as follows.
SQ02 - Create Infoset
For the join I used the tables LFB1, LFBK, BNKA (Swift-Code of the bank).
In addition, I then created an additional field IBAN, which receives the following coding:
CLEAR IBAN.
SELECT SINGLE IBAN FROM TIBAN INTO IBAN
WHERE TABKEY = LFA1-LIFNR.
Then simply create the Infoset as a query and the report is ready.
Best regards
Stanley - Perhaps a small addition to the method suggested by Stanley.
Another alternative is to insert table TIBAN as an additional table on the basis of the bank details (fields BANKS, BANKL, BANKN, BKONT of table LFBK or KNBK). A direct join is not possible here, because the field BANKN (bank account number) is defined in table LFBK as a char with 18 characters and in table TIBAN as char 35 characters and therefore a join is rejected with the error message "Illegal join condition". (see"Query via IBAN and master data Kred...n in SAP Query)".
Again, many ways lead to the result :-)
Many greetings
Andreas - Please think about S4/Hana Finance when you create it! There are some of these tables no longer! The IBAN's are then no longer in the TIBAN, but in the FCLM_BAM_AMD. And this applies to some other bank tables as well!
You will touch all this again in the foreseeable future.
Greetings
Alfred - Hello Alfred,
Thank you very much for pointing out the change in the context of S/4 Hana. If I read the OSS note 1976487 correctly, some adjustments of various evaluations are required here anyway.
I would add this note (with reference to this post) accordingly in the article.
Many thanks for this
Andreas - Hello Stanley,
I am doing this for the first time. I have managed the table links but where do you create the additional field IBAN with the code?
PS.: The system says I do not have authorization to maintain ABAP code. :-(
V.G.
Tiger Tiger:
Hello Stanley,
I am doing this for the first time. I have managed the table links but where do you create the additional field IBAN with the coding?
PS.: The system says I do not have authorization to maintain ABAP coding. :-(
V.G.
Tiger
Hi Tiger,
as far as I remember correctly query maintenance authorizations should be enough to insert an additional table in the Infoset.Quote:
Extension of the Infoset via additional table TIBAN
An additional table can now be inserted via the button Extras (F5) or via SPRINGEN-> ADDITIONS TO THE NODE within the transaction SQ02 (maintenance of the Infoset). For this purpose, the button Create can be selected in the tab Extras.
For this purpose, we enter the name TIBAN and as type of additional information Additional table. Now a query is made using SELECT SINGLE * FROM TIBAN WHERE ...
in which several conditions are to be fulfilled.
I have explained these for both Infosets in the following table.
Condition INFOSET IBAN-KREDITOR INFOSET IBAN-DEBITOR
Link conditions Additional table TIBAN WHERE BANKS = LFBK-BANKS KNBK-BANKS
AND BANKL= LFBK-BANKL KNBK-BANKL
AND BANKN= LFBK-BANKN KNBK-BANKN
AND BKONT= LFBK-BKONT KNBK-BKONT
For performance reasons, the field "buffer internally" can still be checked here, whereby this table is buffered and thus with frequent query of an IBAN the data can be found faster.The disadvantage, however, is the increased memory requirement, since a new internal table is created for the additional table.
It is important that the IBAN field from the TIBAN table is also included in a field group within the Infoset. In the query, this is available in the corresponding field group of the Infoset.
Do not forget to then assign the Infoset to a corresponding user group using the "Assignment to Roles/User Group" button, otherwise this Infoset cannot be used for a query.
This is described in more detail in the article"Query via IBAN and master data credit...n in SAP Query)".- Thank you Thank you
- A very small note about the fields TIBAN-TABNAME and TIBAN-TABKEY. These fields contain e.g. LFBK if the IBAN was created via transactions like FK02 or XK02.
However, once in the project, due to a change in the bank key logic in transaction OY17, we had to manually update the TIBAN table with transaction FIBAN. We then deleted IBANs and created new ones. After maintenance with transaction FIBAN, the IBAN was then assigned to the vendor again, but the fields TIBAN-TABNAME and TIBAN-TABKEY did not contain "LFBK" and the vendor number afterwards. I.e. the use of the fields TIBAN-TABNAME and TIBAN-TABKEY in analyses can show inaccuracies under certain circumstances.Last edited on 23.06.16 10:05
Matching learning content
Release: May 23, 2025
Practical Guide to SAP Payment Runs with SAP S/4HANA
David Taskiran
- Comprehensive guide to SAP Payment Runs in SAP S/4HANA
- Innovations in electronic payment processing and configuration (DMEEX)
- Optimizing payment workfl ows
- Latest updates in ISO 20022, SAP’s payment architecture
Release: Oct 29, 2020
A Practical Guide to Accounts Payable in SAP S/4HANA Fiori
Oona Flanagan
- Introduction to SAP S/4HANA and Fiori
- Organizational structure and master data
- Purchase-to-pay process, invoice and credit note posting, and the GR/IR reconciliation
- Payments and closing and reporting
Release: Aug 20, 2021
A Practical Guide to the General Ledger in SAP S/4HANA Fiori
Oona Flanagan
- Organizational structure and master data essentials
- General Ledger basics including document splitting and document types
- Key transactions from journal entries to intercompany postings
- Closing tasks and reporting