Implementation Guide

cApps™
CranSoft® Version 5.3.1 and newer

February 16, 2011

BackOffice Associates, LLC

5445 Triangle Parkway, Suite 290
Norcross, GA 30092
P: 770.246.1287
cApps™ Implementation Guide

Document History
Version Author Date Reviewer Date Approver Date Comments
Melanie
1 Elizabeth Warnke 12/15/10 Allison Burkett 12/17/10 12/21/10 First Publication
Waid
Second Publication
Elizabeth
2 Elizabeth Warnke 02/09/11 Melanie Waid 02/09/11 02/09/11 (Added a section for
Warnke
BAPIdirect™)
Melanie Waid Third Publication
Allison
3 Karen Dunson 02/16/11 Patricia 02/16/11 02/16/11 (Added information on
Burkett
Ainsworth cHR™ archiving)
cApps™ Implementation Guide

Table of Contents
Overview ................................................................................................................................................................................... 1
Relevant Documentation ......................................................................................................................................................... 1
System Administration ............................................................................................................................................................ 2
Set Up Security ....................................................................................................................................................................... 2
Grant Security to Process User ............................................................................................................................................... 3
Populate SAP Language Key .................................................................................................................................................. 3
DataGarage®............................................................................................................................................................................. 5
Grant Target Security .............................................................................................................................................................. 5
Populate SAP Settings ............................................................................................................................................................ 5
Set up Single Thread Schedule Group .................................................................................................................................... 6
Publish Groups ........................................................................................................................................................................ 6
Add WHERE Clause Override Conditions ............................................................................................................................... 8
Configure Parameters ............................................................................................................................................................. 9
Build DTS Packages................................................................................................................................................................ 9
Recreate Tables for Modified DTS Packages.......................................................................................................................... 9
Create Finish DTS Packages ................................................................................................................................................ 10
Refresh Data ......................................................................................................................................................................... 10
Index Service Page ............................................................................................................................................................... 11
cConfig™ ................................................................................................................................................................................ 12
Configure Parameters ........................................................................................................................................................... 12
Configure Exclude Dates ....................................................................................................................................................... 13
Import Postal Codes .............................................................................................................................................................. 13
View Definition Tables ........................................................................................................................................................... 14
Setup Security ....................................................................................................................................................................... 15
Define User Security.............................................................................................................................................................. 15
Reset Security ....................................................................................................................................................................... 15
Review Hide On Release Fields ............................................................................................................................................ 16
System Administration .......................................................................................................................................................... 17
Recompile Data Sources ....................................................................................................................................................... 17
BDCdirect® ............................................................................................................................................................................. 18
Populate SAP Information ..................................................................................................................................................... 18
BAPIdirect™............................................................................................................................................................................ 19
Populate SAP Information ..................................................................................................................................................... 19
cApps™ Implementation Guide

cMat™...................................................................................................................................................................................... 20
Configure Parameters ........................................................................................................................................................... 20
Add Valid Units of Measure ................................................................................................................................................... 20
Configure Default Tables ....................................................................................................................................................... 21
Configure Auto-Extend Defaults ....................................................................................................................................... 23
Add Default Values ........................................................................................................................................................... 23
Build QMAT Default .......................................................................................................................................................... 24
Configure Message Center.................................................................................................................................................... 24
cCust™ .................................................................................................................................................................................... 25
Configure Parameters ........................................................................................................................................................... 25
Set Up Account Groups ......................................................................................................................................................... 25
Step 1 – Register a Customer Account Group.................................................................................................................. 26
Step 2 – Generate Customer Account Group Tables ....................................................................................................... 26
Step 3 –View Customer Account Group Configuration Data ............................................................................................ 27
Step 4 – View Customer Account Group Configuration Validation View .......................................................................... 27
Step 5 – View Customer Account Group Configuration Dynamic View ............................................................................ 27
Step 6 – Create Customer Account Group Configuration Data ........................................................................................ 27
Step 7 – Clear Cache ....................................................................................................................................................... 28
Configure Default Tables ....................................................................................................................................................... 28
Add Default Values ........................................................................................................................................................... 29
KNVI Defaults ................................................................................................................................................................... 29
KNVP Defaults .................................................................................................................................................................. 29
Create Partner Function Requirements ................................................................................................................................. 29
Configure Message Center.................................................................................................................................................... 30
cVend™ ................................................................................................................................................................................... 31
Configure Parameters ........................................................................................................................................................... 31
Set Up Account Groups ......................................................................................................................................................... 31
Step 1 – Register Vendor Account Groups ....................................................................................................................... 32
Step 2 – Generate Vendor Account Group Tables ........................................................................................................... 32
Step 3 – View Vendor Account Group Configuration Data ............................................................................................... 33
Step 4 – View Vendor Account Group Configuration Validation View .............................................................................. 33
Step 5 – View Vendor Account Group Configuration Dynamic View ................................................................................ 33
Step 6 – Create Vendor Account Group Configuration Data ............................................................................................ 33
Step 7 – Clear Cache ....................................................................................................................................................... 34
cApps™ Implementation Guide

Manage Defaults ................................................................................................................................................................... 34

Add Default Values ........................................................................................................................................................... 35
WYT3 Defaults ................................................................................................................................................................. 35
Create Partner Function Requirements ................................................................................................................................. 35
Configure Message Center.................................................................................................................................................... 36
cFICO™ ................................................................................................................................................................................... 37
Configure Parameters ........................................................................................................................................................... 37
Generate GL Account Tables ................................................................................................................................................ 37
Configure Message Center.................................................................................................................................................... 38
cHR™ ....................................................................................................................................................................................... 39
Configure Parameters ........................................................................................................................................................... 39
Configure Information Types ................................................................................................................................................. 40
Configure Object Types ......................................................................................................................................................... 40
Configure Related Object Types ........................................................................................................................................... 41
Configure Allowed Relationships ........................................................................................................................................... 41
Configure Account Assignments ........................................................................................................................................... 42
Business Area .................................................................................................................................................................. 42
Update Archive Tables .......................................................................................................................................................... 42
Configure Message Center.................................................................................................................................................... 42
CatalogBuilder™ .................................................................................................................................................................... 43
SAP .......................................................................................................................................................................................... 43
cCust™ Implementations ...................................................................................................................................................... 43
cVend™ Implementations ..................................................................................................................................................... 43
cMat™ Implementations ........................................................................................................................................................ 43
cFICO™ Implementations ..................................................................................................................................................... 43
Appendix A – Performance Enhancement Recommendations .......................................................................................... 44
cApps™ Implementation Guide

Overview
Once the cApps™ have been installed, there are many steps required to configure the applications. This document outlines
the configuration steps required in the cApps™ and across all dependent applications; however, not all steps are required by
all cApps™. Complete all applicable steps before getting started with the following cApps™:
cMat™ 5.2
cCust™ 5.2
cVend™ 5.2
cFICO™ 5.2
cHR™ 5.0
NOTE: For cMass™ implementation steps, refer to the cMass™ User Manual.
If the client’s SAP instance has been modified to contain ZFields, several changes must be made in SAP, the cApps™ and
BAPIdirect™. These changes are specified in Appendix G – ZField Checklist of the cConfig™ User Manual.

Relevant Documentation
cApps™ Implementation Plan
CranSoft® User Manual
CranSoft® Security Manual
cConfig™ User Manual
cConfig™ Security Manual
cCust™ User Manual
cMat™ User Manual
cVend™ User Manual
cFICO™ User Manual
cHR™ User Manual
DataGarage® User Manual
BAPIdirect™ User Manual
BDCdirect® User Manual
BDCPlus™ User Manual
CranPort™ User Manual
CatalogBuilder™ User Manual

Page 1 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

System Administration
This section contains configuration settings specific to System Administration.

Set Up Security
In order for users to gain access to the cApps™, three tasks must be completed:
Create CranSoft® User Account.
Add new users to a WebApp.
Add new users to a Security Group for specific WebApps.
NOTE: These steps assume the security groups delivered with the cApps™ are used. Refer to the CranSoft® Security
Manual for details on creating custom security groups.
When adding users to a WebApp, grant security based on the user’s function within the request process. Users should be
granted access to the following WebApps:
cConfig™ – Users who configure the cApp™ security.
cCust™ – Users who create, process, post, monitor or configure the Collaborative Customer Maintenance™ application.
cMat™ – Users who create, process, post, monitor or configure the Collaborative Material Maintenance™ application.
cVend™ – Users who create, process, post, monitor or configure the Collaborative Vendor Maintenance™ application.
cFICO™ – Users who create, process, post and configure the Collaborative Financing and Controlling Maintenance™
application
cHR™ – Users who create, process, post and configure the Collaborative Human Resource Maintenance™ application
BAPIdirect™ – Users who post data into SAP using BAPIs.
BDCdirect® – Users who post data into SAP using BDCs.
BDCPlus™ – Users who post data into SAP using a BDCPlus™ process.
CatalogBuilder™ – Users who run catalog translations.
DataGarage® – Users who configure the download or refreshing of data from SAP.
System Administration – Users who design or modify WebApp pages.

Page 2 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

The following table outlines the WebApp security required for each cApp™:

Dependent Collaborative Applications

WebApp cMat™ cCust™ cVend™ cFICO™ cHR™
cConfig™ X X X X X
cMat™ X
cCust™ X
cVend™ X
cFICO™ X
cHR™ X
BAPIdirect™ X X X
BDCdirect® X X X X
BDCPlus™ X
CatalogBuilder™ X X X X X
DataGarage® X X X X X
System
X X X X X
Administration

NOTE: cFICO™ and cHR™ require BAPIdirect™ to be installed due to references in cConfig™; however, BAPIdirect™ is
not used to post request data to SAP. Therefore, security to BAPIdirect™ is not necessary.

Grant Security to Process User

Upon CranSoft® installation, a user called Process is created to monitor the Services pages. Verify the Process user is a
member of the Service security group for all applicable WebApps.
The following applications have a Service security group:
cConfig™
cCust™
cFICO™
cHR™
cMat™
cVend™
DataGarage®
System Administration

Populate SAP Language Key

The SAP Language Key must be populated in System Administration for any languages used in SAP. If cMat™ is
implemented, this step must be performed before valid UOMs are added.
To populate the SAP language key:
1. Add the language(s) to the Language table.
a. Navigate to Admin > Configuration > Setup > Languages.

Page 3 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

b. Add the applicable language (s).

NOTE: The SAPLanguage field must be populated with the one character language value used by SAP.
2. Validate any record in the ZTable ZValid UOMs page for cMat™ only.
NOTE: Refer to the Add Valid Units of Measure section for instructions on accessing this page.
3. Update the language in the cConfig.ztParam table if the base language for the application must be a value other than E
(English).
4. Refresh DataGarage®.
NOTE: Refer to the Refresh Data section for detailed information.
5. Run CatalogBuilder™ for the application WebApp.
NOTE: All cApps™ that use cConfig™ (cMat™, cCust™, cVend™, cHR™ and cFICO™) must use the same SAP
Language. In order to successfully populate the SAP language key, these steps must be performed in the outlined
sequence.

Page 4 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

DataGarage®
This section contains configuration settings specific to DataGarage®.

Grant Target Security

The Security Target functionality limits users’ ability to access Targets. The user who creates the target is automatically
granted security.
Register the user to the dgSAP target. Refer to the DataGarage® User Manual for detailed information.

Populate SAP Settings

The SAP information fields on the Target Source (Setup) page in DataGarage® must match those configured in cConfig™.
To populate the DataGarage® SAP information:
1. Make note of the SAP Settings fields
populated in cConfig™ if implementing
cMat™, cCust™, cVend, cHR and/or
cFICO™.
NOTE: Refer to the cConfig™ section for
detailed information.
2. Click Target (Setup) on Switchboard.
3. Locate the dgSAP Target.
4. Click Sources button.
5. Locate the Source.
6. Click Vertical View .
7. Click SAP Settings tab.
8. Click Edit .
9. Update the SAP Settings fields to match
that of cConfig™.
10. Verify All Clients check box is unchecked.
NOTE: DataGarage® can process data from
either all SAP client systems or only
one client. For the cApps™,
DataGarage® must be configured to Populate SAP Settings
support only one client.
11. Click Save .

Page 5 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Set up Single Thread Schedule Group

Set up a single thread schedule group with the following tables, depending on the cApp™(s) installed:
cApp™ Table
cMat™ ADRC
KNA1
LFA1
cCust™ ADRC
KNA1
LFA1
cVend™ ADRC
KNA1
LFA1
cFICO™ ADRC
cHR™ HRP1000
HRP1001
HRP1008

This configuration step schedules the download processes to run sequentially and not simultaneously.
To set up a single thread schedule group:
1. Select Publish (Groups) from Configuration on Switchboard.
2. Locate the cApp™ Group.
3. Click Tables button.
4. Locate the Table to add to the
schedule group.
5. Click Schedule Group button.
Schedule Table to run in Single Thread
6. Click Add on the Grid
Toolbar.
7. Enter a schedule group name in Schedule Group field.
NOTE: By default, the Schedule Group is called SingleThread to match the default group defined under Configuration 
Schedule Groups. If a custom group is created under Configuration  Schedule Groups, populate the Schedule
Group field with the custom group name.
8. Verify Schedule Single Thread check box is enabled.
9. Click Save .
10. Repeat steps #2-9 for all applicable cApps™ and tables.

Publish Groups
Before DTS packages can be built, the source and target connections must be created and the applicable cApp™ groups
must be published. Publishing a group of tables is the process of copying tables from a source to a target. Refer to the
DataGarage® User Manual for a detailed explanation of the publish groups functionality.
The following groups must be published (if installed):

Page 6 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

DataGarage
cConfig
cMat
cMatClassBatch
cVend
cCust
cFICO
cHR
cHR2
To publish groups:
1. Select Publish (Groups) from Configuration on Switchboard.
2. Locate the Group.
3. Click Vertical View .
4. Click Edit .
5. Select a database from Target list box.
NOTE: The Target is typically the
DataGarage® database (dgSAP).
6. Select a database from Source
Database list box.
NOTE: The Source is an SAP Instance
associated with the SAPSystem
listed in the SAP Settings.
7. Click Publish Rules check box to allow
rules for tables in the group to be
published.
8. Verify Publish Tables Schema Owner Publish Groups
is disabled; this feature is not used by
the cApps™.
9. Click Save .
10. Click Publish button; a confirmation message displays.
11. Click Yes .
NOTE: Once the publish group process completes, a confirmation message displays.
12. Click Ok .
13. Repeat steps #2-12 for all applicable groups.

Page 7 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Add WHERE Clause Override Conditions

WHERE Clause Override conditions should be added to particular tables within DataGarage® to eliminate data records that
are not required for the cApps™ from being downloaded. The following table outlines the table and where clause override(s)
that must be configured for the applicable cApp™:
cApp™ Table Where Clause Override
ADRC WHERE ADDR_GROUP = 'BP'
cVend™
T002T WHERE SPRAS NOT IN ('a', 'b','c','d','i') AND SPRSL NOT IN ('a', 'b','c','d','i')
AUSP WHERE KLART in ('001', '022', '023')
KSSK WHERE KLART in ('001', '022', '023')
TQ29T WHERE [TOLERANZSL] < N'a'
cMat™ INOB WHERE (KLART = '022' OR KLART = '023') AND OBTAB = 'MARA'
ADRC WHERE ADDR_GROUP = 'BP'
AUSP WHERE KLART in ('001', '022', '023')
T002T WHERE SPRAS NOT IN ('a', 'b','c','d','i') AND SPRSL NOT IN ('a', 'b','c','d','i')
ADRC WHERE ADDR_GROUP = 'BP'
cCust™ T002 WHERE SPRAS NOT IN ('a', 'b','c','d','i')
T002T WHERE SPRAS NOT IN ('a', 'b','c','d','i') AND SPRSL NOT IN ('a', 'b','c','d','i')
ADRC WHERE ADDR_GROUP = 'BP'
cFICO™
T002T WHERE SPRAS NOT IN ('a', 'b','c','d','i')
cHR™ T002T WHERE SPRAS NOT IN ('a', 'b','c','d','i') AND SPRSL NOT IN ('a', 'b','c','d','i')

To add a WHERE Clause Override condition:

1. Click Target (Setup) on Switchboard.
2. Locate the Target.
3. Click Sources button.
4. Locate the Source.
5. Click Tables button.
6. Locate the Table.
7. Click Vertical View .
8. Click Advanced Settings tab.
9. Click Edit .
10. Enter text in Where Clause Override field.
11. Click Save .
NOTE: Tables to include in the DataGarage® vary
depending upon the cApp(s) installed.

Add a WHERE Clause Override Condition

Page 8 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Configure Parameters
There are specific DataGarage® parameters that must be configured in order to support the cApps™.
To configure DataGarage® parameters:
1. Select Parameters from Configuration on Switchboard.
2. Click Package Info tab.
3. Click Edit .
4. Set the RFC Name Space Option depending on the SAP configuration.
NOTE: The RFC Name Space Options are NAMESPACE and NONNAMESPACE. BackOffice Associates® owns the
Namespace /BOA; Non-namespace transports begin with ZBOA. Consult with the Basis Team to determine if the
SAP installation is configured to run Namespace or Non-namespace.
5. Select BOA RFC from RFC Type list box.
6. Click Save .

Build DTS Packages

All DTS packages must be created when each cApp™ is initially installed.
To build DTS packages:
1. Click Target (Setup) on Switchboard.
2. Locate the Target.
3. Click Sources button.
4. Locate the Source.
5. Click Build Package button; a confirmation message displays.
NOTE: If any tables have been configured to create a Finish DTS package, the Finish DTS package is created in addition to
the DTS package to download the entire content of the table. Refer to Create Finish DTS Packages section for
detailed information.
6. Click Yes .
NOTE: Once the build package process is submitted to run in the background, a confirmation message displays.
7. Click Ok .

Recreate Tables for Modified DTS Packages

If tables are modified, the DTS package(s) for those individual tables must be recreated. If tables have not been modified
these steps do not need to be completed.
To generate the packages for one table:
1. Click Target (Setup) on Switchboard.
2. Locate the Target.
3. Click Sources button.
4. Locate the Source.
5. Click Tables button.
6. Locate the Table.
7. Click Build Package button; a confirmation message displays.
8. Click Yes .
Page 9 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Create Finish DTS Packages

When a cApp™ request is finished, Finish DTS packages are executed to refresh data in DataGarage®. Only data related to
the request object (e.g., material, customer or vendor), not the entire contents of the tables, is refreshed.
In order to create a Finish package for a table, configure DataGarage® to specify which key fields are used to restrict the
data downloaded on Finish.
This configuration is delivered with the cApps™ for all standard tables which utilize the Finish process. If additional tables
are added to a cApps Finish process, those tables must be configured for Finish in DataGarage® as well.
To configure a Finish DTS package for an additional table:
1. Select Publish (Groups) from Configuration on Switchboard.
2. Locate the Group.
3. Click Tables button.
4. Locate the Table.
5. Click Finish button.
6. Click Add on the Grid Toolbar.

Specify Criteria for Finish DTS Package

7. Select a DataGarage® group from Group list box.
NOTE: The Group value is the group name listed in the Publish Groups section.
8. Enter a priority in Order field.
NOTE: The Order is the sequence of the variables in the finish stored procedure.
9. Select a field from Field Name list box.
10. Enter a variable to pass into the Finish DTS package in Variable Name field.
11. Click Save .
12. Click Target Source (Setup) Breadcrumb Link to create the Finish DTS package.
13. Locate the Table.
14. Click Build Package button to build a Finish DTS Package for the table; a confirmation message displays.
15. Click Yes .
NOTE: Once the build package process completes, a confirmation message displays.
16. Click Ok .

Refresh Data
If configuring and using the cApps™ directly subsequent to installation, refreshing all DataGarage® tables is not necessary;
only those tables that have been modified with the addition of a WHERE clause or which have had new DTS packages
created must be refreshed. Data can be refreshed at the target, source or table level. Refer to the DataGarage® User
Manual for detailed information on refreshing DataGarage®.
NOTE: Refreshing data in DataGarage® may take several hours depending on the volume of data.

Page 10 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Index Service Page

A CranSoft® Service page is executed periodically to populate CranSoft® indices. The relevant indices for each cApp™ are
listed in the corresponding Installation Manual. The Search Indexing Service (Full) Service page should be scheduled to
execute after the indexed tables are downloaded by DataGarage®.
The user configuring the Search Indexing Service (Full) Service page must be a member of the Designer Security Group for
the System Administration application to complete these steps.
NOTE: If the DataGarage® downloads are run after the index job executes, the indices may not be populated.
To set/adjust the schedule for this Service Page:
1. Click Admin on the Switchboard if logged into a WebApp.
Or
Click Admin on the Vertical Menu if currently on the Site home page.
2. Click WebApps on Switchboard.
3. Locate System Administration WebApp Name.
4. Click Pages .
5. Locate Search Indexing Service (Full) page.
6. Click Vertical View .
7. Click Service Properties tab.
8. Click Edit .
9. Enter a date in Next Service Date field.
Or
Click Calendar to select a date.
10. Enter a quantity in Service Qty field.
11. Select a unit of measure from Service UOM
field.
12. Click Save .
Customize Index Service Page

Page 11 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

cConfig™
This section contains configuration settings specific to cConfig™.

Configure Parameters
cConfig™ parameters are high-level fields used throughout the WebApp and must be configured per installation.
The SAP Information within cConfig™ parameters must be populated before the individual cApps™ are configured. SAP
information entered in cConfig™ automatically populates the corresponding fields in cMat™, cCust™, cVend™, cFICO™,
cHR™ and BAPIdirect™.
The SAP information for DataGarage® and BDCdirect® must be manually entered. Refer to the DataGarage® and
BDCdirect® sections for detailed information.
Refer to the following table for a description of cConfig™ parameters.
Parameter Group Parameter Description
Characters that are unable to be used in Scenario IDs or Business
Invalid Characters
Process IDs. The default values are '~`!@#$%^_+|{}:"<>.
Options Only used if cHR™ is installed. The Root Organization entered is
Root Organization copied into the cHR™ parameters. It is used to determine the Upper
Limit Organization for the organization chart.
SAP Instance SAP instance to which the cApps™ connect.
SAP Client Number to which the cApps™ connect. An instance of
SAP Client the cApps™ retrieves data from and posts data to a single SAP
client.
Language used for SAP login. If the SAP Language is a language
SAP Info
other than English and cMat™ is installed, populate this field after
SAP Language
valid units of measure have been defined for cMat™. Refer to the
Add Valid Units of Measure section for detailed information.
SAP Server Host Server hosting the SAP database.
SAP System No SAP system number
DataGarage Name of the DataGarage® database. Not editable by the end user.
Name of the DataGarage® database used for the cApps™. Not
DataGarage Info DataGarage Connection
editable by the end user.
SAP Connection Name of the SAP database used for the cApps™
Trace Logging Enables trace logging. By default, this setting is disabled.
Trace Log Settings Number of days the logs are stored. The default value is 0.It is
Trace Log Retention
recommended this value not be set > 7 days.

To configure parameters:
1. Log into cConfig™.
2. Select Parameters from Configuration on Switchboard.
3. Click Edit .
4. Update parameters as needed.
5. Click Save .
Page 12 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

NOTE: The cConfig™ parameters record must be validated after every initial installation of a cApp™.

Configure Exclude Dates

Dates can be set up to be excluded from the monitor functionality, which sends late notification emails when the processing
of a role has exceeded the defined processing time. Dates, such as holidays, can be configured to be excluded from
computation. Exclude Dates must be added for each calendar year. For example, if a request was submitted on a
Wednesday with one day to complete, and the following day was a holiday and therefore excluded, the request would not
have to be completed until Friday. Excluded dates must be added for each calendar year.
To configure exclude dates:
1. Select Exclude Dates from Configuration on
Switchboard.
2. Click Add on the Grid Toolbar.
3. Enter a date in Exclude Date field.
Or
Click Calendar to select a date. Configure Exclude Dates

4. Enter text in Description field.

5. Click Save .

Import Postal Codes

If postal codes will be validated in cCust™ and/or cVend™, they must be maintained in cConfig™. If postal codes are not
maintained in cConfig™, deactivate the postal code and zip code validation rules.
To import Postal Codes:
1. Obtain a file of all valid postal codes for the country.
2. Export the CranPort™ package cConfigPostalCodes_Template.
NOTE: Exporting this CranPort™ package creates a spreadsheet on the Web Server called
C:\cConfig\PostalCode_Template.xls. Refer to the CranPort™ User Manual for detailed information on exporting
a CranPort™ package.
3. Rename the auto-generated spreadsheet to C:\cConfig\PostalCode.xls.
4. Import the postal codes for the current country into the spreadsheet.
5. Log into cConfig™.
6. Select Postal Code Setup from
Configuration on Switchboard.
NOTE: If replacing existing postal codes for a
country, navigate to the Vertical View and
click the Clear Postal Codes button.
7. Click Add on the Grid Toolbar.
8. Select a country from Country list box.
9. Click Save .
10. Click Vertical View .
11. Click Import Postal Codes button to import Import Postal Codes
the spreadsheet; a confirmation message
displays.
12. Click Yes .
Page 13 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

NOTE: Once the postal codes for the country have been imported, a confirmation message displays.
13. Click Ok .
14. Click Apply Postal Codes button to validate the imported data for the country and to transfer it to the ttPostalCode
table; a confirmation message displays.
15. Click Yes .
NOTE: Once the postal codes for the country have been validated, a confirmation message displays.
16. Click Ok .
NOTE: If any entries are incorrect, validation messages display to outline what must be corrected. Correct the data, clear
the postal codes (via the Clear Postal Codes button on the Vertical View), import the spreadsheet and apply the
postal codes again.

View Definition Tables

Definition tables define all the elements of cConfig™ setup. These tables should never be changed by the end user, only the
individual configuring this application.
To view the cConfig™ definition tables, select Definition Tables from the Configuration Menu on the Switchboard.
Definitions are set for the following tables:
Role Type Posting Status Type
Task Type Request Status Type
Scenario Type Process Type
Number Assignment Type Table Mapping
Org Unit Type Decimal Delimiters
Child Scenario Criteria SAP Objects
Table Mapping provides additional functionality. It shows the relationship between the SAP tables, the cApp™ tables and
the BAPIdirect tables (where applicable). Having the cross reference is an easier way to validate posting and debug errors
rather than trying to parse the table mapping from the code. The Table Mapping page is read-only; the values are defined in
BAPIdirect™.

Page 14 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Setup Security
Org Units are defined at the object level. cMat™, cCust™ and cVend™ only support one object; cFICO™, however, supports
multiple objects. Org Units for each object in cFICO™ are individually configured. Org Units are not used by cHR™.
The following table outlines the Org Units available for each object:
Object Org Unit 1 Org Unit 2 Org Unit 3
Company NONE NONE NONE
Company Code NONE NONE NONE
Cost Center Controlling Area NONE NONE
Country Code Company NONE NONE
Customer Company Sales Organization Business Unit
GLAccount Company NONE NONE
Material Plant Sales Organization Business Unit
Profit Center Controlling Area NONE NONE
Vendor Company Purchasing Organization Business Unit

Org Unit values must be registered for each object. Refer to the cConfig™ Security Manual for information on registering the
following Org Units:
Controlling Area
Company
Plant
Sales Organization
Purchasing Organization
Business Unit

Define User Security

There is an additional security step for cConfig™. Once users have been created, assigned to the WebApp and assigned to
a Security Group, they must be registered within cConfig™ and assigned cApp-specific security (e.g., Org Units, roles and
business processes).
The following steps must be completed to finalize security for cMat™, cVend™, cCust™, cFICO™ and cHR™:
1. Register users
2. Assign Org Units (for cFICO™ implementations, only)
3. Assign roles
4. Assign business processes (not applicable for cHR™)
Refer to the cConfig™ Security Manual for details on defining user security.

Reset Security
Security is automatically reset if rights are extended to existing users for roles, business processes or Org Units. Security
must be manually reset if
There are additions, updates, or deletions to roles, business processes or Org Units

Page 15 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Individual users’ roles, business processes or Org Units are deleted.

Once all Org Units are created, security must be reset. Refer to the cConfig™ Security Manual for details on the reset
security feature.

Review Hide On Release Fields

Review all fields with Hide On Release enabled. The Hide On Release indicator should not be changed.
To review Hide On Release fields:
1. Click Reports on Switchboard.
2. Click Report (Hide On Release Columns) link.
Any fields hidden in the delivered cConfig™ that will be used onsite must be unhidden after installation.
To unhide fields:
1. Click Admin on Switchboard.
2. Click WebApps on Switchboard.
3. Locate the WebApp Name.
4. Click Pages .
5. Locate the Page.
6. Click Column Properties .
7. Click Edit .
8. Select Enabled from Control Status list box.
9. Click Save .
NOTE: Refer to the cConfig™ User Manual for detailed information on the Hide on Release feature.

Page 16 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

System Administration
This section contains configuration settings specific to System Administration.

Recompile Data Sources

Recompile the Data Sources to verify all views are correct. Once the SAP tables are created in the dgSAP database,
recompile the following Data Sources in the order listed:
dgSAP
DataGarage
BAPIdirect
BDCdirect
BDCPlus
cConfig
cMat/cVend/cFICO/cCust/cHR
To recompile a Data Source:
1. Click Admin on the Switchboard if logged into a WebApp.
Or
Click Admin on the Vertical Menu if currently on the Site home page.
2. Select Data Sources from Configuration on Switchboard.
3. Locate the Data Source Name.
4. Click Recompile Objects button; a confirmation message displays.
5. Click Yes .
6. Click Status .
7. Repeat steps #2-6 for all applicable Data Sources.
NOTE: Objects may have to be recompiled a few times. If recompile fails after three attempts, submit an issue to IssueTrak.
When recompiling objects in SQL Server 2008 an error message may display, stating that the recompile failed when
the view actually worked. There are two ways to resolve this error:
a. Open the view in Design mode and save.
b. Right-click the view. Select Script View As > Alter To > New Query Editor Window. Click Execute.

Page 17 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

BDCdirect®
This section contains configuration settings specific to BDCdirect®.

Populate SAP Information

The SAP information fields on the Parameters page in BDCdirect® must match those configured in cConfig™.
To populate SAP information:
1. Make note of the SAP Settings fields populated in
cConfig™.
NOTE: Refer to the cConfig™ section for additional
information.
2. Select Parameters from Configuration on
Switchboard.
3. Click Edit .
4. Update the SAP Settings fields to match that of
cConfig™.
5. Click NameSpace check box if the SAP installation Populate SAP Information
is configured to run Namespace objects.
NOTE: BackOffice Associates® owns the Namespace /BOA; Non-namespace transports begin with ZBOA. Consult with
the Basis Team to determine if the SAP installation is configured to run Namespace or Non-namespace.
6. Click Save .

Page 18 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

BAPIdirect™
This section contains configuration settings specific to BAPIdirect™.

Populate SAP Information

The only SAP setting in BAPIdirect™ is to determine whether the SAP installation is configured to run Namespace or
Non-namespace objects.
To populate SAP information:
1. Select Parameters from Configuration on Switchboard.
2. Click Edit .
3. Click Use Name Space check box if the SAP installation is configured to run Namespace objects.
NOTE: BackOffice Associates® owns the Namespace /BOA; Non-namespace transports begin with ZBOA. Consult with
the Basis Team to determine if the SAP installation is configured to run Namespace or Non-namespace.
4. Click Save .

Page 19 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

cMat™
This section contains configuration settings specific to cMat™.

Configure Parameters
cMat™ parameters are fields that configure the WebApp per installation. Refer to the following table for a description of
cMat™ parameters.
Parameter Group Parameter Description
Characters not permitted in the Material Name or Description
Invalid Characters
fields. The default values are ~`!@#$%^*+|{}:<>.
Characters not permitted in the Material Number field. The
Invalid ID Characters
Options default values are ~`!@#$%^*()_+|{}:"<>'.
If checked, the Delete Archives button displays on the Delete
Enable Archive Delete Archives page to allow archives to be deleted. By default, this
setting is enabled.
SAP Instance SAP instance used by SAP when interfacing with the application.
Automatically
SAP Client SAP client the application is interfacing with.
SAP Info populated from
SAP cConfig™ SAP language used when interfacing with the application.
Language
DataGarage Name of the DataGarage® database.
DataGarage Automatically Name of the DataGarage® database with which the application is
DataGarage Info Connection populated from interfacing.
cConfig™
SAP SAP database used by the application.
Connection

To configure parameters:
1. Log into cMat™.
2. Select Parameters from Configuration on Switchboard.
3. Click Edit .
4. Update parameters as needed.
5. Click Save .

Add Valid Units of Measure

SAP’s table of valid units of measure (UOM) contains over 200 entries. The Valid UOMs feature in cMat™ lists the units of
measure available for a particular cMat™ implementation. This page allows the client to designate which units of measure
can be entered as the Base UOM for a new material request. The UOM is always taken from this list, not SAP’s master list.
Make sure to check the units of measure that are already in use in the client’s system. All existing units being used should
either be added to the list of valid units of measure or be updated to the proper unit in the SAP system. Look beyond base
units to all units used by the system. Determine which fields are units of measure by looking at the data dictionary for each
table. The Data Type for units of measure is UNIT.
If the SAP Language on the Parameters page is changed to a language other than English, the Valid UOM may not display
in the updated language. In such an event, validate any record on the Valid UOM page before changing the SAP Language
on the Parameters page. Entries are automatically generated in the new language.

Page 20 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

To add a valid UOM:

1. Select Valid UOMs from Configuration on Switchboard.
2. Click Add on the Grid Toolbar.

Add a Valid UOM

3. Select a unit from Internal UOM list box.
4. Click Allow For Base check box to assign the UOM as a base unit.
NOTE: Allow For Base permits the UOM to be entered on a Request (Basic) page of a cApp™. All UOMs with Allow For
Base deactivated are considered Alternate UOMs, which are available on the Request (AUM) page.
5. Click Save .
NOTE: The Dimension, Unit of Measure and Language Key fields are automatically generated.

Configure Default Tables

Table-level defaults are established during implementation of the cApps™ and are used to enhance the data entry
experience by populating commonly-used fields with pre-set values. Additionally, some defaults are established to specify
records which should be auto-generated at the time a request is submitted. Refer to the Configure Auto-Extend Defaults
section for detailed information.
The default table names reference the corresponding SAP table name. Defaults are automatically populated when the
corresponding Request page record is created.
Default table values are delivered empty. It is recommended that all defaults be set up in cMat™ before configuring the
application. Where allowed, always create a default value with an asterisk (*) for all keys, even if values are not
specified at this level.
To configure default tables, select Defaults from the Configuration Menu on the Switchboard.
NOTE: Defaults do not copy into request records already in SAP.

Page 21 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Refer to the following table for details on cMat™ defaults.

Default Table Key Application Data Pages
ttDGTMD_DGTM2 Default Scenario ID, DG Regulation Request (Dangerous Goods)
ttEINEDefault Scenario ID, Plant, Info Type Request (Purchasing Info Rec OrgData)
ttEKPODefault Scenario ID, Plant, Item Category Request (Purchasing Contract Items)
ttMAEXDefault Scenario ID, Country, Legal Regulation Request (Legal Control)
ttMAPL_PLKODefault Scenario ID, Plant, Task List Type Request (Routing) & Request (Master Recipe)
ttMAPR_PROPDefault Scenario ID, Plant Request(Forecasting)
ttMARADefault Scenario ID, Material Type Request, Request (Basic) & Request (Basic
Purchasing)
ttMARCDefault Scenario ID, Plant Request (Plant) & Request (Foreign Trade)
ttMARDDefault Scenario ID, Plant, Storage Location Request (Storage Location)
ttMAST_STKODefault Scenario ID, Plant, BOM Usage Request (BOM)
ttMBEWDefault Scenario ID, Plant/Valuation Area, Valuation Request (Accounting) & Request (Accounting
Type Split Valuations)
ttMKALDefault Scenario ID, Plant Request (Production Version) & Request (Mass
Production Version)
ttMLANDefault Country, Tax Category Request (Tax Category)
ttMLGNDefault Scenario ID, Warehouse Number Request (Warehouse)
ttMLGTDefault Scenario ID, Warehouse Number, Storage Request (Warehouse Storage Type)
Type
ttMVKEDefault Scenario ID, Sales Organization, Distribution Request (Sales)
Channel, Item Category Group
ttPLFLDefault Scenario ID, Plant, Task List Type, Sequence Request (Routing Sequences)
Category
ttPLPODefault Scenario ID, Plant, Task List Type, Std. Val. Request (Routing Steps/Operations), Request
Key (from the Work Center) (Master Recipe Steps/Operations) & Request
(Routing Steps/Operations Interoperation)
ttQMATDefault Scenario ID, Plant, Inspection Type Request (Material Quality)
ttSTPODefault Scenario ID, Plant, BOM Usage, Item Request (BOM Components)
Category

Default tables have been provided where it is logical to default data. For example, Purchasing Source List data would vary
widely, so source list data is not available for defaults.
Most default tables contain ScenarioID as a key. For those that do, defaults may be specified at four levels and are
processed in the following order:
All keys specified – Valid values populated for each key field.
Across Scenario for specified keys – Asterisk (*) populated for Scenario ID and valid values populated for all other
key fields.
Scenario specified for all keys – Valid value populated for Scenario ID and asterisk (*) for all other key fields.

Page 22 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Across all Scenarios and keys – Asterisk (*) populated for Scenario ID and all other key fields.
Records on the Default page write to the corresponding table. When the record is validated, all possible combinations of
default values are computed and stored in a second extended table. When a record is added, changed or deleted, the
defaults process in the background and compute the exact default values for all combinations of keys. When new key values
(e.g., Account Group, Plant) are configured in SAP and/or cConfig™, at least one default value for each table must be
validated in order to recreate the extended default tables.
Configure Auto-Extend Defaults
If the following default tables are populated, target table records are generated automatically.
Default Table Keys Related Request Page Processing
ttKSSKDefault Material Type, Request (Class) Classes specified in ttKSSKDefault are automatically
Class Type, inserted into the ttKSSK table when a create Request is
Class Submitted for the specified Material Type and ‘Auto
Create Class’ is enabled on the Request.
ttMARMDefault Material Type, Request (AUM) Alternative Units of Measure specified in
Order Unit (Base ttMARMDefault are automatically inserted into the
Unit of Measure) ttMARM table when a create Request is submitted for
the specified Material Type/Order Unit combination.
ttDefaultPlant Plant Request (Org Unit – Plants entered in ttDefaultPlant are automatically
Plants) inserted into ttRequestOrgUnit1 when requests are
created.
ttDefaultSalesArea Sales Request (Org Unit – Sales Sales Areas entered in ttDefaultSalesArea are
Organization, Organizations), Request automatically inserted into ttRequestSalesArea and
Distribution (Sales Areas) Sales Organizations are inserted into
Channel ttRequestOrgUnit2 when requests are created.
ttMARDDefault Scenario ID, Request (Storage If Autoextend Storage Location is enabled, the record is
Plant, Storage Location) automatically inserted into the ttMARD table when the
Location corresponding plant (ttMARC) record is created, on
submit of the request or when added on the Request
(Plant) page, and when ‘Auto Create Warehouse’ is
enabled on the Request.
ttMLGTDefault Scenario ID, Request (Warehouse If Auto Extend Storage Type is enabled, the record is
Warehouse Storage Type) automatically inserted into the ttMLGT table when the
Number, corresponding warehouse (ttMLGN) record is created,
Storage Type on submit of the request or when added on the Request
(Warehouse) page, and when ‘Auto Create Warehouse’
is enabled on the Request.

Add Default Values

To add a default value:
1. Click Configuration on Switchboard.
2. Select a default table from Defaults on Vertical Menu.
3. Click Add on the Grid Toolbar.
4. Select options from available list boxes.
Or
Click Insert to manually enter a value.
5. Click Save .

Page 23 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Build QMAT Default

The QMAT defaults must be built from the TQ34 table.
To build QMAT defaults:
1. Click Configuration on Switchboard.
2. Select Build QMAT Default from TQ34 from Defaults on Vertical Menu.
3. Click Build Defaults From TQ34 button; a confirmation message displays.
4. Click Yes .
NOTE: Once the TQ34 Default build process completes, a confirmation message displays.
5. Click Ok .

Configure Message Center

The Message Center on the cMat™ Home page is delivered blank and should be configured with appropriate text as part of
implementation.
To configure the Message Center text:
1. Navigate to cMat™ Home page.
2. Click Add on the Grid Toolbar.
3. Click HTML Edit ; the Editor window displays.
4. Enter text.
5. Click Save to close the Editor window.
6. Click Save to save the new message.

Page 24 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

cCust™
This section contains configuration settings specific to cCust™.

Configure Parameters
cCust™ parameters are fields that configure the WebApp per installation. Refer to the following table for a description of
cCust™ parameters.
Parameter Group Parameter Description
Characters not permitted in the Customer Name or Description fields.
Invalid Characters
The default values are ~`!@#$%^*+|{}:<>.
Characters not permitted in the Customer Number field. The default
Invalid ID Characters
values are ~`!@#$%^*()_+|{}:"<>'.

Options Defaulted into the Country fields on the Request page and into any
Default Country default records created on the KNA1_ADRC Defaults page. The
default value is US-USA.
If checked, the Delete Archives button displays on the Delete
Enable Archive Delete Archives page to allow archives to be deleted. By default, this setting
is enabled.
SAP Instance Automatically SAP instance used by SAP when interfacing with the application.
populated
SAP Info SAP Client SAP client the application is interfacing with.
from
SAP Language cConfig™ SAP language used when interfacing with the application.
DataGarage Name of the DataGarage® database.
Automatically
populated Name of the DataGarage® database with which the application is
DataGarage Info DGConnection
from interfacing.
cConfig™
SAP Connection SAP database used by the application.

To configure parameters:
1. Log into cCust™.
2. Select Parameters from Configuration on Switchboard.
3. Click Edit .
4. Update parameters as needed.
5. Click Save .

Set Up Account Groups

Customer Account Groups page determines what is displayed on each Overview page in cCust™. Tasks can be configured
by account group.
Additional account group functions include the following:
Automatically generates dynamic views for the Customer pages based on Account Group.
Generates validation rules based on the SAP Configuration for required fields based on Account Group, Company Code
and Sales Organization.
Sets up Partner Functions.

Page 25 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Account Groups should be set up at the onset of the project and whenever a new Account Group, Company Code or Sales
Organization is added to the SAP configuration. The setup process should also be repeated when Account Group field
properties are reconfigured in SAP.
The following sections outline the seven steps required to set up a Customer Account Group.
Step 1 – Register a Customer Account Group
All customer account groups to be used by cCust™ must be registered.
To register a customer account group:
1. Click Configuration on Switchboard.
2. Select Group Registration from Account Group Setup on Vertical Menu.
NOTE: All Customer Account Groups that are valid for cCust™ must be registered on this page. cCust™ is delivered with
standard, pre-registered SAP groups. Do not delete the delivered Account Groups.
3. Click Add on the Grid Toolbar.

Register a Customer Account Group

4. Select a group from Account Group list box.
NOTE: The options in the Account Group list box include all possible groups in SAP.
5. Click the appropriate check boxes to designate available tasks.
6. Click Auto Create Partner Functions check box to automatically insert mandatory and recommended partner function
records when sales records are created on a Request for this Account Group.
7. Click Save .
Step 2 – Generate Customer Account Group Tables
The account group configuration process builds the following tables:
ttCustomerAccountGroupConfig – Contains one record for each Account Group, Company Code, Sales Organization
combination and displays customer table fields in SAP that are required, optional and suppressed. The table is used by
the validation rules.
ttCustomerAccountGroup_DynamicView – Contains SQL page views for all Account Groups. Suppressed fields are
removed from the view.
ttCustomerAccountGroup_ValidationRegistration – Contains SQL views and page validation data needed to support
required data elements on SAP tables by Account Group, Company Code and/or Sales Organization.
To generate Customer Account Groups:
1. Click Configuration on Switchboard.
2. Select Configuration Setup from Account Group Setup on Vertical Menu.
3. Click Generate button; a confirmation message displays.
4. Click Yes .
NOTE: Once the generate table process has been successfully submitted to the background, a confirmation message
displays.
5. Click Ok .

Page 26 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Step 3 –View Customer Account Group Configuration Data

The Customer Account Group Configuration Data page displays the objects from the ttCustomerAccountGroupConfig
table and all configurable fields in cCust™.
To view Customer Account Group Configuration data:
1. Click Configuration on Switchboard.
2. Select Configuration Data from Account Group Setup on Vertical Menu.
Step 4 – View Customer Account Group Configuration Validation View
The Customer Account Group Config. Validation View page displays the objects that require validation rules to be created.
The Vertical View displays validation view content for rules that have not been registered.
To view Customer Account Group Configuration Validation view:
1. Click Configuration on Switchboard.
2. Select Validation Views from Account Group Setup on Vertical Menu.
Step 5 – View Customer Account Group Configuration Dynamic View
The Customer Account Group Configuration Dynamic View page displays the objects with initial Dynamic Views. These
pages must be customized to further limit or hide optional fields that are not used. The Vertical View displays specific view
content.
To view Customer Account Group configuration dynamic view:
1. Click Configuration on Switchboard.
2. Select Dynamic Views from Account Group Setup on Vertical Menu.
Step 6 – Create Customer Account Group Configuration Data
The Customer Account Group Configuration Create page provides the following functions:
Create Dynamic Views.
Create and register validation rules.
Generate the SAP configured Partner Functions in the ttKNVPDefaults table.
To create Customer Account Group Configuration data:
1. Click Configuration on Switchboard.
2. Select Configuration Create from Account Group Setup on Vertical Menu.
3. Click Dynamic View button to create all dynamic views that do not currently exist in cCust™; a confirmation message
displays.
4. Click Yes .
NOTE: Once the dynamic view creation process completes, a confirmation message displays.
5. Click Ok .
6. Click Validation View button to create all validation rules that do not currently exist in cCust™ and to register all rules
that are not currently registered; a confirmation message displays.
7. Click Yes .
NOTE: Once the validation rule creation and registration process completes, a confirmation message displays.
8. Click Ok .
9. Click Partner Functions button to generate the SAP Configured Partner Functions in the ttKNVPDefaults table that do
not currently exist in cCust™; a confirmation message displays.

Page 27 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

10. Click Yes .

NOTE: Once the partner function default creation process completes, a confirmation message displays.
11. Click Ok .
NOTE: SAP tables that control the Partner Functions are T077D and TPAER.
Step 7 – Clear Cache
Since account group generation updates base CranSoft® tables, changes will not take effect until the cache is cleared. In
order to clear the cache, security must be granted to the System Administration WebApp.
To clear the cache:
1. Click Admin on the Switchboard if logged into a WebApp.
Or
Click Admin on the Vertical Menu if currently on the Site home page.
2. Select Parameters from Configuration on Switchboard.
3. Click Clear Cache button; a confirmation message displays.
4. Click Yes .
NOTE: Once the clear cache process completes, a confirmation message displays.
5. Click Ok .

Configure Default Tables

Defaults are established during implementation of the cApps™ and are used to enhance the data entry experience by
populating commonly-used field with pre-set values.
The names of these default tables reference the SAP table name. Defaults are automatically populated when the
corresponding Request page record is created.
Defaults are delivered empty. It is recommended that all defaults be set up in cCust™ before configuring the application.
Always create a default record with an asterisk (*) for all keys, even if values are not specified at this level.
To configure default tables, select Defaults from the Configuration Menu on the Switchboard.
NOTE: Defaults do not copy into request records already in SAP.
Refer to the following table for details on cCust™ defaults.
Default Table Key Application Data Page
Request (General), Request
ttKNA1_ADRCDefault Scenario ID, Account Group
(Address – General)
ttKNB1Default Scenario ID, Account Group, Company Code Request (Company Code)
ttKNB5Default Scenario ID, Company Code, Dunning Area Request (Dunning Data)
ttKNKKDefault Scenario ID, Credit Control Area Request (Credit Control Area)
ttKNVIDefault Scenario ID, Account Group, Country, Tax Category Request (Sales Tax Categories)
ttKNVPDefault Account Group Request (Partner Functions)
Scenario ID, Account Group, Sales Organization, Distribution
ttKNVVDefault Request (Sales)
Channel, Division

Page 28 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Default tables have been provided where it is logical to default data. They may be specified at four levels and are processed
in the following order:
All keys specified – Valid values populated for each key field.
Across Scenario for specified keys – Asterisk (*) populated for Scenario ID and valid values populated for all other
key fields.
Scenario specified for all keys – Valid value populated for Scenario ID and asterisk (*) for all other key fields.
Across all Scenarios and keys – Asterisk (*) populated for Scenario ID and all other key fields.
Records on the Default page write to the corresponding table. When the record is validated, all possible combinations of
default values are computed and stored in a second extended table. When a record is added, changed or deleted, the
defaults process in the background and compute the exact default values for all combinations of keys. When new key values
(e.g., Account Group, Company Code, Sales Organization) are configured in SAP and/or cConfig™, at least one default
value for each table must be validated in order to recreate the extended default tables.
Tax Category and Partner Function defaults work differently than other defaults.
On the Default KNVI page, valid Tax Categories are automatically generated when Account Group and Country are
populated. Afterward, Tax Classification can be edited for each Tax Category.
During Customer Account Group Configuration, valid partner functions for each account group are added to the
ttKNVPDefault table and become visible on the Default KNVP page. If the Partner Function is mandatory for the Account
Group in SAP, the record cannot be edited or deleted from the Default KNVP page. Non-mandatory partner functions can be
deleted or marked Recommended. Mandatory and recommended partner functions are automatically created for a Request
when a Sales record is created if that Account Group is configured to auto create partner functions.
NOTE: KNVI Defaults and KNVP Defaults are the exceptions to how cCust™ defaults are processed.
Add Default Values
To add a default value:
1. Click Configuration on Switchboard.
2. Select a default table from Defaults on Vertical Menu.
3. Click Add on the Grid Toolbar.
4. Select options from available list boxes.
Or
5. Click Insert , to manually enter a default value.
6. Click Save .
KNVI Defaults
KNVI Defaults (Tax Category) may only be configured with asterisk (*) populated for Scenario ID and valid values populated
for all other keys.
KNVP Defaults
KNVP Defaults (Partner Functions) are generated by the Account Groups setup process. Mandatory partner functions cannot
be edited on the Default KNVP page. Only the Recommended indicator can be changed for optional KNVP Default records.

Create Partner Function Requirements

Partner Function Requirements allow the Administrator to decide if Partner Functions should require additional information
beyond SAP’s requirements.
To place additional requirements on a Partner function:

Page 29 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

1. Select Partner Function Requirements from Configuration on Switchboard.

2. Click Add on the Grid Toolbar.

Create Partner Function Requirements

3. Select a value from Partner Function list box.
4. Click Company Code Required check box.
And/Or
Click Sales Org Required check box.
NOTE: If Company Code Required is selected for a Partner Function, any customer added for that Partner Function must
exist in a valid Company Code. If Sales Org Required is selected for a Partner Function, any customer added for
that Partner Function must exist in a valid Sales Organization.
5. Click Save .

Configure Message Center

The Message Center on the cCust™ Home page is delivered blank and should be configured with appropriate text as part of
implementation.
To configure the Message Center text:
1. Navigate to cCust™ Home page.
2. Click Add on the Grid Toolbar.
3. Click HTML Edit ; the Editor window displays.
4. Enter text.
5. Click Save to close the Editor window.
6. Click Save to save the new message.

Page 30 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

cVend™
This section contains configuration settings specific to cVend™.

Configure Parameters
cVend™ parameters are fields that configure the WebApp per installation. Refer to the following table for a description of
cVend™ parameters.
Parameter Group Parameter Description
Characters not permitted in the Vendor Name or Description fields.
Invalid Characters
The default values are ~`!@#$%^*+|{}:<>.
Characters not permitted in the Vendor Number field. The default
Invalid ID Characters
values are ~`!@#$%^*()_+|{}:"<>'.

Options Defaulted into the Country fields on the Request page and into any
Default Country default records created on the LFA1_ADRC Defaults page. The
default value is US-USA.
If checked, the Delete Archives button displays on the Delete
Enable Archive Delete Archives page to allow archives to be deleted. By default, this setting
is enabled.
SAP Instance Automatically SAP instance used by SAP when interfacing with the application.
populated
SAP Info SAP Client SAP client the application is interfacing with.
from
SAP Language cConfig™ SAP language used when interfacing with the application.
DataGarage Name of the DataGarage® database.
Automatically
DataGarage populated Name of the DataGarage® database with which the application is
DataGarage Info
Connection from interfacing.
cConfig™
SAP Connection SAP database used by the application.

To configure parameters:
1. Log into cVend™.
2. Select Parameters from Configuration on Switchboard.
3. Click Edit .
4. Update parameters as needed.
5. Click Save .

Set Up Account Groups

The Vendor Account Groups page determines what is displayed on each Overview page in cVend™. Tasks can be
configured by account group.
Additional account group functions include the following:
Automatically generates dynamic views for the Vendor pages based on Account Group.
Generates validation rules based on the SAP Configuration for required fields, based on Account Group, Company Code
and Purchasing Organization.
Sets up Partner Functions.

Page 31 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Account Groups should be set up at the onset of the project and whenever a new Account Group, Company Code or
Purchasing Organization is added to the SAP Configuration. The setup process should also be repeated when Account
Group field properties are reconfigured in SAP.
The following sections outline the steps required to set up a Vendor Account Group.
Step 1 – Register Vendor Account Groups
All vendor Account Groups to be used by cVend™ must be registered.
To register a Vendor Account Group:
1. Click Configuration on Switchboard.
2. Select Group Registration from Account Group Setup on Vertical Menu.
NOTE: All Vendor Account Groups that are valid for cVend™ must be registered on this page. cVend™ is delivered with
standard, pre-registered SAP groups . Do not delete the delivered Account Groups.
3. Click Add on the Grid Toolbar.

Register a Vendor Account Group

4. Select a group from Account Group list box.
NOTE: The options in the Account Group list box include all possible account groups in SAP.
5. Click the appropriate check boxes to designate available tasks.
6. Click Auto Create Partner Functions check box to automatically insert mandatory and recommended partner function
records when sales records are created on a Request for this Account Group.
7. Click Save .
Step 2 – Generate Vendor Account Group Tables
The account group configuration process builds the following tables:
ttVendorAccountGroupConfig – Contains one record for each Account Group, Company Code, Purchasing
Organization combination and displays vendor table fields in SAP that are required, optional and suppressed. The table
is used by the validation rules.
ttVendorAccountGroup_DynamicView – Contains SQL views for all Account Groups. Suppressed fields are removed
from the view.
ttVendorAccountGroup_ValidationRegistration – Contains SQL views and page validation data needed to support
required data elements on SAP tables by Account Group, Company Code and/or Purchasing Organization.
To generate Vendor Account Groups:
1. Click Configuration on Switchboard.
2. Select Configuration Setup from Account Group Setup on Vertical Menu.
3. Click Generate button; a confirmation message displays.
4. Click Yes .
NOTE: Once the generate tables process has been submitted to run in the background, a confirmation message displays.
5. Click Ok .

Page 32 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Step 3 – View Vendor Account Group Configuration Data

The Vendor Account Group Configuration Data page displays the objects from the ttVendorAccountGroupConfig table and
all configurable fields in cVend™.
To view Vendor Account Group Configuration data:
1. Click Configuration on Switchboard.
2. Select Configuration Data from Account Group Setup on Vertical Menu.
Step 4 – View Vendor Account Group Configuration Validation View
The Vendor Account Group Configuration Validation View page displays the objects where validation views must be created.
The Vertical View displays validation view content for rules that have not been registered.
To view Vendor Account Group Configuration Validation View:
1. Click Configuration on Switchboard.
2. Select Validation Views from Account Group Setup on Vertical Menu.
Step 5 – View Vendor Account Group Configuration Dynamic View
The Vendor Account Group Configuration Dynamic View page displays the pages that reference base Dynamic Views as
either Horizontal and/or Vertical View. These pages must be customized to further limit or hide optional fields that are not
used. The Vertical View displays specific view content.
To view Vendor Account Group Configuration Dynamic View:
1. Click Configuration on Switchboard.
2. Select Dynamic Views from Account Group Setup on Vertical Menu.
Step 6 – Create Vendor Account Group Configuration Data
The Vendor Account Group Configuration Create page provides the following functions:
Create Dynamic Views.
Create and register validation rules.
Generate the SAP configured Partner Functions in the ttWYT3Defaults table.
To create Vendor Account Group Configuration data:
1. Click Configuration on Switchboard.
2. Select Configuration Create from Account Group Setup on Vertical Menu.
3. Click Dynamic View button to create all dynamic views that do not currently exist in cVend™; a confirmation message
displays.
4. Click Yes .
NOTE: Once the dynamic view creation process completes, a confirmation message displays.
5. Click Ok .
6. Click Validation View button to create all validation rules that do not currently exist in cVend™ and to register all rules
that are not currently registered; a confirmation message displays.
7. Click Yes .
NOTE: Once the validation rule creation and registration process completes, a confirmation message displays.
8. Click Ok .
9. Click Partner Functions button to generate the SAP Configured Partner Functions in the ttWYT3Defaults table that do
not currently exist in cVend™; a confirmation message displays.

Page 33 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

10. Click Yes .

NOTE: Once the partner function default creation process completes, a confirmation message displays.
11. Click Ok .
NOTE: SAP tables that control the Partner Functions are T077K and TPAER.
Step 7 – Clear Cache
Since account group generation updates base CranSoft® tables, changes will not take effect until the cache is cleared. In
order to clear the cache, security must be granted to the System Administration WebApp.
To clear the cache:
1. Click Admin on the Switchboard if logged into a WebApp.
Or
Click Admin on the Vertical Menu if currently on the Site home page.
2. Select Parameters from Configuration on Switchboard.
3. Click Clear Cache button; a confirmation message displays.
4. Click Yes .
NOTE: Once the clear cache process completes, a confirmation message displays.
5. Click Ok .

Manage Defaults
Defaults are established during implementation of the cApps™ and are used to enhance the data entry experience by
populating commonly used field with pre-set values.
The names of these default tables reference the SAP table name. Defaults are automatically populated when the
corresponding Request page record is created.
Defaults are delivered empty. It is recommended that all defaults be set up in cVend™ before configuring the application.
Always create a default record with an asterisk (*) for all keys, even if values are not specified at this level.
To configure default tables, select Defaults from the Configuration Menu on the Switchboard.
NOTE: Defaults do not copy into request records already in SAP.
Refer to the following table for details on cVend™ defaults.
Default Table Key Application Data Page
ttLFA1_ADRCDefault Scenario ID, Account Group Request (Address – General), Request (General)
ttLFB1Default Scenario ID, Account Group, Company Code Request (Company Code)
ttLFB5Default Scenario ID, Company Code, Dunning Area Request (Dunning Data)
ttLFM1Default Scenario ID, Account Group, Purchasing Organization Request (Purchasing)
Scenario ID, Account Group, Purchasing Organization,
ttLFM2Default Request (Purchasing – Alternative)
Plant
ttWYT3Default Account Group Request (Partner Functions)

Default tables have been provided where it is logical to default data. The WYT3 (partner function) defaults are generated by
the Account Groups setup process. All other defaults may be specified at four levels and are processed in the following
order:

Page 34 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

All keys specified – Valid values populated for each key field.
Across Scenario for specified keys – Asterisk (*) populated for Scenario ID and valid values populated for all other
key fields.
Scenario specified for all keys – Valid value populated for Scenario ID and asterisk (*) for all other key fields.
Across all Scenarios and keys – Asterisk (*) populated for Scenario ID and all other key fields.
Records on the Default page write to the corresponding table. When the record is validated, all possible combinations of
default values are computed and stored in a second extended table. When a record is added, changed or deleted, the
defaults process in the background and compute the exact default values for all combinations of keys. When new key values
(e.g., Account Group, Company Code, Purchasing Organization) are configured in SAP and/or cConfig™, at least one default
value for each table must be validated in order to recreate the extended default tables.
Partner Function defaults work differently than other defaults. During Vendor Account Group Configuration, valid partner
functions for each account group are added to the ttWYT3Default table and, therefore, become visible on the Default WYT3
page. If the Partner Function is mandatory for the Account Group in SAP, the record cannot be edited or deleted from the
Default WYT3 page. Non-mandatory partner functions can be deleted or marked Recommended. Mandatory and
recommended partner functions are automatically created for a Request when a Purchasing record is created if that Account
Group is configured to auto create partner functions.
NOTE: WYT3 Defaults are the exceptions to how cVend™ defaults are processed.
Add Default Values
To add a default value:
1. Click Configuration on Switchboard.
2. Select a default table from Defaults on Vertical Menu.
3. Click Add on the Grid Toolbar.
4. Select options from available list boxes.
Or
Click Insert to manually add a default value.
5. Click Save .
WYT3 Defaults
WYT3 (Partner Function) defaults are generated by the Account Groups setup process. Mandatory partner functions cannot
be edited on the Default WYT3 page. Only the Recommended indicator can be changed for optional WYT3 Default records.

Create Partner Function Requirements

Partner Function Requirements allow the Administrator to decide if Partner Functions should require additional information
beyond SAP’s requirements.
To place additional requirements on a Partner Function:
1. Select Partner Function Requirements from Configuration on Switchboard.
2. Click Add on the Grid Toolbar.

Create Partner Functions Requirements

3. Select a value from Partner Function list box.
4. Click Company Code Required check box.
Page 35 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

And/Or
Click Purchase Org Required check box.
NOTE: If Company Code Required is selected for a Partner Function, any vendor added for that Partner Function must
exist in a valid Company Code. If Purchase Org Required is selected for a Partner Function, any vendor added for
that Partner Function must exist in a valid Purchasing Organization.
5. Click Save .

Configure Message Center

The Message Center on the cVend™ Home page is delivered blank and should be configured with appropriate text as part of
implementation.
To configure the Message Center text:
1. Navigate to cVend™ Home page.
2. Click Add on the Grid Toolbar.
3. Click HTML Edit ; the Editor window displays.
4. Enter text.
5. Click Save to close the Editor window.
6. Click Save to save the new message.

Page 36 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

cFICO™
This section contains configuration settings specific to cFICO™.

Configure Parameters
cFICO™ parameters are high-level fields used throughout the WebApp that must be configured per installation. Refer to the
following table for a description of cFICO ™ parameters.
Parameter Group Parameter Description
Characters not permitted in the Object Name or Description fields.
Invalid Characters
The default values are ~`!@#$%^*+|{}:"<>.
Characters not permitted in the Object Number field. The default
Invalid ID Characters
Options values are ~`!@#$%^*()_+|{}:"<>'.
If checked, the Delete Archives button displays on the Delete
Enable Archive Delete Archives page to allow archives to be deleted. By default, this setting
is enabled.
SAP Instance SAP instance used by SAP when interfacing with the application.
Automatically
SAP Client SAP client the application is interfacing with.
SAP Info populated from
SAP cConfig™ SAP language used when interfacing with the application.
Language
DataGarage Name of the DataGarage® database.
DataGarage Automatically Name of the DataGarage® database with which the application is
DataGarage Info Connection populated from interfacing.
cConfig™
SAP SAP database used by the application.
Connection

To configure parameters:
1. Log into cFICO™.
2. Select Parameters from Configuration on Switchboard.
3. Click Edit .
4. Update parameters as needed.
5. Click Save .

Generate GL Account Tables

The account group configuration process builds the following tables:
ttGLAccountConfig – Contains one record for each Chart of Accounts/GL Account Group combination and displays
table fields in SAP that are required, optional and suppressed. The table is used by the validation rules.
ttGLAccount_DynamicView – Contains SQL page views for all Chart of Accounts/GL Account Group. Suppressed
fields are removed from the view.
ttGLAccount_ValidationRegistration – Contains SQL views and page validation data needed to support required data
elements on SAP tables by GL Account.
To generate GL Account Tables:
1. Select GL Account Setup from Configuration on Switchboard.
Page 37 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

2. Click Process button; a confirmation message displays.

3. Click Yes .
NOTE: When the generate table process has been successfully submitted to the background, a confirmation message
displays.
4. Click Ok .

Configure Message Center

The Message Center on the cFICO™ Home page is delivered blank and should be configured with appropriate text as part of
implementation.
To configure the Message Center text:
1. Navigate to cFICO ™ Home page.
2. Click Add on the Grid Toolbar.
3. Click HTML Edit ; the Editor window displays.
4. Enter text.
5. Click Save to close the Editor window.
6. Click Save to save the new message.

Page 38 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

cHR™
This section contains configuration settings specific to cHR™.

Configure Parameters
cHR™ parameters are high-level fields used throughout the WebApp that must be configured per installation. Refer to the
following table for a description of cHR ™ parameters.
Parameter Group Parameter Description
Characters not permitted in the Object Name or Description fields.
Invalid Characters
The default values are ~`!@#$%^*+|{}:"<>.
Characters not permitted in the Object Number field. The default
Invalid ID Characters
values are ~`!@#$%^*()_+|{}:"<>'.
If checked, the Delete Archives button displays on the Delete
Enable Archive Delete Archives page to allow archives to be deleted. By default, this setting
is enabled.
Options
Delete Archives Before Data that contrails when archives are deleted.
Finish in Background Not supported in the current release.
Defaulted into the Country fields on the Request page and into any
Default Country default records created on the LFA1_ADRC Defaults page. The
default value is US-USA.
Manual Security Update Not supported in the current release.
SAP Instance SAP instance used by SAP when interfacing with the application.
Automatically
SAP Client SAP client the application is interfacing with.
populated from
SAP Info SAP cConfig™ SAP language used when interfacing with the application.
Language
Root Organization The organization that is at the top of the organization hierarchy.
DataGarage Name of the DataGarage® database.
DataGarage Automatically Name of the DataGarage® database with which the application is
DataGarage Info Connection populated from interfacing.
cConfig™
SAP SAP database used by the application.
Connection
Tracing Trace Level Enables trace logging. By default, this setting is enabled.
Trace Log Retention Interval Number of days the logs are kept. The default value is 7 days.

To configure parameters:
1. Log into cHR™.
2. Select Parameters from Configuration on Switchboard.
3. Click Edit .
4. Update parameters as needed.
5. Click Save .

Page 39 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Configure Information Types

Configure the SAP information type supported in
cHR™. A standard set of information types is delivered
with cHR™; however, additional types can be
configured to meet the client’s needs.
To configure Information Types:
1. Select Information Type from Configuration on
Switchboard.
2. Click Add on the Grid Toolbar.
3. Enter an SAP screen name in Information Type
field.
4. Select an SAP infotype table from SAP Table list Configure Information Types
box.
5. Click Save .

Configure Object Types

Configure the objects and associated information types supported in cHR™. Object types control which fields display and
can be updated in cHR™. A standard set of object types is delivered with cHR™; however, additional types can be
configured to meet the client’s needs.
To configure Object Types:
1. Select Object Type from Configuration on Switchboard.
2. Click Add on the Grid Toolbar.

Configure Object Types

3. Enter a sort value in Priority field to control how the object types are listed when adding objects to a request.
4. Select a type from Object Type list box.
Or
Click Insert to manually add an object type.
5. Click Organization Approval check box to signify if the Manager Review role is needed on a request.
NOTE: If the Organization Approval field is enabled, the Manager Review and the HR Review roles appear on the
Request (Role) page. If it is disabled, only the HR Review role appears on the Request (Role) page.
6. Click Save ; a warning message displays indicating an information type must be added.
7. Click Ok .
8. Click Information Type button.
Page 40 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

9. Click Add on the Grid Toolbar.

Add Information Types

10. Enter a sort value in Priority field.
11. Select a type from Information Type list box.
12. Click Active check box to make the information type available.
13. Click Save .
NOTE: The SAPTable field is automatically populated.
14. Click Table Fields button to configure the fields pulled from SAP.

Configure Table Fields

15. Enable or disable Page Update check box to determine whether or not data can be entered into the field.

Configure Related Object Types

When an object is created, it can be related to another object. The objects to which new objects are related must be
configured. A standard set of related object types is delivered with cHR™; however, additional types can be configured to
meet the client’s needs.
To configure related object types:
1. Select Related Object Type from Configuration on Switchboard.
2. Click Add on the Grid Toolbar.
3. Select an object from Type of related object list box.
4. Click Save .

Configure Allowed Relationships

Several HR object relationships are downloaded from SAP. Configure these relationships by activating those that will be
used in cHR™ and identify those that are required. A required relationship must be maintained when the object is created.
To configure allowed relationships:
1. Select Allowed Relationships from Configuration on Switchboard.
2. Locate a relationship.
3. Click Edit .
4. Enter a sort value in Priority field to rank how the relationship is sorted in the list view.
5. Click Active check box to make the relationship available in cHR™.
6. Click Required check box to make the relationship required in the request.
7. Click Save .
Page 41 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Configure Account Assignments

Account assignments provide a way to manage the organization structure.
Business Area
To add a business area:
1. Click Configuration on Switchboard.
2. Select Business Area from Account Assignment on Vertical View.
3. Click Add on the Grid Toolbar.
4. Select a value from Business Area list box.
5. Click Save .

Update Archive Tables

Archive tables, designed in the cHR™ database with an ‘rt’ prefix, are initially created with the completion of the first Archive
Request event on the Archive Request page. If there are any fields added to the ‘tt’ version of the table(s) after the first
Archive Request event, the same fields must also be added to the ‘rt’ version of the table(s).
The only archiving tables delivered with the application are rtRequest and rtRequestProcess. If customizations are made to
the ‘tt’ equivalent for either of these tables, delete the delivered table so it will be rebuilt via the Archive Request event.

Configure Message Center

The Message Center on the cHR™ Home page is delivered blank and should be configured with appropriate text as part of
implementation.
To configure the Message Center text:
1. Navigate to cHR™ Home page.
2. Click Add on the Grid Toolbar.
3. Click HTML Edit ; the Editor window displays.
4. Enter text.
5. Click Save to close the Editor window.
6. Click Save to save the new message.

Page 42 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

CatalogBuilder™
Run CatalogBuilder™ for all installed cApps™ to pull in SAP translations. Refer to the CatalogBuilder™ User Manual for
detailed information.

SAP
If a view contains records that include the language aliased to boaSAPLanguage, CranSoft® displays the data in the
language defined in the user’s login language. The boaSAPLanguage feature aids clients who intend to have multiple
languages logging into the cApps™. If language-specific configuration is not maintained in SAP, the user may experience
undesirable results.

cCust™ Implementations
For cCust™ implementations, perform the following steps for every supported language:
Maintain language-specific text for Country (LAND1) in T005T. If text is not maintained for all supported languages,
some pages will not render.
Maintain language-specific text for Account Group (KTOKD) in T077X. If text is not maintained for all supported
languages, Search capability is limited.
Maintain language-specific text for all list box fields used in the application. If a text value is not maintained for a
supported language, users logging in with that language cannot select/view values for the field.

cVend™ Implementations
For cVend™ implementations, perform the following steps for every supported language:
Maintain language-specific text for Country (LAND1) in T005T. If text is not maintained for all supported languages,
some pages will not render.
Maintain language-specific text for Account Group (KTOKK) in T077Y. If text is not maintained for all supported
languages, Search capability is limited.
Maintain language-specific text for all list box fields used in the application. If a text value is not maintained for a
supported language, users logging in with that language cannot select/view values for the field.

cMat™ Implementations
For cMat™ implementations, perform the following steps for every supported language:
Maintain language-specific text for Country (LAND1) in T005T. If text is not maintained for all supported languages,
some pages may not render.
Maintain language-specific text for Unit of Measures (MSEHI) in T006A. If text is not maintained for all supported
languages, some pages may not render.
Maintain language-specific texts for all list box fields used in the application. If a text value is not maintained for a
supported language, users logging in with that language cannot select/view values for the field.

cFICO™ Implementations
For cFICO™ implementations, perform the following steps for every supported language:
Maintain language-specific text for Country (LAND1) in T005T. If text is not maintained for all supported languages,
some pages will not render.

Page 43 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.
cApps™ Implementation Guide

Maintain language-specific text for Chart of Account Names in T004T. If text is not maintained for all supported
languages, Search capability is limited.
Maintain language-specific text for all list box fields used in the application. If a text value is not maintained for a
supported language, users logging in with that language cannot select/view values for the field.

Appendix A – Performance Enhancement Recommendations

The following are recommendations to increase performance when using the cApps™.
Avoid joining a view to the ztParam table to restrict the Instance, Client and/or Language fields. DataGarage tables for
cApps will only contain data for one SAP instance and client.
After running the initial download of DataGarage® tables for the cApps™, deactivate the following tables in
DataGarage®:
 DD02L
 DD02T
 DD03L
 DD03T
 DD04L
 DD04T
 DOKID
 DOKTL
 D020T
NOTE: Do not deactivate DD07T.

Last Updated: 2/16/2011 – V1

Page 44 of 44
This document contains confidential and proprietary information and is for the privileged use of the intended client only. Reproduction is prohibited unless
authorized by BackOffice Associates. CranSoft and cApps are trademarks or registered trademarks of BackOffice Associates, LLC. Copyright 2010©
BackOffice Associates, LLC.