APIs for VTBSTA3 (Standing Instructions Authorizations)

[monika_eggers]

Have you found yourself in the difficult situation of needing to mass-create or replicate/distribute VTBSTA3 data (the standing instructions authorizations that are part of the EA-FINSERV extension of the company code data of the Financial Services Business Partner)? Until recently the only way to maintain VTBSTA3 data other than through transaction BP used to be via Direct Input, i.e. function module FTB_BUPA_DARK_MAINTAIN_INTERN.

Now with note 2887500 there is an API (no BAPI though) and it is part of the CIF (complex interface for business partner, customer and vendor/supplier, e.g. function module CVI_EI_INBOUND_MAIN and method CL_MD_BP_MAINTAIN=>MAINTAIN). You can find it at this navigation path:

I_DATA TYPE CVIS_EI_EXTERN_T -> CVIS_EI_EXTERN -> PARTNER Type BUS_EI_EXTERN -> FINSERV_DATA_CC Type FTBP_EI_DATA_CC -> COMPANY_CODE Type FTBP_EI_COMPANY_CODE_T -> FTBP_EI_COMPANY_CODE -> SI_AUTHORIZATIONS Type FTBP_EI_SI_AUTHORIZATIONS -> SI_AUTHORIZATIONS Type FTBP_EI_SI_AUTH_DATA_T -> FTBP_EI_SI_AUTH_DATA -> DATA_KEY Type FTBP_EI_SI_AUTH_KEY

You may wonder why there is no DATA segment, only DATA_KEY, and the field AUTHOR is nowhere to be found. The reason is that the only permitted value is 'X'. Entries with AUTHOR = space must not occur on the database. The API will set VTBSTA3-AUTHOR to 'X' internally, there is nothing for you to do. If you wish to express that a combination is not authorized, delete the line, do not attempt to set AUTHOR to space.

In addition to the API the table is being included in the business partner replication service {http://sap.com/xi/SAP_BS_FND/MDG/Global2}BusinessPartnerSUITEBulkReplicateRequest_In.

Now with this new API and enterprise service integration you will have a much easier time when you need to mass-create or replicate VTBSTA3 data. If you have questions you can comment here or ask in the SAP Q&A Community under the FIN Treasury tag.