Payment terms in customer master data

Hi,
How can I customize that the paymennt terms will come to the order from the company master data and not from the sales data of the customer?
Thanks!!

Hi
The Terms of Payment maintained in CoCode Data is not related to sales and the one maintained in Sales Area Data of CMR is related to sales and hence there is no chance to use this.
Instead maintain the same payment terms in both the place of Customer Master. It will meet your requirement.
Thanks,
Ravi

Similar Messages

MATCHCODE ON PAYMENT TERMS IN CUSTOMER MASTER DATA

HI,
Could you please help me on the point described below ?
When I use the Transaction XD03 on customer master data, the matchcode on the field "payment terms" ( in the sales area data) only displays the current value of the field.
It is not possible to have all the possible values; only the value written in the field is displayed in the matchcode; It is also the same thing if i use the transaction XD02.
The others values are displayed if I delete the current entry...
Could you please explain me how I could retrieve all the possible entries ( in display mode) of the field without deleting any entry ?
NB : it seems that This is linked to the sales area; when I display the same customer on different sales areas, the result is not the same. On some sales areas, I can have the other possible entries...
Thanks in advance for your help.

Hi,
I remember there is a way to do this, but forgot. Please discuss with your developers. They should be able to do this for you. Its a small thing on the screen which pops up, but I forgot what is that.

Payment Term in customer master to be given restricted access

Hi All,
My client has a requirement...
Payment Term in customer master should be editable only to authorised persons...for all others it should be in display mode...
do we have any user exits to achieve this???
or any valuable inputs/suggestions will be awarded marks...
Prasad

Dear Prasad,
You can acheive this in standard.
Go to IMG>Logistics - General>Business Partner>Customers>Control>Define and Assign Field Authorization Groups
Maintain Customer field groups and maintain the fields(KNVV-ZTERM) in the Group fields.
Go through the help file you will get the detail process to acheive this.
Also if in your company person creating sales area data(Sales Personnel) and person maintaining company code data (FI Personnel) is different and suppose if you want only FI people should be authorized to Maintain and change Payment terms then you can make Payment term field greyed out for T code VD01/VD02 and make it editable in XD01/XD02.
This can be done in TCode OB20 - Transaction dependent screen layout.
Hope any of the solution can be worked around to acheive ur requirement.
Regards
Mayank

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

Payment terms in Customer Master

Hi,
In Customer Master,we have payment terms field in Company Code View and Sales Area View.What is the difference between them.If i maintain different payments in those views,which has the highest priority.
Vinu

Hi
Terms of payment key
Key for defining payment terms composed of cash discount percentages and payment periods.
Use
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:
·     Cash management
·     Dunning procedures
·     Payment transactions
Procedure
Data 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:
o     item level in sales orders
o     header level in purchase orders and invoices
Note
Master 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.

Payment terms in Vendor Master data and purchasing info record

Hi, all, I met one trouble. While I create Purchase Order. In the header item, payment terms is automatically pop up from the data maintaining the vendor master data or purchasing info record if there is difference payment terms between in vendor master data and in purchasing info record. What happend?
Sometimes, When you create purchase order, payment terms is not automatically pop up even you maintained in the vendor master data or purchasing info record. Why? Is it meaning that I can manually to input payment terms while create each purchase order which can be difference data with vendor master data or purchase info record?
Thank you very much in advance,

Hi,
The payment terms is usually defaulted from either vendor master or purchasing master data record such as contract/outline agreement. Unless it is set through configuration that the payment terms be set as mandatory, any failure to maintain payment terms won't stop you from posting your PO as this information will only be useful during invoice receipt maintenance. Having said that if you are setting up your system with discount condition type as part of your PO pricing schema then it is necessary that the payment terms shall be maintained during PO creation.
Cheers,
HT

Two Payment terms in Customer Master

Dear Gurus
Can we have two different payment terms for the same customer?
Regards
Vaibhav

Dear Vikas
This is a very logical way of presenting things. The payment terms at sales org level are valid in line items. If payment terms are defined only in the company code area, than the same is valid irrespective of the product or sales organization. You can disable the payment terms at sales organization level based on your business requirements.
Thanks & Best Regards
Sanil K Bhandari

Payment terms for customer Spl Gl

Hi,
Please suggest the way in which i could get the due date based on the payment terms from customer master for a customer down-payment.
As even when in ob41 & obc4 the field payment terms is kept optional it does not appear for the spl gl posting.
Is there any way out or is it advisable to keep the due date editable
Regards,
Charmaine Martin

Hi,
can you please test to enter Payment term in Vendor/Customer master in Comapny code in field Cr meno field . Please see below screen shot .
Screen shot is vendor related but you should have same in Customer

Question about terms of payment of company code tab of customer master data

Hi:
As I know there are two places to be maintained terms of payment of customer master data, one is in billing documents of sales area data tab and I understood it will default to the one in sales order when you create, another is in company code tab and I don't know what does it be used for? Could you advise?

Hi
Along with the payment terms, the reconciliation account number and the dunning procedure is set specifically for the customer to the particular company code.
This would be the default data for all transactions specific to the customer in specific company code.
If you extend the customer to another company code, you can have different recon, payment terms etc.
All FI transactions are relative to these settings.
In SD when you process, any changes to the particular customer can be modified and it will supercede the default settings of PT
Reg
Suresh

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

Payment terms in vendor Master

Hi,
In XK01- create vendor master, There are two payment terms--> payment transaction field and other in purchasing organisation data.
Is there a configuration which will default the payment terms in purchasing org screen based on the inputs in the company code screen
Regards,
Srijith

No there is no such customizing.,
Not every vendor with purchasing org data needs company code data. Not every vendor with company code data needs purchasing data.
The payment terms at company code level are used if you post non-PO related invoices with FI transactions.
the payment term of purchasing org data is used if the process is PO related.

Query in customer master data upload ....?

Hi Guru's,
I am uploading the customer master data from presentaion server to customer tables using functional module SD_CUSTOMER_MAINTAIN_ALL.
while check the Function module separatly and it working properley and i am able to ctere customer...
and i am using the same function module in the program i am unable to upload ..could please check and let me know where i am doing mistake in the below program logis..and values also moving properly before calling function module..while calling the functinal module the controle comming out of the loop and program went to dump i am able to see the message in dump as like this(it may helpfull for resolve):
Name of function module...............: "SD_CUSTOMER_MAINTAIN_ALL"
Name of formal parameter..............: "O_KNA1"
Technical type of actual parameter....: "C"
Technical length of actual parameter..: 20 bytes
Technical type of formal parameter....: "u"
Technical length of formal parameter..: 3634 bytes
Name of formal parameter at caller....: "O_KNA1"
*& Report ZERP_CUSTOMER_CREATE_UPLOAD
REPORT zerp_customer_create_upload.
PARAMETERS:p_files        TYPE string.
*DATA :xkunnr(10)      LIKE kna1-kunnr. "unique KUNNR
DATA: gs_i_kna1           TYPE kna1,
      gs_i_knb1             TYPE knb1,
      gs_i_knvv           TYPE knvv,
      gs_return           TYPE bapireturn1,
      gs_i_bapiaddr1      TYPE   bapiaddr1,
      gt_t_xknvi          TYPE STANDARD TABLE OF fknvi,
      gwa_t_xknvi         TYPE fknvi,
      gt_t_xknbk          TYPE STANDARD TABLE OF fknbk,
      gwa_t_xknbk         TYPE fknbk,
      gt_t_yknvp          TYPE STANDARD TABLE OF fknvp,
      gwa_t_xknvp         TYPE fknvp.
TYPES:BEGIN OF gty_itab1,
      abc(305),
      END OF gty_itab1.
DATA: gt_itab1 TYPE STANDARD TABLE OF gty_itab1,
      gwa_itab1 TYPE gty_itab1.
TYPES :BEGIN OF gty_itab2,
       ktokd(4),        "customer account grp      kna1
       kunnr(10),       "customer                  kna1
       name1(35),       "name1                     kna1
       sortl(10),       "sort filed                kna1
       stras(35),       "house number and adres    kna1
       pstlz(10),       "postal code               kna1
       ort01(35),       "city                      kna1
       land1(3),        "country                   kna1
       telf1(16),       "tele phone no             kna1
       telfx(31),       "fax num                   kna1
       kukla(2),        "cust classificaion        kna1
       bukrs(4),        "company code              knb1
       akont(10),       "reconcilation acct        knb1
       vkorg(4),        "sales org                 knvv
       vtweg(2),        "distr chan                knvv
       spart(2),        "division                  knvv
       zterm(4),        "terms of payment          knvv
       bzirk(6),        "sales district            knvv
       vkbur(4),        "sales office              knvv
       vkgrp(3),        "sales grp                 knvv
       kdgrp(2),        "cust grp                  knvv
       waers(5),        "currency                  knvv
       konda(2),        "price grp                 knvv
       kalks(1),        "pricing procedure assign knvv
       lprio(2),        "delivery plant            knvv
       vsbed(2),        "shipping conditions       knvv
       vwerk(4),        "delivering plant          knvv
       inco1(3),        "inco1                     knvv
       inco2(28),       "inco2                     knvv
       kkber(4),        "cred control area         knvv
       ktgrd(2),        "acc assgn grp             knvv
       taxkd(1),        "tax classification 4 cust knvi
       bankn(18),       "bank account number       knbk -
        xkunnr(10),
       END OF gty_itab2.
DATA: gt_itab2 TYPE STANDARD TABLE OF gty_itab2,
      gwa_itab2 TYPE gty_itab2.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    filename                = p_files
    filetype                = 'ASC'
TABLES
    data_tab                = gt_itab1
EXCEPTIONS
    file_open_error         = 1
    file_read_error         = 2
    no_batch                = 3
    gui_refuse_filetransfer = 4
    invalid_type            = 5
    no_authority            = 6
    unknown_error           = 7
    bad_data_format         = 8
    header_not_allowed      = 9
    separator_not_allowed   = 10
    header_too_long         = 11
    unknown_dp_error        = 12
    access_denied           = 13
    dp_out_of_memory        = 14
    disk_full               = 15
    dp_timeout              = 16
    OTHERS                  = 17.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT gt_itab1 INTO gwa_itab1.
gwa_itab2 = gwa_itab1-abc(305).
APPEND gwa_itab2 TO gt_itab2.
ENDLOOP.
LOOP AT gt_itab2 INTO gwa_itab2.
SPLIT gwa_itab2 AT ',' INTO gwa_itab2-ktokd
                              gwa_itab2-kunnr
                              gwa_itab2-name1 gwa_itab2-sortl
                              gwa_itab2-stras gwa_itab2-pstlz
                              gwa_itab2-ort01 gwa_itab2-land1
                              gwa_itab2-telf1 gwa_itab2-telfx
                              gwa_itab2-kukla gwa_itab2-bukrs
                              gwa_itab2-akont gwa_itab2-vkorg
                              gwa_itab2-vtweg gwa_itab2-spart
                              gwa_itab2-zterm gwa_itab2-bzirk
                              gwa_itab2-vkbur gwa_itab2-vkgrp
                              gwa_itab2-kdgrp gwa_itab2-waers
                              gwa_itab2-konda gwa_itab2-kalks
                              gwa_itab2-lprio gwa_itab2-vsbed
                              gwa_itab2-vwerk gwa_itab2-inco1
                              gwa_itab2-inco2 gwa_itab2-kkber
                              gwa_itab2-ktgrd
                              gwa_itab2-taxkd
                              gwa_itab2-bankn.
*moving files values from ITAB2 work area to global structure related to FM.
gs_i_kna1-ktokd   = gwa_itab2-ktokd.
gs_i_kna1-kunnr   = gwa_itab2-kunnr.
gs_i_kna1-name1   = gwa_itab2-name1.
gs_i_kna1-sortl   = gwa_itab2-sortl.
gs_i_kna1-stras   = gwa_itab2-stras.
gs_i_kna1-pstlz   = gwa_itab2-pstlz.
gs_i_kna1-ort01   = gwa_itab2-ort01.
gs_i_kna1-regio   = gwa_itab2-land1.
gs_i_kna1-telf1   = gwa_itab2-telf1.
gs_i_kna1-telfx   = gwa_itab2-telfx.
gs_i_kna1-kukla   = gwa_itab2-kukla.
gs_i_knb1-bukrs   = gwa_itab2-bukrs.
gs_i_knb1-akont   = gwa_itab2-akont.
*I FOR GOT TO INCLUDE THE ZTERM VALUE IN EXCELL SHEET SO INCLUDED HARD CODE HERE
gs_i_knb1-zterm   = '0001'.
gs_i_knvv-vkorg   = gwa_itab2-vkorg.
gs_i_knvv-vtweg   = gwa_itab2-vtweg.
gs_i_knvv-spart   = gwa_itab2-spart.
gs_i_knvv-zterm   = gwa_itab2-zterm.
gs_i_knvv-bzirk   = gwa_itab2-bzirk.
gs_i_knvv-vkbur   = gwa_itab2-vkbur.
gs_i_knvv-vkgrp   = gwa_itab2-vkgrp.
gs_i_knvv-kdgrp   = gwa_itab2-kdgrp.
gs_i_knvv-waers   = gwa_itab2-waers.
gs_i_knvv-konda   = gwa_itab2-konda.
gs_i_knvv-kalks   = gwa_itab2-kalks.
gs_i_knvv-lprio   = '02'.             "gwa_itab2-lprio.
gs_i_knvv-vsbed   = gwa_itab2-vsbed.
gs_i_knvv-vwerk   = gwa_itab2-vwerk.
gs_i_knvv-inco1   = gwa_itab2-inco1.
gs_i_knvv-inco2   = gwa_itab2-inco2.
gs_i_knvv-kkber   = gwa_itab2-kkber.
gs_i_knvv-ktgrd   = gwa_itab2-ktgrd.
gwa_t_xknvi-tatyp = 'UTXJ'.          "HARD CODE
gwa_t_xknvi-aland = 'US'.            "HARD CODED
gwa_t_xknvi-kz     = '0'.             "HADR CODE
gwa_t_xknvi-taxkd = '0'.             "gwa_itab2-taxkd.
APPEND gwa_t_xknvi TO gt_t_xknvi.
gwa_t_xknbk-bankn = gwa_itab2-bankn.
APPEND gwa_t_xknbk TO gt_t_xknbk.
gs_i_knb1-lockb          = 'X'.
gs_i_knvv-kzazu          = 'X'.
gs_i_knvv-kztlf          = 'X'.
gs_i_knvv-perfk          = 'X'.
gs_i_knvv-prfre          = 'X'.
gs_i_kna1-spras          = 'EN'.
CALL FUNCTION 'SD_CUSTOMER_MAINTAIN_ALL'
   EXPORTING
     i_kna1                              = gs_i_kna1
     i_knb1                              = gs_i_knb1
     i_knvv                              = gs_i_knvv
I_BAPIADDR1                         =
I_BAPIADDR2                         =
I_MAINTAIN_ADDRESS_BY_KNA1          = ' '
I_KNB1_REFERENCE                    = ' '
I_FORCE_EXTERNAL_NUMBER_RANGE       = ' '
I_NO_BANK_MASTER_UPDATE             = ' '
I_CUSTOMER_IS_CONSUMER              = ' '
I_RAISE_NO_BTE                      = ' '
PI_POSTFLAG                         = ' '
PI_CAM_CHANGED                      = ' '
PI_ADD_ON_DATA                      =
I_FROM_CUSTOMERMASTER               = ' '
IMPORTING
e_kunnr                             = xkunnr
o_kna1                              = xkunnr
E_SD_CUST_1321_DONE                 =
   TABLES
T_XKNAS                             =
     t_xknbk                             = gt_t_xknbk
T_XKNB5                             =
T_XKNEX                             =
T_XKNVA                             =
T_XKNVD                             =
     t_xknvi                             = gt_t_xknvi
T_XKNVK                             =
T_XKNVL                             =
T_XKNVP                             =
T_XKNZA                             =
T_YKNAS                             =
T_YKNBK                             =
T_YKNB5                             =
T_YKNEX                             =
T_YKNVA                             =
T_YKNVD                             =
T_YKNVI                             =
T_YKNVK                             =
T_YKNVL                             =
   t_yknvp                             = gt_t_yknvp
T_YKNZA                             =
T_UPD_TXT                           =
   EXCEPTIONS
     client_error                        = 1
     kna1_incomplete                     = 2
     knb1_incomplete                     = 3
     knb5_incomplete                     = 4
     knvv_incomplete                     = 5
     kunnr_not_unique                    = 6
     sales_area_not_unique               = 7
     sales_area_not_valid                = 8
     insert_update_conflict              = 9
     number_assignment_error             = 10
     number_not_in_range                 = 11
     number_range_not_extern             = 12
     number_range_not_intern             = 13
     account_group_not_valid             = 14
     parnr_invalid                       = 15
     bank_address_invalid                = 16
     tax_data_not_valid                  = 17
     no_authority                        = 18
     company_code_not_unique             = 19
     dunning_data_not_valid              = 20
     knb1_reference_invalid              = 21
     cam_error                           = 22
     OTHERS                              = 23.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF sy-subrc EQ 0.
    CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
    WRITE: / 'Error Message:', 'error in creation'.
ELSE.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'costomer', gwa_itab2-kunnr, 'created'.
ENDIF.
ENDLOOP.

please let me know if my qestion is not clear...
and please cinfirm me ..that can i use the function module (SD_CUSTOMER_MAINTAIN_ALL) instead of BAPI (BAPI_CUSTOMER_CREATEFROMDATA1) for uploading customer master data.
please respond me ASAP.
thanks in advance and will give full points
thanks&regards
Srinivas.

Impacts in COPA of changing material and customer master data

Dear experts,
In my company we are considering following scenario:
Currently mySAPerp 6.0 is implemented for all modules for the mother company.
We have developed a new global template where there are significant changes versus the existing system, especially in the SD processes. Material and customer master also change significantly in terms of content in the tables/fields and/or values in the fields.
The idea was to build the template from scratch in a new machine and roll-out all group affiliates, but now we are considering the possibility of making an evolutionary of the current system and try to stretch it to the processes defined in the global template.
The scenario we want to analyze is: Keeping same organizational structure in terms of Company code, CO area and Operating Concern in existing SAP client and make an evolutionary of the existing settings to the global template processes.
The doubts we are having are the following:
Changing material & customer master data: Impact in COPA
Option 1: Material master data and customer master data codes are maintained but content in the tables/fields is changed substantially, both in terms of logical content of specific fields and/or the values in the specific fields. We have following examples of changes.
Case 1: source field in material master changes logical content. E.g. Material master field MVGR1 is currently used for product series (design line) and the content changes to be the Market Segment. The product series will be moved to a classification field. At least 5 other fields are affected by this. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Case 2: the source field is not changed so that the logical content of the field remains but the values change, i.e. for the same concept there will be different codifications. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Case 3: Characteristics where currently the source material master field is a Z field and the derivation is via table look up and where the Z field changes to a classification field. How can you convert the existing COPA line items to ensure that attributes are aligned? Should new characteristics be created or just change the derivation logic of the characteristic?
Option 2: Material master data and customer data codes are re-created (codification of records is changed), meaning that new material and customer codes will exist and content in tables/fields is changed (as in option 1)
Case: material and customer codes are changed. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Iu2019ve never phased a similar scenario and I fear that maintaining operating concern while changing source master data and also SD flows (we have new billing types, item categories, sales doc. Types, order reasons) may lead to inconsistencies and problems in COPA.
I would like to ask you experts if you have come across a similar scenario and if from your experience, it is something feasible to do or there are many risks involved. What can be the impact of this scenario in existing Operating Concern for both option 1 and 2 and what would be the key activities to perform to adapt the existing operating concern. What will be the impact of the needed conversions on P&L reporting?
Sorry for the long story. I hope you can help me out.
Thanks and Regards,
Eric

Hi,
First i think you will need to test if it works for new COPA documents created via billing.
If it works fine then the issue is if you wish to apply these changes to the historical data already posted.
Normally there are transactions like KE4S where you can repost the billing document to COPA
However this may not be viable for bulk postings
You can perform realignment (KEND) but this only works at the PA segment level (table CE4XXXX)
regards
Waman

Problem in Customer Master data

Hio friend
I need some examples what type of problems or issues or ticket comes at clients in Customer Master data maintenance. If possible send some scnerios with solution also how it was solved.
Thanks
Raj

Hi,
1. 'Entry GVK 0000140000 does not exist in SKB1 - check your entry'.
Solution :Reconcilation account 140000 has to be created in GL Master Data - T.code FS00.
2. Customer is Vendor and Vendor is customer.How do you see the net profit?
Solution : In customer Master , you have to input vendor master and in vendor master, you have input customer master, tick the clearing with customer box on the vendor record and the netting with vendor box on the customer record, Payment can be made by Automatic Payment PRogram.
Additionally search SDN with the search word customer master, you will find losts of real time problems with solutions.
Please let me know if you need more information.
Regards
Sridhar M

Customer Master data.. Bank Account No.

Hi
In customer master data ( XD01) > General Data > Payment Transaction > Bank Details
we maintain. Bank key , Bank Account and other details.
my concern is , by maintaining customer bank account number in customer master data, what are the integrated effects to FI > Bank Accounting > House Bank ? ( On Invoice Creation, Payment Receipt , Credit note, Debit note all FI Transaction ).
Actually we want to use it just for information & reporting purpose. NOT FOR ANY AUTOMATIC RECEIPT \ Integration to FI > BANK Accounting \ House Bank.
Thanks

Hi.
'customer master data, what are the integrated effects to FI > Bank Accounting > House Bank ?' House bank not linked with Customer master data(only if customer affiliated company).
Bank details in customer could be used eg for invoicing(printing form)

Payment terms in customer master data

Similar Messages

Maybe you are looking for