It is not possible to set the Central Contract status to Saved after mass update of the selected Contracts. As a result Purchase cannot enrich the document with specific details and release later.

Feature:

It is possible to set the Contracts to Saved status after a mass update to the Contracts. This  allows the purchaser to make common changes in the mass update transaction and later on update the individual contracts with specific changes before publishing.

Following check box is available in the Contract Mass Change second screen, Define Mass Change, to set the status of the Contracts to Saved status.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_3 and then activate the Customizing switch Mass Changes to Contracts(SRM_703_MC_ADD_STATUS) under SRM Server-> Continuous Improvement-> Activate/Deactivate Mass Changes to Contracts.

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

There is no option for an expert user to purchase some items on priority, by mentioning the follow-on document type as Purchase Order or Contracts for those Shopping Cart items and avoid bidding process. As a result he/she might have to wait till the entire biding process is over.

Feature:

There is an option for users with specific authorization to control the follow-on document that can be created for a shopping cart item which are relevant for sourcing. Purchaser can assign the follow-on documents applicable for items in a shopping cart. These follow-on documents appear against the items in the Carry Out Sourcing screen. The operational purchaser can then view, select, and assign only those follow-on documents for the item(s) in shopping cart. This enables faster purchasing of items relevant for sourcing.

Following Drop down field is introduced in Shopping Cart item details as part of this feature and the options appearing in the drop down can be configured.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_3 and then activate the Customizing switch Follow-On Documents for Shopping Cart(SRM_703_SC_FOLLOW_ON_IND) under SRM Server-> Continuous Improvement-> Activate/Deactivate Follow-On Documents for Shopping Cart.

The drop down entries for follow on documents can be configured under SRM Server-> Cross-Application Basic Settings-> Define Settings for Creation of Follow-On Documents in Shopping Cart.

Notes:

2087914 - SC New Filed For Follow-on Documents - Interface Note

2107661 - SC New Field for Follow-on Documents - Implementation Note

2108193 - New Field for Follow-on Documents - some improvements

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

There in an option to update the release values in the central contract at item level for hierarchical items (services & limits). At the moment, the release values are updated only at the outline level and this causes incorrect values in the BI/BW reporting of contract consumption at the item level.

Feature:

This feature enables you to activate the function that updates the release value of a hierarchical service line item under a central contract hierarchy.

At the time of assigning the contract as Source of Supply, user will be allowed to assign the service line item within the hierarchy. The system also updates the release value for the selected hierarchical service line item and updates the aggregated release value for the entire central contract hierarchy.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_1 and then activate the Customizing switch Additional Status for Release Value for a Hierarchical Service Item (SRM_701_CTR_SRV_HIER_REL_UPD) under SRM Server-> Sourcing->  Activate/Deactivate Release Value for a Hierarchical Service Item.

Notes:

2091297: Interface Note for Contract Release value updation

2106269: Contract Release value updation- Implementation note

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

Output medium for business documents like Purchase Order (PO) and Central Contract is inflexible. It is difficult for customers to change the output medium and the output language based upon different customer criterion.

Feature:

A new BAdI is introduced using which the output medium and language of the business documents like Purchase Order and Contract can be influenced. Customers can change the output medium and language of PO and Central Contract by creating a new implementation for the BAdI.

Below is the name of BAdI:

BBP_OUTPUT_MED_CHANGE

Note:

2066055 - Output Language and Medium Determination BAdI BBP_OUTPUT_MDE_CHANGE

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

Introduction

This procedure is for new vendor addition/ extending an existing vendor to a particular Purch. Org.

Vendors in SRM are replicated from ECC R/3 system. Usually a batch job runs in the background that will replicate the vendors from ECC to SRM in periodic routine. Here, in this document I will show you how to manually transfer/replicate a vendor from ECC to SRM.

Standard T. Codes for vendor org structure in SRM:

PPOSV_BBP       : Display Vendor
PPOMV_BBP       : Change Vendor
PPOCV_BBP       : Create Vendor

Pre-requisites:

For a fresh SRM installation the vendor root node is created in transaction PPOCV_BBP. And, if an existing SRM 4.0 system is upgraded to a later release then we need to run report BBP_XPRA_ORGEH_TO_VENDOR_GROUP from SE38 to get the vendor node created under Vendor Org Structure. Once Vendor root is created, we can proceed with the vendor transfer from R/3 to SRM system. Same can be displayed in transaction PPOSV_BBP.

In above figure, in right hand side panel window, Vendor Group assignment is the description of the supplier, Code is the supplier number, ID denotes the business partner ID and then comes the validity dates.

Number ranges

For number range definition of vendors, please refer to the following customizing:

1. Cross-Application Components > SAP Business Partner > Business Partner > Basic Settings > Number Ranges and Groupings > Define Number Ranges

Or

Use t-code SNRO and input object 'BU_PARTNER'. Here you should define an external number range which corresponds to the R/3 numbers.

2.Cross-Application Components > SAP Business Partner > Business Partner> Basic Settings > Number Ranges and Groupings > Define Groupings and Assign Number Ranges

Or

Use t-code BUC2 to check it

For each replication run, you can download the vendors which corresponds to the external number range / grouping which is marked as 'standard external'.

Creation/Addition of new Supplier in SRM system

New supplier is created in R/3 system and is replicated to SRM via BBPGETVD

Below is the example with step by step procedure for the same-

Create a vendor in ECC system-

Vendor account created successfully-

Now run BBPGETVD in SRM system to get the vendor from ECC to SRM system-

This will lead you to another window which will show the total no. of entries given and no. of updates possible. You can display list for your reference. And start transmission.

Check SLG1 for application log.

Vendor has been transferred successfully from R/3 system to SRM system.

Checking the same in SRM portal –

In this way a new Supplier is integrated to the SRM system manually.

Update Existing Vendor's Master records

This procedure is for updating data records for any existing vendor or extending a vendor to any purticular Purchasing organization.

T.Code- BBPGETVD – To transfer Vendor from ECC to SRM system. Enter the below required fields-

System represents the backend R/3 system from where vendor data has to be picked. Enter Supplier number and P.Org. To transfer a vendor without ref to any backend Purchasing Org, we need to check without reference to backend purchasing org. box and leave the Purchasing Organization filed blank.

To avoid any duplicity of the vendors check for the address comparison box and proceed.

Object ID is the Vendor Root ID (Refer PPOSA_BBP screenshot)

Select “Only transfer R/3 Numbers” radio button and Click “Start Transfer”. If vendor is not transferred via batch job then it will be transferred instantly else an information pop up will be displayed as shown below-

This, above message, shows that Vendor is already transferred to the SRM system.

Now we need to update the vendor master record using T.Code BBPUPDVD. This will update the vendor backend data from ECC to SRM.

Enter the below mentioned mandatory fields and click start transfer.

This will lead you to another window which will show the total no. of entries given and no. of updates possible. You can display list for your reference. And start update.

Vendor will be updated in SRM system with this.

Now we can check whether it went successfully or not. So for that analyze application log.

Tcode- SLG1–Give the accurate entry data to populate the required data only.

In case of any update failure, we can find the root cause for vendor update failure here and then it needs to be rectified from ECC front.

Click execute

Messages in red are errors else rest all means it went through successfully.

Log in to portal and specify vendor no. in search criteria.

We can find the Purchasing organization details under the Supplier data tab.

This shows Supplier has been extended to the SRM system for the required Purchasing organization.

Every user expects his/her shopping cart should convert into desired follow on document without any errors.As you aware every requisition is a critical business need and it must be procured from the external vendors.Every Requisition activity is very important for the business. SRM consultants must train the Business users and Buyers to use the application effectively.However there are some situations some of the shopping carts were failed due to many reasons like Master data (Material , Vendor and Finance data) issues, system issues , configuration while creation of purchase order. SRM system may not able to validate all the data while creating the shopping cart. Actually SRM is a very effective procurement system with tightly integrate to any ERP system/ Financial system. Unfortunately due to some Technical reasons SRM Requester never gets notification if any shopping carts failed after approval. These failed shopping carts are monitored by EBP administrator on daily basis. EBP administrator contacted the various master data team/Procurement team to correct the master data and helps to reprocess the shopping carts and make ensure that all failed shopping cart turned to follow on documents. Here there are some examples with error codes and solution.This document shall be useful for SRM beginners to address the issues.

Introduction

This procedure is for new vendor addition/ extending an existing vendor to a particular Purch. Org.

Vendors in SRM are replicated from ECC R/3 system. Usually a batch job runs in the background that will replicate the vendors from ECC to SRM in periodic routine. Here, in this document I will show you how to manually transfer/replicate a vendor from ECC to SRM.

Standard T. Codes for vendor org structure in SRM:

PPOSV_BBP       : Display Vendor
PPOMV_BBP       : Change Vendor
PPOCV_BBP       : Create Vendor

Pre-requisites:

For a fresh SRM installation the vendor root node is created in transaction PPOCV_BBP. And, if an existing SRM 4.0 system is upgraded to a later release then we need to run report BBP_XPRA_ORGEH_TO_VENDOR_GROUP from SE38 to get the vendor node created under Vendor Org Structure. Once Vendor root is created, we can proceed with the vendor transfer from R/3 to SRM system. Same can be displayed in transaction PPOSV_BBP.

In above figure, in right hand side panel window, Vendor Group assignment is the description of the supplier, Code is the supplier number, ID denotes the business partner ID and then comes the validity dates.

Number ranges

For number range definition of vendors, please refer to the following customizing:

1. Cross-Application Components > SAP Business Partner > Business Partner > Basic Settings > Number Ranges and Groupings > Define Number Ranges

Or

Use t-code SNRO and input object 'BU_PARTNER'. Here you should define an external number range which corresponds to the R/3 numbers.

2.Cross-Application Components > SAP Business Partner > Business Partner> Basic Settings > Number Ranges and Groupings > Define Groupings and Assign Number Ranges

Or

Use t-code BUC2 to check it

For each replication run, you can download the vendors which corresponds to the external number range / grouping which is marked as 'standard external'.

Creation/Addition of new Supplier in SRM system

New supplier is created in R/3 system and is replicated to SRM via BBPGETVD

Below is the example with step by step procedure for the same-

Create a vendor in ECC system-

Vendor account created successfully-

Now run BBPGETVD in SRM system to get the vendor from ECC to SRM system-

This will lead you to another window which will show the total no. of entries given and no. of updates possible. You can display list for your reference. And start transmission.

Check SLG1 for application log.

Vendor has been transferred successfully from R/3 system to SRM system.

Checking the same in SRM portal –

In this way a new Supplier is integrated to the SRM system manually.

Update Existing Vendor's Master records

This procedure is for updating data records for any existing vendor or extending a vendor to any purticular Purchasing organization.

T.Code- BBPGETVD – To transfer Vendor from ECC to SRM system. Enter the below required fields-

System represents the backend R/3 system from where vendor data has to be picked. Enter Supplier number and P.Org. To transfer a vendor without ref to any backend Purchasing Org, we need to check without reference to backend purchasing org. box and leave the Purchasing Organization filed blank.

To avoid any duplicity of the vendors check for the address comparison box and proceed.

Object ID is the Vendor Root ID (Refer PPOSA_BBP screenshot)

Select “Only transfer R/3 Numbers” radio button and Click “Start Transfer”. If vendor is not transferred via batch job then it will be transferred instantly else an information pop up will be displayed as shown below-

This, above message, shows that Vendor is already transferred to the SRM system.

Now we need to update the vendor master record using T.Code BBPUPDVD. This will update the vendor backend data from ECC to SRM.

Enter the below mentioned mandatory fields and click start transfer.

This will lead you to another window which will show the total no. of entries given and no. of updates possible. You can display list for your reference. And start update.

Vendor will be updated in SRM system with this.

Now we can check whether it went successfully or not. So for that analyze application log.

Tcode- SLG1–Give the accurate entry data to populate the required data only.

In case of any update failure, we can find the root cause for vendor update failure here and then it needs to be rectified from ECC front.

Click execute

Messages in red are errors else rest all means it went through successfully.

Log in to portal and specify vendor no. in search criteria.

We can find the Purchasing organization details under the Supplier data tab.

This shows Supplier has been extended to the SRM system for the required Purchasing organization.

Issue details :

Particular Users getting TIMEOUT Dumps while using perform sourcing in SRM Portal Application.

Whenever the user clicks on perform sourcing then it end with Connection Timeout screen and thereby generating TIMEOUT DUMP in the SRM System.

Below is the screenshot of the Portal Screen :

Cause :

Users must have checked the above highlighted option (Start Search Upon Opening Application)

All these customizing are stored in table /SAPSRM/SOCO_SET in SRM System.

Resolution:

Please follow the below steps to fix the above TIMEOUT issue :

1. Login into SRM system

2. Run Tcode SE16

3. Give the table name as /SAPSRM/SOCO_SET

4. Enter the user names in the search criteria who are facing the above mentioned issue.

5. The below entries can be seen :

    Observer the AUTOSTART Column for the users. Autostart option is enabled for the users who all are facing the TIMEOUT issues.

6. Select the users and delete their entries from the above table.

7. Once the entries are deleted; the issue is resolved.

------------------------------------------------------------------------------------------------------------------------------------

Recently some clients encountered problem while using live auction, and some documents or KBA note (For example, KBA 2075978) would suggest checking JCO settings first. However the path to check JCO settings changed a lot for different versions of NetWeaver. It would be difficult for some of you who are not familiar with EP.
Now I will show you the detailed path to maintain JCO settings:

For NW 7.0X (7.01, 7.02, etc), you have two ways to modify the properties.

A,  Visual Administrator

1. Launch the J2EE engine Visual Administrator.
   On Windows: Go to <drive:>usr\sap\<sapsid>\<instance number>\j2ee\admin and double-click go.bat
   On UNIX: Go to usr\sap\<sapsid>\<instance number>\j2ee\admin and run go.sh.
2. Navigate to the Configuration Adapter by choosing=>Server-> <instance number>->Services->Configuration Adapter
3. On the Display Configuration tab, choose=>Configurations->apps->sap.com->com.sap.srm.la->appcfg
4. Choose the icon with the quick info text Switch between view and edit mode
5. Double-click Propertysheet application.global.properties

A separate window containing the Change Configurations page opens and you can modify here

B, Configuration Adapter Service

1. Launch the J2EE engine Configuration Adapter Service.
   On Windows: Go to usr\sap\<sapsid>\<instancenumber>\j2ee\configtool\configtool.bat and double-click go.bat
   On UNIX: Go to usr\sap\<sapsid>\<instance number>\j2ee\\configtool\configtool.sh and run go.sh.
2. Choose the icon with the quick info text Switch to configuration editor mode.
3. On the Display Configuration tab, choose=>Configurations->apps->sap.com->com.sap.srm.la->appcfg
4. Choose the icon with the quick info text Switch between view and edit mode
5. Double-click Propertysheet application.global.properties

A separate window containing the Change Configurations page opens and you can modify here

For NW 7.3 & 7.4, you have to maintain this in NWA.

1. Go to the SAP NetWeaver Administrator using the following URL:http://<host>:<port>/nwa
2. Choose=>Operations->Systems->Start&Stop->Java Applications
3. Search for and select com.sap.srm.la
4. Choose More Actions
5. Choose View Application Properties
6. Under Extended Details select the property to be changed and modify it

market

In the service market place, for each version of SRM release, there are corresponding installation guide for live auction, but some version content is not accurate enough. Hence I suggest you download the following version if you would like to know more about this:

service.sap.com/srm-inst

Select "SAP SRM Server 7.02" (left menu)

    Select "Installation Guides for SRM 7.0 EHP2 "

      Select "3.Installation Guide - SAP enhancement package 2 for SRM 7.0 - ABAP and Java"

Best regards,
Ivy

Purpose:

One KBA note 1494536(EP-PIN-OBN) talked about the solution to solve such error in general.
However from application side, the solution is a little difficulty to understand. So I would like to create this document to show one example in SRM system.

Problematic Case:

This is just one example in SRM which would be convenient for our further analysis.
Steps to reproduce the error:
====
While clicking the link of contract owner in contract, error  “There is no iview available for system "SAP_SRM": object "bupa". For more information, contact your administrator.” is raised.
====

Analysis Method:

1.  Please make trace of this process with HttpWatch tool, and check ‘POST data’ as below:

Here, there are some important parameters: business object, operation, resolvingMode, source and systemAlias.

2.  Since resolvingMode is ‘SourceRole’ which means that this iView must be located in some specific portal role, it is necessary to get known about the target role.

To get what this portal role is, we can copy the value in ‘source’ field and translate it to exact portal role with the following method:

• For NW 7.0, please follow path ‘System Administration-> Navigation -> Short URLs’ and insert short URL which is character string in ‘source’ field. In this example it is “a5b4fd7de628b9fc60797c79ae86799b” .

•   For NW7.3, please follow path ‘System Administration-> System Configuration-> Runtime Settings-> Short URLs’.

3.  Please make sure that portal role is assigned to the portal user.

Go to tab ‘User administration’: search for portal user and go to tab ‘Assigned Roles’ to check if the target portal role is assigned.
If not, please add this portal role to this problematic portal user.

4.  Please make sure the relevant business object and operation exists in the portal and find out the target application (Here is iView) for the OBN action.

• For NW 7.0

     Go to ‘Content Administration’ and search ‘Business Object’. In this case, it is ‘bupa’.

     If you find out more than one similar BOs, please check the system alias in it, and in this case, it should be ‘SAP_SRM’.

    Then we should choose the relevant operation ‘readonly_emp’ and click ‘Display iView/Pages’ to show all the table results as below:

• For NW 7.3

        Go to ‘Content Administration’ and search ‘Business Object’. For example, the object is 'auctions'.
        Please click 'open object' to display it and navigate to 'Business Object'. After this, you have to click 'All implemented Targets' in order to expand all the operations, and choose the target operation and click 'Properties' to check the assigned iview.

From the table results, both iView/Page and location are listed.

In this case, the iView is "com.sap.pct.srm.core.iv_display_bp_emp_ro". Since SourceRole is set as resolvingMode, this iView should be located inside the portal role. And you have to assign this iView to this portal role.

After this, please check if the iView inside the portal role is tagged to the operation ‘readonly_emp’. If not, please also tag this iView to the operation.
(Please refer to the attachment in KBA 1494536 to tag application)

Hope this will be of help to solve the error in SRM application.

This article present benefit of leveraging FEH (Forward Error Handling) concept in SOA (Service Oriented Architecture) to monitor failed error messages and perform troubleshooting based on displayed error messages.

Sometimes SAP SRM Central Contract will not successfully distribute to ERP backend and we may not get detail error message from SRM Portal to perform further investigation.

As a prerequisite, FEH should be activated in SAP SRM as well as SAP ECC backend.

Below screenshot depicts this configuration in SAP SRM.

As an example, below is shown one SRM Central contract which has System Status as “In Distribution” meaning it is not successfully distributed to SAP ECC backend.

Based on SRM Portal screen it is very difficult and time consuming to find exact error why this SRM Central Contract unable to distribute to ECC.In this case FEH(Forward Error Handling) come as very useful tool to diagnose the issue.

Assuming all the required configurations are completed in SRM as well as ECC, execute transaction /SAPPO/PPO2 in SAP ECC.

Enter filter criteria as per your data requirement.

After executing the transaction we will get below screen with error message

Double click object/key to display detail message

From above screen it shows that Material is flagged for deletion. This is a reason for failure of distribution of contract to ECC.

This can also be verified by checking Material Status in SAP ECC

It is recommended to check this transaction /SAPPO/PPO2 in SAP ECC regularly to proactively monitor and resolve the issues identified based on the result of this transaction.

Networked Economy

1. 1.Analyze Spend to unleash potential savings and planning KPI targets @ Ariba Spend
2. 2.Conduct research for new sourcing plans and needs @ Ariba Discovery. Ariba does the matching for buyers/sellers
3. 3.Initiate RFP & Auction @ Ariba Sourcing
4. 4.Suppliers submit RFP responses @ Ariba Supplier Network
5. 5.Create contracts for winning suppliers @ Ariba Contracting
6. 6.Update contracts as catalogs for suppliers @ Ariba Procurement content
7. 7.All business users continue indirect procurement with SAP SRM 7.0
8. 8.All business users continue direct procurement with SAP S4/HANA
9. 9.Suppliers respond to all Purchaser Orders @ Ariba Network
10. 10.OR Suppliers can also receive PO @ XML/EDI
11. 11.Suppliers submit Invoices @ Ariba Network
12. 12.OR Suppliers can charge to Credit Card @ Ariba Pay [Presently Discover]
13. 13.Conduct Invoice Management @ SAP Open Text Add-on for ERP
14. 14.Release payments @ SAP ERP
15. 15.Suppliers receive all payment information @ Ariba Discounting [Ariba Supplier Network]
16. 16.Conduct Supplier performance @ Ariba Supplier Performance Management
17. 17.Manage suppliers @ Ariba Supplier Information Management

Migration Sequence

Upgrade to S4/HANA with Fiori Apps on the speed raceway

Migrate to Ariba Spend

Migrate to Ariba Sourcing, Contract Management with Procurement Content and Integrate with Supplier Network

Integrate Ariba Pay and Discount Management

Integrate and build Supplier Performance

System Integration

1. 1.SAP SNC Ariba Supplier Network*
2. 2.SAP ERP Ariba Supplier Network*
3. 3.Leverage SAP ERP Add On for Analytics with Ariba Spend, as required
4. 4.Ariba Contract Integration with SAP SRM (Indirect) & SAP ERP (Direct), as required

•Indicates learning opportunities for SAP Consultants

•Indicates Rapid Deployment Solutions [RDS] package availability for accelerated implementations

Disclaimer - Framework for Companies with Source to Settle Global Workforce over 10,000 and SAP SRM 7.0 On Premise Implementation

It is not possible to set the Central Contract status to Saved after mass update of the selected Contracts. As a result Purchase cannot enrich the document with specific details and release later.

Feature:

It is possible to set the Contracts to Saved status after a mass update to the Contracts. This  allows the purchaser to make common changes in the mass update transaction and later on update the individual contracts with specific changes before publishing.

Following check box is available in the Contract Mass Change second screen, Define Mass Change, to set the status of the Contracts to Saved status.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_3 and then activate the Customizing switch Mass Changes to Contracts(SRM_703_MC_ADD_STATUS) under SRM Server-> Continuous Improvement-> Activate/Deactivate Mass Changes to Contracts.

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

There is no option for an expert user to purchase some items on priority, by mentioning the follow-on document type as Purchase Order or Contracts for those Shopping Cart items and avoid bidding process. As a result he/she might have to wait till the entire biding process is over.

Feature:

There is an option for users with specific authorization to control the follow-on document that can be created for a shopping cart item which are relevant for sourcing. Purchaser can assign the follow-on documents applicable for items in a shopping cart. These follow-on documents appear against the items in the Carry Out Sourcing screen. The operational purchaser can then view, select, and assign only those follow-on documents for the item(s) in shopping cart. This enables faster purchasing of items relevant for sourcing.

Following Drop down field is introduced in Shopping Cart item details as part of this feature and the options appearing in the drop down can be configured.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_3 and then activate the Customizing switch Follow-On Documents for Shopping Cart(SRM_703_SC_FOLLOW_ON_IND) under SRM Server-> Continuous Improvement-> Activate/Deactivate Follow-On Documents for Shopping Cart.

The drop down entries for follow on documents can be configured under SRM Server-> Cross-Application Basic Settings-> Define Settings for Creation of Follow-On Documents in Shopping Cart.

Notes:

2087914 - SC New Filed For Follow-on Documents - Interface Note

2107661 - SC New Field for Follow-on Documents - Implementation Note

2108193 - New Field for Follow-on Documents - some improvements

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

Every user expects his/her shopping cart should convert into desired follow on document without any errors.As you aware every requisition is a critical business need and it must be procured from the external vendors.Every Requisition activity is very important for the business. SRM consultants must train the Business users and Buyers to use the application effectively.However there are some situations some of the shopping carts were failed due to many reasons like Master data (Material , Vendor and Finance data) issues, system issues , configuration while creation of purchase order. SRM system may not able to validate all the data while creating the shopping cart. Actually SRM is a very effective procurement system with tightly integrate to any ERP system/ Financial system. Unfortunately due to some Technical reasons SRM Requester never gets notification if any shopping carts failed after approval. These failed shopping carts are monitored by EBP administrator on daily basis. EBP administrator contacted the various master data team/Procurement team to correct the master data and helps to reprocess the shopping carts and make ensure that all failed shopping cart turned to follow on documents. Here there are some examples with error codes and solution.This document shall be useful for SRM beginners to address the issues.

Introduction

This procedure is for new vendor addition/ extending an existing vendor to a particular Purch. Org.

Vendors in SRM are replicated from ECC R/3 system. Usually a batch job runs in the background that will replicate the vendors from ECC to SRM in periodic routine. Here, in this document I will show you how to manually transfer/replicate a vendor from ECC to SRM.

Standard T. Codes for vendor org structure in SRM:

PPOSV_BBP       : Display Vendor
PPOMV_BBP       : Change Vendor
PPOCV_BBP       : Create Vendor

Pre-requisites:

For a fresh SRM installation the vendor root node is created in transaction PPOCV_BBP. And, if an existing SRM 4.0 system is upgraded to a later release then we need to run report BBP_XPRA_ORGEH_TO_VENDOR_GROUP from SE38 to get the vendor node created under Vendor Org Structure. Once Vendor root is created, we can proceed with the vendor transfer from R/3 to SRM system. Same can be displayed in transaction PPOSV_BBP.

In above figure, in right hand side panel window, Vendor Group assignment is the description of the supplier, Code is the supplier number, ID denotes the business partner ID and then comes the validity dates.

Number ranges

For number range definition of vendors, please refer to the following customizing:

1. Cross-Application Components > SAP Business Partner > Business Partner > Basic Settings > Number Ranges and Groupings > Define Number Ranges

Or

Use t-code SNRO and input object 'BU_PARTNER'. Here you should define an external number range which corresponds to the R/3 numbers.

2.Cross-Application Components > SAP Business Partner > Business Partner> Basic Settings > Number Ranges and Groupings > Define Groupings and Assign Number Ranges

Or

Use t-code BUC2 to check it

For each replication run, you can download the vendors which corresponds to the external number range / grouping which is marked as 'standard external'.

Creation/Addition of new Supplier in SRM system

New supplier is created in R/3 system and is replicated to SRM via BBPGETVD

Below is the example with step by step procedure for the same-

Create a vendor in ECC system-

Vendor account created successfully-

Now run BBPGETVD in SRM system to get the vendor from ECC to SRM system-

This will lead you to another window which will show the total no. of entries given and no. of updates possible. You can display list for your reference. And start transmission.

Check SLG1 for application log.

Vendor has been transferred successfully from R/3 system to SRM system.

Checking the same in SRM portal –

In this way a new Supplier is integrated to the SRM system manually.

Update Existing Vendor's Master records

This procedure is for updating data records for any existing vendor or extending a vendor to any purticular Purchasing organization.

T.Code- BBPGETVD – To transfer Vendor from ECC to SRM system. Enter the below required fields-

System represents the backend R/3 system from where vendor data has to be picked. Enter Supplier number and P.Org. To transfer a vendor without ref to any backend Purchasing Org, we need to check without reference to backend purchasing org. box and leave the Purchasing Organization filed blank.

To avoid any duplicity of the vendors check for the address comparison box and proceed.

Object ID is the Vendor Root ID (Refer PPOSA_BBP screenshot)

Select “Only transfer R/3 Numbers” radio button and Click “Start Transfer”. If vendor is not transferred via batch job then it will be transferred instantly else an information pop up will be displayed as shown below-

This, above message, shows that Vendor is already transferred to the SRM system.

Now we need to update the vendor master record using T.Code BBPUPDVD. This will update the vendor backend data from ECC to SRM.

Enter the below mentioned mandatory fields and click start transfer.

This will lead you to another window which will show the total no. of entries given and no. of updates possible. You can display list for your reference. And start update.

Vendor will be updated in SRM system with this.

Now we can check whether it went successfully or not. So for that analyze application log.

Tcode- SLG1–Give the accurate entry data to populate the required data only.

In case of any update failure, we can find the root cause for vendor update failure here and then it needs to be rectified from ECC front.

Click execute

Messages in red are errors else rest all means it went through successfully.

Log in to portal and specify vendor no. in search criteria.

We can find the Purchasing organization details under the Supplier data tab.

This shows Supplier has been extended to the SRM system for the required Purchasing organization.

In the past customers have complained about the slow response time while working with business documents containing thousands of item.

Feature:

Usually, when an user works with large business document like Contract, RFx etc., he/she would be working with small subset of items at one point of time.

Utilising this knowledge from customers,search based lazy loading is enabled for item(s) for large documents. superior response time and end user experience is rendered with possibility of loading what the items end user is interested to work with. Use of SAP HANA as underlying database delivers immense value and generate breathtaking response time. Large document handling (LDH) for a business object allows a purchaser to work on a definite set of line items of a business object.While displaying a large document no items are loaded.

Display of Business Document in LDH mode:

When a business document is displayed in LDH mode, none of the items are loaded by default. Only the header information are displayed to the user.

Search for items:

There is a detailed search criteria to enable user to find the required items. User can also save preferred search criteria as variants and use them for future searches. This increases time efficiency by reducing the search efforts.

Handling of header actions:

In LDH mode, certain header actions are processed in the background which helps completing the activity in no time. On completion of the background processing, user will receive an e-mail notifying the same. In case the background processing fails, user will receive an e-mail with the error details for that document.

Document check event results into foreground processing for header and currently loaded items . Complete document check is performed in background. User can view the messages logged during background processing of check under the new Message tab on the Overview screen of the document.

Handling of item actions:

Deletion of items from a document opened in LDH mode can be done by choosing the Delete and Save button. Deletion of items is processed in the background. User will receive an e-mail notification on completion of the background action. User can also view all the details and messages in the application log.

Items copied in a large document are always pasted at the end. Since user has an option to search for related items, there is no business need for Cut and Paste or Move up and Move down option and hence these actions are not available.

Large Document handling is enabled for Contracts and RFx. You can maintain the threshold for Large Documents. Documents containing number of items equal to or crossing the threshold will be displayed in LDH(Large document handling) mode and the above mentioned features will be available for the same. In the customizing user can also maintain the threshold for displaying the search result soon after search and this helps to have a preview of the result and help drill down further if required.

Customizing to define LDH threshold:

LDH threshold can be defined under SRM Server-> Cross-Application Basic Settings->Large Document Handling-> Define Threshold values for Large Document Handling.

Large Document Handling for Contracts:

Following header actions are performed in background for Contract opened in LDH mode:

Copy, Print preview, Export, Import, Create template, Check, Delete, Renew, Release, Accept, Register, Submit and Review

To use the feature, you have to first activate the Business Function SRM_LDH_3 and then activate the Customizing switch Large Document Handling for Central Contracts(SRM_703_LDH_CTR) under SRM Server-> Cross-Application Basic Settings->Large Document Handling-> Activate/Deactivate Large Document Handling for Central Contracts.

Large Document Handling for RFx:

Following header actions are performed in background for RFx opened in LDH mode:

Copy, Print preview, Export, Import, Create template, Check, Delete, Publish and Convert to Auction

To use the feature, you have to first activate the Business Function SRM_LDH_3 and then activate the Customizing switch Large Document Handling for RFx(SRM_703_LDH_RFX) under SRM Server-> Cross-Application Basic Settings->Large Document Handling-> Activate/Deactivate Large Document Handling for RFx.

Purpose:

One KBA note 1494536(EP-PIN-OBN) talked about the solution to solve such error in general.
However from application side, the solution is a little difficulty to understand. So I would like to create this document to show one example in SRM system.

Problematic Case:

This is just one example in SRM which would be convenient for our further analysis.
Steps to reproduce the error:
====
While clicking the link of contract owner in contract, error  “There is no iview available for system "SAP_SRM": object "bupa". For more information, contact your administrator.” is raised.
====

Analysis Method:

1.  Please make trace of this process with HttpWatch tool, and check ‘POST data’ as below:

Here, there are some important parameters: business object, operation, resolvingMode, source and systemAlias.

2.  Since resolvingMode is ‘SourceRole’ which means that this iView must be located in some specific portal role, it is necessary to get known about the target role.

To get what this portal role is, we can copy the value in ‘source’ field and translate it to exact portal role with the following method:

• For NW 7.0, please follow path ‘System Administration-> Navigation -> Short URLs’ and insert short URL which is character string in ‘source’ field. In this example it is “a5b4fd7de628b9fc60797c79ae86799b” .

•   For NW7.3, please follow path ‘System Administration-> System Configuration-> Runtime Settings-> Short URLs’.

3.  Please make sure that portal role is assigned to the portal user.

Go to tab ‘User administration’: search for portal user and go to tab ‘Assigned Roles’ to check if the target portal role is assigned.
If not, please add this portal role to this problematic portal user.

4.  Please make sure the relevant business object and operation exists in the portal and find out the target application (Here is iView) for the OBN action.

• For NW 7.0

     Go to ‘Content Administration’ and search ‘Business Object’. In this case, it is ‘bupa’.

     If you find out more than one similar BOs, please check the system alias in it, and in this case, it should be ‘SAP_SRM’.

    Then we should choose the relevant operation ‘readonly_emp’ and click ‘Display iView/Pages’ to show all the table results as below:

• For NW 7.3

        Go to ‘Content Administration’ and search ‘Business Object’. For example, the object is 'auctions'.
        Please click 'open object' to display it and navigate to 'Business Object'. After this, you have to click 'All implemented Targets' in order to expand all the operations, and choose the target operation and click 'Properties' to check the assigned iview.

From the table results, both iView/Page and location are listed.

In this case, the iView is "com.sap.pct.srm.core.iv_display_bp_emp_ro". Since SourceRole is set as resolvingMode, this iView should be located inside the portal role. And you have to assign this iView to this portal role.

After this, please check if the iView inside the portal role is tagged to the operation ‘readonly_emp’. If not, please also tag this iView to the operation.
(Please refer to the attachment in KBA 1494536 to tag application)

Hope this will be of help to solve the error in SRM application.

Purchasers often has to enter conditions with a different currency than the one maintained in the contract. A typical example would the freight cost which is often negotiated in US Dollar. However conditions with different currencies are not supported in Central Contracts. All the conditions are defaulted to the currency maintained in the Central Contract.

Feature:

This feature enables user to maintain conditions with different currencies in Central Contract both at header and item level. For example, if an item’s price is maintained in EUR in the central contract, you can maintain any condition such as discount absolute for the same item in USD.

The currency field is enabled for conditions which are not of percentage type.

While negotiating a Central Contract with conditions maintained in different currencies, the different currencies are carried forward to RFx and RFx Response as well. As a result, bidder can create response by mentioning condition values in different currencies. The different currencies maintained for conditions in Central Contract needs to be maintained in RFx as allowed exchange rates in order to allow the bidder to change the currency in Response.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_3 and then activate the Customizing switch Multiple Currencies for Conditions in Contract(SRM_703_MUL_CUR_CTR) under SRM Server Continuous Improvement Activate/Deactivate Multiple Currencies for Conditions in Central Contract.

For complete details about SAP SRM 7.03 refer: SAP SRM 7.0 Enhancement Package 3

     It was not possible for the user to create and save templates which could be later on used as notes in business documents.

Feature:

     This feature enables users to create, save and use text templates for notes in the following business documents:

          Shopping Cart

          Purchase Order

          RFx

          RFx Response

          Central Contract

     Under Notes and Attachments while adding a note, user will get the following popup. For creating/updating a text template, user will have to enter a text template name and select the checkbox, 'Create or Update Templates'. Now whichever text is entered will get saved or updated.

     In order to use an existing template user will have to enter the text template name and click on 'Go' button. The saved text will get displayed and this can be added as a note in the business document.

     Templates can be created for each note type and can be used across business documents for which text template is enabled.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_3 and then activate the Customizing switch Text Templates for Notes(SRM_703_TEXT_TEMPLATE) under SRM Server Cross-Application Basic Settings Text TemplatesActivate/Deactivate Text Templates for Notes.

Text template feature for business objects can be enabled under the customizing: SRM Server Cross-Application Basic Settings Text Templates Define Business Objects for Text Templates.

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