Problem with Time stamp function module for converting US to Japan

Hi All,
I need standard function module for converting US Timestamp to Japan, Can any one let me know is there any standard function modules.
thanks in advance!
Regards,
Kalidas.T
Edited by: Kalidas Thirumoorthy on May 5, 2009 5:29 PM
Edited by: Kalidas Thirumoorthy on May 5, 2009 5:30 PM
Edited by: Kalidas Thirumoorthy on May 5, 2009 5:30 PM

Try this way:
CONVERT TIME STAMP <tst> TIME ZONE <tz> INTO DATE <d> TIME <t>.
CONVERT DATE <d> TIME <t> INTO TIME STAMP <tst> TIME ZONE <tz>.
<tst> is of type P(8) or P(11) with 7 decimal places
<tz> of type C(6)
Refer to help.sap.com for more details.

Similar Messages

Function module for converting weight unit to another unit.

What is the function module for converting weight unit to another unit.
I want to convert LB to KG.
Tried with fm UNIT_CONVERSION_SIMPLE.
INPUT                           100
NO_TYPE_CHECK
ROUND_SIGN                      X
UNIT_IN                         LB
UNIT_OUT                        KG
But there is no output.
Can some one help.

The trick here is we need decalre input output with non-character data type like VBPLK-BRGEW.
We can test using normal SE37.
I tested and this program worked fine:
   data: UNIT_IN LIKE T006-MSEHI,
       UNIT_OUT LIKE T006-MSEHI,
       output LIKE VBPLK-BRGEW,
       input LIKE VBPLK-BRGEW.
input = 10.
CALL FUNCTION 'UNIT_CONVERSION_SIMPLE'
       EXPORTING
            INPUT    = INPUT
            UNIT_IN = 'LB' "UNIT_IN
            UNIT_OUT = 'KG' "UNIT_OUT
       IMPORTING
            OUTPUT   = OUTPUT.
write: output.

Function module for converting the foreign currency to words

hi,
can anybody tell me about the function module for converting the foreign currency to words format.
Like 25.50 USD
should be "Twenty Five Dollar & Fifty Sents."
foreign currency can be anyone like USD, JPY, EUR etc.
Regards
Nitin Varshney

Hi,
Try using the FM SPELL_AMOUNT
Check this wiki
[SPELL_AMOUNT|https://wiki.sdn.sap.com/wiki/display/Snippets/SpelltheAmountenteredin+words]
Regards
Sarves

Function module for converting number to exponential???

Hi All
please tell me Function module for converting number to exponential.
Deepak

try:
REPORT Zconvertf.
parameters p1 type p decimals 2 default '4711.99'.
data f1 type f.
move p1 to f1.
write: / p1, f1.
hope that helps
Andreas

Function modules for converting Char value to hexadecimal value

Hi All,
Function modules for converting Char value to hexadecimal value.
Thanks in advance

Hi,
use this function module:
RSS_UNIQUE_CONVERT_TO_HEX
regards
Debjani
Rewards point for helpful answer

Function module for converting sap script to smartforms?

hi ,
wat is the name of function module for converting sap script to smartforms?
regard's
Deepak sharma

Hi,
No function module is there..
But go to T-code..Smartforms and in the menubar..
Utilities-->Migration->Import SApScript Form.
U can thus migrate SAPScipt to smartforms...
How ever a lot of changes have to be done in the migrated one,,
Regards

Need Function Module for convertion of Foreign currency to Indian currency

hi friends,
i need function module for converting amount from
Foreign currency to Indian currency
thanks

hi Venkat,
Please use the function module CONVERT_TO_LOCAL_CURRENCY
Sample code:
 call function 'CONVERT_TO_LOCAL_CURRENCY'
 exporting
 date = p_alv_tab-begda
 foreign_amount = p_alv_tab-kkost_p_person
 foreign_currency = p_alv_tab-kwaer " foreign currency
 local_currency = l_ev_waer " Indian currency
 importing
 local_amount = p_alv_tab-kkost_p_person
 exceptions
 no_rate_found = 1
 overflow = 2
 no_factors_found = 3
 no_spread_found = 4
 others = 5.
Hope this helps,
Sajan Joseph.

Function module for convert date as sap internal format ?

Hi All,
Is there any standard function module to convert the date filed as SAP internal date?
My problem is while uploading data from excel sheet date filed can be any format
for exp: dd/mm/yyyy or mm/dd/yyyy or yyyy/dd/mm or dd-mm-yyyy,mm-dd-yyyy
             dd-mm-yyyy or dd.mm.yyyy or mm.dd.yyyy etc...
In our case there is no particular format in excel it can be differ for each user. I know we have few FM's in standard.
But those are not working for my req. pls help me if you have any idea.
Thanks in advance.
Regards,
Venkat Mote.

Hi Venkatesh,
Can you please check with the following function module. For my case, it is working fine.
CALL FUNCTION 'CONVERT_DATE_TO_INTERN_FORMAT'
EXPORTING
    datum = p_gs_date
    dtype = 'DATS'
IMPORTING
    idate = p_gs_date
Hope it helps to you.
Regards
Rajkumar Narasimman

Problem with IDOC inbound function module

hi
 While excecuting the inbound function module in WE19
I am getting error (short dump)
Incorrect parameter with Call transaction.

Creating a Function Module (Direct Inbound Processing)
This step describes how to create a function module which is identified by the IDoc Interface using a new process code and called from ALE (field TBD52-FUNCNAME). Direct inbound processing using a function module (not using a workflow) always includes the ALE layer. This setting (processing with function module and ALE layer) is identified by the value 6 in the field TEDE2-EDIVRS, which is read by the function module IDOC_START_INBOUND. IDOC_START_INBOUND then calls ALE.
Prerequisites
You must have completed the required steps in Defining and Using a Basic Type .
Procedure
Choose Tools ® ABAP Workbench ® Development ® Function Builder, and create a new function module.
Create the segments as global data in your function group. The function module should copy the application data from the segments into the corresponding application tables and modify the IDoc status accordingly. If an error occurs, the function module must set the corresponding workflow parameters for exception handling.
Activate the function module: From the initial screen of the Function Builder select .
In the example, create the function module IDOC_INPUT_TESTER with a global interface. The function module is called when an IDoc of type TESTER01 is received for inbound processing. You will assign an application object ("standard order") to this IDoc type and therefore maintain tables from SD. To do this, call transaction VA01 using the command CALL TRANSACTION. Please note that the intention here is not to simulate a realistic standard order, but only to illustrate how data reaches application tables from an IDoc table via segment structures (form routine READ_IDOC_TESTER) and how the function module triggers an event for exception handling (by returning suitable return variables to the ALE layer in the FORM routine RETURN_VARIABLES_FILL).
A comprehensive example of the code for an inbound function module is provided in the ALE documentation in the SAP Library under Example Program to Generate an IDoc. This function module, for example, also checks whether the logical message is correct and calls a (fictitious) second function module which first writes the application data and then returns the number of the generated document. In addition, status 53 is only set if the application document was posted correctly.
Administration parameters for IDOC_INPUT_TESTER
Application abbreviation
V (Sales and Distribution)
Processing type
Normal, start immediately
Interface for IDOC_INPUT_TESTER (global interface)
Formal parameters
Reference structure
Explanation
Import parameters
INPUT_METHOD
BDWFAP_PAR-INPUTMETHD
Describes how the function module is to be processed (example: in the background)
MASS_PROCESSING
BDWFAP_PAR-MASS_PROC
Mass inbound processing? (indicator)
Export parameters
WORKFLOW_RESULT
BDWFAP_PAR-RESULT
Set to 99999 if an event is to be triggered for error handling.
APPLICATION_VARIABLE
BDWFAP_PAR-APPL_VAR
Variable freely available from application for workflow
IN_UPDATE_TASK
BDWFAP_PAR-UPDATETASK
Asynchronous update? (indicator is not set in example)
CALL_TRANSACTION_DONE
BDWFAP_PAR-CALLTRANS
Transaction called? (indicator is not set in example)
Table
IDOC_CONTRL
EDIDC
IDoc control record
IDOC_DATA
EDIDD
IDoc data records
IDOC_STATUS
BDIDOCSTAT
IDoc status records for ALE
RETURN_VARIABLES
BDWFRETVAR
IDoc assigned to Object type method parameters.
SERIALIZATION_INFO
BDI_SER
If several IDocs are to be processed in a certain sequence: this structure contains the necessary information
Example
FUNCTION IDOC_INPUT_TESTER.
""Globale Schnittstelle:
*" IMPORTING
*" VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*" VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*" VALUE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*" VALUE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*" VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*" VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*" IDOC_CONTRL STRUCTURE EDIDC OPTIONAL
*" IDOC_DATA STRUCTURE EDIDD
*" IDOC_STATUS STRUCTURE BDIDOCSTAT
*" RETURN_VARIABLES STRUCTURE BDWFRETVAR
*" SERIALIZATION_INFO STRUCTURE BDI_SER
initialize SET/GET Parameter and internal tables
PERFORM INITIALIZE_ORGANIZATIONAL_DATA.
Move IDOC to internal tables of application
PERFORM READ_IDOC_TESTER.
call transaction Order Entry VA01
PERFORM CALL_VA01_IDOC_ORDERS USING ERRORCODE.
set status value
perform write_status_record using errorcode.
return values of function module
PERFORM RETURN_VARIABLES_FILL USING ERRORCODE.
ENDFUNCTION.
FORM INITIALIZE_ORGANIZATIONAL_DATA.
initialize SET/GET parameters
 SET PARAMETER ID 'VKO' FIELD SPACE.
 SET PARAMETER ID 'VTW' FIELD SPACE.
 SET PARAMETER ID 'SPA' FIELD SPACE.
 SET PARAMETER ID 'VKB' FIELD SPACE.
 SET PARAMETER ID 'VKG' FIELD SPACE.
initialize internal tables
 REFRESH BDCDATA.
 CLEAR BDCDATA.
 CLEAR BELEGNUMMER.
 CLEAR ERRTAB.
 REFRESH ERRTAB.
 REFRESH XBDCMSGCOLL.
 CLEAR XBDCMSGCOLL.
ENDFORM. " INITIALIZE_ORGANIZATIONAL_DATA
FORM READ_IDOC_TESTER.
PERFORM INITIALIZE_IDOC.
LOOP AT IDOC_DATA
 WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
 CASE IDOC_DATA-SEGNAM.
header data
 WHEN 'E1HEAD'.
 MOVE IDOC_DATA-SDATA TO E1HEAD.
 PERFORM PROCESS_SEGMENT_E1HEAD.
position data
 WHEN 'E1ITEM'.
 MOVE IDOC_DATA-SDATA TO E1ITEM.
 PERFORM PROCESS_SEGMENT_E1ITEM.
 ENDCASE.
ENDLOOP.
only when there were one or more items
CHECK FIRST NE 'X'.
APPEND XVBAP. "last one
ENDFORM. " READ_IDOC_TESTER
FORM INITIALIZE_IDOC.
CLEAR XVBAK.
REFRESH XVBAP.
CLEAR XVBAP.
POSNR = 0.
FIRST = 'X'.
ENDFORM. " INITIALIZE_IDOC
FORM PROCESS_SEGMENT_E1HEAD.
requested date of delivery
WLDAT = E1HEAD-WLDAT.
delivery date
XVBAK-BSTDK = E1HEAD-BSTDK.
customer number
XVBAK-KUNNR = E1HEAD-AUGEB.
order number
XVBAK-BSTNK = E1HEAD-BELNR.
division
XVBAK-SPART = E1HEAD-SPART.
distribution channel
XVBAK-VTWEG = E1HEAD-VTWEG.
sales organization
XVBAK-VKORG = E1HEAD-VKORG.
order type
XVBAK-AUART = E1HEAD-AUART.
do not fill incoterms (inco1, inco2)
customer function
CALL CUSTOMER-FUNCTION '001'
 EXPORTING
 PI_VBAK621 = XVBAK
 IMPORTING
 PE_VBAK621 = XVBAK
 TABLES
 PT_IDOC_DATA_RECORDS = IDOC_DATA.
ENDFORM. " PROCESS_SEGMENT_E1HEAD
FORM PROCESS_SEGMENT_E1ITEM.
position number
XVBAP-POSNR = XVBAP-POSNR + 1.
amount
XVBAP-WMENG = E1ITEM-MENGE.
unit
CALL FUNCTION 'ISO_TO_SAP_MEASURE_UNIT_CODE'
 EXPORTING
 ISO_CODE = E1ITEM-BMEINH
 IMPORTING
 SAP_CODE = XVBAP-VRKME
 EXCEPTIONS
 OTHERS = 0.
material number
XVBAP-MATNR = E1ITEM-LMATNR.
CALL CUSTOMER-FUNCTION '002'
 EXPORTING
 PI_VBAP621 = XVBAP
 IMPORTING
 PE_VBAP621 = XVBAP
 TABLES
 PT_IDOC_DATA_RECORDS = IDOC_DATA.
APPEND XVBAP.
ENDFORM. " PROCESS_SEGMENT_E1ITEM
FORM CALL_VA01_IDOC_ORDERS USING ERRORCODE.
call transaction first dynpro
PERFORM DYNPRO_START.
call transaction double-line entry
PERFORM DYNPRO_DETAIL2.
incoterms
PERFORM DYNPRO_HEAD_300.
call transaction item datas
PERFORM DYNPRO_POSITION.
PERFORM DYNPRO_SET USING 'BDC_OKCODE' 'SICH'.
determine input method
IF INPUT_METHOD IS INITIAL.
 INPUT_METHOD = 'N'.
ENDIF.
call transaction VA01
CALL TRANSACTION 'VA01' USING BDCDATA
 MODE INPUT_METHOD
 UPDATE 'S'
 MESSAGES INTO XBDCMSGCOLL.
errorcode = SY-SUBRC. " remember returncode for status update
ENDFORM. " CALL_VA01_IDOC_ORDERS
form write_status_record using errorcode.
FILL IDOC_STATUS
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IF ERRORCODE = 0.
IDOC_STATUS-STATUS = BELEG_GEBUCHT. "value 53
 GET PARAMETER ID 'AUN' FIELD BELEGNUMMER.
 IDOC_STATUS-MSGID = 'V1'.
 IDOC_STATUS-MSGNO = '311'.
 IDOC_STATUS-MSGV1 = 'Terminauftrag'.
 IDOC_STATUS-MSGV2 = BELEGNUMMER.
ELSE.
 IDOC_STATUS-STATUS = BELEG_NICHT_GEBUCHT. "value 51
 IDOC_STATUS-MSGID = SY-MSwGID.
 IDOC_STATUS-MSGNO = SY-MSGNO.
 IDOC_STATUS-MSGV1 = SY-MSGV1.
 IDOC_STATUS-MSGV2 = SY-MSGV2.
 IDOC_STATUS-MSGV3 = SY-MSGV3.
 IDOC_STATUS-MSGV4 = SY-MSGV4.
ENDIF.
APPEND IDOC_STATUS.
ENDFORM.
FORM DYNPRO_START.
PERFORM DYNPRO_NEW USING PROGRAMM_AUFTRAG
 DYNPRO-EINSTIEG
 CHANGING LAST_DYNPRO.
ordertype
PERFORM DYNPRO_SET USING 'VBAK-AUART' XVBAK-AUART.
sales organization
PERFORM DYNPRO_SET USING 'VBAK-VKORG' XVBAK-VKORG.
Distribution channel
PERFORM DYNPRO_SET USING 'VBAK-VTWEG' XVBAK-VTWEG.
Division
PERFORM DYNPRO_SET USING 'VBAK-SPART' XVBAK-SPART.
Sales office
PERFORM DYNPRO_SET USING 'VBAK-VKBUR' XVBAK-VKBUR.
Sales group
PERFORM DYNPRO_SET USING 'VBAK-VKGRP' XVBAK-VKGRP.
ENDFORM. " DYNPRO_START
FORM DYNPRO_NEW USING PROGNAME
 DYNPRONR
 CHANGING LAST_DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGNAME.
BDCDATA-DYNPRO = DYNPRONR.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
LAST_DYNPRO = DYNPRONR.
ENDFORM. " DYNPRO_NEW
FORM DYNPRO_SET USING FELDNAME
 FELDINHALT.
CLEAR BDCDATA.
CHECK FELDINHALT NE SPACE.
dynpro field name
BDCDATA-FNAM = FELDNAME.
contents
BDCDATA-FVAL = FELDINHALT.
APPEND BDCDATA.
ENDFORM. " DYNPRO_SET
FORM DYNPRO_DETAIL2.
okcode
PERFORM DYNPRO_SET USING 'BDC_OKCODE' PANEL-UER2.
fix dynpro number 4001
PERFORM DYNPRO_NEW USING PROGRAMM_AUFTRAG
 '4001'
 CHANGING LAST_DYNPRO.
order party
PERFORM DYNPRO_SET USING 'KUAGV-KUNNR' XVBAK-KUNNR.
purchase order number
PERFORM DYNPRO_SET USING 'VBKD-BSTKD' XVBAK-BSTNK.
requested delivery date
PERFORM DYNPRO_DATE_SET USING 'VBKD-BSTDK' XVBAK-BSTDK.
purchase order date
PERFORM DYNPRO_DATE_SET USING 'RV45A-KETDAT' WLDAT.
ENDFORM. " DYNPRO_DETAIL2
FORM DYNPRO_DATE_SET USING FELDNAME
 FELDINHALT.
DATA: DATE TYPE D.
CLEAR BDCDATA.
CHECK FELDINHALT NE SPACE.
BDCDATA-FNAM = FELDNAME.
WRITE FELDINHALT TO DATE.
BDCDATA-FVAL = DATE.
APPEND BDCDATA.
ENDFORM. " DYNPRO_DATE_SET
FORM DYNPRO_HEAD_300.
PERFORM DYNPRO_SET USING 'BDC_OKCODE' PANEL-KKAU.
incoterms part 1
IF NOT XVBAK-INCO1 IS INITIAL.
 PERFORM DYNPRO_SET USING 'VBKD-INCO1' XVBAK-INCO1.
ENDIF.
incoterms part 2
IF NOT XVBAK-INCO2 IS INITIAL.
 PERFORM DYNPRO_SET USING 'VBKD-INCO2' XVBAK-INCO2.
ENDIF.
PERFORM DYNPRO_SET USING 'BDC_OKCODE' 'BACK'.
ENDFORM. " DYNPRO_HEAD_300
FORM DYNPRO_POSITION.
LOOP AT XVBAP.
dynpro item double line entry
PERFORM DYNPRO_SET USING 'BDC_OKCODE' 'UER2'.
 IF XVBAP-POSNR = 1.
material number
 PERFORM DYNPRO_SET USING 'VBAP-MATNR(01)' XVBAP-MATNR.
order quantity
 PERFORM DYNPRO_SET USING 'RV45A-KWMENG(01)' XVBAP-WMENG.
desired delivery date
 PERFORM DYNPRO_DATE_SET USING 'RV45A-ETDAT(1)' WLDAT.
sales unit
 PERFORM DYNPRO_SET USING 'VBAP-VRKME(1)' XVBAP-VRKME.
 ELSE.
 PERFORM DYNPRO_SET USING 'BDC_OKCODE' 'POAN'.
material number
 PERFORM DYNPRO_SET USING 'VBAP-MATNR(02)' XVBAP-MATNR.
order quantity
 PERFORM DYNPRO_SET USING 'RV45A-KWMENG(02)' XVBAP-WMENG.
desired delivery date
 PERFORM DYNPRO_DATE_SET USING 'RV45A-ETDAT(02)' WLDAT.
sales unit
 PERFORM DYNPRO_SET USING 'VBAP-VRKME(02)' XVBAP-VRKME.
 ENDIF.
ENDLOOP.
ENDFORM. " DYNPRO_POSITION
FORM RETURN_VARIABLES_FILL USING ERRORCODE.
allocate IDOC numbers to Workflow output parameters
IF MASS_PROCESSING <> SPACE.
 IF ERRORCODE = 0.
 RETURN_VARIABLES-WF_PARAM = PID.
 RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
 APPEND RETURN_VARIABLES.
 RETURN_VARIABLES-WF_PARAM = APO.
 RETURN_VARIABLES-DOC_NUMBER = BELEGNUMMER.
 APPEND RETURN_VARIABLES.
 WORKFLOW_RESULT = C_WF_RESULT_OK.
 ELSE.
 RETURN_VARIABLES-WF_PARAM = EID.
 RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
 APPEND RETURN_VARIABLES.
 WORKFLOW_RESULT = C_WF_RESULT_ERROR.
 ENDIF.
ELSE.
 IF ERRORCODE = 0.
 RETURN_VARIABLES-WF_PARAM = APE.
 RETURN_VARIABLES-DOC_NUMBER = BELEGNUMMER.
 APPEND RETURN_VARIABLES.
 WORKFLOW_RESULT = C_WF_RESULT_OK.
 ELSE.
 WORKFLOW_RESULT = C_WF_RESULT_ERROR.
 ENDIF.
ENDIF.
ENDFORM. " RETURN_VARIABLES_FILL
Globale Daten von IDOC_INPUT_TESTER
TABLES: E1HEAD, E1ITEM.
DATA: BEGIN OF BDCDATA OCCURS 500.
 INCLUDE STRUCTURE BDCDATA.
DATA: END OF BDCDATA.
DATA: BEGIN OF XVBAK. "Kopfdaten
 INCLUDE STRUCTURE VBAK621.
DATA: END OF XVBAK.
DATA: BEGIN OF XVBAP OCCURS 50. "Position
 INCLUDE STRUCTURE VBAP.
DATA: WMENG(18) TYPE C.
DATA: LFDAT LIKE VBAP-ABDAT.
DATA: KSCHL LIKE KOMV-KSCHL.
DATA: KBTRG(16) TYPE C.
DATA: KSCHL_NETWR LIKE KOMV-KSCHL.
DATA: KBTRG_NETWR(16) TYPE C.
DATA: INCO1 LIKE VBKD-INCO1.
DATA: INCO2 LIKE VBKD-INCO2.
DATA: YANTLF(1) TYPE C.
DATA: PRSDT LIKE VBKD-PRSDT.
DATA: HPRSFD LIKE TVAP-PRSFD.
DATA: END OF XVBAP.
DATA: BEGIN OF DYNPRO,
 EINSTIEG LIKE T185V-DYNNR VALUE 101,
 KKAU LIKE T185V-DYNNR,
 UER2 LIKE T185V-DYNNR,
 KBES LIKE T185V-DYNNR,
 ERF1 LIKE T185V-DYNNR,
 PBES LIKE T185V-DYNNR,
 PKAU LIKE T185V-DYNNR,
 PEIN LIKE T185V-DYNNR,
 EID1 LIKE T185V-DYNNR,
 POPO LIKE T185V-DYNNR,
 EIPO LIKE T185V-DYNNR,
 KPAR LIKE T185V-DYNNR,
 PSDE LIKE T185V-DYNNR,
 PPAR LIKE T185V-DYNNR,
 KDE1 LIKE T185V-DYNNR,
 KDE2 LIKE T185V-DYNNR,
 PDE1 LIKE T185V-DYNNR,
 PDE2 LIKE T185V-DYNNR,
 PKON LIKE T185V-DYNNR,
 END OF DYNPRO.
DATA: BEGIN OF PANEL,
 KKAU LIKE T185V-PANEL VALUE 'KKAU',
 UER2 LIKE T185V-PANEL VALUE 'UER2',
 KBES LIKE T185V-PANEL VALUE 'KBES',
 ERF1 LIKE T185V-PANEL VALUE 'ERF1',
 PBES LIKE T185V-PANEL VALUE 'PBES',
 PKAU LIKE T185V-PANEL VALUE 'PKAU',
 PEIN LIKE T185V-PANEL VALUE 'PEIN',
 EID1 LIKE T185V-PANEL VALUE 'EID1',
 EIAN LIKE T185V-PANEL VALUE 'EIAN',
 POPO LIKE T185V-PANEL VALUE 'POPO',
 EIPO LIKE T185V-PANEL VALUE 'EIPO',
 KPAR LIKE T185V-PANEL VALUE 'KPAR',
 PSDE LIKE T185V-PANEL VALUE 'PSDE',
 POAN LIKE T185V-PANEL VALUE 'POAN',
 PPAR LIKE T185V-PANEL VALUE 'PPAR',
 KDE1 LIKE T185V-PANEL VALUE 'KDE1',
 KDE2 LIKE T185V-PANEL VALUE 'KDE2',
 PDE1 LIKE T185V-PANEL VALUE 'PDE1',
 PDE2 LIKE T185V-PANEL VALUE 'PDE2',
 PKON LIKE T185V-PANEL VALUE 'PKON',
 KOAN LIKE T185V-PANEL VALUE 'KOAN',
 END OF PANEL.
DATA: BEGIN OF ERRTAB OCCURS 20,
 TRANS LIKE TSTC-TCODE,
 ARBGB LIKE T100-ARBGB,
 CLASS(1) TYPE C,
 MSGNR LIKE T100-MSGNR,
 TEXT LIKE T100-TEXT,
 TEXT(123) TYPE C,
 MSGV1 LIKE SY-MSGV1,
 MSGV2 LIKE SY-MSGV2,
 MSGV3 LIKE SY-MSGV3,
 MSGV4 LIKE SY-MSGV4,
 END OF ERRTAB.
*---- Hilfsfelder -
DATA: PROGRAMM_AUFTRAG LIKE T185V-AGIDV VALUE 'SAPMV45A'.
DATA: LAST_DYNPRO LIKE T185V-DYNNR,
 WLDAT LIKE VBAK-BSTDK,
 POSNR LIKE VBAP-POSNR,
 FIRST(1) TYPE C VALUE 'X'.
DATA: BEGIN OF XBDCMSGCOLL OCCURS 10.
 INCLUDE STRUCTURE BDCMSGCOLL.
DATA: END OF XBDCMSGCOLL.
Terminauftrag ( Auftragsart wird fest gesetzt !)
DATA: BELEGNUMMER LIKE VBAK-VBELN.
DATA: ERRORCODE LIKE SY-SUBRC.
Statuswerte fuer IDOC-Status
DATA: BELEG_NICHT_GEBUCHT LIKE TEDS1-STATUS VALUE '51'.
DATA: BELEG_GEBUCHT LIKE TEDS1-STATUS VALUE '53'.
*- Direktwerte für Return_variables -
data:
 eid like bdwfretvar-wf_param value 'Error_IDOCs',
 pid like bdwfretvar-wf_param value 'Processed_IDOCs',
 apo like bdwfretvar-wf_param value 'Appl_Objects',
 ape like bdwfretvar-wf_param value 'Appl_Object'.
*- Direktwerte für Workflow_Result -
DATA: C_WF_RESULT_ERROR LIKE BDWFAP_PAR-RESULT VALUE '99999'.
DATA: C_WF_RESULT_OK LIKE BDWFAP_PAR-RESULT VALUE '0'.

Function module for converting German Data/Time to Indian Date/Time

Dear All,
My requirement is to convert German date and time to Indian date and time. Is there any function module available or any way we can get it?
Thanks and regards,
Atanu

hi,
first get the timezone of that country
CALL FUNCTION 'TZON_LOCATION_TIMEZONE'
      EXPORTING
        if_country        = p_it_userid-zcountry
      IMPORTING
        ef_timezone       = l_tzone
      EXCEPTIONS
        no_timezone_found = 1
        OTHERS            = 2.
then use the below statements
-- Convert from server time to GMT
      CLEAR l_tstmp.
      CONVERT DATE l_datum
              TIME l_ctime
         INTO TIME STAMP l_tstmp TIME ZONE sy-zonlo.
*-- Convert from GMT to user backup time
      CONVERT TIME STAMP l_tstmp TIME ZONE it_usr_timezone-ztzone
        INTO DATE it_usr_timezone-zdate
             TIME it_usr_timezone-ztime.

SAP NCO 3 (Patch 3) - Problems with USE_SAPGUI and Function Module

Hello,
We are moving our code to use the new SAP .NET v3 connector and have run into a slight issue which works on v2 but doesn't seem to work the same way in v3.
We are calling a function module in SAP that will invoke the SAP GUI allow the user to interact with it. Once the user has completed their interaction and clicked the last button, the SAP GUI is meant to disappear. With v3 this is no longer the case.
We are forcing the USE_SAPGUI value to 2 but this has no effect on the problem.
In V3, the last dialog box stays on the screen and control returns to our application. The dialog box is not active anymore and cannot be clicked. It seems the SAP GUI will stay open with this frozen dialog box until we invoke another RFC that brings up the SAP GUI.
My questions are:
1) Is this a bug or is there something more I need to do to achieve this functionality?
2) Is there anyway to forcibly close the SAP GUI connection for a RFCDestination? The connection is closed when we close our application but I can't find a way to close all connections which would hopefully close the dialog box.
Thanks in advance for any help on this matter.
Thanks,
Tim

I can't be sure but most of the dota2 output looks "normal" to me (I get the same yet it works fine).
eurotrucks is clearly crashing. You could try to force the resolution it uses in its config files?
Or maybe it's missing a lib (you may need to install 32bit versions):
ldd /path/to/eurotrucks
to see if that's the case. If not, you might have to take it up with the eurotrucks developers.
And you could try using fluxbox/openbox just to see what happens. A lot lighter than KDE.
Have a good look though: https://wiki.archlinux.org/index.php/Steam
and remember to check for missing 32bit libs.

Problem with time stamp

Hello,
I got mistake in ODS manage like this:
The time stamp in the source system is 24.09.2007
The time stamp in the BW is 23.05.2009.
I have problem to load data in ODS.
What should I do ?? Replicate the data source ? But then it's possible to get double data. What to do ??
THX

I replicated data source, source system and loaded data one more time and I have got the same mistake.
this:
Error message from the source system
Diagnosis
An error occurred in the source system.
System response
An error occurred in Service API .
Check the error message.
Procedure
The procedure for removing errors takes place depending on
the error message:
Note
If the source system is a Client Workstation, then it is possible that the file that was to be loaded was being edited at the time of the data request. Make sure that the file is in the specified directory and is not being edited, and restart the request.
AND ALSO mistake WITH TIME STAMP

Problem with time series functions against Essbase

Hello all,
I'm having problems with displaying correct results when using AGO function in OBIEE. I'm using Essbase 9.3.1 and OBIEE 10.1.3.4.1. Logical column named MAGO1 is created in repository like this: IFNULL( AGO("Measure01", Time.Month, 1), 0). In Answers when I use columns Measure01,MAGO1,Time.Month with filter just on Time.Month column results are OK. When I put another filter, for example Dim1.Gen2,Dim1, MAGO1 returns zero as a result. But when I put Dim1.Gen2,Dim1 also as a column and as a filter results are OK. I don't want to have Dim1.Gen2,Dim1 as a column but just in a filter. Also hiding column is not an option. I want to have grouped results and not multiple rows for one month if I remove filter Dim1.Gen2,Dim1. Filter is selected on prompt in dashboard and can be some value from Dim1.Gen2,Dim1 or All Choices. Reason for this is that I'm using this answers report as a data source for BI Publisher so additional formatting on answers report isn't helpful.
I am suspecting that something is wrong with hierarchy it time dimension or other dimensions. Or maybe MDX is not generated right ? If you need more details regarding my repository or configuration please feel free to ask. Any help is greatly appreciated.
Thanks,
D.

I am using BI Publisher and Answers report as data source. Making changes like hiding column or displaying results as pivot table won't help in this case.
Anyway I did discover something else. When I put in report logical columns with ago function they return correct results. But when I add additional logical column with todate function all logical columns with ago and todate function return zero as a result. Also this happens only when result is more than one row. If you have only one row, for example grand total level of dimension, than result is OK, but if you have more rows on a lower level than zero values appear.
Some columns that are used in filter do not appear as columns in report. This is the main problem. If I put all columns that are filtered in report than the result is OK. But I don't want to do this because I want to have option to select values on dashboard prompt on different levels.
Hope this narrows the problem.
Thanks,
D.

Function Module for converting timestamp

Hi all
I have a scenario where in the timestamp is getting stored in a z table in the UTC format (i.e. 20,100,125,080,528).
Now when i have to display this value to the user, it should be like "25.01.2010 08:05:28". Is there any standard function module to accomplish this? or is it like i have to do it in my code using the offset?
please guide me.
Thanks in advance.
Regards
Gaurav

Hello
Use this:
DATA:
tstamp TYPE timestamp,
d TYPE D VALUE '19971224',
t TYPE T VALUE '235500'.
CONVERT TIME STAMP tstamp TIME ZONE 'UTC+12' INTO DATE d TIME t.
Just press F1 on TIME STAMP.

Problem with Remotely Invoked Function Module

Hi All,
I have a requirement to develop a Remote Enabled Function Module in SAP R/3 which will be invoked from an XI environment via an XML message.
The purpose of this FM is to validate the incoming data(which comes as a pair of values) by comparing it with values in a corresponding SAP Table.
If the incoming data is consistent with the values in the SAP Table, i need to return the data in the same format as it is passed. If any inconsistent record is encountered, then i just need to delete that particular record and return the rest of them.
I used a TABLE for the Input/Output in the FM and tried it. Though it works fine stand-alone, when invoked from the XI environment, the calling system is able to receive only the name of the Table Structure that is used in the FM for I/O.
I am unable to comprehend the format the input comes into SAP when the FM is invoked. So I'm not able to exactly pin-point the place where the problem arises.
Please suggest a solution.
Any pointers in this regard will be helpful.
Thanks in Advance.

Hi,
You can view the incoming message in the local XI Message Monitor SXMB_MONI. There you will see if the input table parameter is correctly filled. In the same transaction, you can also see the reply that is sent to XI. If that is OK, you know that your function works correctly. When you are sure of that, and the calling system does not get the same parameters returned as you could see, that means the mapping in XI is wrong.
good luck,
Peter Glas

Problem with Time stamp function module for converting US to Japan

Similar Messages

Maybe you are looking for