Note!! Please register for a free account to access the full content and also to participate in Q&A in the community
Backdate transaction date for cycle count adjustments
Summary:
We have cycle counts created on the last day of the month May 31 but the cycle sequences are submitted on June 1st. So the Cycle count adjustment transactions are having June 1 transaction date which are not getting costed to May period in Cost Management. What are the options or workaround to backdate transaction date to 31-May through the fscmRestApi/resources/11.13.18.05/cycleCountSequenceDetails?
We followed the solutions on the oracle cloud connect but none of them worked. Example : Populate count date as last day of the month or remove approval but still same result.
Content (please ensure you mask any confidential information):
Tagged:
0