In Classic scenario the leading system is the Backend R/3 System. Classic Scenario is the first scenario of SRM, This scenario is mainly used by clients/customers who have strong backend system and only part of the procurement activity takes place in SRM in capturing the requirements from enduser in form of Shopping carts.
Classic Scenario supports SUS-MM ( Supplier Self Service with Material Management )
Overview of the Process
Configuration part of Classic Scenario.
The following config settings needs to be configured in your SRM system
1) Generation of Roles (Tcode PFCG)
2)Define Logical Systems (Tcode BD54)
3) Assign Logical System to Client (Tcode SCC4)
4)Define SRM Logical System in Backend R/3 System, (Tcode SALE)
5)Define RFC User ( This user will used to connected R/3 System)
6)Define RFC Destination (T code SM59)
7)Define RFC Destination in R/3 System (Tcode SM59)
8)Maintain table TWPURLSVR from Tcode SM30
Once these activities are done we should replicate Master data.
Under Master data there are two major master data that we should replicate from R/3 System.
Material Master
Vendor Master.
In the next post we will see the other side of the configuration of Classic scenario where we will see Vendor Replication , Master Data Replication and other config settings required for Classic Scenario
Classic Scenario supports SUS-MM ( Supplier Self Service with Material Management )
Overview of the Process
- End user Creates a Shopping cart
- SRM System triggers approval flow for the shopping cart created. Once approval flow got triggered respective work item goes to manager's inbox for approval. Once the approval is done then Follow-on-document will get created for the Shopping cart which created .
- Config Path : SRM Server->Cross-Application Settings->Define Objects in Backend System. This setting will identify the type of Follow-on-document that should get created. It can create a Purchase Requistion , Purchase Document (or) a Reservation depend upon the product category that is selected.
- For Example ( <Product Category> < Backend R/3 System> <PR,PO,Reservation).
- The Product category is your material group and the Backend R/3 System is your SAP MM System and from the drop down you can select the type of Follow on document that should created for that particular product category
- Once a Follow-on-document is created Goods Receipt(GR) and Invoice and be posted from either SAP SRM or directly from SAP R/3 System.
Configuration part of Classic Scenario.
The following config settings needs to be configured in your SRM system
1) Generation of Roles (Tcode PFCG)
2)Define Logical Systems (Tcode BD54)
3) Assign Logical System to Client (Tcode SCC4)
4)Define SRM Logical System in Backend R/3 System, (Tcode SALE)
5)Define RFC User ( This user will used to connected R/3 System)
6)Define RFC Destination (T code SM59)
7)Define RFC Destination in R/3 System (Tcode SM59)
8)Maintain table TWPURLSVR from Tcode SM30
Once these activities are done we should replicate Master data.
Under Master data there are two major master data that we should replicate from R/3 System.
Material Master
Vendor Master.
In the next post we will see the other side of the configuration of Classic scenario where we will see Vendor Replication , Master Data Replication and other config settings required for Classic Scenario
No comments:
Post a Comment