LSMW PUMAPAA-data conversion issue

[Former Member]

Hi Team,

I am using above mentioned LSMW project to upload pricing rules such as YPS1, YPS2, YPEO etc. But recently we found out that the LSMW is not converting (In the CONVERT DATA step of LSMW) the data for YPEO Condition Type. I debugged and found out that there is a conversion program which runs whenever I execute CONVERT DATA step of LSMW. And in this Conversion program there is a check for the YPEO condition Type. I found out that the code contains nothing but the code that had been written in rules and subroutines of the LSMW steps- "Field Maintain Field Mapping and Conversion Rules" and " Maintain Fixed Values, Translations, User-Defined Routines". I tried to find the same section of restrictive code in the LSMW but could not find that only piece of code. I do not know how that restrictive piece of code came into the conversion program. The user claims that he has been using the same LSMW for the many years but only now he is facing issue for some particular condition types.

Probable solution: Correct the conversion program to remove the restrictive piece of code, but that may not work as the conversion program has different names in Testing and development systems, and whenever any one do a Syntax check of the LSMW the conversion program will be regenarated.

But please let me know how is it possible for Conversion program to have a piece of code that is not present in LSMW.

Regards,

Amit

[JL23]

LSMW is a project, which is subdivided into subproject and object.

If somebody added this code in own routines in a different object, then this routine is inlcuded in all generated programs of the whole project.

[Former Member]

Hi Jurgen,

I looked into all the SubProjects and objects of the LSMW Project and could not find the required piece of code. Please let me know what could be the solution of this issue.

Regards,

Amit

[Former Member]

Hi Team,

This issue is resolved.

Regards,

Amit

[Former Member]

Hi Team,

This issue is resolved.

Regards,

Amit

[Former Member]

Hi amit,

please share as to how did you resolve the issue so that everybody gets a chance to learn through this forum.

Regards,

Rahul

[Former Member]

Hi Team,

The LSMW was executing a piece of code which was not found anywhere in the LSMW. So the aim was to find out the location of code and the person who wrote the code. I debugged and found out that there is this table /SAPDMC/LSOCOD which contains ABAP Code of Conversion Rules. So the conversion program(Used when converting read data) consults this table and creates the code and executes the same code. The code that I was searching was found in the table for the same LSMW project/Subproject/Object. I also found out the name of person who wrote that code and the date at which it was written, but I never found the exact location where it was written. The user told me that there had been Patch Upgrade activity in the system and that is the reason that some of the changes earlier done by them has been removed. From there on they convinced me that the User will copy the working LSMW from production into the Test System and the Development system. It is not done yet, but this is supposed to solve our problem.

Regards,

Amit

[JL23]

table /SAPDMC/LSOCOD keeps any code that is added manually or automatically for any field and processing time in step 5 Field Mapping

Can it be that you had not ticked all options from menu Extras > Display variant

and hence you did not see the coding that was added at the processing times such as BEGINOF_TRANSACTION_

[Former Member]

Hi Jurgen,

Thank you for your input. I could not find the option Extras-Display variant. Please enlighten me by guiding me in finding it. But in table /SAPDMC/LSOCOD I found that the target field(TRGFLD) was '__END_OF_RECORD__'.

Regards,

Amit

[JL23]

Sorry, I did a free translation.

it is in step 5, menu Extras > Layout.

[Former Member]

Hi Jurgen,

Yes I found the code that I could not find earlier, but now by using method suggested by you. Please accept my heartfelt thanks for the same. This solves this issue.

Regards,

Amit