SAP Cloud for Customer里BusinessPartner, Customer和Employee这些BO的区别

A person, an organization, or a group of persons or organizations, in which a company has a business interest.

Business Context and Use

The Business Partner business object provides business partner master data that is used independently of the application-specific business processes. A business partner can therefore have various functions that do not depend directly on business processes in sales or purchases.
The business object predominantly contains general business partner data such as:

Roles

Relationships

Addresses

Identification

Bank details

A business partner can have different roles, for example:

Contact person

Competitor

Sales and service partner

Carrier

SAP Cloud for Customer里BusinessPartner, Customer和Employee这些BO的区别

未定义access context.

Customer

SAP Cloud for Customer里BusinessPartner, Customer和Employee这些BO的区别

Access context

1004 -Personal Work

1010 -Employee

1015 -Employee, Territory, Account, Sales Data

Definition

A business partner to whom materials or services are offered or provided.

Business Context and Use

The Customer business object provides business partner master data that is used in the context of selling materials and services. A customer can have all those functions that a business partner performs for sales-related business processes.

In addition to the general business partner data such as address data, roles, relationship data, and bank details, the business object provides data that is required for the processes such as:

Operating hours - This includes information about when a business partner can be contacted (visiting hours, calling hours, and goods receiving hours of a customer).

Capital investment - This includes attributes of the shareholder relationship such as the principal and the percentage of the investment.

Contact person data
This includes identification data and address data of the two partners in a contact person relationship.

3.1 Industry sector to which the customer is assigned

3.2 Marketing data

This includes attributes that are relevant for marketing processes, such as the Nielsen ID.

A customer can, depending on the various business processes in which it is involved, have different roles, for example:

Prospect

Customer

使用代码创建Customer BO实例的一些注意事项

When you interact with the Customer business object, there are some details you need to consider.

Customer Root Node and Category Code

The root node of a customer is created automatically by the PDI when you create an instance of the Customer business object. When you create a customer, you must define the customer\'s category code. This must be either a “person” or an “organization”.

If the customer is a person, it is mandatory to fill in the “FamilyName”.

If the customer is an organization, it is mandatory to fill in the “OrganizationalName”; technically, the fieldname is “FirstLineName”.

Role Code

As a prerequisite, a customer must also have a role code, defined by the attributes “Customer Indicator” or “Prospect Indicator” as described in the chapter “Business Context and Use”. The customer must be of either the "customer" or "prospect" role. This role can be changed at any time.

Example: Creating a Customer

The following example demonstrates how to create a new customer of the category “person” and role “customer” with the family name “Testname”.

Prerequisites

The category code must be either “person” or “organization”; in this example, “person” is used.

The role must be set; in this case, it is set to “customer”.

If customizing is set to an internal number range, then the ID need not be provided by the user. Instead, the internal ID is generated in the backend.

However, if customizing requires that the ID be set externally, the ID must be conform to the number range. Then the ID is set externally (i.e. by the user) and automatically approved and saved by the backend.

例子:

import ABSL; import AP.FO.BusinessPartner.Global; import AP.FO.Address.Global; // define root node var elCustomerRoot: elementsof Customer; var newCustomer; // define common node - person var elCustomerPerson: elementsof Customer.Common.Person; //create root instance and set parameter CategoryCode. // CategoryCode = "1" = Person, // CategoryCode = "2" = Organization. elCustomerRoot.CategoryCode = "1"; newCustomer = Customer.Create(elCustomerRoot); //if new instance was set, set relation from this BO to BO Customer: if ( newCustomer.IsSet() ) { this.toCustomer = newCustomer;} else { raise BOCreationFailed.Create("E", this.ID); } // Filling node CurrentBusinessCharacters with aim at variable CustomerIndicator, which is manadatory! // CustomerIndicator = true, then Person is customer // OR ProspectIndicator = true, then Person is prospect newCustomer.CurrentBusinessCharacters.CustomerIndicator = true; // node Person-Name: Field PersonFamilyName is mandatory newCustomer.CurrentCommon.Person.Name.FamilyName = “Testname”; 使用query 读取customer数据的代码: import import ABSL; import AP.FO.BusinessPartner.Global; // Define variables var query; var selParams; var queryResult; // define query and selection parameter query = Customer.QueryByIdentification; selParams = query.CreateSelectionParams(); // Retrieve customer by query identification selParams.Add(query.InternalID,"I","EQ", “1000480”); queryResult = query.Execute(selParams); foreach (Customer in queryResult) { this.PersonFamilyName = Customer.CurrentCommon.Person.Name.FamilyName; 只有状态为Active的Customer才能参与到Sales流程中来

内容版权声明:除非注明,否则皆为本站原创文章。

转载注明出处:https://www.heiqu.com/zzfwxs.html