Your client has posted a fixed asset journal entry to the G/L but is getting errors when trying to post the entry to fixed assets. Which two statements correctly indicate reasons for the entry not getting posted?

In JD Edwards EnterpriseOne, posting a General Ledger journal entry to Fixed Assets updates the Asset Account Balances File (F1202). For this process to succeed, specific prerequisites must be met. The system strictly requires a valid asset number on the transaction to identify which asset's balances to update. If the entry does not contain an asset number, the system generates an error and halts the post. Additionally, the Fixed Asset Post Code must be blank, indicating it is unposted. If the entry has a Fixed Asset Post Code of 'P', it signifies the transaction has already been posted to Fixed Assets. Attempting to post it again will result in an error or cause the system to bypass the record to prevent duplicate accounting entries.

Option B: A blank hold code indicates the transaction is not on hold, which makes it eligible for posting rather than causing an error.
Option C: A General Ledger post code of 'P' (Posted) is a mandatory prerequisite for posting to Fixed Assets, not a reason for failure.
Option D: The transaction's account must fall within the FX AAI range to be recognized as a fixed asset entry; this is a requirement, not an error cause.

Oracle Corporation. JD Edwards EnterpriseOne Applications Fixed Assets Implementation Guide (Release 9.2). Document E63914-11. Chapter 6: "Processing G/L to Fixed Assets," Section 6.1: "Understanding G/L to Fixed Assets Processing."

Oracle Corporation. JD Edwards EnterpriseOne Applications Fixed Assets Implementation Guide (Release 9.2). Document E63914-11. Chapter 6: "Processing G/L to Fixed Assets," Section 6.4: "Posting G/L Entries to Fixed Assets" (Prerequisites and Error Messages).