Lost Append structure on adding standard field in exctractor 2LIS_13_VDITM

Hi,
In 2LIS_13_VDITM i have appended structure. Now i required to pull in another standard field from from the extractor from LBWE maintenance.
One doing that and activating ii somehow lost the custom appended structure from the extract structure.
I came to know this while replicating it into BW where it gave error about missing fields from the extractors.
Have anyone faced similar issue. If yes can you please let me know why this happened and how can i get those fields back in to the structure.
One way i know is by comparing it with the Q system i can manually append that structure again.
Please let me know.
Thanks a lot for responding.
Ritesh

Hello Ritesh,
Are you adding the new field through append structure of the existing one or new one (Only one append structure is possible).
If in the same append structure , then check whether that structure is active and consistent.
If everything is ok, then check the hide option in the datasource (RSA6) whether its unchecked.
Hope it helps
Thanks
Chandran

Similar Messages

Adding standard field (CTNUM) in screen in pa30

Hi Experts,
How to add standard field in PA30 transaction.
Regards
Subhaskar
Moderator message: please do more research before asking, show what you have done yourself when asking.
Edited by: Thomas Zloch on Nov 1, 2011 10:38 AM

Hello,
Can you please tell me how I can creat a custom field for CTNUM and show it like the standard one?
I'm not a progremmer, so I must manage this via standard basis.
I've tryed to add some custom fields for IT 0016 in PM01 but something is missing.
After I add to the IT 0016 a custom field, I get the message:
"Changing PS Struct. without generating code can lead to inconsistencies
Message no. PG455
Diagnosis
If the PS structure is changed by adding, deleting, or changing fields, then
this change must also be reflected in the associated screen structure. As the PS
structure is not included here, but rather is copied, the screen structure must
be edited accordingly.
Procedure
If you have not yet made any changes to the screen structure, simply choose
"Generate Code". The screen structure is then deleted and created again as a
copy of the new PS structure. The other objects of the infotype remain
unchanged.
If the screen structure no longer corresponds to the (relevant part of the)
PS structure, perhaps because you have included new fields, you must modify the
screen structure manually on the "Screen Structure" tab page using "Edit".
If I go to "Generate Object" I reach to "BADi Builder" screen:
Tranzaction : SE19
Program : SAPLSEXO
Enhancement Spot : HRPAD00INFTYBL
And from here I don't know what to do.
Can someone please help me?
Thank you!
Daniela

Appending DS with a standard field from another DS

Hi
I am appending a standard field( 0catcode_ud) from QM datasource to 2LIS_03_BF.Hence i created a ZZcatcode_ud field and appended to the MC03BFO Structure.Got to write an exit code to populate the zzcatcode field in BF datasource.Now my query is whether my standard field (0catcode_ud) in QM will get populated as well or not??Because i need to execute reports on the standard QM cube aswell.
manythanks

Hi Arun,
Your standard field will not be populated in BF extractor because you have appended ZZcatcode_ud to your extract structure.I think it will not disturb the standard flow of QM Cube.You can generate reports on QM Cube.
Regards
Karthik

Adding Standard field in SC POWL result in SRM 7.0

Hello Experts,
We have Upgraded the system from SRM 4.0 to 7.0. Here, we have a requirement to add a standard field(BE_OBJECT_ID = PO Number) to the SC POWL result list. I know to procedure to do for Custom fields.
Could any one of you help me in this.
Thanks in Advance,
Vishnu Reddy

Hi! To add columns to POWL result, you can accesthe path below in SPRO:
SAP SRM
-> SRM server
-> Cross-Application Basic Settings
-> POWL and Advanced Search
-> Adjust POWL Layout, Search Criteria and Pushbuttons
After this, select the POWL (Feeder Type). For SC, you can use SAPSRM_FEEDER_SC, for example.
Then click on Field Catalog (right menu). Set a value in the Position column for the field you need to add.
I hope this helps.
Best regards,
Christian Zeuch

Update field of an Append Structure

Hi! I need help!!
I made an extension using Append Structure (I Added a owner field) of a standart table ( EBAN ) about "purchase requisition".
I want to update this field when a new purcahse requisitions is created , using the bapi BAPI_REQUISITION_CREATE.
anynone kown how to do it?

hi Ariel,
use BAdI <b>ME_PROCESS_REQ_CUST</b> and choose appropriate method
to polulate the structure (BAPIPAREX) with the newly updated field, before PR is updated.
Hope this helps,
Sajan Joseph.

Error when adding append structure

Hi All,
I need help. We have a "new" source system (GRC), but all the required config was put in place by the BASIS team.
The required datasource was activated and tested - all working 100%.
As soon as an append structure is added, no matter what the fields within the append are, we get the following error:
unsupported field type 'P', correct DataSource definition
The structure that the datasource is based on has enhancement category = Can be enhanced(Char and numeric).
Any ideas would be greatly appreciated as this is rather urgent.
Thanks
Werner

Hi,
Field names/types etc...in the append structure makes no difference. We have tried CHAR and NUMC - all gives the same error.
If you use a different field, with different specifications, then the exact same error appears with the new field.
This leads us to believe that there might be a setting somewhere that needs to be maintained to allow append structures to GRC datasources.

Append structures - key field?

Hi guys.
Can a field from an append structure be part of the key fields?
Regards.
wm

Hi
No it's not possible because append structures are added to the bottom of the table I mean to the last row of the table.
Customizing Includes in an table is used to add the custom fields to the existing table. this include can be added any where in the table fields ie at the starting or middle or at the bottom.
Regards
Murali Papana

Adding form fields breaks tag structure

I have been teaching workshops at my university on creating accessible PDF forms from MS Word. I am very familiar with PDF accessibility. For the most part, the process of field recognition, marking up tables, writing tooltips, manipulating the tag tree, etc., all goes smoothly. I have noticed something that is creating a lot more work for our people, however.
After adding forms to the tagged PDF using recognition and the Tools > Forms > Add New Field tool, we adjust the field tab order and add tooltips. Once all of that is in place and we are ready to fine tune, we click the Tools > Accessibility > Add Form Fields to Tags button. Adding Form Fields to Tags does not work consistently if you edit the tag structure manually while in the Forms creation process. You can do some tag remediation prior to entering the Forms tool, but if you edit the tag structure while in Forms, the Adding Form Fields to Tags often does nothing -- this is certainly a bug in Acrobat X but it is not hard to work around.
The larger problem is that after we click Add Form Fields to Tags button, the tag structure reveals itself to be very much distorted and extreme amounts of tag structure remediation is required. Here are three screen shots that illustrate the point.
This first image shows the on-screen appearance.
Below is the expanded tags tree, prior to adding fields to the tag structure:
The tag structure is clean and elegant. If I were to publish this, no remediation would be necessary.
And here is the tag structure after adding form fields:
What has happened is Acrobat has grabbed recognized form fields and other elements in the document and has jammed them into the tag structure. Other things are affected as well. For example, headings in the page have extra, redundant textruns in them.
This has radically negatively affected the tag structure, requiring the author to do lots of remediation.
Any recommendations? solutions? similar experiences?
It seems obvious to me that this is a flaw in Acrobat that needs to be addressed, if accessibility is a goal. Or perhaps I'm doing something wrong??

Hi Daver1111,
Nope. No answer and nothing from Adobe.
I know something is going really really wrong, too: We have a product called CommonLook. It's an enterprise-level PDF accessibility remediation tool. It works well in fixing most structural problems in PDF through a relatively easy to use interface--you just drag textruns and elements around. It also has some tools that automate cleanup for accessibility.
I have no problem using this tool 99% of the time, but when I use it on forms I have made in Acrobat, the CommonLook plugin hangs when I try to save the PDF. It identifies a "structural error" in the PDF and crashes, leaving the PDF unchanged.
You can change the PDF in Acrobat by spending time moving around and creating new elements and deleting extra textruns and such, but, wow, what a royal pain in the *** that is!
Since no one is from Adobe is responding, I'm going to file a bug report.
Cheers,
ken

DB Utility (SE14) when adding new fields on standard dictionary table

Hi all,
we're searching of an official SAP document (or OSS Note) that certifies the mandatory use of DB utility (SE14) when we add one or more custom fileds on an append structure of a standard table (i.e. like VBAP).
Note: The custom append Structure already exists.
Thanks in advance,
Gianluca

Here is some info pointing to the same..[SAP Help|http://help.sap.com/erp2005_ehp_04/helpdata/EN/cf/21f1ab446011d189700000e8322d00/frameset.htm].
Regards
Narasimhan

Appending structures to the tables

Hi experts,
Why we are appending sturctures to the tables?
can any one tell me the main differences between the APPEND and INCLUDE structures
in Datadictionary.
Thanks in Advance.

Hi Ankita,
Customizing Includes
A Customizing include is a structure that satisfies a special naming convention. The name of a Customizing include begins with u2018CI_u2019 and the include is in the customer namespace.
If enhancements are already planned in the R/3 standard using customer-specific fields, such Customizing includes are included. in the corresponding standard table or standard structure. The Customizing include (that is the definition of the structure itself) is usually first created in the customer system and filled with fields by special Customizing transactions.
Customers can thus enhance tables and structures of the R/3 standard system without themselves having to modify the table and structure definitions. This means that these enhancements will not be lost when upgrading. If a table or structure of the R/3 standard system is enhanced with customer fields using a Customizing include, these customer fields are automatically inserted in the new delivered table or structure definition during an upgrade.
If you create a Customizing include for a table or structure, only those enhancements are allowed that are consistent with the enhancement category of the enhanced table or structure. For more information, see Structure Enhancements.
Customers can but need not create a Customizing include and fill it with fields. If there is no Customizing include, there is no error message when the table or structure including it is activated.
A Customizing include can be contained in several tables or structures, so that they remain consistent when the include is modified.
Append Structures
Append structures are used for enhancements that are not included in the standard. This includes special developments, country versions and adding customer fields to any tables or structures.
An append structure is a structure that is assigned to exactly one table or structure. There can be more than one append structure for a table or structure.
The following enhancements can be made to a table or structure TAB with an append structure:
Insert new fields in TAB,
Define foreign keys for fields of TAB that already exist,
Attach search helps to fields of TAB that already exist,
These enhancements are part of the append structure, i.e. they must always be changed and transported with the append structure.
When a table or structure is activated, all the append structures of the table are searched and the fields of these append structures are added to the table or structure. Foreign keys and search help attachments added using the append structure are also added to the table. If an append structure is created or changed, the table or structure assigned to it is also adjusted to these changes when the append structure is activated.
Since the order of the fields in the ABAP Dictionary can differ from the order of the fields on the database, adding append structures or inserting fields in such append structures does not result in a table conversion.
The customer creates append structures in the customer namespace. The append structure is thus protected against overwriting during an upgrade. The fields in the append structure should also reside in the customer namespace, that is the field names should begin with ZZ or YY. This prevents name conflicts with fields inserted in the table by SAP.
Reward if found helpful.
Anirban Bhattacharjee

Purpose of Append Structure in DDIC(SE11)

What is the purpose of Append Structure in DDIC(SE11)-Table?How to use this?
Title by: Alvaro Tejada Galindo on Jan 23, 2008 6:11 PM

Append structures are like user exits provided by SAP to enhance the Standard tables. It behaves like include structure only, but this append structure is taken care in the SAP version upgrage process, automatically. The name of append structure starts with 'Z' namespace..SAP by default proposes the append structure name with the table name prefixed with 'Z'.
It is always recommended to modiy or append the Standard tables using append structure.
It is the standard provided for SAP standard table enhancement.
APPEND STRUCTURE->
Append structures are used for enhancements that are not included in the standard. This includes special developments, country versions and adding customer fields to any tables or structures.
An append structure is a structure that is assigned to exactly one table or structure. There can be more than one append structure for a table or structure.
The following enhancements can be made to a table or structure TAB with an append structure:
· Insert new fields in TAB,
· Define foreign keys for fields of TAB that already exist,
· Attach search helps to fields of TAB that already exist,
These enhancements are part of the append structure, i.e. they must always be changed and transported with the append structure.
When a table or structure is activated, all the append structures of the table are searched and the fields of these append structures are added to the table or structure. Foreign keys and search help attachments added using the append structure are also added to the table. If an append structure is created or changed, the table or structure assigned to it is also adjusted to these changes when the append structure is activated.
Since the order of the fields in the ABAP Dictionary can differ from the order of the fields on the database, adding append structures or inserting fields in such append structures does not result in a table conversion.
The customer creates append structures in the customer namespace. The append structure is thus protected against overwriting during an upgrade. The fields in the append structure should also reside in the customer namespace, that is the field names should begin with ZZ or YY. This prevents name conflicts with fields inserted in the table by SAP.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eb61446011d189700000e8322d00/content.htm
INCLUDE->
http://www.sapdb.org/7.4/htmhelp/f2/b1219d1b9646b0ae248a7a5a95a33e/content.htm

How to make added custom field Delta mechanism work for LO Cookpit?

We appended a new custome field into extraction structure of the LO Cookpit datasource 2LIS_02_ITM through RSA6. And then run CMOD to write the exit code to populate the value and it works fine. But after we read Roberto's Weblog:
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it , find the enhancement we did can't make the Delta mechanism works if only this new field gets changed in a record, and the change cannot be reflected on BW.
In order to make the Delta mechansim works, one option is to append the custom field into one of the LIS Communication Structure MCEKKO of 2LIS_02_ITM extraction structure and then write the enhancement code to this LIS Communication Structure. In this way, the custom field can be treated like standard field that whenever it gets changed, the Delta mechanism or the user exit will be triggered. The enhancement for this LIS Communication Struture is LEINS001.
Now we've got two problems when doing the above enhancements of the LIS Communication structure:
1. Maintain extraction structure problem in LBWE:
We added a custom field, e.g., called ZZZ in LIS Communication structure MCEKKO (Purchasing Document Header) by creating a new custom append structure and add the field ZZZ into it, then activate the new append structure, but get warning msg like "Field name DUMMY is reserved (Do not use structure as include in DB table)".
We do find a field called DUMMY in the structure MCEKKO. How to get rid of the warning msg and successfully activate the new custom append structure with the new field ZZZ?
You could say that we can ignore the warning msg, but why the new custom field appended can not be seen from the right side pool of the Maintain Extract Structure in LBWE? We need to make the new custom field shows up in the right side pool and then drag it over to the left side frame and to activate the extraction structure to change it. But now it doesn't show up in the right frame pool!
2. Refer to Sanyam's weblog
/people/sanyam.kapur/blog/2005/04/30/custom-fields-and-bw-extractors-making-a-mixed-marriage-work-part-ii, there is a sample code inside this article which tells us how the sample code looks like to write this LIS Communicaton structure enhancement to make the Delta mechanism works, below is the code we modified to suit our needs, but don't know if it would work?
DATA: i_t_ekko LIKE ekko   OCCURS 1 WITH HEADER LINE.
DATA: ebeln LIKE ekpo-ebeln,
      it_ekko TYPE TABLE OF ekko WITH HEADER LINE,
      old_val(50) TYPE c. "For storing the value from the Field Symbol
FIELD-SYMBOLS <fs> TYPE ANY TABLE.
CASE zeitp.
WHEN 'MA'.                            "When creating a purchase order
    MOVE '(SAPLEINS)T_EKKO[]' TO old_val.
    ASSIGN (old_val) TO <fs>.
    i_t_ekko[] = <fs>.
    LOOP AT xmcekko.
      ebeln = xmcekko-ebeln.
      IF xmcekko-supkz = '1'.            "Old Value ?
        SELECT SINGLE * FROM ekko INTO it_ekko WHERE ebeln = ebeln.
        xmcekko-ZZZ = it_ekko-ZZZ.
      ELSE.                              "New Value ?
        READ TABLE i_t_ekko WITH KEY ebeln = ebeln.
        xmcekko-ZZZ = i_t_ekko-ZZZ.
      ENDIF.
      MODIFY xmcekko.
    ENDLOOP.
EndCase.
Share your ideas and we will give you reward points!

Hello Kevin
We have exactly the same problem. Did you solve it? If you did, could you please tell us how you did it? We neither see our field in LBWE. Our field is a Z field from a Z table.
I hope you could help us. We just have this issue to finish our project.
Thanks a lot in advanced

Adding custom fields to notifications-approval tab alv grid

Transaction IW21 - Create PM Notifications.
on the Approval Tab - there is an ALV grid that contains lots of fields. I know that i can click on the upper right hand corner and modifiy the layout by hidding fields. I want to add some custom fields to this grid.
I added my fields to view QMSM and now when I look at the database table using SE16 - i can see my new fields.
But how do I add them to this ALV grid?
Please and Thank you,
Julia Ramos
Orange County Public Schools.

I have read SAP OSS NOTE: 586523 Customer-defined fields in list editing. This note helped me add these same fields to many of the standard reporting transactions. IQS8, IW28, IW29, IW38, IW39
I added my fields to
QMEL - Quality Notification
RIHQMEL_LIST - Display structure reporting for QMEL
RQMQMEL - Quality notification - header data
RQMQMSM - Quality notification - measures (reporting)
Then i ran SAP program BALVBUFDEL. This program refreshs the alv buffer. This was very cool in that it allows us to access and report on all of my custom fields thru the standard reporting transactions!
I thought this same logic might work for transaction IW21. I found the structure used by the approval tab alv program, QMSM, and created an append structure, ZAQMSM with my fields - ran the balvbufdel program to refresh the alv buffers - but i still can not see my fields in the approval tab. I believe that there must be a way to do this - i will keep trying different things and read thru move OSS notes. If you have any sugestions or ideas - they would be greatly appreciated.
Thanks

Difference between include structure and Append structure

Could you please tell me
I have bsis table and it contains append structure in 4.7 SAP System.
my program in 4.7 system contains internal table which used same structure of bsis table ( which contains additonal field in its append structure ).
I need to have same table structure in 4.6 C because I am copying the same program into 4.6 system.
As I could not append structure to bsis table in 4.6C SAP system,
instead of that shall I add the field or Shall include the structure to run .
What is the difference between Include structure and Append structure ( I forgot )
How to achieve this please help me ?

Hi ,
As you know append structure can be used only once in table ,that to at last of all entries,
Append structures are used for enhancements that are not included in the standard. This includes special developments, country versions and adding customer fields to any tables or structures.
An append structure is a structure that is assigned to exactly one table or structure. There can be more than one append structure for a table or structure.
The following enhancements can be made to a table or structure TAB with an append structure:
Insert new fields in TAB,
Define foreign keys for fields of TAB that already exist,
Attach search helps to fields of TAB that already exist,
These enhancements are part of the append structure, i.e. they must always be changed and transported with the append structure.
When a table or structure is activated, all the append structures of the table are searched and the fields of these append structures are added to the table or structure. Foreign keys and search help attachments added using the append structure are also added to the table. If an append structure is created or changed, the table or structure assigned to it is also adjusted to these changes when the append structure is activated.
Since the order of the fields in the ABAP Dictionary can differ from the order of the fields on the database, adding append structures or inserting fields in such append structures does not result in a table conversion.
The customer creates append structures in the customer namespace. The append structure is thus protected against overwriting during an upgrade. The fields in the append structure should also reside in the customer namespace, that is the field names should begin with ZZ or YY. This prevents name conflicts with fields inserted in the table by SAP.
The new versions of the standard tables are imported after an upgrade, and the fields, foreign key definitions and search help attachments contained in the append structures are added to the new standard tables at activation.
A standard table contains the fields Field 1, Field 2 and Field 3. An append structure containing the fields ZZA and ZZB is defined for this table. After activating the table, the corresponding database table contains fields Field 1, Field 2, Field 3, ZZA and ZZB.
Further Remarks:
An append structure can only be assigned to exactly one table or structure. If you want to append the same fields to several tables or structures, you can store these fields in an include structure. In this case you must create an append structure for each of these tables or structures and include the include structure there.
Adding an append structure to an SAP standard table is supported by the Modification Assistant.
If you want to insert a field that is to be delivered with the R/3 standard in the next Release in the customer system in advance, you must include it in the table itself as a repair. If you include such a field in an append structure for the table, it will occur twice when the new standard table is imported. This will result in an activation error.
No append structures may be added to tables with long fields (data types VARC, LCHR or LRAW). This is because a long field must always be the last field in the table. However, structures with long fields can be enhanced with append structures.
If a table or structure with an append structure is copied, the fields of the append structure become fields of the target table. Foreign key definitions and search help attachments appended with the append structure are copied to the target table.
Foreign keys for the appended fields must be defined within the append structure. Fields of the table or structure assigned to the append structure may be defined when assigning the key field and foreign key field.
Indexes on the appended fields must be defined in the original table.
A table or structure TAB can only be enhanced with new foreign keys or search help attachments using an append structure. You therefore cannot change an existing foreign key definition or search help attachment for a field of TAB with the append structure.
Thanks
Manju

Delete customs append structure issue

Hi Gurus,
I added a customs append structure with a 'YY' field in one of LO extractr structures.
Now I don't need that field, I need to delete that customs append structure and field from the extract structure. I deleted that 'YY' field but I don't how to delete customs append structure which one I created.
Please advice ?
Thanks
Liza

Goto SE11 -> Give append structure name ..should be ZA* and select delete option , This will delete append structrure ref. from extract structure.
Hope it helps..

Lost Append structure on adding standard field in exctractor 2LIS_13_VDITM

Similar Messages

Maybe you are looking for