Ansicht
Dokumentation
BAPI_FTR_SL_CHANGE - Change a Security Lending Transaction
CPI1466 during Backup SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
Functionality
You can use this method to change the data for a Security lending.
The transferred data corresponds to the existing data in the online transaction under structure, collateral, administration and status.
For detail screen data including conditions, other flows, main flows and payment details, use the methods for the corresponding business objects.
The changes are carried out with the selected field changes concept. That means that only the data for which the field name is indicated in the corresponding change parameter (for example, GENERALCONTRACTDATAX) is transferred from the data of a parameter (for example, GENERALCONTRACTDATA).
There can also be the import parameter (parameter name)_COMPLETE_INDICATOR for table parameters. This specifies whether the entries transferred in the table are complete (and entries that are not transferred are deleted) or whether only new/changed entries were transferred.
Example
Changing the Start Term of a Security Lending transaction:
Set the parameters COMPANYCODE and FINANCIALTRANSACTION. Set the field SECURITYLENDING-START_TERM to the new value. Set the field SECURITYLENDINGX-START_TERM to 'X'. Call method Security Lending .Change.
This is a possibility to use the Change method. The following general procedure applies to changing a Security Lending transaction:
Read the data for a Security Lending transaction using Security Lending.GetDetail. Copy and change the data to suit your requirements. Then Call Security Lending.Change to change the Corresponding Value .
Notes
If you set the TESTRUN parameter this calls the BAPI in simulation mode.
To write the data to the database after running a BAPI call in an update run (TESTRUN initial), a commit work must be triggered, for example with BapiService.TransactionCommit.
Messages are returned in the parameter RETURN.
A BAPI can only be executed successfully if the transferred data meets the online transaction consistency conditions. In this case, the export parameters are filled and a success message is returned.
If the data is not consistent or complete it is rejected. In this case, the export parameters are initial parameters; an error message and the consistency check messages are displayed.
Refer to the parameter documentation for information about the parameters; which data is mandatory, optional, or depends on the settings in Customizing, and what default settings exist.
Notes
Further information
Parameters
CASHCOLLATERALCASHCOLLATERALX
CASHCOLL_COMPLETE_INDICATOR
COMPANYCODE
FINANCIALTRANSACTION
GENERALCONTRACTDATA
GENERALCONTRACTDATAX
RETURN
RETURNCOMPANYCODE
RETURNFINANCIALTRANSACTION
SECCOLL_COMPLETE_INDICATOR
SECURITYCOLLATERAL
SECURITYCOLLATERALX
SECURITYLENDING
SECURITYLENDINGX
TESTRUN
Exceptions
Function Group
FTR_BAPI_SLBAL Application Log Documentation SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 4928 Date: 20240523 Time: 113137 sap01-206 ( 69 ms )