6615 lines
566 KiB
XML
6615 lines
566 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
||
<edmx:Edmx Version="1.0" xmlns:edmx="http://schemas.microsoft.com/ado/2007/06/edmx" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" xmlns:sap="http://www.sap.com/Protocols/SAPData">
|
||
<edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_COMMON',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
|
||
<edmx:Include Namespace="com.sap.vocabularies.Common.v1" Alias="Common"/>
|
||
</edmx:Reference>
|
||
<edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_CAPABILITIES',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
|
||
<edmx:Include Namespace="Org.OData.Capabilities.V1" Alias="Capabilities"/>
|
||
</edmx:Reference>
|
||
<edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_COMMUNICATION',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
|
||
<edmx:Include Namespace="com.sap.vocabularies.Communication.v1" Alias="Communication"/>
|
||
</edmx:Reference>
|
||
<edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_AGGREGATION',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
|
||
<edmx:Include Namespace="Org.OData.Aggregation.V1" Alias="Aggregation"/>
|
||
</edmx:Reference>
|
||
<edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_PERSONALDATA',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
|
||
<edmx:Include Namespace="com.sap.vocabularies.PersonalData.v1" Alias="PersonalData"/>
|
||
</edmx:Reference>
|
||
<edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_VALIDATION',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
|
||
<edmx:Include Namespace="Org.OData.Validation.V1" Alias="Validation"/>
|
||
</edmx:Reference>
|
||
<edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_ANALYTICS',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
|
||
<edmx:Include Namespace="com.sap.vocabularies.Analytics.v1" Alias="Analytics"/>
|
||
</edmx:Reference>
|
||
<edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_MEASURES',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
|
||
<edmx:Include Namespace="Org.OData.Measures.V1" Alias="Measures"/>
|
||
</edmx:Reference>
|
||
<edmx:Reference Uri="https://host:port/sap/opu/odata/iwfnd/catalogservice;v=2/Vocabularies(TechnicalName='%2FIWBEP%2FVOC_UI',Version='0001',SAP__Origin='LOCAL')/$value" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">
|
||
<edmx:Include Namespace="com.sap.vocabularies.UI.v1" Alias="UI"/>
|
||
</edmx:Reference>
|
||
<edmx:DataServices m:DataServiceVersion="2.0">
|
||
<Schema Namespace="API_BUSINESS_PARTNER" xml:lang="en" sap:schema-version="1" xmlns="http://schemas.microsoft.com/ado/2008/09/edm">
|
||
<EntityType Name="A_AddressEmailAddressType" sap:label="Email Address" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="AddressID"/>
|
||
<PropertyRef Name="Person"/>
|
||
<PropertyRef Name="OrdinalNumber"/>
|
||
</Key>
|
||
<Property Name="AddressID" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Address Number" sap:heading="Addr. No.">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a Business Address Services address.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the address number and the Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Person" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Person Number" sap:heading="Person">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a person in Business Address Services.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the person number and Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="OrdinalNumber" Type="Edm.String" Nullable="false" MaxLength="3" sap:display-format="NonNegative" sap:label="Sequence Number" sap:heading="ID"/>
|
||
<Property Name="IsDefaultEmailAddress" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Standard addr." sap:heading="#" sap:quickinfo="Flag: this address is the default address"/>
|
||
<Property Name="EmailAddress" Type="Edm.String" MaxLength="241" sap:label="Email Address">
|
||
<Documentation>
|
||
<Summary>Internet mail address, also called e-mail address.</Summary>
|
||
<LongDescription>Example: user.name@company.comThe Internet mail address is used to send mail via the Internet world-wide; the protocol used is SMTP (Simple Mail Transfer Protocol).The Internet mail address format is specified in various RFCs (Internet Request for Comment), including RFCs 821 and 822.This is not an IP address (192.56.30.6).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SearchEmailAddress" Type="Edm.String" MaxLength="20" sap:display-format="UpperCase" sap:label="E-Mail Address" sap:quickinfo="E-Mail Address Search Field">
|
||
<Documentation>
|
||
<Summary>This field is generated by the system from the complete Internet mail address and is stored in table ADR6.</Summary>
|
||
<LongDescription>It contains the first 20 characters of the Internet mail address in normalized form, that is, without comment characters and converted into uppercase.The field cannot be maintained by the user or from an interface.The table ADR6 contains an index for this field.Using an Internet mail address, the corresponding key of table ADR6 and the owner of the address are determined (for example, business partner or user).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AddressCommunicationRemarkText" Type="Edm.String" MaxLength="50" sap:label="Notes" sap:heading="Communication link notes" sap:quickinfo="Communication link notes">
|
||
<Documentation>
|
||
<Summary>Additional information about the communication connection</Summary>
|
||
<LongDescription>You can maintain further information about the communication connection here. In the case of telephone numbers, for example, you can maintain the times at which the call recipient is available and those at which they are not, or you can specify whether the number is that of the secretary.The information is stored in table ADRT, regardless of language.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_AddressFaxNumberType" sap:label="Fax Number" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="AddressID"/>
|
||
<PropertyRef Name="Person"/>
|
||
<PropertyRef Name="OrdinalNumber"/>
|
||
</Key>
|
||
<Property Name="AddressID" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Address Number" sap:heading="Addr. No.">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a Business Address Services address.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the address number and the Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Person" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Person Number" sap:heading="Person">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a person in Business Address Services.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the person number and Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="OrdinalNumber" Type="Edm.String" Nullable="false" MaxLength="3" sap:display-format="NonNegative" sap:label="Sequence Number" sap:heading="ID"/>
|
||
<Property Name="IsDefaultFaxNumber" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Standard No." sap:heading="Standard Number" sap:quickinfo="Standard Sender Address in this Communication Type">
|
||
<Documentation>
|
||
<Summary>If several addresses are maintained for one communication type, the user in the SAP System can be reached under one of these addresses. One address can be set as theStandard Address.</Summary>
|
||
<LongDescription>The standard address is used for the following functions:When sending using the SMTP nodein SAPconnect, the home address of the communication type used is the one set as the sender address. The recipient can see this address in the sender information and can also reply directly to this address. The standard address is also transferred and can be used for incoming status notifications, for example.When sending using an RFC node in SAPconnect, the standard address of the communication type used is the one set as the sender address. The structure defined in the case of the RFC does not permit another address to be transferred, so the standard address is used for incoming status notifications too.The SAP users have the addresses of their exchange P.O. boxes in their standard communication type 'Internet Mail' as the home address and their Internet address in the SAP system as their standard address. Example:Home address: Bernard.Brown@Company.comStandard address: Bernard.Brown@System.Company.comSending using an SMTP nodeThe home address of the communication type 'Internet Mail' (Bernard.Brown@Company.com) is used as the sender address. If a reply is sent to this address the user receives directly in the exchange postbox.Sending using the RFC nodeThe standard address of the communication type 'Internet Mail' (Bernard.Brown@System.Company.com) is used as the sender address. If a reply is sent to this address, it arrives back to the SAP system.Example using a mail system groupThe users should get all messages in their Microsoft Exchange postboxes. In the SAP system the mail system group is activated for this using the setting "Send Messages to the Home Address".The address settings of the SAP users remain unchanged:Home address: Bernard.Brown@Company.comStandard address: Bernard.Brown@System.Company.comSending using an SMTP nodeThe home address of the communication type 'Internet Mail' (Bernard.Brown@Company.com) is used as the sender address. If a reply is sent to this address the user receives directly in the exchange postbox.Sending using the RFC nodeThe standard address of the communication type 'Internet Mail' (Bernard.Brown@System.Company.com) is used as the sender address. If a reply is sent to this address it arrives back in the SAP system. It is then forwarded using the mail system group to the home address and the user gets it in the exchange postbox.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="FaxCountry" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Country/Region" sap:heading="Ctry/Reg." sap:quickinfo="Country/Region for Telephone/Fax Number">
|
||
<Documentation>
|
||
<Summary>The country/region for the telephone number or fax number is maintained here.</Summary>
|
||
<LongDescription>This specification is used to determine the correct country/region code. A normalized form of the telephone number or fax number is then derived and stored in a field for a program-driven search.In most cases, the telephone number or fax number refers directly to an address.If this is the case, when a new number is created, the country/region of the address is proposed.If this is not the case (for example, with address-independent communication data for a business partner), the country/region from the user parameter LND is proposed (if it is maintained).If the user parameter LND is not maintained, the country/region of the company address assigned in the user master data is proposed.If the country/region of the address changes, the country/region of the corresponding telephone number and fax address is not changed automatically.Example: A business partner moves abroad.If the telephone number is for a permanent connection, the telephone number also changes when the business partner moves and has to be maintained again in the system.If the telephone number is for a mobile telephone and the number is retained, the original country/region for this telephone number also has to be retained and must not be changed automatically to the new country/region of the address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="FaxNumber" Type="Edm.String" MaxLength="30" sap:display-format="UpperCase" sap:label="Fax" sap:quickinfo="Fax number: dialling code+number">
|
||
<Documentation>
|
||
<Summary>Fax number, consisting of dialling code and number, but without country dialling code.</Summary>
|
||
<LongDescription>If the fax number consists of a company number and an extension, the extension must be entered in the field extension.Fax number, as it is to be dialled from within the same country.Enter the following for the number "01234/567-0":Fax: 01234/567Extension: 0Enter the following for the number "01234/567-891":Fax: 01234/567Extension: 891For the number "012-345-678" (678 as extension) enter the following:Fax: 012-345Extension: 678In the following cases, enter the complete number (without country dialing code) in the field Fax:No part of the number can be considered as an extension.You are not sure which part of the number can be considered as an extension.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="FaxNumberExtension" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Extension" sap:quickinfo="Fax no.: Extension">
|
||
<Documentation>
|
||
<Summary>Fax extension number</Summary>
|
||
<LongDescription>If the fax number consists of a company number and an extension, the extension must be entered here.Enter the extensionThe following rules apply for the format of telephone and fax numbers:The length of the entries in the field Telephone and Extension (Fax and Extension) cannot be more than 24 characters in total.Leading spaces are not allowed in the field Telephone or Fax or in the field Extension.Valid characters are:Numbers (0123456789)Letters (ABCDEFGHIJKLMNOPQRSTUVWXYZ)Following other characters: /, (, ), - *, # and " " (space), but not as a leading space.If an + is entered as the first character, the system checks whether the specified number starts with a country code. If so, a warning message is displayed because the country code is automatically determined by the system and should not be stored in the Telephone number (Fax number) field.If an & is entered as the first character, the automatic check and formatting of the telephone number (fax number), as well as the determination of the country code, is suppressed.Enter the following for the number "01234/567-0":Fax: 01234/567Extension: 0Enter the following for the number "01234/567-891":Fax: 01234/567Extension: 891For the number "012-345-678" (678 as extension) enter the following:Fax: 012-345Extension: 678In the following cases, enter the complete number (without country dialing code) in the field Fax:No part of the number can be considered as an extension.You are not sure which part of the number can be considered as an extension.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InternationalFaxNumber" Type="Edm.String" MaxLength="30" sap:display-format="UpperCase" sap:label="Fax Number" sap:quickinfo="Complete Number: Dialling Code+Number+Extension">
|
||
<Documentation>
|
||
<Summary>The content of this field is automatically calculated by the system based on fax number and country code components.</Summary>
|
||
<LongDescription>This field is therefore not to be filled when Business Address Services function modules are called.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AddressCommunicationRemarkText" Type="Edm.String" MaxLength="50" sap:label="Notes" sap:heading="Communication link notes" sap:quickinfo="Communication link notes">
|
||
<Documentation>
|
||
<Summary>Additional information about the communication connection</Summary>
|
||
<LongDescription>You can maintain further information about the communication connection here. In the case of telephone numbers, for example, you can maintain the times at which the call recipient is available and those at which they are not, or you can specify whether the number is that of the secretary.The information is stored in table ADRT, regardless of language.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_AddressHomePageURLType" sap:label="Home Page URL" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="AddressID"/>
|
||
<PropertyRef Name="Person"/>
|
||
<PropertyRef Name="OrdinalNumber"/>
|
||
<PropertyRef Name="ValidityStartDate"/>
|
||
<PropertyRef Name="IsDefaultURLAddress"/>
|
||
</Key>
|
||
<Property Name="AddressID" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Address Number" sap:heading="Addr. No.">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a Business Address Services address.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the address number and the Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Person" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Person Number" sap:heading="Person">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a person in Business Address Services.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the person number and Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="OrdinalNumber" Type="Edm.String" Nullable="false" MaxLength="3" sap:display-format="NonNegative" sap:label="Sequence Number" sap:heading="ID"/>
|
||
<Property Name="ValidityStartDate" Type="Edm.DateTime" Nullable="false" Precision="0" sap:display-format="Date" sap:label="from" sap:heading="From" sap:quickinfo="Valid-from date - in current Release only 00010101 possible"/>
|
||
<Property Name="IsDefaultURLAddress" Type="Edm.Boolean" Nullable="false" sap:display-format="UpperCase" sap:label="Standard addr." sap:heading="#" sap:quickinfo="Flag: this address is the default address"/>
|
||
<Property Name="SearchURLAddress" Type="Edm.String" MaxLength="50" sap:display-format="UpperCase" sap:label="URI address" sap:quickinfo="URI address search field"/>
|
||
<Property Name="AddressCommunicationRemarkText" Type="Edm.String" MaxLength="50" sap:label="Notes" sap:heading="Communication link notes" sap:quickinfo="Communication link notes">
|
||
<Documentation>
|
||
<Summary>Additional information about the communication connection</Summary>
|
||
<LongDescription>You can maintain further information about the communication connection here. In the case of telephone numbers, for example, you can maintain the times at which the call recipient is available and those at which they are not, or you can specify whether the number is that of the secretary.The information is stored in table ADRT, regardless of language.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="URLFieldLength" Type="Edm.Int16" sap:label="URI length" sap:quickinfo="URI field length"/>
|
||
<Property Name="WebsiteURL" Type="Edm.String" MaxLength="2048" sap:label="URI" sap:quickinfo="Universal Resource Identifier (URI)"/>
|
||
</EntityType>
|
||
<EntityType Name="A_AddressPhoneNumberType" sap:label="Phone Number" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="AddressID"/>
|
||
<PropertyRef Name="Person"/>
|
||
<PropertyRef Name="OrdinalNumber"/>
|
||
</Key>
|
||
<Property Name="AddressID" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Address Number" sap:heading="Addr. No.">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a Business Address Services address.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the address number and the Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Person" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Person Number" sap:heading="Person">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a person in Business Address Services.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the person number and Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="OrdinalNumber" Type="Edm.String" Nullable="false" MaxLength="3" sap:display-format="NonNegative" sap:label="Sequence Number" sap:heading="ID"/>
|
||
<Property Name="DestinationLocationCountry" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Country/Region" sap:heading="Ctry/Reg." sap:quickinfo="Country/Region for Telephone/Fax Number">
|
||
<Documentation>
|
||
<Summary>The country/region for the telephone number or fax number is maintained here.</Summary>
|
||
<LongDescription>This specification is used to determine the correct country/region code. A normalized form of the telephone number or fax number is then derived and stored in a field for a program-driven search.In most cases, the telephone number or fax number refers directly to an address.If this is the case, when a new number is created, the country/region of the address is proposed.If this is not the case (for example, with address-independent communication data for a business partner), the country/region from the user parameter LND is proposed (if it is maintained).If the user parameter LND is not maintained, the country/region of the company address assigned in the user master data is proposed.If the country/region of the address changes, the country/region of the corresponding telephone number and fax address is not changed automatically.Example: A business partner moves abroad.If the telephone number is for a permanent connection, the telephone number also changes when the business partner moves and has to be maintained again in the system.If the telephone number is for a mobile telephone and the number is retained, the original country/region for this telephone number also has to be retained and must not be changed automatically to the new country/region of the address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IsDefaultPhoneNumber" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Standard No." sap:heading="Standard Number" sap:quickinfo="Standard Sender Address in this Communication Type">
|
||
<Documentation>
|
||
<Summary>If several addresses are maintained for one communication type, the user in the SAP System can be reached under one of these addresses. One address can be set as theStandard Address.</Summary>
|
||
<LongDescription>The standard address is used for the following functions:When sending using the SMTP nodein SAPconnect, the home address of the communication type used is the one set as the sender address. The recipient can see this address in the sender information and can also reply directly to this address. The standard address is also transferred and can be used for incoming status notifications, for example.When sending using an RFC node in SAPconnect, the standard address of the communication type used is the one set as the sender address. The structure defined in the case of the RFC does not permit another address to be transferred, so the standard address is used for incoming status notifications too.The SAP users have the addresses of their exchange P.O. boxes in their standard communication type 'Internet Mail' as the home address and their Internet address in the SAP system as their standard address. Example:Home address: Bernard.Brown@Company.comStandard address: Bernard.Brown@System.Company.comSending using an SMTP nodeThe home address of the communication type 'Internet Mail' (Bernard.Brown@Company.com) is used as the sender address. If a reply is sent to this address the user receives directly in the exchange postbox.Sending using the RFC nodeThe standard address of the communication type 'Internet Mail' (Bernard.Brown@System.Company.com) is used as the sender address. If a reply is sent to this address, it arrives back to the SAP system.Example using a mail system groupThe users should get all messages in their Microsoft Exchange postboxes. In the SAP system the mail system group is activated for this using the setting "Send Messages to the Home Address".The address settings of the SAP users remain unchanged:Home address: Bernard.Brown@Company.comStandard address: Bernard.Brown@System.Company.comSending using an SMTP nodeThe home address of the communication type 'Internet Mail' (Bernard.Brown@Company.com) is used as the sender address. If a reply is sent to this address the user receives directly in the exchange postbox.Sending using the RFC nodeThe standard address of the communication type 'Internet Mail' (Bernard.Brown@System.Company.com) is used as the sender address. If a reply is sent to this address it arrives back in the SAP system. It is then forwarded using the mail system group to the home address and the user gets it in the exchange postbox.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PhoneNumber" Type="Edm.String" MaxLength="30" sap:display-format="UpperCase" sap:label="Telephone" sap:quickinfo="Telephone no.: dialling code+number">
|
||
<Documentation>
|
||
<Summary>Telephone number, consisting of dialling code and number, but without country dialling code.</Summary>
|
||
<LongDescription>If the telephone number consists of a company number and an extension, the extension must be entered in the field extension.Telephone number, as it is dialled from within the country.For the number "01234/567-0" enter the following:Telephone: 01234/567Estension: 0For the number "01234/567-891" enter the following:Telephone: 01234/567Extension: 891For the number "012-345-678" (678 as extension) enter the following:Telepone: 012-345Extension: 678In the following cases enter the complete number (without country dialling code) in the field Telephone:No part of the number can be regarded as an extension.You are not sure which part of the number can be regarded as an extension.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PhoneNumberExtension" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Extension" sap:quickinfo="Telephone no.: Extension">
|
||
<Documentation>
|
||
<Summary>Telephone extension number</Summary>
|
||
<LongDescription>If the telephone number consists of a company number and an extension, the extension should be entered here.Enter the extension.The following rules apply for the format of telephone and fax numbers:The length of the entries in the field Telephone and Extension (Fax and Extension) cannot be more than 24 characters in total.Leading spaces are not allowed in the field Telephone or Fax or in the field Extension.Valid characters are:Numbers (0123456789)Letters (ABCDEFGHIJKLMNOPQRSTUVWXYZ)Following other characters: /, (, ), - *, # and " " (space), but not as a leading space.If an + is entered as the first character, the system checks whether the specified number starts with a country code. If so, a warning message is displayed because the country code is automatically determined by the system and should not be stored in the Telephone number (Fax number) field.If an & is entered as the first character, the automatic check and formatting of the telephone number (fax number), as well as the determination of the country code, is suppressed.For the number "01234/567-0" enter the following:Telephone: 01234/567Estension: 0For the number "01234/567-891" enter the following:Telephone: 01234/567Extension: 891For the number "012-345-678" (678 as extension) enter the following:Telepone: 012-345Extension: 678In the following cases enter the complete number (without country dialling code) in the field Telephone:No part of the number can be regarded as an extension.You are not sure which part of the number can be regarded as an extension.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InternationalPhoneNumber" Type="Edm.String" MaxLength="30" sap:display-format="UpperCase" sap:label="Telephone Number" sap:quickinfo="Complete Number: Dialling Code+Number+Extension">
|
||
<Documentation>
|
||
<Summary>The content of this field is automatically calculated by the system based on the telephone number and country code components.</Summary>
|
||
<LongDescription>This field is therefore not to be filled when Business Address Services function modules are called.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PhoneNumberType" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Mobile phone" sap:quickinfo="Indicator: Telephone is a Mobile Telephone">
|
||
<Documentation>
|
||
<Summary>This field specifies whether the telephone number is a mobile telephone number.</Summary>
|
||
<LongDescription>' ' : The telephone number is a fixed-line telephone'1' : The telephone number is the standard fixed-line telephone'2' : The telephone nubmer is a mobile telephone'3' : The telephone number is the standard mobile telephoneEither the standard fixed-line telephone number or the standard mobile telephone number is also the standard telephone number (FLGDEFAULT = 'X').In older data sets, this field may have also have the value ' ' for the standard fixed-line telephone. In this case, however, FLGDEFAULT is always 'X'.In Customizing, you can specify whether the SMS-compatible indicator is to be proposed for new mobile telephone numbers created in dialog by choosing General Settings -> Set countries -> Define Mobile Telephone Attributes for each country.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AddressCommunicationRemarkText" Type="Edm.String" MaxLength="50" sap:label="Notes" sap:heading="Communication link notes" sap:quickinfo="Communication link notes">
|
||
<Documentation>
|
||
<Summary>Additional information about the communication connection</Summary>
|
||
<LongDescription>You can maintain further information about the communication connection here. In the case of telephone numbers, for example, you can maintain the times at which the call recipient is available and those at which they are not, or you can specify whether the number is that of the secretary.The information is stored in table ADRT, regardless of language.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_BPContactToAddressType" sap:label="Contact Person Address" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="RelationshipNumber"/>
|
||
<PropertyRef Name="BusinessPartnerCompany"/>
|
||
<PropertyRef Name="BusinessPartnerPerson"/>
|
||
<PropertyRef Name="ValidityEndDate"/>
|
||
<PropertyRef Name="AddressID"/>
|
||
</Key>
|
||
<Property Name="RelationshipNumber" Type="Edm.String" Nullable="false" MaxLength="12" sap:display-format="UpperCase" sap:label="BP Relationship No." sap:heading="BP Relation. No." sap:quickinfo="BP Relationship Number">
|
||
<Documentation>
|
||
<Summary>The business partner relationship number is an internal number that identifies the business partner relationship set.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartnerCompany" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartnerPerson" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ValidityEndDate" Type="Edm.DateTime" Nullable="false" Precision="0" sap:display-format="Date" sap:label="Valid To" sap:quickinfo="Validity Date (Valid To)"/>
|
||
<Property Name="AddressID" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Address Number" sap:heading="Addr. No.">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a Business Address Services address.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the address number and the Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AddressNumber" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Address Number" sap:heading="Addr. No.">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a Business Address Services address.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the address number and the Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AdditionalStreetPrefixName" Type="Edm.String" MaxLength="40" sap:label="Street 3">
|
||
<Documentation>
|
||
<Summary>Additional address field which is printed above the Street line.</Summary>
|
||
<LongDescription>The Street address contains two lines above the street and two lines below the street.See Print the Street address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AdditionalStreetSuffixName" Type="Edm.String" MaxLength="40" sap:label="Street 5">
|
||
<Documentation>
|
||
<Summary>Additional address field which is printed under the Street line.</Summary>
|
||
<LongDescription>The Street address has two lines above the street and two lines below the steet.See Print the Street address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AddressTimeZone" Type="Edm.String" MaxLength="6" sap:display-format="UpperCase" sap:label="Time zone" sap:heading="Zone" sap:quickinfo="Address time zone">
|
||
<Documentation>
|
||
<Summary>Time zone as part of an address.</Summary>
|
||
<LongDescription>The time zone is automatically determined by the system in address maintenance if time zone Customizing is maintained.It depends on the country and the region. (Region means state, province or county, depending on the country)The automatic determination is only made if there is no value in the time zone field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CareOfName" Type="Edm.String" MaxLength="40" sap:label="c/o" sap:heading="c/o name" sap:quickinfo="c/o name">
|
||
<Documentation>
|
||
<Summary>Part of the address (c/o = care of) if the recipient is different from the occupant and the names are not similar (e.g. subtenants).</Summary>
|
||
<LongDescription>Put the country-specific code (e.g. c/o) in front of the name of the occupant. This is not automatically done in the print format, like the language-specific word "PO Box".John Smithc/o David BrownThis field is not always automatically printed, as it was subsequently added to the address structure.The print program or form may need to be adjusted.This exception applies to the following fields:Street2, Street3, Street4, Street5, c/o name, and to all address fields added after Release 4.5.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CityCode" Type="Edm.String" MaxLength="12" sap:display-format="UpperCase" sap:label="City Code" sap:quickinfo="City code for city/street file"/>
|
||
<Property Name="CityName" Type="Edm.String" MaxLength="40" sap:label="City">
|
||
<Documentation>
|
||
<Summary>City name as part of the address.</Summary>
|
||
<LongDescription>The city name is saved redundantly in another database field in upper- case letters, for search help.If the Postal regional structure ('city file') is active, the city name is checked against the Cities defined in the regional structure.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CompanyPostalCode" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Company Postal Code" sap:heading="Postl Code" sap:quickinfo="Company Postal Code (for Large Customers)">
|
||
<Documentation>
|
||
<Summary>Postal code that is assigned directly to one company (= company postal code = major customer postal code).</Summary>
|
||
<LongDescription>This field is used for countries where major companies are assigned their own postal code by the national post office.This postal code has to be entered in the field "Company Postal Code". Postal codes for group major customers, however, have to be entered in the field "PO Box Postal Code", since individual customers with a shared postal code for group major customers are differentiated by means of their PO box.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Country" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Country/Region Key" sap:heading="C/R">
|
||
<Documentation>
|
||
<Summary>The country/region key contains information which the system uses to check entries such as the length of the postal code or bank account number.</Summary>
|
||
<LongDescription>The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.It could also be the vehicle license plate country/region code or a typical country/region key, for example, in Germany the Federal statistics office key.The country/region keys are determined at system installation in the global settings.The definition of the country/region keys in the SAP system does not necessarily have to match political or state units.Since the country/region key does not have to correspond to the ISO code in all installations, programs that differ according to certain values of the country/region key cannot query the country/region key T005-LAND1, but have to program based on the ISO code T005 INTCA.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="County" Type="Edm.String" MaxLength="40" sap:label="County">
|
||
<Documentation>
|
||
<Summary>Specifies the county’s name</Summary>
|
||
<LongDescription>This field is used to store the county’s name. You can enter the name of the county in this field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DeliveryServiceNumber" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Delivery Service No." sap:heading="Delivery Service Number" sap:quickinfo="Number of Delivery Service">
|
||
<Documentation>
|
||
<Summary>The delivery service is part of the PO box address.</Summary>
|
||
<LongDescription>Some countries offer different services in addition to regular postal delivery and PO boxes, for example the Private Bag or Response Bag. If an address is related to one of these delivery services, the information about this particular delivery service has to be entered in the corresponding fields.In the field "Number of Delivery Service," the number of the Private Bag, Response Bag, or other relevant service has to be entered. Entering a number is not mandatory for each delivery service.For each address, either the information about the PO box or the information about the delivery service can be entered, but not both types of information at the same time.Mr PickeringPrivate Bag 106999Timaru 7942Delivery services will only be taken into account for address formatting in countries in which they are commonly used in addition to regular postal delivery and PO boxes, for example, in Australia, New Zealand, and the USA. In all other countries, these fields will not be taken into account for address formatting.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DeliveryServiceTypeCode" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Delvry Serv Type" sap:quickinfo="Type of Delivery Service">
|
||
<Documentation>
|
||
<Summary>The delivery service is part of the PO box address.</Summary>
|
||
<LongDescription>Some countries offer different services in addition to regular postal delivery and PO boxes, for example the Private Bag or Response Bag. If an address is related to one of these delivery services, the information about this particular delivery service has to be entered in the corresponding fields.In the field "Type of Delivery Service," the type of the delivery service has to be entered.For each address, either the information about the PO box or the information about the delivery service can be entered, but not both types of information at the same time.Mr PickeringPrivate Bag 106999Timaru 7942Delivery services will only be taken into account for address formatting in countries in which they are commonly used in addition to regular postal delivery and PO boxes, for example, in Australia, New Zealand, and the USA. In all other countries, these fields will not be taken into account for address formatting.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="District" Type="Edm.String" MaxLength="40" sap:label="District">
|
||
<Documentation>
|
||
<Summary>City or District supplement</Summary>
|
||
<LongDescription>In some countries, this entry is appended with a hyphen to the city name by the automatic address formatting, other countries, it is output on a line of its own or (e.g. in the USA) not printed.See the examples in the Address Layout Key documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="FormOfAddress" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Title" sap:heading="Key" sap:quickinfo="Form-of-Address Key" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Key for form of address text.</Summary>
|
||
<LongDescription>You can also define a form of address text in Customizing.The form of address text can be maintained in different languages.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="FullName" Type="Edm.String" MaxLength="80" sap:label="Full Name" sap:quickinfo="Full name of a party (Bus. Partner, Org. Unit, Doc. address)" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>This field contains the full name or formatted name of a party.</Summary>
|
||
<LongDescription>For organizations or document addresses, typically the fields Name1 and Name2 are concatenated.For persons the field contains the formatted name according to country specific rules. It corresponds e.g. to the content of the fields BUT000-NAME1_TEXT or ADRP-NAME_TEXT.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="HomeCityName" Type="Edm.String" MaxLength="40" sap:label="Different City" sap:heading="City (Diff. from Postal City)" sap:quickinfo="City (different from postal city)">
|
||
<Documentation>
|
||
<Summary>City of residence which is different from the postal city</Summary>
|
||
<LongDescription>In some countries, the residential city is required if it differs from the postal city.In the USA, the official street indexes, against which data can be checked, are based on the residential city, not the postal city, which may be different.It is the same in France, where a postally correct address must contain the residential city in a separate line above the postal city, if it differs from the postal city.This field is not always automatically printed, as it was subsequently added to the address structure.The print program or form may need to be adjusted.This exception applies to the following fields:Street2, Street3, Street4, Street5, c/o name, and to all address fields added after Release 4.5.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="HouseNumber" Type="Edm.String" MaxLength="10" sap:label="House Number" sap:heading="House No.">
|
||
<Documentation>
|
||
<Summary>House number as part of an address.</Summary>
|
||
<LongDescription>It is printed in the Street line.Other supplementary street information can be entered in the House number supplement or one of the Street2, Street3, Street4 or Street5 fields. See Print the Street address.A house number (e.g. 117) or a house number with supplement (e.g. 117a), or a house number range (e.g. 16-20), can be maintained in this field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="HouseNumberSupplementText" Type="Edm.String" MaxLength="10" sap:label="Supplement" sap:quickinfo="House number supplement">
|
||
<Documentation>
|
||
<Summary>House number supplement as part of an address, e.g.</Summary>
|
||
<LongDescription>App. 17 orSuite 600.It is printed in the Street line.Further Street supplements can be put in one of the fields Street2, Street3, Street4 or Street5.See Print the Street address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Language" Type="Edm.String" MaxLength="2" sap:label="Language Key" sap:heading="Language">
|
||
<Documentation>
|
||
<Summary>The language key indicates</Summary>
|
||
<LongDescription>- the language in which texts are displayed,- the language in which you enter texts,- the language in which the system prints texts.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBox" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="PO Box">
|
||
<Documentation>
|
||
<Summary>PO Box number as part of an address.</Summary>
|
||
<LongDescription>Only enter the PO Box number in this field. The text "PO Box" is provided in the recipient language by the system when you print the address.When you print an address, the "Street address" and the "PO Box address" are distinguished. The print program determines which of them has priority if both are maintained in an address record.Besides the PO Box number, the PO Box address uses the following fields:PO Box postal code, if specified (otherwise the normal postal code)PO Box city, if specified (otherwise the normal city)PO Box region, if specified (otherwise the normal region)PO Box country, if specified (otherwise the normal country)If the address is a "PO Box" (without a number), do not fill the "PO Box" field. Select the "PO Box w/o Number" indicator instead.You can also enter a company postal code for organizational addresses, instead of a PO Box. A separate field is predefined for this entry.For general information and examples about address formatting, see the documentation on the Address Structure Key.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBoxDeviatingCityName" Type="Edm.String" MaxLength="40" sap:label="PO Box City" sap:quickinfo="PO Box city">
|
||
<Documentation>
|
||
<Summary>Different city for the PO Box as an address component.</Summary>
|
||
<LongDescription>The PO Box city can be entered here if it is different from the address city.If the address is only a PO Box address, enter the city in the normal city field.If the address contains two different city names for the address and the PO Box address, use this field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBoxDeviatingCountry" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="PO Box Ctry/Region" sap:heading="PO C/R" sap:quickinfo="PO Box of Country/Region">
|
||
<Documentation>
|
||
<Summary>Other country/region for PO box in an address.</Summary>
|
||
<LongDescription>Here you can enter the country/region for the PO box if this country/region is different to the country/region of the street address.If the address only has a PO box address, you enter the country/region in in the normal field for country/region.If the street address and the PO box belong to two different countries/regions, you fill this field.This field is not always automatically printed, as it was subsequently added to the address structure.The print program or form may need to be adjusted.This exception applies to the following fields:Street2, Street3, Street4, Street5, c/o name, and to all address fields added after Release 4.5.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBoxDeviatingRegion" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="PO Box Region" sap:heading="PO Region" sap:quickinfo="Region for PO Box (Country, State, Province, ...)">
|
||
<Documentation>
|
||
<Summary>Different Region for PO Box in an address.</Summary>
|
||
<LongDescription>Enter the PO Box Region here, if it differs from the street address region.If the address only has a PO Box address, the Region in in the normal Region field.Use this field if the address has two different Region values for the street address and the PO Box address.This field is not always automatically printed, as it was subsequently added to the address structure.The print program or form may need to be adjusted.This exception applies to the following fields:Street2, Street3, Street4, Street5, c/o name, and to all address fields added after Release 4.5.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBoxIsWithoutNumber" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="PO Box w/o No." sap:heading="PO" sap:quickinfo="Flag: PO Box Without Number">
|
||
<Documentation>
|
||
<Summary>PO Box address without PO Box number flag.</Summary>
|
||
<LongDescription>Only the word 'PO Box' is output in PO Box addresses without PO Box number.Set this flag for a PO Box address without PO Box number.This field is not always automatically printed, as it was subsequently added to the address structure.The print program or form may need to be adjusted.This exception applies to the following fields:Street2, Street3, Street4, Street5, c/o name, and to all address fields added after Release 4.5.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBoxLobbyName" Type="Edm.String" MaxLength="40" sap:label="PO Box Lobby">
|
||
<Documentation>
|
||
<Summary>The PO box lobby is part of the PO box address.</Summary>
|
||
<LongDescription>In some countries, entering a PO box, postal code and city is not sufficient to uniquely identify a PO box, because the same PO box number is assigned multiple times in some cities.Therefore, additional information might be required to determine the post office of the PO box in question. This information can be entered in the field "PO Box Lobby."Mr NellingPO Box 4099HighfieldTimaru 7942The PO box lobby will only be taken into account for address formatting in countries in which it is commonly used in addition to regular postal delivery and PO boxes, for example, in Canada or New Zealand. In all other countries, this field will not be taken into account for address formatting.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBoxPostalCode" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="PO Box Postal Code" sap:heading="Postl Code">
|
||
<Documentation>
|
||
<Summary>Postal code that is required for a unique assignment of the PO box.</Summary>
|
||
<LongDescription>This field is used for countries where a different postal code applies to mail that is sent to the PO box rather than to the street address of a particular business partner.Postal codes for group major customers also have to be entered in the field for the PO box postal code since individual customers with a shared postal code for group major customers are differentiated by means of the PO box. Postal codes for major customers (= company postal codes), however, are assigned to one customer only and have to be entered in the field 'Company Postal Code'.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Person" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Person Number" sap:heading="Person" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a person in Business Address Services.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the person number and Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PostalCode" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Postal Code" sap:heading="Post. Code" sap:quickinfo="City Postal Code">
|
||
<Documentation>
|
||
<Summary>Postal code as part of the address</Summary>
|
||
<LongDescription>If different postal codes are maintained for the PO Box and Street address of an address, this field contains the Street address postal code.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PrfrdCommMediumType" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Comm. Method" sap:quickinfo="Communication Method (Key) (Business Address Services)">
|
||
<Documentation>
|
||
<Summary>Communication method with which you can exchange documents and messages with a business partner.</Summary>
|
||
<LongDescription>In Business Address Services, you can specify a standard communication method that can be used by programs to determine the means of communication for sending messages.One business partner wants all messages by fax, another by e-mail.The application context can restrict the possible methods of communication. For example, invitations should perhaps only be sent by post because of enclosures, whereas minutes can be sent by post, fax or e-mail.Communication strategies can be defined for this purpose and applied in application contexts.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Region" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Region" sap:heading="Rg" sap:quickinfo="Region (State, Province, County)">
|
||
<Documentation>
|
||
<Summary>In some countries, the region forms part of the address. The meaning depends on the country.</Summary>
|
||
<LongDescription>The automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.For more information, see the examples in the documentation on the Address Layout Key.Meaning of the regional code in ...Australia -> ProvinceBrazil -> StateCanada -> ProvinceGermany -> StateGreat Britain -> CountyItaly -> ProvinceJapan -> PrefectureSwitzerland -> CantonUSA -> State</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="StreetName" Type="Edm.String" MaxLength="60" sap:label="Street">
|
||
<Documentation>
|
||
<Summary>Street name as part of the address.</Summary>
|
||
<LongDescription>The street name is saved, redundantly in upper case in another database field, for search help purposes.There are other fields for address parts which can be printed above or below the street. See Print the Street address.The house number and other supplements are usually maintained in their own fields. See Formatting the Street line.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="StreetPrefixName" Type="Edm.String" MaxLength="40" sap:label="Street 2">
|
||
<Documentation>
|
||
<Summary>Additional address field which is printed above the Street line.</Summary>
|
||
<LongDescription>The Street address contains two lines above the street and two lines below the street.See Print the Street address.This field is not always automatically printed, as it was subsequently added to the address structure.The print program or form may need to be adjusted.This exception applies to the following fields:Street2, Street3, Street4, Street5, c/o name, and to all address fields added after Release 4.5.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="StreetSuffixName" Type="Edm.String" MaxLength="40" sap:label="Street 4">
|
||
<Documentation>
|
||
<Summary>Additional address field which is printed below the Street line.</Summary>
|
||
<LongDescription>The Street address contains two lines above the street and two lines below the street.See Print the Street address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxJurisdiction" Type="Edm.String" MaxLength="15" sap:display-format="UpperCase" sap:label="Tax Jurisdiction">
|
||
<Documentation>
|
||
<Summary>Specifies the tax jurisdiction.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TransportZone" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Transportation Zone" sap:heading="TranspZone" sap:quickinfo="Transportation zone to or from which the goods are delivered">
|
||
<Documentation>
|
||
<Summary>Sales and distribution:</Summary>
|
||
<LongDescription>Regional zone of Goods recipient.Purchasing:Regional zone of supplier.You can define regional zones to suit the requirements of your own business and country.Sales and distributionthe system automatically proposes a suitable route by using the transportation zone of the goods recipient in combination with other information about the delivery, such as theCountries of origin and destinationShipping conditionsTransportation groupIn the USA, for example, you can define regional zones to correspond to the US postal zip codes.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AddressRepresentationCode" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Address Version" sap:heading="Version" sap:quickinfo="Version ID for International Addresses">
|
||
<Documentation>
|
||
<Summary>Version indicator of an address.</Summary>
|
||
<LongDescription>You can maintain addresses in multiple versions. In this way, addresses can be stored in the system in different international display formats (such as Kanji or Latin letters).The version indicator is a part of the address key.You can use the standard version keys or enter your own version keys in the view V_SAPTSADV.For more information, see the section 'Print Formatting for Addresses' in the BAS documentation (see SAP note 383362).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ContactRelationshipFunction" Type="Edm.String" MaxLength="40" sap:label="Function">
|
||
<Documentation>
|
||
<Summary>Function of a person, e.g. as contact person in a company.</Summary>
|
||
<LongDescription>In anglo-saxon countries this is often part of the formatted address (e.g. in an address window).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ContactRelationshipDepartment" Type="Edm.String" MaxLength="40" sap:label="Department">
|
||
<Documentation>
|
||
<Summary>This field contains the department in a company as part of the company address.</Summary>
|
||
<LongDescription>It is the department name used at the customer for a customer contact person.It is usually the same as the department name used on business cards.The department is printed, e.g.:SAP AGBasis Technology <<<<Herr Peter LarssonNeurottstr. 16D-69190 Walldorf</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Floor" Type="Edm.String" MaxLength="10" sap:label="Floor" sap:quickinfo="Floor in building">
|
||
<Documentation>
|
||
<Summary>Floor of the building as more exact specification of an address.</Summary>
|
||
<LongDescription>This field is not printed in the address.Floors which should be printed must be in the field house number supplement or in one of the fields Street2, Street3, Street4 or Street5 depending on the desired position. See Print the Street address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ContactPersonBuilding" Type="Edm.String" MaxLength="10" sap:label="Building code" sap:heading="Buildings" sap:quickinfo="Building (number or code)">
|
||
<Documentation>
|
||
<Summary>Number or ID for the building in a contact person address.</Summary>
|
||
<LongDescription>This field is not printed.This is not the same as the building name which is part of an address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="RoomNumber" Type="Edm.String" MaxLength="10" sap:label="Room Number" sap:heading="Room No." sap:quickinfo="Room or Apartment Number">
|
||
<Documentation>
|
||
<Summary>Appartment or room number in an a ddress.</Summary>
|
||
<LongDescription>This field is not printed.Entries which are to be printed must in the house number supplement field or in one of the Street2, Street3, Street4 or Street5 fields, depending on the desired position. See Print the Street address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ContactPersonPrfrdCommMedium" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Comm. Method" sap:quickinfo="Communication Method (Key) (Business Address Services)">
|
||
<Documentation>
|
||
<Summary>Communication method with which you can exchange documents and messages with a business partner.</Summary>
|
||
<LongDescription>In Business Address Services, you can specify a standard communication method that can be used by programs to determine the means of communication for sending messages.One business partner wants all messages by fax, another by e-mail.The application context can restrict the possible methods of communication. For example, invitations should perhaps only be sent by post because of enclosures, whereas minutes can be sent by post, fax or e-mail.Communication strategies can be defined for this purpose and applied in application contexts.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CorrespondenceShortName" Type="Edm.String" MaxLength="10" sap:label="Short name" sap:quickinfo="Short name for correspondence"/>
|
||
<Property Name="InhouseMail" Type="Edm.String" MaxLength="10" sap:label="Internal mail" sap:heading="Internal" sap:quickinfo="Internal Mail Postal Code"/>
|
||
<NavigationProperty Name="to_EmailAddress" Relationship="API_BUSINESS_PARTNER.assoc_76A1D4C9690D91482219A96E6133DCA1" FromRole="FromRole_assoc_76A1D4C9690D91482219A96E6133DCA1" ToRole="ToRole_assoc_76A1D4C9690D91482219A96E6133DCA1"/>
|
||
<NavigationProperty Name="to_FaxNumber" Relationship="API_BUSINESS_PARTNER.assoc_EC8BD55FE296CB9F7E96A12A10A83C8A" FromRole="FromRole_assoc_EC8BD55FE296CB9F7E96A12A10A83C8A" ToRole="ToRole_assoc_EC8BD55FE296CB9F7E96A12A10A83C8A"/>
|
||
<NavigationProperty Name="to_MobilePhoneNumber" Relationship="API_BUSINESS_PARTNER.assoc_A30D7A481BC8C28A25685BA876365019" FromRole="FromRole_assoc_A30D7A481BC8C28A25685BA876365019" ToRole="ToRole_assoc_A30D7A481BC8C28A25685BA876365019"/>
|
||
<NavigationProperty Name="to_PhoneNumber" Relationship="API_BUSINESS_PARTNER.assoc_E5744DCC3F8BA081306832D86DBAE35B" FromRole="FromRole_assoc_E5744DCC3F8BA081306832D86DBAE35B" ToRole="ToRole_assoc_E5744DCC3F8BA081306832D86DBAE35B"/>
|
||
<NavigationProperty Name="to_URLAddress" Relationship="API_BUSINESS_PARTNER.assoc_313909BAAED14CA9CB4829C648286478" FromRole="FromRole_assoc_313909BAAED14CA9CB4829C648286478" ToRole="ToRole_assoc_313909BAAED14CA9CB4829C648286478"/>
|
||
</EntityType>
|
||
<EntityType Name="A_BPContactToFuncAndDeptType" sap:label="Function and Department" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="RelationshipNumber"/>
|
||
<PropertyRef Name="BusinessPartnerCompany"/>
|
||
<PropertyRef Name="BusinessPartnerPerson"/>
|
||
<PropertyRef Name="ValidityEndDate"/>
|
||
</Key>
|
||
<Property Name="RelationshipNumber" Type="Edm.String" Nullable="false" MaxLength="12" sap:display-format="UpperCase" sap:label="BP Relationship No." sap:heading="BP Relation. No." sap:quickinfo="BP Relationship Number">
|
||
<Documentation>
|
||
<Summary>The business partner relationship number is an internal number that identifies the business partner relationship set.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartnerCompany" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartnerPerson" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ValidityEndDate" Type="Edm.DateTime" Nullable="false" Precision="0" sap:display-format="Date" sap:label="Valid To" sap:quickinfo="Validity Date (Valid To)"/>
|
||
<Property Name="ContactPersonFunction" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Function" sap:heading="Fct" sap:quickinfo="Function of partner">
|
||
<Documentation>
|
||
<Summary>Identifies the function that a person has within a company.</Summary>
|
||
<LongDescription>This is a contact person attribute that you can define in Customizing.Personnel managerSecretary</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ContactPersonDepartment" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Department" sap:heading="Dept">
|
||
<Documentation>
|
||
<Summary>Name of the department of a business partner for your internal usage.</Summary>
|
||
<LongDescription>The name given by the business partner to this particular department may differ from the name that you use. You can enter the name given by the business partner in the field company department.This is a contact person attribute that you can define in Customizing.For your purposes, the department name is "Sales". The business partner names the same department "Sales South".</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PhoneNumber" Type="Edm.String" MaxLength="30" sap:display-format="UpperCase" sap:label="Telephone" sap:quickinfo="Telephone no.: dialling code+number">
|
||
<Documentation>
|
||
<Summary>Telephone number, consisting of dialling code and number, but without country dialling code.</Summary>
|
||
<LongDescription>If the telephone number consists of a company number and an extension, the extension must be entered in the field extension.Telephone number, as it is dialled from within the country.For the number "01234/567-0" enter the following:Telephone: 01234/567Estension: 0For the number "01234/567-891" enter the following:Telephone: 01234/567Extension: 891For the number "012-345-678" (678 as extension) enter the following:Telepone: 012-345Extension: 678In the following cases enter the complete number (without country dialling code) in the field Telephone:No part of the number can be regarded as an extension.You are not sure which part of the number can be regarded as an extension.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PhoneNumberExtension" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Extension" sap:quickinfo="Telephone no.: Extension">
|
||
<Documentation>
|
||
<Summary>Telephone extension number</Summary>
|
||
<LongDescription>If the telephone number consists of a company number and an extension, the extension should be entered here.Enter the extension.The following rules apply for the format of telephone and fax numbers:The length of the entries in the field Telephone and Extension (Fax and Extension) cannot be more than 24 characters in total.Leading spaces are not allowed in the field Telephone or Fax or in the field Extension.Valid characters are:Numbers (0123456789)Letters (ABCDEFGHIJKLMNOPQRSTUVWXYZ)Following other characters: /, (, ), - *, # and " " (space), but not as a leading space.If an + is entered as the first character, the system checks whether the specified number starts with a country code. If so, a warning message is displayed because the country code is automatically determined by the system and should not be stored in the Telephone number (Fax number) field.If an & is entered as the first character, the automatic check and formatting of the telephone number (fax number), as well as the determination of the country code, is suppressed.For the number "01234/567-0" enter the following:Telephone: 01234/567Estension: 0For the number "01234/567-891" enter the following:Telephone: 01234/567Extension: 891For the number "012-345-678" (678 as extension) enter the following:Telepone: 012-345Extension: 678In the following cases enter the complete number (without country dialling code) in the field Telephone:No part of the number can be regarded as an extension.You are not sure which part of the number can be regarded as an extension.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="FaxNumber" Type="Edm.String" MaxLength="30" sap:display-format="UpperCase" sap:label="Fax" sap:quickinfo="Fax number: dialling code+number">
|
||
<Documentation>
|
||
<Summary>Fax number, consisting of dialling code and number, but without country dialling code.</Summary>
|
||
<LongDescription>If the fax number consists of a company number and an extension, the extension must be entered in the field extension.Fax number, as it is to be dialled from within the same country.Enter the following for the number "01234/567-0":Fax: 01234/567Extension: 0Enter the following for the number "01234/567-891":Fax: 01234/567Extension: 891For the number "012-345-678" (678 as extension) enter the following:Fax: 012-345Extension: 678In the following cases, enter the complete number (without country dialing code) in the field Fax:No part of the number can be considered as an extension.You are not sure which part of the number can be considered as an extension.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="FaxNumberExtension" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Extension" sap:quickinfo="Fax no.: Extension">
|
||
<Documentation>
|
||
<Summary>Fax extension number</Summary>
|
||
<LongDescription>If the fax number consists of a company number and an extension, the extension must be entered here.Enter the extensionThe following rules apply for the format of telephone and fax numbers:The length of the entries in the field Telephone and Extension (Fax and Extension) cannot be more than 24 characters in total.Leading spaces are not allowed in the field Telephone or Fax or in the field Extension.Valid characters are:Numbers (0123456789)Letters (ABCDEFGHIJKLMNOPQRSTUVWXYZ)Following other characters: /, (, ), - *, # and " " (space), but not as a leading space.If an + is entered as the first character, the system checks whether the specified number starts with a country code. If so, a warning message is displayed because the country code is automatically determined by the system and should not be stored in the Telephone number (Fax number) field.If an & is entered as the first character, the automatic check and formatting of the telephone number (fax number), as well as the determination of the country code, is suppressed.Enter the following for the number "01234/567-0":Fax: 01234/567Extension: 0Enter the following for the number "01234/567-891":Fax: 01234/567Extension: 891For the number "012-345-678" (678 as extension) enter the following:Fax: 012-345Extension: 678In the following cases, enter the complete number (without country dialing code) in the field Fax:No part of the number can be considered as an extension.You are not sure which part of the number can be considered as an extension.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="EmailAddress" Type="Edm.String" MaxLength="241" sap:label="Email Address">
|
||
<Documentation>
|
||
<Summary>Internet mail address, also called e-mail address.</Summary>
|
||
<LongDescription>Example: user.name@company.comThe Internet mail address is used to send mail via the Internet world-wide; the protocol used is SMTP (Simple Mail Transfer Protocol).The Internet mail address format is specified in various RFCs (Internet Request for Comment), including RFCs 821 and 822.This is not an IP address (192.56.30.6).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="RelationshipCategory" Type="Edm.String" MaxLength="6" sap:display-format="UpperCase" sap:label="Relationship Cat." sap:heading="RelCat" sap:quickinfo="Business Partner Relationship Category">
|
||
<Documentation>
|
||
<Summary>A relationship may exist between two business partners. The business partner relationship category characterizes the features of the relationship.</Summary>
|
||
<LongDescription>A distinction is made between a one-way and an undirected business partner relationship category. In a one-way relationship category, the relationship extends from one partner to another, but not vice versa.Marriage (undirected)Employee (one-way)Contact person (one-way)</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_BuPaAddressUsageType" sap:label="Address Usage" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="BusinessPartner"/>
|
||
<PropertyRef Name="ValidityEndDate"/>
|
||
<PropertyRef Name="AddressUsage"/>
|
||
<PropertyRef Name="AddressID"/>
|
||
</Key>
|
||
<Property Name="BusinessPartner" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ValidityEndDate" Type="Edm.DateTimeOffset" Nullable="false" Precision="0" sap:label="Valid To" sap:quickinfo="Validity End of a Business Partner Address Usage"/>
|
||
<Property Name="AddressUsage" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Address Type" sap:heading="Addr">
|
||
<Documentation>
|
||
<Summary>Business partner attribute, which you can use to distinguish between various addresses by defining the address usage for communication with business partners.</Summary>
|
||
<LongDescription>Maintain the usage types for addresses (address types) in Customizing.You can create a short description and a name for the address type.When maintaining business partners you can use the function address usage to assign business partner addresses to address types.If necessary, you can set the indicator for multiple use in Customizing.Correspondence addressDelivery address</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AddressID" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Address Number" sap:heading="Addr. No.">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a Business Address Services address.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the address number and the Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ValidityStartDate" Type="Edm.DateTimeOffset" Precision="0" sap:label="Valid From" sap:quickinfo="Validity Start of a Business Partner Address Usage"/>
|
||
<Property Name="StandardUsage" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Standard Usage" sap:quickinfo="Indicator: Standard Address Usage">
|
||
<Documentation>
|
||
<Summary>Establishes which is the standard address for an address usage.</Summary>
|
||
<LongDescription>Several addresses per period can be assigned to an address usage.If this is the case, then this indicator controls which of the assigned addresses should be the standard address of the relevant usage. This is determined automatically when the address usage is accessed.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization Group" sap:heading="AGrp">
|
||
<Documentation>
|
||
<Summary>You can use authorization groups to stipulate which business partners a user is allowed to process.</Summary>
|
||
<LongDescription>Use the following authorization object:'Business partners: authorization groups' (B_BUPA_GRP).The system only checks this authorization if you made an entry in the "Authorization group" field for the business partner. Otherwise, any user may process the business partner.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_BuPaIdentificationType" sap:label="Identification" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="BusinessPartner"/>
|
||
<PropertyRef Name="BPIdentificationType"/>
|
||
<PropertyRef Name="BPIdentificationNumber"/>
|
||
</Key>
|
||
<Property Name="BusinessPartner" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BPIdentificationType" Type="Edm.String" Nullable="false" MaxLength="6" sap:display-format="UpperCase" sap:label="Identification Type" sap:heading="IDType">
|
||
<Documentation>
|
||
<Summary>A document (such as an ID card or driver's license) or an entry in a system of records (such as a commercial register) whose key can be stored as an attribute for a business partner.</Summary>
|
||
<LongDescription>The identification type is for classifying identification numbers.You can define the identification types and their descriptions in Customizing.You can also specify for which business partner category an ID type should be valid.If necessary, assign the identification type to an Identification Category.You can only assign one identification type to an identification category.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BPIdentificationNumber" Type="Edm.String" Nullable="false" MaxLength="60" sap:display-format="UpperCase" sap:label="ID number" sap:heading="Identification number" sap:quickinfo="Identification Number">
|
||
<Documentation>
|
||
<Summary>Number that serves to identify a business partner, such as driver's license, or ID card number.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BPIdnNmbrIssuingInstitute" Type="Edm.String" MaxLength="40" sap:label="Responsible Institn" sap:heading="Responsible Institution" sap:quickinfo="Responsible Institution for ID Number">
|
||
<Documentation>
|
||
<Summary>Institution that adminsters or assigns an ID number.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BPIdentificationEntryDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Entry date" sap:quickinfo="Date of Entry for ID Number">
|
||
<Documentation>
|
||
<Summary>Date on which the ID number was registered or assigned by the appropriate authority.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Country" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Country/Region" sap:heading="C/R" sap:quickinfo="Country/Region in Which ID Number is Valid or Was Assigned">
|
||
<Documentation>
|
||
<Summary>Country/region in which an ID number was assigned, or in which the number is valid.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Region" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Region" sap:heading="Rg" sap:quickinfo="Region (State, Province, County)">
|
||
<Documentation>
|
||
<Summary>In some countries, the region forms part of the address. The meaning depends on the country.</Summary>
|
||
<LongDescription>The automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.For more information, see the examples in the documentation on the Address Layout Key.Meaning of the regional code in ...Australia -> ProvinceBrazil -> StateCanada -> ProvinceGermany -> StateGreat Britain -> CountyItaly -> ProvinceJapan -> PrefectureSwitzerland -> CantonUSA -> State</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ValidityStartDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Valid from" sap:quickinfo="Validity Start for ID Number">
|
||
<Documentation>
|
||
<Summary>This date marks the start of validity of an ID number.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ValidityEndDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Valid To" sap:quickinfo="Validity End for ID Number">
|
||
<Documentation>
|
||
<Summary>This date marks the end of validity of an ID number.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization Group" sap:heading="AGrp">
|
||
<Documentation>
|
||
<Summary>You can use authorization groups to stipulate which business partners a user is allowed to process.</Summary>
|
||
<LongDescription>Use the following authorization object:'Business partners: authorization groups' (B_BUPA_GRP).The system only checks this authorization if you made an entry in the "Authorization group" field for the business partner. Otherwise, any user may process the business partner.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_BuPaIndustryType" sap:label="Industry" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="IndustrySector"/>
|
||
<PropertyRef Name="IndustrySystemType"/>
|
||
<PropertyRef Name="BusinessPartner"/>
|
||
</Key>
|
||
<Property Name="IndustrySector" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Industry">
|
||
<Documentation>
|
||
<Summary>Describes an industry.</Summary>
|
||
<LongDescription>An industry is a classification of companies according to their main business activity. For example, you can use Commerce, Banking, Services, Industry, Healthcare, Public Sector, Media, and so on, as industries.You can define industries along with their descriptions in Customizing.Assign the industry key to an industry key system.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IndustrySystemType" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Industry System" sap:heading="System">
|
||
<Documentation>
|
||
<Summary>Serves to combine and categorize several industries into a group.</Summary>
|
||
<LongDescription>You can create different industry systems, each with its own catalog of industries, whereby an industry can be assigned to several industry systems.You have to select one industry system as the standard industry system. This is then automatically displayed in the initial screen for the maintenance of industry data.You can define an industry system along with its description in Customizing. You can assign several industry systems to a business partner.If you choose the button All Industry Systems, you can access all the industry systems defined in the Customizing using the input help.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartner" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IsStandardIndustry" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Standard Industry" sap:heading="Standard" sap:quickinfo="Industry is Standard for BP in Industry System">
|
||
<Documentation>
|
||
<Summary>Identifies the industry in an industry system that can be defined as the standard industry.</Summary>
|
||
<LongDescription>It is recommended that you define an industry within an industry system as the standard industry, because only the standard industries can be determined at the interfaces to BW or the APIs, for example.This means that even if only one industry exists within an industry system, it should be indicated as the standard industry as this this information cannot be determined otherwise.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IndustryKeyDescription" Type="Edm.String" MaxLength="100" sap:label="Description"/>
|
||
</EntityType>
|
||
<EntityType Name="A_BusinessPartnerType" sap:label="Business Partner" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="BusinessPartner"/>
|
||
</Key>
|
||
<Property Name="BusinessPartner" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Customer" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Supplier" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Supplier" sap:quickinfo="Account Number of Supplier" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AcademicTitle" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Academic Title 1" sap:quickinfo="Academic Title: Key">
|
||
<Documentation>
|
||
<Summary>Key for academic title.</Summary>
|
||
<LongDescription>You can define a key for an academic title in Customizing.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization Group" sap:heading="AGrp">
|
||
<Documentation>
|
||
<Summary>You can use authorization groups to stipulate which business partners a user is allowed to process.</Summary>
|
||
<LongDescription>Use the following authorization object:'Business partners: authorization groups' (B_BUPA_GRP).The system only checks this authorization if you made an entry in the "Authorization group" field for the business partner. Otherwise, any user may process the business partner.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartnerCategory" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="BP Category" sap:heading="BPC" sap:quickinfo="Business Partner Category">
|
||
<Documentation>
|
||
<Summary>Category under which a business partner is classified.</Summary>
|
||
<LongDescription>You can distinguish between the following business partner categories:OrganizationNatural personGroup of natural persons or organizationsThe processing screens for the business partner categories are set up differently.So, for example, the screen for an organization contains the field Legal form, but this is not needed in the screen for a natural person.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartnerFullName" Type="Edm.String" MaxLength="81" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="BusinessPartnerGrouping" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Grouping" sap:heading="Grp." sap:quickinfo="Business Partner Grouping">
|
||
<Documentation>
|
||
<Summary>Classification assigned when creating a business partner.</Summary>
|
||
<LongDescription>Assign each business partner to a grouping when you create the business partner. The grouping determines the number range. You cannot change the assignment afterwards.You can define the groupings, their descriptions, the associated number range and other attributes in Customizing.You can define standard groupings for the internal and the external number assignment.For each grouping create a number range.When you create a business partner, the entry in the grouping field determines whether and how an entry is made in the business partner number field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartnerName" Type="Edm.String" MaxLength="81" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="BusinessPartnerUUID" Type="Edm.Guid" sap:label="BP GUID" sap:heading="Business Partner GUID" sap:quickinfo="Business Partner GUID" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="CorrespondenceLanguage" Type="Edm.String" MaxLength="2" sap:label="Correspondence lang." sap:heading="LG" sap:quickinfo="Business Partner: Correspondence Language">
|
||
<Documentation>
|
||
<Summary>Correspondence language (written) for business partners in the 'Person' category. Maintain the correspondence language for business partners in the 'Organization' and 'Group' category with the address (communication).</Summary>
|
||
<LongDescription>When transferring data (direct input), make sure that for a'Person', the field 'LANGU_CORR' and for an'Organization' or "Group" the field 'LANGU'has an entry.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CreatedByUser" Type="Edm.String" MaxLength="12" sap:display-format="UpperCase" sap:label="Created By" sap:heading="User" sap:quickinfo="User who created the object" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="CreationDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Created on" sap:heading="Date" sap:quickinfo="Date on which the object was created" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="CreationTime" Type="Edm.Time" Precision="0" sap:label="Created at" sap:heading="Time" sap:quickinfo="Time at which the object was created" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="FirstName" Type="Edm.String" MaxLength="40" sap:label="First Name" sap:quickinfo="First Name of Business Partner (Person)"/>
|
||
<Property Name="FormOfAddress" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Title" sap:heading="Key" sap:quickinfo="Form-of-Address Key">
|
||
<Documentation>
|
||
<Summary>Key for form of address text.</Summary>
|
||
<LongDescription>You can also define a form of address text in Customizing.The form of address text can be maintained in different languages.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Industry" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Industry sector" sap:heading="Industry">
|
||
<Documentation>
|
||
<Summary>An industry sector is the term used to classify a company according to its main business activity.</Summary>
|
||
<LongDescription>You can assign an industry sector to business partners in the category 'Organization'RetailBanksServicesIndustryHealth servicePublic sectorMedia</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InternationalLocationNumber1" Type="Edm.String" MaxLength="7" sap:display-format="NonNegative" sap:label="Int. location no. 1" sap:heading="ILN 1" sap:quickinfo="International location number (part 1)">
|
||
<Documentation>
|
||
<Summary>Here you enter the first 7 digits of the international location number.</Summary>
|
||
<LongDescription>The International Location Number (ILN) is assigned (in Germany by the Centrale for Coorganisation GmbH)) when a company is founded. It consists of 13 digits, the last digit being the check digit. There are two categories of location numbers:Participants who only need an ILN to cleary and unmistakably identify themselves for communication with the business partner are given a category 1 ILN. This cannot be used to identify articles by means of EAN.Participants who wish to assign the location numbers for their own enterprise areas are given a category 2 ILN. For a category 2 ILN, digits 1 to 7 are described as basis number. This is used as basis for the creation of article numbers (EAN).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InternationalLocationNumber2" Type="Edm.String" MaxLength="5" sap:display-format="NonNegative" sap:label="Int. location no. 2" sap:heading="ILN 2" sap:quickinfo="International location number (Part 2)">
|
||
<Documentation>
|
||
<Summary>Here, you enter digits 8-12 of the 13-digit international location number.</Summary>
|
||
<LongDescription>The international location number (ILN) is assigned when establishing a company (by the "Zentrale für Coorganisation GmbH" in Germany). It consists of 13 digits, the last of which is the check digit. There are two types of international location numbers:Subscribers who only need one ILN to identify themselves in communication with the business partner are given an ILN of type 1. These cannot be used for identifying articles by means of EAN.Subscribers who need to assign location numbers for their own company areas are given an ILN of type 2. Positions 1 through 7 of the ILN type 2 are known as the basis number. This basis number forms the basis for article numbers (EAN).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IsFemale" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Female" sap:heading="F" sap:quickinfo="Selection: Business partner is female"/>
|
||
<Property Name="IsMale" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Male" sap:heading="M" sap:quickinfo="Selection: Business partner is male"/>
|
||
<Property Name="IsNaturalPerson" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Natural Person" sap:quickinfo="Business Partner Is a Natural Person Under the Tax Laws">
|
||
<Documentation>
|
||
<Summary>Indicator through which a distinction between natural and legal persons can be made during tax reporting.</Summary>
|
||
<LongDescription>Is used in Italy and Mexico ,among other countries.Brasil: If the indicator is not set, 'CGC' is relevant in tax number 1. If the indicator is set, 'CPF' is relevant in tax number 2.Colombia: In the case of some natural persons, the NIT number does not have a check digit. In this case you should set this indicator and the check is deactivated.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IsSexUnknown" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Unknown" sap:heading="U" sap:quickinfo="Selection: Sex of business partner is not known"/>
|
||
<Property Name="GenderCodeName" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Gender" sap:quickinfo="Gender of Business Partner (Person)"/>
|
||
<Property Name="Language" Type="Edm.String" MaxLength="2" sap:label="Language" sap:heading="LG" sap:quickinfo="Business partner: Language">
|
||
<Documentation>
|
||
<Summary>Language for verbal communication with a business partner.</Summary>
|
||
<LongDescription>This language may differ from the language(s) defined for written correspondence.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LastChangeDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Changed on" sap:heading="Date" sap:quickinfo="Date when object was last changed" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="LastChangeTime" Type="Edm.Time" Precision="0" sap:label="Changed at" sap:heading="Time" sap:quickinfo="Time at which object was last changed" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="LastChangedByUser" Type="Edm.String" MaxLength="12" sap:display-format="UpperCase" sap:label="Changed by" sap:heading="User" sap:quickinfo="Last user to change object" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="LastName" Type="Edm.String" MaxLength="40" sap:label="Last Name" sap:quickinfo="Last Name of Business Partner (Person)"/>
|
||
<Property Name="LegalForm" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Legal form" sap:quickinfo="BP: Legal form of organization">
|
||
<Documentation>
|
||
<Summary>Denotes certain legal norms that are of significance for the organization of a company.</Summary>
|
||
<LongDescription>For business partners in the category "Organization", you can state the legal form of the company. This is for information purposes only.Stock corporation (AG in Germany)Limited liability company (GmbH in Germany)</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="OrganizationBPName1" Type="Edm.String" MaxLength="40" sap:label="Name 1" sap:quickinfo="Name 1 of organization">
|
||
<Documentation>
|
||
<Summary>First name field for business partners in the Organization category.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="OrganizationBPName2" Type="Edm.String" MaxLength="40" sap:label="Name 2" sap:quickinfo="Name 2 of organization">
|
||
<Documentation>
|
||
<Summary>Second name field for business partners in the Organization category.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="OrganizationBPName3" Type="Edm.String" MaxLength="40" sap:label="Name 3" sap:quickinfo="Name 3 of organization">
|
||
<Documentation>
|
||
<Summary>Third name field for business partners in the Organization category.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="OrganizationBPName4" Type="Edm.String" MaxLength="40" sap:label="Name 4" sap:quickinfo="Name 4 of organization">
|
||
<Documentation>
|
||
<Summary>Fourth name field for business partners in the Organization category.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="OrganizationFoundationDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Date founded" sap:heading="Founded" sap:quickinfo="Date organization founded">
|
||
<Documentation>
|
||
<Summary>Indicates the official registration of a company in the Commercial Register.</Summary>
|
||
<LongDescription>If a company is not officially registered in the Commercial Register, it has to use some type of text addition, such as foundation pending, when referring to the legal form.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="OrganizationLiquidationDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Liquidation date" sap:heading="Liq. date" sap:quickinfo="Liquidation date of organization">
|
||
<Documentation>
|
||
<Summary>Term for the end of bankruptcy proceedings.</Summary>
|
||
<LongDescription>This date also indicates that the company no longer exists.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SearchTerm1" Type="Edm.String" MaxLength="20" sap:display-format="UpperCase" sap:label="Search Term 1" sap:quickinfo="Search Term 1 for Business Partner">
|
||
<Documentation>
|
||
<Summary>Denotes the term that you define for a business partner, and via which you can restrict the search for a business partner in the business partner search or in the locator.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SearchTerm2" Type="Edm.String" MaxLength="20" sap:display-format="UpperCase" sap:label="Search Term 2" sap:quickinfo="Search Term 2 for Business Partner">
|
||
<Documentation>
|
||
<Summary>Denotes the term that you define for a business partner, and via which you can restrict the search for a business partner in the business partner search or in the locator.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AdditionalLastName" Type="Edm.String" MaxLength="40" sap:label="Other Last Name" sap:quickinfo="Other Last Name of a Person"/>
|
||
<Property Name="BirthDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Date of Birth" sap:heading="Birth Date" sap:quickinfo="Date of Birth of Business Partner"/>
|
||
<Property Name="BusinessPartnerBirthDateStatus" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Birth Date Status" sap:quickinfo="Date of Birth: Status">
|
||
<Documentation>
|
||
<Summary>If the Business partner's actual birthdate is unknown, a partial entry can be made or read. This field then indicates which part of the birthdate is unknown. Below are some examples (Dates are specified in format MM/DD/YYYY):</Summary>
|
||
<LongDescription>01/01/0000 => 01/01/1880 Year unknown00/01/1911 => 01/01/1911 Month unknown05/00/1911 => 05/01/1911 Day unknown05/05/1911 => 05/05/1911 Fully known00/00/1911 => 05/05/1911 Day & Month unknown00/05/0000 => 05/05/1911 Month & Year unknown05/00/0000 => 05/05/1911 Day & Year unknown00/00/0000=> 05/05/1911 Fully unknown'Date of Birth: Status' field determines the unknown parts of birthdate.Enter a valid date under Birthdate. Future dates are not accepted. If any part/s of the date is/are unknown, select the nearest date.If year is unknown, select any random valid year.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartnerBirthplaceName" Type="Edm.String" MaxLength="40" sap:label="Birthplace" sap:quickinfo="Birthplace of business partner"/>
|
||
<Property Name="BusinessPartnerIsBlocked" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Central Block" sap:quickinfo="Central Block for Business Partner">
|
||
<Documentation>
|
||
<Summary>If the business partner is blocked centrally, certain activities cannot be executed.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartnerType" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="BP Type" sap:heading="Type" sap:quickinfo="Business Partner Type">
|
||
<Documentation>
|
||
<Summary>You can use the business partner type to group business partners according to your own criteria in Customizing (IMG).</Summary>
|
||
<LongDescription>In Customizing you can show or hide fields for data entry, depending on the requirements of the relevant business partner type.Select a business partner type. You can obtain help by pressing the F4 key.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ETag" Type="Edm.String" MaxLength="26" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="GroupBusinessPartnerName1" Type="Edm.String" MaxLength="40" sap:label="Name 1" sap:quickinfo="Name 1 (group)">
|
||
<Documentation>
|
||
<Summary>First name field for business partners in the Group category.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="GroupBusinessPartnerName2" Type="Edm.String" MaxLength="40" sap:label="Name 2" sap:quickinfo="Name 2 (group)">
|
||
<Documentation>
|
||
<Summary>Second name field for business partners in the Group category.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IndependentAddressID" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Address Number" sap:heading="Addr. no." sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying the address for communication data that spans all addresses in Business Partner.</Summary>
|
||
<LongDescription>For more information on the significance and usage of the address number, see the documentation for Business Address Services (BAS).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InternationalLocationNumber3" Type="Edm.String" MaxLength="1" sap:display-format="NonNegative" sap:label="Check digit" sap:quickinfo="Check digit for the international location number">
|
||
<Documentation>
|
||
<Summary>The check digit is derived from a special check digit procedure from digits of the previous international location numbers. In this way, you can check whether the ILN entered is actually valid.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="MiddleName" Type="Edm.String" MaxLength="40" sap:label="Middle Name" sap:heading="Middle or second name" sap:quickinfo="Middle Name or Second Forename of a Person"/>
|
||
<Property Name="NameCountry" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Ctry/Reg. for Format" sap:heading="C/R" sap:quickinfo="Country/Region for Name Format Rule">
|
||
<Documentation>
|
||
<Summary>The country/region for the name format rule and the name format rule key together uniquely identify a formatting rule.</Summary>
|
||
<LongDescription>A country/region can have several formats which correspond to different rules. You need formatting rules to describe the composition of a person's name.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="NameFormat" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Name Format" sap:heading="Format" sap:quickinfo="Name format">
|
||
<Documentation>
|
||
<Summary>See Name format.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PersonFullName" Type="Edm.String" MaxLength="80" sap:label="Full Name">
|
||
<Documentation>
|
||
<Summary>States the complete name of a person.</Summary>
|
||
<LongDescription>The complete name is generally generated and saved by the Business Address Services (BAS) according to country-specific rules from the individual name components (without the form of address).If, during the formatting of an address, you want to use an alternative name, you can manually format the alternative name here.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PersonNumber" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Person Number" sap:heading="Person" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a person in Business Address Services.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the person number and Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IsMarkedForArchiving" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Archiving Flag" sap:quickinfo="Central Archiving Flag">
|
||
<Documentation>
|
||
<Summary>Establishes if the business partner is meant to be archived.</Summary>
|
||
<LongDescription>If the indicator is set, the relevant business partner can be archived from the view of the business partner administration.If the check of the data to be archived shows, for example, that there are still active business transactions the archiving of the business partner data is prevented even if the indicator is set.If the indicator is not set, the business partner will not be taken into consideration during archiving.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartnerIDByExtSystem" Type="Edm.String" MaxLength="20" sap:display-format="UpperCase" sap:label="External BP Number" sap:quickinfo="Business Partner Number in External System">
|
||
<Documentation>
|
||
<Summary>Business partner number from an external system or a legacy system.</Summary>
|
||
<LongDescription>If the current business partner is known under a different number in an external system, you can store this number here for information purposes.Direct input gives you the option of maintaining a business partner by specifying the external business partner number. If you maintain business partner data in your legacy system, you can transmit changes made to business partners to the SAP system without having to know the SAP business partner number in the legacy system.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TradingPartner" Type="Edm.String" MaxLength="6" sap:display-format="UpperCase" sap:label="Trading Partner No." sap:heading="Tr.prt" sap:quickinfo="Company ID of trading partner">
|
||
<Documentation>
|
||
<Summary>Company ID standard for the whole group.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<NavigationProperty Name="to_BuPaIdentification" Relationship="API_BUSINESS_PARTNER.assoc_07A4C6774A79F32D8C1BDA1CBE5A2FA7" FromRole="FromRole_assoc_07A4C6774A79F32D8C1BDA1CBE5A2FA7" ToRole="ToRole_assoc_07A4C6774A79F32D8C1BDA1CBE5A2FA7"/>
|
||
<NavigationProperty Name="to_BuPaIndustry" Relationship="API_BUSINESS_PARTNER.assoc_91BCE13588BD3046353CD68D3098C2E5" FromRole="FromRole_assoc_91BCE13588BD3046353CD68D3098C2E5" ToRole="ToRole_assoc_91BCE13588BD3046353CD68D3098C2E5"/>
|
||
<NavigationProperty Name="to_BusinessPartnerAddress" Relationship="API_BUSINESS_PARTNER.assoc_6247ED959B75350E6EA6CEDD2CBEC7E7" FromRole="FromRole_assoc_6247ED959B75350E6EA6CEDD2CBEC7E7" ToRole="ToRole_assoc_6247ED959B75350E6EA6CEDD2CBEC7E7"/>
|
||
<NavigationProperty Name="to_BusinessPartnerBank" Relationship="API_BUSINESS_PARTNER.assoc_05F0DA10FFAB2836605571E5ABB6E5B9" FromRole="FromRole_assoc_05F0DA10FFAB2836605571E5ABB6E5B9" ToRole="ToRole_assoc_05F0DA10FFAB2836605571E5ABB6E5B9"/>
|
||
<NavigationProperty Name="to_BusinessPartnerContact" Relationship="API_BUSINESS_PARTNER.assoc_02AC1AF45478434AAB93B18ECA2FB863" FromRole="FromRole_assoc_02AC1AF45478434AAB93B18ECA2FB863" ToRole="ToRole_assoc_02AC1AF45478434AAB93B18ECA2FB863"/>
|
||
<NavigationProperty Name="to_BusinessPartnerRole" Relationship="API_BUSINESS_PARTNER.assoc_FB863C7C69262D926CE14CA6A50667DB" FromRole="FromRole_assoc_FB863C7C69262D926CE14CA6A50667DB" ToRole="ToRole_assoc_FB863C7C69262D926CE14CA6A50667DB"/>
|
||
<NavigationProperty Name="to_BusinessPartnerTax" Relationship="API_BUSINESS_PARTNER.assoc_DADC7016DBB892642F90D68E0E47B6E8" FromRole="FromRole_assoc_DADC7016DBB892642F90D68E0E47B6E8" ToRole="ToRole_assoc_DADC7016DBB892642F90D68E0E47B6E8"/>
|
||
<NavigationProperty Name="to_Customer" Relationship="API_BUSINESS_PARTNER.assoc_80838433DCE8E16AA7C9031C32896631" FromRole="FromRole_assoc_80838433DCE8E16AA7C9031C32896631" ToRole="ToRole_assoc_80838433DCE8E16AA7C9031C32896631"/>
|
||
<NavigationProperty Name="to_Supplier" Relationship="API_BUSINESS_PARTNER.assoc_7256A9801E68AE14E59054C2738099F1" FromRole="FromRole_assoc_7256A9801E68AE14E59054C2738099F1" ToRole="ToRole_assoc_7256A9801E68AE14E59054C2738099F1"/>
|
||
</EntityType>
|
||
<EntityType Name="A_BusinessPartnerAddressType" sap:label="Address" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="BusinessPartner"/>
|
||
<PropertyRef Name="AddressID"/>
|
||
</Key>
|
||
<Property Name="BusinessPartner" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AddressID" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Address Number" sap:heading="Addr. No.">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a Business Address Services address.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the address number and the Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ValidityStartDate" Type="Edm.DateTimeOffset" Precision="0" sap:label="Valid From" sap:quickinfo="Validity Start of a Business Partner Address"/>
|
||
<Property Name="ValidityEndDate" Type="Edm.DateTimeOffset" Precision="0" sap:label="Valid To" sap:quickinfo="Validity End of a Business Partner Address"/>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization Group" sap:heading="AGrp">
|
||
<Documentation>
|
||
<Summary>You can use authorization groups to stipulate which business partners a user is allowed to process.</Summary>
|
||
<LongDescription>Use the following authorization object:'Business partners: authorization groups' (B_BUPA_GRP).The system only checks this authorization if you made an entry in the "Authorization group" field for the business partner. Otherwise, any user may process the business partner.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AddressUUID" Type="Edm.Guid" sap:label="GUID of a Business Partner Address" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="AdditionalStreetPrefixName" Type="Edm.String" MaxLength="40" sap:label="Street 3">
|
||
<Documentation>
|
||
<Summary>Additional address field which is printed above the Street line.</Summary>
|
||
<LongDescription>The Street address contains two lines above the street and two lines below the street.See Print the Street address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AdditionalStreetSuffixName" Type="Edm.String" MaxLength="40" sap:label="Street 5">
|
||
<Documentation>
|
||
<Summary>Additional address field which is printed under the Street line.</Summary>
|
||
<LongDescription>The Street address has two lines above the street and two lines below the steet.See Print the Street address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AddressTimeZone" Type="Edm.String" MaxLength="6" sap:display-format="UpperCase" sap:label="Time zone" sap:heading="Zone" sap:quickinfo="Address time zone">
|
||
<Documentation>
|
||
<Summary>Time zone as part of an address.</Summary>
|
||
<LongDescription>The time zone is automatically determined by the system in address maintenance if time zone Customizing is maintained.It depends on the country and the region. (Region means state, province or county, depending on the country)The automatic determination is only made if there is no value in the time zone field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CareOfName" Type="Edm.String" MaxLength="40" sap:label="c/o" sap:heading="c/o name" sap:quickinfo="c/o name">
|
||
<Documentation>
|
||
<Summary>Part of the address (c/o = care of) if the recipient is different from the occupant and the names are not similar (e.g. subtenants).</Summary>
|
||
<LongDescription>Put the country-specific code (e.g. c/o) in front of the name of the occupant. This is not automatically done in the print format, like the language-specific word "PO Box".John Smithc/o David BrownThis field is not always automatically printed, as it was subsequently added to the address structure.The print program or form may need to be adjusted.This exception applies to the following fields:Street2, Street3, Street4, Street5, c/o name, and to all address fields added after Release 4.5.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CityCode" Type="Edm.String" MaxLength="12" sap:display-format="UpperCase" sap:label="City Code" sap:quickinfo="City code for city/street file"/>
|
||
<Property Name="CityName" Type="Edm.String" MaxLength="40" sap:label="City">
|
||
<Documentation>
|
||
<Summary>City name as part of the address.</Summary>
|
||
<LongDescription>The city name is saved redundantly in another database field in upper- case letters, for search help.If the Postal regional structure ('city file') is active, the city name is checked against the Cities defined in the regional structure.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CompanyPostalCode" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Company Postal Code" sap:heading="Postl Code" sap:quickinfo="Company Postal Code (for Large Customers)">
|
||
<Documentation>
|
||
<Summary>Postal code that is assigned directly to one company (= company postal code = major customer postal code).</Summary>
|
||
<LongDescription>This field is used for countries where major companies are assigned their own postal code by the national post office.This postal code has to be entered in the field "Company Postal Code". Postal codes for group major customers, however, have to be entered in the field "PO Box Postal Code", since individual customers with a shared postal code for group major customers are differentiated by means of their PO box.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Country" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Country/Region Key" sap:heading="C/R">
|
||
<Documentation>
|
||
<Summary>The country/region key contains information which the system uses to check entries such as the length of the postal code or bank account number.</Summary>
|
||
<LongDescription>The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.It could also be the vehicle license plate country/region code or a typical country/region key, for example, in Germany the Federal statistics office key.The country/region keys are determined at system installation in the global settings.The definition of the country/region keys in the SAP system does not necessarily have to match political or state units.Since the country/region key does not have to correspond to the ISO code in all installations, programs that differ according to certain values of the country/region key cannot query the country/region key T005-LAND1, but have to program based on the ISO code T005 INTCA.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="County" Type="Edm.String" MaxLength="40" sap:label="County">
|
||
<Documentation>
|
||
<Summary>Specifies the county’s name</Summary>
|
||
<LongDescription>This field is used to store the county’s name. You can enter the name of the county in this field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DeliveryServiceNumber" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Delivery Service No." sap:heading="Delivery Service Number" sap:quickinfo="Number of Delivery Service">
|
||
<Documentation>
|
||
<Summary>The delivery service is part of the PO box address.</Summary>
|
||
<LongDescription>Some countries offer different services in addition to regular postal delivery and PO boxes, for example the Private Bag or Response Bag. If an address is related to one of these delivery services, the information about this particular delivery service has to be entered in the corresponding fields.In the field "Number of Delivery Service," the number of the Private Bag, Response Bag, or other relevant service has to be entered. Entering a number is not mandatory for each delivery service.For each address, either the information about the PO box or the information about the delivery service can be entered, but not both types of information at the same time.Mr PickeringPrivate Bag 106999Timaru 7942Delivery services will only be taken into account for address formatting in countries in which they are commonly used in addition to regular postal delivery and PO boxes, for example, in Australia, New Zealand, and the USA. In all other countries, these fields will not be taken into account for address formatting.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DeliveryServiceTypeCode" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Delvry Serv Type" sap:quickinfo="Type of Delivery Service">
|
||
<Documentation>
|
||
<Summary>The delivery service is part of the PO box address.</Summary>
|
||
<LongDescription>Some countries offer different services in addition to regular postal delivery and PO boxes, for example the Private Bag or Response Bag. If an address is related to one of these delivery services, the information about this particular delivery service has to be entered in the corresponding fields.In the field "Type of Delivery Service," the type of the delivery service has to be entered.For each address, either the information about the PO box or the information about the delivery service can be entered, but not both types of information at the same time.Mr PickeringPrivate Bag 106999Timaru 7942Delivery services will only be taken into account for address formatting in countries in which they are commonly used in addition to regular postal delivery and PO boxes, for example, in Australia, New Zealand, and the USA. In all other countries, these fields will not be taken into account for address formatting.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="District" Type="Edm.String" MaxLength="40" sap:label="District">
|
||
<Documentation>
|
||
<Summary>City or District supplement</Summary>
|
||
<LongDescription>In some countries, this entry is appended with a hyphen to the city name by the automatic address formatting, other countries, it is output on a line of its own or (e.g. in the USA) not printed.See the examples in the Address Layout Key documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="FormOfAddress" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Title" sap:heading="Key" sap:quickinfo="Form-of-Address Key" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Key for form of address text.</Summary>
|
||
<LongDescription>You can also define a form of address text in Customizing.The form of address text can be maintained in different languages.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="FullName" Type="Edm.String" MaxLength="80" sap:label="Full Name" sap:quickinfo="Full name of a party (Bus. Partner, Org. Unit, Doc. address)" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>This field contains the full name or formatted name of a party.</Summary>
|
||
<LongDescription>For organizations or document addresses, typically the fields Name1 and Name2 are concatenated.For persons the field contains the formatted name according to country specific rules. It corresponds e.g. to the content of the fields BUT000-NAME1_TEXT or ADRP-NAME_TEXT.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="HomeCityName" Type="Edm.String" MaxLength="40" sap:label="Different City" sap:heading="City (Diff. from Postal City)" sap:quickinfo="City (different from postal city)">
|
||
<Documentation>
|
||
<Summary>City of residence which is different from the postal city</Summary>
|
||
<LongDescription>In some countries, the residential city is required if it differs from the postal city.In the USA, the official street indexes, against which data can be checked, are based on the residential city, not the postal city, which may be different.It is the same in France, where a postally correct address must contain the residential city in a separate line above the postal city, if it differs from the postal city.This field is not always automatically printed, as it was subsequently added to the address structure.The print program or form may need to be adjusted.This exception applies to the following fields:Street2, Street3, Street4, Street5, c/o name, and to all address fields added after Release 4.5.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="HouseNumber" Type="Edm.String" MaxLength="10" sap:label="House Number" sap:heading="House No.">
|
||
<Documentation>
|
||
<Summary>House number as part of an address.</Summary>
|
||
<LongDescription>It is printed in the Street line.Other supplementary street information can be entered in the House number supplement or one of the Street2, Street3, Street4 or Street5 fields. See Print the Street address.A house number (e.g. 117) or a house number with supplement (e.g. 117a), or a house number range (e.g. 16-20), can be maintained in this field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="HouseNumberSupplementText" Type="Edm.String" MaxLength="10" sap:label="Supplement" sap:quickinfo="House number supplement">
|
||
<Documentation>
|
||
<Summary>House number supplement as part of an address, e.g.</Summary>
|
||
<LongDescription>App. 17 orSuite 600.It is printed in the Street line.Further Street supplements can be put in one of the fields Street2, Street3, Street4 or Street5.See Print the Street address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Language" Type="Edm.String" MaxLength="2" sap:label="Language Key" sap:heading="Language">
|
||
<Documentation>
|
||
<Summary>The language key indicates</Summary>
|
||
<LongDescription>- the language in which texts are displayed,- the language in which you enter texts,- the language in which the system prints texts.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBox" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="PO Box">
|
||
<Documentation>
|
||
<Summary>PO Box number as part of an address.</Summary>
|
||
<LongDescription>Only enter the PO Box number in this field. The text "PO Box" is provided in the recipient language by the system when you print the address.When you print an address, the "Street address" and the "PO Box address" are distinguished. The print program determines which of them has priority if both are maintained in an address record.Besides the PO Box number, the PO Box address uses the following fields:PO Box postal code, if specified (otherwise the normal postal code)PO Box city, if specified (otherwise the normal city)PO Box region, if specified (otherwise the normal region)PO Box country, if specified (otherwise the normal country)If the address is a "PO Box" (without a number), do not fill the "PO Box" field. Select the "PO Box w/o Number" indicator instead.You can also enter a company postal code for organizational addresses, instead of a PO Box. A separate field is predefined for this entry.For general information and examples about address formatting, see the documentation on the Address Structure Key.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBoxDeviatingCityName" Type="Edm.String" MaxLength="40" sap:label="PO Box City" sap:quickinfo="PO Box city">
|
||
<Documentation>
|
||
<Summary>Different city for the PO Box as an address component.</Summary>
|
||
<LongDescription>The PO Box city can be entered here if it is different from the address city.If the address is only a PO Box address, enter the city in the normal city field.If the address contains two different city names for the address and the PO Box address, use this field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBoxDeviatingCountry" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="PO Box Ctry/Region" sap:heading="PO C/R" sap:quickinfo="PO Box of Country/Region">
|
||
<Documentation>
|
||
<Summary>Other country/region for PO box in an address.</Summary>
|
||
<LongDescription>Here you can enter the country/region for the PO box if this country/region is different to the country/region of the street address.If the address only has a PO box address, you enter the country/region in in the normal field for country/region.If the street address and the PO box belong to two different countries/regions, you fill this field.This field is not always automatically printed, as it was subsequently added to the address structure.The print program or form may need to be adjusted.This exception applies to the following fields:Street2, Street3, Street4, Street5, c/o name, and to all address fields added after Release 4.5.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBoxDeviatingRegion" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="PO Box Region" sap:heading="PO Region" sap:quickinfo="Region for PO Box (Country, State, Province, ...)">
|
||
<Documentation>
|
||
<Summary>Different Region for PO Box in an address.</Summary>
|
||
<LongDescription>Enter the PO Box Region here, if it differs from the street address region.If the address only has a PO Box address, the Region in in the normal Region field.Use this field if the address has two different Region values for the street address and the PO Box address.This field is not always automatically printed, as it was subsequently added to the address structure.The print program or form may need to be adjusted.This exception applies to the following fields:Street2, Street3, Street4, Street5, c/o name, and to all address fields added after Release 4.5.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBoxIsWithoutNumber" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="PO Box w/o No." sap:heading="PO" sap:quickinfo="Flag: PO Box Without Number">
|
||
<Documentation>
|
||
<Summary>PO Box address without PO Box number flag.</Summary>
|
||
<LongDescription>Only the word 'PO Box' is output in PO Box addresses without PO Box number.Set this flag for a PO Box address without PO Box number.This field is not always automatically printed, as it was subsequently added to the address structure.The print program or form may need to be adjusted.This exception applies to the following fields:Street2, Street3, Street4, Street5, c/o name, and to all address fields added after Release 4.5.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBoxLobbyName" Type="Edm.String" MaxLength="40" sap:label="PO Box Lobby">
|
||
<Documentation>
|
||
<Summary>The PO box lobby is part of the PO box address.</Summary>
|
||
<LongDescription>In some countries, entering a PO box, postal code and city is not sufficient to uniquely identify a PO box, because the same PO box number is assigned multiple times in some cities.Therefore, additional information might be required to determine the post office of the PO box in question. This information can be entered in the field "PO Box Lobby."Mr NellingPO Box 4099HighfieldTimaru 7942The PO box lobby will only be taken into account for address formatting in countries in which it is commonly used in addition to regular postal delivery and PO boxes, for example, in Canada or New Zealand. In all other countries, this field will not be taken into account for address formatting.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="POBoxPostalCode" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="PO Box Postal Code" sap:heading="Postl Code">
|
||
<Documentation>
|
||
<Summary>Postal code that is required for a unique assignment of the PO box.</Summary>
|
||
<LongDescription>This field is used for countries where a different postal code applies to mail that is sent to the PO box rather than to the street address of a particular business partner.Postal codes for group major customers also have to be entered in the field for the PO box postal code since individual customers with a shared postal code for group major customers are differentiated by means of the PO box. Postal codes for major customers (= company postal codes), however, are assigned to one customer only and have to be entered in the field 'Company Postal Code'.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Person" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Person Number" sap:heading="Person" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Internal key for identifying a person in Business Address Services.</Summary>
|
||
<LongDescription>For more information about the meaning and use of the person number and Business Address Services concepts, see the function group SZA0 documentation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PostalCode" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Postal Code" sap:heading="Post. Code" sap:quickinfo="City Postal Code">
|
||
<Documentation>
|
||
<Summary>Postal code as part of the address</Summary>
|
||
<LongDescription>If different postal codes are maintained for the PO Box and Street address of an address, this field contains the Street address postal code.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PrfrdCommMediumType" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Comm. Method" sap:quickinfo="Communication Method (Key) (Business Address Services)">
|
||
<Documentation>
|
||
<Summary>Communication method with which you can exchange documents and messages with a business partner.</Summary>
|
||
<LongDescription>In Business Address Services, you can specify a standard communication method that can be used by programs to determine the means of communication for sending messages.One business partner wants all messages by fax, another by e-mail.The application context can restrict the possible methods of communication. For example, invitations should perhaps only be sent by post because of enclosures, whereas minutes can be sent by post, fax or e-mail.Communication strategies can be defined for this purpose and applied in application contexts.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Region" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Region" sap:heading="Rg" sap:quickinfo="Region (State, Province, County)">
|
||
<Documentation>
|
||
<Summary>In some countries, the region forms part of the address. The meaning depends on the country.</Summary>
|
||
<LongDescription>The automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.For more information, see the examples in the documentation on the Address Layout Key.Meaning of the regional code in ...Australia -> ProvinceBrazil -> StateCanada -> ProvinceGermany -> StateGreat Britain -> CountyItaly -> ProvinceJapan -> PrefectureSwitzerland -> CantonUSA -> State</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="StreetName" Type="Edm.String" MaxLength="60" sap:label="Street">
|
||
<Documentation>
|
||
<Summary>Street name as part of the address.</Summary>
|
||
<LongDescription>The street name is saved, redundantly in upper case in another database field, for search help purposes.There are other fields for address parts which can be printed above or below the street. See Print the Street address.The house number and other supplements are usually maintained in their own fields. See Formatting the Street line.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="StreetPrefixName" Type="Edm.String" MaxLength="40" sap:label="Street 2">
|
||
<Documentation>
|
||
<Summary>Additional address field which is printed above the Street line.</Summary>
|
||
<LongDescription>The Street address contains two lines above the street and two lines below the street.See Print the Street address.This field is not always automatically printed, as it was subsequently added to the address structure.The print program or form may need to be adjusted.This exception applies to the following fields:Street2, Street3, Street4, Street5, c/o name, and to all address fields added after Release 4.5.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="StreetSuffixName" Type="Edm.String" MaxLength="40" sap:label="Street 4">
|
||
<Documentation>
|
||
<Summary>Additional address field which is printed below the Street line.</Summary>
|
||
<LongDescription>The Street address contains two lines above the street and two lines below the street.See Print the Street address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxJurisdiction" Type="Edm.String" MaxLength="15" sap:display-format="UpperCase" sap:label="Tax Jurisdiction">
|
||
<Documentation>
|
||
<Summary>Specifies the tax jurisdiction.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TransportZone" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Transportation Zone" sap:heading="TranspZone" sap:quickinfo="Transportation zone to or from which the goods are delivered">
|
||
<Documentation>
|
||
<Summary>Sales and distribution:</Summary>
|
||
<LongDescription>Regional zone of Goods recipient.Purchasing:Regional zone of supplier.You can define regional zones to suit the requirements of your own business and country.Sales and distributionthe system automatically proposes a suitable route by using the transportation zone of the goods recipient in combination with other information about the delivery, such as theCountries of origin and destinationShipping conditionsTransportation groupIn the USA, for example, you can define regional zones to correspond to the US postal zip codes.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AddressIDByExternalSystem" Type="Edm.String" MaxLength="20" sap:display-format="UpperCase" sap:label="External Address No." sap:quickinfo="Address number in external system">
|
||
<Documentation>
|
||
<Summary>Address number from an external system or a legacy system</Summary>
|
||
<LongDescription>If the current address has a different number in an external system, you can save this number here for information purposes.In direct input you are able to maintain an address for a business partner by stating the external address number. If your business partner data is maintained in a legacy system, you can thus transmit changes to a BP address to the SAP system without having to know the SAP address number in the legacy system.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CountyCode" Type="Edm.String" MaxLength="8" sap:display-format="UpperCase" sap:label="County code" sap:quickinfo="County code for county">
|
||
<Documentation>
|
||
<Summary>Specifies the county’s code</Summary>
|
||
<LongDescription>This field stores the county’s code. You cannot enter any data in this field. The system fetches this data from the ADRCOUNTY table and updates it in this field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TownshipCode" Type="Edm.String" MaxLength="8" sap:display-format="UpperCase" sap:label="Township code" sap:quickinfo="Township code for Township">
|
||
<Documentation>
|
||
<Summary>Specifies the township’s code</Summary>
|
||
<LongDescription>This field stores the township’s code. You cannot enter any data in this field. The system fetches this data from the ADRTOWNSHIP table and updates it in this field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TownshipName" Type="Edm.String" MaxLength="40" sap:label="Township">
|
||
<Documentation>
|
||
<Summary>Specifies the township’s name</Summary>
|
||
<LongDescription>This field is used to store the township’s name. You can enter the name of the township in this field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<NavigationProperty Name="to_AddressUsage" Relationship="API_BUSINESS_PARTNER.assoc_091DBA85F5FE3E747FC3884B40B4EBFD" FromRole="FromRole_assoc_091DBA85F5FE3E747FC3884B40B4EBFD" ToRole="ToRole_assoc_091DBA85F5FE3E747FC3884B40B4EBFD"/>
|
||
<NavigationProperty Name="to_EmailAddress" Relationship="API_BUSINESS_PARTNER.assoc_B21DC96A1904D36E94FBE84771BD7E99" FromRole="FromRole_assoc_B21DC96A1904D36E94FBE84771BD7E99" ToRole="ToRole_assoc_B21DC96A1904D36E94FBE84771BD7E99"/>
|
||
<NavigationProperty Name="to_FaxNumber" Relationship="API_BUSINESS_PARTNER.assoc_43B546339886BBB6ED35EA7CA84FB32B" FromRole="FromRole_assoc_43B546339886BBB6ED35EA7CA84FB32B" ToRole="ToRole_assoc_43B546339886BBB6ED35EA7CA84FB32B"/>
|
||
<NavigationProperty Name="to_MobilePhoneNumber" Relationship="API_BUSINESS_PARTNER.assoc_60DDA2597182EA56C114908472D2FB81" FromRole="FromRole_assoc_60DDA2597182EA56C114908472D2FB81" ToRole="ToRole_assoc_60DDA2597182EA56C114908472D2FB81"/>
|
||
<NavigationProperty Name="to_PhoneNumber" Relationship="API_BUSINESS_PARTNER.assoc_35D5A40C930BECE699C4526B1B1F8D1C" FromRole="FromRole_assoc_35D5A40C930BECE699C4526B1B1F8D1C" ToRole="ToRole_assoc_35D5A40C930BECE699C4526B1B1F8D1C"/>
|
||
<NavigationProperty Name="to_URLAddress" Relationship="API_BUSINESS_PARTNER.assoc_24C290CBC7FE69574AD9D79A5C631212" FromRole="FromRole_assoc_24C290CBC7FE69574AD9D79A5C631212" ToRole="ToRole_assoc_24C290CBC7FE69574AD9D79A5C631212"/>
|
||
</EntityType>
|
||
<EntityType Name="A_BusinessPartnerBankType" sap:label="Bank" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="BusinessPartner"/>
|
||
<PropertyRef Name="BankIdentification"/>
|
||
</Key>
|
||
<Property Name="BusinessPartner" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BankIdentification" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Bank details ID" sap:heading="ID">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner's bank details.</Summary>
|
||
<LongDescription>Enter a bank details ID for each separate set of bank details for a business partner.Business Partner: H. MillerBD-ID Fin.institution Acct no. 0001 Chemical Bank, NYC 56234560002 Chemical Bank, NYC 56231220003 First Bank of Pittsburgh ...Business partner: T.Wolsey and Co.BD-ID Fin.institution Acct no.GIR0 Citibank, Charleston ...GIR1 Chemical Bank, NYC ...</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BankCountryKey" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Bank Country/Region" sap:heading="C/R" sap:quickinfo="Country/Region Key of Bank">
|
||
<Documentation>
|
||
<Summary>Specifies the country/region where the bank is based.</Summary>
|
||
<LongDescription>The country/region key determines according to which rules the remaining bank data (for example, bank number and bank account number) is checked.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BankName" Type="Edm.String" MaxLength="60" sap:label="Bank Name" sap:heading="Name of Bank" sap:quickinfo="Name of Bank" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>The name under which the bank operates.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BankNumber" Type="Edm.String" MaxLength="15" sap:display-format="UpperCase" sap:label="Bank Key">
|
||
<Documentation>
|
||
<Summary>The bank key (under which the bank data is stored in the appropriate country) is specified in this field.</Summary>
|
||
<LongDescription>The country-specific meaning of this bank key is specified when defining country key.Normally banks have a bank number, which then also appears in the control data of the bank.In certain countries the bank account number assumes this function; in such a case there would be no bank numbers, the bank details are then under the account number.For data medium exchange it can be useful to be able create banks for foreign business partners without a bank number, even if the country in question has bank numbers. In such cases the bank key can be assigned internally.If the bank data is under another key, such as the SWIFT code for example, numbers can also be assigned externally.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SWIFTCode" Type="Edm.String" MaxLength="11" sap:display-format="UpperCase" sap:label="SWIFT/BIC" sap:quickinfo="SWIFT/BIC for International Payments" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Uniquely identifies a bank throughout the world.</Summary>
|
||
<LongDescription>SWIFT stands for Society for Worldwide Interbank Financial Telecommunication.BIC stands for Bank Identifier Code.This globally unique code can be used in international payment transactions to identify the bank without the need to specify an address or bank number. Specification of the SWIFT code/BIC is mainly relevant for automatic payment transactions.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BankControlKey" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Bank Control Key" sap:heading="CK">
|
||
<Documentation>
|
||
<Summary> Brazil, France, Spain, Portugal and Italy</Summary>
|
||
<LongDescription>The field contains a check key for the combination bank number and bank account number.USAIn USA this field is used to differentiate between a savings and a current account (if no value is entered, the default value 01 is used).01 Current account02 Savings account03 Loan account04 General ledgerJapanIn Japan this field specifies the type of account. This information is is copied from the payment medium print program into payment medium. The following is an example of the account types used:01 FUTSU (similar to a savings account)02 TOUZA (similar to a current account)04 CHOCHIKU (similar to an investment account)09 Other types of bank accountsSouth AfricaIn South Africa this field specifies the type of account. The information entered here is forwarded to the bank that carries out the payment order. The following account types are permitted in ABC format:01 Current (Cheque) Account02 Savings Account03 Transmission Account04 Bond Account06 Subscription Share AccountArgentinaIn Argentina this field specifies the type of account:CC Current Account (Cuenta corriente)CA Saving Account (Caja de ahorro)CE Special Saving Account (Caja de ahorro especial)CS Salary Account (Cuenta sueldos)VenezuelaIn Venezuela this field specifies the type of account:CC Checking Account (Cuenta corriente)CA Saving Account (Cuenta de ahorro)CE Special Saving Account (Cuenta de ahorro especial)CS Salary Account (Cuenta sueldos)MexicoIn Mexico this field contains a two-digit key for classifying the bank account (for example, as a savings or current account). This key have different definitions, depending on the bank.NoteFor countries that are not listed here, this field can be used for account-specific information.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BankAccountHolderName" Type="Edm.String" MaxLength="60" sap:label="Account Holder" sap:heading="Account Holder Name" sap:quickinfo="Account Holder Name">
|
||
<Documentation>
|
||
<Summary>Here you can enter another name that the payment program can use if the name of the account holder is not the same as the name of the Business Partner.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BankAccountName" Type="Edm.String" MaxLength="40" sap:label="Account Name" sap:quickinfo="Name of Bank Account"/>
|
||
<Property Name="ValidityStartDate" Type="Edm.DateTimeOffset" Precision="0" sap:label="Valid From" sap:quickinfo="Validity Start of Business Partner Bank Details"/>
|
||
<Property Name="ValidityEndDate" Type="Edm.DateTimeOffset" Precision="0" sap:label="Valid To" sap:quickinfo="Validity End of Business Partner Bank Details"/>
|
||
<Property Name="IBAN" Type="Edm.String" MaxLength="34" sap:display-format="UpperCase" sap:label="IBAN" sap:quickinfo="IBAN (International Bank Account Number)">
|
||
<Documentation>
|
||
<Summary>A uniform standardized ID number for representing bank details that is in accordance with the ECBS (European Committee for Banking Standards). An IBAN has a maximum of 34 alphanumeric characters and is a combination of the following elements:</Summary>
|
||
<LongDescription>Country key of the bank (ISO code)Two-digit check numberCountry-specific account number (in Germany this consists of the bank number and account number, in France the bank number, account number and check key).The IBAN not only makes international payments easier, in some countries it has advantages for domestic payments as well. Depending on the country, it can mean advantages for value and fees.The IBAN can be maintained in parallel with the bank details but does not replace them. It is stored under the master data of the business partner and can then be used when creating the payment medium.Since it is only the bank that has the account that may generate the IBAN corresponding to an account number, the SAP system only generates a proposal. You can confirm or change this proposal. If no proposal is generated, enter the IBAN manually.An IBAN in Belgium may look like this:Electronic Form:BE62510007547061Printed form, as it would appear on an invoice:IBAN BE62 5100 0754 7061</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IBANValidityStartDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="IBAN Valid From" sap:heading="Validity Start of IBAN" sap:quickinfo="Validity Start of IBAN"/>
|
||
<Property Name="BankAccount" Type="Edm.String" MaxLength="18" sap:display-format="UpperCase" sap:label="Bank Account" sap:quickinfo="Bank Account Number">
|
||
<Documentation>
|
||
<Summary>This field contains the number under which the account is managed at the bank.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BankAccountReferenceText" Type="Edm.String" MaxLength="20" sap:display-format="UpperCase" sap:label="Reference Details" sap:quickinfo="Reference Details for Bank Details">
|
||
<Documentation>
|
||
<Summary>Additional details for the bank details of the business partner.</Summary>
|
||
<LongDescription>In some countries the data for the bank details of the business partner (bank number, bank account number, name of the account holder) have to supplemented by other details in order to be able to use certain payment processes. This supplementary details are defined here.If additional data is required for the bank details for payment transactions in your country (see the following examples), enter the reference information.If for an automatic debit the bank requires the reference number of the collection authorization in Norway or Great Britain, specify this number here.In Great Britain when making payments to an account in a 'Building Society' you must specify which number payment recipient has. These details must be defined in the reference field, whereas the fields Bank Key and Account Number are to be used for the bank details of the 'Building Society'.In Great Britain when entering a building society account number, the name of the building society should also be maintained in the system.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CollectionAuthInd" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Collect.author." sap:heading="CollectAut." sap:quickinfo="Indicator: Collection Authorization">
|
||
<Documentation>
|
||
<Summary>States that the bank has collection authorization from the business partner for the account.</Summary>
|
||
<LongDescription>Set this indicator if the bank has collection authorization.Note for Accounts Receivable (FI-AR)If this indicator is not set, there is no bank collection.Note for Contract Accounts Receivable and Payable (FI-CA)This indicator is not relevant.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CityName" Type="Edm.String" MaxLength="35" sap:label="City" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Name of the city as a part of the address.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization Group" sap:heading="AGrp">
|
||
<Documentation>
|
||
<Summary>You can use authorization groups to stipulate which business partners a user is allowed to process.</Summary>
|
||
<LongDescription>Use the following authorization object:'Business partners: authorization groups' (B_BUPA_GRP).The system only checks this authorization if you made an entry in the "Authorization group" field for the business partner. Otherwise, any user may process the business partner.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_BusinessPartnerContactType" sap:label="Contact" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="RelationshipNumber"/>
|
||
<PropertyRef Name="BusinessPartnerCompany"/>
|
||
<PropertyRef Name="BusinessPartnerPerson"/>
|
||
<PropertyRef Name="ValidityEndDate"/>
|
||
</Key>
|
||
<Property Name="RelationshipNumber" Type="Edm.String" Nullable="false" MaxLength="12" sap:display-format="UpperCase" sap:label="BP Relationship No." sap:heading="BP Relation. No." sap:quickinfo="BP Relationship Number">
|
||
<Documentation>
|
||
<Summary>The business partner relationship number is an internal number that identifies the business partner relationship set.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartnerCompany" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartnerPerson" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ValidityEndDate" Type="Edm.DateTime" Nullable="false" Precision="0" sap:display-format="Date" sap:label="Valid To" sap:quickinfo="Validity Date (Valid To)"/>
|
||
<Property Name="ValidityStartDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Valid From" sap:quickinfo="Validity Date (Valid From)"/>
|
||
<Property Name="IsStandardRelationship" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Standard" sap:quickinfo="Standard Relationship">
|
||
<Documentation>
|
||
<Summary>States whether the relationship is a standard relationship.</Summary>
|
||
<LongDescription>If several relationships of the BP relationship category contact person have been defined for, you can set the indicator standard relationship for one of these relationships.A relationship that is marked as a standard relationship can be used whenA certain scenario automatically selects a contact personThe contact person responsible is not knownYou can give this indicator to only one business partner relationship of a BP relationship category for a particular period. Another relationship of the same relationship category can be indicated as the standard relationship only if the periods for the relationship do not overlap or coincide.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="RelationshipCategory" Type="Edm.String" MaxLength="6" sap:display-format="UpperCase" sap:label="Relationship Cat." sap:heading="RelCat" sap:quickinfo="Business Partner Relationship Category">
|
||
<Documentation>
|
||
<Summary>A relationship may exist between two business partners. The business partner relationship category characterizes the features of the relationship.</Summary>
|
||
<LongDescription>A distinction is made between a one-way and an undirected business partner relationship category. In a one-way relationship category, the relationship extends from one partner to another, but not vice versa.Marriage (undirected)Employee (one-way)Contact person (one-way)</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<NavigationProperty Name="to_ContactAddress" Relationship="API_BUSINESS_PARTNER.assoc_68C6FA4D5F974F8BBFCA5D234FA05107" FromRole="FromRole_assoc_68C6FA4D5F974F8BBFCA5D234FA05107" ToRole="ToRole_assoc_68C6FA4D5F974F8BBFCA5D234FA05107"/>
|
||
<NavigationProperty Name="to_ContactRelationship" Relationship="API_BUSINESS_PARTNER.assoc_ABC4A572A4A8802D97BA70498CCE4A4E" FromRole="FromRole_assoc_ABC4A572A4A8802D97BA70498CCE4A4E" ToRole="ToRole_assoc_ABC4A572A4A8802D97BA70498CCE4A4E"/>
|
||
</EntityType>
|
||
<EntityType Name="A_BusinessPartnerRoleType" sap:label="Role" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="BusinessPartner"/>
|
||
<PropertyRef Name="BusinessPartnerRole"/>
|
||
</Key>
|
||
<Property Name="BusinessPartner" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BusinessPartnerRole" Type="Edm.String" Nullable="false" MaxLength="6" sap:display-format="UpperCase" sap:label="BP Role">
|
||
<Documentation>
|
||
<Summary>Function that a business partner takes on, depending on a business transaction.</Summary>
|
||
<LongDescription>You can define business partner roles along with their attributes in Customizing.You can create an alphanumeric, 6-digit key for the BP role. You can also choose a title as the short form and a description as the long form for the role text.Screen control in the dialog takes place by assigning a BP view.A program can access specific business partner roles for a business partner using thebusiness partner role category . The role categories are also in the TB003 table.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ValidFrom" Type="Edm.DateTimeOffset" Precision="0" sap:label="Valid From" sap:quickinfo="Validity Start of a BP Role"/>
|
||
<Property Name="ValidTo" Type="Edm.DateTimeOffset" Precision="0" sap:label="Valid To" sap:quickinfo="Validity End of a BP Role"/>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization Group" sap:heading="AGrp">
|
||
<Documentation>
|
||
<Summary>You can use authorization groups to stipulate which business partners a user is allowed to process.</Summary>
|
||
<LongDescription>Use the following authorization object:'Business partners: authorization groups' (B_BUPA_GRP).The system only checks this authorization if you made an entry in the "Authorization group" field for the business partner. Otherwise, any user may process the business partner.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_BusinessPartnerTaxNumberType" sap:label="Tax Number" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="BusinessPartner"/>
|
||
<PropertyRef Name="BPTaxType"/>
|
||
</Key>
|
||
<Property Name="BusinessPartner" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Business Partner" sap:quickinfo="Business Partner Number">
|
||
<Documentation>
|
||
<Summary>Key identifying a business partner in the SAP system. The key is unique within a client.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BPTaxType" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Tax Number Category">
|
||
<Documentation>
|
||
<Summary>Specifies the tax number category.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BPTaxNumber" Type="Edm.String" MaxLength="20" sap:display-format="UpperCase" sap:label="Tax number" sap:heading="Tax Number" sap:quickinfo="Business Partner Tax Number">
|
||
<Documentation>
|
||
<Summary>Specifies the tax number.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BPTaxLongNumber" Type="Edm.String" MaxLength="60" sap:display-format="UpperCase" sap:label="Tax Number" sap:quickinfo="Business Partner Tax Number">
|
||
<Documentation>
|
||
<Summary>Specifies the tax number.</Summary>
|
||
<LongDescription>You can enter up to 60 characters in this field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization Group" sap:heading="AGrp">
|
||
<Documentation>
|
||
<Summary>You can use authorization groups to stipulate which business partners a user is allowed to process.</Summary>
|
||
<LongDescription>Use the following authorization object:'Business partners: authorization groups' (B_BUPA_GRP).The system only checks this authorization if you made an entry in the "Authorization group" field for the business partner. Otherwise, any user may process the business partner.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_CustomerType" sap:label="Customer" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Customer"/>
|
||
</Key>
|
||
<Property Name="Customer" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number">
|
||
<Documentation>
|
||
<Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization" sap:heading="AuGr" sap:quickinfo="Authorization Group">
|
||
<Documentation>
|
||
<Summary>The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BillingIsBlockedForCustomer" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Billing Block" sap:heading="BlBlk" sap:quickinfo="Central Billing Block for Customer">
|
||
<Documentation>
|
||
<Summary>Indicates if the processing of billing documents is blocked for the customer in all sales areas (company-wide, for example).</Summary>
|
||
<LongDescription>You can define different kinds of block, according to the needs of your organization. You can, for example, automatically block the processing of all credit memos to a certain customer, pending manual approval.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CreatedByUser" Type="Edm.String" MaxLength="12" sap:display-format="UpperCase" sap:label="Created by" sap:quickinfo="Name of Person who Created the Object" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Name with which the user who entered the master record was logged on in the R/3 System.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CreationDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Created on" sap:heading="Date" sap:quickinfo="Date on which the Record Was Created" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Date on which the master record, or the part of the master record being viewed, was created.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerAccountGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Account Group" sap:heading="Group" sap:quickinfo="Customer Account Group">
|
||
<Documentation>
|
||
<Summary>The account group is a classifying feature within customer master records. The account group determines:</Summary>
|
||
<LongDescription>in which number range the customer account number should be;whether the number is assigned by the user or by the system;which specifications are necessary or possible in the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerClassification" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Customer Classific." sap:heading="Cl" sap:quickinfo="Customer Classification">
|
||
<Documentation>
|
||
<Summary>Specifies a classification of the customer (for example, classifies the customer as a bulk purchaser).</Summary>
|
||
<LongDescription>The classifications are freely definable according to the needs of your organization.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerFullName" Type="Edm.String" MaxLength="220" sap:display-format="UpperCase" sap:label="Customer Name" sap:quickinfo="Customer Full Name" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="CustomerName" Type="Edm.String" MaxLength="80" sap:label="Name of Customer" sap:heading="Customer" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="DeliveryIsBlocked" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Delivery block" sap:heading="DlvBl" sap:quickinfo="Central delivery block for the customer">
|
||
<Documentation>
|
||
<Summary>Indicates if delivery processing is blocked for the customer in all sales areas (company-wide, for example).</Summary>
|
||
<LongDescription>You can define different kinds of block, according to the needs of your organization. You can, for example, automatically block all deliveries to a certain customer for credit reasons.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="NFPartnerIsNaturalPerson" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Natural Person">
|
||
<Documentation>
|
||
<Summary>Denotes a natural person.</Summary>
|
||
<LongDescription>In the following countries, the system needs to know whether the taxpayer is a legal or natural person so that it can check the tax numbers correctly:BrazilBulgariaColombiaCroatiaGreeceItalyMexicoPeruSloveniaThailandUkraineThe flag is also used in conjunction with the Statement of Payments to Natural Persons report, as used in the Czech Republic and in Slovakia. This report only covers customers and vendors for whom you have set this indicator.In South Korea, it is used in conjunction with the Generic Withholding Tax Reporting program.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="OrderIsBlockedForCustomer" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Order Block" sap:heading="OrBlk" sap:quickinfo="Central Order Block for Customer">
|
||
<Documentation>
|
||
<Summary>Indicates if sales order processing is blocked for the customer in all sales areas (company-wide, for example).</Summary>
|
||
<LongDescription>If you block sales order processing, the block counts for the following partner functions of the customer:Sold-to partyShip-to partyPayerIf you want to process an order where the ship-to party differs from the sold-to party, and the ship-to party is blocked, you cannot process the order.You can define different kinds of block, according to the needs of your organization. You can, for example, automatically block all free of charge deliveries and credit memo requests for a certain customer, pending manual approval before further processing can take place.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PostingIsBlocked" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Posting Block" sap:heading="B" sap:quickinfo="Central Posting Block">
|
||
<Documentation>
|
||
<Summary>Indicates that the account is blocked for posting for all company codes.</Summary>
|
||
<LongDescription>If you set this indicator, the system prevents users from posting items to this account and issues an error message to inform them that the account is blocked.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Supplier" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Supplier" sap:quickinfo="Account Number of Supplier">
|
||
<Documentation>
|
||
<Summary>Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerCorporateGroup" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Group Key" sap:heading="Group">
|
||
<Documentation>
|
||
<Summary>If the customer or the vendor belongs to a group, you can enter a group key here. The group key is freely assignable.</Summary>
|
||
<LongDescription>If you create a matchcode using this group key, group evaluations are possible.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="FiscalAddress" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Fiscal address" sap:heading="Fisc.addr." sap:quickinfo="Account number of the master record with the fiscal address">
|
||
<Documentation>
|
||
<Summary>Account number of another master record in which the official address is stored. This address is used, for example, for tax reports to the tax authorities in Italy.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Industry" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Industry" sap:heading="Indus." sap:quickinfo="Industry key" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>An industry is a distinct group of companies with the same basic business activity. The industry key is used in selecting data for evaluations (for example, a vendor master data list). You can specify industries such as trade, banking, service, manufacturing, health care, public service, media and so on.</Summary>
|
||
<LongDescription>The industry field belongs to the general data area of customer and vendor master records.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IndustryCode1" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Industry Code 1" sap:heading="Ind.Code 1">
|
||
<Documentation>
|
||
<Summary>Specifies the code that uniquely identifies the industry (or industries) of the customer.</Summary>
|
||
<LongDescription>Depending on the standards your organization uses (for example, Standard Industry Codes (SIC)), enter the appropriate code. You can assign more than one industry code to a customer by choosing Create more.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IndustryCode2" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Industry Code 2" sap:heading="Ind.Code 2">
|
||
<Documentation>
|
||
<Summary>Specifies an additional code that identifies the industry (or industries) of the customer.</Summary>
|
||
<LongDescription>Depending on the standards your organization uses (for example, Standard Industry Codes (SIC)), enter the appropriate code.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IndustryCode3" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Industry Code 3" sap:heading="Ind.Code 3">
|
||
<Documentation>
|
||
<Summary>Specifies an additional code that identifies the industry (or industries) of the customer.</Summary>
|
||
<LongDescription>Depending on the standards your organization uses (for example, Standard Industry Codes (SIC)), enter the appropriate code.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IndustryCode4" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Industry Code 4" sap:heading="Ind.Code 4">
|
||
<Documentation>
|
||
<Summary>Specifies an additional code that identifies the industry (or industries) of the customer.</Summary>
|
||
<LongDescription>Depending on the standards your organization uses (for example, Standard Industry Codes (SIC)), enter the appropriate code.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IndustryCode5" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Industry Code 5" sap:heading="Ind.Code 5">
|
||
<Documentation>
|
||
<Summary>Specifies an additional code that identifies the industry (or industries) of the customer.</Summary>
|
||
<LongDescription>Depending on the standards your organization uses (for example, Standard Industry Codes (SIC)), enter the appropriate code.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InternationalLocationNumber1" Type="Edm.String" MaxLength="7" sap:display-format="NonNegative" sap:label="Int. location no. 1" sap:heading="ILN 1" sap:quickinfo="International location number (part 1)">
|
||
<Documentation>
|
||
<Summary>Here you enter the first 7 digits of the international location number.</Summary>
|
||
<LongDescription>The International Location Number (ILN) is assigned (in Germany by the Centrale for Coorganisation GmbH)) when a company is founded. It consists of 13 digits, the last digit being the check digit. There are two categories of location numbers:Participants who only need an ILN to cleary and unmistakably identify themselves for communication with the business partner are given a category 1 ILN. This cannot be used to identify articles by means of EAN.Participants who wish to assign the location numbers for their own enterprise areas are given a category 2 ILN. For a category 2 ILN, digits 1 to 7 are described as basis number. This is used as basis for the creation of article numbers (EAN).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="NielsenRegion" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Nielsen Indicator" sap:heading="NS" sap:quickinfo="Nielsen ID">
|
||
<Documentation>
|
||
<Summary>Specifies a regional division according to the market categories created by the A. C. Nielsen company.</Summary>
|
||
<LongDescription>By allocating a Nielsen division, you can use the services of the Nielsen Institute to create a market analysis of your customers.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ResponsibleType" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Tax type">
|
||
<Documentation>
|
||
<Summary>Classification of companies according to tax aspects.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxNumber1" Type="Edm.String" MaxLength="16" sap:display-format="UpperCase" sap:label="Tax Number 1" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Specifies the tax number.</Summary>
|
||
<LongDescription>Enter the appropriate tax number:Country/Region Tax NumberArgentina CUIT number or CUIL numberBelgium Enterprise numberBrazil CNPJ numberBulgaria Unified identification codeChile RUT numberChina VAT registration number (shui wu deng ji hao)Colombia NIT numberCroatia Legal persons: company identification numberNatural persons: JMBG numberCzech Republic DIC numberFrance SIRET numberGreece Personal IDHungary Tax numberItaly Fiscal codeKazakhstan RNN (obsolete)Mexico RFC numberNetherlands SI registration number (Aansluitnummer UWV) of chain- liability vendorNorway VAT numberPeru RUC numberPhilippines Taxpayer identification number (see below)Poland NIP numberPortugal NIF numberRomania Tax numberRussia INNSlovakia DIC numberSlovenia Tax numberSouth Korea Natural persons: Personal identification numberLegal persons: Corporation IDSpain NIF numberSwitzerland UID numberTaiwan GUI registration numberThailand Personal IDTurkey Name of business partner's tax officeUkraine Taxpayer identification numberUnited Kingdom Company registration numberUnited States Social security numberVenezuela RIF numberIn the Philippines, enter the taxpayer identification number with a V or N at the end, as follows:If the business partner is liable to VAT: 999-999-999-999VIf the business partner is not liable to VAT: 999-999-999-999N</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxNumber2" Type="Edm.String" MaxLength="11" sap:display-format="UpperCase" sap:label="Tax Number 2" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Specifies the tax number.</Summary>
|
||
<LongDescription>Enter the appropriate tax number:Country/Region Tax NumberArgentina NIP number or CM numberBelgium VAT numberBrazil CPF numberBulgaria Legal persons: tax numberNatural persons: personal IDCroatia OIB number Czech Republic ICO numberFrance SIREN numberGreece AFM numberIndia TINItaly VAT numberKazakhstan BC (Beneficiary Code)Netherlands BSN numberNorway Organization registration numberRussia OKPO codeSlovakia ICO numberSouth Korea VAT registration numberSweden Organization registration numberSwitzerland VAT numberTaiwan Tax registration numberUkraine Legal persons: USREOU numberNatural persons: SRNP numberTurkey Tax numberUnited Kingdom NI numberUnited States Employer identification numberVenezuela NIT number</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxNumber3" Type="Edm.String" MaxLength="18" sap:display-format="UpperCase" sap:label="Tax Number 3" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Specifies the tax number.</Summary>
|
||
<LongDescription>Enter the tax number that applies:Country Tax numberArgentina Withholding agent numberBrazil State tax numberBulgaria Social security numberMexico CURP numberKazakhstan BINNetherlands Tax registration number (Loonbelastingnummer) of the chain-liability vendorRussia KPP numberThailand Tax ID Ukraine VAT registration number</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxNumber4" Type="Edm.String" MaxLength="18" sap:display-format="UpperCase" sap:label="Tax Number 4" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Specifies the tax number.</Summary>
|
||
<LongDescription>Enter the appropriate tax number:Country Tax NumberBrazil Municipal tax numberKazakhstan IINRussia OFK number (for public bodies only)</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxNumber5" Type="Edm.String" MaxLength="60" sap:display-format="UpperCase" sap:label="Tax Number 5" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Kazakhstan</Summary>
|
||
<LongDescription>Specifies the certificate of registration as VAT payer in the following format: XXXXXYYYYYYYZZZZZZZZ, where: XXXXX is the certificate serial number, YYYYYYY is the certificate number and ZZZZZZZZ is the date of certificate issue.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxNumberType" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Tax Number Type" sap:heading="Tax No.Ty.">
|
||
<Documentation>
|
||
<Summary>Taxes in Argentina:</Summary>
|
||
<LongDescription>The format and the check of tax number 1 depend on the two-digit tax number type.The tax number type is an identification type for tax in Argentina (for example, 80 for CUIT) and is used for the DGI tax report.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="VATRegistration" Type="Edm.String" MaxLength="20" sap:display-format="UpperCase" sap:label="VAT Registration No." sap:quickinfo="VAT Registration Number">
|
||
<Documentation>
|
||
<Summary>VAT registration number (VAT reg.no.) of the customer, vendor or your company code.</Summary>
|
||
<LongDescription>The VAT registration number is used within the EU for tax-exempt deliveries for the "EC sales list". The check rules are defined for each EU country and cannot be changed.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DeletionIndicator" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Deletion flag" sap:heading="DelF" sap:quickinfo="Central Deletion Flag for Master Record">
|
||
<Documentation>
|
||
<Summary>Indicates that all data in this master record is to be deleted.</Summary>
|
||
<LongDescription>To delete this data, you have to run the archiving program for Accounts Receivable or Payable. This program will archive all master records marked for deletion provided that there is no dependent data in them.Deletion flags can also be used in the program for deleting master data. You should, however, run this program only to delete test data prior to production startup.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<NavigationProperty Name="to_CustomerCompany" Relationship="API_BUSINESS_PARTNER.assoc_BB9464C0EE976A75A05F937B73A26763" FromRole="FromRole_assoc_BB9464C0EE976A75A05F937B73A26763" ToRole="ToRole_assoc_BB9464C0EE976A75A05F937B73A26763"/>
|
||
<NavigationProperty Name="to_CustomerSalesArea" Relationship="API_BUSINESS_PARTNER.assoc_70A8B5CCADF265E097DC86BC7B699B31" FromRole="FromRole_assoc_70A8B5CCADF265E097DC86BC7B699B31" ToRole="ToRole_assoc_70A8B5CCADF265E097DC86BC7B699B31"/>
|
||
<NavigationProperty Name="to_CustomerTaxGrouping" Relationship="API_BUSINESS_PARTNER.assoc_0DE5F89839F0BD9497F35D85212F05CE" FromRole="FromRole_assoc_0DE5F89839F0BD9497F35D85212F05CE" ToRole="ToRole_assoc_0DE5F89839F0BD9497F35D85212F05CE"/>
|
||
<NavigationProperty Name="to_CustomerText" Relationship="API_BUSINESS_PARTNER.assoc_301BF3C95F38823A34CFF6B5A5EF3514" FromRole="FromRole_assoc_301BF3C95F38823A34CFF6B5A5EF3514" ToRole="ToRole_assoc_301BF3C95F38823A34CFF6B5A5EF3514"/>
|
||
</EntityType>
|
||
<EntityType Name="A_CustomerCompanyType" sap:label="Customer Company" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Customer"/>
|
||
<PropertyRef Name="CompanyCode"/>
|
||
</Key>
|
||
<Property Name="Customer" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number">
|
||
<Documentation>
|
||
<Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CompanyCode" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Company Code" sap:heading="CoCd">
|
||
<Documentation>
|
||
<Summary>The company code is an organizational unit within financial accounting.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="APARToleranceGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Tolerance Group" sap:quickinfo="Tolerance Group for Business Partner/G/L Account">
|
||
<Documentation>
|
||
<Summary>Contains settings that control how the system handles differences between the invoice amount and the amount received from a customer or the amount paid to a supplier. A tolerance group is unique within a company code.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AccountByCustomer" Type="Edm.String" MaxLength="12" sap:display-format="UpperCase" sap:label="Account at customer" sap:heading="Acct at cust" sap:quickinfo="Our account number at customer">
|
||
<Documentation>
|
||
<Summary>This field contains the account number the company is listed under at the customer.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AccountingClerk" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Clerk Abbrev." sap:quickinfo="Accounting Clerk Abbreviation">
|
||
<Documentation>
|
||
<Summary>Identification code for the accounting clerk.</Summary>
|
||
<LongDescription>The name of the accounting clerk defined by this identification code can be used in the payment program for correspondence and reporting (for example, open item lists).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AccountingClerkFaxNumber" Type="Edm.String" MaxLength="31" sap:label="Acctg clerk's fax" sap:heading="Accounting clerk's fax" sap:quickinfo="Accounting clerk's fax number at the customer/vendor"/>
|
||
<Property Name="AccountingClerkInternetAddress" Type="Edm.String" MaxLength="130" sap:label="Clrk's internet add." sap:heading="Clerk's internet address" sap:quickinfo="Internet address of partner company clerk"/>
|
||
<Property Name="AccountingClerkPhoneNumber" Type="Edm.String" MaxLength="30" sap:display-format="UpperCase" sap:label="Acct.clerks tel.no." sap:heading="Accting clerk's telephone no." sap:quickinfo="Accounting clerk's telephone number at business partner"/>
|
||
<Property Name="AlternativePayerAccount" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Alternative payer" sap:heading="Alt.payer" sap:quickinfo="Account number of an alternative payer">
|
||
<Documentation>
|
||
<Summary/>
|
||
<LongDescription>Account number of the customer for whom automatic payment transactions are to be carried out.The account number is only needed if bank collections are not to be made via the customer who owes the receivables. The same applies to refunds of payables.The specification in this field only applies to this company code. There is another field in which you can enter an alternative payee for all company codes. If both fields are filled, the specification for the company code has priority.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization" sap:heading="AuGr" sap:quickinfo="Authorization Group">
|
||
<Documentation>
|
||
<Summary>The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CollectiveInvoiceVariant" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Coll.Invoice Variant" sap:quickinfo="Collective Invoice Variant">
|
||
<Documentation>
|
||
<Summary>Indicator which specifies at what intervals the collective invoices are to be created for the customer.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerAccountNote" Type="Edm.String" MaxLength="30" sap:label="Account Memo" sap:quickinfo="Memo">
|
||
<Documentation>
|
||
<Summary>Internal memo of the accounting department.</Summary>
|
||
<LongDescription>The memo serves only as information on special features of the customer/vendor.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerHeadOffice" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Head office" sap:heading="Hd office" sap:quickinfo="Head office account number (in branch accounts)">
|
||
<Documentation>
|
||
<Summary>This field contains the account number of the head office.</Summary>
|
||
<LongDescription>This account number is only specified for branch accounts. All postings for which the account number of the branch is specified, are automatically posted to the head office account. The account number of the branch affected is noted in the line items.No line items or balances are managed in the branch account.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerSupplierClearingIsUsed" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Clearing with vendor" sap:quickinfo="Indicator: Clearing between customer and vendor ?">
|
||
<Documentation>
|
||
<Summary>Indicates that during automatic payment transactions clearing is made with the corresponding vendor account, and that during manual clearing procedures, the items of that vendor account are also selected.</Summary>
|
||
<LongDescription>To use this function in automatic payment transactions, you have toenter the vendor account number in the customer master record,enter the customer account number in the vendor master record, andselect the "Clearing with customer" indicator in the vendor master record.If you set this indicator, the system will also include items of the vendor account in customer dunning.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="HouseBank" Type="Edm.String" MaxLength="5" sap:display-format="UpperCase" sap:label="House Bank" sap:heading="House Bk" sap:quickinfo="Short Key for a House Bank">
|
||
<Documentation>
|
||
<Summary>All bank data is determined using this key.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InterestCalculationCode" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Interest indicator" sap:heading="Interest Indicator" sap:quickinfo="Interest Indicator">
|
||
<Documentation>
|
||
<Summary>You enter an interest indicator here if you want the business partner to be included in automatic interest calculation.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InterestCalculationDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Last Key Date" sap:heading="Key Date Lst Int.Calc" sap:quickinfo="Key Date of Last Interest Calculation">
|
||
<Documentation>
|
||
<Summary>The date in this field displays the last time the interest calculation program processed this account. This is generally the upper limit of the last interest run.</Summary>
|
||
<LongDescription>Generally, this date is automatically maintained by the program (batch input). A manual entry in this field should only be made if an error has occurred or when implementing the interest calculation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IntrstCalcFrequencyInMonths" Type="Edm.String" MaxLength="2" sap:display-format="NonNegative" sap:label="Int.Calc.Freq." sap:heading="Interest Calc. Frequency" sap:quickinfo="Interest Calculation Frequency in Months">
|
||
<Documentation>
|
||
<Summary>An entry in this field determines the intervals (in months) at which interest is to be calculated automatically for this account (account balance interest calculation). The interest calculation frequency is added to the date of the last interest calculation.</Summary>
|
||
<LongDescription>Date of last interest calculation: 3/31.+ 01 month interest calculation frequency= 4/30 upper limit for the current interest runThe calculation period specified as a report parameter determines whether an account is included in an interest run.The upper limit of the interest run is calculated as in the above example and compared with the upper limit of the calculation entered in the interest run (report parameter). If the calculated upper limit is after the calculation period, the account is not included in interest calculation.If you maintain the interest calculation frequency in the account master record, this entry is used to calculate the upper limit. If not, the interest calculation frequency entered for the interest indicator is used.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IsToBeLocallyProcessed" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Local Processing" sap:quickinfo="Indicator: Local Processing?">
|
||
<Documentation>
|
||
<Summary>Indicates that payment transactions and dunning notices are created for the branch.</Summary>
|
||
<LongDescription>Normally automatic payment transactions and dunning notices are created for the head office.NoteSelect this indicator only if this account is a head office account.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ItemIsToBePaidSeparately" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Individual Payment" sap:quickinfo="Indicator: Pay All Items Separately?">
|
||
<Documentation>
|
||
<Summary>If this indicator is set, every customer/vendor open item is paid separately during automatic payment transactions. This means that open items are not grouped together for payment.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LayoutSortingRule" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Sort Key" sap:heading="Sort" sap:quickinfo="Key for Sorting According to Assignment Numbers">
|
||
<Documentation>
|
||
<Summary>Indicates the layout rule for the Allocation field in the document line item.</Summary>
|
||
<LongDescription>The system uses a standard sort sequence for displaying line items. Among other things, it sorts the items according to the content of the Allocation field. This field can be filled either manually or automatically (by the system) when a document line item is entered.For this purpose, the system requires rules that determine which information is to be taken from the document header or from the document line item and placed in the field. The rules can be stored in the master record of an account which enables you to determine the standard sort sequence on an account-specific basis.NoteField information from another document line item cannot be adopted into the field of a particular item.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PaymentBlockingReason" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Payment Block" sap:heading="Block Ind." sap:quickinfo="Block Key for Payment">
|
||
<Documentation>
|
||
<Summary>Block key (enqueue key) that is used to block an open item or an account to payment transactions.</Summary>
|
||
<LongDescription>You can use the block key as described below.Automatic Payment TransactionsIn automatic payment transactions, the block takes effect when it is entered in the system as follows:In the master recordIn the documentIf you enter the block in the master record then all open items for this account are contained in the exception list.The following block keys have a special meaning in the master record:The block key * has the effect that all items of the account are skipped in automatic payment transactions.The block key + has the effect that all items are skipped in which a payment method was not entered explicitly.The block key A is always set automatically when a down payment is entered. Therefore, you must not delete the block key A or use it for other purposes.Whether a block key can be set or removed in payment proposal processing depends on the attribute Changeable in payment proposal of the block key.Manual PaymentsManual payments are only affected by a block key in the document if you set the attribute Blocked for manual payments in the block key.A block key that was set in the master record does not have any effect on manual payments. You can have the system issue a warning message in that case. To do so, you have to make system settings. Set up message 671 of work area F5 in the configuration step Change Message Control, udter Finance -> Localization -> General Settings.Release for PaymentIf you want to use a block key for payment release in accounting, then you have to set the attribute Not Changeable for the block key. You make this setting in the configuration step Control Payment Block Reasons, under Finance -> Accounts Payable -> General Payment Settings.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PaymentMethodsList" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Payment Methods" sap:heading="Methods" sap:quickinfo="List of Respected Payment Methods">
|
||
<Documentation>
|
||
<Summary>List of payment methods which may be used in automatic payment transactions with this customer/vendor if you do not specify a payment method in the item to be paid.</Summary>
|
||
<LongDescription>If you do specify a particular payment method in the item to be paid, this specification has priority over the specifications in the master record. You may also specify payment methods in the item which are not listed in the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PaymentTerms" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Terms of Payment" sap:heading="PayT" sap:quickinfo="Terms of Payment Key">
|
||
<Documentation>
|
||
<Summary>Key for defining payment terms composed of cash discount percentages and payment periods.</Summary>
|
||
<LongDescription>It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PaytAdviceIsSentbyEDI" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Pmnt advice by EDI" sap:heading="EDI" sap:quickinfo="Indicator: Send Payment Advices by EDI">
|
||
<Documentation>
|
||
<Summary>This indicator specifies that the customer/vendor should be sent all payment advice information by EDI.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PhysicalInventoryBlockInd" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Co.code post.block" sap:heading="B" sap:quickinfo="Posting block for company code">
|
||
<Documentation>
|
||
<Summary>Indicates that the account is blocked for posting in the specified company code.</Summary>
|
||
<LongDescription>If you set this indicator, the system prevents users from posting items to this account and issues an error message to inform them that the account is blocked.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ReconciliationAccount" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Reconciliation Acct" sap:heading="Recon.Acct" sap:quickinfo="Reconciliation Account in General Ledger">
|
||
<Documentation>
|
||
<Summary>The reconciliation account in G/L accounting is the account which is updated parallel to the subledger account for normal postings (for example, invoice or payment).</Summary>
|
||
<LongDescription>For special postings (for example, down payment or bill of exchange), this account is replaced by another account (for example, 'down payments received' instead of 'receivables').The replacement takes place due to the special G/L indicator which you must specify for these types of postings.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="RecordPaymentHistoryIndicator" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Record Pmnt History" sap:quickinfo="Indicator: Record Payment History ?">
|
||
<Documentation>
|
||
<Summary>Indicator that the payment history of the customer is to be recorded.</Summary>
|
||
<LongDescription>The amount and number of payments are then recorded per calendar month, as well as the average days in arrears.Information about cash discount payments and net payments is recorded separately.The indicator should not be set for one-time accounts and accounts which are paid automatically (bank collection or bank bill in Germany, bill of exchange payment request in France).You can only carry out evaluation of the payment history, for example, with the report for customer evaluation with OI listing, if you have selected this field.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="UserAtCustomer" Type="Edm.String" MaxLength="15" sap:label="User at customer" sap:heading="User at cust.">
|
||
<Documentation>
|
||
<Summary>Name or identification code of the accounting clerk at the customer.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DeletionIndicator" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Co.cde deletion flag" sap:heading="DelF" sap:quickinfo="Deletion Flag for Master Record (Company Code Level)">
|
||
<Documentation>
|
||
<Summary>Indicates that the company code data in this master record is to be deleted.</Summary>
|
||
<LongDescription>To delete this data, you have to run the archiving program for Accounts Receivable or Payable. This program will archive all master records marked for deletion provided that there is no dependent data in them.This deletion flag cannot be used in the program that deletes master data. You should, however, run this program only to delete test data prior to production startup.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CashPlanningGroup" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Planning Group" sap:heading="Plan. Group">
|
||
<Documentation>
|
||
<Summary>In cash management, customers and vendors are allocated to planning groups by means of an entry made in the master record.</Summary>
|
||
<LongDescription>You can define these planning groups in Customizing or the Implementation Guide (you will need to ensure that they are all the same length). In order to improve the liquidity forecast display for major customers and vendors, it can be advisable to enter their account number as the planning group.For the planning groups themselves a naming convention should be set up to improve liquidity forecasting. In the following examples, the customer planning groups begin with an "R" for receipts, and the vendor planning groups begin with an "E" for expenses.R1 Customers paying by bank collectionR2 Other domestic customersR3 Customers abroadR4 Affiliated company customersR5 High risk customersR6 Major customersR7 Rental incomeR8 Repayment of loans...E1 Domestic vendorsE2 Vendors abroadE3 Affiliated company vendorsE4 Major vendorsE5 Personnel costsE6 TaxesE7 Investments...</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="KnownOrNegotiatedLeave" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Known/Negotiat.Leave" sap:heading="Leave" sap:quickinfo="Short Key for Known/Negotiated Leave">
|
||
<Documentation>
|
||
<Summary>With the key specified here, you can refer to known/negotiated leave.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ValueAdjustmentKey" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Value Adjustment" sap:quickinfo="Value Adjustment Key">
|
||
<Documentation>
|
||
<Summary>The value adjustment key controls the way the open items are processed during individual value adjustment.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerAccountGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Account Group" sap:heading="Group" sap:quickinfo="Customer Account Group">
|
||
<Documentation>
|
||
<Summary>The account group is a classifying feature within customer master records. The account group determines:</Summary>
|
||
<LongDescription>in which number range the customer account number should be;whether the number is assigned by the user or by the system;which specifications are necessary or possible in the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<NavigationProperty Name="to_CompanyText" Relationship="API_BUSINESS_PARTNER.assoc_B60166D8890DDF85A7D581A0BB2D1255" FromRole="FromRole_assoc_B60166D8890DDF85A7D581A0BB2D1255" ToRole="ToRole_assoc_B60166D8890DDF85A7D581A0BB2D1255"/>
|
||
<NavigationProperty Name="to_CustomerDunning" Relationship="API_BUSINESS_PARTNER.assoc_8273BE5CD7CC24B836264946436461DA" FromRole="FromRole_assoc_8273BE5CD7CC24B836264946436461DA" ToRole="ToRole_assoc_8273BE5CD7CC24B836264946436461DA"/>
|
||
<NavigationProperty Name="to_WithHoldingTax" Relationship="API_BUSINESS_PARTNER.assoc_65B2B550EF37ECC341EC132360E3D0A8" FromRole="FromRole_assoc_65B2B550EF37ECC341EC132360E3D0A8" ToRole="ToRole_assoc_65B2B550EF37ECC341EC132360E3D0A8"/>
|
||
</EntityType>
|
||
<EntityType Name="A_CustomerCompanyTextType" sap:label="Customer Company Text" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Customer"/>
|
||
<PropertyRef Name="CompanyCode"/>
|
||
<PropertyRef Name="Language"/>
|
||
<PropertyRef Name="LongTextID"/>
|
||
</Key>
|
||
<Property Name="Customer" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CompanyCode" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Company Code" sap:heading="CoCd">
|
||
<Documentation>
|
||
<Summary>The company code is an organizational unit within financial accounting.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Language" Type="Edm.String" Nullable="false" MaxLength="2" sap:label="Language" sap:heading="L" sap:quickinfo="Language key">
|
||
<Documentation>
|
||
<Summary>The language key is an abbreviation for the language of the object being processed (for example, standard text, form, style).</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LongTextID" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Text ID" sap:heading="ID">
|
||
<Documentation>
|
||
<Summary>The text ID defines the various types of texts related to a text object. For example, the object "TEXT" (standard texts) can have the following text IDs:</Summary>
|
||
<LongDescription>ST for user-specific standard texts (individual texts)SYST for cross-application system textsvarious IDs for specific application departments. You must have the appropriate access authorization in order to access these texts.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LongText" Type="Edm.String" sap:label="String" sap:sortable="false" sap:filterable="false"/>
|
||
</EntityType>
|
||
<EntityType Name="A_CustomerDunningType" sap:label="Customer Dunning" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Customer"/>
|
||
<PropertyRef Name="CompanyCode"/>
|
||
<PropertyRef Name="DunningArea"/>
|
||
</Key>
|
||
<Property Name="Customer" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number">
|
||
<Documentation>
|
||
<Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CompanyCode" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Company Code" sap:heading="CoCd">
|
||
<Documentation>
|
||
<Summary>The company code is an organizational unit within financial accounting.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DunningArea" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Dunning Area" sap:heading="Area">
|
||
<Documentation>
|
||
<Summary>The dunning area represents an organizational entity that is responsible for dunning. The dunning areas represent a sub-structure of the company codes.</Summary>
|
||
<LongDescription>If different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas.All dunning notices are made separately according to dunning areas, and if necessary with different dunning procedures.The dunning area must be noted in the line items. As long as documents are copied from preliminary work areas (billing documents), the dunning area can be derived from details such as division or sales area, if necessary.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DunningBlock" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Dunning Block" sap:heading="Block">
|
||
<Documentation>
|
||
<Summary>Key which reflects the reason for a dunning block indicator.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DunningLevel" Type="Edm.String" MaxLength="1" sap:display-format="NonNegative" sap:label="Dunning Level" sap:heading="Dun">
|
||
<Documentation>
|
||
<Summary>Number that specifies how often an item or account has been dunned.</Summary>
|
||
<LongDescription>The business partner has received the dunning level from the last dunning run.If you use dunning areas, it is the dunning level that the business partner received from the last dunning run in the dunning area assigned.The dunning program sets the dunning level automatically when the customer or vendor receives a dunning notice.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DunningProcedure" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Dunning Procedure" sap:heading="Procedure">
|
||
<Documentation>
|
||
<Summary>This field contains the key for the dunning procedure to be used.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DunningRecipient" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Dunning Recipient" sap:heading="Recipient" sap:quickinfo="Account Number of the Dunning Recipient">
|
||
<Documentation>
|
||
<Summary>Account number of the customer who is to be the recipient of the dunning letters.</Summary>
|
||
<LongDescription>The account number is only needed if dunning letters are not sent to the customer who owes the receivables.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LastDunnedOn" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Last Dunned" sap:heading="Date" sap:quickinfo="Date of Last Dunning Notice">
|
||
<Documentation>
|
||
<Summary>Date on which the last dunning notice was made.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LegDunningProcedureOn" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Legal Dunn.Proc.From" sap:heading="Leg.Dunn.Proc" sap:quickinfo="Date of the Legal Dunning Proceedings">
|
||
<Documentation>
|
||
<Summary>Date on which a legal dunning procedure was initiated.</Summary>
|
||
<LongDescription>The printing of dunning notices in the legal dunning procedure generates an internal notice about any further account movements. A dunning notice is not created for the customer.If the Legal dunning procedure field in the master record contains a date, this means that the account is involved in a legal dunning procedure. The relationship between this date and the dunning date does not affect how the account is processed.The printing of account movements in the legal dunning procedure differs from the normal printing of dunning notices as follows:You must specify a separate form for your dunning procedure in Customizing. For more information, see Customizing (IMG) under Dunning Forms.The dunning program also displays text element 520 "Legal dunning procedure". This makes it possible to display the date of the legal dunning procedure from the master record.The program also displays the documents blocked for dunning and those with a payment method (automatic debit, bank direct debit).Although dunning notices are printed, the dunning level does not change in the master record or in the items. New dunning level = old dunning level.The program only updates the date of the last dunning run.Enter the date manually.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DunningClerk" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Dunning Clerk" sap:heading="Clerk">
|
||
<Documentation>
|
||
<Summary>Identification code for the accounting clerk dealing with dunning letters.</Summary>
|
||
<LongDescription>Using this identification code, the accounting clerk whose name is printed on the dunning letters is determined.If this field is not filled, then the entry from the Accounting clerk field is used.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization" sap:heading="AuGr" sap:quickinfo="Authorization Group">
|
||
<Documentation>
|
||
<Summary>The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerAccountGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Account Group" sap:heading="Group" sap:quickinfo="Customer Account Group">
|
||
<Documentation>
|
||
<Summary>The account group is a classifying feature within customer master records. The account group determines:</Summary>
|
||
<LongDescription>in which number range the customer account number should be;whether the number is assigned by the user or by the system;which specifications are necessary or possible in the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_CustomerSalesAreaType" sap:label="Sales Area" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Customer"/>
|
||
<PropertyRef Name="SalesOrganization"/>
|
||
<PropertyRef Name="DistributionChannel"/>
|
||
<PropertyRef Name="Division"/>
|
||
</Key>
|
||
<Property Name="Customer" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number">
|
||
<Documentation>
|
||
<Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SalesOrganization" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Sales Organization" sap:heading="SOrg.">
|
||
<Documentation>
|
||
<Summary>An organizational unit responsible for the sale of certain products or services. The responsibility of a sales organization may include legal liability for products and customer claims.</Summary>
|
||
<LongDescription>You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DistributionChannel" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Distribution Channel" sap:heading="DChl">
|
||
<Documentation>
|
||
<Summary>The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.</Summary>
|
||
<LongDescription>You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Division" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Division" sap:heading="Dv">
|
||
<Documentation>
|
||
<Summary>A way of grouping materials, products, or services. The system uses divisions to determine the sales areas and the business areas for a material, product, or service.</Summary>
|
||
<LongDescription>A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AccountByCustomer" Type="Edm.String" MaxLength="12" sap:display-format="UpperCase" sap:label="Account at customer" sap:heading="Acct at cust" sap:quickinfo="Shipper's (Our) Account Number at the Customer or Vendor">
|
||
<Documentation>
|
||
<Summary>This field contains the account number your company is listed under at the customer or vendor.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization Group" sap:heading="AGrp">
|
||
<Documentation>
|
||
<Summary>The authorization group enables you protect access to certain objects.</Summary>
|
||
<LongDescription>In order to carry out a specific activity, the user must have authorization for the combination of the activity and the authorization group.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BillingIsBlockedForCustomer" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="BBlock for SlsA" sap:heading="BlBlk" sap:quickinfo="Billing block for customer (sales and distribution)">
|
||
<Documentation>
|
||
<Summary>Indicates if further billing activities are blocked for the customer. The block applies throughout the specified sales area.</Summary>
|
||
<LongDescription>If you enter a blocking indicator, billing that is already underway is continued. However, you cannot process the document further.Enter one of the values predefined for your system. If you want to block billing for a customer throughout an entire sales organization, you must enter a blocking indicator for each sales area in which the sales organization is defined.You can block billing for a customer if, for example, there are credit-related or legal problems to be resolved.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CompleteDeliveryIsDefined" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Complete Delivery" sap:heading="CDl" sap:quickinfo="Complete Delivery Defined for Each Sales Order?">
|
||
<Documentation>
|
||
<Summary>Indicates whether a sales order must be delivered completely in a single delivery or whether the order can be partially delivered and completed over a number of deliveries.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Currency" Type="Edm.String" MaxLength="5" sap:label="Currency" sap:heading="Curr." sap:semantics="currency-code">
|
||
<Documentation>
|
||
<Summary>Customer's currency for a sales area. This currency will be used to settle the customer's charges for the given sales organization.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerABCClassification" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="ABC classification" sap:heading="Cl" sap:quickinfo="Customer classification (ABC analysis)"/>
|
||
<Property Name="CustomerAccountAssignmentGroup" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Acct Assmt Grp Cust." sap:heading="AAGC" sap:quickinfo="Account Assignment Group for this Customer">
|
||
<Documentation>
|
||
<Summary>The account assignment group to which the system automatically posts the sales document.</Summary>
|
||
<LongDescription>The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerGroup" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Customer Group" sap:heading="CGrp">
|
||
<Documentation>
|
||
<Summary>Identifies a particular group of customers (for example, wholesale or retail) for the purpose of pricing or generating statistics.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerPaymentTerms" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Terms of Payment" sap:heading="PayT" sap:quickinfo="Terms of Payment Key">
|
||
<Documentation>
|
||
<Summary>Key for defining payment terms composed of cash discount percentages and payment periods.</Summary>
|
||
<LongDescription>It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerPriceGroup" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Customer Price Group" sap:heading="CPG">
|
||
<Documentation>
|
||
<Summary>A grouping of customers who share the same pricing requirements.</Summary>
|
||
<LongDescription>You can define price groups according to the needs of your organization and create pricing records for each group. You can, for example, define a group of customers to whom you want to give the same kind of discount. You can assign a price group to an individual customer either in the customer master record or in the sales document.The system can propose the price group from the customer master record. You can change the proposed value manually in the sales document at both header and item level.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerPricingProcedure" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Cust.Pric.Procedure" sap:heading="CuPP" sap:quickinfo="Customer Classification for Pricing Procedure Determination">
|
||
<Documentation>
|
||
<Summary>Determines which pricing procedure the system should apply when you create a sales document for the customer.</Summary>
|
||
<LongDescription>You can define different pricing procedures for your system. A pricing procedure determines the type and sequence of conditions that the system uses for pricing in, for example, a sales order.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DeliveryIsBlockedForCustomer" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="DelBlckSalesAr." sap:heading="DlvBl" sap:quickinfo="Customer delivery block (sales area)">
|
||
<Documentation>
|
||
<Summary>Indicates if further delivery processing is blocked for the customer. The block applies throughout the specified sales area.</Summary>
|
||
<LongDescription>If you enter a blocking indicator, delivery processing that is already underway is continued. However, no new processing can take place.Enter one of the values predefined for your system. If you want to block delivery processing for a customer within a particular sales organization, you must enter a blocking indicator for each sales area in which the sales organization is defined.You can block delivery processing for a customer if, for example, there are credit-related or legal problems to be resolved.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DeliveryPriority" Type="Edm.String" MaxLength="2" sap:display-format="NonNegative" sap:label="Delivery Priority" sap:heading="DPrio">
|
||
<Documentation>
|
||
<Summary>The delivery priority assigned to an item.</Summary>
|
||
<LongDescription>You can assign delivery priority to either a particular material or to a combination of customer and material. When you process deliveries collectively, you can use delivery priority as one of the selection criteria.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IncotermsClassification" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Incoterms" sap:heading="IncoT" sap:quickinfo="Incoterms (Part 1)">
|
||
<Documentation>
|
||
<Summary>Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).</Summary>
|
||
<LongDescription>Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IncotermsLocation2" Type="Edm.String" MaxLength="70" sap:label="Incoterms Location 2">
|
||
<Documentation>
|
||
<Summary>Provides additional information for the Incoterms. This field is only available for C-Clauses (if customized appropriately). Note the following for the incoterms versions below:</Summary>
|
||
<LongDescription>No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IncotermsVersion" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Incoterms Version" sap:heading="IncoV">
|
||
<Documentation>
|
||
<Summary>An incoterms version is an edition containing a list of international terms for transportation that is defined by the International Chamber of Commerce (ICC).</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IncotermsLocation1" Type="Edm.String" MaxLength="70" sap:label="Incoterms Location 1">
|
||
<Documentation>
|
||
<Summary>Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:</Summary>
|
||
<LongDescription>1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DeletionIndicator" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Del.ID SlsArea" sap:heading="D.ID" sap:quickinfo="Deletion flag for customer (sales level)">
|
||
<Documentation>
|
||
<Summary>Indicates that all data in the master record will be deleted for the specified sales area. Before the deletion is made, the system checks for dependent data that would prevent the deletion.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IncotermsTransferLocation" Type="Edm.String" MaxLength="28" sap:label="Incoterms (Part 2)" sap:heading="Inco. 2">
|
||
<Documentation>
|
||
<Summary>Additional information for the primary Incoterm.</Summary>
|
||
<LongDescription>If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InvoiceDate" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Invoicing Dates" sap:heading="IDate" sap:quickinfo="Invoice Dates (Calendar Identification)">
|
||
<Documentation>
|
||
<Summary>Identifies the calendar that determines the schedule of billing dates for the customer.</Summary>
|
||
<LongDescription>If, for example, a customer wants to consolidate the invoices you send out, you can predefine the billing schedule in a calendar in the system. During billing, the system automatically proposes the appropriate billing date from the calendar.The system proposes the billing schedule from the customer master record of the payer. You can change the value manually in the sales document.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ItemOrderProbabilityInPercent" Type="Edm.String" MaxLength="3" sap:display-format="NonNegative" sap:label="Order Probability" sap:heading="Prb" sap:quickinfo="Order Probability of the Item">
|
||
<Documentation>
|
||
<Summary>The probability (expressed as a percentage) of the customer confirming the inquiry or quotation item as part of a sales order.</Summary>
|
||
<LongDescription>The system combines the probability factors from the sales document type and from the customer master record of the sold-to party.If probability is 80% for the sales document type and 50% in the customer master record, the system combines the two values. In this case, the system takes 50% of 80% and proposes 40% for the item.The system proposes the probability. You can change the value manually for the item.You can generate requirements from quotations. Accordingly, the probability of quotation items affects how requirements are passed on. For example, a quotation for 100 pieces and a probability of 50% will generate requirements for 50 pieces.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="OrderCombinationIsAllowed" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Order Combination" sap:heading="OrdCm" sap:quickinfo="Order Combination Indicator">
|
||
<Documentation>
|
||
<Summary>Indicates whether you are allowed to combine orders during delivery processing.</Summary>
|
||
<LongDescription>The system proposes the indicator from the customer master record. You can change the value manually in the sales document at both header and item level.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="OrderIsBlockedForCustomer" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Ord.blk:sls ar." sap:heading="OrBlk" sap:quickinfo="Customer order block (sales area)">
|
||
<Documentation>
|
||
<Summary>Indicates if further sales order processing is blocked for the customer. The block applies throughout the specified sales area.</Summary>
|
||
<LongDescription>You can define blocks according to the needs of your organization. If you enter a blocking indicator, sales order processing that is already underway is continued. However, no new processing can occur.Enter one of the values predefined for your system. If you want to block sales order processing for a customer within a particular sales organization, you must enter a blocking indicator for each sales area in which the sale organization is defined.You can block sales order processing for a customer if, for example, there are credit-related or legal problems to be resolved.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PartialDeliveryIsAllowed" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Partial Deliv./Item" sap:heading="PD" sap:quickinfo="Partial Delivery at Item Level">
|
||
<Documentation>
|
||
<Summary>Specifies whether the customer requires full or partial delivery for the item.</Summary>
|
||
<LongDescription>You use this field to control partial deliveries at the item level. If the customer allows partial delivery, you can choose from different partial delivery options. For example, you can specify whether the customer allows you to make one delivery attempt only on the requested delivery date or whether unlimited delivery attempts are possible.When partial delivery indicator 'D' is set, the order can never have status 'fully delivered'. You must complete each item by entering a reason for rejection. This could be applied to scheduling agreements, for example.You can enter a value in this field only if the customer allows partial deliveries for the entire sales document.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PriceListType" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Price List Type" sap:heading="PL">
|
||
<Documentation>
|
||
<Summary>Identifies a price list or other condition type (for example, a surcharge or discount).</Summary>
|
||
<LongDescription>You can define price list types according to the needs of your own organization. Price list types can be grouped according to:the kind of price list (for example, wholesale or retail)the currency in which the price appearsthe number of the price list typeYou can use price list types to apply conditions during pricing or to generate statistics.In the customer master record, enter one of the values predefined for your system. The system proposes the value automatically during sales order processing. You can change the value manually in the sales document header.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SalesGroup" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Sales Group" sap:heading="SGrp">
|
||
<Documentation>
|
||
<Summary>A group of sales people who are responsible for processing sales of certain products or services.</Summary>
|
||
<LongDescription>By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria.If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market.You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SalesOffice" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Sales Office" sap:heading="SOff.">
|
||
<Documentation>
|
||
<Summary>A physical location (for example, a branch office) that has responsibility for the sale of certain products or services within a given geographical area.</Summary>
|
||
<LongDescription>When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office.You can assign each customer to a sales office in the customer master record.Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ShippingCondition" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Shipping Conditions" sap:heading="SC">
|
||
<Documentation>
|
||
<Summary>General shipping strategy for the delivery of goods from the vendor to the customer.</Summary>
|
||
<LongDescription>You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplyingPlant" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Delivering Plant" sap:heading="Plnt" sap:quickinfo="Delivering Plant (Own or External)">
|
||
<Documentation>
|
||
<Summary>Plant from which the goods should be delivered to the customer.</Summary>
|
||
<LongDescription>This plant is automatically copied into the sales order item as the default value.If there is no default value when you process the sales order item, enter a delivering plant.The value proposed in the item is eitherfrom the customer master record of the goods recipient, orfrom the material master recordThe system checks whether it can propose a value (and for your own plants, whether the material has been created in the plant). If the system can propose a value, the plant is copied to the sales order item where you can change it as required.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SalesDistrict" Type="Edm.String" MaxLength="6" sap:display-format="UpperCase" sap:label="Sales District" sap:heading="SDst">
|
||
<Documentation>
|
||
<Summary>A geographical sales district or region.</Summary>
|
||
<LongDescription>Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InvoiceListSchedule" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Invoice List Sched." sap:heading="InvSc" sap:quickinfo="Invoice List Schedule (calendar identification)">
|
||
<Documentation>
|
||
<Summary>Identifies the customer's factory calendar that is used during the processing of invoice lists.</Summary>
|
||
<LongDescription>An invoice list is a list of invoices (single or collective) that you create for the customer either periodically or on predefined dates. The periods and dates are defined in the customer's factory calendar. Typically, the recipient of an invoice list takes on the responsibility for collecting payments from numerous individual customers and receives a factoring or del credere discount for the service.If you want to create invoice lists for the customer, you must enter an identifier for a predefined factory calendar.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ExchangeRateType" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Exchange Rate Type">
|
||
<Documentation>
|
||
<Summary>Key representing a type of exchange rate in the system.</Summary>
|
||
<LongDescription>You enter the exchange rate type to store different exchange rates.You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AdditionalCustomerGroup1" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Customer Group 1" sap:heading="Grp1">
|
||
<Documentation>
|
||
<Summary>Specifies a customer-defined group of customers.</Summary>
|
||
<LongDescription>You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AdditionalCustomerGroup2" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Customer Group 2" sap:heading="Grp2">
|
||
<Documentation>
|
||
<Summary>Specifies a customer-defined group of customers.</Summary>
|
||
<LongDescription>You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AdditionalCustomerGroup3" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Customer Group 3" sap:heading="Grp3">
|
||
<Documentation>
|
||
<Summary>Specifies a customer-defined group of customers.</Summary>
|
||
<LongDescription>You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AdditionalCustomerGroup4" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Customer Group 4" sap:heading="Grp4">
|
||
<Documentation>
|
||
<Summary>Specifies a customer-defined group of customers.</Summary>
|
||
<LongDescription>You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AdditionalCustomerGroup5" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Customer Group 5" sap:heading="Grp5">
|
||
<Documentation>
|
||
<Summary>Specifies a customer-defined group of customers.</Summary>
|
||
<LongDescription>You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PaymentGuaranteeProcedure" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Paymt guarant. proc." sap:heading="CusPayGua" sap:quickinfo="Customer payment guarantee procedure">
|
||
<Documentation>
|
||
<Summary>This key identifies the customer payment guarantee procedure.</Summary>
|
||
<LongDescription>The customer payment guarantee procedure determines which payment guarantee procedure the system automatically uses when you create a sales document for the customer.In receivables risk management, the system determines the payment guarantee procedure taking into account:the key for the document payment guarantee procedure in the header for the sales document type.the customer payment guarantee procedure key in the customer master.You can define different payment guarantee procedures for your system. The payment guarantee procedure defines the type and sequence of forms of payment guarantee that the system assigns to the sales document items.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerAccountGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Account Group" sap:heading="Group" sap:quickinfo="Customer Account Group">
|
||
<Documentation>
|
||
<Summary>The account group is a classifying feature within customer master records. The account group determines:</Summary>
|
||
<LongDescription>in which number range the customer account number should be;whether the number is assigned by the user or by the system;which specifications are necessary or possible in the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<NavigationProperty Name="to_PartnerFunction" Relationship="API_BUSINESS_PARTNER.assoc_3747E462BFFBB3127682A67959ECC8AA" FromRole="FromRole_assoc_3747E462BFFBB3127682A67959ECC8AA" ToRole="ToRole_assoc_3747E462BFFBB3127682A67959ECC8AA"/>
|
||
<NavigationProperty Name="to_SalesAreaTax" Relationship="API_BUSINESS_PARTNER.assoc_49CF1243367384CB6C19B5648CA1F817" FromRole="FromRole_assoc_49CF1243367384CB6C19B5648CA1F817" ToRole="ToRole_assoc_49CF1243367384CB6C19B5648CA1F817"/>
|
||
<NavigationProperty Name="to_SalesAreaText" Relationship="API_BUSINESS_PARTNER.assoc_46D370A62F67996B992AE7C09589BEAD" FromRole="FromRole_assoc_46D370A62F67996B992AE7C09589BEAD" ToRole="ToRole_assoc_46D370A62F67996B992AE7C09589BEAD"/>
|
||
</EntityType>
|
||
<EntityType Name="A_CustomerSalesAreaTaxType" sap:label="Sales Area Tax" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Customer"/>
|
||
<PropertyRef Name="SalesOrganization"/>
|
||
<PropertyRef Name="DistributionChannel"/>
|
||
<PropertyRef Name="Division"/>
|
||
<PropertyRef Name="DepartureCountry"/>
|
||
<PropertyRef Name="CustomerTaxCategory"/>
|
||
</Key>
|
||
<Property Name="Customer" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number">
|
||
<Documentation>
|
||
<Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SalesOrganization" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Sales Organization" sap:heading="SOrg.">
|
||
<Documentation>
|
||
<Summary>An organizational unit responsible for the sale of certain products or services. The responsibility of a sales organization may include legal liability for products and customer claims.</Summary>
|
||
<LongDescription>You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DistributionChannel" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="RefDistCh-Cust/Mat." sap:heading="DCh-Cust/Mt" sap:quickinfo="Reference distrib.channel for cust.and material masters">
|
||
<Documentation>
|
||
<Summary>Specifies a distribution channel that you want to use as a reference for customer and material master data for other distribution channels.</Summary>
|
||
<LongDescription>You can specify one distribution channel as the source of customer and material master data for other distribution channels. You need then only to maintain the data in one place.Distrib.channel Ref.distrib.channel01 0102 0103 0104 04In this example, only distribution channels 01 and 04 have customer and material master data defined. Distribution channels 01, 02, and 03 share the master data that you defined for distribution channel 01. Distribution channel 04 has its own master data. When you create a sales order in distribution channel 03, the system checks the customer and material master data against the data defined for distribution channel 01.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Division" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Division" sap:heading="Dv">
|
||
<Documentation>
|
||
<Summary>A way of grouping materials, products, or services. The system uses divisions to determine the sales areas and the business areas for a material, product, or service.</Summary>
|
||
<LongDescription>A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DepartureCountry" Type="Edm.String" Nullable="false" MaxLength="3" sap:display-format="UpperCase" sap:label="Departure Ctry/Reg." sap:heading="DeCR" sap:quickinfo="Departure Country/Region (from which the goods are sent)">
|
||
<Documentation>
|
||
<Summary>Identifies the country or region in which the delivery originates.</Summary>
|
||
<LongDescription>You can define the country/region key in a table. As a rule, it is a good idea to use the existing international standards for identifying vehicles from different countries or regions (for example: USA = United States, I = Italy, and so on). The system uses the key to do the following:Help determine the relevant taxes during pricingDetermine important country or region-specific standards (the length of postal codes and bank account numbers, for example)</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerTaxCategory" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Tax Category" sap:heading="TxCat" sap:quickinfo="Tax category (sales tax, federal sales tax,...)">
|
||
<Documentation>
|
||
<Summary>Identifies the condition that the system uses to automatically determine country-specific taxes during pricing.</Summary>
|
||
<LongDescription>You can define one or more tax categories for each country. During sales order processing, the system applies the tax category according tothe geographical location of your delivering plant and the location of the customer receiving the goodstax classifications in the customer master record and the material master record.In the USA, for example, you can define tax categories for Federal Sales Tax and Federal Excise Tax. In the U.K., you can define a tax category for Value Added Tax (VAT).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerTaxClassification" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Tax Classification" sap:heading="TaxCl" sap:quickinfo="Tax classification for customer">
|
||
<Documentation>
|
||
<Summary>Specifies the tax liability of the customer, based on the tax structure of the customer's country.</Summary>
|
||
<LongDescription>You can use the tax classification to specify, for example, whether a customer is liable for sales taxes, such as VAT or state sales taxes.During sales order processing, the system copies the tax classification from the tax information stored in thecustomer master record of the payer, if the payer is different from the sold-to party and the sales tax identification number is maintained for the payer.ship to party, if the sales tax identification number of the ship-to party is maintained.sold-to party, if none of the criteria for the payer or the ship-to party are met.During pricing, the system calculates any relevant taxes by taking the following factors into account:The tax classification of the customer and the materialThe country keys of the customer and the delivering plant</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_CustomerSalesAreaTextType" sap:label="Customer Sales Area Text" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Customer"/>
|
||
<PropertyRef Name="SalesOrganization"/>
|
||
<PropertyRef Name="DistributionChannel"/>
|
||
<PropertyRef Name="Division"/>
|
||
<PropertyRef Name="Language"/>
|
||
<PropertyRef Name="LongTextID"/>
|
||
</Key>
|
||
<Property Name="Customer" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SalesOrganization" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Sales Organization" sap:heading="SOrg.">
|
||
<Documentation>
|
||
<Summary>An organizational unit responsible for the sale of certain products or services. The responsibility of a sales organization may include legal liability for products and customer claims.</Summary>
|
||
<LongDescription>You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DistributionChannel" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Distribution Channel" sap:heading="DChl">
|
||
<Documentation>
|
||
<Summary>The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.</Summary>
|
||
<LongDescription>You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Division" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Division" sap:heading="Dv">
|
||
<Documentation>
|
||
<Summary>A way of grouping materials, products, or services. The system uses divisions to determine the sales areas and the business areas for a material, product, or service.</Summary>
|
||
<LongDescription>A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Language" Type="Edm.String" Nullable="false" MaxLength="2" sap:label="Language" sap:heading="L" sap:quickinfo="Language key">
|
||
<Documentation>
|
||
<Summary>The language key is an abbreviation for the language of the object being processed (for example, standard text, form, style).</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LongTextID" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Text ID" sap:heading="ID">
|
||
<Documentation>
|
||
<Summary>The text ID defines the various types of texts related to a text object. For example, the object "TEXT" (standard texts) can have the following text IDs:</Summary>
|
||
<LongDescription>ST for user-specific standard texts (individual texts)SYST for cross-application system textsvarious IDs for specific application departments. You must have the appropriate access authorization in order to access these texts.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LongText" Type="Edm.String" sap:label="String" sap:sortable="false" sap:filterable="false"/>
|
||
</EntityType>
|
||
<EntityType Name="A_CustomerTaxGroupingType" sap:label="Customer Tax Grouping" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Customer"/>
|
||
<PropertyRef Name="CustomerTaxGroupingCode"/>
|
||
</Key>
|
||
<Property Name="Customer" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustomerTaxGroupingCode" Type="Edm.String" Nullable="false" MaxLength="3" sap:display-format="UpperCase" sap:label="Tax Category" sap:heading="TC" sap:quickinfo="Category Indicator for Tax Codes">
|
||
<Documentation>
|
||
<Summary>This indicator is used to allocate customers and vendors to different tax categories. The system evaluates this information during document entry to assist users in selecting the tax code.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustTaxGrpExemptionCertificate" Type="Edm.String" MaxLength="15" sap:display-format="UpperCase" sap:label="Exempt. Number" sap:quickinfo="Number of exemption certificate">
|
||
<Documentation>
|
||
<Summary>The exemption information are displayed while posting a document to help the user find the correct tax code. If the posting date lies within an exemption interval the corresponding tax category will be highlighted.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustTaxGroupExemptionRate" Type="Edm.Decimal" Precision="5" Scale="2" sap:label="Exemption Rate" sap:heading="Exmpt.%" sap:quickinfo="Exemption rate">
|
||
<Documentation>
|
||
<Summary>Tax categories</Summary>
|
||
<LongDescription>The exemption information is used by the system to help the user find the correct tax code while posting a document.The system will not apply the exemption rate to a tax amount previously calculated. This has to be done by defining a special tax code with a reduced percentage rate.Withholding taxThe exemption percentage is applied to the calculated withholding tax amount.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustTaxGroupExemptionStartDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Exempted from" sap:heading="Exmp.fr." sap:quickinfo="Start date of exemption"/>
|
||
<Property Name="CustTaxGroupExemptionEndDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Exempted until" sap:heading="Ex.until" sap:quickinfo="End date of exemption"/>
|
||
<Property Name="CustTaxGroupSubjectedStartDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="subjected from" sap:heading="subj. from" sap:quickinfo="Subjected from">
|
||
<Documentation>
|
||
<Summary>This field gives the start date of the status of being subjected.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CustTaxGroupSubjectedEndDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="subjected until" sap:heading="subj.until" sap:quickinfo="Subjected until">
|
||
<Documentation>
|
||
<Summary>This field gives the end date of the status of being subjected.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_CustomerTextType" sap:label="Customer Text" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Customer"/>
|
||
<PropertyRef Name="Language"/>
|
||
<PropertyRef Name="LongTextID"/>
|
||
</Key>
|
||
<Property Name="Customer" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Language" Type="Edm.String" Nullable="false" MaxLength="2" sap:label="Language" sap:heading="L" sap:quickinfo="Language key">
|
||
<Documentation>
|
||
<Summary>The language key is an abbreviation for the language of the object being processed (for example, standard text, form, style).</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LongTextID" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Text ID" sap:heading="ID">
|
||
<Documentation>
|
||
<Summary>The text ID defines the various types of texts related to a text object. For example, the object "TEXT" (standard texts) can have the following text IDs:</Summary>
|
||
<LongDescription>ST for user-specific standard texts (individual texts)SYST for cross-application system textsvarious IDs for specific application departments. You must have the appropriate access authorization in order to access these texts.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LongText" Type="Edm.String" sap:label="String" sap:sortable="false" sap:filterable="false"/>
|
||
</EntityType>
|
||
<EntityType Name="A_CustomerWithHoldingTaxType" sap:label="Withholding Tax" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Customer"/>
|
||
<PropertyRef Name="CompanyCode"/>
|
||
<PropertyRef Name="WithholdingTaxType"/>
|
||
</Key>
|
||
<Property Name="Customer" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number">
|
||
<Documentation>
|
||
<Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CompanyCode" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Company Code" sap:heading="CoCd">
|
||
<Documentation>
|
||
<Summary>The company code is an organizational unit within financial accounting.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="WithholdingTaxType" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Withholding Tax Type" sap:heading="Withhld tax type" sap:quickinfo="Indicator for Withholding Tax Type">
|
||
<Documentation>
|
||
<Summary>This indicator is used to classify the different types of withholding tax.</Summary>
|
||
<LongDescription>Withholding tax types classify particular features of a withholding tax including:The time at which the withholding tax is postedThe basis on which the base amount is calculatedThe basis for accumulation (if applicable)Withholding tax types are to be distinguished from withholding tax codes, to which are allocated the withholding tax percentage rate example.Whether a withholding tax can be defined as an existing type by means of a new code, or if a new type needs to be defined will depend on the type of transaction (see below).Note that a business transaction can only be assigned one withholding tax code per withholding tax type. If the business transaction is subject to several withholding taxes simultaneously, these must be represented by different types.This is the case in Argentina for example, where up to four kinds of withholding tax per business transaction are possible.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="WithholdingTaxCode" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="W/Tax Code" sap:heading="WTx" sap:quickinfo="Withholding Tax Code">
|
||
<Documentation>
|
||
<Summary>One or more "withholding tax codes" are assigned to each withholding tax type. One of the things these codes determine is the various percentage rates for the withholding tax type.</Summary>
|
||
<LongDescription>Note that when processing a business transaction, no more than one withholding tax code can be assigned per withholding tax type. If the business transaction is subject to more than one withholding taxes, these must be represented in the system by defining various withholding tax types.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="WithholdingTaxAgent" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="WTax Agent" sap:heading="WT Agent" sap:quickinfo="Indicator: Withholding Tax Agent?"/>
|
||
<Property Name="ObligationDateBegin" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="W/Tax Obligated Frm" sap:heading="Oblig. Frm" sap:quickinfo="Obligated to Withhold Tax From">
|
||
<Documentation>
|
||
<Summary>Date from which:</Summary>
|
||
<LongDescription>The company code is obligated to withhold tax for the given withholding tax type.This date must be entered in Customizing under the withholding tax information for the company code.The customer is obligated to withhold tax for the withholding tax type.This date must be defined in the customer master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ObligationDateEnd" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Oblig.to W/Tax Until" sap:heading="With.Until" sap:quickinfo="Obligated to Withhold Tax Until">
|
||
<Documentation>
|
||
<Summary>Date to which:</Summary>
|
||
<LongDescription>The company code is obligated to withhold tax for the withholding tax type.This date must be entered in Customizing under the withholding tax information for the company code.The customer is obigated to withhold tax for the withholding tax type.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="WithholdingTaxNumber" Type="Edm.String" MaxLength="16" sap:display-format="UpperCase" sap:label="W/tax number" sap:heading="W/TxID" sap:quickinfo="Withholding tax identification number">
|
||
<Documentation>
|
||
<Summary>This is a number issued by the tax authorities per withholding tax type.</Summary>
|
||
<LongDescription>This number must be specified in Customizing either:(a) As part of the withholding tax information defined for the company code, or(b) As part of the withholding tax information defined in the customer or vendor master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="WithholdingTaxCertificate" Type="Edm.String" MaxLength="25" sap:display-format="UpperCase" sap:label="Exemption Number" sap:heading="Exem. No." sap:quickinfo="Exemption Certificate Number">
|
||
<Documentation>
|
||
<Summary>Numbered assigned by the relevant authorities for exemption from withholding tax.</Summary>
|
||
<LongDescription>This number must be entered in the system as follows:In the vendor master record in the case of vendorsFor customers, in Customizing under the settings for withholding tax information for the company code per withholding tax type.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="WithholdingTaxExmptPercent" Type="Edm.Decimal" Precision="5" Scale="2" sap:label="Exemption Rate" sap:heading="Exem.%">
|
||
<Documentation>
|
||
<Summary>Rate of exemption from withholding tax.</Summary>
|
||
<LongDescription>Those persons/activities subject to withholding tax can be exempted from withholding tax up to the percentage rate you enter here. This exemption rate refers to the withholding tax amount itself and not to the whole amount liable to withholding tax (withholding tax base amount).The gross amount of an invoice is 100.00 and the withholding tax base amount is defined as gross. The withholding tax rate is 10% meaning that the withholding tax amount is 10.00. Given an exemption rate of 30%, the withholding tax amount is reduced to 7.00.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ExemptionDateBegin" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Exemption Start Date" sap:heading="Exempt Fr." sap:quickinfo="Date on Which Exemption Begins">
|
||
<Documentation>
|
||
<Summary>Date from which withholding tax exemption applies.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ExemptionDateEnd" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Exemption End Date" sap:heading="Exempt To" sap:quickinfo="Date on Which Exemption Ends">
|
||
<Documentation>
|
||
<Summary>Date on which withholding tax exemption expires.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ExemptionReason" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Exemption Reason" sap:heading="Exmpt.Resn" sap:quickinfo="Reason for Exemption">
|
||
<Documentation>
|
||
<Summary>Indicator used to classify different types of exemption from liability to a particular withholding tax.</Summary>
|
||
<LongDescription>These indicators can be defined per withholding tax type in the vendor master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization" sap:heading="AuGr" sap:quickinfo="Authorization Group">
|
||
<Documentation>
|
||
<Summary>The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_CustSalesPartnerFuncType" sap:label="Sales Partner Functions" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Customer"/>
|
||
<PropertyRef Name="SalesOrganization"/>
|
||
<PropertyRef Name="DistributionChannel"/>
|
||
<PropertyRef Name="Division"/>
|
||
<PropertyRef Name="PartnerCounter"/>
|
||
<PropertyRef Name="PartnerFunction"/>
|
||
</Key>
|
||
<Property Name="Customer" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number">
|
||
<Documentation>
|
||
<Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SalesOrganization" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Sales Organization" sap:heading="SOrg.">
|
||
<Documentation>
|
||
<Summary>An organizational unit responsible for the sale of certain products or services. The responsibility of a sales organization may include legal liability for products and customer claims.</Summary>
|
||
<LongDescription>You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DistributionChannel" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Distribution Channel" sap:heading="DChl">
|
||
<Documentation>
|
||
<Summary>The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.</Summary>
|
||
<LongDescription>You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Division" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Division" sap:heading="Dv">
|
||
<Documentation>
|
||
<Summary>A way of grouping materials, products, or services. The system uses divisions to determine the sales areas and the business areas for a material, product, or service.</Summary>
|
||
<LongDescription>A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PartnerCounter" Type="Edm.String" Nullable="false" MaxLength="3" sap:display-format="NonNegative" sap:label="Partner counter" sap:heading="ParC">
|
||
<Documentation>
|
||
<Summary>The sequential number that the system applies when there is more than one partner for a particular partner function.</Summary>
|
||
<LongDescription>When you create a sales order for a particular customer, there may be more than one ship-to party defined. The different ship-to parties are numbered sequentially.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PartnerFunction" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Partner Function" sap:heading="Funct">
|
||
<Documentation>
|
||
<Summary>The abbreviated form of the name that identifies the partner function.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BPCustomerNumber" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer number of business partner"/>
|
||
<Property Name="CustomerPartnerDescription" Type="Edm.String" MaxLength="30" sap:label="Partner Description" sap:heading="Part" sap:quickinfo="Cust.-Specif. Descr. of Business Partner (Plant, Stor. Loc.)">
|
||
<Documentation>
|
||
<Summary>Sold-to party number sent in by the customer in delivery schedules.</Summary>
|
||
<LongDescription>The system uses this number to automatically determine the ship-to party.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DefaultPartner" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Default Partner" sap:heading="D">
|
||
<Documentation>
|
||
<Summary>Specifies a partner as the default for a particular partner function.</Summary>
|
||
<LongDescription>When you enter more than one partner for a particular partner function (for example, you define three different ship-to parties), you can select one partner as the default. During sales or purchasing processing, if you have defined multiple partners for a partner function, the system prompts you to choose just one partner. The system presents the default partner as the first choice in the pop-up window.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Supplier" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Supplier" sap:quickinfo="Account Number of Supplier">
|
||
<Documentation>
|
||
<Summary>Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PersonnelNumber" Type="Edm.String" MaxLength="8" sap:display-format="NonNegative" sap:label="Personnel Number" sap:heading="Pers.No.">
|
||
<Documentation>
|
||
<Summary>The personnel number is the only feature within a client which is unique to an employee. You have to enter a personnel number before you can display and maintain an employee's master data and time data.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ContactPerson" Type="Edm.String" MaxLength="10" sap:display-format="NonNegative" sap:label="Contact Person" sap:heading="Partner" sap:quickinfo="Number of Contact Person">
|
||
<Documentation>
|
||
<Summary>The number that uniquely identifies the contact person.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization" sap:heading="AuGr" sap:quickinfo="Authorization Group">
|
||
<Documentation>
|
||
<Summary>The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_SupplierType" sap:label="Supplier" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Supplier"/>
|
||
</Key>
|
||
<Property Name="Supplier" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Supplier" sap:quickinfo="Account Number of Supplier">
|
||
<Documentation>
|
||
<Summary>Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AlternativePayeeAccountNumber" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Alternative Payee" sap:heading="Alt. Payee" sap:quickinfo="Account Number of the Alternative Payee">
|
||
<Documentation>
|
||
<Summary>The account number of the vendor with whom automatic payment transactions are carried out.</Summary>
|
||
<LongDescription>The field is only needed if payments are not to be made directly to the vendor to whom the payable is owed. The same applies to bank collections of receivables.The specification in this field applies to all company codes. There is a further field in which every company code can enter an alternative payee separately. If both fields are filled, the company code specification has priority.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization" sap:heading="AuGr" sap:quickinfo="Authorization Group">
|
||
<Documentation>
|
||
<Summary>The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CreatedByUser" Type="Edm.String" MaxLength="12" sap:display-format="UpperCase" sap:label="Created by" sap:quickinfo="Name of Person who Created the Object" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Name with which the user who entered the master record was logged on in the R/3 System.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CreationDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Created on" sap:heading="Date" sap:quickinfo="Date on which the Record Was Created" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Date on which the master record, or the part of the master record being viewed, was created.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Customer" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Customer" sap:quickinfo="Customer Number">
|
||
<Documentation>
|
||
<Summary>Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PaymentIsBlockedForSupplier" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Payment block" sap:quickinfo="Payment Block"/>
|
||
<Property Name="PostingIsBlocked" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Posting Block" sap:heading="B" sap:quickinfo="Central Posting Block">
|
||
<Documentation>
|
||
<Summary>Indicates that the account is blocked for posting for all company codes.</Summary>
|
||
<LongDescription>If you set this indicator, the system prevents users from posting items to this account and issues an error message to inform them that the account is blocked.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PurchasingIsBlocked" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Purch. block" sap:heading="B" sap:quickinfo="Centrally imposed purchasing block">
|
||
<Documentation>
|
||
<Summary>Indicates whether or not the supplier master record is blocked for all departments (that is, whether or not posting to this record is allowed at all).</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierAccountGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Account Group" sap:heading="Group" sap:quickinfo="Supplier Account Group">
|
||
<Documentation>
|
||
<Summary>The account group is a classifying feature within vendor master records. The account group determines:</Summary>
|
||
<LongDescription>the number interval for the account number of the vendor,whether the number is assigned by the user or by the system,which specifications are necessary and/or possible in the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierFullName" Type="Edm.String" MaxLength="220" sap:display-format="UpperCase" sap:label="Supplier Name" sap:quickinfo="Supplier Full Name" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="SupplierName" Type="Edm.String" MaxLength="80" sap:label="Name of Supplier" sap:heading="Supplier" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="VATRegistration" Type="Edm.String" MaxLength="20" sap:display-format="UpperCase" sap:label="VAT Registration No." sap:quickinfo="VAT Registration Number">
|
||
<Documentation>
|
||
<Summary>VAT registration number (VAT reg.no.) of the customer, vendor or your company code.</Summary>
|
||
<LongDescription>The VAT registration number is used within the EU for tax-exempt deliveries for the "EC sales list". The check rules are defined for each EU country and cannot be changed.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BirthDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Date of Birth" sap:heading="Birth Date" sap:quickinfo="Date of Birth of the Person Subject to Withholding Tax"/>
|
||
<Property Name="ConcatenatedInternationalLocNo" Type="Edm.String" MaxLength="20" sap:label="Int. Location No." sap:heading="International Location Number" sap:quickinfo="Cocatenated International Location Number" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="DeletionIndicator" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Deletion flag" sap:heading="DelF" sap:quickinfo="Central Deletion Flag for Master Record">
|
||
<Documentation>
|
||
<Summary>Indicates that all data in this master record is to be deleted.</Summary>
|
||
<LongDescription>To delete this data, you have to run the archiving program for Accounts Receivable or Payable. This program will archive all master records marked for deletion provided that there is no dependent data in them.Deletion flags can also be used in the program for deleting master data. You should, however, run this program only to delete test data prior to production startup.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="FiscalAddress" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Fiscal address" sap:heading="Fisc.addr." sap:quickinfo="Account number of the master record with fiscal address">
|
||
<Documentation>
|
||
<Summary>Specifies an additional master record in which the official address is stored.</Summary>
|
||
<LongDescription>This address is used in Italy for business transactions with the tax office in Italy.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Industry" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Industry" sap:heading="Indus." sap:quickinfo="Industry key" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>An industry is a distinct group of companies with the same basic business activity. The industry key is used in selecting data for evaluations (for example, a vendor master data list). You can specify industries such as trade, banking, service, manufacturing, health care, public service, media and so on.</Summary>
|
||
<LongDescription>The industry field belongs to the general data area of customer and vendor master records.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InternationalLocationNumber1" Type="Edm.String" MaxLength="7" sap:display-format="NonNegative" sap:label="Int. location no. 1" sap:heading="ILN 1" sap:quickinfo="International location number (part 1)">
|
||
<Documentation>
|
||
<Summary>Here you enter the first 7 digits of the international location number.</Summary>
|
||
<LongDescription>The International Location Number (ILN) is assigned (in Germany by the Centrale for Coorganisation GmbH)) when a company is founded. It consists of 13 digits, the last digit being the check digit. There are two categories of location numbers:Participants who only need an ILN to cleary and unmistakably identify themselves for communication with the business partner are given a category 1 ILN. This cannot be used to identify articles by means of EAN.Participants who wish to assign the location numbers for their own enterprise areas are given a category 2 ILN. For a category 2 ILN, digits 1 to 7 are described as basis number. This is used as basis for the creation of article numbers (EAN).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InternationalLocationNumber2" Type="Edm.String" MaxLength="5" sap:display-format="NonNegative" sap:label="Int. location no. 2" sap:heading="ILN 2" sap:quickinfo="International location number (Part 2)">
|
||
<Documentation>
|
||
<Summary>Here, you enter digits 8-12 of the 13-digit international location number.</Summary>
|
||
<LongDescription>The international location number (ILN) is assigned when establishing a company (by the "Zentrale für Coorganisation GmbH" in Germany). It consists of 13 digits, the last of which is the check digit. There are two types of international location numbers:Subscribers who only need one ILN to identify themselves in communication with the business partner are given an ILN of type 1. These cannot be used for identifying articles by means of EAN.Subscribers who need to assign location numbers for their own company areas are given an ILN of type 2. Positions 1 through 7 of the ILN type 2 are known as the basis number. This basis number forms the basis for article numbers (EAN).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InternationalLocationNumber3" Type="Edm.String" MaxLength="1" sap:display-format="NonNegative" sap:label="Check digit" sap:quickinfo="Check digit for the international location number">
|
||
<Documentation>
|
||
<Summary>The check digit is derived from a special check digit procedure from digits of the previous international location numbers. In this way, you can check whether the ILN entered is actually valid.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IsNaturalPerson" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Natural Person">
|
||
<Documentation>
|
||
<Summary>Denotes a natural person.</Summary>
|
||
<LongDescription>In the following countries, the system needs to know whether the taxpayer is a legal or natural person so that it can check the tax numbers correctly:BrazilBulgariaColombiaCroatiaGreeceItalyMexicoPeruSloveniaThailandUkraineThe flag is also used in conjunction with the Statement of Payments to Natural Persons report, as used in the Czech Republic and in Slovakia. This report only covers customers and vendors for whom you have set this indicator.In South Korea, it is used in conjunction with the Generic Withholding Tax Reporting program.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ResponsibleType" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Tax type">
|
||
<Documentation>
|
||
<Summary>Classification of companies according to tax aspects.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SuplrQltyInProcmtCertfnValidTo" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="QM System Valid To" sap:heading="Dat" sap:quickinfo="Validity date of certification">
|
||
<Documentation>
|
||
<Summary>Date up to which the certification of the QM-system is valid.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SuplrQualityManagementSystem" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Actual QM System" sap:quickinfo="Supplier's QM System">
|
||
<Documentation>
|
||
<Summary>If a QM system is maintained by the supplier, you can store a description of the QM system here.</Summary>
|
||
<LongDescription>If a material is activated for QM in procurement, the system initiates the following check whenever purchasing functions are carried out (for example, when a request for a quotation is made or if a purchase order is created):Whether the supplier's verified QM system, according to supplier master record or quality info record (for a combination of supplier/material) meets the requirements for QM systems as specified in the material master.When carrying out the check, the system relies on the defined assignments for target QM systems and actual QM systems in the Customizing application. When carrying out the check, the system relies on the assignments for target QM systems and actual QM systems defined in the configuration.If the check is unsuccessful, a warning message is issued when a request for quotation is initiated and an error message is issued for all other procurement activities.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierCorporateGroup" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Group Key" sap:heading="Group">
|
||
<Documentation>
|
||
<Summary>If the customer or the vendor belongs to a group, you can enter a group key here. The group key is freely assignable.</Summary>
|
||
<LongDescription>If you create a matchcode using this group key, group evaluations are possible.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierProcurementBlock" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Block Function" sap:heading="BF" sap:quickinfo="Function That Will Be Blocked">
|
||
<Documentation>
|
||
<Summary>Key that determines which procurement functions (for example, request for quotation, purchase order, or goods receipt) should be blocked for quality reasons.</Summary>
|
||
<LongDescription>You can enter a block key in the:Supplier master recordIn this case, the supplier block applies to all materials and plants.Quality info record for QM in procurementIn this case, the supplier block applies to a single material and plant.A block for quality reasons applies only to those materials for which QM in procurement is active.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxNumber1" Type="Edm.String" MaxLength="16" sap:display-format="UpperCase" sap:label="Tax Number 1" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Specifies the tax number.</Summary>
|
||
<LongDescription>Enter the appropriate tax number:Country/Region Tax NumberArgentina CUIT number or CUIL numberBelgium Enterprise numberBrazil CNPJ numberBulgaria Unified identification codeChile RUT numberChina VAT registration number (shui wu deng ji hao)Colombia NIT numberCroatia Legal persons: company identification numberNatural persons: JMBG numberCzech Republic DIC numberFrance SIRET numberGreece Personal IDHungary Tax numberItaly Fiscal codeKazakhstan RNN (obsolete)Mexico RFC numberNetherlands SI registration number (Aansluitnummer UWV) of chain- liability vendorNorway VAT numberPeru RUC numberPhilippines Taxpayer identification number (see below)Poland NIP numberPortugal NIF numberRomania Tax numberRussia INNSlovakia DIC numberSlovenia Tax numberSouth Korea Natural persons: Personal identification numberLegal persons: Corporation IDSpain NIF numberSwitzerland UID numberTaiwan GUI registration numberThailand Personal IDTurkey Name of business partner's tax officeUkraine Taxpayer identification numberUnited Kingdom Company registration numberUnited States Social security numberVenezuela RIF numberIn the Philippines, enter the taxpayer identification number with a V or N at the end, as follows:If the business partner is liable to VAT: 999-999-999-999VIf the business partner is not liable to VAT: 999-999-999-999N</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxNumber2" Type="Edm.String" MaxLength="11" sap:display-format="UpperCase" sap:label="Tax Number 2" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Specifies the tax number.</Summary>
|
||
<LongDescription>Enter the appropriate tax number:Country/Region Tax NumberArgentina NIP number or CM numberBelgium VAT numberBrazil CPF numberBulgaria Legal persons: tax numberNatural persons: personal IDCroatia OIB number Czech Republic ICO numberFrance SIREN numberGreece AFM numberIndia TINItaly VAT numberKazakhstan BC (Beneficiary Code)Netherlands BSN numberNorway Organization registration numberRussia OKPO codeSlovakia ICO numberSouth Korea VAT registration numberSweden Organization registration numberSwitzerland VAT numberTaiwan Tax registration numberUkraine Legal persons: USREOU numberNatural persons: SRNP numberTurkey Tax numberUnited Kingdom NI numberUnited States Employer identification numberVenezuela NIT number</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxNumber3" Type="Edm.String" MaxLength="18" sap:display-format="UpperCase" sap:label="Tax Number 3" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Specifies the tax number.</Summary>
|
||
<LongDescription>Enter the tax number that applies:Country Tax numberArgentina Withholding agent numberBrazil State tax numberBulgaria Social security numberMexico CURP numberKazakhstan BINNetherlands Tax registration number (Loonbelastingnummer) of the chain-liability vendorRussia KPP numberThailand Tax ID Ukraine VAT registration number</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxNumber4" Type="Edm.String" MaxLength="18" sap:display-format="UpperCase" sap:label="Tax Number 4" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Specifies the tax number.</Summary>
|
||
<LongDescription>Enter the appropriate tax number:Country Tax NumberBrazil Municipal tax numberKazakhstan IINRussia OFK number (for public bodies only)</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxNumber5" Type="Edm.String" MaxLength="60" sap:display-format="UpperCase" sap:label="Tax Number 5" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Kazakhstan</Summary>
|
||
<LongDescription>Specifies the certificate of registration as VAT payer in the following format: XXXXXYYYYYYYZZZZZZZZ, where: XXXXX is the certificate serial number, YYYYYYY is the certificate number and ZZZZZZZZ is the date of certificate issue.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxNumberResponsible" Type="Edm.String" MaxLength="18" sap:display-format="UpperCase" sap:label="Tax Number" sap:quickinfo="Tax Number at Responsible Tax Authority">
|
||
<Documentation>
|
||
<Summary>The tax number of the vendor at the responsible tax authority.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="TaxNumberType" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Tax Number Type" sap:heading="Tax No.Ty.">
|
||
<Documentation>
|
||
<Summary>Taxes in Argentina:</Summary>
|
||
<LongDescription>The format and the check of tax number 1 depend on the two-digit tax number type.The tax number type is an identification type for tax in Argentina (for example, 80 for CUIT) and is used for the DGI tax report.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SuplrProofOfDelivRlvtCode" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Relevant for POD" sap:heading="POD-Rel." sap:quickinfo="Supplier indicator relevant for proof of delivery">
|
||
<Documentation>
|
||
<Summary>This indicator controls the process of proof of delivery during the incoming goods process for inbound deliveries. Processing is activating by switching on this indicator in the supplier master and by switching on the corresponding indicator in the delivery item category.</Summary>
|
||
<LongDescription>There are the following different characteristics:' ': not relevant for POD'A': generally relevant for POD'B': only relevant for POD if differences(Difference between notified quantity and actual quantity received)</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BR_TaxIsSplit" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Tax split" sap:heading="S" sap:quickinfo="Tax Split">
|
||
<Documentation>
|
||
<Summary>Tax calculation for Brazil:</Summary>
|
||
<LongDescription>The IPI tax value is split up for this vendor. 50% of the calculated IPI tax value is posted as deductible input tax, 50% is deducted from the inventory posting or posting to expense account.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<NavigationProperty Name="to_SupplierCompany" Relationship="API_BUSINESS_PARTNER.assoc_138939C49DA3F66FEE8C74425F390DD3" FromRole="FromRole_assoc_138939C49DA3F66FEE8C74425F390DD3" ToRole="ToRole_assoc_138939C49DA3F66FEE8C74425F390DD3"/>
|
||
<NavigationProperty Name="to_SupplierPurchasingOrg" Relationship="API_BUSINESS_PARTNER.assoc_B2EAAC3147A4639C17A2CFEACA07BE23" FromRole="FromRole_assoc_B2EAAC3147A4639C17A2CFEACA07BE23" ToRole="ToRole_assoc_B2EAAC3147A4639C17A2CFEACA07BE23"/>
|
||
<NavigationProperty Name="to_SupplierText" Relationship="API_BUSINESS_PARTNER.assoc_A47744B1176D2172C3109B5E43FFC7F9" FromRole="FromRole_assoc_A47744B1176D2172C3109B5E43FFC7F9" ToRole="ToRole_assoc_A47744B1176D2172C3109B5E43FFC7F9"/>
|
||
</EntityType>
|
||
<EntityType Name="A_SupplierCompanyType" sap:label="Supplier Company" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Supplier"/>
|
||
<PropertyRef Name="CompanyCode"/>
|
||
</Key>
|
||
<Property Name="Supplier" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Supplier" sap:quickinfo="Account Number of Supplier">
|
||
<Documentation>
|
||
<Summary>Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CompanyCode" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Company Code" sap:heading="CoCd">
|
||
<Documentation>
|
||
<Summary>The company code is an organizational unit within financial accounting.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization" sap:heading="AuGr" sap:quickinfo="Authorization Group">
|
||
<Documentation>
|
||
<Summary>The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CompanyCodeName" Type="Edm.String" MaxLength="25" sap:label="Company Name" sap:quickinfo="Name of Company Code or Company" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="PaymentBlockingReason" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Payment Block" sap:heading="Block Ind." sap:quickinfo="Block Key for Payment">
|
||
<Documentation>
|
||
<Summary>Block key (enqueue key) that is used to block an open item or an account to payment transactions.</Summary>
|
||
<LongDescription>You can use the block key as described below.Automatic Payment TransactionsIn automatic payment transactions, the block takes effect when it is entered in the system as follows:In the master recordIn the documentIf you enter the block in the master record then all open items for this account are contained in the exception list.The following block keys have a special meaning in the master record:The block key * has the effect that all items of the account are skipped in automatic payment transactions.The block key + has the effect that all items are skipped in which a payment method was not entered explicitly.The block key A is always set automatically when a down payment is entered. Therefore, you must not delete the block key A or use it for other purposes.Whether a block key can be set or removed in payment proposal processing depends on the attribute Changeable in payment proposal of the block key.Manual PaymentsManual payments are only affected by a block key in the document if you set the attribute Blocked for manual payments in the block key.A block key that was set in the master record does not have any effect on manual payments. You can have the system issue a warning message in that case. To do so, you have to make system settings. Set up message 671 of work area F5 in the configuration step Change Message Control, udter Finance -> Localization -> General Settings.Release for PaymentIf you want to use a block key for payment release in accounting, then you have to set the attribute Not Changeable for the block key. You make this setting in the configuration step Control Payment Block Reasons, under Finance -> Accounts Payable -> General Payment Settings.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierIsBlockedForPosting" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Co.code post.block" sap:heading="B" sap:quickinfo="Posting block for company code">
|
||
<Documentation>
|
||
<Summary>Indicates that the account is blocked for posting in the specified company code.</Summary>
|
||
<LongDescription>If you set this indicator, the system prevents users from posting items to this account and issues an error message to inform them that the account is blocked.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AccountingClerk" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Clerk Abbrev." sap:quickinfo="Accounting Clerk Abbreviation">
|
||
<Documentation>
|
||
<Summary>Identification code for the accounting clerk.</Summary>
|
||
<LongDescription>The name of the accounting clerk defined by this identification code can be used in the payment program for correspondence and reporting (for example, open item lists).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AccountingClerkFaxNumber" Type="Edm.String" MaxLength="31" sap:label="Acctg clerk's fax" sap:heading="Accounting clerk's fax" sap:quickinfo="Accounting clerk's fax number at the customer/vendor"/>
|
||
<Property Name="AccountingClerkPhoneNumber" Type="Edm.String" MaxLength="30" sap:display-format="UpperCase" sap:label="Acct.clerks tel.no." sap:heading="Accting clerk's telephone no." sap:quickinfo="Accounting clerk's telephone number at business partner"/>
|
||
<Property Name="SupplierClerk" Type="Edm.String" MaxLength="15" sap:label="Clerk at vendor">
|
||
<Documentation>
|
||
<Summary>Name or identification code of the accounting clerk at the vendor.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierClerkURL" Type="Edm.String" MaxLength="130" sap:label="Clrk's internet add." sap:heading="Clerk's internet address" sap:quickinfo="Internet address of partner company clerk"/>
|
||
<Property Name="PaymentMethodsList" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Payment Methods" sap:heading="Methods" sap:quickinfo="List of Respected Payment Methods">
|
||
<Documentation>
|
||
<Summary>List of payment methods which may be used in automatic payment transactions with this customer/vendor if you do not specify a payment method in the item to be paid.</Summary>
|
||
<LongDescription>If you do specify a particular payment method in the item to be paid, this specification has priority over the specifications in the master record. You may also specify payment methods in the item which are not listed in the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PaymentTerms" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Terms of Payment" sap:heading="PayT" sap:quickinfo="Terms of Payment Key">
|
||
<Documentation>
|
||
<Summary>Key for defining payment terms composed of cash discount percentages and payment periods.</Summary>
|
||
<LongDescription>It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ClearCustomerSupplier" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Clearing with cust." sap:quickinfo="Indicator: Clearing between customer and vendor?">
|
||
<Documentation>
|
||
<Summary>Indicates that during automatic payment transactions, clearing is made with the corresponding customer account, and that during manual clearing procedures, the items of that customer account are also selected.</Summary>
|
||
<LongDescription>To use this function in automatic payment transactions, you have toenter the customer account number in the vendor master record,enter the vendor account number in the customer master record, andselect the "Clearing with vendor" indicator in the customer master record.If this indicator is set, items belonging to the customer account will be included in any dunning run.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IsToBeLocallyProcessed" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Local Processing" sap:quickinfo="Indicator: Local Processing?">
|
||
<Documentation>
|
||
<Summary>Indicates that payment transactions and dunning notices are created for the branch.</Summary>
|
||
<LongDescription>Normally automatic payment transactions and dunning notices are created for the head office.NoteSelect this indicator only if this account is a head office account.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ItemIsToBePaidSeparately" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Individual Payment" sap:quickinfo="Indicator: Pay All Items Separately?">
|
||
<Documentation>
|
||
<Summary>If this indicator is set, every customer/vendor open item is paid separately during automatic payment transactions. This means that open items are not grouped together for payment.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PaymentIsToBeSentByEDI" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Pmnt advice by EDI" sap:heading="EDI" sap:quickinfo="Indicator: Send Payment Advices by EDI">
|
||
<Documentation>
|
||
<Summary>This indicator specifies that the customer/vendor should be sent all payment advice information by EDI.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="HouseBank" Type="Edm.String" MaxLength="5" sap:display-format="UpperCase" sap:label="House Bank" sap:heading="House Bk" sap:quickinfo="Short Key for a House Bank">
|
||
<Documentation>
|
||
<Summary>All bank data is determined using this key.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CheckPaidDurationInDays" Type="Edm.Decimal" Precision="3" Scale="0" sap:label="Check Cashing Time" sap:heading="GrP" sap:quickinfo="Probable Time Until Check Is Paid">
|
||
<Documentation>
|
||
<Summary>Number of days which usually pass until the vendor has cashed your check.</Summary>
|
||
<LongDescription>During automatic payment transactions, the system calculates the value date for check payments using this information and stores the date in the line item. The date is calculated as follows:Value date = posting date + check cashing timeIn Cash Management, the value date is used as information about the expected cash outflow.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Currency" Type="Edm.String" MaxLength="5" sap:label="Currency" sap:heading="Crcy" sap:quickinfo="Currency Key" sap:semantics="currency-code">
|
||
<Documentation>
|
||
<Summary>Currency key for amounts in the system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="BillOfExchLmtAmtInCoCodeCrcy" Type="Edm.Decimal" Precision="14" Scale="3" sap:unit="Currency" sap:label="Bill/Ex. Limit" sap:quickinfo="Bill of Exchange Limit (in Local Currency)">
|
||
<Documentation>
|
||
<Summary>Maximum amount which may be issued on a bill of exchange if it is to be used in payment transactions with the business partner.</Summary>
|
||
<LongDescription>The amount limit is taken into consideration in automatic payment transactions for payments by bill of exchange and bill of exchange payment requests. Several bill of exchange forms are created if the amount to be settled is higher than the maximum amount given here. Each of these bills of exchange is issued for the maximum amount or for a smaller amount.Amount limits for bills of exchange are used in Spain, for example.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierClerkIDBySupplier" Type="Edm.String" MaxLength="12" sap:display-format="UpperCase" sap:label="Account with vendor" sap:heading="Acct w/ vndr" sap:quickinfo="Our account number with the vendor">
|
||
<Documentation>
|
||
<Summary>This field contains the account number the company is listed under at the vendor.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ReconciliationAccount" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Reconciliation Acct" sap:heading="Recon.Acct" sap:quickinfo="Reconciliation Account in General Ledger">
|
||
<Documentation>
|
||
<Summary>The reconciliation account in G/L accounting is the account which is updated parallel to the subledger account for normal postings (for example, invoice or payment).</Summary>
|
||
<LongDescription>For special postings (for example, down payment or bill of exchange), this account is replaced by another account (for example, 'down payments received' instead of 'receivables').The replacement takes place due to the special G/L indicator which you must specify for these types of postings.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InterestCalculationCode" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Interest indicator" sap:heading="Interest Indicator" sap:quickinfo="Interest Indicator">
|
||
<Documentation>
|
||
<Summary>You enter an interest indicator here if you want the business partner to be included in automatic interest calculation.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InterestCalculationDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Last Key Date" sap:heading="Key Date Lst Int.Calc" sap:quickinfo="Key Date of Last Interest Calculation">
|
||
<Documentation>
|
||
<Summary>The date in this field displays the last time the interest calculation program processed this account. This is generally the upper limit of the last interest run.</Summary>
|
||
<LongDescription>Generally, this date is automatically maintained by the program (batch input). A manual entry in this field should only be made if an error has occurred or when implementing the interest calculation.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IntrstCalcFrequencyInMonths" Type="Edm.String" MaxLength="2" sap:display-format="NonNegative" sap:label="Int.Calc.Freq." sap:heading="Interest Calc. Frequency" sap:quickinfo="Interest Calculation Frequency in Months">
|
||
<Documentation>
|
||
<Summary>An entry in this field determines the intervals (in months) at which interest is to be calculated automatically for this account (account balance interest calculation). The interest calculation frequency is added to the date of the last interest calculation.</Summary>
|
||
<LongDescription>Date of last interest calculation: 3/31.+ 01 month interest calculation frequency= 4/30 upper limit for the current interest runThe calculation period specified as a report parameter determines whether an account is included in an interest run.The upper limit of the interest run is calculated as in the above example and compared with the upper limit of the calculation entered in the interest run (report parameter). If the calculated upper limit is after the calculation period, the account is not included in interest calculation.If you maintain the interest calculation frequency in the account master record, this entry is used to calculate the upper limit. If not, the interest calculation frequency entered for the interest indicator is used.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierHeadOffice" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Head office" sap:heading="Hd office" sap:quickinfo="Head office account number">
|
||
<Documentation>
|
||
<Summary>This field contains the account number of the master record for the head office account.</Summary>
|
||
<LongDescription>You specify this account number only for branch accounts. Items that you post using the branch account number are automatically posted to the head office account. The system records the branch account number in the line items.Neither transactions nor balances are kept in the branch account.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AlternativePayee" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Alternative payee" sap:heading="Alt.payee" sap:quickinfo="Account number of the alternative payee">
|
||
<Documentation>
|
||
<Summary>The account number of the vendor with whom automatic payment transactions are to be carried out.</Summary>
|
||
<LongDescription>The field is only needed if payments are not to be made directly to the vendor to whom the payable is owed. The same applies to bank collections of receivables.The specification in this field applies only to the company code. There is a further field in which you can enter an alternative payee for each company code. If both fields are filled, the company code specified has priority.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LayoutSortingRule" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Sort Key" sap:heading="Sort" sap:quickinfo="Key for Sorting According to Assignment Numbers">
|
||
<Documentation>
|
||
<Summary>Indicates the layout rule for the Allocation field in the document line item.</Summary>
|
||
<LongDescription>The system uses a standard sort sequence for displaying line items. Among other things, it sorts the items according to the content of the Allocation field. This field can be filled either manually or automatically (by the system) when a document line item is entered.For this purpose, the system requires rules that determine which information is to be taken from the document header or from the document line item and placed in the field. The rules can be stored in the master record of an account which enables you to determine the standard sort sequence on an account-specific basis.NoteField information from another document line item cannot be adopted into the field of a particular item.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="APARToleranceGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Tolerance Group" sap:quickinfo="Tolerance Group for Business Partner/G/L Account">
|
||
<Documentation>
|
||
<Summary>Contains settings that control how the system handles differences between the invoice amount and the amount received from a customer or the amount paid to a supplier. A tolerance group is unique within a company code.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierCertificationDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Certification Date">
|
||
<Documentation>
|
||
<Summary>US government requirement.</Summary>
|
||
<LongDescription>Date field in which to enter certification date for small companies run by women or minorities. This certificate must be renewed every two years.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierAccountNote" Type="Edm.String" MaxLength="30" sap:label="Account Memo" sap:quickinfo="Memo">
|
||
<Documentation>
|
||
<Summary>Internal memo of the accounting department.</Summary>
|
||
<LongDescription>The memo serves only as information on special features of the customer/vendor.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="WithholdingTaxCountry" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="WTax Country" sap:heading="WCty" sap:quickinfo="Withholding Tax Country Key">
|
||
<Documentation>
|
||
<Summary>In some countries, an additional country is needed for calculating or reporting withholding tax.</Summary>
|
||
<LongDescription>The calculation can depend on the payee's country.A particular country key can be required by law for reporting which may possibly be different to the key used in the address.Examples: Japan, USA (1042), Argentina</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DeletionIndicator" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Co.cde deletion flag" sap:heading="DelF" sap:quickinfo="Deletion Flag for Master Record (Company Code Level)">
|
||
<Documentation>
|
||
<Summary>Indicates that the company code data in this master record is to be deleted.</Summary>
|
||
<LongDescription>To delete this data, you have to run the archiving program for Accounts Receivable or Payable. This program will archive all master records marked for deletion provided that there is no dependent data in them.This deletion flag cannot be used in the program that deletes master data. You should, however, run this program only to delete test data prior to production startup.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CashPlanningGroup" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Planning Group" sap:heading="Plan. Group">
|
||
<Documentation>
|
||
<Summary>In cash management, customers and vendors are allocated to planning groups by means of an entry made in the master record.</Summary>
|
||
<LongDescription>You can define these planning groups in Customizing or the Implementation Guide (you will need to ensure that they are all the same length). In order to improve the liquidity forecast display for major customers and vendors, it can be advisable to enter their account number as the planning group.For the planning groups themselves a naming convention should be set up to improve liquidity forecasting. In the following examples, the customer planning groups begin with an "R" for receipts, and the vendor planning groups begin with an "E" for expenses.R1 Customers paying by bank collectionR2 Other domestic customersR3 Customers abroadR4 Affiliated company customersR5 High risk customersR6 Major customersR7 Rental incomeR8 Repayment of loans...E1 Domestic vendorsE2 Vendors abroadE3 Affiliated company vendorsE4 Major vendorsE5 Personnel costsE6 TaxesE7 Investments...</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IsToBeCheckedForDuplicates" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Check Double Invoice" sap:quickinfo="Check Flag for Double Invoices or Credit Memos">
|
||
<Documentation>
|
||
<Summary>When incoming invoices are entered or when memos are entered in Financial Accounting (FI), the system checks whether an invoice or credit memo has already been entered for the same date.</Summary>
|
||
<LongDescription>Checking Logistics DocumentsThe system checks whether the invoice documents have already been entered in the Logistics invoice verification. For this, the system checks invoices that have been held or parked or that contain errors, or invoices that were entered for invoice verification in the background. The check is performed only if you specify the reference document number when you enter the invoices.When checking for duplicate invoices, the system compares the following specified characteristics:VendorCurrencyCompany CodeGross Invoice AmountReference Document NumberInvoice Document DateIf all of these characteristics are the same, the system issues a message for which you can change the message type in Customizing.When you enter credit memos or subsequent adjustments, the system does not check for duplicate invoices.Exception: For Argentina, invoices and credit memos are checked for duplicates.No message is issued if you enter a document that has previously been reversed.In Customizing for Logistics Invoice Verification under Incoming Invoice -> Set Check for Duplicate Invoices, you can specify that the following characteristics are not checked:Reference Document NumberInvoice Document DateCompany CodeHaving fewer attributes to check increases the likelihood that the system will find a duplicate invoice.Example:The following document has already been entered and posted:Reference Document Number 333Invoice Date: 4/28/2000Gross Invoice Amount 100.00Currency: EURVendor: SpencerCompany Code: ChicagoYou have set up the check for duplicate invoices as follows in Customizing:The characteristics Reference Document Number and Company Code are not activated. Consequently, these characteristics are not checked.Now you enter the following invoice:Reference Document Number 334Invoice Date: 4/28/2000Gross Invoice Amount 100.00Currency: EURVendor: SpencerCompany Code: FlagstaffResultBecause you entered a reference document when you entered the invoice, the system checks for duplicate invoices. Compared against the invoice entered earlier, the invoice just entered has different values in the characteristics Reference and Company Code. However, these characteristics are not checked due to the settings that you have made in Customizing. All other characteristics are the same. The system issues a message telling you that an invoice has been entered twice.If the characteristic "Reference Document Number" had been selected in Customizing, the system would have checked the reference document number and established that it was different from the invoice entered earlier, and it consequently would not have issued a message.Checking FI DocumentsThe system checks whether there are FI documents that were posted or parked with the Logistics invoice verification or with an FI invoice transaction. Depending on the entry in the Reference field, one of the following checks is performed:If a reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has already been posted for which all the following attributes agree:Company CodeVendorCurrencyDocument DateReference NumberIf no reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has already been posted for which all the following attributes agree:Company CodeVendorCurrencyDocument DateAmount in Document CurrencyIn Materials Management, the system applies the check for duplicate invoices for invoices only, not for credit memos.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="MinorityGroup" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Minority Indicator" sap:heading="Minority Indic."/>
|
||
<Property Name="SupplierAccountGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Account Group" sap:heading="Group" sap:quickinfo="Supplier Account Group">
|
||
<Documentation>
|
||
<Summary>The account group is a classifying feature within vendor master records. The account group determines:</Summary>
|
||
<LongDescription>the number interval for the account number of the vendor,whether the number is assigned by the user or by the system,which specifications are necessary and/or possible in the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<NavigationProperty Name="to_CompanyText" Relationship="API_BUSINESS_PARTNER.assoc_F9C7FCCBA7A34C05B6E3BFA2C66C2485" FromRole="FromRole_assoc_F9C7FCCBA7A34C05B6E3BFA2C66C2485" ToRole="ToRole_assoc_F9C7FCCBA7A34C05B6E3BFA2C66C2485"/>
|
||
<NavigationProperty Name="to_Supplier" Relationship="API_BUSINESS_PARTNER.assoc_5D8ED7225F3F084CF706245AFBB65A6A" FromRole="FromRole_assoc_5D8ED7225F3F084CF706245AFBB65A6A" ToRole="ToRole_assoc_5D8ED7225F3F084CF706245AFBB65A6A"/>
|
||
<NavigationProperty Name="to_SupplierDunning" Relationship="API_BUSINESS_PARTNER.assoc_5E8DB5909F6A0FD5A1171E3650CDC3F9" FromRole="FromRole_assoc_5E8DB5909F6A0FD5A1171E3650CDC3F9" ToRole="ToRole_assoc_5E8DB5909F6A0FD5A1171E3650CDC3F9"/>
|
||
<NavigationProperty Name="to_SupplierWithHoldingTax" Relationship="API_BUSINESS_PARTNER.assoc_55F62B4F505C71EB6E4B122E91DC5745" FromRole="FromRole_assoc_55F62B4F505C71EB6E4B122E91DC5745" ToRole="ToRole_assoc_55F62B4F505C71EB6E4B122E91DC5745"/>
|
||
</EntityType>
|
||
<EntityType Name="A_SupplierCompanyTextType" sap:label="Supplier Company Text" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Supplier"/>
|
||
<PropertyRef Name="CompanyCode"/>
|
||
<PropertyRef Name="Language"/>
|
||
<PropertyRef Name="LongTextID"/>
|
||
</Key>
|
||
<Property Name="Supplier" Type="Edm.String" Nullable="false" MaxLength="10" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="CompanyCode" Type="Edm.String" Nullable="false" MaxLength="4"/>
|
||
<Property Name="Language" Type="Edm.String" Nullable="false" MaxLength="2" sap:label="Language" sap:heading="L" sap:quickinfo="Language key">
|
||
<Documentation>
|
||
<Summary>The language key is an abbreviation for the language of the object being processed (for example, standard text, form, style).</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LongTextID" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Text ID" sap:heading="ID">
|
||
<Documentation>
|
||
<Summary>The text ID defines the various types of texts related to a text object. For example, the object "TEXT" (standard texts) can have the following text IDs:</Summary>
|
||
<LongDescription>ST for user-specific standard texts (individual texts)SYST for cross-application system textsvarious IDs for specific application departments. You must have the appropriate access authorization in order to access these texts.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LongText" Type="Edm.String" sap:label="String" sap:sortable="false" sap:filterable="false"/>
|
||
</EntityType>
|
||
<EntityType Name="A_SupplierDunningType" sap:label="Supplier Dunning" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Supplier"/>
|
||
<PropertyRef Name="CompanyCode"/>
|
||
<PropertyRef Name="DunningArea"/>
|
||
</Key>
|
||
<Property Name="Supplier" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Supplier" sap:quickinfo="Account Number of Supplier">
|
||
<Documentation>
|
||
<Summary>Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CompanyCode" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Company Code" sap:heading="CoCd">
|
||
<Documentation>
|
||
<Summary>The company code is an organizational unit within financial accounting.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DunningArea" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Dunning Area" sap:heading="Area">
|
||
<Documentation>
|
||
<Summary>The dunning area represents an organizational entity that is responsible for dunning. The dunning areas represent a sub-structure of the company codes.</Summary>
|
||
<LongDescription>If different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas.All dunning notices are made separately according to dunning areas, and if necessary with different dunning procedures.The dunning area must be noted in the line items. As long as documents are copied from preliminary work areas (billing documents), the dunning area can be derived from details such as division or sales area, if necessary.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DunningBlock" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Dunning Block" sap:heading="Block">
|
||
<Documentation>
|
||
<Summary>Key which reflects the reason for a dunning block indicator.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DunningLevel" Type="Edm.String" MaxLength="1" sap:display-format="NonNegative" sap:label="Dunning Level" sap:heading="Dun">
|
||
<Documentation>
|
||
<Summary>Number that specifies how often an item or account has been dunned.</Summary>
|
||
<LongDescription>The business partner has received the dunning level from the last dunning run.If you use dunning areas, it is the dunning level that the business partner received from the last dunning run in the dunning area assigned.The dunning program sets the dunning level automatically when the customer or vendor receives a dunning notice.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DunningProcedure" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Dunning Procedure" sap:heading="Procedure">
|
||
<Documentation>
|
||
<Summary>This field contains the key for the dunning procedure to be used.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DunningRecipient" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Dunn.recipient" sap:heading="Recipient" sap:quickinfo="Account number of the dunning recipient">
|
||
<Documentation>
|
||
<Summary>Account number of the vendor who is to receive the dunning notice.</Summary>
|
||
<LongDescription>Note:If an entry is not made in this field, the dunning notice is sent to the address of the vendor to be processed.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LastDunnedOn" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Last Dunned" sap:heading="Date" sap:quickinfo="Date of Last Dunning Notice">
|
||
<Documentation>
|
||
<Summary>Date on which the last dunning notice was made.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LegDunningProcedureOn" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Legal Dunn.Proc.From" sap:heading="Leg.Dunn.Proc" sap:quickinfo="Date of the Legal Dunning Proceedings">
|
||
<Documentation>
|
||
<Summary>Date on which a legal dunning procedure was initiated.</Summary>
|
||
<LongDescription>The printing of dunning notices in the legal dunning procedure generates an internal notice about any further account movements. A dunning notice is not created for the customer.If the Legal dunning procedure field in the master record contains a date, this means that the account is involved in a legal dunning procedure. The relationship between this date and the dunning date does not affect how the account is processed.The printing of account movements in the legal dunning procedure differs from the normal printing of dunning notices as follows:You must specify a separate form for your dunning procedure in Customizing. For more information, see Customizing (IMG) under Dunning Forms.The dunning program also displays text element 520 "Legal dunning procedure". This makes it possible to display the date of the legal dunning procedure from the master record.The program also displays the documents blocked for dunning and those with a payment method (automatic debit, bank direct debit).Although dunning notices are printed, the dunning level does not change in the master record or in the items. New dunning level = old dunning level.The program only updates the date of the last dunning run.Enter the date manually.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DunningClerk" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Dunning Clerk" sap:heading="Clerk">
|
||
<Documentation>
|
||
<Summary>Identification code for the accounting clerk dealing with dunning letters.</Summary>
|
||
<LongDescription>Using this identification code, the accounting clerk whose name is printed on the dunning letters is determined.If this field is not filled, then the entry from the Accounting clerk field is used.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization" sap:heading="AuGr" sap:quickinfo="Authorization Group">
|
||
<Documentation>
|
||
<Summary>The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierAccountGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Account Group" sap:heading="Group" sap:quickinfo="Supplier Account Group">
|
||
<Documentation>
|
||
<Summary>The account group is a classifying feature within vendor master records. The account group determines:</Summary>
|
||
<LongDescription>the number interval for the account number of the vendor,whether the number is assigned by the user or by the system,which specifications are necessary and/or possible in the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_SupplierPartnerFuncType" sap:label="Purchasing Partner Functions" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Supplier"/>
|
||
<PropertyRef Name="PurchasingOrganization"/>
|
||
<PropertyRef Name="SupplierSubrange"/>
|
||
<PropertyRef Name="Plant"/>
|
||
<PropertyRef Name="PartnerFunction"/>
|
||
<PropertyRef Name="PartnerCounter"/>
|
||
</Key>
|
||
<Property Name="Supplier" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Supplier" sap:quickinfo="Account Number of Supplier">
|
||
<Documentation>
|
||
<Summary>Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PurchasingOrganization" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Purch. Organization" sap:heading="POrg" sap:quickinfo="Purchasing Organization">
|
||
<Documentation>
|
||
<Summary>Denotes the purchasing organization.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierSubrange" Type="Edm.String" Nullable="false" MaxLength="6" sap:display-format="UpperCase" sap:label="Supplier Subrange" sap:heading="SSR">
|
||
<Documentation>
|
||
<Summary>Subdivision of a supplier's overall product range according to various criteria.</Summary>
|
||
<LongDescription>For each supplier sub-range:The master data is kept on a common basisCertain conditions applyIn the supplier master, you can create different purchasing data and different partner functions for each supplier sub-range.You can also maintain and change the conditions for each supplier sub-range. You assign a material to a supplier sub-range in the info record.In the supplier master, you can maintain different data for particular supplier sub-ranges, such as ordering addresses or terms of payment, for example.When creating a purchase order with a known supplier, different data is only determined if the supplier sub-range is entered in the initial screen.Your supplier Smith in Houston has two sub-ranges: paint and glue.All materials from the "paint" sub-range are ordered in Houston.You have maintained an alternative ordering address in Detroit for the "glue" sub-range.If you order materials from the "glue" sub-range, the supplier sub-range finds the Detroit ordering address.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Plant" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Plant" sap:heading="Plnt">
|
||
<Documentation>
|
||
<Summary>Key uniquely identifying a plant.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PartnerFunction" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Partner Function" sap:heading="Funct">
|
||
<Documentation>
|
||
<Summary>The abbreviated form of the name that identifies the partner function.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PartnerCounter" Type="Edm.String" Nullable="false" MaxLength="3" sap:display-format="NonNegative" sap:label="Partner counter" sap:heading="ParC">
|
||
<Documentation>
|
||
<Summary>The sequential number that the system applies when there is more than one partner for a particular partner function.</Summary>
|
||
<LongDescription>When you create a sales order for a particular customer, there may be more than one ship-to party defined. The different ship-to parties are numbered sequentially.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DefaultPartner" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Default Partner" sap:heading="D">
|
||
<Documentation>
|
||
<Summary>Specifies a partner as the default for a particular partner function.</Summary>
|
||
<LongDescription>When you enter more than one partner for a particular partner function (for example, you define three different ship-to parties), you can select one partner as the default. During sales or purchasing processing, if you have defined multiple partners for a partner function, the system prompts you to choose just one partner. The system presents the default partner as the first choice in the pop-up window.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CreationDate" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Created On" sap:quickinfo="Date on Which Record Was Created" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="CreatedByUser" Type="Edm.String" MaxLength="12" sap:display-format="UpperCase" sap:label="Created By" sap:quickinfo="Name of Person Who Created Object" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="ReferenceSupplier" Type="Edm.String" MaxLength="10" sap:display-format="UpperCase" sap:label="Ref. to vendor" sap:heading="Reference to other vendor" sap:quickinfo="Reference to other vendor"/>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization" sap:heading="AuGr" sap:quickinfo="Authorization Group">
|
||
<Documentation>
|
||
<Summary>The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<EntityType Name="A_SupplierPurchasingOrgType" sap:label="Purchasing Organization" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Supplier"/>
|
||
<PropertyRef Name="PurchasingOrganization"/>
|
||
</Key>
|
||
<Property Name="Supplier" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Supplier" sap:quickinfo="Account Number of the Vendor">
|
||
<Documentation>
|
||
<Summary>Alphanumeric key uniquely identifying the document.</Summary>
|
||
<LongDescription>With the supplier number, information from the supplier master record (such as the supplier's address and bank details) is copied into a purchasing document (such as a request for quotation or a purchase order).You can use the supplier number to keep track of requests for quotation, purchase orders and outline agreements.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PurchasingOrganization" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Purch. Organization" sap:heading="POrg" sap:quickinfo="Purchasing Organization">
|
||
<Documentation>
|
||
<Summary>Denotes the purchasing organization.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CalculationSchemaGroupCode" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Schema Grp, Supplier" sap:heading="Gr" sap:quickinfo="Group for Calculation Schema (Supplier)">
|
||
<Documentation>
|
||
<Summary>Determines which calculation schema (pricing procedure) is to be used in purchasing documents containing this supplier number.</Summary>
|
||
<LongDescription>You can use the schema group to specify the calculation schema per purchasing organization or supplier. The relevant calculation schema is determined by reference to the schema group.The effect of this is that the conditions to be maintained in a purchasing document can differ depending on the relevant purchasing organization or supplier.If a calculation schema is only to be valid for certain purchasing organizations or suppliers, proceed as follows:Define the schema group for the purchasing organization or the supplier using the relevant function in the menu "Calculation schema -> Schema groups".Assign the schema group to the calculation schema via "Calculation schema -> Determine schema".Enter the schema group for the supplier in the supplier master records to which the calculation schema is to be assigned. Assign the schema group of the purchasing organization to the relevant purchasing organization using "Calculation schema -> Schema group -> Assign to purch. org.".</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="DeletionIndicator" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Del. flag POrg." sap:heading="D" sap:quickinfo="Deletion Indicator for Supplier at Purchasing Level">
|
||
<Documentation>
|
||
<Summary>Indicates whether or not the supplier master record is earmarked for deletion.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IncotermsClassification" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Incoterms" sap:heading="IncoT" sap:quickinfo="Incoterms (Part 1)">
|
||
<Documentation>
|
||
<Summary>Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).</Summary>
|
||
<LongDescription>Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IncotermsTransferLocation" Type="Edm.String" MaxLength="28" sap:label="Incoterms (Part 2)" sap:heading="Inco. 2">
|
||
<Documentation>
|
||
<Summary>Additional information for the primary Incoterm.</Summary>
|
||
<LongDescription>If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IncotermsVersion" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Incoterms Version" sap:heading="IncoV">
|
||
<Documentation>
|
||
<Summary>An incoterms version is an edition containing a list of international terms for transportation that is defined by the International Chamber of Commerce (ICC).</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IncotermsLocation1" Type="Edm.String" MaxLength="70" sap:label="Incoterms Location 1">
|
||
<Documentation>
|
||
<Summary>Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:</Summary>
|
||
<LongDescription>1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IncotermsLocation2" Type="Edm.String" MaxLength="70" sap:label="Incoterms Location 2">
|
||
<Documentation>
|
||
<Summary>Provides additional information for the Incoterms. This field is only available for C-Clauses (if customized appropriately). Note the following for the incoterms versions below:</Summary>
|
||
<LongDescription>No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="InvoiceIsGoodsReceiptBased" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="GR-Based Inv. Verif." sap:heading="GR-IV" sap:quickinfo="Indicator: GR-Based Invoice Verification">
|
||
<Documentation>
|
||
<Summary>Indicator specifying that provision has been made for goods-receipt-based invoice verification for a purchase order item or invoice item.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="MaterialPlannedDeliveryDurn" Type="Edm.Decimal" Precision="3" Scale="0" sap:label="Planned Deliv. Time" sap:heading="PDT" sap:quickinfo="Planned Delivery Time in Days">
|
||
<Documentation>
|
||
<Summary>Number of calendar days needed to obtain the material or service if it is procured externally.</Summary>
|
||
<LongDescription>If you have different vendors for a material, you must specify an average value. The same applies if you order the material from a fixed vendor that has varying delivery times.If you use the SAP Retail System, the planned delivery time can be suggested from the vendor sub-range in the vendor master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="MinimumOrderAmount" Type="Edm.Decimal" Precision="14" Scale="3" sap:unit="PurchaseOrderCurrency" sap:label="Minimum order value" sap:heading="Minimum value">
|
||
<Documentation>
|
||
<Summary>Minimum value specified for purchase orders issued to the relevant supplier.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PaymentTerms" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Terms of Payment" sap:heading="PayT" sap:quickinfo="Terms of Payment Key">
|
||
<Documentation>
|
||
<Summary>Key for defining payment terms composed of cash discount percentages and payment periods.</Summary>
|
||
<LongDescription>It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PricingDateControl" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="Pricing Date Control" sap:heading="C" sap:quickinfo="Price Determination (Pricing) Date Control">
|
||
<Documentation>
|
||
<Summary>Determines which date is to be used for price determination (pricing) purposes.</Summary>
|
||
<LongDescription>Enter the key for the desired date.If you choose the date of goods receipt, for example, a new price will be determined upon the arrival of the goods, causing the item to be revaluated at this time.NoteIf you have chosen the delivery date as the date for price determination and an item contains several delivery dates (i.e. has a delivery schedule), the first delivery date (the delivery date specified in the first schedule line) is taken.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PurOrdAutoGenerationIsAllowed" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Automatic PO" sap:heading="Aut" sap:quickinfo="Automatic Generation of Purchase Order Allowed">
|
||
<Documentation>
|
||
<Summary>Allows you to automatically generate purchase orders from purchase requisitions if the requisition has been assigned to a supplier (source of supply).</Summary>
|
||
<LongDescription>If you want to use automatic conversion, note the following additional conditions:In the case of purchase requisitions for materials, you should also select the indicator Autom.purch.ord. in the Purchasing view in the material master record.In the case of purchase requisitions for services, you should also select the indicator Automatic creation of POs for service PReqs in Customizing for Services by choosing:IMG -> MM -> External Services Management -> Source Determination and Default Values- for Client or- for Purchasing Organization</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PurchaseOrderCurrency" Type="Edm.String" MaxLength="5" sap:label="Order currency" sap:heading="Crcy" sap:quickinfo="Purchase order currency" sap:semantics="currency-code">
|
||
<Documentation>
|
||
<Summary>Key for the currency on which an order placed with a supplier is based.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PurchasingGroup" Type="Edm.String" MaxLength="3" sap:display-format="UpperCase" sap:label="Purchasing Group" sap:heading="PGr">
|
||
<Documentation>
|
||
<Summary>Key for a buyer or a group of buyers, who is/are responsible for certain purchasing activities.</Summary>
|
||
<LongDescription>Internally, the purchasing group is responsible for the procurement of a material or a class of materials.Externally, it is the medium through which contacts with the vendor are maintained.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="PurchasingIsBlockedForSupplier" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Pur. block POrg" sap:heading="B" sap:quickinfo="Purchasing block at purchasing organization level">
|
||
<Documentation>
|
||
<Summary>Indicates whether or not the supplier master record is blocked for the purchasing organization for posting purposes.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ShippingCondition" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Shipping Conditions" sap:heading="SC">
|
||
<Documentation>
|
||
<Summary>General shipping strategy for the delivery of goods from the vendor to the customer.</Summary>
|
||
<LongDescription>You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierABCClassificationCode" Type="Edm.String" MaxLength="1" sap:display-format="UpperCase" sap:label="ABC indicator" sap:heading="ABC">
|
||
<Documentation>
|
||
<Summary>Means of classifying suppliers according to their significance to your company.</Summary>
|
||
<LongDescription>The indicator serves to assign the supplier to one of the categories A, B or C, in accordance with ABC analysis.'A' category suppliers, for instance, are those accounting for the greatest share of the company's total annual spend (in value terms).</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierPhoneNumber" Type="Edm.String" MaxLength="16" sap:label="Telephone" sap:quickinfo="Supplier's Telephone Number">
|
||
<Documentation>
|
||
<Summary>This telephone number is maintained in the supplier master record and adopted in the purchasing document.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierRespSalesPersonName" Type="Edm.String" MaxLength="30" sap:label="Salesperson" sap:quickinfo="Responsible Salesperson at Supplier's Office">
|
||
<Documentation>
|
||
<Summary>The name of a contact on the supplier side can be freely maintained.</Summary>
|
||
<LongDescription>There is no relation to any other data in the system, for examplebusiness partner.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierConfirmationControlKey" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Confirmation Control" sap:heading="Ctr." sap:quickinfo="Confirmation Control Key">
|
||
<Documentation>
|
||
<Summary>Determines which confirmation categories are expected for a PO item (e.g. order acknowledgment, shipping notification).</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IsOrderAcknRqd" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Acknowledgment Reqd" sap:heading="ARq" sap:quickinfo="Order Acknowledgment Requirement">
|
||
<Documentation>
|
||
<Summary>Determines whether the purchasing document (purchase order, outline purchase agreement, etc.) is to be acknowledged by the supplier.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization" sap:heading="AuGr" sap:quickinfo="Authorization Group">
|
||
<Documentation>
|
||
<Summary>The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="SupplierAccountGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Account Group" sap:heading="Group" sap:quickinfo="Supplier Account Group">
|
||
<Documentation>
|
||
<Summary>The account group is a classifying feature within vendor master records. The account group determines:</Summary>
|
||
<LongDescription>the number interval for the account number of the vendor,whether the number is assigned by the user or by the system,which specifications are necessary and/or possible in the master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<NavigationProperty Name="to_PartnerFunction" Relationship="API_BUSINESS_PARTNER.assoc_20F5EAD3848FBFF2C9E0F6D45CFF1BA9" FromRole="FromRole_assoc_20F5EAD3848FBFF2C9E0F6D45CFF1BA9" ToRole="ToRole_assoc_20F5EAD3848FBFF2C9E0F6D45CFF1BA9"/>
|
||
<NavigationProperty Name="to_PurchasingOrgText" Relationship="API_BUSINESS_PARTNER.assoc_B7FB1F1D45FB656EF3D9435CA2A39EE9" FromRole="FromRole_assoc_B7FB1F1D45FB656EF3D9435CA2A39EE9" ToRole="ToRole_assoc_B7FB1F1D45FB656EF3D9435CA2A39EE9"/>
|
||
</EntityType>
|
||
<EntityType Name="A_SupplierPurchasingOrgTextType" sap:label="Purchasing Organization Text" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Supplier"/>
|
||
<PropertyRef Name="PurchasingOrganization"/>
|
||
<PropertyRef Name="Language"/>
|
||
<PropertyRef Name="LongTextID"/>
|
||
</Key>
|
||
<Property Name="Supplier" Type="Edm.String" Nullable="false" MaxLength="10" sap:creatable="false" sap:updatable="false"/>
|
||
<Property Name="PurchasingOrganization" Type="Edm.String" Nullable="false" MaxLength="4"/>
|
||
<Property Name="Language" Type="Edm.String" Nullable="false" MaxLength="2" sap:label="Language" sap:heading="L" sap:quickinfo="Language key">
|
||
<Documentation>
|
||
<Summary>The language key is an abbreviation for the language of the object being processed (for example, standard text, form, style).</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LongTextID" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Text ID" sap:heading="ID">
|
||
<Documentation>
|
||
<Summary>The text ID defines the various types of texts related to a text object. For example, the object "TEXT" (standard texts) can have the following text IDs:</Summary>
|
||
<LongDescription>ST for user-specific standard texts (individual texts)SYST for cross-application system textsvarious IDs for specific application departments. You must have the appropriate access authorization in order to access these texts.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LongText" Type="Edm.String" sap:label="String" sap:sortable="false" sap:filterable="false"/>
|
||
</EntityType>
|
||
<EntityType Name="A_SupplierTextType" sap:label="Supplier Text" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Supplier"/>
|
||
<PropertyRef Name="Language"/>
|
||
<PropertyRef Name="LongTextID"/>
|
||
</Key>
|
||
<Property Name="Supplier" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Supplier" sap:quickinfo="Account Number of Supplier" sap:creatable="false" sap:updatable="false">
|
||
<Documentation>
|
||
<Summary>Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="Language" Type="Edm.String" Nullable="false" MaxLength="2" sap:label="Language" sap:heading="L" sap:quickinfo="Language key">
|
||
<Documentation>
|
||
<Summary>The language key is an abbreviation for the language of the object being processed (for example, standard text, form, style).</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LongTextID" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Text ID" sap:heading="ID">
|
||
<Documentation>
|
||
<Summary>The text ID defines the various types of texts related to a text object. For example, the object "TEXT" (standard texts) can have the following text IDs:</Summary>
|
||
<LongDescription>ST for user-specific standard texts (individual texts)SYST for cross-application system textsvarious IDs for specific application departments. You must have the appropriate access authorization in order to access these texts.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="LongText" Type="Edm.String" sap:label="String" sap:sortable="false" sap:filterable="false"/>
|
||
</EntityType>
|
||
<EntityType Name="A_SupplierWithHoldingTaxType" sap:label="Company Withholding Tax" sap:content-version="1">
|
||
<Key>
|
||
<PropertyRef Name="Supplier"/>
|
||
<PropertyRef Name="CompanyCode"/>
|
||
<PropertyRef Name="WithholdingTaxType"/>
|
||
</Key>
|
||
<Property Name="Supplier" Type="Edm.String" Nullable="false" MaxLength="10" sap:display-format="UpperCase" sap:label="Supplier" sap:quickinfo="Account Number of Supplier">
|
||
<Documentation>
|
||
<Summary>Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="CompanyCode" Type="Edm.String" Nullable="false" MaxLength="4" sap:display-format="UpperCase" sap:label="Company Code" sap:heading="CoCd">
|
||
<Documentation>
|
||
<Summary>The company code is an organizational unit within financial accounting.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="WithholdingTaxType" Type="Edm.String" Nullable="false" MaxLength="2" sap:display-format="UpperCase" sap:label="Withholding Tax Type" sap:heading="Withhld tax type" sap:quickinfo="Indicator for Withholding Tax Type">
|
||
<Documentation>
|
||
<Summary>This indicator is used to classify the different types of withholding tax.</Summary>
|
||
<LongDescription>Withholding tax types classify particular features of a withholding tax including:The time at which the withholding tax is postedThe basis on which the base amount is calculatedThe basis for accumulation (if applicable)Withholding tax types are to be distinguished from withholding tax codes, to which are allocated the withholding tax percentage rate example.Whether a withholding tax can be defined as an existing type by means of a new code, or if a new type needs to be defined will depend on the type of transaction (see below).Note that a business transaction can only be assigned one withholding tax code per withholding tax type. If the business transaction is subject to several withholding taxes simultaneously, these must be represented by different types.This is the case in Argentina for example, where up to four kinds of withholding tax per business transaction are possible.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ExemptionDateBegin" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Exemption Start Date" sap:heading="Exempt Fr." sap:quickinfo="Date on Which Exemption Begins">
|
||
<Documentation>
|
||
<Summary>Date from which withholding tax exemption applies.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ExemptionDateEnd" Type="Edm.DateTime" Precision="0" sap:display-format="Date" sap:label="Exemption End Date" sap:heading="Exempt To" sap:quickinfo="Date on Which Exemption Ends">
|
||
<Documentation>
|
||
<Summary>Date on which withholding tax exemption expires.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="ExemptionReason" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Exemption Reason" sap:heading="Exmpt.Resn" sap:quickinfo="Reason for Exemption">
|
||
<Documentation>
|
||
<Summary>Indicator used to classify different types of exemption from liability to a particular withholding tax.</Summary>
|
||
<LongDescription>These indicators can be defined per withholding tax type in the vendor master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="IsWithholdingTaxSubject" Type="Edm.Boolean" sap:display-format="UpperCase" sap:label="Subject to W/Tx" sap:heading="W/Tax" sap:quickinfo="Indicator: Subject to Withholding Tax?"/>
|
||
<Property Name="RecipientType" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="Recipient Type" sap:heading="Rec.Ty" sap:quickinfo="Type of Recipient">
|
||
<Documentation>
|
||
<Summary>The type of recipient can be defined in the vendor master record.</Summary>
|
||
<LongDescription>It is used to group vendors together according to particular characteristics such as occupations that may be subject to the same withholding tax type, but which are required to pay different percentage rates (as defined by the withholding tax code).Application in ThailandThis corresponds to the official Thai form number (Phaw.Ngor.Daw) and is used to determine the sequential numbering of a withholding tax certificate. The form number is defined in the vendor master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="WithholdingTaxCertificate" Type="Edm.String" MaxLength="25" sap:display-format="UpperCase" sap:label="Exemption Number" sap:heading="Exem. No." sap:quickinfo="Exemption Certificate Number">
|
||
<Documentation>
|
||
<Summary>Numbered assigned by the relevant authorities for exemption from withholding tax.</Summary>
|
||
<LongDescription>This number must be entered in the system as follows:In the vendor master record in the case of vendorsFor customers, in Customizing under the settings for withholding tax information for the company code per withholding tax type.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="WithholdingTaxCode" Type="Edm.String" MaxLength="2" sap:display-format="UpperCase" sap:label="W/Tax Code" sap:heading="WTx" sap:quickinfo="Withholding Tax Code">
|
||
<Documentation>
|
||
<Summary>One or more "withholding tax codes" are assigned to each withholding tax type. One of the things these codes determine is the various percentage rates for the withholding tax type.</Summary>
|
||
<LongDescription>Note that when processing a business transaction, no more than one withholding tax code can be assigned per withholding tax type. If the business transaction is subject to more than one withholding taxes, these must be represented in the system by defining various withholding tax types.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="WithholdingTaxExmptPercent" Type="Edm.Decimal" Precision="5" Scale="2" sap:label="Exemption Rate" sap:heading="Exem.%">
|
||
<Documentation>
|
||
<Summary>Rate of exemption from withholding tax.</Summary>
|
||
<LongDescription>Those persons/activities subject to withholding tax can be exempted from withholding tax up to the percentage rate you enter here. This exemption rate refers to the withholding tax amount itself and not to the whole amount liable to withholding tax (withholding tax base amount).The gross amount of an invoice is 100.00 and the withholding tax base amount is defined as gross. The withholding tax rate is 10% meaning that the withholding tax amount is 10.00. Given an exemption rate of 30%, the withholding tax amount is reduced to 7.00.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="WithholdingTaxNumber" Type="Edm.String" MaxLength="16" sap:display-format="UpperCase" sap:label="W/tax number" sap:heading="W/TxID" sap:quickinfo="Withholding tax identification number">
|
||
<Documentation>
|
||
<Summary>This is a number issued by the tax authorities per withholding tax type.</Summary>
|
||
<LongDescription>This number must be specified in Customizing either:(a) As part of the withholding tax information defined for the company code, or(b) As part of the withholding tax information defined in the customer or vendor master record.</LongDescription>
|
||
</Documentation>
|
||
</Property>
|
||
<Property Name="AuthorizationGroup" Type="Edm.String" MaxLength="4" sap:display-format="UpperCase" sap:label="Authorization" sap:heading="AuGr" sap:quickinfo="Authorization Group">
|
||
<Documentation>
|
||
<Summary>The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.</Summary>
|
||
<LongDescription/>
|
||
</Documentation>
|
||
</Property>
|
||
</EntityType>
|
||
<Association Name="assoc_20F5EAD3848FBFF2C9E0F6D45CFF1BA9" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierPurchasingOrgType" Multiplicity="1" Role="FromRole_assoc_20F5EAD3848FBFF2C9E0F6D45CFF1BA9"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierPartnerFuncType" Multiplicity="*" Role="ToRole_assoc_20F5EAD3848FBFF2C9E0F6D45CFF1BA9"/>
|
||
</Association>
|
||
<Association Name="assoc_B7FB1F1D45FB656EF3D9435CA2A39EE9" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierPurchasingOrgType" Multiplicity="1" Role="FromRole_assoc_B7FB1F1D45FB656EF3D9435CA2A39EE9"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierPurchasingOrgTextType" Multiplicity="*" Role="ToRole_assoc_B7FB1F1D45FB656EF3D9435CA2A39EE9"/>
|
||
</Association>
|
||
<Association Name="assoc_138939C49DA3F66FEE8C74425F390DD3" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierType" Multiplicity="1" Role="FromRole_assoc_138939C49DA3F66FEE8C74425F390DD3"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierCompanyType" Multiplicity="*" Role="ToRole_assoc_138939C49DA3F66FEE8C74425F390DD3"/>
|
||
</Association>
|
||
<Association Name="assoc_B2EAAC3147A4639C17A2CFEACA07BE23" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierType" Multiplicity="1" Role="FromRole_assoc_B2EAAC3147A4639C17A2CFEACA07BE23"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierPurchasingOrgType" Multiplicity="*" Role="ToRole_assoc_B2EAAC3147A4639C17A2CFEACA07BE23"/>
|
||
</Association>
|
||
<Association Name="assoc_A47744B1176D2172C3109B5E43FFC7F9" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierType" Multiplicity="1" Role="FromRole_assoc_A47744B1176D2172C3109B5E43FFC7F9"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierTextType" Multiplicity="*" Role="ToRole_assoc_A47744B1176D2172C3109B5E43FFC7F9"/>
|
||
</Association>
|
||
<Association Name="assoc_BB9464C0EE976A75A05F937B73A26763" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerType" Multiplicity="1" Role="FromRole_assoc_BB9464C0EE976A75A05F937B73A26763"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerCompanyType" Multiplicity="*" Role="ToRole_assoc_BB9464C0EE976A75A05F937B73A26763"/>
|
||
</Association>
|
||
<Association Name="assoc_70A8B5CCADF265E097DC86BC7B699B31" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerType" Multiplicity="1" Role="FromRole_assoc_70A8B5CCADF265E097DC86BC7B699B31"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerSalesAreaType" Multiplicity="*" Role="ToRole_assoc_70A8B5CCADF265E097DC86BC7B699B31"/>
|
||
</Association>
|
||
<Association Name="assoc_0DE5F89839F0BD9497F35D85212F05CE" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerType" Multiplicity="1" Role="FromRole_assoc_0DE5F89839F0BD9497F35D85212F05CE"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerTaxGroupingType" Multiplicity="*" Role="ToRole_assoc_0DE5F89839F0BD9497F35D85212F05CE"/>
|
||
</Association>
|
||
<Association Name="assoc_301BF3C95F38823A34CFF6B5A5EF3514" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerType" Multiplicity="1" Role="FromRole_assoc_301BF3C95F38823A34CFF6B5A5EF3514"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerTextType" Multiplicity="*" Role="ToRole_assoc_301BF3C95F38823A34CFF6B5A5EF3514"/>
|
||
</Association>
|
||
<Association Name="assoc_07A4C6774A79F32D8C1BDA1CBE5A2FA7" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerType" Multiplicity="1" Role="FromRole_assoc_07A4C6774A79F32D8C1BDA1CBE5A2FA7"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_BuPaIdentificationType" Multiplicity="*" Role="ToRole_assoc_07A4C6774A79F32D8C1BDA1CBE5A2FA7"/>
|
||
</Association>
|
||
<Association Name="assoc_91BCE13588BD3046353CD68D3098C2E5" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerType" Multiplicity="1" Role="FromRole_assoc_91BCE13588BD3046353CD68D3098C2E5"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_BuPaIndustryType" Multiplicity="*" Role="ToRole_assoc_91BCE13588BD3046353CD68D3098C2E5"/>
|
||
</Association>
|
||
<Association Name="assoc_6247ED959B75350E6EA6CEDD2CBEC7E7" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerType" Multiplicity="1" Role="FromRole_assoc_6247ED959B75350E6EA6CEDD2CBEC7E7"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerAddressType" Multiplicity="*" Role="ToRole_assoc_6247ED959B75350E6EA6CEDD2CBEC7E7"/>
|
||
</Association>
|
||
<Association Name="assoc_05F0DA10FFAB2836605571E5ABB6E5B9" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerType" Multiplicity="1" Role="FromRole_assoc_05F0DA10FFAB2836605571E5ABB6E5B9"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerBankType" Multiplicity="*" Role="ToRole_assoc_05F0DA10FFAB2836605571E5ABB6E5B9"/>
|
||
</Association>
|
||
<Association Name="assoc_02AC1AF45478434AAB93B18ECA2FB863" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerType" Multiplicity="1" Role="FromRole_assoc_02AC1AF45478434AAB93B18ECA2FB863"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerContactType" Multiplicity="*" Role="ToRole_assoc_02AC1AF45478434AAB93B18ECA2FB863"/>
|
||
</Association>
|
||
<Association Name="assoc_FB863C7C69262D926CE14CA6A50667DB" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerType" Multiplicity="1" Role="FromRole_assoc_FB863C7C69262D926CE14CA6A50667DB"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerRoleType" Multiplicity="*" Role="ToRole_assoc_FB863C7C69262D926CE14CA6A50667DB"/>
|
||
</Association>
|
||
<Association Name="assoc_DADC7016DBB892642F90D68E0E47B6E8" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerType" Multiplicity="1" Role="FromRole_assoc_DADC7016DBB892642F90D68E0E47B6E8"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerTaxNumberType" Multiplicity="*" Role="ToRole_assoc_DADC7016DBB892642F90D68E0E47B6E8"/>
|
||
</Association>
|
||
<Association Name="assoc_80838433DCE8E16AA7C9031C32896631" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerType" Multiplicity="1" Role="FromRole_assoc_80838433DCE8E16AA7C9031C32896631"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerType" Multiplicity="0..1" Role="ToRole_assoc_80838433DCE8E16AA7C9031C32896631"/>
|
||
</Association>
|
||
<Association Name="assoc_7256A9801E68AE14E59054C2738099F1" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerType" Multiplicity="1" Role="FromRole_assoc_7256A9801E68AE14E59054C2738099F1"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierType" Multiplicity="0..1" Role="ToRole_assoc_7256A9801E68AE14E59054C2738099F1"/>
|
||
</Association>
|
||
<Association Name="assoc_EC8BD55FE296CB9F7E96A12A10A83C8A" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BPContactToAddressType" Multiplicity="1" Role="FromRole_assoc_EC8BD55FE296CB9F7E96A12A10A83C8A"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_AddressFaxNumberType" Multiplicity="*" Role="ToRole_assoc_EC8BD55FE296CB9F7E96A12A10A83C8A"/>
|
||
</Association>
|
||
<Association Name="assoc_A30D7A481BC8C28A25685BA876365019" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BPContactToAddressType" Multiplicity="1" Role="FromRole_assoc_A30D7A481BC8C28A25685BA876365019"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_AddressPhoneNumberType" Multiplicity="*" Role="ToRole_assoc_A30D7A481BC8C28A25685BA876365019"/>
|
||
</Association>
|
||
<Association Name="assoc_E5744DCC3F8BA081306832D86DBAE35B" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BPContactToAddressType" Multiplicity="1" Role="FromRole_assoc_E5744DCC3F8BA081306832D86DBAE35B"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_AddressPhoneNumberType" Multiplicity="*" Role="ToRole_assoc_E5744DCC3F8BA081306832D86DBAE35B"/>
|
||
</Association>
|
||
<Association Name="assoc_313909BAAED14CA9CB4829C648286478" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BPContactToAddressType" Multiplicity="1" Role="FromRole_assoc_313909BAAED14CA9CB4829C648286478"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_AddressHomePageURLType" Multiplicity="*" Role="ToRole_assoc_313909BAAED14CA9CB4829C648286478"/>
|
||
</Association>
|
||
<Association Name="assoc_76A1D4C9690D91482219A96E6133DCA1" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BPContactToAddressType" Multiplicity="1" Role="FromRole_assoc_76A1D4C9690D91482219A96E6133DCA1"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_AddressEmailAddressType" Multiplicity="*" Role="ToRole_assoc_76A1D4C9690D91482219A96E6133DCA1"/>
|
||
</Association>
|
||
<Association Name="assoc_B60166D8890DDF85A7D581A0BB2D1255" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerCompanyType" Multiplicity="1" Role="FromRole_assoc_B60166D8890DDF85A7D581A0BB2D1255"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerCompanyTextType" Multiplicity="*" Role="ToRole_assoc_B60166D8890DDF85A7D581A0BB2D1255"/>
|
||
</Association>
|
||
<Association Name="assoc_8273BE5CD7CC24B836264946436461DA" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerCompanyType" Multiplicity="1" Role="FromRole_assoc_8273BE5CD7CC24B836264946436461DA"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerDunningType" Multiplicity="*" Role="ToRole_assoc_8273BE5CD7CC24B836264946436461DA"/>
|
||
</Association>
|
||
<Association Name="assoc_65B2B550EF37ECC341EC132360E3D0A8" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerCompanyType" Multiplicity="1" Role="FromRole_assoc_65B2B550EF37ECC341EC132360E3D0A8"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerWithHoldingTaxType" Multiplicity="*" Role="ToRole_assoc_65B2B550EF37ECC341EC132360E3D0A8"/>
|
||
</Association>
|
||
<Association Name="assoc_091DBA85F5FE3E747FC3884B40B4EBFD" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerAddressType" Multiplicity="1" Role="FromRole_assoc_091DBA85F5FE3E747FC3884B40B4EBFD"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_BuPaAddressUsageType" Multiplicity="*" Role="ToRole_assoc_091DBA85F5FE3E747FC3884B40B4EBFD"/>
|
||
</Association>
|
||
<Association Name="assoc_B21DC96A1904D36E94FBE84771BD7E99" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerAddressType" Multiplicity="1" Role="FromRole_assoc_B21DC96A1904D36E94FBE84771BD7E99"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_AddressEmailAddressType" Multiplicity="*" Role="ToRole_assoc_B21DC96A1904D36E94FBE84771BD7E99"/>
|
||
</Association>
|
||
<Association Name="assoc_43B546339886BBB6ED35EA7CA84FB32B" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerAddressType" Multiplicity="1" Role="FromRole_assoc_43B546339886BBB6ED35EA7CA84FB32B"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_AddressFaxNumberType" Multiplicity="*" Role="ToRole_assoc_43B546339886BBB6ED35EA7CA84FB32B"/>
|
||
</Association>
|
||
<Association Name="assoc_60DDA2597182EA56C114908472D2FB81" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerAddressType" Multiplicity="1" Role="FromRole_assoc_60DDA2597182EA56C114908472D2FB81"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_AddressPhoneNumberType" Multiplicity="*" Role="ToRole_assoc_60DDA2597182EA56C114908472D2FB81"/>
|
||
</Association>
|
||
<Association Name="assoc_35D5A40C930BECE699C4526B1B1F8D1C" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerAddressType" Multiplicity="1" Role="FromRole_assoc_35D5A40C930BECE699C4526B1B1F8D1C"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_AddressPhoneNumberType" Multiplicity="*" Role="ToRole_assoc_35D5A40C930BECE699C4526B1B1F8D1C"/>
|
||
</Association>
|
||
<Association Name="assoc_24C290CBC7FE69574AD9D79A5C631212" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerAddressType" Multiplicity="1" Role="FromRole_assoc_24C290CBC7FE69574AD9D79A5C631212"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_AddressHomePageURLType" Multiplicity="*" Role="ToRole_assoc_24C290CBC7FE69574AD9D79A5C631212"/>
|
||
</Association>
|
||
<Association Name="assoc_68C6FA4D5F974F8BBFCA5D234FA05107" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerContactType" Multiplicity="1" Role="FromRole_assoc_68C6FA4D5F974F8BBFCA5D234FA05107"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_BPContactToAddressType" Multiplicity="*" Role="ToRole_assoc_68C6FA4D5F974F8BBFCA5D234FA05107"/>
|
||
</Association>
|
||
<Association Name="assoc_ABC4A572A4A8802D97BA70498CCE4A4E" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_BusinessPartnerContactType" Multiplicity="1" Role="FromRole_assoc_ABC4A572A4A8802D97BA70498CCE4A4E"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_BPContactToFuncAndDeptType" Multiplicity="0..1" Role="ToRole_assoc_ABC4A572A4A8802D97BA70498CCE4A4E"/>
|
||
</Association>
|
||
<Association Name="assoc_F9C7FCCBA7A34C05B6E3BFA2C66C2485" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierCompanyType" Multiplicity="1" Role="FromRole_assoc_F9C7FCCBA7A34C05B6E3BFA2C66C2485"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierCompanyTextType" Multiplicity="*" Role="ToRole_assoc_F9C7FCCBA7A34C05B6E3BFA2C66C2485"/>
|
||
</Association>
|
||
<Association Name="assoc_5D8ED7225F3F084CF706245AFBB65A6A" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierCompanyType" Multiplicity="1" Role="FromRole_assoc_5D8ED7225F3F084CF706245AFBB65A6A"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierType" Multiplicity="1" Role="ToRole_assoc_5D8ED7225F3F084CF706245AFBB65A6A"/>
|
||
</Association>
|
||
<Association Name="assoc_5E8DB5909F6A0FD5A1171E3650CDC3F9" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierCompanyType" Multiplicity="1" Role="FromRole_assoc_5E8DB5909F6A0FD5A1171E3650CDC3F9"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierDunningType" Multiplicity="*" Role="ToRole_assoc_5E8DB5909F6A0FD5A1171E3650CDC3F9"/>
|
||
</Association>
|
||
<Association Name="assoc_55F62B4F505C71EB6E4B122E91DC5745" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierCompanyType" Multiplicity="1" Role="FromRole_assoc_55F62B4F505C71EB6E4B122E91DC5745"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_SupplierWithHoldingTaxType" Multiplicity="*" Role="ToRole_assoc_55F62B4F505C71EB6E4B122E91DC5745"/>
|
||
</Association>
|
||
<Association Name="assoc_3747E462BFFBB3127682A67959ECC8AA" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerSalesAreaType" Multiplicity="1" Role="FromRole_assoc_3747E462BFFBB3127682A67959ECC8AA"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_CustSalesPartnerFuncType" Multiplicity="*" Role="ToRole_assoc_3747E462BFFBB3127682A67959ECC8AA"/>
|
||
</Association>
|
||
<Association Name="assoc_49CF1243367384CB6C19B5648CA1F817" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerSalesAreaType" Multiplicity="1" Role="FromRole_assoc_49CF1243367384CB6C19B5648CA1F817"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerSalesAreaTaxType" Multiplicity="*" Role="ToRole_assoc_49CF1243367384CB6C19B5648CA1F817"/>
|
||
</Association>
|
||
<Association Name="assoc_46D370A62F67996B992AE7C09589BEAD" sap:content-version="1">
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerSalesAreaType" Multiplicity="1" Role="FromRole_assoc_46D370A62F67996B992AE7C09589BEAD"/>
|
||
<End Type="API_BUSINESS_PARTNER.A_CustomerSalesAreaTextType" Multiplicity="*" Role="ToRole_assoc_46D370A62F67996B992AE7C09589BEAD"/>
|
||
</Association>
|
||
<EntityContainer Name="API_BUSINESS_PARTNER_Entities" m:IsDefaultEntityContainer="true" sap:message-scope-supported="true" sap:supported-formats="atom json xlsx">
|
||
<EntitySet Name="A_AddressEmailAddress" EntityType="API_BUSINESS_PARTNER.A_AddressEmailAddressType" sap:content-version="1"/>
|
||
<EntitySet Name="A_AddressFaxNumber" EntityType="API_BUSINESS_PARTNER.A_AddressFaxNumberType" sap:content-version="1"/>
|
||
<EntitySet Name="A_AddressHomePageURL" EntityType="API_BUSINESS_PARTNER.A_AddressHomePageURLType" sap:content-version="1"/>
|
||
<EntitySet Name="A_AddressPhoneNumber" EntityType="API_BUSINESS_PARTNER.A_AddressPhoneNumberType" sap:content-version="1"/>
|
||
<EntitySet Name="A_BPContactToAddress" EntityType="API_BUSINESS_PARTNER.A_BPContactToAddressType" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1"/>
|
||
<EntitySet Name="A_BPContactToFuncAndDept" EntityType="API_BUSINESS_PARTNER.A_BPContactToFuncAndDeptType" sap:creatable="false" sap:deletable="false" sap:content-version="1"/>
|
||
<EntitySet Name="A_BuPaAddressUsage" EntityType="API_BUSINESS_PARTNER.A_BuPaAddressUsageType" sap:content-version="1"/>
|
||
<EntitySet Name="A_BuPaIdentification" EntityType="API_BUSINESS_PARTNER.A_BuPaIdentificationType" sap:content-version="1"/>
|
||
<EntitySet Name="A_BuPaIndustry" EntityType="API_BUSINESS_PARTNER.A_BuPaIndustryType" sap:content-version="1"/>
|
||
<EntitySet Name="A_BusinessPartner" EntityType="API_BUSINESS_PARTNER.A_BusinessPartnerType" sap:deletable="false" sap:content-version="1"/>
|
||
<EntitySet Name="A_BusinessPartnerAddress" EntityType="API_BUSINESS_PARTNER.A_BusinessPartnerAddressType" sap:content-version="1"/>
|
||
<EntitySet Name="A_BusinessPartnerBank" EntityType="API_BUSINESS_PARTNER.A_BusinessPartnerBankType" sap:content-version="1"/>
|
||
<EntitySet Name="A_BusinessPartnerContact" EntityType="API_BUSINESS_PARTNER.A_BusinessPartnerContactType" sap:content-version="1"/>
|
||
<EntitySet Name="A_BusinessPartnerRole" EntityType="API_BUSINESS_PARTNER.A_BusinessPartnerRoleType" sap:deletable="false" sap:content-version="1"/>
|
||
<EntitySet Name="A_BusinessPartnerTaxNumber" EntityType="API_BUSINESS_PARTNER.A_BusinessPartnerTaxNumberType" sap:content-version="1"/>
|
||
<EntitySet Name="A_Customer" EntityType="API_BUSINESS_PARTNER.A_CustomerType" sap:creatable="false" sap:deletable="false" sap:content-version="1"/>
|
||
<EntitySet Name="A_CustomerCompany" EntityType="API_BUSINESS_PARTNER.A_CustomerCompanyType" sap:deletable="false" sap:content-version="1"/>
|
||
<EntitySet Name="A_CustomerCompanyText" EntityType="API_BUSINESS_PARTNER.A_CustomerCompanyTextType" sap:content-version="1"/>
|
||
<EntitySet Name="A_CustomerDunning" EntityType="API_BUSINESS_PARTNER.A_CustomerDunningType" sap:content-version="1"/>
|
||
<EntitySet Name="A_CustomerSalesArea" EntityType="API_BUSINESS_PARTNER.A_CustomerSalesAreaType" sap:deletable="false" sap:content-version="1"/>
|
||
<EntitySet Name="A_CustomerSalesAreaTax" EntityType="API_BUSINESS_PARTNER.A_CustomerSalesAreaTaxType" sap:deletable="false" sap:content-version="1"/>
|
||
<EntitySet Name="A_CustomerSalesAreaText" EntityType="API_BUSINESS_PARTNER.A_CustomerSalesAreaTextType" sap:content-version="1"/>
|
||
<EntitySet Name="A_CustomerTaxGrouping" EntityType="API_BUSINESS_PARTNER.A_CustomerTaxGroupingType" sap:creatable="false" sap:content-version="1"/>
|
||
<EntitySet Name="A_CustomerText" EntityType="API_BUSINESS_PARTNER.A_CustomerTextType" sap:content-version="1"/>
|
||
<EntitySet Name="A_CustomerWithHoldingTax" EntityType="API_BUSINESS_PARTNER.A_CustomerWithHoldingTaxType" sap:content-version="1"/>
|
||
<EntitySet Name="A_CustSalesPartnerFunc" EntityType="API_BUSINESS_PARTNER.A_CustSalesPartnerFuncType" sap:content-version="1"/>
|
||
<EntitySet Name="A_Supplier" EntityType="API_BUSINESS_PARTNER.A_SupplierType" sap:creatable="false" sap:deletable="false" sap:content-version="1"/>
|
||
<EntitySet Name="A_SupplierCompany" EntityType="API_BUSINESS_PARTNER.A_SupplierCompanyType" sap:deletable="false" sap:content-version="1"/>
|
||
<EntitySet Name="A_SupplierCompanyText" EntityType="API_BUSINESS_PARTNER.A_SupplierCompanyTextType" sap:content-version="1"/>
|
||
<EntitySet Name="A_SupplierDunning" EntityType="API_BUSINESS_PARTNER.A_SupplierDunningType" sap:content-version="1"/>
|
||
<EntitySet Name="A_SupplierPartnerFunc" EntityType="API_BUSINESS_PARTNER.A_SupplierPartnerFuncType" sap:content-version="1"/>
|
||
<EntitySet Name="A_SupplierPurchasingOrg" EntityType="API_BUSINESS_PARTNER.A_SupplierPurchasingOrgType" sap:deletable="false" sap:content-version="1"/>
|
||
<EntitySet Name="A_SupplierPurchasingOrgText" EntityType="API_BUSINESS_PARTNER.A_SupplierPurchasingOrgTextType" sap:content-version="1"/>
|
||
<EntitySet Name="A_SupplierText" EntityType="API_BUSINESS_PARTNER.A_SupplierTextType" sap:content-version="1"/>
|
||
<EntitySet Name="A_SupplierWithHoldingTax" EntityType="API_BUSINESS_PARTNER.A_SupplierWithHoldingTaxType" sap:content-version="1"/>
|
||
<AssociationSet Name="assoc_20F5EAD3848FBFF2C9E0F6D45CFF1BA9" Association="API_BUSINESS_PARTNER.assoc_20F5EAD3848FBFF2C9E0F6D45CFF1BA9" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_SupplierPurchasingOrg" Role="FromRole_assoc_20F5EAD3848FBFF2C9E0F6D45CFF1BA9"/>
|
||
<End EntitySet="A_SupplierPartnerFunc" Role="ToRole_assoc_20F5EAD3848FBFF2C9E0F6D45CFF1BA9"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_46D370A62F67996B992AE7C09589BEAD" Association="API_BUSINESS_PARTNER.assoc_46D370A62F67996B992AE7C09589BEAD" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_CustomerSalesArea" Role="FromRole_assoc_46D370A62F67996B992AE7C09589BEAD"/>
|
||
<End EntitySet="A_CustomerSalesAreaText" Role="ToRole_assoc_46D370A62F67996B992AE7C09589BEAD"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_68C6FA4D5F974F8BBFCA5D234FA05107" Association="API_BUSINESS_PARTNER.assoc_68C6FA4D5F974F8BBFCA5D234FA05107" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartnerContact" Role="FromRole_assoc_68C6FA4D5F974F8BBFCA5D234FA05107"/>
|
||
<End EntitySet="A_BPContactToAddress" Role="ToRole_assoc_68C6FA4D5F974F8BBFCA5D234FA05107"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_35D5A40C930BECE699C4526B1B1F8D1C" Association="API_BUSINESS_PARTNER.assoc_35D5A40C930BECE699C4526B1B1F8D1C" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartnerAddress" Role="FromRole_assoc_35D5A40C930BECE699C4526B1B1F8D1C"/>
|
||
<End EntitySet="A_AddressPhoneNumber" Role="ToRole_assoc_35D5A40C930BECE699C4526B1B1F8D1C"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_7256A9801E68AE14E59054C2738099F1" Association="API_BUSINESS_PARTNER.assoc_7256A9801E68AE14E59054C2738099F1" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartner" Role="FromRole_assoc_7256A9801E68AE14E59054C2738099F1"/>
|
||
<End EntitySet="A_Supplier" Role="ToRole_assoc_7256A9801E68AE14E59054C2738099F1"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_0DE5F89839F0BD9497F35D85212F05CE" Association="API_BUSINESS_PARTNER.assoc_0DE5F89839F0BD9497F35D85212F05CE" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_Customer" Role="FromRole_assoc_0DE5F89839F0BD9497F35D85212F05CE"/>
|
||
<End EntitySet="A_CustomerTaxGrouping" Role="ToRole_assoc_0DE5F89839F0BD9497F35D85212F05CE"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_07A4C6774A79F32D8C1BDA1CBE5A2FA7" Association="API_BUSINESS_PARTNER.assoc_07A4C6774A79F32D8C1BDA1CBE5A2FA7" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartner" Role="FromRole_assoc_07A4C6774A79F32D8C1BDA1CBE5A2FA7"/>
|
||
<End EntitySet="A_BuPaIdentification" Role="ToRole_assoc_07A4C6774A79F32D8C1BDA1CBE5A2FA7"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_8273BE5CD7CC24B836264946436461DA" Association="API_BUSINESS_PARTNER.assoc_8273BE5CD7CC24B836264946436461DA" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_CustomerCompany" Role="FromRole_assoc_8273BE5CD7CC24B836264946436461DA"/>
|
||
<End EntitySet="A_CustomerDunning" Role="ToRole_assoc_8273BE5CD7CC24B836264946436461DA"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_138939C49DA3F66FEE8C74425F390DD3" Association="API_BUSINESS_PARTNER.assoc_138939C49DA3F66FEE8C74425F390DD3" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_Supplier" Role="FromRole_assoc_138939C49DA3F66FEE8C74425F390DD3"/>
|
||
<End EntitySet="A_SupplierCompany" Role="ToRole_assoc_138939C49DA3F66FEE8C74425F390DD3"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_F9C7FCCBA7A34C05B6E3BFA2C66C2485" Association="API_BUSINESS_PARTNER.assoc_F9C7FCCBA7A34C05B6E3BFA2C66C2485" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_SupplierCompany" Role="FromRole_assoc_F9C7FCCBA7A34C05B6E3BFA2C66C2485"/>
|
||
<End EntitySet="A_SupplierCompanyText" Role="ToRole_assoc_F9C7FCCBA7A34C05B6E3BFA2C66C2485"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_3747E462BFFBB3127682A67959ECC8AA" Association="API_BUSINESS_PARTNER.assoc_3747E462BFFBB3127682A67959ECC8AA" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_CustomerSalesArea" Role="FromRole_assoc_3747E462BFFBB3127682A67959ECC8AA"/>
|
||
<End EntitySet="A_CustSalesPartnerFunc" Role="ToRole_assoc_3747E462BFFBB3127682A67959ECC8AA"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_B60166D8890DDF85A7D581A0BB2D1255" Association="API_BUSINESS_PARTNER.assoc_B60166D8890DDF85A7D581A0BB2D1255" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_CustomerCompany" Role="FromRole_assoc_B60166D8890DDF85A7D581A0BB2D1255"/>
|
||
<End EntitySet="A_CustomerCompanyText" Role="ToRole_assoc_B60166D8890DDF85A7D581A0BB2D1255"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_60DDA2597182EA56C114908472D2FB81" Association="API_BUSINESS_PARTNER.assoc_60DDA2597182EA56C114908472D2FB81" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartnerAddress" Role="FromRole_assoc_60DDA2597182EA56C114908472D2FB81"/>
|
||
<End EntitySet="A_AddressPhoneNumber" Role="ToRole_assoc_60DDA2597182EA56C114908472D2FB81"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_49CF1243367384CB6C19B5648CA1F817" Association="API_BUSINESS_PARTNER.assoc_49CF1243367384CB6C19B5648CA1F817" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_CustomerSalesArea" Role="FromRole_assoc_49CF1243367384CB6C19B5648CA1F817"/>
|
||
<End EntitySet="A_CustomerSalesAreaTax" Role="ToRole_assoc_49CF1243367384CB6C19B5648CA1F817"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_ABC4A572A4A8802D97BA70498CCE4A4E" Association="API_BUSINESS_PARTNER.assoc_ABC4A572A4A8802D97BA70498CCE4A4E" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartnerContact" Role="FromRole_assoc_ABC4A572A4A8802D97BA70498CCE4A4E"/>
|
||
<End EntitySet="A_BPContactToFuncAndDept" Role="ToRole_assoc_ABC4A572A4A8802D97BA70498CCE4A4E"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_EC8BD55FE296CB9F7E96A12A10A83C8A" Association="API_BUSINESS_PARTNER.assoc_EC8BD55FE296CB9F7E96A12A10A83C8A" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BPContactToAddress" Role="FromRole_assoc_EC8BD55FE296CB9F7E96A12A10A83C8A"/>
|
||
<End EntitySet="A_AddressFaxNumber" Role="ToRole_assoc_EC8BD55FE296CB9F7E96A12A10A83C8A"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_70A8B5CCADF265E097DC86BC7B699B31" Association="API_BUSINESS_PARTNER.assoc_70A8B5CCADF265E097DC86BC7B699B31" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_Customer" Role="FromRole_assoc_70A8B5CCADF265E097DC86BC7B699B31"/>
|
||
<End EntitySet="A_CustomerSalesArea" Role="ToRole_assoc_70A8B5CCADF265E097DC86BC7B699B31"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_24C290CBC7FE69574AD9D79A5C631212" Association="API_BUSINESS_PARTNER.assoc_24C290CBC7FE69574AD9D79A5C631212" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartnerAddress" Role="FromRole_assoc_24C290CBC7FE69574AD9D79A5C631212"/>
|
||
<End EntitySet="A_AddressHomePageURL" Role="ToRole_assoc_24C290CBC7FE69574AD9D79A5C631212"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_B7FB1F1D45FB656EF3D9435CA2A39EE9" Association="API_BUSINESS_PARTNER.assoc_B7FB1F1D45FB656EF3D9435CA2A39EE9" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_SupplierPurchasingOrg" Role="FromRole_assoc_B7FB1F1D45FB656EF3D9435CA2A39EE9"/>
|
||
<End EntitySet="A_SupplierPurchasingOrgText" Role="ToRole_assoc_B7FB1F1D45FB656EF3D9435CA2A39EE9"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_DADC7016DBB892642F90D68E0E47B6E8" Association="API_BUSINESS_PARTNER.assoc_DADC7016DBB892642F90D68E0E47B6E8" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartner" Role="FromRole_assoc_DADC7016DBB892642F90D68E0E47B6E8"/>
|
||
<End EntitySet="A_BusinessPartnerTaxNumber" Role="ToRole_assoc_DADC7016DBB892642F90D68E0E47B6E8"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_091DBA85F5FE3E747FC3884B40B4EBFD" Association="API_BUSINESS_PARTNER.assoc_091DBA85F5FE3E747FC3884B40B4EBFD" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartnerAddress" Role="FromRole_assoc_091DBA85F5FE3E747FC3884B40B4EBFD"/>
|
||
<End EntitySet="A_BuPaAddressUsage" Role="ToRole_assoc_091DBA85F5FE3E747FC3884B40B4EBFD"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_55F62B4F505C71EB6E4B122E91DC5745" Association="API_BUSINESS_PARTNER.assoc_55F62B4F505C71EB6E4B122E91DC5745" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_SupplierCompany" Role="FromRole_assoc_55F62B4F505C71EB6E4B122E91DC5745"/>
|
||
<End EntitySet="A_SupplierWithHoldingTax" Role="ToRole_assoc_55F62B4F505C71EB6E4B122E91DC5745"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_91BCE13588BD3046353CD68D3098C2E5" Association="API_BUSINESS_PARTNER.assoc_91BCE13588BD3046353CD68D3098C2E5" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartner" Role="FromRole_assoc_91BCE13588BD3046353CD68D3098C2E5"/>
|
||
<End EntitySet="A_BuPaIndustry" Role="ToRole_assoc_91BCE13588BD3046353CD68D3098C2E5"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_A47744B1176D2172C3109B5E43FFC7F9" Association="API_BUSINESS_PARTNER.assoc_A47744B1176D2172C3109B5E43FFC7F9" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_Supplier" Role="FromRole_assoc_A47744B1176D2172C3109B5E43FFC7F9"/>
|
||
<End EntitySet="A_SupplierText" Role="ToRole_assoc_A47744B1176D2172C3109B5E43FFC7F9"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_BB9464C0EE976A75A05F937B73A26763" Association="API_BUSINESS_PARTNER.assoc_BB9464C0EE976A75A05F937B73A26763" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_Customer" Role="FromRole_assoc_BB9464C0EE976A75A05F937B73A26763"/>
|
||
<End EntitySet="A_CustomerCompany" Role="ToRole_assoc_BB9464C0EE976A75A05F937B73A26763"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_B2EAAC3147A4639C17A2CFEACA07BE23" Association="API_BUSINESS_PARTNER.assoc_B2EAAC3147A4639C17A2CFEACA07BE23" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_Supplier" Role="FromRole_assoc_B2EAAC3147A4639C17A2CFEACA07BE23"/>
|
||
<End EntitySet="A_SupplierPurchasingOrg" Role="ToRole_assoc_B2EAAC3147A4639C17A2CFEACA07BE23"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_43B546339886BBB6ED35EA7CA84FB32B" Association="API_BUSINESS_PARTNER.assoc_43B546339886BBB6ED35EA7CA84FB32B" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartnerAddress" Role="FromRole_assoc_43B546339886BBB6ED35EA7CA84FB32B"/>
|
||
<End EntitySet="A_AddressFaxNumber" Role="ToRole_assoc_43B546339886BBB6ED35EA7CA84FB32B"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_301BF3C95F38823A34CFF6B5A5EF3514" Association="API_BUSINESS_PARTNER.assoc_301BF3C95F38823A34CFF6B5A5EF3514" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_Customer" Role="FromRole_assoc_301BF3C95F38823A34CFF6B5A5EF3514"/>
|
||
<End EntitySet="A_CustomerText" Role="ToRole_assoc_301BF3C95F38823A34CFF6B5A5EF3514"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_5E8DB5909F6A0FD5A1171E3650CDC3F9" Association="API_BUSINESS_PARTNER.assoc_5E8DB5909F6A0FD5A1171E3650CDC3F9" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_SupplierCompany" Role="FromRole_assoc_5E8DB5909F6A0FD5A1171E3650CDC3F9"/>
|
||
<End EntitySet="A_SupplierDunning" Role="ToRole_assoc_5E8DB5909F6A0FD5A1171E3650CDC3F9"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_80838433DCE8E16AA7C9031C32896631" Association="API_BUSINESS_PARTNER.assoc_80838433DCE8E16AA7C9031C32896631" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartner" Role="FromRole_assoc_80838433DCE8E16AA7C9031C32896631"/>
|
||
<End EntitySet="A_Customer" Role="ToRole_assoc_80838433DCE8E16AA7C9031C32896631"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_65B2B550EF37ECC341EC132360E3D0A8" Association="API_BUSINESS_PARTNER.assoc_65B2B550EF37ECC341EC132360E3D0A8" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_CustomerCompany" Role="FromRole_assoc_65B2B550EF37ECC341EC132360E3D0A8"/>
|
||
<End EntitySet="A_CustomerWithHoldingTax" Role="ToRole_assoc_65B2B550EF37ECC341EC132360E3D0A8"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_A30D7A481BC8C28A25685BA876365019" Association="API_BUSINESS_PARTNER.assoc_A30D7A481BC8C28A25685BA876365019" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BPContactToAddress" Role="FromRole_assoc_A30D7A481BC8C28A25685BA876365019"/>
|
||
<End EntitySet="A_AddressPhoneNumber" Role="ToRole_assoc_A30D7A481BC8C28A25685BA876365019"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_313909BAAED14CA9CB4829C648286478" Association="API_BUSINESS_PARTNER.assoc_313909BAAED14CA9CB4829C648286478" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BPContactToAddress" Role="FromRole_assoc_313909BAAED14CA9CB4829C648286478"/>
|
||
<End EntitySet="A_AddressHomePageURL" Role="ToRole_assoc_313909BAAED14CA9CB4829C648286478"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_5D8ED7225F3F084CF706245AFBB65A6A" Association="API_BUSINESS_PARTNER.assoc_5D8ED7225F3F084CF706245AFBB65A6A" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_SupplierCompany" Role="FromRole_assoc_5D8ED7225F3F084CF706245AFBB65A6A"/>
|
||
<End EntitySet="A_Supplier" Role="ToRole_assoc_5D8ED7225F3F084CF706245AFBB65A6A"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_02AC1AF45478434AAB93B18ECA2FB863" Association="API_BUSINESS_PARTNER.assoc_02AC1AF45478434AAB93B18ECA2FB863" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartner" Role="FromRole_assoc_02AC1AF45478434AAB93B18ECA2FB863"/>
|
||
<End EntitySet="A_BusinessPartnerContact" Role="ToRole_assoc_02AC1AF45478434AAB93B18ECA2FB863"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_FB863C7C69262D926CE14CA6A50667DB" Association="API_BUSINESS_PARTNER.assoc_FB863C7C69262D926CE14CA6A50667DB" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartner" Role="FromRole_assoc_FB863C7C69262D926CE14CA6A50667DB"/>
|
||
<End EntitySet="A_BusinessPartnerRole" Role="ToRole_assoc_FB863C7C69262D926CE14CA6A50667DB"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_76A1D4C9690D91482219A96E6133DCA1" Association="API_BUSINESS_PARTNER.assoc_76A1D4C9690D91482219A96E6133DCA1" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BPContactToAddress" Role="FromRole_assoc_76A1D4C9690D91482219A96E6133DCA1"/>
|
||
<End EntitySet="A_AddressEmailAddress" Role="ToRole_assoc_76A1D4C9690D91482219A96E6133DCA1"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_B21DC96A1904D36E94FBE84771BD7E99" Association="API_BUSINESS_PARTNER.assoc_B21DC96A1904D36E94FBE84771BD7E99" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartnerAddress" Role="FromRole_assoc_B21DC96A1904D36E94FBE84771BD7E99"/>
|
||
<End EntitySet="A_AddressEmailAddress" Role="ToRole_assoc_B21DC96A1904D36E94FBE84771BD7E99"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_6247ED959B75350E6EA6CEDD2CBEC7E7" Association="API_BUSINESS_PARTNER.assoc_6247ED959B75350E6EA6CEDD2CBEC7E7" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartner" Role="FromRole_assoc_6247ED959B75350E6EA6CEDD2CBEC7E7"/>
|
||
<End EntitySet="A_BusinessPartnerAddress" Role="ToRole_assoc_6247ED959B75350E6EA6CEDD2CBEC7E7"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_05F0DA10FFAB2836605571E5ABB6E5B9" Association="API_BUSINESS_PARTNER.assoc_05F0DA10FFAB2836605571E5ABB6E5B9" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BusinessPartner" Role="FromRole_assoc_05F0DA10FFAB2836605571E5ABB6E5B9"/>
|
||
<End EntitySet="A_BusinessPartnerBank" Role="ToRole_assoc_05F0DA10FFAB2836605571E5ABB6E5B9"/>
|
||
</AssociationSet>
|
||
<AssociationSet Name="assoc_E5744DCC3F8BA081306832D86DBAE35B" Association="API_BUSINESS_PARTNER.assoc_E5744DCC3F8BA081306832D86DBAE35B" sap:creatable="false" sap:updatable="false" sap:deletable="false" sap:content-version="1">
|
||
<End EntitySet="A_BPContactToAddress" Role="FromRole_assoc_E5744DCC3F8BA081306832D86DBAE35B"/>
|
||
<End EntitySet="A_AddressPhoneNumber" Role="ToRole_assoc_E5744DCC3F8BA081306832D86DBAE35B"/>
|
||
</AssociationSet>
|
||
</EntityContainer>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Common.ApplyMultiUnitBehaviorForSortingAndFiltering" Bool="true"/>
|
||
<Annotation Term="Aggregation.ApplySupported">
|
||
<Record>
|
||
<PropertyValue Property="Transformations">
|
||
<Collection>
|
||
<String>aggregate</String>
|
||
<String>groupby</String>
|
||
<String>filter</String>
|
||
</Collection>
|
||
</PropertyValue>
|
||
<PropertyValue Property="Rollup" EnumMember="None"/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompanyText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.FilterRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="FilterExpressionRestrictions">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="Property" PropertyPath="LongText"/>
|
||
<PropertyValue Property="AllowedExpressions" String="SearchExpression"/>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
<PropertyValue Property="NonFilterableProperties">
|
||
<Collection>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
<Annotation Term="Capabilities.SortRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="NonSortableProperties">
|
||
<Collection>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesAreaText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.FilterRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="FilterExpressionRestrictions">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="Property" PropertyPath="LongText"/>
|
||
<PropertyValue Property="AllowedExpressions" String="SearchExpression"/>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
<PropertyValue Property="NonFilterableProperties">
|
||
<Collection>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
<Annotation Term="Capabilities.SortRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="NonSortableProperties">
|
||
<Collection>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.FilterRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="FilterExpressionRestrictions">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="Property" PropertyPath="LongText"/>
|
||
<PropertyValue Property="AllowedExpressions" String="SearchExpression"/>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
<PropertyValue Property="NonFilterableProperties">
|
||
<Collection>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
<Annotation Term="Capabilities.SortRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="NonSortableProperties">
|
||
<Collection>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompanyText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.FilterRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="FilterExpressionRestrictions">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="Property" PropertyPath="LongText"/>
|
||
<PropertyValue Property="AllowedExpressions" String="SearchExpression"/>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
<PropertyValue Property="NonFilterableProperties">
|
||
<Collection>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
<Annotation Term="Capabilities.SortRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="NonSortableProperties">
|
||
<Collection>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPurchasingOrgText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.FilterRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="FilterExpressionRestrictions">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="Property" PropertyPath="LongText"/>
|
||
<PropertyValue Property="AllowedExpressions" String="SearchExpression"/>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
<PropertyValue Property="NonFilterableProperties">
|
||
<Collection>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
<Annotation Term="Capabilities.SortRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="NonSortableProperties">
|
||
<Collection>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.FilterRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="FilterExpressionRestrictions">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="Property" PropertyPath="LongText"/>
|
||
<PropertyValue Property="AllowedExpressions" String="SearchExpression"/>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
<PropertyValue Property="NonFilterableProperties">
|
||
<Collection>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
<Annotation Term="Capabilities.SortRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="NonSortableProperties">
|
||
<Collection>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
<PropertyPath>LongText</PropertyPath>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner general data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves general data fields of all the business partner records available in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner data by using business partner number."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves the general data fields of the business partner record by using business partner number."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new business partner record."/>
|
||
<PropertyValue Property="LongDescription" String="Creates a business partner including Customer, Supplier, Address, Role, Tax, Bank, Identification, Contact, and Industry data."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates business partner general data."/>
|
||
<PropertyValue Property="LongDescription" String="Updates business partner general data by using business partner number."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Customer" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer general data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves general data of all the customer records available in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer data by using customer number."/>
|
||
<PropertyValue Property="LongDescription" String="Retreives the general data of the customer record by using customer number."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Customer" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates customer general data."/>
|
||
<PropertyValue Property="LongDescription" String="Updates customer general data by using customer number."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Supplier" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier general data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves general data of all the supplier records available in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier general data by using supplier number."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves the general data of the supplier record by using supplier number."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Supplier" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates supplier general data."/>
|
||
<PropertyValue Property="LongDescription" String="Updates supplier general data by using supplier number."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner address data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner address data fields of all the available records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner address data by using the key field."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner address data by using business partner number and address ID."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new address data for an existing business partner."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new address data for an existing business partner. Address ID is automatically generated."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates business partner address data."/>
|
||
<PropertyValue Property="LongDescription" String="Updates business partner address data of the record identified by address ID and business partner number."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes business partner address record identified by address ID and business partner number."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes address data of the business partner including Phone, Fax, Email, URI, and Usage data."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerRole" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner role data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner role data fields of all the records available records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner role data using the key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner role data using business partner number and business partner role."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerRole" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new role for an existing business partner."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new role to the existing business partner record with role and validity details."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerRole" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates role data fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates role validity data identified by business partner number and business partner role."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerTaxNumber" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner tax number data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves tax number data of all the available records linked to business partners in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner tax number data by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves tax number data by using the key fields such as business partner number and tax type."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerTaxNumber" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new tax number data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates a new tax number data linked to an existing business partner."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerTaxNumber" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates tax number data linked to a business partner."/>
|
||
<PropertyValue Property="LongDescription" String="Updates tax number data identified by key fields such as business partner number and tax type."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerTaxNumber" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes tax number data linked to a business partner."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes tax number data identified by key fields such as business partner number and tax type."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerBank" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner bank data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner bank data fields of all the available records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner bank data by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner bank data identified by key fields such as business partner number and bank dentification."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerBank" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new business partner bank data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates new business partner bank data linked to business partner."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerBank" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates business partner bank data."/>
|
||
<PropertyValue Property="LongDescription" String="Updates bank data of the business partner record identified by business partner number and bank identification."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerBank" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes business partner bank data."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes bank data of the business partner record identified by business partner number and bank identification."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BuPaIdentification" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner identification data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner identification data fields of all the records available records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner identification data by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner identification data using business partner number, identification type, and identification number."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BuPaIdentification" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new business partner identification data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates new identification data record linked to business partner."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BuPaIdentification" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates business partner identification data."/>
|
||
<PropertyValue Property="LongDescription" String="Updates business partner identification data by using business partner number, identification type, and identification number."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BuPaIdentification" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes business partner identification data."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes business partner identification data by using business partner number, identification type, and identification number."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerContact" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner contact data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner contact data fields of all the available records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner contact data by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner contact data using relationship number, BusinessPartnerCompany, BusinessPartnerPerson and ValidityEndDate"/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerContact" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new business partner contact relationship data of type 'BUR001'"/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new business partner contact relationship data of type 'BUR001' to the business partner."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerContact" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates business partner contact data."/>
|
||
<PropertyValue Property="LongDescription" String="Updates business partner contact data by RelationshipNumber, BusinessPartnerCompany, BusinessPartnerPerson and ValidityEndDate"/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerContact" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes business partner contact data by by RelationshipNumber, BusinessPartnerCompany, BusinessPartnerPerson and ValidityEndDate"/>
|
||
<PropertyValue Property="LongDescription" String="Removes the contact person relationship assigned to the business partner by using the key fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BuPaIndustry" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner industry data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner industry data fields of all the available records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner industry data by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner industry data by using industry sector, industry system type and business partner number"/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BuPaIndustry" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates industry data linked to business partner record."/>
|
||
<PropertyValue Property="LongDescription" String="Assigns new industry data to the business partner record."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BuPaIndustry" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates business partner industry data."/>
|
||
<PropertyValue Property="LongDescription" String="Updates business partner industry data by industry sector, industry system type and business partner number"/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BuPaIndustry" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes business partner industry data."/>
|
||
<PropertyValue Property="LongDescription" String="Removes industry data linked to the business partner record identified by IndustrySector, IndustrySystemType, and BusinessPartner."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesArea" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer sales area data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer sales area data fields of all the available records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer sales area data by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer sales area data by using Customer, SalesOrganization, DistributionChannel and Division."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesArea" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates customer sales data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates sales data linked to a customer including Sales Area Tax, Partner Functions, and Sales Area Text."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesArea" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates customer sales data."/>
|
||
<PropertyValue Property="LongDescription" String="Updates sales data identified by Customer, SalesOrganization, DistributionChannel and Division."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesAreaTax" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer sales area tax data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer sales area tax data fields of all the available records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer sales area tax data using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Get sales area tax data by Customer, SalesOrganization, DistributionChannel, Division, DepartureCountry and CustomerTaxCategory"/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesAreaTax" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates customer sales area tax data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates customer sales area tax data in the sales record linked to the customer."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesAreaTax" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes customer sales area tax data."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes customer sales area tax data from the sales record linked to the customer."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustSalesPartnerFunc" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer sales area partner function records."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves partner function fields of all the available records in the system linked to customer sales areas."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves sales area partner function data by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves partner function data by Customer, SalesOrganization, DistributionChannel, Division, PartnerCounter, and PartnerFunction."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustSalesPartnerFunc" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new partner function record linked to customer sales area."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new partner function record. Partner counter will be automatically determined if a similar partner function already exist."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustSalesPartnerFunc" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates partner function record linked to customer sales area"/>
|
||
<PropertyValue Property="LongDescription" String="Updates partner function record by Customer, SalesOrganization, DistributionChannel, Division, PartnerCounter and PartnerFunction"/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustSalesPartnerFunc" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes partner function record linked to customer sales area."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes partner function record by Customer, SalesOrganization, DistributionChannel, Division, PartnerCounter and PartnerFunction"/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesAreaText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer sales area text data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer sales area text fields of all the available records in the system linked to customer sales areas."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer sales area text data by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retreives customer sales area text data by Customer, SalesOrganization, DistributionChannel, Division, and Language."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesAreaText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new customer sales area text data."/>
|
||
<PropertyValue Property="LongDescription" String="Adds new sales area text record in the language specified. If no language is specified, the text will be created in system language."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesAreaText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates sales area text record linked to customer sales area."/>
|
||
<PropertyValue Property="LongDescription" String="Updates customer sales area text data identified by Customer, SalesOrganization, DistributionChannel, Division and Language"/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesAreaText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes sales area text data linked to customer sales area."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes customer sales area text data identified by Customer, SalesOrganization, DistributionChannel, Division, and Language."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer company data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer company data fields of all the available records in the system linked to customer."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer company data by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer company data by key fields such as customer and company code."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new company code data linked to the customer."/>
|
||
<PropertyValue Property="LongDescription" String="Assigns company code data to a customer. A customer can be assigned to multiple company records."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates company code data linked to the customer."/>
|
||
<PropertyValue Property="LongDescription" String="Updates company code data linked to the customer by customer and company code."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerDunning" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves dunning records attached to customer company."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the dunning records attached to customer company in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves all the dunning records by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the dunning records by customer, company code, and dunning area."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerDunning" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new dunning record attached to customer company."/>
|
||
<PropertyValue Property="LongDescription" String="Assigns a new dunning record to a customer company code."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerDunning" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates customer company code dunning record."/>
|
||
<PropertyValue Property="LongDescription" String="Updates customer company code dunning record identified by key fields such as Customer, CompanyCode, and Dunning Area."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerDunning" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates customer company code dunning record by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes customer company code dunning record identified by key fields such as Customer, CompanyCode, and Dunning Area."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerWithHoldingTax" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer withholding tax records attached to customer company."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the withholding tax records attached to customer company in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer withholding tax records by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer withholding tax records by customer, company code, and withholding tax type."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerWithHoldingTax" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new customer withholding tax record."/>
|
||
<PropertyValue Property="LongDescription" String="Creates customer withholding tax record linked to customer company."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerWithHoldingTax" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates customer company withholding tax record."/>
|
||
<PropertyValue Property="LongDescription" String="Updates customer withholding tax record linked to customer company by fields such as Customer, CompanyCode and WithholdingTaxType"/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerWithHoldingTax" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes customer withholding tax record linked to customer company by customer, customer company, withholding tax."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes customer withholding tax record linked to customer company by fields such as Customer, CompanyCode, and WithholdingTaxType"/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompanyText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer company text records attached to company data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the customer company text records attached to customer company in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer company text data by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer company text data by using the fields Customer, CompanyCode, Language and LongTextID."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompanyText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates customer company text data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates text data linked to customer company."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompanyText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates customer company text data."/>
|
||
<PropertyValue Property="LongDescription" String="Updates text data linked to customer company by using fields Customer, CompanyCode, Language and LongTextID."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompanyText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes customer company text data."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes text data linked to customer company by using the fields Customer, CompanyCode, Language and LongTextID."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer text data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all customer text data attached to a customer in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer text records using the key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer text records by using Customer, Language, and LongTextID fields."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates customer long text."/>
|
||
<PropertyValue Property="LongDescription" String="Creates text data attached to a customer in the system."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates customer text records by using the key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates customer text records by using Customer, Language, and LongTextID fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes customer text records by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes customer text records by Customer, Language, and LongTextID fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerTaxGrouping" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer tax grouping data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the customer tax grouping data attached to a customer in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer tax grouping records using the key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer tax grouping records by using Customer and CustomerTaxGroupingCode."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerTaxGrouping" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates customer tax grouping records using the key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates customer tax grouping records by Customer and CustomerTaxGroupingCode."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerTaxGrouping" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes customer tax grouping records by using the key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes customer tax grouping records by Customer and CustomerTaxGroupingCode."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier company data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all supplier company data available in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier company data using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves supplier company data by using Supplier and CompanyCode fields."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates supplier company data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates supplier company data including Dunning, WithholdingTax, and Text data."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates supplier company data using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates supplier company data by using Supplier and CompanyCode fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierDunning" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves dunning records attached to supplier company data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the dunning records attached to supplier company in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier dunning records by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the dunning records by using Supplier, CompanyCode, and DunningArea fields."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierDunning" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new dunning records attached to supplier company."/>
|
||
<PropertyValue Property="LongDescription" String="Assigns a new dunning records to a supplier company code."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierDunning" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates supplier company code dunning data using the key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates dunning data of a supplier company record identified by Supplier, CompanyCode, and DunningArea fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierDunning" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes supplier company code dunning record by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes supplier company code dunning record identified by Supplier, CompanyCode, and DunningArea fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierWithHoldingTax" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier withholding tax records."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all withholding tax records attached to supplier company in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier withholding tax records by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves supplier withholding tax records by Supplier, CompanyCode, and WithholdingTaxType fields."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierWithHoldingTax" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new supplier witholding tax data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates supplier withholding tax record linked to supplier company data."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierWithHoldingTax" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates supplier company withholding tax records using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates supplier withholding tax data linked to supplier company by using Supplier, CompanyCode, and WithholdingTaxType fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierWithHoldingTax" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes supplier withholding tax data."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes supplier withholding tax data linked to supplier company by using Supplier, CompanyCode, and WithholdingTaxType fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompanyText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier company text data attached to company data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the supplier company text data attached to supplier company in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier company text data by using the key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves supplier company text data by using Supplier, CompanyCode, Language and LongTextID fields."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompanyText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates supplier company text data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates text data attached to a supplier company in the system."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompanyText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates supplier company text data."/>
|
||
<PropertyValue Property="LongDescription" String="Updates text data linked to supplier company by using Supplier, CompanyCode, Language, and LongTextID fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompanyText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes supplier company text data."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes text record linked to supplier company by Supplier, CompanyCode, Language, and LongTextID fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPurchasingOrg" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier purchasing organization data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the supplier purchasing organization data attached to supplier records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier purchasing organization data by using the key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves supplier purchasing organization data by using Supplier and PurchasingOrganization fields."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPurchasingOrg" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates supplier purchasing organization data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates supplier purchasing organization data including PartnerFunctions and Text data."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPurchasingOrg" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates supplier purchasing organization data by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates supplier purchasing organization record by Supplier and PurchasingOrganization fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPartnerFunc" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier purchasing organization partner function records."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves partner function fields of all the available records in the system linked to supplier purchasing organization"/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier purchasing organization partner function data by using the key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves partner function data by Supplier, PurchasingOrganization, SupplierSubrange, Plant, PartnerCounter, and PartnerFunction."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPartnerFunc" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new partner function data linked to supplier purchasing organization."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new partner function record. Partner Counter will be automatically determined if a similar partner function already exists."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPartnerFunc" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates partner function record linked to supplier purchasing organization by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates partner function record by Supplier, PurchasingOrganization, SupplierSubrange, Plant, PartnerCounter, and PartnerFunction."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPartnerFunc" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes partner function record linked to supplier purchasing organization."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes partner function record by Supplier, PurchasingOrganization, SupplierSubrange, Plant, PartnerCounter and PartnerFunction"/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPurchasingOrgText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier purchasing organization text data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the supplier purchasing organization text data attached to purchasing organization in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier purchasing organization text data by using the key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves supplier purchasing organization text data using Supplier, PurchasingOrganization, Language, and LongTextID"/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPurchasingOrgText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates supplier purchasing organization text data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates text data attached to a supplier purchasing organization in the system."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPurchasingOrgText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates supplier purchasing organization text data using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates text data linked to purchasing organization by using Supplier, PurchasingOrganization, Language, and LongTextID fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPurchasingOrgText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes supplier purchasing organization text data by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes text data linked to purchasing organization by Supplier, PurchasingOrganization, Language, and LongTextID."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier text data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the supplier text data attached to purchasing organization in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier text data by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves supplier purchasing organization text data by using Supplier, Language, and LongTextID fields."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates supplier text data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates text data attached to a supplier in the system."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates supplier text data by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates text data linked to supplier by using Supplier, Language and LongTextID fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierText" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes supplier text data by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes text data linked to supplier by Supplier, Language, and LongTextID fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressEmailAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves email address data linked to business partner address fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the email address data linked to all business partner address records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves email address data by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves email address data by using AddressID, Person and OrdinalNumber fields."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressEmailAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new email address data for the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new email address data for the existing business partner address record. Multiple emails can be linked to an address record."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressEmailAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates email address record by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates business partner email address data of the record identified by AddressID, Person and OrdinalNumber fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressEmailAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes email address record by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes business partner email address data of the record identified by AddressID, Person, and OrdinalNumber."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressFaxNumber" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves fax address data linked to business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the fax address data linked to all the business partner address records in the system"/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves fax address records by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves fax address records by AddressID, Person, and OrdinalNumber field."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressFaxNumber" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new fax address data for the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new fax address record for the existing business partner address record. Multiple fax can be linked to an address record."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressFaxNumber" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates fax address record by key field."/>
|
||
<PropertyValue Property="LongDescription" String="Updates business partner fax address data of the record identified by AddressID, Person, and OrdinalNumber."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressFaxNumber" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes fax address record by key field."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes business partner fax address data of the record identified by AddressID, Person and OrdinalNumber."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressHomePageURL" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves home page URL address records linked to business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the home page URL address records linked to all business partner address records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves home page URL address records by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves home page URL address records by using AddressID, Person, and OrdinalNumber fields."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressHomePageURL" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new home page URL address record to the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new home page URL to the existing business partner address record. Multiple URLs can be linked to an address record."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressHomePageURL" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates home page URL address record by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates business partner home page URL address data of the record identified by AddressID, Person, and OrdinalNumber."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressHomePageURL" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes home page URL address record by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes business Partner home page URL address data of the record identified by AddressID, Person, and OrdinalNumber"/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressPhoneNumber" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves mobile/telephone address records linked to business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the mobile/telephone address records linked to all the business partner address records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves mobile/telephone address record by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retreives mobile/telephone address record by AddressID, Person and OrdinalNumber."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressPhoneNumber" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new mobile/telephone address record for the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new mobile/telephone record for the existing business partner address records. Multiple records can be linked to an address."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressPhoneNumber" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates mobile/telephone address records by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates business partner mobile/telephone address data of the record identified by AddressID, Person, and OrdinalNumber."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_AddressPhoneNumber" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes mobile/telephone address records by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Delete business partner mobile/telephone address data of the record identified by AddressID, Person, and OrdinalNumber fields."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BuPaAddressUsage" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves address usage linked to business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the address usage records linked to all business partner address records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves address usage record by key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves address usage record linked to a business partner address by BusinessPartner, ValidityEndDate, AddressUsage and AddressID."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BuPaAddressUsage" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates an address usage record linked to a existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Assigns address usage data to existing business partner address."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BuPaAddressUsage" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates address usage record by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Updates address usage record by BusinessPartner, ValidityEndDate, AddressUsage and AddressID."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BuPaAddressUsage" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.DeleteRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Deletes address usage record by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Deletes address usage record by BusinessPartner, ValidityEndDate, AddressUsage and AddressID."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BPContactToAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves workplace address records linked to business partner contact."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the workplace address records linked to all the business partner contact records in the system."/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves contact person workplace address record by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves workplace address record by RelationshipNumber, BusinessPartnerCompany, BusinessPartnerPerson and ValidityEndDate."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BPContactToFuncAndDept" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves contact person department and function data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the contact person department and function data linked to all business partner contact records in the system"/>
|
||
<PropertyValue Property="ReadByKeyRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves contact person department and function data by using key fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves department and function record by RelationshipNumber, BusinessPartnerCompany, BusinessPartnerPerson, and ValidityEndDate."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BPContactToFuncAndDept" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.UpdateRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Updates contact person department and function data record by key field."/>
|
||
<PropertyValue Property="LongDescription" String="Updates department and function data by RelationshipNumber, BusinessPartnerCompany, BusinessPartnerPerson, and ValidityEndDate."/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BusinessPartnerAddress"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner address data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner address data fields of all the available records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BusinessPartnerAddress"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new address data for an existing business partner."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new address data for an existing business partner. Address ID is automatically generated."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BusinessPartnerRole"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner role data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner role data fields of all the records available records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BusinessPartnerRole"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new role for an existing business partner."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new role to the existing business partner record with role and validity details."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BusinessPartnerTax"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner tax number data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves tax number data of all the available records linked to business partners in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BusinessPartnerTax"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new tax number data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates a new tax number data linked to an existing business partner."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BusinessPartnerBank"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner bank data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner bank data fields of all the available records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BusinessPartnerBank"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new business partner bank data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates new business partner bank data linked to business partner."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BuPaIdentification"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner identification data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner identification data fields of all the records available records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BuPaIdentification"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new business partner identification data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates new identification data record linked to business partner."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BusinessPartnerContact"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner contact data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner contact data fields of all the available records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BusinessPartnerContact"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new business partner contact relationship data of type 'BUR001'"/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new business partner contact relationship data of type 'BUR001' to the business partner."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BuPaIndustry"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves business partner industry data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves business partner industry data fields of all the available records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_BuPaIndustry"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates industry data linked to business partner record."/>
|
||
<PropertyValue Property="LongDescription" String="Assigns new industry data to the business partner record."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_Customer"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer general data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves general data of all the customer records available in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartner" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_Supplier"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier general data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves general data of all the supplier records available in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Customer" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_CustomerSalesArea"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer sales area data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer sales area data fields of all the available records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Customer" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_CustomerSalesArea"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates customer sales data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates sales data linked to a customer including Sales Area Tax, Partner Functions, and Sales Area Text."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Customer" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_CustomerCompany"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer company data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer company data fields of all the available records in the system linked to customer."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Customer" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_CustomerCompany"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new company code data linked to the customer."/>
|
||
<PropertyValue Property="LongDescription" String="Assigns company code data to a customer. A customer can be assigned to multiple company records."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Customer" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_CustomerText"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer text data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all customer text data attached to a customer in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Customer" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_CustomerText"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates customer long text."/>
|
||
<PropertyValue Property="LongDescription" String="Creates text data attached to a customer in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Customer" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_CustomerTaxGrouping"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer tax grouping data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the customer tax grouping data attached to a customer in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesArea" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesAreaTax"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer sales area data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer sales area data fields of all the available records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesArea" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesAreaTax"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer sales area tax data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer sales area tax data fields of all the available records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesArea" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PartnerFunction"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer sales area partner function records."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves partner function fields of all the available records in the system linked to customer sales areas."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesArea" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PartnerFunction"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new partner function record linked to customer sales area."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new partner function record. Partner counter will be automatically determined if a similar partner function already exist."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesArea" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesAreaText"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer sales area text data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves customer sales area text fields of all the available records in the system linked to customer sales areas."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerSalesArea" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SalesAreaText"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new customer sales area text data."/>
|
||
<PropertyValue Property="LongDescription" String="Adds new sales area text record in the language specified. If no language is specified, the text will be created in system language."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_CustomerDunning"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves dunning records attached to customer company."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the dunning records attached to customer company in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_CustomerDunning"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new dunning record attached to customer company."/>
|
||
<PropertyValue Property="LongDescription" String="Assigns a new dunning record to a customer company code."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_WithHoldingTax"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer withholding tax records attached to customer company."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the withholding tax records attached to customer company in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_WithHoldingTax"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new customer withholding tax record."/>
|
||
<PropertyValue Property="LongDescription" String="Creates customer withholding tax record linked to customer company."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_CompanyText"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves customer company text records attached to company data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the customer company text records attached to customer company in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_CustomerCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_CompanyText"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates customer company text data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates text data linked to customer company."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Supplier" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SupplierCompany"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier company data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all supplier company data available in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Supplier" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SupplierCompany"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates supplier company data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates supplier company data including Dunning, WithholdingTax, and Text data."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Supplier" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SupplierPurchasingOrg"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier purchasing organization data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the supplier purchasing organization data attached to supplier records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Supplier" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SupplierPurchasingOrg"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates supplier purchasing organization data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates supplier purchasing organization data including PartnerFunctions and Text data."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Supplier" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SupplierText"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier text data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the supplier text data attached to purchasing organization in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_Supplier" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SupplierText"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates supplier text data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates text data attached to a supplier in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SupplierDunning"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves dunning records attached to supplier company data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the dunning records attached to supplier company in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SupplierDunning"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new dunning records attached to supplier company."/>
|
||
<PropertyValue Property="LongDescription" String="Assigns a new dunning records to a supplier company code."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SupplierWithHoldingTax"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier withholding tax records."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all withholding tax records attached to supplier company in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_SupplierWithHoldingTax"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates new supplier witholding tax data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates supplier withholding tax record linked to supplier company data."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_CompanyText"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier company text data attached to company data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the supplier company text data attached to supplier company in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_CompanyText"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates supplier company text data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates text data attached to a supplier company in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPurchasingOrg" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PartnerFunction"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier purchasing organization partner function records."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves partner function fields of all the available records in the system linked to supplier purchasing organization"/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPurchasingOrg" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PartnerFunction"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new partner function data linked to supplier purchasing organization."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new partner function record. Partner Counter will be automatically determined if a similar partner function already exists."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPurchasingOrg" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PurchasingOrgText"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier purchasing organization text data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the supplier purchasing organization text data attached to purchasing organization in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierPurchasingOrg" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PurchasingOrgText"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates supplier purchasing organization text data."/>
|
||
<PropertyValue Property="LongDescription" String="Creates text data attached to a supplier purchasing organization in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PhoneNumber"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves mobile/telephone address records linked to business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the mobile/telephone address records linked to all the business partner address records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PhoneNumber"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new mobile/telephone address record for the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new mobile/telephone record for the existing business partner address records. Multiple records can be linked to an address."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_MobilePhoneNumber"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves mobile/telephone address records linked to business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the mobile/telephone address records linked to all the business partner address records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_MobilePhoneNumber"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new mobile/telephone address record for the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new mobile/telephone record for the existing business partner address records. Multiple records can be linked to an address."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_FaxNumber"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves fax address data linked to business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the fax address data linked to all the business partner address records in the system"/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_FaxNumber"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new fax address data for the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new fax address record for the existing business partner address record. Multiple fax can be linked to an address record."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_EmailAddress"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves email address data linked to business partner address fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the email address data linked to all business partner address records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_EmailAddress"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new email address data for the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new email address data for the existing business partner address record. Multiple emails can be linked to an address record."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_URLAddress"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves home page URL address records linked to business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the home page URL address records linked to all business partner address records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_URLAddress"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new home page URL address record to the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new home page URL to the existing business partner address record. Multiple URLs can be linked to an address record."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_AddressUsage"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves address usage linked to business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the address usage records linked to all business partner address records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_AddressUsage"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates an address usage record linked to a existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Assigns address usage data to existing business partner address."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerContact" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_ContactAddress"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves workplace address records linked to business partner contact."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the workplace address records linked to all the business partner contact records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BusinessPartnerContact" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_ContactRelationship"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves contact person department and function data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the contact person department and function data linked to all business partner contact records in the system"/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BPContactToAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_EmailAddress"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves email address data linked to business partner address fields."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the email address data linked to all business partner address records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BPContactToAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_EmailAddress"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new email address data for the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new email address data for the existing business partner address record. Multiple emails can be linked to an address record."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BPContactToAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_FaxNumber"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves fax address data linked to business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the fax address data linked to all the business partner address records in the system"/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BPContactToAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_FaxNumber"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new fax address data for the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new fax address record for the existing business partner address record. Multiple fax can be linked to an address record."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BPContactToAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_URLAddress"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves home page URL address records linked to business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the home page URL address records linked to all business partner address records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BPContactToAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_URLAddress"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new home page URL address record to the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new home page URL to the existing business partner address record. Multiple URLs can be linked to an address record."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BPContactToAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PhoneNumber"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves mobile/telephone address records linked to business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the mobile/telephone address records linked to all the business partner address records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BPContactToAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_PhoneNumber"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new mobile/telephone address record for the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new mobile/telephone record for the existing business partner address records. Multiple records can be linked to an address."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BPContactToAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_MobilePhoneNumber"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves mobile/telephone address records linked to business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves all the mobile/telephone address records linked to all the business partner address records in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_BPContactToAddress" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_MobilePhoneNumber"/>
|
||
<PropertyValue Property="InsertRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Creates a new mobile/telephone address record for the existing business partner address."/>
|
||
<PropertyValue Property="LongDescription" String="Adds a new mobile/telephone record for the existing business partner address records. Multiple records can be linked to an address."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities/A_SupplierCompany" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Capabilities.NavigationRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="RestrictedProperties">
|
||
<Collection>
|
||
<Record>
|
||
<PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_Supplier"/>
|
||
<PropertyValue Property="ReadRestrictions">
|
||
<Record>
|
||
<PropertyValue Property="Description" String="Retrieves supplier general data."/>
|
||
<PropertyValue Property="LongDescription" String="Retrieves general data of all the supplier records available in the system."/>
|
||
</Record>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Collection>
|
||
</PropertyValue>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<Annotations Target="API_BUSINESS_PARTNER.API_BUSINESS_PARTNER_Entities" xmlns="http://docs.oasis-open.org/odata/ns/edm">
|
||
<Annotation Term="Org.OData.Capabilities.V1.BatchSupport">
|
||
<Record Type="Org.OData.Capabilities.V1.BatchSupportType">
|
||
<PropertyValue Property="ReferencesAcrossChangeSetsSupported" Bool="true"/>
|
||
</Record>
|
||
</Annotation>
|
||
</Annotations>
|
||
<atom:link rel="self" href="https://host:port/sap/opu/odata/sap/API_BUSINESS_PARTNER/$metadata" xmlns:atom="http://www.w3.org/2005/Atom"/>
|
||
<atom:link rel="latest-version" href="https://host:port/sap/opu/odata/sap/API_BUSINESS_PARTNER/$metadata" xmlns:atom="http://www.w3.org/2005/Atom"/>
|
||
</Schema>
|
||
</edmx:DataServices>
|
||
</edmx:Edmx>
|