Error when signing on SRM portal

[Former Member]

Hi, i have this problem, when user signs on in the SRM portal (SRM 3.0) and the shopping cart page suppossed to appears (after enters user and pwd), the following error displays:

ITS System Information

Interpreter Failed

The Internet Transaction Server failed to generate the response for current request.

Please contact the system administrator.

Internal error code: 0x2101

In an already existent imlementation for badi BBP_DOC_CHECK_BADI i've added this code just to check some error messages from the document and if founded, add a custom message to the internal table

*----

-

---

• Data declaration

*----

-

---

• Variable

data:

lv_guid type CRMD_ORDERADM_H-GUID.

• Constants

constants:

lc_slash(1) type c value '/',

lc_015 type bbp_pds_messages-msgno value '015',

lc_000 type bbp_pds_messages-msgno value '000',

lc_fmavc type bbp_pds_messages-msgid value 'FMAVC',

lc_zebp type bbp_pds_messages-msgid value 'ZEBP'.

• Internal tables & Structures

data:

ls_messages type bbp_pds_messages,

lt_messages type table of bbp_pds_messages.

• First, check the SC

call function 'BBP_PD_SC_CHECK'

exporting

i_guid = lv_guid

TABLES

E_MESSAGES = lt_messages.

• Look for the right message

read table lt_messages into ls_messages with key msgid = lc_FMAVC

msgno = lc_015.

if sy-subrc = 0.

• Message founded, build custom message

• Add the message to table

read table it_account into wa_account index 1.

wa_error-msgty = 'E'.

wa_error-msgid = lc_zebp.

wa_error-msgno = lc_000.

concatenate wa_header-posting_date+0(4) " Year

lc_slash

wa_account-funds_ctr " Funds center

lc_slash

wa_account-fund " Fund

lc_slash

wa_account-func_area " Functional area

lc_slash

wa_account-cmmt_item " Commitment item

into wa_error-msgv1.

APPEND wa_error TO et_messages.

endif.

but in the call for 'BBP_PD_SC_CHECK' the systems generates a dump, if i comment the fm call, the page displays correctly, the parameters for fm are the right type.

The dump appears as follows:

Errores tiempo ejec. UNCAUGHT_EXCEPTION

Excepción CX_BBP_PD_ABORT

ocurrido el 26.12.2007 a 19:42:04

-

-

---

Es ist eine Ausnahme aufgetreten, die nicht abgefangen wurde.

-

-

---

¿Qué ha sucedido?

-

-

---

Die Ausnahme 'CX_BBP_PD_ABORT' wurde ausgelöst,

sie wurde aber entlang der Aufrufhierarchie nirgendwo abgefangen.

Da Ausnahmen Fehlersituationen darstellen und auf diesen Fehler nicht

adäquat reagiert wurde, mußte das laufende ABAP-Programm 'SAPLBBP_PDH'

abgebrochen werden.

-

-

---

¿Qué puede hacer?

-

-

---

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

is especially useful if you want to keep a particular message.

-

-

---

Anál.errores

-

-

---

Es ist eine Ausnahme aufgetreten, die weiter unten näher erläutert wird.

Die Ausnahme, der die Klasse 'CX_BBP_PD_ABORT' zugeordnet ist,

wurde nicht abgefangen und führte deshalb zu einem Laufzeitfehler.

Der Grund für die Ausnahme ist:

Übernehmen

-

-

---

Notas para corregir errores

-

-

---

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-

-

---

"UNCAUGHT_EXCEPTION" CX_BBP_PD_ABORTC

"SAPLBBP_PDH" or "LBBP_PDHU08"

"BBP_PD_ABORT"

-

-

---

-

-

---

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.

-

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

and select the "Print" function to print out the relevant

part.

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, you can either use the "PRINT" command in the editor or

print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

-

-

---

Entorno sistema

-

-

---

SAP-Release.............. "620"

Applikationsserver....... "ebpqas"

Netzwerkadresse.......... "144.127.70.32"

Betriebssystem........... "SunOS"

Release.................. "5.9"

Hardwaretyp.............. "sun4u"

Zeichen-Länge............ 8 Bits

Pointer-Länge............ 64 Bits

Workprozess-Nummer....... 0

Kurzdump-Einstellung..... "full"

Datenbankserver.......... "ebpqas"

Datenbanktyp............. "ORACLE"

Datenbankname............ "EBQ"

Datenbank-User-Id........ "SAPEBP"

Zeichensatz.............. "es"

SAP-Kernel............... "640"

hergestellt am........... "Jul 4 2005 21:14:29"

hergestellt auf.......... "SunOS 5.8 Generic_108528-16 sun4u"

Datenbankversion......... "OCI_920 "

Patch-Level.............. "80"

Patch-Text " "

Unterstützte Umgebung....

Datenbank ............... "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE

10.2.0.."

SAP-Datenbankversion..... "640"

Betriebssystem........... "SunOS 5.8, SunOS 5.9, SunOS 5.10"

-

-

---

Usuario, transacción....

-

-

---

Mandant............. 010

Benutzer............ "CRARIABR"

Sprachenschlüssel... "S"

Transaktion......... "BBPSC02 "

Programm............ "SAPLBBP_PDH"

Dynpro.............. "SAPLBBP_SC_UI_ITS 2000"

Dynprozeile......... 4

-

-

---

Info posición de cancelación

-

-

---

Der Abbruch trat im ABAP-Programm "SAPLBBP_PDH" auf, und zwar in

"BBP_PD_ABORT". Das Hauptprogramm war "SAPLBBP_SC_UI_ITS ".

Im Quelltext befindet sich die Abbruchstelle in Zeile 67

des (Include-)Programms "LBBP_PDHU08".

(bei Anwahl des Editors: 670) der ABAP-Source "LBBP_PDHU08".

-

-

---

Detalle código fuente

-

-

---

000370 LS_CALLSTACK1-EVENTNAME LS_CALLSTACK1-PROGNAME

000380 INTO LV_MSGARG2 SEPARATED BY SPACE.

000390

000400 READ TABLE LT_CALLSTACK INTO LS_CALLSTACK2 INDEX 4.

000410 CONCATENATE '/' LS_CALLSTACK2-EVENTTYPE

000420 LS_CALLSTACK2-EVENTNAME LS_CALLSTACK2-PROGNAME

000430 INTO LV_MSGARG3 SEPARATED BY SPACE.

000440

000450 CALL FUNCTION 'BBP_ALERT_INTERNAL_OT'

000460 EXPORTING

000470 MSGID = GC_MSGID_BBP_PD

000480 MSGNO = 047

000490 MSGARG1 = LV_MSGARG1

000500 MSGARG2 = LV_MSGARG2

000510 MSGARG3 = LV_MSGARG3.

000520

000530 MESSAGE ID GC_MSGID_BBP_PD TYPE C_MSGTY_I NUMBER IV_MSG_NO

000540 WITH LS_CALLSTACK1-EVENTTYPE

000550 LS_CALLSTACK1-EVENTNAME

000560 LS_CALLSTACK1-PROGNAME.

000570

000580 * get the messages from the application log

000590 TRY.

000600 CALL FUNCTION 'BBP_PD_LOG_GET_MESSAGES'

000610 TABLES

000620 E_MESSAGES = LT_MESSAGES.

000630 CATCH CX_BBP_PD_ABORT.

000640 REFRESH LT_MESSAGES.

000650 ENDTRY.

000660

-

-

---

RAISE EXCEPTION TYPE CX_BBP_PD_ABORT EXPORTING

000680 WORKED_ON_DOCUMENT = LV_GUID

000690 T100_MSGID = GC_MSGID_BBP_PD

000700 T100_MSGNO = IV_MSG_NO

000710 T_APPL_LOG_MESSAGES = LT_MESSAGES.

000720

000730 ENDFUNCTION.

Thanks in advance for your help.

[Former Member · Accepted solution]

Hi

It seems some mandatory System configuration settings are missing.

For time-being, please Try de-activating the active customer implementations of the BADIs BBPDOC_CHANGE / BBP_DOC_CHECK_BADIs and then try again the Shop process._

Please try to look into RZ20, ST22, RZ10, and SLG1 transactions for any error logs generated.

Also, Please Check the SAP OSS Notes ->

Note 673372 - Short dumps UNCAUGHTEXCEPTION in SRM 3.0, 4.0, and 5.0_

Note 833442 Data inconsistency due to termination when you save

Note 851825 Copying a reference without ship-to address ==> error

Note 847427 Error when you copy template without ship-to address

Note 746569 CX_BBP_PD_ABORT in routine CHECK_CF_QUANTITY

Note 651994 PO with several hierarchy levels causes termination

Hope this will definitely help. Do let me know.

Regards

- Atul

[Former Member · Accepted solution]

Thanks, i'm checking the notes, due to conection limit in customer facilities can't response as fast as i wish. I'll let you know the solution soon, i hope.

Thanks to all.

[ravindra_mantri2]

Hi Guillermo,

It seems that SU01 user id does not have any business partner created in SRM system.

Use USERS_GEN t-code for the same and then try loggin in in SRM portal.

rgds,

Ravi

Pl reward points for useful answers.

[Former Member]

Ravi, the user have among others the following:

role

SAP_BBP_MULTI_ADMINISTRATOR

SAP_EC_BBP_ADMINISTRATOR

SAP_EC_BBP_CONTENT_MANAGER

SAP_EC_BBP_EMPLOYEE

authorization profile

T-ED310120

T_AC980036

T_AC980037

T_AC980051

I've repaired the user using transaction USERS_GEN, but the error is still being generated. If user doesn't have any business partner, why at calling this function generates the error and without the call the user seems to be all right?

Thanks in advance.