Field Description inside the Segment structure

Hi All,
I have some customized segments and when I see in the WE31 transaction, I am able to find only field names with data element and length. But I need descriptions of each field.
Please let me know how to find the descriptions of the fields located inside a Segment.
Thanks in Advance,
Ramana

One way is to copy the Dataelement from the table control and put them into DD04T table for the description of that field.
Regards,
Naimesh Patel

Similar Messages

Change the field description in the query report

Dear All,
I have created a querry using SQVI,It is working fine Now i want to change the field description in the querry report,Please suggest on this.

Hi,
follow below steps
SQVI -> Enter Report name -> Change -> click on layout mode - > Expand tables - > double click on filed names - >
coming right side you are able see list of output fields .
Just double click on the field then going to the editable mode Description.
Thanks
Balakrishna

Issue with the new COPA field added into the BBSEG Structure

Hello All,
I have an issue with the new COPA field added into the BBSEG Structure.
I think its added becuase of test Operationa Conern Created by somebody.
Can you please let me know how to remove that structure from BBSEG Structure.
Thanks
vsr

Hi Monohar & Ankur,
Thanks for your answers..
main issue is suddenly new field called RKE_COPA_KOSTL has been added to the BBESG Structure..
Because of this RFBIBL00 Upload is not working. I heard that this new fields will come by generating Operating Concerns by Transaction KEA0.I found an operating concern which was created as a test in developemt system..
But I am not sure how to delete that operating concern.Even i am not sure if we delete the Operating Concern ..is it going to delete that field in BBESG Structure or not??
Please advise me..
Thanks
sathi

Want to download the segment structure into xsd or wsdl

Hi Guys,
I want to dwonload the segement structure (E1KNA1M) into XSD or WSDL.
Then i can import into XI as datatype,
How can i download the segment structure into XSD?
Thanks
Srinivas

Srinivas,
I tried to put the E1KNA1M segment xsd here. But it seems I cannot do because the length of it is more than 15000 characters. So I just send a mail this xsd. Take a look and update here.
What I did basically is copied the DEBMAS.DEBMAS04 xsd into altova xml spy and manually deleted all the segments except E1KNA1M segement. You can change the name of the segment names also if you want.
Regards,
---Satish

Populating the field description on the screen

Hi Group,
In the program after executing on the screen I have 3 screen fields. After entering the two fields when user hit the enter it needs to retrieve third field value from the table and have to display on the screen,and again I will click execute button the program needs to run.
But after entering the two fields and hitting the enter program executing and the third field value getting populated after the execution.
I am using the following code:
here in this P_scen and p_fid filed I am entering on the screen and after hitting the Enter I need to populate
p_des before doing the execution.
AT SELECTION-SCREEN on block selblock.
*Fetch the the database table
PERFORM retrieve_table tables    it_des
                          using     p_scen
                                    p_fid
if sy-subrc <> 0.
    MESSAGE 'Not found'.
endif.
* Pass the description of the scenario.
p_des = it-desc.

Check the FM DYNP_VALUES_UPDATE:
    ws_dyname   = 'ZSRO_MASTER_DATA'.
    ws_dynumb   = '1000'.
    ws_dynpfld-fieldname ='PPDESC'.
    ws_dynpfld-fieldvalue = ty_aa-name_textc.
    APPEND ws_dynpfld TO i_dnpfld.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = ws_dyname
        dynumb               = ws_dynumb
      TABLES
        dynpfields           = i_dnpfld
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.

Field Descriptions in the IDT

Hello,
Is there a way to get the field description in IDT 4.1? Currently my universe is incorporated with SAP ECC tables like MARA,MARC etc from the SQL.
But the fields like MATNR,MMSTA does not come up with the description. The user is writing a WEBi report on top of this universe but having hard time in pulling the fields into report, because its coming up with technical name only not with descrption.
Any help would be great.
thanks,
Vinay

Then you can change names of target fields in query transform in data Services.
OR
You can add field description in IDT.
So when user move mouse on that fields in query browser of webi report ,he can view field decription.

??? DESCRIPTION OF THE "ChannelReadPort" STRUCTURE ???

Hi,
would someone tell me where to get the definition of the "ChannelReadPort" structure from?
I am writing a Photoshop Plug-in, that should read image lines from an image opened in Photoshop. I want to use the "ReadPixelsProc" function. The first argument of this function is a "ChannelReadPort" variable. I can't find anything about this structure, neither in the docs nor in the header files of the SDK...
Or there is another function to get the pixels of an image opened in Photoshop?
Can somebody help me?
Thanks.
Chavdar

You must have a really old SDK. It is defined in PIGeneral.h

Loading images inside the package structure

i am having trouble loading images that are imbedded into the package structure. I am assuming this is possible(99.9% sure)
the classes are
cardgameframework/CardGame.class
cardgameframework/cardsupport/Card.class
cardgameframework/cardsupport/images/2D.GIF
cardgameframework/cardsupport/images/2C.GIF
how do i load 2D.gif and 2C.gif from CardGame
i tried
Image i = Toolkit.getDefaultToolkit.getImage(
"/cardgameframe/cardsupport/images/2C.GIF");
and
Image i = Toolkit.getDefaultToolkit.getImage(getClass().getResource(
"/cardgameframe/cardsupport/images/2C.GIF"));
but neither of these seem 2 work
any help would be appreciated

My initial thought is that you've got the package wrong in your two examples - you've got cardgameframe and not cardgameframework.
Anyway, I tend to use the latter of your approaches - getClass().getResource("/cardgameframework/cardsupport/images/2D.GIF").
Be careful of case in your URLs.
Note that if getResource can't find your file it will return null - ensure that you're getting back a non-null URL:
URL url = getClass().getResource("/cardgameframework/cardsupport/images/2D.GIF");
System.out.println("URL: " + url);
...If your URL is non-null then the problem will be with the format of your image file (if it is null then you'll get a NullPointerException eventually).
Hope this helps.

Field description in the material master record

Hello
Our customer is requiring having 75 characters for the field MAKT-MAKTX instead of 40 as standard SAP. Is it possible to extend the length of this field up to 75 characters without any impact in SAP? Is there any way to go around this requirement without having a big impact in standard SAP?

Hi
I think you have raised the question in the wrong thread. Raise it here :
/community [original link is broken]
Vijay

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

Field descriptions not showing in page layout

I have custom content types with custom fields. The field types vary - text, image, user and so forth. I am building an intranet so this is a publishing site with workflow and I am using custom page layouts with a custom master page.
The issue I have is that the field controls, whilst all having descriptions, rarely show the description in the custom page layout. They are all shown correctly in EditForm.aspx so I know that they are there. However when editing a page using a custom page
layout it seems that only UserField types show the description. Below is an extract from a page layout:
<SharePointWebControls:UserField FieldName="ContentOwner" runat="server"></SharePointWebControls:UserField>
<SharePointWebControls:TextField FieldName="ContentOwnerRemark" runat="server"></SharePointWebControls:TextField>
The first field ContentOwner shows the field description. The second does not. I have tried deleting and re-adding, making fields mandatory and optional, but to no avail. If it's not a UserField it doesn't show the description.

Showing names of Site Columns on a Page Layout
Thanks. That allows me to do this:
<SharePointWebControls:FieldProperty FieldName="ContentOwnerRemark" PropertyName="Description" runat="server" />
However the original question is why is it that the OOTB control only displays the description for UserField and not for other types of field in a custom page layout, whereas it shows all descriptions in EditForm.aspx. I could do what you have suggested but
it's a lot of work as I have many fields and custom page layouts, and it seems to me that having the OOTB field control on the page should display the description for all field types not just user field types.

Two source fields in one target idoc structure

Hi Experts!
I have a problem.
I have a flat file with two fields desc1 and desc2. They have to be put into the field MAKTX of the table structure E1MAKTM. But not via concat or useOneAsMandy!
I need a new E1MAKTM structure for each desc1 and desc2 . So that i get following target structure:
<recordset>
-E1MAKTM
- MAKTX = "content of desc1"
-E1MAKTM
- MAKTX = "content of desc2"
</recordset>
I hope you understand what I am trying to do.
How can i solve this problem?
Thanks for your answers in advance.

Hi,
>>Is there a possibility to dynamically duplicate the structures?
>>So that i get automatically a duplicated target structure for each content filled source field?
The solution that has give above would only do this.
Even though you are duplicating the segement in the design time, you are mapping the desc1 and desc2 to the E1MAKTM root node(for MAKTX).
During the runtime the node E1MAKTM will only be generated based on the number of occurance of the desc1 and desc2 in the source message.
For example if there are 2 desc1 and 1 desc2 field then 3 E1MAKTM node will be generated.
But make sure that the occurance of E1MAKTM is 0 to unbounded to achieve this.
Thanks
SaNv...

Field description changes not showing on one client only

Hello!
I have a network with several clients all running SAP. I have modified lots of field descriptions (by pressing CTRL double click on the field).
This is great - except I have one PC where the field descriptions show the original text, rather than my updated descriptions. This happens even when other SAP users login to this PC.
Can you explain why one PC is not showing the modified field descriptions?
Thank you
Omam-B

What do you mean? I have restarted the PC and reinstalled SAP.
What else is there to restart?
Thanks

Event structure inside a case structure

Hi,
I've got a problem w/ my porgram, and managed to boil it down to this
simple example. The program basically hangs if you change the
Numeric value when the boolean is false. I don't understand
why. I suspect it has to do with the way event structures are
treated, but if someone cou please explain this I'd be greatful.
Also, now imagine I have 7 numeric controls, handled by 7 cases in that
event structure, and I actually want to do things in response to the
value change for each. Can someone suggest an elegant way to do
that? I thought what I had here was a good design, but apparently
not.
Bjorn
(I'm using labview 7.1)
Attachments:
EventInCase.vi ‏24 KB

It is generally a bad idea to place event structures into cases. Events structures need to be able to breathe.
Maybe you can redesign your program and place the case structure inside the event structure, for example? (Also have a look at the online help for the event structure, especially the link "caveats and recommendations for using events ".)
Detailed analysis:
Your event case for the numeric is set to "lock front panel until event completes". If you change the numeric while the case is false, the evet structure cannot execute, so the front panel locks forever. The observed behavior is as expected. All clear?
In addition, if the case is false, the main loop spins at nearly infinite rate, consuming all available CPU. Place a small wait to be more cosiderate to everything else running on your rig.
LabVIEW Champion . Do more with less code and in less time .

Field description of HRP5104

Anybody know where is the description(text) of the field description in the table hrp5104? is additional formation i think.
thanks

Hi,
From the Data element you can get the description for the field or use F1 for help
Regards
Ramakrishna Pathi

Field Description inside the Segment structure

Similar Messages

Maybe you are looking for