Customer Having Issues With SF30 SGD With Custom Base Standard Form
(Doc ID 2790501.1)
Last updated on JUNE 18, 2023
Applies to:
Oracle Contract Lifecycle Management for Public Sector - Version 12.2 and laterInformation in this document applies to any platform.
Goal
Issues with SF30 SGD with Custom Base Standard Form
It is known that the SF30 SGD for CLM Modifications - the continuation pages - print differently depending on the original base document format (COM vs UCF vs CSI)
You can see this code directly in the Oracle standard POMODSGD.rtf:
"call:mod_justcall:pr_listIFcall:dist_changesIF<?call:com_award?>EFIF<?call:csi_award?>EFIF<?call:ucf_award?>…"
What is the expectation/design with an SF30 SGD for CLM Modification when the original base document format is CUSTOM.
Currently, it seems to print on thing but the Accounting and Appropriation Data Changes.
Can the Oracle SF30 and POMODSGD be used when the base award has a CUSTOM standard form/document format.
Currently , we have 3 CUSTOM standard forms that this could be applicable to: MISCOB, IAA, and OTA
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |