You are on page 1of 32

The org structure forms the hierarchy in

which the various organizational units of an


enterprise are arranged according to the
tasks and functions

SRM Organization Hierarchy
Vendor Organization Hierarchy
Purchasing Organization Hierarchy

Root organizational unit
Organizational unit
Users
Organizational unit
Position
Central Person
Business partner id
SU01 user
Attributes Description Mandatory
ACS Backend accounting
system
Yes
ADDR_SHIPT Delivery address in
purchasing order
No
BSA Document type in
backend
Yes
BUK Company code in
backend
Yes
BWA Moment type in
backend
Yes
CAT Catalog id No
CUR Currency Yes
KNT Account assignment Yes
RESP_PGPR Org unit object for org
units representing
purchasing orgs
Yes
REQUESTOR Ship to party for which
a user/org unit will be
allowed to order
Yes
Define RFC connection at SRM for backend
system
IMG->SRM->technical basic settings->define
rfc 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
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 logical
systems
Assign client to logical systems
Tcode SALE->logical systems->assign logical
system 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->maintain
distribution model and distribute views
Select Model
You specify the number ranges for the materials management
documents 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

Product Master Records(Material Master)
Business Partner Master Records(Vendor
Master)
Product Categories
Vendor Organization structure
Transaction BBPGETVD downloads vendor
information as a business partner information
from the backend to EBP
BBP_UPLOAD_PAYMENT_TERMS is used to
replicate the payment terms from backend to
EBP
BBP_UPDATE_PROG is to add , change , delete
purchasing organizations

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


In SRM system
Goto SRNO and assign number ranges
Output format of product id in both backend
and srm system
Start of download of material master
Goto transaction R3AS and choose 1
st
object
to download
Goto R3AM1 to check for success
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 this
report:
COM_PRODUCT_DELETE_SINGLE - Deletion of a product
from the database
COM_PRODUCT_DELETE_ALL - Deletion of all product
master data

SAP is known for delivering business software
easily adaptable by customers for their specific
needs.
Typically the software (for example, mySAP ERP)
can be adapted by one of the following
techniques:
Customizing
Enhancement
Modification
Enhancement Framework brings together all
enhancement techniques under one roof and
improves the way SAP software is enhanced
What is Enhancement Framework?
Enhancement Framework is the new paradigm to
bring all enhancement techniques under one
roof. It can also be switched using Switch
Framework. The following are different
enhancement technologies available under this
framework.
Source Code Enhancement
Function Group Enhancement
Class Enhancement
Kernel-BADI Enhancement

Whenever enhancement needs to be
incorporated directly into the ABAP source
code, this technology shall be provided.
Implementing this technology is also called as
Source Code Plug-In. There are two types of
Source Code enhancements possible.
Implicit enhancement option
Explicit enhancement option

Implicit enhancement option
Throughout the ABAP system, enhancement options are
automatically available at certain pre-defined places. Some
of 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 Implicit
Enhancement Options from the editor.

Explicit enhancement option
There are two types of Explicit Enhancement
options available. One which can be provided
at a specific place - called Enhancement
Point, and another which can be used to
replace a set of statements called
Enhancement Section. For this, we now have
two new ABAP statements, viz.
ENHANCEMENT-POINT
ENHANCEMENT-SECTION

Function Group Enhancement
All application function modules can be
enhanced by adding parameters to the standard
function module interface. These parameters
must be optional in nature, since adding a
mandatory parameter will require all calls to be
changed. Additionally any function module that is
part of the Central Basis can not be enhanced (for
example: function module
POPUP_TO_CONFIRM). From the menu, choose
Function module -> Enhance interface to add
optional parameters to a function module.
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 invoking
the respective method. These are achieved by an automatically
generated local class. All methods are stored as part of this local
class. (Point to ponder: Are private and protected attributes
accessible from the Pre and Post exits?).
Choose menu option Class -> Enhance to add new methods or
parameters. Choose menu option Edit -> Enhancement
operations to add or delete the Pre/Post/Overwrite exit
methods.

Kernel BADI Enhancement
The new Kernel-BADI takes it to the ABAP
language level. Because of this, the new
Kernel-BADIs are much faster compared to
the old classic-BADIs.
There are two new ABAP statements available
now to support the Kernel-BADIs, namely
GET BADI and CALL BADI.
All enhancement technologies are now under
a single roof of Enhancement Framework
The options to enhance standard SAP code
have increased tremendously.
Kernel-BADIs are much faster compared to
the old classic-BADIs
Implementing classes of Kernel-BADIs are
re-usable through inheritance

You might also like