1)

In this error sometimes while data load there are few lock in the BI or source system due to which it takes a lot of t

2)

if any request is in red it doesn't mean it is wrong we need to check it's message sometimes it shows process is ov

3)

If any errors occurs then we need to make that request red in the rsmo then delete it in the data target else sometim

4)

Sometimes while data load some of the data packages are not updates that it out of 100 data packages 5-6 are

5)

sometimes special Hex characters are available in the data load due to which error will ocure so in that case we ne

6)

sometimes while DSO data activation it gives an error so in that case we need to check manually activate DSO dat

7)

through SM37 we can cancel the data load or can chek the status of our data load request or can change the da

8)

in case of data load fail then you can repeat the particular load step for that go to RSPC process chain select the b

9)

For daily data load RSMO,RSPC,SM37 tcodes are very imp.for APD data loadgo to SM37 check BI_process

to which it takes a lot of time for data loading so through this spet wen and view lock in BI system then can release it by selecting that partic

es it shows process is overdue in that case IDOCS are not available for data load so we need to reduce the system load by canceling few o

e data target else sometimes it is running in the back ground

0 data packages 5-6 are in red and are in green so we need to manually make those 5-6 data packages greenbut make sure u don't clos

ure so in that case we ned to modify/correct that error in the PSA/DSand the again need to execute DTPOT through RSKC tcode we

manually activate DSO dataor sometimes it won't allow DSO data activation at all then we can uncheck DSO setting SID generation whil

st or can change the data load server

rocess chain select the box where the error has occurred ..right click and select repeat option..

o SM37 check BI_process_abapor go to rsanwb tcode and check data load if APD is in process chain then u can onitor process chain thro

e it by selecting that particular request and pressing F6 for release.....if the locks are in the source system then also we can release by sele

m load by canceling few other loads or by releasing those overdue requests

ut make sure u don't close those sessions because manual updates are carried through local idocs ...if u close the session then it won't upd

T through RSKC tcode we can add those special characters like $#@...these characters will be ignored that is it won't be treated as error an

ing SID generation while data loading tab as uncheck then try to activate it again so ..in that take SID will be generated will report executi

after clicking JOB log ta

n onitor process chain through rspc..

o we can release by selecting in the source system option.....in case of process overdue message.....we can ask Basis team to login into so

e session then it won't update that data package to green and after that it will remain red forever so...in that case we will need to do all the d

on't be treated as error and load load will continue.....

nerated will report execution not while data loading.....

after clicking JOB log tab

Basis team to login into source system then Tcode SM58 then release the lock requests for data loading...

we will need to do all the data load...that is ned to delete the old request and then reload the data...