1z0-1056-22 Oracle Financials Cloud: Receivables 2022 Implementation Professional Questions and Answers

Mapping Set

Supporting References

Transaction References

Description Rule

only after manual intervention

after 100 days

immediately

after 60 days

55

25

100

50

45

an inactive Journal Line Type

an inactive Accounting Method

an inactive Mapping Set

an inactive Journal Entry Rule Set

Sales credit tracking is required

FBDI Loader is required

Auto-Invoicing is required

Revenue accounting is required

state tax of $166.67 USD for the invoice, city tax of $16.67 USD, and an invoice total of $1,184.34 USD.

state tax of $166.67 USD for the invoice, city tax of $91.11 USD, and an invoice total of $1,257.78 USD.

state tax of $166.67 USD for the invoice, city tax of $91.11 USD, and an invoice total of $1,000 USD.

state tax of $200 USD for the invoice, city tax of $10 USD, and an invoice total of $1,210 USD.

state tax of $200 USD for the invoice, city tax of $100 USD, and an invoice total of $1,300 USD.

Create a Business Intelligence Publisher Report because you cannot create an OTBI Report for refunds.

Create an Oracle Business Intelligence Applications (OBIA) Report.

Query each customer refund and verify the Refund Status.

Create a Real Time Report by using Oracle Transactional Business Intelligence (OTBI).

The billing cycle does not have any impact on new transactions.

Existing transactions with no activity retain the old billing cycle.

Existing transactions with activity adapt the new billing cycle.

New transactions after this change inherit the new billing cycle.

Changing information on the Profile tab does not have an impact on the level at which collections are done.

Adding or modifying customer contact name on theContacts tab impacts where the correspondence is sent.

Making changes on the Profile tab impacts the collection process.

Business-unit-level changes will not impact the display of delinquent customers on the dashboard.

Changing the Collector impacts the individual working with the delinquent customer.

For Miscellaneous receipts, if the receivable activity tax rate code source is Activity for the activity type of Miscellaneous Cash, Receivables use the tax account that is defined on the receivable activity.

For Adjustments, if the receivable activity tax rate code source is Invoice, Receivables derive the tax account from auto-accounting.

For Adjustments, if the receivable activity tax rate code source is Invoice, Receivables use the tax account that is defined on thereceivable activity.

For Adjustments, if the receivable activity tax rate code source is Invoice, Receivables use the tax account of the tax code.

For Credit memos, if the profile "AR: Use Invoice Accounting for Credit Memos" is set to Yes, Receivables derive the item distribution from the invoice and the tax account from auto-accounting.

For Credit memos, if the profile "AR: Use Invoice Accounting for Credit Memos" is set to No, Receivables derive the tax account from auto-accounting.

Receipt Method

Profile option

Customer

AutoMatch Rule

System Options

Soft, Regular, Hard

Regular, Medium, Hard

Final Demand, Soft, Medium

Regular, Final Demand, Medium

Line-level transaction flexfield, Header-level transaction flexfield, Reference flexfield

Line-level transaction flexfield, Header-level transaction flexfield

Line-level transaction flexfield, Invoice transaction flexfield, Reference flexfield, Link to transaction flexfield

Line-level transaction flexfield, Header-level transaction flexfield, Link to transaction flexfield

The program allows the use of parent, child, and grandchild table hierarchies, but it requires multiple Customer Master records for each customer within the hierarchy.

The program allows table hierarchies for customer bank accounts, but not for other customer information.

No; the program contains parent, child, and grandchild table hierarchies to represent the hierarchy of data in the customer information.

Yes; the program specificallyprohibits parent, child, and grandchild table hierarchies to represent the hierarchy of data in the customer information.

The use of parent, child, and grandchild table hierarchies is allowed only in Accounts Payable, not Accounts Receivable.

Receivables can look at invoice and retrieve the tax rate code.

There is no need to retrieve the tax rate code.

Receivables can look at the adjustment activity and retrieve the tax rate code.

Receivables can look at System Options and retrieve the tax rate code.

20+ Days Link

0-10 Days Link

0-5 Days Link

10+Days Link

Previous Balance

Adjusted Balance

Overdue Transactions only

Average Daily Balance

Set "Minimum Transaction Amount" to 3,000 and "Minimum entered Currency" to USD.

Set "Minimum Transaction Amount" to 2,999.99 and "Minimum Entered Currency" to ALL

Define intercompany approval rule, to automatically reject intercompany transactions that do not meet the minimum amount requirement.

Set "Minimum Invoice Amount" to 3,000 and "Invoice Currency" to USD in Payables Invoice Options and Receivables System Options.

one customer account and one customer site with a bill-to site business purpose

one customer account without any customer site

one customer account with two sites: one with a bill-to business purpose and the other with a ship-to business purpose

one customer account and one customer site with a ship-to site business purpose