BBP_BACKEND_DEST not maintained

[Former Member]

The table BBP_BACKEND_DEST is already maintained in SRM. But still I get the error - No customizing entry for LS-T10-200 in table BBP_BACKEND_DEST, when I am trying to use Document tracing on SRM portal. Any suggestion.

[pedro_santos6 · Accepted solution]

Hi,

Everything is below ok in the configuration:

SPRO >> SRM Server >> Technical Basic Settings >> it Defines Backend Systems

Are Backends marked like RFC? Is SRM marked as local?

Rgs,

Pedro Marques

[Former Member · Accepted solution]

Refer to this link:

http://help.sap.com/saphelp_tm70/helpdata/EN/4e/2a570d2a724c10bcd7a9313dbc351a/content.htm

Choose the system type depending on ur backend system i.e., ERP 3.0 or ERP 4.0 etc.,

Cheers,

AJ!

[Former Member]

Is this the same as mine??

[Former Member]

Hi there,

In case of ECC EHP 4.0 the use of PI is mandatory. However, on your

on risk and keeping in mind that this is kind of a modification, you

could change the backend sys-type in table BBP_BACKEND_DEST back to

ERP_3.0; a further option would be to create an implementation in

the BADI BBP_DRIVER_DETERMINE, to call a customer own driver during the

transfer of documents to the backend.

1) In case you run a EHP 4 in backend, you need to set system

type ERP_4.0 in table bbp_backend_dest, which requires the use

of PI.

2) As prerequisite for activitaing LOG_MM_P2PSE_1, you need to have

EhP 4 installed in your ECC system, also the following business

functions need to be activated:

ESOA_OPS01, LOG_ESOA_OPS_2 and LOG_MM_CI_2

(please also check the information and documentation about the BF

in your backend ECC system)

Hope this helps,

Kind Regards,

Matthew

[Former Member]

what exactly you are trying to in the portal?

are you creating shopping cart?

Muthu