‎2013 Sep 19 2:55 AM
Hi experts,
I have to create an LSMW using a BAPI for Purchase Documents (BUS2014)!
I have found the BAPI, have identified that it will most likely fulfill my requirement but I am stuck at how I should define my input file.
I have the headers, the line items, scale values for conditions and also split cost centers.
Should I define different files for these? If so, what should I use as the key for the scale values for example? Each contract can contain various materials, each material can contain multiple scale values...
Does anyone have an example of this?
Any help is highly appreciated!
Thanks!
Fernanda
‎2013 Sep 19 8:52 AM
Hi,
Use separate files for each structure. Use any key as a link between different structures.
We faced such scenarios in many of our objects. For example, for Inspection plan below sequence of fields we used as link:
Header: PLNNR
Material data: PLNNR (since material data is at header level, only PLNNR is key field)
Item: PLNNR, VORNR (VORNR is the line item number to identify unique key)
Item text: PLNNR, VORNR (VORNR is the line item number to identify unique key)
Similarly in your case decide which fields you would like to make as key. Some times we use a key field just to match this sequence and never use for upload. And also the same sequence has to be maintained in source structures. And in your data file the file has to start with above fields followed by other fields.
Its a bit tricky. But I tried to simplify as much as possible.
Please let me know in case of any questions.
Regards,
Revanth
‎2013 Sep 19 8:23 AM
‎2013 Sep 19 8:52 AM
Hi,
Use separate files for each structure. Use any key as a link between different structures.
We faced such scenarios in many of our objects. For example, for Inspection plan below sequence of fields we used as link:
Header: PLNNR
Material data: PLNNR (since material data is at header level, only PLNNR is key field)
Item: PLNNR, VORNR (VORNR is the line item number to identify unique key)
Item text: PLNNR, VORNR (VORNR is the line item number to identify unique key)
Similarly in your case decide which fields you would like to make as key. Some times we use a key field just to match this sequence and never use for upload. And also the same sequence has to be maintained in source structures. And in your data file the file has to start with above fields followed by other fields.
Its a bit tricky. But I tried to simplify as much as possible.
Please let me know in case of any questions.
Regards,
Revanth