Kontakt

Ansicht
Dokumentation

ERP_WEC_USER_MGMT - BAdI: Definition of User Checks in ERP

ERP_WEC_USER_MGMT - BAdI: Definition of User Checks in ERP

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

This Business Add-In (BAdI) is used in the User Management (WEC-APP-UM) component. The BAdI belongs to enhancement spot ERP_WEC_USER_MGMT_CHECK.

You can use the BAdI to check additional user details during logon and registration. In the standard system, when a user logs on to the Web shop, the system checks if the user name and e-mail address are valid. If you want to check against additional fields, like the first name or last name, before authenticating a user, you have to implement this BAdI.

You cannot modify the given data in the BAdI. You are only allowed to check the values given by the user management and to set the return code. An exception is the method CHECK_LOGIN where - besides the status - the R3 user name must be returned.

The BAdI contains interface IF_ERP_WEC_UM_CHECK_BADI. This interface has the following methods:

  • Method CHECK_LOGIN, which checks user details during logon. This method has the following parameters:
  • Importing Parameters:,,

TECHNICAL_ID
R3_USERNAME
  • Exporting Parameters:

RETURNCODE
MESSAGES
Result:
  • It should return ET_BUPA_KEY key as a result if the user is found by using the technical ID. In other cases, null should be returned.

  • ES_BUPA_KEY is currently not used.

  • RETURNCODEshould be:

Null, if no error occurs the given technical ID is valid
99, if an error occurs (MESSAGES must contain an appropriate error message)
  • MESSAGES contain only error messages.

  • Method CHECK_REGISTRATION, which checks user details during registration. It is called before the user and the corresponding business partner are created. If the method returns any other return value than null, the user creation stops and neither user nor the corresponding business partner are created. This method has the following parameters:
  • Importing Parameters:,,

TECHNICAL_ID
IV_IUSERNAME
IV_USERALIAS
IV_CUSTOMERDATA
IV_CUSTOMERDATA_X
  • Exporting Parameters:

RETURNCODE
MESSAGES
Result:
  • RETURNCODE should be:

Null, if no error occurs the given technical ID is valid
99, if an error occurs (MESSAGESmust contain an appropriate error message)
  • MESSAGES contain only error messages.

  • Method POST_REGISTRATION, which checks user details after registration. It is called after the user and the corresponding business partner have been created and the transaction has been committed. You can only create an error message if an error occurs. This method has the following parameters:
  • Importing Parameters:

TECHNICAL_ID
R3_USERNAME
CUSTOMERID
CONTACTID
  • Exporting Parameters:

RETURNCODE
MESSAGES
Result:
  • RETURNCODE should be:

Null, if no error occurs the given technical ID is valid
99, if an error occurs (MESSAGES must contain a appropriate error message)
  • MESSAGES contain only error messages.

This BAdI is a prerequisite if you use the technical ID as logon type in the Web shop.

In the standard system, there is no activated BAdI implementation. Therefore, a logon with technical ID is not possible by default.

Information about the implementation of BAdIs in the context of the enhancement concept is available in the SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.






CPI1466 during Backup   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 7092 Date: 20240523 Time: 211635     sap01-206 ( 124 ms )