Kontakt

Ansicht
Dokumentation

T_SLS_LO_API_EWB - Start Enhancement Workbench

T_SLS_LO_API_EWB - Start Enhancement Workbench

General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you start the Enhancement Workbench for the Lean Order API (LO API).

The LO API enables decoupled and dialog-free access to the sales logic in the back-end system. This API is used in the SOA environment or for the configurable sales user interface, such as for the Internal Sales Representative portal role in the Business Package for Internal Sales Representative portal application.

Customer-specific fields that you have implemented in the SD back-end logic are not immediately available via the LO API in the delivery.
Using the workbench, however, you can declare these customer-specific fields in the LO API and integrate them in the sales process. These customer-specific fields are available in the activity Configure User Interface in the field catalog, for example, so that you can include your customer-specific fields in the configurable sales UI.

Note
This workbench is not intended for internal sales representatives or other end users.
System administrators and consultants can use the workbench to declare new or additional customer-specific fields in the LO API. If they set the value X in their user settings for parameter ID LO_API_EWB, they can also start the workbench from the configurable sales UI (Web Dynpro application: LO_OIF_MAIN_APP, application configuration: LO_OIF_SDOC_APPL). You can call the Enhancement Workbench under You can also.

The following are the prerequisites for making the settings for the customer-specific fields in the Enhancement Workbench:

  • You have activated the business function LOG_SD_CI_02.
  • You are working in a customer system and the current client allows changes.
  • You have sufficient administrator authorization for the Enhancement Workbench, such as for creating, changing and activating DDIC appends, maintaining tables, recording and transporting changes.
  • You have already created customer-specific fields for the sales document objects header or item and, if necessary, you have implemented user exits or Business Add-Ins (BAdIs) in the Sales and Distribution back-end logic:
  • Sales Document Header

You have defined customer-specific fields in the following tables: VBAK, VBUK, and/or VBKD.
  • Sales Document Item

You have defined customer-specific fields in the following tables: VBAP, VBUP, and/or VBKD.

When you declare a new customer-specific field for the LO API, the system preassigns the following field properties:

  • Unique Field ID: Next free number
    Counting starts at ZZSAP_0000000001
Since several source tables for customer-specific fields can be used for a sales document object, the field name of the customer-specific fields is not necessarily unique. This is why this unique technical field ID is used. You can change this ID before you initially save the data.
  • Search help type: Search help
You can choose from the following types: search help, fixed values, and check table.
  • Data transport: Automatic
You can choose from the following attributes: Automatic and Control via BAdI Implementation.
  • Input behavior: Ready for input for create/change, not changeable for display
You can choose from the following attributes:
  • Ready for input for create/change, not changeable for display

  • Required entry for create/change, not changeable for display

  • Not changeable for create/change/display

  • Ready for input for create/change/display

  • Control via BAdI implementation

You can use this workbench to carry out the following activities:

  1. Select the object category for which you want to declare customer-specific fields: Sales document header or sales document item.
  2. Create or change the field properties for the customer-specific fields.
    In this step, the system creates or changes a TABU table entry within the LO API.
  3. You then publish these fields for the LO API. In this step, the system enhances the append structure within the LO API.
The field is only available via the LO API once you have carried out the second and third substeps for a customer-specific field:
  • The system displays the fields and their properties that are available for the LO API in the Configure User Interface activity.

  • The system displays the orders from the Transport Organizer in which the field properties and/or the field publications have been recorded.

Note
In this workbench, the system might automatically generate orders that are organized and processed in the Transport Organizer application. You must therefore check if there are automatically generated orders for your enhancement and release the transport manually in the Transport Organizer.






BAL_S_LOG - Application Log: Log header data   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 6241 Date: 20240523 Time: 160911     sap01-206 ( 90 ms )