Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8578

Re: Variable Issue

$
0
0

Hi Saideep,

 

Nice question. It will help us to think in several ways.

 

We can use same variable on Characteristic (0SEG_LEV1) and navigation attribute (0BPARTNER__0SEG_LEV1).

 

Note: The variable would have been created on one object and the same has been reflected at all places. There will not be any issue with the overall result.

  • Since we have same master data, you will get blank entries in BPARTNER case if you restrict with 0SEG_LEV1 alone - for the places where there is no PARTNER entries.
  • You will get only PARTNER related segment levels only if you restrict with 0BPARTNER__0SEG_LEV1 (v/v)

 

In the Development system, it will show warnings (with red or yellow color). But it is just for our reference and the same warnings wont come further or in execution.

 

During transports it will not give any problem, because variable originated from some master object, that would have been transported before and also it will consider developed procedure instaed of usage behaviour.

 

Hope this provide you clarification.

 

regards,

kumar


Viewing all articles
Browse latest Browse all 8578

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>