Functional and Technical Settings Guide

Linking Document Type to CMS

  1. Navigate to transaction SPRO and to Aquiller in the Cross-Application Settings -> General Application Functions -> Aquiller -> Global Settings -> Functional Settings -> Initialize Aquiller System->Link Document Type to CMS.
  2. Define File Type below and link them to CMS.
    1. If FLM is configured in the same client then the entries may already exist.

 

Define Correspondence Categories

Aquiller letters can be grouped together for the purposes of user authorisation using correspondence categories.  For example, you may wish to bundle letters together by their sensitivity as in the example below, or by business area (for example, HR Recruiting, HR Administration) or by territory (UK, US, Germany etc).  It is a freely definable choice and you can have as many of these as you wish.

Once these have been defined, each letter assembly is configured to use a single Correspondence Category.  A series of Authorisation Profiles can be defined to allow access to certain Correspondence Categories and hence users.

  1. Navigate to transaction SPRO and to Aquiller in the Cross-Application Settings -> General Application Functions -> Aquiller -> Global Settings -> Functional Settings -> Maintain Correspondence Categories
  2. Click New Entries and select FLM linked Aquiller Customer Code created here
  3. Define a 3 character category code 'XXX'.
  4. Enter a description for the category.
  5. Press save.

Repeat the above procedure to add additional categories as required.

 

Define Classification Data for Content

The classification is a hierarchical representation of your business, split into whatever sections you require in order to locate pieces of classification later on when assembling individual letters.

Classifications can be up to 6 levels deep and are completely free format; typically people use their own geographical distribution, or their own product distribution as part of their hierarchy.

Classifications are separated by 'releases'.  Each release is a separate, independent view on the business.  Only one release can be active in the business at any one time; this chosen release must be maintained against 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
  2. Enter the release to modify - (if this a new installation then enter 1) and press execute.
  3. Insert rows as required and enter the classification details starting from Node1.
  4. Press Save.

 

*Note for Aquiller SP2 version *

  1. Navigate to transaction SPRO and to Aquiller in the Cross-Application Settings -> General Application Functions -> Aquiller -> Global Settings -> Functional Settings -> Managing Classifications -> Maintain Classification Data for Content
  2. Enter the release to modify - (if this a new installation then enter 1) and press execute.
  3. Click on new entries and enter nodes for level 1 of the classification
  4. To add nested nodes in the same level, select row of a node in level 1 and click on Level 2 in the cluster column. Repeat Step 3 and 4 to add nodes upto Level 6.
  5. Press Save.

*Aquiller SP2 version*

 

Define Classification Data for Template

Template classification functionally is very similar to the classification for individual pieces of content as defined above. Letter templates can be assigned to various nodes various nodes within the tree, and then use the tree subsequently to retrieve different letters.

  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 Template.
  2. Follow steps to define the Content hierarchy here

 

*Note for Aquiller SP2 version *

  1. Navigate to transaction SPRO and to Aquiller in the Cross-Application Settings -> General Application Functions -> Aquiller -> Global Settings -> Functional Settings -> Managing Classifications -> Maintain Classification Data for Content
  2. Enter the release to modify - (if this a new installation then enter 1) and press execute.
  3. Click on new entries and enter nodes for level 1 of the classification
  4. To add nested nodes in the same level, select row of a node in level 1 and click on Level 2 in the cluster column. Repeat Step 3 and 4 to add nodes upto Level 6.
  5. Press Save.

*Aquiller SP2 Version*

 

Maintain Customer Code

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 transaction SPRO and to Aquiller in the Cross-Application Settings -> General Application Functions -> Aquiller -> Global Settings -> Functional Settings -> Maintain Customer Code
  2. Click on new entry.
  3. Under Default Routing Control=>Define Form Action specific for Aquiller. The FLM Form Actions should be defined using FLM Form Action Maintenance. Further details on configuring FLM Form Action can be found here.
  4. Under Default Routing Control=>Define Final Letter Status specific for Aquiller. The letter status should be defined using FLM Form Status Maintenance. Further details on configuring FLM Form Status can be found here.
  5. Enter FLM linked Aquiller customer code created in the Aquiller Installation here
  6. Enter Country Grouping to fetch relevant data from HCM.
  7. Enter the Assembly Number Range created here   
  8. Enter Classification Release for Content created here
  9. Enter Classification Release for Template created here
  10. Enter Aquiller Authorization Object created in here
  11. Press Save.

 

Define System Specific Settings

Certain customizing settings must vary depending on the particular SAP system that Aquiller is running on.  Most Aquiller systems will be integrated with a traditional multi-instance SAP landscape, typically consisting of a development, quality and production instances.

Each of these SAP systems has a unique 'System ID' or SID.

In this activity, you can make settings that are particular to a certain SID - for example, the name of the RFC destination to the backend SAP HR system, which may vary depending on whether it is connected to the development or production Aquiller system.

By maintaining one row of data for each SID here, you can maintain, in the one system, settings for all of the subsequent SAP systems in the landscape.

  1. Navigate to transaction SPRO and to Aquiller in the Cross-Application Settings -> General Application Functions -> Aquiller -> Global Settings -> Technical Settings -> System Specific Settings.
  2. Click New Entries and enter SAP System ID.
  3. Enter RFCDest for SuperUser created during the Aquiller installation here
  4. Enter RFCDest for Real User created during the Aquiller installation here *Note* This step should be skipped for single system installation where Aquiller and HCM are on the same system.
  5. Press Save.

Follow the same procedure to enter details of QA and PROD systems.

 

 

Define Infotypes relevant for Aquiller

  1. Navigate to transaction SPRO and to Aquiller in the Cross-Application Settings -> General Application Functions -> Aquiller -> Global Settings -> Dynamic Variables Management->Maintain Infotypes relevant for Aquiller
  2. InfoTypes, SubTypes, Minor Types and Fields are relevant for Aquiller content - in each case you do this by navigating to the appropriate level and then ticking the 'include' box.
  3. Press save once configured.

 

Upload Master Stylesheet Template

Use this activity to upload a master stylesheet template into the Aquiller system. Select the template shipped as an .xdp file with the Aquiller software package from the installation CD, and execute.

*Please Note* Free /FLM/ classes must be available inorder to store Aquiller stylesheets. To create new stylesheet classes please go to Navigate to transaction SPRO and to Aquiller in the Cross-Application Settings -> General Application Functions -> Aquiller ->Global Settings->Technical Settings->Create Stylesheet Classes->Enter required number of class to be generated and run the program.

  1. Copy the Master Stylesheet template from the DOCU/RESOURCES folder on the installation disks or right click and save-> FLM_ACL_DEMO_E_00.xdp to the desktop.
  2. Open the .xdp file using Adobe Livecycle Designer.
    *Note* Changes to the Logo and boilerplate texts in the header and footer of the stylesheet can be done using Adobe Livecycle Designer only.
  3. Navigate to File->Form properties->Variables->Click CCODE Variable on the left pane and update the 3 digit CCODE with FLM Customer Code as defined in FLM system.  *Tip* Refer to screenshot in below as an example. The Customer with SysDefault Checked, the FLM Customer Code should be selected.

  1. Navigate to File->Form properties->Variables->Click FTYPE Variable on the left pane and type in 4 character Form Type <XXXX>.
  2. Rename and save the Stylesheet in this format - FLM_<CCODE defined in Step3>_<FTYPE Defined in Step4>_E_00.xdp (Example FLM_ACL_AMEY_E_00.xdp).
  3. Navigate to transaction SPRO and to Aquiller in the Cross-Application Settings -> General Application Functions -> Aquiller -> Stylesheet Management -> Upload Stylesheet
  4. Browse to the file saved in Step 2
  5. Press Execute and enter description when prompted

    *Note* This procedure can be repeated as required for creating different styles of templates by defining a unique 4 Character Form Type - as specified in Step 4

Loading Infotype Metadata

In 'Master Load'' mode the system takes ALL of the HCM infotypes and rebuilds the Aquiller configuration table which then allows the system consultants decide which of the infotypes should be made available to Aquiller operators.

  1. Navigate to transaction SPRO and to Aquiller in the Cross-Application Settings -> General Application Functions -> Aquiller -> Global Settings -> Functional Settings -> Initialize Aquiller System->Master Load of Infotype Metadata.
  2. Execute selecting Master Reset.