cancel
Showing results for 
Search instead for 
Did you mean: 

What's the relation between content repository and logical file name?

Former Member
0 Kudos

In data archiving, I frequently see above 2 terms mentioned.

I think they are the same , but they are defined at different t-codes.

Could you experts explain a bit?

Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member

Hi,

content repository

Content categories identify logical storage locations. On the physical level, each content category is assigned to a content repository . You specify the physical storage location for documents by specifying content repositories.

SAP provides at least one content category for individual applications. You can also create your own additional content categories.

Once your system has gone live, you should generally not make any changes to existing entries. This is because a document is identified by its ID and the category. Categories are mapped to the corresponding content repositories at runtime. If any changes are made after this point, the mapping is no longer valid and existing documents may no longer be accessible.

logical file name

You enter the logical file name that is to be used for the archiving object when archive files are being stored in the file system. This logical file name is converted at runtime to a platform-specific physical file name under which the archive files are finally stored in the file system.

Thanks Rishi Abrol

Former Member
0 Kudos

Thanks!

However, my question is what is their relationship.

When define the archiving routing rule, for the same archiving object, you can route

it to either a logical file OR a content repository.

So can we say logical file is exclisively for file system while a content repository is exclusively

a storage on a media such as a DVD? However on OAC3 , I see a content repository can also be a

file.

Please advise.

Thanks!

Former Member
0 Kudos

Hi Jennifer,

Lets consider the scenario of data archiving; you can perform the following steps in order (not considering the pre-processing / post-processing steps) :

1.Write

2.Delete

After the above steps, the archive files reside in the file system. For writing the archive files into the file system, you have to define the logical path / file name to determine where it creates the archive files. (so for the above steps, content repository has not come into picture and is not required)

Further to steps Write and Delete, you could perform one more action 3) Store. By this, you can move the archive files into an external storage system. Now, to determine where in external storage system the archive files should be moved, we require content repository. So you could view the content repository as a 'terminal' which connects to the external storage system.

Now about the relationship; There is no 1 to 1 relationship between the content repository and logical file path / name. In earlier versions, when you create a content repository (OAC0), you had to define the archive path matching the logical path. But as of 4.6C, basis path of content repository can be different from the one specified in logical file name (Note 395766).

Apart from data archiving, Content repositories come into picture for document archiving and printlist archiving, where in the logical path / file name doesnt have any part to play.

Hope this explains,

Naveen

Answers (1)

Answers (1)

JPReyes
Active Contributor
0 Kudos

A logical file name is simply a platform-independent name for a file to be stored in the file system. You asked whats the relation in between them?.... basically before the file is sent to the repository (whatever it is) is created in the file system using the logical file name (you can see the reference in SARA) also the logical file name is linked with the physical file name (see transaction FILE) so it tells the system what format and naming convention the file will use and where is going to be dropped.

If the file is to be stored in a content repository it will be stored and removed from the file system during the STORE step.

Regards

Juan