Infotype and Include Structures in HR - ECC50

Hi,
I would like to know what are the changes in each and every infotype like different include structures or added fields or modified or deleted fields. How do you compare 46C version with ECC50.
Is there any way apart from remote version management option?
Thanks,
Kiran.

Hi,
I don't know what your actual requirement is.. but the event GET PAYROLL already exists. PL take a look at the Program EXAMPLE_PNP_GET_PAYROLL to get an idea. You can also see the same at this <a href="http://help.sap.com/saphelp_47x200/helpdata/en/33/62ac39d22d11d396e700a0c9306433/frameset.htm">SAP help</a>
Regards,
Suresh Datti

Similar Messages

Difference between append structure and include structure in DDIC

Plz give me the apt difference between append structure and include structure in DDIC.
Thanks in advance.
Regards
Raj

This has been discussed please check it in forum
https://forums.sdn.sap.com/click.jspa?searchID=480466&messageID=114309
https://forums.sdn.sap.com/click.jspa?searchID=480466&messageID=1419481
https://forums.sdn.sap.com/click.jspa?searchID=480466&messageID=1479212
Shortly:
Append structures are used for enhancements that are not included in the standard. 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.
http://help.sap.com/saphelp_erp2004/helpdata/en/cf/21eb61446011d189700000e8322d00/content.htm
Includes are used to group fields, an include structure can be assigned to many tables. If you add a fields to an include structure, all tables/structures, which contain that include structure, will be updated too.
http://help.sap.com/saphelp_erp2004/helpdata/en/cf/21ea6a446011d189700000e8322d00/content.htm
Regards,
Santosh

Is Customising Include and Include structures same?

Hi,
Could any one tell me
whether
Is Customising Include and Include structures same?

hi,
Structures can be included in tables or other structures to avoid redundant structure definitions.
A table may only be included as an entire table.
A chain of includes may only contain one database table. The table in which you are including belongs to the include chain. This means that you may not include a transparent table in a transparent table.
Includes may contain further includes.
Foreign key definitions are generally imparted from the include to the including table. The attributes of the foreign key definition are passed from the include to the including table so that the foreign key depends on the definition in the include.
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.
A Customizing include is a structure that satisfies a special naming convention. The name of a Customizing include begins with CI_ and the include is in the customer namespace.
If enhancements are already planned in the 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 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 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.
Hope this helps. Do reward.
Edited by: Runal Singh on Mar 19, 2008 2:39 PM

Difference between Append structure and include structure

hi can anyone tell me the difference between include structure and append structure with respect to tables defined in ABAP dictionary?
Also how to create them in ABAP dictionary?

HI
INCLUDE:
Includes are used to group fields and insert them together in a table or structure.
An include program has two main functions:
It contains code which can be used by several different programs.
It helps you to modularize programs, which consist of many different logically related parts. Each of these parts is stored as a separate include program.
Include programs improve the readability of programs and make maintenance easier.
Include reports contain rolled out parts of reports. They are called by the main report, and can only be run in conjunction with the main report.
APPEND:
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
Just have a look at this link:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ebd6446011d189700000e8322d00/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ebd6446011d189700000e8322d00/frameset.htm</a>
Rsgards,
Gunasree.
Award marks to helpful answers

How do I Make Include Structures Expand Automatically?

As usual some of the simplest things take the longest time.
I've created a custom structure in the dictionary. I've also created a custom table in which I include the structure. I expected that after I added the include structure to the custom table, that it would be expanded and display in se11, and behave just as SAP-delivered tables do. For example, look at table PA0001. There are include lines followed by the contents of the include.
In my custom table though, I only see the include line itself. To see the structure I must expand it by pressing the expand button. Each and every time I display the custom table I must manually expand it. I want the behavior I see on every other SAP table.
Any ideas?
Thank you.
Tom

Hi,
if You have include structure in Your table, all fields are displayed only in display mode.
That is the way You see the PA0001 table.
If You create your own table and include structure, in edit mode You can change fields of the include structure,
that is why it is not expanded. But if You change from edit to display mode, SAP does not expand it automatically.
You should display in SE11 this table - all fields will be visible.
Regards,
Przemysław

Include structure field kunnr

Dear Friends,
In the structure FPAYHX, field ZBANK is working perfectly while using T.code FDTA-Data Medium overview and when the data is downloaded,the field citibank is shown.
A field kunnr was inserted as include structure and using T.code FDTA-Data Medium overview, we downloaded the data, but we are unable to see any data.
We have checked and include structure is activated and also checked with other structures, but we unable to find why it is not working like SAP structure field.
Any suggestions will be highly appreciated.
Regards
Sridhar

hi Sridhar ,
for uploading data in field kunnr u have to write a code or sm user exit. as the field is there but u are using an standard t code which dont know about the new field . so the data has to be passed through
custom code to the field for downloading.
regards,
Aditya Shrivastava.

What is diff b/w Include Structure and Append Structure at Database Level

Hi Experts,
Could you please let me know what is the main difference between .Include Structure and .Append Structure at SE11?
Thanks in advance and for good answer will give good points.
Sekhar

Hi,
1. Append Structures
Append structures can only be assigned to a single table.
Append structures are created in the custome rnamespace ( ZZ or YY)
In case of new versions of the standard table during upgrade, the append structures are automatically appended to the new version of the standard table
Append structures can not be used with cluster and pool tables
Append structures are created in transaction SE11. Display the standard table fields and press the Append structure button.
When you press the button, SAP sugests a name for the new append structure. After you has accepted the name,
a screen will be shown where you can enter the new fields.
Remember to activate.
2. Customizing Includes
Some of the SAP standard tables contains special include statements called Customizing includes. In contrast to Append structures,
Note that customizing includes are created by SAP, but the customer supply the fields for the include.
Customizing includes begin with CI_ and is part of the customer namespace
One Customizing include can be inserted into more than one table.
You can find Customizing includes in SE11 under structures.
Try to take a look at table RKPF which uses the Customizing include CI_COBL (In an IDES system). Next try to add a field to CI_COBL, and activate it. If you go back to table RKPF you will se that your new field has been added.
Regards,
Ferry Lianto

Include structure and extra fields in the same Internal Table

Hi developers,
im trying to declare an internal table with include structure and extra fields,
something like this:
data: BEGIN OF it_loans occurs 0,
      include structure zthrca006,
      status(10),
      pernr   like pa0001-pernr,
      sname   like pa0001-pernr,
      tipomov(20),
      monto   like zthrca006-monto,
data: END of it_loans.
zthrca006 is huge so i dont want to type everithing.

What is the issue?
data: BEGIN OF it_loans occurs 0.
             include structure zthrca006.
data :     status(10),
data :     pernr like pa0001-pernr.
data :     sname like pa0001-pernr.
data :     tipomov(20).
data :     monto like zthrca006-monto,.
data: END of it_loans.
Regards,
Ravi
Note - Please mark all the helpful answers

User include structure and routines/program/user exits

Hello Gurus,
     following is the step for modify the field catalog in material determination .
Modify the field catalog (OV26)
1.     Add the new field to the user include structure:
o     Header data KOMKDZ
o     Item data KOMPDZ.
2.     Add coding to the routines for assigning values to the new fields in order processing in program MV45AFZA. Use user exits:
o     USEREXIT_MOVE_FIELD_TO_KOMKD (header fields)
o     USEREXIT_MOVE_FIELD_TO_KOMPD (item fields)
3.     Add the new field to the field catalog (Customizing activity Basic Functions  Material Determination  Maintain prerequisites for material determination  Maintain field catalog).
Will you please tell me what the step 1 and step 2 mean ? and what 's the user include structure and USEREXIT_MOVE_FIELD_TO_KOMKD/USEREXIT_MOVE_FIELD_TO_KOMPD and program MV45AFZA ?
thanks very much!

Hi,
KOMKD is cummunication header and KOMPD is communication item which are actually contained in KOMGD structure. So automatically when you add a field to either of header or item it becomes a part of KOMGD. And moreover KOMGD contains all the fields of KOMKD and KOMPD which are required for materail determination.
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination" .
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination ".
regards
sadhu kishore

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

Share Global structure for different module and include

Hi,
How can shared the data declaration for different module and include??
Regards,
Kit

Declare your variables in TOP include of the function group.
a®

In a server proxy how can I use a INCLUDE STRUCTURE?

Hi people!!, how can I put an internal table with an INCLUDE statement in a server proxy in abap. If I put the next code the system present me this error: Within classes and interfaces, you can only use "TYPE" to refer to ABAP , Dictionary types, not "LIKE" or "STRUCTURE".
The problem is that I need the STRUCTURE to make a APPEND.
Thanks for the help.
DATA: BEGIN OF bdc_tab .
INCLUDE STRUCTURE bdcdata.
DATA: END OF bdc_tab.

Hi Carlos,
Yes. It mainly accepts TYPE statements.
You can use this as:
DATA: BDC_LINE type bdcdata.
DATA: BDC_TAB type table of bdcdata.
When you want to use,
Fill the BDC_LINE.
Then:
Append BDC_LINE to BDC_TAB.
Or:
Loop at BDC_TAB into BDC_LINE.
Cheers,
Bhanu

How to add fields in custom infotype and update its screens

Hi Experts
I want to enhance a custom infotype ( Add some new fields, and add special function on its screen). This custom infotype is created in previous release. is there any way to add fields in infotype? and let system automatcailly modify corresponding screens to add new fields

Go to Transaction PM01.
2) Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
3) Select the u2018Employee Infotypeu2019 radio button.
4) Select the u2018PS Structure Infotypeu2019.
5) Click on Createu2026 A separate table maintenance window appearsu2026
6) Create a PS structure with all the fields you want on the Infotype
7) Save and Activate the PS structure
8) Go back to the initial screen of PM01.
9) Click on u2018Allu2019 push button. It takes a few moments.
10) Click on u2018Technical Characteristicsu2019. Infotype list screen appears
11) Click on u2018Changeu2019(pencil) button
12) Select your Infotype and click on u2018Detailu2019 (magnifying glass) button
13) Give u2018T591Au2019 as subtype table
14) Give u2018T591Su2019 as subtype txt tab
15) Give your subtype field as subtype field
16) Save and come back to PM01 initial screen
17) Click on u2018Infotype Characteristicsu2019 u2026 Infotype list screen appears
18) Click on u2018Changeu2019 (pencil) button
19) Click on u2018New Entriesu2019
20) Enter your Infotype number and short text
21) Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotypeu2019s infotype characteristics screen and use as the reference to fill yours)
22) Save your entries.
23) Now the Infotype is created and ready to use.
24) If you want to change the layout of the Infotype as per your requirementu2026
25) In the PM01 initial screenu2026Select u2018Screenu2019 radio button and give 2000 as the screen name, then click on edit.
26) In the next screen.. Select u2018Layout Editoru2019 and click u2018Changeu2019.
27) Screen default layout appearsu2026here you can design/modify the screen..change the attributes of the fields..etc.
28) Save and activate. (Donu2019t forget to u2018Activate at every level
i think u have to select CI_INCLUDE while enhanceing the Standrad Infotype

The source and target structure have a different number of fields

Hi,
I am new to workflow and I am trying to create an attachment in Workflow (SAP ECC 6.0) and pass it through to a User Decision (User Decision works fine) however the workflow is failing on the attachment step with u2018The source and target structure have a different number of fieldsu2019. The bindings check ok. Please see details below.
I have used document u2018Creating Attachments to Work Items or to User Decisions in Workflowsu2019 by Ramakanth Reddy for guidance. Thanks in advance.
1) Workflow containers (SWDD)
WORKITEMID (import)
ZSWR_ATT_ID (export)
SOFM (export)
2) Task Container (PFTC)
1 Import parameter defined u2013 WORKITEMID (swr_struct-workitemid)
2 Export parameters defined
- SOFM (Ref. obj. type SOFM)
- ZSWR_ATT_ID (swr_att_id-doc_id)
Binding task -> Method
Binding for 1 parameter (import) defined
Task <- Method
Binding for 2 parameters (export) defined
3) Z BOR object created with a Method, Method Parameters and Event (SWO1)
1 import parameter defined
2 export parameters defined
Method calls FM SSF_FUNCTION_MODULE_NAME, CONVERT_OTF, SCMS_XSTRING_TO_BINARY and SAP_WAPI_ATTACHMENT_ADD
Workflow is triggered by FM SAP_WAPI_CREATE_EVENT, Return_code = 0
Event_id = 00000000000000000001
Test results
A) Triggered by ABAP/ FM SAP_WAPI_CREATE_EVENT - SWI2_DIAG results
Work item 14791: object <z bor object name> method <method name> cannot be executed. The source and target structure have a different number of fields (this message is repeated 3 times). Error handling for work item 14791. No errors occurred -> details in long text (message is repeated 3 times).
Message no. WL821, OL383, WL050 in long text
B) Z BOR Test method <execute>
Enter workitem id.
Runtime error - Data objects in Unicode programs cannot be converted. The statement "MOVE src TO dst" requires that the operands "dst" and "src" are convertible. Since this statement is in a Unicode program, the special conversion rules for Unicode programs apply.
In this case, these rules were violated.
Program                             SAPLSWCD
Include                                LSWCDF00
Row                                    475
Module type                        (FORM)
Module Name                      MOVE_CONTAINER_TO_VALUE
C) Z BOR Test method <debugging>
Enter workitem id.
SAP_WAPI_ATTACHMENT_ADD, return_code = 0, message_lines = Attachment created
both swc_set_element container work ok
Runtime error occurs after end_method executed. Data objects in Unicode programs cannot be converted.
D) Workflow test
Enter workitem id <execute>
Task started> Workflow log> Status = Error
Workflow errors in Attachment step (however Office document can be viewed in details for step).

Problem has now been resolved. Problem was related to use of swr_att_id structure and swc_set_element statement in BOR program - problem resolved by only setting w/f container to swr_att_id-doc_id.

Fields missing in import and export structure PPCO0001 - PPCO0023

Hello Experts,
I'm hoping that you can help me. I am trying to add some logic in user exits to default data and do some checking in production orders. It would be great if I could talk to you about what Iu2019m trying to do and the problem that Iu2019m running into.
My main problem is that in the exits provided (enhancements PPCO0001 u2013 PPCO0023), most of the time either fields being imported or the field being exported do not include the fields that I want to change or check. Iu2019m wondering if there is some way to just pull-in the data and change/check in addition to what is already available to the exit. - Can I append the structures?
Hereu2019s an example below:
u2022 PPCO0006 Enhancement to predefine fields in order header
With this enhancement you can take fields from the order header in your own program and process them or define values for them and transfer the changed data again to the standard system. The transfer to the system takes place before you reach the order header screen. EXIT_SAPLCOZF_003 Exit for predefining fields in order header. The fields in the order header (structure CAUFVD) are placed in the function exit. All the fields that you can define or change are defined in the structure HEADER_CUST. The contents of HEADER_CUST is transferred back to CAUFVD on leaving the function exit.
Problem 1.
The documentation sounds greatu2026. Seems like the right place -- all the data I need is supposed to already be in CAUFVD_IMPu2026. BUT HEADER_CUST and HEADER_CUST_EXP do not have the fields that I need change. If I try to append the structure and include additional CAUFVD fields I either get a warning in the activation because of duplicate fields or If I try to add them as Zfields the program doesnu2019t take the change data because it does a move-corresponding from HEADER_CUST_EXP to CAUFVD and the Z fields donu2019t match. - what is the correct way to change header values if the fields that you want to change are not already defined in the structure HEADER_CUST?
Problem 2.
It seems that this exit occurs prior to pulling in the data from the standard routing (which would normally populate CAUFVD-PLGRP ... at the time of the exit this field is blank so i cannot use it to determine the value for another header field. I could get around this by reading directly PLKO but that won't help me if I cannot add CAUFVD-FEVOR as a field availble for changing/defaulting.
Problem 3.
If I get around Problem 2, I still have another problem. In PPCO0007& PPCO0001 I'm trying to change the user status to block the order from being printined until it passes the validation check and is error free. In PPCO007 I can block the order from being saved or in PPCO0001 I can raise a message that an error was found... but I need to change the user status at the same time as rasing the error or blocking the save.
Thanks so much for any guidance that you can give.

Dear,
When you do so, in the PPCO0001 customer enhancement, you should carry out follow actions based on the status changes since the contents of the STATUS_TABLE and STATUS_TABLE_OLD Exist is EXIT_SAPLCOBT_001 and CALL FUNCTION 'STATUS_CHANGE_EXTERN'
For details refer the OSS note 86553
Hope it will help you.
Regards,
R.Brahmankar

Infotype and Include Structures in HR - ECC50

Similar Messages

Maybe you are looking for