2lis Data Sources Enhancement

[Geralyn]

Whatdo u want to enhance. If it is datasource and the fields u find them in the communication structure in LBWE (right side) then send them to leftside and activate ur datasource. No need to write any code also. If the fields are not available there do the enhancement in RSA6 append structure. Then write the code in the Exits. Then replicate in BW. Map them to the Infosource then to the cube. U can use or create relavance Infoobjects for those fields in the source and add them in the cube.

I'm new to SAP BI, I've involved in the implementation of extracting sales data from source system (ECC), from the technical spec I'm unable to figure out some fields in the communication structure of 2LIS_03_BF Data source to extract through extract structure, some of those fields are

ANS: Make sure that you write an exit code to populate the added/enahnced fields. When you fil lthe setup table ,then first check NPRT table and then in RSA3. once it is confirmed that posted data is avialable for added fields then pull the data into BW.

Thanks for your response, I've checked Application table and ROOSFIELD table of Data Source as you mentioned. In the Application table (MSEG) related to 2LIS_03_BF data source, it contain some fields (Ex: HSDAT) which are not present in the ROOSFIELD table relating to Data Source. The Fields which are present in the ROOSFIELD table are not available in the communication structure of Data Source to add them to Extract structure (Tcode: LBWE).

How can I sort out them to be available into the communication structure ? and Which fields I need to enhance ? I mean the fields which are totally not present in the Application table has to be enhanced ? or the fields which are not available in the extract structure of Data Source has to be Enhanced ?

Take abaper help and do the syntax check for above code at SE38. once you run above program, it changes properties of that field A to P and it will be visible at RSA6 or communication structure. if its available at communications tructure, you can move them to extract str at LBWE.

I've checked those fields which are present in the ROOSFIELD table and not available in the communication structure of data source. For those fields under SELECTIONS (Field Attributes) column, there is no field with attribute A (Field in OLTP and BW hidden by SAP), all are with Blank ( No Selection Possible, Visibility Set) and some are with X ( Selection Adjustable, Visibility Set).

Actually Data source will have default fields which are in blue colored at LBWE--> maintenance --> left side pane. those will be visible at of your data source at RSA6. at RSA6--> 2LIS_11_VAITM-->double click , see the fields which are present.check for your field.

Thanks for you response, I've checked as you mentioned. I've found LGTYP, PERIV and NOPOS fields in ROOSFIELDS table. And I've found APOPLANNED filed of 2LIS_11_VAITM. But I'm unable to find them in the Extract structure 'Maintenance' in LBWE.

From your spec,s find the target info cube. Thru info cube you can find the data sources which are feeding data into cube. Like that above you can check other data sources have above fields. if yes then just enhance the fields which are not part of your data sources.

Hi ADI KANTIPUDI, Right now i am doing enhancement to LO datasources.My req is= in such a way that i have to append the field to extract= structure or communication structure(MCVBAK). I am not getting= where to append, and where i can append this I mean in RSA6 r in= SE11 can u pl help me out. Thanks giri

4>>select the extractstructure it shows existing fields in left side and all fields in right side. if the requerid filed is in right side .just select the that filed and transfer it into left side. before going to do this remove the data from setup table

hi giri,

goto rsa6. find the data source. and then double click on data source and then double click on extract structure. in that screen appen structure tab is there. select that tab. then you are geting the new screen. there you should enter the requeried fields and save it.ofter that goto cmod transaction code select the project and select the componet depends on data, there you should write the apap code for those filed for picking the data .

We need to add a user-defined field to a LO-Cockpit DataSource. This field can change with no other field of the standard extract structure changing at the same time. We want this change to be registered by the DataSource's delta queue.

In the following example we will see how to add a custom field for the sales rep specified in a sales document. We will assume that the sales rep is modeled as a line-item partner function, and we will therefore enhance the DataSource 2LIS_11_VDITM (Sales Document Item Data).

Introduction

1. Enhancing the LIS communication structure

2. Customizing the extract structure

3. Implementing the extraction logic for delta process

4. Implementing the extraction logic for the initialisation run

Related content

The extraction process for the Logistics DataSources (those found in the LO Customising Cockpit, transaction code LBWE) is pretty complex. No wonder that, when you need to add a custom field to one of such DataSources, you have to pay especially carefull attention in order to avoid losing data from the DataSource's extraction or delta queues. On top of that, if your custom field is delta relevant as well, you may well end up with a broken delta process, where document changes are not always sent to the delta queue.

Here delta relevant means that when this field changes, this change should be felt by the V3 delta process, even though no additional field in the standard extract structure changes. It can be difficult to figure out exactly which steps are needed to ensure that the delta process works--although there is some good piece information around, such as this one, all in all I find the documentation available is pretty fragmented.

In the following I will concisely discuss an example which illustrates how to add a custom field for the sales rep specified in a sales document. We will assume that the sales rep is modeled as a line-item partner function, which in our example will have the value 'Z1'. We will therefore enhance the DataSource 2LIS_11_VDITM (Sales Document Item Data). I will not give details as to use the LO Customising Cockpit (LBWE) or implement an enhancement through the CMOD, though. If you need information about these tools, you should probably look for some specific documents on these topics as well. I do not even expalain the concept of before- and after-image records--should you need such information please refer to the related content section at the end of this document.

In this step we will implement the code for extracting the value of the sales rep when a sales order's line item is created, modified or deleted (delta process). In the last step, instead, we will implement the extraction logic needed when performing the initialisation of a delta process.

The code for the delta extraction has to be written into the function EXIT_SAPLMCS1_002 (this function refers to the sales orders' line items) of the enhancement MCS10001 (SIS: Statistics update, sales documents). This can be done via the transaction CMOD:

Every time a line item is changed, deleted, or added, the EXIT function is called two times: one execution step processes the status of the data before the change (before-image), while the other the status after the change (after-image).

The field YY_KAM has to be filled with the value of the sales rep before or after the change, depending on whether the record is the before- or after-image. We can figure out which record is being processed through the field i_xmcvbap-supkz--its value being 1 for the before-image or 2 for the after-image record:

Being the sales rep a partner function, its before- and after-image values will be read from internal tables YVBPA and XVBPA respectively. These two internal tables are defined and filled in the program SAPMV45A, and to access to their content we need to reference them through the ABAP instruction ASSIGN:

When users modify the sales rep in an order line item, they can enter the original value again. When this happens, the before-image and the after-image values for the field YYKAM have to be the same. In this case, however, the table YVBPA does not contain the before-image value, so we will need to fetch it from the after-image table XVBPA:

The code in the EXIT above is only run when a sales document line is created, modified, or deleted (delta process). However, that code is not executed during the initialisation of the delta process, i.e. when all data from setup tables are loaded in BW.

In order for the extraction to take place also during the initialisation run, we need to implement the same extraction logic in the function EXIT_SAPLRSAP_001 (normally used to enhance non-LO transactional DataSources) of the enhancement RSAP0001 (Customer function calls in the service API).

Since we have already implemented the extraction logic for the delta process, we have to make sure that the code we put here is executed only when data are requested in full mode--i.e. when the field i_updmode has the value 'F' (transfer of all requested data), 'C' (initialization of the delta transfer), 'S' (simulation of initialzation of delta transfer), or 'I' (transfer of an opening balance for non-cumulative values, not relevant in our case), but not when its value is 'D' (transfer of the delta since the last request) and 'R' (repetition of the transfer of a data packet):

Hey Folks.... This blog is all about SAP BI, here I want to share Important SAP BI Interview questions, Details about SAP BI Certifications, real-time scenarios and little knowledge which i earned. I think itz a nice place to share. i will try to keep Updating this blog.... If you feel some good BI stuff is fare enough to be here, please do email to bisharath...@gmail.com.... Hav fun.... Hav a nice Time....

3a8082e126