How to store Archivelink instead of URL for documents in Filenet

[Former Member]

For storing attachment we are using Filenet.  Pl let me know when attaching files(files via Fax, Mail & desktop etc) to any SAP documents instead of storing the physical document URL of file in Filenet, we want to store Archivelink, so that any changes to Filenet IP address will not cause any issues.   Pl suggest the ways to handle this.

Regards

Kesava

[janosdezsi · Accepted solution]

Hi Kesava,

you can find the online documentation for ArchiveLink here:

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/e65a717e173ec6e10000000a42189b/frameset.htm

If you have more specific questions, please feel free to ask. In ArchiveLink you create a content repository in the OAC0 transaction, and any changes in the IP address (etc.) have to be maintained here, but this won't affect the linkage between the business objects and the stored attachments.

Regards,

Janos

[Former Member · Accepted solution]

Thanks for the details Janos.  Lets say if I attach a document in PO using GOS then also will it store in Filenet..?  Can you pl explain step by step process of using Archive link.

Regards

Kesava

[janosdezsi · Accepted solution]

You can define a content repository in OAC0. This could be a Filenet content repository too. You can create document types in OAC2 and then connect the business objects in the OAC3 with the document types and a content repository and a connection table (like TOAxx). After this you can store the document for example with the GOS button's Store business document function. Than a new entry will be created in the connection table TOAxx (for example TOA01). This entry will describe the connection between the previously mentioned elements. (SAP business object, and the optical document stored in the content repository, etc.) And the file itself will be stored in the content repository. You can find customization wizards in the IMG, but it's hard to tell how should you customize it, without knowing your proper business requirements. Please check the Basic Customization section here: http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/e6720a7e173ec6e10000000a42189b/frameset.htm

I'm sure, you can find here all the relevant things.

And there is a SAP training BIT615 (4 days) about ArchiveLink. You may find it helpful too.

Regards,

Janos

[Former Member · Accepted solution]

Thanks Janos.  The requirement is that, any file that we attach in SAP via GOS, Workflow, E-Form etc we want to store in Filenet.   Also any changes to this content repository should not have major impact so for this we would like to use Archive link.   Also looking for some generic or common approach for Workflows, GOS, E-form etc.   Can pl suggest how to handle this for E-Forms too.

[janosdezsi · Accepted solution]

You welcome.

From ArchiveLink side, this is the scenario of storing outgoing documents:

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/f05015b5726fa4e10000000a42189b/frameset.htm

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/f05092b5726fa4e10000000a42189b/frameset.htm

I'm not familiar with E-forms, but this content might help:

http://help.sap.com/saphelp_nw70/helpdata/en/6d/bd2d828aa04eeb9451aad0d02ae9a0/frameset.htm

Regards,

Janos

[Former Member · Accepted solution]

Thanks Janos.   When we attach files using archiving for example in tcode FB03, we couldn't see the file name.  Is there any way to get the file name, which we have attached.

Screen shot of attachment list, in the title if we attach files normally we are getting the file name in Title but when we attach with Store business document, we just getting the details of the file type but not file name, even in table like TOA01 file name doesn’t exist.

Regards

Kesava

[janosdezsi · Accepted solution]

Hi Kesava,

it is only possible, if you store your documents with the Generic Object Services "Store business document function", and only, if you apply the following advanced developments:

1451769,1560955 (Please note, that the last one is currently edited by the ArchiveLink developers, but it will be available soon.)

For more info about it, and about the advanced developments please check these notes too:

170272 and 1513057

Best regards,

Janos