E1: 42: Sales Update (R42800) Fetch Unsuccessful (017F) And Posting Edit Code Does Not Allow Entry (0069) Errors Written to Work Center With Flex Accounting Active (Doc ID 2441685.1)

Last updated on APRIL 19, 2023

Applies to:

Symptoms

When attempting to process sales order 4876101 SA through Sales Update (R42800) the job fails and following errors are sent to the work center.

Fetch Unsuccessful (017F)
CAUSE: An error occured while fetching a record.
RESOLUTION: Verify that the record being fetched is valid.

Posting Edit Code Does Not Allow Entry (0069)
CAUSE: The posting edit code does not allow transactions to be posted to this account.
RESOLUTION: Blank - all postings are allowed. 'N' - the Account or Business Unit does not allow posting. 'B' - only budgets may be entered for an account. 'S' or 'L' - a subledger and type must be entered for all transactions. 'X' - a subledger and type are not allowed for any transactions. 'I' - the account is inactive, posting is not allowed. 'K' - the final budget is "Locked" or frozen and budget changes must be entered using journal entries. 'U' - units are required for all transactions. 'M' - only machine generated transactions are allowed for this account. The posting edit code is defined for business units in the Business Unit Master file (F0006) using Single Business Unit Revisions or Job Master Setup. The posting edit is defined for accounts in the Account Master file (F0901) using G/L Account Structure programs and Job Cost Basic/Speed Budget Setup.

The issue can be reproduced at will with the following steps:

1. Run Sales Update (R42800) Version AWM0002
2. Enter sales order 4876101 SA in the data selection
3. Check the PDF Report and notice the Job Fails
4. Check the Work Center and note the following errors
   1.   Fetch Unsuccessful (017F)
   2.   Posting Edit Code Does Not Allow Entry (0069)

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.