Purchase Organation Disappearing after cancelliation of Assignments

Question

HI,
step1: i was created purchase requisation Of Type K - Cost center using me51n Transaction.
step2: after that using ME54n Tcode i was release that purchase Requisation and saved.
step 3: after releasing go to T code ME57  and execute Me57 Tcode for created Purchase requisation.
           now select the check box of material and click Assign Automatically and click save
       go to Tcode : ME53n in another session  and check that purchase requisation ,in that Preq I am getting Purcase  organisation.
Now again  in ME57 Tcode  check the material check box and click Cancel Assignments (5 th Tab On Screen) and save
again you check the PREQ in ME53n Tcode ,now purchase organisation is disappearing from purcase req.
the business needs purchase organasition info on purchase req after cancelation of assignments.
please provide me the possible soluction for this.
regards
Moderator message: please investigate yourself first before asking for solutions.
Edited by: Thomas Zloch on Feb 24, 2011 1:08 PM

Answer 1

Hi FF,
I think we are on the same page with terminology
Indeed, our process is a bit "enhanced" I would say. When doing the GR from purchase order, the batch characteristic LOBM_UDCODE is pre-filled with the UD of "Q" (LEANQM1  Q) whereas the IL created upon packing of HUs has no UD.
Then, when user makes UD for this IL, the pre-filled UD on batch level should be changed to the UD user made. It is not and the value disappears. I've run some checks on the ABAP code and the issue seems to be caused by the VB_CHANGE_BATCH used in the MQEVAF40 in form charge_klassifizieren. When the initial UD is made (QA11), the internal table for this f-n module has only the new values the batch classification is to be updated with. When the UD change is made (QA12) - both new and old values are provided. If I change the internal table values to include old and new ones for the initial UD, the process works correctly (batch LOBM_UDCODE is updated with new value).
As we are upgrading to ECC6 EHP5, I've compared the flow to the ECC5 and the values provided to VB_CHANGE_BATCH at initial UD (QA11) are the same for both systems. The process works in ECC5. As result, we have created the OSS message.
In MSC3n changes to the batch characteristics are visible from change docs - and the log is kept for QA11 and QA12. For the removal of LOBM_UDCODE it displays "deleted" values, and for QA12 it shows "created" values. In other words - change logs are working correctly.
Once SAP responds to OSS message I will update this tread. Any ideas appreciated.
/J