Expense Report Creation Doesn't Accept BusinessUnit in Release 20B
Summary
All this while we could pass BusinessUnit to create Expense ReportContent
Hi,
On Monday (6th July 2020) onwards, we couldn't pass BusinessUnit in the request payload - keep getting 400 Bad Request.
{
"ExpenseReportDate": "2020-05-07",
"ExpenseStatusCode": "SAVED",
"PaymentMethodCode": "TEST ACH",
"Purpose": "Test Payload Rest API NF",
"ReimbursementCurrencyCode": "USD",
"BusinessUnit":"TEST BU", <<<<<<<<<<<<<< BU
"ExpenseReportDff": [
{
"testName": "11111"
}
]
}
We've got sign-off for Unit Test and SIT by sending BusinessUnit, and now it's not working all of sudden.
How does the system defaulting the BusinessUnit and what if it defaults to the invalid BU? What is the impact of this new limitation in Release 20B?
Tagged:
0