Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Medruck Problem!

Former Member
0 Likes
419

Dear Experts!

My problem is that in the purchase order print , the item text is not being printed.

i.e for 45 series po nos it is printing but for 47 serisespos i.e 4700000000 the item text is not printed .

i have debugged the medruck program and have found that the element "item_text" is not processed at all but i coluldn't find why is it not processing this element in 47 series po's.

Thanks in advance for your kind reply.

Regards,

Parwez.

Dear Experts!

My problem is that in the purchase order print , the item text is not being printed.

i.e for 45 series po nos it is printing but for 47 serisespos i.e 4700000000 the item text is not printed .

i have debugged the medruck program and have found that the element "item_text" is not processed at all but i coluldn't find why is it not processing this element in 47 series po's.

Thanks in advance for your kind reply.

Regards,

Parwez.

1 REPLY 1
Read only

Former Member
0 Likes
374

Hi Mirza,

Considering the POs have a different number range, it's quite possible because the POs are of different type, i.e. POS of number range 45* are Purchase Orders and documents with number range 47* are probably contract ..... distinguished by document type viz. EKKO-BSART.

I would suggest you (or consult your functional who has defined the number ranges, and criteria for the same) find the pattern and determine the difference between the two ranges.

Having done that, check the driver program to see where the ITEM_TEXT text element is called. I am sure there was must a validation like e.g. if EKKO-BSART is purchase order . WRITE_FORM ITEM_TEXT ...... etc.

If you check with your functional, I think he might be able to point out the issue immediately.

Regards,

Aditya