When creating an ASN document for a Schedule Agreement Release (SAR) in SUS the system will propose the full quantity for all items, even when for some of the items ASN has been created for the full quantity. To consider the already ASN-ed quantity you can implement user-exit MEETA001 in ECC with this sample coding:

 

data: ls_ekeh like i_ekeh,

      lv_menge like i_ekeh-menge.

 

 

loop at i_ekeh into ls_ekeh.

 

  check not ls_ekeh-updkz is initial.

   lv_menge = ls_ekeh-menge - ls_ekeh-dabmg.

   if lv_menge eq 0.

      clear ls_ekeh-updkz.

   else.

  ls_ekeh-menge = lv_menge.

   endif.

   modify i_ekeh from ls_ekeh.

 

endloop.

You can adjust the coding to your requirements when needed. As an alternative you can implement the BADI BBP_SUS_FILTER_SCHAR on SUS side to achieve the same effect.

Recently, I found some customers encountered problem in displaying document in portal. This might be caused by one known bug in EP-RUNTIME.

I would like to propose an example for your reference.
In the 'external business partner' part, you can display the suppliers from external systems. The supplier already exists in table VENMAP and BUT000. Meanwhile it is also not blocked. However while clicking the supplier in portal, the error 'business partner has already been deleted' is thrown.

This error is raised due to field mv_bo_guid in the following method:

METH /SAPSRM/CL_CH_WD_AO_SUPP~ CONSTRUCTOR

line 37   lv_partner_guid = mo_task_container->get_bo_guid( ).

===

METH  /SAPSRM/IF_CLL_TASK_CONTAINER~GET_BO_GUID.

rv_bo_guid = mv_bo_guid.

endmethod.
===

Here, mv_bo_guid should contain GUID of BP, but currently it is still filled with default zero value.

In the httpwatch trace, sapsrm_boid(POST Data) contains the GUID value, but the value is not transferred from JAVA to ABAP.

The solution is to upgrade the patch level for EP-RUNTIME as documented in the note below:

2021994 - Malfunctioning of Portal due to omission of post parameters

This is just one example in ADM area, and it also applies for other similar symptom in application.

Hope this helps anyway.

Some end users might feel confused while encountering dump in creating some business parter in SRM:

This kind of dump is caused by missing PDO instance:

<ls_pdo>-pdo is empty which is the key.

In order to create/get PDO instance, Method CONSTRUCTOR in the following classes will be called for different actions:

/SAPSRM/CL_CH_WD_AO_BIDDER               Create Bidder

/SAPSRM/CL_CH_WD_AO_CHGATTR           Edit Attributes

/SAPSRM/CL_CH_WD_AO_EMP_BID            Create Contact Person With Reference(Supplier/Bidder)

/SAPSRM/CL_CH_WD_AO_INVP                    Create Invoicing Party

/SAPSRM/CL_CH_WD_AO_LOCATION          Create Location

/SAPSRM/CL_CH_WD_AO_PERS_SETGS    Create Employee/Create Employee With Reference

/SAPSRM/CL_CH_WD_AO_PORTAL              Create Portal Provider

/SAPSRM/CL_CH_WD_AO_PR_ORG             Create Purchasing Company

/SAPSRM/CL_CH_WD_AO_SUPP                  Create Supplier

/SAPSRM/CL_CH_WD_AO_UEMP_BID          Create User with Reference(Contact Person)

In order to help you understand this, I will show you an example.
Someone click button 'Create User with Reference' for contact person, and encountered this dump.
Then we can set external breakpoint at /SAPSRM/CL_CH_WD_AO_UEMP_BID~Constructor.

In the debugger, method CREATE_NEW_INSTANCE is called in constructor, and later the following method is also called:
method /SAPSRM/CL_PDO_AOF_CP_USER~GET_INSTANCE

Error BBP_BUPA 400 is raised because this contace person has no BBP000(vendor) or BBP001(bidder) role.
This error stopped the processing of getting instance, and the dump is poped up finally.

Of course, the reasons why instance is misisng can be different, and I just put up with one method to find out why the instance is missing in ADM area.

Hope this would be of help in your daily work.

When an RFx is in published status, there is no way of knowing if the bidding period is still ongoing or the bidding has ended without checking the submission deadline of the document. In the purchaser’s view, the RFx is still in status published status, even when the submission deadline is over.

Feature:

As part of this feature, a new status, 'Ended' is introduced for RFx and this status is set for the document when the submission deadline is over. This feature brings in more transparency in the bidding process. The new status indicates that the bidding period of an RFx has ended. It will help you to track the bidding process in an efficient manner.

This feature is also supported for  BId-Decoupled scenario. In this case the switch has to be activated in both SRM and SUS systems.

When we display an RFx for which the bidding period is over, the status will be displayed as 'Ended' as follows:

Also, there will be an option in POWL(Personal Object Work list) to search for all Ended RFx.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_2 and then activate the Customizing switch Additional Status for RFx(SRM_702_RFQ_END) under SRM Server-> RFx->  Activate/Deactivate Additional status after Publishing RFx.

Also, the report, /SAPSRM/RFX_ENDED_STAT_UPDATE, has to be run or scheduled in background for changing the status of all RFx for which submission deadline is over.

Notes:

2045450: Interface Changes: Preparation Changes for Ended RFx

2038376: Interface Changes: Ended RFx

2038377: Implementation note for Ended RFx

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

It is not possible to format long texts. Plain texts can be added as long texts(notes) in SRM documents.

Feature:

This feature enables the user to format the texts entered in long text boxes. With text formatting options users can emphasize key points and hence improves the readability of the entered text by providing multiple formatting options such as bold, italics, bullets etc.

This feature is available in Rfx, Rfx Response, Purchase Order, Central Contract and Shopping Cart Business Object.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_1 and then activate the Customizing switch Text format for long text boxes (SRM_701_TEXT_FORMAT) under SRM Server-> Cross Application Basic Setting->  Activate/Deactivate Text Format for Long Text Boxes.

Notes:

2045021: Interface Change: Preparation Changes for Text Formatting

2038548: Interface Change: Text Formatting

2039409: Implementation Note for Text Formatting

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

If a business partner is no more valid then there is no way to search for the documents which are assigned to this business partner or change the ownership of the document.

Feature:

This feature enables you to edit or display any document in Supplier Relationship Management (SAP SRM) that is assigned to a business partner who is terminated or whose role has become inconsistent in the SAP SRM org structure. This feature is available from SAP SRM 703 Support Package 06.

Allows New business partner to be assigned to a SRM document in case the existing partner is terminated or becomes inconsistent in SRM HR Organization. Thus, allows to create Follow-on documents to be created for documents containing old business partner.

This feature also helps us to track transfer of SRM documents from old Business Partner to new Business Partner.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_3 and then activate the Customizing switch Inconsistent Busines Partner handling(SRM_703_TERMIN_EMP) under SRM Server-> Continuous Improvement->  Activate/Deactivate Inconsistent Business Partner Handling.

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

It is possible to close a Contract ( Transaction Completed ) even if the document has Open PO associated with it.

Feature:

This feature prevents the completion of Contract if there is any Open Purchase Order against it. Configurable message will be displayed upon trying to close the Contract which has open Purchase Order. Thus, this feature ensures better compliance of the business process.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_1 and then activate the Customizing switch Check for open PO before Contract Completion (SRM_701_CONT_CLOSE) under SRM Server-> Cross Application Basic Setting->  Service Procurement-> Activate/Deactivate Check for Open Purchase Orders before Contract Complet.

Notes:

2042218: Interface Changes: Check for Open Purchase Order before Contract Completion

2040522: Implementation note: Check for Open Purchase Order before Contract Completion

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

As part of SAP SRM 7.03 SP06 based on customer connection requirements, the following features are delivered:

Additional status for RFx at end of bidding period:

     A new status, 'Ended', is introduced for RFx at the end of bidding period.

Formatted Text modules in Business Documents:

     User can format texts entered in the long text boxes with text formatting.

Search for SC using ECC PO number:

     Employees can search for SC using ECC back-end PO number.

Inconsistent Business Partner handling:

     Enables you to edit or display any document in SAP SRM that is assigned to a business partner who is terminated or whose role has become inconsistent in SAP SRM Org structure.

Check for open Purchase Order before Contract completion:

     Error or warning message will be displayed while trying to close a Contract with open PO.

Assign Supplier / Currency in Shopping Cart:

     This provides an easier way of assigning supplier or currency for items in SC.

Assign Supplier button obsolete:

    Simplifies the process of assigning suppliers for items in SC by reducing the number of user clicks.

SRM Fiori Carry Out Sourcing App:

     This app with intuitive UX helps user to easily identify right suppliers and source of supply.

You can find detailed description about these features by following the links mentioned below:

Additional status for RFx at end of bidding period

Formatted Text modules in Business Documents

Search for SC using ECC PO number

Inconsistent Business Partner handling

Check for open Purchase Order before Contract completion

Assign Supplier / Currency in Shopping Cart

Assign Supplier button obsolete

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

It's sometime useful to create toolbar button at runtime to meet the dynamic requirements. For example, we may want to give print of comparative statement to bidder after successful evaluation of bids submitted.

To create the "Comparative Statement" button at runtime as shown above.

Step - 1 :  Create Enhancement Implementation for the View "CNR_VIEW" of the  WDA Component "FPM_OIF_COMPONENT".

Step - 2 :  Create Post-Exit for the method "WDDOMODIFYVIEW" of "CNR_VIEW".

Step - 3 :  Write the following Codes in the Post Exit of WDDOMODIFYVIEW.

DATA l_cmp_api TYPE REF TO if_wd_component.

DATA l_key        TYPE wdy_config_key.

* Get the Configuration ID

   l_cmp_api = wd_comp_controller->wd_get_api( ).

   CALL METHOD l_cmp_api->GET_CONFIGURATION_KEY

     RECEIVING

       CONFIG_KEY = l_key.

* Add Button Only in Bidder Screen

   IF l_key-CONFIG_ID = '/SAPSRM/WDCC_FPM_OIF_QTE_BIDDER'.

     DATA lo_fpm TYPE REF TO if_fpm.

     DATA lo_oif TYPE REF TO if_fpm_cnr_oif.

*   Get reference to FPM service object

     lo_fpm = cl_fpm_factory=>get_instance( ).

*   Get reference to Toolbar service object

     lo_oif  ?= lo_fpm->get_service( cl_fpm_service_manager=>gc_key_cnr_oif ).

CALL METHOD lo_oif->DEFINE_BUTTON        

      EXPORTING

        IV_VARIANT_ID       = 'VARIANT_QTE_BIDD'        " Bidder Varient

        IV_FUNCTION         = 'OTHER_FUNCTIONS'

        IV_ELEMENT_ID     = 'EXTENSIBILITY1'               " 'BIDDER_CS'

        IV_VISIBILITY         = '02'                                    " Yes

        IV_SEQUENCE_ID = '40'

        IV_ENABLED         = 'X'                                      " Yes

        IV_EXPLANATION  = 'Comparative Statement - Bidder Version'

        IV_TOOLTIP           = 'Comparative Statement - Bidder Version'

        IV_TEXT                = 'Comparative Statement'

        IV_ON_ACTION     = 'ZBIDDER_CS'.                   " Action

* Render buttons

     WD_THIS->MO_CNR->RENDER_BUTTONS( ).

* Render button choices

     WD_THIS->MO_CNR->RENDER_BUTTON_CHOICES( ).

* Render separators

     WD_THIS->MO_CNR->RENDER_SEPARATORS( ).

* Render duplicate_toolbar

     WD_THIS->MO_CNR->RENDER_DUPLICATE_TOOLBAR( ).

* Render YOU CAN ALSO

     WD_THIS->MO_CNR->RENDER_YOU_CAN_ALSO( ).

* Render RELATED_LINKS

     WD_THIS->MO_CNR->RENDER_RELATED_LINKS( ).

     CALL METHOD WD_ASSIST->PREPARE_TOOLBAR

       EXPORTING

         IV_FIRST_TIME = FIRST_TIME

         IO_VIEW       = VIEW

         IO_CONTEXT    = WD_COMP_CONTROLLER->MO_TOOLBAR_NODE.

Step - 4  : Create Post-Exit for the method "ONACTIONBUTTON_PRESSED" of "CNR_VIEW".

Step - 5  :  Write the  Codes in the Post Exit of method "ONACTIONBUTTON_PRESSED" to give print of comparative statement to bidder when button is pressed.

When creating an ASN document for a Schedule Agreement Release (SAR) in SUS the system will propose the full quantity for all items, even when for some of the items ASN has been created for the full quantity. To consider the already ASN-ed quantity you can implement user-exit MEETA001 in ECC with this sample coding:

 

data: ls_ekeh like i_ekeh,

      lv_menge like i_ekeh-menge.

 

 

loop at i_ekeh into ls_ekeh.

 

  check not ls_ekeh-updkz is initial.

   lv_menge = ls_ekeh-menge - ls_ekeh-dabmg.

   if lv_menge eq 0.

      clear ls_ekeh-updkz.

   else.

  ls_ekeh-menge = lv_menge.

   endif.

   modify i_ekeh from ls_ekeh.

 

endloop.

You can adjust the coding to your requirements when needed. As an alternative you can implement the BADI BBP_SUS_FILTER_SCHAR on SUS side to achieve the same effect.

In SRM systems, direct Currency conversion (e.g. from USD to ARS) is used for Exchange Rate. There may be a few cases where  Customers are using Alternative Exchange rate type(e.g. EURX) for conversion from ‘from currency’(e.g. USD) to ‘To Currency' (e.g. ARS).

Configuration for Alternate Exchange Rate type (e.g. EURX):

Figure1: Table TCURF showing the conversion factors and field  'ABWCT' for Alternative exchange rate type.

Figure2: Alternative Exchange rate type(e.g. EURX) is maintained for conversion from

'from currency'(e.g. USD) to 'to currency' (e.g. ARS).

.

Steps tohandle erroneous Total Value in Purchase Order:

In SAP SRM Procurement Scenario, purchaser/employee creates a shopping cart with free text item in ‘local currency’ (since User/purchasing organization has ‘local currency’ as default currency). A preferred supplier is added to the shopping cart which has ‘foreign currency’ as default currency. A Purchase Order is created out of this shopping cart with currency ‘foreign currency’.

During currency conversion, a rounding error occurs for certain prices(not all) resulting in erroneous Total Value(multiplied by conversion factor twice instead of once).

• Rounding issue occurs for some prices(not for all).
• Internal SAP standard uses direct conversion. When using Indirect conversion there is a huge impact in business due to error in Purchase order total value can be an unexplored area for most of the users.
• Huge Effort in Understanding the root cause for the error as when SRM application calls IPC multiple times, there may be a very slight rounding difference in values for some Price Values, resulting in huge erroneous Total Value in Purchase Order.
            

SRM architecture calls IPC Multiple time as per the design. For the first call to IPC from SRM, currency conversion is done as maintained in

customization by the customer i.e. from ‘local currency’ to EUR and then from  EUR to ‘foreign Currency’, that creates a particular rounded value in IPC.  For the second call to IPC, ‘local currency’ to ‘foreign Currency’ conversion is direct which
creates a different rounded value. Due to rounding off value difference, Function Module for conversion to foreign currency  is called again causing a huge Total Value by multiplying the value again with conversion factor.

When using indirect currency conversion for certain Prices, Rounding Errors can impact the procurement process ,

by calculating:

Total Value(foreign currency) calculated wrongly in Purchase Order = Price(local currency) x Conversion Factor  x Conversion Factor

Kindly note that the behavior mentioned above occurs only for European Monetary Union (EMU) Exchange Rate Type.

Solution:

This Rounding Off issue is resolved via note 2061300. Customer can download the latest IPC patch from the service marketplace
using the instructions in note 880749 and apply it.

Release Information:

SAP SRM 7.0 Enhancement pack 3.

Summary

PO form that is displaying at ECC ME23n transaction level with print preview option should be displayed in SRM system portal level.

Analysis

As it is classical scenario PO details and standard PO form will not be there in SRM. So we have to get the details from backend ECC system.

Displaying PO Form

One way is like fetching all the data that is needed for PO form display and create a custom Adobe form same like ECC PO from in SRM system. Other way is calling the same ECC PO Form from SRM and display.

First way is more complex and need more development objects creation. So second one is good but we should be able to call the PO from and display the same form in SRM.

We can call the PO from in ECC using the generated Function Module for adobe form and that FM will give us PDF raw data. Then you have to get that PDF raw data in SRM and display PDF form.

We are creating Webdynpro Application to display PO form, so using the PDF raw data we can directly display the Adobe form in Webdynpro.

PO Search Screen

We wanted a PO form search screen like the below

So user should be able to search PO’s with all these criteria’s.  But we don’t have PO’s available in SRM for all Carts. Because PO will be created in the backend, for some carts PO will be the first follow on document and for some documents PR will be the first follow on document. It depends on Country, so PO will be available in SRM table BBP_PDBEI if PO is the first follow on document. Otherwise PR only will be available.

We have an API to search Shopping Carts with different criteria.

Class: /SAPSRM/CL_PDO_AOMS_SC-> /SAPSRM/IF_PDO_AOMS_SC~SEARCH with this method you can search shopping carts with different criteria’s. With this class you can only search with single range of values. I mean if you wanted to search based on the PO numbers but you can only search 1 PO at one time or you can specify range. But you cannot search based on the different range of PO and different PO numbers at one time.

FM: BBP_BW_SC_SELECT_1 using this FM we can search with same search criteria that class provided with multiple range of values. You can pass every value as range table and based on that you can search. You can even specify OPTIONS (EQ, NE, etc..) and SIGN(Include, Exclude).

Once we get the Shopping cart details you have to get the PO of those carts. So using the BBP_GET_DOC_HISTORY we can get the PO details.

If you don’t want use these APIs then you have to find the database tables to query. But this will be more complex and have to write lot of queries and conditions. Coz you have different search criteria’s and you should be able to write logic to achieve all those.

Search based Shopping cart, Date range, Created by

CRMD_ORDERADM_H - You can read Shopping cart with those criteria directly from this table.

Then read the PO using tables using FM BBP_GET_DOC_HISTORY

Or you can read the PO using the below relationship tables
SRRELROLES
BBP_PDBINREL

Requester Based search

First you have to read the Shopping carts created by this requester, so using the below tables you can read.

CRMD_ORDERADM_H
CRMD_ORDERADM_I
CRMD_LINK
CRMD_PARTNER
BUT000

Then read the PO using tables using FM BBP_GET_DOC_HISTORY

Or you can read the PO using the below relationship tables
SRRELROLES
BBP_PDBINREL

PO number based Search

SRRELROLES
BBP_PDBINREL
CRMD_ORDERADM_H

Development Steps

ECC level Development

Create an RFC function module that calls PO form and send PDF data of form based on the PO number.

Attached file has the logic

SRM Level Development

Webdynpro ABAP Application

Create a webdynpro component and all the sub object as like below screen shot.

Component usage

Create context as like below

Create a selection screen in WDDOINIT method

Attached file has the logic.

Search Button action

Link to Action Download PO

Download Selected PO Button action

same logic like above method

Webynpro Application

Search PO based on the entered Criteria

Central class for different generic and database relate operations methods. Selected methods are related to PO Search. The main method GET_PO_FORM_SEARCH_RESULT that is calling from the Webdynpro Search action and the other methods inside the main method.

Method Signature

Logic attached

Methods which are calling inside the main method to search. logic of these methods are attached

GET_PO_FOR_CARTS - this will search PO for the Carts

SEARCH_CARTS_REQUESTED_BY - This method will search carts based on the Requested by user

SEARCH_CARTS_PR_BASED - This method search carts PR based

SEPERATE_PO_PR - Separate PO based and PR based PO's

SEARCH_CARTS_PO_BASED - Search carts which are PO based

Testing

Integrated webdynpro application with IView.

Carts created by me and click on Purchase order number or select and click on button

PO form will be downloaded

When an RFx is in published status, there is no way of knowing if the bidding period is still ongoing or the bidding has ended without checking the submission deadline of the document. In the purchaser’s view, the RFx is still in status published status, even when the submission deadline is over.

Feature:

As part of this feature, a new status, 'Ended' is introduced for RFx and this status is set for the document when the submission deadline is over. This feature brings in more transparency in the bidding process. The new status indicates that the bidding period of an RFx has ended. It will help you to track the bidding process in an efficient manner.

This feature is also supported for  BId-Decoupled scenario. In this case the switch has to be activated in both SRM and SUS systems.

When we display an RFx for which the bidding period is over, the status will be displayed as 'Ended' as follows:

Also, there will be an option in POWL(Personal Object Work list) to search for all Ended RFx.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_2 and then activate the Customizing switch Additional Status for RFx(SRM_702_RFQ_END) under SRM Server-> RFx->  Activate/Deactivate Additional status after Publishing RFx.

Also, the report, /SAPSRM/RFX_ENDED_STAT_UPDATE, has to be run or scheduled in background for changing the status of all RFx for which submission deadline is over.

Notes:

2045450: Interface Changes: Preparation Changes for Ended RFx

2038376: Interface Changes: Ended RFx

2038377: Implementation note for Ended RFx

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

It is not possible to format long texts. Plain texts can be added as long texts(notes) in SRM documents.

Feature:

This feature enables the user to format the texts entered in long text boxes. With text formatting options users can emphasize key points and hence improves the readability of the entered text by providing multiple formatting options such as bold, italics, bullets etc.

This feature is available in Rfx, Rfx Response, Purchase Order, Central Contract and Shopping Cart Business Object.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_1 and then activate the Customizing switch Text format for long text boxes (SRM_701_TEXT_FORMAT) under SRM Server-> Cross Application Basic Setting->  Activate/Deactivate Text Format for Long Text Boxes.

Notes:

2045021: Interface Change: Preparation Changes for Text Formatting

2038548: Interface Change: Text Formatting

2039409: Implementation Note for Text Formatting

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

If a business partner is no more valid then there is no way to search for the documents which are assigned to this business partner or change the ownership of the document.

Feature:

This feature enables you to edit or display any document in Supplier Relationship Management (SAP SRM) that is assigned to a business partner who is terminated or whose role has become inconsistent in the SAP SRM org structure. This feature is available from SAP SRM 703 Support Package 06.

Allows New business partner to be assigned to a SRM document in case the existing partner is terminated or becomes inconsistent in SRM HR Organization. Thus, allows to create Follow-on documents to be created for documents containing old business partner.

This feature also helps us to track transfer of SRM documents from old Business Partner to new Business Partner.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_3 and then activate the Customizing switch Inconsistent Busines Partner handling(SRM_703_TERMIN_EMP) under SRM Server-> Continuous Improvement->  Activate/Deactivate Inconsistent Business Partner Handling.

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

It is possible to close a Contract ( Transaction Completed ) even if the document has Open PO associated with it.

Feature:

This feature prevents the completion of Contract if there is any Open Purchase Order against it. Configurable message will be displayed upon trying to close the Contract which has open Purchase Order. Thus, this feature ensures better compliance of the business process.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_1 and then activate the Customizing switch Check for open PO before Contract Completion (SRM_701_CONT_CLOSE) under SRM Server-> Cross Application Basic Setting->  Service Procurement-> Activate/Deactivate Check for Open Purchase Orders before Contract Complet.

Notes:

2042218: Interface Changes: Check for Open Purchase Order before Contract Completion

2040522: Implementation note: Check for Open Purchase Order before Contract Completion

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

As part of SAP SRM 7.03 SP06 based on customer connection requirements, the following features are delivered:

Additional status for RFx at end of bidding period:

     A new status, 'Ended', is introduced for RFx at the end of bidding period.

Formatted Text modules in Business Documents:

     User can format texts entered in the long text boxes with text formatting.

Search for SC using ECC PO number:

     Employees can search for SC using ECC back-end PO number.

Inconsistent Business Partner handling:

     Enables you to edit or display any document in SAP SRM that is assigned to a business partner who is terminated or whose role has become inconsistent in SAP SRM Org structure.

Check for open Purchase Order before Contract completion:

     Error or warning message will be displayed while trying to close a Contract with open PO.

Assign Supplier / Currency in Shopping Cart:

     This provides an easier way of assigning supplier or currency for items in SC.

Assign Supplier button obsolete:

    Simplifies the process of assigning suppliers for items in SC by reducing the number of user clicks.

SRM Fiori Carry Out Sourcing App:

     This app with intuitive UX helps user to easily identify right suppliers and source of supply.

You can find detailed description about these features by following the links mentioned below:

Additional status for RFx at end of bidding period

Formatted Text modules in Business Documents

Search for SC using ECC PO number

Inconsistent Business Partner handling

Check for open Purchase Order before Contract completion

Assign Supplier / Currency in Shopping Cart

Assign Supplier button obsolete

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

It's sometime useful to create toolbar button at runtime to meet the dynamic requirements. For example, we may want to give print of comparative statement to bidder after successful evaluation of bids submitted.

To create the "Comparative Statement" button at runtime as shown above.

Step - 1 :  Create Enhancement Implementation for the View "CNR_VIEW" of the  WDA Component "FPM_OIF_COMPONENT".

Step - 2 :  Create Post-Exit for the method "WDDOMODIFYVIEW" of "CNR_VIEW".

Step - 3 :  Write the following Codes in the Post Exit of WDDOMODIFYVIEW.

DATA l_cmp_api TYPE REF TO if_wd_component.

DATA l_key        TYPE wdy_config_key.

* Get the Configuration ID

   l_cmp_api = wd_comp_controller->wd_get_api( ).

   CALL METHOD l_cmp_api->GET_CONFIGURATION_KEY

     RECEIVING

       CONFIG_KEY = l_key.

* Add Button Only in Bidder Screen

   IF l_key-CONFIG_ID = '/SAPSRM/WDCC_FPM_OIF_QTE_BIDDER'.

     DATA lo_fpm TYPE REF TO if_fpm.

     DATA lo_oif TYPE REF TO if_fpm_cnr_oif.

*   Get reference to FPM service object

     lo_fpm = cl_fpm_factory=>get_instance( ).

*   Get reference to Toolbar service object

     lo_oif  ?= lo_fpm->get_service( cl_fpm_service_manager=>gc_key_cnr_oif ).

CALL METHOD lo_oif->DEFINE_BUTTON        

      EXPORTING

        IV_VARIANT_ID       = 'VARIANT_QTE_BIDD'        " Bidder Varient

        IV_FUNCTION         = 'OTHER_FUNCTIONS'

        IV_ELEMENT_ID     = 'EXTENSIBILITY1'               " 'BIDDER_CS'

        IV_VISIBILITY         = '02'                                    " Yes

        IV_SEQUENCE_ID = '40'

        IV_ENABLED         = 'X'                                      " Yes

        IV_EXPLANATION  = 'Comparative Statement - Bidder Version'

        IV_TOOLTIP           = 'Comparative Statement - Bidder Version'

        IV_TEXT                = 'Comparative Statement'

        IV_ON_ACTION     = 'ZBIDDER_CS'.                   " Action

* Render buttons

     WD_THIS->MO_CNR->RENDER_BUTTONS( ).

* Render button choices

     WD_THIS->MO_CNR->RENDER_BUTTON_CHOICES( ).

* Render separators

     WD_THIS->MO_CNR->RENDER_SEPARATORS( ).

* Render duplicate_toolbar

     WD_THIS->MO_CNR->RENDER_DUPLICATE_TOOLBAR( ).

* Render YOU CAN ALSO

     WD_THIS->MO_CNR->RENDER_YOU_CAN_ALSO( ).

* Render RELATED_LINKS

     WD_THIS->MO_CNR->RENDER_RELATED_LINKS( ).

     CALL METHOD WD_ASSIST->PREPARE_TOOLBAR

       EXPORTING

         IV_FIRST_TIME = FIRST_TIME

         IO_VIEW       = VIEW

         IO_CONTEXT    = WD_COMP_CONTROLLER->MO_TOOLBAR_NODE.

Step - 4  : Create Post-Exit for the method "ONACTIONBUTTON_PRESSED" of "CNR_VIEW".

Step - 5  :  Write the  Codes in the Post Exit of method "ONACTIONBUTTON_PRESSED" to give print of comparative statement to bidder when button is pressed.