Generic R/3 Data Extraction
Generic R 3 Data Extraction
In Chapter 10, we discussed how to use Business Content's standard DataSources. In this chapter, we will describe how to use its generic R/3 data extraction capability. Generic R/3 data extraction allows us to extract virtually any R/3 data.
For example, the 0VENDOR characteristic in Business Content contains only vendor master data. The data are from R/3 table LFA1 (Screen 11.1).
If the information about a vendor in our business depends on the purchasing organization with which the vendor deals, then we must create a new vendor characteristic compounded with 0PURCH_ORG (Purchasing Organization). In R/3, the data will come from another table LFM1 (Screen 11.2). LFM1 is a join table containing vendor and purchasing organization data. It provides a reference from vendors to purchasing organizations, and vice versa.
Our goal in this chapter is to load the appropriate R/3 data into the new vendor characteristic called ZVENDOR. Its master data and text will be extracted from LFM1 and LFA1. Tables 11.1 and 11.2 list the necessary fields.
SCREEN 11.1
SCREEN 11.2
| Fields | Data Type | Length | Decimal Places | Check Table | Short Text |
|---|---|---|---|---|---|
| MANDT | CLNT | 3 | 0 | T000 | Client |
| LIFNR | CHAR | 10 | 0 | LFA1 | Vendor's account number |
| EKORG | CHAR | 4 | 0 | T024E | Purchasing organization |
| VERKF | CHAR | 30 | 0 | Responsible salesperson at vendor's office | |
| MINBW | CURR | 13 | 2 | Minimum order value | |
| ZTERM | CHAR | 4 | 0 | Terms of payment key | |
| INCO1 | CHAR | 3 | 0 | TINC | Incoterms (part 1) |
| INCO2 | CHAR | 28 | 0 | Incoterms (part 2) | |
| WAERS | CUKY | 5 | 0 | TCURC | Purchase order currency |
| Fields | Data Type | Length | Decimal Places | Check Table | Short Text |
|---|---|---|---|---|---|
| MANDT | CLNT | 3 | 0 | T000 | Client |
| LIFNR | CHAR | 10 | 0 | LFA1 | Vendor's account number |
| EKORG | CHAR | 4 | 0 | T024E | Purchasing organization |
| NAME1 | CHAR | 35 | Name 1 | ||
| NAME2 | CHAR | 35 | Name 2 | ||
| NAME3 | CHAR | 35 | Name 3 |
To link the text with the master data, the field LIFNR of the table LFA1 must be equal to the field LIFNR of the table LFM1.
As before, we will use step-by-step work instructions to demonstrate this process. The R/3 source system used in our example is release 4.0B with R/3 Plug-In PI-A 1999_1_40B patch 0004.
Note
Like other SAP products, R/3 Plug-In has its own releases and patches. The feature discussed in this chapter has not been changed in the current R/3 Plug-In release and patch, although its screens may have a slightly different appearance from those of the screens shown here.