Field "Ship-to Party's Customer Reference Date" in SD_SLS_ORDER_CONFIRM

[ciskoy]

Dear all,

I couldn't find the field "Ship-to Party's Customer Reference Date" (VBKD-BSTDK_E) in the form SD_SLS_ORDER_CONFIRM.
I did a Data Source Extension on FDP_V1_ORDER_CONFIRM_SRV but I couldn't find it either.

Do you know if this field can only be read only via a Custom Logic or did I miss something?

And do you know how to find a field in Public Cloud forms only with technical name (example: VBKD-BSTDK_E)?
The only way I could find is by adding the field in the form and test it in Public Cloud... Which is a bit archaic and VERY time consuming. 

[Troy · Accepted solution]

Hi @ciskoy,

Unfortunately, this field VBKD-BSTDK_E is not exposed in the released CDS view, which means you are also not able to get the value of this field in custom logic. The current workaround is to create a custom field and manually enter the same date into it.

We don't have documentation for mapping the technical name. Basically, all field names follow the Global Field Name. (Also, the technical name is not user-friendly for the"non-SAPer" 😞 ).

If you need the field "Ship-to Party's Customer Reference Date" (VBKD-BSTDK_E) via standard Data Source Extension, please consider raising a new feature request (2963059 - How to Submit Feature Requests for SAP S/4HANA Cloud Public Edition - SAP for Me).

Best regards,

Troy

[DequanXu]

Hello,

You may need to involve custom logic if you find out that it's not directly available in your standard data sources or forms.

1. **Data Source Extension**:
- If you’ve already extended the data source (FDP_V1_ORDER_CONFIRM_SRV) and couldn’t find VBKD-BSTDK_E, it's possible that the field is not exposed in the standard SAP S/4HANA Cloud services. Extending data sources is usually the first step, but if that doesn’t work, the Custom Logic approach would indeed be required.

2. **Scouting Fields in Forms by Technical Name**:
- Generally, finding a field in Public Cloud forms using only the technical name isn’t straightforward. You would typically do the following:
- **Enhanced Developer Extensibility**: Use this to add additional fields if available.
- **Form Template Customization**: Modify the form template in the Form Builder and attempt to add the field manually. Testing directly on the Public Cloud as you mentioned is often a practical approach.
- **Custom Logic (ABAP in SAP S/4HANA Cloud)**: If the field isn't available, you might consider using an enhancement logic to populate or fetch the required field data.

Best regards,

Dequan Xu