Ansicht
Dokumentation

VLC_SOA_SO_UPDATE - BAdI: Sales Order Update

rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

This BAdI is used for the integration of the Vehicle Managment System (VMS) in the Update Sales Order inbound service operation (message types: SalesOrderERPUpdateRequest_sync, SalesOrderERPUpdateConfirmation_sync). It can only be called when the sales order item is a vehicle (the vehicle can be uniquely identified by the material and the batch).

You can use this BAdI to handle your own actions that you have defined in Customizing for the Vehicle Management System in the Customizing activity Define Actions. As a default, the following actions are set and processed:

• CUOR (Create Sales Order)

• CHCO (Change Sales Order)

• DECO (Delete Sales Order)

The action is determined depending on the action code which is set on the sales order item.

The BADI has the following methods:

• SET_ACTION
  If you do not want to use the default action, you can use this method to change the action. All information available at this processing point in time are transferred to the method. The method is called once per sales order item. You can change the action using the INCOMING_ACTION_TEMP changing parameter.

• HANDLE_ACTION_INPUT
  You can use this method to implement the preparation and checks that should take place before executing the sales order update. The action to be processed is transferred to the ACTION importing parameter. If the BADI implementation is active for this customer-specific action, it replaces the default coding.

• HANDLE_ACTION_OUTPUT
  You can use this method to implement the follow-up processes of sales order update like data updates . If the BADI implementation is active, it replaces the action-specific default processing. General handling after action execution like update of table VLCHISTORY always takes place.

Note that due to the concept of services the action handling works slightly different as in VMS. It is split into a part before and after sales order update, the update of the sales order itself is part of the service operation implementation.

• In the standard system, there is no activated BAdI implementation.

• The BAdI is designed for multiple use. All activated implementations are called and executed.

• The BAdI is not filter-dependent.

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

Methods

Set Customer-Specific Action

Handle Customer-Specific Action Input

Handle Customer-Specific Action Output

General Data in Customer Master   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 4074 Date: 20240523 Time: 165019     sap01-206 ( 120 ms )