|
| Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
| Lbodi_OUInstance | udd_ctxt_ouinstance | int(4) | No | The Organization unit at which user has logged in the system, and created the Library Details. | Yes |
| Lboddi_Document_No | udd_documentno | varchar(40) | No | A mandatory field. It is the unique identifying number to be entered by user, for identifying a particular document. Cannot be changed / modified later on. | Yes |
| Lboddi_Rev_No | udd_revisionno | varchar(40) | No | Some documents might have undergone revisions. The revision # of the current document being registered needs to be entered. Cannot be modified later. | Yes |
| Lboddi_Seq_No | udd_seqno | int(4) | No | Key Sequence No | Yes |
| Lboddi_Dist_Date | udd_date | varchar(15) | No | The date on which the document was distributed to the user is entered/modified here. And if list is being prepared for distribution, then date of distribution can be mentioned here. | No |
| Lboddi_User_Type | udd_designparamcode | varchar(5) | No | The "user type" of the member, to whom the document is to be distributed, is captured and displayed here. The combo is loaded with pre defined values: Library, Work center, Supplier, Customer, Employee, Others. For members not present in mapped Std. | No |
| Lboddi_User_Info | udd_suppliername | varchar(40) | Yes | Any info on member as provided in Std. Distribution list is fetched here. User can edit this information. For members not present in mapped Std. Distribution list, but entered directly here, user can enter User information for them. | No |
| Lboddi_User_Name | udd_hrusername | varchar(25) | Yes | The login user for the user info identified (as recorded in Std. Distribution member list), will be displayed here. User can enter a new member name, by launching Help on User Name page. | No |
| Lboddi_Emp_Code | udd_hrempcode | varchar(20) | Yes | The member name as recorded in Std. Distribution member list, will be displayed here. User can enter a new employee number, who is not a part of the mapped standard distribution list, by launching Help on Employee Number page. | No |
| Lboddi_Emp_OU | udd_ctxt_ouinstance | int(4) | Yes | Employee OUInstance | No |
| Lboddi_Dist_Type | udd_designparamcode | varchar(5) | Yes | The distribution type of the document for the concerned member is to be defaulted in the multiline. The combo is to be loaded with predefined values: Permanent, Returnable, and Returned. User can reset any of these values, for any of the members. And | No |
| Lboddi_Dist_Reason | udd_txt255 | varchar(255) | Yes | Distribution reason for each of the members populated in the multiline, or new members added here, is to be entered in this field. | No |
| Lboddi_No_of_Copies | udd_count | int(4) | No | Number of copies distributed to each of the member in the list, and to new members added, is to be entered here. | No |
| Lboddi_Media | udd_quickcodes | varchar(25) | No | The medium in which the document was distributed to each of the member populated/added in multiline is entered here. The combo is loaded with different media types that are user defined in Maintain Quick codes activity. | No |
| Lboddi_Location | udd_organizationunit | varchar(40) | Yes | The location of document distribution is entered in this field. | No |
| Lboddi_Std_Issue_Dur | udd_count | int(4) | Yes | Standard Issue Duration (in days) | No |
| Lboddi_Ack_Status | udd_quickcodes | varchar(25) | Yes | Combo is to be loaded with pre defined values: Not Required, Pending and Required. The values mapped with each of the members in the Std. Distribution list will be defaulted here. User will select the status value for each the new user added here, an | No |
| Lboddi_Return_Date | udd_date | varchar(15) | Yes | The expected return date of the respective document for each of the members is recorded in this field. This is mandatory if the distribution type is "Returnable". | No |
| Lboddi_Codition | udd_designparamcode | varchar(5) | Yes | Combo is loaded with pre defined values: Usable, Discarded. User has to select one of these for all the documents lying with all the members, populated/added in the multiline. The value states whether a particular copy with the associated member is u | No |
| Lboddi_Phone | udd_communicationid | varchar(70) | Yes | Phone number of the member is fetched and displayed here. For new members added here, user has to enter their contact number. User can also update phone numbers of existing members. | No |
| Lboddi_Fax | udd_communicationid | varchar(70) | Yes | Fax number of the member is fetched and displayed here. For new members added here, user has to enter their fax number. User can also update phone numbers of existing members. | No |
| Lboddi_Email | udd_communicationid | varchar(70) | Yes | Email address of the member is fetched and displayed here. For new members added here, user has to enter their Email address. User can also update Email address of existing members. | No |
| Lboddi_Dist_Remarks | udd_text255 | varchar(255) | Yes | Any remark relevant to the document distribution to the respective person is entered here. | No |
| Lboddi_Ack_Datetime | _varchar_30 | varchar(30) | Yes | If the member has acknowledged receipt of the document, then the date of acknowledgement and time tobe captured here. | No |
| Lboddi_Ack_User_Status | udd_quickcodes | varchar(25) | Yes | This combo is a quick code to be loaded with various user defined values of Acknowledged Status, defined in Maintain Quick Codes | No |
| Lboddi_Ack_Remarks | udd_txt255 | varchar(255) | Yes | Remarks or comments given by each member with respect to the document can be captured in this field. | No |
| Lboddi_Ack_By | udd_hrempcode | varchar(20) | Yes | If a person has already acknowledged receipt of the document, then it should be fetched and displayed here. Else the person who has received the document, but not yet acknowledged, is to be entered here. If a person does not have login rights like Su | No |
| Lboddi_Reference | udd_txt150 | varchar(150) | Yes | The reference information, for the members in the multiline/new members added, is entered here. | No |
| Lboddi_Updated_By | udd_ctxt_user | varchar(30) | No | The last login-user, who has updated the information on this page, is displayed here. | No |
| Lboddi_Updated_Date | udd_date | varchar(15) | No | The last date, on which the distribution information for this document was updated, is displayed here. | No |
| Lboddi_Timestamp | udd_timestamp | int(4) | No | Timestamp | No | |
| Table Name : | Lbo_Lbodi_Document_Info |
| Comment : | This Table captures all information related to the document, classifies it under a user-defined category. Each of the document received in a library, can be provided a unique identifying reference as Document #. |
|
| Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
| Lbodi_OUInstance | udd_ctxt_ouinstance | int(4) | No | The Organization unit at which user has logged in the system, and created the Library Details. | Yes |
| Lbodi_Document_No | udd_documentno | varchar(40) | No | A mandatory field. It is the unique identifying number to be entered by user, for identifying a particular document. Cannot be changed / modified later on. | Yes |
| Lbodi_Rev_No | udd_revisionno | varchar(40) | No | Some documents might have undergone revisions. The revision # of the current document being registered needs to be entered. Cannot be modified later. | Yes |
| Lbodi_Library_No | udd_documentno | varchar(40) | No | The unique identifying reference allotted to the library.This is mandatory information. | No |
| Lbodi_Status | udd_designparamcode | varchar(5) | Yes | Pre Defined values here are: Fresh, Active, Inactive, Revised, and Obsolete. This field is used to set the status of document concerned. | No |
| Lbodi_Doc_Title | udd_txt150 | varchar(150) | No | A mandatory field. The title of the document or document name has to be entered here. | No |
| Lbodi_Doc_Type | udd_CM_DocType | varchar(30) | Yes | All Reference Document Type pages that are Active and have attribute "Maintained in Library?" flag set as "Yes" in Common Masters in Create Reference Document Type, will be loaded in combo here. Its a mandatory field | No |
| Lbodi_Doc_Cat | udd_quickcodes | varchar(25) | Yes | Quick Codes defined for Document Category Quick Code Type in "Active" status will be loaded. The values for this combo are defined in maintain quick codes activity. | No |
| Lbodi_Doc_Subject | udd_txt150 | varchar(150) | Yes | A brief note on the subject to which the document relates to. | No |
| Lbodi_Doc_Purpose | udd_quickcodes | varchar(25) | Yes | User defined quick codes will be loaded in this combo. Users can set/change the purpose of document here. | No |
| Lbodi_Doc_Nature | udd_quickcodes | varchar(25) | Yes | User defined quick codes to be loaded in this combo here. On screen launch the existing document nature value for the particular document will be loaded here. It can be changed, to some other values loaded in the combo. | No |
| Lbodi_Doc_Class | udd_quickcodes | varchar(25) | Yes | User defined quick codes to be loaded in this combo here. On screen launch the existing document class value for the particular document will be loaded here. It can be changed, to some other values loaded in the combo. | No |
| Lbodi_No_of_Copies | udd_count | int(4) | No | Number of copies received for each of the documents at the time of registration is entered here. | No |
| Lbodi_Usable_Copies | udd_count | int(4) | No | No of Usable Copies in the Library for the Document. | No |
| Lbodi_Discarded_Copies | udd_count | int(4) | No | The number of copies discarded for the document concerned will be displayed here. | No |
| Lbodi_Appl_Lvel | udd_designparamcode | varchar(5) | Yes | Provides user with facility to set applicability of the document. Applicability values loaded in combo are: Model, Aircraft, Part, Others. | No |
| Lbodi_Std_Dist_List | udd_documentno | varchar(40) | Yes | All the active distribution lists will be loaded in the combo here. User can set/change the distribution list to which he wants the document to be associated with. | No |
| Lbodi_Source_Typ | udd_quickcodes | varchar(25) | Yes | Provision for selecting the source of documents that are to be registered. Values loaded in combo are from the user defined Quick Codes in maintain Quick codes activity. | No |
| Lbodi_Doc_Ref_no | udd_documentno | varchar(40) | Yes | User enterable field for entering a reference number to the document being registered. | No |
| Lbodi_Ref_Doc_Typ | udd_designparamcode | varchar(5) | Yes | User can set a reference document type or change it. The combo will be loaded with the following Reference document types: Customer Order # Visit Package # Hangar Work Order # Work Scope # Technical Log # Engineering Order # Repair Order Others | No |
| Lbodi_Ref_Doc_Dtl | udd_documentno | varchar(40) | Yes | The details pertaining to selected reference document type can be entered/modified by the user in this field. This will not be validated with the respective documents | No |
| Lbodi_Oth_Keyword1 | udd_keyword | varchar(25) | Yes | Key word related to document. | No |
| Lbodi_Oth_Keyword2 | udd_keyword | varchar(25) | Yes | Keyword 2 | No |
| Lbodi_Oth_Keyword3 | udd_keyword | varchar(25) | Yes | Keyword 3 | No |
| Lbodi_Web_Ref | udd_txt150 | varchar(150) | Yes | Web reference, if entered during registering document, will be fetched here. Or else, user can enter/edit web reference in this column. | No |
| Lbodi_Remarks | udd_txt2000 | varchar(2000) | Yes | Document reference #, if entered during registering document, will be fetched here. It is any reference for the document # under consideration. | No |
| Lbodi_Oth_Filename | udd_filename | varchar(50) | Yes | Other Filename Reference. | No |
| Lbodi_Filename | udd_filename | varchar(50) | Yes | Path of files that are to be attached, or tagged against the document, should be entered here. | No |
| Lbodi_Created_By | udd_ctxt_user | varchar(30) | Yes | Name of the login user who created the library information. | No |
| Lbodi_Created_date | udd_date | varchar(15) | No | Date on which the library information is created. | No |
| Lbodi_Modified_By | udd_ctxt_user | varchar(30) | Yes | Name of the login user who is the last to modify respective library information. | No |
| Lbodi_Modified_Date | udd_date | varchar(15) | Yes | The last date on which the particular library information was modified. | No |
| Lbodi_Registered_By | udd_ctxt_user | varchar(30) | Yes | Name of the login user who registered the library information. | No |
| Lbodi_Registered_Date | udd_date | varchar(15) | Yes | The last date on which the particular library information was registered | No |
| Lbodi_Registered_At | udd_oucode | varchar(32) | Yes | The place/location on which the particular library information was registered | No |
| Lbodi_Revised_By | udd_ctxt_user | varchar(30) | Yes | Name of the login user who is the last to revised respective library information. | No |
| Lbodi_Revised_Date | udd_date | varchar(15) | Yes | The last date on which the particular library information was revised. | No |
| Lbodi_Timestamp | udd_timestamp | int(4) | No | Timestamp | No |
| LBODI_ARCHIVE | udd_designparamcode | varchar(5) | Yes | Archive | No |
| LBODI_REF_DOC_OU | udd_ctxt_ouinstance | int(4) | Yes | Reference document Ouinstance | No |
| Lbodi_ATA_No | udd_txt150 | varchar(150) | Yes | ATA number | No | |
| Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
| Lbodi_OUInstance | udd_ctxt_ouinstance | int(4) | No | The Organization unit at which user has logged in the system, and created the Library Details. | Yes |
| Lbodpc_Document_No | udd_documentno | varchar(40) | No | A mandatory field. It is the unique identifying number to be entered by user, for identifying a particular document. Cannot be changed / modified later on. | Yes |
| Lbodpc_Rev_No | udd_revisionno | varchar(40) | No | Some documents might have undergone revisions. The revision # of the current document being registered needs to be entered. Cannot be modified later. | Yes |
| Lbodpc_Seq_No | udd_seqno | int(4) | No | Key Sequence No | Yes |
| Lbodpc_Corr_Date | udd_date | varchar(15) | No | The date of correspondence is to be entered in this field. | No |
| Lbodpc_Corr_Cat | udd_flag2 | varchar(25) | No | The values of this combo are to be loaded with user defined quick codes, for "Corresponding Category" quick code type. | No |
| Lbodpc_Partner_Details | udd_itemdesc | varchar(150) | No | Details of partner, like name & contact information could be recorded here. | No |
| Lbodpc_Inchge_Remarks | udd_text255 | varchar(255) | Yes | Library In-charge remarks relating to the concerned partner could be entered/modified here. | No |
| Lbodpc_Partner_Remarks | udd_text255 | varchar(255) | Yes | Remarks given by respective partner could be entered/modified in this column. | No |
| Lbodpc_Corr_Status | udd_flag2 | varchar(25) | No | The values of this combo are to be loaded with user defined quick codes, for "Corresponding Status" quick code type. | No |
| Lbodpc_Reference | udd_txt150 | varchar(150) | Yes | Any reference for correspondence with the partner could be entered/modified here. | No |
| Lbodpc_Updated_By | udd_ctxt_user | varchar(30) | No | The login user name, who updated the corresponding partner details, is displayed here. | No |
| Lbodpc_Updated_Date | udd_date | varchar(15) | No | The system date, as on which, the Partner details were updated for the last time, is displayed here. | No |
| Lbodpc_Timestamp | udd_timestamp | int(4) | No | Timestamp | No | |
| Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
| Lbodi_OUInstance | udd_ctxt_ouinstance | int(4) | No | The Organization unit at which user has logged in the system, and created the Library Details. | Yes |
| Lbodpd_Document_No | udd_documentno | varchar(40) | No | A mandatory field. It is the unique identifying number to be entered by user, for identifying a particular document. Cannot be changed / modified later on. | Yes |
| Lbodpd_Rev_No | udd_revisionno | varchar(40) | No | Some documents might have undergone revisions. The revision # of the current document being registered needs to be entered. Cannot be modified later. | Yes |
| Lbodi_Publisher | udd_vendorcode | varchar(45) | Yes | Publisher - who has printed or created the concerned document. | No |
| Lbodi_Publish_date | udd_date | varchar(15) | Yes | The date of publication of document has to be entered here. | No |
| Lbodi_Publish_Ref | udd_txt2000 | varchar(2000) | Yes | The reference details of the publisher could be entered / modified in this field. | No |
| Lbodi_Cont_Details | udd_txt2000 | varchar(2000) | Yes | The contact details of the publisher could be entered / modified in this field. | No |
| Lbodi_Source_Typ | udd_quickcodes | varchar(25) | Yes | Provision for selecting the source of documents that are to be registered. Values loaded in combo are from the user defined Quick Codes in maintain Quick codes activity. | No |
| Lbodi_Received_From | udd_flag1 | varchar(25) | Yes | Source name from which the document has come to the library. User enterable field. Can have any value. | No |
| Lbodi_Receipt_Datetime | _datetime_8 | datetime(8) | Yes | The date and time of receiving the documents have to be entered here. | No |
| Lbodi_PO_Refno | udd_documentno | varchar(40) | Yes | If purchase order was used for procuring the current document, then PO # is to be entered here. | No |
| Lbodi_Receipt_Ref | udd_txt2000 | varchar(2000) | Yes | Receipt reference number or details of the receipt, which was used while receiving documents in the library, is to be entered here. User can even update the existing values. | No |
| Lbodi_Cost | udd_amount | numeric(13) | Yes | The cost of the document is entered here, in the editable text box. Existing cost can also be updated here. | No |
| Lbodi_Currency | udd_currency | varchar(20) | Yes | If cost value is entered, then selection of one of the currency denominations is mandatory. | No | |
| Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
| Lbodi_OUInstance | udd_ctxt_ouinstance | int(4) | No | The Organization unit at which user has logged in the system, and created the Library Details. | Yes |
| Lbodrd_Document_No | udd_documentno | varchar(40) | No | A mandatory field. It is the unique identifying number to be entered by user, for identifying a particular document. Cannot be changed / modified later on. | Yes |
| Lbodrd_Rev_No | udd_revisionno | varchar(40) | No | Some documents might have undergone revisions. The revision # of the current document being registered needs to be entered. Cannot be modified later. | Yes |
| Lbodrd_Rev_Cycle | udd_designparamcode | varchar(5) | Yes | Combo is to be loaded with Pre Defined values: Not Required, As Required, or Periodic. User can select any of these values to define the periodicity of document revision | No |
| Lbodrd_Rev_Interval | udd_count | int(4) | Yes | If the value in above combo is selected as: Required, then entering time interval value in this combo is mandatory. | No |
| Lbodrd_Rev_Due_On | udd_date | varchar(15) | Yes | The next revision due date is to be entered here. | No |
| Lbodrd_Rev_Action_On | udd_designparamcode | varchar(5) | Yes | "Action on Previous Revision" combo (in Revision Details/Policy tab page) with values: None, Supercede Previous Revision, As Required. | No |
| Lbodrd_Superced_Action | udd_designparamcode | varchar(5) | Yes | uperceding Action combo according to following rules: 1) If Action on Prev Rev is "As Required" or "None" then load "None" 2)If Action on Prev Rev is "Supercede Prev Rev" then it has to be loaded with the following values in the combo : None, Disc | No |
| Lbodi_Revised_date | udd_date | varchar(15) | Yes | The last date on which the particular library information was revised. | No |
| Lbodrd_Rev_Reason | udd_txt2000 | varchar(2000) | Yes | When a document undergoes revision, the reason for the same can be recorded here. | No |
| Lbodrd_Rev_Remarks | udd_txt255 | varchar(255) | Yes | When a document undergoes revision, the remarks for the same can be recorded here. | No |
| Lbodrd_Superced_Rev_No | udd_revisionno | varchar(40) | Yes | Superceding RevisionNo | No |
| Lbodrd_Rev_Implication | udd_quickcodes | varchar(25) | Yes | The combo is to be loaded with user defined quick code values as created for the quick code type: "Revision Implications" in Maintain Quick Codes activity. This is to identify any implication because of the revision of the document #. | No |
| Lbodrd_Rev_Action_Status | udd_quickcodes | varchar(25) | Yes | The combo is to be loaded with user defined quick code values as created for the quick code type: "Revision Action Status" in Maintain Quick Codes activity. This could be related to the action taken with respect to the implication of the document rev | No |