...

Trouble Shooting to Importing Structures into Controller using Microsoft SQL

by user

on
Category: Documents
6

views

Report

Comments

Transcript

Trouble Shooting to Importing Structures into Controller using Microsoft SQL
Guideline
Trouble Shooting to Importing
Structures into Controller using
Microsoft SQL
Product(s): IBM Cognos Controller 8.3 and higher
Area of Interest: Financial Management
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
2
Copyright
Copyright © 2008 Cognos ULC (formerly Cognos Incorporated). Cognos ULC
is an IBM Company. While every attempt has been made to ensure that the
information in this document is accurate and complete, some typographical
errors or technical inaccuracies may exist. Cognos does not accept
responsibility for any kind of loss resulting from the use of information
contained in this document. This document shows the publication date. The
information contained in this document is subject to change without notice.
Any improvements or changes to the information contained in this document
will be documented in subsequent editions. This document contains
proprietary information of Cognos. All rights are reserved. No part of this
document may be copied, photocopied, reproduced, stored in a retrieval
system, transmitted in any form or by any means, or translated into another
language without the prior written consent of Cognos. Cognos and the
Cognos logo are trademarks of Cognos ULC (formerly Cognos Incorporated)
in the United States and/or other countries. IBM and the IBM logo are
trademarks of International Business Machines Corporation in the United
States, or other countries, or both. All other names are trademarks or
registered trademarks of their respective companies. Information about
Cognos products can be found at www.cognos.com
This document is maintained by the Best Practices, Product and Technology
team. You can send comments, suggestions, and additions to
[email protected] .
IBM Cognos Proprietary Information
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
3
Contents
1
INTRODUCTION ............................................................................................ 4
1.1
1.2
1.3
PURPOSE ............................................................................................................4
APPLICABILITY .....................................................................................................4
EXCLUSIONS AND EXCEPTIONS ..................................................................................4
2
TROUBLE SHOOTING – SOURCE FILES ......................................................... 5
2.1
2.2
2.3
2.4
2.5
STRUCTURE OF THE FIELDS ......................................................................................5
COMPANY STRUCTURES ...........................................................................................5
ACCOUNT STRUCTURES ..........................................................................................7
DIMENSIONS...................................................................................................... 11
CURRENCY RATES ............................................................................................... 12
3
TROUBLE SHOOTING – SIGNON ................................................................. 13
3.1
USER SIGN-ON ................................................................................................... 13
4
TROUBLE SHOOTING – IMPORTING THE STRUCTURES ............................. 14
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
MAPPING .......................................................................................................... 14
MAPPING – DIMENSIONS ERRORS ............................................................................. 15
MAPPING – DTS PACKAGE ..................................................................................... 17
BATCH ID – ERROR CODE 1060 .............................................................................. 20
DUPLICATE DATA IN THE STAGING TABLE .................................................................... 21
RESCHEDULING IMPORTING OF STRUCTURES ................................................................ 21
USP_TRIGGERIMPORTBATCHJOBS - ORACLE...................................................... 22
PARAMETERS FOR USP_TRIGGERIMPORT BATCH ............................................................ 22
IBM Cognos Proprietary Information
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
1 Introduction
1.1
Purpose
This document will provides some information around trouble shooting the
importing of structures into Controller.
1.2
Applicability
Controller 8.2 and higher.
1.3
Exclusions and Exceptions
Not Applicable
IBM Cognos Proprietary Information
4
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
5
2 Trouble Shooting – Source files
2.1
Structure of the fields
Controller allows you to import structures into controller. However, you need to
be aware of the field requires, i.e. character type and size for each field. Plus,
there are also some mandatory fields that must be part of the data load.
2.2
Company Structures
Enclosed is information around the field properties for loading company
structures into Controller:
Company Structure
FIELD NAME
MANDATORY
FIELD
DESCRIPTION
CODE
Yes
Company code
NAME_GROUP
Yes
Company name Group Language
NAME_LOCAL
No
Company name Local Language
SHORTNAME_GROUP
Yes
Company Short
Name - Group
Language
SHORTNAME_LOCAL
No
Company Short
Name - Local
Language
LOCAL_CURRENCY
Yes
Local currency
assigned to
company
CO_TYPE
Yes
Company Type
(Group or
Subsidiary or Group
Adjustment
Company)
CONV_METHOD
Yes
Conversion Method
IBM Cognos Proprietary Information
ALLOWED
VALUE /
OPTIONS
FOR FIELD
Alphanumeric
code with a
maximum of 6
characters.
Alphanumeric
code with a
maximum of 50
characters.
Alphanumeric
code with a
maximum of 50
characters.
Alphanumeric
code with a
maximum of 9
characters.
Alphanumeric
code with a
maximum of 9
characters.
Alphanumeric
code with a
maximum of 3
characters
Acceptable
values are K, D
and B. Where
K=Group,
D=Subsidiary
and B=Group
Adjustment
Company.
Acceptable
values are 1 and
2. 1=Current
Method and
2=monetary/nonmonetary
method.
DEFAULT
VALUE IF FIELD
IS NOT
DEFINED IN
IMPORT
SPECIFICATION
No default value as
field is a mandatory
field
No default value as
field is a mandatory
field
No default value as
field is a mandatory
field
No default value as
field is a mandatory
field
No default value as
field is a mandatory
field
Default value = 1
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
The actual Staging table in Controller is what you will need to match correctly – see
below table:
Staging Table Name
Controller Name
Mandatory
ST_CODE
CODE
YES
ST_CO_TYPE
CO_TYPE
YES
ST_CONV_METHOD
CONV_METHOD
YES
ST_NAME_LOCAL
NAME_LOCAL
NO
ST_NAME_GROUP
NAME_GROUP
YES
ST_SHORTNAME_LOCAL
SHORTNAME_LOCAL
NO
ST_SHORTNAME_GROUP
SHORTNAME_GROUP
YES
ST_FREE1
ST_FREE2
ST_FREE3
ST_FREE4
ST_FREE5
IBM Cognos Proprietary Information
6
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
2.3
7
Account Structures
Enclosed is information around the field properties for loading account
structures into Controller:
Account Structure
FIELD NAME
MANDATORY
FIELD
DESCRIPTION
CODE
Yes
Account code
G_NAME
Yes
Account Name - Group
Language
L_NAME
No
Account Name - Local
Language
G_SHORTNAME
Yes
Account Shortname Group Language
L_SHORTNAME
No
Account Shortname Local Language
ACCT_DESC_GROUP
No
ACCT_DESC_LOCAL
No
LEV_EXTDIM1
No
Account Description
(online accounting
manual) - Group
Language
Account Description
(online accounting
manual) - Local
Language
Extended Dimension 1
Level to be used for a
specific account
LEV_EXTDIM2
No
LEV_EXTDIM3
ALLOWED
VALUE /
OPTIONS FOR
FIELD
DEFAULT
VALUE IF FIELD
IS NOT DEFINED
IN IMPORT
SPECIFICATION
Alphanumeric code
with a maximum of 13
characters.Valid
characters are A-Z,,_,0-9.
Alphanumeric code
with a maximum of 50
characters.
Alphanumeric code
with a maximum of 50
characters.
Alphanumeric code
with a maximum of 20
characters.
Alphanumeric code
with a maximum of 20
characters.
Alphanumeric code
with a maximum of
2000 characters.
No default value as
field is a mandatory
field
Alphanumeric code
with a maximum of
2000 characters.
Default value = ' '
integers 0,1,2,3,4,5,6
are the only acceptable
values for this field.
Default value = 0
Extended Dimension 2
Level to be used for a
specific account
integers 0,1,2,3,4,5,6
are the only acceptable
values for this field.
Default value = 0
No
Extended Dimension 3
Level to be used for a
specific account
integers 0,1,2,3,4,5,6
are the only acceptable
values for this field.
Default value = 0
LEV_EXTDIM4
No
Extended Dimension 4
Level to be used for a
specific account
integers 0,1,2,3,4,5,6
are the only acceptable
values for this field.
Default value = 0
SIGN_CHANGE
No
Acceptable values are
1 and -1.
Default value = 1
ACCT_TYPE
No
This field should be
marked if a specific
account should reverse
the sign convention
defined in the Reconcile
tab of the General
Configuration for this
account type
Account Type
Acceptable characters
are A,L,I,C,E,R,S,T,U.
Default value = A
IBM Cognos Proprietary Information
No default value as
field is a mandatory
field
Default value = ' '
No default value as
field is a mandatory
field
Default value = ' '
Default value = ' '
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
8
DECIMALS
No
Number of decimals to
be set for R,S,T,U
account types
integers 0,1,2,3,4,5,6
are the only acceptable
values for this field.
Default value = 0
CONSOLIDATE
No
Field which identifies if a
specific account should
be consolidated
Acceptable values are
T and F.
Default value = T
IC_CODE
No
This field indicates if
intercompany
information is required to
be entered on a specific
account, and if so, define
how information should
be collected.
Default value = ' '
SHARES
No
This field indicates if the
investment register
should be used for a
specific account, and if
so, how it should be
enabled.
COMMENTS
No
Allow comments to be
entered for a specific
account
Acceptable characters
are I, J, M, A or ' '. I =
Intercompany without
transaction currency. J
= Intercompany with
transaction currency. M
= Intercompany with
Margin %. A =
Acquisition
Calculations. ' '
represents the default
value and implies that
no intercompany
information will be
collected for a specific
account.
Acceptable characters
are I, E or ' '. I =
Investments in Group
Companies, E =
Investments in External
Companies and ' '
means the investment
register is not to be
used the a specific
account.
Acceptable values are
T, F and M.
SIGN_SUM1
No
Value entered here
determines whether an
account is required for
ACCT_SUM1 and if so
what sign the value on
that account should be
added to the
ACCT_SUM1
Acceptable values are
0, 1 and -1.
Default value = 0
ACCT_SUM1
No
Summation account that
a specific account
should be summed to
either negatively or
positively according to
SIGN_SUM1
Default = ' '
SIGN_SUM2
No
Value entered here
determines whether an
account is required for
ACCT_SUM2 and if so
what sign the value on
that account should be
added to the
ACCT_SUM2
Any valid Frango
Controller Account
code or valid account
code defined during the
import of external
structures. Valid
characters are A-Z,,_,0-9.
Acceptable values are
0, 1 and -1.
IBM Cognos Proprietary Information
Default value = ' '
Default value = F
Default value = 0
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
ACCT_SUM2
No
Summation account that
a specific account
should be summed to
either negatively or
positively according to
SIGN_SUM2
SIGN_SUM3
No
Value entered here
determines whether an
account is required for
ACCT_SUM3 and if so
what sign the value on
that account should be
added to the
ACCT_SUM3
ACCT_SUM3
No
Summation account that
a specific account
should be summed to
either negatively or
positively according to
SIGN_SUM3
RECONS_M1
No
Reconciliation codes and
references to other
codes determine how a
specific account will
handle opening balances
and reconciliation
between accounts. It is
also possible to copy
opening balances
RECONS_M1_ACCT
No
RECONS_M2
RECONS_M2_ACCT
9
Any valid Frango
Controller Account
code or valid account
code defined during the
import of external
structures. Valid
characters are A-Z,,_,0-9.
Acceptable values are
0, 1 and -1.
Default = ' '
Any valid Frango
Controller Account
code or valid account
code defined during the
import of external
structures. Valid
characters are A-Z,,_,0-9.
Valid codes are +, -, I,
J, K, L, ' '.
Default = ' '
This field is used when
the method entered for
RECONS_M1 requires
an account to be used
as a reference.
RECONS_M1 codes that
require this field to be
completed with account
information are +, -, I, J,
K and L.
Any valid Frango
Controller Account
code or valid account
code defined during the
import of external
structures. Valid
characters are A-Z,,_,0-9.
Default = ' '
No
Reconciliation codes and
references to other
codes determine how a
specific account will
handle opening balances
and reconciliation
between accounts. It is
also possible to copy
opening balances
Valid codes are +, -, I,
J, K, L, ' '.
Default = ' '
No
This field is used when
the method entered for
RECONS_M2 requires
an account to be used
as a reference.
RECONS_M2 codes that
require this field to be
completed with account
information are +, -, I, J,
K and L.
Any valid Frango
Controller Account
code or valid account
code defined during the
import of external
structures. Valid
characters are A-Z,,_,0-9.
Default = ' '
IBM Cognos Proprietary Information
Default value = 0
Default = ' '
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
CONV_M1
No
CONV_M1_ACCT
No
CONV_M2
No
CONV_M2_ACCT
No
ID_CODE
10
Determines the method
used when currency
conversion is run.
Currency conversion
codes are normally only
specified for detail
accounts
This field is used when
the method entered for
CONV_M1 requires an
account to be used as a
reference. CONV_M1
codes that require this
field to be completed
with account information
are I, C, O, P, A, A2 and
A3.
Valid codes are B, M,
D, N, E, F, G, K, L, I, C,
O, P, U, V, X, A, A2,
A3, ' '.
Default = ' '
Any valid Frango
Controller Account
code or valid account
code defined during the
import of external
structures. Valid
characters are A-Z,,_,0-9.
Default = ' '
Determines the method
used when currency
conversion is run.
Currency conversion
codes are normally only
specified for detail
accounts
This field is used when
the method entered for
CONV_M2 requires an
account to be used as a
reference. CONV_M2
codes that require this
field to be completed
with account information
are I, C, O, P, A, A2 and
A3.
Valid codes are B, M,
D, N, E, F, G, K, L, I, C,
O, P, U, V, X, A, A2,
A3, ' '.
Default = ' '
Any valid Frango
Controller Account
code or valid account
code defined during the
import of external
structures. Valid
characters are A-Z,,_,0-9.
Default = ' '
No
This field indicates if the
intercompany
transactions for a
specific account should
to be enabled to use
extended dimension 1.
This is used
Acceptable values are
T and F.
Default = F
NONREV_JOU
No
Indicates if a specific
account should be
copied according to the
alternative rules for nonreversing journals when
copying journals. This is
only applicable when the
same option is selected
in the General 3 tab of
the General
Configuration.
Acceptable values are
T and F.
Default = F
REV_JOU
No
Indicates if a specific
account should be
copied according to the
alternative rules for
reversing journals when
copying journals. This is
only applicable when the
same option is selected
in the General 3 tab of
the General
Configuration.
Acceptable values are
T and F.
Default = F
IBM Cognos Proprietary Information
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
CALC_ACCT
No
Indicates if a specific
account will be used as
a calculation account for
key ratios. This can only
be applied to statistical
accounts with account
types R, S, T and U.
Acceptable values are
0 and 1.
11
Default value = 0 or
blank
You will need to ensure your source data complies with field properties for the
characters.
2.4
Dimensions
Enclosed is information around the field properties for loading Dimensions into
Controller:
Dimension 1
FIELD NAME
MANDATORY
FIELD
DESCRIPTION
ALLOWED
VALUE /
OPTIONS FOR
FIELD
DEFAULT VALUE IF
FIELD IS NOT
DEFINED IN IMPORT
SPECIFICATION
CODE
Yes
Extended Dimension 1
code
Alphanumeric code
with a maximum of 4
characters.
No default value as field is a
mandatory field
OVCODE
Yes
Next higher level in
dimension structure for
CODE defined
Alphanumeric code
with a maximum of 4
characters.
No default value as field is a
mandatory field
NAME_GROUP
Yes
Extended Dimension 1
Name - Group Language
Alphanumeric code
with a maximum of
50 characters.
No default value as field is a
mandatory field
NAME_LOCAL
Yes
Extended Dimension 1
Name - Local Language
Alphanumeric code
with a maximum of
50 characters.
No default value as field is a
mandatory field
ACTIVE
No
This field indicates
whether the CODE
should be active or
inactive in the extended
dimension 1 structure
Acceptable values
are T or F
Default value = T
SORTORD
No
Sort order of extended
dimension 1 structure
Numeric values from
0 (zero) upwards
Default value = 0
ADJUST
No
This field defines if CODE
will be used as an
adjustment dimension.
Please note this only
applies to Extended
Dimension 1.
Acceptable values
are T or F
Default value = F
IBM Cognos Proprietary Information
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
•
•
•
2.5
12
The OVCODE can be blank, if there are no dimensionalities below the
first level.
It is important to ensure that you comply with the mandatory fields and
the code definition for each field.
You will also need to ensure that the dimensionalities are active in the
general configuration tab
Currency Rates
Enclosed is information around the field properties for loading Curency Rates
into Controller:
Currency Rates
ALLOWED
VALUE /
OPTIONS
FOR FIELD
DEFAULT VALUE
IF FIELD IS NOT
DEFINED IN
IMPORT
SPECIFICATION
FIELD NAME
MANDATORY
FIELD
CURRENCY_CODE
Yes
Currency Code
Alpha code
with maximum
of 3 characters.
No default value as field
is a mandatory field
CURRENCY_TYPE
Yes
Currency Type defines the
conversion code used for a
specific account. For example,
B for Closing Rate, M for
Period Average rate (YTD) or
D for Period Average Rate.
No default value as field
is a mandatory field
RATE
Yes
This field represents the
currency rate that will apply for
a specific period, actuality,
currency code and currency
type.
Acceptable
characters are
B,D,M where
B=Closing
Rate, D=Period
Average Rate
and M= Year
To Date
Average Rate.
Numeric value
with a
maximum of 5
digits and 6
decimals.
UNIT
Yes
The unit amount would
normally be collected from the
currency configuration. It is
possible to change the unit
value temporarily when
entering currency rates.
PERIOD
Yes
The period that a currency
code and currency type will
apply for.
IBM Cognos Proprietary Information
DESCRIPTION
No default value as field
is a mandatory field
No default value as field
is a mandatory field
Numeric value
with a
maximum of 4
characters to
define a period.
No default value as field
is a mandatory field
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
ACTUALITY
•
•
Yes
The actuality that a currency
code and currency type will
apply for.
Uppercase
alphanumeric
code with a
maximum of 2
characters.
Actuality code
must already
exist in the
Frango
Controller
database.
13
No default value as field
is a mandatory field
You can load in historical rates. The historical rates must be enter using the
historical rate register.
This is method can only be used for B-Closing rate, M-YTD average, D-period
average rates.
3 Trouble Shooting – Signon
3.1
User Sign-on
Controller allows you to import structures into controller. However, you need to
be sign-on in single mode
IBM Cognos Proprietary Information
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
•
No other users can be on the system, including excel.
4 Trouble Shooting – Importing the Structures
4.1
Mapping
a) Have you mapped all the mandatory fields to the appropriate staging
table? If you have not done this then you will get an error when you
validate the import specification (see below example)
IBM Cognos Proprietary Information
14
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
•
4.2
15
The error will show up before you are able to import. There is no
error log, because there is a problem specifically with the import
specification and its relationship with the staging table. There is a
conflict here – see below
a) You are saying the file is a staging table, but you are getting
an item from the file.
b) You should mapped the corresponding code to the correct
st_code.
Mapping – Dimensions errors
If you have not define the OVCODE properly, i.e. the next level and/or as
blank then you could get the following error:
IBM Cognos Proprietary Information
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
IBM Cognos Proprietary Information
16
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
4.3
17
Mapping – DTS Package
It is good suggestion to ensure that your names in the source file for each
column correspond to the name in staging table’s files, i.e.
-NB- It’s not mandatory to have the same names in the source and in table.
It is good practice to have the same name, but it’s possible to map other
source names to columns.
Here is an example of the staging table’s layout for the accounts
So, it is very important that your source file has the exact names as the
staging tables. If not, it could cause an error when you go to map the dts
package.
IBM Cognos Proprietary Information
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
IBM Cognos Proprietary Information
18
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
19
The process of mapping the source data base to the staging table is based on
the field names being correct. If this not correct then joins will not work and
you will get an error. However, it is possible to join any source name to the
destination column in the staging table. So, it is important to review the joins
to ensure that they are correct.
IBM Cognos Proprietary Information
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
4.4
20
Batch ID – error code 1060
No rows were updated in the staging table, possibly due to wrong imported
was sent in
Solution:
Delete the entries inside the BATCH_ID and re-run
Steps:
•
•
•
•
•
•
•
Before proceeding, backup the Controller data base
Launch Microsoft SQL and/or your ETL tool
Open Controller Data base
Open Controller Schema (user)
Locate the correct staging table (i.e. XSTAGEDIM1)
Right-click the staging table and choose view/edit contents
Notice there is a column called ‘BATCHID’
If the rows beneath this column are filled in (for example with ‘35’) then it
means that a BATCH_ID number has already been assigned. If you were to
delete the numbers inside this column, then the script would run.
-NB- The error message 1060 will occur when you don’t have a match
between ids in the staging table and pImpId.
IBM Cognos Proprietary Information
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
4.5
21
Duplicate data in the staging table
If you run the initial DTS package then you could get duplicate values
depending how you run the process. The best solution is to delete all values
in the staging tables to ensure there are not duplicate values – see below
information:
It is good practice to review the staging tables (xstage) information prior to
loading to ensure the information is complete.
4.6
Rescheduling importing of structures
You can not re-schedule batch jobs which correspond to an import of external
structures. Importing of structures can *only* occur during ‘single-user
mode’, using a special dedicated import specification. In this case, the user is
(erroneously) attempting to re-use an existing import specification for the
staging table structure import. In stead, you must have a new (dedicated)
import structures ‘staging table’ import specification.
Solution
Create a new (dedicated) import structures ‘staging table’ import
specification, and perform actions inside single-mode.
IBM Cognos Proprietary Information
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
4.7
22
USP_TRIGGERIMPORTBATCHJOBS - ORACLE
The consultant logs into Oracle 10G sever, launches ‘SQLPlus Worksheet’.
Consultant runs a command such as: execute
schemaname.usp_triggerimportbatchjobs (‘110’, ‘#ST_DATA’, ‘X’, ‘’, ‘ADM’,
’10.10.2007’) SQLPlus returns an error
ORA–06550: Line 1, Column 7:
PLS-00221: ‘USP_TRIGGERIMPORTBATCHJOBS’ is not a procedure or is
defined
ORA-06550: Line 1, column 7:
PL/SQL: Statement ignored
Solution
Execute the function ‘usp_triggerbatchjobs’ by using a script such as SQL:
Declare
xx number;
Begin
-- call the function
xx ;=schemaname.usp_triggerimportbatchjobs(‘110’, ‘ST_DATA’, ‘X’, ‘’, ‘ADM’,
1, to_date(‘2007-11-01’)); end;
Consider the following:
• 110 is the import id, the identical number for the data that should be
imported, you find this in the first column (st_id) of the table1 xstage
• #ST_DATA is the name of the import specification
• X refers to type being imported, i.e. D for data,
• ADM is the user ID with which the import is to be done
• 1 is for immediate import, 0 would be put the schedule on hold and
start in Controller.
• To_date must be today or a date in the future = the format might
differ ‘2007-11-01’ or ’20-May-2008’
4.8
Parameters for usp_triggerimport batch
You should check the parameter codes to ensure they have been properly
completed:
a) @pImpID nvarchar(30), -- Import ID
b) @pImpSpec varchar(12), -- Import spec name to be used.
c) @pImpSpecType varchar (1), -- import spec type (D=Data, A=Account,
R=Currency Rates, C=Company, 1=Dim1, 2=Dim2, 3=Dim4, 4=Dim4)
d) @pImpSpecParams nvarchar(255), --import spec params, (if the Import
Spec demands this)
IBM Cognos Proprietary Information
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
23
e) @pCtrlUser varchar(8), -- Controller user
f) @pSchedType int, --0=on hold, 1=Immediately, 2=OneTimeOnly
g) @pExecTime datatime – Data and time when the import should take
place.
It is important that you check to see that your import jobs has required fields
identified properly, if not then the following error codes could occur:
1050 – Only schedule type 0 is allowed when importing structures
1010 – Given import specification is not found/valid
1060 – No rows were updated in staging table, possibly wrong imported id
was sent in
IBM Cognos Proprietary Information
Trouble Shooting to Importing Structures into Controller using
Microsoft SQL
IBM Cognos Proprietary Information
24
Fly UP