Sunday, August 31, 2008

The Basics - What's RICEF

What is RICEF? Many a times asked in interviews! Unfortunately a lot of people fail to
answer a simple question even thou!h workin! on it for years"
#ou usually $ome a$$ross the word RICEF when sear$hin! for %&' &(&' )eveloper *o+s"
RICEF isn,t a standard %&' a$ronym" It,s not defined +y %&' like we have &(&' &-.
et$" It,s a $omon term used to des$ri+e five areas of te$hni$al developments in %&'"
RICEF stands for Reports Interfa$es Conversions Enhan$ements Forms"
R- Reports
R stands for Report developments" &ll the te$hni$al o+*e$ts/developments that deal
with pro!ramin! of %&' Reports" It in$ludes different types of reports0 %imple reports
where you output usin! WRI1E statements %imple &-. reports &-. 2rid &-. 2rid with
advan$ed fun$tionalityet$"
I - Interfaces
I stands for Interfa$e developments" Interfa$es are &-E/I)3Cs development" Involves
not *ust &(&' pro!rammin! for I)3Cs +ut also I)3C $ustomi4ation"
C - Conversion
C stands for $onversion o+*e$ts" Conversion refers to ()C pro!ramin!" )ata upload
from le!a$y system in flat files format to %&' system is done via Conversion 3+*e$ts"
1his involves uploadin! data throu!h ()C -%MW (&'I et$"
E - Enhancements
Enhan$ements are User E5its Customer E5its (&)I,s et$" &(&' $ode that has to +e
written in order to enhan$e %&' system fun$tionality"
F - Forms
Forms in$lude %&' %martforms %&' %$ripts" 1e$hni$al development that deals with
fet$hin! ne$essary data from %&' system and displayin! in terms of forms for printout
are $lassified as under Forms"
Common questions :-
6" &s an &(&'er why do I $are what RICEF means? What does it have to do with me?
Well it,s really simple" It,s *ust that one must know the $ate!ory of the te$hni$al
development he is workin! upon"
7" What,s the use of RICEF?
%&' 'ro*e$t mana!ers usually refer te$hni$al development in terms of RICEF o+*e$ts"
'ro*e$t te$hni$al team leads usually distin!uish the o+*e$ts +ased on this
$ate!ori4ation and assi!n them to team on +asis of e5perien$e" Reports +ein! a first
$hoi$e for +e!inners and Enhan$ements +ein! the favourite $hoi$e for e5perts"
CONVERSION : Legacy System To Flat File.
INTERFACE : Flat File to SAP System.
When you tans!e legacy "ata into the R#$ System% you nee" to ensue that it is
in the SAP !omat. Thee ae se&eal 'ays o! "oing this:
Con&eting the "ata in the legacy system has the a"&antage that the use is
!amilia 'ith the (ogamming language that it uses.
Con&eting the "ata in the R#$ System using A)AP has the a"&antage o!
automatic ty(e con&esion. *ou can use the stuctue "e+nitions o! the A)AP
,ictionay "iectly.
Con&eting the "ata 'ith E-cel. *ou can use this metho" !o sim(le an" com(le-
con&esions !o .at stuctues.
*ou use inte!aces "e+ne" /y SAP !o the stan"a" tans!e. The legacy "ata must
/e "eli&ee" in a suita/le !omat to su((ly these inte!aces. The inte!ace
"esci(tions ae "e+ne" in the R#$ System an" the tans!e metho" is "e&elo(e"
an" !omulate" acco"ing to these "esci(tions.
,IFFERENCE )ETWEEN CONVERSION AN, INTERFACE:
A Con&esion means "ata that is con&ete" !om one !omat to anothe !omat an"
!om one system to anothe.So 'hen you +st im(lement SAP% you ae actually
e(lacing some o! you legacy systems% /ut you ae not com(letely tashing the
"ata. *ou still nee" some o! that "ata !om the systems that ae /eing e(lace". So
you (ull the "ata out o! you legacy systems an" (ut them on some +les. *ou then
'ant to loa" that "ata into you ne' SAP system.
That is 'hen you 'ite some (ogams 'hich 'ill ea" that "ata an" loa" it into SAP.
Imagine you ha" a home go'n (uchasing system. *ou ae no' e(lacing all that
'ith SAP. )ut until SAP goes li&e% you 'ant to 0ee( using you home go'n
(uchasing system.So "uing go li&e% you 'ant to tans!e the POs !om you legacy
system to SAP. No' a PO in you legacy system may not ha&e the same +el"s as a
PO in SAP. So you con&et the "ata.
E-: ),C%LS1W
Inte!acing is connecting t'o o moe "i2eent entities. In ou case% it is connecting
one o moe systems 'ith SAP. No' e-ten"ing ou (e&ious e-am(le% you ae
e(lacing some legacy a((lications /ut thee ae some a((lications that you "on3t
'ant to e(lace yet.
*ou nee" to someho' (ass "ata /ac0 an" !oth /et'een SAP an" these emaining
systems. ,ata may /e going one 'ay o the othe 'ay o /oth 'ays. *ou 'ill still
nee" to "o some "ata tans!omations#tanslations etc to ma0e the "ata
un"estan"a/le to the ecei&ing system.
This 'ill continue as long as you 'ant to 0ee( the systems unning alongsi"e SAP.
E-: i"oc%/a(i
In shot% con&esions ae 'itten to loa" "ata into SAP onetime. These ae ty(ically
+le /ase".
Inte!aces ae 'itten to e-change#u("ate#sen"#ecei&e "ata /et'een SAP an" othe
systems on an ongoing /asis. These can /e in many !oms% +le /ase"% i"oc /ase"%
eal time4/usiness connecto% 5I etc ae use!ul in this6% -ml% an" the list goes on.
Input and Output Conversions
Depending on the data type of the field, there is a conversion when the contents of a screen field are
converted from display format to SAP-internal format and vice versa. If this standard conversion is not
suitable, it can be overridden by defining a conversion routine in the underlying domain.
Conversion routines are identified by a five-place name and are stored as a group of two function
modules. he function modules have a fi!ed naming convention. he following function modules are
assigned to conversion routine !!!!!"
C#$%&'SI#$(&)I(!!!!!(I$P*
C#$%&'SI#$(&)I(!!!!!(#*P*
he I$P* module converts from display format to internal format, and the #*P* module converts
from internal format to display format.
When is a Conversion Routine Executed?
If a screen field refers to a domain with a conversion routine, this conversion routine is e!ecuted
automatically when entries are saved in this screen field or when values are displayed in this screen field.
he conversion routine of the domain is also triggered when the field contents are output with the +'I&
statement.
able SP,-I in the flight model contains information about the flights offered by the
carriers. he time for each flight is recorded in field ,-I.&. &nter and display the time of
the flight in input templates in the form ///".. 0hours"minutes1. Store the flight time
entered in the database as an integer number 0number of minutes of the flight1. An entry
2"34 is therefore stored in the database as 354 02 hours, 34 minutes 6 354 minutes1.
,ield ,-I.& refers to domain S(D*'A, to which conversion routine SD*'A is
assigned. he value is thus converted by the two function modules
C#$%&'SI#$(&)I(SD*'A(I$P* and C#$%&'SI#$(&)I(SD*'A(#*P*.
A conversion routine can also be triggered by specifying its five-place name in the attributes of a field in
the Screen Painter or with the addition USING EDIT MASK <Name of conversion routine> in the +'I&
command in the program. +ith the USING NO EDIT MASK addition in the +'I& statement, you can
s7ip a conversion routine defined for a domain when outputting.
Parameters
he two function modules of a conversion routine must have precisely two parameters with the names
I$P* and #*P* for the value to be converted and the converted value.
he I$P* parameter in the I$P* conversion and the #*P* parameter in the #*P* conversion
should not have any reference fields because the value passed in the call could have a different length
than that e!pected.
Programming Conversion Routines
A8AP statements that result in an interruption of processing 0such as CA-- SC'&&$, CA-- DIA-#9,
CA-- 'A$SACI#$, S*8.I, C#..I +#':, '#--8AC: +#':, .&SSA9& I, .&SSA9& +1 are
not allowed in conversion routines.
#nly A messages are meaningful in output conversion, but A, & and S messages can be triggered in input
conversion 0although S messages are not very meaningful here1. & messages result in an error dialog.
&!ceptions are not intercepted in the call.
he output conversion is also triggered with +'I& and +'I& #. he conversion routine may
therefore occur very fre;uently with lists. he output conversion should therefore be programmed as
efficiently as possible.
$o e!ternal performs should be used in conversion routines. Programs that are called e!ternally use the
table wor7 areas of the first calling main program. In conversion routines this can result in errors that
cannot be easily analy<ed since they are sometimes called at unpredictable times in the program flow.
Type Conversions
&very time you assign a data ob=ect to a variable, the data types involved must either be compatible , that
is, their technical attributes 0data type, field length, number of decimal places1 must be identical, or the
data type of the source field must be convertible into the data type of the target field.
In A8AP, two non-compatible data types can be converted to each other if a corresponding conversion
rule e!ists. If data types are compatible, no conversion rule is necessary.
If you use the .#%& statement to transfer values between non-compatible ob=ects, the value of the
source ob=ect is always converted into the data type of the target ob=ect. +ith all A8AP operations that
perform value assignments between data ob=ects 0for e!ample, arithmetic operations or filling internal
tables1, the system handles all the necessary type conversions as for the .#%& statement. If you try to
assign values between two data types for which no conversion rule e!ists, a synta! error or runtime error
occurs.
he following sections contain the conversion rules for incompatible A8AP data types"
Conversion 'ules for &lementary Data ypes
Conversion 'ules for 'eferences
Conversion 'ules for Structures
Conversion 'ules for Internal ables
+ith some A8AP statements that pass data between different ob=ects, the alignment of the data ob=ects is
also important.
Alignment of Data #b=ects

Conversion Rules for Elementary ata Types
here are eight predefined A8AP data types. here are >? possible type combinations between these
elementary data types. A8AP supports automatic type conversion and length ad=ustment for all of them
e!cept type D 0date1 and type 0time1 fields which cannot be converted into each other.
he following conversion tables define the rules for converting elementary data types for all possible
combinations of source and target fields.
!ource Type Character
Conversion ta"le for source type C
Target Conversion
C he target field is filled from left to right. If it is too long, it is filled with blan7s from the right. If it
is too short, the contents are truncated at the right-hand end.
D he character field should contain an @-character date in the format AAAA..DD .
, he contents of the source field must be a valid representation of a type , field as described
in -iterals .
$ #nly the digits in the source field are copied. he field is right-=ustified and filled with trailing
<eros.
I
P
he source field must contain the representation of a decimal number, that is, a se;uence of
digits with an optional sign and no more than one decimal point. he source field can contain
blan7s. If the target field is too short, an overflow may occur. his may cause the system to
terminate the program.
he character field should contain a >-character time in //..SS format.
) Since the character field should contain a he!adecimal-character string, the only valid
characters are 5,B,3,2,?,C,>,4,@,D,A,8,C,D,&,,. his character string is pac7ed as a
he!adecimal number, transported left-=ustified, and padded with <eros or truncated on the
right.

!ource Type ate
Conversion ta"le for source type
Target Conversion
C he date is transported left-=ustified without conversion.
D ransport without conversion.
, he date is converted into a pac7ed number. he pac7ed number is then converted into a
floating point number 0see corresponding table1.
$ he date is converted into a character field. he character field is then converted into a
numeric te!t field 0see corresponding table1.
I
P
he date is converted to the number of days since 5B.5B.555B.
$ot supported. 'esults in an error message during the synta! chec7 or in a runtime error.
) he date is converted to the number of days since 5B.5B.555B in he!adecimal format.

!ource Type #loating Point $um"er
Conversion ta"le for source type #
Target Conversion
C he floating point number is converted to the EmantissaF&Ee!ponentF format and transported
to the character field. he value of the mantissa lies between B and B5 unless the number is
<ero. he e!ponent is always signed. If the target field is too short, the mantissa is rounded.
he length of the character field should be at least > bytes.
D he source field is converted into a pac7ed number. he pac7ed number is then converted
into a date field 0see corresponding table1.
, ransport without conversion.
$ he source field is converted into a pac7ed number. he pac7ed number is then converted
into a numeric te!t field 0see corresponding table1.
I
P
he floating point number is converted to an integer or fi!ed point value and, if necessary,
rounded.
he source field is converted into a pac7ed number. he pac7ed number is then converted
into a time field 0see corresponding table1.
) he source field is converted into a pac7ed number. he pac7ed number is then converted
into a he!adecimal number 0see corresponding table1.

!ource Type Integer
ype I is always treated in the same way as type P without decimal places. +herever type P is
mentioned, the same applies to type I fields.

!ource Type $umeric Text
Conversion ta"le for source type $
Target Conversion
C he numeric field is treated li7e a character field. -eading <eros are retained.
D he numeric field is converted into a character field. he character field is then converted into
a date field 0see corresponding table1.
, he numeric field is converted into a pac7ed number. he pac7ed number is then converted
into a floating point number 0see corresponding table1.
$ he numeric field is transported right-=ustified and padded with <eros or truncated on the left.
I
P
he numeric field is interpreted as a number, and transferred to the target field, where it is
right-=ustified, and adopts a plus sign. If the target field is too short, the program may be
terminated.
he numeric field is converted into a character field. he character field is then converted into
a time field 0see corresponding table1.
) he numeric field is converted into a pac7ed number. he pac7ed number is then converted
into a he!adecimal number 0see corresponding table1.

!ource Type Pac%ed $um"er
If the program attribute Fixe !oint arit"metic is set, the system rounds type P fields according to the
number of decimal places or fills them out with <eros.
Conversion ta"le for source type P
Target Conversion
C he pac7ed field is transported right-=ustified to the character field, if re;uired with a decimal
point. he first position is reserved for the sign. -eading <eros appear as blan7s. If the target
field is too short, the sign is omitted for positive numbers. If this is still not sufficient, the field is
truncated on the left. A8AP indicates the truncation with an asteris7 0G1. If you want the leading
<eros to appear in the character field, use *$PAC: instead of .#%&.
D he pac7ed field value represents the number of days since 5B.5B.555B and is converted to a
date in AAAA..DD format.
, he pac7ed field is accepted and transported as a floating point number.
$ he pac7ed field is rounded if necessary, unpac7ed, and then transported right-=ustified. he
sign is omitted. If re;uired, the target field is padded with <eros on the left.
I
P
he pac7ed field is transported right-=ustified. If the target field is too short, an overflow occurs.
he pac7ed field value represents the number of seconds since midnight and is converted to a
time in //..SS format.
) he pac7ed field is rounded if necessary and then converted to a he!adecimal number.
$egative numbers are represented by the twoHs complement. If the target field is too short, the
number is truncated on the left.

!ource Type Time
Conversion ta"le for source type T
Target Conversion
C he source field is transported left-=ustified without conversion.
D $ot supported. 'esults in an error message during the synta! chec7 or in a runtime error.
, he source field is converted into a pac7ed number. he pac7ed number is then converted
into a floating point number 0see corresponding table1.
$ he date is converted into a character field. he character field is then converted into a
numeric te!t field 0see corresponding table1.
I
P
he date is converted to the number of seconds since midnight.
ransport without conversion.
) he date is converted to the number of seconds since midnight in he!adecimal format.

!ource Type &exadecimal
Conversion ta"le for source type '
Target Conversion
C he value in the he!adecimal field is converted to a he!adecimal character string, transported
left-=ustified to the target field, and padded with <eros.
D he source field value represents the number of days since 5B.5B.555B and is converted to a
date in AAAA..DD format.
, he source field is converted into a pac7ed number. he pac7ed number is then converted
into a floating point number 0see corresponding table1.
$ he source field is converted into a pac7ed number. he pac7ed number is then converted
into a numeric te!t field 0see corresponding table1.
I
P
he value of the source field is interpreted as a he!adecimal number. It is converted to a
pac7ed decimal number and transported right-=ustified to the target field. If the he!adecimal
field is longer than ? bytes, only the last four bytes are converted. If it is too short, a runtime
error may occur.
he source field value represents the number of seconds since midnight and is converted to a
time in //..SS format.
) he value is transported left-=ustified and filled with )H55H on the right, if necessary.

https"IIhelp.sap.comIsaphelp(?>cIhelpdataIenIfcIeb2?2?2C@?BBdB@3Df5555e@3DfbfeIcontent.htm
Type Conversions
&very time you assign a data ob=ect to a variable, the data types involved must either be compatible , that
is, their technical attributes 0data type, field length, number of decimal places1 must be identical, or the
data type of the source field must be convertible into the data type of the target field.
In A8AP, two non-compatible data types can be converted to each other if a corresponding conversion
rule e!ists. If data types are compatible, no conversion rule is necessary.
If you use the .#%& statement to transfer values between non-compatible ob=ects, the value of the
source ob=ect is always converted into the data type of the target ob=ect. +ith all A8AP operations that
perform value assignments between data ob=ects 0for e!ample, arithmetic operations or filling internal
tables1, the system handles all the necessary type conversions as for the .#%& statement. If you try to
assign values between two data types for which no conversion rule e!ists, a synta! error or runtime error
occurs.
he following sections contain the conversion rules for incompatible A8AP data types"
How to convert date format to MM/DD/YYYY
This question is !"t Ans#e$ed%
Senthilkumar T N No& 78% 9::; <:$; A1
Hi,
How to convert date format to MM/DD/YYYY.

Thanks,
Senthil
Helpful Answer /y sasi0uma (alanichamy
=:<$ Vie's
o Topics: A)AP

A&eage >se Rating

4: atings6
Re: How to convert date format to MM/DD/YYYY
era enkata Nekenti No& 78% 9::; <:<< A1 4in es(onse to Senthil0uma
T N6
WRT!" s#$datum MM/DD/YYYY
.
o Re(ot A/use
o Li0e 4:6
o Re: How to convert date format to MM/DD/YYYY
Senthilkumar T N No& 78% 9::; <:;7 A1 4in es(onse to Vea
Ven0ata Ne0enti6
Hi %enkat,
want to assi&n MM/DD/YYYY foramt to another varia'le. So is there is
an# function is availa'le otherwise how to convert a(art from usin& write
statement.

Thanks,
Senthil
Re(ot A/use
Li0e 4:6
Re: How to convert date format to MM/DD/YYYY
Ra!hava M"needu No& 78% 9::; <:;8 A1 4in es(onse to
Senthil0uma T N6
Senthil ,
You can also tr# this
Date ) YYYYMMDD
*oncatenate date4(2) / date+,-. //0 date,1. into Date-.

*heers
Ra&hava
Re(ot A/use
Li0e 4:6
Re: How to convert date format to MM/DD/YYYY
era enkata Nekenti No& 78% 9::; ;::: A1 4in es(onse to Senthil0uma
T N6
data " l2date,34. t#(e c .
concatenate s#$datum6(2) '/' sy-datum1,-. 5/5 s#$datum,1. into l2date.
write " l2date.
o Re(ot A/use
o Li0e 4:6
Helpful Answer Re: How to convert date format to MM/DD/YYYY
sasikumar palanicham" No& 78% 9::; ;::; A1 4in es(onse to
Senthil0uma T N6
hi,

tri with this function module

data "l2date,34. t#(e c

*677 89:*T;: 5*;:%!RT2D6T!2T;2!<T!R:675
!<=;RT:>
D6T!2:T!R:67 ) SY$D6T9M
M=;RT:>
D6T!2!<T!R:67 ) l2date.


this function module converts date from -44?4+43 to e@ternal format which is s(ecified
in user (rofile

cheers,
sasi
o
A#A$ % &unction module for convertin! an"
'(ternal date format to )nternal format

A""e" /y Naen"an 1uthu0umaan% last e"ite" /y ?uest on A( 9@% 9::=

4&ie' change6
Auth"$& :arendran Muthukumaran
Su'(itted& 41/-?/-44A
)esc$i*ti"n& This is function module can 'e used for convertin& an# !@ternal date format to
nternal format.
The followin& S6=5s e@ternal formats which can 'e found in the user settin&s are su((orted in
this function module.
DD.MM.YYYY
MM/DD/YYYY
MM$DD$YYYY
YYYY.MM.DD
YYYY/MM/DD
YYYY$MM$DD
The function module needs to created with the (arameters as mentioned in the code.
FUNCTION z_convert_to_internal_format.
*"----------------------------------------------------------------------
*"*"Local interface:
*" IMPORTIN
*" !"LU#$IM_INPUT% T&P# C'"R()
*" #*PORTIN
*" !"LU#$#*_OUTPUT% T&P# +&,"TUM
*" #*C#PTION+
*" IN!"LI,_,"T#
*"----------------------------------------------------------------------
* et t-e format.
* ,,.MM.&&&&
IF im_in./t01$(% 2 3.3.
CONC"T#N"T# im_in./t04$5% im_in./t06$1% im_in./t$1% INTO e7_o/t./t.
#N,IF.
* MM8,,8&&&&
IF im_in./t01$(% 2 383.
CONC"T#N"T# im_in./t04$5% im_in./t$1% im_in./t06$1% INTO e7_o/t./t.
#N,IF.
* MM-,,-&&&&
IF im_in./t01$(% 2 3-3.
CONC"T#N"T# im_in./t04$5% im_in./t$1% im_in./t06$1% INTO e7_o/t./t.
#N,IF.
* &&&&.MM.,,
IF im_in./t05$(% 2 3.3.
CONC"T#N"T# im_in./t$5% im_in./t09$1% im_in./t0:$1% INTO e7_o/t./t.
#N,IF.
* &&&&8MM8,,
IF im_in./t05$(% 2 383.
CONC"T#N"T# im_in./t$5% im_in./t09$1% im_in./t0:$1% INTO e7_o/t./t.
#N,IF.
* &&&&-MM-,,
IF im_in./t05$(% 2 3-3.
CONC"T#N"T# im_in./t$5% im_in./t09$1% im_in./t0:$1% INTO e7_o/t./t.
#N,IF.
* C-ec; t-e vali< <ate.
C"LL FUNCTION 3,"T#_C'#C=_PL"U+I>ILIT&3
#*PORTIN
<ate 2 e7_o/t./t
#*C#PTION+
.la/?i@ilitA_c-ec;_faile< 2 (
OT'#R+ 2 1.
* C-ec; if t-e o/t./t .arameter i? .o./late<. ot-erBi?e rai?e an
* e7ce.tion.
IF e7_o/t./t I+ INITI"L OR ?A-?/@rc CD ).
R"I+# invali<_<ate.
#N,IF.
#N,FUNCTION.
T6B7!S v'ak.
D6T6 "B!>: ;8 ita' ;**9RS 4,
v'eln 7C! v'ak$v'eln,
erdat 7C! v'ak$erdat,
!:D ;8 ita'.
D6T6 "l2date,34. TY=! c.
S!7!*T$;=T;:S" s2v'eln 8;R v'ak$v'eln.
S!7!*T v'eln erdat 8R;M v'ak
:T; T6B7! ita'
WH!R! v'eln : s2v'eln.
7;;= 6T ita'.
DM;%!"ita'$erdat T; s#$datum.
D*677 89:*T;: 5;=!:28;RM5
D !<=;RT:>
D device ) 5=R:T!R5
D dialo& ) 5<5
D form ) 5Escri(t2test 5
D lan&ua&e ) s#$lan&u.
D
D*677 89:*T;: 5Write2form5
D!<=;RT:>
D element ) 5address5
D function ) 5set5
D T#(e ) 5Bod#5
D window ) 5Main5.
*677 89:*T;: 5*;:%!RT2D6T!2T;2!<T!R:675
!<=;RT:>
date2internal ) ita'$erdat
M=;RT:>
date2e@ternal ) l2date.
WRT!" / l2date.
!:D7;;=.
What is B)C- its use, and h"# t" use it
t is Batch Data conversion used for transferrin& some data other than sa( into sa( ... this is also a
work of an 6B6=er.
What is +,TS+ -$ (ay 'e it is +,ST+, s"(ething ca..ed ,nit test
9se" 6fter develo(in& an# o'Fect we should write a test case (rovin& that the o'Fect is workin&
(ro(erl# or not. This is done '# the 6B6=er. This is 9:T T!ST *6S!.
In B)C h"# can #e hand.e Ta'.e C"nt$".s
When #ou do #our recordin& #ou will have a ta' for :e@t line or nsert. You have to ca(ture that
in #our recordin&. f #our transaction code doesn5t have that in the recordin& then #ou have to set
u( a (a&e down ,)=G. and loo( it 'ased on the line entries u c on teh screen.
Su**"se #e a$e t$ans/e$ data th$"ugh B)C /$"( .eagacy t" SA0 and thei$ is s"(e
du*.icate data in .egacy syste( 'ut #e d"n't #ant this in SA0 syste( %S" h"# can #e chec1
that this data is a.$eady e2ist
n BD* #ou would have all #our le&ac# data in an internal ta'le. 9se Delete 6dFacent dul(icates
s#nta@ to delete du(licate entries.
Can #e use t#" t$ansacti"n c"de in "ne B)C .i1e 3401 5 3)01 i/ yes h"#
Yes, we can do that '# com'inin& the two 'dc (ro&ram codes to&ether. Then #ou (erform the
(ro&ram routine accordin&l#. However, it will make #our BD* (ro&ram ver# lon& and com(le@.
6"# can #e hand.e e$$"$s in Functi"n 7"du.e
!@ce(tions is used to handle errors.
Can #e use Sessi"n (eth"d 5 Ca.. t$ansacti"n '"th in "ne B)C i/ yes *.ease gi8e (e
e2a(*.e and scene$i" #he$e #e use this
You start #our dataload usin& *all Transaction and if an# errors occur (ush all those errors in a
session so that #our dataload takes (lace uninterru(ted and #ou can (rocesss ur errors later.