Applies to:

Oracle Field Service - Version 12.1.3 and laterInformation in this document applies to any platform.
***Checked for relevance on 06-SEP-2016**

Symptoms

On : 12.1.3 version,

When a parts requirement is created and this function creates an internal requisition and an internal order, the created requisition has a null value in the po_req_distributions_all.budget_account_id field. When the order is shipped and received, the corresponding receiving transactions fail in cost manager because the encumbrance account is not populated. Manually created requisitions work fine.

STEPS-----------------------The issue can be reproduced at will with the following steps:1. Create a parts requirement in Field Service 2. Create Order3. Ship the Order4. Cost the transaction5. Cost manager will complete with error

Changes

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a Million Knowledge Articles and hundreds of Community platforms