Upload data in infotype 1520 using BADi(HRECM00_BDG0001).

hi experts,
We have a requirement wherein the BADi (HRECM00_BDG0001- which uses DETERMINE_BUDGET_VALUES method) needs to upload initial Budget Values into the Budget Structure, through an Excel Spreadsheet input (which will contain Organization Units and its respective Budget Values)
This will result in upload of initial budget values into the Budget Values Infotype 1520.
and based on this the Budget structure is created and ready for use.
Is there any functional module or any other method to upload the data (excel file) into the infotype 1520?
regards,
joy.

Hi Christian,
Please check if hte below links help you in some way.
Uploading Files and Manipulating their Content
http://help.sap.com/saphelp_nw04/helpdata/en/ba/78d3c747b24546ab1c1499a054d8a5/content.htm
File Upload in BSP Applications
http://help.sap.com/saphelp_nw04/helpdata/en/eb/8c683c8de8a969e10000000a114084/content.htm
Regards,
SuryaD.
Edited by: SuryaD on Dec 18, 2009 11:15 PM

Similar Messages

How to upload data in infotype 0025 (Appraisals)

I want to make an upload program for infotype 0025 (Appraisals). The program will upload the data in 'Potentials' but I cannot make a recording work in it. Each time the system posts the data into next row and recording does not work since the line number is fixed in recording. There is no + sign to add a row at the top. Can someone please tell me a way to do this or if there is a Function Module that can upload data into infotype 0025.
Thanks

Dear Sohaib,
This upload could not be performed by BDC recording. You will have to make use of around four Appraisal BAPI's to create an entry in Infotype 25(Appraisals). I had the same scenario of uploading appraisal data here at NBP(National Bank of Pakistan). Here is the link for the article i wrote,covering this topic in depth,along with the complete solution:
http://scn.sap.com/docs/DOC-32084
If you like this article,kindly flag it as a 'Correct Answer.
Regards,
Fahad

Uploading data in infotype-0586 and infotype-0587

Dear Experts,
     Can i use the standard bapi HR_INFOTYPE_OPERATION for uploading data into infotype-0586( sec 80c deduction) and infotype-0587 (pf related).if so what are the parameters to be passed for the upload.
Please inform if there are any other bapi for the upload process.
regards,
Aeroshil Nameirakpam

Hi,
yes you can use...HR_INFOTYPE_OPERATION for your purpose.
in that you should pass....
INFTY                - infotype number
NUMBER           --pernr
SUBTYPE          --subtype of infotype (if applicable)
VALIDITYEND      -ENDDA
VALIDITYBEGIN   -BEGDA
but before you call this FM...make sure that you lock the employee for which you are updating the record and after this FM updates the record for that employee make sure you unlock the employee...
to lock the pernr ...use FM....HR_EMPLOYEE_ENQUEUE
and to unlock...use FM... HR_EMPLOYEE_DEQUEUE
in both of these FMs you just need to passs PERNR..
summerizing this...first use...
HR_EMPLOYEE_ENQUEUE
then call...HR_INFOTYPE_OPERATION
and then...
HR_EMPLOYEE_DEQUEUE
thats it!
<b>Reward Points if answer was helpful,</b>
Regards,
Tejas

Bapi - upload data for infotypes 0016 and 0019

hello,
Please let me know bapi to upload data for infotypes 0016 and 0019 as i am unable to find any bapi for this infotypes.
Please use a more meaningful subject in future - I've edited it for you this time.
Edited by: Matt on Nov 6, 2008 12:08 PM

Hi Sunny,
My suggestion is go txcode BAPI.
After this in the left side of the window complete information on BAPIs will be available search out in Human resource you may get the BAPI, in the mean while some one may help you.
Cheers!!
VEnk@

Query on uploading data into infotype

Hi,
I am in search of a method to upload data into infotypes IT0001,HRP1001.
I have serached and found we can do it using BDC,LSMW and through Hr_INOFYTPE_OPERATION--fm.
But in my flat file am having pernr ,begda,endda and supervisor..
Some of my searches said if i had a pernr in flat file its impossible to do with HR_INFOTYPE_OPERATION.
CAN ANYONE PLS SUGGEST ME THE BEST WAY TO DO?
Thanks

Hi Salini
Using BDC or LSMW might lead to some inconsistencies.
Uploading of various infotype data depends upon its volume.
There is a FM: HR_MAINTAIN_MASTERDATA through which you can upload the data. But this does for one record at a time. So the performance gets affected at times. Before calling this FM each time, clear the buffer using the FM: 'HR_PSBUFFER_INITIALIZE'. This will be of great help.
Incase you want to upload all your data at once, you can use BAPI_HRMASTER_SAVE_REPL_MULT.
Let me know incase you need any help in any of these.
Regards
Harsh

ECM Budget Upload using BAdI HRECM00_BDG0001

Hi experts,
Iu2019m implementing HRECM00_BDG0001 BAdI in transaction PECM_START_BDG_BSP. This transaction executes a BSP application, in this application after clicking a button the BAdI is called. I need to show a file browser to let the user to upload a file. Iu2019m using FM 'KD_GET_FILENAME_ON_F4' to show the file browser, but Iu2019m unable to see the file browser dialog and, even worse, Iu2019m getting an error: Exception condition "NO_BATCH" raised. I suppose than BSP applications execute backend calls in background, but I need to give user the chance of selecting a file to upload, is there another approach? What could I do? Iu2019m really stuck. I need some help.
Thanks in advance.

Hi Christian,
Please check if hte below links help you in some way.
Uploading Files and Manipulating their Content
http://help.sap.com/saphelp_nw04/helpdata/en/ba/78d3c747b24546ab1c1499a054d8a5/content.htm
File Upload in BSP Applications
http://help.sap.com/saphelp_nw04/helpdata/en/eb/8c683c8de8a969e10000000a114084/content.htm
Regards,
SuryaD.
Edited by: SuryaD on Dec 18, 2009 11:15 PM

Uploading data in infotype 0024

Hi all,
I want to upload datain infotype 0024 - qualifications tab. Now the issue here is that this infotype contains a table control in which the data is not getting stored in infotype 0024 but some place else instead.
Please suggest how to tackel the situation using bdc.
Thanks
Ribhu

Ofcourse i need more information - please read this:
Well please go to pa30 and try to create a record in Infotype 0024.
There in the qualifications tab, you cant enter anything - u have to click on the create button below the table control to choose languages - various check boxes for languages.
Now when I do recording - this step of choosing the languages do not comes up . moreover the fields in the tabstrip for qualification - they are not in the pa0024 table and are stored somewhere else. So even if i use hr_infotype_operation, it do not shows up the fields for qualifiactions tab - like language, profecincey level and dates for various languages.
Please suggest if you know something.
Infotype no 0045 is also a similar infotype where the data gets stored at some other place ..... I mean by any chance if u know how to upload data in IT0045, it would be a great help.
thanks
Ribhu

Problem in updating Data for infotype P0009 through BADI

Hi,
we are facing a problem while trying to update value of Date field for infotype P0009 through PA30.
we have tried to update by using BADI hrpad00infty, we are providing value in new_innnn structure of method
AFTER_INPUT, but the value is not getting updated for that PARNR.
Can anyone help me regarding the same?

Hi
HRPAD00INFTY BADI methods don't allow to modify any values of the current record being processed, but there's a possible wworkaround accessing memory fields using field-symbols:
method IF_EX_HRPAD00INFTY~AFTER_INPUT.
FIELD-SYMBOLS: <fs> type p0009.
assign ('(MP000900)P0009') TO <FS>.
if sy-subrc eq 0.
<FS>-YOURFIELD = YOUR_VALUE.
endif.
endmethod.

Error while uploading data in SAP (me01)using LSMW

Hi All,
I am using LSMW for the first time.
I am trying to upload data to the Source List transaction (me01) using batch input recording. I created a new recording through LSMW itself. My source structure consists of 5 fields:
<b>MATNR C(18)
WERKS C(4)
VDATU N(8)
BDATU N(8)
LIFNR C(10)
EKORG C(10)</b>
Now the problem is when i try to convert the data, it gives me an error saying
"For type "C",a maximum length specification of 65535 is allowed."
I have noticed that unlike Direct Input method,
using batch input does not give any fields in "Maintain Field Mapping & Conversion Rules". So even if I have my fields in my source structure ,there are no fields to which I can map them to.
I don't know that is how it is when we go with batch input.
My file contain data in following order:
DANGEROUS GOODS,ABBY,20060801,20060831,30010,TEST
Pls help me to solve this problem.

Hi Swapna!
You get such an error message, when define a constant and forget the second ':
g_werks = '1000. "wrong
g_werks = '1000'. "correct
In general: a batch input recording can have fixed values and some variables. You need to define, which fields you like to fill with a variable. Go to the overview of the recordings, open the recording in change mode and assign some variable names to the according batch lines.
<a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/76/a05b69e8a411d1b400006094b944c8/frameset.htm">Editing batch input recordings</a>
Follow the help for the following steps of structure assignments.
Regards,
Christian

Not able to modify the data for infotype 0008 using FM

Hi All ,
I have got a requirement for updating the infotype 0008 data using FM : HR_MAINTAIN_MASTER_DATA.
While trying to modify the wagetypes data which is of blank ..unable to upload the amount for that partcular field ..
For this am herewith the link of o/p :
http://i55.tinypic.com/28jfw2c.jpg for this am also posting the code...
Please suggest me furthur in what way i can upload..
      SELECT * FROM pa0008 INTO TABLE itab_pa0008
FOR ALL ENTRIES IN itab
    WHERE pernr = wa_data-pernr
    AND begda = wa_data-begda_out
    AND endda = wa_data-endda_out.
    DESCRIBE TABLE itab_pa0008 LINES lin.
    IF lin EQ 0.
      c_action = 'INS'.
    ELSE.
      c_action = 'MOD'.
    ENDIF.
    LOOP AT itab INTO wa_itab WHERE pernr = wa_data-pernr.
      CLEAR: wa_bapireturn, wa_bapireturn1, wa_hr_return.
      REFRESH: it_pprop[],it_modified_keys[].
      it_pprop-infty = '0008'.
      it_pprop-fname = 'P0008-TRFAR'.                 "1
      it_pprop-fval = wa_itab-trfar.
      APPEND it_pprop.
      CLEAR it_pprop.
      it_pprop-infty = '0008'.
      it_pprop-fname = 'P0008-TRFGB'.                 "2
      it_pprop-fval = wa_itab-trfgb.
      APPEND it_pprop.
      CLEAR it_pprop.
      it_pprop-infty = '0008'.
      it_pprop-fname = 'P0008-TRFGR'.                  "3
      it_pprop-fval = wa_itab-trfgr.
      APPEND it_pprop.
      CLEAR it_pprop.
      it_pprop-infty = '0008'.
      it_pprop-fname = 'P0008-TRFST'.                  "4
      it_pprop-fval = wa_itab-trfst.
      APPEND it_pprop.
      CLEAR it_pprop.
      flag = flag + 1.
*****************************************************************************************************5
      BREAK-POINT.
      IF NOT wa_itab-lga1 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA01'.
        it_pprop-fval = wa_itab-lga1.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet1.
      ENDIF.
      IF NOT wa_itab-bet1 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET01'.
        it_pprop-fval = wa_itab-bet1.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************6
     IF NOT wa_itab-lga2 IS INITIAL.
       it_pprop-infty = '0008'.
       it_pprop-fname = 'P0008-LGA02'.
       it_pprop-fval = wa_itab-lga2.
       APPEND it_pprop.
       CLEAR it_pprop.
       bet1 = wa_itab-bet2.
     ENDIF.
      IF NOT wa_itab-bet2 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET02'.
        it_pprop-fval = wa_itab-bet2.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************7
      IF NOT wa_itab-lga3 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA03'.
        it_pprop-fval = wa_itab-lga3.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet3 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET03'.
        it_pprop-fval = wa_itab-bet3.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************8
      IF NOT wa_itab-lga4 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA04'.
        it_pprop-fval = wa_itab-lga4.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet4 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET04'.
        it_pprop-fval = wa_itab-bet4.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************9
      IF NOT wa_itab-lga5 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA05'.
        it_pprop-fval = wa_itab-lga5.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet5 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET05'.
        it_pprop-fval = wa_itab-bet5.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************10
      IF NOT wa_itab-lga6 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA06'.
        it_pprop-fval = wa_itab-lga6.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet6 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET06'.
        it_pprop-fval = wa_itab-bet6.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************11
      IF NOT wa_itab-lga7 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA07'.
        it_pprop-fval = wa_itab-lga7.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet7 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET07'.
        it_pprop-fval = wa_itab-bet7.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************12
      IF NOT wa_itab-lga8 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA08'.
        it_pprop-fval = wa_itab-lga8.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet8 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET08'.
        it_pprop-fval = wa_itab-bet8.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************13
      IF NOT wa_itab-lga9 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA09'.
        it_pprop-fval = wa_itab-lga9.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet9 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET09'.
        it_pprop-fval = wa_itab-bet9.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************14
      IF NOT wa_itab-lga10 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA010'.
        it_pprop-fval = wa_itab-lga10.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet10 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET010'.
        it_pprop-fval = wa_itab-bet10.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************15
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-LGA11'.
   it_pprop-fval = wa_itab-lga11.
   APPEND it_pprop.
   CLEAR it_pprop.
   bet1 = wa_itab-bet2.
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-BET11'.
   it_pprop-fval = wa_itab-bet11.
   APPEND it_pprop.
   CLEAR it_pprop.
********************************************************************************************************16
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-LGA12'.
   it_pprop-fval = wa_itab-lga12.
   APPEND it_pprop.
   CLEAR it_pprop.
   bet1 = wa_itab-bet2.
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-BET12'.
   it_pprop-fval = wa_itab-bet12.
   APPEND it_pprop.
   CLEAR it_pprop.
********************************************************************************************************17
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-LGA13'.
   it_pprop-fval = wa_itab-lga13.
   APPEND it_pprop.
   CLEAR it_pprop.
   bet1 = wa_itab-bet2.
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-BET13'.
   it_pprop-fval = wa_itab-bet13.
   APPEND it_pprop.
   CLEAR it_pprop.
********************************************************************************************************18
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-LGA14'.
   it_pprop-fval = wa_itab-lga14.
   APPEND it_pprop.
   CLEAR it_pprop.
   bet1 = wa_itab-bet2.
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-BET14'.
   it_pprop-fval = wa_itab-bet14.
   APPEND it_pprop.
   CLEAR it_pprop.
BREAK-POINT.
      CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
        EXPORTING
          number = wa_itab-pernr
        IMPORTING
          return = wa_bapireturn1.
      BREAK-POINT.
     IF c_action = 'INS'.
       CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
         EXPORTING
           pernr           = wa_itab-pernr
           actio           = 'INS'
         tclas           = 'A'
           begda           = wa_data-begda_out             "'20110401'
           endda           = wa_data-endda_out             "'99991231'
           dialog_mode     = '2'
         luw_mode        = '1'
         IMPORTING
           return          = wa_bapireturn
           return1         = wa_bapireturn1
           hr_return       = wa_hr_return
         TABLES
           proposed_values = it_pprop
           modified_keys   = it_modified_keys.
       IF NOT wa_bapireturn IS INITIAL.
         WRITE : / wa_bapireturn.
         CLEAR : wa_itab , wa_bapireturn.
       ENDIF.
     ELSEIF c_action = 'MOD'.
        CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
          EXPORTING
         infty         = '0008'
            pernr           = wa_itab-pernr
            actio           = 'MOD'
            begda           = wa_data-begda_out             "'20110401'
            endda           = wa_data-endda_out             "'99991231'
      record        = p_record
         recordnumber = wa_itab-SEQNR
         operation     = change
         nocommit      = nocommit
            dialog_mode     = '0'
         IMPORTING
            return          = wa_bapireturn
            return1         = wa_bapireturn1
            hr_return       = wa_hr_return
          TABLES
            proposed_values = it_pprop
            modified_keys   = it_modified_keys.
        IF NOT wa_bapireturn IS INITIAL.
          WRITE : / wa_bapireturn.
          CLEAR : wa_itab , wa_bapireturn.
        ENDIF.
     ENDIF.
      CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
        EXPORTING
          number = wa_itab-pernr
        IMPORTING
          return = wa_bapireturn1.
    ENDLOOP.
ENDLOOP.

Here is a sampe, and the logic you are using for wages goes in the internal table for wages (you already have the enqueue & dequeue so you don't have to worry about that, so you only have to add the BAPI_TRANSACTION_COMMIT):
CALL FUNCTION 'BAPI_BASICPAY_CHANGE'
EXPORTING
    employeenumber             = pa0008-pernr
    subtype                    = pa0008-subty
    objectid                   = pa0008-objps
    lockindicator              = pa0008-sprps
    validitybegin              = pa0008-begda
    validityend                = pa0008-endda
    recordnumber               = pa0008-seqnr
    payscaletype               = pa0008-trfar
    payscalearea               = pa0008-trfgb
    payscalegroup              = pa0008-trfgr
    payscalelevel              = pa0008-trfst
*   NEXTINCREASE               =
*   LOCALALLOWLEVEL            =
*   PARTNERSHIP                =
*   CURRENCY                   =
*   COMPARISONPAYSCLTYPE       =
*   COMPARISONPAYSCLAREA       =
*   COMPARISONPAYSCLGRP        =
*   COMPARISONPAYSCLLVL        =
*   COMPNEXTINCREASE           =
*   CAPACITYUTILLEVEL          =
*   HOURSWORKEDPERPERIOD       =
*   ANNUALSALARY               =
*   CASEGROUPCATALOG           =
*   CASEGROUP                  =
*   CURRENCYANNUALSALARY       =
*   REASON                     =
*   NOCOMMIT                   =
* importing
*   return                     =
TABLES
   wagetypes                  = wages.
Regards,
Ryan Crosby

Problem while uploading data in infotype 2

Hi All,
I made BDC to upload required fields in infotype 2. I use text file to upload all the data.
Currently i have only one record in text file for testing purpose. When i run the report in foreground for that record it goes to the pa30 screen which i have accessed recently. It means if i access pa30 for emp. code 123 then my bdc update the records for emp. code 123 and if i access emp. code 456 after that through pa30 then my program is updating records for emp. code 456. Can you please tell me why it is happening.
Thanks.

Hi,
In PA30, the field for PERNR on screen, gets default value as per last used PERNR.
So, in BDC, we should make sure that the screen field is populated by our value from the file. Just check your bdc code, and make sure the field
RP50G-PERNR
gets the value from the file.
Regards,
Amit Mittal.

Modify Infotype 0008 using BADI or EXIT - How to?

Hi,
How to modify the values for infotype '0008' in save moment, using a EXIT or BADI????
What EXIT or BADI to use for this?
Thanks,
Daniel

Use Exit FM: EXIT_SAPFP50M_001 for setting default values and Exit FM: EXIT_SAPFP50M_002 validations for various infotypes(including IT0008) by enhancing PBO and PAI includes respectively.
for Example.
When copying an infotype 0008 record, the reason code *should be cleared.
INCLUDE y_zxpadu01_08.
Data declaration.
DATA: BEGIN OF wa_am7912_0008.
        INCLUDE STRUCTURE p0008.
DATA:   filler(1500) TYPE c,
      END OF wa_am7912_0008.
Only perform for 0008 infotypes....
IF innnn-infty = '0008'.
...that are being copied only....
    IF ipsyst-ioper = 'COP'.
    .....and that are being called manually.
      IF ipsyst-inpst = '0'.
      Parse the data.
        CLEAR wa_am7912_0008.
        wa_am7912_0008 = innnn.
      Clear the reason code.
        clear wa_am7912_0008-preas.
        clear innnn.
        innnn = wa_am7912_0008.
      endif.
    endif.
endif.
Regards,
MM

Cannot upload data to serial device using x-on, x-off in Labview but works OK in Hyperterminal

Hello,
I'm trying to write a Labview 7.1 App that will upload a motorola .S28 file to a custom designed piece of hardware. The serial port on the hardware device requires the serial port settings be set to 9600, 8,N,1, none, for general operation and my Labview app is able to send and receive information from the hardware using the NI VISA 4.00 serial read and write routines, so I know that there are no fundamental communications errors. The general communications also work when I set the com port to 9600, 8,N,1, x-on, x-off.
The problem I'm experiencing is that I can upload calibration files (which require x-on, x-off flow control) in Hyperterminal by:
1. configuring the Hyperterminal session for 9600, 8,N,1, x-on, x-off
2. selecting "Transfer--> Send Text File... when my device prompts me to upload the file.
This works 100% of the time in Hyperterminal, but I cannot accomplish the same upload in my Labview app.
The very first thing my LV app does is to pop up a dialog box to the user prompting him/her to select the desired com port (Visa Resource Name), Baud rate, Data bits, Parity, Stop bits, Flow Control, and allows the user to enable/disable the termination char and to set the termination char (always enabled and set to default 0xA). The flow control is set to x-on, x-off. This is accomplished using the VISA Configure Serial Port vi.
I have tried using both the VISA Write From File vi and also reading the file to a text variable then using the VISA (serial) Write vi but neither work. The VISA Write From File vi return count correctly identifies the number of bytes in the file but the hardware never returns it's transfer complete status message (remember this works 100% of the time in Hyperterminal). Does anyone out there have any advice as to how I can make this work?
Thanks,
Ian

This is going to be a two-part solution, meaning you will need to change the way you read your file and the way you transmit the data.
First, when you read from your file, set the Read VI to read in Line Mode. When you do this, the output of the read will be an array of strings rather than a single string. It will basically read the file until it hits the CR/LF combination, but should strip the terminating characters from each line.
Second, in order to replace the carriage return which was stripped, you can configure VISA to transmit a termination character after each write is performed. In addition to setting the termination character to CR on the Configure Serial Port VI, you will want to use a VISA Property Node to set the Serial::End Mode For Writes properter to use the termination character.
Now, you can simply use a For loop to index through your string array, transmitting each line. You will have eliminated all your manual parsing of the file, which should simplify your application and increase performance. I have included a picture of how this could be done in LabVIEW 8.x. The file I/O interface looks different than it did in 7.1, but the same functionality exists.
-Jason S.
Message Edited by JasonS on 09-26-2007 08:49 AM
Attachments:
sendfile.jpg ‏23 KB

Uploading data from excel sheet using BAPI (BAPI_ACC_MANUAL_ALLOC_POST)

Hi,
I am Using BAPI_ACC_MANUAL_ALLOC_POST (Manual cost allocation) for uploading into database. But i am getting the error "DO NOT USE COST ELEMENT xxxxxxxx FOR REPOST COSTS".
can anyone explain me the possible reasons for this error.
any help will be rewarded.
Thanks and Regards,
Gautham Paspala

Hi,
Refer to the following code:
DATA: lv_filetype(10) TYPE c,
        lv_gui_sep TYPE c,
        lv_file_name TYPE string.
lv_filetype = 'ASC'.
lv_gui_sep = 'X'.
lv_file_name = pa_dfile.
FM call to upload file
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename                = lv_file_name
      filetype                = lv_filetype
      has_field_separator     = lv_gui_sep
    TABLES
      data_tab                = gi_zhralcon_file
    EXCEPTIONS
      file_open_error         = 1
      file_read_error         = 2
      no_batch                = 3
      gui_refuse_filetransfer = 4
      invalid_type            = 5
      no_authority            = 6
      unknown_error           = 7
      bad_data_format         = 8
      header_not_allowed      = 9
      separator_not_allowed   = 10
      header_too_long         = 11
      unknown_dp_error        = 12
      access_denied           = 13
      dp_out_of_memory        = 14
      disk_full               = 15
      dp_timeout              = 16
      OTHERS                  = 17.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
The excel file must be a tab delimited file.
Hope it helps.
Regards,
Rajesh Kumar

Bapi or bdc to upload data in infotype 0267 through workflow

Hi All,
I have designed a workflow for infotype 0267 in which after
the final approval of the offcycle amount the record gets unlocked.
For this purpose in I had used a bdc to unlock the record.
The bdc is working fine if I test the object in SW01, but in the workflow it dosen't work the workflow remains in process.
I would like to know if at all bdc can be used in workflows, or there is an alternative to it like using BAPI.
Thanks and regards
Shraddha

Mike Pokraka wrote:>
> Hi Shradda,
>
> Unfortunately I don't know this offhand, have you tried to find it?
You can also ask in [the forum dedicated to questions about HCM (HR)|SAP ERP Human Capital Management (SAP ERP HCM); - where I am sure you'll find more expertise in this area - because you are not really struggling with a workflow problem, it's plain ABAP.

Upload data in infotype 1520 using BADi(HRECM00_BDG0001).

Similar Messages

Maybe you are looking for