2LIS_02_SCL - need Doc Currency Amount (WRBTR) from EKBE table

[Former Member]

Problem: We are using the 2LIS_02_SCL to get our purchasing order data. The problem is that instead of sending over the Doc Value Amounts found in the EKBE table, SAP is doing a calculation based on the the local currency. They are then using the Exchange rate from the PO Header. Our users are complaining, because they expect it to match up with what is in the purchase order history.

I was planning to create a new amount field and and in my transfer rules write ABAP code to take the following fields from 2LIS_02_SCL:

BW:CValLC(BWGEO), Local cur.(HWAER), Posting Date, Currency(WAERS)

Use this Date to go back to TCURR to get the correct exchange rate that is used and do my calculation to doc currency (basically replicating the data as viewed in PO History).

I ran into an issue however. The Currency (WAERS) field is being filled with the value from EKKO. I have a below example where in EKBE, the PO was invoiced in a currency other than the DOC Currency.

Data in R/3 from EKBE (History per PO)

PO: 1

Amount in Local Currency(DMBTR): 250,01

Local Currency (HSWAE): USD

Amount in Doc Currency(WRBTR): 250,01

Doc Currency (WAERS): USD

Data in R/3 from EKKO (Purchase Order Header)

PO: 1

WAERS: DKK

In this scenario, I am unable to populate the correct value (as seen in purchase order history).

I don’t see of a way that I can get around this. Does anyone have any ideas?

Thanks

[Former Member]

Hi,

have you solved the issue?

Thanks.

Regards.

Andrea

Edited by: Maraviglia Andrea on Dec 9, 2011 3:00 PM

[Former Member]

But what I have to enhance, the program?

Do you think I have to modify function module...

Please tell me.

Rgds,

Giuseppe

[Former Member]

Hi Giuseppe.

There should be a field called BWGEOO in the SCL extractor which will give you the invoiced amount in the order currency.

br

jacob

[Former Member]

Hello,

BWGEOO isn't the solution since based DMBTR, too.

So, please tell me what I have to do?

Really I need community help.

Rgds,

Giuseppe

[Former Member]

Hi Giuseppe.

And why is that a problem? Could you give an example?

regards

jacob

[Former Member]

Hello,

I have the same issue.

In case solved may you feedback on solution applied?

Rgds,

Giuseppe

[former_member666794]

Why not to enhance extractor ?

Or Muliti cube concept suggested earlier is good option I think than enhancement as easy to handle , trace issue & maintance.

Regards,

Viresh

[Former Member]

Hello JP,

have you been able to fix this problem?

I'm in a same situation and I would appreciate a solution.

Thank you.

[Former Member]

Hi Jiri,

You can suggest the RRI from cube built on SCL report to cube built on EKBE based on PO.

Also check if this can be solved by using a multi-cube on these 2 cubes.

I have done a RRI when I was facing the same issue.

Regards,

Niraj

[Former Member]

Hello JP,

Please go through OSS notes 459297 and 670313 and see if it helps.

Regards,

Praveen

[Former Member]

Thanks, unfortunately, these notes don't apply.

[Former Member]

Hello JP,

Those notes are pretty old, but I don't think that problem has been fixed. Recently I ran into the same problem in spite of working on the latest version. You may want to have a look at these notes again and compare with the code in extractor.

Regards,

Praveen