Acquisition Process in GFEBS (1 of 2)

Material Master Data

Sub-process encompasses the creation and maintenance of Material Master Data.

The main activity associated with this sub-process is as follows:

To perform Material Configuration, or the sourcing, maintenance and application

of Material Master Data.

Vendor Master Data

Sub-process encompasses the creation and maintenance of Vendor Master Data.

The activities within this sub-process are:

•Create Vendor Master Data: Manually create or receive Vendor Master Data from the Army Enterprise System Integration Program (AESIP)

•Process Vendor Master Data: Manage and maintain Vendor Master Data

The Procurement Sub-process includes all the steps necessary to purchase goods and services. The activities associated with this sub-process are:

Create / Change

1. Purchase Requisition (PR): Create a PR for goods or services which after fund certification results in a commitment of funds

2. Purchase Order (PO): Create, process and change a PO for obligations

3. Goods Receipt (GR): Receive and accept goods or services

4. Goods Acceptance (GA): Match a GR and a goods acceptance (GA) document to a PO.

5. Funds Commitment Document: Create a simultaneous commitment and obligation in GFEBS using a funds commitment document. Change can occur both manually and through an interface

a. Funds Pre-Commitment Document: In GFEBS, this document is a method to record a line of accounting (LOA) which will be cited by incoming obligation interfaces, such as AccessOnline (AXOL) and the Funds Control lesson (FCM)

Purchase Requisition (PR) Approval:

Within the PR activity, there are multiple steps, approvals and outcomes. After a PR is approved, GFEBS changes the PR status from "Blocked" to "Unblocked." If the approved PR is created with the Standard Procurement System (SPS) PR document type, it is transmitted to the SPS contract writing system. If the approved PR is for a Military Interdepartmental Purchase Request (MIPR), the Department of Defense (DD) Form 448 can be printed using GFEBS and sent to the performing agency. If the PR is created with the Miscellaneous Pay document type, it will not be subject to the PR approval workflow.