Confirm Goods / Services Centrally - BBPCF03

[Former Member]

Hi guys!

We are using SRM5.0 and have the following error:

Start Confirm Goods / Services Centrally - BBPCF03. No matter what we select, the system will dump and bring the following error <i><b>Type conflict during structure parameter transfer at CALL FUNCTION</b></i>

We believe it is a SAP programm error but probably you have another idea?

Thanks for your help.

Regards,

Corinne

[Former Member · Accepted solution]

Hi

Any updates.

Regards

-Atul

[Former Member]

We actually found out ourselves that the problem had something to do with the implementation of SAP-note 488619. And yes, it had to do with internal structures.

Regards,

Corinne

[Former Member]

Hi

<b>I think this is standard SAP Error.</b>

Please go through the following OSS Notes.

Note 691300 - Transfer of BE_ITEM_SRV to BADI BBP_WF_LIST
Note 674819 - Error when creating goods receipt/confirmation
Note 885937 - BADI for XML based PurchaseOrderConfirmation throws except.
Note 925480 - Short dump in history of a purchase order
Note 680676 - 'CALL_FUNCTION_UC_STRUCT' dump after confirmation
Note 970527 - Problems with bbpcf01 IT Service
Note 940418 - EBP XML inbound error for OrderResponse/POConfirmation
Note 1009132 - SRM: Error message ITS_TEMPLATE_NOT_FOUND
Note 951021 - BBPCF02 : Interpreter error occurs when return GR

Hope this will help.

Please reward suitable points.

Regards

- Atul

[Former Member]

Hi

Please paste the details here of the short dump in details, by logging to ST22 transaction.

Regards

- Atul

[Former Member]

Hi Atul

Here is the detailed information.

Runtime Errors CALL_FUNCTION_UC_STRUCT

Exception CX_SY_DYN_CALL_ILLEGAL_TYPE

Date and Time 08.02.2007 15:55:51

Short text

Type conflict during structure parameter transfer at CALL FUNCTION.

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLBBP_PDH_LISTSEL" had to be terminated because it

has

come across a statement that unfortunately cannot be executed.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was

not caught in

procedure "BBP_PO_LISTSEL" "(FUNCTION)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

In the function "BBP_PO_LIST_BE_MAP_PD", the STRUCTURE parameter "I_BE_ITEMS"

is typed in such a way

that only actual parameters are allowed, which are compatible in Unicode

with respect to the fragment view. However, the specified actual

parameter "LT_BE_ITEM" has an incompatible fragment view.

Thanks for any help.

Regards,

Corinne

[yann_bouillut]

Hi,

Maybe it is a plug-in issue.

What plug-in release did you install ?

Kind regards,

Yann

[Former Member]

Hi Yann

Where can I see this plug-in release? Which plug-in?

Thanks for your help.

Regards,

Corinne

[yann_bouillut]

Hi Corinne,

In your backend, go to transaction SPAM to display the patch level of your ECC components and especially look at plug-in one.

For instance in my ECC 60 system , the Pi version is 2005_1_700

Kind regards,

Yann

[Former Member]

Hi Yann

I am not allowed to run SPAM, but I found the following under System - Status in the backendsystem:

PI 2004_1_470 0011 SAPKIPZI5B R/3 Plug-In (PI) 2004.1 for R/3 Enterpri

PI_BASIS 2005_1_620 0007 SAPKIPYJ57 PI_BASIS 2005_1_620

ST-PI 2005_1_620 0004 SAPKITLQG4 SAP Solution Tools Plug-In

Does this give you any more idea?

Regards,

Corinne

[yann_bouillut]

Hi,

What is your backend release and patch level ?

Kind regards,

Yann

[Former Member]

Hi Yann

We have SAP Enterprise 4.7 Patch-Level SAPKH47025

Regards,

Corinne

[yann_bouillut]

Hi,

I did not see any issue with this...

hum...do you use a backend IDES system ?

Kind regards,

Yann