Customer Master - payer

hi all,
i want to know
1. what is the exact functionality of "Payer" in customer master?
2. if i dont assign this customer to any other customer how the GL's for the same will get updated or how can i do the transactions against this payer?
3. is it copulsary to assign this payer to other customer i.e. sold to party?
4. my user want me to create only payer and not to assign the same to any other sold to party.
i have searched in net but could not able to get the proper reply.
need your help.
Thanks
Ashwini K.

Hi Ashwini,
1. what is the exact functionality of "Payer" in customer master?
In SAP the Sales Orders are created for Sold to Party's , Deliveries for Ship to Party's and Invoices for Payers.
In several big customer organizations it so happens that they may have several branches spread across different regions and many times these organizations present at different places might place orders independently and in turn the ordered goods are supplied to that particular location itself and the payment might be done from the place to where the goods were delivered to and not from the HO. In such cases the customer might need more than one payer master and all these payers will have there own accounting.*
2. if i dont assign this customer to any other customer how the GL's for the same will get updated or how can i do the transactions against this payer?
As mentioned above Invoices are created for the payer. The sold to and the payer may be the same in some cases or different, depending on how the buisness requires it. When an invoice is created the customer account i.e. the payer account and the other accounts like the sales revenuew account, sales deduction accounts and the tax accounts gets posted.
3. is it copulsary to assign this payer to other customer i.e. sold to party?
Yes it is mandatory to assign the payer to the sold to. In some cases as mentioned above the sold to and the payer might be same but in other cases it might be different.
4. my user want me to create only payer and not to assign the same to any other sold to party.
You can create only a payer master but this will not make any sense or will not be of any use until and unless it is assigned to a sold to party
Thanks and regards,
J Nagesh.

Similar Messages

Payer is different in sales order than in customer master

Hi Sap Gurus,
While I am creating a B1(Rebate credit memo requst) the payer is different from customer master.
e.g Suppose the payer in customer master is 100000 & sold to party is 100085 but in sales order the payer is getting changed to 100085.
But when I create a normal CR(credit memo request) in sales order it is showing the same payer as in customer master.
I have checked in VBO2 the rebate receipient, it is 100085.However when I changed the rebate receipient to 100000 all the partner funtions are getting changed to 100000 in sales order.
I also tried creating a B1 document with a customer other than 100085, in sales order the payer is same as in customer master.
I am facing problem when I try to raise B1 documnt type for this particular customer i.e 100085.
Need your help badly.
Regds....
Sumit

In case, for your sold to party 100085, if you have assigned payer as 100000, in sales order the payer should be 100000.
If not check your settings as to why you are getting payer as 100085

Output Determination by Payer's Payment Method (Customer Master)

How would i be able to set printing of invoices only for payer with certain payment method (Customer Master field)? Is this possible within standard SAP?

Hi Ramesh,
Thank you for your help. However, i am referring to the field KNB1-ZWELS.
would it be possible just to maintain output condition record based on criteria of this field - payment method?
regards,
Zoanne

Not able to add payer in customer master partner tab page

Dear all,
I am not able to add payer in customer master partner tab page of sold to party
I am getting the below error
Customer 10075 is not defined for function PY(table TPAKD)
kindly advice
with regards
Mohammed

Please check this posting on partner determination. Your problem looks like the same and try to check if all the settings are made for the partner function assignmnet:
Re: Business partner
Regards
Sai

Partner functions for SAP Customer Master

I am in the MDM solution definition phase for SAP Customer Master at one of our Cients place. The requirement is to set up a central master data scenario where creation & modification of any customer record will be done via MDM. The following components of Netweaver are in the landscape - SAP MDM, EP, XI.
I need clarification on the following points -
- Is it possible to set up the partner function in MDM, if so, how?
- Need to replicate the standard SAP functionality where the system can be configured to create Ship To, Payer, Bill To automatically when a Sold To record is created. Is this possible? Are there any work arounds?
Regards
Arvind

Hi,
Hi Arvind,
- Is it possible to set up the partner function in MDM, if so, how?
Partner Function comes under Condition Technique in SAP ECC.here some config has to be done.
For mapping it in MDM, First create a Qualified Table - Partner Function.Determine the Non-Qualifiers and Qualifiers.Then as said by Suresh, u need Java API stuff to complete this task and frontend being EP.
- Need to replicate the standard SAP functionality where the system can be configured to create Ship To, Payer, Bill To automatically when a Sold To record is created. Is this possible? Are there any work arounds?
It can be done using EP as front end and Java API to dertermine the partner based on the account group.
Thanks,
Felix
Edited by: Felix on May 9, 2008 1:38 PM

How to update partner functions in customer master

Hi all,
I want to update the partner functions for the customer master using transaction code XD02. I created the LSMW by means of recording but it doesn't work because the partner functions for the customer changes.
for example , certain customers have shipto paty, sold to party , bill to party payer and forwarding agent. some customers wont have all the above mentioned category.they may have only ship to party, sold to paty & bill to party.
Is there any other alternative way to update the partner functions for the customer.
Regards,
A.Rathinaprakash

Hi A.Rathinaprakash,
Please use the FM 'SD_CUSTOMER_MAINTAIN_ALL' to maintain the partner functions in the customer.
Pass the partner details in the TABLES parameter T_XKNVP.
Regards
Chetan

Using RFBIDE00   - How to update street 4 of Address on customer master

Hi ,
I am creating customer master records (sold-to Bill-to , ship-to & Payer) based on data from a flat file using direct input program RFBIDE00. I have to update the street address 2, 3 and 4 of Address. I am not able to figure out how to populate this data using RFBIDE00 program. What I read so far makes me believe that it can not be done using direct input program as this is part of central address management which is in str_suppl? fields of ARDC table. Is that right ? If yes , What BAPI/FM I can use to update the street address. Your expert help & guidance is appreciated. Please advise. Thanks. Raghu.

Hi Raghu,
I don't know, if you still have this problem, but if you still have this problem...you can do one more thing apart from central address management update suggested by SAP. You can copy standard program into Z program and modify the sub routine for 111 screen:
FORM D0111_FUELLEN.
In the above subroutine, check any one of street 2, 3 or 4 customer address fields are not initial and if so, then add this code after appending 111 screen to FT internal table which already exists...this code will expand more fields option in screen 111.
IF NOT BIADDR2-STR_SUPPL3 IS INITIAL.
    CLEAR FT.
    FT-FNAM = 'BDC_OKCODE'.
    FT-FVAL = '=$2OC'.
    APPEND FT.
ENDIF.
After this code, in the existing subroutine,
PERFORM D0111_FUELLEN_ZAV USING 'KNA1'.
or new sub routine you need to include code for adding extra fields to the FT internal table as
IF NOT BIADDR2-STR_SUPPL3 IS INITIAL.
    CLEAR FT.
    FT-PROGRAM = 'SAPMF02D'.
    FT-DYNPRO   = '0111'.
    FT-DYNBEGIN = 'X'.
    APPEND FT.
    CLEAR FT.
    FT-FNAM = 'BDC_OKCODE'.
    FT-FVAL = '/00'.
    APPEND FT.
    PERFORM D0111_FUELLEN_ZAV USING 'KNA1'.
    FT-FNAM = 'ADDR1_DATA-STR_SUPPL3'.
    FT-FVAL = BIADDR2-STR_SUPPL3.
    APPEND FT.
ENDIF.
This code will work fine as long as you make changes correctly as mentioned. If you don't understand above code or if you need more information contact me at [email protected].believe me this code worked fine for me
Hope this will help you.
Good luck!
Regards,
Vivek

Ship to party is not available in account group while creating Customer Master

Hello All.
While creating customer master in account group there is no SH(ship to party) what is the purpose of it . I can see PY BP but not SH (XD01). We always use Sold to Party but i have seen Payer and Bill to party as well while creating customer master . Just got confused why we select such options when everything comes under sold to party.
I cannot see SH while creating customer for the first time is it necessary that SH should there while creating customer master.
Regards

Hi ,,
please do assign ship to party to account group .
SPRO --> S&D --> BASIC FUNCTION --> PARTNER DETERMINATION--> SET UP PARTNER DETERMINATION --> FOR CUSTOMER MASTER -- > A/C GROUP - FUNCTION ASSIGNMENT
Here assign ship to party(sh) to your account group.
Now you will find sh in customer master.
If you want further clarification , please let me know.
Regards
Patchala.

Customer Master,for a Vendor, takes wrong Ship-to in Return Delivery

Hi Everyone,
Process: Return to vendor based on the standard PO (type NB) with return delivery (type RL).
Settings Made: A customer master with account group Sold-to created and the code maintained in vendor master and vice versa. In this customer master Ship-to parter is not the same as other partner functions. Say Sold-to = Billed-to = Payer = 1234, but Ship-to = 5678.
Issue: Whenever a return delivery is created agianst a PO (in VL10D) the system proposes Ship-to customer same as the sold-to 1234 . Delivery is getting processed without any error but the question is why system should propose 1234 as Ship-to which is not defined in the parter functions of Sold-to cusotmer 1234? Instead system should take 5678 as Ship-to which is the only entry in the sold-to cusotmer 1234 available.
If a sales order is created for this customer, system correctly populates Sold-to (1234) and Ship-to (5678). The issue is only when a return delivery gets created against a standard PO.
Kindly advise.
Thanks,
Hemant

Hi
My reply to you is more of logical than SAP
Normally SP is the most dominant and important party in a sales process
If you have a different SH in a CMR that means this sold to party tells you rather than delivering goods to me you deliver it to this person
In standard SAP goods receiving hrs,Taxes,ship to address these are the data taken from a SH in a sales order
In case of returns the decision to return stocks will be taken only by SP and not the person who receives the goods
What i am telling is more of logical business process
That is why the system is proposing likewise
May be the other experts has give better explanation for this
Regards
Raja

Payment term in customer master

Gurus,
XD02 - Change Customer Master
Payment term is maintained in
=> Company code data -> Payment Transactions -> Payment Data-> Payment term
=> Sales Area Data -> Billing Documents-> Delivery ad payment terms-> Terms of payment
In sales order, system propose payment term from Sales area data.
Please explain importance of these field.
Regards,
Ashish
Edited by: Ashish Desai on May 4, 2009 2:57 AM

Hi
In addition to all the suggestions given by all friends
If the invoicing is done thro SD route that is VF01 then the terms of payment maintained in sales area data will get preference
If the invoicing is done thro FI route that is FB70 then the terms of payment maintained in company code data will get preference
If the credit management is active then the terms of payement maintained in company code will take the control
For easy understanding as long as credit management is not active the terms of payment in sales area data will have the control as we are not going to touch FB70 at all mostly
As said by all others terms of payement is taken from payer
Regards
Raja

Copy mode of payment from customer master data to sales order,

Hi Gurus,
Hope all is fine.
I have a small doubt. If we want to transfer the mode of payment from customer master data to sales order, do we have to use Exit- MV45AFZZ.
Can't we transfer the data without the exit?

Hi,
I have tested this in sand box.Thought the customer master is having payment method ( payer ) ,It is not copying from customer master to sales order but if you maintain manually in sales order ,it is copying into billing document level.FYI see below snap shot.
Note:If you want it from customer master into sales order,may be you need to take help of abaper on this.
BR's,
Naren

Customer Master Address and Outputs

I have maintained two address es in my customer master, The Street address and a PO box. I want the delivery Note out put to print the street address on it and the Invoice out put to print the PO BOX.
Currently my Delivery Note is showing the PO BOX which is a problem since my client can not ship to a PO BOX, and we do not want to maintain another ship to partner with the same customer number.
Is there a way to fix this or an OSS note on this?

Hello,
As i understood correctly, The delivery Output now should print the STREET instead of POBOX number , This is a change in the Logic.
Just Pick the customer Number from the Customer of delivery from LIKP-KUNNR and fetch the STREET from KNA1-KUNNR
In the KNA1 table you will get the ADRNR, then goto ADRC to get the STREET details
In the same way fetch the POBOX from Payer of Billing document
Hope it is clear,
regards,
santosh

List Customer master Filelds (URGENT)

Dear All,
Can you Please provide the list of Customer master fields in one Place.
Please Do the Needful (IT IS URGENT)
Regards,
Vinay

Hi
Do the following.
Go to SE11 and put below tables one by one
KNA1                               General Data in Customer Master
KNA1VV                             Customer Master View KNA1 KNVV
KNAS                               Customer master (VAT registration numbers
KNAT                               Customer Master Record (Tax Groupings)
KNB1                               Customer Master (Company Code)
KNB4                               Customer Payment History
KNB4_AEDAT                         BW FI: KNB4 Extraction using AEDAT
KNB5                               Customer master (dunning data)
KNBK                               Customer Master (Bank Details)
KNBW                               Customer master record (withholding tax ty
KNC1                               Customer master (transaction figures)
KNC1_AEDAT                         BW FI: KNC1 Extraction using AEDAT
KNC3                               Customer master (special G/L transaction f
KNC3_AEDAT                         BW FI: KNC3 Extraction usign AEDAT
KNEA                               Assign Bank Details and Payment Methods to
KNEX                               Customer Master: Legal Control - Sanctione
KNKA                               Customer master credit management: Central
KNKA_AEDAT                         BW FI: KNKA Extraction using AEDAT
KNKK                               Customer master credit management: Control
KNKKF1                             Credit Management: FI Status Data
KNKKF2                             Credit Management: Open Items by Days in A
KNKKF2                             Credit Management: Open Items by Days in
KNKK_AEDAT                         BW FI: KNKK Extraction usign AEDAT
KNKO                               Assignment of Cost Est. Number to Config.
KNMT                               Customer-Material Info Record Data Table
KNMTK                              Customer-Material Info Record Header Tabl
KNMT_REF                           Test - Search Help for KNMT
KNOB                               Assignment of Cost Est. Number to Config.
KNVA                               Customer Master Loading Points
KNVD                               Customer master record sales request form
KNVH                               Customer Hierarchies
KNVI                               Customer Master Tax Indicator
KNVK                               Customer Master Contact Partner
KNVL                               Customer Master Licenses
KNVP                               Customer Master Partner Functions
KNVS                               Customer Master Shipping Data
KNVT                               Customer Master Record Texts for Sales
KNVV                               Customer Master Sales Data
KNZA                               Permitted Alternative Payer
You will get all the needed fields.
Hope this helps. reward if helpful
kind regards
sandeep

Customer master creation or entering data into customer master.

Hi Friends
Can any give good example to create customer master from Account group to entering customer master data? so that to move forward.
Thanks in advance.

2.1 Customer Master
2.1.1 Account Group
2.1.1.1 Maintain Number Range for Account Group
Use
The purpose of this activity is to control number range of Account Group.
Procedure
Access the activity using one of the following navigation options:
IMG --> Financial Accounting (New) --> Accounts Receivable and Accounts Payable --> Customer Accounts --> Master Data --> Preparations for Creating Customer Master Data --> Create Number Ranges for Customer Accounts --> Select the Icon to maintain Number Range
Transaction Code: SPRO
Data to be maintained:
No | From | To | Current No | Ext (Tick in Check Box)
01 | 0000000001 | 0000099999 | 0 | No
02 | 0000100000 | 0000299999 | 0 | No
XX | A | ZZZZZZZZZZ | Yes
2.1.1.2 Assign Number Range to Account Group
Use
The purpose of this activity is to maintain number range of Account Group.
Procedure
Access the activity using one of the following navigation options:
IMG > Financial Accounting (New) > Accounts Receivable and Accounts Payable > Customer Accounts > Master Data > Preparations for Creating Customer Master Data > Assign Number Ranges to Customer Account Groups
Transaction Code : SPRO
Data to be maintained:
Group | Name | Number Range
0001 | Sold-to party | XX
0002 | Goods recipient | XX
0003 | Payer | XX
0004 | Bill-to party | XX
2.1.1.3 Define Account Groups with Screen Layout (Customers)
Use
In this step, you determine the account group of the customer.
Procedure
Access the activity using one of the following navigation options:
IMG > Financial Accounting (New) > Accounts Receivable and Accounts Payable > Customer Accounts > Master Data > Preparations for Creating Customer Master Data > Define Account Groups with Screen Layout (Customers)
Transaction Code : SPRO
The groups indicated below are a few examples. There are many groups in Standard SAP & if we require additional Group, it can be copied from appropriate group & maintained.
Group | Name
0001 | Sold-to party
0002 | Goods recipient
0003 | Payer
0004 | Bill-to party
0005 | Prospective customer
0006 | Competitor
Select Sold-to-party > go to Details > Double Click on General data / Company code data / Sales data. It will take to next screen which details Tab Pages of General data / Company code data / Sales data. Double Click on Tab Page for example: Address, Control, Marketing & so on. Here you can maintain whether the field is to be Suppress, Req. Entry, Opt. entry or Display
2.1.2 Process to Create Customer Master
2.1.2.1 Initial Screen of Customer Master Maintainance
Use
The purpose of this activity is to maintain Customer Master Data. Customer Master Can be created for Sales & Distribution, in which it will be possible to maintain General Data Tab & Sales Area Tab. Alternatively it is also possible to maintain Complete / FI, in which it is possible to maintain General Data, Company Code Data & Sales Area Data (Complete) or General Data & Company Code (F1)
Procedure
Access the activity using one of the following navigation options:
SAP Easy Access > Logistics > Sales and Distribution > Master Data > Business Partner > Customer > Create > Sales and Distribution / Complete
Transaction Code : VD01 / XD01
Fields to be maintained in Initial Screen (referring Complete):
Field - Functionality
Account Group - Take a drop down & select appropriate Account Group
Customer Enter manually
Company Code - Take a drop down
Sales Organization - Take a drop down
Distribution Channel - Take a drop down
Division - Take a drop down
A Customer can be created with reference to an existing Customer & necessary data can be changed.
Reference
Field - Functionality
Customer - Enter manually
Company Code - Take a drop down
Sales Organization - Take a drop down
Distribution Channel - Take a drop down
Division - Take a drop down
2.1.2.2 General Data of Customer Master Maintenance
Use
The purpose of this activity is to maintain General Data. General Data is applicable to the customer centrally. Incase of extending Customer to another Sales Area, General data will remain the same.
Procedure
Fields to be maintained are as under:
ADDRESS
Field - Functionality
Title - Take a drop down
Name - Enter manually
Search Term - Enter Manually (Optional)
Street - Enter Manually (Optional)
House No - Enter Manually (Optional)
Postal Code - Enter manually
City - Enter manually
Country - Take a drop down
Region - Take a drop down
Control Data
Field - Functionality
Vendor - Enter Manually (Optional) To establish Customer Vendor Relationship.
Trading Partner - To be maintained incase of Inter-company Customer,
The above is for Illustration purpose. Please ensure to maintain the fields required.
2.1.2.3 Company Code Data of Customer Master Maintenance
Use
The purpose of this activity is to maintain Company Code Data. This is maintained by an FI person.
Procedure
Fields to be maintained are as under:
Account Management
Field - Functionality
Recon. Account - Take a drop down (Mandatory)
Payment Transaction
Field - Functionality
Terms of payment - Take a drop down.
The above is for Illustration purpose. Please ensure to maintain the fields required.
2.1.2.4 Sales Area Data of Customer Master Maintenance
Use
The purpose of this activity is to maintain Company Code Data. This is maintained by an FI person.
Procedure
Fields to be maintained are as under:
Sales
Field- Functionality
Sales Office - Take a drop down & maintain the appropriate SBU
Currency - Maintain the local / export currency.
Exch. Rate Type- Maintain M, incase of export / inter-company(if required) only.
Cust. Pric. Proc -This is maintained to pick the pricing procedure in Sales Order & Billing Document. It should always be maintained.
Customer Stat. Gr - This is recommended to be maintained to enable the data to flow to SAP standard report.
Shipping
Field -Functionality
Delivery Priority - Take a drop down & maintain the appropriate for Delivery purpose.
Order Combination - Maintain the tick
Shipping Condition -Take a drop down & maintain the appropriate for Delivery purpose.
Delivery Plant - Take a drop down & maintain the appropriate Plant.
Billing
Field - Functionality
Incoterm - Take a drop down & select. Maintain the Description manually.
Terms of payments -Take a drop down & select.
Account assignment Group -Take a drop down & maintain the appropriate. This is very important to be maintained, else it will give an error to release the billing document to accounting.
Tax - Take a drop down & select 0 or appropriate.
The above is for Illustration purpose. Please ensure to maintain the fields required.
Regards,
Rajesh Banka
Reward points if helpful

Customer master record

well, i m new in sap..may i know what is customer hirarchy, how does it work...and how to configure it in the system?

Hi,
CUSTOMER HIERARCHY:
Customer hierarchies are available in Sales and Distribution, so that you can create flexible hierarchies to reflect the structure of customer organizations. If your customer base includes multi-level buying groups, cooperatives, or chains of retail outlets, for example, you can create hierarchies to reflect the structure of these groups. Use customer hierarchies during sales order processing and billing for determining pricing and running statistics.
A customer hierarchy consists of nodes.
To create a customer hierarchy:
1. Create master records for each node.
2. Assign the nodes to each other.
3. Assign the customer master records to the relevant nodes.
Hierarchy nodes are only valid for a certain period of time. They may also be moved. If a node is moved, the system automatically reassigns all related nodes and customer master records.
With customer hierarchies, you can assign price or rebate agreements to a higher level node. The agreements are then valid for customers at all subordinate levels to this node. You can create pricing condition records for each node indicated as relevant for pricing. If one or more nodes in the hierarchy path of a sales order contain pricing information, the system takes them into account automatically during pricing.
'How to check'
All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
1) Define hierarchy type: just put and ID and a name to the new hierarchy.
2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this information, in the order, you obtain the business partner for each partner function.
3) Assign account groups: you indicate which accounts groups are allowed for being part or your hierarchy.
4) Assign sales areas: simple you indicate which sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas).
5) Assigning hierarchy type for pricing: you indicate which classes of documents uses hierarchy in pricing determination.
It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount.
Customer hierarchy setup, firstly decide the hierarchy type to be used.
The standard is type A.
You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?
Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy.
You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level.
You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area.
All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy
You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.
Please go through the following links,
http://help.sap.com/saphelp_46c/helpdata/en/dd/55f4d9545a11d1a7020000e829fd11/frameset.htm
http://www.sap-img.com/sap-sd/customizing-customer-hierarchy-in-sd.htm
Thanks,
Sree.Manam

Customer Master - payer

Similar Messages

Maybe you are looking for