How to use References To Customer-Specific Fields

[Former Member]

Hi,

References To Customer-Specific Fields (.ref) file, this is used for accessing the customer extension fields (Adaptation Fields in specific) into our ABSL scripts.

I need some clarifications on this, could anyone who worked with this in their previous projects help me out in clarifying the below

1. Can we use .ref file only one time in our solution, which means only one .ref file can be created and used. What all the references we are looking to use in ABSL from that file itself we have to select and use

2. After selecting and using the field in our scripts and if anyone deleted that respective field, then what would be the implication to the solution developed in the SDK and scripts which are actually using this deleted field

3. I developed .ref file in SDK of version 1508 and lets say now we will be having 1511 version up-gradation in few days, then how will this .ref file work. Will there needed any maintenance from partners to this .ref file? If yes what kind of maintenance activities are needed and will these activities are to be followed for every version change (once in every 3 months) or is it going to be a one time activity?

4. In Production how the .ref file will be used and how this will be working? The same extension fields should be created in prod tenant once again using adaptation or will they be available as of same type which we created and selected and used in our ABSL scripts with the help of a .ref file in test tenant?

5. In my test tenant I have two solutions (Soln 1 and Soln 2), where in one solution (Soln 1) I have created a .ref file for selecting one of the extension fields of Sales Order and used it in my ABSL scripting. Now I have to use the same extension field in my second solution (Soln 2) so should I create another .ref file in this second solution (soln 2) or will the first .ref file of Soln 1 suffixes the need?

6. What are the advantaged and drawbacks of this.ref file in general and is this a valid option to use the customer extension fields in our ABSL scripting?

7. Instead of using .ref file can I create a SDK extension field which I can enhance to the web services in my solution 1 and that web service can i use in other second solution to access this data of the extension field?

Out of 6 and 7 which option is the best and valid option for easy implementation and maintenance.

Please let me know in case any further detailed information needed on the above points. Looking forward for the clarifications on the above.

Regards

Hanu

[Former Member · Accepted solution]

Hi Hanu,

With respect to your questions, please see following comments:
For Q1:

You are only allow to create one .ref file per solution. And it will list all the customer extension fields for different business object contexts.

For Q2:

In fact, do not delete the fields which are referenced by .ref file, otherwise inconsistent while deployment solution. At least you'd to deselect it in the .ref file first.

For Q3.

As far as know, it should be one time action. however, since 1511 will include those fields in the solution. therefore, don know if them will be the same behaviour created in 1508, you can contact sap standard team for this.

For Q4.

if you are developing in 1508, yes, you have to create the same fields in the any target tenant you want to deploy; if you are using 1511, no, you don't need to create again any longer, as those fields will be assembled in the solution.

ForQ5:

Yes, you have to create a .ref file again to access those cusotmer extension fields in the another solution, and you can only create one ref file for each solution.

For Q6:

my first feeling for it, before 1511, the ref will have double effort for creating thos fields in target tenant. and now you don't.

For Q7.

Yes, you can do that.

For me, i'd choose SDK extesion fields to achieve that though it might be little complex.

Hope this can help you. if there is anyting incorrect, please contact experts on this topic.

Regards,

Qiang

[A-J-S]

Hi Hanumath,

1, Yes, only one .ref item can be created in a solution. You will find all the fields created using KUT in that object. Once you check any field in it you would be able to use in your coding

2, Once the field is reference in the solution then you cannot remove the field from UI, it will give you an error that it is already used. If you want to delete the field means you need to remove all its references and then remove it from UI.

3, It will be a one time activity, unless SAP comes with a different approach to KUT fields.

4, Once you create a KUT field in dev or QA then you import the same in prod tenant and then move the patch to Prod. If you do the import in Prod from QA then the same data type will be passed to Prod also. In case of manual creation you need to make sure the field is exactly the same as QA so that the patch import wont end up in error

5, No, you can use the same KUT field in different solution, not required to create two different fields.

6, KUT field is visible in all solutions and so that it can be accessed in all solutions. KUT field is for functional to extend the standard functionality

7, If you create a PDI field in one solution it cannot be accessed in a different solution, so depends on your requirement you need to choose whether its PDI or KUT. 

Thanks and Regards,

Ajith

[Former Member]

Hi Ajith,

For the point 5-6, though the KUT fields visible for all solutions, you have to create the ref file again in the second solution to access them, otherwise you cannot see them in the absl script.

For the point 7, the PDI fields can be accessed by different solution via external webservice that requires you create comm system and so on. And i agree that developer to choose the appropriate option based on custom requirement.

Regards,
Qiang

[A-J-S]

Hi Qiang,

5 and 6, Exactly, sorry for not being clear.

7, This is new to me, will try this. Thanks.

Ajith

[HorstSchaude]

Hello Ajith,

Reg. 5)

As Qiang wrote, the .ref file is oneper solution.

So if you need the Customer Specific Field in several solution you need to create this .ref once per solution.

You can mark the same field in both .ref files and by this use the same field in different solutions

Reg. 6)

Advantage: You can first create a field via the KUT and later, if you need an enahnced determination, value check or want to use the data in other scenarios, simply add the field via the .ref file to the context of the solution

Disadvantage: you need to maintain the .ref file once per solution

Reg. 7)

If you have more fields from SDK which shall be used in other solutions the WebService may be an option but IMHO it's like breaking a fly on a wheel.

HTH,

    Horst

[Former Member]

Hi Qiang, Ajith and Horst,

Thanks for these clarifications, I have a doubt on the Horst's clarification for Point 6.

Horst as you mentioned disadvantage is like we need to maintain the .ref file once per solution. Is this should be maintained one time or is it a repetitive maintenance task for every version change in those solutions where .ref file is created?

Regards

Hanu

[HorstSchaude]

Hello Hanu,

Every new patch will be based on the existing files. This means, the .ref file is also part of the new patch.

Only if you want to add more fields you need to access the .ref file.

HTH,

   Horst

[Former Member]

Any Clarifications from any member, we will be happy to go through those clarifications and make use of them in our implementations. Thanks.

Regards

Hanu

[former_member520946]

Is it possible ?to make KUT field mandatory from purchase order item level . Any one help.

Reagards,\

suresh

[Former Member]

Please can you help on this if having any idea. Thanks.

Regards

Hanu