10-17-2018 3:44 AM - edited 02-03-2024 10:55 PM
Hi Community,
We are currently searching for a way to retreive the Business Partner number based on his Previous Account Number and/or his Personnal Number.
In our interfaces, the distant system won't send us the internal number of the BP but the number in the distant system which we will store in those fields during our Data Migration Run.
On a BP, for Partner Role "Supplier (Fin.Accounting)" (FLVN00), in Company Code view, in "Vendor: Account Management", we have the block "Reference Data" with both fields
We didn't found them in the Business Partner API, so we wanted to create a custom CDS view exposed ni oData but we couldn't find any standard CDS which are exposing these fields that could allow us to create it.
Is there any way to do the link between those fields and the BP ?
Kind Regards,
Romain
Hi Romain
Unfortunately, I'm not sure if this field exists on any API or CDS view. I set up a test scenario in an internal sandbox and checked every field / navigation entity for the field and couldn't find it.
I see other fields from this screen (like Reconciliation Account) under A_SupplierCompany node. There is a CDS view I_SupplierCompany but here again no external/previous id fields nor personnel number.
I think you could check with SAP Support to see if they know of a CDS view. I would start with component LO-MD-BP
Thanks,
Marty
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Marty,
Thanks for the answer and the time you took to look it up. I see that we arrived at the same conclusion, it seems it should be in I_SupplierCompany but we do not see it.
I followed your advise and send a ticket to SAP Support. I'll let you know of their answers and update this post.
Regards,
Romain
Hi Romain, how about using field BusinessPartnerIDByExtSystem in API https://api.sap.com/api/API_BUSINESS_PARTNER instead of the one you were asking for? To me, it looks like that field may fulfill your business need. The documentation of this field reads: "BusinessPartnerIDByExtSystem. Business partner number from an external system or a legacy system." You'll find it in structure A_BusinessPartner.
Wouldn't that work for you?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andreas,
Thanks for pointing out this field, I do find it in the API as you mentionned and is very promising but I see 2 shortcomings with this solution.
Firstly, a minor one, although we do find the field in the webGUI Tile, we do not find it inside the Fiori Tile (did I missed it?).
Secondly, and that's a major one for us, we were unable to find it in the Data Migration Cockpit for BP. Again we might have missed it but we will do our migration of existing BP using this tool so we need to be able to fill this field using this tool.
Please let me know if I missed something or if there is a way to add the field in the Migration cockpit.
Regards,
Romain
Romain, we may have found a solution for keeping migration and integration requirements in synch. In migration or inbound data replication API https://api.sap.com/api/BUSINESSPARTNERSUITEBULKREPLIC use field “ExternalID”. In OData API API_BUSINESS_PARTNER, use field “BusinessPartnerIDByExtSystem”. It is the same field on the S/4HANA database, unfortunately made known by different names in different APIs.
Hi Andreas,
Sorry I saw only now your reply to my last message. We did used this field for our first roll-out but we did a mass change to charge them.
Also we found another problem for us in the usage of this field, it is linked to the BP but not to the company code. Which means that multiple company can't have different ExternalID.
This should be corrected by SAP in 1902 as the Previous Account Number should be part of the BP API.
Regards,
Romain
User | Count |
---|---|
88 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.