Skip to Content

We all know the how SAP keeps improving its products with

     New releases

     Enhancements

     Service packs

 

This time I wanted to return back to SAP by combing everyone’s Idea in the forum Thus , I would like to exchange  some ideas on what were the Customer driven Enhancements which were made in SRM landscape and which have proven to be valuable to the client . This way we can combine ideas across multiple SRM landscape and can do value add for other clients as well who are looking for continuous improvement .

It could be something which was done to make the existing features change in SRM or It could be an additional feature in SRM which is not provided in SRM standard or maybe is SAP standard but client tweaked it in their own way and it proved to be more beneficial

It would be helpful if pasted in the format as below if needed  additional details can still be included below the same .

Issue description :

Issue Details

Fix employed :

Technical Details : BADI / Class / Method name

Is it provided in SAP standard :

Examples from my end :


CASE 1 : Issue description :  Gr Error message enhancement issue

Issue Details : When trying to Do GR for Fully Grd or locked / deleted line items SC it gives Error message which are not easy to understand .

Fix employed : SAP OSS note 1665796 for GR message enhancement fixes a part of the problem but we also have to make changes in Web dynpro Component

Technical Details : BADI / Class / Method name  /SAPSRM/WDC_UI_BO_CONF_PS View V_SEARCH

Method EXECUTE_SEARCH

Is it provided in SAP standard :  No

CASE 2 : Issue description : Making rejection reason mandatory

Issue Details  ; While rejecting a SC make the reason of rejection mandatory

Fix employed : check the condition where SC is being opened by approver , Check if the carts are having status as rejected if yes check if note if filled 

Technical Details : BADI / Class / Method name DOC_CHECK _BADI

Is it provided in SAP standard : No

CASE 3 : Issue description :Shopping cart currency

Issue Details SC currency is being picked from users attribute and PO currency is picked from vendor We cannot make the SC currency same as PO currency since it defeats the purpose of using SRM since it  has to be requestor specific however we could give user idea on what the currency of the PO would be rather them leaving them to guess it on their own .

Fix Description : Make currency at Item level same as Vendor currency and make changes at item level to disable the field when the currency is changed at item level to vendor currency . Display an information message in  that currency has been changed .

Technical Details : BADI / Class / Method name DOC CHANGE BADI   , DOC CHECK BADI , Meta Deta concept

Is it provided in SAP standard : No


I would request everyone to come forward and share their views on the topic even if its a minor code change , SPRO change , Note applied which solved a long issue or maybe something they want to change in the system

To report this post you need to login first.

7 Comments

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

  1. Konstantin Anikeev

    Hi Vinita,

    I suppose you posted to the wrong thread. Maybe, what you really need is a SAP Service Marketplace – SAP Listens.

    Actually, provided issues / missing functionality, is not so critical for the most customers (except 2).

    CASE 1. GR for FullyGrd / deleted lines is not a typical business case. SAP Provides not only software, but also a ready to use business processes. I would say, for CASE 1 the business process is wrong itself. What means delivery of compl. delivered goods?

    CASE 2. Yeah. From my experience, almost every client implements it. But CHECK_BADI is not called during rejection, how does it work in your system?

    CASE 3. Looks like a typical customer requirement.

    Regards

    Konstantin

    P.S.: all written is my personal opinion.

    (0) 
  2. Suseelan Hari

    Hi Vinitha,

    Thanks for sharing about SRM enhancements. I am new to this and try to learn some good points with the help of this blog. I check this blog only to understand about SRM enhancements features. Keep sharing and updating SRM updates it will be very useful for our New SCN SRM Members.

    All the best! 🙂

    Regards,

    Hari Suseelan

    (0) 
  3. Raghu Seerla

    Hi Vinita,

    Appreciate your interest in taking this initiative as I am sure it would be useful to people working on SRM.

    Following are the details of an issue, we faced in our project:

    Issue description : Output medium being replaced for a supplier in all Purchase Organizations.

    Issue Details : In ECC system, output medium of a vendor will be maintained in the address data whereas in SRM it could be maintained specific to a Purchase Organization.

    When Vendor_sync program was executed output medium in SRM for all P.Org’s was replaced by the one maintained in the address tab of ECC system.

    Fix employed : All field changes expect medium would be transferred to SRM system when sync program is executed.

    Technical Details : BADI / Class / Method name : Z enhancement has been created.

    Is it provided in SAP standard : No

    Best regards,

    Raghavendra.

    (0) 
    1. Vinita kasliwal Post author

      Hi Raghu

      Thanks for the information and looks like an interesting change in system design would have been even better if you could include some technical details on where we could add the enhancement which BADI

      “ll field changes expect medium would be transferred to SRM system when sync program is executed” PLease also comment what is the sync program here . Suggest maybe if you could write a Document or blog on this and paste the link here . .

      (0) 
  4. Susan Keohan

    Hi Vinita,

    Regarding rejection reasons, this is indeed a struggle.  And because Shopping Carts and POs have different structures (in our case, SC’s are ‘headerless’) the enhancements done to the WDA/FPM applications underneath are also different.

    For anyone out there struggling with how to require a rejection reason on a PO, consider this OSS Note:

    https://websmp130.sap-ag.de/sap/support/notes/1875106

    We are working to apply it now, but maybe it will help you out too.

    I’d also be interested in hearing of customers who do *not* require a rejection reason – because if we asked that question the other way around, there might be a host of ‘me too!’ responses.

    Regards,
    Sue

    (0) 
  5. Ashish Shah

    Hi Vinita,

    Last year SAP Procurement lead Heike Kalwak had started a drive to collect enhancement requests from partners and clients for SAP SRM System:

    Entire list can be seen here:

    https://influence.sap.com/11086

    You should post your Ideas in this place to be considered for future implementation post discussions.

    Regards,

    Ashish

    (0) 

Leave a Reply