Ansicht
Dokumentation

/DSD/BAPI_VP_CHANGEFROMDATA - Change Visit Plan

PERFORM Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Functionality

You can make the following changes to a visit plan using this method:

• You can change general data at header and item level. You cannot change the visit plan type of the visit plan in the header data.

• You can use the import parameter VPID_FOR_HRULE to copy a header date rule from another visit plan to the visit plan you want to change. This overwrites the existing header date rule.

• You can add new customers or remove customers from the visit plan using the import structure VPP_IN. You can also change other customer data, such as the sequence of visits. You cannot change customer numbers.

• You can use the import parameter VPID_FOR_CRULE to copy item date rules from another visit plan to the visit plan you want to change. This overwrites the existing item date rules.

Changes you make to individual fields are only taken into account by the system if the following prerequisites are fulfilled:

• You have specified in the update indicator for each item in the visit plan whether the entered values are new (I) or changed (U),or if the existing values are to be deleted (D).

• In the relevant change parameter for the parameter, you have flagged all fields that are change-relevant with an 'X'. If you want to change specific fields in the header data (parameter VPH_IN), for example, you must select these fields in parameter VPHX.

You can use the SIMULATION parameter to specify that you only want the changes to be simulated, and that the changed visit plan data should not initially be written to the database.

Customer Enhancements

To add customer fields to the tables for the visit plan, you can use the following BAPI Table Extensions:

• Structure /DSD/BAPI_VC_TE_VPH for additional fields at header level

• Structure /DSD/BAPI_VC_TE_VPHX to flag the new fields at header level

• Structure /DSD/BAPI_VC_TE_VPP for additional fields at item level
  If customer fields are added to the item data table, these fields must also be added to the structure /DSD/VC_VP_TREE.

• Structure /DSD/BAPI_VC_TE_VPPX to flag the new fields at item level

You can assign the relevant values to customer fields with the EXTENSIONIN table.

All data transferred to the BAPI is checked for consistency before further processing. By implementing the BAdI method VP_CHECK_CONSISTENCY, you can add your own checks or check the consistency of customer fields in the visit plan tables.

Return messages

Messages are returned in the RETURN parameter. See the parameter documentation for the return values and their meanings.

Example

Notes

The following authorization object is checked with the activity 02 (Change): /DSD/VC_VP

Further information

For more information, see the parameter documentation.

Parameters

EXTENSIONIN
RETURN
SIMULATION
VISITPLAN_ID
VPHX
VPH_IN
VPH_OUT
VPID_FOR_CRULE
VPID_FOR_HRULE
VPPX
VPP_IN
VPTEXT_IN

Exceptions

Function Group

/SAPLVC_BAPI_VP

TXBHW - Original Tax Base Amount in Local Currency   General Material Data  
This documentation is copyright by SAP AG.

Length: 4664 Date: 20240419 Time: 014028     sap01-206 ( 53 ms )