Functionality
You use this method to create aliases for thebusiness partner.

Example

Notes
This method processes data for each business partner.
A preprocessing run takes place before the aliases are created:

• A check is performed to determine whether the business partner is
available for processing.

• A simple exclusive lock is activated.

This prevents other users from changing the business partner that iscurrently being processed until either the method TransactionCommitor TransactionRollback for the Business Object BapiServiceis executed. The authorized user can access the same business partnerrepeatedly.
The alias is not written to the database until the methodTransactionCommit for the Business Object BapiService hasbeen called.

Authorizations
You can make settings for business partner authorization objects to bechecked in Customizing for the SAP Business Partner under BusinessPartner-> Basic Settings-> Authorization Management.

Customer Enhancements
The Business Add-In (BAdI)FSBP_ALIAS_ADD_BAPI (BAdI for FSAddAlias) is available for thismethod.
For more information on customer enhancements, see the SAP Library underCross-Application Components -> Business Framework Architecture(CA-BFA) -> Further Development, Modifications -> Customer Enhancementand Modification of BAPIs -> Customer Enhancement of BAPIs.

Buffering
This method uses buffering. Change and read methods for this businessobject category can be repeatedly used for this instance. After callingthe save method, read and write methods can access the bufferedinstances and supply current attributes in the same logical unit of work(LUW).
INCLUDE BAPI_RET OBJECT DOKU ID TX
If errors occur, the entire logical unit of work (LUW) must be discarded. To do this, call themethod TransactionRollback for the Business ObjectBapiService.

Description
This parameter is required.
You can find information on the meaning of the parameter in thecorresponding documentation for the data element business partner number.

Value range

Description
In this parameter you can state that customer enhancements to thisBusiness Application Programming Interface (BAPI) are to be executed.
If this indicator is not set, the system ignores the customerenhancements.

Value range
'X' Execute customer enhancements
' ' Do not execute customer enhancements

Default
' ' Do not execute customer enhancements

Description
You can find information on the meaning of the parameter in thecorresponding documentation for the data element business partner alias.

Description
You can find information on the meaning of the parameter in thecorresponding documentation for the Reference Structurefor BAPI Parameter ExtensionIn / ExtensionOut.
For information about the meaning of each parameter field, see therelevant data element documentation in the ABAP Dictionary.
This parameter serves as a data container. In the parameter you cantransfer additional data to the method that was not considered at theinterface.
The data is transferred in a table. The format for the individual datarecords for this table is determined by the structure BAPIPAREX. Thiscontains several data record fields (VALUEPART1, VALUEPART2, ...) aswell as a field for the name of an internal structure created by thecustomer (STRUCTURE). As the data for each data record is writtenpiecewise, one after the other, in the available data record fields, aninternal structure is required in order to interpret the data.
In the event that a customer wants to add additional fields to an SAPdatabase table, BAPI table extensions are particularly well suited asinternal structures.
You will find more detailed information on the various customerenhancement options, and the internal structures to be used in eachcase, in the document Customer Enhancement and Modification of BAPIs
in the SAP Library under Enhancements, Modifications ...(CA-BFA).
The data for the parameter is transferred to the methods Validateand Transferextensionin for the Business Add-Ins (BAdIs).

Description
This table contains return messages from the message call.