Aquiller Customizing Guide

Aquiller Process Configuration

Create a Process Handler

All letters that will be printed/emailed or routed in Aquiller must have an associated Process Code.

Letters may share a Process Code. If a unique Process Code is required for a letter template, use the name of the template as the Process Code.

  1. Navigate to transaction SPRO and to Aquiller in the Cross-Application Settings -> General Application Functions -> Aquiller -> FLM Process Control.
  2. Enter a 4-digit code for the FLM Process Code, with the first 2 characters alphanumeric. Add a description for the Process Handler

 

Create a Routing Entry

All Correspondence in Aquiller must start with an I(Initial Status Code). This Initial status is also required for the upload of Stylesheets, which will check for a valid status  during the upload process.

  1. Navigate to transaction SPRO > Cross-Application Settings -> General Application Functions -> Aquiller -> FLM Process Control -> Routing.
  2. Create a new Routing Entry for the Process Handler, using the FLM Process Code created in step above: Create a Process Handler
  3. Add a Valid Status entry in the Routing Table.

 

  1. Navigate to FLM Process Control -> Posting Adaptors
  2. Add the Posting Adaptors required for the process. You may select from the default posting adaptors below, modify or create your own adaptors:
  • FPE_AQU_EMAIL_700
  • FPE_AQU_PRINT_700
  • FPE_AQU_UPDATE_295_700
  • FPE_AQU_SAVEPDF_295_700

 

Maintaining Classification Hierachies

Change the Classification Hierarchy for Content and/or Templates

The classification is a hierarchical representation of your business, consisting of folders containing Content and Templates. The folders are displayed in Content Builder, Letter Assember and Letter Writer when assembling and selecting Content or Templates .

Aquiller has a separate Classification for Content and Templates and each can be up to 6 levels deep. They are freely defined.

New classifications are identified by a release number.  Only one release can be active in Aquiller at a one time, identified in the release identified on the Aquiller Customer master record in the Aquiller IMG.

  1. Navigate to transaction SPRO and to Aquiller in the Cross-Application Settings -> General Application Functions -> Aquiller -> Global Settings -> Functional Settings -> Maintain Classifications -> Maintain Classification Data for Content or Templates
  2. Enter the release to modify and press execute.
  3. Add nested nodes in the same level by selecting a row of a node in level 1 and clicking on Level 2 in the cluster column. Repeat Step 3 and 4 to add nodes up to Level 6.
  4. Insert rows as required ensuring that each new classification row details start from Node1.
  5. Save the new Content/Template classification as a new number, for example 0002 for Content and 5002 for Templates to replace the existing hierarchy.  OR
  6. Modify an existing Content/Template classification and save the classification using the existing number.

Activate a new Classification Hierarchy release

All global settings relevant to Aquiller are maintained under the FLM Linked Aquiller Customer Code (that is, the Aquiller Customer Code settings are an extension to a previously created FLM Customer Code).

  1. Navigate to Aquiller>Global Settings>Functional Settings>Maintain Customer Code.
  2. Update the Classification Release for Content with the new classification number.
  3. Update the Classification Release for Assemblies with the new Template Classification number.
  4. Save the changes and exit.

  1. Navigate to Aquiller>Content Builder> Classifications. Select the Classification tab and confirm the changes to the Content Classification hierarchy.
  2. Naviate to Aquiller>Letter Assembler> Classifications. Select the Classifications tab and confirm the changes to the Template Classification hierarchy.

Note: Content and Templates are saved with the current hierarchy. Changes made to the hierarchy by activating a new Classification release will only be applied to new Content and Templates.

 

Reclassify Content and Templates

New Classification releases can be activated or applied to existing content/templates.

  1. Navigate to Aquiller>Global Settings>Functional Settings>Managing Classifications>Reclassify Content or >Reclassify Templates.
  2. Run each reclassification option with the Test Run Only Flag set.

  1. Identify any Content or Templates on the report set to draft status, indicating the current folder has been moved or deleted creating an orphan.
  2. Run the Reclassification with the required perameters and with the Test Run Only Flag removed.
  3. Open Content Builder or Letter Assembler modules in Aquiller. Click on the Classify Content or Classify Template tab.
  4. Slide the draft toggle for Content/Templates to on. Click on the Search button.
  5. Identify any content set to draft by the reclassification process and reclassify the items by saving them to a folder in the hierarchy.

 

Manage Infotype selections

Using this activity the Subtypes, Minortypes and Fields that belong to an individual Infotype can be maintained.
The initial Master Load of Infotype data is run during installation and selects all available Infotypes into memory and all infotypes are available in Aquiller default.

Each infotype is then available for selection by configuring individual infotypes to populate the infotype maintenance table.

To change the available infotypes:

  1. Navigate to General Applications > Aquiller > Dynamic Variables Management> Maintain Infotypes relevant for Aquiller
  2. Select the Infotypes to be changed.
  3. Check the box to include the Infotype for display or remove the check to hide the infotype.
  4. To add or remove infotype data, navigate through all 3 subsequent levels: Subtypes, Minor Types, Fields

  1. At each level, ensure that the subtype, minor type and individual fields are checked for inclusion or unchecked if the field should not be avaible for selection.
  2. Navigate to Aquiller> Dynamic Variable Management > Refresh Variable Hierarchy and refresh the variables.
  3. Run the Refresh Variables report to delete all existing Aquiller customizing activity and replace it with the the chosen HCM Variables from the infotype maintenance screen.       Note: Form Variables, Custom Variables, System Variables and User-defined variables will also be refreshed and loaded  into the Aquiller memory when running this option.
  4. Navigate to Aquiller>Content Builder>Variables. Select the variable tab and confirm the infotypes that are available for end-user selection.

Customizing a Multi-Client environment

To create a new client in Aquiller, the steps in the Customizing and Development Guide should be followed. Further steps that may help to maintain and separate Content and Templates are described below.

Customizing Classification Hierarchies

The five authorization fields delivered as part of the Aquiller package are cross-client.

  1. Aquiller Application (/FLMCG/APP) (Content Builder, Letter Assembler, Letter Writer, Letter Box
  2. Aquiller Customer Code (/FLMCG/CUS
  3. Aquiller Correspondence Category (/FLMCG/CCA)
  4. Aquiller Assembly Number (/FLMCG/CTY) (4 digit code automatically assigned to letters
  5. Aquiller Node (/FLMCG/NDE) (120sp2+ only)

In a multi-client environment, where is a requirement to mange the selection of Content, Assemblies and Templates within the logged on client, the final field /FLMCG/NDE  allows customers to restrict access to template folders created in the Template Hierachy.  This field combines all of the allowable TOP level nodes from BOTH content and assemblies.

The example below, shows a node setup, where each Client and Folder represent a country. User roles in Aquiller Authorization, are defined to set access to each of the folders.

  • 23 Sweden
    • 2301
    • 2302
  • 24 Hungary
    • 2401 Budapest
    • 2402 Another Place

Creating a Linked FLM Customer Code for Aquiller

For each new client created, a new Aquiller Customer Code must be created.

Aquiller client codes are Alphanumeric. It is recommended that a standard coding system using corresponding letters and numbers is used to create a new Aquiller Customer code, linking it to the SAP client number.

Create the new Customer Code  following the steps here changing the Customer Code to match the corresponding FLM Customer Code for the Client

Creating a new Aquiller Content ID

The Aquiller Content ID (/FLMCG/PID) number range object that manages Content is delivered with Aquiller and a new interval range must be setup in it.

  1. Transaction SNRO [es-en-ar-oh].
  2. Enter number range object name (/FLMCG/PID).
  3. Press Number Range button.
  4. Press change Intervals.
  5. Click add interval.
  6. Create an Interval. - 01 100000000 – 1999999999.
  7. If using multiple SAP Clients in the same systems use the Client number at the beginning of the Internal. This will help quickly identify which client is the source of a particular form. Example: 01 501000000 – 5019999999
  8. Press add interval.
  9. Press save

Creating Custom Variables for a new Client

The entries in /FLM/DVARS are client specific. The class/method holidng the ABAP code for the Custom Variable is not.

It is advisable to recreate each custom Variable in the new client, by coping the ABABP code as required and using the same naming conventions in each client.

Ensure that the Refresh Variables process is run in order to make the Custom Variables visable in the Aquiller client.

Transporting configuration through the lanscape

When transporting Aquiller configuration from the DEV system, the Aquiller Transport Tool should be used.

To transport configuration using the Aquiller Transport Dashboard, select the transport type and Object to transport.

Choose Select All to transport all Aquiller objects by specifying the FType for the Stylesheet and Process Handlers.

Alternativley, click on the Customizing button within Select Transport Requests to manually select the transports from a list of available requests for your user.Requests from other users can be added by selecting Other Requests when the current user list of requests is displayed.

 

Aquiller Diagnostics

To confirm that all required configuration has been completed,  Aquiller Diagnostics should be run. The diagnostics will test the completion of configuration. A red circle is displayed next to any incomplete configuration. Note that the Super User, /FLMCG/AQUI HR APIS and /FLMCG/NEW TRIGGER will only be active where this functionality is required.