on 05-31-2010 3:11 PM
During cretion of PO in SRM system we are encountering the following situation:
Prior to that we have configured all the initial settings as below:
"Defining System landscape" on SRM side,(which updates the table BBP_BACKEND_DEST) we have defined it as type ERP_4.0 as we currently have an EhP4 backend .
We are getting the error msg: No customizing entry for "SRICLNT801' in table BBP_BACKEND_DEST when I try to create a PO in SRM Portal.
The following entries in BBP_BACKEND_DEST Table (this table is updated when Defining the System Landscape config) looks as below.
For Backend ECC Clnt - 801, Log System - ERICLNT801, RFC Destn - ERICLNT801 , RFC Dialog - ERICLNT801_DIALOG, Sys type -ERP_4.0
For SRM local clnt - 801, Log System - SRICLNT801, RFC Destn - SRICLNT801 , RFC Dialog - SRICLNT801, Sys type -LOCAL
Any clue on this ?? Its been a while now and i have no idea why is this occuring??
Dear Matthew,
We are indeed using ECC EHP 4.0. Are you sure the use of PI is mandatory..??
If yes, can u brief me wats the use of that if we are not using SUS??
However we are not using SUS.
Also i had earlier changed it to ERP_3.0 and tested, but the same error prevails.
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.
Kind Regards,
Aj!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also the entry for our SRM ssytem is
CLIENT 300
LOG SYS E7UCLNT300
DEST E7UCLNT300
SYS TYPE LOCAL
RFC POSS
LOC SYS X
FI VALIDATION 0
CI CONNECTED
SLD SYS NAME E7U_300
DEST DIALOG E7UCLNT300
ASSIGNED PARTNER
BS CONNECTED X
ES CONNECTED
SYSTEM ALIAS SAP_SRM
LOG DESCRIPTION GLOBAL PROCUREMENT
Please note that you can only have one entry in this table of SYS TYPE LOCAL and LOC SYS X.
This must be the SRM system.
The system asumes that there will only be one entry and that this entry will be the SRM system so looks down through the table and picks the first one as the SRM system.
Hope this helps,
Kind Regards,
Matthew
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there,
Not sure if this will help but this is an entry in our BBP_BACKEDN_DEST table connecting to an ERP 4.0 system.
CLIENT 300
LOG SYS F2TCLNT700
DEST F2TCLNT700
SYS TYPE ERP_4.0
RFC POSS X
LOC SYS
FI VALIDATION 0
CI CONNECTED
SLD SYS NAME F2T_700
DEST DIALOG F2TCLNT700_DIA
ASSIGNED PARTNER
BS CONNECTED
ES CONNECTED
SYSTEM ALIAS
LOG DESCRIPTION IPD (F2TCLNT700)
Hope this helps,
Kind Regards,
Matthew
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there,
I had a further look at our database. Please see the following information.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.