Understanding Inbound Voucher

This chapter discusses the inbound voucher integration point.

Inbound Voucher

This section provides an overview and discusses:

• Inbound voucher assumptions.

• Voucher ID cross reference.

• Inquiring on voucher ID cross reference.

• Running the Inbound Transmissions Master Program.

• Setting processing options for Inbound Transmissions Master (R49T90).

Understanding Inbound Voucher

The Inbound Voucher integration point serves as the trigger to create vouchers for freight in the JD Edwards EnterpriseOne system. It is an approved, matched invoice sent from Oracle Transportation Management to JD Edwards EnterpriseOne to create vouchers for shipments. After receiving the message, the JD Edwards EnterpriseOne system:

• Extracts he basic voucher information such as company, service provider and so on, received from Oracle Transportation Management. The system does not perform data validation at this point. If the service provider is not valid within the JD Edwards EnterpriseOne system, this is edited only in the voucher process.

• Converts the data types to fit into JD Edwards EnterpriseOne as needed.

• Generates an EDI document number and gets the EDI document type from the Transportation Planning Integration Constants (F49T00) table.

• Updates the EDI Invoice Header (F47041), EDI Invoice Detail (F47042), and the EDI Invoice Summary (F47044) tables.

• Creates a cross reference in the Inbound Voucher Cross Reference table (F49T60).

After these things occur, you can run the Inbound EDI Voucher Edit/Create (R47041) program to create vouchers in the JD Edwards EnterpriseOne system.

Taxes

The Oracle Transportation Management system can send either or both the pre tax and the post tax (gross) amount. In the JD Edwards EnterpriseOne system, you must set up the service provider to whom the voucher is paid with tax information. If service-provider tax information does not exist in the JD Edwards EnterpriseOne system, the Oracle Transportation Management system transmits the gross. The tax logic is executed as follows:

• If Oracle Transportation Management sends only the gross amount (invoice amount after tax), JD Edwards EnterpriseOne updates the EDI tables with this amount as the gross. The accounts payable information from the service provider and the taxable and tax are back calculated from the Gross. If the Oracle Transportation Management system performs tax calculations, the results x may be different from what the JD Edwards EnterpriseOne system calculates.

• If Oracle Transportation Management sends only taxable (transaction amount with no tax), JD Edwards EnterpriseOne updates the EDI tables with this amount as taxable. The system uses the accounts payable tax information from the service provider to calculate tax on this taxable amount.

• If Oracle Transportation Management sends both gross and taxable amounts, JD Edwards EnterpriseOne updates the EDI tables with the gross amount.

Voucher Company and Account

The JD Edwards EnterpriseOne system receives inbound voucher information from Oracle Transportation Management. This information may contain one or more shipments which may have multiple order lines (sales and procurement). Furthermore, these order lines may also come from multiple companies.

This voucher integration point does not allocate the voucher costs to multiple companies. The system creates one voucher for the first shipment’s first order line’s ship from location’s company. The system also retrieves the expense account for the voucher from the service provider address book setup.

Inbound Voucher Assumptions

These assumptions apply to the Inbound Voucher integration point:

• There are no freight allocations.

• Taxes are calculated by JD Edwards EnterpriseOne. The system uses the Tax Rate/Area and explanation information that is stored in the address book of the service provider.

• The supplier for the voucher (service provider from Oracle Transportation Management) is sent in the reference field in the XML and hence R47041’s processing options (default tab, option 3 to use reference field) must be set up accordingly.

• There is no separation of freight charges between multiple companies involved in the shipment for which the voucher is sent. In other words, one company (from the branch plant of the first ship from location) pays all freight charges for a ship from location, unless manually overridden. If the shipment voucher involves multiple order lines from multiple companies, there is a manual intervention needed to correct the expense journal entry and voucher. This is the same logic for both sales orders and purchase orders. There is no distinction between these two orders

• You must set up a default expense account for the service provider in JD Edwards EnterpriseOne or the Oracle Transportation Management ship from location in order to expense freight. All Freight expenses incurred from this service provider or from a ship from location are booked to this account, unless manually changed using the P0411Z1 application.

Voucher ID Cross Reference

You use the Voucher ID Cross Reference (P49T60) application to inquire on and track cross referenced information between the EDI document and the Oracle Transportation management voucher, invoice, and transmission. For example if the R47041 program fails to create an EDI document, you access the Voucher ID Cross Reference program to aid with troubleshooting the failure.

Form Used to Inquire on Voucher ID Cross Reference

Inquiring on Voucher ID Cross Reference

Access the Voucher Invoice EDI Cross Reference form.

EDI Doc Number	Enter the ending document number for the range of numbers you want to display.
EDI Doc Type	The document type that is assigned by the transmitter in an EDI transaction. In a non EDI environment, this is consistent with the order type (DCTO) assigned at order entry time, an invoice document type, a voucher document type, and so on.
EDI Doc Company	Displays the Company - Key (EDI - Document Key Co)
Voucher XID	Displays the voucher ID in a transportation system external to JD Edwards EnterpriseOne.
Service Provider Invoice Number	Displays the service provider's invoice number.
Transmission Number	This is the unique identifier for the set of transactions that JD Edwards EnterpriseOne receives in an XML file for processing.
Transportation Planning Domain	A unique domain name that identifies a company. The purpose of a domain is to provide the ability to keep company data separate and secure from other company data in a shared, web-based environment. The value designates the domain in which transportation planning occurs.

Running the Inbound Transmissions Master Program

Select Sales Order Processing (G49T11), Inbound Processor.

Select Purchase Order Processing (G49T12), Inbound Processor.

Setting Processing Options for Inbound Transmissions Master (R49T90)

Processing options enable you to specify the default processing for programs and reports.

Process

Versions