3831045 - Unable to schedule and start output for internal RFQ (Int. Sourcing Request) - SAP S/4HANA Cloud Public Edition

Unable to find a dedicated app to schedule output for an internal RFQ (Int. Sourcing Request).

SAP S/4HANA Cloud Public Edition

1. Set Output Parameter Determination to “Scheduled”.
2. Create an internal RFQ (Int. Sourcing Request); the output status becomes “Scheduled”.
3. Attempt to start the scheduled output; the output cannot be started.

Missing functionality: No dedicated app exists to schedule and start output specifically for internal RFQs (document type RQ – Int. Sourcing Request).

There is no dedicated app to schedule and start output specifically for internal RFQs (document type RQ – Int. Sourcing Request) in SAP S/4HANA Cloud Public Edition.

Output for Internal RFQs is supported, but only through the standard Manage RFQs (F2049) app using the Output Management for SAP S/4HANA (CA-GTF-OC) framework — not via a dedicated scheduling app. 

• Output (email or print) is triggered when the RFQ is published in the Manage RFQs app. The dispatch time is set to "1 – Immediately" in the BRF+ output determination rules, meaning output is sent at the point of publishing — not on a scheduled basis. 
• There is no equivalent of a "Schedule RFQ Output" app (unlike, for example, Purchase Orders which have the dedicated "Schedule the Release of Purchase Order Outputs" app). No such scheduling app exists for the RFQ object in the standard Public Cloud scope.
• Output determination runs only when the RFQ is published — pressing the "Create" button only saves a draft, and no output determination runs for draft documents. 
• Output management for Internal RFQs uses BRF+ (S/4HANA Output Control) exclusively. The legacy NAST-based output (used in ME41/ME42) is not available in the Manage RFQs Fiori app, and vice versa. 
• Output after awarding a supplier quotation is also not available in standard — output can only be generated when the RFQ is created/published via the Manage RFQs app.  

As an interim workaround, ensure the dispatch time is set to "Immediately" so output is reliably sent upon publishing — this is the closest standard behavior to automated output dispatch.

• refer to: Output Management for Manage RFQs - Internal Sourcing Request
• refer to: Output Management for Central RFQs
• refer to: Community: Output in RFQ process
• refer to: Community: Internal sourcing request attachments with RFQ output
• refer to: KBA 3560499 - Storage Access API enablement

internal RFQ, Int. Sourcing Request, RQ document type, schedule output, scheduled output, output parameter determination, output control, RFQ output, manual send, start output, RFQ email, missing functionality, not supported, S/4HANA Cloud, purchasing RFQ , KBA , MM-PUR-RFQ-2CL , RFQ/Quotation (Public Cloud) , Problem