SAP Note 380507 SD partner determination: FAQ for the functions Note Language: English
Version: 18 Validity:
Valid Since 04.05.2006
Summary Symptom 1.
No new partner determination when changing the partner
2.
Partner determination on item level and item partner
3.
Billing document: In VBPA entries for item partners are missing
4.
Address change possible although partner cannot be changed
5.
Address change in the preceding or subsequent document changes address in the subsequent or preceding document
6.
Partner types in SD
7.
Problems with RVINVB00/RVINVB10
8.
Customer hierarchies and pricing
9.
Partner description (KNREF) is supplied incorrectly
10.
Personnel number: Address in the document
11.
Account group function assignment
12.
Creation with reference: Determination of partners from the customer master record
13.
Release 4.5: Functions of Central Address Management
14.
Determination of partners from sy-uname (HERTAB = 'D')
More Terms SD partner determination, partner, VOPA, KPAR, CHECKLISTSD, CHECKLIST SD
Cause and Prerequisites This is a consulting note.
Solution Ad 1) No new partner determination when changing the partner The partner determination always runs when you create a document. Then dependent partners are automatically determined and checked. If in the existing document you change a partner, the system does not run a redetermination of the partners (except when the sold-to party is changed). This works as designed and possible dependent partners are not redetermined. Example: 07.05.2009
Page 1 of
5
SAP Note 380507 SD partner determination: FAQ for the functions According to the Customizing, payer 1200 should be determined from ship-to party 1000. In an existing document, if a ship-to party 1400 is replaced by ship-to party 1000 then the system does not redetermine the payer 1200 because with this the automatically determined payer would be overwritten in the document. Payer overwritten in the document. Ad 2) Partner determination on item level and item partner An item partner determination is not provided in the standard system. You can enter item partners manually. Here, in Customizing of the item partners you can specify which partner functions should be allowed on item level and which not. The header partner functions are always allowed on item level. On item level, if you enter a partner, it is visualized by the item partner flag. For an item partner you can change the address data, header partner addresses cannot be changed on item level. The logic of the item partners is: If for an item there is no partner, the header partners are displayed. If as described above you enter a partner on item level, this partner exists on item level. If for a partner you enter an address differing from the header but the partner should stay the same, you can just enter the partner again manually for the respective item. Thus the partner becomes an item partner and the address can be changed. Ad 3) Billing document: In VBPA entries for item partners are missing In a billing document you have item partners. It seems that in the document partner table VBPA entries are missing. This is no error. In the billing document same item partners are grouped and not posted redundantly in VBPA (example: item ship-to parties for item 10 and 20 are the same: only one VBPA entry). Ad 4) Address change possible although partner cannot be changed In the Customizing for a partner determination procedure a partner function is set as "not changeable". You can change the address of the document partner with this function. This is standard behavior. The "not changeable" just refers to the partner (the partner number), the address can always be changed. Just the same, a "not changeable" partner can of course be deleted (if it is no mandatory partner) since the deletion refers to the function and the changing to the partner number. Ad 5) Address change in the preceding or subsequent document changes the address in the subsequent or preceding document. In a sales order an address is changed manually. In the delivery refering to this you change this manual address again. This change is also reflected in the sales order. This behavior works as designed since the address in the delivery refers to the address in the order and has the same address number. So, during the manual change if you always want to assign a new address number (which prevents the changing of the address in the preceding document), you can use Note 97832 (modification). Ad 6) Partner types in SD 07.05.2009
Page 2 of
5
SAP Note 380507 SD partner determination: FAQ for the functions In SD in the standard system there are five partner types: KU (Customer), LI (Vendor), PE (Personnel Number), AP (Contact Persons), and MP (Mail Partner for SAPoffice -> you can create condition records in the output determination for partner functions of this partner type, MP is not allowed as document partner type. In the condition records this mail partner can be preassigned with a SAPoffice user, if this is not carried out the system uses the user who creates the document). All functions that are used in SD must be assigned to one of the five partner types. Creating own partner types is a modification, you should not do this. Ad 7) Problems with RVINVB00/RVINVB10 If it is purely numerical, the customer number KUNNR must be entered with 10 digits and leading zeros. The address number (ADRNR) must not be filled.
Ad 8) Customer hierarchies and pricing In order to allow pricing via customer hierarchies, the hierarchy type must be assigned to the respective sales document type in Transaction OVH4. The hierarchy partners are only determined correctly if the higher-level functions are maintained correctly in the partner Customizing of the customer master. When you create with reference the hierarchy partners are only copied into the reference document if they exist in the partner determination procedure. Ad 9) Partner description (KNREF) is supplied incorrectly In the customer master record A a partner description DesA is maintained. Now, for example customer A should act as ship-to party for customer B. In the order with sold-to party B the partner description DesA for ship-to party A is not used. This works as designed and is standard behavior. The ship-to party A must be maintained with a partner description DesB in the customer master record B. Then this partner description DesB is used. Ad 10) Personnel number: Address in the document If a personnel number is used in a document (for example, as sales representative), the system does not display the private address of the sales representative. This is standard behavior, data from HR must not be displayed in the document. The sales representative can be assigned to a sales group and this to a sales office. Then for the sales representative the address of the sales office is used. Ad 11) Account group function assignment The system displays an error message that a certain partner must not have a certain account group. In Customizing check whether the account group function assignment is maintained correctly. For all functions of the partner type Customer to be used in one sales order an account group function assignment must be maintained. If changes are made in the production system, this can may result in 07.05.2009
Page 3 of
5
SAP Note 380507 SD partner determination: FAQ for the functions documents that can no longer be used since the account group check is always carried out. If you create a sold-to party for an account group KONT, create an order with this sold-to party and then delete the account group function assignment KONT-AG in Customizing, the order can no longer be processed and the system displays an error message. The account group function assignment must be maintained again. Ad 12) Creation with reference: Determination of partners from the customer master record You create a document with reference to a different document. In this case, the system determines all partners which are permitted in the partner determination procedure from the customer master record of the respective partner. The system does not only determine the partners which are set as mandatory partners in the corresponding partner determination procedure but all partners which exist in the corresponding partner determination procedure.
15.
ad 13) Release 4.5: Functions of central address management As of Release 4.5, the central address management is used in SD to manage the address data. The interface in the sales order, however, was not linked to central address management in Release 4.5 yet. As a result, field "Street" is 60 characters long in the customer master whereas it is only 35 characters in the sales order. In addition, some checks of central address management cannot be used in the sales order (for example, the check of the city). The complete conversion to central address management occured in Release 4.6A. As of this release, the central address management is integrated in the sales order completely.
ad 14) Determination of partners from sy-uname (HERTAB = 'D')
If "D" (Determination from sy-uname) has been maintained for the table of origin in Customizing, then the partner is determined from the user name. For this, infotype 105 (Communication) has to be maintained in the HR master record: Type = 0001 System user name of SAP System (sy-uname) ID/number = Logon user name
Header Data Release Status: Released on: Original Lang.: Priority: Category: Main Component:
07.05.2009
Released for Customer 04.05.2006 15:58:50 German Recommendations/additional info Consulting SD-BF-PD Partner Determination
Page 4 of
5
SAP Note 380507 SD partner determination: FAQ for the functions
The Note is release-independent
Related Notes Number 458297 402090
07.05.2009
Short Text Missing partners in billing item Update termination after address change on item
Page 5 of
5
