cancel
Showing results for 
Search instead for 
Did you mean: 

Generating datasource

Former Member
0 Kudos

Hi Gurus

We have 2 clients in R/3 DEV and I need to append the extractor of 2LIS_03_BF in one client and then need to generate the datasource in other client , I am not sure how should I proceed . So would you pl tell me what I need to do ?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

What do you mean by 'generating datasource'? You can append fields and modify DS in RSA6 in one client, and, use the datasource in another (ie after following the usual setup of update activation etc in LBWE).

Former Member
0 Kudos

Ajay

we 2 clients in R/3 Dev ..A and B.we do ABAP work in client A and config in client B. now I have added few fields which are available in standard CS of datasource but we need some more customized field for which we need to write ABAP / user exit. now I have added those field in client B , the ABAPer is not able to create user exit for new fields in client A so he wants me to append the extrac in client A and then asked me to generate DS in client B.

So i am confused as to what I need to do in client A?

one more question is if I have some transport then no body other can save his work in the same request? if no then do I need to change the ownership to let the person do that?

Pl help.

Former Member
0 Kudos

1 - What you append to a structure is visible in all clients, a structure is not client-dependent. As such, if you add fields to an extract structure in client B, it should be visible in client A. (Check the datasource in client A and B, or table entries in ROOSOURCE and ROOSFIELD in both clients to verify).

Abaper should accordingly be able to write the user-exit in client A, even if the extract structure was extended in B.

- To your second question - one object, while being modified by one user, can not be modified by other, you will need to change the ownership in SE01 or SE09. It will not work if it is in different clients (ie if you changed object X in client B and now want another user to work on it in client A, this will not be possible. You will need to release the request in client B and then it can be changed in another client. Since repository objects are client independent your changes done in another client will remain there.).

Former Member
0 Kudos

Thnaks Ajay

Full points given

KK

Answers (0)