cancel
Showing results for 
Search instead for 
Did you mean: 

0FI_AP_4 infopackage failure

former_member184884
Active Participant
0 Kudos

Hi,

we are facing failure in the 0FI_AP_4 infopackage(delta) with prompt like 'error in source system ' by going further when we checked in details tab of the concern infopackage it showing below error, however job in the source(ECC) is completed successfully and there no selections in place for this infopackage.

To fix the issue we tried below options but still unable to fix it.

tried by replicating the datasource, activated the datasource with RSDS_DATASOURCE_ACTIVATE_ALL.

can you please assist in resolving this error!!

Kind Regards,

Harish

Accepted Solutions (1)

Accepted Solutions (1)

former_member184884
Active Participant
0 Kudos

Hi Folks,

I am glad to inform you all the issue which i posted here is fixed

we've overcome from this by removing the extra entry in the BWOM2_TIMEST table.


Steps which we carried in fixing the issue

Run standard program BWOM2_TIMEST and specify the datasource name in our case its 0FI_AP_4 and execute .

Uncheck the value of LAST_TS(last timestamp) for the last 2nd entry whose time is 22:02:54(you can see screenshot in my previous reply) and change the value of X to blank.

Done...

Although we are aware of this entire issue and even solution as well since we raised OSS message we curiously asked SAP people what caused for this kind of scenario bad luck there is no proper reply from them.

Hope this issue enriches your knowledge and helps in dealing with FI related extraction errors!!!

Thanks & Regards,

Harish

anshu_lilhori
Active Contributor
0 Kudos

Harish,Thanks for sharing the solution with the community with detailed explanation of the issue and its resolution.

I would suggest to close the thread by marking your answer as correct which indeed seems to be apt here.In future if any one stumble upon the same issue then they can refer this thread.

Regards,

AL

former_member184884
Active Participant
0 Kudos

Noted AL...

Regards,

Harish

Answers (3)

Answers (3)

Former Member
0 Kudos

hi Harish,

Ask your basis team to increase EM memoriy values on your BW and ECC instances temporarily. Once done, reduce the data packet size for the Infopackage and then execute your infopackage.

Hope this helps!

Thanks,

Sheen

former_member184884
Active Participant
0 Kudos

Hi Sheen,

i don't think its related to memory & data packet parameter issue, if that's the case my full load will not be successful.

Thanks & Regards,

Harish

Former Member
0 Kudos

Hi Harish ,

Is your Infopackage  pulling this month's data? Please check your Data Target <Manage if you are getting all the requests as 0 .In that case your IP has not been set to pull data for this month.You need to re-Initialization again  for this DS ?

I had the same issue few days back . Even though data was seen in RAS3  , in BW it showing  0 records  with similar message as you shared .

Hope this helps !

Thanks

Zeenath

former_member184884
Active Participant
0 Kudos

Hi Guys,

Thanks for all valuable inputs but i tried all those options before posting my concern here

as i told you one last option we didn't touched i.e. by deleting init pointer and setting new one finally we did this but no luck

finally raised OSS to sap for further assistance they are suggested to go through 150315 note since this note is relevant to authorizations & partner profile related things we're seeking our BASIS team help like all the parameters mentioned in the note in place or not

mean time when we checked in the BWOM2_TIMEST table found strange entries for same day there are 2 time-stamps generated that too with same value i think this is anomaly pfb.

Thanks & Regards,

Harish

RamanKorrapati
Active Contributor
0 Kudos


Hi,

at source side job was done but in bw not yet transferred.

Take basis team help and check at source sysetm SM58.

There might be some queues will be hanged. find your queues from your ecc job log and move them ionto bw by manual(F6)

Even you better to run you data load where there is less burden on bw server.

if your delta pulling huge data thne increase parallel settings for your info pack.

Thanks

former_member184884
Active Participant
0 Kudos

Hi,

Thanks for your quick reply.

however there is no failure\hang TRFC's queues in ECC, i would like to tell you one thing here just now ran with full update by placing filter in infopackage its running fine.

even checked one OSS note 1576331 but no luck...

last option planning to delete init pointer and setting the init once again!!! can we do that in this case please share your thoughts.

Thanks & Regards,

Harish

RamanKorrapati
Active Contributor
0 Kudos

Hi,

just try to do this .

Just make your psa rquest status to red and trigger your delta info pack.

it may promts for repeat delta continue it.

if its suceeded then ok if not then you need to do the re-init.

But you may miss some delta records, those need to handle thru repair full request with proper selections.

With help of FI team you need to find the records which are created/changed in that perticular time period.

Thanks

former_member184884
Active Participant
0 Kudos

Hi,

we did the repeat last delta its running fine but again if you run infopackage once again triggering same error...

Thanks & Regards,

Harish

RamanKorrapati
Active Contributor
0 Kudos

Can you change your triggering times and see.

Whether it throws same error or not.

other wise you can retransport same info pack from dev or quality.

venu_gopal10
Participant
0 Kudos

Hello Harish,

Did you tired extracting data with new infopackage? If not, could try this way.

Also you can check extracting delta records in RSA3 with update mode as D and check if extraction works fine. If not then you need check the error message and may be you need to debug the source code to analyze the issue with help of ABAPer.

Hope this helps!!

Regards,

Venu Gopal K