Binding a field to S/4

A field does not have to hold a value somebody typed. It can read one from S/4 each time the screen renders — the current warranty end, the current stock figure, the current status — without anything being copied into FSA.

1. 1

   Start from a mapping

   Pick one of the curated S/4 templates or a mapping your team saved earlier. A mapping says which service, which entity and which fields, so the binding is a choice from a list rather than a URL you have to get right.

2. 2

   Bind the field

   Choose the S/4 field, and what identifies the record — usually another field on the same screen. The screen fetches it live when it opens, and again when the identifying value changes.

3. 3

   Scope its value help too

   A bound field can offer an S/4 value list, narrowed by context in the same way as any other lookup, so a person picks a real S/4 value rather than typing one.

4. 4

   Check it before your users do

   Run the screen check. It validates every binding against the service's own metadata and names the ones that no longer resolve — which is how you find out a service changed before somebody in the field does.

Back to the designer.