Problem while updating Item category using Bapi_salesorder_change

Hi,
Iam facing a probelm while updating item category using bapi Bapi_salesorder_change
In the Return table iam getting the folowing mesages.
Inforation mesage : Field 'PSTYV' cannot be changed, VBAPKOM 000010 ready for input
Error Message : Item 000010 cannot be processed.
Please find the code below
CLEAR wa_bapisdh1x.
wa_bapisdh1x-updateflag = 'U'.
CLEAR wa_order_item_inx.
wa_order_item_inx-itm_number = wa_vbap-posnr.
wa_order_item_inx-item_categ = 'X'.
wa_order_item_inx-UPDATEFLAG = 'U'.
APPEND wa_order_item_inx TO it_order_item_inx.
CLEAR wa_order_item_inx.
CLEAR wa_order_item_in.
wa_order_item_in-itm_number = wa_vbap-posnr.
wa_order_item_in-item_categ = 'ABC'.
APPEND wa_order_item_in TO it_order_item_in.
CLEAR wa_order_item_in.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
    EXPORTING
      salesdocument    = w_vbeln
      order_header_inx = wa_bapisdh1x
    TABLES
      return           = it_return
      order_item_in    = it_order_item_in
      order_item_inx   = it_order_item_inx
How can i correct it..
Regards
Kumar

Actually iam facing a strange problem here.
When i copy the program into another sample program and execute it iam able to change both the item catgegory and delivery block for particular sales order and item number.
But in my main program i have BDC for MB1B transaction to create the material document.
Once the material document is created succesfully iam using BAPI Sales_order_change to change the item category and delivery block..
In my main program iam not to change the item catgeory getting an error field PSTYV cannot be changed.
But the same code is running percfectly in the copied one..
How can i correct that..
Regards
Kumar

Similar Messages

Problem with updating pricing date using BAPI_SALESORDER_CHANGE

Hi,
I need to update pricing date on sales order (but only on item level).
I have been trying to use BAPI_SALESORDER_CHANGE but nothing changes.Bapi returns no errors, ends with success.
I hoped that bapi would change not only pricing date but also recalculate things the date affected.
Here is my code:
ls_head_inx-updateflag = 'U'.
ls_bapisdls-pricing = 'C'.
ls_item-itm_number = sales_order_posnr
ls_item-price_date = new_price_date
APPEND ls_item TO lt_item.
ls_item_inx-itm_number = sales_order_posnr
ls_item_inx-updateflag = 'U'.
ls_item_inx-price_date = 'X'.
APPEND ls_item_inx TO lt_item_inx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
          EXPORTING
            salesdocument     = sales_order
            order_header_inx = ls_head_inx
            logic_switch         = ls_bapisdls
          TABLES
            return                 = lt_return
            order_item_in     = lt_item
            order_item_inx   = lt_item_inx
Thanks & Regards,
Mario

Mario,
I run same code as yours and work for me fine, able to update ITEM pricing date.
I suppose you are using BAPI_TRANSACTION_COMMIT after your BAPI call, then only it will work.
Also note that VBKD table stores this date for header and item. In my system, there are generally only header rows in that table, but a new item row gets generated when I change the item date with the BAPI to some other date. Also, this BAPI sometimes issues a W message instead of ERROR for something like non-existing items, so carefully check your RETURN table too.
'Item 000002 does not exist' as WARNING message, so might be considering it as a success.
If nothing works, try to do the same thing for the same data using VA02 and check . If that works, BAPI will work surely.
Regards,
Diwakar

Problem while changing Sales order using 'BAPI_SALESORDER_CHANGE'

Hi all,
Below is my code to update delivery block value:
FORM call_bapi_salesorder_change .
DATA: iv_bapi_view LIKE order_view.
DATA: gt_sales_doc TYPE STANDARD TABLE OF sales_key, " Document Numbers to Be Selected
        gt_items TYPE STANDARD TABLE OF bapisdit. " Order Item Data for Document Numbers
*************************************************************8
DATA:order_headers_out LIKE bapisdhd OCCURS 0 WITH HEADER LINE.
DATA:order_header_inx LIKE bapisdh1x.
DATA: lv_salesdocument LIKE bapivbeln-vbeln.
data: lv_matnr(10) type c.
DATA:
gt_schdule TYPE STANDARD TABLE OF bapischdl, " for gl date & load date
gt_schdulex TYPE STANDARD TABLE OF bapischdlx, " for partner role and partner function.
        gt_return TYPE STANDARD TABLE OF bapiret2,
        gt_itemin TYPE STANDARD TABLE OF bapisditm,
        gt_iteminx TYPE STANDARD TABLE OF bapisditmx ,
        gt_bapisdh1 TYPE STANDARD TABLE OF bapisdh1.
DATA:gs_head_bapi TYPE bapisdh1x,
       gs_schdule TYPE bapischdl,
       gs_schdulex TYPE bapischdlx,
       gs_return TYPE bapiret2,
       gs_itemin TYPE bapisditm,
       gs_iteminx TYPE bapisditmx,
       gs_bapisdh1 TYPE bapisdh1.
CLEAR : gt_schdule,gt_schdulex,gs_return.
REFRESH gt_return.
gs_head_bapi-updateflag = 'U'.
SORT gt_final BY vbeln.
CLEAR gs_vbep.
REFRESH gt_vbep[].
CLEAR gs_final.
LOOP AT gt_final1 INTO gs_final.
    gs_itemin-itm_number = gs_final-posnr.
*move gs_final-matnr to lv_matnr."qx94162
   gs_itemin-material = gs_final-matnr.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
      EXPORTING
        input = gs_final-matnr
      IMPORTING
        output = gs_final-matnr.
   CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = lv_matnr
    IMPORTING
     output = lv_matnr.
   gs_itemin-material = lv_matnr.
    gs_itemin-material = gs_final-matnr.
    gs_iteminx-itm_number = gs_final-posnr.
    gs_iteminx-updateflag = 'U'.""changed to I
    gs_iteminx-material = 'X'.
    " gs_schdule-req_dlv_bl = gs_final-lifsp. " Delivery block
    gs_schdule-itm_number = gs_final-posnr.
    gs_schdulex-itm_number = gs_final-posnr.
    gs_schdule-sched_line = '0001'.
    gs_schdulex-sched_line = '0001'.
   MOVE gs_final-lifsp to gs_schdule-req_dlv_bl.
    gs_schdule-req_dlv_bl = gs_final-lifsp.
    gs_schdulex-req_dlv_bl = 'X'. " Delivery block
    gs_schdulex-updateflag = 'U'.
    gs_bapisdh1-sales_org = gs_final-vkorg.
    APPEND gs_schdule TO gt_schdule.
    APPEND gs_schdulex TO gt_schdulex.
    APPEND gs_itemin TO gt_itemin.
    APPEND gs_iteminx TO gt_iteminx.
   Append gs_BAPISDH1 to gt_BAPISDH1.
    lv_salesdocument = gs_final-vbeln.
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
      EXPORTING
        salesdocument               = lv_salesdocument
       ORDER_HEADER_IN             = gs_BAPISDH1
        order_header_inx            = gs_head_bapi
SIMULATION                  =
BEHAVE_WHEN_ERROR           = ' '
INT_NUMBER_ASSIGNMENT       = ' '
LOGIC_SWITCH                =
NO_STATUS_BUF_INIT          = ' '
      TABLES
        return                      = gt_return
   order_item_in               =    gt_itemin
   order_item_inx              = gt_iteminx
PARTNERS                    =
PARTNERCHANGES              =
PARTNERADDRESSES            =
ORDER_CFGS_REF              =
ORDER_CFGS_INST             =
ORDER_CFGS_PART_OF          =
ORDER_CFGS_VALUE            =
ORDER_CFGS_BLOB             =
ORDER_CFGS_VK               =
ORDER_CFGS_REFINST          =
      schedule_lines                = gt_schdule
      schedule_linesx               = gt_schdulex
ORDER_TEXT                  =
ORDER_KEYS                  =
CONDITIONS_IN               =
CONDITIONS_INX              =
EXTENSIONIN                 =
NFMETALLITMS                =
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    REFRESH: gt_schdule, gt_schdulex, gt_itemin , gt_iteminx.
    LOOP AT gt_return INTO gs_return.
      WRITE / gs_return-message .
    ENDLOOP .
ENDLOOP.
ENDFORM.                    " CALL_BAPI_SALESORDER_CHANGE
When I am using material value as 18342 using CONVERSION_EXIT_ALPHA_OUTPUT:
ORDER_HEADER_IN has been processed successfully
Material is not defined for sales org.A101, distr.chan.00, language DE
Error in ITEM_IN 000030
SCHEDULE_IN has been processed successfully
The sales document is not yet complete: Edit data
Sales document 5010000715 was not changed
and when I am using CONVERSION_EXIT_ALPHA_INPUT (000000000000018342)or while debuging when I am changing value to 0018342 :
I am getting below dump:
Runtime Errors         DATA_LENGTH_0
Exception              CX_SY_RANGE_OUT_OF_BOUNDS
Date and Time          21.10.2010 07:22:17
Information on where terminated
     Termination occurred in the ABAP program "SAPLVBAK" - in
      "MAP_VBAP_TO_BAPISDIT".
     The main program was "RS_TESTFRAME_CALL ".
     In the source code you have the termination point in line 168
     of the (Include) program "LVBAK001".
     The termination is caused because exception "CX_SY_RANGE_OUT_OF_BOUNDS"
      occurred in
     procedure "MAP_VBAP_TO_BAPISDIT" "(FORM)", but it was neither handled local
      nor declared
     in the RAISING clause of its signature.
     The procedure is in program "SAPLVBAK "; its source code begins in line
     99 of the (Include program "LVBAK001 ".
The same dump I am getting while executing this above BAPI from SE37 tcode with the same test data.
but I am able to change it though Va02 tcode.
Edited by: Arora26 on Oct 21, 2010 7:58 AM

Hi,
have you searched for OSS notes? The note 1137897 looks like related to your problem. It mentions different BAPI but I assume that both BAPI reuse same routines and therefore it might solve your problem as well.
Cheers

I am Trying to update Item category by using Standar API .. But no Updating .. and it show some erros message.. INV INV_VALID_CAT error message

Hi
I am using Standard API to Update Item category. But it was not updating.any value what passing to paramenter in API But iwas through some.. error mesage INV INV_VALID_CAT
Regards,
Sam

Please see if (PA_PROJECT_PUB.create_project Errors - The Class Category Is Invalid (Doc ID 1323904.1)) helps.
Thanks,
Hussein

Problem while updating Delivery date uisng BAPI_PO_CHANGE

Hi friends,
Iam facing a problem while updating delivery date of a purchase order using the bapi BAPI_PO_CHANGE
After the bapi is getting triggered iam geting sy-subrc = 0
But in the return parameters iam getting 3 error messages so iam unable to update the delivery date..
Error meesage which iam getting are
a) Purchase order still contains faulty items
b) Enter Tax Code
c) Instance 1000001 of object type PurchaseOrder could not be changed.
How can i correct it..
Please find my code below
LOOP AT it_eket INTO wa_eket.
    wa_poschedule-po_item = wa_eket-ebelp.
    wa_poschedule-sched_line = wa_eket-etenr.
    wa_poschedule-delivery_date = wa_eket-eindt.
    APPEND wa_poschedule TO poschedule.
    wa_poschedulex-po_item = wa_eket-ebelp.
    wa_poschedulex-sched_line = wa_eket-etenr.
    wa_poschedulex-po_itemX = 'X'.
    wa_poschedulex-sched_lineX = 'X'.
    wa_poschedulex-delivery_date = 'X'.
    APPEND wa_poschedulex TO poschedulex.
READ TABLE IT_EKPO INTO WA_EKPO WITH KEY EBELN = WA_EKET-EBELN
                                         EBELP = WA_EKET-EBELP.
      IF SY-SUBRC = 0.
      WA_POITEM-PO_ITEM = WA_EKPO-EBELP.
      APPEND WA_POITEM TO POITEM.
      WA_POITEMX-PO_ITEM = WA_EKPO-EBELP.
      WA_POITEMX-PO_ITEMX = 'X'.
      APPEND WA_POITEMX TO POITEMX.
     ENDIF.
    CALL FUNCTION 'BAPI_PO_CHANGE'
      EXPORTING
        purchaseorder = wa_eket-ebeln
      TABLES
        return        = t_bapiret2
        POITEM        = POITEM
        POITEMX       = POITEMX
        poschedule    = poschedule
        poschedulex   = poschedulex.
    READ TABLE t_bapiret2 INTO wa_bapiret2 WITH KEY type = 'E'.
    IF sy-subrc NE 0.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
* EXPORTING
*   WAIT          =
* IMPORTING
*   RETURN        =.
      IF sy-subrc = 0.
        WRITE : 'DELIVERY DATE UPDATED'.
      ENDIF.
    ENDIF.
how can i correct it...
Regards
Kumar

Hi,
Pass the following values...
POACCOUNT LIKE BAPIMEPOACCOUNT...
poaccount-TAX_CODE = ? (value)....
That should take care of the missing field.
Regards,
Madan..

Document Splitting problem while posting asset acquisition using F-90

Hi,
We are using ECC 6.0 with document splitting functionality and are facing problem while posting asset acquisition using F-90.
The transaction entry details are as below:
Document Type - KR
Vendor Line Item PKey - 31
Amount - 10000
Asset Line Item with PKey - 70, Transaction Type - 100
Amount - 10000
The Document Splitting Rule - 0000000012 is used and the Field Status Group for the Vendor Reconciliation Account and Asset Reconciliation account have Cost Center, Profit Center and Segment as "Optional" field.
The Balance Sheet Item - Asset Reconciliation Account has been created as
Secondary Cost Element - 90.
The Profit Center and Segment field have been made mandatory and zero balancing is also set in the settings for Document Splitting.
While posting asset acquisition using F-90, we are getting the error message - "Balancing Field "Profit Center" in line item 001 not filled"
The first line refers to the Vendor Line item.
Please let me know how to overcome this error.
Regards,
Ramanand

Please follow the below path and do config :-
IMG>FA>Asset Accounting>Integration with the General Ledger>Additional Account Assignment Objects>Specify Account Assignment Types for Account Assignment Objects
here you have to put KOSTL (Cost center) for both against APC and Dep run for each Dep area.
Thanks
Pyare

Facing problem while updating IInfotype 0009-bank details through workflow

Dear SAP Gurus,
I am facing a problem while updating Infotype 0009 through workflow which is integrdated with portal.
Scenario:
Employee logins to portal and changes his/her bank details like payee name, bank key, account number, postal code and city of bank, bank name etc.
Once he submits the request, my workflow is triggered through SAP_WAPI_START_WORKFLOW which is called from portal and goes through various approval steps and finally reaches the step where the container elements are finally to be updated in IT0009.
Field bank account number (BANKN), which is part of table PA0009 are easily updates using the FM HR_INFOTYPE_OPERATION by first enqueuing the employee number and after the update dequeuing it.
However fields like payee name (EMFTX) bank key (BANKL) , bank name(BANKA -structure BNKA_BF-this is automatically fetched based on bank key) and postal code(BKPLZ) and city of bank (BKORT) are from structure Q0009 (on the infotype 9 screen level) and from table BNKA (at table level). The problem is that these are not getting updated by HR_INFOTYPE_OPERATION as they are not the part of infotype 9.
Can anyone help me to understand how can these fields be updated ?
Quick help will be highly appreciated.

Hi Spantaleoni,
Thanks for your quick response.
Well actually the table BNKA is a master table for the bank information and we must not create entries in it or update the table programatically, rather we should use the available data in it.
Now say employee currently has bank as A and he wants to change it as B which is available in BNKA then he will just select the bank B from search help provided in portal which again comes from table BNKA only. Employee then submits the info and it must get updated in the infotype PA0009.
As far as think, this should be done on screen level of infotype PA0009 as I have already mentioned that certain fields are coming from structure Q0009 and they cannot be updated on PA0009 table level.
I am just looking for way through which I can update the screen of infotype PA0009 of employee through workflow.
Regards

There was a problem while updating ios 7.1 now my ipad isnt starting up just shows a symbol of itunes with a arrow towards it with its USB cable

there was a problem while updating ios 7.1 now my ipad isnt starting up just shows a symbol of itunes with a arrow towards it with its USB cable

YOU ARE IN RECOVERY MODE
1. Turn off iPad
2. Turn on computer and launch iTunes (make sure you have the latest version of iTune)
3. Plug USB cable into computer's USB port
4. Hold Home button down and plug the other end of cable into docking port.
DO NOT RELEASE BUTTON until you see picture of iTunes and plug
5. Release Home button.
ON COMPUTER
6. iTunes has detected iPad in recovery mode. You must restore this iPad before it can be used with iTunes.
7. Select "Restore iPad"...
Note:
1. Data will be lost if you do not have backup
2. You must follow step 1 to step 4 VERY CLOSELY.

Update sales order using BAPI_SALESORDER_CHANGE --- URGENT!!!!

Hello,
<b> I want to update Batch, Pricing date, Header text & Item text using BAPI_SALESORDER_CHANGE.</b>
But i am not able to do it.
i have written a code, but it's still not updating:
PARAMETERS: p_vbeln LIKE vbak-vbeln.
TYPES: BEGIN OF t_return.
        INCLUDE STRUCTURE bapiret2.
TYPES: END OF t_return.
TYPES: BEGIN OF t_order_item_in.
        INCLUDE STRUCTURE bapisditm.
TYPES: END OF t_order_item_in.
TYPES: BEGIN OF t_order_item_inx.
        INCLUDE STRUCTURE bapisditmx.
TYPES: END OF t_order_item_inx.
TYPES: BEGIN OF t_schedule_lines.
        INCLUDE STRUCTURE bapischdl.
TYPES: END OF t_schedule_lines.
TYPES: BEGIN OF t_schedule_linesx.
        INCLUDE STRUCTURE bapischdlx.
TYPES: END OF t_schedule_linesx.
TYPES: BEGIN OF t_order_text.
        INCLUDE STRUCTURE bapisdtext.
TYPES: END OF t_order_text.
DATA: l_vbeln              LIKE          bapivbeln-vbeln,
      i_order_header_inx   LIKE          bapisdh1x,
      i_order_header_in    LIKE          bapisdh1,
      i_return             TYPE TABLE OF t_return,
      i_order_item_in      TYPE TABLE OF t_order_item_in,
      wa_order_item_in     LIKE LINE OF i_order_item_in,
      i_order_item_inx     TYPE TABLE OF t_order_item_inx,
      wa_order_item_inx    LIKE LINE OF i_order_item_inx,
      i_schedule_lines     TYPE TABLE OF t_schedule_lines,
      wa_schedule_lines    LIKE LINE OF i_schedule_lines,
      i_schedule_linesx    TYPE TABLE OF t_schedule_linesx,
      wa_schedule_linesx   LIKE LINE OF i_schedule_linesx,
      i_order_text         TYPE TABLE OF t_order_text,
      wa_order_text        LIKE LINE OF i_order_text,
      w_return             LIKE          bapiret2,
      l_date               TYPE char10.
CLEAR l_vbeln.
l_vbeln = p_vbeln.
          UPDATE REJECTION REASON IN SALES ORDER                *
*WRITE sy-datum TO l_date.
i_order_header_inx-updateflag = 'U'.
REFRESH i_order_item_in.
CLEAR wa_order_item_in.
wa_order_item_in-itm_number = '000010'.
wa_order_item_in-batch = '2007450027'.
wa_order_item_in-price_date = sy-datum.
wa_order_item_in-reason_rej = '00'.
APPEND wa_order_item_in TO i_order_item_in.
REFRESH i_order_item_inx.
CLEAR wa_order_item_inx.
wa_order_item_inx-itm_number = '000010'.
wa_order_item_inx-updateflag = 'U'.
wa_order_item_in-batch = 'X'.
wa_order_item_in-price_date = 'X'.
wa_order_item_inx-reason_rej = 'X'.
APPEND wa_order_item_inx TO i_order_item_inx.
*wa_order_text-doc_number = l_vbeln.
**wa_order_text-TDOBJECT = 'EHSWA_MAN'.
***wa_order_text-text_id = '0001'.
**wa_order_text-TDTEXT = 'Header Texts'.
*wa_order_text-text_line = 'SYNGENTA HEADER'.
***wa_order_text-function = 'U'.
wa_order_text-doc_number = l_vbeln.
wa_order_text-itm_number = '000010'.
*wa_order_text-TDOBJECT = 'EBAN'.
wa_order_text-text_id = '0001'.
*wa_order_text-TDTEXT = 'Item text'.
wa_order_text-text_line = 'SYNGENTA TEXT'.
wa_order_text-function = '004'.
APPEND wa_order_text TO i_order_text.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
    salesdocument               = l_vbeln
ORDER_HEADER_IN             =
    order_header_inx            = i_order_header_inx
SIMULATION                  =
BEHAVE_WHEN_ERROR           = ' '
INT_NUMBER_ASSIGNMENT       = ' '
LOGIC_SWITCH                =
NO_STATUS_BUF_INIT          = ' '
TABLES
    return                      = i_return
    order_item_in               = i_order_item_in
    order_item_inx              = i_order_item_inx
PARTNERS                    =
PARTNERCHANGES              =
PARTNERADDRESSES            =
ORDER_CFGS_REF              =
ORDER_CFGS_INST             =
ORDER_CFGS_PART_OF          =
ORDER_CFGS_VALUE            =
ORDER_CFGS_BLOB             =
ORDER_CFGS_VK               =
ORDER_CFGS_REFINST          =
   schedule_lines              = i_schedule_lines
   schedule_linesx             = i_schedule_linesx
   order_text                  = i_order_text
ORDER_KEYS                  =
CONDITIONS_IN               =
CONDITIONS_INX              =
EXTENSIONIN                 =
IF sy-subrc = 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait   = 'X'
    IMPORTING
      return = w_return.
ENDIF.
Please help out.
Please send the code of it.
Thanks in advance...

START-OF-SELECTION.
Get Blocked Orders
PERFORM sub_select_orders.
PERFORM order_reason_for_reject.
END-OF-SELECTION.
Display output
PERFORM sub_display_output.
*&      Form sub_select_orders
      text
FORM sub_select_orders .
SELECT a~vbeln
         a~erdat
         a~erzet
         a~auart
         b~posnr
         FROM ( vbak as A
         INNER JOIN VBAP AS B
         on Bvbeln = AVBELN )
         INTO TABLE i_order_data
         WHERE a~vbeln IN s_ordno AND
               A~auart IN s_auart AND
               A~erdat IN s_orddt AND
               A~vkorg IN s_vkorg AND
               A~vtweg IN s_vtweg AND
               A~spart IN s_spart .
IF sy-subrc NE 0.
    MESSAGE i001.
No data selected
    LEAVE LIST-PROCESSING.
ENDIF.
ENDFORM.                    " sub_get_blocked_orders
*&      Form order_reason_for_reject
      text
--> p1        text
<-- p2        text
FORM order_reason_for_reject .
LOOP AT i_order_data INTO w_order_data.
    w_output-vbeln = w_order_data-vbeln.
    w_ordhdrx-updateflag = c_update.
Update Order Reason for rejection .
    w_orditem-ITM_NUMBER = w_order_data-posnr.
    w_orditem-reason_rej = p_abgru.
    append w_orditem to i_orditem .
    w_orditemx-ITM_NUMBER = w_order_data-posnr.
    w_orditemx-updateflag = c_update.
    w_orditemx-reason_rej = 'X'.
    append w_orditemx to i_orditemx .
    At end of vbeln .
    w_output-vbeln = w_order_data-vbeln .
      CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
        EXPORTING
          salesdocument    = w_order_data-vbeln
          order_header_in = w_ordhdr
          order_header_inx = w_ordhdrx
        TABLES
          ORDER_ITEM_IN    = i_orditem
          ORDER_ITEM_INX   = i_orditemx
          return           = i_bapiret.
      READ TABLE i_bapiret WITH KEY type = c_error
                           TRANSPORTING NO FIELDS.
      IF sy-subrc EQ '0'.
        move 'Order Reason for rejection update Failed' to
        w_output-message .
      ELSE.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            wait   = c_check
          IMPORTING
             return = i_return.
      move 'Order Reason for rejection update successful' to
      w_output-message .
     endif .
     refresh :i_orditemx , i_orditem .
    Endat .
    APPEND w_output TO i_output.
    CLEAR w_output.
endloop .
ENDFORM.                    " order_reason_for_reject

Problem while updating the Support Package 17 on my SAP WAS SP9

Hi,
I'm facing problem while updating the Support Package 17 on my SAP WAS SP9
ERROR 2006-10-13 10:23:22
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...).
Please help me in this regard.....
Thanks in advance...
Satya

Hello gentlemen, I am also having problem with the following running on 64 bit Windows and SQL2005/64 bit. I am erroring in Step 8 'Updating JDBC' driver. I am attempting to update from SP9 to SP18. The WEBAS Jave installed went flawless but I seem to be stuck here. Any help is appreciated...
ERROR 2006-11-22 10:13:57
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...).

Item category used for third party

Gurus,
need to know the item category used for third party process and its determination, kindly help.
thanks
SP

Dear Partasarathy,
there are three different processes within the third-party.
The usual third-party process (the delivery will be made directly from the third-party partner). The item category here is TAS in the standard.
The individual purchase order (the delivery will be done from third-party partner to SD-partner and then the normal delivery will be created from the sales order). The item category here is TAB in the standard.
The ALE-process is the third-party process where the purchase order (not only the purchase requisition) will be created after saving the sales order. The item category here is ALES in the standard.
I hope, this additional info helps you further.
Kind regards,
Akmal Vakhidov
Development Support IMS SD, SAP, Walldorf/Germany

Getting error message while updating Job attributes using PP03 for IT1641

Hey Guys,
We are getting error message while updating Job attributes using transaction PP03 for IT1641 (WC Attributes for JOB): 'Client has status not modifiable'.
Update to the infotype 1641 should not require open SAP system. Would anyone suggest any SAP note/solution?
Thanks...
Edited by: Karan Gheewala on Apr 3, 2008 9:06 PM

Solved using Note 123383 - WC: Customizing worker's compensation tables
Thanks,..

Access Privileges problem while updating ipod

Access Privileges problem while updating ipod
so im having troubles updating my ipod when i attempt to update it i get a message that says The ipod "Mitch" cannot be updated you do not have enough access privileges for this opperation
some of my things are updated but not all
any help would be greatly appreciated!
Dell Windows XP

hi j.block!
hmmmmmmmmmmm. one other thing that might be worth a try if all else fails. i have once seen something like this turn out to be caused by a really kinky version of this issue:
iTunes: "privileges" or "permissions" issue when importing audio CD or adding music to library
... where the permissions were odd on the ipod itself ... but i've only seen that happen once. it's probably worth checking on only if nothing else seems to be working for you.
love, b

Updation Error in Schedule line category using 'BAPI_SALESORDER_CHANGE'

HI ,
I am using BAPI_SALESORDER_CHANGE to Update schedule line category for an order.But the issue is...the entries are updated if it is having single schedule line item,but if more than on item it is giving error in Last Record.
15192625   000200 0001 2.608.596.065               130,000 21.09.2009 ZX CP
*15192625   000200 0002 2.608.596.065                 0,000 04.02.2010 ZX CP
*EV1                  335System error: Schedule line 0002 for item 000200 does not exist
EV4                  219Sales document 0015192625 was not changed
i have written the code like below:
loop at i_ma4_etenr.
          i_salesdocument = i_ma4_etenr-vbeln.
         i_order_header_inx-updateflag = 'U'.
        r_schedule_lines-itm_number = i_ma4_etenr-posnr.
        r_schedule_lines-sched_line = i_ma4_etenr-etenr.
        r_schedule_lines-sched_type = i__ma4_etenr-ettyp .
        APPEND r_schedule_lines TO i_schedule_lines.
        CLEAR : r_schedule_linesx.
        r_schedule_linesx-itm_number = i_y16v_ma4_etenr-posnr.
        r_schedule_linesx-sched_line = i_y16v_ma4_etenr-etenr.
        r_schedule_linesx-updateflag = 'U'.
        r_schedule_linesx-sched_type = 'X'.
        APPEND r_schedule_linesx TO i_schedule_linesx.
endloop.
        CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
          EXPORTING
            salesdocument               = i_salesdocument
            order_header_inx            = i_order_header_inx
          TABLES
            return                      = i_return
            schedule_lines              = i_schedule_lines
            schedule_linesx             = i_schedule_linesx.
Thanks in Advance,
Sateesh Kumar.

Hi,
As you are facing error , so check wheather in VA02 schedule line fields have been uploaded or not initially.
If they are not uploaded then you will be facing the error.
Otherwise check:
Did you pass the X fields for the schedule lines properly. As you are changing only the schedule lines, Just pass the SCHEDULE_LINES , SCHEDULE_LINESX Internal tables.
Please also check whether anything is passed to ORDER_ITEM_INX- UPDATE field. it should be blank.
May it helps you.
Regards,
DS.

BAPI_SALESORDER_CHANGE - not updating ITEM CATEGORY(VBAP-PSTYV)

Hi all,
I have used bapi to change sales order but the Item category(pstyv) is not updating .
please tell me whether it needs to be passed to the bapi structure , if passed then how to retrieve (table) the item cateogry(pstyv) for the material.
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
            EXPORTING
              salesdocument               = e_vbeln
             ORDER_HEADER_IN             = wa_hdr
              order_header_inx           = wa_hdrx
            tables
              return                     = i_ret
             ORDER_ITEM_IN               = i_item
             ORDER_ITEM_INX              = i_itemx
             SCHEDULE_LINES              = i_sch
             SCHEDULE_LINESx             = i_schx
              EXTENSIONIN                = i_parex.
          endif.
please help me out.

Hi,
I think if you use FM BAPI_SALESORDER_CHANGE, you have to explicitly specify the field and its value you want to change. So put the value you want in the field ORDER_ITEM_IN-ITEM_CATEG and also "X" to ORDER_ITEM_INX-ITEM_CATEG and see what happen.
Hope it helps,
Chang

Problem while updating Item category using Bapi_salesorder_change

Similar Messages

Maybe you are looking for