Appending fields to LIS

[Former Member]

Hi,

I am new to SAP. I have to fetch data from billing tables for which i am using LIS structures. But there are few more filed on which i need to report on which are in delivery and sales tables. Can I append these fields to the LIS strucuture using Sales Document Number as a KEY.

Rgds

[Former Member · Accepted solution]

Hi Roberto,

i am trying to enhance the Business content. I am trying to enhabce 2LIS_12_VCTIM with few fields from

VBAK, VBAP and VBRK tables.

Rgds

Nitin

[Former Member · Accepted solution]

Hi Nitin

sorry for my misunderstanding, but when we call about LIS structures we refer to the 'old' LIS structures (as the S601, S602, S603 and so on..)...

2LIS_12_VCITM is one of the so-called Logistic Cockpit datasources and you can enhance it without problem (in theory)...create an append from RSA6 for your extract structure (double-click on 2LIS_12_VCITM, double-click on his extract structure, then create the append with your ZZ* fields), then fill them with the specific user-exit EXIT_SAPLRSAP_001 (previously assigned to a project in CMOD) with some SELECT statement from your sales and billing tables !

If you want some more detail (or if you want to let me know with some details your requirements)...

Bye,

Roberto

[Former Member · Accepted solution]

Hi Roberto

It's my understanding that there's a problem with using EXIT_SAPLRSAP_001,as it doesn't pick up delta changes to the user-defined fields.

The alternative is supposed to be to use LIS customer exits to filled appended fields on the communication structures.

But how and where are LIS customer exits created?

Kate

[Former Member · Accepted solution]

Hi Kate,

you are perfectly right, with the normal exit you wil get into trouble, when dealing with "changable" fields in the enhancement (you won't get a delta update).

You speak of the MCS-enhancements (MCS10001, MCS50001, MCS60001), which can be used to enhance the MC-Structures for sales orders and so on. The infos for the enhancement are pretty good and helpful for the implementation.

But almost the same applies to this enhancements, every time you select something in your exit, which can be independently changed, you won't get an update, when its changed.

You have to be aware of this fact, when you enrich the structures with such fields.

Regards

Frank

[BerndSieger · Accepted solution]

Roberto,

you can not enhance the LO Cockpit Data Sources via RSA6. The option has been disabled in RSA6 some years ago. The reason is that the cockpit (LBWE) needs to be aware of all fields that are appended to a LO extract structure.

Otherwise regenerating the extract structure (happens when you change it via cockpit or when you upgrade the PlugIn) may result in errors or in lost fields.

If you want to enhance the LO Cockpit Data Sources please always start with appending the LIS communication structures (shown on the right hand side in the maintenance dialogue of the cockpit, e.g. MCVBAP, MCEKKO, ...).

Those appended fields will be automatically available in the cockpit. Now you only have to find a way to fill them with data (there are other posts about that in this thread).

Hope that helps,

Bernd Sieger

[Former Member · Accepted solution]

Bernd,

thanks for your suggestion, but if you want to have a survey of different available methods when you want to enhance a LC datasource, take a look to /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it ...

Anyway, you can enhance your datasource via RSA6 simply following what I described "(...) create an append from RSA6 for your extract structure (double-click on 2LIS_12_VCITM, double-click on his extract structure, then create the append with your ZZ* fields), then fill them (...)" .... in this way you can add fields, but not delta-relevant. If you enhance your communication structure (and nothing else), the problem still exists.

There is no perfect answer, but only good solution taking into account every peculiarity of your scenario.

Bye,

Roberto

[BerndSieger · Accepted solution]

Roberto,

please try your suggestion with a recent PI/PI_BASIS release. You will get the error message R8525 ("DataSource 2LIS_12_VCITM does not allow append structures").

This is true for all recent PI_BASIS releases and all Cockpit Data Sources.

Furthermore, if you would try to enhance an extract structure without the LO cockpit knowing it, you will face the following major risk:

If SAP in a future release decides to deliver a field as part of the extract structure you enhanced, that has the same name than one of the fields you appended, then the upgrade will fail with an activation error. Please have a look at my OSS note 489259, reason 1 in the solution part.

Of course this is not a risk, if you only append ZZ* fields.

Best regards,

Bernd Sieger

[Former Member · Accepted solution]

What is the equivalent MCS_enhancement for application component 17 (PM)?

[Former Member · Accepted solution]

Hi Frank, any idea for any MCS-enhancements for 2LIS_02_SCL and 2LIS_02_ITM ?

[Former Member]

Hi Nitin,

are you talkin'about the possibility to enhance your BW datasource or directly your LIS structure ?

At which LIS/Datasource are you referring to?

If you can give some additional info I will try to help you !

Bye,

Roberto

[Former Member]

Hi Siggi,

Good explanation but that still doesn't answer my question. Any ways i have rewarded some points to you.

[Former Member]

Hi,

extracting data from LIS structures to BW is a bit old fashioned. Do you really need to do this? It is better to use the new LO-extraction. For your needs, the datasources 2LIS_11_VAHDR (Sales order header), 2LIS_11_VAITM (Sales order item), 2LIS_11_VASCL (Sales order schedule line), 2LIS_12_VCHDR (delivery header) and 2LIS_12_VCITM (delivery item) would be the right ones. Almost all fields of the related transactional tables (vbak, vbap, vbfa, vbuk, vbup, likp, lips, ...) are available for extraction. And, additionally these structures are very easy to enhance.

Check out transaction LBWE for the application components 11 and 12 in your R/3 system.

If you need more information let us know.

regards

Siggi

[Former Member]

hi Siegfried,

every one opts for lo than lis.

why do u say that the lis extraction is old .is it b'cas the LO is fetching more data from r/3 or is there any speed issue too . pls clarify.

thanks.

[Former Member]

Hi,

it is old, because it was the first option to extract data to BW, release 1.2. Starting with 2.0 SAP implemented the logistics customizing cockpit (transaction lbwe) to extract logistics data. With the new extraction you can get almost every characteristic and every keyfigure you want to BW. With the old LIS-extraction, you were limited to 8 characteristics per infostructure. The LIS is posting the data redundant to the transactions in the lis tables (S001 to S499) and additionally the data is stored in BW. The new extraction does a redundant storage only temporarely. If you need more information let me know.

regards

Siggi