Recently, in one of the project, we found one issue with the Logistic extractor 2LIS_04_P_MATNR.

Initially, the setting for the extractor was looking fine. The log was saying Setup table is filled with data, but extractor was fetching '0' records in the RSA3 transaction. Whew..! So... here we will talk about the issue first and then how we found the solution with interesting facts.

About the Issue

We were struggling with the DataSource 2LIS_04_P_MATNR. The RSA3 was fetching '0' records for the extractor. We started with asking simple questions like- Have you refill Setup Tables? Is there any special settings exist for extractor in t-code SBIW and have you done it? Have you searched for the solution on SDN and Non-SDN forums? And based on the answers we started investigating the issue. Using LBWG transaction, we deleted the setup table. In the t-code, specified Application as '04' and executed. Then ran tcode OLI4BW to refill Setup table for the extractor. Here we provided Name of the Run as '2LIS04_001' (Note: This name can be anything. To check log, you will need this name in t-code NPRT). After successful refill of setup table, we checked log in t-code NPRT using 'Name Of the Run' as '2LIS04_001'.

(Fig. T-code NPRT Initial screen) Provided 'Name of Run' = '2LIS04_001' (This name had used in OLI4BW transaction) Log was saying 359 records were processed which was matching with the underlying table 'CAUFV' of the extractor 2LIS_04_P_MATNR.

(Fig. T-code NPRT screen with specific log) But still we didn't get any record in RSA3.

Solution
We checked SDN forums, blogs and articles, but we didn't find any solution for the same. But we were fortunate enough that we got some clue from one of the forum threads. (Always thankful to our great SDN!) The discussion was asking to do some settings in transaction OPL5. But what settings it didn't explain. When we ran this t-code, we didn't find any documentation for how to use this t-code. After struggling for some time, we implemented following steps. And the magic worked. The t-code RSA3 was able to fetch data. Below are the steps to implement OPL5 (in Customizing client 100)-

Run OPL5 transaction. In this transaction, you will see list of Plant and Order Types. (This extractor is related to Production Orders, so we didn't surprise to see this information in OPL5)

(Fig. T-code OPL5 Initial screen)

Select the required Plnt and Order Typesto be populated in the Production Order Extractor(s) (As this is Production Order Extractor, you will need to get list of valid Order Types and Plnts from Business).

Press 'Edit/Change' Button Double click on first Plant to be changed. You will get following screen where you will need to 'check' Updateoption. Depending on the requirement, you will need to choose other release options - Header, Item and Operation. Please see below screenshot.

(Fig. T-code OPL5 screen with Plant and Order Type details)

Press 'Save' button after updating required Plants and Order Types. It gives you pop-up for Transport request(TR). Provide TR# and proceed. This changes need to be imported to see data in client where data reside (example client 120). So run t-code SCC1 to import the above changes captured in Transport request so that the changes reflect from client 100 to 120. After following above steps, we deleted and refilled the setup table using LBWG and OLI4BW respectively. After that checked log and no. of records in NPRT. Ran RSA3 with extractor 2LIS_04_P_MATNR and surprise surprise... there were expected data returned.. Phew...!

After investigating more about OPL5 transaction, we found this t-code can be accessible through SBIW as below-

(Fig. SBIW navigation screenshot) I hope this information will help you in future. Also, please feel free to add/modify the content related to this extractor.