Vendor Contact Business-Address (Assign Street/City/St/Zip to Contact)

Question

I cannot load business-addresses for Vendor Contacts, can some please help?
Have successfuly loaded Vendor and its Contacts (via LSMW) and even created addresses (ADRC recs via BAPI) but cannot link that address to the contact and it seems like it should be so easy after getting this far.
For example, note the two tables KNVK (Contacts) and ADRC below - I created a Contact manually (XK02) and Address (BAPI_ADDRESSORG_SAVEREPLICA)
but note field KNVK-ADRND is blank. This is the link to the address rec and if I could only find a function to connect the two. In Dev I "slammed" the ADRC-ADDRNUMBER directly into KNVK-ADRND via UPDATE and it all works! The Contacts Business-Address shows up in the Vendor tcodes XK01-3 (Contacts scrn) but I can't get away with that in Prod - or can I - it's tempting?
Table: KNVK
PARNR        NAMEV         ADRND      PRSNR
0000023245 TEST1                             0000023914
Table: ADRC
ADDRNUMBER STREET                      ADDR_GROU
0000023916       E2190 STREET           BP
Have tired (painstakingly) these functions:
BAPI_ADDRESSORG_CHANGE() - am able to change an existing contact business-address, but not create it.
BAPI_ADDRESSORG_SAVEREPLICA() - am able to create an address, ADRC rec, but not link it to the contact.
BAPI_ADDRCONTPART_SAVEREPLICA() - does NOT support Street/City/St/Zip
BAPI_ADDRESSCONTPART_CHANGE() - does NOT support Street/City/St/Zip
ADDR_SINGLE_SAVE() - wont run cuz all vars are not setup deep inside.
ADDR_PERSON_REFERENCE_INSERT() - does not like something.
BUPA_OUTBOUND_ADDR1_SAVE() - struggling with params.
Any ideas - thank you?

Answer 1

Since the Vendor LSMW has no provisions to load contact addresses I wrote a separate report that used the same vendor load-data. In other words, this is a separate step after the LSMW is complete.
To update the contact address I used a simple BDC for tcode MAP2 (edit-contacts). (Too many SAP ADDRESS functions to deal with and the BDC was only a few lines and very clear.)
Note, tcode MAP2 uses PARNR to identify the specific contact in question. I had to first retrieve the PARNR for the contact created during the vendor load (LSMW) by their partner-function (PAFKT - this is easy) but also using their name (NAMEV & NAME1 which is hazy) since we had duplicates. ie same person same partner-function but with some other differences. In these cases, I just listed a msg on the output rpt that these could not be identified due to multiples.
However, once you know the specific PARNR, the BDC is a breeze.