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
SAP SRM Challenges
This blog will provide you with the challenges what we face on day to day on SRM
Friday, September 27, 2013
Thursday, March 28, 2013
Purchasing Org and Purchasing Group in SRM
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
Thursday, January 31, 2013
SRM G/L Account Determination.
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.
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.
Friday, November 16, 2012
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
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
Thursday, November 15, 2012
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
Friday, September 14, 2012
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
Thursday, September 13, 2012
Subscribe to:
Posts (Atom)