1Z0-518 practice question 5 of 25

Several fields are required during manual Invoice entry. Which are the fields required at the header level?

Full set: 101 questions
Answer options
A: date, customer, source, type, GL date, legal entity
B: date, legal entity, bill-to, source, type, class, remit-to
C: terms, date, bill-to, source, legal entity, type, remit-to
D: date, customer, source, type, General Ledger (GL) date, class
E: date, source, class, type, GL date, legal entity, bill-to, terms, remit-to Correct answer
Correct Answer:
E. date, source, class, type, GL date, legal entity, bill-to, terms, remit-to
Explanation

Oracle Receivables requires specific mandatory fields at the invoice header level during manual entry. These include: Transaction Date (for recording when the transaction occurred), Source (to identify the invoice origin), Class (Invoice, Credit Memo, etc.), Type (to define transaction processing rules), GL Date (for accounting period determination), Legal Entity (for compliance and reporting), Bill-to Customer (to identify who receives the invoice), Payment Terms (to determine due dates), and Remit-to Address (to specify where payment should be sent).

Why Incorrect

A. Missing required fields: class, payment terms, remit-to address, and bill-to customer designation.
B. Missing GL date and payment terms which are mandatory for invoice processing.
C. Missing class field which is required to categorize the transaction type.
D. Missing legal entity, bill-to customer, payment terms, and remit-to address.

References

- Oracle Receivables User Guide Release 12.1, Part No. E13508-04, Chapter 7 "Transactions", Section "Creating Transactions Manually", Pages 7-15 to 7-18

- Oracle Receivables Implementation Guide Release 12.1, Part No. E13511-04, Chapter 3 "Transaction Setup", Section "Transaction Types", Pages 3-22 to 3-25

- Oracle E-Business Suite Concepts Release 12.1, Part No. B31181-06, Chapter 2 "Oracle E-Business Suite Architecture", Section "Legal Entity", Pages 2-8 to 2-9

Scroll to Top