LO Cookpit: How to add new field into datasource 2LIS_02_ITM on R3?

[Former Member]

We've created a new field called, e.g., Z1, and we try to add this new field into the LO Cookpit datasource 2LIS_02_ITM.

Inside LBWE, click the Maintenance button for this 2LIS_02_ITM, the left frame is "Selection criteria" and the right frame is "Pool", but we don't know on how to locate our new field Z1 from this Structure Maintenance window. Then we try to click Datasource 2LIS_02_ITM change button, and then double click ExtractStruct. MC02M_0ITM to see if we can add this new field into the ExtractStruct, but get a msg at status bar that says "Function code cannot be selected".

Any idea on how to add this new field and also do we have to use customer exit to modify code to bring value of this new field into BW?

Thanks

[Former Member · Accepted solution]

Hi Kevin,

be careful when using the delta-mechanism of this datasource (and extractor).

The standard bw-exit rsap0001 is only performed during runtime of the extractor! it then gets the data out of the relevant tables. so you will have only have the current value of the RUNTIME. if this is sufficient, fine. otherwise:

the mc02m_0itm is one of the remains of the old LIS-Application.

try to fill the append in the structure by exit LEINS001 (trc smod, only one component). this is executed when the document has been saved. then you have the values in the queue as well.

or else, append the relevant table (ekpo or ekko i suppose) and in the "save_document" exit, create the pre and after images ...

related oss-note (it's sd but anyway - it works the same way): 576886

hth

cheers

sven

[Former Member · Accepted solution]

hi Sven,

We added the following code to make the added custom field ZZ work for Delta mechanism in the exit LEINS001, but find it can be only executed when filling in the setup table, but when we run RSA3 in debug mode, find it does not execute the below code at all, or in other word, running RSA3 doesn't execute this user exit LEINS001.

DATA: i_t_ekko LIKE ekko OCCURS 1 WITH HEADER LINE.

DATA: ebeln LIKE ekpo-ebeln,

it_ekko TYPE TABLE OF ekko WITH HEADER LINE,

old_val(50) TYPE c. "For storing the value from the Field Symbol

FIELD-SYMBOLS <fs> TYPE ANY TABLE.

CASE zeitp.

WHEN 'MA'. "When creating a purchase order

MOVE '(SAPLEINS)T_EKKO[]' TO old_val.

ASSIGN (old_val) TO <fs>.

i_t_ekko[] = <fs>.

LOOP AT xmcekko.

ebeln = xmcekko-ebeln.

IF xmcekko-supkz = '1'. "Old Value ?

SELECT SINGLE * FROM ekko INTO it_ekko WHERE ebeln = ebeln.

xmcekko-ZZ = it_ekko-ZZ.

ELSE. "New Value ?

READ TABLE i_t_ekko WITH KEY ebeln = ebeln.

xmcekko-ZZ = i_t_ekko-ZZ.

ENDIF.

MODIFY xmcekko.

ENDLOOP.

EndCase.

[Former Member]

you must enhance the extract structure using an append structure that contains the new field (using tcode se11)

after creare the append structure and link to the extract structure, you must populate the field with the user-exit

tcode CMOD;

[Former Member]

Hi,

The new fields are appended to the extract structure using Append Structure, wherein we need to put in the sample code . This basically defines the logic to fill these fields. The actual filling of these fields by extracting data from the tables is done through CMOD

later if you need to trace the code to see if the new field(s) filled or not, you can put a 'break-point.' in your code and run rsa3 with 'Debug' checkbox marked.

To get data - you need to enhance your datasource & extract structure & need to write your own code (exit) to fill up that field.

you can directly add this field to communication structure & through update rule can take it to Cube / ODS ( obviously you must have added it to cubde/ODS)

download pdf 'enhancements in sap bw'

here you can find the steps ...

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/59069d90-0201-0010-fd81-d5e...

Roberto's Weblog:

/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it

-Shreya

[Former Member]

hi Luigi,

What would be the name of the table when using SE11. Then in CMOD, how to locate the code?

We know how to use CMOD on other applications like FI-AP/GL, but don't have experiece of using CMOD for LO Cookpit applications.

Looking forward to seeing your answer soon!

[edwin_harpino]

hi Kevin,

actually it's the extract structure,

you can get the structure name by display the datasource (rsa6), 'extract structure'.

and you can enhance/add new fields with rsa6, double click the extract structure, then in next screen click 'append structure', the same steps like in fi-ap/gl.

also the same user exit zxrsau01 is used,

add

when '2LIS_02_ITM'.

loop at c_t_data into l_s_....

...

hope this helps.

[Former Member]

hi AHP,

You are always great! We know that we can add the new field into the Append Structure of the extract. structure MC02M_0ITM of the datasource 2LIS_02_ITM on RSA6, but we wonder what the difference between this extract stucture MC02M_0ITM in RSA6 and the Maintenance structure in LBWE? or it seems that there is no use for Maintenance structure in LBWE at all, right? Also we can't see the use of the change datasouce button in LBWE. If there is no use of these two in LBWE, then why SAP provides this screen for LO Cookpit application? We are sorry that we are pretty new at LO Cookpit application. We are expecting to give you full reward points!

Also we have added this new field into the append structure and when activating it, create a change request for it. Then come back to RSA6 screen, select the datasource 2LIS_02_ITM, and click the Transport button with a picture of truck, but get a warning msg, why?

Thanks

Message was edited by: Kevin Smith

[Former Member]

hi Shreya,

Confused by Roberto's Weblog:

/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it

In his article, he said to add a custom field, we don't have to use Maintenance structure in LBWE, but he still gives the screen of it in his article! And also wonder who he looked up his new field from the right frame of this maintenance structure? Both of the frames look like a massive confusing and we don't think it's easy to find if our new field exist in the right frame of the Maintenance Structure window of LBWE.

Looking forward to seeing your explanation!

[Former Member]

Hi Kevin,

with the LBWE you control the extraction process (based on DATASOURCE 2LIS_02_ITM that use the extract. structure MC02M_0ITM), so you can define the method of extraction (delta, delta in queue, V3 non serialized) and run or schedule the job for do it.

However, these weblog would help you,

/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146

/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur

/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods

/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it

/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis

bye Kevin,

i hope that you remeber to assign me forum point if the answer that i give you is helpful for your aspectative

[Former Member]

Maybe this link could be of some help..

cheers,

Vishvesh

[Former Member]

hi Liugi,

We know that we can add the new field into the Append Structure of the extract. structure MC02M_0ITM of the datasource 2LIS_02_ITM on RSA6, but we wonder what the difference between this extract stucture MC02M_0ITM in RSA6 and the Maintenance structure in LBWE? or it seems that there is no use for Maintenance structure in LBWE at all, right? Also we can't see the use of the change datasouce button in LBWE. If there is no use of these two in LBWE, then why SAP provides this screen for LO Cookpit application?

So far there is no anyone who can answer the above question. The article links you sent us sound complicated to us and confusing us. Just answer the above questions and we will give you full points!

Thanks

[Former Member]

hi kevin

within Logistic cockipt (LBWE) a tool is provided that enables you to add fields from the LIS communication structure (to the extract structure) without having to do any modification.

In the maintenance screen, on the left side, you see what has already beeen selected in the standard extract structure and on the right side, you see all the available fields of the communication structure where you can select fields from for the update.

bye

[Former Member]

if you use the logistic cockipt to enhance the extract structure using field already present in the comunication structure, you must populate new field using SMOD to modify the sap exit for 2LIS_02_ITM (SMOD).

Instead if you use RSA6 for enhance the extract structure with custom field (ZZ..) via append structure, in this case you must populate extra field using CMOD to modify customer exit (EXIT_SAPLRSAP_001).

note that in this case the ZZ field are not relevant for delta method; so SAP suggests to use the first enhacement

[Former Member]

hi luigi,

Currently we use RSA6 for enhance the extract structure with custom field (ZZ..) via append structure, and we populate extra field using CMOD to modify customer exit (EXIT_SAPLRSAP_001). But you say "SAP suggests to use the first enhacement", what's the 1st enhancement you are talking about? Also CMOD and SMOD should be the same thing, right? Could you elaborate 1st enhancement you suggested?

Thanks