Deployment Scenario - Standalone

This article will give an idea when a customer/client should go for standalone scenario.

Since there are 4 deployment scenario in SRM and when and why we should choose these scenarios. This post will focus on "Standalone Scenario"

In standalone scenario the leading system is SRM since there is no "SAP-Material Management " system available,  All the procurement activities will happen in SRM and the invoice is created in Backend SAP-FI

Custom Attribute Creation in SRM

The following procedure needs to follow to create a z Attribute in SRM

• Go to Tcode SM30 and input the name of the table "T77OMATTR" and click on "Maintain"
• You can  click on "New Attributes " (or) copy the previous attribute and do the necesssary changes

Vendor Structure in SRM 7.0(PPOMV_BBP)

When we upgrade SRM System from SRM 4.0 to SRM 7.0  then we need to do Vendor Structure Migration.

We need to follow the list of things before we start migrating vendor strucutre in SRM 7

Deployment Scenario of SAP-SRM

Deployment Scenarios of SRM

There are 4 standard Deployment Scenarios in SRM.

1. Classic
2. Extended Classic
3. Standalone
4. Decoupled