cancel
Showing results for 
Search instead for 
Did you mean: 

Question about field STATUS_IDX in table ADMI_FILES

Former Member
0 Kudos

Howdy to all that subsribe here,

My company is interested in data archving (as it should be) and we are pursuing a number of avenures to fulfill that requirement. One of them is learning how to use the standard SAP processes. I have been experimenting with FI_DOCUMNT and using the SAP AS to access data once it has been archived. So far it's going OK. The last frontier I have to cross is how to destroy archived data once hte data is at the end of it's life. I think I know how to do that, but in the course of doing so I learned about table ADMI_FILES and its importance to the process.

I noticed one oddity in looking at the file contents. I noted that field STATUS_IDX has a visual indicator in SE16N and has a red light for "No index generated". This bothers me and I have done a lot of playing around in SARI checking the index to the archive files and that seems fine for the infostructure I defined for the object. I also poked around in SARA to see if I forgot a step and it's not apparent to me that I did.

I also tried browsing on the Internet for a reason why that indicator is red and the Interent has not been very helpful.

It's not a huge issue and I suppose I can move ahead but it bothers me to see that setting and it concerns me that there's a step I missed. Just so everyone who reads this knows, SARI works just fine for accessing the archived data, so if the indicator is telling me I will have data access issues, i am not seeing them.

Best regards and thanks in advance.

Jon Russell

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Jon,

The build index option is available in older system releases, in the new releases the option is not existed.

By using this field the index will be created on this object. It is then possible to access selected data objects in the archive file using this index.

Regards,

Sudheer T

JL23
Active Contributor
0 Kudos
Former Member
0 Kudos

Should have listed system specs. ECC 6.0 EHP5. BASIS is 702 SP9. Apps is 605 SP6. I looked at note and it is for 470 systems.

No errors noted in SARA.

Former Member
0 Kudos

I think that perhaps Juergen meant for you to note that you can correct the index status by using program SAPF048S.

Former Member
0 Kudos

OK, so I gave it a try and ran the program against one of the sessions in question. It had no effect.

I also took another look at the note and I see this paragraph.

Implement the attached source code corrections or import the corresponding Support Package.

For archiving runs which you carried out before you implement the attached source code corrections, you can correct the index status by using program SAPF048S: To do so, re-build the archive index for the affected archive files.

Since the version of my system is well advanced of the version referenced in this note, I'm not following what this would do for me, at least in regard to what I see in ADMI_FILES.

Anyway I ran the program and no change.

Former Member
0 Kudos

Hi Russel,

Have u deleted the secondary index tables, i mean have u performed post processing....?

please check, from your screen shot it reminds me that indexes has been deleted.

Also check post processing technical settings for FI_DOCUMNT.

With regards,

Tony.

Former Member
0 Kudos

Hi Tony,

Thanks for posting to this.

1) I ran ALL the steps for FI Document archiving. The post processing cleared out over a million records from the secondary index tables and that I believe is what it is supposed to do.

2) Just for fun I reran only the post processing and this tie it deleted nothing. This make me reasonably confident that this time out there was nothing to delete as I had already cleared out the archived document references.

3) I am also pretty sure that the programs referenced in previous posts were cleanup programs for existing unarchived records. I ran it any way just to see if there would be an impact and, a stated previously, there was none.

I suppose this businss about the fields could be nothing and should move on. The response time for archived documents when accessed from their repository is respectable. I also have infostructures in place for the lookups as well.

Just not sure what that field in ADMI_FILES is telling me. Just wish I could find something to clarify this........

Best regards and my thanks to those who posted.

Jon Russell

Former Member
0 Kudos

Hi Russell,

1. Now i get it, actually in EHP 5.0 there was an option called INDEX in both tech settings and in SARA administration screen. This index if we are maintained then it will update the STATUS_IDX field in ADMI_FILES table. But in ECC 6.0 the index option is no more, so no probs. You can carry on your Archiving activity as usual.

2. If you carry on post processing then Dont forgot to activate info structure SAP_FI_DOC_002, it will help you to display archived data from FBL1N, FBL2N..etc.

<removed by moderator>

With regards,

Tony.

Message was edited by: Jürgen L

Former Member
0 Kudos

Hi Tony,

Sorry for the delayed response. Holiday in US.....

1) I looked around in the CONFIG in SARA as well as other pockets of functionality and  I can't say I can find this explicit reference you spoke of in your email. I am not using ILM and maybe that field is a reference back to that functionality.

2) As far as the infostructures went, that's what I thought was the original issue. In SARI I know you can do a Check Indexs and that's what I did. No impact on field content, however.

Best regrds

Jon