0

SAP AG 1999
Transfer tools and methods
Tasks in data transfer projects
Project Concept: Contents
SAP AG BC420 3-1

0.2
SAP AG 1999
Describe the data transfer methods
Describe the tasks in a transfer project
Explain the use of business objects and BP!s
Create a data transfer project in the D" # $B and
execute a customer data transfer
t the conclusion of this unit% &ou 'ill be able to:
Project Concept: (nit )bjecti*es
SAP AG BC420 3-2

0.+
SAP AG 1999
Course )*er*ie' Dia,ram Course
Daten-bernahme
D" $orkbench
./0 $orkbench
Principles of /tandard
Data Tansfer
D
i
r
e
c
t

!
n
p
u
t
BP!
T

1
e
c
o
r
d
e
r
Course )*er*ie'
+
B
a
t
c
h

!
n
p
u
t
C
a
l
l

T
r
a
n
s
a
c
t
i
o
n
ED!
Basics
2
3
4
5
6 70
77
70
8
77
75
7+
72
77
72
7
2
SAP AG BC420 3-3

0.5
SAP AG 1999
Data Transfer Project
Technolo,ies and Tools
Technolo,ies and Tools
Project )r,ani9ation
Project )r,ani9ation
Business )bjects
Business )bjects
Project in the D"#$B
Project in the D"#$B
SAP AG BC420 3-4

0.2
SAP AG 1999
Data Transfer in 1:+
C) C)
Controllin, Controllin,
0 0
sset sset
mana,ement mana,ement
P/ P/
Project Project
s&stem s&stem
$; $;
$orkflo' $orkflo'
!/ !/
!ndustr& !ndustr&
/olutions /olutions
;! ;!
;inance ;inance
<1 <1
<uman <uman
1esources 1esources
/D /D
/ales /ales
PP PP
Production Production
plannin, plannin,
=0 =0
=ualit& =ualit&
0,mt. 0,mt.
P0 P0
!n*entor& !n*entor&
comtrol comtrol
00 00
0aterial 0aterial
mana,ement mana,ement
Each application provides its own transfer program. As other data always plays a role in each
application, the interfaces are not the same.
SAP AG BC420 3-5

0.3
SAP AG 1999
Transfer 0ethods
Transaction 1ecorder
Data Transfer
Pro,ram
Data Transfer
Pro,ram
Batch !nput
Batch !nput
Call Transaction
Batch !nput
Call Transaction
CT
D!
CT
BP!
Direct input
Most applications provide a standard interface.
Several data transfer methods are supported in the SAP System. These are batch input, call
transaction, direct input and BAPs. !hich method is supported in a certain situation depends solely
on the application involved. The e"pected amount of data usually plays a decisive role in which
methods are supported.
n special cases and for a few applications, a standard interface may not be provided. f this is the
case, you can use the transaction recorder #TA$ instead. The TA supports both batch input and call
transaction.
SAP AG BC420 3-6

0.4
SAP AG 1999
Online
transaction
Batch !nput 0ethod
External
format
SAP format
B! session
B! data transfer
pro,ram
>
USD
External
format
B! data transfer
pro,ram
>
USD
Batch input is a standard method used to transfer data into the %&' System. The transaction process is
simulated and the data is transferred as if it had been entered online. The advantage of this process is
that all the transaction chec(s are carried out and therefore data consistency is assured.
The batch input process runs in two phases)
*.$ A batch input session is created containing all the relevant data.
+.$ The batch input session is processed and the data contained in it is imported into the %&' System.
Most of the SAP standard data transfer programs use batch input.
,ote) The online transaction is used for importing, chec(ing and transferring the data into the %&'
database.
SAP AG BC420 3-7

0.6
SAP AG 1999
Online
transaction
Call Transaction 0ethod
SAP format
External
format
CT data transfer
pro,ram
CT
>
USD
>
USD
-all transaction is a standard method used to transfer data into the %&' System. The transaction flow
is simulated and the data is transferred as if it had been entered online. The advantage of this
procedure is that all transaction chec(s are carried out, thereby guaranteeing data consistency.
-all transaction posts the data directly via the online transaction.
This method provides the same functions as with batch input.
,ote) the online transaction is used for importing and chec(ing.
SAP AG BC420 3-8

0.8
SAP AG 1999
Direct !nput 0ethod
External
format
D! data transfer
pro,ram
SAP format
>
USD
>
USD
!ith direct input the data in the data transfer file is chec(ed thoroughly and then transferred directly
into the %&' System. The %&' database tables are loaded&updated with the new data.
The direct input program used for importing and chec(ing the data carries out the same tests as the
online transaction. This guarantees data integrity.
The direct input method uses function calls in place of the online transaction screens.
,ote) the direct input method is not available for all data transfer applications.
SAP AG BC420 3-9

0.70
SAP AG 2001
ED! Technolo,&
SAP IDoc
Structure
External
format
>
USD
.E inbound
function module
.E inbound processin,
.sing E/ #Electronic /ata nterchange$ technology, data can be e"changed between systems #also
between non0SAP systems$.
f E/ is used in the %&' environment, function modules are provided for inbound and outbound
processing in A1E # Application 1in( Enabling$ to process the data in /ocs #intermediate
documents$.
n this scenario A1E inbound processing uses /ocs to transfer data.
This technology does not use online transactions as chec( mechanisms. All chec(s are carried out in
the function module of each application and the data is posted directly.
SAP AG BC420 3-10

0.77
SAP AG 1999
BP! 0ethod
SAP IDoc
structure
External
format
Con*rsion
pro,ram
>
USD
BP!
>
USD
BAPs are standardi2ed programming interfaces that provide e"ternal access to the business
processes and data of the %&' System.
Business Application Programming nterfaces #BAPs$ are defined in the Business 3b4ect %epository
#B3%$ as methods of SAP business ob4ects or SAP interface types and enable an ob4ect0oriented
view of the business components #application components$ of the %&' System.
The data is transferred by calling a BAP in the application.
The same chec(s are made as with online transfer.
SAP AG BC420 3-11

0.72
SAP AG 1999
Online
Transaction
Transaction 1ecorder
1ecordin,
Transfer Pro,ram
CT
5ou use the transaction recorder to create a recording of a se6uence of transactions along with their
corresponding se6uence of screens.
5ou can generate a data transfer program from the recording7 this program will be used to import the
data into the %&' System. The program can e"ecute data transfer using either the batch input or call
transaction methods.
SAP AG BC420 3-12

0.7+
SAP AG 1999
Project Concept
Tools and 0ethods
Tools and 0ethods
Project )r,ani9ation
Project )r,ani9ation
Business )bject
Business )bject
D" # $B Project
D" # $B Project
SAP AG BC420 3-13

0.75
SAP AG 1999
/P 1oadmap: Project )r,ani9ation
Project
Preparation
Business
Blueprint
!mplementation
Production
Preparation
?o#.i*e @
/upport
Data transfer is referred to in about 22
places in the /P 1oadmap
Phase 1: Project Preparation 0 planning and preparing the SAP pro4ect.
Phase 2: Business Blueprint 0 creating the business blueprint document. This is a detailed
description of the results of wor(shops on the business process re6uirements of a company. 8rom
this document you can get an overview of how the company would li(e to represent its business
processes in the SAP System.
Phase 3: Implementation 0 configuring business and process re6uirements from the business
blueprint in the SAP System. The system is configured into two wor( pac(ages 0 the baseline
configuration #main scope$ and the detail configuration #detail scope$.
Phase 4: Production Preparation 0 carrying out tests and user training, for system management and
data transfer to meet the re6uirements for productive operation. n this last preparation phase all
important, open 6uestions are cleared up. 3nce this phase has been successfully completed, you can
perform your business operations in the SAP productive system.
Phase 5: Go-Live & upport 0 the transition from the pro4ect0oriented, preproductive environment
to the successful productive operation.
SAP AG BC420 3-14

0.72
SAP AG 1999
;orm project team
/pecif& tasks
ssi,n tasks and roles
Data Transfer Project
f a data transfer is to be carried out, it should be implemented in a pro4ect for each application.
Pro4ects can be divided into sub0pro4ects as needed.
A pro4ect team should be assembed for the data transfer. Each member of the pro4ect should be able
to carry out specified tas(s of the entire pro4ect, so that the team is in a position to be able to carry
out the complete process.
After forming the team the tas(s involved in the pro4ect should be specified.
After the tas(s are specified, they should be assigned to team members. 3ne person may have
several roles.
SAP AG BC420 3-15

0.73
SAP AG 1999
Project PrereAuisites
Customi9in, completedB
Cno'led,e of:
.e,ac& s&stem
/P /&stem
Personnel a*ailable
-ustomi2ing is e"tremely important for data transfer. -ustomi2ing changes automatically result in
changes to the chec(s and valid values of the %&' System. 8or data transfer this means that data that
could be transferred error0free before -ustomi2ing was changed, may be transferred with errors after
changes in -ustomi2ing. Therefore, always test data transfer after every -ustomi2ing change.
To e"ecute the data transfer, you must have the re6uired bac(ground (nowledge and understand the
techni6ues for e"tracting data from e"ternal systems, as well as the procedures for transferring the
data to the SAP System.
,ote) 5ou must also have comprehensive (nowledge of the applications whose data is to be
transferred.
Another 6uestion to be answered is) Are there enough people on the team to carry out the re6uired
tas(s9
SAP AG BC420 3-16

0.74
SAP AG 1999
Project Tasks
Extract data
;ormat data
0ap data
Test and:or execute data
transfer
Check data
>
USD
format
Map
Check
ra!"fer #ata
$%tract
The tas(s listed above should be e"ecuted in a data transfer pro4ect.
SAP AG BC420 3-17

0.76
SAP AG 1999
Test Procedure
& Check data in 1:+
& Correct : add to data in le,ac& s&stem
Transfer Data
Con*ert Data
TE/T
>
USD
/tart
;inish
A test should always be run with a representative amount of data. This means the test data should
include as many t!pical data records "rom the e#ternal s!stem as possible$ Testing using *:: data
records that are all copies of the first is of no use at all.
There are three phases in the test)
-onverting the data into the interface format
Transferring the data to the %&' System
Testing the data in the %&' System
f data errors are found, fi" these errors in the legacy system. /ata 6uality is e"tremely important for
data transfer. /ata records with errors usually result in errors in the data transfer.
Therefore, the data from the legacy system must be *::; correct to ensure error0free data transfer.
The appendi" has additional information on the test procedure.
SAP AG BC420 3-18

0.78
SAP AG 1999
Documentation from D"#$B
pplication help <elp
C C
;! ;!
<1 <1
.) .)
/D /D
00 00
PP PP
?eneral help on data transfer
Data transfer techniAues
Data transfer before 1elease 5.3
Data transfer objects in
applications
The /<0!B documentation is in the /<0!B itself.
SAP AG BC420 3-19

0.20
SAP AG 1999
dditional Documentation
Data Transfer d*iser
Technical information about a*ailable tools and
technolo,ies for data transfer.
http'(("er)*ce+"ap+com(#ta
Delta Ciosk
!nformation about transactions re*ised in 5.3
http'(("er)*ce+"ap+com(46k*o"k
-,-hat." !e/ *! th*" 0e1ea"e
-,A11 re)*"e# tra!"act*o!"
SAP AG BC420 3-20

0.27
SAP AG 1999
)ther Data Transfer $orkbenches
External Data Transfer
Ba!k*!23 rea"4r5
64rther *!format*o! *! the o!1*!e #oc4me!tat*o!
!B!P
P1a!t ma*!te!a!ce
64rther *!format*o! *! the o!1*!e tra!"act*o! 7B7P
!/#(
89:ect" of the ;t*1*t*e" 7!#4"tr5 B4"*!e"" So14t*o!
64rther *!format*o! *! the o!1*!e #oc4me!tat*o!
5ou can find documentation on the e#ternal data trans"er %or&'ench in the SAP 1ibrary under)
-ross0Application -omponents 0= -A /ata Transfer.
The e"ternal data transfer wor(bench is used in the following areas)
Treasury #T%$
-entral business partners
E"ecutive nformation System #ES$
Profitability analysis #-30PA$
Ban( -ustomer Accounts #B-A$, profitability and ris( analysis of the ndustry Business Solution,
SAP Ban(ing
IBIP supports ob4ects for plant maintenance. 8or more information see the documentation
#information icon$ in the transaction BP.
SAP AG BC420 3-21

0.22
SAP AG 1999
Data Transfer Project
Tools and 0ethods
Tools and 0ethods
Project )r,ani9ation
Project )r,ani9ation
Business )bject
Business )bject
D"#$B Project
D"#$B Project
SAP AG BC420 3-22

0.2+
SAP AG 1999
Business )bject 1epositor& # B)1
Business )bject Builder
Business )bject 1epositor&
Business )bjects
pplication components
B)
B)
B)
B)
)r,ani9ation of transfer
pro,rams usin, B)1 objects
B3%) Business 3b4ect %epository
-entral repository within the %&' System containing all the SAP business ob4ect types, SAP
interface types, their definitions and methods etc.
t identifies and describes the available SAP business ob4ect types and interface types and their
BAPs.
8or e"ample, if you are developing an application program you use the (ey fields and the BAP
methods from the information stored in the B3% on the SAP business ob4ect types or SAP
interface types. The B3% contains all the details you need to integrate the correct ob4ect type
definitions and BAP calls into your application program.
1i(ewise, all the transfer programs as of >.? are organi2ed by the B3% ob4ects in the application.
SAP AG BC420 3-23

0.25
SAP AG 1999
Business )bjects
Business
object
Transfer
pro,ram
Transfer
pro,ram
Transfer
pro,ram
)r,ani9ation of transfer pro,rams and BP!s usin, B)1 objects
BP!
BP!
BP!
BP!
BAP) Business (pplication Programming Interface
Standardi2ed programming interface that enables access to business processes and data in the %&'
System.
BAPs are defined in the B3% as methods of SAP 'usiness o'ject t!pes that carry out specific
business functions.
There may be different transfer methods for each B3% ob4ect. These may be BAPs or transfer
programs. As the BAPs are already defined through B3% ob4ects, the standard transfer programs are
also closely defined through them. So a B3% ob4ect can identify all the transfer programs that it can
use.
The B3% is the %&' interface to e"ternal systems, so all the transfer programs have been assigned to
the B3% ob4ects.
SAP AG BC420 3-24

0.22
SAP AG 1999
Project Concept
Tools and 0ethods
Tools and 0ethods
Project )r,ani9ation
Project )r,ani9ation
Business )bject
Business )bject
D"#$B Project
D"#$B Project
SAP AG BC420 3-25

0.23
SAP AG 1999
D"#$B ;unctions
Project
)r,ani9ation
Tools 1e,istration
/tandard transfer
pro,rams and
BP!s are
re,istered
CustomersD
pro,rams and
function modules
Overview of
available
procedures
Create test data
;ile functions
Acquire
knowledge of
transfer obect
and load program
Project% subproject%
run% task%
Execute and
schedule
Organi!ation of data
transfer
The /ata Transfer !or(bench provides you with integrated pro4ect management to carry out all the
steps re6uired for transferring data into your %&' System.
The /<0!B provdes various tools to support you with the data transfer.
SAP provides a range of standard data transfer programs and BAPs for loading data into %&'. These
can be called from the /<0!B.
SAP AG BC420 3-26

0.24
SAP AG 1999
The D" .ibrar&
BP!
BP!
BP!
B)
/election of pro,rams that
execute the task
)*er*ie' of 1e,istered D" Pro,rams
n the /<0!B under @Aoto 0= %egister ProgramsB, you can find an overview of all business ob4ects
for which a program has already been registered.
8or most ob4ects SAP provides standard transfer programs or BAPs. These are registered as tas(
type 13A #load$.
f you need other programs for the data transfer, you have to create them. To be able to use them in
the /<0!B, you have to first register them. They have to be assigned to tas( types. 8or e"ample, the
tas( type @MAPB is provided for converting e"ternal data.
SAP AG BC420 3-27

0.26
SAP AG 1999
0appin, Project to the D"#$B
Tasks:
Con*ert data
>
USD
Online
Transaction
Create B! session
Process B! session
SAP format
External
format
06B7<$00
0SB<CS;B
Example
Customer master data
The functions of the /<0!B are e"plained on following slides using the transfer of customer data.
The prere6uisite is that the e"ternal data is available in the file system of the %&' application server.
The following tas(s are to be carried out)
8ormat data
Map data to the target structure
Transfer data into the SAP System
SAP AG BC420 3-28

0.28
SAP AG 1999
)r,ani9ation of Data Transfer Projects
Task n
:
:
:
SAP Standard transfer
"onvert data
"reate customers using "T
"ustomer master record
data
#inancial Accounting
:
Customers
/ubproject
Task 7
Project
1un
5ou can create transfer pro4ects in the /<0!B. 5ou can create, change, display and delete pro4ects,
subpro4ects, runs and tas(s.
SAP AG BC420 3-29

0.+0
SAP AG 1999
Proects are used to group transfer
obects
Project
Creatin, Projects
Project
67
Description
6*!a!c*a1 acco4!t*!2
)bject attributes
Eame of the project
Description of the object
Pro4ects are used to group the transfer of business ob4ects.
8or each 'usiness o'ject t!pe you want to transfer, you must create at least one su'project$ 8or
each subpro4ect, you must create at least one flow definition and one tas(.
Each pro4ect name must be uni6ue within a system, as the name is used as a (ey.
SAP AG BC420 3-30

0.+7
SAP AG 1999
Creatin, /ubproject
Subproects are used to
divide a proect into business
obect t$pes%
Project
67
Subproject
C4"tomer
Description
C4"tomer ma"ter #ata
Object type
=>A1
/election of a*ailable
object t&pes
/ubproject
)bject ttributes
Eame of subproject
)bject description
Business objects in the Business )bject 1epositor& FB)1G.
Subpro4ects are used to subdivide pro4ects. )ach su'project is assi*ned e#actl! one 'usiness
o'ject t!pe whose data is transferred as part of that subpro4ect. !ithin a pro4ect, you can create
several subpro4ects for the same business ob4ect type #for e"ample, subpro4ects for Document data
transfer from plants 1, 2, and 3$.
f after reading all the descriptions of the available ob4ects you cannot find the ob4ect you need, see
the application documentation for more information.
Subpro4ect names in the system must be uni6ue as they are used as a (ey.
SAP AG BC420 3-31

0.+2
SAP AG 1999
Create 1un Definition
Project
67
Subproject
C4"tomer
Run definition Create
Description Create c4"tomer /*th B7
In t&e run definition $ou
specif$ &ow t&e data
transfer for a subproect is
to be transferred%
1un
T&e tasks can be defined in
t&e run
)bject attribute
Eame of run definition
Description of object
n the run specification you specify ho% the data "or a su'project is trans"erred, by creating tas(s
and specifying the files #see Task (n)$. 5ou can create more than one run definition for each
subpro4ect. /epending on the type different methods are possible for each run.
5ou can transfer the data in parallel by creating several run definitions with different file names in
one subpro4ect and then starting parallel runs.
SAP AG BC420 3-32

0.++
SAP AG 1999
Tasks: Con*ersion
Pro:ect
67
S49pro:ect
C4"tomer"
04! #ef*!*t*o! Create
a"k
Se""*o!"
<e"cr*pt*o!
Map #ata
a"k t5pe
MAP
Pro2ram t5pe
?SM-
Define atttributes for
converting wit& t&e 'S()
Input and output files of 'S()
proect are automaticall$
transferred
./0$ Project BC420-@@
7!p4t 6*1e"
5pe >ame
P 9c420++1e2
84tp4t 6*1e"
5p >ame
./0$ /ubproj. <$B7-@@
./0$ )bject B7-@@-7>
?oc+
A
?oc+
A P 9c420+++co!)
<ef*!e Attr*94te"
Task t$pe *(AP+ and program
t$pe *'S()+ are specified as
t&e conversion task
The conversion tas( can be e"ecuted using tas( tape @MAPB.
This tas( can be e"ecuted with the 1SM! tool or with a registered conversion program #for
registration, see .nit @ToolsB$.
To use the 1SM! for this tas(, program type @1SM!B is re6uired.
5ou have to specify the 1SM! pro4ect together with its subpro4ects and ob4ect names for the
maintenance of the attribute mas(. The 1SM! input and output files will then be automatically
transferred.
SAP AG BC420 3-33

0.+5
SAP AG 1999
Tasks: .oadin,
Pro:ect
67
S49pro:ect
C4"tomer"
04! #ef*!*t*o! Create
a"k
?oa#
<e"cr*pt*o!
?oa# #ata
a"k t5pe
?8A
Pro2ram t5pe
B7>P
,eport and variant must be
specified for program t$pe
*-I.P+ or *,EPO+%
1eport 06B7<$00
Hariant AA01
<ef*!e Attr*94te"
a"k e!#e# /*tho4t error"
a"k e!#e# /*th error"
a"k e!#e# /*th error"3 !o re"tart
Task t$pe *'OA+ and program
t$pe *-I.P+ are specified as
t&e load task%
To load data into %&', tas( type @13AB is used. A transfer procedure already registered in the /<0
!B that uses the B method, could now be selected with the program type @B,PB.
An attribute maintenance mas( with the input fields @%eportB and @CariantB appears. The registered
programs can be proposed and selected using 8> input help.
The variant should be created earlier and should contain the file name with the converted data.
SAP AG BC420 3-34

0.+2
SAP AG 1999
/tartin, and nal&9in, 1un
0anuall& set status
& Task 'ith no errors
& Task has errors
& Task terminated 'ith errorsI no restart
/tart
Displa& lo,
................
................
1un
Task 7
Task 2
Task +
:
The actual data transfer from a file is e"ecuted during a run. !hen the run is started, the system
starts all the tas(s in the flow definition by calling the corresponding programs.
Tas(s are automatically e"ecuted in order from top to bottom.
The run stops if there are errors in a tas(.
5ou can e"ecute any number of runs for a flow definition. Each run has a status and a log
#application log$. f needed, you can restart a run that has not completed.
After a tas( of program type %EP3, B,P, or /,P has run, you must define the status. The status of
all other tas(s is set automatically by the tas(.
The following statuses are available for every started run in a flow definition)
Tas( terminated,
Tas( completed without errors
Tas( completed with errors, no restart, and tas( manually ended.
SAP AG BC420 3-35

0.+3
SAP AG 1999
.o,
01+11+1999 10'34'42 08B$0S 5 BC420'++++ <ata ra!"fer
Pro91em c1a"" 8ther 5
04! 00001 Starte#
a"k e"t Starte#
a"k e"t Ma!4a115 Set to Stat4" 1
a"k e"t $%ec4te# -*tho4t $rror"
04! 00001 $%ec4te# -*tho4t $rror"
T&pe 0essa,e text
A log is generated for every e"ecuted run in a flow definition)
To view the log, choose Display log.
The log contains all actions that occur during a pro4ect. Every tas( e"ecuted within a run can create
messages in this log. The pro4ect log itself is contained in the application log.
SAP AG BC420 3-36

0.+4
SAP AG 1999
Processin, 1un Problems
Possible actions for dealin, 'ith runs that 'ere not
completed successfull&:
Cancel run
The run is ended
Continue run
!f a task is ended 'ith an error% this run can be
continued 'ith this task
End task
The task 'ith the error is ended and subseAuent tasks are executed
Delete run
Current lo, is deleted. !f attributes of the run are to be
chan,ed% all lo,s must be deleted.
f a run did not complete successfully, you can choose from the possible actions)
-ontinue run)
To complete a run that did not finish successfully, fi" the error using the log as a source of error
information, position the cursor on the run / #for e"ample, ::'$, and choose Continue run.
-ancel run)
f a run cannot be completed, cancel the run by choosing Cancel run.
This run must be canceled before any other run can be e"ecuted.
-ancel tas(
f a tas( has not been completed, you can still set it to completed by choosing Cancel task. !hen
the run is continued, this tas( will be s(ipped.
/elete run
5ou can delete runs that have completed or been manually terminated, by choosing Delete run.
SAP AG BC420 3-37

0.+6
SAP AG 1999
Describe the data transfer methods
Describe the tasks in a transfer project
Explain the use of business objects and BP!s
Create a data transfer project in the D" # $B and
execute a customer data transfer
Jou are no' able to:
Project Concept : (nit /ummar&
SAP AG BC420 3-38

)#ercises
+nit: Project ,oncept
-opic: ,reate .ata -rans"er Project in ./-0B

-reating a transfer pro4ect in the /<0!B and using it to
transfer debtor data in the %&' system. To do this you have to
create a pro4ect, a subpro4ect, a flow and three tas(s in the data
transfer wor(bench.
/ebtor data from a legacy system will be imported with an
internal number assignment into the %&' system.
Project: 1I-22
u'project: .)B-22
3un: BI-22
-as&s: 4(P-225 L6(-225 4,22
Load pro*ram: 31BI.)77
A pro4ect is to be created in the data transfer wor(bench. This pro4ect consists of three tas(s.
The first tas( uses the 1SM! to convert a source file with debtor data into a target file. The
second tas( creates a B session using the standard transfer program %8B/E::. Program
%8B/E:: re6uires the target file from the 1SM!. The third tas( processes the B session
automatically)
* -reate a trans"er project.
*0* n the /<0!B create pro4ect FI- with the name FI !roup-.
,ote) Specify the group number in the description as mentioned above.
*0+ .nder the pro4ect, create the subpro4ect D"#- with the description De$tors
and the ob4ect type D,A*.
*0' -reate the run B0EE with the description Transfer %it& #I under the subpro4ect.
SAP AG BC420 3-39

*0> -reate the following three tas(s. The tas(s represent the following process
steps) ,onvert data5 ,reate BI session and Process B(I session$
*0>0* -reate the following tas( in the run B0EE)
0 Tas() MAP0EE
0 /escription) -onvert data
0 Tas( type) MAP
0 Program type) 1SM!
Select the following 1SM! ob4ect)
1SM! pro4ect) B->+:0EE
1SM! subpro4ect) /EB0EE
1SM! 3b4ect) B0EE0,T
*0>0+ n run B0EE create the following tas()
0 Tas() 13A0EE
0 ,ame) -reate B session
- Tas( type) 13A
0 Program type) B,P
Select the program %8B/E:: with the variant B0,0EE.
*0>0' n run B0EE create the following tas()
0 Tas() MS-0EE
0 ,ame) Process B session
- Tas( type) MS-
0 Program type) %EP3
Select program %SB/-S.B with the variant S.B0,0EE.
,ote that you have to correct the se6uence of the tas(s. ,onvert data5 create
BI session and process BI session$ .se buttons) &
*0F Select the run #mouse clic($. Start the run by choosing button 'tart run(
The programs are started. -onfirm all tas(s manually.
*0? The debtors are created with internal number assignment.
*0G /isplay the log.
SAP AG BC420 3-40

olutions
,hapter: Project ,oncept
* Start the /<0!B
*0* n the tree structure display select Data Transfer )ro*ects .
-reate the pro4ect FI- with the name FI !roup-( .se the Create )ro*ect
button(
*0+ Select your pro4ect in the tree structure display. n the pro4ect create the
subpro4ect D"#- with the name De$tors and the ob4ect type D,A*. .se the
Create 'u$pro*ect button(
*0' Select your subpro4ect in the tree structure display. n the subpro4ect create the
run B0EE with the name Transfer %it& #I. .se the Create +un Definition button.
SAP AG BC420 3-41

*0> Select your run definition in the tree structure display.
-reate the following three tas(s. The tas(s represent the following process steps)
convert data, create B session, process B session.
.se the Create task button.
*0>0* n run B0EE create the following tas()
0 Tas() MAP0EE
0 ,ame) -onvert data
0 Tas( type) MAP
0 Program type) 1SM!
-hoose Continue to define the attributes for the 1SM!.
Select the following 1SM! ob4ect)
1SM! pro4ect) B->+:0EE
1SM! subpro4ect) /EB0EE
1SM! ob4ect) B0EE0,T
*0>0+ n run B0EE create the following tas()
0 Tas() 13A0EE
0 ,ame) -reate B session
- Tas( type) 13A
0 Program type) B,P
Select program %8B/E:: with the variant B0,0EE.
*0>0' n run B0EE create the following tas()
0 Tas() MS-0EE
0 ,ame) Process B session
- Tas( type) MS-
0 Program type) %EP3
Select program %SB/-S.B with the variant S.B0,0EE.
,ote that you have to correct the se6uence of the tas(s. ,onvert data5 create
BI session and process BI session$ .se buttons) &
*0F Select the run #mouse clic($. Start the run by choosing 'tart run(
The tas( MAP0EE of 1SM! will be e"ecuted automatically.
Program %8B/E:: is called. The selection screen appears. Start the program.
The B session is created. 1eave the program using the 8' button. -onfirm the
status Task ended %it&out errors.
Program %SB/-S.B is called. The selection screen appears. Start the program.
The B session is processed. 1eave the program using the 8' button. -onfirm
the status Task ended %it&out errors.
*0G Select and display the log.
SAP AG BC420 3-42