View
217
Download
0
Category
Preview:
Citation preview
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
1/16
0
SAP AG 1999
Software Logistics and Software Adjustment:Contents
Team- and project-oriented software development
using the Workench !rgani"er
Wa#s of changing the SA$ standard software
(C) SAP AG BC400 13-1
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
2/16
0%&
SAP AG 1999
At the conclusion of this unit' #ou will e ale to:
Software Logistics and Software Adjustment: (nit!jectives
)ap a project in the *+, S#stem using the
Workench !rgani"er
escrie the options for enhancing or changing
the functions of e.isting programs
(C) SAP AG BC400 13-2
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
3/16
0%,
SAP AG 1999
Software Logistics and *+, Adjustment:
Software logisticsSoftware logistics
*+, adjustment*+, adjustment
(C) SAP AG BC400 13-3
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
4/16
0%/
SAP AG 1999
At the nd of evelopment
Team:Team:
$roject )anager:$roject )anager:
nd of evelopmentSchedule: % % %
1ualit# control project1ualit# control project
•• S#nta. checkS#nta. check
•• 2nactive ojects2nactive ojects
•• Task consistenc#Task consistenc#$roject documentation$roject documentation
*e3uest is released*e3uest is released
4C/00-00
4C/00-05
4C/00-0&
4C/00-0,
4C/00-0/
%%%
1ualit# control tasks:
• S#nta. check
• Activation of inactive ojects
Task documentation
Tasks are released
(C) SAP AG BC400 13-4
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
5/16
0%6
SAP AG 1999
!riginals and Copies
Cop#Cop#
!riginal!riginal
Cop#Cop#
Cop#Cop#
!riginal!riginal
SA$ oject
evelopment s#stemevelopment s#stem 7e.t s#stem7e.t s#stem
SA$ oject SA$ oject
Customer
oject
Customer
oject
TransportTransport
developmentdevelopment
When you create a Repository object, the Workbench Organizer automatically notes the system in
which you created it. We say that the original of a Repository object is in a certain system.
The original version of an object can only eist in one system. !ll other systems contain copies of
the object.
The idea of having an original system is to ensure that Repository objects can only be changed in the
integration system. The integration system is where you carry out your development work, so all of
the objects in it are originals. This means that there is one central location for changing Repository
objects.
"f you now transport your Repository objects into a consolidation system, it eists there as a copy.
!lthough it is possible to change copies in eceptional cases, you should always try to make the
changes in the integration system and transport the new version to other systems. This ensures that
the state of objects remains consistent across systems. Originals are never overwritten in transports.
(C) SAP AG BC400 13-5
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
6/16
0%8
SAP AG 1999
)odified)odifiedCop#Cop#
CorrectedCorrected
!riginal!riginal
Cop#Cop#
Cop#Cop#
CorrectedCorrected!riginal!riginal
SA$ oject
evelopment s#stemevelopment s#stem 7e.t s#stem7e.t s#stem
TransportTransport
correctioncorrection
SA$ oject SA$ oject
Customer oject Customer oject
CorrectionCorrection
*epair *epair CorrectionCorrectionTransportTransport
repair repair
Corrections and *epairs
#hanging an original is called a correction. The system records these changes in a re$uest containing
tasks of type %development&correction%.
"f a copy is changed 'that is, if an object is not changed in its original system(, this change is
recorded in a task with type %repair%. ! repair of an )!* object is called a modification.
The changes made to your own objects 'e.g. due to an emergency in the production system( can also
be made immediately to the originals in the develoment system. It is imperative that you
immediately make the changes you made to copies to the original as well!!
This is not possible for )!* objects because the originals are not in any of your systems.
(C) SAP AG BC400 13-6
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
7/16
0%9
SAP AG 1999
)odifications uring the (pgrade
)odified)odifiedCop#Cop#
CorrectedCorrected
!riginal!riginal
Cop#Cop#
Cop#Cop#
CorrectedCorrected!riginal!riginal
SA$ oject
evelopment s#stemevelopment s#stem 7e.t s#stem7e.t s#stem
TransportTransport
adjustmentadjustment
SA$ oject SA$ oject
Customer oject Customer oject
(pgrade(pgrade(pgrade(pgrade
)odification)odification
adjustmentadjustment
! conflict could occur when you apply an upgrade, a support package, or some other transport
re$uest from )!* to your system.
! conflict occurs if you change an )!* object and a new copy is being delivered by )!* in an
upgrade. The object delivered by )!* becomes the active object in the repository of your R&+
)ystem.
"f you want to save your changes, you have to make a modification adjustment for the
corresponding objects. odifying a number of )!* objects can cause a substantial delay when
performing an upgrade.
To ensure that the development system and the net system are consistent, you should only make the
modification adjustment in the development system. The objects of the adjustment are then
transported to the later systems.
(C) SAP AG BC400 13-7
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
8/16
0%
SAP AG 1999
Software Logistics and *+, Adjustment:
Software logisticsSoftware logistics
*+, adjustment*+, adjustment
(C) SAP AG BC400 13-8
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
9/16
0%;
SAP AG 1999
Change Levels
*+, usiness*+, usiness
applicationsapplications
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
10/16
0%50
SAP AG 1999
>ow nhancements ?unction
* REPORT *
*********************************
REPORT .
@Call enhancement
* Object in customer namespace *
******************************
)!* objects are usually enahanced as shown.
The )!* object enables you to go to a customer object. )ince this object usually does not eist, you
have to implement it in the specified manner.
/ifferent enhancement techni$ues are implemented differently. /epending on the enhancement
techni$ue, you have to use a different maintenance transaction to use the enhancement and to create
the corresponding objects.
The corresponding maintenance transaction has a search function for finding a suitable enhancement.
0ou can also find documentation about the corresponding enhancement here.
(C) SAP AG BC400 13-10
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
11/16
0%55
SAP AG 1999
?inding nhancements
(ser e.its Customer e.its 4usiness transaction
events
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
12/16
0%5&
SAP AG 1999
Is a similar fun!i"n
ma##$% in !&$ SAP s!an%ar%'
Can !&$ SAP
fun!i"n $ a%us!$%
!" !&$ us!"m$r*s r$+uir$m$n!s
usin, $n&an$m$n!s'
"$s !&$
SAP a##lia!i"n all".
m"r$ fun!i"ns !" $
lin/$% .i!& $n&an$m$n!s'
"
$s
$s
"
$s
"
Customer development
Customi"ing
nhancement
*e3uest enhancement'
Avoid modification
?unctional nhancements
3efore starting a modification, check whether it is possible to meet your re$uirements using
#ustomizing or the enhancement concept instead.
7nhancements are a method of changing )!* software while avoiding a classic modification. 0ou
can change or etend functions without having to adjust the software manually during upgrades. The
different types of enhancement are mentioned later in this unit.
0ou can re$uest an enhancement in the )!*5et R&+ 4rontend.
(C) SAP AG BC400 13-12
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
13/16
0%5,
SAP AG 1999
)enu &
un!i"n 1
un!i"n 2
Cust% function
un!i"n 3
$nu 1 $nu 3
)enu e.it)enu e.it
?ield .
?ield #
ScreenScreen
e.ite.it?ield e.it?ield e.it
nhancing (ser ialogs
0ou can enhance the R&+ )ystem at the following levels-
Menu exit: The system contains various points at which you can include menu items that start
customer programs.
creen exit: )ome screens contain areas 'subscreens( in which you can display your own
screens.
ield exits: 4ield eits allow you to incorporate etra field checks.
(C) SAP AG BC400 13-13
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
14/16
0%5/
SAP AG 1999
nhancements: .amples
$rogram e.its:
$redefined e.its to application programs
ictionar# enhancements:
Tale appends: Allow #ou to add e.tra fields to standard
tales
Semantic information for data elements: Fou can change the
field documentation
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
15/16
0%56
SAP AG 1999
$rogram
$$l"#m$n! "$! %i! G"!" !ili!i$s S$!!in,s nir"nm$n!
Add eveloper
"u ar$ n"! r$,is!$r$% as a %$$l"#$r
Pl$as$ r$,is!$r in !&$
SAP$! - 3 r"n!$n%
:&$n ;"u r$,is!$r< ;"u .ill $ ,i$n
an a$ss /$;
s$r
$,is!ra!i"n %i! S$l$!i"n S;s!$m =$l#
>=I
07319180563617100772?$;
*egister Changes to SA$ !jects
*epositor# 4rowser: $rogram SA$A4A$
Customer
s#stem
SA$7et
*+,
?rontend
*egistering evelopers in the SSC*
@ABAP
When you start developing in the R&+ )ystem, you must re$uest a key in the )!*5et R&+ 4rontend.
This registers you as a developer. 0ou are asked to enter the key the first time you create or change a
Repository object. The system assigns keys related to your customer number and user name.
To register as a developer-
9og onto )!*5et R&+ 4rontend. "f you do not have a system user, ask a colleague to log on for
you. :e or she will be able to register you. ':owever, your colleague;s name will be recorded as
having re$uested the registration(.
#hoose Registration.. The Register Changes to SAP Objects screen appears.
7nter the R&+ user name of the developer you want to register. The system will display a
8/16/2019 EXP_0013 Software Logistics and Software Adjustment Contents.doc
16/16
0%58
SAP AG 1999
Fou are now ale to:
Software Logistics and Software Adjustment: (nitSummar#
)ap a project in the *+, S#stem using the
Workench !rgani"er
escrie the options for enhancing or changing
the functions of e.isting programs
(C) SAP AG BC400 13-16
Recommended