Project and Portfolio Management Practitioners Forum
cancel

Error in date forman using KSC_create proyect from a request

SOLVED
Go to solution
Highlighted
mvillalobos
Super Contributor.

Error in date forman using KSC_create proyect from a request

Hello

I am trying to use the execution step ksc_create_project to create a new proyect from a request.

The project is created, but the dates of start and finish fail and the project does not work.

the call is:

ksc_create_project PROJECT_NAME="proyecto creado desde una solicitud" REQUEST_ID="30663" REGION_ID="100021" FINISH_DATE="January 2014" START_DATE="December 2013" PROJECT_TYPE_NAME="Enterprise" PROJECT_MANAGER="100081"

Thank you
9 REPLIES
Edtroleis
Super Contributor.
Solution

Re: Error in date forman using KSC_create proyect from a request

Check the points:
- to create a project from a request (demand) you need:
- region_id (KNTA_REGION)
- start_date (KNTA_PLAN_START_DATE)
- finish_date (KNTA_PLAN_FINISH_DATE)
- project_name (KNTA_PROJECT_NAME)
- project_manager (KNTA_PROJECT_MANAGER)
- project_type_name (KNTA_PROJECT_TYPE)
- if your demand (request) has 'PFM-Proposal' field group enabled it's necessary only fill the specific fields, otherwise, you must set manually in the command ksc_create_project

- check the tokens and if you get START_DATE and FINISH_DATE correctly.
mvillalobos
Super Contributor.

Re: Error in date forman using KSC_create proyect from a request

Thank you very much

Those tables are not in my database.
I do not know if in diferent versions of PPM those tables are called in a diferent way

The KNTA_ Tables:

KNTA_ACCESS_GRANTS_LOC
KNTA_ACCESS_GRANTS_NLS
KNTA_ACCESS_SECURITY
KNTA_ACCESS_SECURITY_HIST
KNTA_APPLET_KEYS
KNTA_APP_SERVER_DETAILS
KNTA_APP_SERVER_MODE
KNTA_APP_SERVER_PROPERTIES
KNTA_ARCHIVES
KNTA_COMMANDS
KNTA_COMMAND_STEPS
KNTA_DEBUG_MESSAGES
KNTA_DEFAULT_HELP_CONTENTS
KNTA_DOCUMENTS
KNTA_ENTITIES_LOC
KNTA_ENTITIES_NLS
KNTA_ENTITY_GROUPS_LOC
KNTA_ENTITY_GROUPS_NLS
KNTA_ENTITY_GROUP_MEMBERS
KNTA_ENTITY_RESTRICTIONS
KNTA_ENTITY_SECURITY
KNTA_ENTITY_TABLES
KNTA_ENTITY_TOKENS_LOC
KNTA_ENTITY_TOKENS_NLS
KNTA_EXCEPTIONS
KNTA_EXCEPTION_RULES_LOC
KNTA_EXCEPTION_RULES_NLS
KNTA_EXC_RULE_TYPES_LOC
KNTA_EXC_RULE_TYPES_NLS
KNTA_EXTERNAL_SYNCH
KNTA_FIELD_CHANGE_NOTES
KNTA_FIELD_FILTERS
KNTA_FIELD_GROUPS_LOC
KNTA_FIELD_GROUPS_NLS
KNTA_FIELD_SECURITY
KNTA_HELP_CONTENTS_LOC
KNTA_HELP_CONTENTS_NLS
KNTA_I18N_RESOURCES_LOC
KNTA_I18N_RESOURCES_NLS
KNTA_INTERFACE_ERRORS
KNTA_INTERRUPTED_EXECUTIONS
KNTA_LANGUAGES
KNTA_LOCKED_USERS_TEMP
KNTA_LOGON_ATTEMPTS
KNTA_LOOKUPS_LOC
KNTA_LOOKUPS_NLS
KNTA_MESSAGES_LOC
KNTA_MESSAGES_NLS
KNTA_MESSAGE_TYPES_LOC
KNTA_MESSAGE_TYPES_NLS
KNTA_NOTE_ENTRIES
KNTA_NOTIFICATIONS_LOC
KNTA_NOTIFICATIONS_NLS
KNTA_NOTIFICATIONS_TEMP
KNTA_NOTIFICATION_COLUMNS
KNTA_NOTIFICATION_RECIPIENTS
KNTA_NOTIFICATION_TYPES
KNTA_NOTIF_INTERVALS_LOC
KNTA_NOTIF_INTERVALS_NLS
KNTA_NOTIF_TXN_COLUMNS
KNTA_NOTIF_TXN_DETAILS
KNTA_NOTIF_TXN_PARENTS
KNTA_NOTIF_TXN_RECIPIENTS
KNTA_NOTIF_TYPE_MESSAGES
KNTA_OPENAPI_TXN_AUDIT
KNTA_PAGES_LOC
KNTA_PAGES_NLS
KNTA_PAGE_PORTLET_TYPES
KNTA_PARAMETER_SETS_LOC
KNTA_PARAMETER_SETS_NLS
KNTA_PARAMETER_SET_CONTEXTS
KNTA_PARAM_RULES
KNTA_PARAM_RULE_DEPENDENCIES
KNTA_PARAM_RULE_RESULTS
KNTA_PARAM_SET_FIELDS_LOC
KNTA_PARAM_SET_FIELDS_NLS
KNTA_PARAM_SET_FLD_SETUPS
KNTA_PASSWORD_CHANGES
KNTA_PENDING_API_CHANGES
KNTA_PENDING_EXCEPTIONS
KNTA_PENDING_FLS_DENORM
KNTA_PENDING_REFERENCES
KNTA_PENDING_ROLLUPS
KNTA_PERIOD_TYPES_LOC
KNTA_PERIOD_TYPES_NLS
KNTA_PERSONALIZATION_VALUES
KNTA_PORTLETS
KNTA_PORTLET_COLUMNS
KNTA_PORTLET_QUERIES
KNTA_PORTLET_SQL_PARAMETERS
KNTA_PORTLET_TYPES
KNTA_PORTLET_TYPES_BACKUP
KNTA_PORTLET_TYPE_COLUMNS
KNTA_PORTLET_TYPE_FILTERS
KNTA_PORTLET_TYPE_SECURITY
KNTA_PORTLET_TYPE_WS_INFO
KNTA_PREPARED_COMMANDS
KNTA_PREPARED_COMMAND_STEPS
KNTA_PRODUCTS_LOC
KNTA_PRODUCTS_NLS
KNTA_REFERENCES
KNTA_REFRESH_GROUPS
KNTA_REFRESH_LINES
KNTA_REFRESH_LINE_DETAILS
KNTA_REF_RELATIONSHIPS_LOC
KNTA_REF_RELATIONSHIPS_NLS
KNTA_REGIONS_LOC
KNTA_REGIONS_NLS
KNTA_REPORT_NOTIF_OUTPUT
KNTA_REPORT_OUTPUT
KNTA_REPORT_SUBMISSIONS
KNTA_REPORT_TYPES_LOC
KNTA_REPORT_TYPES_NLS
KNTA_RESOLVED_SEC_TOKENS
KNTA_RESULT_COLUMNS
KNTA_SAVED_SEARCHES
KNTA_SAVED_SEARCH_FILTERS
KNTA_SAVED_SEARCH_TYPES
KNTA_SCHEDULED_TASKS
KNTA_SCHEDULED_TASK_RECUR
KNTA_SCREENS_LOC
KNTA_SCREENS_NLS
KNTA_SEARCH_CATEGORIES
KNTA_SECTIONS_LOC
KNTA_SECTIONS_NLS
KNTA_SECTION_LAYOUTS
KNTA_SECURITY_GROUPS_LOC
KNTA_SECURITY_GROUPS_NLS
KNTA_SERVER_PARAMETERS_LOC
KNTA_SERVER_PARAMETERS_NLS
KNTA_SERVER_PARAM_DEF_LOC
KNTA_SERVER_PARAM_DEF_NLS
KNTA_SERVER_RESTARTS
KNTA_SERVICES_LOC
KNTA_SERVICES_NLS
KNTA_SHARED_LOCKS
KNTA_SPECIAL_CMD_PARAMS
KNTA_SPECIAL_COMMAND_TYPES
KNTA_STORED_QUERIES
KNTA_STORED_QUERY_DETAILS
KNTA_UCMDB_CI_ENTRIES
KNTA_UCMDB_CI_SETS
KNTA_UPGRADE_RECORDS
KNTA_USERS
KNTA_USERS_INT
KNTA_USER_MENU_STATES
KNTA_USER_PAGE_TABS
KNTA_USER_PRODUCTS
KNTA_USER_PROFILES
KNTA_USER_REGIONAL_SETTINGS
KNTA_USER_SECTION_STATES
KNTA_USER_SECURITY
KNTA_USER_SECURITY_HIST
KNTA_USER_SECURITY_INT
KNTA_USER_SESSIONS
KNTA_VALIDATIONS_LOC
KNTA_VALIDATIONS_NLS
KNTA_VALIDATION_FILTERS
KNTA_VALIDATION_PROFILES_LOC
KNTA_VALIDATION_PROFILES_NLS
KNTA_VALID_SQL_HEADERS_LOC
KNTA_VALID_SQL_HEADERS_NLS
KNTA_VERSION_HISTORY
KNTA_WEBSESSION_KEYS
Edtroleis
Super Contributor.

Re: Error in date forman using KSC_create proyect from a request

Please, explain me how is the request configured? Do you enabled 'PFM-Proposal' field group?
mvillalobos
Super Contributor.

Re: Error in date forman using KSC_create proyect from a request

Hello

The request is a normal request, i am not using tokens only the text:

ksc_create_project PROJECT_NAME="proyecto creado desde una solicitud" REQUEST_ID="30663" REGION_ID="100021" FINISH_DATE="January 2014" START_DATE="December 2013" PROJECT_TYPE_NAME="Enterprise" PROJECT_MANAGER="100081"

I am using it in a 2 step workflow to test the ksc_create_project call.

The PFM proposal is disabled.

Thank you
mvillalobos
Super Contributor.

Re: Error in date forman using KSC_create proyect from a request

If I create a project by the normal way (Create / create proyect..)

In the BBDD PPMUSER.PM_PROJECTS appears:

PROJECT_ID 30100
VERSION 2
ROLLUP_ID 30100
PROJECT_NAME hola hola
DESCRIPTION {null}
ASSOCIATED_MSP_PROJECT {null}
PROJECT_MANAGER {null}
START_DATE_PERIOD 30934
FINISH_DATE_PERIOD 30986
REGION_ID 100001
PROJECT_TYPE_ID 30160
PFM_REQUEST_ID 30676
DISPLAY_STATUS Sin enviar
STATUS 0
PROJECT_ACCESS_ID 30180
PROJECT_COST_ACCESS_ID 30181
CREATED_BY 1
CREATION_DATE 2011-03-17 13:05:43
LAST_UPDATED_BY 1
LAST_UPDATE_DATE 2011-03-17 13:05:44




Where does the start_date_ID and Finish_date_id comes from?

Thank you


Edtroleis
Super Contributor.

Re: Error in date forman using KSC_create proyect from a request

ksc_create_project
PROJECT_NAME="Project name"
REQUEST_ID="Request's id"
REGION_ID="region id"
FINISH_DATE="id finish_date"
START_DATE="id start_date"
PROJECT_TYPE_NAME="Project Type Name"
PROJECT_MANAGER="Project manager's id"

Put the id in the START_DATE and FINISH_DATE
Edtroleis
Super Contributor.

Re: Error in date forman using KSC_create proyect from a request

They come from 'Planned Start Period' and 'Planned End Period' field
mvillalobos
Super Contributor.

Re: Error in date forman using KSC_create proyect from a request

Hello

Thank you very much.

I have used the "PPM_FISCAL_PERIODS_NLS" . "START_DATE" & "END_DATE" and it worked :)
mvillalobos
Super Contributor.

Re: Error in date forman using KSC_create proyect from a request

It works properly