Loading General Task list (IA05) through transaction IBIP transaction.

[Former Member]

Hi,

I have to populate the profile field in task list (IA05). I am using transaction IBIP to load task list. the header structure IBIPTLST does not have profile ID so i have used structure IBIPBDCD and passing values for Profile ID in this structure but still I am not able to populate it. Following are the values I passed for structure IBIPBDCD.

RECORDNAME = IBIPBDCD

PROGRAM = SAPLCPDI

DYNPRO = 3001

DYNBEGIN = X

FNAM = RC271-PROFIDNETZ

FVAL = 0000001

Can any one tell me how to populate Profile field using structure IBIPBDCD through transaction IBIP.

Thanks and Regards,

Aparajita.

Edited by: arun sharma on Jun 26, 2008 10:53 AM

[Former Member]

Hi arun,

try this.....

<copy&paste_removed_by_moderator>

thanks,

karthik

<removed_by_moderator>

Edited by: Julius Bussche on Aug 20, 2008 7:25 PM

[Former Member]

Hi Karthik,

The matter that you have given me is from the IBIP documentation and I have tried those options. It does not work. Can you try for yourself and let me know.

Regards,

Aparajita

[Former Member]

Hello Arun Sharma

IBIP could use the transaction? How did you do? I'm having trouble using the field PROFIDNETZ.

[Former Member]

Hi

If i am not wrong you are loading Equipment Task list.I had though loaded it using standard batch input methood.I think it would be must easy inloading thru LSMW however for ur information the object is:- 0470.

Program Type:-B(batch input).

In the equipment Task list header ID (char 10) as well as in Task list Header txt ,task list line.Maintain field mappings there is no way that you would be going wrong.However you need to specify 5 files apart from header ,line,texts you need to include PRT too.

Regards

Somnath

[Former Member]

Hi,

I want to use the structure IBIPBDCD IBIP: direct BDCData to fill the field that I lack (RC271-PROFIDNETZ, IA01 transaction) but not as fill.

Thank you very much

[Former Member]

We also faced the issue of populating the PROFILE field. We resolved this by using a user defined parameter value on the executing users account (defaults tab).

This allowed us to populate a constant profile value on all task lists processed by that user.

Not sure if you have a requriement to use different profile values - but this was the quick fix for us.