QM_QCERT_01 - DISPLAY MODE to CHANGE MODE

Dear Experts,
I had make a copy of SAPScript form-QM_QCERT_01 in to ZQM_QCERT_01 and does some changes, the changes/enhamncements are working fine but i want to add a new window of footer for which it is not allowing since all its attributes are in display mode, create-new window is also in display mode , how can i change it to change mode and add a footer window into the form.
Alternatively is their any footer SAP SCRIPT command available ?, so that fixed text will always appear at the footer , this will also helps me to solve my issue
Your answer to this query highly appreciated
SHAFEEQ

Hi,
1.Go to Se71.
2.give the form name zformname and language as DE.
3.Edit the form and utilitiea--->convert from language
slanguage:DE
destination language:En.
4.Now make your changes(creating the window).windows---edit ---create element.
5.page windows---window name and dimensions
Regards,
Kumar(if helpful reward).
Edited by: shiva kumar on Apr 14, 2008 3:03 PM

Similar Messages

How to know if an transaction is in display mode or change mode

Hi,
I have to set an information message if any transaction is in display mode and an error message if it is in change mode for a particular condition.
How would I know programmatically that it is in display mode or change mode for a screen?

>
Neela M B wrote:
> Hi,
>
> You can use the importing parameter I_ACTIVITY of the method SET_DATA in the BADI. Pass this flag along with the data and use it to determine the Create/Change or Display Mode.
>
>
> CASE I_ACTIVITY.
>   WHEN 'H' or 'V'. " Create or Change
>     ...
>   WHEN 'A'.    " Display
>     ...
> ENDCASE.
You sure are a direct collegue and have access to his problem or you are indeed the successor of Uri Geller.
I never would have guessed he's using SET_DATA in a BADI.
Test: what am i thinking right now?

How to make a field from display mode to change mode for a perticular tcode

hi all,
my client want to change one field which is in display mode of a material doc in mb02.
Restrictions in some fields in MIGO needs to be changed.
Uploading point in case of issue: While editing the MIGO latter, this field needs to be edited.
Goods recipient in case of receipt: While editing the MIGO latter, this field needs to be edited.

hi thanks for quick replay,
my requirement is, supose i post a material doc through migo in 101 mtype, in item detail, where tab i have given the good reciepitant and unloading point. but while i want to change that material doc in mb02, i saw unloading point is in change mode, but good reciepitant field is in display mode. my client requirement is to change that field. so for change that field, the field should be in change mode, so thats what i want.
i have checked in configuration side, but i didnt get any setting, i think we have to customize that standard screen.
any comments?
regards,
susanta
Edited by: susanta bindhani on Jun 19, 2008 2:18 PM

How to make a field as display in a change mode

hi gurus
is there any option to reduce the accessblity of a particular field has to be set as deactive mode.
Eg
In tcode XD02
I have to deactive any one of the field in this.
please explain is there any chance to do ?
regards
Maithrayan

Transaction variants simplify transaction flow by:
Inserting default values in fields
Hiding and changing the ready for input status of fields
Hiding and changing the attributes of table control columns
Hiding individual menu functions
Hiding entire screens
Transaction variants are actually made up of a series of screen variants. The field values and field attributes for each screen in a transaction variant are stored in screen variants. Each variant is assigned to a transaction. Variants may, however, contain values for screens in multiple transactions, if transaction flow makes this necessary. The transaction the variant is assigned to serves as its initial transaction, whenever you start the variant.
Both client-specific and cross-client transaction variants exist. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction.
A specific namespace has been designated for cross-client transaction variants and screen variants and they are both automatically attached to the Change and Transport System. Client-specific transaction variants can be transported manually.
Transaction and screen variants may be created for all dialog and reporting transactions. However, there are certain restrictions that apply to their use, depending on how their corresponding transactions have been realized internally.
Transaction variants may not be created for transactions already containing pre-defined parameters (parameter transactions and variant transactions).
You can only create transaction variants for dialog transactions and reporting transactions.
Only "normal" screens, dialog boxes, and subscreens can be included in the variant.
Screen variants are automatically created anytime you create a transaction variant.
To create a transaction variant, proceed as follows:
Choose Tools ® AcceleratedSAP ® Personalization to call the transaction variant maintenance transaction, or use transaction code SHD0.
Enter the name of the transaction and the transaction variant on the initial screen.
The system creates a cross-client transaction variant. If you want to create a client-specific transaction variant, choose Goto ® Client-specific transaction variants to branch the client-specific transaction variant maintenance transaction.
Client-specific transaction variants only exist in the client in which they are created. The field contents of the transaction variant must be available in this client. Cross-client transaction variants are available throughout the system, regardless of the client currently being used. The field contents of these transaction variants must be available in all clients.
Choose Create to create a variant.
The system calls the application transaction that you want to create a variant for.
Enter the values you want to use in the input fields. Each time an action is completed (choosing for example), a dialog box appears listing the fields of the current screen with their current values. The kind of dialog box called depends on the kind of screen currently being processed ( see Requirements).
Choose the options you want. The following options checkboxes can be selected: Adopt field values
Saves the field values you have inserted on the current screen
Resetting this field (deselecting it) allows you to delete all values saved for this screen in your transaction variant.
Do not display screen
Hides screen
This is only possible if settings are copied to your variant (Adopt field values).
With contents
Field contents are saved with it
Output only
Field is no longer ready for input (display mode only)
Invisible
Hides field
Mandatory
Required field
You may or may not be able to select each of these checkboxes for every field depending on the field's type (see Requirements).
Enter a screen variant name and corresponding short text if necessary.
Screen variants are created automatically for each screen where values have been saved (copied). Enter screen variant names in the Name of screen variant: field. These names must be unique. If the system is able to find a unique name for a screen variant, it is automatically inserted into this field. (The convention reads as follows: .)
The following pushbuttons are available from this dialog box:
Cancel
Displays current application transaction screen again. Here you can make changes to your settings.
Deactivate menu functions
Deactivates menu functions in an additional dialog box.
GuiXT
Allows user to edit a GuiXT script for the current screen ( GuiXT).
Exit and Save
Exits and saves application transaction.
Choose the function Continue to proceed to the next screen in your application transaction. Repeat steps 3-5 for all further screens in the transaction.
When you have reached the last screen of the transaction and inserted the values you want to insert, choose Exit and Save. The system exits the application transaction and saves your entries. A list appears containing all of the screens in the application transaction that you want to save entries for (that is, all screens for which screen variants will be created).
You can also branch to this list using the Change values function during the function selection process.
Enter a short text for your transaction variant.
Display settings can be changed as needed from this list in the future. Settings that require information at application transaction runtime (field values, table control columns) cannot be changed from this list.
Choose Save. The system saves your transaction variant and the corresponding screen variants. The Workbench Organizer dialog box is displayed for the transaction variant and for each screen variant. Use it to assign each of these objects to a package.
Deleting Preassigned Values
You can delete all of the values you assigned to fields of a single screen in a transaction variant by resetting (deselecting) the Adopt field values checkbox. This deletes the screen from your variant, even those entries that were transferred to the variant during previous processing.
If a screen variant has already been created for this screen, then the system simply deletes the screen variant's transaction variant assignment; the screen variant itself is not actually deleted.
Individual fields can be deleted from transaction and screen variants by resetting (deselecting) their corresponding checkboxes.
Also refer to document;
http://help.sap.com/saphelp_nw04s/helpdata/en/67/232037ebf1cc09e10000009b38f889/content.htm

Excise invoice number showing display option in J1IEX change mode.

Hi CIN Experts,
We are using E.C.C6.0.
In Excise transaction T.code: J1IEX Change option, Official Excise invoice number (J_1IEXHEAD-EXNUM) showing the display mode. How can change the Official Excise Document Number is display mode to change mode in T.code: J1IEX change option.
In 4.7E system showing the change option in T.code: J1IEX change mode.
Regards,
Hanuman

We cannot change this field from display to change. Once the excise invoice is captured the excise invoice number is freezed.
It is SAP Standard & to break this you would need the access key from SAP.
If the change in excise invoice number is by user mistake, please cancel the excise invocie and capture the new one.
Thanks & regards
Hameed Parvez

Problem with change mode in program

Hi,
I have problem to chage the program from display mode to change mode. I tried to change the mode by clicking change icon(little pen indicator) and also i tried with menu path program->Dispaly<>change also. But i got message that The user kumar currently editing the program. But i have not opened any sessions ,No one has opened this program also. I am not able to understand why the message "The user kumar currently editing the program coming". SO how to solve this. Plz help me regarding this.
Regards,
Kumar

go to SM12 delete all the lock entries for your user name. then try changing your program.
Regards
Raja

How to - only display the price of approved PO (not change mode)

Hi,
Following are our PO release strategy
1. Release id : P has
a. Released indicator (tick)
b. Changeablity - 4
The above setup is working fine, means still after the approval users can change all the fields. New strategy is triggered once the values are changed.
Now the issue is business owner does not want the price, qty in change mode after approval. After approval ME22N to show
1. Price & qty to be in display mode
2. All other fields (except the one which affects PRICE) in change mode.
I tried to all the combinations, but after approval I get to see either all the fields in display mode or all in change mode.
Is it possible to display the price related fields only for the approved PO in ME22N.
Please advice
Thanks,
Raj.

Hi Mani,
Thanks for the fast reply.
1. There is no ME22N - Fsel Key available.
2. Only for the approved PO - we want the price fields in display mode.
3. There is no restriction required for the un approved POs.
Is there any way.
Please reply
Thanks
Raj.

All photos in portrait format are displayed blurred in the preview mode "fill" of the library. In all other modes e.g. "fit"or "1:2" the photos are sharp. How can I change this, so that the photos are still sharp when displaying them in the mode "fill"?

All photos in portrait format are displayed blurred in the preview mode "fill" of the library. In all other modes e.g. "fit"or "1:2" the photos are sharp. How can I change this, so that the photos are still sharp when displaying them in the mode "fill"? My Lightroom release is 5.7.1.
Thanking you in anticipation!

I'd like to get all these '-1 suffix' files together with their associated Develop adjustments into one folder (if they aren't already) so I can see them in Grid view in the Library module, which I use as my basic starting point for everything else at this early stage of my Lightroom 'career'.
To see what folder these are stored in, right-click on a photo and select "Go to Folder in Library".
Advice: if you are going to use Lightroom effectively, you probably want to stop using folders as your method to create a grouping of photos that are already in Lightroom; there are plenty of built-in tools, such as keywords, collections, color labels, etc.
I don't understand why the search on the entire catalog picked up apparently the same two file versions but also got the Develop adjustments when going to the relevant Folder didn't show the adjustment black squares against each image in Grid view nor were they there when the images were opened in the Develop module. Perhaps if I understood this, I'd be a bit more confident of moving forward myself.
These are most likely different versions of the same photo, in different folders. Lightroom stores the edits in its own catalog, and so it knows that one folder's photos have edits, and the other folder's photos do not have edits. Please understand that Lightroom is a database, it knows where the photos are at the time you import them (or add them to the catalog by synchronize), and then if you move things around in your operating system, Lightroom does not know anything about that and problems begin. Thus the advice to organize using Lightroom tools and methods and not operating system tools and methods.

How to make the Business Area field from Change Mod to Display Mode in AS02

Hi Gurus,
I created a Customized T-code YAS02 for making the Business Area in Display mode with the help of SHD0.
But my client wants to do the same in standard T-code of AS02 and they don't like to use the customized T-code.
Kindly advise to make the Business Area from Change Mode to Display Mode in AS02.
Thanks in advance...
regs / Devi Aparna

Hi Devi,
check the following customization
asset accounting -> Integration with the General Ledger> Additional Account Assignment Objects-> Activate Account Assignment Objects---
Regards,
Ranjith

How to handle "Display/Change" mode in XD0x with CUSTOMER_ADD_DATA_CS

Hi,
I've implemented customer fields to the debitor master data screen with BADI CUSTOMER_ADD_DATA_CS,
using methods SET_DATA and GET_DATA and created a new screen within a Z-function group.
So I have a new tab with the custom fields. If I do nothing further, the fields are input enabeld also within transaction XD03.
At the moment, I'm using the value of sy-tcode to check for display (=XD03) or change/create (XD02/XD01) mode to handle
the enable/disable mode of this fields.
This is my coding in the PBO of my Z-screen.
LOOP AT SCREEN.
    IF screen-group1 = 'Z01'.
      IF sy-tcode = 'XD03' OR sy-tcode = 'VD03'.
        IF sy-ucomm = 'ENTR'.
          screen-input = '1'.
         ELSE.
*.. display mode
          screen-input = '0'.
        ENDIF.
      ENDIF.
   ENDLOOP.
But if the user change form display to change mode wthin(!) the transaction, the sy-tcode is still XD03 and not XD02.
If this is done in the screen with the custom fields, I can check for sy-ucomm (='ENTR'), but if an other screen is opened, I could not check for sy-ucomm.
How can I handle this?
I've found the following enhancement point:
ENHANCEMENT-POINT MF02DFD0_01 SPOTS ES_MF02DFD0 INCLUDE BOUND.
Or can I use the other methods in the BADI like SET_FCODE?
Thanks in advance!
Andreas

Hi Andreas:
I have to do something similar but for t-code FD02/FD03.
I've created a program type M to control my new dynpro, and using a PBO module to change the screen depending on display/modify.
I'm trying to add code to method SET_DATA, but my knowledge on OO programamtion is limited.
Could you please provide the part of your code to implement the solution described in this post?.
Best regards,
Carlos.

How to change qty field as change mode to display mode in VL32N

Hi Guru's,
My requirement is for particular users quantity field in VL32N to display mode remaining users it should be in change mode.
We are already created a Security Object for this.
Can you please anyone help how to approach this requiremnt. Is there any standard BAdI for this.
Thanks in Advance.
Regards,
Sai Rama

Hi
There are Badi for this T-code
VMDE0004                                Shipping Interface: Message SDPACK (Packing, Inbound)
VMDE0003                                Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0002                                Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0001                                Shipping Interface: Error Handling - Inbound IDoc
V53W0001                                User exits for creating picking waves
V53C0002                                W&S: RWE enhancement - shipping material type/time slot
V53C0001                                Rough workload calculation in time per item
V50S0001                                User Exits for Delivery Processing
V50R0004                                Calculation of Stock for POs for Shipping Due Date List
V50R0002                                Collective processing for delivery creation
V50R0001                                Collective processing for delivery creation
V50Q0001                                Delivery Monitor: User Exits for Filling Display Fields
V50PSTAT                                Delivery: Item Status Calculation
V02V0004                                User Exit for Staging Area Determination (Item)
V02V0003                                User exit for gate + matl staging area determination (headr)
V02V0002                                User exit for storage location determination
V02V0001                                Sales area determination for stock transport
You can try with any one of them V53W0001, V50S0001, V50Q0001, V02V0004, also you can proceed with table auhtorization as there is need to check one table before entring in T-code as if user id is there then not able to edit.
Here don't make code like need to maintain all id's, if id is there then not able to edit, so to whom you don't want to allow maintain their id's in that.
Thanks
Bhupinder Singh Arora

Quantity confirmed in sales order change mode not in display mode !!!

Dear All !!
We have a problem in sales order .
In sales order the line item 580 quantity confirmed 15 pc in change mode VA02 if I open the sales order in display mode VA03 the quantity confirmed “0”
More details refer the attachment .
Kindly advise why the system behaving like this and suggest how to control.
Thanks in advance.
Best Regards,
Rampe

Dear All !!
The issue has been sort it out .
Reason for cause : The Problem happened due to wrong material master data defined in material master.
The material has been changed and marked "as configurable material" in material view "Basic Data 2".Even though the material is not configurable. So we have forced correct value in material master and open the sales order with VA02 and then saved in order to redetermine correct master data. Then the problem got resolved.
Thanks for your Help.
Best Regards
Rampe

Header net value different in display and change mode in Sales Order.

Hi All,
I am facing a strange problem. When I check an order in display mode, I can see the header net value as 120047 Euro. However, If I open the order in change mode, it shows value as 133099.
Do not understand why?
Please help me to solve the issue.
Regards,
Neha

Dear Neha
Can you please clarify as to whether any header condition type is flowing in the sale order, so that I will try to give a suitable solution accordingly.
thanks
G. Lakshmipathi

ALV from Display to Change Mode

Hello,
I created an application that starts with a selection screen and then the user selects either a Create/Change/Display. Then a call screen is done in which i added an ALV with some editable fields.
The point is that when the user first selects 'Display' the ALV is all in the display mode. If he makes a BACK then goes to 'Change' the ALV is still displayed in the output mode. and vice-versa.
Is there a reason for this??
Please help

hi emym,
try this it may be helpful
Making ALV Grid Editable
->To make a column editable, it will be sufficient to set the field EDIT in the field catalog. The ALV Grid perceives if there are some editable fields and adds buttons for editing purposes. If you do not need these new buttons, you know how to exclude them.
->To make individual cells editable, we will utilize the table we used for making a cell a pushbutton. As you remember, it was of type LVC_T_STYL. If you have not added this inner table, add it now. For this procedure; add the name of the field to the field FIELDNAME, and pass cl_gui_alv_grid=>mc_style_enabled to make a field editable and cl_gui_alv_grid=>mc_style_disabled to make a field non-editable, to the field STYLE. You can use the one with disable when you make an entire column editable and want just a few of cells along it non-editable.
ps_layout-stylefname = CELLSTYLES .
If we want our column SEATSMAX entirely editable except the case CARRID is XY which is a rare case and we want our cells along the column PLANETYPE editable if their respective CONNID fields contain the value 02.
Assume we have added our style table (CELLSTYLES) to our list data table and tell the layout structure about it and we adjust the field catalog so that the column SEATSMAX has the property EDIT set to X.
refer this:
FORM adjust_editables USING pt_list LIKE gt_list[] .
DATA ls_listrow LIKE LINE OF pt_list .
DATA ls_stylerow TYPE lvc_s_styl .
DATA lt_styletab TYPE lvc_t_styl .
LOOP AT pt_list INTO ls_listrow .
IF ls_listrow-carrid = 'XY' .
ls_stylerow-fieldname = 'SEATSMAX' .
ls_stylerow-style = cl_gui_alv_grid=>mc_style_disabled .
APPEND ls_stylerow TO lt_styletab .
ENDIF .
IF ls_listrow-connid = '02' .
ls_stylerow-fieldname = 'PLANETYPE' .
ls_stylerow-style = cl_gui_alv_grid=>mc_style_enabled .
APPEND ls_stylerow TO lt_styletab .
ENDIF .
INSERT LINES OF lt_styletab INTO ls_listrow-cellstyles .
MODIFY pt_list FROM ls_listrow .
ENDLOOP .
ENDFORM
Conditionally setting fields to be editable or non-editable
->As usual, cell based settings override entire column settings. You can dynamically switch between cases in any proper part of your execution. Just fill your inner table as required and refresh table display; for entire column settings, set or unset the property EDIT of the field catalog for the column and reset the field catalog using set_frontend_fieldcatalog.
->As the last condition to be met for editability, you must call the method set_ready_for_input passing 1 to the parameter i_ready_for_input.
Using this method you can switch between editable and non-editable mode. As you guess, passing 0 to the parameter while calling the method, switches to non-editable mode.
rewrad if helpful
regards,
sravanthi

How to display particular ROW of a table control in display/change mode

Hi,
Can we make particular ROW in a table control display mode or editable mode depending upon the conditions?.
Any inputs..
Rgds,
Lakshmiraj

Hi,
Yes it is possible. check the follwoing code for help.
*& Include           Z101954_ASSIGNMENT1I01
*&      Module VALIDATE_SALES_ORG INPUT
      text
MODULE validate_sales_org INPUT.
SELECT SINGLE zvkorg FROM vbak INTO zvbak-zvkorg
*WHERE zvbeln = zbookhdr-zvbeln.
IF sy-subrc <> 0.
   MESSAGE 'INVALID AIRLINE ID INPUT' TYPE 'I'.
   CALL SCREEN 1000.
ENDIF.
ENDMODULE.                 " VALIDATE_SALES_ORG INPUT
*&      Module USER_COMMAND_1001 INPUT
      text
MODULE user_command_1001 INPUT.
var3 = 1.
IF sy-ucomm <> 'SAVE'.
    PERFORM material_check.
    IF sy-subrc <> 0.
      MESSAGE 'ENTER THE CORRECT MATERIAL NUMBER' TYPE 'I'.
    ELSE.
      SELECT SINGLE zmaktx zmeins zwaerk zstprs FROM zmara
        INTO CORRESPONDING FIELDS OF it_salesitems
         WHERE zmatnr = it_salesitems-zmatnr.
      SELECT SINGLE zwerks zlgort FROM zorg
        INTO CORRESPONDING FIELDS OF it_salesitems
        WHERE zvkorg = wa_salesorder-zvkorg
         AND zvtweg = wa_salesorder-zvtweg
         AND zspart = wa_salesorder-zspart.
      it_salesitems-znetwr = it_salesitems-zstprs * it_salesitems-zbrgew.
     MODIFY it_salesitems FROM it_salesitems INDEX sy-tabix.
      MOVE-CORRESPONDING it_salesitems TO temp_salesitems.
      APPEND temp_salesitems.
      REFRESH it_salesitems.
    ENDIF.
ENDIF.
LOOP AT temp_salesitems.
if it_salesitems-pick = 'X'.
           LOOP AT SCREEN.
         IF screen-name EQ 'DETAIL'.
           screen-input = 1.
           MODIFY SCREEN.
         ENDIF.
       ENDLOOP.
       endif.
       endloop.
CASE sy-ucomm.
    WHEN 'SAVE'.
      PERFORM check_ship_to_party.
      IF sy-subrc <> 0.
        MESSAGE 'ENTER THE CORRECT SHIP TO PARTY ' TYPE 'I'.
      ELSE.
        PERFORM check_payer.
        IF sy-subrc <> 0.
          MESSAGE 'ENTER THE CORRECT PAYER' TYPE 'I'.
        ELSE.
          PERFORM check_bill_to_party.
          IF sy-subrc <> 0.
            MESSAGE 'ENTER THE CORRECT BILL TO PARTY' TYPE 'I'.
          ELSE.
            wa_salesorder-zernam = sy-uname.
            MOVE-CORRESPONDING wa_salesorder TO zvbak.
            MODIFY zvbak.
            LOOP AT it_salesitems.
              it_salesitems-zvbeln = wa_salesorder-zvbeln.
              MOVE-CORRESPONDING it_salesitems TO zvbap.
              MODIFY zvbap.
            ENDLOOP.
            IF sy-subrc = 0.
              MESSAGE 'THE DATA IS SAVED SUCCESSFULLY' TYPE 'I'.
              CLEAR wa_salesorder.
              REFRESH it_salesitems.
              REFRESH temp_salesitems.
              IF sy-tcode = 'ZVA01'.
                CALL SCREEN '1000'.
              ELSE.
                CALL SCREEN '1003'.
              ENDIF.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDIF.
    WHEN 'DETAIL'.
      CALL SCREEN '1002'.
    WHEN 'BACK'.
      IF sy-tcode = 'ZVA03'.
        CLEAR wa_salesorder.
        CALL SCREEN '1003'.
      ELSE.
        PERFORM pop_up.
      ENDIF.
    WHEN 'EXIT'.
      IF sy-tcode = 'ZVA03'.
        LEAVE PROGRAM.
      ELSE.
        PERFORM pop_up.
      ENDIF.
    WHEN 'CANCEL'.
      IF sy-tcode = 'ZVA03'.
        CLEAR wa_salesorder.
        CALL SCREEN '1003'.
      ELSE.
        PERFORM pop_up.
      ENDIF.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_1001 INPUT
*&      Module input_help_sold_to_party INPUT
      text
MODULE input_help_sold_to_party INPUT.
SELECT zkunag FROM zvbak INTO CORRESPONDING FIELDS OF TABLE
    itab.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
DDIC_STRUCTURE         = ' '
      retfield               = 'ZKUNAG'
PVALKEY                = ' '
     dynpprog               = sy-cprog
     dynpnr                 = '1000'
     dynprofield            = 'ZKUNAG'
STEPL                  = 0
WINDOW_TITLE           =
VALUE                  = ' '
     value_org              = 'S'
MULTIPLE_CHOICE        = ' '
DISPLAY                = ' '
CALLBACK_PROGRAM       = ' '
CALLBACK_FORM          = ' '
MARK_TAB               =
IMPORTING
USER_RESET             =
    TABLES
      value_tab              = itab
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.                 " input_help_sold_to_party INPUT
*&      Form pop_up
      text
--> p1        text
<-- p2        text
FORM pop_up .
CALL FUNCTION 'POPUP_TO_CONFIRM'
    EXPORTING
TITLEBAR                    = ' '
DIAGNOSE_OBJECT             = ' '
      text_question               = 'DO YOU WANT TO SAVE THE ORDER?'
     text_button_1               = 'YES'(001)
     icon_button_1               = ' '
     text_button_2               = 'No'(002)
     icon_button_2               = ' '
     default_button              = '1'
     display_cancel_button       = 'X'
     userdefined_f1_help         = ' '
START_COLUMN                = 25
START_ROW                   = 6
POPUP_TYPE                  =
IV_QUICKINFO_BUTTON_1       = ' '
IV_QUICKINFO_BUTTON_2       = ' '
IMPORTING
     answer                      = ans
TABLES
PARAMETER                   =
EXCEPTIONS
TEXT_NOT_FOUND              = 1
OTHERS                      = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CASE ans.
    WHEN '001'.
      PERFORM check_ship_to_party.
      IF sy-subrc <> 0.
        MESSAGE 'ENTER THE CORRECT SHIP TO PARTY ' TYPE 'I'.
      ELSE.
        PERFORM check_payer.
        IF sy-subrc <> 0.
          MESSAGE 'ENTER THE CORRECT PAYER' TYPE 'I'.
        ELSE.
          PERFORM check_bill_to_party.
          IF sy-subrc <> 0.
            MESSAGE 'ENTER THE CORRECT BILL TO PARTY' TYPE 'I'.
          ELSE.
            wa_salesorder-zernam = sy-uname.
            MOVE-CORRESPONDING wa_salesorder TO zvbak.
            MODIFY zvbak_101954.
            temp_salesitems-zvbeln = wa_salesorder-zvbeln.
            MOVE-CORRESPONDING temp_salesitems TO zvbap.
            MODIFY zvbap.
            IF sy-subrc = 0.
              MESSAGE 'THE DATA IS SAVED SUCCESSFULLY' TYPE 'I'.
              CLEAR wa_salesorder.
              REFRESH it_salesitems.
              REFRESH temp_salesitems.
              IF sy-ucomm = 'EXIT'.
                LEAVE PROGRAM.
              ENDIF.
              IF sy-tcode = 'ZVA01'.
                CALL SCREEN '1000'.
              ELSE.
                CALL SCREEN '1003'.
              ENDIF.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDIF.
    WHEN '002'.
      IF sy-tcode = 'ZVA01'.
        CLEAR wa_salesorder.
        REFRESH it_salesitems.
        REFRESH temp_salesitems.
        CALL SCREEN '1000'.
      ELSE.
        CLEAR wa_salesorder.
        REFRESH it_salesitems.
        REFRESH temp_salesitems.
        CALL SCREEN '1003'.
        CLEAR ans.
      ENDIF.
ENDCASE.
ENDFORM.                    " pop_up
*&      Module USER_COMMAND_1002 INPUT
      text
MODULE user_command_1002 INPUT.
IF sy-datar = 'X'.
   PERFORM material_check.
   IF sy-subrc <> 0.
     MESSAGE 'ENTER THE CORRECT MATERIAL' TYPE 'I'.
   ELSE.
     SELECT SINGLE zmaktx zmeins zwaerk zstprs FROM zmara_101954
     INTO CORRESPONDING FIELDS OF wa_salesitems
       WHERE zmatnr = wa_salesitems-zmatnr.
     wa_salesitems-znetwr = wa_salesitems-zstprs * wa_salesitems-zbrgew.
   ENDIF.
   var = 1.
ENDIF.
IF sy-ucomm = 'BACK'.
    LOOP AT temp_salesitems.
      MODIFY temp_salesitems FROM wa_salesitems .
    ENDLOOP.
    it_salesitems-pick = ' '.
    CALL SCREEN '1001'.
ENDIF.
ENDMODULE.                 " USER_COMMAND_1002 INPUT
*&      Module USER_COMMAND_1000 INPUT
      text
MODULE user_command_1000 INPUT.
CASE sy-ucomm.
    WHEN 'NEXT'.
      SELECT * FROM zt001k_101954 INTO CORRESPONDING FIELDS OF
        temp_salesorder WHERE
        zvkorg = wa_salesorder-zvkorg AND
        zvtweg = wa_salesorder-zvtweg AND
        zspart = wa_salesorder-zspart.
      ENDSELECT.
      IF sy-subrc = 0.
        CALL SCREEN '1001'.
      ELSE.
        MESSAGE 'Invalid Data Entered' TYPE 'I'.
        CALL SCREEN '1000'.
      ENDIF.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_1000 INPUT
*&      Module USER_COMMAND_1003 INPUT
      text
MODULE user_command_1003 INPUT.
IF sy-ucomm = 'NEXT'.
   IF sy-datar = ' '.
     MESSAGE 'ENTER PURCHASE ORDER NUMBER' TYPE 'I'.
     CALL SCREEN 1000.
    IF NOT wa_salesorder-zvbeln CO '0123456789'.
      MESSAGE 'PURCHASE ORDER NUMBER IS NOT IN THE EXPECTED FORMAT' TYPE 'I'.
      CALL SCREEN '1003'.
    ENDIF.
    var3 = 0.
    CALL SCREEN '1001'.
ENDIF.
ENDMODULE.                 " USER_COMMAND_1003 INPUT
*&      Module input_help_sales_order INPUT
      text
MODULE input_help_sales_order INPUT.
SELECT zvbeln FROM zvbak_101954 INTO CORRESPONDING FIELDS OF TABLE
itab1.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
DDIC_STRUCTURE         = ' '
      retfield               = 'ZVBELN'
PVALKEY                = ' '
     dynpprog               = sy-cprog
     dynpnr                 = '1003'
     dynprofield            = 'ZVBELN'
STEPL                  = 0
WINDOW_TITLE           =
VALUE                  = ' '
     value_org              = 'S'
MULTIPLE_CHOICE        = ' '
DISPLAY                = ' '
CALLBACK_PROGRAM       = ' '
CALLBACK_FORM          = ' '
MARK_TAB               =
IMPORTING
USER_RESET             =
    TABLES
      value_tab              = itab1
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.                 " input_help_sales_order INPUT
*&      Module back_command INPUT
      text
module back_command input.
*if sy-ucomm = 'SAVE' OR 'BACK' OR 'DETAIL' OR 'EXIT' OR 'CANCEL'.
*endif.
endmodule.                 " back_command INPUT
Regards
Rajesh Kumar

QM_QCERT_01 - DISPLAY MODE to CHANGE MODE

Similar Messages

Maybe you are looking for