FUNCTION EXIT_SAPFP50M_001 - Infotypes with dec fields

Following an upgrade to 4.7 we have a problem with the above function exit in HR. (Function Group XPAD)
Using the SAP example code 'MOVE INNNN to I0008' given in include LXPADF01 produces the following message on activation when we try to use it for infotype 386:
"<b>I0386" and "INNNN" are not mutually convertible. In Unicode programs,
"I0386" must have the same structure layout as "INNNN", independent of
the length of a Unicode character</b>.
All worked Ok in 4.5B and we think it is caused by the fact that the Infotype contains non-character fields causing a conversion problem. Does anyone have an easy solution to this problem?

Don't worry I found the answer myself!!
Using objects/methods
CALL METHOD CL_HR_PNNNN_TYPE_CAST=>PRELP_TO_PNNNN
        EXPORTING
          PRELP = INNNN
        IMPORTING
          PNNNN = I0386.
etc to do the conversion.

Similar Messages

Create infotype with PM01+ field lenght in table

hello my HR friends, a friend of mine create an infotype with tcode PM01 so far everthing is ok but when she finished, i found an error and neither i or she knows how to solve it.
Picture of infotype: http://img197.imageshack.us/img197/8236/infotype1.jpg
and problem is, in field that have the rectangle, this field have this possible values:
http://img529.imageshack.us/img529/1887/infotype2.jpg
the problem is if a choose the first possible value, field stays like this:
http://img836.imageshack.us/img836/4494/infotype3.jpg and then when im going to save the system says that content doesn't exist in the table that is feeding that textbox.
Do anyone knows how to solve this problem or the solution is to put that possible values shorter or put text box bigger.
regards and thanks in advance for the help.
Mário

Instead of INT use DEC or NUMC data types.
To know why INT cannot be used try searching with Hardware Restriction in terms of general computing.

Create InfoType with decimal field

Hi,
I would like to create an InfoType with some numeric, char and currency type in the structure
Then I run PM01, create the structure
http://img119.imageshack.us/my.php?image=ps9080ze4.jpg
activate it and go back to PM01 but when I click on GENERATE button, il get the following message :
msg type error : The infotype must not include an integer type or floating point no.field
I dont realy understand why this error occurs and why an IT couldn't have integer type in his structure...
Any idea ?
Thanks,
Ant.

Instead of INT use DEC or NUMC data types.
To know why INT cannot be used try searching with Hardware Restriction in terms of general computing.

Creation of HR infotype with repeated fields

Hi,
We have a requirement in our project where in we need to implement the repeat field screen structure.
We have to create an info type with 96 fields in which some of the fields are repeated more than once.
We have tried to create a table control to represent the repeated fields, for this we have a standard way which SAP follows. We have done the same way but we are not able to get the table control in the info type screen.
We have done the following steps using this link
http://help.sap.com/saphelp_erp2005vp/helpdata/en/4f/d52552575e11d189270000e8322f96/frameset.htm
1) I have created a structure with the repeated fields of the info type
2) created the entries in Mapping for Conversion of Repeat Structure/Tables (table T588AUTO_MAP) with the repeated fields
3) For each type LINE screen structure to be used, a corresponding entry was defined in Mapping for Conversion of Repeat Structure/Tables (table T588AUTO_TABLE).
4) I have created an info type with all these fields where in I should get the repeated fields in the table control format, but this was not happening.
Is there any task to be done to link all these transactions before going for creation of the info type?
Can any one suggest me how to get the table format on the screen with all these repeated fields.
with regards,
ramu mullapudi

Hi Choudhury,
Thanks for your reply. The infotype that you suggested solved my problem.
Regards,
RSS.

Creation of infotype with lengthy fields?

Hello All,
I am trying to create a custom infotype which has fields of length 200 characters.
But when I try to create infotype I am getting the following message:
'Field PXXXX-field1 is too long(it has been shortened to 132 bytes)'
And one of the fields I want to display as list box. So I modified the module pool. But I couldn't find the input field for the 200 length field in the screen. And hence I am not able to activate the screen after modifying the other field to list box.
Please help me out in solving this issue.
Thanks in advacne.
RSS.

Steps to create a HR Infotype:
1) Go to Transaction PM01.
2) Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
3) Select the 'Employee Infotype' radio button.
4) Select the 'PS Structure Infotype'.
5) Click on Create... A separate table maintenance window appears...
6) Create a PS structure with all the fields you want on the Infotype
7) Save and Activate the PS structure
8) Go back to the initial screen of PM01.
9) Click on 'All' push button. It takes a few moments.
10) Click on 'Technical Characteristics'. Infotype list screen appears
11) Click on 'Change'(pencil) button
12) Select your Infotype and click on 'Detail' (magnifying glass) button
13) Give 'T591A' as subtype table
14) Give 'T591S' as subtype txt tab
15) Give your subtype field as subtype field
16) Save and come back to PM01 initial screen
17) Click on 'Infotype Characteristics' ... Infotype list screen appears
18) Click on 'Change' (pencil) button
19) Click on 'New Entries'
20) Enter your Infotype number and short text
21) Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotype's infotype characteristics screen and use as the reference to fill yours)
22) Save your entries.
23) Now the Infotype is created and ready to use.
24) If you want to change the layout of the Infotype as per your requirement...
25) In the PM01 initial screen...Select 'Screen' radio button and give 2000 as the screen name, then click on edit.
26) In the next screen.. Select 'Layout Editor' and click 'Change'.
27) Screen default layout appears...here you can design/modify the screen..change the attributes of the fields..etc.
28) Save and activate. (Don't forget to 'Activate at every level)
Subtype Creation :
Transaction PM01 Goto Subtype Characteristics. Click on Append and then subtype. Enter the name and description of subtype on screen.
Then goto technical Characteristics and maintain the details of subtype there. I.e name of subtype i.e. component name defined in PSnnnn. Subtype table is T591A.
Subty.text tab is T591S and time const tab is T591A.
See:
http://help.sap.com/saphelp_46c/helpdata/en/4f/d5268a575e11d189270000e8322f96/content.htm
HR related site:
http://www.sapdevelopment.co.uk/hr/hrhome.htm
Enhancement of Infotype
Check the following
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAXX/PYINT_INFOTYP.pdf
Infotype Enhancement overview screen
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60a7586d-edd9-2910-68a8-8204303835a1
Reward points if uesful.

Field catalog does not agree with the fields of the functional area

G'day everyone,
I am using a generic extractor via infoset to extract data from R/3 source system.
Using RSA3, I have obtained an error message and no further details.
****ERROR MESSAGE
"Field catalog does not agree with the fields of the functional area
Message no. RSUQ134
****ERROR MESSAGE
I have checked and adjusted my infoset in SQ02 and they seems fine but still obtain the same error.
In BW, replicated the datasource and activate the transfer rules but still obtain the same error.
Anyone knows how to get more details for this type of error? Or how to fix this problem?
Regards
Wayne

I think I have just solved it.
Transaction RS02 delete and recreate after checking the structure in BW and Source system are the same.
Cheers

Rfc functions with export field type exid h

Hi, in WAS700 I encountered rfc functions with export fields of the type exid h
I found in the rfccal.c the following section:
        if (*exid == 'h') continue;
               I don't know how handle type 'h' (internal table)
               with RFC API. Therefore ignore it.
Example function : SWNC_GET_WORKLOAD_STATISTIC
In the rfcsdk docs I can't find a thing how you should handle such an export field.
Any solution for this ?

hi hans,
sorry i shouldn't have answered your question. to me RFC is tooo strange. I had a quick look at the FM, searched DDIC for something like exid and had a look at the WSDL of the webservice WSDL of that FM. nothing seemed very complicated to me in terms of a webservice call to it (apart from the semantically...uhm...questionable interface; MEM_OBJS_FR_YOUN anybody?) but I really have no idea of the inner workings of RFC.
sorry again. hope you get it solved here.
anton

Dynamic actions - how to create an infotype with a date - 1 day.

Hi everyone,
I need a requirement to change an infotype through dynamic action with ENDDA = BEGDA of maintaned infotype(0000) - 1 day.
In other words when a personel action is performed, another infotype (2001) should appear for change, and in the validity period of this infotype should end with the day before the start of the personel action.
is it possible to achieive this using dynamic actions? how?
Thanks!
Stanislaw Adamski

Hi Adamski,
A dynamic action has the following components.
Infotype Number (INFTY): specifies the infotype for which you want the dynamic action triggered
Subtype (SUBTY): narrows the focus to a specific subtype
Field Name (FIELDN): starts your action when a maintenance function is performed on a particular field
Function (FC): specifies the various maintenance operations to which your dynamic action would respond. They are 02 (change); 04 (create); 06 (create and change); 08 (delete); 10 (change and delete); 12 (create and delete). Dynamic actions are only applicable in maintenance operations, not in display functions.
Sequence Number (NO): refers to a sequential number.
Step (A): specifies a particular type of action. No dynamic action is executed if the function character has a value other than one of the following:
             P: Plausibility checks, which allow you to check certain conditions.
             I: Calls an infotype for processing
             W: Called after the I statement and used to assign values to screen fields while creating or copying another infotype record through the I statement
              F: Calls a FORM routine (subroutines in ABAP) during your action. The routine may reside in or out the module pool MPNNNN00.
             V: Lets you treat collectively a number of fields for which you want to define a common dynamic action
              M: Sends SAP Office mail
Variable function part: The variable function part along with the step indicator forms the core part of your action. It specifies the processing details when the dynamic action is triggered. For example:
you have to look for the scenario what you are planning tyo create .
The maintenance of dynamic actions is done via the view V_T588Z, as shown in 1 (IMG menu path Personnel Management>Global Settings in Personnel Management>Basic Settings>Infotypes>Create Dynamic Actions
Here you havev to use conditions INS for the infotype what you want to create..
Please brief the light on the scenario.
Warm Regards,
Kapil Kaushal

Custom infotype with subtypes

Hi Experts,
I have a requirement to create a custom infotype with subtypes. I have maintained all the fields + 'zzsubty' field (to store subtype no. - of type subty) in PSnnnn and also maintained infotype characteristics and Technical attributes (all the standard steps). But, I want only some of the fields to be displayed depending on the subtype entered. By using the current method, I see all the fields I created in the structure irrespective of the subtype. So, is there anything else that I need to work on to make sure that only the fields I want to be displayed will be visible depending on the subtype? If I need to work on the module pool, could you please be descriptive as I am new to it.
Thanks
Sri

Hello,
Try using the user -exit EXIT_SAPFP50M_001 for ur requirement.
Cheers,
Manoj.

Functions in Calculation and Summary Fields

Hi,
I'll give a bit of background to my situation before describing the advice I'm looking for here.
I am experienced Mac user and I have used AW a fair bit in the past, but since I've been working in a job which has Windows machines and uses a complex custom-written relational database for its main tool, I use it less often than I did, so I am a little rusty. It is the shortcomings of the complex relational database (which I do not have admin rights to) that has led me back to AW and its database module.
Essentially, I am a complaints investigator, and the relational database provided by my employer is used to keep track of correspondence and various metadata associated with the investigation of the complaint. However, although it is called a Complaints Management System (CMS), it does not help me manage my caseload very well. I've previously tried to create an Excel spreadsheet that would help me manage my work, but it is not a database (or I am not sufficiently skilled with Excel) and I cannot get it to provide me with what I want.
So, my problems.
I have complaints (cases) assigned to me to investigate. These cases have differing priorities, which means differing time limits for completion of the investigation. The priorities and time limits are set out below:
J (jurisdictional issues) - time limit = 1 month
D (discretion not to investigate) - time limit = 3 months
1 - time limit = 4 months
2 - time limit = 6 months
3 - time limit = 12 months
The priority field in my AW DB is currently a 'pop-up menu' field, but I could change this to another type if this would be advisable.
I have a date-type field in which I enter the date the complaint was received. I have an calculation-type field in which I calculate the age of the complaint using the function:
=(NOW()-'DateReceived')
This returns an age in days, which I input into a separate calculation field that divides the result of 'age in days' by 30, to give a rough approximation of the number of months old the complaint is (If AW has an equivalent to Excel's 'workdays' variable, I'd love to hear about it). This latter field is the one that I display in the main data entry view of the database.
Given the priority assigned to the complaint, and the age of it, I am either 'On Target' or 'Over Target' for completing the investigation.
Each month I have a meeting with my manager to review progress, and since the reports that can be extracted from the CMS are not very useful for this purpose, I want my AW database to help me generate reports that can form the basis of discussion in these meetings.
Part A of My Query
At present, I have a manually operated field, in the form of a pop-up menu, to indicate for each record (complaint) whether I am over or on target for completion of the investigation. I would like to make this a calculated field, so that the database keeps track of this for me automatically. Unfortunately, I'm either too dense, or not good enough with the syntax of AW functions, to be able to write a function which essentially does the following:
IF 'Priority'=1 AND 'Age in Months'<4 THEN 'On Target' ELSE 'Over Target'
- and then repeats that for the other priority possibilities. It seems likely that the 'IF' function is what I'm after, but I haven't been able to get the syntax right to combine 'Priority' and 'Age in Months' in the format spelt out in the AW help, which is:
=IF(logical,true value,false value)
Getting the syntax of one part of this function right would be a good start. However, I suspect that I have a larger problem, in that I have 5 priorities to measure against and I need the overall calculation (that produces the 'On Target' or 'Over Target' results) to report in one result field. This means nesting the functions that look at the 5 priorities and 5 age limits. I've tried and failed to get the syntax of such nesting right, so advice on this is doubly welcome.
Unfortunately, I have a sneaking suspicion that unless the answer is much more concise than I imagine it to be, there will be an additional problem: AW appears to have a character limit for the length of a function string in a calculation field which may be too short for my needs. If you think this is an issue but that it can be solved through the use of intermediate fields (which don't need to be displayed in the main 'data entry' layout), I'm happy to give that a shot.
Part B of my Query
Even if the problem above cannot be solved, and I have to manually enter whether a complaint is 'On Target' or 'Over Target', I have a separate but related question for the reports I have to present to my manager.
On these reports, I would like to have a summary at the top of the first page (in a grand-summary part, I assume) which gives a count of how many complaints are 'On Target' or 'Over Target' for each priority. Below that is a sub-summary part, ordered by the type of action that must next be taken in the investigation. (Getting that right may be a subject of a separate post at a later date.) The report must, of course, only report on those complaints that are still being investigated ('open complaints') and not those which have been completed ('closed complaints'). So, I need a function in a summary field which will present an accurate count of the number of open complaints that are 'on target' for priority J (with separate summary fields that do the same thing for priorities D, 1, 2, and 3), and a separate set of summary fields that will present a count of open complaints that are 'over target' for each type of priority.
It might look a bit like this table below, with figures from the summary fields populating the cells in the third row:
Priority
J
D
1
2
3
In / Out of Target
In
Out
In
Out
In
Out
In
Out
In
Out
Number of Complaints
My guess is that it is easier to have the summary field simply count all the complaints that are on or over target for a given priority, regardless of whether they are open or closed, since the report could be based on a saved search (match) which strips out all closed complaints. But if I'm off-beam with that idea, I'm happy to have another way of cracking this nut.
Many thanks in advance to any Community members that take the time to try and help me with this.
Andrew
PS Cross posted in AWUG forum too, if people prefer to answer there.

Hi Andrew,
Part A:
I've done some restating of the question, and distributed the calculations among several fields, not all of which need to be included on the visible layout. Other than formatting the Date fields and moving the 'Completed Date' field and its label, I've left this in the default "Layout 1" produced by AppleWorks.
Field List:
Priority: Popup menu with six items: 00, J, D, 1, 2, 3 Defaults to 00
TL (time limit in months): Calculation: CHOOSE('Priority',0,1,3,4,6,12)
Received: Date. Option: Automatically insert today's date (ie. Date Record created) (may be edited)
Target Date: Calculation:
DATE(YEAR('Received')+INT(MONTH('Received')+'TL')/12,MOD(MONTH('Received')+'TL', 12),DAY('Received'))
Remaining (Days): Calculation: INT('Target Date'+1-NOW()) (see revision below)
Completed: Checkbox. Set default value to Unchecked.
Completed Date: Date: Entered manually
OnTarget: Calculation: IF('Completed',IF('Completed Date'<'Target Date',"On Target","Over"),IF(INT(NOW())>'Target Date',"Over","On Target"))
The On Target field shows the current status of the case while still open, and the state on the closing date when it was closed.
Having done that, I was unhappy with the Remaining field continuing to calculate an ever larger negative number after the case had been closed. Hence this revision below:
Remaining: Calculation: IF('Completed','Target Date'-'Completed Date',INT('Target Date'+1-NOW()))
Shows the number of days remaining while the case is open, the days remaining at completion if the case has been marked Completed and the completion date entered.
Rsults (and some further formatting of the Layout) below.
Part B:
You will need Subsummary parts when sorted on Completed and on On Target. Fields can appear on a Layout only once, so each subsummary part will need a separate Summary type field for each field to be summarized.
Regards,
Barry

What is the Function MOdule that returns the fields in database table order

Hello Folks
I have a dynamic internal table with fields ( which are not in order). I want to display them in the order of which they are present in the database table? Is there any function module that returns the fields in database order?
FAQ. Please search before posting your question.
Edited by: Suhas Saha on Oct 10, 2011 10:19 PM

Hi,
You can use this BAPI.
<b>BAPI_SALESORDER_GETLIST</b>
Reward if useful.
Regards,
Vimal

To capture the selected rows along with edited field contents in alv report

Dear All,
         I do have requirement where, in alv report output one field is editable and need to save the content of the edited field along with the selected rows.
         For example If there are 10 records displayed in the alv output with 20 fields.
Out of this 20 fields one field (say XYZ) is editable. Also i have already created a new pushbutton (say ABC) on alv output. Now in the alv output if we maintain some value in the field (XYZ ) for the 2nd and 4th record and select this two records, and when clicked on the pushbutton (ABC) it has to update the DB table.
      I am using the Func Module 'REUSE_ALV_GRID_DISPLAY'.
      Your early reply with sample code would be appreciated.
Thanks in Advance.

HI Naveen ,
There is an import parameter "i_callback_program" in the function module,
plz pass the program name to it.
Capture the command by passing a field of type sy-ucomm to "I_CALLBACK_USER_COMMAND ". Check the returned command and
and program a functionality as desired.
u can try the event double_click or at line selection. there u can use READLINE command to c if the line has been selected.
In case it is , process the code segment.
Regards
Pankaj

Create a Procedural ALV Report with editable fields and save the changes

Hi,
I am new to ABAP. I have created a Procedural ALV Report with 3 fields. I want to make 2 fields editable. When executed, if the fields are modified, I want to save the changes. All this I want to do without using OO concepts. Please help . Also, I checked out the forum and also the examples
BCALV_TEST_GRID_EDIT_01
BCALV_TEST_GRID_EDIT_02
BCALV_TEST_GRID_EDIT_04_FORMS
BCALV_TEST_GRID_EDITABLE
BCALV_EDIT_01
BCALV_EDIT_02
BCALV_EDIT_03
BCALV_EDIT_04
BCALV_EDIT_05
BCALV_EDIT_06
BCALV_EDIT_07
BCALV_EDIT_08
BCALV_FULLSCREEN_GRID_EDIT
But all these are using OO Concepts.
Please help.
Regards,
Smruthi

TABLES:     ekko.
TYPE-POOLS: slis.                                 "ALV Declarations
*Data Declaration
TYPES: BEGIN OF t_ekko,
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
statu TYPE ekpo-statu,
aedat TYPE ekpo-aedat,
matnr TYPE ekpo-matnr,
menge TYPE ekpo-menge,
meins TYPE ekpo-meins,
netpr TYPE ekpo-netpr,
peinh TYPE ekpo-peinh,
line_color(4) TYPE c,     "Used to store row color attributes
END OF t_ekko.
DATA: it_ekko TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_ekko TYPE t_ekko.
*ALV data declarations
DATA: fieldcatalog TYPE slis_t_fieldcat_alv WITH HEADER LINE,
      gd_tab_group TYPE slis_t_sp_group_alv,
      gd_layout    TYPE slis_layout_alv,
      gd_repid     LIKE sy-repid.
START-OF-SELECTION.
PERFORM data_retrieval.
PERFORM build_fieldcatalog.
PERFORM build_layout.
PERFORM display_alv_report.
*&      Form BUILD_FIELDCATALOG
      Build Fieldcatalog for ALV Report
FORM build_fieldcatalog.
fieldcatalog-fieldname   = 'EBELN'.
fieldcatalog-seltext_m   = 'Purchase Order'.
fieldcatalog-col_pos     = 0.
fieldcatalog-outputlen   = 10.
fieldcatalog-emphasize   = 'X'.
fieldcatalog-key         = 'X'.
fieldcatalog-do_sum      = 'X'.
fieldcatalog-no_zero     = 'X'.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'EBELP'.
fieldcatalog-seltext_m   = 'PO Item'.
fieldcatalog-col_pos     = 1.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'STATU'.
fieldcatalog-seltext_m   = 'Status'.
fieldcatalog-col_pos     = 2.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'AEDAT'.
fieldcatalog-seltext_m   = 'Item change date'.
fieldcatalog-col_pos     = 3.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'MATNR'.
fieldcatalog-seltext_m   = 'Material Number'.
fieldcatalog-col_pos     = 4.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'MENGE'.
fieldcatalog-seltext_m   = 'PO quantity'.
fieldcatalog-edit             = 'X'
fieldcatalog-col_pos     = 5.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'MEINS'.
fieldcatalog-seltext_m   = 'Order Unit'.
fieldcatalog-col_pos     = 6.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'NETPR'.
fieldcatalog-seltext_m   = 'Net Price'.
fieldcatalog-col_pos     = 7.
fieldcatalog-outputlen   = 15.
fieldcatalog-datatype     = 'CURR'.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname   = 'PEINH'.
fieldcatalog-seltext_m   = 'Price Unit'.
fieldcatalog-col_pos     = 8.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
ENDFORM.                    " BUILD_FIELDCATALOG
*&      Form BUILD_LAYOUT
      Build layout for ALV grid report
FORM build_layout.
gd_layout-no_input          = 'X'.
gd_layout-colwidth_optimize = 'X'.
gd_layout-totals_text       = 'Totals'(201).
gd_layout-info_fieldname =      'LINE_COLOR'.
ENDFORM.                    " BUILD_LAYOUT
*&      Form DISPLAY_ALV_REPORT
      Display report using ALV grid
FORM display_alv_report.
gd_repid = sy-repid.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            i_callback_program      = gd_repid
            i_callback_pf_status_set = 'STATUS'
            i_callback_top_of_page   = 'TOP-OF-PAGE'
           i_callback_user_command = 'USER_COMMAND'
           i_grid_title           = outtext
            is_layout               = gd_layout
            it_fieldcat             = fieldcatalog[]
           it_special_groups       = gd_tabgroup
           IT_EVENTS                = GT_XEVENTS
            i_save                  = 'X'
           is_variant              = z_template
       TABLES
            t_outtab                = it_ekko
       EXCEPTIONS
            program_error           = 1
            OTHERS                  = 2.
ENDFORM.                    " DISPLAY_ALV_REPORT
*&      Form DATA_RETRIEVAL
      Retrieve data form EKPO table and populate itab it_ekko
FORM data_retrieval.
DATA: ld_color(1) TYPE c.
SELECT ebeln ebelp statu aedat matnr menge meins netpr peinh
   UP TO 10 ROWS
    FROM ekpo
    INTO TABLE it_ekko.
LOOP AT it_ekko INTO wa_ekko.
    ld_color = ld_color + 1.
    IF ld_color = 8.
      ld_color = 1.
    ENDIF.
    CONCATENATE 'C' ld_color '10' INTO wa_ekko-line_color.
    MODIFY it_ekko FROM wa_ekko.
ENDLOOP.
ENDFORM.                    " DATA_RETRIEVAL
      FORM top-of-page                                              *
FORM top-of-page.
WRITE:/ 'This is First Line of the Page'.
ENDFORM.
      FORM status                                                   *
FORM status USING rt_extab TYPE slis_t_extab. .
SET PF-STATUS 'ALV'.
ENDFORM.
      FORM USER_COMMAND                                          *
--> RF_UCOMM                                                      *
--> RS                                                            *
FORM user_command USING rf_ucomm LIKE sy-ucomm
                         rs TYPE slis_selfield.
DATA ref1 TYPE REF TO cl_gui_alv_grid.
CALL FUNCTION 'GET_GLOBALS_FROM_SLVC_FULLSCR'
    IMPORTING
      e_grid = ref1.
CALL METHOD ref1->check_changed_data.
CASE rf_ucomm.
when 'SAVE'.
get all the modified entries and store them in an internal table and udpate them in to the required transaction or your custom table.
endcase.
endform.
ENDFORM.
here u need to 2 performs for PF status and USER_COMMAND in the ALV parameters.
create a custom PF status and create push buttons and assign your ok codes in your PF status.
if the field has to be edited in the ALV then pass EDIT = 'X' for that field in the fieldcatlog preparation.
Hope this will help you.
Regards,
phani.

Maintenance View with Subset Fields

Hi All,
I have created a maintenance view based on a single DB table. Two key fields are defined to be as subset fields. No selection conditions are added to the view. I have used table maintenance genrator to define the screen (one step) along with the events.
In SM30, i get the popup to fill the subset fields.
I have created an event for AA (to replace default read). I am filling total attribute here.
a) Is there some other attribute that i need to fill apart from total?
I receive following dump
" Exception condition "NO_VALUE_FOR_SUBSET_IDENT" is raised"
When i set <status>-sbsid_rcvd = 'R' in read routine along with total, then the above exception doesn't appear.
But filtering based on the subset values doesn't happen automatically.
b) I also need have to have routines to perform insert, copy and validation.
c) Would the contents displayed be automatically filtered based on the subset values or we need to process this in user routines for read and so on?
As i find very limited documentation available for maintenance views with subset fields, could you suggest me some example to do the above?
Thanks in Advance,
Regards,
Rekha

Hello Rekha,
Yes I've same idea, documentation for maintenance screens is inadequate.
But there is way to find examples for all events,
table TVIMF is storing the Table name - Event - Form name columns.
For example when u want to do something about "creating a new entry"
Just go se11 > Table maintenance generator and find related event : 05
- Then go to TVIMF and display a record for event = 05
- than go to function group of maintenance screen of the TABLE in that record
- find the subroutine form ( TVIMF-FORMNAME) in that function group
This is a working example for that event, try or copy & use.
I hope it helps you for the coding for all the events.
Bulent
Edited by: Bulent Balci on Aug 5, 2010 11:28 PM
Edited by: Bulent Balci on Aug 5, 2010 11:29 PM

Arrow mark with kunnr field values in alv output.

Hi ,
I need to increase the column field length. I am using Function Module REUSE_ALV_LIST_DISPLAY because alv_grid display fm is not available in 4.0b version. I have used column optimization in layout. The column kunnr is coming with a small arrow though there is no data loss. Is there any way I can remove the arrow mark with kunnr field values.

Hi,
You can increase your column lenght in fieldcat by using Fcat-columnwidth = "SIZE OF KUNNR ".
Set the size of kunnr field in fieldcat and get the appropiate output.
Regards
Abdul

FUNCTION EXIT_SAPFP50M_001 - Infotypes with dec fields

Similar Messages

Maybe you are looking for