Able to submit a shopping cart with errors

[Former Member]

HI there everyone,

First of all, our SRM version is 7.02 of an OneClient implementation.

We have implement the DOC_CHECK_BADI to validate some of the data during the creation of the shopping cart.   We generate error messages that prevents the creator from ordering the cart (i.e when they push button "Order").

However, during the approval process (Approval with Completion) the approver is able to change the data that would cause an error, but the DOC_CHECK_BADI  does not prevent the approver from approving the SC (i.e. when they push button "Submit").

As a result, the shopping cart continues to be processed, even though it contains errors.   The errors do appear when the user presses the "Check" button, but they do not appear when they "Submit" the cart.

During the troubleshooting I was able to determine that  DOC_CHECK_BADI gets called with the IV_MODE = "U" and IV_SAVE = "X" during the "Order" process and then returns the to application, however, during  the "Submit" process, it does call with the same values above, but it also calls the BADI a second time with the IV_MODE = "T" and IV_SAVE = "", and the SC is then approved and moved on the the next approver.  I am assuming that this is the reason it allows the SC to be saved/processed with errors.

I've looked at configuration in SPRO looking for a setting that would allow the "Submit" action have the same behaivour as the "Order" action, but I have not be able to do so.

I would appreciate any insight in this matter.

Thanks in advance.

[Former Member]

Hi there,

Once again, thanks for your input.

As it turns out, this was an error in SAP and they created an OSS note to correct the problem.

The OSS note is 1807067.   I've applied it and it corrected the problem.

[Former Member]

Hi Joe,

     I have been searching the OSS note but seems to be that OSS note is not released. How have you implemented it?

Thanks in advance for your help.

Jose.

[Former Member]

Hi all,

     I answer myself. I have fixed the problem using the OSS note 1361411 (disallow approver to delete items on a completion level). I've applied it and it corrected the problem.

Best Regards.