Which cross-field validation example best illustrates a DPAS transaction rule?

• A. If transaction type is Return, asset must be damaged.
• B. If transaction type is Adjust, asset location must be null.
• C. If transaction type is Issue, asset must be On-hand and location must belong to issuing organization.
• D. If transaction type is Issue, asset must be on loan.

Answer: (C)

Cross-field validation ensures a chosen transaction type only proceeds when related fields line up logically across the record. For issuing an asset, the rule that the asset must be On-hand and its location must belong to the issuing organization captures two essential checks at once: the asset is actually available (on-hand) and the issuer has custody and control over where it’s kept. This prevents attempting to issue something that isn’t in stock or isn’t under the issuer’s control, which is exactly the kind of integrity the DPAS system needs.

Other scenarios don’t demonstrate this cross-field integrity as clearly. Returning a damaged asset, or adjusting with a null location, or issuing an asset that’s already on loan either don’t reflect a consistent, real-world workflow or rely on less directly related fields. The combination of on-hand status and proper ownership/location with the issuing action best embodies cross-field validation in DPAS.