The ASSERT condition was violated

[Former Member]

Hello,

I'm having an issue when running the transaction BP. I've created a business partner and I'm trying to assign the role BKK010 Account Holder but it's going in dump when saving.

Short Text
The ASSERT condition was violated.

Trigger Location of Runtime Error
Program XO_SEGMENT_FACTORY============CP
Include XO_SEGMENT_FACTORY============CM005
Row 19
Module Type (METHOD)
Module Name GET_INSTANCE

Most certainly there is some data missing but I can't figure out exactly what.

I've already trying a couple of solution proposed, but none of them fixed the problem.

Do you have any idea what could be the cause?

Regards,

Nick

[Former Member]

Hi Nick,

Could you solve the problem?

I'm having the same error.

Thanks!.

[JL23]

Had you already searched for OSS notes? use the search term: BP assert condition violated

[Former Member]

Finally applied the note N°1555393 and I solved the problem!.

Thanks!.

[former_member447287]

Hello,

I am facing the same issue when I run BP transaction and try to assign the role FS0000 or TR0151. Actually it seems to be linked with the company code. I have already implemented note 1555393 as well as note 2256149.

Do you have any idea about this dump.

Many thanks in advance for you help.

Arnaud

[Former Member]

Hello Arnaud,

Did you solve this issue. I'm facing exactly the same problem (note 1555393 didn't work).

Thanks and regards.

J.A.

[Former Member]

Dear Nick

I have the same issue,would you please share your solution?

Thanks a lot

BR/Tony

[Former Member]

Solution: put the element into a transport order, and then modify

[grigoriy_babitskiy]

Hello,

text from comments in BP's ABAP code:

"If dump occours here, have a look at the content of the structure LS_ERROR

"in the debugger for error messages causing the error.

"Hint: This is a quite complex data structure, so you might have to navigate down

"some levels in the structure to find the relevant error messages.

"In addition the first 7 messages are will be visible within the short dump

If you would like to avoid dumps - activate PPO (PostProcessing Office)

• SPRO -> Cross-Application Components-> Master Data Synchronization -> Synchronization Control -> Synchronization Control -> Activate PPO Requests for Platform Objects in the Dialog

Then you'll be able to search errors in

• SAP Menu -> Cross-Application Components -> Postprocessing Office -> Postprocessing Order -> /SAPPO/PPO3 - Display Postprocessing Order