Processing Excise Duty and Sales Tax/VAT in the PO Receipt Push Process

The Receipt Push process (PO_RECVPUSH) takes receipt lines and distributions and joins in purchase order schedule excise duty and sales tax/VAT details to create receipt-landed cost transactions. Receipt-landed cost data is passed on to inventory using the Staged Cost table.

Once landed cost transactions are created for receipt lines, any online changes to the quantities accepted on the receipt are applied to the landed cost transactions upon saving the receipt.

The Receiver Interface Push process passes the receipt lines to the PeopleSoft PO/AP/AM Interface process (AMPS1000). When the Allocate Purchasing Group check box is selected on the Purchasing Options page, the following processing is done for each receipt with a procurement group ID:

• The procurement group asset data is written to the Receipt Line Asset table and the Asset Management Interface table (INTFC_PRE_AM). Online receipts facilitate the process by generating entries in the receipt line asset table that are based on the allocation quantity (or amount) multiple. As such, by the time the Receipt Push process is triggered, the initial receipt line asset structure (as adjusted for procurement groups) is already in place.

• For the item flagged as a primary unit, a separate entry is created in the Asset Management Interface table for each increment of unit allocation quantity or unit allocation amount. Each entry is assigned the next available procurement group sequence.

• Similarly separate entries are created in the PeopleSoft Asset Management interface table for non-primary items for each increment of unit allocation quantity or unit allocation amount. Each non-primary item entry is Arbortext Editor Unformatted Print: temp_ResolvedDoc.xml Printed then assigned the procurement group sequence associated with the corresponding primary unit entry (for example, for each non-primary item, the first unit of allocation gets assigned the same sequence associated with the first primary item unit of allocation and so on).

• The load status on the PeopleSoft Asset Management interface table will be set to PGI (procurement group incomplete) for any procurement grouping (sequence) that does not contain all of the items within a procurement group or if any of the items within that grouping (sequence) do not have a full unit of allocation. Groupings without a primary item will also be set to 'PGI’ Procurement group items are identified by the Receipt Push process by taking into account all transaction line items across all purchase orders that are assigned to that procurement group. Also taken into consideration are requisition lines with asset items that have any open quantity (or amount). For this reason, in terms of asset allocation, the items that comprise a procurement group cannot be changed once the structure has been established (based on existing transactions). If item composition needs to be addressed after a procurement group has already been established, a new procurement group should be utilized instead. Receipt Push will examine older data in the interface table in status 'PGI' to determine if the incoming Receipt Asset Lines can complete the asset.

• Since Receipt Push matches on descriptions (for description only items), care must be exercised when entering a non-primary description only item on a transaction line so that it is spelled exactly as an existing description only item that is intended to be the same item.

• The Receiver Interface Push process keeps the rows in the RECV_LN_ASSET table in sync with the rows in the Asset Management Interface table. This enables future changes to a receipt to be passed to the Asset Management Interface table.