Account assignment while creating reservation using bapi

Hi , I am creating reservation using BAPI (BAPI_RESERVATION_CREATE1), but when I seeing the open reservation account assignment field is blank, could any on ehelp me on this, i.e what parameter I am missing in BAPI for account assignment.
best regards
pankaj

Hi,
there is not field to assign the account assignment in Bapi..
you need to assignt he account manaually.
Assign account assignment category.
    SELECT * FROM eban INTO TABLE lt_eban WHERE banfn = w_banfn .
    IF sy-subrc = 0.
      LOOP AT lt_eban .
        lt_eban-knttp = 'J'.    "assign your own account categeory
        MODIFY eban FROM lt_eban.
        COMMIT WORK AND WAIT.
      ENDLOOP.
endif.
Regards,
Prabhudas

Similar Messages

Problem while creating assets using BAPI

Use table enhancement BAPI_TE_ANLU
Diagnosis :The BAPIs for creating and changing assets currently support only those customer enhancements that relate to the user fields created using SAP enhancement AIST0002.
Can anybody give the appropriate solution why this error is coming while creating assets using BAPI.

Looks like you are trying to transfer custom fields into the asset master data that were not added following the steps in enhancement AIST0002.
Using EXTENSIONIN parameter, you can transfer user fields from the asset master record. However, it is not possible to transfer fields that are updated in user-defined tables. Only user fields that were defined using SAP enhancement AIST0002 and are automatically updated in table ANLU can be udpated in this way. This means you have to use table extension BAPI_TE_ANLU.
Enhancement AIST0002 contains function module EXIT_SAPL1022_001 as a component in which user fields can be implemented.
The documentation ( BAPIPAREX) of the structure that forms the basis for this parameter contains additional information about using this parameter.
Please check how table ANLU has been enhanced and also go through the documentation of enhancement AIST0002.
Regards,
Shyam

Error while creating GR using BAPI

*I am creating material document using BAPI_GOODSMVT_CREATE .
When I create the Material document using this BAPI I am able to create is successfully when there is no Account assignment category used means it blank at scheduling agreement level.
But if the Account assignment category is given at the scheduling agreement level then BAPI fails and shows the error message u201CNo goods receipt possible for purchase order.
I am using SAP version 4.6C
    SPLIT w_file-dln AT '.' INTO w_dd w_mm w_yyyy.
    CONCATENATE w_yyyy w_mm w_dd INTO w_dt.
    w_gm_hdr-pstng_date = w_dt.    " Posting Date
    w_gm_hdr-doc_date   = sy-datum." Doc Date
    w_gm_hdr-pr_uname   = sy-uname." User Name
    w_gm_cd-gm_code     = '01'.    "01 Goods Receipts for Purchase Order
    w_gm_itm-move_type = '101'.
    w_gm_itm-mvt_ind    = 'B'.
BAPI Call.
Edited by: Nandkumar Ghodke on May 21, 2010 4:15 PM
Edited by: Nandkumar Ghodke on May 21, 2010 4:16 PM

As per i know..
that the account assignment information applies to the item level and not to the schedule line level. This means that the quantities, values, and percentage rates indicate how the account assignment information of an item is assigned. This also applies to service items and purchase orders with invoicing plan
Thanks
Naresh

Error while creating BOM using BAPI 'BAPI_BOM_UPLOAD_SAVE'

Hi All,
We are getting an error as 'Data is incomplete' while trying to create BoM using the bapi 'BAPI_BOM_UPLOAD_SAVE', if the item contains Item category as 'T'. But for other item category like 'L' or 'N', the bapi is sucessfull.
The values that we pass to fill the item category 'T' are operation, item_cat, bom_itm_no, COMPON_QTY, FIXED_QTY as 'X', UNMEAS as 'ST', ITEM_TEXT1 and ITEM_TEXT2.
Anyone who has faced same problem or has a solution to the problem, kindly provide a solution.
Regards,
Vijay

The error you receive is because of different config for different Item Categories. Find out from the functional team what fields have they kept mandatory for the item category 'T'. You may not be passing one of those fields in the BAPI.
Try creating a BOM manually for item category 'T' and you may figure our which field you are missing.

Recon Accounts assignment while creating a new GL Account

Hey everybody,
I was wondering if there is any global rule to which accounts should be selected as Recon A/c while creating a GL master in fs00. From my point of understanding the only Recon A/c's are Accounts Receivable as recon account :Customer and Accounts Payable as recon account: Vendor! So in which situation do we select Recon account : Asset or Recon account: Contract Account Receivable?
If you could please help me figure this out, I would greatly appreciate.
Thanks in advance.
Nick
help.sap.com

General ledger is the main accounting record of a business which uses double-entry bookkeeping. In SAP, the central task of G/L accounting is to provide a comprehensive picture for external accounting and accounts. Reconciliation Accounts are G/L accounts that receive postings from a subsidiary ledgers. Meaning, transactions data are not posted directly to recon accounts. Example of recon accounts are Accounts Receivable, Accounts Payable and Fixed Assets G/L. For accounts receivable G/L the subsidiary ledger is the customer account. All transactions with the customers are posted directly to the customer account and the recon account is automatically updated. How this thing happen? Well, when you create a customer account you specify under the Company Code data the reconciliation account.
Regards
Sanil

Error while creating Contracts using BAPI

Hello,
I am trying to use BAPI BUS2014 to create new Purchasing Contracts. Now everything works fine, except for some strange cases where Contracts are failing out with a message as:
Reference document or master record has different language
I don't understand it why. Language being set in Contracts is defined for those items in MM and it works for others but not for all. I think I am missing some basic point here. Can anyone please suggest?
Any help is highly appreciated!
Cheers
EssKay

OK - stupid question. I did figure it out myself. Sorry for my impatience. This is my first BAPI program, so a bit too shaky
Cheers
EssKay

Error while creating BOM using BAPI (urgent)

Hi all,
Thanks for ur help. i am getting some error while creting a BOM using that BAPI
BAPI_MATERIAL_BOM_GROUP_CREATE.
errors are
1) Error/warning when checking the structure of the BOM group with ID =
2)Alternative does not exist for material assignment to material BAPIBOMFG1
is it mandatory to pass the bom group id to this bapi?
In bomgroup structure , i am not passing anything to BOM_GROUP field.
is it mandatory to pass this data? i am giving my coding below.plz suggest , where i am making mistake. it is urgent.
regards
pabitra
report z_bom_create
line-size 132
line-count 65
no standard page heading.
*-- DATA DECLARATION--
include <icon> .
*---Tables
tables : s076, t100, marc .
*---Types
types : begin of t_upload, " Upload file data
col1(18),
col2(10),
col3(30),
col4(12),
col5(50),
end of t_upload,
begin of t_split,
location like stpu-ebort,
end of t_split.
data:begin of i_return occurs 10.
include structure bapiret2.
data:end of i_return.
types:begin of t_item."occurs 10.
include structure BAPI1080_ITM_C.
types:end of t_item.
types:begin of t_subitem." occurs 10.
include structure BAPI1080_SUI_C.
types:end of t_subitem.
types:begin of t_header." occurs 10.
include structure BAPI1080_MBM_C.
types:end of t_header.
types:begin of t_bomgroup." occurs 10.
include structure BAPI1080_BGR_C.
types:end of t_bomgroup.
types:begin of t_variant." occurs 10.
include structure BAPI1080_BOM_C.
types:end of t_variant.
*--- Tables
data: i_upload type standard table of t_upload, " to hold data
i_upload1 type standard table of t_upload,
i_split type standard table of t_split,
i_item type standard table of t_item,
i_subitem type standard table of t_subitem,
i_header type standard table of t_header,
i_bomgroup type standard table of t_bomgroup,
i_variant type standard table of t_variant.
data: wa_upload type t_upload, " to hold file data,
wa_upload1 type t_upload, " to hold plan data,
wa_split type t_split,
wa_item type t_item,
wa_subitem type t_subitem,
wa_header type t_header,
wa_bomgroup type t_bomgroup,
wa_variant type t_variant.
data:v_matnr like mara-matnr,
v_start like sy-index,
v_count(3) type c.
*--Constants
data: c_dot type c value '.',
c_x type c value 'X',
c_comma type c value ','.
-------Selection Screen Design -
*Selection screen for input of upload file address
selection-screen skip 2.
selection-screen begin of block blk1 with frame.
parameters : p_file like rlgrap-filename obligatory .
parameters : p_matnr like mara-matnr obligatory,
p_werks like marc-werks obligatory memory id wrk,
p_stlan like afko-stlan obligatory default '1' .
selection-screen end of block blk1.
---AT SELECTION SCREEN -
at selection-screen on value-request for p_file.
*--For popup to select file.
perform f_give_help.
at selection-screen on p_matnr.
perform f_check_matnr.
-----START OF SELECTION -
*--Data upload using WS_Upload.
perform f_get_data.
perform f_get_bom_data.
perform f_get_bom_data1.
perform f_call_bapi.
*& Form f_give_help
text
--> p1 text
<-- p2 text
FORM f_give_help.
call function 'WS_FILENAME_GET'
exporting
mask = ',.,..'
mode = 'O'
importing
filename = p_file
exceptions
inv_winsys = 1
no_batch = 2
selection_cancel = 3
selection_error = 4
others = 5.
if sy-subrc <> 0 and not sy-msgty is initial.
message id sy-msgid type sy-msgty number sy-msgno
with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
ENDFORM. " f_give_help
*& Form f_check_matnr
text
--> p1 text
<-- p2 text
FORM f_check_matnr.
CALL FUNCTION 'BAPI_MAT_BOM_EXISTENCE_CHECK'
EXPORTING
MATERIAL = p_matnr
PLANT = p_werks
BOMUSAGE = '1'
VALID_FROM_DATE =
VALID_TO_DATE =
TABLES
RETURN = i_return.
ENDFORM. " f_check_matnr
*& Form f_get_data
text
--> p1 text
<-- p2 text
FORM f_get_data.
call function 'WS_UPLOAD'
exporting
CODEPAGE = ' '
filename = p_file
filetype = 'DAT'
tables
data_tab = i_upload
exceptions
conversion_error = 1
file_open_error = 2
file_read_error = 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.
message id sy-msgid type sy-msgty number sy-msgno
with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
ENDFORM. " f_get_data
*& Form f_get_bom_data
text
--> p1 text
<-- p2 text
FORM f_get_bom_data.
delete i_upload where col1 is initial.
delete i_upload where col1 cs 'ITEM'.
read table i_upload into wa_upload with key col1 = 'FINISHED GOOD:'.
if sy-subrc = 0.
v_matnr = wa_upload-col2.
if v_matnr <> p_matnr.
message e001(zl) with p_matnr.
endif.
else.
message e000(zl).
endif.
ENDFORM. " f_get_bom_data
*& Form f_get_bom_data1
text
--> p1 text
<-- p2 text
FORM f_get_bom_data1.
loop at i_upload into wa_upload where col1 CS 'FINISHED GOOD'.
v_start = sy-tabix + 1.
loop at i_upload into wa_upload1 from v_start .
if wa_upload1-col1 cs 'FINISHED GOOD'.
exit.
else.
perform f_split_upload_data.
endif.
endloop.
endloop.
ENDFORM. " f_get_bom_data1
*& Form f_split_upload_data
text
--> p1 text
<-- p2 text
FORM f_split_upload_data.
if not wa_upload1-col5 is initial.
if wa_upload1-col5 cs c_comma.
split wa_upload1-col5 at c_comma into table i_split.
loop at i_split into wa_split.
v_count = v_count + 1.
endloop.
if wa_upload1-col4 <> v_count.
wa_upload1-col4 = v_count.
endif.
clear wa_upload1-col5.
clear wa_split.
loop at i_split into wa_split.
wa_upload1-col5 = wa_split-location.
append wa_upload1 to i_upload1.
endloop.
else.
append wa_upload1 to i_upload1.
endif.
else.
append wa_upload1 to i_upload1.
endif.
ENDFORM. " f_split_upload_data
*& Form f_call_bapi
text
--> p1 text
<-- p2 text
FORM f_call_bapi.
clear wa_upload1.
wa_header-material = p_matnr.
wa_header-plant = p_werks.
wa_header-bom_usage = p_stlan.
append wa_header to i_header.
wa_bomgroup-bom_usage = p_stlan.
wa_bomgroup-created_in_plant = p_werks.
append wa_bomgroup to i_bomgroup.
wa_variant-alternative_bom = 1.
wa_variant-base_qty = 1.
wa_variant-valid_from_date = sy-datum.
append wa_variant to i_variant.
loop at i_upload1 into wa_upload1.
wa_item-item_no = wa_upload1-col1.
wa_item-item_cat = wa_upload1-col2.
wa_item-component = wa_upload1-col3.
wa_item-comp_qty = wa_upload1-col4.
append wa_item to i_item.
wa_subitem-subitem_qty = '1'.
wa_subitem-installation_point = wa_upload1-col5.
append wa_subitem to i_subitem.
endloop.
CALL FUNCTION 'BAPI_MATERIAL_BOM_GROUP_CREATE'
EXPORTING
TESTRUN = ' '
ALL_ERROR = ' '
TABLES
BOMGROUP = i_bomgroup
VARIANTS = i_variant
ITEMS = i_item
SUBITEMS = i_subitem
MATERIALRELATIONS = i_header
ITEMASSIGNMENTS =
SUBITEMASSIGNMENTS =
TEXTS =
RETURN = i_return.
if i_return[] is initial.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
*write: /'BOM created:', stpo-stlnr.
else.
*if not i_return[] is initial.
loop at i_return.
IF i_return-TYPE = 'E'.
errmsg-type = i_return-type.
errmsg-line = i_return-message.
append errmsg.
ULINE /1(108).
write:/ icon_led_RED as icon, i_return-MESSAGE.
ULINE /1(108).
ENDIF.
IF i_return-TYPE = 'W'.
errmsg-type = i_return-type.
errmsg-line = i_return-message.
append errmsg.
ULINE /1(108).
write:/ icon_led_YELLOW as icon, i_return-MESSAGE.
ULINE /1(108).
ENDIF.
ENDLOOP.
*write: / i_return-id, i_return-number, i_return-message(80).
*endloop.
*write: /'Error'.
endif.
ENDFORM. " f_call_bapi

Hi shashi,
Thanks for ur help.i tried after passing the group but it is giving same error.
i am getting the error
"Error/warning when checking the structure of the BOM group with ID= test"
i am gettig the above error when i put bomgroup-bom_group_identification = 'TEST'.
whatever i am putting in this field, the same error is comming having different value.
if i put--- bomgroup-bom_group_identification = ' '. then i will get error
"Error/warning when checking the structure of the BOM group with ID=
if i omit that field, then also , i am getting same error.
plz suggest what r the fields i need to pass for BOMGROUP structure for that bapi?
regards
pabitra

Batch not updating while creating delivery using bapi

Hi
I have used following bapi to create delivery BAPI_DELIVERYPROCESSING_EXEC and passed the following parameters into bapi
lt_request-document_type = 'A'.
        lt_request-document_numb = deltab-vbeln.
        lt_request-document_item = deltab-posnr.
        lt_request-batch        = deltab-charg.
        lt_request-material = deltab-matnr.
        lt_request-plant = '3200'.
        lt_request-quantity_base__uom = deltab-kwmeng.
        lt_request-delivery_date = sy-datum.
CALL FUNCTION 'BAPI_DELIVERYPROCESSING_EXEC'
EXPORTING
DELIVERY_EXTEND =
TECHN_CONTROL =
      TABLES
      request = lt_request
      createditems = lt_createditems
      return = lt_return.
here i am able to create delivery successfully but the batch which i passed in bapi is not getting updated in vl02n to do PGI.
again i need to go to vl02n and give batch and quanitty manually to do PGI.is there anyway that batch gets updated in vl02n also.
Regards,
Venkat.

Hi
My answer is pure assumption.
Please check the following OSS notes
Note 758810 - BAPI_PO_CHANGE vendor batch and batch not visible
Note 1230268 - Field Vendor Batch never filled for PO BAPIs
Please take help from BASIS and SAP, before implementing the OSS note
Regards
Madhan D

Net price must be greater than 0 error while creating PO using BAPI

Hi guys!
I'm using BAPI_PO_CREATE1 to create several PO's from a Z table record. I finally achieved that my BAPI to work as wished, with conditions, etc.
The problem im having is that i get the error of net price must be > 0.
I do not have any condition type defined . Is it necessary to define one?
Plz any help will be very appreciated.
Thx.

It will be configuration problem,create one PO manually and see the results
and create same data for Po using Function module and see the results
most of the time net price should be more than 0,keep net price should be more than zero
see the simple program ,what i created :
*& Report ZBAPI
REPORT ZBAPI.
DATA: BEGIN OF i_data OCCURS 0,
        text(255),
      END OF i_data.
DATA: i_ekko TYPE bapiekkoc.
DATA: it_ekko LIKE TABLE OF i_ekko INITIAL SIZE 0 WITH HEADER LINE.
DATA: BEGIN OF i_ekpo OCCURS 0,
        po_item(5),
        pur_mat(18),
        plant(4),
        net_price(23),
        disp_quan(13),
     END OF i_ekpo.
DATA: it_ekpo LIKE TABLE OF bapiekpoc INITIAL SIZE 0 WITH HEADER LINE .
DATA: BEGIN OF i_eket OCCURS 0,
         po_item(5),
         deliv_date(8),
         quantity(13),
      END OF i_eket.
DATA: it_eket LIKE TABLE OF bapieket INITIAL SIZE 0 WITH HEADER LINE.
DATA: v_index TYPE i.
DATA: return TYPE TABLE OF bapireturn INITIAL SIZE 0 WITH HEADER LINE.
DATA: po_num(10).
START-OF-SELECTION.
CALL FUNCTION 'UPLOAD'
EXPORTING
CODEPAGE                      = ' '
FILENAME                      = ' '
FILETYPE                      = ' '
ITEM                          = ' '
FILEMASK_MASK                 = ' '
FILEMASK_TEXT                 = ' '
FILETYPE_NO_CHANGE            = ' '
FILEMASK_ALL                  = ' '
FILETYPE_NO_SHOW              = ' '
LINE_EXIT                     = ' '
USER_FORM                     = ' '
USER_PROG                     = ' '
SILENT                        = 'S'
IMPORTING
FILESIZE                      =
CANCEL                        =
ACT_FILENAME                  =
ACT_FILETYPE                  =
TABLES
    data_tab                      = i_data
EXCEPTIONS
CONVERSION_ERROR              = 1
INVALID_TABLE_WIDTH           = 2
INVALID_TYPE                  = 3
NO_BATCH                      = 4
UNKNOWN_ERROR                 = 5
GUI_REFUSE_FILETRANSFER       = 6
OTHERS                        = 7
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
loop at i_data.
if i_data-text(1) = 'H'.
   shift i_data-text.
   v_index = v_index + 1.
   split i_data-text at ',' into i_ekko-doc_type
                                i_ekko-purch_org
                                i_ekko-pur_group
                                i_ekko-vendor.
append i_ekko to it_ekko.
elseif i_data-text(1) = 'I'.
shift i_data-text.
split i_data-text at ',' into i_ekpo-po_item
                               i_ekpo-pur_mat
                               i_ekpo-plant
                               i_ekpo-net_price
                               i_ekpo-disp_quan.
append i_ekpo.
move-corresponding i_ekpo to it_ekpo.
append it_ekpo.
clear it_ekpo.
else.
shift i_data-text.
split i_data-text at ',' into i_eket-po_item
                               i_eket-deliv_date
                               i_eket-quantity.
append it_eket .
move-corresponding i_eket to it_eket.
append it_eket.
clear it_eket.
endif.
endloop.
CALL FUNCTION 'BAPI_PO_CREATE'
EXPORTING
    po_header                        = i_ekko
PO_HEADER_ADD_DATA               =
HEADER_ADD_DATA_RELEVANT         =
PO_ADDRESS                       =
SKIP_ITEMS_WITH_ERROR            = 'X'
ITEM_ADD_DATA_RELEVANT           =
HEADER_TECH_FIELDS               =
IMPORTING
PURCHASEORDER                    =
tables
    po_items                         = it_ekpo
PO_ITEM_ADD_DATA                 =
    po_item_schedules                = it_eket
PO_ITEM_ACCOUNT_ASSIGNMENT       =
PO_ITEM_TEXT                     =
   RETURN                           = return
PO_LIMITS                        =
PO_CONTRACT_LIMITS               =
PO_SERVICES                      =
PO_SRV_ACCASS_VALUES             =
PO_SERVICES_TEXT                 =
PO_BUSINESS_PARTNER              =
EXTENSIONIN                      =
POADDRDELIVERY                   =
write: po_num.
use BAPi_TRANSACTION_COMITT FM always
loop at return.
write:/ return-message,return-type.
endloop.
Thanks
Seshu
Message was edited by:
        Seshu Maramreddy
Message was edited by:
        Seshu Maramreddy

Error while creating Salesorder using BAPI

hello frnds,
I m new to abap and tryin to make use of BAPI_SALESORDER_CREATEFROMDAT1 to create Sales Order
I have used the progrtam below.
*& Report ZSALESBAPITRIAL
REPORT zsalesbapitrial.
TABLES : vbak , vbap.
Parameter Screen.
Sales Document Type.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
Sales document type.
PARAMETERS: p_auart TYPE vbak-auart OBLIGATORY.
Sales Organisation.
PARAMETERS: p_vkorg TYPE vbak-vkorg OBLIGATORY.
Distribution channel.
PARAMETERS: p_vtweg TYPE vbak-vtweg OBLIGATORY.
Division.
PARAMETERS: p_spart TYPE vbak-spart OBLIGATORY.
SKIP 1.
Sold to.
PARAMETERS: p_sold TYPE vbak-kunnr OBLIGATORY.
Ship to.
PARAMETERS: p_ship TYPE vbak-kunnr OBLIGATORY.
SKIP 1.
Material(Article No).
PARAMETERS: p_matnr TYPE vbap-matnr   OBLIGATORY.
Quantity (Cummulative quantity of sales Order)
PARAMETERS: p_menge type vbap-kwmeng obligatory.
Plant(Site )
parameters: p_plant type vbap-werks obligatory.
SELECTION-SCREEN END OF BLOCK b1.
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.
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'.
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'.
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.
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.
WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.
but its giving 'Error in creating document' I m unable to figure wat i m missing . Is it tht i m gving wrong parameters.
Please help !!!

Does tht mean i need to add the following code
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'.
APPEND item.
APPEND itemx.
For second item.
Line item number.
item-itm_number = '000020'.
itemx-itm_number = 'X'.
Material
item-material = '600020001'.
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 lines
lt_schedules_in-itm_number = '000020'.
lt_schedules_in-sched_line = '0002'.
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 line flags
lt_schedules_inx-itm_number = '000020'.
lt_schedules_inx-sched_line = '0002'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
But i guess it is overwritting my frst material..
Also i m gettin a error
For object rv_beleg, number range interval doesnot exist
Pls suggest

Error while creating SO using BAPI

Hello frnds,
I m new to abap and trying to create sales orser

Dear Rachana More,
Maintain the number range interval for object rv_beleg.
In IMG under
Sales and Distribution -> Sales -> Sales Documents -> Sales Document Header -> Define Number Ranges for Sales Documents -> enter
Or from Transaction SNRO -> enter number range object rv_beleg -> Choose Number Range pushbutton from application tool bar -> Click on change intervals pushbutton -> Maintain intervals
Regards,
Naveen.

Material availability while creating reservation

Dear All,
While creating reservation in Maintenance Order how can we check the material availability of that particular material???????? plz guide
rgrds
DM

Availability Check
There are two types of availability check:
_ Availability check for the various stock types in Inventory Management
_ Check for the available stocks in Materials Planning (MRP)
Availability check of the stock types is carried out automatically and cannot be manually set in the
system. Non-availability results in an error message.
The available stocks check in MRP is activated in the material master record and can be
configured in Customizing for MRP (refer to Net Requirements Calculation [Ext.]).
Your system administrator can define:
_ Whether an availability check is to be carried out
_ Whether non-availability is to result in a warning message or an error message
In Customizing for Inventory Management, you can configure the dynamic availability
check for goods movements. In the step Define Checking Rule, you determine for
each checking rule which stocks, receipts, and issues should be included in the
availability overview (transaction code CO09).
Remember that the system does not update the consumption statistics in the material master
record if you post goods movements using the special stock types Sales order stock and Project
stock.
Checking Availability of Stock Types
For every material movement, the system automatically performs an availability check of the
stock types if this has been defined for a material. The availability check prevents the book
inventory balance of the various physical stock types (for example, unrestricted-use stock) from
becoming negative.
If several withdrawals of material are entered in a single document (for example, for different
account assignments), the system checks the availability of the material for each item entered. It
checks whether the desired quantity can be withdrawn. The system takes into account those
items of the document that have already been entered, but not yet posted.
If there is not enough stock to cover the withdrawal, the system issues an error message.
The availability check includes the stock in question at plant, storage-location, and special-stocks
level, for the current month and, if necessary, for the previous month. Different stocks are
checked, depending on the movement type:
_ In the case of a withdrawal for consumption, unrestricted-use stock is checked.
_ In the case of a release from stock in quality inspection, quality inspection stock is
checked.
_ In the case of consumption of consignment material, consignment stock for unrestricted
use is checked.
Checking Available Stocks
In addition to checking the various types of physical stock, you can also check available stock
from a Materials Planning perspective. With this type of availability check, you can, for example,
prevent a quantity already reserved from being used for another purpose.
There are 100 pieces of a material in unrestricted-use stock. 70 pieces of these 100
have been reserved for a particular requirement date.
You want to withdraw 50 pieces for a different purpose. If the availability check is
active, depending on how the system is set, you will receive:
_ A warning message
_ An error message
_ No message

Error while creating stock using tcode: MB1C

Error while creating stock using tcode: MB1C
The Error is: Check table T004F:entry G006 does not exist

Hi ,
Please check the FSV (field status variant) for your company code in OBY6 .
then go to transaction code OB14 --> enter the FSV --> Check if field status group G006(Material account) is maintained there or not.
if not please maintain it.
Thanks & Regards
Anshu

PO with account assignment category K and use two cost center

Dear Experts
When I create a PO with account assignment category K and use two cost center in the account assigment tab of PO with the same GL or with different GL in the both line item, The FI document does not get posted.
Any input on this please.
Regards
Paul

Hi,
Check in the PO document - Item level - Delivery tab
There are two indicators
1. Good receipt
2. GR non-valuated.
If you are giving only one cost centre, only GR check box active and GR non-valuated check box is in-active. That's why System creating FI document during GR.
If you are giving two cost centres, Both GR check box and GR non-valuated check box are active. That's why System is not creating any FI documents during GR.
Regards
Ravi

Error in creating reservation using 'BAPI_RESERVATION_CREATE'

Hi All,
I am using bapi 'BAPI_RESERVATION_CREATE' for creating reservation.But bapi is returning following message.
Cost center XXXX does not exist on 12.01.2009.
What can be the reason for this error ?

hi
try to use BAPI_RESERVATION_CREATE1
hope it helps
regards
Aakash Banga

Account assignment while creating reservation using bapi

Similar Messages

Maybe you are looking for