Not able to create item under initiative in SAP PPM thru SAP EP 7.3

Hello,
We have deployed SAP BP for PPM on SAP EP for PPM. We have created successfully created initiative under the bucket.
Now we are trying to add item under the initiative but the SAP standard webdynpro ABAP application gives error.
Below are the steps we perform on portal:
Under Portfolio and Project Admin --> Portfolio Structure --> Select the bucket --> Select the initiative --> Add item
On the first instance it does not saves the item (no message displyed for Data Saved successfully), on second time click of Save it gives attached error:

Hi Sneha,
I think in the first instance it has saved the item and when you tried second time, item ID is conflicting. So change the item id and check.
At the same time, check whether the item id-11 is linked to initiative after the first instance of save.
Regards,
Ravi

Similar Messages

Not able to remove items from initiative

Hello All,
We are on PPM 5.0 and I am trying to remove added items from the 'initiative' but I am not able to remove them.
Can someone kindly help, as to what might be preventing from removing items from initiatives.
Thanks,
Sachin

Hi,
If you want to remove the Items from Intiative , you need remove the relationships object . Not possible to delete directly !
Steps :
Navigate to the Relationships tab , then go to the Sub tab Related Objects , select the Item and click Delete Assignment. You will remove the Item from Initiative dashboard !
Hope it works for you !
Regards,
Vincent
Edited by: ddd002 on Oct 4, 2011 6:53 AM

Not able to create sales order using BAPI - BAPI_SALESORDER_CREATEFROMDAT2

Hi Experts,
I am not able to create sales order . I am using BAPI - BAPI_SALESORDER_CREATEFROMDAT2
to create sales order .I am passing external sales order number to the parameter
SALESDOCUMENTIN.
I am getting following error.
"524   |Only quantity 1 EA is allowed (Item 00001"
Here EA is UOM(Unit of measurement).
Below is the sample program through which i am trying to create the sales order.
*& Report ZSDC_SALES_TEST
report zsdc_sales_test.
*DATA: wa_bapi_header    TYPE bapisdhd1.
Include Name    - ZSDC_SALES_ORD_UPLOAD_TOP
Program Name    - ZSDC_SALES_ORD_UPLOAD_1393
Program Title   - Include for Data Declaration and selection screen
Created by      - Lalitha W
Created on      - 18-Nov-2008
Object ID       - SD_C_1393_SALES_ORDER_UPLOAD
Request Id      - SD3K905579
Description - This is a common INCLUDE for data declarations and
*selection screen details.
                        HISTORY
Date    |Developer |Req by    | Description              |Reference ID
        |          |          |                          |
        |          |          |                          |
                           TYPE-POOLS
*TYPE-POOLS: truxs, abap, slis.
                          TABLES
*TABLES: t100.
                           TYPES
types:begin of   ty_header,
        auart(4)    type c,    " Sales Order Type
        vkorg(4)    type c,    " Sales Organization
        vtweg(2)    type c,    " Distrubution Channel
        spart(2)    type c,    " Division
        kunnr_1(10) type c,    " Sold to Party
        kunnr_2(10) type c,    " Ship to Party
        augru(3)    type c,    " Order Reason
        bstkd(35)   type c,    " PO Number
        bstdk(10)   type c,    " PO Date
        ketdat(10) type c,    " Required Delivery Date
        zterm(4)    type c,    " Payment Terms
        inco1(3)    type c,    " Inco Terms -1
        inco2(28)   type c,    " Inco Terms -2
        prsdt(10)   type c,    " pricing date
        waerk(5)    type c,    " Document Currency
        vkbur(4)    type c,    " Sales Office
        vkgrp(3)    type c,    " Sales group
        pltyp(2)    type c,    " Price List type
        kdgrp(2)    type c,    " Customer Group
        bstkd_e(35) type c,    " Ship-to-party PO number
        submi(10)   type c,    " Collective Number
        bname(35)   type c,    " Name
        ihrez(12)   type c,    " Your Reference
        kschl_1(4)   type c,    " Condition Type
        kbetr_1(11) type c,    " Amount
        kschl_2(4)   type c,    " Condition Type
        kbetr_2(11) type c,    " Amount
        kschl_3(4)   type c,    " Condition Type
        kbetr_3(11) type c,    " Amount
       partner_1(25) TYPE c,    " Partner(Bill To Party Number)
       partner_2(25) TYPE c,    " Partner(Payer Number)
       partner_3(25) TYPE c,    " Partner(Sales Responsible Number)
       partner_4(25) TYPE c,    " Partner(Order admin)
       partner_5(25) TYPE c,    " Partner(Contact person)
        partner_1(10) type c,    " Partner(Bill To Party Number)
        partner_2(10) type c,    " Partner(Payer Number)
        partner_3(10) type c,    " Partner(Sales Responsible Number)
        partner_4(10) type c,    " Partner(Order admin)
        partner_5(10) type c,    " Partner(Contact person)
        tdspras_1(2) type c,
        text_1(500)   type c,    " Text Before Items Z012
        tdspras_2(2) type c,
        text_2(500)   type c,    " Invocie Up Z034
        tdspras_3(2) type c,
        text_3(500)   type c,    " Invocie Down Z035
        tdspras_4(2) type c,
        text_4(500)   type c,    " Customer Reference Continue Z018
        tdspras_5(2) type c,
        text_5(500)   type c,    " Dispatch Marks/ Order Z019
        tdspras_6(2) type c,
        text_6(500)   type c,    " Ordered By Z003
        tdspras_7(2) type c,
        text_7(500)   type c,    " Sales Parameters Z002
        kvgr1(3)      type c,    " Industry
        kvgr2(3)      type c,    " customer BU
end of ty_header.
types: begin of ty_item,
          bstkd(35)     type c,    " PO Number
          bstdk(10)     type c,    " PO Date
          bstkd_e(35)   type c,    " Ship-to-party PO number
          posnr(6)      type c,    " POSTION NUMBER
          matnr(18)     type c,    " Material Number
          kwmeng(18)    type c,    " Order Quantity
          pstyv(4)      type c,    " Sales doc. item categ
          kursk(18)     type c,    " EXCHANGE RATE****
          ffprf(8)      type c,    " DIP PROFILE
          werks(4)      type c,    " Delivering Plant
          vstel(4)      type c,    " SHIPPING POINT
          lgort(4)      type c,    " STORAGE LOCATION
          route(6)      type c,    " Route
          kurrf(18)     type c,    " EXCHANGE RATE-FI
          ntgew(18)     type c,    " Net Weight
          brgew(18)     type c,    " Gross Weight
          gewei(3)      type c,    " Weight Unit
          prctr(10)     type c,    " profit center
          abgrs(6)      type c,    " RESULT ANALYSIS KEY
          kalsm_k(4)    type c,    " COSTING SHEET
          kschl_1(4)    type c,    " Condition Type
          kbetr_1(11)   type c,    " Amount
          kschl_2(4)    type c,    " Condition Type
          kbetr_2(11)   type c,    " Amount
          kschl_3(4)    type c,    " Condition Type
          kbetr_3(11)   type c,    " Amount
          text_1(500)    type c,    " material Text 0001
          tdspras_1(1)   type c,
          text_2(500)    type c,    " Pr Text 9001
          tdspras_2(1)   type c,
       end of ty_item.
types: begin of ty_schedule_line,
         bstkd(35)       type c, "PO number
         bstdk(10)       type c, "PO date
         bstkd_e(35)     type c, "Ship-to-party PO number
         posnr(6)        type c, "sales doc.Item
         etdat(10)       type c, "Schedule line date
         wmeng(2)        type c, "Order Quantity
        end of ty_schedule_line.
types: begin of ty_err ,
        auart(4)    type c,    " Sales Order Type
        vkorg(4)    type c,    " Sales Organization
        vtweg(2)    type c,    " Distrubution Channel
        spart(2)    type c,    " Division
        kunnr_1(10) type c,    " Sold to Party
        kunnr_2(10) type c,    " Ship to Party
        augru(3)    type c,    " Order Reason
        bstkd(35)   type c,    " PO Number
        bstdk(10)   type c,    " PO Date
        ketdat(10) type c,    " Required Delivery Date
        zterm(4)    type c,    " Payment Terms
        inco1(3)    type c,    " Inco Terms -1
        inco2(28)   type c,    " Inco Terms -2
        prsdt(10)   type c,    " pricing date
        waerk(5)    type c,    " Document Currency
        vkbur(2)    type c,    " Sales Office
        vkgrp(3)    type c,    " Sales group
        pltyp(2)    type c,    " Price List type
        kdgrp(2)    type c,    " Customer Group
        bstkd_e(35) type c,    " Ship-to-party PO number
        submi(10)   type c,    " Collective Number
        bname(35)   type c,    " Name
        ihrez(12)   type c,    " Your Reference
        kschl_1(4)   type c,    " Condition Type
        kbetr_1(11) type c,    " Amount
        kschl_2(4)   type c,    " Condition Type
        kbetr_2(11) type c,    " Amount
        kschl_3(4)   type c,    " Condition Type
        kbetr_3(11) type c,    " Amount
        partner_1(25) type c,    " Partner(Bill To Party Number)
        partner_2(25) type c,    " Partner(Payer Number)
        partner_3(25) type c,    " Partner(Sales Responsible Number)
        partner_4(25) type c,    " Partner(Order admin)
        partner_5(25) type c,    " Partner(Contact person)
        tdspras_1(2) type c,
        text_1(500)   type c,    " Text Before Items Z012
        tdspras_2(2) type c,
        text_2(500)   type c,    " Invocie Up Z034
        tdspras_3(2) type c,
        text_3(500)   type c,    " Invocie Down Z035
        tdspras_4(2) type c,
        text_4(500)   type c,    " Customer Reference Continue Z018
        tdspras_5(2) type c,
        text_5(500)   type c,    " Dispatch Marks/ Order Z019
        tdspras_6(2) type c,
        text_6(500)   type c,    " Ordered By Z003
        tdspras_7(2) type c,
        text_7(500)   type c,    " Sales Parameters Z002
        kvgr1(3)      type c,    " Industry
        kvgr2(3)      type c,    " customer BU
        message(600) type c,
end of ty_err.
types: begin of ty_t685a,
        kschl type kschl,
        krech type krech,
      end of ty_t685a.
                   INTERNAL TABLES
***header
data: g_krech_1(4)    type c,    " Calculation type for condition
       g_krech_2(4)    type c,    " Calculation type for condition
       g_krech_3(4)    type c.    " Calculation type for condition
      g_krech_4(4)    TYPE c,    " Calculation type for condition
      g_krech_5(4)    TYPE c,    " Calculation type for condition
      g_krech_6(4)    TYPE c,    " Calculation type for condition
      g_krech_7(4)    TYPE c,    " Calculation type for condition
      g_krech_8(4)    TYPE c,    " Calculation type for condition
      g_krech_9(4)    TYPE c,    " Calculation type for condition
      g_krech_10(4)   TYPE c,    " Calculation type for condition
      g_krech_11(4)   TYPE c,    " Calculation type for condition
      g_krech_12(4)   TYPE c,    " Calculation type for condition
      g_krech_13(4)   TYPE c,    " Calculation type for condition
      g_krech_14(4)   TYPE c,    " Calculation type for condition
      g_krech_15(4)   TYPE c,    " Calculation type for condition
      g_krech_16(4)   TYPE c,    " Calculation type for condition
      g_krech_17(4)   TYPE c,    " Calculation type for condition
      g_krech_18(4)   TYPE c,    " Calculation type for condition
      g_krech_19(4)   TYPE c,    " Calculation type for condition
      g_krech_20(4)   TYPE c.    " Calculation type for condition
Items
data:   g_krech_item_1(4)   type c,    " Calculation type for condition
        g_krech_item_2(4)   type c,    " Calculation type for condition
        g_krech_item_3(4)   type c.    " Calculation type for condition
       g_krech_item_4(4)   TYPE c,    " Calculation type for condition
       g_krech_item_5(4)   TYPE c,    " Calculation type for condition
       g_krech_item_6(4)   TYPE c,    " Calculation type for condition
       g_krech_item_7(4)   TYPE c,    " Calculation type for condition
       g_krech_item_8(4)   TYPE c,    " Calculation type for condition
       g_krech_item_9(4)   TYPE c,    " Calculation type for condition
       g_krech_item_10(4) TYPE c,    " Calculation type for condition
       g_krech_item_11(4) TYPE c,    " Calculation type for condition
       g_krech_item_12(4) TYPE c,    " Calculation type for condition
       g_krech_item_13(4) TYPE c,    " Calculation type for condition
       g_krech_item_14(4) TYPE c,    " Calculation type for condition
       g_krech_item_15(4) TYPE c,    " Calculation type for condition
       g_krech_item_16(4) TYPE c.    " Calculation type for condition
data: it_t685a type standard table of ty_t685a.
data: wa_bapi_header    type bapisdhd1,
     wa_bapi_headerx   TYPE bapisdhd1x,
      it_bapi_item      type table of bapisditm,
     it_bapi_itemx     TYPE TABLE OF bapisditmx,
      it_bapi_cond      type table of bapicond,
     it_bapi_condx     TYPE TABLE OF bapicondx,
      it_bapi_partner   type table of bapiparnr,
      it_bapi_shdl      type table of bapischdl,
     it_bapi_shdlx     TYPE TABLE OF bapischdlx,
     it_bapi_order_text type TABLE OF BAPISDTEXT,
      it_bapireturn     type table of bapiret2.
data: wa_bapi_item       like line of it_bapi_item,
      wa_bapi_itemx      LIKE LINE OF it_bapi_itemx,
       wa_bapi_cond       like line of it_bapi_cond,
      wa_bapi_condx      LIKE LINE OF it_bapi_condx,
       wa_bapi_partner    like line of it_bapi_partner,
       wa_bapi_shdl       like line of it_bapi_shdl,
      wa_bapi_shdlx      LIKE LINE OF it_bapi_shdlx,
      wa_bapi_order_text like LINE OF it_bapi_order_text,
       wa_bapireturn      like line of it_bapireturn.
*DATA: zmode(1) VALUE 'N'.
data: it_header      type standard table of ty_header.
*DATA: it_temp_header TYPE STANDARD TABLE OF ty_header.
data: it_item        type standard table of ty_item.
*DATA: it_temp_item   TYPE STANDARD TABLE OF ty_item.
data: it_err         type standard table of ty_err.
data: it_fline1 type standard table of tline,
      wa_fline1 type tline.
data: it_thead1 type thead.
data: it_fline2 type standard table of tline,
      wa_fline2 type tline.
data: it_thead2 type thead.
data: it_fline3 type standard table of tline,
      wa_fline3 type tline.
data: it_thead3 type thead.
data: it_fline4 type standard table of tline,
      wa_fline4 type tline.
data: it_thead4 type thead.
data: it_fline5 type standard table of tline,
      wa_fline5 type tline.
data: it_thead5 type thead.
data: wa_header         like line of it_header,
      wa_item           like line of it_item,
      wa_err            type ty_err,
     wa_bill           LIKE LINE OF it_bill,
     wa_bill1          LIKE LINE OF it_bill,
      wa_iterr          like line of it_err,
      wa_t685a          like line of it_t685a.
     wa_bill_item TYPE ty_bill_item.
data: it_schedule_line type standard table of ty_schedule_line,
      wa_schedule_line type ty_schedule_line.
data: sales_order_no     type bapivbeln-vbeln.
data: ext_sales_order_no type bapivbeln-vbeln.
Variable to be used to separate the fields which are concatenated by a
runtime character
*DATA: g_tabchar(1) TYPE c VALUE cl_abap_char_utilities=>horizontal_tab.
*DATA: wa_truxs_t_text_data TYPE truxs_t_text_data.
*DATA: g_filename      TYPE string,
     g_path          TYPE string,
     g_fullpath      TYPE string,
     g_user_action   TYPE i,
     g_file_encoding TYPE abap_encoding.
*DATA : g_text(8192),
data : g_mstring1(100) type c,
      g_mstring2(100) type c,
      g_mstring3(100) type c,
      g_mstring4(100) type c,
      g_mstring5(100) type c.
data: g_count1 type ebelp,
      g_str_count1(6) type c.
data: g_count type ebelp,
      g_str_count(6) type c.
*DATA: f_subrc      LIKE sy-subrc,
     f_subrc1     LIKE sy-subrc,
     f_error(500) TYPE c,
     item1(27)    TYPE c,
     item2(27)    TYPE c,
     item3(27)    TYPE c,
     item4(27)    TYPE c,
     i            TYPE ekpo-ebelp.
*DATA: g_billplan_header TYPE c,
     g_billplan_item TYPE c.
data : g_external_so type vbak-vbeln. "SO
                      SELECTION-SCREEN
selection-screen begin of block frame1 with frame title text-001 .
parameters:p_file1 type rlgrap-filename, "OBLIGATORY, "Header data.
           p_file2 type rlgrap-filename, "OBLIGATORY, "Item Data.
           p_file3 type rlgrap-filename,            "Schedule line.
           p_file4 type rlgrap-filename ."OBLIGATORY. "Error file.
selection-screen end of block frame1.
start-of-selection.
wa_bapi_header-doc_type     = 'Z0MX'. "order type
wa_bapi_header-sales_org    = '0130'."sales org
wa_bapi_header-distr_chan   = '13'. "distr channel
wa_bapi_header-division     = '13'. "division
Old code from copied program
wa_bapi_header-purch_no_s   = wa_header-kunnr_2. " Ship to party
New code as required in Finland project
We are using to Header ->Order Tab -> Ship to Party -> Purchase order no (BSTKD_E) to store Old legacy SO number
wa_bapi_header-purch_no_s   = 'MX100443'. "External SO i.e Old legacey SO number
wa_bapi_header-ref_1_s      = '0000666666'. "Sold to party
wa_bapi_header-ord_reason   = wa_header-augru.
wa_bapi_header-purch_no_c   = 'ddr1234'.    " PO number
wa_bapi_header-purch_date   = sy-datum.    " PO date
wa_bapi_header-req_date_h   = sy-datum.   " Required Delivery Date
wa_bapi_header-pmnttrms     = '01'.    " Payment Terms
wa_bapi_header-incoterms1   = wa_header-inco1.
wa_bapi_header-incoterms2   = wa_header-inco2.
wa_bapi_header-price_date   = wa_header-prsdt.    " Pricing date
wa_bapi_header-currency     = wa_header-waerk.    " Document Currency
wa_bapi_header-sales_grp = wa_header-vkgrp. " Sales group
wa_bapi_header-price_list   = wa_header-pltyp. " Price list type
wa_bapi_header-cust_group   = wa_header-kdgrp.   " Cust Group
wa_bapi_header-ship_type    = wa_header-vsart.   " Shipping Type
wa_bapi_header-purch_no_s   = wa_header-bstkd_e. " Ship-to-party po number
wa_bapi_header-collect_no   = wa_header-submi.   " Collective No.
wa_bapi_header-name         = wa_header-bname.   " Name
wa_bapi_header-ref_1        = wa_header-ihrez.   " Your Reference
wa_bapi_header-cust_grp1    = wa_header-kvgr1.   " Industry
wa_bapi_header-cust_grp2    = wa_header-kvgr2.   " Customer BU
*ENDFORM.                    " f_header
IF wa_header-partner_1 IS NOT INITIAL.
    wa_bapi_partner-partn_role = 'AG'.
    wa_bapi_partner-partn_numb = '0000666666'.
    wa_bapi_partner-itm_number = '000000'.
    append wa_bapi_partner to it_bapi_partner.
    clear wa_bapi_partner.
ENDIF.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
    exporting
      input = wa_header-partner_2
    importing
      output = wa_header-partner_2.
IF wa_header-partner_2 IS NOT INITIAL.
    wa_bapi_partner-partn_role = 'WE'.
    wa_bapi_partner-partn_numb = '0000666666'.
    wa_bapi_partner-itm_number = '000000'.
    append wa_bapi_partner to it_bapi_partner.
    clear wa_bapi_partner.
ENDIF.
perform f_item.
data : order_items_inx type table of bapisditmx with header line.
order_items_inx-material          = 'X'. "
order_items_inx-target_qty        = 'X'. "
order_items_inx-comp_quant        = 'X'. "
order_items_inx-trgqty_den        = 'X'.
order_items_inx-rnddlv_qty        = 'X'.
order_items_inx-updateflag = 'I'.
order_items_inx-target_qu = 'X'.
order_items_inx-plant             = 'X'. "
append order_items_inx.
call function 'BAPI_SALESORDER_CREATEFROMDAT2'
    exporting
      salesdocumentin = 'MX11111152'
order_header_in      = wa_bapi_header
         order_header_inx     = wa_bapi_headerx
importing
salesdocument        = sales_order_no
tables
return               = it_bapireturn
order_items_in       = it_bapi_item
order_items_inx      = order_items_inx
order_partners       = it_bapi_partner
   order_conditions_in = it_bapi_cond.
if sy-subrc is initial.
commit work.
endif.
*&      Form f_item
      text
form f_item .
call function 'CONVERSION_EXIT_ALPHA_INPUT'
    exporting
      input = wa_item-posnr
    importing
      output = wa_item-posnr.
wa_item-posnr = '000010'.
IF sy-subrc EQ 0. "IS INITIAL.
move wa_item-posnr to g_str_count."commented out by shakti
ENDIF.
wa_bapi_item-itm_number        = wa_item-posnr. " Line item
WA_BAPI_ITEM-PO_ITM_NO         = WA_ITEM-EBELP.
wa_bapi_item-division          = wa_item-spart.
wa_bapi_item-purch_no_c        = 'ddr1234'.   " po number
wa_bapi_item-purch_date        = sy-datum.   " po date
wa_bapi_item-purch_no_s        = 'MX11111112'. " Ship-to-party po number
wa_item-matnr = 'MAXIMO_SERVICE'.
call function 'CONVERSION_EXIT_MATN1_INPUT'
    exporting
      input        = wa_item-matnr
    importing
      output       = wa_item-matnr
    exceptions
      length_error = 1
      others       = 2.
if sy-subrc is initial.
    wa_bapi_item-material        = wa_item-matnr. "material
endif.
wa_bapi_item-target_qty        = '1'. " Order qty
wa_bapi_item-comp_quant = '1'.
wa_bapi_item-target_qu = 'EA'.
    wa_bapi_item-fixed_quan = '1'.
wa_bapi_item-comp_quant        = wa_item-kwmeng.
wa_bapi_item-trgqty_den        = '1'.
wa_bapi_item-rnddlv_qty        = wa_item-kwmeng.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
   EXPORTING
     input = wa_item-ps_psp_pnr
   IMPORTING
     output = wa_item-ps_psp_pnr.
IF sy-subrc = 0.
   wa_bapi_item-wbs_elem          = wa_item-ps_psp_pnr.
ENDIF.
wa_bapi_item-item_categ        = 'ZMAX'.
wa_bapi_item-ex_rate_fi        = wa_item-kurrf.
wa_bapi_item-dli_profil        = wa_item-ffprf.   " Dynamic item processor profile
wa_bapi_item-route             = wa_item-route.   " route
wa_bapi_item-exchg_rate        = wa_item-kursk.
wa_bapi_item-plant             = '2090'.   " Plant
wa_bapi_item-ship_point        = 'FN11'.   " Shipping point
wa_bapi_item-store_loc         = wa_item-lgort.   " stg loc
REPLACE ALL OCCURRENCES OF ',' IN wa_item-ntgew WITH '.'.
REPLACE ALL OCCURRENCES OF ',' IN wa_item-brgew WITH '.'.
wa_bapi_item-net_weight        = wa_item-ntgew. "
wa_bapi_item-gross_wght        = wa_item-brgew. "
call function 'CONVERSION_EXIT_CUNIT_INPUT'
    exporting
      input    = wa_item-gewei
      language = sy-langu
    importing
      output   = wa_item-gewei.
   EXCEPTIONS
     unit_not_found = 1
     OTHERS         = 2.
IF sy-subrc <> 0.
ENDIF.
wa_bapi_item-untof_wght        = 'KG'. " weight unit
replace all occurrences of ',' in wa_item-kursk with '.'.
replace all occurrences of ',' in wa_item-kurrf with '.'.
wa_bapi_item-profit_ctr        = wa_item-prctr.   " Profit center
wa_bapi_item-resanalkey        = wa_item-abgrs.   " RESULT ANALYSIS KEY
wa_bapi_item-cstg_sheet        = wa_item-kalsm_k. " COSTING SHEET
append wa_bapi_item to it_bapi_item.
endform.                    " f_item
Thanks & regards,
Chetan

see the following to create sales order:-
*& Report ZSALESORDER
*&DEVELOPED BY JANI KRUPA 4.10.2008
REPORT ZSALESORDER.
Parameters
Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d .
SELECTION-SCREEN END OF LINE.
Complete Deliver
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
SELECTION-SCREEN END OF LINE.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                         WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
v_text10 = 'Complete delivery'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
*Complete delivery
    header-COMPL_DLV = p_autlf.
    header-COMPL_DLV = 'X'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
item category
itemx-ITEM_CATEG = 'X'.
APPEND item.
APPEND itemx.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000020'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Fill schedule lines
lt_schedules_in-itm_number = '000020'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000020'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.

Not able to create Follow up transaction since it has been grayed out

Hi Experts,
We have a scenario where in we will create the Sales Transactions (OR) in ECC and then it will replicates to CRM.
In CRM we wants to create Returns Order (RE) as a follow up Transaction to OR (which is replicated from ECC to CRM) .
When I tried to create Returns Order (RE) in CRM as a follow up document to Sales Transaction (OR), the follow up Transaction CRM Returns (RE) has been grayed out. I mean it is in display mode only.
And then I created Sales Transaction (OR) in CRM itself and then I tried to create follow up Returns Transaction (RE) I was able to create.
But I am not able to Create Returns Order (RE) for the Sales Transactions (OR) that have been replicated from ECC to CRM.
Can anybody help me in resolving this issue. Any help ful answer will be rewarded with points.
Thanks in advance,
-Frederick Johnson.

Hi Fredrick,
Please check, whether you have completed all the steps for Copying Control for Business Transactions in the following path in IMG:
SPRO->Customer Relationship Management->Transactions->Basic Settings->Copying Control for Business Transactions:
- Define Copying Control for Transaction Types
In this step, you define the control for copying business transaction types.
To do this, you enter a source tranaction type and a target transaction type, and define the corresponding conditions for this combination.
- Define Copying Control for Item Categories
In this step, you define the control for copying item categories.
To do so, you enter a source item category and a target item category, and define the corresponding conditions.
- Define Item Category Determination when Copying
In this step, you define a specific item category determination which should be run during copying. The item category is used to find the target item category in the source transaction for the transaction type in the target transaction. This means that the transaction type for the source transaction is not relevant for the item category determination.
If the system cannot find an entry for the copying transaction in this table, the item category is found in the target transaction using the normal item category determination.
This might help you
regards
Srikantan

Not able to create a material document with movement type 103

I am not able to create a material document with movement type 103,
The system is populating the value as 101 .
How do I create a matdoc with movement type 103?

What is the error you receive? Please specify with message number.
On MIGO, you need to change the default value mvmt type value to 103 before you enter the PO number to be able to do 103.
Once this defualt value is set, you can enter the PO and item number in the document number fields and proceed with 103.
But you cannot change the mvmt type for already entered items from 101-103 or vice versa.
I think the 101-103 and 103-101 mvmt type conversion message is standard error message

Not able to create a customer master record with US as the country code

Hey All,
I am not able to create customer master data in the Transaction Code XD01/FD01 with the country code as US.
The error message for the same is *NO JURISDICTION CODE* COULD BE DETERMINED. I have checked the tax code settings but could not locate the problem.
I have checked the field in the account group(OBD2) but tax code is in optional status
and also checked the country settings for US in the transaction code OY17 still the same error message,
but when I tried checking the settings for a different company code's customer data base (us in county code)
I can see that there is a number mentioned in the address tab under tax jurisdiction field (beside time zone) which is not populating for this company code.
So, do anyone know where exactly we mention this number so that it populates in that field of address.
Hope am clear.
hope to receive a solution
thanks & regards
vinila

Hi,
You need to maintain the JURISDICTION CODE for country US. This JURISDICTION CODE code mainatanance purely FI/CO part.. it depends on the country's tax procedures.. Better take the help from your FI/CO consultant..
Menu path for Defining tax jurisdiction code
IMG -- Financial accounting -- Financial accounting global settings -- tax on sales and purchases -- basic settings -- define tax jurisdiction
reward if helps
Muthu
Edited by: Muthupandiyan on Mar 14, 2008 11:09 AM

Not able to create new folder in list/library sharepoint 2013 foundation

I am not able to create new folder in library and also not able to edit existing list item
Below is the error:
Getting Error Message for Exception
System.Web.HttpUnhandledException (0x80004005): Exception of type
'System.Web.HttpUnhandledException' was thrown. --->
System.NullReferenceException: Object reference not set to an
instance of an object. at
Microsoft.SharePoint.WebPartPages.ListFormWebPart.EnsureList()
at Microsoft.SharePoint.WebPartPages.ListFormWebPart.EnsureListAndFor
m() at
Microsoft.SharePoint.WebPartPages.ListFormWebPart.UseLegacyForm()
at Microsoft.SharePoint.WebPartPages.ListFormWebPart.CreateChildCont
rols() at System.Web.UI.Control.EnsureChildControls() at
Microsoft.SharePoint.WebPartPages.WebPart.get_WebPartMenu() at Mi
crosoft.SharePoint.WebPartPages.ListFormWebPart.CreateWebPartMenu()
at Microsoft.SharePoint.WebPartPages.ListFormWebPart.OnLoad(Ev...
Please help.It happens only on few sub sites

Hi V_K04,
You said that it happened only on few sub sites, whether this issue occurred on some subsites, and some subsite worked well.
Please check whether there are some differences between the subsites that worked well and the problematic subsites.
Whether this issue occurred on all libraries and lists on problematic subsites.
Whether there are some customizations in these problematic libraries and lists.
Please create a new library and a new list, test again, compare the result.
BestRegards,
Wendy
Wendy Li
TechNet Community Support

Not able to create customer master data with country code US

Hey All,
I am not able to create customer master data in the Transaction Code XD01/FD01 with the country code as US.
The error message for the same is NO JURISDICTION CODE COULD BE DETERMINED. I have checked the tax code settings but could not locate the problem.
Request you to provide me with a solution.
Thanks & Regards
VK

Hey all,
I have checked the field in the account group(OBD2) but its in optional status
and also checked the country settings for US in the transaction code OY17 still the same error message, but when i tried checking the settings for a differnt company code's customer data base i can see that there is a number mentioned in the address tab under tax jurisdiction feild (beside time zone) which is not populating for this company code.
so, do anyone know where exaclty we mention this number so that it populates in that field of address.
hope am clear
hope to receive a solution
thanks & regards
vinila

Not able to create purchase orders

Hi Experts,
I am not able to create purchase order , it is not allowing me to save , I I am giving purchase requisition number in Po and trying to crete po .When i give purchase requistion number all the revelant data is copied and when i click on item level tab of delivery address following error occurs : Address doesn't exist T001W 2000 00010. Then the entire PO is cancelled. not able to save going out of po screen
Please give me your valuable advice so that it can help me in resolving this issue
Please do the need ful
Regards
Ayub

Hi
We had to change the name text of he plant from ABCD COMPANY TO ABCD COMPANY PRIVATE LTD so , we had change and in both name 1:ABCD COMPANY PRIVATE LTD and NAme 2: ABCD COMPANY PRIVATE LTD
but in print out it the plant name appearing twice we decided to to erase name 1 that is we left blank and gave name 2:ABCD COMPANY PRIVATE LTD
But while creatimg Po from req ad the clicking item level adress tab eror pops up , and if i click on error tick mark it will take you out from Po screen
Regards
Ayub

GRC 10 ERM Not able to create Business/Single Role

Hello Experts,
In GRC 10, ERM, i have completed all the pre-requisites i.e. Maintaining Connectors, Configuration for Role Management, Maintained and generated the default MSMP workflow (methodology), maintaining role owners.
Now when i am trying to create a business role or let's say a single role i am unable to to do so as the edit button is disabled.
I just can't get through this.
Have i missed anything, and for the record when i tried to Import the Role(Under Role mass maintenance) from backend system i was successfully able to do so and that way only i could get my first role in GRC via import.
Now if i open this role and try to edit it, can;t do again, because edit button is disabled. But if i perform Role Update(Under Role Mass Maintenance) i can successfully change the attributes and other information and am able to see the new values.
Why is it like this, i am not able to create Roles in GRC, just i am able to import and update from backend.
This is really frustrating..what i am missing over here.
Experts pl. Kindly help!

Hi Triera,
1) After opening BRM, Create button is not greyed out. Its available, and if i click on it, then i see all the possible type of Roles that i can create i.e. Business role, composite role, Group, PD Profile, Profile, Single Role, Template etc.
2) When i try to edit a role by clicking on "Open" , and when the role opens, and then if I click on "Additional Details" (you said "More Details" , i believe you meant that only) link, then also the Edit button is not enabled. Its still greyed.
What else could this issue be possibly about.
Configuration- Check.
Authorizations- Check.
Workflow- Check.
Should i raise it with SAP.
Thanks.

Inbound document not able to created from an outbound message EDI

Dear all,
Our inbound delivery was not able to create automatically during GI for an outbound delivery. Our inbound delivery is created via an EDI output type in the header of the outbound delivery as soon as the GI is posted.
All along, all the inbound docs are able to generate. However, for this particular outbound document, which has already GI, does not trigger the inbound document creation, and I notice that the output type message having a red light status in the message output.
When I checked the error processing log on this output message type (i.e. the red status), error message said
No goods receiving point for the combination of plant 1120 and stor.loc.
Message no. VL377
Diagnosis
No goods receiving point could be found for plant 1120 and storage location for the inbound delivery item. The delivery should still take place for the goods receiving point .
System Response
The system does not permit creation of and/or changes to the inbound delivery item.
Procedure for System Administration
Check your settings in Customizing for Determining the goods receiving point.
The funny thing is I check the SPRO setup (i.e. Assign Goods Receiving Points for Inbound Deliveries), and I notice that the goods receipt point has been assigned and configured. Further, other Delivery Order which is having the same data, does not generate such error in the message output, and the inbound is able to create.
WHy?
thanks.
Edited by: tuffy on May 12, 2011 12:04 PM

Hi Sudhir,
This is a production thus, I don't want to save the inbound delivery, but it seem no problem of creating it, I will have the business create it.
So, how do i debug the idoc?
at first how do I find the idoc number of the failed transaction as when i go to the output message (i.e. in DO header) and check the processing log, system said..
Object 0082658402 (i.e. DO number)
output type: Stk Transfe Crte Deliv
Processing log for program /spe/sto_id_processing
no goods receiving point for the combination of plant 1120 and stor loc
no inbound delivery create for the replenishment order
There is IDOC no for this faild message (though GI is incurs)?
thanks.

Users are not able to create POs from PRs having Production Order (F)

Hi Gurus
Users are not able to create POs from PRs having Production Order (F) as creation indicator.
Whenever we are trying to convert the PR to PO we are getting the error message "Requisition has different doc. type NB and item cat. >&<" based on the below OSS# 938154 condition for the creation indicator type F.
Would you please investigate and advise what OSS notes are required to be able to use item category L (subcontracting) on a PO for a requisition generated from a network activity via Procurement Type = "Preliminary requisition for WBS element".
Thanks,
Sada.

Hi Ajay & Andra
Whenever we are trying to convert the PR to PO we are getting the error message "Requisition has different doc. type NB and item cat. >&<" based on the below OSS# 938154 condition for the creation indicator type Production order (F).
Our Business requirement as shown below.
1).The problem - we currently have no way to "direct requisition" an item to be procured via subcontracting - only itu2019s possible via MRP.
2).These behaviors are inconsistent as the requisition process should not impact the procurement process. Can we find a way to influence the creation indicator on the requisition so that it does not appear as a production order?
Please suggest any alternate method for achieving this.
Thanks & Regards
Sada

Not able to create function in ALBPM Studio 6.0

Hi,
I am trying to write a method that returns a string.
But i keep on getting an error which says that return statement can only be present in functions.
Now I tried all possible ways but i was not able to create a function.
Could anyone please help me out with creating a function in ALBPM. else tell me how do i return a string from a method.

Hi,
I suspect you have written a method having String return type but the method does not have return statement.
Go to the Catalogue component->BPM Object->Right click on the BPM object and select New Method->Give the method name. Now the method window will be opened. Go to the propertied tab of the right most panel. Set the return type as string. In the method window editor write your business logic. The below mentioned code is for sample one.
String msg = "Hello World";
return msg;
Bibhu

Not able to create new e-mail on N8 using Mail for...

Not able to create new e-mail on N8 using Mail for Exchange.
Currently using google for my domain, but settings are the same as explained on the google Sync webpage: http://www.google.com/support/mobile/bin/answer.py?hl=en&answer=147951
When creating reply on mail the application crashes. When creating new mail it says "Kan bewerking niet uitvoeren" in english: "Unable to execute action".
Any idea why creating mail is not possible?
Regards,
Joris

problem is known
more info there:
/t5/Nseries-and-S60-Smartphones/N8-syncing-with-Google-contacts-amp-calendar/td-p/772020
there is little workaround aslo.

Not able to create VF on T5-2 server

Not able to create VF on T5-2 server..
My interface card supports 64 VF but while craeting i am getting below error.
root@Solaris11U1-T5:~#
root@Solaris11U1-T5:~# ldm ls-io -l /SYS/MB/PCIE3/IOVNET.PF0
NAME                                      TYPE   BUS      DOMAIN   STATUS
/SYS/MB/PCIE3/IOVNET.PF0                  PF     pci_2    primary
[pci@380/pci@1/pci@0/pci@6/oce@0]
    maxvfs = 64
root@Solaris11U1-T5:~# ldm create-vf /SYS/MB/PCIE3/IOVNET.PF0
The parent bus pci_2 of the device /SYS/MB/PCIE3/IOVNET.PF0 does not currently
support IOV operations. Please check the iov= setting of this bus
root@Solaris11U1-T5:~#

Hi - have you tried first issuing 'ldm set-iov=on pci@380' ?
regards, Jeff

Not able to create item under initiative in SAP PPM thru SAP EP 7.3

Similar Messages

Maybe you are looking for