SAP SRM Challenges

Service Procurement in SRM

2013-09-27T23:35:00.001+05:30

Service Procurement is much more complex than Material. SRM supports both Material and Services. In this post we will see the how Service Procurement is handled in SRM

Purchasing Org and Purchasing Group in SRM

2013-03-28T14:52:00.004+05:30

Purchasing Group

Purchasing group in SRM is linked with ECC/MM System. We link Purchasing group and purchasing org from org sturucture

Steps that we follow to config purchasing group and purchasing org from R/3

1. Go to PPOCA_BBP and create a Root node

2. Right click on the “New Organization Unit” and click on Create , to create a new org unit

3. Select “Is line supervisor of Organization unit”

4. Go to Function tab of the newly created org unit

5. Clcik on “Purch Organization” and select the Purchasing Org and select R/3 system from the drop down .

6. Once Purchasing Org is maintained we need to maintain purchasing group, The procedure is same create a new Org unit and go to Function tab and now Purhchasing group is active

7. Now click on Purchasing group and assign the purchasing group and the R/3 System

8. Once this is done then purchasing org and group is maintained.

9. Once the purchasing group is maintained we need to maintain Responsibility tab as well

10. Here the responsible product category and the “Organizational Responsibility” should be maintained

SRM G/L Account Determination.

2013-01-31T20:22:00.001+05:30

I have seen people searching for how G/L account is getting determined in SRM. So thought of explaining this to users.

It's very simple. If you see the config

SRM Server->Cross Application Basic Settings->Account Assignment-> G/l Account Determination for product category.

Basically G/L is determined from this Configuration. So depend upon the product category G/L Account will be displayed on the portal.

For example:

Product category G/L Account
P12345 5001234

So when ever user selects "P12345" as product catetegory the appropriate G/L account will be picked up by the system and displayed on portal.

Organization Structure Relationship (PPOSA_BBP)

2012-11-16T16:06:00.000+05:30

We usually try to assign users in Org Strctures either by creating a new postion and assigning the user id to it (or) Drag and drop.

There is one more way by which you can assing the user which is there in Org id A to Org id B. This is a standard procedure and you can follow it

Go to Tcode P013 and input the postion Number

Enter the postion number and select "Relationship and clcik on "Edit"

In the above screen shot you can see that there is a filed called "ID of the related Object". This is actually the link between the Org id and the Postion. So for example if it is assigned to Org id 500000 and if you input 500001 in the filed then the postion will get assigned to that particualr ID.

Instead of Drag and drop you can directly do it this way or else the tables that store these relationship are as follows
HRP1000
HRP1001
HRP5500.

Here also via bebugging you can change the Id of the related object. But by doing PO13 is a safest way and easiest.

BRF Process

2012-11-15T17:15:00.003+05:30

We are all know that BRF (Business Rule Framework) is part of SRM 6 Onwards. Instead of going on technical, In this post I provide you the basic understanding of the BRF. When BRF is created and what all it does in the system to retunn the value

This is what basically BRF does.

Once a user creates a SC
System triggeres a WF Template
This template checks the process shcema (which is already defined) evaluation and filters
Depend upon the Filters & Process Schema BRF Event is triggered
This BRF Event calls "Rules & Expressins" and returns a result (For Example in case of Boolean it will retrun TRUE or FALSE)
If the resutl is TRUE then Process schema1 gets exected
If the resutlt is FASLE then Process Schema 2 gets executed
Both intern will call WF WS40000014
So when Process Schema 1 is triggered then Process level 1 gets executed which intern retrun Agent

Once the WF gets the agent then it will display those Agents in WF Preview and once you order the SC then WF gets triggered and the WI is sent to repsective Agents for approval.

Delete Vendor from SRM

2012-09-14T14:34:00.003+05:30

The common issue what we used to get is to delete the vendor from SRM. SAP has provided with a standard report "BUPA_TEST_DELETE" or you can use Tcode bupa_del by either of them we can delete the vendor from the SRM.

This actually deletes the BP Number form the System. So for example you have a vendor 10001234 and this BP Number also is the same and you don't require this vendor in you SRM System.

Execute the report and input the vendor and uncheck all the Checkboxes which you see on the screen and execute . Once executed the report shows that that particular Vendor is deleted from the system and you can cross check tables like VENMAP and BUT000

User is not able to create shopping cart

2012-09-13T17:12:00.001+05:30

User is not an EBP User

This is the basic issue what we face whenever a user is new to Procurement system (SRM) and his user id is created but not able to create Shopping Cart

If we see in Org Strucutre PPOSA_BBP and search for the user then you will be able to find the user but if we see closely the BP Number will not be available to that particular user. This means that the user id is created but he is not a BBP User , In other words we can see user is not a SRM User and will not be able to create Shopping cart.

To creat a BBP User or User can be able to create Shopping cart. All you need to do is assign BP Number to that user ,Once user is assigned with the BP Number then you can define the attributes. Then the user should be able to create Shopping cart .

So inorder to assing BP Number we have to do the following things in SRM System

Go to Users_Gen
Click on "Copy User and Employee data from Template"
Select radio button "Create Users from Existing SUO1 Profile" and click on "Execute Action"

Once you click on "Execute Action" in the next screen you need to input Org id where the user should get assigned

When you click on "Continute" then a popup box comes up where it asks for all users or Area of users , If BP number needs to be generated for all the users the select radio box "All users" (or) if only one user needs the BP Number assignemnt then select "Area of Users" and input his id.

System search's for the user id and will display the details. Select the check box against that user id and press enter. Now the activity will be carried out sucessfully.

Now go to PPOSA_BBP Tcode and see the BP Number will be generated to that user. Go to Attributes and assign the values to these attributes like Account Assignment Catagory , Document Type in R/3 , Company code,Cost center. e.t.c.,

Once this id done the user should be able to create Shopping cart.

BRF Configuration Part - 1

2012-08-07T16:32:00.000+05:30

BRF (Business Rule Framework)

In this Article we will see the basic config settings required for the BRF.

BRF Stands for Business Rule Framework. Here we will see the configuration required for BRF.

If we see the config the BRF is categorized into 3

Technical Configuration

BRF Configuration

Business Process Configuration

Technical Configuration:

Customize SAP Business Workflow Automatically

( Tcode ACWF (or) Program BBP_AUTO_CUST)

Here we can do the automatic customizing of the workflow, This must be done on client-specific and it does not cover task specific customizing, that is assignment between taks and possible agents.

These are the following steps we need to follow

1. Choose Perform Automatic Workflow Customizing.

2. See whether the check results listed are all correct.

3. Choose RFC Destination Info

4. Choose Start Verification Workflow.

Check Event Trigger Configuration

Tcode SWDD

In this task we can check whether Main workflow “WS 40000014” can be started with an event. We need to follow the below steps

1. Enter the main workflow name WS40000014 into the Workflow field.

2. Choose Goto -> Basic Data.

3. Choose Start Events and check whether a new event has been created.

Check Event Type Linkage

Here we check the Event type linkage , The following entry should have maintained with “Type Linkage = Type equation here.

Generalize Tasks

In this activity we will set all tasks of task groups TG 40000003, 40000005, and TG 40000007 as “General”. So that these tasks can be processed by all users

Check Task Generation

In this Customizing activity, you check whether all tasks are delivered as general tasks

Check Task Consistency

This activity is used to check whether the Task is consistent or no

Copy BRF Objects

Program : BRF_TRANSPORT_SIMPLE

Tcode : /SAPSRM/BRFTRANSPORT

This is a report when executed the BRF objects specific to SRM will be transported to a sandbox system.

Process flow

1. Define events

2. Define expressions

3. Define groups

If you don’t have authorization then go to table TSTC and input the Tcode you will get the program name “BRF_SCREEN_START”

Define Events

Once you click on “Define Events” the following screen comes up, Events are used to execute process levels and to define how a workflow runs.

Each process level is assigned to an event.

This event connects a level in the level table “SAPSRM/VC_WF_P” with rule evaluation.

Which is used to determine whether this level is required for a document.

An event contains expressions that access fields of a document for example, the product category of an item. In this way, document data can be used to determine whether an approval step needs to be activated.

The event provides the value 'true' (the level is not required) or 'false' (the level is required).

Created one Application Class and Events

Define Events

Right click on “events “ and click on “Create Events”

Select from the F4 Help(Impl Class), Under Event Enter the Event Name and event gets created

So when you create a Event then there are two classes gets assigned to your event

CL_DET_ASSIGNMNT_RL_BRF

CL_DET_ASSIGNMNT_RS_BRF

You can define your own class for the event

Define Expression

To create Expression Right click on “Expressions” and click on “Create Expression”

When we create Expression then we need to input the Impl Class which you can select from the F4 Help

Once you select the Impl class click on “Enter”

So we have defined a Constant Event

In the above screen shot we have created an event and an expression

Define Groups

Here we create groups to group together Business Rule Framework Objects of the same area

In the Next Post we will see "Business Process Configuration".

Vendor Creation in SRM 7.0

2012-06-19T16:40:00.001+05:30

We offenly replicate vendor master data from R/3 System whether it's classic and Extended Classic. When a customer goes for Standalone scenario to implement all the master data should be created in SRM itself since ther is no Backend Material Manangement System.

In this post we will see how to create vendor in SRM. This process is simple you just need to go to Tcode BBPMAININT

Here in this screen for Business Partner as enter "BBP000" -This is a Vendor role in SRM. Once you enter the role we need click on "Create"

We need to fill all the data like as follows

Central Data for Business Partner
Address Data for Business Partner
Contact for Business Partner
Fax Numbers
E-Mail Addresses
Send Medium
Tax Numbers for Business Partner

We can see the Business Partner Type, Based upon the role which we have used "BBP000" the checmark for Supplier and Bidder will be checked default. There is a checkbox called "Portal Supplier" , You can make this vendor as a Portal Supplier which is used in SUS (Supplier Self Service)

Once you fill all the data click on Save. You will see that a message some thing like this "Business partner test (partner number XXXXXX) was created, and linked to organizational object "VGXXXXXXX".

This how you can create a Business Partner as Vendor.

Business Addin Part - II

2012-06-18T14:58:00.004+05:30

In this Post we will see the other badi's useful for self service procurement

Badi Name: BBP_DETERMINE_ACCT

Purpose To determine the G/L Account of your defined criteria

This badi is used to determine your own G/L Account. If we see standard there is a config. In Standard SRM System the G/L account is determined by configuration.

If we see the configuration under SRM Server->Cross-Application Basic Settings ->Account Assignment->Define G/L account for product category and Account Assignment Category

This is the config where we need to maintain the G/L account for a particular Product Category.So this badi can be used to determine your own cirteria for the G/L determination based upon the product category. This badi has only one method called " DETERMINE_ACCOUNT", This method has two parameters

ITEM_DATA
ACCT_DATA

Badi Name: BBP_DETERMINE_LOGSYS

Purpose: To determint backend system and company code based upon cirteria

As the name suggests that it determines the logical system. So this badi is used to define your own criteria for determining of Backend sytem and company code. If we see standard there is a config to maintain this. Under SRM SERVER-> Technical Basic Settings->Define Backend System for Product category

We can overwrite this by using own criteria and that is being passed to this badi for determination of Logical system

This badi has two methods
DETERMINE_LOGSYS-> Use this method to determine the backend system for the Shopping Cart
CONTRACT_LOGSYS_DETERMINE-> Use this method to determine backend sytem for the contract.

Badi: BBP_DOC_CHANGE_BADI

Purpose:Making changes to the document

This badi is a filter dependent badi which is used to do changes to the document.This badi has following mehtods
BBP_BID_CHANGE
BBP_AUC_CHANGE
BBP_QUOT_CHANGE
BBP_CONF_CHANGE
BBP_SC_CHANGE
BBP_PO_CHANGE
BBP_IV_CHANGE
BBP_CTR_CHANGE
BBP_SUSPCO_CHANGE
BBP_SUSPO_CHANGE
BBP_SUSASN_CHANGE
BBP_SUSINV_CHANGE
BBP_PCO_CHANGE
BBP_SUSCF_CHANGE

You can use this badi and implement it for the above object types.

Badi: BBP_DOC_SAVE_BADI

Purpose: To update Data at the time of saving document

This badi also is a Filter dependent badi, This badi is used basically to update/save user data while saving the document. This badi has one method called "BBP_DOC_SAVE"

Badi : BBP_TARGET_OBJTYPE

Purpose: To determine backend target system by defining user criteria.

This is a Filter Dependent badi. There is a config for the determinaiton of the object type.
Path: SRM Server->Cross Applicaiton Basic Settings->Define Objects in Backned System . By implemnting this badi you can define you own cirteria for determination of the object type. This badi has only one method "DETERMINE_TARGET_OBJECT_TYPES"

Badi:BBP_WFL_APPROV_BADI

Purpose: To implement n-Step approval workflow

This badi is a Filter Depedent badi, This badi is implemented when you are defining the n-step approval flow for the Shopping carts. This Badi has two methods
GET_REMAING_APPROVERS -Determines the Approvers and the Approval Steps
SET_APPROVAL_DESCRIPTION- Allows (Lang.Dependent) Setting of Step Description

SRM Business Add in (Badi) - I

2012-06-11T12:02:00.000+05:30

Business Add in

Business Add in as well call it as Badi's are the integral part of SRM. To give an overiview of what is badi it is just a enhancement point where the customer can add their custom process by doing ABAP coding. Badi's are Object Oriented enhancement spot (or) Badi is a standard exit where customers can customize the business process according to them and without changing any system modification.

In this Post we will see few badis that are used most commonly

We will seee few Badi's in this part and rest of the badis in the next post.

BBP_BS_GROUP_BE

This is a filter dependend Badi ,This badi has the following methods

Methods:
GROUP_PO_BACKEND
GROUP_RQ_BACKEND
GROUP_RS_BACKEND
GET_NUMBER_OR_RANGE

GROUP_RQ_BACKEND- If we define this method then we can define our own logic of grouping PR. Purchase Requistions can be grouped togher depend upon the document type

GROUP_PO_BACKEND - PO items can be groupded together in a better way.

GROUP_RS_BACKEND- This method is used for Reservations. As per standard only one Reservation is created for a particular item, But this standard procedure can be overwritten by implementing this method.

GET_NUMBER_OR_RANGE- By implementing this mehtod we can overwirte the number range for PO, PR and Reservations

BBP_CATALOG_TRANSFER

We use this badi inorder to change the data from the catalog to SRM. When we do changes to this badi then there will be an impact on Business functions like GR Confirmation and Service Entry and this is a Filter Dependend Badi. This badi has one method called "ENRICH_ITEM_DATA"
When end user tries to add a item from the catalog then Function module gets triggered 'BBP_WS_IMPORT_SC_DATA'. After the system picks the item from the catalog. System converts the ISO , Currency, Price to Standard SAP Format.

If the material master is transfered from the catalog then system tries to fetch the product number from the Standard table COMM_PRODUCT and transferes

This method has following parameters

BBP_CHNG_AGNT_ALLOW:

We can use this badi inorder to add/change the approvers in the workflow preview. This Badi has the following methods

AUTHORISE_FOR_CHANGE -This method is used to change the approver

AUTHORISE_FOR_INSERT - This method is used to add the approver

BBP_CREATE_BE_PO_NEW

This Badi is used to change the data while SC is creating a Purchase Order aganist that particular Shopping Cart. This Badi has two methods

FILL_PO_INTERFACE - This methods gets triggered when bapi "BAPI_PO_CREATE1" is called

FILL_PO_INTERFACE1- This methods gets triggered when bapi "BAPI_PO_CREATE" is called

BBP_CREATE_BE_RQ_NEW

This badi is used to change the data while you are creating a Purchase Requistion (PR) aganist that particular Shopping cart. This Badi has only one method called "FILL_RQ_INTERFACE". Bapi "BAPI_REQUISITION_CREATE" calls this method to create a PR in the respective Backend System.

BBP_CREATE_BE_RS_NEW

We use this badi to create a Reservation aganist a parituclar SC in the backend system. This badi has two methods:

FILL_RS_INTERFACE1 - This mehtod gets triggered when we use bapi API_RESERVATION_CREATE1"
FILL_RS_INTERFACE- This mehtod gets triggered when we use bapi "BAPI_RESERVATION_CREATE"

These are the badi's which needs to be active in your system when you have implemented Self Service Procuremente.will see other badi's related to Self -Service procurement in the next post. If you want to view what are all the badi's activated in your system landsapce then go to Tcode SE95 and check it out.

SRM Business Scenario Overview

2012-06-07T11:49:00.000+05:30

In this post we will see the list of SRM business scenarios SAP offers to the customer. This post is just an overviw of the business scenarios SAP offers to customers. We will see much more on the below scenarios in the coming posts.

SRM is implemented in different business scenarios, where SRM acts as a central procurement system. The following are the list of SRM Business scenarios (or) Implementation scenarios.

Self Service Procurement
Plan Driven Procurement
Service Procurement
Catalog Content Management
Spend Analysis
Supplier Collaboration
Operational Contracts
Sourcing with RFX / Live Auction
SAP PPS( Public Procurement Sector).

All the above scenarios are fit into the following Major procurement process

Operational Procurement

Sourcing

Supplier enablement

Within Operational Procuremnt the following Busincess scenarios comes under this.

Self Service Procurement
Plan Driven Procurement
Service Procurement

Under sourcing the following Business process comes under this

Catalog Content Management
Stategic Sourcing
Contract Management
Spend Analysis

Supplier Enablement where suppliers be a part of the entriprise, So under this Major business process the following Business process comes under this

Supplier Self Registration
Collaborative Replenishment
Desing & Order Collabration

Self Service Procurement can be implemented in Classic , Extended Classic and standalone as well. So when we implement Self Service Procuremtn in Classic scenario then the process flow happens

Plan driven procurement can be implemted with Extended Classic Scenario

Service Procurement can be implemented in Classic Scenario.

CCM Can be implemented either in Classic and Extended Classic

Vendor Replication in SRM 7.0

2012-05-31T16:41:00.000+05:30

Vendor Master Data Replication from R/3 System haven't chagned much in SRM 7.0 We still use the same old procedure to Replicate Vendor Master Data from R/3 System. The only thing that is changed is the Vendor Organization Strucutre.

From SRM 5.0 (or) Higer the Vendor Organizaiton Structure is available. We will see how to create a Vendor Oranziaiton Structure and the Replication of the vendors.

Following Tcodes shoule be used to create/maintain/display vendor organization structure.

PPOCV_BBP - Create Supplier Groups
PPOMV_BBP-Change Supplier Groups
PPOSV_BBP- Display Supplier Groups

First of all we need to create a Supplier group by executing Tcode PPOCV_BBP

Dates will be taken automatically, So just click on "Continue" or press enter

Enter the Object |abbr as your Object id and Name it as as per the requirement. Once this is done, Click on Save. Go to Attributes tab and input the values to the attributes Like Accounting System for the vendor, Company code,e.t.c, and click on Save.

Once this is done you will get a Vendor Group Number . Now go to BBPGETVD Tcode input the Object id as the new vendor group which was created earlier, Select system from the drop down box and in supplier text box insert the vendor number (or) range of vendors, Clcik on "Start Transmission" push botton in order to replicate vendor from R/3 and in the next screen clcik on "Start Transfer".

By doing this the vendor gets replicated to SRM System. Go to Tcode SLG1 to check whether the vendor is replicated or it has any errors, If it has errors then we need to correct those in R/3 and repeat the procedure.Go to table VENMAP and check there will be an entry of the newly vendor replicated

Organization Structure in SRM

2012-05-29T17:27:00.004+05:30

Organziation Creation

The basic and the important task in SRM is to create a Orgranizaton Strucutre. There are few steps that needs our attention before creating a Organizaiton Strucutre. SRM Organizaiton Structure provides to execute all the business transactions from the Portal, By creating requirements in form of Shopping cart.

Organization structure creates a hierarchy for the organization where there are plenty of departments who execute busisness transactions on day to day.

Before creating a org structure we should make sure the Master data is replicated and the Basic settings are configured.

Once these Settngs are configured. You can go ahead and create a Organization Strucutre.

Go to Tcode PPOCA_BBP of config path SRM Server->Cross Application basic settings->Organizational Management

Click on "Create Organizational Plan"

Enter the Name of your Company and click on Save
Fill the Basic data tab and Address tab, Go to Functions Tab and input the Company code and the respcective R/3 System
Create a Purchasing Organization and a Purchasing Group by right clicking on the Org node which is created(company root node)
Once a Purchasing Org is created, Update the Basic data tab and the Address tab. Go to Function Tab and click check box for purchasing organization and input the respective purchasing orgranizaiton and select backned R/3 Box
Again right click on the root node and create one more organization node and make this as purchasing group by selecting the check box from Function tab of the node. Make sure that the Basic data and the Address tab is filled
Once these are created and the respective Purchasing Org and Purchasing Group is assigned, Go to Responsibiltity tab of the Purchasing group and assign the Purchasing Organization and the product categories
The users should be created under the purchaisng org and the and under purchasing group the purchasing manager will be assigned.
Once the user is created, We need to assign the attributes to the users like company code ,cost centre, catalog id, account assignment category , document type, Local Currency, Movement type,Requistioner (Shop-on-behalf), System Alias, System Alias for Accounting System, System Alias for Vendor,e.t.c,
Go to Extended Attributes and assing Location (Plant), Product Categories.
Now login to Portal and create a shopping cart.
Tcodes used in creation and maintenance of org structure

Self Service Procureent -Classic Part 2 (Master Data Replication)

2012-05-22T17:33:00.001+05:30

In continuation to part 1, Here in this post we will see the settings and procedure to replicate master data from R/3

First of all we should create a site for receiving master data from the R/3 System

Create a site with Tcode SMOEAC
Once site is created you should check the following tables in R/3
CRMCONSUM, CRMSUBTAB, CRMRFCPAR, CRMPAROLTP, TBE11
If you check this table CRMRFCPAR it defines the Logical system where the material master should get replciated. Here we define the Customizing objects like DNL_CUST_BASIS3,DNL_CUST_PROD0,DNL_CUST_PROD1, MATERIAL
We should define the Load type as well whether it should be the initial download or delta download.
Once these table settings have been validated we need to run the initial load
Before running the initial load we need to execute report "BBP_PRODUCT_SETTINGS"
To run the initial load Execute T code R3AS.
Once you execute the initial load you need to monitor it whether the status is done , running . You can monitor this from R3AM1
If the status is running then you need to check SMQ2( Inbound queue) of SRM and SMQ1 (Outbound queue) of R/3
If there any error then you should rectify those errors. Access Tcode SMWP , SMW01 to get the error details
If there are no error then the Master data will get replciated and if you see the status in R3AM1 then you can find the status as done.
If you see the customizing objects DNL_CUST_BASIS3,DNL_CUST_PROD0,DNL_CUST_PROD1, MATERIAL status as done that means your material master data has replicated successfully.
If you want to define filters, then go to Tcode R3AC1 define the filters for Material Master and Service Master.
Once you are done with the replication, check in tcode COMM_HIERARCHY to check whether the material, material groups have been replicated.(Material Table :COMM_PRODUCT)
This completes the process of material replicaton.

Vendor Replication.

From SRM 5.0 there is Vendor Org Structure. So before replicating vendors we need to define for which Org structure these vendors should get replicated.
The following steps needs to be followed in order to replicate vendor.

Create a Vendor Group (Tcode PPOCV_BBP)
Once you define the vendor group you need to define the Attibutes like the logical system Currency e.t.c,
Go to Tcode BBPGETVD. Select the logical system , input the vendor number and in Object id input the vendor group which you have created.
Click on "Start Transfer"
It will show the list of vendors that will be replicated from the specified R/3 System. Click on "Start Transfer"
Go to Slg1 and input the object as "BBPGETVD" to see the log
Once you see "End Program reached" in the log go to table VENMAP and check the vendor you have replicated, You will find the entry.
You can schedule job BBP_VENDOR_SYNC for this report to avoid manual replication of vendor master

Once Vendor Master data is replicated we need to replicate Currency and exchange rate from R/3. Basically there are 2 reports

BBP_GET_CURRENCY-To replicate Currency from R/3
BBP_GET_EXRATE- To replicate Exchange Rate from R/3

Replicate Plants and Company code from R/3
Execute the following reports to replicate Plants and Company code from R/3
BBP_LOCATIONS_GET_ALL
BBP_LOCATIONS_GET_FROM_SYSTEM
BBP_LOCATIONS_GET_SELECTED

Once these master data are successfully replicated, We need to Define the Organization.

Create a Root Organization (Tcode PPOCA_BBP) and Click on "Save"
Create a Purchase Organization and purchasing group (Tcode PPOMA_BBP)
Create user from su01 and assign the BP using Tcode USERS_GEN.
User gets assigned to the Purchasing Organizaiton. Go to Purchasing group and under responsibility assign the org id (Purchase Organization) where the user is assigned.
Assign the attributes to the user, Organization.
Click on "Save". User will now be responsible to create Shopping Carts

Generate ALE Distribution Model from BD64.

Self Service Procurement -Classic Scenario

2012-05-13T12:46:00.001+05:30

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

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

Company Code Creation in SRM

2012-05-02T15:04:00.001+05:30

We Might have come across this situation when we create a company code in the bakend System and we need to replicate the company code and do the necessary settings in MM and in SRM . This blog gives you Step by Step procedure how to create a Company code in R/3(MM) and then replicate it and configure it in you Org Structure.

Below settings needs to be done in Material Management (MM) System.

Create new company code (Tcode OX02) and Plant (Tcode OX10).
Assign Plant to Company code ( Tcode OX18).
Assign Purchasing Organisation to Plant (Tcode OX17).
If Purch Org is not there then create a Purch Org (Tcode OX08) and assign to Plant (Tcode OX17)
Extend vendors(MKO1) to the new company code and then replicate to SRM (BBPGETVD / BBPUPDVD).
Extend WBS elements to the new company code
Create a New PO for the newly created Company code

Congiuring SRM System for the Newly created company code

Replicate the new plant to SRM , You can execute report "BBP_LOCATIONS_GET_SELECTED" so that only that company code gets replicated in SRM. Once you sucessfully executed the report check in table BBP_LOCMAP to cross verify that the newly created company code is available in SRM
Create a node for the new company code in the Org. Structure and maintain the company code in the attribute "Company Code" in the Attributes tab and maintain plant in the Extended Attributes --> Location . Also maintain the product categories which will be used to raise the shopping cart in the Extended Attributes --> Product Categories of the new node created for the company code.
Maintain the company code and location attributes for the users who will be using this new company code for raising carts.
Map the org id of the new company code node to respective purchasing groups in the org structure.(Tcode PPOMA_BBP)
Do the respective cost center approver set-up for the new company code
Define Ship-To address for the new company code and use this for Delivery address attribute in the user profiles in the Org.structure.
Once done create a SC with the newly created Comapny code , Once the approval flow is complete the Follow-On document will get created in the backend system.

Deployment Scenario - Standalone

2012-04-28T10:08:00.000+05:30

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

Who should go for Standalone Scenario?

Who doesn't have Backend (SAP-MM) system and wants to handle all the procurement activities in SRM itself.

Who don't want to maintain any master data ( Product Master Data)

Who want to use SRM for specific product categories (Indirect Materials & Services)

Who would go for P-Card Functionality

Who want Supplier Self Service integration in SRM

Process Flow of Standalone Scenario

End user creates SC in SRM
Approval Flow triggeres in SRM
PO is created in SRM
GR is posted in SRM
Invoice is created in backend FI system

In the next post we will see the configuration part of standalone scenario.

Custom Attribute Creation in SRM

2012-04-27T17:05:00.002+05:30

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

Once you press enter you will get the attribute in the attribute section

Click on "Save" so that the attribute gets saved
Once the attribute is saved click on "Attributes/Scenarios" and assign "BBP" as scenario.
Click on "Object Types" and assign the attribute which is created as "O" and "S"
O-Organization and S-Position. So that the attribute is available at the Org level as well as at Position Level.
Once this is created click on "Save".
Now go to PPOMA_BBP there you will find the attribute which you have created. Assign the respective value to the attribute.

Vendor Structure in SRM 7.0(PPOMV_BBP)

2012-04-26T16:30:00.004+05:30

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

Ensure that your structure is in proper format as per SAP. In the below screen where you can see that First is the Root node -> Followed by a dummy node -> Vendor Node

As per the above struture your vendor node for a a particular R/3 System should be in the format as per the above image
Once it's there then you need to execute report "BBP_XPRA_ORGEH_TO_VENDOR_GROUP". Once you execute report a new node will be created. You can view this node by going to T.code PPOSV_BBP, If you want to modify the structure then go to PPOMV_BBP. This way you can migrate your vendor org structure from SRM 4 to SRM 7
Trouble shooting :
When you try to migrate the struture you will get errors like you node dosen't have supplier role (or) Org Assignment role, Then execute report "BBP_ASSIGN_ROLE_TO_ORGUNIT_BP" and assign role to the Org unit which is specified on the screen
If you get an error saying that there is no BP number assigned then we need to execute report “BBP_ASSIGN_BP_TO_ORGUNIT” in order to assign BP number to that particular Org unit.Once you execute these reports then run the report "BBP_XPRA_ORGEH_TO_VENDOR_GROUP" and check is there any errors. If there are no errors then a node will get created. You can view this node in PPOSV_BBP/PPOMV_BBP

This is how we can migrate a vendor org structure from SRM 4.0 to SRM 7.0

Deployment Scenario of SAP-SRM

2012-04-26T16:09:00.004+05:30

Deployment Scenarios of SRM

There are 4 standard Deployment Scenarios in SRM.

Classic
Extended Classic
Standalone
Decoupled

Classic:

Classic Scenario is a scenario where the leading System will be the Backend R/3 System. Here the Shopping carts gets created in SRM and the PO will be created in R/3.

Confirmation & Invocing can be posted from the SRM or from the R/3 System.

Extended Classic:

In Extended Classic Scenario (ECS) the leading system will be the SRM System. Here the Shopping cart is created and the PO is created locally. Replica of the PO will be transferred to the backend system.

Confirmation and Invoicing can be done in SRM and in R/3

Standalone:

In this scenario there will be a SRM System and there will be no MM Backend system. Everything happens in the SRM System. So the leading system is also SRM System.

De-Coupled.

This scenario is a mix of Classic + Extended Classic Scenario. You can configure few product categories behave as "Classic" and other Product categories behave as "Extended Classic" scenario.
For this Badi "BBP_EXTLOCALPO_BADI" needs to be coded.

SAP SRM Challenges

Service Procurement in SRM

Purchasing Org and Purchasing Group in SRM

Purchasing Group

SRM G/L Account Determination.

Organization Structure Relationship (PPOSA_BBP)

BRF Process

Delete Vendor from SRM

User is not able to create shopping cart

User is not an EBP User

BRF Configuration Part - 1

BRF (Business Rule Framework)

Technical Configuration:

Customize SAP Business Workflow Automatically

Check Event Trigger Configuration

Check Event Type Linkage

Define Events

Define Expression

Define Groups

Vendor Creation in SRM 7.0

Business Addin Part - II

Badi Name: BBP_DETERMINE_ACCT

Badi Name: BBP_DETERMINE_LOGSYS

Badi: BBP_DOC_CHANGE_BADI

Badi: BBP_DOC_SAVE_BADI

Badi : BBP_TARGET_OBJTYPE

Badi:BBP_WFL_APPROV_BADI

SRM Business Add in (Badi) - I

BBP_BS_GROUP_BE

Methods:GROUP_PO_BACKENDGROUP_RQ_BACKENDGROUP_RS_BACKENDGET_NUMBER_OR_RANGE

BBP_CATALOG_TRANSFER

BBP_CHNG_AGNT_ALLOW:

BBP_CREATE_BE_PO_NEW

BBP_CREATE_BE_RQ_NEW

BBP_CREATE_BE_RS_NEW

SRM Business Scenario Overview

Operational Procurement

Sourcing

Supplier enablement

Vendor Replication in SRM 7.0

Organization Structure in SRM

Self Service Procureent -Classic Part 2 (Master Data Replication)

Self Service Procurement -Classic Scenario

Company Code Creation in SRM

Deployment Scenario - Standalone

Who should go for Standalone Scenario?

Process Flow of Standalone Scenario

Custom Attribute Creation in SRM

Vendor Structure in SRM 7.0(PPOMV_BBP)

Deployment Scenario of SAP-SRM

Classic:

Extended Classic:

Standalone:

De-Coupled.

Methods:
GROUP_PO_BACKEND
GROUP_RQ_BACKEND
GROUP_RS_BACKEND
GET_NUMBER_OR_RANGE