Jump to content

Welcome to The Motor Pool

Sign In 

Create Account
Welcome to The Motor Pool, like most online communities you must register to view or post in our community, but don't worry this is a simple free process that requires minimal information for you to signup. Be part of The Motor Pool by signing in or creating an account.
  • Ensure to register with a .mil acct, or register from an installation with a known IP address.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Customize your experience here
If you're having problems accessing your acct, watch this video to regain access. Contact us if you're having issues. Known issues: Internet Explorer (IE) 8 java verification code not visible, causing error "The security code you supplied did not match the one displayed, a new code has been generated, please try again" Solution: On top of page Click on "Disable All content" or Access using a later browser on a different computer..

The Motorpool Management
Guest Message by DevFuse

* * * * *

Global Combat Support System - POs, PRs and Release Strategy

Having issues understanding release strategy and zPARK? As Army units continue to be fielded GCSS-Wave II, it is apparent that some of us do not completely understand how GFEBS interacts with GCSS-A. I myself, have had several issues with the fielding. Since the whole system is role based, all of our screens in GCSS-A do not look the same and we all cannot access the same Tcodes. At the Company / Battalion level, we use ME5A to check zPARK, yet at the BDE RM level, they can access zPARK to allocate the funds for requisitions. It does not appear that all the players are on the same sheet of music.

I started Post Go Live Activities (PGLA) and resumed CLIX ordering last week. I think I may have cracked the code why BDE RMs are unable see CLIX requisitions. In SAMSE, SAMSE and PBUSE submitted Purchase Orders (POs) due to the fact that we had just a document number to track from SAMSE into GCSS-A. In GCSSA, we now submit Purchase requisitions (PRs) with the prefix 10XXXXXXXX which turn into Stock Transport Orders (STOs) with prefixes of 71XXXXXXXX (SSA) or 45XXXXXXXX (wholesale / national) which is considered a Purchase Order coming from the supported SSA. BDE RMs/G8s apparently did not get the memo that Wave II GCSSA requisitions require them to click the tab on the top of zPARK page that states "Purchase Requisitions". If they continue to pull purchase orders they cannot see our CLIX requisitions from the unit 910 DODAACs/SLOCs. They will only see unit requisitions from Wave I STAMIS users.
Release strategy hold codes:
A1 - ADP Computer Equipment
B1 - Controlled Material Numbers (NIINs)
C1 - Order Dollar Limit Restrictions
D1 - Order Quantity Limit Restrictions
E1 - Acquisition Advice Code (AAC)
F1 - Controlled Inventory Item (CIIC)
G1 - Reportable Item Category Code (RIIC)
H1 - Accounting Requirements Code (ARC)


The most common are D1 and E1. For instance: I currently have two items held in release strategy. They are rolls of wire for power generation that only come in a quantity of 500 with a unit of issue of SL (spool). Release strategy caught them because in AESIP, the quantity shows 500 but I only ordered 1 roll each. E1 is because maybe the part is terminal AAC V or Y and there is not a replacement NIIN in AESIP. This is where AESIP and FEDLOG and I2log may be different. I would first check FEDLOG to see if there is an alternate NIIN then go to i2log at https://lrcweb1.apg.army.mil/i2log/ to see if there is any item manager notes that reference a new NIIN. GCSSA uses AESIP for cataloging NIINs and is not always tracking what the item manager is.

  • MantieSC, car1ro, KevinJ64 and 3 others like this



Ordnance Coin

Posted Image

Buy Now close