topic Re: common fields in Application Development and Automation Discussions

common fields

Former Member — Tue, 03 Jun 2014 11:11:55 GMT

Hello Experts,

I have a requirement. In my report I have to add a field "Movement type (T156-BWART)". My report is about Purchase document details. I am using tables "BKPF,BSEG,EKPO". I want to relate T156 table with these any of the tables. Please let me know how to relate these tables?

Thanks

Re: common fields

Former Member — Tue, 03 Jun 2014 12:09:03 GMT

Hi Vinod,

Please add one more table EKBE in your report.

EKPO -ebeln = EKBE-ebeln.

EKPO-EBELP = EKBE-EBELP.

you can get correct movement type BWART from EKBE table. and then you can pass the same value in T156.

Regards,

Prasenjit

Re: common fields

kiran_k8 — Tue, 03 Jun 2014 12:14:43 GMT

Vinod,

Also sort the itab by BWART,SOBKZ,KZBEW,KZZUG,KZVBR and then delete the adjacent duplicates by comparing BWART,SOBKZ,KZBEW,KZZUG,KZVBR.if the itab that you have is related to ITEM.

This way you will get the unique entries whose related data you can fetch from T156 and T156T

K.Kiran.

Re: common fields

former_member183424 — Tue, 03 Jun 2014 12:20:32 GMT

In EKBE table, you will find the movement type. But the table will only update, when any movement type happens against the Purchase Order..

You can call the movement type against the PO number and PO item number..

Re: common fields

Former Member — Tue, 03 Jun 2014 14:14:27 GMT

Hi Mishra,

I have tried with your option and getting BWART from EKBE table. My question is EKBE-BWART is always equal to T156-BWART? If equal then why I need to access T156 table for BWART?

Re: common fields

Former Member — Tue, 03 Jun 2014 16:07:11 GMT

Hi Vinod,

I don't think this table T156 is needed because this is config table . if you need PO related move

ment type then no need to take T156 but if you need to add bwart related description or any value then you can add otherwise useless for report.

Regards,

Prasenjit