srm orgstructure
DESCRIPTION
supplier relationship management organisation structureTRANSCRIPT
-
5/23/2018 SRM Orgstructure
1/32
-
5/23/2018 SRM Orgstructure
2/32
-
5/23/2018 SRM Orgstructure
3/32
The org structure forms the hierarchy inwhich the various organizational units of anenterprise are arranged according to thetasks and functions
SRM Organization Hierarchy
Vendor Organization Hierarchy
Purchasing Organization Hierarchy
-
5/23/2018 SRM Orgstructure
4/32
-
5/23/2018 SRM Orgstructure
5/32
Root organizational unit Organizational unit
Users
-
5/23/2018 SRM Orgstructure
6/32
-
5/23/2018 SRM Orgstructure
7/32
-
5/23/2018 SRM Orgstructure
8/32
Organizational unit Position
Central Person
Business partner id SU01 user
-
5/23/2018 SRM Orgstructure
9/32
-
5/23/2018 SRM Orgstructure
10/32
-
5/23/2018 SRM Orgstructure
11/32
Attributes Description MandatoryACS Backend accounting
systemYes
ADDR_SHIPT Delivery address inpurchasing order
No
BSA Document type in
backend
Yes
BUK Company code inbackend
Yes
BWA Moment type inbackend
Yes
CAT Catalog id NoCUR Currency Yes
KNT Account assignment Yes
RESP_PGPR Org unit object for orgunits representing
purchasing orgs
Yes
-
5/23/2018 SRM Orgstructure
12/32
Define RFC connection at SRM for backendsystem
IMG->SRM->technical basic settings->definerfc destinations->abap connections->create.
Define RFC connection at Backend for SRM
Define logical system in srm
IMG->SRM->technical basic settings->ALE
settings->distribution->logical systems->define logical systems
-
5/23/2018 SRM Orgstructure
13/32
Assign logical system to client in SRM IMG->SRM->technical basic settings->ale
settings->distribution->logical systems->assign logical system to client
Define logical system in backend system
Tcode SALE->logical systems->define logicalsystems
Assign client to logical systems
-
5/23/2018 SRM Orgstructure
14/32
Tcode SALE->logical systems->assign logicalsystem to client
Maintain distribution model Generate partner profile Distribute model Logon to backend system SPRO->sap web application server-
>application link enabling->modelling and
implementing business processes->maintaindistribution model and distribute views
Select Model
-
5/23/2018 SRM Orgstructure
15/32
You specify the number ranges for the materials managementdocuments in the SAP Enterprise Buyer system. You must specify number ranges for the following local
documents: Shopping carts Purchase orders
Purchase contracts Purchase order responses Confirmations for goods and services Invoices If you create materials management documents in the backend
system, you also determine in Enterprise Buyer the internal
number range for : Purchase requisitions Purchase orders Reservations
-
5/23/2018 SRM Orgstructure
16/32
Product Master Records(Material Master) Business Partner Master Records(Vendor
Master)
Product Categories
-
5/23/2018 SRM Orgstructure
17/32
Vendor Organization structure Transaction BBPGETVD downloads vendor
information as a business partner informationfrom the backend to EBP
BBP_UPLOAD_PAYMENT_TERMS is used toreplicate the payment terms from backend toEBP
BBP_UPDATE_PROG is to add , change , deletepurchasing organizations
-
5/23/2018 SRM Orgstructure
18/32
Technical Basic settings Update entries in following tables(Backend):
CRMCONSUM
CRMSUBTAB
CRMRFCPAR
CRMPAROLTP
Edit table TBE11
Generate repository objects Goto transaction SMOGGEN and choose product_mat
-
5/23/2018 SRM Orgstructure
19/32
In SRM system Goto SRNO and assign number ranges
Output format of product id in both backendand srm system
Start of download of material master
Goto transaction R3AS and choose 1stobjectto download
Goto R3AM1 to check for success
-
5/23/2018 SRM Orgstructure
20/32
Goto R3AS and repeat the steps If you want to delete hierarchy of product, run this
report: COM_HIERARCHY_DELETE_SINGLE- Deletes all hierarchy
and category data COM_HIERARCHY_DELETE_ALL- Deletes all hierarchy and
category data
If you want to delete all or selected product, run thisreport: COM_PRODUCT_DELETE_SINGLE- Deletion of a productfrom the database COM_PRODUCT_DELETE_ALL- Deletion of all product
master data
-
5/23/2018 SRM Orgstructure
21/32
SAP is known for delivering business softwareeasily adaptable by customers for their specificneeds.
Typically the software (for example, mySAP ERP)
can be adapted by one of the followingtechniques: Customizing
Enhancement
Modification
Enhancement Framework brings together allenhancement techniques under one roof andimproves the way SAP software is enhanced
-
5/23/2018 SRM Orgstructure
22/32
-
5/23/2018 SRM Orgstructure
23/32
What is Enhancement Framework Enhancement Framework is the new paradigm to
bring all enhancement techniques under oneroof. It can also be switched using Switch
Framework. The following are differentenhancement technologies available under thisframework.
Source Code Enhancement
Function Group Enhancement
Class Enhancement Kernel-BADI Enhancement
-
5/23/2018 SRM Orgstructure
24/32
Whenever enhancement needs to beincorporated directly into the ABAP sourcecode, this technology shall be provided.Implementing this technology is also called as
Source Code Plug-In. There are two types ofSource Code enhancements possible.
Implicit enhancement option
Explicit enhancement option
-
5/23/2018 SRM Orgstructure
25/32
Implicit enhancement option Throughout the ABAP system, enhancement options are
automatically available at certain pre-defined places. Someof the implicit options are:
At the end of all the programs (Includes, Reports,Function pool, Module pool, etc.), after the last statement
At the beginning and end of all FORM subroutines At the end of all Function Modules At the end of all visibility areas (public, protected and
private) of local class
To view all the implicit options available in a source code,choose Edit -> Enhancement Operations -> Show ImplicitEnhancement Options from the editor.
-
5/23/2018 SRM Orgstructure
26/32
Explicit enhancement option There are two types of Explicit Enhancement
options available. One which can be providedat a specific place - called Enhancement
Point, and another which can be used toreplace a set of statements calledEnhancement Section. For this, we now havetwo new ABAP statements, viz.
ENHANCEMENT-POINT ENHANCEMENT-SECTION
-
5/23/2018 SRM Orgstructure
27/32
-
5/23/2018 SRM Orgstructure
28/32
Function Group Enhancement All application function modules can be
enhanced by adding parameters to the standardfunction module interface. These parametersmust be optional in nature, since adding amandatory parameter will require all calls to bechanged. Additionally any function module that ispart of the Central Basis can not be enhanced (forexample: function module
POPUP_TO_CONFIRM). From the menu, chooseFunction module -> Enhance interface to addoptional parameters to a function module.
-
5/23/2018 SRM Orgstructure
29/32
Class enhancement The global Classes and Interfaces can be enhanced as follows:
Adding optional parameters to existing Methods Adding new Methods to the global Class / Interface Adding Pre-exit, Post-exit or Overwrite-exit to an existing
Method
The Pre and Post exits get executed before and after invokingthe respective method. These are achieved by an automaticallygenerated local class. All methods are stored as part of this localclass. (Point to ponder: Are private and protected attributesaccessible from the Pre and Post exits?).
Choose menu option Class -> Enhance to add new methods orparameters. Choose menu option Edit -> Enhancementoperations to add or delete the Pre/Post/Overwrite exitmethods.
-
5/23/2018 SRM Orgstructure
30/32
Kernel BADI Enhancement The new Kernel-BADI takes it to the ABAP
language level. Because of this, the newKernel-BADIs are much faster compared to
the old classic-BADIs.
There are two new ABAP statements availablenow to support the Kernel-BADIs, namely
GET BADI and CALL BADI.
-
5/23/2018 SRM Orgstructure
31/32
All enhancement technologies are now undera single roof of Enhancement Framework
The options to enhance standard SAP codehave increased tremendously.
Kernel-BADIs are much faster compared tothe old classic-BADIs
Implementing classes of Kernel-BADIs are
re-usable through inheritance
-
5/23/2018 SRM Orgstructure
32/32