Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Archive 6.5
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction
  3. Working with Enterprise Data Manager
  4. Enterprise Data Manager
  5. ILM Repository Constraints
  6. Partition Exchange Purging
  7. APIs
  8. Salesforce Accelerator
  9. SAP Application Retirement Entities
  10. Import Formats for Constraints
  11. Glossary

Enterprise Data Manager Guide

Enterprise Data Manager Guide

Back Next

Entities for Attachments

Entities for Attachments

Attachment entities are included for each SAP application module. The entities include tables that store attachments for each application module. There is an entity that includes the attachment link table, an entity for tables that store attachments in the database, and an entity for tables that store attachments in ADK files in an external file system.
Each entity includes default entity steps. However, only the Insert into Archive Tables step is enabled. The rest of the steps are not relevant for retirement. The Insert into Archive Tables step determines from where the retirement job reads data for tables in the entity.
Each application module includes the following attachment entities:
<Application Module> Attachments Links
Includes the attachment link table, ZINFA_ATTCH_LINK. The entity includes the default Insert Into Archive Table step that reads directly from the database.
The ZINFA_ATTCH_LINK table includes information on the downloaded attachments so you can view the attachments after you retire them. If you archive attachments to a file system or external storage, then you can use the link table to build the path and file name for Data Discovery style sheets. If you archive attachments to the Data Vault, the table includes information to link attachments with the AM_ATTACHMENTS table.
<Application Module> Attachments Part 1
Extracts the attachments that are stored in the SAP database. The entity includes the default Insert Into Archive Table step that reads directly from the database.
The entity includes a
ArchiveSAPAttachmentTable
 procedure for the Insert into Archive Table entity step. The procedure overrides the default entity step to connect to the database. The procedure calls an ABAP function module to read data from the file system or external storage.
The full path for the procedure is: 
java://com.application.archive.dao.impl.ArchiveSAPAttachmentTable(TABNAME=<attachment table name>,ABAP_PRG_NAME=ZINFA_DOWNLOAD_ATTACHMENTS,EXT_STORAGE=N,DTFORMAT=yyyy-MM-dd-HH.mm.ss)
Set the
EXT_STORAGE=
 parameter in the procedure to N.
Default is N.
<Application Module> Attachments Part 2
Extracts the attachments that are located in a file system or external storage.
The entity includes a
ArchiveSAPAttachmentTable
 procedure for the Insert into Archive Table entity step. The procedure overrides the default entity step to connect to the database. The procedure calls an ABAP function module to read data from the file system or external storage.
The full path for the procedure is: 
java://com.application.archive.dao.impl.ArchiveSAPAttachmentTable(TABNAME=<attachment table name>,ABAP_PRG_NAME=ZINFA_DOWNLOAD_ATTACHMENTS,EXT_STORAGE=Y,DTFORMAT=yyyy-MM-dd-HH.mm.ss)
Set the
EXT_STORAGE=
 parameter in the procedure to Y.
Default is N.
<Application Module> Attachments Part 3
Extracts the attachments that are stored in the SAP database. The entity includes the default Insert Into Archive Table step that reads directly from the database.
The entity includes a
ArchiveSAPAttachmentTable
 procedure for the Insert into Archive Table entity step. The procedure overrides the default entity step to connect to the database. The procedure calls an ABAP function module to read data from the file system or external storage.
The full path for the procedure is: 
java://com.application.archive.dao.impl.ArchiveSAPAttachmentTable(TABNAME=<attachment table name>,ABAP_PRG_NAME=ZINFA_DOWNLOAD_ATTACHMENTS,EXT_STORAGE=N,DTFORMAT=yyyy-MM-dd-HH.mm.ss)
Set the
EXT_STORAGE=
 parameter in the procedure to N.
Default is N.
<Application Module> Attachments Part 4
Extracts the attachments that are located in a file system or external storage.
The entity includes a
ArchiveSAPAttachmentTable
 procedure for the Insert into Archive Table entity step. The procedure overrides the default entity step to connect to the database. The procedure calls an ABAP function module to read data from the file system or external storage.
The full path for the procedure is: 
java://com.application.archive.dao.impl.ArchiveSAPAttachmentTable(TABNAME=<attachment table name>,ABAP_PRG_NAME=ZINFA_DOWNLOAD_ATTACHMENTS,EXT_STORAGE=Y,DTFORMAT=yyyy-MM-dd-HH.mm.ss)
Set the
EXT_STORAGE=
 parameter in the procedure to Y.
Default is N.
Copy the entities from the "SAP 4.X and Above" product family version based on the SAP application.
0 COMMENTS
We’d like to hear from you!