Ansicht
Dokumentation

CRMC_PARTNER_AS - Define Access Sequences

General Material Data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

In this Customizing activity, you define access sequences that are used in partner determination. You can either define access sequences manually or use the wizard Create Access Sequence.

An access sequence is a search strategy that specifies the sources of data and the order in which the system checks these sources, when it determines partners in business transactions.

You specify which source the system should check first, and list other possible sources. If the system cannot determine a partner from the first source, it checks the next source on the list.

You tell the system which partner to search for by assigning the access sequence to a partner function. The system then searches for a partner with that function. To assign access sequences to partner functions in Customizing, choose Define Partner Determination Procedure.

You have defined partner functions.

Before defining new access sequences, check if you can use existing ones, which cover many common situations in partner determination.

Avoid changing the existing access sequences. Instead, copy them and change the copies.

Use the wizard to create new access sequences.

The system includes commonly used access sequences and pre-defined sources.

Examples of sources:

• Business Partner Relationships and Business Partner Relationships by Sales Organization

• These relationships defined in business partner master data, can be either general or sales organization-specific. If business partner relationships by sales organization is the source, the system looks in the relationships defined for the sales organization involved in the current transaction.

• When you use these sources, you must tell the system which relationships you mean. For example, should the system look in the relationships entered for the sold-to party, the ship-to party or the payer? You do this by maintaining one of the fields in the group box Details on the Source.

• Organizational Data

• The organizational data defined in master data. When you choose this source, you must enter a determination rule for organizational data.

• If you do not maintain Details on the Source, the system uses the organizational data of the main partner in the transaction, such as the sold-to party in a sales transaction, or the sales prospect in an opportunity.

• Pricing Hierarchy

• Pricing hierarchies are group hierarchies, defined in business partner master data and marked as pricing-relevant, that contain partners to whom pricing conditions are assigned. Use this source to carry out pricing based on a hierarchy belonging to a partner other than the sold-to party, or when you want to be able to display the hierarchy tree from within the transaction.

• If you do not maintain Details on the Source, the system uses the pricing hierarchy of the main partner in the transaction.

• Preceding Document

• The transaction document that came before the current one. For example, if an end user is creating a sales order, and the preceding document was an opportunity, the system uses the opportunity as the source for partner data.

• Business Partner Assigned to the User

• Users also exist as business partners in the system. This source is the business partner master data maintained for the user who is logged on to the system when partner determination occurs.

• Current Partner

• A partner included in the current transaction document. For example, you choose current partner as the source, and assign the access sequence to the ship-to party. An end user then creates a document and enters Johnson Electronics as the sold-to party. The system enters Johnson Electronics as the ship-to party as well.

• Own Products

• You use this source for business transactions in Opportunity Management. You maintain information on competitors and competitor products in your Business Partner Master Data and use the source to enable automatic determination of this information in the transaction.

Access sequence descriptions

The description of an access sequence lists the sources, separated by arrows (->), included in that access sequence. In some cases, it also lists a partner function or partner function category. This indicates either that the system looks for a particular function or category in the source (Mapping), or that it looks in the data maintained for a partner with that function or category (Details on the Source). Open the access sequences and look at the single accesses for detailed information.

Examples of descriptions and what they mean

Here are examples of access sequence descriptions with explanations of how the system behave during partner determination:

• Preceding document: Activity partner → Preceding document: Sold-to party

• The system first looks in the preceding document for an activity partner. If it does not find one, it looks in the preceding document again, but this time for a sold-to party. In the transaction, it enters the partner it finds as the partner to which you have assigned this access sequence. For example, if you have assigned this access sequence to the ship-to party, it enters the partner as the ship-to party in the current transaction.

• Preceding document → Business partner relationships: activity partner

• The system looks first in the preceding document for the partner to which you have assigned this access sequence. (If you have assigned it to the ship-to party it looks for a ship-to party.) If it does not find a partner there, it looks in the business partner relationships defined for the activity partner in the current transaction. If you have assigned this access sequence to the payer, the system looks for the relationship "is the payer". It enters this partner as the payer in the current transaction.

General Material Data   General Material Data  
This documentation is copyright by SAP AG.

Length: 7839 Date: 20240523 Time: 172539     sap01-206 ( 133 ms )