Paramètre | Reférence | Type | Long. | Valeur par déf. | Facultatif | Description |
---|---|---|---|---|---|---|
PI_ADDRESS | BAPIKNA101 | u | 477 | Customer Address Data | ||
PI_SALESORG | BAPIKNA102-SALESORG | C | 4 | Sales Organization | ||
PI_SEARCH_FLAG | BAPIKNA104-SEARCHFLAG | C | 1 | Search Criterion |
Paramètre | Reférence | Type | Long. | Description |
---|---|---|---|---|
PE_CUSTOMER | BAPIKNA103-CUSTOMER | C | 10 | Customer Number |
RETURN | BAPIRETURN | u | 452 | Return Value |
Paramètre | Reférence | Long. | Facultatif | Description |
---|---|---|---|---|
MULTIPLE | BAPIKNA103 | 10 | X | Duplicates |
Functionality Notes
A maximum of one e-mail address must exist for a customer number atcompany code level. A maximum of one customer must exist for an e-mail address (also atcompany code level). Reasons for this: A single customer should not have two customer nubers. It must be possible to identify a customer by the e-mail address alone. A customer has forgotten his/her password for his/her customer number,and therefore tries to create a new customer record. This is notpermitted (if the e-mail address is the same). In addition to ensuringuniqueness of customer number for e-mail address, there are securityreasons for this. If a customer forgets a password, he/she can only logon to the system as follows: He/she must ring up the merchant, who provides a new initial password,which can be used with the "old" customer number or e-mail address tolog on to the system. The customer has both company and private addresses, but the samee-mail address, which he/she wants to use for purchasing. This is onlyallowed if the customer has different e-mail addresses. Company employees have a joint e-mail address. This case is permittedif a joint password is also used. In SAP R/3, several customers can exist for one e-mail address. Thesecustomers are referred to as 'duplicates' below. If the BAPI findsduplicates, these are entered in transfer table "MULTIPLE". Inaddition, the BAPI issues a message of type "E" (error). Messages are returned in parameter RETURN. The return values and theirmeanings can be found in this parameter documentation. Description Description Value range Description Description Description Value range Successful: No message, no PE_CUSTOMER, no MULTIPE entry Error: Message, no PE_CUSTOMER and 0..n MULTIPLE entries Successful: No message, PE_CUSTOMER is delivered, 1 entry in MULTIPLE Error: Message, no PE_CUSTOMER, 0 or 2..n MULTIPLE entries Description |