Cyclic LOGREP Schedule of Events: A Step-by-Step Guide

Instead of having one cycle working at a time, the activity will have an active record of all LOGREP Cycles for the past 12 months. In addition, future LOGREP Cycles can be loaded and prepared in advance if needed. One LOGREP Cycle can be assigned to multiple Customers in the event that several Customers submitted LOGREP Request at the same time (i.e. Battle Group customers).

Incoming requisitions (in MILSTRIP format) are fed into a batch process - Batch Job number JSS220. The incoming LOGREP Requests were uploaded in Step #3.

 

Report ID JSS220A & JSS220AR are produce after completion of Batch Job JSS220. Report JSS220A will be in three headings: ‘INCOMING STATUS FOR SUPPLY, CARCASS AND MOV’, ‘INCOMING REFERRAL REQUESTS AND LOGREP/REFERRAL STATUS’, and ‘INCOMING PREVIOUSLY SUBMITTED SUPPLY AF/AT/AM/AC/AK’.

Report JSS220AR “INCOMING REQUISTIONS SUMMARY LISTING” lists all incoming LOGREP Requests. This portion of the report (Report ID JSS220AR) must be included in the customer’s LOGREP Package so the customer can verify what they have sent to the Supply Ship .

 

Note: Prepare an envelop and label it with the customer ’s UIC. This envelop will contain all documents that will be handed to the customer during the UNREP.

This step is critical and must be performed. Go to: Log>Suspense then select LOGREP Requests function. Any suspended transactions must be processed before you proceed to the next step (Activate Customer Requirements). Otherwise, these requests will not be included in the expenditures listing for the particular LOGREP Cycle. In the event that the suspended transactions were not processed, you may delete the transactions from the suspense module (take notes of the reason for suspension so you can make the corrections) and use ‘Material Requirements – External’ function to process these transactions or refer to Step #13a or if the reason for suspension is “Not Carried”, you may manually prepare and send an “AE8” with “CA” status to the customer. The status can be included in Step #6b or Step #15.

This Batch Job will match all LOGREP Requests in the queue to the 'stock_item' table and set the items for "Hatch Sheets" and printing of "Picking Tickets". Statuses (AE8/A41) will be created for transmission to the customers (See Step #6b).

Notes:

(1) You must generate the ‘Activate Requirements’ twice if you are processing requirements from USNS ships using Service Designator of “N” with UIC.  Transferring End-use requirements to another USNS Ship that consists of 1Q cog (“XP” fund code) and other FILL/HULL/9M cog items.

First Run: Generate the ‘Activate Requirements’ selecting the LOGREP Cycle Number and UIC. (Make sure the Service Code of this UIC at the ‘Other Activities’ table is equal to “N”. DO NOT set the Cash Sales indicator.) The first run should set the ‘Activate Date’ for LOGREP Requirements with non-XP fund code. After completion of the first run, perform query of a LOGREP Requirement with an “XP” fund code. The ‘Activate Date’ should be blank.

Second Run: Generate the ‘Activate Requirements’ for the second time. Make sure to set the “Cash Sales” indicator (Both the Cash Sales checkbox and the Cash Sales Non-local radio button on the ‘Cash Sale' option block.) After completion of the second run, perform queries to some of the LOGREP requirements (Both XP and non-XP fund code on this LOGREP Cycle Number to ensure all LOGREP transactions have an ‘Activate Date’ set. If everything is OK, proceed to the next Step (Either Step #6b or Step #7).

(2) Set Cash Sale Indicator. This indicator must be set if the transactions you are processing are Cash Sales either cash collected locally or not.

(3) Set Load-to-Load (LTL) Indicator. (This is required only for CLF Activities with Service Designator of “V or R”- NWCF/DWCF units). This indicator must be set when transferring NWCF/DWCF material between CLF units.  Ensure Color Code is different from UIC with service designator of “N” (End-use account).

(4) Batch Job JSI302 (Activate Requirements) will produce Report ID JSI302AR in various headers. Review the report. If the LOGREP Cycle consists of two or more customers, pay attention of the report header that says “ACTIVATE REQUIREMENTS RATION CANDIDATES REPORT”. If Ration Candidates are present, you must run Step #6c to ration the quantity to various customers. This happens when you (the Supply Ship) do not have enough onhand to fill each customer's request requesting the same item in any given LOGREP Cycle process.

This process will generate billings for all transactions processed in Step #11.  Ensure DD 1348-1A (1Q Cog) and DD 1149 documents (Cash Sales Report) were generated and included in customer’s billing package.  Recommend 2 copies, 1 copy for customer billing package and 1 copy to be retained in customer’s completed LOGREP folder. 

 

Notes:

(1) Batch Job JSI285 will produce hard copy output (Report ID: SL3530AR) and generate electronic X71 transactions. Copy of this report will be included in the customer’s LOGREP Package.

 

(2) X71 transactions (located at h/data/local/SUP1BT/tape_out) … menu path: File>Utilities>Batch Review>Output File) must be downloaded (Using File Transfer) into CD for inclusion to the customer’s LOGREP Package. These X71 transactions can be used by the customer to automate the receipt processing. If File Transfer does not work, select and open the file then highlight the transactions to copy (Ctrl + C) and paste into ‘Notepad’ (Ctrl + V). Print a hard copy of the file and include it (with CD) in the customer's LOGREP Package.

(3) If batch job number JSI285 did not produced the actual invoice/billing package listing on the first run (Step 12), run/process another batch job to print "Duplicate Invoice/Billing Package" listing for subject customer/UIC." - Path: Inventory>Management> Inventory Actions>LOGREP Processing>Produce Invoice/Billing Package

Supplemental LOGREP requirements can be added at this point. If it happens, follow Steps #3 through #11).

Note: Supplemental LOGREP Requirements are defined as additional requirements from the customers included in this current LOGREP Cycle Number.

This Batch Job (JSI280) completes the LOGREP cycle process. Shipment status are generated at this point and are written in 'logrep_status_out' table. This batch job generates a hard copy output (Report ID: SL3530AR).

 

Highly recommended to run the Reports listed below after completion of the LOGREP Cycle.

(Data from these reports maybe utilized for the monthly submission of your Supply Effectiveness report to your TYCOM)