Problem with updating DB table in using BAPI

HI,
The code below does not update the DB table even if the commit work is executed... is there something wrong or missing??? Thanks a lot!
Technically complete process Order
       CALL FUNCTION 'BAPI_PROCORD_COMPLETE_TECH'
         IMPORTING
           return = i_messages
         TABLES
           orders = i_orders.
         IF i_messages-type NE c_error.
           REFRESH i_messages3.
           CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
             EXPORTING
               wait   = 'X'
             IMPORTING
               return = i_messages3.
        ENDIF.

Hi this is your code right.
You have to check the return table not messages.
Check the return table is there any message type is there with 'E' .
if it is there then the commit work won't give the result in fact the BAPI function is not executed successfully.
If you got any Error message in return table please have a look into that table errors and take the necessary action.
Pass the required paramaters for the BAPI function module.
Regards,
Madan.

Similar Messages

Problem with updating a Table in LabVIEW 7

I have a table on my front panel that I am using as a program control input. It has 3 columns, and adding certain values to these columns forces the program to do certain actions in a certain order. This part works fine, however if I ever want to reduce the number of rows in the table it all falls to pieces. This happens whether or not I reduce the number of rows whilst the program is running or in design mode. Despite what the table is displaying on the front panel it is always retaining the last data entered with a greater number of rows.
e.g.
I have 3 rows of information : Works fine
I add 2 more rows for 5 rows used : Works fine
I delete 1 row so now there are 4 : Still runs as if it had all 5 even though the front
panel display says differently.
The only way around this I have found is to right click the table and choose "Empty Table" but this is not a convenient solution for users of the software (who may well forget to do that).
Is there any way to programmatically make sure the table only uses what it's meant to (ie what's showing on the front panel).
I'm using a local variable to read in the values of the table within my program.
Thanks
Neil

I've solved this problem now. I had an initializer on a feedback node wired incorrectly which caused unbounded increases in array size.
Thanks for the suggestions I did receive
Neil

Problem with update a table

Hi,
--I need to update a table with only year 2010 data, it looks like this:
update abc_tab set dept_cd = replace(dept_cd, 'HRE','HW')
where dept_cd in (select dept_cd from edu_tab e, edu_lkp l
where l.dept_rnd_cd =e.dept_rnd_cd
and l.fy_cd ='2010');
--when I run above query, it updated all the data in the column , not just 2010 data, but if I do following
(select dept_cd from edu_tab e, edu_lkp l
where l.dept_rnd_cd =e.dept_rnd_cd
and l.fy_cd ='2010');
-- I got only 2010 data, so what did I do wrong on the update statement?
Thanks a lot.
Wendy

data is not correlated based on DEPT_CD,
try this:
update abc_tab abc set abc.dept_cd = replace(abc.dept_cd, 'HRE','HW')
where abc.dept_cd in (select e.dept_cd
                      from   edu_tab e
                            ,edu_lkp l
                      where l.dept_rnd_cd = e.dept_rnd_cd
                      and    e.dept_cd     = abc.dept_cd
                      and    l.fy_cd       = '2010'
commit
/

Update the table SCMG_T_CASE_ATTR using BAPI

Hi Experts,
I have query regarding bapi BAPI_DISPUTE_ATTRIBUTES_CHANGE.
what are the values to be passed in attribute of tables section.
I have pass field name as 'closed_by' (of table SCMG_T_CASE_ATTR) in parameter of bapi (ATTR_ID).
And attr_value field with 'test'.
Please help me to update a field value like 'closed_by' of SCMG_T_CASE_ATTR using this bapi.
Thanks in advance,
Sahil

Hi Cristobal,
Thanks for helping me, however the function does not give me any results, the problem is that this document is a linked object, and not an attachment.
Thanks for your help.
Best regards,
Adriana

Problem with creating Process order confirmation using BAPI

Hello,
While creating Process Order confirmation using BAPI_PROCORDCONF_CREATE_TT, material document is getting created. But a line item is inserted in the table AFRU without material document number. When it is created manually using the transaction COR6, the table is getting updated with material doc in the line item. Can anyone let me know what other attributes to be passed in order the update the same?
Thanks in Advance.
Regards, Senthil G.

Hello , I am working with the same Bapi, can you please send me the code to fill the parameters, if I find the same error like you, I will send you the solution if I correct that.
Thanks for your help.
[email protected]
Guatemala, Cempro ADATSA

Problem in updating IMRG table when using MEASUREM_DOCUM_RFC_SINGLE_001

Hi experts,
I am using MEASUREM_DOCUM_RFC_SINGLE_001 to create measuring documents for the equipment assigned to a functional location. But when i used this in ECC 5.0 the table IMRG is updated rightly. Now i am using the same in ECC 6.0 , I observe that the following fields of IMRG table are not get updated when compared with 5.0:
CNTRG
CNTRR
CNTRRI
CDIFF
CDIFFI
IDIFF
Can any one tell what could be the problem.

Check for Sap notes for Function module MEASUREM_DOCUM_RFC_SINGLE_001.
And apply SAP notes correctly according to patch levels.

HT201210 nowadays have many user have problem with update to ios7 and need active with apple id maybe in the future in order escape from these problems must be stop use these products else. Because of simple user don't know about this technology and somet

nowadays have many user have problem with update to ios7 and need active with apple id maybe in the future in order escape from these problems must be stop use these products else. Because of simple user don't know about this technology and sometime just hear from other user that it 's difficult to use then force they change phone that use to handle to another.

It is a feature to discourage the theft of iPhones by making them useless if resold. It's not going anywhere. It's simple: just don't buy a phone until you make sure that the activation lock has been disabled.

Planner group is not updated in service notification using BAPI

Hi,
Planner group is not updated in service notification using BAPI BAPI_ALM_ORDER_MAINTAIN.
I have written the below code, but planner group is not updated in the service notification.
Please advice which parameters do i need to pass to update planner group in the service notification.
          wa_methods-refnumber      = '000001'.
          wa_methods-objecttype     = 'PARTNER'.
          wa_methods-method         = 'CREATE'.
          wa_methods-objectkey      = wa_subscr1-aufnr.
          APPEND wa_methods TO i_methods.
          wa_methods-refnumber      = '000002'.
          wa_methods-objecttype     = 'HEADER'.
          wa_methods-method         = 'CREATE'.
          wa_methods-objectkey      = wa_subscr1-aufnr.
          APPEND wa_methods TO i_methods.
          wa_methods-refnumber      = '000000'.
          wa_methods-objecttype     = ' '.
          wa_methods-method         = 'SAVE'.
          APPEND wa_methods TO i_methods.
          REFRESH i_partner.
          CLEAR wa_partner.
          wa_partner-orderid        = wa_subscr1-aufnr.
          wa_partner-partn_role     = 'VW'.
          wa_partner-partn_role_old = ''.
          wa_partner-partner        = wa_subscr1-parnr.
          wa_partner-partner_old    = ''.
          APPEND wa_partner TO i_partner.
          REFRESH i_planrgrp.
          CLEAR wa_planrgrp.
          wa_planrgrp-orderid        = wa_subscr1-aufnr.
          wa_planrgrp-plangroup      = wa_subscr1-ingpr.
          APPEND wa_planrgrp TO i_planrgrp.
          REFRESH i_planrgrp_up.
          CLEAR wa_planrgrp_up.
          wa_planrgrp_up-orderid     = wa_subscr1-aufnr.
          wa_planrgrp_up-plangroup   = 'X'.
          APPEND wa_planrgrp_up TO i_planrgrp_up.
*----Change order details with Technician name
          CALL FUNCTION 'BAPI_ALM_ORDER_MAINTAIN'
            TABLES
              it_methods   = i_methods
              it_header    = i_planrgrp
            it_header_up = i_planrgrp_up
              it_partner   = i_partner
              return       = i_return.
Thanks & regards,
Krishna

Try this way
CALL FUNCTION 'BAPI_SERVNOT_CREATE'
EXPORTING
* EXTERNAL_NUMBER =
notif_type = 'S3'
notifheader = ls_notif_h
* TASK_DETERMINATION = ' '
* SENDER =
* ORDERID =
IMPORTING
NOTIFHEADER_EXPORT = ls_notif_e
TABLES
* NOTITEM =
* NOTIFCAUS =
* NOTIFACTV =
* NOTIFTASK =
* NOTIFPARTNR =
* LONGTEXTS =
* KEY_RELATIONSHIPS =
return = lt_return
* IF lt_return IS INITIAL.                                               " <<< Comment this lie
read table lt_return into ls_return with key type = 'E'. " << Change
if sy-subrc ne 0.                                                             " << Change
COMMIT WORK AND WAIT.
write: / ls_notif_e-NOTIF_NO.
ELSE.
LOOP AT lt_return INTO ls_return.
WRITE:/ 'errors'.
* ls_return.
ENDLOOP.
endif.
a®

Updating T'code ME23N using BAPI's

Dear All,
I am updating T'code ME23N using BAPI " BAPI_PO_CHANGE". First i m tried in SE37 there its not updating it giving error like " PO could not be changed using the Enjoy-BAPI" for this i m trying in 4.6c.
Here i have to update only two check boxes those are NO_MORE_GR(ELIKZ) and FINAL_INV(EREKZ).
Please tell me any one there are any other BAPI's are avialable or how to slove this porblem.
Best Regards,
Srinivas.

Hello
I just have run this code in 4.6C. It working fine.
DATA: xreturn like BAPIRET2      occurs 0 with header line,
      xpoitem like BAPIMEPOITEM occurs 0 with header line,
      xpoitemx like BAPIMEPOITEMX occurs 0 with header line.
xpoitem-po_item = p_ebelp. " set position here
xpoitem-no_more_gr = 'X'.
xpoitem-final_inv = 'X'.
append xpoitem.
xpoitemx-po_item = p_ebelp. " set position here
xpoitemx-no_more_gr = 'X'.
xpoitemx-final_inv = 'X'.
append xpoitemx.
CALL FUNCTION 'BAPI_PO_CHANGE'
     EXPORTING
              purchaseorder    = p_ebeln "set ebeln here
     TABLES
              return           = xreturn
              poitem           = xpoitem
              poitemx          = xpoitemx.
if sy-subrc = 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
       EXPORTING WAIT = 'X'.
endif.

Issue with updating partitioned table

Hi,
Anyone seen this bug with updating partitioned tables.
Its very esoteric - its occurs when we update a partitioned table using a join to a temp table (not non-temp table) when the join has multiple joins and you're updating the partitoned column that isn't the first column in the primary key and the table contains a bit field. We've tried changing just one of these features and the bug disappears.
We've tested this on 15.5 and 15.7 SP122 and the error occurs in both of them.
Here's the test case - it does the same operation of a partitioned table and a non-partitioned table, but the partitioned table shows and error of "Attempt to insert duplicate key row in object 'partitioned' with unique index 'pk'".
I'd be interested if anyone has seen this and has a version of Sybase without the issue.
Unfortunately when it happens on a replicated table - it takes down rep server.
CREATE TABLE #table1
    (   PK          char(8) null,
        FileDate        date,
        changed         bit
CREATE TABLE partitioned (
PK         char(8) NOT NULL,
ValidFrom     date DEFAULT current_date() NOT NULL,
ValidTo       date DEFAULT '31-Dec-9999' NOT NULL
LOCK DATAROWS
PARTITION BY RANGE (ValidTo)
( p2014 VALUES <= ('20141231') ON [default],
p2015 VALUES <= ('20151231') ON [default],
pMAX VALUES <= (MAX) ON [default]
CREATE UNIQUE CLUSTERED INDEX pk
ON partitioned(PK, ValidFrom, ValidTo)
LOCAL INDEX
CREATE TABLE unpartitioned (
PK         char(8) NOT NULL,
ValidFrom     date DEFAULT current_date() NOT NULL,
ValidTo       date DEFAULT '31-Dec-9999' NOT NULL,
LOCK DATAROWS
CREATE UNIQUE CLUSTERED INDEX pk
ON unpartitioned(PK, ValidFrom, ValidTo)
insert partitioned
select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
insert unpartitioned
select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
insert #table1
select "ET00jPzh", "Jan 15 2015", 1
union all
select "ET00jPzh", "Jan 15 2015", 1
go
update partitioned
set    ValidTo = dateadd(dd,-1,FileDate)
from   #table1 t
inner join partitioned p on (p.PK = t.PK)
where p.ValidTo = '99991231'
and    t.changed = 1
go
update unpartitioned
set    ValidTo = dateadd(dd,-1,FileDate)
from   #table1 t
inner join unpartitioned u on (u.PK = t.PK)
where u.ValidTo = '99991231'
and    t.changed = 1
go
drop table #table1
go
drop table partitioned
drop table unpartitioned
go

wrt to replication - it is a bit unclear as not enough information has been stated to point out what happened. I also am not sure that your DBA's are accurately telling you what happened - and may have made the problem worse by not knowing themselves what to do - e.g. 'losing' the log points to fact that someone doesn't know what they should.   You can *always* disable the replication secondary truncation point and resync a standby system, so claims about 'losing' the log are a bit strange to be making.
wrt to ASE versions, I suspect if there are any differences, it may have to do with endian-ness and not the version of ASE itself.   There may be other factors.....but I would suggest the best thing would be to open a separate message/case on it.
Adaptive Server Enterprise/15.7/EBF 23010 SMP SP130 /P/X64/Windows Server/ase157sp13x/3819/64-bit/OPT/Fri Aug 22 22:28:21 2014:
-- testing with tinyint
1> use demo_db
1>
2> CREATE TABLE #table1
3>     (   PK          char(8) null,
4>         FileDate        date,
5> --        changed         bit
6> changed tinyint
7>     )
8>
9> CREATE TABLE partitioned (
10>   PK         char(8) NOT NULL,
11>   ValidFrom     date DEFAULT current_date() NOT NULL,
12>   ValidTo       date DEFAULT '31-Dec-9999' NOT NULL
13>   )
14>
15> LOCK DATAROWS
16>   PARTITION BY RANGE (ValidTo)
17>   ( p2014 VALUES <= ('20141231') ON [default],
18>   p2015 VALUES <= ('20151231') ON [default],
19>   pMAX VALUES <= (MAX) ON [default]
20>         )
21>
22> CREATE UNIQUE CLUSTERED INDEX pk
23>   ON partitioned(PK, ValidFrom, ValidTo)
24>   LOCAL INDEX
25>
26> CREATE TABLE unpartitioned (
27>   PK         char(8) NOT NULL,
28>   ValidFrom     date DEFAULT current_date() NOT NULL,
29>   ValidTo       date DEFAULT '31-Dec-9999' NOT NULL,
30>   )
31> LOCK DATAROWS
32>
33> CREATE UNIQUE CLUSTERED INDEX pk
34>   ON unpartitioned(PK, ValidFrom, ValidTo)
35>
36> insert partitioned
37> select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
38>
39> insert unpartitioned
40> select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
41>
42> insert #table1
43> select "ET00jPzh", "Jan 15 2015", 1
44> union all
45> select "ET00jPzh", "Jan 15 2015", 1
(1 row affected)
(1 row affected)
(2 rows affected)
1>
2> update partitioned
3> set    ValidTo = dateadd(dd,-1,FileDate)
4> from   #table1 t
5> inner join partitioned p on (p.PK = t.PK)
6> where p.ValidTo = '99991231'
7> and    t.changed = 1
Msg 2601, Level 14, State 6:
Server 'PHILLY_ASE', Line 2:
Attempt to insert duplicate key row in object 'partitioned' with unique index 'pk'
Command has been aborted.
(0 rows affected)
1>
2> update unpartitioned
3> set    ValidTo = dateadd(dd,-1,FileDate)
4> from   #table1 t
5> inner join unpartitioned u on (u.PK = t.PK)
6> where u.ValidTo = '99991231'
7> and    t.changed = 1
(1 row affected)
1>
2> drop table #table1
1>
2> drop table partitioned
3> drop table unpartitioned
-- duplicating with 'int'
1> use demo_db
1>
2> CREATE TABLE #table1
3>     (   PK          char(8) null,
4>         FileDate        date,
5> --        changed         bit
6> changed int
7>     )
8>
9> CREATE TABLE partitioned (
10>   PK         char(8) NOT NULL,
11>   ValidFrom     date DEFAULT current_date() NOT NULL,
12>   ValidTo       date DEFAULT '31-Dec-9999' NOT NULL
13>   )
14>
15> LOCK DATAROWS
16>   PARTITION BY RANGE (ValidTo)
17>   ( p2014 VALUES <= ('20141231') ON [default],
18>   p2015 VALUES <= ('20151231') ON [default],
19>   pMAX VALUES <= (MAX) ON [default]
20>         )
21>
22> CREATE UNIQUE CLUSTERED INDEX pk
23>   ON partitioned(PK, ValidFrom, ValidTo)
24>   LOCAL INDEX
25>
26> CREATE TABLE unpartitioned (
27>   PK         char(8) NOT NULL,
28>   ValidFrom     date DEFAULT current_date() NOT NULL,
29>   ValidTo       date DEFAULT '31-Dec-9999' NOT NULL,
30>   )
31> LOCK DATAROWS
32>
33> CREATE UNIQUE CLUSTERED INDEX pk
34>   ON unpartitioned(PK, ValidFrom, ValidTo)
35>
36> insert partitioned
37> select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
38>
39> insert unpartitioned
40> select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
41>
42> insert #table1
43> select "ET00jPzh", "Jan 15 2015", 1
44> union all
45> select "ET00jPzh", "Jan 15 2015", 1
(1 row affected)
(1 row affected)
(2 rows affected)
1>
2> update partitioned
3> set    ValidTo = dateadd(dd,-1,FileDate)
4> from   #table1 t
5> inner join partitioned p on (p.PK = t.PK)
6> where p.ValidTo = '99991231'
7> and    t.changed = 1
Msg 2601, Level 14, State 6:
Server 'PHILLY_ASE', Line 2:
Attempt to insert duplicate key row in object 'partitioned' with unique index 'pk'
Command has been aborted.
(0 rows affected)
1>
2> update unpartitioned
3> set    ValidTo = dateadd(dd,-1,FileDate)
4> from   #table1 t
5> inner join unpartitioned u on (u.PK = t.PK)
6> where u.ValidTo = '99991231'
7> and    t.changed = 1
(1 row affected)
1>
2> drop table #table1
1>
2> drop table partitioned
3> drop table unpartitioned

Creating a material with just the basic view using BAPI

Hi
   I intend to create a new material with just the basic view using BAPI BAPI_MATERIAL_SAVEDATA -
To do this - I believe I have to fill in the structure HEADDATA data - ( mandatory ) with the required values - I fill values for fields IND_SECTOR, MATL_TYPE & basic view ( check this field ) and leave the MATERIAL field as blank (assuming internal numbering ) and then fill values of the CLIENTDATA structure with values for the basic data view.
Is this correct ? Will my material number created be returned in the RETURN structure - how do I look for the material number exclusively in my RETURN structure ?

hi
good
go through this progarm which ll give you detail idea about BAPI_MATERIAL_SAVEDATA
REPORT ZBAPIMM01 LINE-SIZE 255 NO STANDARD PAGE HEADING
                 LINE-COUNT 065(001).
TABLES: T001L, "Storage Locations
        MARA, "General Material Data
        MAKT, "Material Descriptions
        MBEW, "Material Valuation
        MARC. "Plant Data for Material
DATA: BAPI_HEAD   LIKE BAPIMATHEAD,
      BAPI_MAKT   LIKE BAPI_MAKT,    "Material Description
      BAPI_MARA1 LIKE BAPI_MARA,    "Client Data
      BAPI_MARAX LIKE BAPI_MARAX,
      BAPI_MARC1 LIKE BAPI_MARC,    "Plant View
      BAPI_MARCX LIKE BAPI_MARCX,
      BAPI_MBEW1 LIKE BAPI_MBEW,    "Accounting View
      BAPI_MBEWX LIKE BAPI_MBEWX,
      BAPI_RETURN LIKE BAPIRET2.
DATA: BEGIN OF INT_MAKT OCCURS 100.
        INCLUDE STRUCTURE BAPI_MAKT.
DATA: END OF INT_MAKT.
DATA: BEGIN OF INT_MAT OCCURS 100,
         WERKS(4),     "Plant
         MTART(4),     "Material type
         MATNR(18),    "Material number
         MATKL(9) ,    "Material group
         MBRSH(1),     "Industry sector
         MEINS(3),     "Base unit of measure
         GEWEI(3),     "Weight Unit
         SPART(2),     "Division
         EKGRP(3),     "Purchasing group
         VPRSV(1),     "Price control indicator
         STPRS(12),    "Standard price
         PEINH(3),     "Price unit
         SPRAS(2),     "Language key
         MAKTX(40),     "Material description
       END OF INT_MAT.
SELECT-OPTIONS:
            PLANT    FOR MARC-WERKS OBLIGATORY MEMORY ID PLT,
            MATERIAL FOR MARA-MATNR MEMORY ID MAT,
            MATLTYPE FOR MARA-MTART MEMORY ID MTY,
            DIVISION FOR MARA-SPART MEMORY ID DIV.
PARAMETERS: F_FILE LIKE RLGRAP-FILENAME
             DEFAULT 'C:\DATA\ZMATERIAL.XLS' MEMORY ID F_FILE,
             GETDATA AS CHECKBOX, "Tick to download materials data to local harddisk
             UPDDATA AS CHECKBOX. "Tick to update date to Materials Master
IF GETDATA = 'X'.
   PERFORM DOWNLOAD_DATA.
   PERFORM DOWNLOAD_FILE.
ENDIF.
IF UPDDATA = 'X'.
   PERFORM UPLOAD_FILE.
   PERFORM UPDATE_MM.
ENDIF.
FORM DOWNLOAD_DATA.
SELECT * FROM MARC WHERE LVORM EQ ' '
                      AND WERKS IN PLANT
                      AND MATNR IN MATERIAL.
    CLEAR MARA.
    SELECT SINGLE * FROM MARA WHERE MATNR = MARC-MATNR.
    CHECK MATLTYPE.
    CHECK DIVISION.
    CLEAR MBEW.
    SELECT SINGLE * FROM MBEW WHERE MATNR = MARC-MATNR
                                AND BWKEY = MARC-WERKS.
    CLEAR MAKT.
    SELECT SINGLE * FROM MAKT WHERE SPRAS = 'EN'
                                AND MATNR = MARC-MATNR.
    WRITE:/ MARC-WERKS,    "Plant
            MARA-MTART,    "Material type
            MARA-MATNR,    "Material number
            MARA-MATKL,    "Material group
            MARA-MBRSH,    "Industry sector
            MARA-MEINS,    "Base unit of measure
            MARA-GEWEI,    "Weight Unit
            MARA-SPART,    "Division
            MARC-EKGRP,    "Purchasing group
            MBEW-VPRSV,    "Price control indicator
            MBEW-STPRS,    "Standard price
            MBEW-PEINH,    "Price unit
            MAKT-SPRAS,    "Language key
            MAKT-MAKTX.    "Material description
            INT_MAT-WERKS = MARC-WERKS.    "Plant
            INT_MAT-MTART = MARA-MTART.    "Material type
            INT_MAT-MATNR = MARA-MATNR.    "Material number
            INT_MAT-MATKL = MARA-MATKL.    "Material group
            INT_MAT-MBRSH = MARA-MBRSH.    "Industry sector
            INT_MAT-MEINS = MARA-MEINS.    "Base unit of measure
            INT_MAT-GEWEI = MARA-GEWEI.    "Weight Unit
            INT_MAT-SPART = MARA-SPART.    "Division
            INT_MAT-EKGRP = MARC-EKGRP.    "Purchasing group
            INT_MAT-VPRSV = MBEW-VPRSV.    "Price control indicator
            INT_MAT-STPRS = MBEW-STPRS.    "Standard price
            INT_MAT-PEINH = MBEW-PEINH.    "Price unit
            INT_MAT-SPRAS = MAKT-SPRAS.    "Language key
            INT_MAT-MAKTX = MAKT-MAKTX.    "Material description
            APPEND INT_MAT.
            CLEAR INT_MAT.
ENDSELECT.
ENDFORM.
FORM DOWNLOAD_FILE.
call function 'WS_DOWNLOAD'
EXPORTING
    FILENAME                      = F_FILE
    FILETYPE                      = 'DAT'
FILETYPE                      = 'WK1'
tables
    data_tab                      = INT_MAT
EXCEPTIONS
    FILE_OPEN_ERROR               = 1
    FILE_WRITE_ERROR              = 2
    INVALID_FILESIZE              = 3
    INVALID_TYPE                  = 4
    NO_BATCH                      = 5
    UNKNOWN_ERROR                 = 6
    INVALID_TABLE_WIDTH           = 7
    GUI_REFUSE_FILETRANSFER       = 8
    CUSTOMER_ERROR                = 9
    OTHERS                        = 10.
IF SY-SUBRC = 0.
   FORMAT COLOR COL_GROUP.
   WRITE:/ 'Data Download Successfully to your local harddisk'.
   SKIP.
ENDIF.
ENDFORM.
FORM UPLOAD_FILE.
call function 'WS_UPLOAD'
EXPORTING
    FILENAME                      = F_FILE
    FILETYPE                      = 'DAT'
FILETYPE                      = 'WK1'
tables
    data_tab                      = INT_MAT
EXCEPTIONS
    FILE_OPEN_ERROR               = 1
    FILE_WRITE_ERROR              = 2
    INVALID_FILESIZE              = 3
    INVALID_TYPE                  = 4
    NO_BATCH                      = 5
    UNKNOWN_ERROR                 = 6
    INVALID_TABLE_WIDTH           = 7
    GUI_REFUSE_FILETRANSFER       = 8
    CUSTOMER_ERROR                = 9
    OTHERS                        = 10.
IF SY-SUBRC = 0.
   FORMAT COLOR COL_GROUP.
   WRITE:/ 'Data Upload Successfully from your local harddisk'.
   SKIP.
ENDIF.
ENDFORM.
FORM UPDATE_MM.
LOOP AT INT_MAT.
Header
    BAPI_HEAD-MATERIAL        = INT_MAT-MATNR.
    BAPI_HEAD-IND_SECTOR      = INT_MAT-MBRSH.
    BAPI_HEAD-MATL_TYPE       = INT_MAT-MTART.
    BAPI_HEAD-BASIC_VIEW      = 'X'.
    BAPI_HEAD-PURCHASE_VIEW   = 'X'.
    BAPI_HEAD-ACCOUNT_VIEW    = 'X'.
Material Description
    REFRESH INT_MAKT.
    INT_MAKT-LANGU           = INT_MAT-SPRAS.
    INT_MAKT-MATL_DESC       = INT_MAT-MAKTX.
    APPEND INT_MAKT.
Client Data - Basic
    BAPI_MARA1-MATL_GROUP     = INT_MAT-MATKL.
    BAPI_MARA1-BASE_UOM       = INT_MAT-MEINS.
    BAPI_MARA1-UNIT_OF_WT     = INT_MAT-GEWEI.
    BAPI_MARA1-DIVISION       = INT_MAT-SPART.
    BAPI_MARAX-MATL_GROUP = 'X'.
    BAPI_MARAX-BASE_UOM   = 'X'.
    BAPI_MARAX-UNIT_OF_WT = 'X'.
    BAPI_MARAX-DIVISION   = 'X'.
Plant - Purchasing
    BAPI_MARC1-PLANT      = INT_MAT-WERKS.
    BAPI_MARC1-PUR_GROUP = INT_MAT-EKGRP.
    BAPI_MARCX-PLANT      = INT_MAT-WERKS.
    BAPI_MARCX-PUR_GROUP = 'X'.
Accounting
    BAPI_MBEW1-VAL_AREA   = INT_MAT-WERKS.
    BAPI_MBEW1-PRICE_CTRL = INT_MAT-VPRSV.
    BAPI_MBEW1-STD_PRICE = INT_MAT-STPRS.
    BAPI_MBEW1-PRICE_UNIT = INT_MAT-PEINH.
    BAPI_MBEWX-VAL_AREA   = INT_MAT-WERKS.
    BAPI_MBEWX-PRICE_CTRL = 'X'.
    BAPI_MBEWX-STD_PRICE = 'X'.
    BAPI_MBEWX-PRICE_UNIT = 'X'.
    WRITE:/ BAPI_HEAD, BAPI_MARC1.
    call function 'BAPI_MATERIAL_SAVEDATA'
      exporting
        HEADDATA                   = BAPI_HEAD
        CLIENTDATA                 = BAPI_MARA1
        CLIENTDATAX                = BAPI_MARAX
        PLANTDATA                  = BAPI_MARC1
        PLANTDATAX                 = BAPI_MARCX
      FORECASTPARAMETERS         =
      FORECASTPARAMETERSX        =
      PLANNINGDATA               =
      PLANNINGDATAX              =
      STORAGELOCATIONDATA        =
      STORAGELOCATIONDATAX       =
        VALUATIONDATA              = BAPI_MBEW1
        VALUATIONDATAX             = BAPI_MBEWX
      WAREHOUSENUMBERDATA        =
      WAREHOUSENUMBERDATAX       =
      SALESDATA                  = BAPI_MVKE1
      SALESDATAX                 = BAPI_MVKEX
      STORAGETYPEDATA            =
      STORAGETYPEDATAX           =
      IMPORTING
        RETURN                     = BAPI_RETURN
      TABLES
        MATERIALDESCRIPTION        = INT_MAKT
      UNITSOFMEASURE             =
      UNITSOFMEASUREX            =
      INTERNATIONALARTNOS        =
      MATERIALLONGTEXT           =
      TAXCLASSIFICATIONS         =
      RETURNMESSAGES             =
      PRTDATA                    =
      PRTDATAX                   =
      EXTENSIONIN                =
      EXTENSIONINX               =
IF BAPI_RETURN-TYPE = 'E'.
   WRITE:/ 'Error Message ', BAPI_RETURN.
ENDIF.
ENDLOOP.
ENDFORM.
*---End of Program
thanks
mrutyun^

Issue with Update of Table VARINUM

Hi,
I am getting waiting Issues with Update of table VARINUM. Has anybody faced such an issue.
I have a lot of Jobs which are running in background. I am submitting it through a report. what can be the issue.
Regards,
Abhishek jolly

Thisi is quite old, but not answered properly yet, so there you go:
SAP generates a new job and temporary variant on report RSDBSPJS, for each HTTP call,which creates database locks on table VARINUM .
This causes any heavyweight BSP application to hang and give timeout errors.
The problem is fixed applying OSS note 1791958, which is not included in any service pack.

Y510p and problem with Update Nvidia Driver

Hi everyonei have problem with updating my y510p lenovo laptop nvidia driver ,my current nvidia driver version is 327.62 which i download from lenovo website,Now for better performance in new games like gta v and witcher3 ,i decide to updating nvidia driver,first remove my nvidia graphic driver from add or remove then download nvidia ver 350 from nvidia official web site , which nvidia website confirm it support my graphic card which is Gt755m , then i install new ver and during install i check clean install , after successful install , restart laptop , then there was problem . when i try to open nvidia control panel it wont running and an error showed up and said "You are not currently using a display attached to an NVIDIA GPU" .i try to open a game , game running in really low fps and i find out game run on hd graphic of my laptop and my nvidia graphic wont run .The only way to repair was i install my last nvidia driver 327.62 and run a system restore .guys what is your suggestion and how i can update my y510p nvidia driver ?Thanks

Hi Y510Man,
     The video graphics installation order is important. You need to install the Intel Graphics first, and then do the Nvidia. IIRC you should un-install the Nvidia driver, then re-install (or upgrade) the Intel HD Graphics driver. Reboot, and install the new Nvidia driver.
     I don't know why, but every time I upgraded my Y470 Nvidia driver, I had to use this procedure. First install, or re-install, the Intel driver, then install the Nvidia. You can't just upgrade the Nvidia driver without a re-install of the Intel. I think it has to do with the Optimus setting, and the automatic switching.
    Let us know how it goes.
Cheers
DragonRider

Problem with updating the PC Updater software

Good evening (from Germany). I have a problem with updating my Nokia Software Updater. I can download the setup and I can execute this. But when the installation starts (0%) a error message appears. It's a problem with Windows Installer but I don't know how to solve the problem. Here is a picture with the exactly error message:
http://img-up.net/?up=Nokia_probES8HJXXg.jpg
I hope somebody knows the anser with this software...
Greetings
OS: Windows XP SP2
Phone: Nokia 3110 classic Firmware: V 5.50
Message Edited by dernamenlose on 24-Apr-2008 08:56 PM

Good morning (from Denmark).
I hve the same problem.
OS: WinXP SP2
Phone: N73.
Greetings.

Problem with flash on IE11 after using adobe cleaner

Problem with flash on IE11 after using adobe cleaner to remove a trial version of photoshop because there was not any entry on add/remove applications in windows 8.1
Its to frustrating to reinstall everything. I tried everything from your support page with no luck…

Link for Download & Install & Setup & Activation problems may help
-Online Chat http://www.adobe.com/support/download-install/supportinfo/

Problem with updating DB table in using BAPI

Similar Messages

Maybe you are looking for