Restrict use of payment terms

Is there a way where I could restrict use/view of payment term in the customer master data entry (FD01, XD01)?  I  have created an authorization object for ZTERM (SU20, SU21) and assigned this object (SU24) to tcode FD01, XD01.  The authorization assigned has only COD as valid payment term.  But still, using payment term other than COD is permitted.

Rhyz 
Some where in the code of FD01 & XD01, you need code which checks whether user have access to your ZTERM object .
this has to be done by ABAPer by using either user exit or Enhancement (ECC6.0).
code will be
AUTHORITY-CHECK OBJECTS 'ZTERM'
Regards,
Surpreet
e.g
AUTHORITY-CHECK OBJECT 'S_USER_AGR'
ID 'ACT_GROUP' FIELD ACTIVITY_GROUP
ID 'ACTVT' FIELD ACT_ADD.

Similar Messages

  • Incorrect Withholding TAX Split when using Installment Payment term

    Hi SAP Gurus,
    When we are using installment payments, the withholding tax is split and calculated in as many vendor positions as the installment payment term dictates. In our location (ECUADOR) it is necesary to calculate the Withholding TAX adding all the vendor positions (PstKy - 31) and posting only one Withholding tax position. When we simulate the document, we get the next snapshot:
    001 31       0000100035                                                               0.00
    002 40       5201001001 Sueldos                                          1,000.00                                       60
    003 31       0000100035 RAMOS ANDRADE CARLO                             309.64-
    004 31       0000100035 RAMOS ANDRADE CARLO                             300.54-
    005 31       0000100035 RAMOS ANDRADE CARLO                             300.54-
    006 50       2401003003 10% Retención Profe                                          30.36-
    007 50       2401003003 10% Retención Profe                                          29.46-
    008 50       2401003003 10% Retención Profe                                          29.46-
    009 40       1301003001  IVA 12%                                           107.14
    And we shoul get the next one for our needs:
    001 31       0000100035                                                               0.00
    002 40       5201001001 Sueldos                                          1,000.00                                       60
    003 31       0000100035 RAMOS ANDRADE CARLO                             250,72- ==========> (Here is made the tax disccount)
    004 31       0000100035 RAMOS ANDRADE CARLO                             389,82-
    005 31       0000100035 RAMOS ANDRADE CARLO                             389,82-
    006 50       2401003003 10% Retención Profe                                          89,28- ==========> (Here is the 3 tax positions added)
    007 40       1301003001  IVA 12%                                           107.14
    Regards,
    Esteban Moreno
    SAP FI-CO consultant

    Hi Srikanth,
    Thanks for your suggestion.
    I am looking for way in which two accounting documents are created automatically by the system having the desired values. Due to huge number of customer invoices which will need this, it will not be possible to handle it manually and will leave a room for error due to manual intervention.
    If somehow we can configure this payment term in system, then it would really help
    Regards
    Harpreet

  • Restrict changes in payment terms

    Hi All,
    We have a requirement where in we have to restrict certain users from changing the sales order payment terms. This process has to be SOX compliant also.
    This requirement is for a certain sales org.
    What are all the various ways of achieving this objective with a scalable solution.
    Thanks in advance,
    Ashish

    Hi,
    In the userexit USEREXIT_FIELD_MODIFICATION in the include MV45AFZZ...
    Check for the sales org..
    FORM USEREXIT_FIELD_MODIFICATION.
    IF VBAK-VKORG = '0100'.  " CERTAIN SALES ORG.
    disable the input for payment terms..
      IF SCREEN-NAME = 'VBKD-ZTERM'.
        SCREEN-INPUT = '0'.
      ENDIF.
    ENDIF.
    ENDFORM.
    Thanks,
    Naren

  • Restrict selection for Payment Terms on VA01/VA02

    In user exit MV45AFZZ I want field VBKD-ZTERM to be changed to certain values.
    I have other fields disable like this:
    WHEN 'VBKD-PRSDT'.
            screen-active = 1.
            screen-input = 0.
    And other fields have a condition check prior to disable them:
    IF kuagv-kunnr NE 90000.
              screen-active = 1.
              screen-input = 0.
    But now the user wants the field active but only allow some values.
    For example if the default field options can be A, B or C. That only A and B are available to select when a modification ocurrs.
    Anyone has an idea how to develop this?
    Thanks
    Regards,
    Carlos

    In USEREXIT_SAVE_DOCUMENT_PREPARE in MV45AFZZ.
    Check if the field has been changed and that the value selected its allowed, else throw an error.
    But I dont know the code to check if field VBKD-ZTERM has been changed.

  • Payment Terms not saved using BAPI_PO_CHANGE

    Hi,
    We are using BAPI_PO_CHANGE to save changes to the PO.
    When I use a Payment Term with 'Day Limit' (i. e Day Limit not zero) the Payment term field in the PO header is blank after commit. This doesnt happen for other payment terms.
    Has anyone faced this issue?
    Any suggestions will be appreciated.
    Ramesh-

    Hi ramana ,
    How r u populating the two table s?
    POCOND
    POCONDX of the bapi , can i know the code
    here u have to populate all this
    COND_TYPE
    COND_VALUE
    CURRENCY
    COND_UNIT
    COND_P_UNT
    CHANGE_ID(I for insert a new condition ,U for Update , D for delete)
    pls checjk thios and Pls ask if u have any thing.

  • Payment Term Restricted & PLD

    Hi experts,
    I met the problems bellow :
    1.  To payment term restriction because the payment terms in Sales Order --> Accounting --> Payment Terms is always change if users filled in Payment Term. How to restricted it ?
    2. How to set in PLD to differentiating among AR Invoice, AR DP Invoice, and AR Invoice + Payment? Because on print out is appeared just AR Invoice, so we can not differentiate among them. But if we can separate on each on the print out, so we can be easier than to differentiating.
    Please can help me.
    Regards,
    Agung

    I'm not sure I understand your first question, but I believe you are asking if there is field level authorization control for the Payment Terms field.  There is not.
    B1 provides document level User Authorizations for most documents, with some exceptions.
    For the PLD questions, all you need to do is launch Print Layout Designer and alter the field for Document Name.
    Change it from Invoice to A/R Down Payment Invoice for the A/R DP Invoice.

  • Maintaining payment terms for Installment payments

    Hi;
    Kindly let me know how to create payement term record for more than 4 installments.
    As in STD. 3 installments we can maintain.
    But how more than 4??????
    Thanks in advance;
    avinash

    Hi Avinash,
    you can use T. code OBB8 & OBB9 to create payment terms for installment planning.
    1. Create Payment terms in OBB8 and Assign the payment terms created in OBB9.
    2. I don't think there is any restriction on number payment terms you can create and assign. You can create and assign as many to meet your requirement.
    Hope this helps you....

  • AP Payment Terms

    Hello
    Could you please help me with the below mentioned issue
    We have two payment terms
    A15TH_P30TH3% (1st – 15th)
    A30TH_P15TH3% (16th – 31st)
    “Invoices arrived till the 15th, pay on the 30th – invoices arrived till the 30th, pay on the 15th of the following month with 3% discount”
    So invoices from the 1st – 15th we pay on the 30th with discount
    Invoices from the 16th – 31st we pay on the 15th of the following month with discount
    The Supplier payment-term in this case is A15TH_P30TH3%, because each supplier could only have one payment-term.
    For each invoice from 16th-31st of the month we have to change the payment-term to A30TH_P15TH3% to get the discount.
    If we forget to change the payment-term we lose the discount.
    We use this payment-term really often because we only pay on the 15th and 30th or 31st of the month.
    Is it possible to get a solution that we only need one payment-term for this first and second half of the month – payment term.
    Thanks for your help

    Hi,
    You do not need to create two payment terms. What you require here is proxima payment term.
    While defining the payment term in AP, enter "15" in the cut off day. In the "Due" Tab, enter "31" in Day of Month and "0" in months ahead. In the First Discount Tab, enter 3% discount and "31" in Day of Month and "0" in months ahead.
    Now, the system will automatically take due date for all the invoices received till 15th as 31st of the current months and for all the invoices received after 16th as 31st of the next month.
    Attach this Payment Term to the Supplier and use it for all the invoice. No need to manually change it while creating the invoice.
    I hope this functionality is available in the Application Version, you are working on.
    Gajendra

  • Payment term key with limit days in Extended Classic Scenario

    Hello,
    We have an SRM 4.0 implementation (SRM Server 5.0 with Support Package
    9) using the Extended Classic Scenario.
    When a shopping cart is created, it must be approved, and then a
    purchase order is generated (first locally at SRM, and then is
    replicated to the backend).
    The problem is that the payment term key (field at header level EKKO-
    ZTERM) of the backend purchase order is empty, only in cases when we use a payment term key which have several different values for the
    field "limit days" (T052-ZTAGG in backend, BBP_PAYTERM-ZTAGG in SRM).
    Example:
         ZTERM     ZTAGG
          K180           09
          K180           19
          K180           31
    If the payment term key selected has no several values for the field "limit
    days" (one single entry), the payment term key arrives correctly at the backend purchase order.
    Example:
         ZTERM     ZTAGG
          E000           00
    In SRM table BBP_PAYTERM we have upload the backend payment terms
    (using report BBP_UPLOAD_PAYMENT_TERMS). In other threads it is said that you must copy the entries generated by the report with the logical system of the SRM system, but in extended classic scenario it seems to be not necessary.
    We have already implemented note 846009, in order to use always the backend payment term, but the error didn’t get resolved.
    We have our vendor business partners mapped to the local and backend
    purchasing organizations, but it is only necessary indicate the Payment term key for the Backend Purchasing Organization.
    Regards

    hi,
    Pls see the foll notes:
    Note 576349 - Terms of payment in the ECS
    Note 541934 - Modification note: Copying base date from T052
    Note 953999 - ECS: Terms of Payment values not in PO header
    <b>Note 940453 - Backend payment term data not updated in the extended PO
    Note 945018 - Incoterms data not transferred to the back end</b>
    BR,
    Disha.
    Pls reward points for useful answers.

  • Multiple condition for payment terms

    Hi,
    I wanted to create new payment terms with multiple combination say for example
    95% Payment in Advance & Remining 5% in Net 360 days.  How to configure with multiple conditions.

    Hi
    You may have to use instalment payment terms.
    Regards

  • Payment  term issue

    we are using one payment term called BT03 that pay term is assign to vendor master at company code data and purchase data level.we; have created a P.O. in R/3 with vendor which is having same payment term after given mandatory details payment term  is reflecting.But when same vendor is SAP-SRM when user is creating a Purchase order with payment term BT03 is not reflecting i am not able to get why this error is happening. so  let us know your thought on this thread.All suggestions are welcome.

    Have you confirmed that the payment term also exists in SRM?  Not sure if you have a job that synchs them or if you manually have to do it.  Have you confirmed that you synched the vendor data between SRM and R/3?  Can you see in SRM under Manage Vendor Data the terms of payment is displayed?  I'm assuming you are NOT using Extended Classic config in SRM?

  • Payment terms with flexible downpayment option

    hi all,
    we need to design a 'Payment Terms' with a flexible down-payment option. The down-payment has to be variable and the system should accept any down-payment and divide the rest of the balance payment into monthly installments. Eg. if total amount to be paid is Rs.160000, the down-payment should be configured such that the system should accept any amount between Rs.10000 and 30,000 and divide the balance into 11 EMI's.
    To start off with, a Sales Order (VA01) is created for the complete amount and then the billing is done(VF01). The billing document is then release to FI. The system should then allow FI to post any down-payment as explained in the above example. The rest of the balance should be divided into EMI's.
    NOTE - We have to configure this on SAP R/3 ECC 6. Please advice accordingly.
    regards,
    Vivek
    Edited by: vivek_84 on Jun 22, 2009 6:38 AM
    Edited by: vivek_84 on Jun 22, 2009 6:39 AM
    Edited by: vivek_84 on Jun 22, 2009 6:40 AM

    Hello,
    There is no threshold figures for down payment can be configured.
    Try to use Instalment payment terms (OBB9).
    For this first of you must have created payment terms with reference to instalement payment terms in OBB8.
    Regards,
    Ravi

  • Certain payment terms neglected

    All-
    We are working on a SRM 5.0 classic scenario implementation. We need to use the payment terms for creating Invoices w/o PO in SRM. We realise for this we need to maintain it locally in table view BBPV_PTERM_LOCAL.
    So we are ensuring that in the replication report BBP_UPLOAD_PAYMENT_TERMS, we use both the selection criteria Data transfer from the backend system and also preassign data to the local system. Essentially this will populate data in BBP_PAYTERM for both Logical system. I.e. Data from R/3 and data in the local system which will populate the Table view BBPV_PTERM_LOCAL.
    Now the issue is that almost all payment terms get replicated locally. However, few terms get neglected and dont come over to the table view. for example a payment term like 0051 Due immediately/ Due on receipt.
    Is there some sort of setting on R/3 which is preventing this entry while using report BBP_UPLOAD_PAYMENT_TERMS??? This entry gets created in SRM in table BBP_PAYTERM with backend logical system but doesnot make an entry for the local system.
    Any ideas on why this behaviour?? We have also opened an OSS note on the same...please let me know if you guys have any suggestions.
    Thanks,
    Sundeep

    Hi Sundeep,
    BBP_UPLOAD_PAYMENT_TERMS program does not work well.I tried using this and this ask for RFC destination(LOGSYS) while replicating the payment terms.
    and when you try to see these payment terms in customzing it does not give you correct result and so result in SRM HTML screens.
    What I did for this.
    There are two tables involved in this
    BBP_PAYTERM
    BBP_PAYTERM_TEXT .
    If you see entries in table BBP_PAYTERM ,it will have data with ERPCLNTXXX system while same kind of data will not be there for SRMCLNTXXX.
    You have to copy ERPCNLTXXX data into SRMCLNTXXX data.
    To do that copy all data with SRMCLNTXXX ,go to table Entry in Menu and delete all entries.
    Then copy all ERPCLNTXXX data and go to Table Entry ,Create with template.
    You can do this is SE11 or SE16 transactions.Do similarly with BBP_PAYTERM_TEXT.Please check entries before doing it for BBP_PAYTERM_TEXT table as this table may have similar entries for SRMCLNTXXX and then you will not require to copy all.
    Actaully program recognise only Payment terms in SRM.
    Once you have done this..You can see in customzing all correct payment terms replicated.
    SPRO->SRM server->Cross application basic setting->Create payment conditions.
    I hope this helps.
    regards,nishant
    please reward if this helps

  • Payment Terms at Item Level

    Hi All,
    1.After SO Creation, When I change payment terms at Header level, Payment terms at Item level are not changing.
    2. We are using same payment terms at both Header and Item Level.(Payment terms are not getting determined from Condition Record. PT are determining from Customer master)
    3. We can change payment terms at Item manually, But the SO are in bulk.
    Anybody came across such situation.
    Thank$
    Hidayath

    Thanks Jignesh and Siva,
    The payment terms are not automatically updating only in particular sales document for Ex: SO and for Other contracts It's working as expected.
    --> I checked in VOV7 for all the Item categories. config is Ok.
    Any pointers on this issue?
    Thank$
    Hidayath

  • Payment terms not exist in contract

    Dear SAP experts,
    We are in SRM 7 and ECC 6 and using extended scenario. For payment terms we download payment terms from ECC by using program BBP_UPLOAD_PAYMENT_TERMS and entries created in table BBP_PAYTERM. When we create PO we can use this payment terms from ECC. However the odd thing happen when we create contract, we can see the paymet terms as possible selection, but if we select it we got error 'Payment term not exist in target system'. However if we create payment terms directly in SRM (using config payment conditions), then we can choose the payment term from SRM.
    But this is not making any sense as why do we need to have duplicate payment terms one coming from ECC and the other coming from SRM. Do I miss something in here? (Note that in RFx response, vendor can NOT choose payment terms locally in SRM as they can ONLY see the one coming from ECC).
    Best regards,
    John

    Hi John,
    Please implement the following note & retest this issue:
    1609905 Validation for local contracts contains errors
    Kind Regards,
    Edel.

Maybe you are looking for