ManPageW RequestType

From ADempiere ERP Wiki

Jump to: navigation, search

Return to Index

Enjoy it, and help to fill it! But please, always respecting copyright.

Please write your contributions under the Contributions Section



Contents

Window: Request Type

Description : Maintain Request Types

Help : Request Types are used for processing and categorizing requests. Options are Account Inquiry, Warranty Issue, etc.



Tab: Request Type

Description : Type of request (e.g. Inquiry, Complaint, ..)

Help : Request Types are used for processing and categorizing requests. Options are Account Inquiry, Warranty Issue, etc.

Table Name  : R_RequestType

Fields

Name Description Help Technical Data
Client Client/Tenant for this installation. A Client is a company or a legal entity. You cannot share data between Clients. Tenant is a synonym for Client. AD_Client_ID

NUMBER(10)

TableDir

Organization Organizational entity within client An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations. AD_Org_ID

NUMBER(10)

TableDir

Name Alphanumeric identifier of the entity The name of an entity (record) is used as an default search option in addition to the search key. The name is up to 60 characters in length. Name

NVARCHAR2(60)

String

Description Optional short description of the record A description is limited to 255 characters. Description

NVARCHAR2(255)

String

Active The record is active in the system There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.

There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.

IsActive

CHAR(1)

YesNo

Status Category Request Status Category Category of Request Status enables to maintain different set of Status for different Request Categories R_StatusCategory_ID

NUMBER(10)

TableDir

Default Default value The Default Checkbox indicates if this record will be used as a default value. IsDefault

CHAR(1)

YesNo

Self-Service This is a Self-Service entry or this entry can be changed via Self-Service Self-Service allows users to enter data or update their data. The flag indicates, that this record was entered or created via Self-Service or that the user can change it via the Self-Service functionality. IsSelfService

CHAR(1)

YesNo

EMail when Due Send EMail when Request becomes due Send EMail when Request becomes due IsEMailWhenDue

CHAR(1)

YesNo

Due Date Tolerance Tolerance in days between the Date Next Action and the date the request is regarded as overdue When the Date Next Action is passed, the Request becomes Due. After the Due Date Tolerance, the Request becomes Overdue. DueDateTolerance

NUMBER(10)

Integer

EMail when Overdue Send EMail when Request becomes overdue Send EMail when Request becomes overdue IsEMailWhenOverdue

CHAR(1)

YesNo

Auto Due Date Days Automatic Due Date Days If a due date is not defined and the Auto Due Days ins greater then zero, a due date in the number of days is automatically created. AutoDueDateDays

NUMBER(10)

Integer

Invoiced Is this invoiced? If selected, invoices are created IsInvoiced

CHAR(1)

YesNo

Confidentiality Type of Confidentiality ConfidentialType

CHAR(1)

List

Confidential Info Can enter confidential information When entering/updating Requests over the web, the user can mark his info as confidential IsConfidentialInfo

CHAR(1)

YesNo

Create Change Request Automatically create BOM (Engineering) Change Request Create automatically a Product Bill of Material (Engineering) Change Request when the Request Group references a Product BOM IsAutoChangeRequest

CHAR(1)

YesNo


Tab: Update Notification

Description : List Recipients for to receive Request Updates

Help :

Table Name  : R_RequestTypeUpdates

Fields

Name Description Help Technical Data
Client Client/Tenant for this installation. A Client is a company or a legal entity. You cannot share data between Clients. Tenant is a synonym for Client. AD_Client_ID

NUMBER(10)

TableDir

Organization Organizational entity within client An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations. AD_Org_ID

NUMBER(10)

TableDir

Request Type Type of request (e.g. Inquiry, Complaint, ..) Request Types are used for processing and categorizing requests. Options are Account Inquiry, Warranty Issue, etc. R_RequestType_ID

NUMBER(10)

TableDir

User/Contact User within the system - Internal or Business Partner Contact The User identifies a unique user in the system. This could be an internal user or a business partner contact AD_User_ID

NUMBER(10)

Search

Active The record is active in the system There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.

There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.

IsActive

CHAR(1)

YesNo

Self-Service This is a Self-Service entry or this entry can be changed via Self-Service Self-Service allows users to enter data or update their data. The flag indicates, that this record was entered or created via Self-Service or that the user can change it via the Self-Service functionality. IsSelfService

CHAR(1)

YesNo

Contributions

You will find further information here in the Contributions section, as the above sections are automatically generated. Therefore, any changes there would be lost.

The information below should be only additional information to supplement the above. If you find duplications to the above then please edit or raise a note in the Adempiere forum in Sourceforge.

To understand the meaning of mandatory, optional & required as used below, see Optional & Required Definitions for an explanation.

Window : Request Type (optional)

Path: Menu > Partner Relations > Request > Request Type

The purpose of requests is to track communication with the business partners, both on an internal and external basis. The requests can be generated via incoming emails, web store, or logged into Adempiere.

Request Type window allows you to define the different types of requests that you want to control. The request type also controls what should happen to a request, eg send an email when a expiry period is triggered.

Note, If you want to reuse the information that you enter here in other organizations under the same client, make sure to select the organization "*" at login or choose "*" in the organization drop down when creating a new record. That will make all settings you create common for all organizations under this client. This will apply to any codes, groupings, etc that you want to appear in many levels of an organization in your company (client).

Tab : Request Type (optional)

Define the different types of requests to be dealt with in the organization.

You will find that the Client and Organization are defaulted based on the choice you made when you logged in. Creating a new record allows you to change the Client and Organization, however, after saving, these values are fixed.

Field: Client (required)

See Basic & Common Field Definitions - Client

Field: Organization (required)

See Basic & Common Field Definitions - Organization

You may choose an organization of "*" as the BP is valid for all organizations in the client. For example, certain vendors, like your phone provider, stationary, etc.

Field: Name (mandatory)

See Basic & Common Field Definitions - Name

Field: Description (optional)

See Basic & Common Field Definitions - Description

Field: Active(optional)

See Basic & Common Field Definitions - Active

Field: Status Category (required)

What status it should open with when creating a new request of this request type. The status category helps the user to determine what status it currently is at. Other Status Categories can be defined.

(??? link to the maintenance of status category ???)

Field: Default (optional)

See Basic & Common Field Definitions - Optional

Field: Self Service (optional)

Requests created with this request type can be maintained by the user via the self service facilities.

Field: Email when Due (optional)

Tick this field if you want an email generated when the request is due. The generation is based on the field, Due Date Tolerance.

(??? Who receives the email? / Is the email sent to the creator of the request or the assignee? ???)

Field: Due Date Tolerance (optional)

Enter the number of days that the due date is required for an email to be generated. The tolerance is used on the request created date, or the last date it was updated while still within this request type.

Field: Email when Overdue (optional)

Tick this field if an email is to be generated if the request is now overdue. This is based on the next due date on the request.

(??? is this correct? ???)

Field: Auto Due Date Days (optional)

This is used to determine the due date if one is not entered on the request.

Field: Invoiced (optional)

Tick this field if you want to generate an invoice. Generation of an invoice is for support requests that are to be invoiced.

(??? Correct interpretation? ???)

Field: Confidentiality (required)

Select the type of confidentiality to apply to requests created with this request type.

No further types can be defined for this field. They are set by Adempiere.

Field: Confidential Info (optional)

If ticked then the user on the web can mark the request as confidential. Confidential for the BP that has created the request.

Field: Create Change Request (optional)

(??? Purpose ???)

Tab : Update Notification (optional)

Define who should receive update notifications when this request type is used.

You will find that the Client and Organization are defaulted based on the choice you made when you logged in. Creating a new record allows you to change the Client and Organization, however, after saving, these values are fixed.

Field: Client (required)

See Basic & Common Field Definitions - Client

Field: Organization (required)

See Basic & Common Field Definitions - Organization

You may choose an organization of "*" as the BP is valid for all organizations in the client. For example, certain vendors, like your phone provider, stationary, etc.

Field: Request Type(required)

The request type selected for maintaining from the Request Type tab.

Field: User / Contact (mandatory)

Which user/contact is to be sent the email. It can be any user/contact defined in the organization.

Field: Active (optional)

See Basic & Common Field Definitions - Active

Field: Self Service (optional)

The field is greyed out and unchecked even if Self Service is selected in the Request Type tab.

(??? why? ???)

Personal tools