Property Document Type e-mail flow

The purpose of this was to expand the use of the CAGE-Code-to-Contractor-DoDAAC link to allow the Contractor Property roles requested at the CAGE Code level to cover all contractor DoDAACs which are tied to that CAGE Code.

The CAGE Code / Contractor DoDAAC relationship does not change.

Users will only have to register for a Property Role at the “CAGE Code” level to gain access to property documents for the Contractor DoDAACs assigned to that CAGE Code.

Contractor Property user may elect to originate a property document using their CAGE Code or an associated Contractor DoDAAC.

CAGE-to-Contractor-DoDAAC link for Property Transfers Demo:

The purpose of this was to modify DAAS to route the EDI 856S to WAWF via GEX. GEX should create the 856 from the 856S and send it to WAWF.

Shipment:

For Government to Contractor Shipments:

• WAWF should drop any transactions where the ship-to location code is not signed up as a property receiver.
• WAWF should extract the 856_GFP Shipment to the property receiver if the user is signed up to receive EDI extracts.

For Contractor to Government Shipments:

• WAWF should allow transactions where the ship-to DoDAAC is not signed up as a property receiver.

Receipt:

GEX should route the 527R to PIEE with no translation.

The PTD created by the 856S can be closed:

• On the web through a GFP receipt
• Using an EDI 856_GFP Receipt
• Using a 527R Receipt
• Through a parameter based auto-close feature

IUID Registry Updating:

For government to contractor property transfers:

• Update the Registry upon contractor receipt.

For contractor to government property transfers:

• Update the Registry upon contractor shipment.
• Update the Registry again upon government receipt.

All data will be captured in the EDA Database.

The Government Property Transfer Role API allows automated request/response for GFP roles based on location code.

An API will be in place to automate system-to-system querying of GFP for all GFP Government roles and the following property roles:

• Contractor Property Shipper
• Contractor Property Receiver

Government Property Transfer Role API Demo:

Multiple Serial Numbers for Non-UII Items serves to capture and transmit serial numbers for item quantities > 1 per line item when the items are GFP and not UII’d. This multiple serial number functionality has been added to the Reparable Receiving Report and Property Transfer documents.

In addition, the multiple serial number functionality has been added to the appropriate Wide Area Workflow extracts/database inserts such as PSN and the IUID Registry.

Multiple Serial Numbers for Non-UII Items and Add Condition Code Demo:

The Supply Condition code is on the Property Transfer and Reparables Receiving Reports:

• At the line level
• On the UID Tab for UID’d items

The approved Supply Condition Code list (same as in Registry) will be used and will be a drop down on the web.

The Supply Condition Codes will be:

• Added to EDI and Flat File formats of Property Transfer and the Reparables Receiving Report.
• Included in data injected into IUID Registry; update the Registry Supply condition code.
• Included in transactions sent to Accountable Property System of Record (APSRs) and Repair systems.
• This applies to both UID’d and nonUID’d items.
• Supply Condition Code on Property Transfer and Reparables Receiving Reports will be optional.