Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML KM-Dim7: Return Item - 2374 Error: Originator : "NAME" requires at least one of the following roles at Design Part PART_NAME : (ROLE NAME), Please inform the PRODUCT_MANAGER.
KM-Dim7: Return Item - 2374 Error: Originator : "NAME" requires at least one of the following roles at Design Part PART_NAME : (ROLE NAME), Please inform the PRODUCT_MANAGER.
CMS-XML KM-Dim9: Should a developer that is assigned to a specific workset be able to create a baseline? Getting error Create Baseline: 2374-Error Originator: 'User' requires at least one of the following roles at Design Part (DEVELOPER, BUILD MANAGER)...
KM-Dim9: Should a developer that is assigned to a specific workset be able to create a baseline? Getting error Create Baseline: 2374-Error Originator : 'User' requires at least one of the following roles at Design Part (DEVELOPER, BUILD MANAGER)...
CMS-XML KM-Dim9: Create Baseline: 2374-Error: '' requires at least one of the following roles at the design part : (). Please inform the Product-Manager. Assign $ORIGINATOR Role to the Create Document Status
KM-Dim9: Create Baseline: 2374-Error: '' requires at least one of the following roles at the design part : (). Please inform the Product-Manager. Assign $ ORIGINATOR Role to the Create Document Status
CMS-XML KM-Dim10: Delete Item - COR0005378E Error: You do not have the role to delete Item
User has the delete item privilege but the item type LifeCycle(LC) only has $ Originator role. It appeared that only the user that generated the item has the role for the first lifecycle transition.
CMS-XML KM-Dim9: Error: 1342 The leader role constraint is violated for role $AUTHOR....when creating a change document
Either one role MUST be assigned at creation time in the lifecycle of a change document - and must be of a type Leader (eg - $ ORIGINATOR ) or any other role/s assigned at creation time in the lifecycle of a change document MUST all be of type Leader.
CMS-XML KM-Dim7: with PM Copy Rules.
Display in this Role Section: What section the attribute is displayed e.g. if $ ORIGINATOR then it will be displayed when the change document is created.
CMS-XML KM-Dim9: Action item - 2289- Error: item < item name> is not pending for you
User can only action an item from the first state in the lifecycle if he/she created it , or he/she is Product Manager or the item has already been down the lifecycle and back again to the first state. This is expected behavior for Dimensions where originators can action an item from the initial lifecycle state
CMS-XML KM-Dim7: Error: "Value for DOC_SEQ must be numeric" received when importing change document
$CURRENT_STATUS CLOSED $ ORIGINATOR Harry Putman $CREATE_DATE 16-APR-1999 16:16:16
CMS-XML KM-Dim7: Error: cannot include system attribute ( PCMS_CHDOC_DETAIL_DESC) in any role section
Click on the pull-down arrow and select PCMS_CHDOC_DETAIL_DESC. Select the $ Originator role. Deselect the 'Display in the Role Section Button'.
CMS-XML DimCM2009R2: SQL-1438(101015810) ORA-01438: value larger than specified precision allowed for this column
This was line 2 of the export file as mentioned in the message above: insert into product catalogue (OBJ_UID, PRODUCT_ID, VARIANT, REVISION, STATUS, ORIGINATOR , USER_NAME, DESCRIPTION, CREATE_DATE, UPDATE_DATE, LOCKED, TYPE_UID , LC_SEQ
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs