Organization Structure Relationship (PPOSA_BBP)

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

BRF Process

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

Delete Vendor from SRM

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

User is not an EBP User

BRF Configuration Part - 1

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

Vendor Creation in SRM 7.0

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

Business Addin Part - II

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

SRM Business Add in (Badi) - I

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

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).

Vendor Replication in SRM 7.0

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

Organization Structure in SRM

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.

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

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

Self Service Procurement -Classic Scenario

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 )

Company Code Creation in SRM

 
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.

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