Openbravo Issue Tracking System - Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0031147ModulesService Contract Managementpublic2015-10-14 10:282015-10-14 13:35
Reporterngarcia 
Assigned ToTriage Omni OMS 
PriorityhighSeverityminorReproducibilityalways
StatusclosedResolutioninvalid 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Regression date
Regression introduced by commit
Regression level
Review Assigned Tovmromanos
Support ticket
OBNetwork customer
Regression introduced in release
Summary0031147: Search Key of Contracts is not automatically filled although you define a Document Sequence
DescriptionSearch Key of Contracts is not automatically filled although you define a Document Sequence
Steps To ReproduceAs group admin role:
   Create a Document Sequence for F&B España, S.A.
   Set its name as Contract
   Auto Numbering = 'Y'
   Create a new contract and check the Search Key is not filled automatically as it is explained in the documentation:
      http://wiki.openbravo.com/wiki/Service_Contracts_Management#Contract_Header [^]
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Filesxml OBTHC_SEQUENCE_NEXT.xml (1,635) 2015-10-14 13:33
https://issues.openbravo.com/file_download.php?file_id=8567&type=bug
Issue History
Date ModifiedUsernameFieldChange
2015-10-14 10:28ngarciaNew Issue
2015-10-14 10:28ngarciaAssigned To => Triage Finance
2015-10-14 10:28ngarciaIssue Monitored: networkb
2015-10-14 13:33vmromanosFile Added: OBTHC_SEQUENCE_NEXT.xml
2015-10-14 13:35vmromanosReview Assigned To => vmromanos
2015-10-14 13:35vmromanosNote Added: 0081007
2015-10-14 13:35vmromanosStatusnew => closed
2015-10-14 13:35vmromanosResolutionopen => invalid

Notes
(0081007)
vmromanos   
2015-10-14 13:35   
This is a feature that it's not included in the Service Contract Management (it was included as a customization in some coworking environments)

However it can be easily developed as a customization:
1. Create a customer template where we can export the changes
2. Modify the application dictionary. Table:C_Project, Column=DEFAULTVALUE.
Add the following defaultvalue (replace the OBTHC by the custom module db prefix):
@SQL=SELECT '<' || OBTHC_SEQUENCE_NEXT('Contract', '@AD_Org_ID@', 'N') || '>' from dual
3. Create a new function similar to the one attached (replace the OBTHC by the custom module db prefix)
4. The configuration is the one explained in the steps to reproduce:
 Create a Document Sequence for the right organization
 Set its name as Contract
 Auto Numbering = 'Y'