Adding fiels in XD01 subscreen-program SAPLV02Z screen no. 0200

Hi All,
I need to create custom fields in XD01 (Sales area-Extras-Additional Data) subscreen.
Program - SAPLV02Z screen no. 0200
I added fields in structure KNVV using append structure.
Now how to add these fields in the screen? I did not find any exist to add fields in this screen.
I think using BADI CUSTOMER_ADD_DATA_CS I canu2019t add fields in SAPLV02Z screen no. 0200
Do I have any option with out using modification?
What are the options I have to add the fields in that subscreen?
Any ideas please? I appreciate your help on this.
Thanks.

Hi,
Can u give some more details.like how many fields you are trying to add.
SAP has given 5 fields cutomer grp1 to customer grp5. which we can use anyway.
KNVV-KVGR1 TO KNVV-KVGR5
you can use these 5 fields and descriptions anyway can be changed using CMOD project implementation
Tcode : CMOD
GOTO---Text Enhancements--Data elements----New DE cust desc
Create a modification and change the description.
this will work if you need upto 5 fields.
Regards
Anil
Edited by: Anil Kumar Palle on Mar 5, 2010 7:50 AM

Similar Messages

Subscreen field value is not transferring from ABAP program to Screen

Hi All,
I have a requirement to add a new field in a standard program subscreen( program SAPLKACB, Screen: 1006 ). This subscreen is being called from main standard program SAPMV45A.
When i see the new field value in Debug mode, some value is there. But when the subscreen is displayed value is not displayed. The value is available till end of Main program PBO. But it is displayed with no value, when the subscreen is shown.
Please let me know what could be the reason behind this. Points will be awarded for the helpful answers. It is very urgent.
Regards,
Yellappa.

Hi
did you add code to the flow lgic?
INCLUDE MV45AOZZ. " User-modules PBO
INCLUDE MV45AIZZ. " User-modules PAI
Rgds,
JP

Steps to create tabstrip for subscreen in selection screen

hi,
can let me know the steps taken to create subscreen in selection screen and put in tabstrip?
i need to have 3 screens. 1000 being the tabstrip, 2000 being first subscreen and 3000 being the second subscreen.
i have the abap code but i do not know the steps to create especially 1000 screen.
for 2000 and 3000, once i activated the program, these 2 screens added but i do not know where can i create the 1000 screen.
also, should i use wizard to create tabstrip?
please advise. thanks
SELECTION-SCREEN BEGIN OF SCREEN 2000 AS SUBSCREEN.        SELECTION-SCREEN BEGIN OF BLOCK x WITH FRAME TITLE text-001.
SELECT-OPTIONS: para1 FOR field1 ,
                              para2 FOR field2.
SELECTION-SCREEN END OF BLOCK x.
SELECTION-SCREEN END OF SCREEN 2000.
SELECTION-SCREEN BEGIN OF SCREEN 3000 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK y WITH FRAME TITLE text-002.
SELECT-OPTIONS: para3 FOR field3 ,
                              para4 FOR field4.
SELECTION-SCREEN END OF BLOCK y.
SELECTION-SCREEN:SKIP.
SELECTION-SCREEN END OF SCREEN 3000.

e_l,
See the total doc.. with example.
Assigning a Subscreen Area to a Tab Title
You must assign a subscreen area to each tab title. There are two ways of doing this:
Paging in the SAPgui
You need to assign a separate subscreen area to each tab title, and define the function codes of the tab titles with type P (local GUI function). In the screen flow logic, you call all the subscreens in the PBO event. This means that all of the tab pages reside locally on the SAPgui.
When the user chooses a tab title, paging takes place within the SAPgui. In this respect, the tabstrip control behaves like a single screen. In particular, the PAI event is not triggered when the user chooses a tab title, and no data is transported. While this improves the performance of your tabstrip control, it also has the negative effect that when the user does trigger the PAI event, all of the input checks for all of the subscreens are performed. This means that when the user is working on one tab page, the input checks may jump to an unfilled mandatory field on another page.
Local paging at the SAPgui is therefore most appropriate for screens that display data rather than for input screens.
Paging on the Application Server
One subscreen area is shared by all tab titles and called in the PBO event. You define the function codes of the individual tab titles without a special function type. When the user chooses a tab page, the PAI event is triggered, and you must include a module in your flow logic that activates the appropriate tab page and assigns the correct subscreen to the subscreen area.
Since the PAI event is triggered each time the user chooses a tab title, this method is less economical for the application server, but the input checks that are performed only affect the current tab page.
Procedure in Either Case
You create the subscreen areas within the tabstrip area. You assign the subscreen areas to one or more tab titles in the Screen Painter by selecting one or more titles. You can also assign a subscreen area to a tab title in the tab title attributes by entering the name of the subscreen area in the Reference field attribute.
The procedure for the alphanumeric Screen Painter is described under Creating Tabstrip Controls.
If you are paging at the SAPgui, create a subscreen area for each tab title. If you are paging at the application server, select all tab titles and create a single subscreen area. The subscreen areas may not cover the top line of the tab area. However, within a tab area, more than one subscreen area can overlap.
Programming the Flow Logic
In the flow logic, all you have to do by hand is include the correct subscreens. The screen flow and data transport to the ABAP program is the same as for normal subscreens. There are two ways of programming the screen flow logic, depending on how you have decided to page through the tabstrip control.
Paging in the SAPgui
When you page in the SAPgui, you must include a subscreen for each subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN: <area1> INCLUDING [<prog 1>] <dynp 1>,
                  <area2> INCLUDING [<prog 2>] <dynp 2>,
                  <area3> INCLUDING [<prog 3>] <dynp 3>,
PROCESS AFTER INPUT.
CALL SUBSCREEN: <area1>,
                  <area2>,
                  <area3>,
Paging on the Application Server
When you page on the application server, you only have to include a subscreen for the one subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN <area> INCLUDING [<prog>] <dynp>.
PROCESS AFTER INPUT.
CALL SUBSCREEN <area>.
Handling in the ABAP Program
Before you can use a tabstrip control in your ABAP program, you must create a control for each control in the declaration part of your program using the following statement:
CONTROLS <ctrl> TYPE TABSTRIP.
where <ctrl> is the name of the tabstrip area on a screen in the ABAP program. The control allows the ABAP program to work with the tabstrip control. The statement declares a structure with the name <ctrl> . The only component of this structure that you need in your program is called ACTIVETAB.
Use in the PBO event
Before the screen is displayed, you use the control to set the tab page that is currently active. To do this, assign the function code of the corresponding tab title to the component ACTIVETAB:
<ctrl>-ACTIVETAB = <fcode>.
When you page at the SAPgui, you only need to do this once before the screen is displayed. This initializes the tabstrip control. The default active tab page is the first page. After this, the page activated when the user chooses a tab title is set within SAPgui.
When you page on the application server, you must assign the active page both before the screen is displayed for the first time, and each time the user pages. At the same time, you must set the required subscreen screen.
You can suppress a tab page dynamically by setting the ACTIVE field of table SCREEN to 0 for the corresponding tab title.
Use in the PAI event
In the PAI event, ACTIVETAB contains the function code of the last active tab title on the screen.
When you page in the SAPgui, this allows you to find out the page that the user can currently see. When you page at the application server, the active tab page is controlled by the ABAP program anyway.
The OK_CODE field behaves differently according to the paging method:
Paging in the SAPgui
When you page in the SAPgui, the PAI event is not triggered when the user chooses a tab title, and the OK_CODE field is not filled. The OK_CODE field is only filled by user actions in the GUI status or when the user chooses a pushbutton either outside the tabstrip control or on one of the subscreens.
Paging on the application server
If you are paging at the application server, the PAI event is triggered when the user chooses a tab title, and the OK_CODE field is filled with the corresponding function code.
To page through the tabstrip control, you must assign the function code to the ACTIVETAB component of the control:
<ctrl>-ACTIVETAB = <ok_code>.
This statement overwrites the function code of the last active tab page with that of the new tab title. At the same time, you must ensure that the correct subscreen is inserted in the subscreen area.
Otherwise, tabstrip controls are handled like normal subscrens in ABAP programs, that is, the ABAP program of a subscreen screen must contain the dialog modules called from the flow logic of the subscreen.
Examples
Tabstrip control, paging at SAPgui
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
      SAVE_OK TYPE SY-UCOMM.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
    MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
                                  MYTABSTRIP-ACTIVETAB.
ENDIF.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The screen contains a tabstrip area called MYTABSTRIP with three tab titles PUSH1, PUSH2 and PUSH3. The function codes have the same name, and all have the function type P. One of the subscreen areas SUB1 to SUB3 is assigned to each tab title. The pushbutton has the name BUTTON and the function code OK.
In the same ABAP program, there are three subscreen screens 110 to 130. Each of these fits the subscreen area exactly. The layout is:
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN: SUB1 INCLUDING SY-REPID '0110',
                  SUB2 INCLUDING SY-REPID '0120',
                  SUB3 INCLUDING SY-REPID '0130'.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN: SUB1,
                  SUB2,
                  SUB3.
MODULE USER_COMMAND.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
When you run the program, a screen appears on which the second tab page is active, since the program sets the ACTIVETAB component of the structure MYTABSTRIP to PUSH2 before the screen is displayed. The user can page through the tabstrip control without the PAI event being triggered. One of the three subscreens is included on each tab page.
When the user chooses Continue, the PAI event is triggered, and an information message displays the function code of the tab title of the page that is currently active.
Tabstrip control with paging on the application server.
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
      SAVE_OK TYPE SY-UCOMM.
DATA NUMBER TYPE SY-DYNNR.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
NUMBER = '0120'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
    MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
                                  MYTABSTRIP-ACTIVETAB.
ELSE.
    MYTABSTRIP-ACTIVETAB = SAVE_OK.
    CASE SAVE_OK.
      WHEN 'PUSH1'.
        NUMBER = '0110'.
      WHEN 'PUSH2'.
        NUMBER = '0120'.
      WHEN 'PUSH3'.
        NUMBER = '0130'.
    ENDCASE.
ENDIF.
ENDMODULE.
The statically-defined next screen for screen 100 is itself, and its layout is the same as in the above example. However, the function codes of the three tab titles have the function type <blank> and they all share a single subscreen area SUB.
The same subscreen screens 110 to 130 are defined as in the last example.
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN SUB INCLUDING SY-REPID NUMBER.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN SUB.
MODULE USER_COMMAND.
In this example, the program includes a subscreen screen in the subscreen area SUB dynamically during the PBO event.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
This example has the same function as the previous example, but the paging within the tabstrip control is implemented on the application server. Each time the user chooses a tab title, the function code from the OK_CODE field is assigned to the ACTIVETAB component of structure MYTABSTRIP. At the same time, the variable NUMBER is filled with the screen number of the subscreen that has to be displayed in the subscreen area SUB of the tabstrip control
Pls. reward if useful

To include subscreens in a screen.

Hi ,
I have created a screen 100 , that includes a custom control , in the same screen I have created subscreen area in order to include some I/O fields...but when i try to excute this program ..i get some errors - call subscreen : yprg2 0100 no dynpro name.
yprg2 is the abap program .
Thanx.
Sunitha

Hello.
In PBO and PAI of your screen 100, you must call the subscreens, like:
*PBO
CALL SUBSCREEN sub1 INCLUDING sy-cprog dynnr.
*PAI
CALL SUBSCREEN sub1.
Where SUB1 is the subscreen defined in screen painter of screen 100, sy-cprog and dynnr have the program and subscreen number (101?).
Regards.
Valter Oliveira.

Call subscreen from main screen

Dear all,
I have a subscreen and from that subscreen i am calling another normal screen using 'call screen' statement. After doing some manipulation in the normal screen i want to go back to the subscreen on clicking 'BACK' button. i tried 'leave to screen' and 'call screen' in PAI of normal screen but it is not working. how to come back to the subscreen again?
Thanks in advance,
Aswin.

Dear Friend,
You include a subscreen screen using the CALL SUBSCREEN statement in the flow logic of the main screen.
To include a subscreen screen in the subscreen area of the main screen and call its PBO flow logic, use the following statement in the PBO event of the main screen:
This statement assigns the subscreen screen with number <dynp> to the subscreen area called <area>. With <prog> you must specify the ABAP program in which the subscreen screen is defined. If it does not find a corresponding subscreen screen, a runtime error occurs. The PBO flow logic of the subscreen screen is also included at the same point. This can call PBO modules of the ABAP program in which the subscreen screen is defined. At the end of the subscreen PBO, the global fields from the program are passed to any identically-named screen fields in the subscreen screen. The PBO flow logic of the subscreen screen can itself include further subscreens.
The name <area> of the subscreen area must be entered directly without inverted commas. You can specify the names <prog> and <dynp> either as literals or variables. If you use variables, you must declare and fill identically-named variables in the ABAP program. The screen number <dynp> must be 4 characters long. If you do not assign a subscreen screen to an area, it remains empty.
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN <area> INCLUDING <prog> <dynp>.
find the Below Example Code.
DATA: ok_code TYPE sy-ucomm,
      save_ok TYPE sy-ucomm.
DATA: number1(4) TYPE n VALUE '0110',
      number2(4) TYPE n VALUE '0130',
      field(10) TYPE c, field1(10) TYPE c, field2(10) TYPE c.
CALL SCREEN 100.
MODULE status_100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE fill_0110 OUTPUT.
field = 'Eingabe 1'(001).
ENDMODULE.
MODULE fill_0120 OUTPUT.
field = field1.
ENDMODULE.
MODULE fill_0130 OUTPUT.
field = 'Eingabe 2'(002).
ENDMODULE.
MODULE fill_0140 OUTPUT.
field = field2.
ENDMODULE.
MODULE cancel INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE save_ok INPUT.
save_ok = ok_code.
CLEAR ok_code.
ENDMODULE.
MODULE user_command_0110 INPUT.
IF save_ok = 'OK1'.
    number1 = '0120'.
    field1 = field.
    CLEAR field.
ENDIF.
ENDMODULE.
MODULE user_command_0130 INPUT.
IF save_ok = 'OK2'.
    number2 = '0140'.
    field2 = field.
    CLEAR field.
ENDIF.
ENDMODULE.
MODULE user_command_100 INPUT.
CASE save_ok.
    WHEN 'SUB1'.
      number1 = '0110'.
    WHEN 'SUB2'.
      number1 = '0120'.
      CLEAR field1.
    WHEN 'SUB3'.
      number2 = '0130'.
    WHEN 'SUB4'.
      number2 = '0140'.
      CLEAR field2.
ENDCASE.
ENDMODULE.
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE status_100.
CALL SUBSCREEN: area1 INCLUDING sy-repid number1,
                  area2 INCLUDING sy-repid number2.
PROCESS AFTER INPUT.
MODULE cancel AT EXIT-COMMAND.
MODULE save_ok.
CALL SUBSCREEN: area1,
                  area2.
MODULE user_command_100.
The screen flow logic of subscreen screens 110 and 130 is:
PROCESS BEFORE OUTPUT.
MODULE fill_0110|0130.
PROCESS AFTER INPUT.
MODULE user_command_0110|0130.
The screen flow logic of subscreen screens 120 and 140 is:
PROCESS BEFORE OUTPUT.
MODULE fill_0120|0150.
PROCESS AFTER INPUT.
When you run the program, a screen appears on which subscreens 110 and 130 are displayed. The pushbuttons on the main screen allow you to choose between two subscreen screens for each screen area. The pushbuttons on the subscreens allow you to transfer the data from subscreens 110 and 130 to subscreens 120 and 140.
Since the same field name FIELD is used on all subscreens, the identically-named ABAP field is transferred more than once in each PBO and PAI event of the main screen. For this reason, the values have to be stored in the auxiliary fields FIELD1 and FIELD2 in the ABAP program.
The pushbuttons on the subscreen screens have different function codes, and they are handled normally in an ABAP field. If the function codes had had the same names, it would again have been necessary to use auxiliary fields.

Calling the subscreen into main screen

Hi Guru's,
      I am having a main screen, which holds 2 radio buttons.
      If I select one radio button it has to call one table control, if I select 2nd radio button it has to call different table control.
      For this I have created two subscreens, each one holds a table control.
based on the selection of radio button I have to call these subscreens in to the main screen.
   Please help me how to call the subscreen into main screen.

There is no help text for this dump
Either the text was inadvertently deleted or the release of
the kernel differs from the release of the database
Refer to the Note system for further information on            this dump.
000160           %_archive TYPE arc_params,
000170         END   OF COMMON PART.
000180   *
000190   FIELD-SYMBOLS: <%_1>   %_PREDEFINED.
000200
000210   DATA: %_repid     TYPE syst-repid   %_PREDEFINED,
000220         %_viaselscr TYPE x VALUE '04' %_PREDEFINED.
000230
000240   SYSTEM-EXIT.
000250   PERFORM (sy-xform) IN PROGRAM (sy-xprog).
000260
000270   * Nach Laden des Dynpros
000280   MODULE %_ctl_init OUTPUT.
000290     %_repid = sy-repid.
000300     PERFORM %_ctl_init IN PROGRAM sapmssyd USING %_repid IF FOUND.
     >   ENDMODULE.
000320
000330   * Um DCO
000340   MODULE %_ctl_output OUTPUT.
000350     %_repid = sy-repid.
000360     PERFORM %_ctl_output IN PROGRAM sapmssyd USING %_repid IF FOUND.
000370   ENDMODULE.
000380
000390   * Um DCI
000400   MODULE %_ctl_input INPUT.
000410     %_repid = sy-repid.
000420     PERFORM %_ctl_input IN PROGRAM sapmssyd USING %_repid IF FOUND.
000430   ENDMODULE.
000440
000450   * Erstes Modul in PAI
000460   MODULE %_ctl_pai INPUT.
000470     %_repid = sy-repid.
000480     PERFORM %_ctl_pai IN PROGRAM sapmssyd USING %_repid IF FOUND.
000490   ENDMODULE.

CProjects - Adding a new field to the detail screen of object link

Hi All,
I've a requirement of adding a new field to the detail screen of object link. But the field is a combination of 3 other standard fields.
Please let me know how could i realise this functionality?
Thanks in advance.

Hi Srini,
Thanks for your Reply
I have kept 01 against the field BSEG-AUGDT and selected the preselect check box also.
But still that field is not visible in the dynamic selection screen.
Thanks
Ajay.D

How to have my dial up connection added to the network utility program?

how to have my dial up connection added to the network utility program for monitoring? though i am connected by dial-up, the connection is not monitored by the utility program. the drop down box there does not show the modem at all. ?

Huh? I don't understand what you are asking. I just pulled up the network utility and I don't see what kind of connection monitoring it does for any kind of connection? What kind of information are you looking to obtain? What problem are you interested in solving by having your question answered?

How to show subscreen in split screen

Hi all,
Basically i want to show one tree control in left pane and all relevent subscreens in right pane.
But, I am not able to create subscreen area in right pane.
How i can create sub screen area and/or subscreens in split screen control.
Thanks,
Jogdand M B

Hi Machindra,
I also faced the same kind of problem previously. Actually there is no container which can contain normal dynpro screens / subscreens / ui elements.
However you can still implement the same kind of scenario.
As you said you want to have splitted area - left area should have tree control and right area should have subscreen.
What you can do is make use of docking container (class CL_GUI_DOCKING_CONTAINER) like -
1. Create your normal dynpro screen with a subscreen area as you wanted.
2. In a PBO module write code for creating tree control in docking container, like -
DATA: <docking container object> TYPE REF TO CL_GUI_DOCKING_CONTAINER,
      <ALV grid object>          TYPE REF TO CL_GUI_ALV_GRID.
CREATE OBJECT <docking container object>
              EXPORTING repid     = repid
                        dynnr     = dynnr
                        side      = docking->dock_at_left
                        extension = 180.
CREATE OBJECT <ALV grid object>
       EXPORTING I_PARENT = <docking container object>.
CALL METHOD <ALV grid object>->SET_TABLE_FOR_FIRST_DISPLAY
     EXPORTING I_STRUCTURE_NAME = 'SFLIGHT'
     CHANGING IT_OUTTAB        = <output table>.
Regards,
Manish Joshi
I hope you know how to award points

Translation table for Program name/screen number for ECC 6.0

Hello Experts,
Do you know if there is a translation table and/or document that would list the Program Name / Screen Number for the transactions in SAP 5.0 and the equivalent Program Name / Screen Number for those same transactions in SAP 6.0?
The reason that I ask is that we our encountering errors within the TxShuttle macros we are testing that are telling us that the current screen name listed in the macro in no longer valid in the 6.0 environment.
Regards,
Atul

I thnk we dont have any such program .Try searching for a SAP Note if its a standard program.
Can u tell me the program name and screen number which is not available in ur system.

SPAM - SAPKB70016 error during phase Generation of Programs and Screens

Hi experts,
I am trying import package SAP BASIS 700 level 16, but i have still errors in phase Generation of Programs and Screens:
Program /OSP/SAPLR3_REPORT, Include /OSP/LR3_REPORTU38: Syntax error in line 000014
Type '/OSP/REP_BADI' is unknown
Program CL_HRBAS_INFTY_BL_COMPUTATION=CP, Include CL_HRBAS_INFTY_BL_COMPUTATION=CI: Syntax error in line 000005
Type 'HRBAS00INFTYBL' is unknown
Program CL_HRBAS_OBJECT_OPERATIONS====CP, Include IF_HRBAS_BUF_INTEGRATION_TO_PAIU: Syntax error in line 000007
Type 'HRBAS_PD_PA_INTEGRATION' is unknown
Program CL_HRBAS_RHOMBUFFER===========CP, Include IF_HRBAS_BUF_INTEGRATION_TO_PAIU: Syntax error in line 000007
Type 'HRBAS_PD_PA_INTEGRATION' is unknown
Program CL_PROXY_WSDL2ABAP============CP, Include CL_PROXY_WSDL2ABAP============CM03G: Syntax error in line 000004
Type 'SPRX_PROXY_NAMEPROPOSAL' is unknown
Program CL_WDR_CFG_PERSISTENCE_COMP===CP, Include CL_WDR_CFG_PERSISTENCE_COMP===CM005: Syntax error in line 000014
Transformation 'WDR_CFG_COMP_TRANSL' has no activeversion
Program CL_WSSE_PROCESSOR=============CP, Include CL_WSSE_PROCESSOR=============CM009: Syntax error in line 000131
Transformation 'SEC_SAML_ASSERTION' has no activeversion
Program SAPLPA_PACKAGE_CHECKS, Include LPA_PACKAGE_CHECKSTOP: Syntax error in line 000030
Type 'WB_PACKAGE_COMPONENT_CHECK' is unknown
System is: SAP ERP 6.0 IDES EHP3, kernel221, WIN2003, Oracle 10.2.0.4
Can you help me pls?

thank you for your help Sunny
I solved problem:
1.)
Program /OSP/SAPLR3_REPORT, Include /OSP/LR3_REPORTU38: Syntax error in
line 000014
Type '/OSP/REP_BADI' is unknown
(SE18 -> reactivated Enhancement Spot /OSP/REP_ENH_SPOT )
2.)
Program CL_HRBAS_INFTY_BL_COMPUTATION=CP, Include
CL_HRBAS_INFTY_BL_COMPUTATION=CI: Syntax error in line 000005
Type 'HRBAS00INFTYBL' is unknown
Program CL_HRBAS_OBJECT_OPERATIONS====CP, Include
IF_HRBAS_BUF_INTEGRATION_TO_PAIU: Syntax error in line 000007
Type 'HRBAS_PD_PA_INTEGRATION' is unknown
Program CL_HRBAS_RHOMBUFFER===========CP, Include
IF_HRBAS_BUF_INTEGRATION_TO_PAIU: Syntax error in line 000007
Type 'HRBAS_PD_PA_INTEGRATION' is unknown
Program CL_PROXY_WSDL2ABAP============CP, Include
CL_PROXY_WSDL2ABAP============CM03G: Syntax error in line 000004
Type 'SPRX_PROXY_NAMEPROPOSAL' is unknown
Program SAPLPA_PACKAGE_CHECKS, Include LPA_PACKAGE_CHECKSTOP: Syntax
error in line 000030
Type 'WB_PACKAGE_COMPONENT_CHECK' is unknown
(SE18 -> reactivated types)
3.)
Program CL_WDR_CFG_PERSISTENCE_COMP===CP, Include
CL_WDR_CFG_PERSISTENCE_COMP===CM005: Syntax error in line 000014
Transformation 'WDR_CFG_COMP_TRANSL' has no activeversion
CL_WDR_CFG_PERSISTENCE_COMP===CP ,
Program CL_WSSE_PROCESSOR=============CP, Include
CL_WSSE_PROCESSOR=============CM009: Syntax error in line 000131
Transformation 'SEC_SAML_ASSERTION' has no activeversion
(Tcode STRANS -> reactivated Transformations
Edited by: Miroslav Mihok on Oct 6, 2009 3:37 PM

Difference between DIALOGUE programming and SCREEN programming

Hi,
Please tell me the difference between dialogue programming and screen programming
jomon

hi
-          A transaction is dialog program that change data objects in a consistant way.
A dialog program must fulfil the following requirements
-          A user friendly user interface.
-          Format and consistancey checks for the data entered by the user.
-          Easy correction of input errors.
-          Access to data by storing it in the data bases.
screen progarmming means.dialogue programming contains.
-          Screens (Dynpros)
-          Each dialog in an SAP system is controlled by dynpros.A dynpros consists of a screen
And its flow logic and controls exactly one dialog step.
-          ABAP/4 module Pool.
     Each dynpro refers to exactly one ABAP/4 dialog program .Such a dialog program is also       called a module pool ,since it consists of interactive modules.
regads
praveen

No batch input data screen SAPLSDH4 0200

Hi,
While doing Check deposit transaction, i got the below error
" No batch input data screen SAPLSDH4 0200". When i press enter, it is going to FS01 screen and showing the customer number as * =D.xxxx (customer number)* and a dialogue box is appeared, in that search item and customer number is displayed. When i press enter, it is not accepting. When i clear it and press enter, it is showing all customers. I have selected the customer which i gave at the time of customizing and press enter. Then it is showing the "OK code" again selected ok.. Then the batch process competed. But when i go to SM35, i cant able to see the session again.
I dont understand why this problem is coming. But the posting were done properly. Can anyone explain me what exactly the problem with this transaction.
Regards
Sabera

Hi,
These error normally comes if the screen control branches out to different view or a screen.If a session is created for error logs, process the session in foreground mode and see at which point the OK CODE branches out to this particular screen. you also need to debug the particular record which is failing to see if its a data related issue or any particular field value is being wrongly processed. If your program is not creating any session for error logs i request you to generate a session for error logs or else if you are using call transaction ,run it in MODE 'A' to check whats happening.It's quite common to come accross such issues while developing a BDC.

Need help with adding the following to a program

Modify the mortgage program to display the mortgage payment amount. Then, list the loan balance and interest paid for each payment over the term of the loan. The list would scroll off the screen, but use loops to display a partial list, hesitate, and then display more of the list. Do not use a graphical user interface. Insert comments in the program to document the program.
Currently I am working on adding the following line in bold but getting error expected ";" on line 27
import java.io.*;
import java.util.Date;
import java.text.DecimalFormat;
public class Mortgage5
public static void main(String[] args)
Date currentDate = new Date(); //Date constructor
DecimalFormat decimalPlaces = new DecimalFormat("$###,###.##");
//declaring variables
final double PRINCIPLE = 200000;
final double INTEREST = .0575/12;
final double TERM = 12*30;
//declaring variables
final double MONTHLY =PRINCIPLE*(INTEREST/(1-Math.pow(1+INTEREST, -TERM)));
//displaying variables
System.out.println("\t\t" + currentDate);
System.out.println("\t\tPrinciple or Loan Amount: " + decimalPlaces.format(PRINCIPLE));
System.out.println("\t\tInterest Rate: " + (INTEREST));
System.out.println("\t\tThe Term of Loan (in months): " + (TERM));
System.out.println("\t\tThe Monthly Payment is: " + decimalPlaces.format(MONTHLY));
System.out.println("\t\tThe Balence - Your Payment is: " + decimalPlaces.format(PRINCIPLE*INTEREST*TERM)-MONTHLY));
Any suggestions??? PLEASE

Ok I figured out the issue now if someone can help me. I need to create a loop for the following:
The list would scroll off the screen, but use loops to display a partial list, hesitate, and then display more of the list.
Here is the Program so far.
import java.io.*;
import java.util.Date;
import java.text.DecimalFormat;
public class Mortgage5
public static void main(String[] args)
Date currentDate = new Date(); //Date constructor
DecimalFormat decimalPlaces = new DecimalFormat("$###,###.##");
//declaring variables
final double PRINCIPLE = 200000;
final double INTEREST = .0575/12;
final double TERM = 12*30;
//declaring variables
final double MONTHLY =PRINCIPLE*(INTEREST/(1-Math.pow(1+INTEREST, -TERM)));
final double NEWBAL = (PRINCIPLE*INTEREST*TERM) -MONTHLY;
//displaying variables
System.out.println("\t\t" + currentDate);
System.out.println("\t\tPrinciple or Loan Amount: " + decimalPlaces.format(PRINCIPLE));
System.out.println("\t\tInterest Rate: " + (INTEREST));
System.out.println("\t\tThe Term of Loan (in months): " + (TERM));
System.out.println("\t\tThe Monthly Payment is: " + decimalPlaces.format(MONTHLY));
System.out.println("\t\tThe Balence - Your Payment is: " + decimalPlaces.format(NEWBAL));
}

To call subscreen in another screen

hi
How to call a subscreen if i check certain checkbox.please help

Hi,
In screen painter(SE51) choose the subscreen tool button and draw a subscreen area on the screen,this subscreen area will be used to hold the subscreen at run time.To make a subscreen select the attribute screen type as subscreen and specify the size of the subscreen according to the size of the subscreen area in which it will be placed.
We use ABAP statement to embed and start the flow logic of the subscreen area in the PBO of a screen. A subscreen can contain another subscreen.
CALL SUBSCREEN subscreen_area INCLUDING program screen_number.
A similar call should also exist in PAI of screen.It will also call the PAI modules of the subscreen and will transfer data from subscreen to ABAP program.
CALL SUBSCREEN subscreen_area.
open T.code : ABAPDOCU
path:BC ABAP Prg ->ABAP User dialog ->Screen ->Complex screen element - >Subscreen.
You will get sample prg, Run it.You can get lot of sample prg in T.Code ABAPDOCU.
Regards,
Raj.

Adding fiels in XD01 subscreen-program SAPLV02Z screen no. 0200

Similar Messages

Maybe you are looking for