First Time Setup
To set up the Simplified Loader Requisitioning mobile app, you need to follow the steps mentioned in the Mobile App – First Time Setup guide. After completing Mobile App – First Time Setup steps, also perform the following two steps
Step 1. Configure fields displayed in the mobile app
Requisitioning mobile app gives administrator flexibility to defines fields displayed in the mobile app. The administrator also controls the field behaviour, which is configured using Preference. The fields for the mobile app should be defined in SL_REQUISITIONING_FIELDS_SETUP lookup type. In the absence of SL_REQUISITIONING_FIELDS_SETUP lookup type, the Requisitioning app’s default behaviour shows the following fields in the mobile device.
| Display Sequence | Meaning (User Field Name) | Description (Preference) |
|---|---|---|
| 5 | Requisition Number | ShowByDefault[Y] | UserOverride[N] | Mandatory[N] |
| 10 | Requisition Business Unit | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| 20 | Requisition Business Unit ID | ShowByDefault[N] | UserOverride[Y] | Mandatory[Y] |
| 30 | Description | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| 40 | Preparer Email | ShowByDefault[N] | UserOverride[N] | Mandatory[Y] | DefaultFromSQL[PREPARER_EMAIL] |
| 50 | Initiate Approval After Requisition Import | ShowByDefault[N] | UserOverride[N] | Mandatory[Y] | DefaultValue[Y] |
| 60 | Document Status Code | ShowByDefault[N] | UserOverride[N] | Mandatory[Y] | DefaultValue[INCOMPLETE] |
| 70 | Taxation Country Code | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| 90 | Interface Source Code | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] | DefaultValue[Simplified Loader] |
| 100 | Externally Managed Flag | ShowByDefault[N] | UserOverride[N] | Mandatory[Y] | DefaultValue[N] |
| 110 | Product Type Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| 120 | Requester Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] | DefaultFromSQL[PREPARER_NAME] |
| 130 | Requester Email | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] | DefaultFromSQL[PREPARER_EMAIL] |
| 140 | Deliver To Location Code | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] | DefaultFromSQL[DELIVER_TO_LOCATION_CODE] |
| 150 | Line Type | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| 160 | Category Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| 170 | Supplier Number | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| 180 | Supplier Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| 190 | Supplier Site Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| 200 | Supplier Contact Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| 210 | Supplier Item Number | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| 220 | Item Description | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| 230 | Quantity | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| 240 | Unit Of Measure | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| 250 | Price | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| 255 | Amount | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] |
| 260 | Destination Type Code | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| 270 | Negotiation Required Flag | ShowByDefault[N] | UserOverride[N] | Mandatory[Y] | DefaultValue[N] |
| 280 | Negotiated By Preparer Flag | ShowByDefault[N] | UserOverride[N] | Mandatory[Y] | DefaultValue[Y] |
| 290 | Buyer Name | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] |
| 300 | Percent | ShowByDefault[Y] | UserOverride[Y] | Mandatory[Y] | DefaultValue[100] |
| 310 | Charge Account Segment1 | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] | DefaultFromSQL[GL_SEGMENT1] |
| 320 | Charge Account Segment2 | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] | DefaultFromSQL[GL_SEGMENT2] |
| 330 | Charge Account Segment3 | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] | DefaultFromSQL[GL_SEGMENT3] |
| 340 | Charge Account Segment4 | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] | DefaultFromSQL[GL_SEGMENT4] |
| 350 | Charge Account Segment5 | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] | DefaultFromSQL[GL_SEGMENT5] |
| 360 | Charge Account Segment6 | ShowByDefault[Y] | UserOverride[Y] | Mandatory[N] | DefaultFromSQL[GL_SEGMENT6] |
You can choose to modify the default fields and apply custom controls the behaviour of individual fields. To define fields for Requisitiong app, you would need to define Requisition fields in SL_REQUISITIONING_FIELDS_SETUP lookup type. This lookup type defines which fields should get displayed in the mobile app and Preferences against each field to control field behaviour.
1. Navigate to Setup and Maintenance and search task Manage Common Lookups. Create a new Lookup Type SL_REQUISITIONING_FIELDS_SETUP. SL Requisitioning app utilizes SL_REQUISITIONING_FIELDS_SETUP lookup type to render fields in mobile app
| Lookup Type | : | SL_REQUISITIONING_FIELDS_SETUP |
| Meaning | : | Simplified Loader Requisitioning Mobile app fields setup |
| Description | : | Leave blank |
| Module | : | Common Lookups |
| Lookup Configuration Level | : | User |
| REST Access Secured | : | Secure |
2. Enter Requisition field details in the Lookup Code section:
| Lookup Code | : | Enter the same value as used in the Meaning field. In case length of the Meaning field, contains is more than 30 characters then use any value in Lookup Code field |
| Display Sequence | : | The sequence in which field will display in the mobile app |
| Enabled | : | Indicate if a field is enabled for Requisitioning mobile app |
| Start Date | : | Leave blank |
| End Date | : | Leave blank |
| Meaning | : | Enter the field name that gets displayed to the user. Select the field name from the table of allowed field names |
| Description | : | Preferences related to Requisitioning fields |
| Tag | : | Leave blank |
Allowed fields in Requisitioning app
Requisitioning mobile app support fields mentioned in the following table. You are required to use the value from the User Field Name column in this table. The other fields (Section Name, Data Type, and User Field Description) are for information purposes only. To define a new field in the Requisitioning mobile app put the value from the User Field Name column to Meaning field in the Lookup Code section of SL_REQUISITIONING_FIELDS_SETUP Lookup Type.
| Section Name | User Field Name | Data Type | Field Description |
|---|---|---|---|
| None | Requisition Title | Character | Title to identify Requisition in your mobile device. This is a reserved field and should not be used in SL_REQUISITIONING_FIELDS_SETUP Lookup Type. |
| None | Load Status | Character | Requisition upload status. This is a reserved field and should not be used in SL_REQUISITIONING_FIELDS_SETUP Lookup Type. |
| None | Error Message | Character | Requisition upload error message. This is a reserved field and should not be used in SL_REQUISITIONING_FIELDS_SETUP Lookup Type. |
| Header | Interface Header Key | Character | The cloud interface alternate header key code, for integrating applications to be able to identify the requisition header data loaded in the interface table. |
| Header | Requisition Number | Character | The display number used to identify a requisition. |
| Header | Requisition Business Unit ID | Character | The unique identifier of a requisitioning business unit. |
| Header | Requisition Business Unit | Character | The display name of a requisitioning business unit. |
| Header | Interface Source Code | Character | A code indicating the outside source that the data was imported from. Reserved values for internal use include ORA_FUSION_DOO, ORA_FUSION_SCO, ORA_FUSION_INV. |
| Header | Description | Character | A text description capturing the purpose of the requisition. |
| Header | Document Status Code | Character | A code indicating the status of the requisition. Valid values include incomplete and approved. |
| Header | Preparer ID | Character | The unique identifier of the requisition preparer that maps to the person ID within Oracle Fusion Applications. |
| Header | Preparer Email | Character | The e-mail address for the requisition preparer. |
| Header | Initiate Approval After Requisition Import | Character | Flag to indicate whether to Requisition for approval after a successful import. |
| Header | Emergency PO Number | Character | The display number used to identify a purchase order number reserved in advanced for an emergency requisition. |
| Header | Justification | Character | A text description capturing the reason for the requisition. |
| Header | Taxation Country Code | Character | A code indicating the country where the transaction is deemed to have taken place for taxation purposes. |
| Header | Taxation Territory | Character | A code indicating the territory where the transaction is deemed to have taken place for taxation purposes. |
| Header | Document Fiscal Classification Code | Character | A classification used by a tax authority to categorize a document associated with a transaction for a tax. |
| Header | Document Fiscal Classification | Character | A classification used by a tax authority to categorize a document associated with a transaction for a tax. |
| Header | Sold To Legal Entity ID | Character | The unique identifier of the legal entity that is liable for the purchase order amount. |
| Header | Sold To Legal Entity Name | Character | The name of the legal entity that is liable for the purchase order amount. |
| Header | Approver Email | Character | The e-mail address of the requisition approver. |
| Header | Approver ID | Character | The unique identifier of the requisition approver. |
| Header | Interface Source Line ID | Character | The unique identifier of the source transaction. |
| Header | Externally Managed Flag | Y / N | Indicates whether or not the requisition line is externally managed. |
| Header | Header Attribute Category | Character | The user descriptive flexfield structure. |
| Line | Interface Line Key | Character | The cloud interface alternate line key code, for integrating applications to be able to identify the requisition line data loaded in the interface table. |
| Line | Line Type | Character | The display name of a line type that indicates whether a purchase is for goods or services. |
| Line | Line Type ID | Character | The unique identifier of a type to indicate whether a purchasing document line is for goods or services, as well as to default some attributes associated with the line. |
| Line | Category ID | Character | The unique identifier of the code used to group items with similar characteristics. |
| Line | Category Name | Character | The display name of a category used to group items with similar characteristics. |
| Line | Destination Type Code | Character | A code indicating if the item should be charged to an inventory or should be expensed. |
| Line | Destination Subinventory | Character | The display name of a subinventory to which the requested item should be delivered. |
| Line | Currency Code | Character | A code indicating the three-letter ISO code associated with a currency. |
| Line | Amount | Character | The total amount according to the quantities and prices of the goods and service items specified on the requisition line. |
| Line | Price | Character | The price of the item on the requisition line. |
| Line | Quantity | Character | The quantity for the item to be added to the requisition. |
| Line | Unit Of Measure Code | Character | A code indicating the division of quantity defined as a standard of measurement or exchange. |
| Line | Unit Of Measure | Character | A division of quantity defined as a standard of measurement or exchange. |
| Line | Secondary Quantity | Character | The quantity converted in the secondary unit of measure of a dual UOM controlled item. |
| Line | Secondary UOM Code | Character | A code indicating the alternative unit of measure that is allowed to quantify a dual UOM controlled item. |
| Line | Secondary UOM | Character | An alternative unit of measure that is allowed to quantify a dual UOM controlled item. |
| Line | Procurement Business Unit ID | Character | The unique identifier of a procurement business unit. |
| Line | Procurement Business Unit Name | Character | The display name of a procurement business unit. |
| Line | Rate | Character | The ratio at which the principal unit of one currency can be converted into another currency. |
| Line | Rate Date | Date | The date as of which a conversion rate is used to convert an amount into another currency. |
| Line | Rate Type | Character | The source of a currency conversion rate, such as user defined, spot, or corporate. For user-defined rate, provide USER in the rate type. |
| Line | Requester ID | Character | The unique identifier of a requester. |
| Line | Requester Email | Character | The e-mail address for a requester. |
| Line | Product Category | Character | A code indicating the type of product fiscal classification used to classify products. |
| Line | Product Category Name | Character | The display name of a product fiscal classification type used to classify products. |
| Line | Product Type | Character | A code indicating the type of product fiscal classification used to classify products. Related term(s) product fiscal classification. |
| Line | Product Type Name | Character | The display name of a product fiscal classification type used to classify products. |
| Line | Urgent Requisition Line Flag | Y / N | Indicates whether the requisition is urgent or not. |
| Line | Note To Buyer | Character | A text description capturing the instructions to the buyer when processing the requisition line. |
| Line | Note To Supplier | Character | A text description capturing the instructions to the supplier. |
| Line | Note To Receiver | Character | A text description capturing the instructions to the receiver in the docking area to be reviewed while performing the receipt. |
| Line | Buyer ID | Character | The unique identifier of the buyer specified on the document. A buyer is a person responsible for placing item resupply orders with suppliers and negotiating supplier contracts. |
| Line | Buyer Name | Character | The display name of a buyer specified on the document. A buyer is a person responsible for placing item resupply orders with suppliers and negotiating supplier contracts. |
| Line | Buyer Email | Character | The e-mail address of the buyer specified on the document. A buyer is a person responsible for placing item resupply orders with suppliers and negotiating supplier contracts. |
| Line | New Supplier Flag | Y / N | Indicates whether or not the supplier is new. |
| Line | Supplier Item Number | Character | The display name of a suppliers identification number or code for the goods ordered on your order line. |
| Line | Supplier ID | Character | The unique identifier of an organization or individual that provides goods or services to the buying organization for payment, bound by a contractual obligation. |
| Line | Supplier Name | Character | The display name of an organization or individual that provides goods or services to the buying organization for payment, bound by a contractual obligation. |
| Line | Supplier Site ID | Character | The unique identifier of an entity that models how the buying organization conducts business with the supplier. |
| Line | Supplier Site Name | Character | The display name of an entity that models how the buying organization conducts business with the supplier. |
| Line | Supplier Contact ID | Character | The unique identifier of a supplier employee who represents the supplier in communications with the buying organization. |
| Line | Supplier Contact Name | Character | The display name of a supplier employee who represents the supplier in communications with the buying organization. |
| Line | Supplier Contact Email | Character | The e-mail address for a supplier employee who represents the supplier in communications with the buying organization. |
| Line | Supplier Contact Fax | Character | The fax number for a supplier employee who represents the supplier in communications with the buying organization. |
| Line | Supplier Contact Phone | Character | The phone number for a supplier employee who represents the supplier in communications with the buying organization. |
| Line | Source Agreement ID | Character | The unique identifier of a purchase agreement against which this purchase order line is released. |
| Line | Source Agreement Number | Character | The display number used to identify a purchase agreement against which this purchase order line is released. |
| Line | Source Agreement Line ID | Character | The unique identifier of a purchase agreement line against which this purchase order line is released. |
| Line | Source Agreement Line Number | Character | The display number used to identify a purchase agreement line against which this purchase order line is released. |
| Line | Item ID | Character | The unique identifier of an item. |
| Line | Item Description | Character | A text description capturing details about the item being purchased. |
| Line | Item Number | Character | The display name of an item representing anything you make, purchase, or sell, including components, subassemblies, finished products, or supplies. |
| Line | Item Revision | Character | Identifier that indicates version of inventory item being referenced on the order line. |
| Line | Base Model ID | Character | The unique identifier of a model from which an ATO configuration was created. |
| Line | Base Model Number | Character | The display name of a model from which an ATO configuration was created. |
| Line | Base Model Price | Character | The model price from which an ATO configuration was created. |
| Line | First Party Tax Registration ID | Character | The unique identifier of the tax registration record corresponding to the sold-to legal entity on the purchase order. |
| Line | First Party Tax Registration Number | Character | The unique display number assigned to the sold-to legal entity by a tax authority in order to manage tax liabilities. |
| Line | Line Intended Use ID | Character | The unique identifier of a tax classification that is based on the purpose for which a product is used. |
| Line | Line Intended Use | Character | A code indicating the type of the tax classification that is based on the purpose for which a product is used. |
| Line | Line Intended Use Name | Character | The display name of a tax classification that is based on the purpose for which a product is used. |
| Line | Assessable Amount | Character | The price at which a product is valued, by a tax authority, for tax calculation purposes. The same product can have more than one assessable value, as given by different tax authorities. |
| Line | Tax Classification Code | Character | A code indicating the group of taxes for reporting and processing purposes. |
| Line | Tax Classification Name | Character | The display name of a group of taxes for reporting and processing purposes. |
| Line | Third Party Tax Registration ID | Character | A unique identifier of the registration number assigned to the supplier or supplier site, when it is registered by a tax authority, and by which the party or party site registration will be identified. |
| Line | Third Party Tax Registration Number | Character | A unique sequence of letters and/or numbers assigned to the supplier or supplier site, when it is registered by a tax authority, and by which the party or party site registration will be identified. |
| Line | Product Fiscal Classification ID | Character | The unique identifier of a classification used by a tax authority to categorize a product for a tax. There could be more than one by tax. For example, for Brazil two classifications are required. |
| Line | Product Fiscal Classification | Character | A code indicating the classification used by a tax authority to categorize a product for a tax. There could be more than one by tax. For example, for Brazil two classifications are required. |
| Line | Product Fiscal Classification Name | Character | The display name of a classification used by a tax authority to categorize a product for a tax. There could be more than one by tax. For example, for Brazil two classifications are required. |
| Line | User Defined Fiscal Classification | Character | A coding indicating the classification for any tax requirement that you cannot define using the existing fiscal classification types. |
| Line | User Defined Fiscal Classification Name | Character | The display name of a classification for any tax requirement that you cannot define using the existing fiscal classification types. |
| Line | Transaction Business Category | Character | A code indicating the business classification used by Oracle Fusion Tax to identify and categorize an external transaction into an Oracle Fusion Tax transaction. |
| Line | Transaction Business Category Name | Character | The display name of a business classification used by Oracle Fusion Tax to identify and categorize an external transaction into an Oracle Fusion Tax transaction. |
| Line | Negotiated By Preparer Flag | Y / N | Indicates whether or not the requested item is negotiated with the supplier. |
| Line | Negotiation Required Flag | Y / N | Indicates whether or not a negotiation is required for the requested item. |
| Line | Service Level Code | Character | A code indicating the priority of transportation that affects how quickly goods are transported. Applicable values are all codes of the lookup Carrier Service Levels. |
| Line | Hazard Class ID | Character | The unique identifier of a classification of hazardous materials, to facilitate safety regulations compliance. |
| Line | Hazard Class | Character | The display name of a classification of hazardous materials, to facilitate safety regulations compliance. |
| Line | UN Number ID | Character | The unique identifier of a United Nations identification number for the hazardous material. |
| Line | UN Number | Character | The display name of a United Nations identification number for the hazardous material. |
| Line | Customer Item Number | Character | The display name of a customers identification number or code for the goods ordered on your order line. |
| Line | Customer Item Description | Character | A text description capturing a customers identification number or code for the goods ordered on your order line. |
| Line | Customer PO Line Number | Character | The display number used to identify a purchase order line from the customer that originated the sales order, which is being fulfilled by the material being procured in a drop ship arrangement. |
| Line | Customer PO Number | Character | The display number used to identify a purchase order from the customer that originated the sales order, which is being fulfilled by the material being procured in a drop ship arrangement. |
| Line | Customer PO Schedule Number | Character | The display number used to identify a purchase order schedule from the customer that originated the sales order, which is being fulfilled by the material being procured in a drop ship arrangement. |
| Line | Deliver To Customer Contact ID | Character | The unique identifier of a customer contact to which materials, being procured in a drop ship arrangement, need to be delivered. |
| Line | Deliver To Customer Contact Name | Character | The display name of a customer contact to which materials, being procured in a drop ship arrangement, need to be delivered. |
| Line | Deliver To Customer Contact Number | Character | The display number used to identify a customer contact to which materials, being procured in a drop ship arrangement, need to be delivered. |
| Line | Deliver To Customer Contact Email | Character | The e-mail for a customer contact to which materials, being procured in a drop ship arrangement, need to be delivered. |
| Line | Deliver To Customer ID | Character | The unique identifier of a customer to which materials, being procured in a drop ship or back to back arrangement, need to be delivered. |
| Line | Deliver To Customer Name | Character | The display name of a customer to which materials, being procured in a drop ship or back to back arrangement, need to be delivered. |
| Line | Deliver To Customer Number | Character | The display number used to identify a customer to which materials, being procured in a drop ship or a back to back arrangement, need to be delivered. |
| Line | Deliver To Customer Location CLLI Code | Character | The CLLI code for the customer location to which materials, being procured in a drop ship arrangement, need to be delivered. |
| Line | Deliver To Customer Location Original System Reference | Character | The original system reference for the customer location to which materials, being procured in a drop ship arrangement, need to be delivered. |
| Line | Deliver To Customer Location ID | Character | The unique identifier of a customer location to which materials, being procured in a drop ship arrangement, need to be delivered. |
| Line | Deliver To Location Code | Character | A code indicating the final delivery location for goods previously received from a supplier. |
| Line | Deliver To Location ID | Character | The unique identifier of a final delivery location for goods previously received from a supplier. |
| Line | Deliver To Organization Code | Character | A code indicating the organization to which the requested item should be delivered. |
| Line | Deliver To Organization ID | Character | The unique identifier of a organization to which the requested item should be delivered. |
| Line | Ship To Customer Contact ID | Character | The unique identifier of a customer contact to whom materials, being procured in a drop ship arrangement, need to be shipped. |
| Line | Ship To Customer Contact Name | Character | The display name of a customer contact to whom materials, being procured in a drop ship arrangement, need to be shipped. |
| Line | Ship To Customer Contact Number | Character | The display number used to identify a customer contact to whom materials, being procured in a drop ship arrangement, need to be shipped. |
| Line | Ship To Customer Contact Email | Character | The e-mail address of a customer contact to whom materials, being procured in a drop ship arrangement, need to be shipped. |
| Line | Ship To Customer ID | Character | The unique identifier of a customer to whom materials, being procured in a drop ship or a back to back arrangement need to be shipped. |
| Line | Ship To Customer Name | Character | The display name of a customer to whom materials, being procured in a drop ship or a back to back arrangement, need to be shipped. |
| Line | Ship To Customer Number | Character | The display number used to identify a customer to whom materials, being procured in a drop ship or a back to back arrangement, need to be shipped. |
| Line | Ship To Customer Location CLLI Code | Character | The CLLI Code for the customer location where materials, being procured in a drop ship arrangement, need to be shipped. |
| Line | Ship To Customer Location Original System Reference | Character | The original system reference for the customer location where materials, being procured in a drop ship arrangement, need to be shipped. |
| Line | Ship To Customer Location ID | Character | The unique identifier of a customer location where materials, being procured in a drop ship arrangement, need to be shipped. |
| Line | Sales Order Number | Character | The display number used to identify a backing customer sales order number. |
| Line | Sales Order Line Number | Character | The display number used to identify a backing customer sales order line number. |
| Line | Sales Order Schedule Number | Character | The display number used to identify a backing customer sales order schedule number. |
| Line | Work Order ID | Character | The unique identifier of a contract manufacturing work order. |
| Line | Work Order Number | Character | The display number used to identify the finished goods product of a contract manufacturing work order. |
| Line | Work Order Product | Character | The display name of the finished goods product of the contract manufacturing work order. |
| Line | Work Order Operation ID | Character | The unique identifier of a contract manufacturing work order operation. |
| Line | Work Order Operation Sequence | Character | The sequence number of work order operation. |
| Line | Work Order Sub Type Code | Character | The code of the work order sub type. |
| Line | Location Of Final Discharge ID | Character | The unique identifier of a final destination location for the purchases made by the customer. The location of the final customer or where the goods would be used is not necessarily the same as the initial ship-to location. |
| Line | Location Of Final Discharge Code | Character | A code indicating the final destination location for the purchases made by the customer. The location of the final customer, or where the goods would be used, is not necessarily the same as the initial ship-to location. |
| Line | Mode Of Transport Code | Character | The display name of a mode of transportation used to describe the movement of goods. |
| Line | Carrier ID | Character | The unique identifier of the company that transports goods from one point to another by land, sea, or air. |
| Line | Carrier | Character | The display name of the company that transports goods from one point to another by land, sea, or air. |
| Line | Requested Ship Date | Date | The date when the buying company has requested the ordered item is ready to be shipped. |
| Line | Requested Delivery Date | Date | The date when the buying company has requested the ordered item or service to be delivered. |
| Line | Days Early Receipt Allowed | Character | The maximum acceptable number of days early for receipts. |
| Line | Days Late Receipt Allowed | Character | The maximum acceptable number of days late for receipts. |
| Line | Configured Item Flag | Y / N | Indicates whether the requisition line is for a configured item and configuration details might exist. |
| Line | Orchestration Code | Character | A code indicating if the integrating application is synchronizing changes between their application and Oracle Fusion Procurement. Example values include DOO_TRACKED and SCO_TRACKED. |
| Line | Group Code | Character | A code indicating the option by which the requisition lines are grouped when they are being processed by the import program. Requisition lines that are grouped together will be put on the same requisition header. Valid values include none, buyer, category, item, location, and supplier. |
| Line | Over Receipt Tolerance Percent | Character | The tolerance that allows a purchase order schedule to receive more than ordered quantity or amount without triggering the over-receipt action. |
| Line | Back To Back Flag | Y / N | Indicates whether the purchase order schedule has a backing sales order that is fulfilled using a back to back order. |
| Line | Autosource Flag | Y / N | Indicates whether supplier and price information is derived from source purchase agreements. |
| Line | Line Attribute Category | Character | The user descriptive flexfield structure. |
| Distribution | Interface Distribution Key | Character | The cloud interface alternate distribution key code, for integrating applications to be able to identify the requisition distribution data loaded in the interface table. |
| Distribution | Percent | Character | The percentage of the requisition distribution. |
| Distribution | Distribution Amount | Character | The total amount of the distribution according to the distribution quantity and requisition line price. |
| Distribution | Distribution Quantity | Character | The quantity for the requisition distribution. |
| Distribution | Budget Date | Date | The date used to derive the budget period from which budget is consumed. |
| Distribution | Charge Account ID | Character | The unique identifier of the General Ledger charge account. |
| Distribution | Charge Account Segment1 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment2 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment3 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment4 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment5 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment6 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment7 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment8 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment9 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment10 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment11 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment12 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment13 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment14 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment15 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment16 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment17 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment18 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment19 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment20 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment21 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment22 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment23 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment24 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment25 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment26 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment27 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment28 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment29 | Character | The charge account key flexfield segment. |
| Distribution | Charge Account Segment30 | Character | The charge account key flexfield segment. |
| Distribution | Project ID | Character | The unique identifier of a project. |
| Distribution | Project Number | Character | The number assigned to a project. A project is a finite endeavor (having specific start and finish dates) undertaken to create a product or provide a service. |
| Distribution | Project Name | Character | The display name of a project. A project is a finite endeavor (having specific start and finish dates) undertaken to create a product or provide a service. |
| Distribution | Project Task ID | Character | The unique identifier of the number of a task which is a subdivision of project work. |
| Distribution | Project Task Name | Character | The display name of a task which is a subdivision of project work. |
| Distribution | Project Organization ID | Character | The unique identifier of the organization that incurred the cost on the expenditure item. |
| Distribution | Project Organization Name | Character | The display name of the organization that incurred the cost on the expenditure item. |
| Distribution | Project Expenditure Item Date | Date | The specified day when the expenditure item was incurred. |
| Distribution | Project Expenditure Type ID | Character | The unique identifier of a classification of cost that is assigned to each expenditure item. Expenditure types are grouped into cost groups (expenditure categories) and revenue groups (revenue categories). |
| Distribution | Project Expenditure Type Name | Character | The display name of a classification of cost that you assign to each expenditure item. Expenditure types are grouped into cost groups and revenue groups. |
| Distribution | Project Capitalizable Flag | Y / N | Indicates whether or not the expenditure item is capitalizable after it is fully processed. The debit amount for a capitalizable transaction is generally made to a construction in progress account. |
| Distribution | Project Work Type ID | Character | The unique identifier of a classification of the work associated with a task. |
| Distribution | Project Work Type Name | Character | The display name of a classification of the work associated with a task. |
| Distribution | Project Billable Flag | Y / N | Indicates whether or not the expenditure item is billable after it is fully processed. |
| Distribution | Project Funding Allocation ID | Character | The unique identifier of the project funding override. This attribute is used when Oracle Fusion Project Billing or Oracle Fusion Grants Management is installed. |
| Distribution | Project Funding Source Name | Character | The display name used to identify the funding source associated with a sponsored project. |
| Distribution | Project Context Category | Character | An attribute that determines which contextual segments of a descriptive flexfield to display for a transaction. For example, an expense report transaction may have different descriptive flexfield segments defined as compared to a time card transaction. |
| Distribution | Project Contract ID | Character | The unique identifier of the contract. This attribute is used when Oracle Fusion Project Billing or Oracle Fusion Grants Management is installed. |
| Distribution | Project Contract Name | Character | Name of the contract. This attribute is used when Oracle Fusion Project Billing or Oracle Fusion Grants Management is installed. |
| Distribution | Project Contract Number | Character | Number of the contract. This attribute is used when Oracle Fusion Project Billing or Oracle Fusion Grants Management is installed. |
| Distribution | Project Contract Line ID | Character | The unique identifier of the contract line. This attribute is used when Oracle Fusion Project Billing or Oracle Fusion Grants Management is installed. |
| Distribution | Project Reserved Attribute1 | Character | The reserved descriptive flexfield segment for future project related functionality. |
| Distribution | Distribution Attribute Category | Character | The user descriptive flexfield structure. |
Preferences
Requisitioning mobile app allows defining the following preferences to control the field behaviour. Preferences are entered in the Description field of the Lookup Code section. The format to enter Preference and its value is
PreferenceName[PreferenceValue]
The preference value is specified within the square brackets. The administrator can choose to use one or more preferences. When using multiple preferences, enter pipe (|) delimiter between preferences.
Mandatory
The Mandatory Preference is used to specify a field as mandatory. Mandatory Preference allows Y or N value. Enter Mandatory[Y] to indicate a field required in the mobile app. By default, all fields are set as non-mandatory.
The Mandatory field validation check is performed when a user submits the Requisition for creation.
UserOverride
The administrator can set up fields such that the user is not allowed to override values in the mobile app. UserOverride Preference allows Y or N value. When using UserOverride[N] preference, the administrator must ensure to specify a default value using DefaultValue or DefaultFromSQL preferences. By default, all fields are set as UserOverride[Y].
ShowByDefault
The ShowByDefault preference defines whether a field gets displayed to the user while entering Requisition in the mobile app. ShowByDefault Preference allows Y or N value. Using ShowByDefault preference, the administrator can determine fields that the user should see when entering a Requisition. When using ShowByDefault[N] preference, the administrator must ensure to specify a default value using DefaultValue or DefaultFromSQL preferences. By default, all fields are set as ShowByDefault[Y].
The user can override ShowByDefault Preference from the Field Setup section in the mobile app.
The usage of this Preference is to define fields like Initiate Approval, where the administrator doesn’t want the mobile user to override field value in the mobile app.
DefaultValue
The DefaultValue Preference defines a static default value of a field. The default value is specified within the square brackets. Example, to default the value “INCOMPLETE” in the Document Status Code field, set DefaultValue[INCOMPLETE] as Preference.
To define a default value for fields having Y / N data type, specify value true or false in the DefaultValue Preference.
By default, the user can override the default value in the mobile app. To stop the users from overriding default value use preference UserOverride.
DefaultFromSQL
The DefaultFromSQL Preference defines a default value based on the SQL select statement. Configuring DefaultFromSQL is a two-step process
a. Define the SQL to fetch data based on user:
- Navigate to BI Report /custom/SL_Templates/MobileCreateReq/UserSQLDefaultsReport
- Add an SQL statement that returns a single row with two-columns, SQL_OUTPUT and FIELD_VALUE. Specify the field name in SQL_OUTPUT column, the field name specified as SQL_OUTPUT is used as DefaultFromSQL preference value. FIELD_VALUE column should contain the value that gets defaulted in the mobile app.
- If required, use parameter SL_USER_NAME to filter records using username accessing the mobile app.
- NOTE: The SQL query specified in /custom/SL_Templates/MobileCreateReq/UserSQLDefaultsReport gets executed when the user logs in after entering their username and password.
b. Specify Preference using DefaultFromSQL: Enter the value of DefaultFromSQL Preference the value in SQL_OUTPUT field in UserSQLDefaultsReport report. Example, if the value of SQL_OUTPUT field is PREPARER_NAME, then enter DefaultFromSQL[PREPARER_NAME] in the Preference.
In the Fields Setup section, the value specified in DefaultFromSQL Preference appears with “SQL:” prefix. Example, the user sees SQL:PREPARER_NAME as the value in the Field Setup. When the user creates a Requisition, they see the FIELD_VALUE fetched from the SQL statement.
By default, the user can override the default value in the mobile app. To stop the users from overriding default value use preference UserOverride.
Defaulting field values
The following data flow demonstrates how data gets defaulted in the mobile app.
Step 2. Setup FieldsSetupVersion preference
After configuring Lookup Type linked with the mobile app for user validation, it is mandatory to setup FieldsSetupVersion preference in the lookup. FieldsSetupVersion preference value is used to control if Requisition fields should refresh in the mobile app using the latest setup in SL_REQUISITIONING_FIELDS_SETUP Lookup Type. The following flow highlights how FieldsSetupVersion preference triggers the operation to refresh fields from SL_REQUISITIONING_FIELDS_SETUP Lookup Type in the mobile app.
Admin Guide
The instructions to administer the Requisitioning app are common across all Simplified Loader applications. Click here to view the Admin Guide. Additionally, the administrator can centrally control the mobile app’s fields by following the First Time Setup instructions.
User Guide
The instructions to setup app for first-time usage and login are common across all Simplified Loader applications. Click on the links below to setup and login into SL Requisitioning app
1. First-time app setup
2. Login
Requisitioning Page
After a successful login, the Requisitioning page is displayed to the user. This page contains four sections,
1. Setup: The Setup button is located at the top right-hand side of the Requisitioning page. The Setup page allows retrieving lookup values from Oracle Fusion and to set up fields used for entering Requisition. Click here to read more about the Setup page.
2. Create Requisition: The top part of the Requisitioning page contains navigation to create a new Requisition based on the fields setup. Click here to read more about Create Requisition.
3. Review and edit existing Requisitions: The user can review, edit, duplicate, or delete Requisitions entered using the mobile app. The changes (editing, copying, or deleting Requisition) performed using this section are not sent immediately to Oracle Fusion. Example, duplicating Requisition in the mobile app will create a copy in the mobile app only and not in Oracle Fusion. Similarly, deleting a Requisition from the mobile app will only delete from the mobile app and not from Oracle Fusion. The only operation that sends Requisition details to Oracle Fusion is the Submit button in the Create Requisition page.
4. Logout: The Logout button is located at the top left-hand side of the Requisitioning page. The Logout button takes the user back to the login page.
Setup
The Setup page allows retrieving lookup values from Oracle Fusion and to set up fields used for entering Requisition.
Lookup Values
Use the Lookup Values section to pull the latest lookup values list from Oracle Fusion. The user should refresh lookups on a need by basis. To start the lookup process, click on the Refresh Lookups button. After successful lookup values refresh, the last refresh date/time is displayed next to the Refresh Lookups button.
Fields Setup
Fields Setup section displays all fields based on the configuration in Configure fields used by the mobile user. For each Requisition field, this section shows the following four details:
1. Default value – Setup by Admin: This is a read-only field and displays the default value set up by the administrator.
2. Default value – User Override: Use this field to enter the default value. When creating a new Requisition or Requisition Line or Distribution, the value entered in this field will get defaulted on Requisition.
The administrator may choose to disable data override on a field. In such cases, the ‘Default value – User Override’ field will display as a read-only field.
3. Show field – Setup by Admin: This is a read-only field to indicate if an administrator wants to display a field in Create Requisition page.
4. Show field – User Override: Use this field to override the ‘Show field’ default behaviour set up by the administrator.
Create Requisition
The Create Requisition page allows entering Requisition Header, Line, and Distribution details. The user can click on the magnifying lens to search values downloaded using Refresh Lookups operation. After completing data input in all fields, click the Submit button to send Requisition details to Oracle Fusion. When submitting Requisition, the mobile app validates if data is entered in all mandatory fields. As part of the Submit operation, the mobile app populates Load Status to indicate if Requisition is successfully created in Oracle Fusion. In the case of failure, the failure message is populated in the Error Message field.