Logic for verifying the destination type of a purchase order

-- Validation Logic:
-- If not null, validate destination_type_code based on item_status,
-- Accrue_on_receipt_flag, transaction_flow_header_id;
--
-- Validation Business Rules
-- Item status
-- 'O' = outside processing item
-- Destination type must be SHOP FLOOR
-- 'E' = item stockable in the org
-- Destination type cannot be SHOP FLOOR
-- 'D' = item defined but not stockable in org
---Destination type must be EXPENSE
-- Null = item not defined in org
--
-- Accrue on receept
-- 'N'-destination type must be expense
-- 'Y'-if expense_accrual = PERIOD END
-- Then destination type code cannot be EXPENSE
-- Cannot be INVENTORY if item_id is null.
-- If SHIKYU item, then dest type code must be INVENTORY.

That is to say, the value of the destination type of the item depends on the status of the item, the acceptance identifier, and transaction_flow_header_id.

These verification logics are valid when purchasing orders are added, but are there any restrictions when purchasing orders.

The type of destination affects the generation of accounting subjects.