Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Information related to demanded materials or services is recorded using "New" option on the Demand Slips list. General slip information is recorded on the fields at the top of the demand slip, while information regarding the requested material or service is recorded on the slip lines.

Slip Number: The record and tracking number of the demand slip. The slips are sorted by their numbers. The Slip Number field is mandatory. Slips cannot be recorded without entering slip number.

Date: The record date of the demand slip. The system date comes into field as default. This data can be changed if necessary. Slips are sorted by date. The Slip date field is mandatory.

Hour: The record time of the demand slip. The system time comes into field as default. This data can be changed if necessary.

Document Number: Document number of the demand slip. Slips are not sorted by document number. Therefore, more than one slip may have the same document number.

Division: Indicates the division of the demand slip. This field is used to associate the demand transaction with one of the defined divisions of the company. The head office is displayed as default. The recorded divisions are listed and the related definition is selected.

Department: Indicates the department of the demand information. This field is used to associate the demand transaction with one of the defined departments of the company.

Plant: Indicates the plant of the demand information.

Warehouse: The locations that are used to store the company's goods or used for other purposes (such as scrap or production) are called

Warehouses. Warehouses are specified in connection with the Company or Division definitions. Indicates the warehouse of the demand slip.

Aux. Code: A secondary code field used to classify slips. Contains 10 characters. The Aux. Code is used to classify slips by company specific criteria. The user can use this field to record any necessary information that is not included in the slip.

Authorization Code: Used to define detailed authorizations. The string is 10 characters long. Each user may be authorized to use different records depending on job definitions. A planning process must be performed for detailed authorization definitions. First, slips to be accessed or processed by each user or user group should be specified. Then, separate authorization codes are assigned to slip groups accessible by each authorization group. Slip based encryption can be performed by authorization code. In this way, only the users who log in with the specified authorization code can access and process the slips.

Status: The field used to track the demand slip status. The Status field contains the following options:

  • Proposal
  • Approved
  • Delivering
  • Closed
  • Cancel

When the slip is recorded for the first time, all demand lines have "Proposal" status, which cannot be changed by the user.

When the demand slip is approved, the status of all lines within the slip changes to Approved.

When part of the demands on the slip is being delivered, the status of the related demand line and demand slip will change to Delivering.

If whole of the demand on the slip line is delivered, the line status changes to Closed. However, if the slip contains other demands that are not fully delivered, the status of the demand slip will be "Delivering".

The status of lines added to a demand slip with Approved/Delivering/Closed status will be "Approved". When a new line is added to a slip with "Closed" status, the status of the line and slip will be "Approved" and "Delivering" respectively.

If the status of all demand lines on the slip is "Proposal", the status of the demand slip will be "Proposal" as well. The demand status will be "Delivering" if the status of at least one line is different than "Proposal". The status of the slip changes to "Closed" if all lines are delivered.

Demanded By: The person to whom the demand belongs.

Employee: This field is used to determine the relevant employee to whom the demand belongs. Provided that the application runs in integration with Human Resources, all recorded employee cards are listed, and the relevant employee is selected. If no connection is available, an employee is selected from the Resource Management/Main Records/Employee Definitions.


  • No labels