Extractor 2LIS_03_BF

[Former Member]

Hi

During extraction (init or delta) with 2LIS_03_BF, no key figure values are updated. While checking in R/3 with transaction RSA3, fields BWAPPLNM and BWVORG are empty, so we assume that routines in update rules filter all values.

We already configured Industry Sector in SBIW, chosing "standard". We also activated NDI application in Tx BF11, and set other table entries suggested in note 315880 (TPS01 and TPS31). Finally we deleted the content of setup tables, repeated initialization process (stock initialization and setup of statistical data) and performed initial loads in BW (initial stock load with datasource BX and delta initial load with datasource BF). We are using direct delta update.

Regard

Rodrigo Araya.

[Former Member]

Hi,

Can you tell me what problem do you have now running in ?

Does this mean that you are still not able to pull data after successfull reinitializations of the 2LIS_03_BF ?

I too am studying about the same. And have gone through many documents and pdf's regarding the same.

Let me know the problem if it is still there.

Pradip.

[Former Member]

Pradip

I don´t understand what you mean to me

you have the same problem?

i solved my problem.

Regard

Rodrigo Araya

[Former Member]

I encountered a similar problem: BWAPPLNM = space and BWBREL = space in RSA3 - RSA7 when 2LIS_03_BF is running in delta extraction mode. Key figures are reset to 0 when both fields are space (instead of = MM and = 1).

we opened an OSS message and got the input back that 2 entries in table TPS31 with PROCS = 00001120 caused the problem.

Indeed removing our own customized entry solved the problem of the empty value in above fields.

We are not sorting out how to have the open_fi function module can continue to exist without 'confusing' the delta extractor of 2lis_03_bf

[Former Member]

Follow-up on my previous posting:

TPS31 was customized at the time TPS34 table was not yet available (2004).

We are now going to remove the entry from TPS31 and move it to TPS34.

[edwin_harpino]

hi Rodrigro,

check if helps oss 353042-Howto: Activate transaction key (PROCESSKEY)

Symptom

Fields BWGEO, BWGEOO, BWGVP, BWGVO, BWNETWR, BWMNG, etc. of DataSources 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_03_BF, 2LIS_03_UM, 2LIS_40_REVAL are not filled.

This may lead to the following:

The system does not perform any update into an InfoCube (for example: 0RT_C*, 0PUR_C01, 0CP_PURC1 and so on), even though data arrives in BW.

This occurs with the following InfoSources:

• 2LIS_02_SCL, 2LIS_02_ITM

• 2LIS_03_BF, 2LIS_03_UM

• 2LIS_40_REVAL

With some restriction, this symptom also occurs with the following InfoSources if they are used in connection with retail or consumer products. (InfoCube: 0RT_* or 0CP_* ).

• 2LIS_11_VAITM, 2LIS_12_VCITM, 2LIS_13_VDITM

Other terms

0PROCESSKEY, PROCESSKEY, 0RT_C01, 0RT_C02, 0RT_C03, 0RT_C04, BWBRTWR, BWGEO, BWGEOO, BWGVP, BWGVO, BWNETWR, BWMNG

Reason and Prerequisites

The process key (0PROCESSKEY and 0BWAPPLNM) of the InfoSources has not been filled. As a result, no key figures are updated because of the update routine of the participating InfoCube and along with it no records are inserted into the InfoCube. In each update routine, the system checks the content of the PROCESSKEY. If this field has no contents, then no data is written into the InfoCube because of the IF condition in the update rules.

Solution

So that you can work in the above mentioned InfoSources, you MUST activate the determination of the process key. This is done with the help of Transaction MCB_ which you can find in the OLTP IMG for BW (Transaction SBIW) in your attached R/3 source system.

Here you can choose your industry sector. 'Standard' and 'Consumer products' are for R/3 standard customers, whereas 'Retail' is intended for customers with R/3 Retail only.

You can display the characteristics of the process key (R/3 field BWVORG, BW field 0PROCESSKEY) by using Transaction MCB0.

If you have already set up historical data (for example for testing purposes) by using the setup transactions (Statistical Setup Programs) (for example: Purchasing: Tx OLI3BW, material movements: OLI1BW) into the provided setup tables (for example: MC02M_0SCLSETUP, MC03BF0SETUP), you unfortunately have to delete this data (Tx LBWG). After you have chosen the industry sector by using MCB_, perform the setup again, so that the system fills a valid transaction key for each data record generated. Then load this data into your connected BW by using 'Full update' or 'Initialization of the delta process'. Check, whether the system updates data into the involved InfoCubes now.

If all this is not successful, please see Note 315880, and set the application indicator 'BW' to active using Transaction 'BF11'.

Related notes:

157317 --> You MUST make sure that this note is relevant for you.

352344 -> Process key + reversals in Inventory Management

(Consulting note).