Mapping with backend

[Former Member]

Hi,

Can any one send me the details on tcode "BBP_UPDATE_MAPPING".

So can u explain , what inputs we have to gve to different scenarios.

Regards,

RAghu.

[Former Member · Accepted solution]

Hi Raghu,

Let me explain to you the transaction precisely:

The Transaction has two screens, one on the top and the other at the bottom:

<b>Top Screen: Adjust Backend Reference:</b>

In multiple back-end scenarios, transaction BBP_UPDATE_MAPPING can be very useful because vendors that once have been replicated do not need to be replicated again from other back ends if their numbers are equal (top area). This transaction essentially will adjust those different numbers as one single number in the SRM system.

Example: You have 4 backends A, B, C and D and Vendor "Circuit City" has numbers as follows:

A- 100

B - 200

C - 300

D - 400

Now that you have already replicated circuit city from A (100) -> SRM, you dont want to overlap the same vendor with different vendor numbers. So, this transaction in the top area gives the ability to adjust the mapping of the local (SRM) vendor number to other vendor numbers in other backends.

The input parameter on the top area will be the logical system of the corresponsing backedn system for which you wish to perform an adjustment. Once you do this, SRM vendor number will have one to many mapping created. (i.e. Vendor Number 100 in SRM is same as Vendor Number 100, 200, 300 and 400 in backend A, B, C and D)

<b>Add/Delete/Change Backend (Bottom Area)</b>

The Bottom Area assists if a back-end has been replaced (for example, from test to productive), this can be switched very easily from this transaction (bottom area). In this area you can add, delete and change backends.

Hope this info helps !!

Pls assign points for usefull answers !!

Sundeep

[Former Member]

Hi

<b>Transaction BBP_UPDATE_MAPPING</b>

Using the transaction BBP_UPDATE_MAPPING, Vendor Mapping - Adjust Backend, you can map backend vendors to business partners in SAP Supplier Relationship Management (SRM), even if you have a heterogeneous landscape in which the different backend systems may have, for example, different numbers for the same vendor. Alternatively, you can use this transaction when changing from a test or development system to a productive system to ensure that there is no discrepancy between the two systems.

<b>Related link -></b>

http://help.sap.com/saphelp_srm50/helpdata/en/bb/6c0e3b02616a42e10000000a11402f/frameset.htm

<u>Please provide the SRM system version details in next reply, meanwhile please go through the following SAP OSS Notes -></u>

Note 842673 Unable to start BBP_UPDATE_MAPPING

Note 752958 Parameter missing during call of B*VENDOR_GET_DATA driver

Note 606441 Relationship address of contact person (ext. bus.partner)

Note 460385 'Dun & Bradstreet' number for 'update mapping'

Note 361829 EBP (BBP2.0C): Business partner <-> vendor mapping

Note 357201 BBP 2.0B: Business partner <--> vendor mapping

Hope this will help. Do let me know.

Regards

- Atul