to find row store utilization :
SELECT round (sum(USED_FIXED_PART_SIZE + USED_VARIABLE_PART_SIZE)/1024/1024) AS "Row
Tables MB" FROM M_RS_TABLES;
Migrating tables to specified nodes in SAP HANA multi node system
by vinaysingh | Tuesday, August 06, 2013 in | comments (1)
If you want to migrate a particular table from one node of HANA to another for performance or space issue :-
1. To view current location of table -
open SQL editor on HANA studio and run the sql query :-
select * from "SYS"."M_TABLE_LOCATIONS" order by LOCATION,
table_name
2. To view current location decide the node where you want to move it and run the below query on SQL editor of HANA studio:-
ALTER TABLE MOVE TO ‘node:port number’
SD Foreign Trade vs. SAP Global Trade Services (GTS)
by vinaysingh | Saturday, August 25, 2012 in | comments (30)
Dear Reader,
we have moved to a better platform , you can find the Blog now at:-
http://www.sapyard.com/sd- foreign-trade-vs-sap-global- trade-services-gts/
thanks for reading our blogs . We hope you would like our new platform.
regards,
vinaysingh
we have moved to a better platform , you can find the Blog now at:-
http://www.sapyard.com/sd-
thanks for reading our blogs . We hope you would like our new platform.
regards,
vinaysingh
Steps to add custom Tab in standard MIRO item screen using BADI MRM_ITEM_CUSTFIELDS
by Raju | Thursday, July 05, 2012 in custom Tab in MIRO, MRM_ITEM_CUSTFIELDS | comments (7)
We are moving to a better and faster site SAPYard.com (http://www.sapyard.com/).
The content has been moved to below link. Please visit it at your convenience. Thank you for all your cooperation.
PO re-price issue in BAPI_PO_CHANGE
by Raju | Thursday, July 05, 2012 in BAPI_PO_CHANGE issue, CALCTYPE, Opt. entry, Pr Date Cat, Pricing date control, RE-PRICE | comments (0)
We are moving to a better and faster site SAPYard.com (http://www.sapyard.com/).
The content has been moved to below link. Please visit it at your convenience. Thank you for all your cooperation.
http://www.sapyard.com/po-re-price-issue-in-bapi_po_change/
1) Use of user validation and preferably with a control table.
2) Code should be written in the custom include and not in the enhancement.
3) In case same user exit, BADI or form routine is used for more than one changes, it is better to save the custom include in separate transports. The custom include should have the syntax 'IF FOUND'.
4) No CHECK statement should be used.
5) SAP internal tables should not be sorted in the custom logic
6) If entry is being read from the stack, please check whether the value is assigned to the field symbol or not.
7) Some form routines likes MV45AFZZ does not have 'Fixed Point arithmetic' check. Beware of that and make adjustments in your calculations
8) Unless and until required, do not give an error message from an ehancement
I will update the list if I remember more
Often we need to convert the system time to local time of the plant and if the local time of the plant observes day light then result is 1 hour off sometimes. This problem occurs due to time difference of daylight saving. If you are facing this problem (like me) then please check your DST system using transaction STZBC.
Fig1 - First check whether Daylight rule is active or not.
Fig2 Check the rule (Variable summer time rule)
Fig3 Check the rule (Fixed summer time rule)
Let us know if this was helpful.
Fig1 - First check whether Daylight rule is active or not.
Fig2 Check the rule (Variable summer time rule)
Fig3 Check the rule (Fixed summer time rule)
Let us know if this was helpful.
Subscribe to:
Posts (Atom)


