Publication Date: 11/12/2024
![]() ![]() ![]() ![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Inventory Initial Provision LoadThe Inventory Initial Provision Load is a program used mainly by new users to generate their open status Purchase Order data from the previous system. By doing so, the Inventory Initial Provision Load will create Order Headers for each vendor within the import file and create a detail item for each part number required and quantity required in the Purchase Order Detail for receiving. The program will read a tab delimited text file (.txt) and enter the parts. Once a new aircraft has been created, or a new type series, the user can utilize the Initial Provision Load option to load parts into the system that will be needed for maintenance at a later time. Note: All the part numbers and vendors need to be known in the system before they can be imported. Note: Only the Part Number, Vendor, Description, Price and Quantity fields are mandatory for this import file. Many of the fields are only required for column positioning during the import, but may remain null. These fields are not imported into the system and may only be relevant to the customer. Note: The Part Number, Vendor and Unit of Measurement need to be known to the system before they can be imported. First, the user must prepare the file. For information regarding how to prepare the import file, refer to Preparing File For Import, via the Import Button of the System Standards Training Manual. Criteria for Inventory Initial Provision Load Import file:
Be sure to select the ‘First Line is Header’checkbox if the first line in your file is not the first data row schema but a header line. From the Import From File window complete all of the Import steps. For information regarding how to Import a file, refer to Importing a File via Import Button of the System Standards Training Manual. The Inventory Provision Load window will appear. Populate all mandatory information and select the Save Complete the following fields for the parts to import: _____________________________________________________________________________________ Location The Location for maintenance events, inventory stores, orders, transactions, or training events. This is the inventory location where the parts are to be received. Priority The priority placed on the transaction (e.g., routine, AOG, etc.). For additional information and functionality, refer to the Priority transaction code via the Orders Transaction Codes. Condition The condition of the part. Delivery Date The date when the part(s) is/are expected to be received. UOM The unit of measure. This will default if associated with a Part Number as defined in the P/N Master. Transactions for parts can be conducted in a different UOM than defined in the P/N Master. However, upon receiving the UOM, conversion will automatically adjust the quantities, providing that the conversion rate is defined in the UOM System Transaction Code (via Setting/Explorer/System Transaction Code). G/L The General Ledger account(s) reference used for financial control throughout the system. _____________________________________________________________________________________ |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Top of Page |
Publication Date: 11/12/2024
![]() ![]() ![]() ![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||