Problems while uploading Task List - Service Pack with LSMW

Question

We are trying to upload General Maintenance Task List using LSMW. We are using Standard Batch/Direct Input method with Object 0490.
We need to upload task list header, operations, maintenance pack, component and service pack for operations.
We have created separate files containing data for different structures and they are linked using Group, group counter and operation number according below
Header
|----Operations
.......... |----Long Text
..........|----Maintenance Pack
..........|----Components
..........|----Service Pack
We have multiple operations per task list and multiple services per operation. The service pack is required only for a specific control key - PM03.  As per the configuration this screen (PROGRAM - SPLMLSP, Screen Number - 0200) is accessible only when the value PM03 is entered in the operation. We are able to upload all other details except service pack details. We have tried using structure IBIPBDCD for the same.
While uploading the task list in foreground, when control key is entered as PM03 in an operation, service pack screen is displayed with error u201CNo batch input data for screen SAPLMLSP 0200u201D. The data provided in structure IBIPBDCD does not get processed at this time.
On exiting the screen using back button, the data in IBIPBDCD structure is passed incorrectly to fields in screen 3400 (SAPLCPDI)
Are we doing something incorrect? Is there a way to use this standard functionality to upload task lists with service packs?
Thanks
Edited by: jvalitp on Dec 15, 2011 12:46 PM

Answer 1

Hi,
When loading the tasklists you need to define a source structure as per the IBIP structure. You have different levels for example level 1 - header then below that level 2 - Operations, Header Long text then below that you have level 3 - Operation Long text, Operation Package assignments, operation component allocation.
For each of these levels you need an identifier that links then together. In your source file specify identifier 1 for header, Identifier 1 and Identifier 2 for operations, identifier 1 identifier 2 and identifier 3 for packages. This way the system can create the correct structure when it reads the data from the text file.
The identifiers are numeric and will dissapear once the files are loaded. specify then in the source structure as 2 characters and remember to set the xcel file up to have a 2 character field.
For the header file each line will be a new identifier 1,2,3,etc.
The operations are assigned to the header and have 2 identifiers. The first corresponds to the header identifier the next is a sequential number stating at 1 and incrementing for each line e.g Header 1 op 1, header 1 op 2, header 2 op 3, header 2 op 4, header 2 op 5 (this would be 2 header records. The first with 2 operations on it the second with 3 operations)
The package is assigned to the operation and as such needs to have a third identifier. Header (identifier 1), Operation (identifier 2), Package (identifier 3) Example Header 1 op 1 pack 1, header 1 op 2 pack 2, header 2 op 3 pack 3, header 2 op 4 pack 4, header 2 op 5 pack 5
I have a loading file for each of the items i.e. Header file, Operation file, maintenance package file. This is then assigned to the respective source structure.
Regards,
ravi