3663286 - JobOffer entity returns an error when using application FO/GO Fields in Offer Templates - Recruiting Management

Customers who reference Field Object/Generic Object (FO/GO) fields from Application templates within Job Offer templates encounter API failures when using the Job Offer entity OData V2 calls. This limitation occurs because Application-referenced FO/GO fields are currently not supported in the Offer OData V2 implementation.

Background: While Application templates support FO/GO fields independently (available since 2402 release)  and Offer Approval also supports FO/GO fields as an existing feature, the integration between these two components remains incomplete. When Application-referenced FO/GO fields are included in Job Offer templates, the entire Offer Approval OData feature becomes non-functional 

SAP SuccessFactors Recruiting Management 

1. Enable FO/GO on Application templates.
2. Reference an Application FO/GO field in a Job Offer template.
3. Attempt to access the Job Offer entity using the OData V2 API.
4. Observe that the operation fails.

This is a product limitation. The Application-referenced FO/GO support was not implemented for Offer OData V2 entities as part of the initial FO/GO support for Application.

As a result:

• FO/GO referenced fields from Application templates are not recognized in Job Offer templates via OData V2.
• The issue stems from a missed gap when rolling out "FO/GO for Application" and was not extended to cover Offer Approval integration.

 This limitation will be addressed as part of product enhancement RCM-155493, currently planned for 1H 2026 release.

Suggested workaround to enable related integrations:

1. Reference FO/GO fields from the Job Requisition instead of the Application.

   • Update the Offer template: Wherever Application-referenced FO/GO fields are used, substitute with analogous fields defined in the Job Requisition.

   • Template Example:

     From:

      

     <field-definition id="YOUR_OBJECT_ID" type="object" required="false" custom="true" object-type="YOUR_OBJECT_TYPE" template-type="job-application" anonymize="false">
       <field-label><![CDATA[LABEL]]></field-label>
       <field-description><![CDATA[DESCRIPTION]]></field-description>
     </field-definition>

     To:

      

     <field-definition id="YOUR_OBJECT_ID" type="object" required="false" custom="true" object-type="YOUR_OBJECT_TYPE" template-type="job-req" anonymize="false">
       <field-label><![CDATA[LABEL]]></field-label>
       <field-description><![CDATA[DESCRIPTION]]></field-description>
     </field-definition>

   • After making the above change, perform an OData metadata refresh to ensure changes are reflected in integrations.

2. Update Integrations: Modify any integrations dependent on Application-referenced FO/GO fields in Offer templates to instead utilize Job Requisition-referenced fields until the enhancement is available.

 RCM-155493, FO/GO, Field Object, Generic Object, Application, Job Offer, Job Requisition, OData, Offer Approval, Recruiting, Limitation, Entity, error, API , KBA , LOD-SF-RCM-CAO , Candidate Offers, Offer Letters , LOD-SF-RCM-INT , Integration Center & Intelligent Services , LOD-SF-RCM-API , Webservices & APIs , Problem