Layout key SAPSFCAS27

Gurus,
How to add and remove the fields from Layout key SAPSFCAS27.
I wants to add MATNR and to remove some fileds.
It is under Overall profile SAPSFCG014 >> Table SAPSFCL015 >> Layout ID >> SAPSFCLA24 >> Chart No 02 2nd chart (dispatched) >> Grouping SAPSFCGR02 >> Layout key SAPSFCAS27.
Thanks
Suresh

Gurus,
Can any body please look in to this issue.
Thanks
Suresh

Similar Messages

Add new field in customizing of define layout keys

hi
i want to add new table & field in customizing of define layout keys of capacity leveling.
pls guide
If you are asking a question, please mark your thread as a question. Otherwise you cannot award points for appropriate answers.
-Paul
(Moderator)
Edited by: Paul Meehan on Mar 9, 2012 10:49 AM

Hi,
In spro -->produciton -->Capacity requirements planning -->Capacity levling and evaluation -->Strategy -->Define sequence and layout keys .. here u can add a field ..this layout key is later used in Planning profile and this planning profile is used in Overall profile .. thus while executing capapcity leveling selecting that particular Overall profile ..

Address format(address layout key problem)

Hi All,
There seems to be a problem the way FM address_into_printform is formatting the address.
Address currently on the form is coming like below:
AGRI-M LTD
Vasisk Aprilso Str 138. PB 135
BG-4003 PLOVDIV
Address should come as below:
AGRI-M LTD
Vasisk Aprilso Str 138. PB 135
4003 PLOVDIV
BULGARIA
Issue here is that country BG(Bulgaria) which should come as "BULGARIA" and not just as "BG"(This is just a short form).
I debugged the function module and i found that when address layout key(t005-addrs) is set in customizing as "001" then system is printing the third line as "BG" but when I removed the "001"(in debugging) then it translates it to "BULGAIRA"(which is required).
I did not throughly debugg to see exactly at what time this happens(when it is set to BG and when it is set BULGARIA).
What do you think ? I know in customizing, removing this value 001 will work but do you have any idea whether it will create any problem for address format when it comes to priority(street over postal code or postal code over street).
Is there any other workout so that format comes as required.
Regards,
Marc

Hello,
In transaction OY01 or IMG menu path:
General Settings-> Set countries-> Define countries-> Position JP and
then go to the details.
You will see an address layout structure key. The standard for Japan is
013. For more information on the address layout structure key, place
your cursor in the field and press the F1 help. The documentation is
very complete.
They are based on different national and international guidelines and
norms, including:
ISO 11180,
contracts of the World Postal Union (Seoul 1994),
international address samples from the World Postal Union
as well as the available rules of the individual countries.
"Customers can program their own formatting routines using a customer
exit. The SZAD0001 SAP enhancement has been defined in development class
SZAD for this (-> transaction CMOD)."
Regards,
David

Invalid Layout Key for the specified Integrator

I have created a new Integrator, designed the layout and created a form function. Whe I click on the form function from the responsibility, I am getting the below error.
20009: <layout key> is invalid Layout Key for the specified Integrator
Please help me resolving this error.

Please see if (Creating Lines Using BEE Spreadsheet Interface Errors With '801:PAY_BATCH_LINES_CRT is an invalid Layout Key for the specified Integrator' [ID 1176075.1]) is applicable.
Thanks,
Hussein

Anyone know of "Address Layout Key" for India?

I am currently using 001 in the country code settings (transaction OY01), but I am concerned that this is not technically correct. My key user in the country appears to be indicating that there is a dash between the city and postal code for address data in India. I have been reviewing note 117557 amongst others, but nothing clearly stands out for India.
Anyone have any insights into this further?
Thanks,
Jay

Michael,
The system I am on is SAP_APPL, SAPKH47022. I checked in the configuration and key 010 points to "Postal code before city without country code". This would not meet the address requirements for India. The closest one that I seem to have available in configuration is 008 "Singapore (postal code after city)". This seems to get things aligned as per my business user's request and what I can see on the India Post website. Again, I appreciate any help or insight you can provide.
BR, Jay

View Crystal Report Layout for my UDO Form

Hi all,
I try to view a report created for my UDO form. I set all settings in Administration -> Setup -> General -> Report and Layout Manager. Now I wonder what should be assigned to eventInfo.LayoutKey. I tried assigned report's DocCode from RDOC, DocEntry of my UDO object or UDO Code but nothing works. Always get an error: Incorrect format of argument or something like that - I didn't get an error in English so I tried to translate it.
How to show a report layout for my UDO form?
Regards
Szymon Lipnicki

Hi and thanks for Your reply.
Help file contains example how to open report layout prepare in Crystla Reports designer for UDO form.
//Add Layout Key Event Handler
SBO_Application.LayoutKeyEvent += new SAPbouiCOM._IApplicationEvents_LayoutKeyEventEventHandler(SBO_Application_LayoutKeyEvent);
void SBO_Application_LayoutKeyEvent(ref SAPbouiCOM.LayoutKeyInfo eventInfo, out bool BubbleEvent)
    BubbleEvent = true;
    if (eventInfo.ReportTemplate == "A001" && eventInfo.ReportCode == "A001001")
        eventInfo.LayoutKey = 1; //Set the key of the layout
I am using SAP 8.81.
Regards
Szymon

Grouping Key Rows In HTMLB Tableview BSP

Hello Experts,
I've a HTMLB Tableview in BSP Application. I need to group the key rows with same value into one.
Current Layout
KEY VALUE 1    VALUE 2
A       X                 Y
A       X                 Y
B       X                 Y
B       X                 Y
Required Layout
KEY VALUE 1    VALUE 2
A       X                 Y
          X                 Y
B       X                 Y
         X                 Y
It's somewhat similar to grouping the key rows in ALV. Not sure how to achieve this in BSP.
Please help....
Regards,
Satyajit
PS: Posted this thread in BSP Forum earlier and haven't got any response yet. So reposting it in ABAP General for a quick response.

Hi Satyajit Mohapatra,
please refer to fixedColumns. Therefore check on your system:
BSP: SBSPEXT_TABLE
Page: TableViewFixedColumns.bsp
There you can find the solution.
Regards, Jonas

Smart Form problem with address layout

Hello everyone,
I need your help please for a smart form problem. We need the address layout for great britain with street1, street2 etc. but currently street2 is alligned before street1.
We are using the FM ADDRESS_INTO_PRINTFORM (SAP standard address node) and according to the documenation the layout for GB is different as we see it currently.
We have checked the sold-to and all contact persons, they have as country GB and language EN maintained.
In customizing for address screen layout there is nothing chosen (tested to set up Europe, but did not change anything).
For the customizing 'specify my countries...' we have maintained GB as country with the address layout key 006, vehicle country key GB and language key EN.
For the described setting shouldn't there be designed the address in our smart forms according to 006? Anyhting in customizing we missed?
Thanks a lot for your answers.
Torsten

Hi,
Try to use line priority of FM, below is a brief of documentation. You can read it more in FM documentation:
Control Parameters
See also the parameter documentation.
ADDRESS_TYPE - Address type (from 3.0C)
There are three types of address:
Address type '1': addresses of firms or organizations; the address
structure which is used in most SAP applications as 'Address'.
Address type '2': address of a person
Address type '3': work address, usually the address of a contact person
in a company
The default value SPACE for the address type is handled like type '1',
and is needed for the upwards-compatibility of the function module.
Which parameters are used for which address type is explained in the
ADDRESS_TYPE parameter documentation.
The three character "address layout key" of the recipient country (LAND1) controls which of the available country-specific routines is used to format addresses for the country in question. This key is stored in field T005-ADDRS and is entered in Customizing under Global settings -> Set countries -> Define countries, on the detail screen under "Address layout key".
Keys for customer routines in the SAP enhancement SZAD0001 can be
maintained via the transaction SM30 (extended table maintenance),table
name T005A, in the customer name range, and be assigned in country customizing.
The address attributes are passed in the structures ADDRESS1 (type 1), ADDRESS2 (type 2), ADDRESS3 (type 3) or ADRSWA_IN (type SPACE).
NUMBER_OF_LINES (ADRSWA_IN-ANZZL)
The number of lines available for the address layout. If the number of
lines is not sufficient for the complete layout of an address, then
lines are consecutively suppressed according to the rules of the country in question. Use the parameter LINE_PRIORITY (ADRSWA_IN-PRIOR) overrules the standard sequence in which the output lines are to be suppressed.
LINE_PRIORITY (ADRSWA_IN-PRIOR)
If not equal to SPACE, this field overwrites the standard sequence in
which the lines are suppressed if the available number of lines ANZZL is
insufficient.
The standard sequence is defined as follows:
Type 1:   'AP43HRT7I86LC2BS5O'       (GB: 'APRT4327I86CBS5LO')
Type 2:   'APHRT7I86LCBS5O'          (GB: 'PRT7I86CBS5LO')
Type 3:   'APF43HR7I86TLC2BSND5O'    (GB: 'APRT4327I86CBS5LNDIO')
where (if they occupy a line of their own):
A = Title
P = Mandatory empty line 1
F = Function of the contact person in the company
4 = Name 4
3 = Name 3
H = Different city
R = Region
T = District
L = Name of country
C = Postal code
T = District
7 = Street 3 (field STR_SUPPL2)
I = Street 5 (field LOCATION)
8 = Street 4 (field STR_SUPPL3)
6 = Street 2 (field STR_SUPPL1)
L = Country
C = Postal code
2 = Name 2
B = PO Box
S = Street or PO Box
5 = c/o name
N = Name (and title) of a person
D = Department
O = City
Which of these attributes are available for maintenance can vary. All
fields exist in Business Address Services.
STREET_HAS_PRIORITY (ADRSWA_IN-WAREN)
'X': Street has priority over PO Box (delivery address for example)
' ': PO Box has priority over street. This is the default value.
regards,

Error While Showing Layout

Hello All,
I am trying to use the new Crystal Reports Integration For Add-Ons functionality in the latest patch levels. I have created a new report type, and than imported crystal report for this new report type.
After this, in my add-on, on the form I have specified this report type. Subsequently, I am catching the LayoutKeyEvent, and setting the layout key from my form.
While running the add-on, when I click on the preview or print button - it opens the report - but 2 things happen:
a) It shows an error saying - Input String is not in correct format
b) It is not able to set the DocKey@ parameter of the document layout - and hence it opens a window for entering the parameter value.
I have tried various methods, possibilities, but nothing worked out. Also, there is no detailed documentation available for this at the moment.
If any of you have tried this and have been able to do so successfully, please let me know, what could be possible wrong.
Thanks,
Rahul Jain

hi,
From A point "Input String was not in a correct format" means
The length of the input string was greater than u Specified.

Splitter ALV container + 2 layout definitions

Hello,
I wrote an ALV report using splitter container. In the upper part of my report I need to define a layout , and another one for the bottom part.
Also in my selection screen there are 2 parametrets for the upper and the lower layouts.
I have 1 problems :
B. when I use F4 functionalty from the selection screen for the upper part I get also layout of the lower part, and the samefor the lower part .
attach is a part of the code.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_lay01.
PERFORM f4_layouts USING if_salv_c_layout=>restrict_none CHANGING p_lay01.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_lay02.
PERFORM f4_layouts_sec USING if_salv_c_layout=>restrict_none CHANGING p_lay02.
FORM f4_layouts   USING i_restrict TYPE salv_de_layout_restriction
                  CHANGING c_layout TYPE disvariant-variant.
DATA: ls_layout TYPE salv_s_layout_info,
        ls_key    TYPE salv_s_layout_key.
ls_key-report = sy-repid.
ls_layout = cl_salv_layout_service=>f4_layouts(
    s_key    = ls_key
    restrict = i_restrict ).
c_layout = ls_layout-layout.
ENDFORM.                    " F4_LAYOUTS
FORM f4_layouts_sec   USING i_restrict TYPE salv_de_layout_restriction
             CHANGING c_layout TYPE disvariant-variant.
DATA: ls_layout TYPE salv_s_layout_info,
        ls_key    TYPE salv_s_layout_key.
ls_key-report = sy-repid.
ls_layout = cl_salv_layout_service=>f4_layouts(
    s_key    = ls_key
    restrict = i_restrict ).
c_layout = ls_layout-layout.
ENDFORM.                    "
screen 100.
CREATE OBJECT g_custom
    EXPORTING
      container_name = 'CONTAINER'.
CREATE OBJECT o_splitter
    EXPORTING
      parent = g_custom
      rows    = 2
      columns = 1.
CALL METHOD o_splitter->get_container
    EXPORTING
      row       = 1
      column    = 1
    RECEIVING
      container = o_grid1.
CALL METHOD o_splitter->get_container
    EXPORTING
      row       = 2
      column    = 1
    RECEIVING
      container = o_grid2.
cl_salv_table=>factory( EXPORTING r_container    = o_grid1
                         IMPORTING r_salv_table   = gr_table1
                         CHANGING t_table        = gt_printout_main ).
cl_salv_table=>factory( EXPORTING r_container    = o_grid2
                          IMPORTING r_salv_table   = gr_table2
                          CHANGING t_table        = lt_printout_second ).
cl_salv_table=>factory( IMPORTING r_salv_table = gr_table
                          CHANGING t_table = gt_alv_data1 ). "<tb> ).
lr_layout = gr_table1->get_layout( ).
lu_layout = gr_table2->get_layout( ).
*... §4.1 set the Layout Key
ls_key-report = sy-repid.
lr_layout->set_key( ls_key ).
lu_layout->set_key( ls_key ).
*... §4.2 set usage of default Layouts
lr_layout->set_default( abap_true ).
lu_layout->set_default( abap_true ).
*... §4.3 set Layout save restriction
lr_layout->set_save_restriction( if_salv_c_layout=>restrict_none ).
gs_test-layout    = p_lay01.
lr_layout->set_initial_layout( gs_test-layout ).
lu_layout->set_save_restriction( if_salv_c_layout=>restrict_none ).
gs_test-layout    = p_lay02.
lu_layout->set_initial_layout( gs_test-layout ).
lr_layout = gr_table2->get_layout( ).
lr_layout->set_save_restriction( if_salv_c_layout=>restrict_none ).
*... §4.1 set the Layout Key
ls_key-report = sy-repid.
CONCATENATE ls_key-report 'SEC' INTO ls_key-report.
lr_layout->set_key( ls_key ).
lr_layout->set_default( abap_true ).
gs_test-layout = p_lay02.
lr_layout->set_initial_layout( gs_test-layout ).
lr_events = gr_table1->get_event( ).
lu_events = gr_table2->get_event( ).
CREATE OBJECT ge_events.
SET HANDLER ge_events->on_user_command FOR lr_events.
SET HANDLER ge_events->on_double_click FOR lr_events.
CREATE OBJECT gu_events.
SET HANDLER gu_events->on_user_command FOR lu_events.
SET HANDLER gu_events->on_double_click FOR lu_events.
lr_selections = gr_table1->get_selections( ).
lr_selections->set_selection_mode( if_salv_c_selection_mode=>multiple ).
lu_selections = gr_table2->get_selections( ).
lu_selections->set_selection_mode( if_salv_c_selection_mode=>multiple ).
lr_columns = gr_table1->get_columns( ).
lr_columns->set_optimize( abap_true ).
lu_columns = gr_table2->get_columns( ).
lu_columns->set_optimize( abap_true ).
PERFORM create_toolbar.
PERFORM set_zebra_pattern.
PERFORM set_columns_technical USING lr_columns lu_columns.
PERFORM sort.
PERFORM add_button_to_pf_status.
*-> Display the grid, for this we use the DISPLAY method
CALL METHOD gr_table1->display.
CALL METHOD gr_table2->display.
Please advise.
Thanks
Yifat

Hi Ifat
to access layouts for tab and bottom independantly, use the 'HANDLE' element of is_variant as follows
at selection-screen on value-request for p_tvar.
is_variant-report = sy-repid.
is_variant-handle = 'TOP'.
call function 'REUSE_ALV_VARIANT_F4'
    exporting
      is_variant                = is_variant
      i_save                    = 'A'
      i_display_via_grid        = 'X'
    importing
      es_variant                = is_variant
    exceptions
      not_found                 = 1
      program_error             = 2
      others                    = 3
if sy-subrc <> 0.
else.
    p_tvar = is_variant-variant.
endif.
at selection-screen on value-request for p_bvar.
is_variant-report = sy-repid.
is_variant-handle = 'BOT'.
call function 'REUSE_ALV_VARIANT_F4'
    exporting
      is_variant                = is_variant
      i_save                    = 'A'
      i_display_via_grid        = 'X'
    importing
      es_variant                = is_variant
    exceptions
      not_found                 = 1
      program_error             = 2
      others                    = 3
if sy-subrc <> 0.
else.
    p_bvar = is_variant-variant.
endif.
Regards
Joel

[SOLVED] Identifier of Meta key in xkb/symbols

Hi! I used to swap CapsLock with Esc for better vim usability by just adding the following lines to xkb/symbols at the section corresponding to my layout:
key <CAPS> { [ Escape, Escape, Escape, Escape ] };
key <ESC> { [ CapsLock, CapsLock, CapsLock, CapsLock ] };
(Maybe it was Escape in lower case but basically that just worked.)
Now I'm on a chromebook with the Meta key in place of CapsLock and I can't find its identifier. I tried <META> and <MOD4> with no success. I don't think it's something chromebook specific as other applications correctly recognize the Meta key.
Thanks for your help!
Last edited by ysetdng (2014-07-03 12:45:50)

OK got it! The key identifier is <LWIN> and the function (to which I want to map <ESC>) is Meta_L.
Last edited by ysetdng (2014-07-03 11:13:00)

ME51N - Screen layout

Hi All
On the delivery address tab on ME51N or ME52N/53N screen we are unable to see the "Region" Field . Is there some config settings which I need to do inorder to see this field.
I can use the "address details" button to see that but we need the "Region" field to be on the delivery address tab.
Any help is highly appreciated
Thanks
Vijay

Region feild is displayed for USA, Canada, Italy, Brazil or Australia, and Great Britain. However if you wanna get it you need to program into ADDRESS_INTO_PRINTFORM function module.
"Address Layout Key" for the recipient country controls the routines. These routines are programmed into the function module mentioned above.

Not allowing totaling of a field in alv output

hi,
I had made a ALV in which i have to hide 1 field for getting it totaling.
i.e. if somebody try to make total of it ,it should not be allowed on dat field . is dere any solution for this problem?
plzz provide me guidelines for it.

Please please it this. I made the total for every field other than RACCT and SUM_COMM.
*&      Form sub_prepare_display_output
      Display output
--> No Parameter
FORM sub_prepare_display_output .
Local variables
DATA: l_lead_col   TYPE char25,       " Lead column
        l_progname   TYPE sy-repid,     " Program name
Local internal tables
        l_oref_layout TYPE REF TO cl_salv_layout, "Layout
Local work area
        l_wa_key      TYPE salv_s_layout_key,     "Work area for key
        l_except1   TYPE REF TO cx_salv_msg,"Exception
        l_text1     TYPE string.            "Exception msg
If profit center is checked
IF p_prfctr = c_check.
    l_lead_col = 'Profit Center'(041).
If product catagory is checked
ELSEIF p_prodc = c_check.
    l_lead_col = 'Product Category'(042).
If material is checked
ELSEIF p_smatnr = c_check.
    l_lead_col = 'Material No.'(043).
ENDIF.
Create ALV instance with class-method cl_salv_table=>factory
TRY.
      CALL METHOD cl_salv_table=>factory
        EXPORTING
          list_display = if_salv_c_bool_sap=>false
        IMPORTING
          r_salv_table = v_oref_table
        CHANGING
          t_table      = i_final.
    CATCH cx_salv_msg INTO l_except1.
      l_text1 = l_except1->get_text( ).
      MESSAGE i000 WITH l_text1.
      LEAVE LIST-PROCESSING.
ENDTRY.
Make header of the report
PERFORM sub_header_report USING v_oref_table.
Get the toolbar
v_oref_functions = v_oref_table->get_functions( ).
For activating application toolbar
v_oref_functions->set_all( abap_true ).
v_oref_columns = v_oref_table->get_columns( ).
It populate the key fields which are always displayed
PERFORM sub_fill_fields_of_fcatalog USING:
'SUM_COMM'        l_lead_col                ' ',
'RACCT'          'Account Number'(035)      ' ',
'FOBAC'          'FOB Acrual'(023)          'X',
'EXCESS'         'Excess'(024)              'X',
'OBSOLE'         'Obsolescence'(025)        'X',
'PPV'            'Puchachse Price Var'(026) 'X',
'FR_VAR'         'Freight Variance'(027)    'X',
'PROD_OR_VAR'    'Produc Ord Var'(028)      'X',
'DEP_VAR'        'Dept. Variance'(029)      'X',
'OTH_PROD_VAR'   'Other Prod Var'(030)      'X',
'PR_OR_SCRP_VAR' 'Scrap Variance'(031)      'X',
'COST_OF_ACC'    'Cost of Sales Accnt'(032) 'X',
'INV_ACC'        'Inventory Account'(033)   'X'.
Optimize the columns
v_oref_columns->set_optimize( value = 'X' ).
Setting the layout
get the LAYOUT object
l_oref_layout = v_oref_table->get_layout( ).
set the layout key
l_progname = sy-repid.
l_wa_key-report = l_progname.
l_oref_layout->set_key( value = l_wa_key ).
set save restriction:
none / only user-dependent / only user-independent
l_oref_layout->set_save_restriction(
value = if_salv_c_layout=>restrict_none ).
set: setting of default layout is allowed / isnu2019t allowed
l_oref_layout->set_default( value = 'X' ).
Dispaly the output
v_oref_table->display( ).
ENDFORM.                    " sub_prepare_display_output
*&      Form sub_header_report
    Create the header of the report
     -->P_v_oref_TABLE table name
FORM sub_header_report USING    p_v_oref_table TYPE REF TO
                                           cl_salv_table .
DATA : l_oref_grid TYPE REF TO cl_salv_form_layout_grid.
CREATE OBJECT l_oref_grid.
Add text items for top of page
l_oref_grid->create_text( row = 1 column = 1 text = 'Program'(022)
l_oref_grid->create_text( row = 1 column = 2 text = sy-repid ).
l_oref_grid->create_text( row = 2 column = 1
text = 'User Name'(021) ).
l_oref_grid->create_text( row = 2 column = 2 text = sy-uname ).
l_oref_grid->create_text( row = 3 column = 1 text = 'Date'(020) ).
l_oref_grid->create_text( row = 3 column = 2 text = sy-datum ).
l_oref_grid->create_text( row = 3 column = 3 text = 'Time'(019) ).
l_oref_grid->create_text( row = 3 column = 4 text = sy-uzeit ).
l_oref_grid->create_text( row = 4 column = 1 text = 'System'(018) ).
l_oref_grid->create_text( row = 4 column = 2 text = sy-sysid ).
l_oref_grid->create_text( row = 4 column = 3 text = 'Client'(017) ).
l_oref_grid->create_text( row = 4 column = 4 text = sy-mandt ).
Declare grid as header of list
p_v_oref_table->set_top_of_list( value = l_oref_grid ).
ENDFORM.                    " sub_header_report
*&      Form sub_fill_fields_of_fcatalog
      This subroutine populates the field catalog excluding
      period fields
     -->P_FIELDNAME Table field name
     -->P_NAME      Field description
     -->P_DEC       Decimal value flag
FORM sub_fill_fields_of_fcatalog USING p_fieldname TYPE lvc_fname
                                        p_name      TYPE c
                                        p_dec       TYPE c.
DATA: l_char_l TYPE scrtext_l, "For short text
        l_char_m TYPE scrtext_m, "For medium text
        l_char_s TYPE scrtext_s, "For long text
        l_except1   TYPE REF TO cx_salv_not_found,"Exception
        l_text1     TYPE string,            "Exception msg
        l_orf_aggregs TYPE REF TO cl_salv_aggregations.
Getting the text long/short/medium into variables
l_char_l = p_name.
l_char_m = p_name.
l_char_s = p_name.
Setting the long/short/medium text and fix the key fileds
TRY.
      CALL METHOD v_oref_columns->get_column
        EXPORTING
          columnname = p_fieldname
        RECEIVING
          value      = v_oref_column1.
    CATCH cx_salv_not_found INTO l_except1.
      l_text1 = l_except1->get_text( ).
      MESSAGE i000 WITH l_text1.
      LEAVE LIST-PROCESSING.
ENDTRY.
v_oref_column ?= v_oref_column1.
v_oref_column->set_long_text( l_char_l ).
v_oref_column->set_medium_text( l_char_m ).
v_oref_column->set_short_text( l_char_s ).
v_oref_column->set_key( value = 'X' ).
v_oref_columns->set_key_fixation( value = 'X' ).
Set the decimal length
IF p_dec = 'X'.
    v_oref_column->set_decimals( value = '2' ).
ENDIF.
IF p_fieldname = 'RACCT' AND p_gl <> c_check.
    v_oref_column->set_visible( value = space ).
ENDIF.
IF p_gl = c_check.
    v_oref_columns->set_column_position( columnname = 'RACCT'
                                           position = 2 ).
ENDIF.
IF p_fieldname NE 'RACCT' AND p_fieldname NE 'SUM_COMM'.
    l_orf_aggregs = v_oref_table->get_aggregations( ).
    l_orf_aggregs->add_aggregation( columnname = p_fieldname
                   aggregation = if_salv_c_aggregation=>total ).
ENDIF.
ENDFORM.                    " sub_fill_fields_of_fcatalog

How to check valuation type and batch during creating PO

Hi All,
can every body help me please,
I have a material which manage by batch and valuation type.
When user create purchase order using that kind of material I want the system checking field batch and valuation type. If they not match then system will give an error message.
What should I do to make the system checking that fields?
Thxs
- ely -

Hi Ely
Fortunately, you do not need to do any coding or need to use exits.
You can configure the screen layout settings as follows:
1) SPRO->MM->Purchasing->Purchase Order-> Define screen layout at doc level
2) Double click on the key-NBF (most probably you are using this for your PO document type. If you are using any other field layout key..make changes there)
3) Double click on GR/IR control .
4) Make Valuation Type & Batch fields 'Required'.
System works intelligently here. If the material is batch managed, system expects you to enter a batch in PO. If the material has split valuation, then system also expects you to enter valuation type. FOr other materials, system does not expect you to enter batch or valuation type.
Best regards
Ramki

Total and Subtotal for set_table_for_first_display

Hello,
I am displaying data in ALV by using set_table_for_first_display , i want to do_sum for
10-15 columns starting from the column index 11.. and i have also passed the value in internal table of type LVC_T_SORT and in the fieldcatlog this fields are checked for DO_SUM but sum is not coming in the final output even summation button is disabled and subtotal is also getting reflected.
Is it i need to do extra to do this when i am displaying data by using the OOPS methos?
Please sugggest what could be the reason..
Thanks
Prince

Hi,
Try the below code.
TABLES: mara.
SELECT-OPTIONS: s_matnr FOR mara-matnr.
types: begin of ty_marc,
         matnr type marc-matnr,
         werks type marc-werks,
         count type i,
       end of ty_marc.
data: it_marc type standard table of ty_marc with header line.
START-OF-SELECTION.
SELECT matnr werks FROM marc INTO TABLE it_marc WHERE matnr IN s_matnr and werks in ('0888', '0811').
loop at it_marc.
    it_marc-count = 1.
    modify it_marc transporting count.
endloop.
"* Definition for Object Oriented ALV
DATA: gr_table      TYPE REF TO cl_salv_table.
DATA: gr_sorts      TYPE REF TO cl_salv_sorts.
DATA: gr_agg        TYPE REF TO cl_salv_aggregations.
DATA: gr_agg2       TYPE REF TO cl_salv_aggregation.
DATA: gr_display    TYPE REF TO cl_salv_display_settings.
DATA: gr_layout     TYPE REF TO cl_salv_layout.
DATA: ls_key        TYPE salv_s_layout_key.
"* Display ALV as a Grid
TRY.
      cl_salv_table=>factory( IMPORTING r_salv_table = gr_table
                              CHANGING t_table      = it_marc[] ).
    CATCH cx_salv_msg.
ENDTRY.
    TRY.
        gr_agg = gr_table->get_aggregations( ).
        CALL METHOD gr_agg->add_aggregation
          EXPORTING
            columnname = 'COUNT'
            aggregation = if_salv_c_aggregation=>total
          RECEIVING
            value       = gr_agg2.
      CATCH cx_salv_data_error .
      CATCH cx_salv_not_found .
      CATCH cx_salv_existing .
    ENDTRY.
"* Set up Sorts
    TRY.
        gr_sorts = gr_table->get_sorts( ).
        CALL METHOD gr_sorts->add_sort
          EXPORTING
            columnname = 'MATNR'
            position   = 1
            sequence   = if_salv_c_sort=>sort_up
            subtotal   = if_salv_c_bool_sap=>true
            group      = if_salv_c_sort=>group_none
            obligatory = if_salv_c_bool_sap=>false.
      CATCH cx_salv_data_error .
      CATCH cx_salv_not_found .
      CATCH cx_salv_existing .
    ENDTRY.
"* Add layout variants in report
    TRY.
      gr_layout = gr_table->get_layout( ).
"*... set the Layout Key
      ls_key-report = sy-repid.
      gr_layout->set_key( ls_key ).
"*... set usage of default Layouts
      gr_layout->set_default( abap_true ).
"*... set Layout save restriction
      gr_layout->set_save_restriction( if_salv_c_layout=>restrict_none ).
    ENDTRY.
    TRY.
"* Display ALV
      gr_table->display( ).
    ENDTRY.
Hope it helps.
Thanks,
Balaji

Layout key SAPSFCAS27

Similar Messages

Maybe you are looking for