Hi Jolin,
Its not a good practice of creating characteristics and value fields directly in PRD server. In future, if someone handles the same by transporting from DEV to PRD, system will overwrite. In your case its outdated data in DEV server will move to PRD and leads to many complications. At least make of document of this for future reference how you are making changes in production server.
BR, Srinivas Salpala
Check this Note : 1149556 - Characteristic ... has no master data for "..."
Una consulta alguien me podria explicar porque no existe la tabla RITL dentro de la base de datos, tengo instalado SBO 882 PL-09
Trato de visualizar la informacion del sistema RITL,CardName y aparentemente me da el nombre de la tabla y campo pero cuando realizo un select * from RITL no existe.
Hi Anshu,
Still I couldnt tested this in Production, I will do that and let you know.
Hi Igno,
Thanks for your response, Yes it is BI4.
We have variable on 0Calday, but this has been defined as a optional variable, not a mandatory variable. No exits are using on this query.
Thanks,
Venu
Hi Rabi,
Lets wait for Anil's Response. If he is generating with Time Evaluation The radio button need to click or it is not required to click on "Increase" radio button.
We will do our best to resolve issue.
Hi,
In the First Component WD1 of Window WD1_W right click on View 2 WD1_V2 and set it as default.
If you are using WD1 for some other purposes where V1 should be Default view, Create another Window in WD1 (say WD1_W2) and in that drag and drop V2 and make it as default.
Then call WD1_W2 from WD2.
Hope this helps u.,
Regards,
Kiran
Hi Venu,
At table ROOSFIELD, enter data source name and keep SELECTION as "A". execute the it check the out put. if you won't get list mean no fields are hidden.
again check the table contents, remove SELECTION "A" and just enter data source name and display table out put.
What ever the field are in that table those fields will be visible at RSA6(other than Hidden fields).
if not showing like that, if you see fields at LBWE, maintenance , Right side pane Communication str.
Move them to left.
Even if not seen what you need, then deactivate data source. again activate data source from RSA5 and do as you done at first time. do this on dev system only.
Thanks
Hi Paul,
You can directly test the function module at SE37, give the inputs and test it.
You have two place to apply this FM, 1. PSA to DSO Level transformation
2. DSO to Cube level transformation.
If your not doing reporting DSO, then you can routine between DSO to Cube level, do on Dev system and check. once it fine then move the same changes to production.
Thanks
Hi,
You cannot pass bulk data like structure or internal table through URL parameters. Why don't you use the other component in your component via Component usage.
Check the Component Usage Tutorial here: http://scn.sap.com/docs/DOC-8863
If you don't want to use the Component usage, pass the data using shared memory objects. Check my document here: http://scn.sap.com/docs/DOC-27396
The above mentioned Import/Export memory won't work in Web Dynpro context.
Hope this helps u.,
Regards,
Kiran
Hi Selva kumar,
What about BOM and it's components? Whether you have activated backflush for BOM components? IF yes, please check any incorrect movements in COGI. What about the production order status? Whether you have done any GI, Confirmation or GR? If yes, cancel all those movements and try again.
Thanks
HI,
Enter the (100)Last Number in Primary Series.
Thanks,
Nithi
Hi Andriy,
Check below Screen Shot ,are you maintain 'rfcexec' in program name ?
then test your RFC destination , you getting below message .
Check this link ...SAP Library - TREX - Configuration Documentation
Program Name : <disk_drive>:\usr\sap\ECC_<instance_number>\rfcexec.exe
Gateway Host : Host name (with domain name if necessary) or
the IP address of the host on which the gateway is installed.
Gateway Service: Name of the gateway in the form sapgw<instance_number>
Regard's
Smruti
Have you maintained the technical settings for survey as given below:-
Thanks
Kumar
Hi Venkat,
Seems like MD2 is primary one, MD1 is reference of MD2. if yes then you may be loaded data to MD2 properly and activate master data.
At info cube level if you added MD1, at transformations you may chose as read master data. Your MD1 object will be filled at cube level. once you do report you can access what you need.
What ever you have info object(think so - MD1 iobj) at cube level, need to be filled.
Thanks
1. How do I need to create the Authorization?
Currently we work with Menu- and Auth Roles with the corresponding Analysis Authorization.
Follow this wonderful doc http://scn.sap.com/docs/DOC-11451
2. Is there an easier way of creating/maintaining the Authorizations if we work with Info-Object-Catalogs?
Do we still need Menu-, Auth Role and Analysis Authorization?
You can't create authorizations on catalogues. You still need Menu, Roles, Authorization Profiles and Analysis Auth..
3. Are we able to restrict User in such a way that in one report
- the User will have access for all company codes and restrictions on Profit center
- but in another report has restriction to one company code and no restriction to Profit center but on business area?
Yes it is possible. You have to create separate roles and give access as per your requirement. You have to assign same report with different authorizations to two roles.
4. If we need to stay with Menu- and Auth Role with Analysis Authorization:
What is the advantage of giving Authorization by Info Object catalog?
The maintanance of Menu- and Auth Role will be low but the maintanance of the User profile's will be big.
As I said, it is not possible to give authorization by catalogue. It is only possible by individual objects like Infoobject, Inforpoviders etc..
Regards,
Suman
Hi,
System determines Company data using a Function module FI_CUSTOMER_DATA in which Customer used is Sold to party
please find the attachment
Hi Ramesh,
As spotted by Ambrish and Aaron, I see the same thing that the Collapse context will collapse the complete queue value but top one and therefore you will run the if condition only once.
That is why you find values for first queue the second repetition of your source structure wont be checked as required.
Regards,
Nipun
About below 2 tables:
V_T001W_MV
+ V_T001K_CCS
do I need to do anything in normal scenarios?
Dear All,
We are using positive Time Management,
The requirement is in IT2011, if there is no record stored, the day need to treated as loss of pay,
My client's Annual leave quota is 18 days, and it's calculates pro rata basis as monthly 1.5 days,
In a month If an Employee takes Annual leave more than 1.5 days, the rest of days should treat as Loss of pay,
For Example :
In a month employee take 3 days Annual leave,
First 1.5 days (Quota entitled) it's calculate correctly,
Rest of 1.5 days make system calculate as Loss of pay,
That mean in a day if there is no record stored like IT2001, IT2002, IT2003 & IT2006 system need to treat the day as loss of pay,
Please provide the information to reach above scenario,
Thanks & Regards,
Prabu.
Hi Vasanth,
As far as I know and understood The Concept is :
It depends on HANA Landscape, from your picture - I can assume that - its a shared disk storage which is connected with different nodes of HANA within the same HANA site.
SPS05 - Onwards
For more detail you can also refer HA on SPS06 : Introduction to High Availability for SAP HANA | SAP HANA
The SAP HANA database system supports high availability with a failover scenarios for hosts. It is possible to have standby hosts that can take over if an active host should fail – for example because of hardware failure. The standby hosts work in “cold” standby mode. This means that they just register with the Master Name Server and wait.
As long as they are in standby mode the Index Servers on these hosts do not contain any data and do not receive any requests. When an active host fails, this is detected by the Master Name Server which selects a standby host to take over. The Index Server on the selected standby host takes over the database volumes of the failed Index Server and loads the data into memory by executing the restart sequence.
Assigning the volumes of the failed host to the standby host requires having the database volumes on a shared storage server. Therefore this high availability scenario is called cold
standby with shared storage.
For large amount of data, loading the data into memory during failover may take considerable time. In “hot” standby mode, the standby server would be kept close to the state of the original server to allow a very fast takeover. This would require replicating all changes to the standby server during normal operation, for example by replicating the transaction logs and replaying them on the standby server. But what happens if the host with the Name Server fails? To ensure high availability of the Master Name Server, up to two Slave Name Servers can act as backup Master Name Servers. If the current Master Name Server fails, the backup Master Name Server
takes over. If two backup Master Name Servers are configured, they negotiate and one of them takes over the role of the Master Name Server. The new master then performs a restart from the persisted data and transaction logs of the old master. This is similar to the process described above for the Index Servers. You may wonder why the new Master Name Server needs to restart?? As a former slave server it received all data already via replication. The reason is transactional consistency: replication is not guaranteed to be immediately consistent. The most recent changes might be missing in the slave name server. Only by restarting from the persisted data it can be assured that all committed changes are restored.
Regards
Kumar
