Amount field KBETR mandatory in VA01

Hello Gurus,
Can you guys give me any hints on how can I set the field "amount" (KBETR) in VA01 as a mandatory field? Already tried the incompleteness procedure and pricing, but no luck so far...
Thanks!
Douglas Haraguchi

Hi Douglas,
Your requirement is not clear.... Because in the log of incompletion itself you can maintain the pricing as incomplete field. the field which you are saying is the rate field which is used to calculate the condition value of the materials.
If you maintain the pricing as one of the incomplete field you can achieve this requirement. System will through an information message that price is missing and depending on the status group it will not allow the user to process the document.
As per my understanding no need to check the specific field "KBETR" to be pulled in to log of incompletion or making it as mandatory field.
If your requirement is different then try to explain it clearly,,,
Venkat Cheedalla

Similar Messages

How to make amount field as mandatory in portal

Hi experts,
We are working on EHP5 , Ecc 6.0. I am working on claims and reimbursements module . We have already done the configurations and in the portal i need to make an amount field as mandatory . I have gone to content administration - Portal Content - Content provided by SAP- End user content - Employee self Service - I views- Benefits and payments - India- Claim Advance request . Here i have selected an iview then Right click on that we can see the properties. there i have made the field as mandatory . It is getting applicable. But when i close the particular screen and click on that iview the same screen comes across with the field not getting mandatory . Wat are the other steps which i need to make this field as mandatory and gets applicalble to all claim types. So please reply .
. So please respond experts.
Thank you
Lokesh

Hello Lokesh,
For all specific claim types while configuring customized header fields in view V_T77WWW_CLHLDC
& configuring customized multiple line fields in view V_T77WWW_CLMLDC there is an option in the form of checkbox to make those fields mandatory.
The mandatory checkbox can be seen inside the box generic properties.
I trust this clarifies.
Regards,
Pankaj

To make the "req.delivery date" field non-mandatory in VA01 Transaction

Hi All,
I want to make "req. delivery date"(RV45A-KETDAT) field non mandatory in VA01 transaction.
I have already checked on screen 4440 .This field is not mentioned as required field.
Please help me to find where can i make this field non-mandatory.
Thanks and Regards,
Dipali.

Hi,
this is a required field, as far as the standard SAP code goes: everytime this field is touched the following function is executed in programme FV45EF0V_VBEP-EDATU_EINGEBEN:
    call function 'PERIOD_AND_DATE_CONVERT_INPUT'
      exporting
        external_date     = rv45a-etdat
        external_period   = rv45a-prgbz
      importing
        internal_date     = vbep-edatu
        internal_period   = vbep-prgrs
        ev_date_in_past   = lv_date_in_past
        ev_period_in_past = lv_period_in_past
      exceptions
        no_data           = 1
        period_invalid    = 2
        date_invalid      = 3.
    case sy-subrc.
      when 1.
        set cursor field 'RV45A-PRGBZ' line sy-stepl.
* Bitte Datum eingeben
        message e394.
The only way to avoid this is create an implicit enhancement at the beginning of this form, copy the exisitng code in there, delete the message after WHEN 1. and put RETURN at the end of the enhancement. But this would be HIGHLY UNRECOMMENDED, because I am positive you cause a lot of misery later on in the process: this field is mandatory for a reason!
Roy

Help reqd for coding to assign the field as mandatory.

HI all,
I got the user exit and also assigned the component as "EXIT_SAPLMRIM_002"..im now here to create a code under the include program of "ZM08U09"....for to make the amount field as mandatory(obligatory)..with some pop-up message...
how to do that....
Do u people have any experience on this...pls post ur comments on urgent basis.
thanks & regards
sankar.

Hi Sriram.P
thanks for ur prompt reply
...but actually,my problem is...i dont know the exact table for miro (invfp-wrbtr showing in the screen)....i've already prepared some coding but the table i've mentioned is not the correct one...
Do u know the table for Incoming invoices records (MIRO)
thanks & regards
sankar.

Enable Amount field (KOMV-KBETR) in VA01 for Documen type DR (Debit Note)

Hi All,
Is it possible to enable the input of Amount field in item level at the VA01 screen?
I can input it in item level at VA01 screen for Normal order, but not found when input the Debit note...
The user want to input it in the main screen not want to input in Condition screen...
Please help.
Thanks.
Terry

Hi Raja,
Thanks for your reply.
I found that the field exist in Document type OR, when I change the Screen sequence group from GA to AU,
the field KOMV-KBETR appear.
But is it possible to change my own Screen sequence group, and assign usable fields in the group?
Terry

How to make Sales Office field mandatory in VA01 initial screen?

Hi,
How to make Sales Office field mandatory in VA01 initial screen? I mean in the first screen where we enter the document type and the sales area?
Regards,
Ajit

Dear Deepak,
Thanks for the clarification.
But, as far, I have understood the query - it is very simple and that is..
Whenever one creates a Sales Order (T.Code: VA01), Parameter: Sales Office needs to be mandatory (for all Sales Order, irrespective of Customer Account).
Until-unless, user won't enter the parameter: Sales Office, System will not lead to next page (now, here we need to enter Customer/ material etc...).
I have answered the query, in this regards, only.
Best Regards,
Amit.
Note: Pls. correct me, if I am wrong. Thanks for everyones guidance.

Re:Profit center as mandatory for VA01

Hi Experts,
Good Morning,
my issue is if i didnt give profit center in va01 the document should not be saved, so in OMS9 which field sel.group (eg:name-0001,0002.....) i need to go and maintain as "Reqd Entry"
Thanks in advance & points will be assign for useful answers,
SAP UK.

For information, Profit Center is flowing in sale order based on the value you maintain in material master. So the first option is make the material master field as mandatory.
Make the said field in material master as mandatory. To set this, go to OMS9, input 8 in "Field sel.group" and enter. Double click on Profit Center and choose the option "Reqd Entry" and save.
Now without maintaining Profit Center, you cannot save the material master.
So while creating sale order for that material, the profit center will flow automatically and no need to maintain the same.
Of course, for sale order, you can make this field as mandatory and it is blank, it cannot be said. To achieve this, Go to OVA2, block Sales - Item and double click on Procedures. There select Standard Item and click on Fields. There maintain the following:-
Table::::Fld name::::::Description::::::::Screen:::Status
VBAP::::::PRCTR::::::::Profit Center::::::::PKNT:::::00
Now without Profit Center, you cannot save the sale order.
thanks
G. Lakshmipathi

Amount field of VK11 isnt fetching from flatfile when im performing it'sBDC

Dear Guru,
Here i have encountered a typical issue.
Im Performing BDC for VK11 (Create Condition Record) with "Key Combination" --->> "Location, Material Code (Base Price for Longs)".
While I am running this BDC ( source code attached below) in All screen mode every datas which are of type "CHAR" like--->>
Condition type(kschl) ,
Plant(werks) ,
Material No(matnr),
Valid From date(datab),
Valid To date(datbi),
Rate Unit(konwa) are coming properly from flatfile except
Rate (condition amount - KBETR) which is are of data type "CURR".
So guru I want to know what code i should add into my below bdc prog to fetch data properly into RATE - Condition amount field which is of type " CURR".
Pls Help.
Source Code:
REPORT z_bdc_vk11_famd
       NO STANDARD PAGE HEADING LINE-SIZE 255.
*& DATA-DECLARATION
TYPES: BEGIN OF t_cust,
            kschl LIKE rv13a-kschl,
            werks LIKE komg-werks,
            matnr LIKE komg-matnr,
            kbetr LIKE konp-kbetr,
***            konwa LIKE konp-konwa,
            datab LIKE rv13a-datab,
            datbi LIKE rv13a-datbi,
       END OF t_cust.
TYPES: BEGIN OF t_sucrec,
         cnum TYPE komg-werks,
         cnam TYPE komg-matnr,
END OF t_sucrec.
TYPES: BEGIN OF t_errrec,
       lineno TYPE string,      "Line Number
      message TYPE string,      "Error Message
END OF t_errrec.
DATA: v_file TYPE string,      "Variable for storing flat file
      it_cust TYPE STANDARD TABLE OF t_cust, "Internal table of Customer
      wa_cust LIKE LINE OF it_cust, "Workarea of Internal table it_cust
    it_sucrec TYPE STANDARD TABLE OF t_sucrec,
                                      "Internal table of Success records
    wa_sucrec LIKE LINE OF it_sucrec,
                                   "Workarea of Internal table it_sucrec
    it_errrec TYPE STANDARD TABLE OF t_errrec,
                                   "Internal table of Error records
    wa_errrec LIKE LINE OF it_errrec,
                                   "Workarea of Internal table it_errrec
    it_bdctab LIKE bdcdata OCCURS 0 WITH HEADER LINE,
                                    "Internal table structure of BDCDATA
it_messagetab LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE,
                                    "Tracing Error Messages
       v_date LIKE sy-datum, "Controlling of session date
      v_index LIKE sy-tabix, "Index Number
     v_totrec TYPE i,         "Total Records
     v_errrec TYPE i,         "Error Records
     v_sucrec TYPE i,         "Success Records
    v_sesschk TYPE c.         "Session maintenance
*& SELECTION-SCREEN
SELECTION-SCREEN: BEGIN OF BLOCK blk1 WITH FRAME TITLE text-001 NO
INTERVALS.
PARAMETERS: p_file    TYPE rlgrap-filename.
"rlgrap-filename is a predefined structure
SELECTION-SCREEN: END OF BLOCK blk1.
SELECTION-SCREEN: BEGIN OF BLOCK blk2 WITH FRAME TITLE text-002 NO
INTERVALS.
PARAMETERS: p_mode    LIKE ctu_params-dismode DEFAULT 'N',
            p_update LIKE ctu_params-updmode DEFAULT 'A'.
SELECTION-SCREEN END OF BLOCK blk2.
*& INITIALIZATION
INITIALIZATION.
v_date = sy-datum - 1.
*& AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      program_name = syst-cprog
      dynpro_number = syst-dynnr
      field_name    = ' '
    IMPORTING
      file_name     = p_file.
*& START-OF-SELECTION
START-OF-SELECTION.
v_file = p_file.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename                = v_file
      filetype                = 'ASC'
      has_field_separator     = 'X'
    TABLES
      data_tab                = it_cust
    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.
*& END-OF-SELECTION
END-OF-SELECTION.
LOOP AT it_cust INTO wa_cust.
    v_index = sy-tabix.
    PERFORM bdc_dynpro      USING 'SAPMV13A' '0100'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RV13A-KSCHL'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=ANTA'.
    PERFORM bdc_field       USING 'RV13A-KSCHL'
                                  wa_cust-kschl.
    PERFORM bdc_dynpro      USING 'SAPLV14A' '0100'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RV130-SELKZ(01)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=WEIT'.
    PERFORM bdc_dynpro      USING 'SAPMV13A' '1595'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RV13A-DATBI(01)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'KOMG-WERKS'
                                  wa_cust-werks.
    PERFORM bdc_field       USING 'KOMG-MATNR(01)'
                                  wa_cust-matnr.
    PERFORM bdc_field       USING 'KONP-KBETR(01)'
                                  wa_cust-kbetr.
    PERFORM bdc_field       USING 'KONP-KONWA(01)'
                                  'INR'.
    PERFORM bdc_field       USING 'RV13A-DATAB(01)'
                                  wa_cust-datab.
    PERFORM bdc_field       USING 'RV13A-DATBI(01)'
                                  wa_cust-datbi.
    PERFORM bdc_dynpro      USING 'SAPMV13A' '1595'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'KOMG-MATNR(01)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=SICH'.
    CALL TRANSACTION 'VK11' USING it_bdctab
                             MODE p_mode
                           UPDATE p_update
                    MESSAGES INTO it_messagetab.
    IF sy-subrc = 0.
*& reading success records to corresponding internal table
      READ TABLE it_messagetab WITH KEY msgtyp = 'S'.
      IF sy-subrc = 0.
*        wa_sucrec-cnum = it_messagetab-msgv1.
        wa_sucrec-cnum = wa_cust-werks.
        wa_sucrec-cnam = wa_cust-matnr.
        APPEND wa_sucrec TO it_sucrec.
        CLEAR wa_sucrec.
      ENDIF.
    ELSE.
*& reading error records to corresponding internal table
      READ TABLE it_messagetab WITH KEY msgtyp = 'E'.
      IF sy-subrc = 0.
        CALL FUNCTION 'FORMAT_MESSAGE'
          EXPORTING
            id = sy-msgid
            no = it_messagetab-msgnr
            v1 = it_messagetab-msgv1
            v2 = it_messagetab-msgv2
            v3 = it_messagetab-msgv3
            v4 = it_messagetab-msgv4
          IMPORTING
            msg = wa_errrec-message.
        wa_errrec-lineno = v_index.
        APPEND wa_errrec TO it_errrec.
        CLEAR wa_errrec.
      ENDIF.
    ENDIF.
    CLEAR : it_bdctab, it_messagetab.
    REFRESH: it_bdctab, it_messagetab.
ENDLOOP.
DESCRIBE TABLE it_cust LINES v_totrec.
DESCRIBE TABLE it_errrec LINES v_errrec.
DESCRIBE TABLE it_sucrec LINES v_sucrec.
PERFORM disp_data.
SKIP 2.
IF v_sucrec > 0.
    PERFORM disp_success_data.
ENDIF.
SKIP 2.
IF v_errrec > 0.
    PERFORM disp_error_data.
ENDIF.
*& Form bdc_dynpro
*# text
*# -->P_0104 text
*# -->P_0105 text
FORM bdc_dynpro USING program dynpro.
CLEAR it_bdctab.
it_bdctab-program = program.
it_bdctab-dynpro   = dynpro.
it_bdctab-dynbegin = 'X'.
APPEND it_bdctab.
ENDFORM. " bdc_dynpro
*& Form bdc_field
FORM bdc_field USING fnam fval.
CLEAR it_bdctab.
it_bdctab-fnam = fnam.
it_bdctab-fval = fval.
APPEND it_bdctab.
ENDFORM. " bdc_field
*& Form disp_data
FORM disp_data .
ULINE (45).
WRITE : / sy-vline,
4 'FAMD Price Master UPDATE SUMMARY'(004) COLOR 1,
45 sy-vline.
ULINE /(45).
WRITE : / sy-vline,
'Total Records Processed'(007),
28 '=',
30 v_totrec,
45 sy-vline,
/ sy-vline,
'Error Records'(005),
28 '=',
30 v_errrec,
45 sy-vline,
/ sy-vline,
'Successful Records'(006),
28 '=',
30 v_sucrec,
45 sy-vline.
ULINE /(45).
ENDFORM. " disp_data
*& Form disp_success_data
FORM disp_success_data .
ULINE (45).
WRITE : / sy-vline,
14 'Successful Records'(012) COLOR 1,
45 sy-vline.
ULINE /(45).
WRITE : / sy-vline ,
'Plant Number'(010) COLOR 2,
17 sy-vline,
25 'Material Number'(011) COLOR 2,
45 sy-vline.
ULINE /(45).
LOOP AT it_sucrec INTO wa_sucrec.
    WRITE: / sy-vline ,
    wa_sucrec-cnum,
    17 sy-vline,
    19 wa_sucrec-cnam,
    45 sy-vline.
ENDLOOP.
ULINE /(45).
ENDFORM. " disp_success_data
*& Form disp_error_data
FORM disp_error_data .
ULINE (90).
WRITE : / sy-vline,
35 'Error Records'(013) COLOR 1,
90 sy-vline.
ULINE /(90).
WRITE : / sy-vline,
'Record Number'(008) COLOR 2,
sy-vline,
37 'Reason for error'(009) COLOR 2,
90 sy-vline.
ULINE /(90).
LOOP AT it_errrec INTO wa_errrec.
    WRITE : / sy-vline,
    wa_errrec-lineno,
    17 sy-vline,
    wa_errrec-message,
    90 sy-vline.
ENDLOOP.
ULINE /(90).
ENDFORM. " disp_error_data
Flat file Sequence:
Condition Type     Plant     Matrial No     Rate      Validity start date     Validity end date

I worked out n i hav found the solution

Need Profit centre field as mandatory field in the sales order

Dear All,
Normally Profit center data maintained in the material master, same data will get coipied to the sales order while creating sales order in VA01 transaction.
My requirement is if profit center data is not maintained/available in the sales order system should give the error message
For this I need Profit center field as mandatory field in the sales order(VA01).
Can you please give possibilities ASAP.
Give the SHD0 maintenance step by step.
Regards,
Murali.

Hi Murali
I beleive that you are talking about the Profit centre field not maintined in sales order hence not picked in delivery and billing and there is an FI posting error (GL account error) because of that
Profit centre is maintained in MMR and the same flows thro the sales cycle and i am quite sure if maintained in MMR it will be picked automatically and no need to make it mandatory in sales order( as the purpose is already solved)
But there is no standard option in SAP like (even if Account assignment category of the material is not maintained in MMR it can be given in VF02 and the document can be released for accounting) to give the Profit centre in the billing and release the same
Profit centre field field is picked from masters and flows in the entire flow and that field is greyed out (like no option of inserting it inbetween)
As told by others incompletion log in sales doc type will take care for future orders and for the already created orders the standard option is cancel billing, reverse delivery and open the sales order and give Profit centre field and process it (if only a few orders are there)
But if the already created orders are many then from the FI Area you need to go for development ( we also faced this issue as profit center not maintained in MMRs and hence accounting got hit and there were tons of billing docs and our FI consultant made some development to open it and solve it) FI consultant should be able to do this for already created orders
Instead of making Profit centre field as mandatory field in the sales order better make it a mandatory entry in MMR
Regards
Raja

User defined function to check the NULL and 0.00 value in a Amount field

Hi Experts,
I have one scenario in which i have amount field in Data type.
I have to create one UDF which will do the following thing.
1. If the amount field is Null it should throw an exception in mapping.
2.If the amount field is 0.00 it should throw an exception in mapping.
3. For all other cases it should pass the amount value to the target.
Can anyone provide me the code For this UDF.
Thanks in advance.

Hi,
You can add this logic to the UDF. Here var1 is the input string.
java.math.BigDecimal b=new java.math.BigDecimal(var1);
if(b.compareTo(new java.math.BigDecimal("0.00"))<=0)
//write your logic for values less equal to zero
One small request, if you think your question has been answered, properly and correctly, could you please kindly if possible close down this thread. It helps people who look for solutions to similar problem.
regards
Anupam

DIsplaying WRBTR (AMOUNT FIELD)WITHOUT DECIMAL PLACES

Dear all,
I am facing a problem in displaying amount field in alv report. I have two currency keys (US dollar and Japan yen). if it is japan yen I should not have to show decimal places and if it is US dollar I should show decimal places.
How can I do it in a alv report if I have only one output amount field?
thanks
Ranjan.

Hi chittaramjan,
1. use this kind of funda (just copy paste in new program)
Important things
a) one extra field in internal table
declared in the same exact fashion
waers LIKE tcurc-waers,
b) Populate this field
c) REST THE System will take care
   (based upon country settings)
2.
REPORT abc.
TYPE-POOLS : slis.
DATA : alvfc TYPE slis_t_fieldcat_alv.
DATA : BEGIN OF itab OCCURS 0,
        f1 LIKE P0008-BET01,
        waers LIKE tcurc-waers,
        END OF itab.
START-OF-SELECTION.
itab-f1 = '-4.15'.
itab-waers = 'KRW'.
APPEND itab.
itab-f1 = '4.68'.
itab-waers = 'GBP'.
APPEND itab.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
    EXPORTING
      i_program_name     = sy-repid
      i_internal_tabname = 'ITAB'
      i_inclname         = sy-repid
    CHANGING
      ct_fieldcat        = alvfc.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
    EXPORTING
      i_callback_program      = sy-repid
      it_fieldcat             = alvfc
    TABLES
      t_outtab                = itab
    EXCEPTIONS
      OTHERS                  = 2.
regards,
amit m

Amount field getting rounded up when run in background

Hello All,
when i run a report in foreground the amount value(KBETR) is displaying properly with the value 12.78.But when the same report is run in background it is displaying 13.what should be done?
Thanks,
Rakesh.

Hi,
Try to fetch records in smaller chunks and process them. For example, if you are trying to fetch records for one year, instead of single query, try to fetch in 12 sets for each month. Fetch first month and process the records and put them in the output internal table. Then go for next month and so on. Anyway your program is running in background. There will not be any user complaint also. The solution might sound bit funny. But it works.
Regards,
Hema

Error in Report: Next to amount field i could see 'ERROR' word in report

Guys,
Problem in Report: Next to amount field i could see 'ERROR' word in report
Eg: Invoice Amount : "1200ERROR" it should be like "$1200".
Pls help where do i need to check.
Thanks

Ajeet wrote :
Hi,
It can heppens if all the records getting aggregated in the report are of different currencies and not belonging to one currency.
Do a currency conversion for the key figures and make them all with same currency.
See if the records in the cube for the selection which you have given in the report gives you records with different currency and if it is true then as above said.
Thanks
AJeet
Are you sure ???
The mixed unit values will be displayed as * (by default unless its changed).
ERR comes if unit is not maintained.

OIM 11g R2 - Setting a field as mandatory while provisioning through catalo

Hi,
May I know how i can make a field as mandatory (Red Asterick) while trying to provision an account through catalog wizard.I dont see any option to set required=true while creating a form for an application instance.Thanks.

login to sysadmin-> create sandbox-> go to form designer->select your form now click on customize link(right top corner)->select your attribute and set the required field as true and then save it. finally export sandbox. run catalog sync job. and then verify if attribute is mandatory in the request form/dataset or not.
same mentioned in R2 release note

Length of amount field in New GL at the document entry

Hi,
1) At present I am working on ECC 6, EhP 4 with New GL Activated & Old GL "Not deactivated" (i.e deactivate update of Classic General Ledger GLT0 not done).
2) The total table (FAGLFLEXT) & Line item table (FAGLFLEXA) field in new GL has amount field length as 23 digit.
3) When I am trying to enter any FI Document in SAP, using transaction code F-02 or FB60 etc, the length of amount field is coming as 13 digit. I am not able to enter higher value
Question:-
a) Is the above issue due to "non-deactivation" of "Old GL"? As per my understanding, it is not, but wanted your opinion.
b) Is there any configuration which needs to be done to increase the length of the amount field at transaction level?
Thanking you in advance
Santosh Agarwal

a) Is the above issue due to "non-deactivation" of "Old GL"? As per my understanding, it is not, but wanted your opinion.
No, it is not.
b) Is there any configuration which needs to be done to increase the length of the amount field at transaction level?
No, there isn't. The field length that is appearing during document entry is really dictated by the data type of fields such as DMBTR, WRBTR in table BSEG; which is CURR (13,2). Although the GL view (FAGLFLEX* tables) have longer length, the limitation in entry view (BSEG, etc.) stays as 13,2.

Amount field KBETR mandatory in VA01

Similar Messages

Maybe you are looking for