Aurea CRM Commands and Parameters

Here is the list of Aurea CRM commands and parameters.

For information on the usage of command line parameters, see Aurea CRM Parameters in the CRM.core Administrator Guide.

mman.exe Parameters

-a

Executes the specified analysis:

mman.exe -u <User> -p <Password> -a "Revenue 2009"

-f

Loads the specified analysis format:

mman.exe -u <User> -p <Password> -f "Revenue 2009"

-s

Use this parameter to execute multiple analyses sequentially:

mman.exe -u <User> -p <Password> -s c:\windows\script.txt

Contents of the text file (ASCII, Unicode, UTF8):

-a "Revenue 2005"
-a "Revenue 2006"
-a "Revenue 2007"
-a "Revenue 2008"

mmco.exe Parameters

-k

Starts the input or output of a communication file, see Communication Steps.

mmco.exe -u com -p <Password> -k I,101,102,l -k o,101,102

The following options are available:

i: Input communication file
o: Output communication file
101,102 etc.: Numbers of the stations to communicate with. If no station numbers are specified, communication takes place for all stations for which a communication connection exists, see Defining Communication Connections.
You can also enter number ranges: mmco.exe -u com -p <Password> -k o ,10 -1000 outputs communication files for stations 10 to 1000.
l: Use this option to delete records marked as deleted automatically, without requiring the deletion to be confirmed manually, see Communicating Deleted Records. The number of days entered in the Delete Cycle in Days field in the Station info area is taken into account when deleting records.
```
mmco.exe -u com -p <Password> -k i,l
```
u: Output a data stock download, see Data Stock Download.
```
mmco.exe -u com -p <Password> -k o,101,u
```
Outputs a data stock download (-k o ,u) for station 101.

Use info area codes to output a data stock download for specific info areas, e.g. u :FI:KP:MA, see Partial Data Stock Download.
+: Inputs a data stock download.
```
mmco.exe -u com -p <Password> -k i,1,+
```
Inputs the data stock download (-k i ,+) generated on the main office (1).
r: Use this option to create a new data stock download for an existing station to reset the station, see Outputting a new Data Stock Download for an Existing Station.
```
mmco.exe -u com -p <Password> -k o,101,r
```
Outputs a new data stock download for station 101.
w: Use this option to output all catalog values. By default, only catalog values that have changed are output.
```
mmco.exe -u com -p <Password> -k o,101,w
```
Catalogs are output for station 101 (o ,101). All catalog values are output (w).
n: Use this option to prevent catalog values that are added on a branch office from being input on the catalog maintenance station.
```
mmco.exe -u com -p <Password> -k i,101,n
```
Data is input from station 101 (i ,101). No catalog changes are input (n), i.e. catalog values added or edited on the branch office. Exception: If a new or edited catalog value is used in a record on the branch office and this record is also communicated. In this case, the catalog value is input.
m: Use this option to execute an automatic communication process using a communication connection with the Execution set to "manual", see Defining Communication Connections.
```
mmco.exe -u com -k ein,101,m
```
Data is input from station 101 (i ,101). The communication connection defined as "manual" is used (m). Change control and manual match-up options are ignored. Combine this parameter with the parameter k to determine that the change control and manual match-up dialogs should be displayed.
k: Use this option to execute automatic communication with manual control.
```
mmco.exe -u com -k ein,101,m,k
```
Data is input from station 101 (i ,101). The communication connection defined as "manual" is used (m). Messages are output, changes can be verified manually and records can be matched up manually (k), see Communication with Change Control and Communication with Manual Match-up.
q: Use this option to suppress the license registration request. Use this option if you use the SU user for automatic communication. Otherwise the communication process is aborted.
```
mmco.exe -u com -p <Password> -k i,101,n
```
z: By default, the delta is determined (time stamp comparison) by writing all data to a temporary file, which prevents further access to the database. However, this requires free disk space equivalent to the size of the database.
Use this option to minimize the memory required by the communication process: the delta is determined by querying the database and written directly to the communication file. When using the z parameter, the disk space requirements are lower, however this can negatively impact on the performance of the communication process.
```
mmco.exe -u com -p <Password> -k o,1,z
```
A branch office outputs data for the main office (o ,1). The memory used by the communication process is minimized (z).
WriteRecTmp: By default, records are output in a compressed format. Use this option to output records in an uncompressed format.
```
mmco.exe -u com -p <Password> -k o,101,WriteRecTmp
```
D3DontCheck: Use this option to prevent the system from checking whether records entered in link fields are also output when outputting D3 links:
```
mmco.exe -u com -p <Password> -k o,101,D3DontCheck
```
b: This option (benchmark) is only for test purposes.

-c

Starts an external application after the communication process:

mmco.exe -u com -p <Password> -k i,l -k o -c x:\move_com_files.bat

Use the –c parameter a second time to specify a working directory for the application.

--oe

Use this parameter to suppress communication via e-mail, >> Communicating via E-mail on page 77. The input or output is started without the Mapi.dll file. This parameter takes precedence over the settings in the Communication info area.

For example, mmco.exe -u com -u com -p <Password> -k o,101,u --oe creates a data stock download for station 101. Communication does not take place via e-mail, irrespective of the settings entered in the communication connection.

-s

Use this parameter to execute multiple communication processes sequentially:

mmco.exe -u <User> -p <Password> -s c:\windows\script.txt

Contents of the text file (ASCII, Unicode, UTF8):

-k o,101,u
-k o,102,u
-k o,200,u

In this example, data stock downloads are created for multiple stations.

--DmMerge

Use this parameter to suppress the confirmation prompt when merging data models. The data models are merged, see Merging Data Models in the CRM.core Administrator Guide.

mmim.exe Parameters

Importing or exporting data using the command line requires:

An import or export format, see Defining an Import/Export format.
The external file containing the import data (at the location specified in the format), see Import File/Import Database.

Check the log files immediately after each automatic import. The log files are overwritten by the next import.

-e

Starts the Export module. If this parameter is not used, the Import module is started.

-f

Specifies the import or export format:

mmim.exe -u <User> -p <Password> -f "Import Companies"
mmim.exe -e -u <User> -p <Password> -f "Export FI/KP"

-d

Path and name of the import or export file. Used instead of the file entered in the format.

mmim.exe -u <User> -p <Password> -f "Import Companies" -d "c:\MyDocuments\companies_csv"

Note: Allowed max. length of path and name: 259 characters. If the string passed with -d exceeds this limit, mmim.exe is not started and a message is written to the log file.

-c

This parameter applies to export only. If the target export file exists, the file is not overwritten, but a new file is created. The files are numbered sequentially (*.0, *.1 etc.).

You can speed up the export process by selecting the Upd field in the Sort By field and starting the export with -c.

mmim.exe -e -u <User> -p <Password> -f "Export Companies" -c

-n YYYYMMDD

This parameter applies to export only. Records are only exported if they are entered on or after the specified date.

mmim.exe -e -u <User> -p <Password> -f "Export Companies" -c -n 20090815

-k

This parameter applies to import only. The import is executed using manual control, see Executing the Import.

mmim.exe -u <user> -p <Password> -f "Import Companies" -d c:\companies_csv -k

Note: The parameters -d, -k, -n and -c apply to the previous format specified with –f:

mmim.exe -e -u <User> -p <Password> -f "Export Companies" -n 20090815 \
-d c:\fi0815.csv -f "Export Activities" -n 20090901 -d c:\ma0901_csv

--lkz

This parameter applies to export only. Records marked as deleted are also exported (DelCd field enabled).

mmim.exe -e -u <User> -p <Password> -f "Export Companies" --lkz

-s

Use this parameter to execute multiple imports or exports sequentially:

mmim.exe -u <User> -p <Password> -s c:\windows\script.txt

Contents of the text file (ASCII, Unicode, UTF8):

-f IMP_FIKP
-f IMP_AK
-f "Import Activities"

If an error occurs during batch import, mmim.exe returns the following error codes:

525	Format not found
526	Format could not be loaded / format defect
502	No access to source file
504	No connection to source table or field(s) in the source table wrong
510	SQL error

--abortOnError

To cancel a batch import as soon as one of the imported files causes an error, use -- abortOnError together with -s.

--sqlwhere

Use this parameter to restrict the imported data using an SQL WHERE clause (in double quotes). This parameter can be used in conjunction with the following parameters:

-f
-s

If the Import table option is not enabled for the format specified the parameter is ignored and a message is written to the log file.

When using -- sqlwhere together with packet size, you need to specify the packet size in the command line as well.

mmim.exe -u <User> -p <Password> -f "Import Companies" --sqlwhere "WHERE PLZ=1040
/*packetSize=1000*/"

--transactional

Use this parameter to use transactions: Each row is imported within a database transaction. If one of the records in a row contains incorrect data, the entire row is rolled back, e.g. if the import of an offer for a company fails, the related company is not imported as well.

If user input is required during the import of a record, the transaction is aborted.

Note: When importing with transactions the Package processing option is not supported, see Info area properties.