Adding Fileds to Standard Dialog programme

Hi All,
Issue related to Transaction F-28(Post Incoming Payments):
I was added two new fields in a standard program SAPMF05A screen 301, I set the attributes and settings as Input enable fileds but I am not able to input into this new fields which are display mode only.
Can any one please clarify my issue, Is there any source code required to enable the fields to input a value.
Or Any other settings required.
Please let me know ASAP.
Thanks in advance.
Message was edited by: Lakshmi b

Hello Lakshmi
That is exactly what I meant:
LOOP AT SCREEN.
IF ( screen-group1 = ... ).
screen-input = 0.
ENDIF.
MODIFY SCREEN.
ENDLOOP.
I am sure you will find coding like this somewhere in your screen.
Regards
Uwe

Similar Messages

Is it possible Without EEWB Adding filed to standard tab.

Hi Experts!
Without EEWB and enhancing Screen Is it Possible to adding filed to standard tab. Any body can help out in this.
<b>
URGENT</b>
Thanks
vikram.c

Hi
Copy sandard table to Ztable then make it change mode . Then add new field...
Thanks
Sasmita

Standard Dialog to select manager name

Hi,
I am new to Adobe forms. My requirement is to activate already existing standard dialog to choose the manager name as a signee that will appear in the form. The form is a standard T1 form. Form name is HR_RU_T1.
Please let me know.
Thanks,
Sri

HI,
check this program.
<b>
report ZTEST2.
data: file type string,
       path type string,
       file_path type string.
data: itab type standard table of cskt.
start-of-selection.
SELECT * FROM cskt INTO TABLE itab.
call method cl_gui_frontend_services=>file_save_dialog
      exporting
                FILE_FILTER = '*.PDF'
      changing FILENAME = file
               path     = path
               fullpath = file_path.
check not file_path is initial.
call method cl_gui_frontend_services=>gui_download
    exporting    filename                = file_Path
                  WRITE_FIELD_SEPARATOR = 'X'
     changing    data_tab                = itab.
</b>
REgards,

Hi adding code in standard prog

hi
i am adding code in standard program J_1IEWT_CERT. in that there is include
J_1IEWT_CERT_F01.
there is standard prog internal table printtab.
i am trying to pass printtab data into wa_printtab, but it not going into wa_printtab.
i writing following code:
loop at PRINTTAB into itab_printtab.
move ITAB_BKTXT-BKTXT to itab_PRINTTAB-cheque_no.
modify printtab from itab_printtab index 1.
endloop.
first data is not going into itab_printtab by loop syntax and it is not modifying as well.
pl help me as soon as possible.
thanx
rocky

Hi,
try this its working for me.
REPORT ZKEERTHITEST.
tables: mara.
DATA: BEGIN OF IT_MARA occurs 0,
        MATNR TYPE MARA-MATNR,
        ERSDA TYPE MARA-ERSDA,
        ERNAM TYPE MARA-ERNAM,
        MTART TYPE MARA-MTART,
      END OF IT_MARA.
data: wa_mara like line of it_mara.
select matnr ersda ernam into corresponding
fields of table it_mara up to 5 rows from mara.
loop at it_mara into wa_mara.
wa_mara-mtart = 'FERT'.
modify it_mara from wa_mara index 1.
endloop.
regards,
keerthi

Adding fileds to va01 transaction

Can any one tell me how to add fields to standard transaction VA01,
steps are
1) after entering order no in va01,goto---heaaderpurch order data> here i have
to add 2 fields in the space below.
2) far right side another tabstrip is there-----> Additional B -
here i have to add
fields,
points will be awarded,
Reddy

Hi,
Here is the step by step process of implementing Screen exit.
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
the tcode is cmod...
1.From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
2.Choose Edit component.
3.Choose the screen exit and double click on it
4.Create your subscreen using the Screen Painter.
5.Design your screen to be added to the standard screen and activate the particular screen and return back to the flow logic .
6.Choose the PAI and PBO to write down the logic.
7.Generate your screen and choose Back (the green arrow) to return to the Project management transaction.
8.Go to the transaction ME22 to view the customer defined screen exit.
9.Enter the purchase order number and press Enter.
10.Go to the menu header --> Details.
11.Purchase number is visible on the standard screen
Regards

Fronting standard dialogs

My custom dialogs (derived from JDialog) have a window listener which overrides the windowActivated and windowDeactivated methods. These methods call toFront, and my dialog always stays on top of its owner.
My problem is how to do something similar with standard dialogs. I often call JOptionPane.showMessageDialog and JColorChooser.showDialog, and they work great, except that they are not fronted when their owners are fronted. These dialogs don't have an addWindowListener method like JDialog, so I can't solve my problem like I do with my custom dialogs. I hope you can give me a hint on how to keep standard dialos fronted.
Thanks.

demo:
import java.awt.*;
import javax.swing.*;
public class MyApplet extends JApplet {
    public void init() {
        JTextArea area = new JTextArea();
        for(Component comp = this; comp != null; comp = comp.getParent()) {
            for(Class cls = comp.getClass(); cls != null; cls=cls.getSuperclass()) {
                area.append(cls.toString());
                if (cls.getSuperclass() != null)
                    area.append(" --> ");
            area.append("\n");
        getContentPane().add(new JScrollPane(area));
}

Standard Dialog module RH_INFOTYP_1001 missing in E-Recruiting

Hi Friends,
We have e-Recruitment on a seperate server and connected it to HR using ALE. The object transfer "O(Organizational Unit)" shows error during PFAL transfer from HR to e-Recruiting.
The problem is the standard dialog module "RH_INFOTYP_1001" does not exist when checked in SE35. When checked from PPCI also, it shows "Dialog module RH_INFOTYP_1001 does not exist".
The table T777D, however, has dialog module entry for Infotype 1001 but the Dialog module name is RH_INFOTYP_S001 which exists.
1. What needs to be done to load the dialog module RH_INFOTYP_1001 in
    the e-Recruitment server ???
2. Also, we have the folowing packages installed on our e-Rec server:
   SAP_OCS(SPAM/SAINT Update)
   SAP_ABA, SAP_BASIS, PI_BASIS, SAP_BW, ERECRUIT
   Do we also need to apply EA-HR and SAP_HR packages ?? Why ??
Please advice.
Thanks,
Shashank Shirali

Well,
have you activated the E-Recruiting ALE Inbound processing?
Take a look at IMG:
SAP E-Recruiting->Technical settings -> SAP ERP Central Component integration -> Sofware running on different systems -> ALE Inbound Processing
You need to activated BADI Implementations HRALE00SPLIT_INBOUND of BADI HR_INB_PROCESS_IDOC and HRALE00INBOUND_IDOC of BADI HRRCF00_DELETE_SPREL.
This is needed because PA infotypes are not existing and the PD-Object P is just defined as external object.

Without EEWB Is it Possible to adding field to standard tab.

Hi Experts!
Without EEWB and enhancing Screen Is it Possible to adding field to standard tab. Any body can help out in this.
URGENT
Thanks
vikram.c

Yes it is possible, but we are talking a modification of SAP standard here. Also the effort needed will be at least 10 times higher than using EEWB as you have to reprogram all generated code / screen helps that SAP provides. Moreover these fields are then still not exchanged with the interfaces / BDocs etc which will be also some more days of work. There is no usable documentation on this - at least not by SAP and I am not aware of another one. It is much easier to create an EEWB enhancement and then move the fields from one tab to another.
Doing this all by hand is like adding a second processor to an existing motherboard for more performance compared to exchanging the existing one with one of higher specifications.This is possible, but requires a) more work/time/material b) more experience c) you lose warranty d) in the end you do not know for sure what the outcome will be
Regards, Kai

Adding fields 2 standard payment list program (RFZALI20) in F110 t-code

hi frnds,
it is a standard progrm using the logical database pfy. to retrive data.
i have to add 5 more fileds along with footer approved by and page break(shown below) to the output list.
please help me with ur inputs.
Header Data:
*Note:
Keep the header data same as standard payment list.
Summary Data:
*Note:
Following fields are only those needs to be added in customized program. For the rest, please refer to the standard program
·     Vendor Chinese Name
·     Check/TT No.
·     PO No.
·     Purchasing Group
·     Reference
·     Due Date
Footer Data:
*Note:
The Footer Data need to be display at the bottom of each page:
·     Review By
·     Prepared By:
Breaking:
·     Page break when information overflow
ZH Name     C     20     As standard     As standard     ADRC- NAME1NAME2     Display vendor Chinese name:Select NAME1NAME2 from ADRCWHERE ADRC-ADDRNUMBER=REGUH- ADRNRAND ADRC-NATION = CIf no data can be retrieved, leave the field as blank.Wrap if the name exceed the limit. Insert the field under Vendor English Name in payment list.Refer to the attached for layout, Highlighted is place should be inserted to :
Check/TT No.     C     8     As standard     As standard     PAYR-CHECT     Display Check/TT number of this payment documentSelect CHECT from PAYRWhere PAYR-LAUFD = REGUH-LAUFDAnd PAYR-LAUFI= REGUH-LAUFIAnd PAYR-VBLNR= REGUH-VBLNR which is displayed in current payment listInsert the field in header line 1 of layout pop-up.
PO No.     C     10     As standard     As standard     BSEG-EBELN     Display the PO number of invoice documentSelect EBELN from BSEG Where BSEG-BELNR=REGUP-BELNRBSEG-GJAHR=REGUP-GJAHRAnd BSEG-BUZEI= REGUP-BUZEIInsert the field in position line 1 of layout pop-up.
Purchasing Group     C     4     As standard     As standard     EKKO-EKGRP     Display purchasing group in order to identify the buyer in charge of related POSelect EKKO-EKGRP from EKKO where EKKO-EBELN =BSEG-EBELN Where BSEG-BELNR=REGUP-BELNRBSEG-GJAHR=REGUP-GJAHR And BSEG-BUZEI= REGUP-BUZEIInsert the field in position line 1 of layout pop-up.
Reference     C     10     As standard     As standard     BKPF-XBLNR     Display physical invoice number of each invoice document in SAPSelect XBLNR from BKPF Where BKPF-BELNR=REGUP-BELNRBKPF-GJAHR=REGUP-GJAHRInsert the field in position line 1 of layout pop-up.
Due Date     C     10     As standard     As standard     Calculated     Display due date for the invoice document.Refer to the calculated logic of the field RFPOSXEXT-FAEDT in program SAPLKKBL (T-Code:FBL1N)Insert the field in position line 1 of layout pop-up.

Hi Sridhar,
Please can you help me. I got the same problem to add the fields to the Payment run Program (RFZALI20). Can You please suggest me how can i solve this problem. I need to add LIFNR, XBLNR & EBELN fields from REGUP table.
Can you please help me ASAP.
Thanks & Regards
Rajendra
Message was edited by:
        Rajendra Prasad

Adding Field in standard Table control in crmd_order (standard order)

Hello All,
I want to add a Field in standard table control in Crmd_order - standard order general tab. Please Let me know it is Possible to add, if Possible Let me know how to achieve this Functionality.
Thanks,
Feroz.

hi,
If you don't want to access key...then only option is ,you have to search USER Exit or BADi (Try using BADI ME_GUI_PO_CUST) for me22n transaction......to adding the field.
Regards
Gaurav

Adding field in standard IDOC Segment E1EDL24

Hello Friends,
I have an urgent requirement that I have to extend IDOC segment E1EDL24 with two fields PABNR and LFSNR.
When I tries to change the segment in WE31, it shows an error message that you can only modify the segments of customer namespace and cannot modify Standard IDOC Segments.
Can we modify the standard IDOC segments, and if yes, how can we modify the standard IDOC segments. Please clarify.
Points will be rewarded generously.
Regards,
Navin

Hi Naveen,
We cannot Modify the Standard segments. But we have to Create a new Segment and Add these fields.
Then Create an Extended Idoc type
Implement User Exits in Outbound And Inbound ..
This is the Complete Steps and Info on this...with an Example...
Enhancing ALE
For example, if in an outbound interface you find that the IDOC type does not contain all the data you need to pass to the other system, you can extend the IDOC to accommodate the additional fields and enhance the ALE function modules to populate the fields. Similarly, if in an inbound interface, there is additional data that needs to be posted to the R/3 application, you can extend the IDOC type to have additional fields populated by the external system or translator or the other R/3 system and then enhance the inbound ALE function modules to post the additional data to the R/3 application.
let us use the SAP Customer Master application as an example. Specifically, letâs focus on the IDOC extension and ALE function module enhancement of IDOC type DEBMAS02 and message type DEBMAS (Customer Master) and the IDOC reduction of message type MATMAS.
IDOC EXTENSIONS
Letâs first look at the concept of IDOC extension. SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type.
Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
Determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Error handling is a very important consideration when making enhancements to inbound ALE/EDI objects. In ALE and EDI inbound processing, workflow is used for handling errors at different levels such as technical and application. If workflow has been configured for the interface, the error messages and workflow items flow to the inbox of the named recipient(s).
It is also critical to enhance the workflow that handles notifications of the inbound ALE/EDI process. In most scenarios this is not a very difficult task because SAP lets you influence the workflow parameters and messages in function exits (customer functions). You typically do this using flags and message codes to trigger certain workflow actions. If you conform to the status codes and flags stipulated for workflow processing, the enhancement could be error-free and seamless. In the case of an inbound IDOC with an extension, you should populate the EDIDC fields IDOCTYP (new IDOC type) and CIMTYP (extension type) accordingly.
Reward if Helpful

Adding image to standard ESS application

Hi all,
We have a requirement to add a help link that opens up an image in the standard bank info application in ESS.
Is this possible?
If yes, how do we go about adding the image through NWDS?
We did some settings in NWDS to get the image, but it does not open in the portal.
Also, we dont see a component path on expanding component in src--->mimes.
TIA!

Hi,
Try using the IFrame UI element which can display any 3rd party content on click of a button or Link to action. Place the picture in the src/mimes folder of ur project.
Try creating ur own package for storing the photo under the src/mimes folder
Regards,
Poojith MV

How to get the Newly added fileds from Oracle to BW

Hi ,
We have created the view in the DB side and extracted the data to BW side. After that in the DB side they have added new filed. I want to extract the data for that filed also. But that filed is not displaying in the data source itself. We have deleted the sources system assignment to that particular info source and generated the data source in the source system side, and then also I an unable to get the newly added filed in the data source. We are extracting the data from the ORACLE data base. Please let me know the steps how to get the newly added filed in the data source.
Thanks,
Visu

Hi Yadav,
yes i have alreday created the info objects in the BW side. In the Oracle DB i can see the fileds in the data sources. Newly added filed is not displaying where as previous all fileds are displaying in the oracle DBside.
Thanks,
Visu

Adding Columns in Standard Report RWBE

hi ,
could u please tell me what are the guidelines we have to follow while adding fields to the standard report RWBE. I am looking into Enhancement spot for it, or is there any method to do it.
Regards
Ali

Hi Ali,
In order to add fields to the report RWBE you can use this exit: COOPA003.
Regards,
Quddus.

Adding button in standard screen

Hi,
I need to add a button in va01 t.code(Sales order)..When we click that button means it want to open a customized screen.How to add a customized screen in standard t.code..
I am new to this exits.Can anyone help me how to do this.

Hi Mahesh,
For finding any exit for a standard t-code follow this way,
1) Goto that screen where you need to add button( here VA01)
2) Click System->Status
3) There Double click the 'GUI Status' for that screen.
In VA01 main screen it is A0. So double click that A0
4) In the Application toolbar there is one exit for adding a button after the Copy button.
You can insert your button details and give the Function code. Then in the user exit you can capture that function code and process accordingly.
Though seems easy do it carefully with modification assistant on.
Cheers,
Kothand

Adding Fileds to Standard Dialog programme

Similar Messages

Maybe you are looking for