Requesting Locations
This file contains the valid requesting locations for the company. If the transaction type is an Issue, the requesting location does not have to be a valid inventory stock location. It can be a user defined entity, such as a department, cost center, or machine. If the transaction type is a T (Direct Transfer) or X (Intransit Transfer), the requesting location has to be a defined as a location in Inventory Control.
REFERENCED BY
| AP510 | IC64.1 | IC64.2 | IC64.3 | IC64.4 | IC64.5 |
| IC64.6 | IC64.7 | IC64.8 | IC64.9 | IC81.1 | IC840 |
| MX500 | RQ01.1 | RQ810 | RQBL.1 |
| FIELD NAME | DESCRIPTION/VALID VALUES | UPDATED BY | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| RQL-COMPANY Element: Company | Numeric 4 Identifies the AP company if the resource type = V. Identifies the HR company if the resource type = E. It is blank for type A, P or Q resources. |
|
||||||||||||||||
| RQL-REQ-LOCATION Element: Req Location | Alpha 5 The location requisitioning items. This location can be an inventory or noninventory location. |
|
||||||||||||||||
| RQL-NAME Element: Name | Alpha 30 (Lower Case) The requesting location name or description. |
|
||||||||||||||||
| RQL-ADDR1 Element: Addr1 | Alpha 30 (Lower Case) This field contains the first line of address information. |
|
||||||||||||||||
| RQL-ADDR2 Element: Addr1 | Alpha 30 (Lower Case) This field contains the first line of address information. |
|
||||||||||||||||
| RQL-ADDR3 Element: Addr1 | Alpha 30 (Lower Case) This field contains the first line of address information. |
|
||||||||||||||||
| RQL-ADDR4 Element: Addr1 | Alpha 30 (Lower Case) This field contains the first line of address information. |
|
||||||||||||||||
| RQL-CITY-ADDR5 Element: City | Alpha 18 (Lower Case) This field contains the city of the address. |
|
||||||||||||||||
| RQL-STATE-PROV Element: State Prov | Alpha 2 The state or province. |
|
||||||||||||||||
| RQL-COUNTY Element: County | Alpha 25 (Lower Case) The county for the company address. |
|
||||||||||||||||
| RQL-POSTAL-CODE Element: Postal Code | Alpha 10 (Lower Case) This field contains the postal code. |
|
||||||||||||||||
| RQL-COUNTRY-CODE Element: Country Code | Alpha 2 The country code. Required for VAT and intrastat reporting. Must be defined in IN01.1 (Country Maintenance). |
|
||||||||||||||||
| RQL-COUNTRY Element: Country | Alpha 30 (Lower Case) This field contains the country of the address, or it can be used for additional information such as an attention name. |
|
||||||||||||||||
| RQL-ISS-ACCT-UNIT Element: Acct Unit | Alpha 15 The accounting unit is a shorthand notation representing the variable level number. When used in the General Ledger Account Master file, the accounting unit must be defined in the General Ledger Names file as a posting accounting unit. |
|
||||||||||||||||
| RQL-ISS-ACCOUNT Element: Account | Numeric 6 This field along with the accounting unit and subaccount make up the location (account) where amounts and other account information is stored. |
|
||||||||||||||||
| RQL-ISS-SUB-ACCT Element: Sub Acct | Numeric 4 This field contains the subaccount from your general ledger chart of accounts that was charged with the amount carried on this record. |
|
||||||||||||||||
| RQL-IC-TRANS-TYPE Element: Ic Trans Type | Alpha 2 This code indicates the type of inventory transaction that will be created when the line is picked. IS = Issues DT = Direct Transfer IT = Intransit Transfer |
|
||||||||||||||||
| RQL-BUYER-CODE Element: Buyer | Alpha 3 |
|
||||||||||||||||
| RQL-FROM-LOCATION Element: Location | Alpha 5 This is the inventory location that supplies the items or it is the purchase order ship to location that receives the items. When entered here, it is the default from location on the requisition. |
|
||||||||||||||||
| RQL-FROM-COMPANY Element: Company | Numeric 4 This is the company that is the source of the items. When entered here, it is the default company on the requisition. |
|
||||||||||||||||
| RQL-PO-CODE Element: Po Code | Alpha 4 This is the purchase order code that will default from a requesting location to a purchase order. |
|
||||||||||||||||
| RQL-PROCESS-LEVEL Element: Process Level | Alpha 5 This field contains the process level, which is the reporting hierarchy below company. |
|
||||||||||||||||
| RQL-FILL-OR-KILL Element: Fill Or Kill | Alpha 1 F = Fill Backorders K = Kill Backorders |
|
||||||||||||||||
| RQL-STOCKLESS-FL Element: All Flag | Alpha 1 |
|
||||||||||||||||
| RQL-ACTIVITY Element: Activity | Alpha 15 Activities are the processes or procedures that produce work. Cost objects (products, services, customers, and so on) are the reasons for performing the activity. |
|
||||||||||||||||
| RQL-ACCT-CATEGORY Element: Acct Category | Alpha 5 Account categories are groupings of costs, revenues, or a combination of both used for reporting and inquiries for activities in the Activity Management system. All transactions are posted to an account category within an activity. You can assign a specific General Ledger account or range of accounts (company, accounting unit, account, and subaccount) that make up the transactions posted to an account category using AC07.1 (Account Assignment). Period-to-date, year-to-date, and life-to-date balances are maintained by account category for activities. Account categories must be assigned to activities before you do any budgeting or transaction processing. Valid account category types are: cost revenue accrual pass thru |
|
||||||||||||||||
| RQL-BILL-CATEGORY Element: Bill Category | Alpha 32 |
|
||||||||||||||||
| RQL-APPROVAL-TYPE Element: Approval Type | Alpha 1 The type of approval record. " " = Use from IC Company 0 = Header approval-Approval codes 1 = Header approval-Process Flow 2 = Line approval 3 = No approval required |
|
||||||||||||||||
| RQL-ACTIVE-STATUS Element: Active Status | Alpha 1 The status of the account. If Inactive, no posting can be done to the account. A = Active I = Inactive |
|
||||||||||||||||
| RQL-RQL-OBJ-ID Element: Obj Id | Numeric 12 This is the object identifier. It is used to relate commitments or posted transactions back to the originating subsystems. Each subsystem record that is updated as a commitment or posted transaction is assigned an object identifier. The object identifier is maintained in the subsystem files and in the Activity Commitments Detail and Activity Transaction files. The object identifier is a unique key used to drill back from Activity Management to the subsystems. |
|
||||||||||||||||
| RQL-ONE-SRC-ONE-PO Element: One Src One Po | Numeric 1 0 = No 1 = One Requisition to One PO |
|
||||||||||||||||
| RQL-PCARD-NBR Element: Pcard Nbr | Alpha 16 |
|
||||||||||||||||
| RQL-GLN-NBR Element: Gln Nbr | Alpha 13 |
|
||||||||||||||||
| RQL-LOCATION-RULE Element: Rule Name | Alpha 12 |
|
||||||||||||||||
| RQL-PURCH-TAX-CD Element: Tax Code | Alpha 10 |
|
||||||||||||||||
| RQL-PURCH-TAX-FL Element: Purch Tax Fl | Alpha 1 |
|
| NAME | KEY FIELDS | DESCRIPTION / SUBSET CONDITION | USED IN | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| RQLSET1 |
COMPANY REQ-LOCATION |
|
|||||||||||||||||||||||||||||
| RQLSET2 |
RQL-OBJ-ID |
|
| ||||||||||||||||||||||||||||
| RELATION NAME |
RELATED FILE | INTEGRITY RULES / FIELD MATCH | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Buyer | BUYER |
Not Required
| ||||||||||||||||||||||||
| From Company | ICCOMPANY |
Required
| ||||||||||||||||||||||||
| From Location | ICLOCATION |
Not Required
| ||||||||||||||||||||||||
| Glnloc | GLNLOC |
Not Required
| ||||||||||||||||||||||||
| Glnlocdtl | GLNLOCDTL |
Not Required
| ||||||||||||||||||||||||
| Ic Company | ICCOMPANY |
Required
| ||||||||||||||||||||||||
| Ic Location | ICLOCATION |
Not Required
| ||||||||||||||||||||||||
| Procuregrp | PROCUREGRP |
Required
|
| RELATION NAME |
RELATED FILE | INTEGRITY RULES / FIELD MATCH | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Rqrqlaudit | RQRQLAUDIT |
|
All trademarks and registered trademarks are the property of their
respective owners.