Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Creating an infotype composed of standard infotypes parts

Former Member
0 Kudos

Hello all,

My purpose is to created an infotype to gather several fields of some standard infotypes.

In order to do this, I started to create a new infotype 9000 copying one of the infotypes whose fields where needed in the new one.

Now I just want to add my new infotype some fields belonging to another ifp. Is it possible to add a part of a standard ifp to my new one or do I have to add my fields one by one ?

Thanks everyone,

Sylvain

1 ACCEPTED SOLUTION

ssimsekler
Active Contributor
0 Kudos

Hi Sylvain

An infotype program is more or less encapsulated. That is; it uses its standardized procedures to handle only one infotype's records (though cross references naturally do exist in the business logic).

So, it will be a dialog program using th standard infotype maintenance program template and nothing more. You will have to write your own procedures to read and update infotype records.

Regards

*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

12 REPLIES 12

Former Member
0 Kudos

Dear Sylvain:

You can directly copy fields of another infotype into your custom infotype (9000) provided you are going to include all fields of the standard infotype.

In order to add/copy selected fields of some other infotype into your custom infotype, you would have to add them manually - one by one (or by doing COPY/PASTE).

Hope it helps.

Regards,

Chetan Singh

0 Kudos

Hi Chetan,

Thanks for your help, I'm afraid I'll have to copy them manually

Regards,

Sylvain

ssimsekler
Active Contributor
0 Kudos

Hi Sylvain

An infotype program is more or less encapsulated. That is; it uses its standardized procedures to handle only one infotype's records (though cross references naturally do exist in the business logic).

So, it will be a dialog program using th standard infotype maintenance program template and nothing more. You will have to write your own procedures to read and update infotype records.

Regards

*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

0 Kudos

Hi Serdar,

An other solution I thought is to create a new infotype (instead of copy one) with a structure that contains fileds of the severals infotypes I need.

This way programs to handle data will be generated. An I wrong ?

Thanks

Sylvain

0 Kudos

Hi Sylvain

I am not sure about your requirement. But if you want to maintain data for various infotypes within the same program, then you should write a dialog program using an update methodology:

i. Batch input

ii. The FM "HR_INFOTYPE_OPERATION"

iii. Related BAPI

Otherwise, just putting the fields with the same name (even with the same data element) to the newly created infotype (call 9000) will just update the table PA9000.

Regards

*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

0 Kudos

Hi Serdar,

In fact, my aim is to create a new infotype which will contain some element of various standard infotypes.

I cannot create a dialog program because I do not want to use standard infotypes.

A solution I found (do not known if it's a good one !) is to copy one of the standard infotype I need, then edit the structure newly generated (pa9000) and add it an include CI_9000 in which I add the other fields I need.

This way I have all my required fields and when using PA30 to create data, all fields are maintained.

I think the solution is not really "beautiful' but it seems to work fine.

What do you think of that ?

Regards

Sylvain

0 Kudos

Hi Sylvain

Let me draw what I see. Do you want to maintain e.g. persg, pesk from IT0001, vorna, nachn from IT0002, stras from IT0006 together from another customer infotype?

If so, generating an infotype will not have much for this. Because it will bring lots of integration problems (think of validity periods).

Regarding your proposal:

P9000 has following fields:

persg

persk

vorna

nachn

stras.

Then do not expect that it can maintain data of PA0001, PA0002 and PA0006. It will just maintain PA9000 unless you code more functionality which more or less is dialog programming. If you want just PA9000 to be filled, then you will lose many functionalities of HR system.

Since IT9000 is your own infotype, why do you need to append a customer include? If it is eligible, you can prefer appending CIs to standard infotypes.

Regards

*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

0 Kudos

Hi Serdar,

You see right ! But the infotype I create is independant, it does not need any link to others infotype. That's why I only care about filling PA9000.

I use an include only to remind the fields I add to the standard infotype I copied.

You're right, appending CIs to standard infotypes would have been better but proceeding this way would have kept the link beetween standard ITP whereas I want something independant.

Thanks for help

Sylvain

0 Kudos

Hi Sylvain

So, I wonder what will e.g. PA0001-PERSG mean and what PA9000-PERSG?

*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

0 Kudos

Hi Serdar,

The fields I use in IT9000 are fields of standard intofypes that are not used.

The infotype I create replaces several others standard ones.

So to answer your question PA0001-PERSG means nothing such it is not used.

Sylvain

0 Kudos

Hi Sylvain

Then you will lack standard HR processes which means you waste the HR system features. Standard reports and other standard objects uses e.g. PERSG. Do you take this risk? If so, do you just use the HR system as a dull template?

Regards

*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

0 Kudos

Hi Serdar,

We do use HR some standard infotypes, but in addition to them, I have to create a spécific infotype containing information that are meant to be independant.

I do not know the reason why it has been decided to proceed this way but it is how things will be done.

Anyway, I think my newly created infotype will be available for report isn't it ? I mean it will be possible to view stats concerning it.

Thanks for useful answers

Sylvain