There are some critical customer requirements which sometimes do not fall in line with the SAP Standard like in this case there could be some messages treated as Warning and let the requestor place the cart or create a contract when actually this is Critical to Quality for Business and need to be be changed to error to not let the requestor place the cart .

Or  for example there is a check which is SAP mandated as Error however the client’s business would treat this as an exception in their case and demand the check to be passed as warning .

So we all are aware of this whats new in here ? We generally check for the message in the code going to class se93 where it appears and then try to either overwrite it by our own custom code etc . However there is a SPRO path which we could use to make this change from Error to warning and thus it would meet the necessary checks as per the Clients need . 

Please check the below few examples based on client scenarios in production which demanded a change from error to warning if it has still not been an area of concern for your client you could anyway check with them if they would like to incorporate the same ?

  1. SPRO Design changes  with some common example scenarios .

Below is the SAP SPRO path where we would make the changes :

  SAP Supplier relationship Management > >SRM server > >Cross Application basic settings >> Message control >> Influence Message control


Select BUS2121 Business object Row and Click on message control . Then you may click on New entry and enter the message details to change from Error to Warning or vice versa .

As per the below Table make changes in TYPE : (Make changes here from E to W or vice versa as per business need )

Below Listed are some most commonly changes Messages  Options in TYPE would be as below :

And standard messages could comprise something from the list : E : Error , W : Warning , I : Information

Examples :

  • Making delivery date in the past : For requestor , Incase of approver for completion step etc allow this to be done make the message as warning where the user would be able to create and approve the SC with a delivery date of past the standard behavior in this case is in being error .
  • Incase of creating a contract the vendor currency should be same as Contract currency this should be changed to error while standard being warning .

OTHERS :

SNO

Object Type

Message Class

Msg#

Description

Standard

Type

1

BUS 2121

BBP_PD

438

Start date of the timeframe is in the past; check the entry

E

W

2

BUS2121

BBP_PD

458

Start date is in the past

E

W

3

BUS2121

BBP_PD

584

Preferred delivery date cannot be kept; earliest date: &

E

W

4

BUS2000113

BBP_PD

323

Currency & of contract differs from purchase order currency & of supplier

W

E

5

BUS2000113

BBP_PD

848

Target value should be greater than minimum order value

E

**W

6

BUS2000113

BBP_PD

867

Target quantity should be greater than minimum order quantity

E

**W

If you haven’t checked this as yet do touch base with your client specially in a new implementation project and you would be also  including this as a requirement soon .

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Jon Azcorra Olano

    Hello Vinita,

    First of all thanks for such a good post, i would like to ask you something about it.

    I have folloewd the steps you indicate to set an error message in SRM as warning, but the message is still appearing.

    I attach the screenshot.

    RegardsSin título.png

    (0) 
    1. Vinita kasliwal Post author

      Hi Jon

      Is it too late to reply ?

      I saw your post now ! Thanks for the feedback .

      The message should appear as a warning in your system if you were able to save this entry successfully and add it into a transport. If you want to remove it completely please put a Hyphen instead –

      Regards

      Vinita

      (0) 

Leave a Reply