significance of BWCOUNTER in 2LIS_03_BF extractor

[Former Member]

Hi All,

Can you please share significance of BWCOUNTER in 2LIS_03_BF extractor.

Thanks

Prasanna

[shanthi_bhaskar · Accepted solution]

To manage SAP stocks using non Cumulative key figure, BW needs type types of material documents.

One type that add stocks, and another that reduces stocks.

In SAP R/3, in some paticular cases, when stocks moves from one Store Location (or Plant) to

another Store Location(or Plant), only one record is created in MSEG.

For example, when using movetype 305 (movement between two plants), only one record is generated at MSEG.

But, for BW, two records are needed. A recored adding stocks to one plant and A record reducing stocks from another plant.

To solve this issue, datasource 2LIS_03_BF program sometimes creates two records from one MSEG record.

When datasource do this, two record have same document number and document line number,

and there is no unique key to discriminate two records.

So,  datasource 2LIS_03_BF add another key - 0BWCOUNTER and

datasource 2LIS_03_BF add unique number that start with 1.

>Due to this fact, the stock balance between R3 and BW aren't matching.

We manages SAP stocks in BW using non Cumulative key figure and

there is no case where 0BWCOUNTER causes stock-unmatching.

But, datasource 2LIS_03_BF had (or has?) many bugs and they have caused stock-unmatching.

[Former Member · Accepted solution]

Hi Shanthi,

Thanks for your reply. I just want to confirm that this is the only one reason behind BWCOUNTER in 2lis_03_bf extractor or anything else. Please let me know if there are any other reasons too....

In SAP R/3, in some particular cases, when stocks moves from one Store Location (or Plant) to

another Store Location(or Plant), only one record is created in MSEG.

For example, when using movetype 305 (movement between two plants), only one record is generated at MSEG. But, for BW, two records are needed. A recored adding stocks to one plant and A record reducing stocks from another plant.

Highly appreciate your help....

Prasanna

[shanthi_bhaskar · Accepted solution]

Hi Prasanna,

I think that is the prime purpose of it.

I also verified in SDN but didnt get any other reason.

Thanks,

SB

[FCI]

The fields MBLNR,MJAHR, ZEILE and BWCOUNTER identify a unique record send by this dataSource. In case of a transit movement, the first 3 fields are not sufficient, you will find one record for the issue and one for the entry (with 2 different values in the field BWCOUNTER).

Regards,

Frédéric CIncet