1.5k likes | 1.71k Views
INTERFACE PROCESSING. UPON COMPLETION OF THIS COURSE, THE STUDENT WILL BE ABLE TO: DESCRIBE ACTIVATE / DEACTIVATE INTERFACE DESCRIBE EXTERNAL RECORD EXTRACT DESCRIBE OUTGOING / INCOMING RECORDS DESCRIBE NALCOMIS and R-SUPPLY INTERFACE. INTERFACE PROCESSING. INTERFACE PROCESS.
E N D
INTERFACE PROCESSING • UPON COMPLETION OF THIS COURSE, THE • STUDENT WILL BE ABLE TO: • DESCRIBE ACTIVATE / DEACTIVATE INTERFACE • DESCRIBE EXTERNAL RECORD EXTRACT • DESCRIBE OUTGOING / INCOMING RECORDS • DESCRIBE NALCOMIS and R-SUPPLY INTERFACE
INTERFACE PROCESSING INTERFACE PROCESS
INTERFACE PROCESSING The interface is the most important aspect of Inventory and Requisition management-why? • Every inventory action in both systems writes through the interface- • work the interface-maintain a mirror image • What happens to all those discrepancies that appear monthly on the • reconciliation's-they no longer appear because they are corrected as • they occur • What happens to all those unobligated charges you receive on the • monthly SFOEDL-they no longer appear because they are obligated daily • What happens to all those interface errors for receipts not posted or • requisitions not on file-you guessed it-they go away • It’s a pay me now or later situation-the choice is yours-a little time • expended each day or a major project at the end of the month
INTERFACE PROCESSING General Processing Information The following general guidelines and processing tips are intended to enhance the interface record management process. The interface record process has a major impact not only on inventory accuracy and financial management, but system response time as well.
INTERFACE PROCESSING REVIEWS You should review all interface processes daily so that you can identify and mitigate potential or existing problems such as these: · Invalid records received from the host supply system. These could be status records received for requisitions not managed by Optimized NALCOMIS IMA (for example, Consumable Stock, Flight Operations, or Public Works). If this happens, notify the Central Design Agency for the host supply system immediately and initiate the applicable Program Procedural Trouble Report (PPTR) or Trouble Report (TR).
INTERFACE PROCESSING · Outgoing internal interface records that are over 1 day old. This would indicate a significant problem within the host supply system because it means no Match and Delete response has been received from it. (The host supply system should send a response for the Match and Delete process in most instances.) You should conduct an immediate review to determine why. In some instances, the host supply system's Suspense process may not be being worked on a timely basis. If the records were processed, there may be an echo back problem. If a problem is located in this process, immediately initiate a PPTR or TR and, if you do not expect any echo back, delete the records manually.
INTERFACE PROCESSING · Maintenance of both Outgoing and Incoming Interface process records in excess of 1 day. At no time should both be maintained for over 1 day because doing so will seriously degrade system response time, burdening other system users, potential inventory discrepancies, parts not issued on time, etc.
INTERFACE PROCESSING REPORTS Reports should be processed daily. Status comes in daily so the reports should be worked daily. The more you work them, the smaller the reports should be. Interface Protocol See the online UADPS-U2 Interface Protocol or R-Supply Interface Protocol for a synopsis of the on-line interface protocol processes.
INTERFACE PROCESSING ACTIVATE / DEACTIVATE INTERFACE - CONTROL
As a part of your daily regimen, you should ensure that the outgoing interface is running. This can be done by viewing the NALCOMIS batch job que in NTCSS.
Right click on tob bar of NTCSS window and select the Batch Job Queue
Check to ensure that the Outgoing Interface Daemon is running.
Occasionally the outgoing interface will not appear in the NTCSS batch job que. If it is not, then proceed to the interface control section of the system subsystem to start up the NALCOMIS interface. The RSUP FAS should be doing the same for RSUP on a daily basis.
OUTGOING INCOMING Toggle from Inactive to Active and then click save. SAVE
ACTIVATE / DEACTIVATE INTERFACE - CONTROL This window allows you to control the status of outgoing and incoming interface transmissions. Menu Path: From the System Subsystem: INTERFACE>CONTROL 1. Select an option under Outgoing Interface Status: - Active allows your site to transmit outgoing interface records to the host supply system (RSupply or UADPS-U2). - Inactive deactivates the transmission process, meaning no outgoing records will be transmitted to the host supply system. Instead they will be queued on the server until the status is changed back to Active.
ACTIVATE / DEACTIVATE INTERFACE - CONTROL 2. Select an option under Incoming Interface Status: - Active allows your site to process incoming interface records from the host supply system (RSupply or UADPS-U2). - Inactive Deactivates the transmission process, meaning no incoming records from the host supply system will be processed. Incoming interface records are either solicited or unsolicited. Solicited records confirm receipt and processing by the host supply system. Unsolicited records are also from the host supply system, but they are forwarded to NALCOMIS IMA for update because of a supply action. 3. Click Save.
INTERFACE PROCESSING EXTERNAL RECORD EXTRACT
EXTERNAL RECORD EXTRACT • FREQUENCY: • DAILY BATCH PROCESS • - THREE TIMES DAILY” • Allows for Creation of a diskette to be loaded into SALTS • for requisitions to be passed off station
EXTERNAL RECORD EXTRACT SUPPORT PROCEDURES: Verify “MILSTRIP Documents” before running “EXTRACT” System >Interface > Outgoing Reports Select “External” Folder
One Record for “Extract” Click on “Close”
EXTERNAL RECORD EXTRACT SUPPORT PROCEDURES: Go ahead and RUN “External Record Extract” System > Interface > External Record Extract
Select “External Record Extract” and then “MILSTRIP”
1. Copy “E60450057” 2. Click on “Yes” Recommend selecting “yes”. This will give you a copy of the batch number which will be required later for file transfer 3. Click on “Ok”
EXTERNAL RECORD EXTRACT SUPPORT PROCEDURES: Go ahead and FTP the “Extract” from the SERVER System >Utility > File Transfer
1. Select “Receive From Server” 2. Save File to “Folder in your C:\Drive” (I.e. c:\program files\ntcss\oimacl\data\xfr) or A: Drive for SALTs processing 5. Click on “Ok” 4. Select “Save... 3. Select “File”
EXTERNAL RECORD EXTRACT SUPPORT PROCEDURES: Copy the “Extract” from the C:\Drive to a Disk (for Salts processing)
Open as ”NOTEPAD” Click on ”OK”
Go ahead and SAVE the “External Record Extract” to a DISK for SALTS PROCESSING
ANOTHER EXAMPLE THE FILE WOULD BE IN MILSTRIP FORMAT
EXTERNAL RECORD EXTRACT Congratulations !!!! You made it.. RUN on a “DAILY BASIS”
INTERFACE PROCESSING OUTGOING / INCOMING REPORTS
OUTGOING / INCOMING REPORTS OUTGOING REPORTS