whether the data is posted in receiver system or not is known through message ty

pe ALEAUD & STATUS

ALEAUD (ALE AUDIT )
This message type confirms about the application data posted succesfully in rec
eiver system
ALEAUD can be used only between two SAP systems
SAP & NON SAP system used message type STATUS for acknowledgement
Working with ALEAUD message Type :
Configration at receiver side.
1. maintain outbound paramters with message type ALEAUD & IDOC type ALEAUD01
2.Execute the report RBDSTATE with variant SAP_AUDIT_SEND ,

Inbound side configrationL

Maintain an inbound paramter at partner profiole with process code as AUD1
Note: In realtime the report RBDSTATE is scheduled in the background with varian
t SAP_AUDIT_SEND in the production server
When this report is run , it send the status of all succesfully posted IDoc i.e
(status 53 ) at receiver side, to sender .
At sender side all the iDoc whose status is 03 is changed to status 43
Q. what is chnage pointer technique ?
sol: change pointer is technique which triggers the IDoc posting when ever the m
aster data is created or changed
The advantage of change pointer is when ever a master data is changed instead of
sending entire data , it only sends the changes .
Note: Matser data is distributes using SMD tool ( shared master data ) where as
transactional data is distributed using Message control.
Q.How a change pointer works?
sol: when ever the data is changed or created its logged in table CDHDR & CDPOS
Change pointer program BD21(or RBDMIDOC) is scheduled in the background in real
time,.
when ever this program runs , it reads the chaged records from CDHDR & CDPOS and
, then it looms in table BDCP to check whether chage pointer is activated for t
hat particular message type or not.
If change pointer is activated for the message type in question , then it reads
the status of change pointer from BDCPS , to check whether changes has been sent
to receiver system or not .If the status flag is initial , it will send the cha
nges to receiver system and update the BDCPS table
CDHDR : Chnage document Header
CDPOS: Change DOcument Item
BDCP : Change pointer
BDCPS: Change pointer status :
PROCESS = 'x' changes are sent
= space change snot sent
(BDCP2)

Steps for configuring change pointer:

1. activte the chnage pointer using BD61
2. Activate the message type for chnage pointer using BD52
3. To send the chnages execute the tcode BD21 or prog RBDMIDOC
Q. what you mean by serialization in ALE_IDoc ?
sol: Serilzation is a technique which si used when ever we transfer dofferent ID
Ocs and we wanted to update the data at receiver side in a serialized way
ex:Materail master can also have classification data . Thsi classification data
is transferred using message type CLFMAS where as material master is transffered
using MATMAS.
If both are sent in order from sender , there are chances the CLFMAS can jump th
e queue even before matmas is updated
To avoid such situation we serilize the data
Steps:
1. First create a serial group using BD44 and assign the message types
2. BD40 : Genarate IDoc for serialization message type
3. BD41 : Dispatch IDocs from sender to receiver
By doing so , the IDocs are sent to receiver system , and have a status 64(IDoc
ready to be transferred to application)
4. BD42 :
This informs the receiver system to start processing the IDoc .
when this tcode is executed it send the message type SERDAT to inform the reciev
er that all data is tranfeereds from sender side , now it can start processing I
Doc with status 64
5. BD43 : ssame job of BD42 can be done at receiver side .
If we execute the tcode BD43 at receiver side , it posts all IDOcs in a serializ
ed manner
Q.
1.
2.
3.
4.

what are the differenbt techniques for serialization?

serialization using message type
serialization using time stamps
serialization using business objects
serialization using qRFC

DEBUGGING :
q. what is the difefrence between classical debugger & new debugger ?
sol: Classical debugger runs in one session where as new debugger runs in two se
ssion
i,.e when we use classical debugger we cannot see the program where as new debug
ger we can also see program screen
or
in classical debugger the bebugee and debugger both are in one session wher as i
n new debugger debuggersesion opens in an external session
2. In classical debugger , debugging statement like selct...endselect leads to r
untime error ( coz internal commit happens in classical debugger which leads the
datbase cursor lost from database )
where as using new debugger we can debug any statements
3. New debugger have 3 custom desktops that can be customized as per user
4. Many new tools are included in new debugger like comparison of two internal d
ata , variables , object reference etc

5.New debugger also supports the XML data view

q. How to debug a update function modules and RFC ?
sol:Update function mdoules are used to update all the data in a group. Till the
n the data is stored in a view VBLOG .
when ever the program encounters the commit work statement , it reads the data f
rom VBLOG and updates the records .
syantx: call <func mod name> in update task
To debug an update function module tuirn the update debugging on from the debugg
er screen
settings->display/chnage debugger settings ->update debugging
RFC
syntax:
call <fm name> in background task.
RFC function modules can be debugged by turning the option Trfc in backround tas
k
By doing so it submits the RFC for background execution in SM58
Then from SM58 we can execute th program and it takes to the debugging mode
Q. what is a watch point ?
watch point is used to monitor the values of a program
30 watch point in new debugger .
ex: suppose while loop a record , and if wanted the program to get into debug mo
de when the work area has value 100 , then create a watchpoint for the required
workarea variable i.e wa_vbak-vbeln = 100
How to change any variable in debugger ?
sol: double cklick the variable and click the pencil symbol , it gets into chang
e mode , chnage the data and hit enter
Note: Only after hitting enter the record is updated