IND_GST – Import PO is not accounted for correctly when procurement category is used

PROBLEM

When procurement category is used in import purchase orders, the tax amount is credited to the vendor but

should be credited to the ‘Import duty payable account’.

ref

Issue 965993

Project quotation journal should have option to track changes made after sending to customer and their revisions after customer asks for changes and resending new quotation. This function is available in Purchase order confirmation journals. This is very important to get to know customer demands

In the Expense Field Visibility (Expense Report – Reimagined) – There are fields which when marked as “required” leads to error, example – “Merchant field is not allowed to be set as required”. 

Blind users have difficulty in accessing ESS workspace to request time off

Repro steps:

1.     go to ESS workspace

Click Request time off

***Actual Result ***

Note that the Request time off opens up as a in window

***Expected Result ***

The request time off should open as a full page similar to view tasks below

When we open view task

Alternate ask

If above is not possible can a direct link be given to access request time off

GST is not being calculated in the invoice journal generated through Transportation Management, even though the SAC/HSN code has been added to the charge code.

The journal includes both Freight Charges and Accessorial Charges, but the tax calculation does not seem to be reflecting as expected.

Quick steps:

• Setup Shipping carrier, Accessorial charges and Freight charges from TMS
• Create SO and processing using Outbound load planning workbench
• Generate Freight bill invoice to process vendor invoice

Require the ability to generate invoice first, then generate product receipt, then have the match product receipt functionality to initialize on the created invoice. Currently, when the product receipt is generated after the invoice, this does not initialize on the invoice. 

Executive Summary

This document summarizes the findings related to the Hold functionality when the Recurring Contract Billing feature is enabled. It provides context, impact, and recommendations for customers to understand the behavior and next steps.

Environment / Context

The observations were made in the subscription billing environment where the Recurring Contract Billing feature was activated.

Findings

1. Enabling the Recurring Contract Billing feature automatically enables Hold functionality.

2. Once Hold is enabled, it becomes available for subscription billing to place holds.

3. Hold functionality is currently tied to the Subscription module feature and does not work for Vendor reason holds.

if we enable Recurring Contract billing feature hold gets enabled

when hold enabled, then it's available for subscription billing place hold

As hold functionality is currently enabled with Subscription module feature ,it will not work for Vendor reason hold