Runtime error ASSERTION_FAILED in transactions XK01 and BP in S/4 HANA 1610 SPS00

[felix_fichtner]

Hello,

I have a Problem when I try to create a vendor in S/4 HANA 1610 SPS00.

This happens in XK01 when I get the popup to select if I want to create a Person / Organization / Group and hit ok (You get forwarded to transaction BP) . It also appears when I use transaction BP and choose "FLVN00 FI Vendor" as role for my Business partner.

The runtime error is:

ASSERTION_FAILED ABAP

XO_SEGMENT_FACTORY============CP

So the assert statement in Program XO_SEGMENT_FACTORY is violated.

The assert looks as follows:

Class: XO_SEGMENT_FACTORY

Method: GET_INSTANCE

* check contract violation: all parameters must be supplied
assert:
i_object_name is not initial,
i_object_key is not initial.

At the moment of the dump the values are:

i_object_name = COMPANY_CODE

i_object_key is empty

I had this problem already in version 1511. I tried to debug it and checked all the customizing, but I could not find the reason for the empty value in the assert statement.

Runtime Error Text:

dump-assertion-failed.txt

[swatisoni18]

Dear Team,

This sap note is already implemented in system,Can you please help to resolve this issue.

Please find details below

;Runtime Error -ASSERTION_FAILED

abap program-xo_memory_factory============CP

application component-FS_BP

[felix_fichtner · Accepted solution]

So it turns out, that our S/4 is completely broken. Looks like we will get a new installation. Anyways, thanks for reading.

[joachimrees1 · Accepted solution]

Thanks for sharing, Felix!

So it works fine now, on your new installtion?

[Lakshmipathi]

Have a look at note 2256149

[felix_fichtner]

Unfortunately we do not have the component EA-FINSERV installed, so the note cannot be applied.

[muralikrishnanpv]

Hi Felix,

We faced the same issue in S/4 HANA 1709 and after hours of debugging we figured out that the BDT adapter for Financial services(FSBP) is not set to active in the system. When we activated this setting using BUPT transaction the issue got resolved.

[former_member617094]

Plz Elaborate how to do it

[muralikrishnanpv]

Hi Muhammad,

We followed the below steps.

1)Execute transaction BUPT

2)From Menu select - Business Partner Control --> Applications

3)Search for FSBP

4)Double click and select activate check box and save.

Please let me know if you require more info.

[Former Member]

Looks like I had the same issue today (at least looks like it).

The feeling I get is that SAP was trying to recover a variant info when I tried to enter the transaction again, but for some reason SAP lost this data which led to the "assert" dump.

All I did was close the session and log in into this SAP client again, and the dump was gone. This made me think that maybe some kind of buffer refresh could also have the possibility of solving it, but I don't have the issue to test this idea anymore.

Hope it helps.

P.S: please score if it helped.

[former_member58096]

All the answers is wrong.

What my solusion is very simple.

1. Open tcode BUPT

2. Create RFC connection to working tcode (example: QAS / PRD)

3. Make compare application ID in tcode BUPT

4. Make transport of copies and transport all different table from working server to failed working system.

5. Done.

[qiuwei52]

Problem solved by below adoption in 1910.

1.T-code BUSD

2.Uncheck the appl BUA/BUB/BUP

[former_member422737]

We've solve the problem but after IS-U activiation its again! Do you have any idea please ?

Thank you

Jeyhun Hajiyev

G Lakshmipathi

[kevin_dewilde]

Were you able to solve this yet? We face the same issue after ISU activation.

[former_member422737]

Hi

We could not solve the problem yet after ISU activation. In addition we dunno how to solve!

[former_member369568]

Thanks a lot G Lakshmipathi. We update EHP0 to EHP7 and after updating EHP5 to EHP7 we meet that error in BP tcode. After look and customizing that XO80 tcode it is worked. Link :

https://launchpad.support.sap.com/#/notes/0002256149