Search Help for Order Number

I wonder if anybody out there can help me.
I need to add a new tab to the search help for VBAK-VBELN (Sales Order Number).
The Search help name is called VMVA.
How do I go about doing this?

Hi Stephan,
Its a collective search help. Fo to the included search help ASH_VMVA. Double click it you will find a follwoing included search helps in this
VMVAA
VMVAB
VMVAC
VMVAD
VMVAE
VMVAF
VMVAH
VMVAI
VMVAM
VMVAN
You have to insert a new search help (ZVMVAZ) here to create a new tab.
Create a new selection method using the tables you want the data from. Enter the input and output parameters.
Hope this helps.
Reply if you need more information
Reward if helpful ****

Similar Messages

Search help for material number in table control

Hi
I have a table which i have generated using table control wizard.
I have used an interal table while creating the table control through wizard.
In this internal table i have field matnr.Now my requirement is to have a search help for this field.
I want a default search help for material as you get one instandard transactions.
In my other i have ip/op field i.e matnr and i have used the field directly from ztable,it has got the search help but since i am using the internal table i am notting getting a search help .
can anyone tell how to assign a search help to my table control material field

hi deepthi,
chk a sample one which will help u. f4 hlp in table control
* Screen flow logic........
PROCESS BEFORE OUTPUT.
*MODULE PBO_MODULE.
PROCESS AFTER INPUT.
*MODULE PAI_MODULE.
PROCESS ON VALUE-REQUEST. "F4
FIELD EKPO-EBELP MODULE help_ekpo.
* populate screen field from within PROCESS ON VALUE-REQUEST(F4) call
*& Module help_responsibility INPUT
* text
MODULE help_ekpo INPUT.
**Transport values to table dynpro/screen table control
DATA: l_stepl LIKE sy-stepl,
 l_indx LIKE sy-stepl.
DATA: dynpfields LIKE dynpread OCCURS 5 WITH HEADER LINE.
* Adjust for scroling within table control
CALL FUNCTION 'DYNP_GET_STEPL'
 IMPORTING
 povstepl = l_stepl
 EXCEPTIONS
 stepl_not_found = 0
 OTHERS = 0.
l_indx = tc_ekpotable-top_line + l_stepl - 1.
 "tc_ekpotable should already have been declared
REFRESH dynpfields.
CLEAR dynpfields.
dynpfields-fieldname = 'EKPO-EBELN'.
dynpfields-fieldvalue = '00010' "wa_ekpo-ebeln.
dynpfields-stepl = l_stepl.
APPEND dynpfields.
dynpfields-fieldname = 'EKPO-EBELP'.
dynpfields-fieldvalue = '00020' "wa_ekpo-ebelp.
dynpfields-stepl = l_stepl.
APPEND dynpfields.
CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = 'SAPLZZ_EKKO' "Program name
 dynumb = '0100' "Screen number
 TABLES
 dynpfields = dynpfields
 EXCEPTIONS
 OTHERS = 0.
ENDMODULE. " help_ekpo INPUT
rgds
Anver
if hlped kindly mark points

Search help for orders not showing favorites because of backend search help

Dear Experts,
We are on an SRM 5 implementation.
As a cost assignment, we want to add an order. We have added authorization object BBP_FUNC to the authorization profile because we need the backend search help, showing all orders. Is there a way that we can change the binoculars to a drop down box? That way, users could assign multiple orders in PPOMA and use as a favorite. Or is there another way to use a favorites selection of orders (from PPOMA) together with the use of backend search help.
Regards,
Tom

Tom
If you've given users access to the search help functionality you will always get the binoculars.
This would still be the case if you have favorites maintained for users.
If you want a drop-down list to appear instead you'll need to maintain all the relevant entries as attributes in the org structure via PPOMA_BBP and then remove the search help Auth Object.
It's a bit of a catch 22 really.
Regards
Keith

Search Help for WebClient

Hi All!
I'm working with CRM2007 over WebClient.
I've enhaced a new Z field in a standard view with the Easy Enhacement Workbench (EEW) and I don't know how to make a Search Help. Can someone help me?
Best regards,
Alejandro.

in CRM2007 you have a default method trying to build the search help for fields of a structure in a generic way (this method is GET_V_S_STRUCT and is inherited by all context nodes)
this method does in order:
- look for a specif search help (method GET_V_fieldname)
- if not found, tries to find Design Layer for the field
- if not found, looks for a value list in domain related to field
so if you field is defined based on a data domain having a list of fixed values (not a check table) then you will get the search help automatically
now if none of these three possibilities is available, then you have to create you own search help^.
This is done by creating the GET_V_fieldname method (you can copy existing method IF_BSP_WD_MODEL_SETTER_GETTER~_GET_V_XYZ so you are sure to have proper signature for your method)
in this method, you put this code:
data: lv_ddlb_threshold      type i value '20', "0: DDLB n: 1-n:, DDLB >n: F4-Popup
        ls_tabname             type ddobjname,
        ls_fieldname           type fieldname,
        lv_op                  type seocmpname,
        lv_component           type name_komp,
        lv_call_search_help    type boolean.
ls_tabname   = me->base_entity_structure.
ls_fieldname = component.
rv_valuehelp_descriptor = cl_crm_uiu_md_valuehelp=>v_getter(
                           is_tabname        = ls_tabname
                           is_fieldname      = ls_fieldname
                           iv_index          = iv_index
                           iv_ddlb_threshold = lv_ddlb_threshold ).
doing this, you will rely on search help as defined on your field (in table definition) and you will display a drop-down list if number of values is less or equal to 20, or a search help if number of values is greater than 20

Search Help for Cost center

Hi All,
I have 2 questions
1) we dont have any default cost center maintained any where in the org-structure (PPOMA_BBP), howeverwhenever I go for shopping I can see a cost center along with GL account, ( I know GL acct is coming from "determine GL account for prod-cat" settings in IMG), but what about cost center where is it coming from ??
2) second, when we do search help for cost center's in shopping application, we are able to see all cost centers from the back end which I guess is good, but we can see even those cost centers which are blocked!!!, why is this happening ??,
Thanks.

Hello,
For First::
In general the CO Area (here: cost center) is derived from R/3 Backend Enterprise
Structure and should be re-determined if another acc. objects is
entered that belongs to a different CO Area. Please also check the
settings in R/3 Backend IMG, path:
->Enterprise Structure ->Assignment ->Controlling
->Assign company code to controlling area
The company code is assigned to the CO Area through the following
assignment:
->Materials Management
->Assign purchasing organization to company code
The CO Area is in general the organizational object in
highest (CO) level. Assignments to other MM/CO objects are located
in lower Enterprise hierarchy level. Hence, the CO Area does not
change if a different CO object of a lower level (here: cost center)
is assigned to a SRM document.
For Second::
The only possibility I see is to set the message to error message in
the customizing in the backend. The message number is KI 170. When you
look at the long text of this message in transaction SE91 in the
backend, you will find the description where to look in the customizing.
When you have set this message to ERROR, then no purchase order will be
created in the backend. Instead the shopping basket gets the status
'ERROR' and the administrator will recieve a work item in his inbox.
Then he can check the backend and either post the purchase orders again
after solving the problem, or he can delete the shopping baskets.
Please check the note for more infos or the documentation.
Setting the message KI 170 to error message will solve your problem.
See note 333136. I would think that if you create
a PO directly in the backend if you do not have the message configured
as and error you will be able to create the PO.
I hope this information helps.
Kind regards,
Gaurav

Search help for SKAT-SAKNR OR SKAT-SAKNR is not working

Hi All,
I have created a Search Help for F4 in a dialog program for SKAT-SAKNR OR SKAT-SAKNR. While i click F4 on that field, it displays blank values.
Here is the module:
module HELP_FOR_SAPGL_ACC input.
CLEAR t_SAPGL.
SELECT SAKNR TXT20
 FROM SKAT
 INTO CORRESPONDING FIELDS OF TABLE t_SAPGL UP TO 1000 ROWS
 WHERE SPRAS = SY-LANGU.
 WHERE L_GL_ACC = v_FIELD_VALUE-FIELDVALUE.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 DDIC_STRUCTURE = ' '
 RETFIELD = 'SAKNR'
 PVALKEY = ' '
 DYNPPROG = PROGNAME
 DYNPNR = DYNNUM
 DYNPROFIELD = 'SKA1-SKANR'
 STEPL = 0
 WINDOW_TITLE =
 VALUE = ' '
 VALUE_ORG = 'S'
 MULTIPLE_CHOICE = ' '
 DISPLAY = ' '
 CALLBACK_PROGRAM = ' '
 CALLBACK_FORM = ' '
 MARK_TAB =
IMPORTING
 USER_RESET =
 TABLES
 VALUE_TAB = t_SAPGL
 FIELD_TAB =
 RETURN_TAB =
 DYNPFLD_MAPPING =
EXCEPTIONS
 PARAMETER_ERROR = 1
 NO_VALUES_FOUND = 2
 OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endmodule.
In the above code I am selecting 1000 rows from SKAT table and in the Search Help Popup it is also displaying 1000 rows but all are blank.
Please help me.
Regards,
Avaneet

Hi check my weblog on search help exit codeing..
https://wiki.sdn.sap.com/wiki/x/du0
\* Prepare for output
CALL FUNCTION 'F4UT_RESULTS_MAP'
TABLES
shlp_tab = shlp_tab
record_tab = record_tab
source_tab = lt_result
CHANGING
shlp = shlp
callcontrol = callcontrol
EXCEPTIONS
illegal_structure = 1
OTHERS = 2.
IF rc = 0.
callcontrol-step = 'DISP'.
ELSE.

Need some help in creating Search Help for standard screen/field

I need some help in adding a search-help to a standard screen-field.
Transaction Code - PP01,
Plan Version - Current Plan (PLVAR = '01'),
Object Type - Position ( OTYPE = 'S'),
Click on Infotype Name - Object ( Infotype 1000) and Create.
I need to add search help to fields Object Abbr (P1000-SHORT) / Object Name (P1000-STEXT).
I want to create one custom table with fields, Position Abb, Position Name, Job. Position Abb should be Primary Key. And when object type is Position (S), I should be able to press F4 for Object Abb/Object Name fields and should return Position Abbr and Position Name.
I specify again, I have to add a new search help to standard screen/field and not to enhance it.
This is HR specific transaction. If someone has done similar thing with some other transation, please let me know.
There is no existing search help for these fields. If sm1 ever tried or has an idea how to add new search help to a standard screen/field.
It's urgent.
Thanks in advace. Suitable answers will be rewarded

Hi Pradeep,
Please have a look into the below site which might be useful
Enhancing a Standard Search Help
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/daeda0d7-0701-0010-8caa-
edc983384237
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee93446011d189700000e8322d00/frameset.htm
A search help exit is a function module for making the input help process described by the search help more flexible than possible with the standard version.
This function module must have the same interface as function module F4IF_SHLP_EXIT_EXAMPLE. The search help exit may also have further optional parameters (in particular any EXPORTING parameters).
A search help exit is called at certain timepoints in the input help process.
Note: The source text and long documentation of the above-specified function module (including the long documentation about the parameters) contain information about using search help exits.
Function modules are provided in the function library for operations that are frequently executed in search help exits. The names of these function modules begin with the prefix F4UT_. These function modules can either be used directly as search help exits or used within other search help exits. You can find precise instructions for use in the long documentation for the corresponding function module.
During the input help process, a number of timepoints are defined that each define the beginning of an important operation of the input help process.
If the input help process is defined with a search help having a search help exit, this search help exit is called at each of these timepoints. If required, the search help exit can also influence the process and even determine that the process should be continued at a different timepoint.
timepoints
The following timepoints are defined:
1. SELONE
Call before selecting an elementary search help. The possible elementary search helps are already in SHLP_TAB. This timepoint can be used in a search help exit of a collective search help to restrict the selection possibilities for the elementary search helps.
Entries that are deleted from SHLP_TAB in this step are not offered in the elementary search help selection. If there is only one entry remaining in SHLP_TAB, the dialog box for selecting elementary search helps is skipped. You may not change the next timepoint.
The timepoint is not accessed again if another elementary search help is to be selected during the dialog.
2. PRESEL1
After selecting an elementary search help. Table INTERFACE has not yet been copied to table SELOPT at this timepoint in the definition of the search help (type SHLP_DESCR_T). This means that you can still influence the attachment of the search help to the screen here. (Table INTERFACE contains the information about how the search help parameters are related to the screen fields).
3. PRESEL
Before sending the dialog box for restricting values. This timepoint is suitable for predefining the value restriction or for completely suppressing or copying the dialog.
4. SELECT
Before selecting the values. If you do not want the default selection, you should copy this timepoint with a search help exit. DISP should be set as the next timepoint.
5. DISP
Before displaying the hit list. This timepoint is suitable for restricting the values to be displayed, e.g. depending on authorizations.
6. RETURN (usually as return value for the next timepoint)
The RETURN timepoint should be returned as the next step if a single hit was selected in a search help exit.
It can make sense to change the F4 flow at this timepoint if control of the process sequence of the Transaction should depend on the selected value (typical example: setting SET/GET parameters). However, you should note that the process will then depend on whether a value was entered manually or with an input help.
7. RETTOP
You only go to this timepoint if the input help is controlled by a collective search help. It directly follows the timepoint RETURN. The search help exit of the collective search help, however, is called at timepoint RETTOP.
8. EXIT (only for return as next timepoint)
The EXIT timepoint should be returned as the next step if the user had the opportunity to terminate the dialog within the search help exit.
9. CREATE
The CREATE timepoint is only accessed if the user selects the function "Create new values". This function is only available if field CUSTTAB of the control string CALLCONTROL was given a value not equal to SPACE earlier on.
The name of the (customizing) table to be maintained is normally entered there. The next step returned after CREATE should be SELECT so that the newly entered value can be selected and then displayed.
10. APP1, APP2, APP3
If further pushbuttons are introduced in the hit list with function module F4UT_LIST_EXIT, these timepoints are introduced. They are accessed when the user presses the corresponding pushbutton.
Note: If the F4 help is controlled by a collective search help, the search help exit of the collective search help is called at timepoints SELONE and RETTOP. (RETTOP only if the user selects a value.) At all other timepoints the search help exit of the selected elementary search help is called.
If the F4 help is controlled by an elementary search help, timepoint RETTOP is not executed. The search help exit of the elementary search help is called at timepoint SELONE (at the
F4IF_SHLP_EXIT_EXAMPLE
This module has been created as an example for the interface and design of Search help exits in Search help.
All the interface parameters defined here are mandatory for a function module to be used as a search help exit, because the calling program does not know which parameters are actually used internally.
A search help exit is called repeatedly in connection with several
events during the F4 process. The relevant step of the process is passed on in the CALLCONTROL step. If the module is intended to perform only a few modifications before the step, CALLCONTROL-STEP should remain unchanged.
However, if the step is performed completely by the module, the following step must be returned in CALLCONTROL-STEP.
The module must react with an immediate EXIT to all steps that it does not know or does not want to handle.
Hope this info will help you.
***Reward points if found useful
Regards,
Naresh

Search help for input fields in a screen

Hi,
Pls help me
how to set search help property for the I/O fields in screen in se80?
1. do we want to add any property for search help in the property window?
2.do we want to create a MODULE PROCESS ON VALUE REQUEST ?
PLS tell me how to set search for the I/O field in se80?pls tell me the process?
i want to set the search help for more I/O fields in se80 but all the fields belongs to the same table?
can i create a single search for all these fields and use that for all the I/O fields ?
elementary search help or collective search help?
thanks & regards in advance,
vsnl.

Hi,
Input Help on the Screen
Within the Screen Painter, you can define two types of input help:
1. The FIELD statement with one of the additions VALUES or SELECT.
2. Linking a search help directly to a screen field.
If you link a search help directly to a screen field, it overrides the additions of the FIELD
statement. However, the input check [Page 581] functions of the FIELD statement remain
unaffected.
Input Help in Flow Logic
The following input help methods are obsolete and should not be used. They are still supported
for compatibility reasons.
In the screen flow logic, you can specify a value list for a screen field <f> as follows:
FIELD <f> VALUES (<val1>, <val2>,...).
The value list contains a series of single values <vali>. The NOT and BETWEEN additions for the
input check [Page 581] are not appropriate for input help.
You can also create a value list by accessing a database table as follows:
FIELD <f> SELECT *
FROM <dbtab>
WHERE <k1> = <f1> AND <k2> = <f2> AND...
In the WHERE condition, the fields of the primary key <ki> of the database table <dbtab> are
checked against the screen fields <fi>. The WHENEVER addition, used with input checks [Page
581], is not necessary for input help.
If you have used a ABAP Dictionary reference for field <f>, the selection and the hit list formatting
may be affected by any check table attached to the field.
Attaching a Search Help
Search helps from the ABAP Dictionary can be attached to a screen field [Ext.]. To do this, enter
the name of the search help in the corresponding field in the attributes of the screen field in the
Screen Painter. This assigns the first parameter of the search help to the screen field. It is only
possible to place a value from the hit list onto the screen.
Input help on a screen.
REPORT DEMO_DYNPRO_F4_HELP_DYNPRO MESSAGE-ID AT.
DATA: CARRIER(3) TYPE C,
CONNECTION(4) TYPE C.
CALL SCREEN 100.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
602 April 2001
Cancel
Airline
Flight number
Screen field with search help
Input help in the flow logic
The input fields have been adopted from the program fields CARRIER and
CONNECTION. The function code of the pushbutton is CANCEL, with function type
E. The search help DEMO_F4_DE with the search help parameter CARRID is
assigned to the screen field CARRIER. The search help uses the database table
SCARR.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
FIELD CARRIER VALUES ('AA', 'LH').
FIELD CONNECTION SELECT *
FROM SPFLI
WHERE CARRID = CARRIER
AND CONNID = CONNECTION.
When the user chooses the input help for the individual fields, the following input
help is displayed:
For the Airline field, the search help displays the names of the airlines and places the airline
code in the input field for the chosen line. If the airline code is not one of those listed in the
VALUES list of the screen flow logic, the input check triggers an error message in the PAI
event. So the search help overrides the VALUES addition for the input help, but not for the
input checks. This is therefore not an appropriate place to use the VALUE addition.
For the Flight number field, the flow logic displays the selected entries from the database
table SPFLI and places the selected line in the input field.
Regards,
Bhaskar

Search Help for Custom field in Sourcing Cockpit

Hi SRM Experts,
I added custom field "rush order" in the Structures as per requirement. I added code in MODIFY_SCREEN function module. Search help is working for "rush order" in Process Purchase Orders (to search PO) and Check Status (Searching Shopping Cart). But it is not working in sourcing cockpit. Please guide or suggest me is there any additional settings or programming is required to have search help for custom fields in Sourcing Cockpit.
Thanks a lot in advance.
Thanks,
Koyya

Hi SRM Experts,
Please let me know any suggestion on this issue.
Thanks a lot in advance.
Thanks,
Koyya

Custom search help for a custom field in SRM 7

EDIT: I'm gonna clarify on this thread since my first post wasn't explicative enough... thanks for the patience
Hi all gurus,
the question is about a search help in SRM7 but since the task is about abap development, I guess this is the right section to ask for.
Shortly; every purchase doc in our SRM7 has a custom header table which contains data which are retrieved from the connected backends. In this custom table, the user has the opportunity to add manually a line, and for a specific input field in table, we have to define a search help which should retrieve the appropriate possible values w.r.t. the "target" backend for the document.
A bit of technical data: say the field is called ZZ_R3_ROLE; it's included in a custom structure ZR7_HEADER_CST_GEN which is itself an append for BBP_PDHCF.
I defined a Search Help for that field and the corresponding exit FM to manage our task.
Unfortunately, to retrieve the possible values for the specific backend I need some informations like:
- the backend on which the document will be distributed;
- the process type of the document.
This means that my search help should take into account additional informations that comes from the document I'm processing; I don't know what's the "clean" solution to do this.
I've seen on an old system (a SAP SRM 3.0) a workaround based on IMPORT/EXPORT ... TO MEMORY ID has been used. Actually, I'd like to find a more elegant solution, if any.
So... as you can see, I'm absolutely a newbie on the argument, but since I can trigger the search help only from a purchase document (PO, contract) process, I should need at least the GUID of the document to retrieve, for example, what's the target backend for that document in order to provide proper values.
Any hint/suggestion and in particular, a sketch of code as example is welcome.
Edited by: Matteo Montalto on Oct 22, 2010 3:01 PM

Hi,
into your modify view,
extract data you need in your search help in an itab (do it into a class do not perform select directly into modify view) and then bind it as value help to your WD element.
Regards,
Ivan

Attaching Search Help for screen field in standard transaction

Dear All,
I want to attach my own custom search help for field 'Requiremenr Tracking Number (BEDNR) in PO (ME21n).
How can i do this?
Pls gv the stps.
Thanks a lot.
Kind Regards.

Prasad, you know, when I search forum for answers, I'm really disappointed when I see people have found a solution but don't share, and as the thread was maybe one year old or later, I don't feel to ask because the guy probably don't remember what he did. So giving a little explanation immediately is always a very good idea.

How to create Search Help for a field in Table control !!

Hello Friends,
 I like to know - How to create Search Help for a field in Table control. Is it possible, if it is please share ur knowledge, I wud be happy if U provide some source code example for this.
Thanks,
Senthil

Check the sample code:
*& Include ZSRO_MPRN_SEARCH *
MODULE PSTLZ_F4 INPUT
MODULE pstlz_f4 INPUT.
reading post code
DATA: stepl TYPE systepl,
 stepl_index TYPE systepl.
CLEAR: stepl, stepl_index.
CLEAR: lt_returntab,lt_dynpfields,i_mprn1.
REFRESH: lt_returntab,lt_dynpfields,i_mprn1.
lt_dynpfields-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields-stepl = stepl.
APPEND lt_dynpfields. CLEAR lt_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
 translate_to_upper = c_x
 determine_loop_index = c_x
 TABLES
 dynpfields = lt_dynpfields
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 OTHERS = 11.
IF sy-subrc EQ 0.
 READ TABLE lt_dynpfields INDEX 1.
ENDIF.
ws_outcode = lt_dynpfields-fieldvalue.
stepl_index = lt_dynpfields-stepl.
REPLACE '*' WITH ' ' INTO lt_dynpfields-fieldvalue.
IF NOT lt_dynpfields-fieldvalue IS INITIAL.
 MOVE lt_dynpfields-fieldvalue TO ws_outcode.
 ws_len = STRLEN( lt_dynpfields-fieldvalue ).
 IF ws_len GE 7.
 ws_len = ws_len - 3.
 ws_icode = ws_code+ws_len(3).
 lt_dynpfields-fieldvalue = lt_dynpfields-fieldvalue+0(ws_len).
 CONCATENATE lt_dynpfields-fieldvalue '%'
 INTO ws_outcode.
 CONDENSE lt_dynpfields-fieldvalue.
 REPLACE ws_icode WITH ' ' INTO lt_dynpfields-fieldvalue.
 ELSE.
 CONCATENATE lt_dynpfields-fieldvalue+0(4) '%'
 INTO ws_outcode.
 ENDIF.
 ws_ocode = ws_code+0(3).
ENDIF.
reading MPRN
CLEAR: lt_returntab,lt_dnpfields,i_mprn1.
REFRESH: lt_returntab,lt_dnpfields,i_mprn1.
lt_dnpfields-fieldname = 'I_MPRN-MPRN'.
lt_dnpfields-stepl = stepl_index.
APPEND lt_dnpfields. CLEAR lt_dnpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
 translate_to_upper = 'X'
 TABLES
 dynpfields = lt_dnpfields
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 OTHERS = 11.
IF sy-subrc EQ 0.
 READ TABLE lt_dnpfields INDEX 1.
ENDIF.
MPRN blank and Post code exist
IF lt_dnpfields-fieldvalue IS INITIAL.
 IF NOT lt_dynpfields-fieldvalue IS INITIAL.
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1
 WHERE outcode LIKE ws_outcode.
 ELSE.
MPRN blank and Post code blank
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1.
 ENDIF.
ELSE.
MPRN exist and Post code exist
 IF NOT lt_dynpfields-fieldvalue IS INITIAL.
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1
 WHERE outcode LIKE ws_outcode AND
 mprn EQ lt_dnpfields-fieldvalue.
 ELSE.
MPRN exist and Post code blank
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1
 WHERE mprn EQ lt_dnpfields-fieldvalue.
 ENDIF.
ENDIF.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 retfield = 'MPRN'
 dynpprog = sy-repid
 dynpnr = sy-dynnr
 window_title = 'Select MPRN'
 value_org = 'S'
 TABLES
 value_tab = i_mprn1 "lt_mprn
 return_tab = lt_returntab
 EXCEPTIONS
 parameter_error = 1
 no_values_found = 2
 OTHERS = 3.
IF sy-subrc EQ 0.
 READ TABLE lt_returntab INDEX 1.
 READ TABLE i_mprn1 WITH KEY mprn = lt_returntab-fieldval.
 IF sy-subrc EQ 0.
Updating post code
 CONCATENATE i_mprn1-outcode i_mprn1-incode
 INTO ws_postcode
 SEPARATED BY space.
 MOVE ws_postcode TO i_mprn-post_code.
 CLEAR : i_dnpfld,
 ws_dynpfld.
 REFRESH : i_dnpfld.
 ws_dyname = 'ZSRO_MASTER_DATA'.
 ws_dynumb = '0301'.
 ws_dynpfld-fieldname ='I_MPRN-POST_CODE'.
 ws_dynpfld-fieldvalue = ws_postcode .
 ws_dynpfld-stepl = stepl_index.
 APPEND ws_dynpfld TO i_dnpfld.
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname
 dynumb = ws_dynumb
 TABLES
 dynpfields = i_dnpfld
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
Updating MPRN
 MOVE i_mprn1-mprn TO i_mprn-mprn.
 CLEAR : i_dnpfld,
 ws_dynpfld.
 REFRESH : i_dnpfld.
 ws_dyname = 'ZSRO_MASTER_DATA'.
 ws_dynumb = '0301'.
 ws_dynpfld-fieldname ='I_MPRN-MPRN'.
 ws_dynpfld-fieldvalue = i_mprn1-mprn .
 ws_dynpfld-stepl = stepl_index.
 APPEND ws_dynpfld TO i_dnpfld.
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname
 dynumb = ws_dynumb
 TABLES
 dynpfields = i_dnpfld
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
 ENDIF.
ELSEIF sy-subrc EQ 2.
 MESSAGE s005(zspa) WITH ws_postcode .
ENDIF.
ENDMODULE. "PSTLZ_F4 INPUT
MODULE MPRN_F4 INPUT
MODULE mprn_f4 INPUT.
reading post code
DATA: stepl TYPE systepl,
 stepl_index TYPE systepl.
CLEAR: stepl, stepl_index.
CLEAR: lt_returntab,lt_dynpfields,i_mprn1.
REFRESH: lt_returntab,lt_dynpfields,i_mprn1.
lt_dynpfields-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields-stepl = stepl.
APPEND lt_dynpfields. CLEAR lt_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
 translate_to_upper = c_x
 determine_loop_index = c_x
 TABLES
 dynpfields = lt_dynpfields
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 OTHERS = 11.
IF sy-subrc EQ 0.
 READ TABLE lt_dynpfields INDEX 1.
ENDIF.
ws_outcode = lt_dynpfields-fieldvalue.
stepl_index = lt_dynpfields-stepl.
REPLACE '*' WITH ' ' INTO lt_dynpfields-fieldvalue.
IF NOT lt_dynpfields-fieldvalue IS INITIAL.
 MOVE lt_dynpfields-fieldvalue TO ws_outcode.
 ws_len = STRLEN( lt_dynpfields-fieldvalue ).
 IF ws_len GE 7.
 ws_len = ws_len - 3.
 ws_icode = ws_code+ws_len(3).
 lt_dynpfields-fieldvalue = lt_dynpfields-fieldvalue+0(ws_len).
 CONCATENATE lt_dynpfields-fieldvalue '%'
 INTO ws_outcode.
 CONDENSE lt_dynpfields-fieldvalue.
 REPLACE ws_icode WITH ' ' INTO lt_dynpfields-fieldvalue.
 ELSE.
 CONCATENATE lt_dynpfields-fieldvalue+0(4) '%'
 INTO ws_outcode.
 ENDIF.
 ws_ocode = ws_code+0(3).
ENDIF.
reading MPRN
CLEAR: lt_returntab,lt_dnpfields,i_mprn1.
REFRESH: lt_returntab,lt_dnpfields,i_mprn1.
lt_dnpfields-fieldname = 'I_MPRN-MPRN'.
lt_dnpfields-stepl = stepl_index.
APPEND lt_dnpfields. CLEAR lt_dnpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
 translate_to_upper = 'X'
 TABLES
 dynpfields = lt_dnpfields
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 OTHERS = 11.
IF sy-subrc EQ 0.
 READ TABLE lt_dnpfields INDEX 1.
ENDIF.
MPRN blank and Post code exist
IF lt_dnpfields-fieldvalue IS INITIAL.
 IF NOT lt_dynpfields-fieldvalue IS INITIAL.
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1
 WHERE outcode LIKE ws_outcode.
 ELSE.
MPRN blank and Post code blank
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1.
 ENDIF.
ELSE.
MPRN exist and Post code exist
 IF NOT lt_dynpfields-fieldvalue IS INITIAL.
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1
 WHERE outcode LIKE ws_outcode AND
 mprn EQ lt_dnpfields-fieldvalue.
 ELSE.
MPRN exist and Post code blank
 SELECT mprn ser_num sub_bud bud_name del_pt_alias
 bud_num dep_street prin_street dbl_dep_street
 dep_locty post_town county outcode incode
 lg_site_ind file_date FROM zspa_mprn INTO
 CORRESPONDING FIELDS OF TABLE i_mprn1
 WHERE mprn EQ lt_dnpfields-fieldvalue.
 ENDIF.
ENDIF.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 retfield = 'MPRN'
 dynpprog = sy-repid
 dynpnr = sy-dynnr
 window_title = 'Select MPRN'
 value_org = 'S'
 TABLES
 value_tab = i_mprn1 "lt_mprn
 return_tab = lt_returntab
 EXCEPTIONS
 parameter_error = 1
 no_values_found = 2
 OTHERS = 3.
IF sy-subrc EQ 0.
 READ TABLE lt_returntab INDEX 1.
 READ TABLE i_mprn1 WITH KEY mprn = lt_returntab-fieldval.
 IF sy-subrc EQ 0.
Updating MPRN
 MOVE i_mprn1-mprn TO i_mprn-mprn.
 CLEAR : i_dnpfld,
 ws_dynpfld.
 REFRESH : i_dnpfld.
 ws_dyname = 'ZSRO_MASTER_DATA'.
 ws_dynumb = '0301'.
 ws_dynpfld-fieldname ='I_MPRN-MPRN'.
 ws_dynpfld-fieldvalue = i_mprn1-mprn .
 ws_dynpfld-stepl = stepl_index.
 APPEND ws_dynpfld TO i_dnpfld.
**code changed by laxman 10.08.2005
 ws_dynpfld-stepl = mprn-current_line.
**code changed by laxman 10.08.2005
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname
 dynumb = ws_dynumb
 TABLES
 dynpfields = i_dnpfld
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
Updating post code
 CONCATENATE i_mprn1-outcode i_mprn1-incode
 INTO ws_postcode
 SEPARATED BY space.
 MOVE ws_postcode TO i_mprn-post_code.
 CLEAR : i_dnpfld,
 ws_dynpfld.
 REFRESH : i_dnpfld.
 ws_dyname = 'ZSRO_MASTER_DATA'.
 ws_dynumb = '0301'.
 ws_dynpfld-fieldname ='I_MPRN-POST_CODE'.
 ws_dynpfld-fieldvalue = ws_postcode .
 ws_dynpfld-stepl = stepl_index.
 APPEND ws_dynpfld TO i_dnpfld.
**code changed by laxman 10.08.2005
 break gblap0.
 ws_dynpfld-stepl = mprn-current_line.
 LOOP AT i_mprn.
 MOVE i_mprn1-mprn TO i_mprn-mprn.
 MOVE ws_postcode TO i_mprn-post_code.
 MODIFY i_mprn INDEX
 mprn-current_line." transporting MPRN POST_CODE.
 ENDLOOP.
**code changed by laxman 10.08.2005
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname
 dynumb = ws_dynumb
 TABLES
 dynpfields = i_dnpfld
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
 ENDIF.
ELSEIF sy-subrc EQ 2.
 MESSAGE s006(zspa) WITH i_mprn1-mprn .
ENDIF.
ENDMODULE. "MPRN_F4 INPUT
MODULE GNTC_F4 INPUT
MODULE gntc_f4 INPUT.
DATA: BEGIN OF lt_gntc OCCURS 0,
 gntc LIKE iflot-zzgntc,
 END OF lt_gntc.
CLEAR: lt_returntab, lt_gntc.
REFRESH: lt_returntab, lt_gntc.
lt_gntc-gntc = 'DM'.
APPEND lt_gntc. CLEAR lt_gntc.
lt_gntc-gntc = 'NDM'.
APPEND lt_gntc. CLEAR lt_gntc.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 retfield = 'ZZGNTC'
 dynpprog = sy-repid
 dynpnr = sy-dynnr
 window_title = 'Select Gas Nomination Type Code'
 value_org = 'S'
 TABLES
 value_tab = lt_gntc
 return_tab = lt_returntab
 EXCEPTIONS
 parameter_error = 1
 no_values_found = 2
 OTHERS = 3.
IF sy-subrc EQ 0.
 READ TABLE lt_returntab INDEX 1.
 i_mprn-dm_ndm = lt_returntab-fieldval.
ENDIF.
ENDMODULE. "GNTC_F4 INPUT
*& Module mprn1_f4 INPUT
 text
MODULE mprn1_f4 INPUT.
DATA: lt_f4 TYPE ddshretval OCCURS 0 WITH HEADER LINE,
 lt_returntab1 LIKE ddshretval OCCURS 0 WITH HEADER LINE,
 lt_dynpfields1 LIKE dynpread OCCURS 0 WITH HEADER LINE,
 lt_dnpfields1 LIKE dynpread OCCURS 0 WITH HEADER LINE.
DATA: stepl1 TYPE systepl,
 stepl_index1 TYPE systepl.
DATA : i_dnpfld1 LIKE dynpread OCCURS 0 WITH HEADER LINE,
 ws_dyname1 LIKE d020s-prog,
 ws_dynumb1 LIKE d020s-dnum,
 ws_dynpfld1 LIKE dynpread.
CLEAR: i_dnpfld1, ws_dyname1, ws_dynumb1, ws_dynpfld1,
 lt_f4, lt_returntab1,lt_dynpfields1, lt_f4,
 stepl1, stepl_index1.
REFRESH: i_dnpfld1, lt_returntab1,lt_dynpfields1, lt_f4.
To Determine Steploop Index
lt_dynpfields1-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields1-stepl = stepl1.
APPEND lt_dynpfields1. CLEAR lt_dynpfields1.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
 translate_to_upper = 'X'
 determine_loop_index = 'X'
 TABLES
 dynpfields = lt_dynpfields1
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 OTHERS = 11.
IF sy-subrc EQ 0.
 READ TABLE lt_dynpfields1 INDEX 1.
ENDIF.
stepl_index1 = lt_dynpfields1-stepl.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
 EXPORTING
 tabname = 'IFLOT'
 fieldname = 'I_MPRN-MPRN'
 searchhelp = 'ZS_MPRN_PC'
 dynpprog = sy-repid
 dynpnr = sy-dynnr
 TABLES
 return_tab = lt_f4
 EXCEPTIONS
 field_not_found = 1
 no_help_for_field = 2
 inconsistent_help = 3
 no_values_found = 4
 OTHERS = 5.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Update tablecontrol
READ TABLE lt_f4 WITH KEY fieldname = 'MPRN'.
IF sy-subrc = 0.
 MOVE lt_f4-fieldval TO i_mprn-mprn.
 ws_dyname1 = 'ZSRO_MASTER_DATA'.
 ws_dynumb1 = '0301'.
 ws_dynpfld1-fieldname ='I_MPRN-MPRN'.
 ws_dynpfld1-fieldvalue = i_mprn-mprn.
 ws_dynpfld1-stepl = stepl_index1.
 APPEND ws_dynpfld1 TO i_dnpfld1.
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname1
 dynumb = ws_dynumb1
 TABLES
 dynpfields = i_dnpfld1
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
ENDIF.
CLEAR : i_dnpfld1, ws_dynpfld1.
REFRESH: i_dnpfld1.
READ TABLE lt_f4 WITH KEY fieldname = 'ZZPSTLZ'.
IF sy-subrc = 0.
 MOVE lt_f4-fieldval TO i_mprn-post_code.
 ws_dyname1 = 'ZSRO_MASTER_DATA'.
 ws_dynumb1 = '0301'.
 ws_dynpfld1-fieldname ='I_MPRN-POST_CODE'.
 ws_dynpfld1-fieldvalue = i_mprn-post_code.
 ws_dynpfld1-stepl = stepl_index1.
 APPEND ws_dynpfld1 TO i_dnpfld1.
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname1
 dynumb = ws_dynumb1
 TABLES
 dynpfields = i_dnpfld1
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
ENDIF.
ENDMODULE. " mprn1_f4 INPUT
*& Module pstlz1_f4 INPUT
 text
MODULE pstlz1_f4 INPUT.
CLEAR: i_dnpfld1, ws_dyname1, ws_dynumb1, ws_dynpfld1,
 lt_f4, lt_returntab1,lt_dynpfields1, lt_f4,
 stepl1, stepl_index1.
REFRESH: i_dnpfld1, lt_returntab1,lt_dynpfields1, lt_f4.
To Determine Steploop Index
lt_dynpfields1-fieldname = 'I_MPRN-MPRN'.
lt_dynpfields1-stepl = stepl1.
APPEND lt_dynpfields1. CLEAR lt_dynpfields1.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
 translate_to_upper = 'X'
 determine_loop_index = 'X'
 TABLES
 dynpfields = lt_dynpfields1
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 OTHERS = 11.
IF sy-subrc EQ 0.
 READ TABLE lt_dynpfields1 INDEX 1.
ENDIF.
stepl_index1 = lt_dynpfields1-stepl.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
 EXPORTING
 tabname = 'IFLOT'
 fieldname = 'I_MPRN-POST_CODE'
 searchhelp = 'ZS_MPRN_PC'
 dynpprog = sy-repid
 dynpnr = sy-dynnr
 TABLES
 return_tab = lt_f4
 EXCEPTIONS
 field_not_found = 1
 no_help_for_field = 2
 inconsistent_help = 3
 no_values_found = 4
 OTHERS = 5.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Update tablecontrol
READ TABLE lt_f4 WITH KEY fieldname = 'ZZPSTLZ'.
IF sy-subrc = 0.
 MOVE lt_f4-fieldval TO i_mprn-post_code.
 ws_dyname1 = 'ZSRO_MASTER_DATA'.
 ws_dynumb1 = '0301'.
 ws_dynpfld1-fieldname ='I_MPRN-POST_CODE'.
 ws_dynpfld1-fieldvalue = i_mprn-post_code.
 ws_dynpfld1-stepl = stepl_index1.
 APPEND ws_dynpfld1 TO i_dnpfld1.
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname1
 dynumb = ws_dynumb1
 TABLES
 dynpfields = i_dnpfld1
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
ENDIF.
CLEAR : i_dnpfld1, ws_dynpfld1.
REFRESH: i_dnpfld1.
READ TABLE lt_f4 WITH KEY fieldname = 'MPRN'.
IF sy-subrc = 0.
 MOVE lt_f4-fieldval TO i_mprn-mprn.
 ws_dyname1 = 'ZSRO_MASTER_DATA'.
 ws_dynumb1 = '0301'.
 ws_dynpfld1-fieldname ='I_MPRN-MPRN'.
 ws_dynpfld1-fieldvalue = i_mprn-mprn.
 ws_dynpfld1-stepl = stepl_index1.
 APPEND ws_dynpfld1 TO i_dnpfld1.
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = ws_dyname1
 dynumb = ws_dynumb1
 TABLES
 dynpfields = i_dnpfld1
 EXCEPTIONS
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 undefind_error = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
ENDIF.
ENDMODULE. " pstlz1_f4 INPUT
Regards,
Prakash.

Creating a search help for a field in selection screen

Hi All,
There are 3 fields in the selection screen. They are
 WERKS
 DATE
 MATNR
Enter a value WERKS = 2465.
When I press the drop down menu for MATNR, it should only give the material number available for 2465.
I think, I should create a search help for it.
Kindly help me to create a search help for the material number based on the above condition.
Thanks in advance.

Hi
i am sending you a sample code where i had implemented a search help
for my req you can understand very easyly and write for ur req
reward if usefull for ur req
TYPES : BEGIN OF ST_OBJID_SH,
 OTYPE TYPE HRP1000-OTYPE,
 OBJID TYPE HRP1000-OBJID,
 END OF ST_OBJID_SH.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_OBJID-LOW.
IF S_OBJID IS NOT INITIAL.
 SELECT OTYPE OBJID FROM HRP1000
 INTO TABLE IT_OBJID_SH
 WHERE OTYPE = 'D'.
IF SY-SUBRC EQ 0.
SEARCH HELP FOR QUALIFICATION.
 CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 DDIC_STRUCTURE = ' '
 RETFIELD = 'OBJID'
 PVALKEY = ' '
 DYNPPROG = SY-REPID
 DYNPNR = SY-DYNNR
 DYNPROFIELD = 'S_OBJID'
 STEPL = 0
 WINDOW_TITLE =
 VALUE = ' '
 VALUE_ORG = 'S'
 MULTIPLE_CHOICE = ' '
 DISPLAY = ' '
 CALLBACK_PROGRAM = ' '
 CALLBACK_FORM = ' '
 MARK_TAB =
 IMPORTING
 USER_RESET =
 TABLES
 VALUE_TAB = IT_OBJID_SH
 FIELD_TAB =
 RETURN_TAB = RETURN_TAB
 DYNPFLD_MAPPING =
 EXCEPTIONS
 PARAMETER_ERROR = 1
 NO_VALUES_FOUND = 2
 OTHERS = 3
 IF SY-SUBRC <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
ENDIF.

Change Search Help for Payment Terms Field

Hi,
I would like to change the Search Help for Payment Terms Field, in Customer Master (KNVV-ZTERM). and in Sales Document. I believe it is the same.
Default is From Table T052 / T052U
ZTERM and TEXT1 Fields
I would like to have
From Table TVZBT
ZTERM and VTEXT
PayT Own Explanation Field.
Can we change the Search Help.

Hi,
The search help for the payment terms is not coming from the DDIC search help..
It is coded in the process on value-request event...
The function module FI_F4_ZTERM is called for this..you have to change this function module in case if you want the values from a different table..
OR do implicit enhancement in the subroutine FORM HELP_ZTERM in the include MF02DFH0 to call your search help instead of the function module FI_F4_ZTERM ..And do the same for the sales order also..
Thanks
Naren

EBS search string for check number

Hello Gurus
My client is using MT940 FORMAT for EBS,requirement is in a bank statement we are having 10 transactions which are having the same amount for ex:rs.1000 for ten payment transactions. now system is not able to post the document when we import the bank statement.
I wanted to use search string for check number, note to payee in bank statement is check number.Please find the below refference
/EI/400229001 010013
0000010013
Reference 010013
How could i use search string for this i tried but im not getting the solution im getting the following error difference is too large F5 263.
Appreciated for our help............
Thanks a lot in advance...............

Hi Paulo,
Thanks for the reply. However i have the following setting and it still does not work..
Mapping -> AB01
When i do the simulation it shows the Number and the hits and mapping.
In the Seach String use i have following settings:
CC 1000
Interpretation : ALL Interpretation
Search String : TEST1 ( this is the name that i gave to above search string)
Target : Posting RUle
Active checked.
But still when i upload the bank statement it is posting to Rule AB03 and not AB01
Also when i try FEBSTS it says no document hits ???
Your answer is greatly appreciated.

Search Help for Order Number

Similar Messages

Maybe you are looking for