Mandatory "Notes" not fullfiled does not block the saving

[anais_jaussaud]

Dear Experts,

We are currently dealing with the following issue :

It is possible for us to save an object even if one mandatory text of the “Notes”  assignement block is not fulfilled.

There is only an informative message appearing “Obligatory text not maintained” but it does not block the saving of the object.

Is there any customizing point that we are missing? (we have customized the text as mandatory in the customizing)

For information, our saving issue is only happening with the block "Notes", everything else is working as expected: when trying to save an object when mandatory fields of the Details block are missing, the saving is blocked.

Has anyone ever met the same problem ?

Is there any other customizing that should be checked ?

Thanks a lot for your help,

Regards,

Anaïs JAUSSAUD

[former_member196467]

Hi Anais,

Can you please implement or check if you have the notes 1976833 and 1956794 in your system.

An additional reason could be an enhancement. If indeed you have enhancements I your system you might consider to test the same process by deactivating them (see note 1311966).

Best regards

Christophe

[anais_jaussaud]

Dear Christophe,

Those 2 notes are not applicable on our system as they are part of package BBPCRM 7.13 SP04. but we aldready are in SP06.

Would that be possible that we still need to implement them or are they already integrated into SP06?

We have done test without the enhancements but this does not work. Saving is still possible even if mandatory text is missing.

Thanks a lot for your help,

Regards,

Anaïs

[former_member196467]

Dear Anais,

You are right the notes do not need to be implemented, they are already part of you release and patches.

Is this occurring in both WebUi and SAPGUI?

Do you use any enhancement?

Best regards - Christophe 

[anais_jaussaud]

Hello Christophe,

Sorry for the late reply, we have created an OSS call for this issue.

I will post the answer when the support answers.

Regards

Anaïs Jaussaud

[anais_jaussaud]

Dear Christophe,

just for your information, SAP has asked us to refer to note OSS 1519171.

Symptom

In your business scenario, you expect that the business transaction is not
saved in certain cases, for example, if the certain fields are missing, or
certain messages have been collected into the application log of the business
transaction. How to do this?

Other Terms

ORDER_SAVE, BADI, save

Reason and Prerequisites

This consulting note explains you the usage of the BADI
order_save.

Solution

Basically all business transactions can be saved unlike in ECC, even though
they contain some errors. However, if you do not want to save the business
transaction in certain cases, you can make the BADI implementation of ORDER_SAVE
in the method CHECK_BEFORE_SAVE with the transaction code SE19.
Typically the
business transaction is not expected to be saved if the certain error message
exists. Then you use the Function Module CRM_MESSAGES_SEARCH to search for the
existing message and raise the exception DO_NOT_SAVE.
If you expect to show
your own message once the business transaction fails to be saved, you can raise
your own message id and set the parameter CV_OWN_MESSAGE to 'X'.
Please note,
DON'T trigger commit work in the BADI implementation.

[former_member196467]

Thank you Anais

Regards Christophe