Understanding GUI/VAT Generation for Multiple Accounts Receivable and Sales Order Transactions

You use the GUI/VAT Creation From Multi-AR program (R75T004S) and the to create government uniform invoices (GUIs) for records that have GUI/VAT Creation from Multi-SO program (R75T004O) been created in the JD Edwards EnterpriseOne Accounts Receivable system or in the JD Edwards EnterpriseOne Sales Order Management system. When you run these programs in final mode, the system assigns GUI numbers to the transactions for which the GUI number has not been assigned.

Note: For GUI transactions that are generated prior to being processed through the Update Customer Sales program (R42800), the Pay Item field in the GUI/VAT Transaction Detail table (F75T005) is blank. This Pay Item field is updated during the Update Customer Sales process when the Customer Ledger table (F03B11) is updated.

The GUI/VAT Creation From Multi-AR program processes records from table F03B11. The GUI/VAT Creation From Multi-SO program processes records from the Sales Order Detail File table (F4211).

The GUI/VAT Creation From Multi-AR and GUI/VAT Creation From Multi-SO programs first create temporary records in the GUI/VAT Transaction Header – Work table (F75T004Z) and the GUI/VAT Transaction Detail – Work table (F75T005Z) from multiple records in tables F03B11 or F4211. The programs then create GUI records in the GUI/VAT Transaction Header table (F75T004) and the GUI/VAT Transaction Detail table (F75T005) from the temporary records in tables F75T004Z and F75T005Z.

You can use the processing options to specify whether to merge all records for a single customer into one GUI record or to create separate GUI records for each transaction.

To create the GUI Number for a sales order that uses Use Taxed Price (UTP) logic, the GUI/VAT Creation From Multi-SO program first checks for the Sales Taxed Price constant (TPSC) in the F4009T1 table. If this constant is turned on, then the system verifies if the SO uses the UTP logic. To verify this, the system checks the value of UTP in the F4201TX table. If the system does not obtain any result from this table, the system tries to retrieve the value of UTP from the F42019TX table. If the value of UTP is 1, the GUI/VAT Creation From Multi-SO program retrieves the taxed prices for the order from the business view V75T421T. This view contains data from F4211TX and F42119TX tables. The system retrieves this data from a combination of two tables because when you run this report after the Sales Update process, the system may have purged the data in F4201TX and F4211TX tables to F42019TX and F42119TX tables, respectively. Therefore, if the system does not retrieve any UTP value from the F4201TX table, it tries to retrieve the value from the F42019TX table.

In the case of sales orders with UTP logic, the system performs no tax calculation. It retrieves the taxable amount from F4211 or F42119 table and the taxed extended price based on tax and gross amount from the F4211TX or F42119TX table.

For the orders that use UTP logic, the system displays taxed extended prices in the Extended Price column of the report and displays a message 'The Extended Prices for the above order include taxes' in the Process Description column of the report.

Note: The GUI/VAT Creation From Multi-AR and GUI/VAT Creation From Multi-SO programs process only transactions for which a GUI number does not already exist.

The system uses the GUI/VAT Number Segment table (F75T003) to keep track of the last-used GUI date and next available GUI number. During the creation of GUI records, the system locks the GUI number segment that it is using to prevent other users from using the same GUI segment numbers.

When the process of creating GUI records in tables F75T004 and F75T005 is finished, the system deletes the temporary records in tables F75T004Z and F75T005Z unless you specify in the processing options of the GUI/VAT Creation From Multi-AR program or GUI/VAT Creation From Multi-SO that the records should be saved for troubleshooting.

Both programs produce reports of the transaction records that are processed and the resulting GUI/VAT records. The reports also list any errors that have occurred during the process.

The programs automatically print the GUIs that they create if you set up the processing options to do so. The system uses the print program that you specified when you set up the GUI/VAT declaration site.

Note:

Do not select the Invoice Consolidation check box on the Billing Information form because invoice consolidation cause multiple sales order numbers to be matched to one invoice number.

Similarly, do not use the Summarize AR Entries by Invoice processing option in the Update Customer Sales program because this option causes related sales order lines to be summarized into one invoice.