How to configure a Syniti BAPI to post client-specific fields (zFields)

The Syniti Transports contain structures that have been named in the format /BOA/ZBAPI_TE_<AAAA> for each table <AAAA>.   Those structures are delivered with the application and contain only the Key Fields for the referenced SAP table.  Use SAP transaction SE11 to modify the structures for tables that have client-specific appends. The User must have a Developer’s Key in SAP in order to perform the task.  Usually, the task is performed in the development instance and client and then transported to other SAP instances.

To modify the structures to append table extensions:

1. Enter Transaction SE11 (with necessary security permissions) and click Data Type radio button
2. Enter structure name (ex: /BOA/ZBAPI_TE_KNVV)
3. Select Display
4. Select Append Structure, a pop-up window displays
5. Enter the name of the append as ZABAPI_TE_<AAAA> where <AAAA> is replaced by the SAP table name.
6. Add the zField Name for each appended field.

Note: the zFields must be the same field names as the database table. However the Data Type must be Character and must be the same length as the database field (dates are 8 characters long). All appended fields in the database table must be listed in the structure even if not all will be populated by the application. Fields must be in the same order in the structure as in the database table.

1. Click Activate or CTRL-F3 to activate the added field.
   (Ignore the warning that the “table is not yet classified” or that the “Field xxxx does not lie within Customer Namespace”)

The completed structure should resemble the following:

1. Repeat the process for the structure /BOA/ZBAPI_TE_<AAAA>X  if it exists. 

The purpose of this structure is to mark which fields should be updated in SAP when the BAPI runs. For the “X” structure, include the same field names in the same sequence as the structure /BOA/ZBAPI_TE_<AAAA>, but with a length of 1 and a data element/component type  of BAPIUPDATE.

In the above screenshots, the structures contain an Append structure before the zField data.  This change is required when the BAPI uses structures that are standard SAP products. The Append with the component type ZA… delineates where the file extensions begin.  The append is not needed for BAPI TE structures that begin with /BOA/… because the actual structure itself is extended. Add the extended fields directly after the key fields.  The other difference between the SAP delivered structures and the custom structures is the whole key is required.  The Material Structure derives the MATNR from the Material Header structure son only the secondary keys are shown in the BAPI_TE_... structures.  In the example below FLD1 is the extended field for table LFA1.

For Material zFields only, ensure that the zFields also have been assigned to Field Selection Groups in SPRO.