1Z0-342 Sample Questions & Answers

During the write step of the automatic payment process, the system calls a specific print program (like R04572 for checks) based on the Payment Instrument Defaults. If this program is not defined correctly, has data selection that excludes the payments, or fails to run for any reason, the payment group will get stuck in a 'Write in Process' or similar status without generating payments. The system is waiting for the print UBE to complete successfully and provide feedback.

The integration between Accounts Payable and Fixed Assets is primarily controlled by the FX range in the Fixed Assets AAIs. When a voucher is posted to a GL account that falls within this defined range, the system recognizes it as a fixed asset acquisition. It then automatically creates a corresponding record in the F1202 Unposted Fixed Assets Ledger, which can then be processed to create the final asset master record in the F1201.

The 'Trial Balance by Ledger Type' report (R094121) is designed to show balances as of a specific point in time. The 'Thru Period' processing option specifies the ending period for the balance calculation (in this case, March, which is period 3). Leaving the 'From Period' blank instructs the report to calculate balances from the beginning of the fiscal year through the specified period, which is the standard behavior for a trial balance.

The Delinquency Policy is the core component that defines the rules for sending notices, including which notice text to use based on the aging of the customer's oldest invoice.

This program is used to create the actual boilerplate text that will be printed on the delinquency notices. The policies defined in P03B20 will reference this text.

The system needs to know which policy applies to which customer. This link is made in the Customer Master record, allowing for different policies to be applied to different types of customers.

OVFS relies on a predefined set of business views for data access. To include a custom table, it must first be registered as a valid data source. This is done in the Financial Report Data Source application (P09015), which allows an administrator to define a business view over the custom table and make it accessible to the OVFS design tool. Without this step, OVFS will not be aware of the custom table.

The Company Names & Numbers program (P0010) is where the fundamental parameters for a company are set. This includes assigning the Fiscal Date Pattern (e.g., 'R' for a standard calendar year) and setting the 'Current Period' and 'Current Year'. Setting these values effectively opens the accounting periods for transaction entry. The General Accounting Constants (P0000) control system-wide settings but not company-specific period management.

The primary function of the Fixed Assets Annual Close (R12825) is to roll forward the asset balances. It takes the ending accumulated depreciation and cost amounts from the current year and populates them into the beginning balance fields for the next fiscal year in the F1202 table. This is a critical step to ensure that depreciation calculations for the new year start with the correct opening balances. It does not post to the GL or handle disposals.

For transactional processing, the system uses the G/L Date of the document to find the corresponding effective exchange rate in the Currency Exchange Rates table (F0015). The rate effective on that date for the specified currency pair (e.g., EUR to USD) is used to calculate the domestic amount. This ensures that transactions are recorded using the appropriate historical rate.

The Voucher JE Redistribution program (P042002) is specifically designed to correct the G/L account on the distribution lines (F0911 records) of an already posted voucher. This process creates auditable journal entries to move the expense from the incorrect account to the correct one, without altering the original posted voucher transaction in the AP ledger (F0411). This maintains the integrity of the subledger while correcting the general ledger.

The Address Book is a foundational component of JD Edwards EnterpriseOne. The data is stored at a system level (not company-specific) in tables like F0101. This means that an entity, identified by its Address Book Number, is the same entity regardless of which company is transacting with it. Company-specific information, such as customer or supplier terms, is stored in separate tables (e.g., F03012, F0401) that link back to the central Address Book number.