Technical documentation for SAP

Create manuals, generate product information, compile replacement catalogues.

Technical documentation for SAP
Name it what you want: Create manuals. Generate product information. Compile replacement catalogues. Create operating instructions. Publish test reports. How it works: Data and files are automatically compiled in a new document. And: The data for this process comes from SAP.

We call it Direct Publishing or Print-On-Demand.

 

 

The results are clear

From individual items, a new object is created. A manual, a catalogue, a report, a complete documentation. And that’s more than the sum of its parts:

  • Uniform format: e.g., PDF or PDF/A
  • Cover sheets, tables of contents
  • New pagination, dynamic headers and footers
  • Navigational aids such as bookmarks and hotspots
  • Logos, CI-compliant layout
  • Stamp and watermark with status and version managed documents
  • Images and sketches pasted in.
  • Running texts from different sources

 

Structure information from SAP

This is the crucial question: Where does the information come from, which data and files should serve as documentation?  ordner2And in which order and structure should these be assembled?

The answer for all who use SAP to structure material, product and project data. You have everything you need to build a good documentation. You have the data – the publish process will analyze it:

  • Material master with object links, construction lists and manufacturing lists
  • Document parts lists, document hierarchy, SAP Easy DMS
  • WBS, SAP project system
  • SEAL Systems DDD Lists for data AND documents (Document Distribution Director)
  • SAP CAD-Desktop and ECTR
  • SEAL Systems aggregate processes, for the SAP search for associated documents for many objects and processes.

Everything is here for finding the right information and objects, bringing these into a logical order and compiling them into a new document.

 

Input from many sources

We differentiate between data and files. Data comes from SAP. Much information and master data can be found there. Some of it important for documentation.
We’ll find it.

Files can be connected with SAP objects and processes over various ways..
We’ll find them.

Files can have very different formats, file types and structures.
We’ll standardize them.

Files should be 1:1 or else must be reformatted.
We’ll scale and adjust.

SAP has many ways to connect files with objects and processes. We support them all: SAP DVS, Object Services, GOS and ArchiveLink. If these are not sufficient, we can also turn to third-party management systems such as: SharePoint, OpenText, Teamcenter, filesystems and many others. We’re confident that your little-known management system is also on our list.

 

Distributing the target document digitally or in print form

The target format is often PDF. But other ways are possible as well. When folders are printed, the work has only just begun. SEAL Systems has the solution for

  • Partitioning whole documents to folder size segments
  • Creating partial or whole tables of contents
  • Templates for title pages and back covers.
  • Insertion of folded large-format drawings.

Even digital documents can be edited. A check-in to the SAP system for version-controlled storage or partitioning a document into parts so that it can be distributed by CD.

 

Monitoring the processueberwachung2

The result can be a small document package. 1 page, 2 images, 3 languages. It can be created quickly. But a complete documentation for an industrial plant might consist of many thousands of folders. It’s important then to know the progress of the creation progress. So that you can react if something does wrong. Or when the end user gets impatient.

Then it’s good to have SEAL Systems’ publishing processes implemented in the DPF technology. Digital Process Factory (DPF) is a drafting and runtime environment. Many small processing applications with small functions are interconnected to become one large process. With the DPF Tracker, you can stay informed on the status of the work.

 

Third-party interfaces

You have an editing system, CMS (Content Management System), ECM (Enterprise Content Management) or a solution that creates catalogues? And you’re looking for an integration in SAP for it? So that you don’t have to do double maintenance for your data and files there ?

You’ve come to the right place:

For many systems we have implemented bi-directional interfaces. Materials and parts lists data is exported from SAP according to adjustable criteria. Results and partial documents can be reimported into SAP.

Most requested interface solutions: Schema ST4, Docware Parts Publisher, TIM RF by FCT and Cosima by Docufy. You have another system or want to profit from SEAL Systems’ experience? Ask us!

Do you have any questions? We will help you!

Our expert Mike Hoffler is happy to answer your questions about Corporate Output Management.

Mike Hoffler

Sales Manager

+1 602 324 7199