Can we add new field in standard idoc segment ?

HI all,
My requirement is to add new field in segment named E1EDL44 (Idoc named - DELVRY03).
Please guide me how to proceed.
thanks
manish

Hi Manish,
You cann't add any new fields into any of the standard segments like E1EDL44 segment.
Inorder to achieve this you need to do the following:-
Create a new segment and with the new fields and this new segment should be added as a child segment to the E1EDL44 segment. You need to write a piece of code to populate that new segment in the userexit. You should create a extension for your basic type DELVRY03. This way you can achieve this scenario.
Thanks,
Mahesh.

Similar Messages

Add new field in standard transaction

Could ou please tell me that can we add material field in standard transaction VF04 selection criteria.
if yes then how?
regards,
Amar

hi Amar,
check this thread
Re: Additional Fields in Selection Screen of VF04 - Billing Due List
it might be helpful to you.
thanks
Sachin

IDOC - add new field in in existing segment definition

Hi,
For segement type say Z1MARA1 if we need to add a new field in segement definition say Z2MARA1 SAP is not allowing to add new field if we tried to cancelled the realsed 30E it not allowing since the SAP realease which we are working is 640 so only we can create new segement defination with version Z2MARA1001 with new field added but issues is that the partner Profile for outbound parameters the Segment release in IDOc Type is 31I so if we change this segment release in IDOC type to new version ie., 640 then it will pick all the new segement associated with it due to which the the format in which we pass the segements to third party will change so is there any way to use the existing segment definition which is release 30E & add addition field to it. Only one way I found is that when i try to cancel the released message is trigger so in the debug if I make it success it allows to add new field in existing segment definition but which is wrong way of doing is there any way we can used same segment definition & add new field without adding new version & new released.
Thanks in advance.
Rajeev

Varma,
I know that we can add new segement with new version my question is existing segement definition can we add a new filed because in partner profile we specified release 31i so even we create new segement type then version will be 640 so it will not pick the latest version.
Thanks
Rajeev

Modify and add new field in standard Purchase Order script

Hi All,
I have some problem with Modify and add some new fields in Standard Purchase Order script. From ME22n transaction code it display PO detail. In item detail with condition tab all data will display in Currently PO script output.
But I want to display ME22n->Item Detail->Invoice->Taxes Data. how to display this data in standard PO script. All data are fetch from Structure like ( KOMV,KOMVD..etc) then How it can be Display?
Waiting for Replay.
Himanshu Patel.

Work with an Abaper.Tell your requirement [ addition of a field] and ask him to include this field by using the functionality " Field Exit".

Cannot Add new fields to standard QM datasource

Hi
I got this erro when I try to add new fields from LBWE.
Field ZZRFKIMG cannot be selected because of unit field VRKME -> see long text
Message no. MCEX032
Diagnosis
Field ZZRFKIMG cannot be transferred, since its unit field VRKME is either not in the communication structure, or was purposefully excluded from the selection.
Procedure
If you have chosen your own field, you must also create a user-defined unit field in the append and use it accordingly.
How can I resolve it.
thanks

Hi,
My Understanding is that if the field is available in the Pool in LBWE then no need to enhance the datasource.
In my case the field is available in LBWE though it is ZFIELD (ZZRFKLMG and ZZNETPRC).
In RSA6 I added the this unit
ZZMEINS     MEINS     UNIT                                                                           Base Unit of Measure
ZZWAERK     WAERK     CUKY                                                                           SD Document Currency
I went back to LBWE and try to add the following Zfieds (ZZRFKLMG and ZZNETPRC) and the error is same.
Now I try to add the the field directly in the append structure * ZZMC05Q02ITM* but its asking to maintain the ref table and ref field.
I added ZZMC05Q02ITM as ref table and ZZRFKLMG as ref unit and I still get errors.
I am are that if I maintain it in RSA6 then I need to write user exit in CMOD but since it is available in LBWE I want to get it from the pool.
I have tried this and there was no errors during activation
ZZRFKLMG     ZZRQE_RFKLMG     QUAN     QMFE     ZZMEINS     Notification quantity in base units
I gave the table name and Unit.
Despite adding it, I still get data even though I did not used LBWE pool.
thanks alot SUV123
Edited by: Bhat Vaidya on Oct 14, 2009 10:44 AM
Edited by: Bhat Vaidya on Oct 14, 2009 11:06 AM

How to add new field at standard report,?

Hi expert,
How do i find an easy way to add new field using this tcode s_alr_87012332 ?

Hi,
In order to add a custom fields , please chech the enhancement MM06E005.
Here, you can get includes in which you can place ur field.
Hope this helps.

Can we add new field to inventory Warehouse Report

I have to add new field name "Desc in Frgn from Item master data" to inventory Warehouse Report
How can I do that

Hello,
IN print out (PLD) yes, in SAP b1 form not possible.
Regards
János

Can we add new fields to the seeded AdvanceTable

Hi,
I wanted to add new fields like LOV's to the seeded Advance Table AccountsDistsAdv Table in the page CheckoutDistdPG. This table is associated to the View Instance PoReqDistributionsVO. I am planning to add 6 LOVs to this table. How can I take the view attributes if I add these fields to the seeded Advance Table as I can be able to take from PoReqDistributionsVO only which are not available in this case.
Can you please let me how can I do this.
Thanks,
HC

Hi
See data is coming from LOV VO that is fine. But as you want to save this data as well while navigating from this page to other and back to this page. In that case There must be a
VO based on which all columns of the advance table be based on. So you have to attach your fields with that VO then you should be able to navigate as well.
More precisely i will say that for LOV field there will be two VO one that will populate the data of LOV and second that will save the value that has been picked from the LOV.
Hope i make it clear!!!
Thanks
AJ

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

Add new field into Standard Adobe Form

Hi Expert,
I'm trying to do a very simple thing (at least that is what i think), we want to have new scenario for PCR (personnel change request). So i copy the standard interface and form (ISR_FORM_SPEG) and add some new field in that form (trough Tcode SFP). The problem is the new field that i added is not showing up any value, i tried to add address or personnel area to the form. What do i miss here? I'm relatively new to this adobe form. Thanks
Regards
Hendri

Hi,
Because I'm new at this i will assume that this problem is just as a matter of binding problem. I've copy the form and interface ISR_form_SPEG to Z.
In interface(TCode SFP) Z_ISR_IF_SPEG there is enty in import like this
position | Type | QISR_TAB_type| | |
In the Z_ISR_FORM_SPEG i drag the interface Position (from import folder) into the context on the right side of screen, in Layout tab i create ISR Text Display, and drag the position into the text display (which i believe is the binding processes). Activate it and save. But no value is displayed when running the iview on the portal (personnel change request), the form show and all label are show too but the value is not showing. Thanks

How to add new fields to standard alv report

Hi,
Tcode(VL10G) .ie.out put list will not showing one new field.I want to add one more field to output list. append the field(VIKP-SDABW) In the SHP_VL10_ITEM structure .And write the logic in the exit LV50R_VIEWG05----
>USEREXIT_PREPARE_LAYOUT_FILL.Please expain what is the process?
Why i have write the code?what logic i will write?
Thanks & Regards,
sairam

FORM ZI004_FIELDCAT_MOULD .
    wa_fieldcat-fieldname = 'ZMLDCDID' .      "Mould Code ID
    wa_fieldcat-tabname   = 'IT_MLDETAILS' .
    wa_fieldcat-outputlen = 40 .
    wa_fieldcat-seltext_l = text-010 .
    APPEND wa_fieldcat TO it_fieldcat.
    CLEAR wa_fieldcat.
    wa_fieldcat-fieldname = 'ZMLDID' .        "Mould ID
    wa_fieldcat-tabname   = 'IT_MLDETAILS' .
    wa_fieldcat-outputlen = 20 .
    wa_fieldcat-seltext_l = text-011 .
    APPEND wa_fieldcat TO it_fieldcat.
    CLEAR wa_fieldcat.
    wa_fieldcat-fieldname = 'ZMLDCODE' .      "Mould Code
    wa_fieldcat-tabname   = 'IT_MLDETAILS' .
    wa_fieldcat-outputlen = 40 .
    wa_fieldcat-seltext_l = text-012 .
    APPEND wa_fieldcat TO it_fieldcat.
    CLEAR wa_fieldcat.
endform.

How to add new fields to standard reports

hi friends,
im into ABAP and working across all modules..the basic thing is users and functional people are not satisfied with the standard reports..they need some logic change or to add some more fieldsinb the standard reports.For logic change we have to copy the standard to zprogram and can do or create a new program itself..but in many cases they ask for extra fields.how to achive it ..
for example my requirement now is adding vendor name field to the report FAGGL03 ....i found a badi and have make changes to it ...now the vendor name will be coming in sgtxt over writing the text ...but they need text also...now what shall i do???
append structure vendor name field in faglposx table ....???how to find out the final internal table from where the output is coming ????
?when we check the standard rewport codes...there are lot of include statements perform statements etc ...how to find out the final structure or internal table which has the output values..???

hi
it would be better if u giv full name of the report
if ur displaying the data in alv then search for the
word REUSE_ALV_LIST_DISPLAY REUSE_ALV_GRID_DISPLAY from which u can get the final table name
then check the data that is comming into
try using implicit enhancement or any other exit in the declaration and declare a new structure with the field and append it to the field catalog
if ur displaying the data using write statement
then create a zprogram and add a write statement
fi ur unable to find here the final table then after displayign the report start the debugging and double click on any row to find out more easily
shiva

How can we add new fields in item customer detail B tab in VA01/VA02/VA03?

Hi all,
Anyone can suggest me, how we can add fields in item detail B tab of VA01/VA02/VA03 transaction.
1) How we can find the screen no and how we can add fileds in it
2) where we have to write the logic for these fields ( I mean in which include)
3) Is there any user exit or BADI for this
4) what is the procedure to do this enhancement .
5) How we can enhance menu bar
i am using ECC 6.0 version.
Please guide me in this .
Thanks in advance.

Hi,
You do not have to do extra coding for this. Just append the extra fields in the table VBAP and include these in the screen 8459 (Additional data A) or 8460 (Additional data B) of program SAPMV45A.
https://forums.sdn.sap.com/click.jspa?searchID=12244867&messageID=1939475
Regards
Kiran Sure

Can we add new field to existing Sales Analysis by Item report?

I would like to add sum total weight of all the items sold so far to the above system report?
How could i do that please?
Thanks.

You need to have your own report. This system report is hard coded. You do not have option to add fields there.
Thanks,
Gordon

Add new field in OAF Page.

I want to personalize a OAF page. My question is, Can i add new field in OAF page linked with database field and some calculations.
I am trying to add new field in Termination page of Self service HR which will show the hiredate of employee and number of year served.

Hi,
As already specified by Kali..
Step 1 - Create a new Field of type MessageStyledText using Personalization Link.
Step 2 - Set the corresponding VO Attribute, which will fetch Hire Date.
Step 3 - Extend the CO and calculate the Served Year, using Java Code.
Step 4- Set the same value over the bean manually.
Regards,
Gyan

Can we add new field in standard idoc segment ?

Similar Messages

Maybe you are looking for