Paramètre | Reférence | Type | Long. | Valeur par déf. | Facultatif | Description |
---|---|---|---|---|---|---|
PI_ADDRESS | BAPIKNA101 | u | 477 | Customer Address Data | ||
PI_COPYREFERENCE | BAPIKNA102 | u | 18 | Reference Data |
Paramètre | Reférence | Type | Long. | Description |
---|---|---|---|---|
CUSTOMERNO | BAPIKNA103-CUSTOMER | C | 10 | New Customer Number |
PE_CUSTOMER | BAPIKNA103-CUSTOMER | C | 10 | New Customer Number |
RETURN | BAPIRETURN | u | 452 | Return Value |
Functionality
Master data: Account group - this must be an account group linked to anumber range that internally assigns a customer number. Company code data: Reconciliation account in Financial Accounting Sales data: Customer schema (for determining the calculation schema),term of payment key, shipping conditions, incoterms part 1, 2 andsupplying plant. Contact person data, partner function data, and bank details. Example Notes Surname, language, location, and country Depending on the country, further data may be necessary. The country can be transferred to the BAPI in either R/3 format or ISOstandard. If both fields (R/3 format and ISO standard) are selected andtransferred to the BAPI, the country key in R/3 format has priorityover the ISO standard format. Note: The 'old' ISO standard fields for the country (numerical andalphanumerical formats) are not supported and have been shut down. Lastly, a language key in R/3 format or ISO 639 standard must also betransferred to the BAPI. If it is transferred to the BAPI in both formats (R/3 and ISOstandard), the country key in R/3 format has priority. R/3 reference customer, sales area data (sales organization,distribution channel and division) Note on reference customer: The reference customer should be created bearing in mind that his onlypurpose is to provide data for customers that are created via the BAPI. In other words, the reference customer is not an operative customer inthe business sense. As a result, the customer should be created with aseparate account group with internal number assignment. In addition,the reference customer must exist in the organizational data that istransferred to the BAPI. If company-code-independent data is transferred to the BAPI, thereference customer must be created for a company code. (ii) The permitted countries are those in R/3 table T005. The permittedregions in these countries are those in R/3 table T005S. The length andnecessity of the postal code depend on the country in question. (iii) An e-mail address is only valid if it contains the character '@'. (iv) A check on duplicate records for the purpose of matchcode fieldconsistency (see MCOD1-3 and table TFMC) is carried out on the basis ofan entry in R/3 table T100C (transaction OBA5 work area F2, for MsgNr145 entry I). If the three matchcode fields are the same, an error message is issued. (v) Messages are returned in parameter RETURN. The return values andtheir meanings can be found in this parameter documentation. (vi) The customer is updated synchronously. (vii) The new customer number is returned in the field CUSTOMERNO. Note: Field PE_CUSTOMER always contains exactly the same value asCUSTOMERNO. Field CUSTOMERNO stands for a method view of the functionmodule, field PE_CUSTOMER for a procedural view of the function module. (viii) Authorization requirements for using the BAPI: "Create" authorization is required for the following objects: F_KNA1_APP (customer: user authorization), F_KNA1_BUK (customer:authorization for company codes, for the selected company code) andV_KNA1_VKO (customer: authorization for sales organization, for theselected sales organization). Authorization profiles that cover the above objects are SAP_ALL,V_Verkauf and V_Versand. Further information Description Description Description Value range Description Description |