Problem in BAPI creation

Hi,
I have created a Function Module as Z_DOC_READ as a local Object.
Now , I am trying to make it as RFC enabled. But, It not allowing to do that.
Instead it is throwing one Message as
"GENERIC TYPES ARE NOT ALLOWED IN RFC".
Please let me know, what is the wrong with this?
Any steps to be followed, while Making the FM as RFC enabled?
Please let me know.
Regards
Sandeep

You might have used generic data types for the interface parameters(like Import, Export, Tables..).
For an RFC function module, the associated type of an interface parameter should be a dictionary type.

Similar Messages

Problem regarding the creation of Table using CSS.

Hi ,
Here I have a Problem regarding the creation of Table using CSS.
In My Application i have a table with multiple rows(Rows are Dynamically added to the table).First i am setting the table with the following properties:
width:900px;
height : auto,
Overflow : visible,
Max-height: : 200px.
If I use above properties,I'm getting a table with 5 or 6 rows(height upto 200px).After that i am getting the Vertical ScrollBar.
The problem is when a table has many columns, Vertical and Horizontal Scrolls are coming at the time of setting the table. The table height is not Increasing dynamically.
How can i use "height" property in CSS? (I want the table height to be increased when the columns are more.)
Thanks & Regards
Madhavi

Hey humble user. Errr I'm trying to understand what ur trying to do. U want to create a section of a region destructively from an existing region right? If so select the option convert to new region (opt-comm-R or selecting it by right clicking). Check your audio bin to make sure. Whats the "merge" function? Are u refering to the glue tool?

Problem in Idoc creation in ME22N

Hi All,
We are facing a problem in Idoc creation in transaction ME22N.Our requirement is to trigger an output type and create a idoc everytime a change is made to a particular Purchase Order.
Presently however,for some vendors,when we change the plant at the item level,an Idoc is not created(with a message that the changes are not relevant to create an Idoc).Any other change to the Purchase Order like changes in quantity or price,results in successful Idoc creation.
We have also noticed that this happens only in the case of certain vendors.The Customer Info records and vendor data are all believed to be fine.
Are any other config settings required to be maintained for this?
Thanks in advance!
Regards,
Nejuma Iqbal

Hi Nejuma,
I don't think there is any problem with cofiguration settings.u r getting the idocs for some vendors .
if iam not wrong u r giving LS in the tcode(we20).The method which u r using is change pointers.As u r using standard idoc all the settings will be done.
Only settings u have to do is
1>generate partner profiles(WE20)
2>Distribute model view(BD64).
REGARDS,
Nagaraj

Problem in BAPI

Hi Friends,
I am having a problem in BAPI when i am executing the program i am getting a error message like this,
Error message:
144The field MARA-MEINS/BAPI_MARA-BASE_UOM(_ISO) is defined as a required field; it does not contain an entry .
any solutions to the above problem.
I am sending the code along with this mail.
coding:
REPORT ZYC_BAPI_MATERIAL_CREATE .
STRUCTURE DECLARATIONS *
TABLES: BAPIMATHEAD, "Headerdata
BAPI_MARA, "Clientdata
BAPI_MAKT, "Material description
BAPIRET2. "Return messages
data : bapi_mara1 LIKE bapi_mara. "Client Data
DATA:V_FILE TYPE STRING.
DATA:
BEGIN OF LSMW_MATERIAL_MASTER,
MATNR(018) TYPE C, "Material number
MBRSH(001) TYPE C, "Industry sector
MTART(004) TYPE C, "Material type
MAKTX(040) TYPE C, "Material description
MEINS(003) TYPE C, "Base unit of measure
END OF LSMW_MATERIAL_MASTER.
INTERNAL TABLE DECLARATIONS *
*to store the input data
DATA: BEGIN OF it_matmaster OCCURS 0.
INCLUDE STRUCTURE LSMW_MATERIAL_MASTER.
DATA: END OF it_matmaster.
*for material description
DATA:BEGIN OF IT_MATERIALDESC OCCURS 0.
INCLUDE STRUCTURE BAPI_MAKT .
DATA:END OF IT_MATERIALDESC.
*to return messages
DATA:BEGIN OF IT_RETURN OCCURS 0.
INCLUDE STRUCTURE BAPIRET2.
DATA:END OF IT_RETURN.
SELECTION SCREEN
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-002.
PARAMETERS:P_FILE LIKE RLGRAP-FILENAME OBLIGATORY.
SELECTION-SCREEN END OF BLOCK B1 .
AT SELECTION SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
PROGRAM_NAME = SYST-CPROG
DYNPRO_NUMBER = SYST-DYNNR
FIELD_NAME = 'P_FILE'
IMPORTING
FILE_NAME = P_FILE.
TO UPLOAD THE DATA *
START-OF-SELECTION.
V_FILE = P_FILE.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = V_FILE
FILETYPE = 'ASC'
HAS_FIELD_SEPARATOR = 'X'
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
DAT_MODE = ' '
IMPORTING
FILELENGTH =
HEADER =
tables
data_tab = IT_MATMASTER
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
DATA POPULATIONS *
LOOP AT IT_MATMASTER.
BAPIMATHEAD-MATERIAL = IT_MATMASTER-MATNR.
BAPIMATHEAD-IND_SECTOR = IT_MATMASTER-Mbrsh.
BAPIMATHEAD-MATL_TYPE = IT_MATMASTER-MTART.
BAPIMATHEAD-BASIC_VIEW = 'X'.
refresh it_materialdesc.
IT_MATERIALDESC-matl_desc = IT_MATMASTER-maktx.
append IT_materialdesc.
bapi_mara1-base_uom = 'TO'. "it_matmaster-meins.
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
EXPORTING
headdata = BAPIMATHEAD
CLIENTDATA = BAPI_MARA
CLIENTDATAX = BAPI_MARAx
IMPORTING
RETURN = IT_RETURN
TABLES
MATERIALDESCRIPTION = IT_MATERIALDESC.
WRITE:/ IT_RETURN-TYPE,
2 IT_RETURN-ID,
22 IT_RETURN-NUMBER,
25 IT_RETURN-MESSAGE.
ENDLOOP.
Regards,
Dinesh

Hi
Basic Unit of Measure is required field in the material master
You are not populating it in the Bapi
populate it in the CLIENTDATA
IT WILL SOLVE THE ISSUE.
CLIENTDATA-BASE_UOM = it_matmaster-meins
Reward points if useful
Regards
Anji

Problem with BAPI BAPI_REQUISITION_CREATE

Hello,
I have problems with BAPI BAPI_REQUISITION_CREATE. I need to create Purchase requisition for services. If I use BAPI BAPI_REQUISITION_CREATE, Purchasing requisition is created, but field NETWR in table EBNK is 0. If I create purchasing requisition manualy using transaction ME51N, field NETWR in table EBNK is filled with correct price.
Can you pls. help me, what do I wrong in calling BAPI_REQUISITION_CREATE?
Thanks&regards,
Jirka

Not sure if you got your answer or went to OSS for a resolution. But, as I was searching OSS for my issue, I came across the following note:
Note 1498435 - BAPI_REQUISITION_CREATE: EBKN-NETWR is not updated

Problem in billing creation

hi dear,
i have problem in billing creation,if i am making credit notes with reference to return order value of assassable value not copied.i have checked copying control for return order to billing doc its already maintained.
regards
ajit
Edited by: SAP SD AJIT on Oct 22, 2009 11:58 AM
Edited by: SAP SD AJIT on Oct 22, 2009 11:58 AM
Edited by: SAP SD AJIT on Oct 22, 2009 11:59 AM
Edited by: SAP SD AJIT on Oct 22, 2009 12:02 PM

hi,
please check the following fields in VTFA
Data VBRK/VBRP - 002 (Ord-Rel Credit Memo)
Pricing type - D (Copy pricing elements unchanged)
regards
senya

How can we find error in BAPI Creation?

Can any one help out in How to findout Errors in BAPI Creation and Usage?

HI,
you can findout error by declaring BAPI RETURN type structure .
for ex:"
DATA : return LIKE bapiret2 OCCURS 0 WITH HEADER LINE.
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_partners      = partner
        sales_conditions_in = i_conditions.
    LOOP AT return WHERE type = 'E' OR type = 'A'.
      EXIT.
    ENDLOOP.
if helpful reward points.

Step by step - Bapi creation

hi,
I want to learn BAPIs..........suggest me links to get step by step BAPI creation procedure.
thanks in advance....

Hi
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
Also refer to the following links..
www.sappoint.com/abap/bapiintro.pdf
www.sap-img.com/bapi.htm
www.sap-img.com/abap/bapi-conventions.htm
www.planetsap.com/Bapi_main_page.htm
www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
u can check the below the material also
what is BAPI?
BAPI stands for Business API(Application Program Interface).
I have answered this question before..
A BAPI is remotely enabled function module ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
You can make your function module remotely enabled in attributes of Function module but
A BAPI are standard SAP function modules provided by SAP for remote access. Also they are part of Businees Objest Repository(BOR).
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
Example Code
U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no condition exists for the given parameters, a new condition will be created.
U can find these parameters for a particular condition type in table KONV.
*& Form saveTransactionJOCR
text
--> p1 text
<-- p2 text
FORM saveTransactionJOCR .
data: salesdocument like BAPIVBELN-VBELN,
order_header_inx like bapisdh1x,
order_header_in like bapisdh1,
return type standard table of bapiret2 with header line,
conditions_in type standard table of bapicond with header line,
conditions_inx type standard table of bapicondx with header line,
logic_switch like BAPISDLS,
step_nr like conditions_in-cond_st_no,
item_nr like conditions_in-itm_number,
cond_count like conditions_in-cond_count,
cond_type like conditions_in-cond_type.
salesdocument = wa_order_information-VBELN.
LOGIC_SWITCH-COND_HANDL = 'X'.
order_header_inx-updateflag = 'U'.
conditions
clear conditions_in[].
clear conditions_inx[].
clear: step_nr,
item_nr,
cond_count,
cond_type.
step_nr = '710'.
item_nr = '000000'.
cond_count = '01'.
cond_type = 'ZCP2'.
CONDITIONS_IN-ITM_NUMBER = item_nr.
conditions_in-cond_st_no = step_nr.
CONDITIONS_IN-COND_COUNT = cond_count.
CONDITIONS_IN-COND_TYPE = cond_type.
CONDITIONS_IN-COND_VALUE = 666.
CONDITIONS_IN-CURRENCY = 'EUR'.
append conditions_in.
CONDITIONS_INX-ITM_NUMBER = item_nr.
conditions_inx-cond_st_no = step_nr.
CONDITIONS_INX-COND_COUNT = cond_count.
CONDITIONS_INX-COND_TYPE = cond_type.
CONDITIONS_INX-UPDATEFLAG = 'U'.
CONDITIONS_INX-COND_VALUE = 'X'.
CONDITIONS_INX-CURRENCY = 'X'.
append conditions_inx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = salesdocument
ORDER_HEADER_IN = order_header_in
ORDER_HEADER_INX = order_header_inx
LOGIC_SWITCH = logic_switch
TABLES
RETURN = return
CONDITIONS_IN = conditions_in
CONDITIONS_INX = conditions_inx
if return-type ne 'E'.
commit work and wait.
endif.
ENDFORM. " saveTransactionJOCR
Bdc to Bapi
The steps to be followed are :
1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
[for VA01 use BAPI_SALESORDER_CREATEFROMDAT2]
2. Create a Z program and call the BAPi (same as a Funtion module call).
2. Now, if you see this BAPi, it has
-> Importing structures.
eg: SALESDOCUMENT: this will take the Sales order header data as input.
-> Tables parameters:
eg: ORDER_ITEM_IN: this will take the line item data as input.
Note :
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data
Possible UPDATEFLAGS:
U = change
D = delete
I = add
Example
1. Delete the whole order
2. Delete order items
3. Change the order
4. Change the configuration
Notes
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
For further details... refer to the Function Module documentation for the BAPi.
Bapi to VB(Visual Basic)
Long back I had used the following flow structure to acheive the same.
Report -> SM59 RFC destination -> COM4ABAP -> VB.exe
my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and manages the flow of data between sap and vb exe.
You need to have com4abap.exe
If com4abap is installed you will find it in sapgui installatin directory , C:\Program Files\SAPpc\sapgui\RFCSDK\com4abap.
else refer OSS note 419822 for installation of com4abap
after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to com4abap session , you can use the following function modules to call the vb code.
for setting up com4abap and rfc destination please refer to the documentation for com4abap.
Invoke NEW DCOM session
call function 'BEGIN_COM_SESSION'
exporting
service_dest = service_dest "(this will be a RFC destination created in SM59)
importing
worker_dest = worker_dest
exceptions
connect_to_dcom_service_failed = 1
connect_to_dcom_worker_failed = 2
others = 3.
call function 'create_com_instance' destination worker_dest
exporting
clsid = g_c_clsid
typelib = g_c_typelib
importing
instid = g_f_oid
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
call function 'com_invoke' destination worker_dest
exporting
%instid = g_f_oid
%method = 'UpdatePDF'
sntemp = g_v_const_filent
snsysid = sy-sysid
snflag = 'N'
tables
rssaptable = g_t_pdfdetail1
%return = g_t_pdfdetail1 "t_test
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
then close the com session , using
FM delete_com_instance
FM END_COM_SESSION
<REMOVED BY MODERATOR>
Regards
Anji
Edited by: Alvaro Tejada Galindo on Feb 22, 2008 9:24 AM

Problem in BAPI 'BAPI_SALESORDER_CHANGE'.

Hi All,
I am facing a problem in BAPI 'BAPI_SALESORDER_CHANGE'. My requirement is as below.
For a particular type of Sales Order i have to update all the ship-to PO.Basically in all these PO's we have to suffix
'old'.
I am pasting the code which I used. I am actually displaying the return message in a table.
The message says 'Schedule Order is saved'.
When i go and check the SO the ship-to PO is not updated.
Also i have one more querry.
Is thsi BAPI to be run for each item or can i collect all items in t_item_in and then call the BAPI.
Please guide me on this.
Thanks in Advance,
Saket.
LOOP AT t_vbkd INTO wa_vbkd.
CONCATENATE wa_vbkd-bstkd_e '-' v_po INTO v_po_ref.
t_item_in-purch_no_c    = v_po_ref.
t_item_inx-purch_no_c   = v_po_ref.
t_item_inx-updateflag = 'X'.
APPEND t_item_in.
APPEND t_item_inx.
*LOOP AT t_vbak INTO wa_vbak.
v_vbeln = wa_vbkd-vbeln.
w_headerx-updateflag = 'U'.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
    SALESDOCUMENT               = v_vbeln
    ORDER_HEADER_INX            = w_headerx
TABLES
    RETURN                      = t_return
    ORDER_ITEM_IN               = t_item_in
    ORDER_ITEM_INX              = t_item_inx.
READ TABLE t_return WITH KEY type = 'E'.
IF sy-subrc = 0.
    t_output-rmks = t_return-message.
ELSE.
    t_output-rmks = t_return-message.
ENDIF.
READ TABLE t_vbak INTO wa_vbak
   WITH KEY vbeln = v_vbeln.
t_output-vbeln = v_vbeln.
t_output-auart = wa_vbak-auart.
t_output-vkorg = wa_vbak-vkorg.
t_output-bstkd_e_old = wa_vbkd-bstkd_e.
t_output-bstkd_e_new = t_item_in-purch_no_c.
APPEND t_output.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
   WAIT          = 'X'
IMPORTING
RETURN        =
ENDLOOP.

REPORT ZSALESORDER_CHANGE MESSAGE-ID 38.
PARAMETERS: p_vbeln TYPE vbap-vbeln OBLIGATORY, "Order Number
p_posnr TYPE vbap-posnr OBLIGATORY, "Order Item
p_etenr TYPE vbep-etenr OBLIGATORY, "Schedule Line
p_reqqty TYPE bapischdl-req_qty OBLIGATORY. " Order Qty
DATA: i_hdr TYPE bapisdh1,
i_hdrx TYPE bapisdh1x,
i_ret TYPE bapiret2 OCCURS 0 WITH HEADER LINE,
wa_ret TYPE bapiret2.
DATA: BEGIN OF i_sched OCCURS 10.
INCLUDE STRUCTURE bapischdl.
DATA: END OF i_sched.
DATA: BEGIN OF i_schedx OCCURS 10.
INCLUDE STRUCTURE bapischdlx.
DATA: END OF i_schedx.
START-OF-SELECTION.
REFRESH: i_sched, i_schedx, i_ret.
CLEAR: i_sched, i_schedx, i_ret.
i_hdrx-updateflag = 'U'.
i_sched-itm_number = p_posnr.
i_sched-sched_line = p_etenr.
i_sched-req_qty = p_reqqty.
i_schedx-updateflag = 'U'.
i_schedx-itm_number = p_posnr.
i_schedx-sched_line = p_etenr.
i_schedx-req_qty = 'X'.
APPEND i_sched.
APPEND i_schedx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
salesdocument = p_vbeln
order_header_in = i_hdr
order_header_inx = i_hdrx
TABLES
return = i_ret
schedule_lines = i_sched
schedule_linesx = i_schedx.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
LOOP AT i_ret.
WRITE / i_ret-message.
ENDLOOP.
http://abap.wikiprog.com/wiki/BAPI_SALESORDER_CHANGE
Edited by: krupa jani on Jul 30, 2009 9:22 AM

Problem with BAPI of Material Master creation

Hi,
I am creating material master(mm01) through BAPI_MATERIAL_SAVEDATA.
Program is working fine but when i m checking in MM03 to display uploaded data through BAPI, i cant able to see material which i created to through BAPI but i can see in MARA table.
i dont know wht is the problem ?
can anybody let me know abt this ?

then u are not committing the work.
flow will be like this
call ' BAPI'
if return[] is initial.
commit work.
else.
endif.
Regards
peram

In BAPI creation iam getting some problem plz help me in this issue?

Hi All
    I am new to BAPI.
    I did one program by watching the below link
    http://www.saptechies.com/step-by-step-procedure-to-create-bapi/
    By watching that tutorial iam able to develop up to the creation of BAPI.
    While the releasing of my BAPI object its showing the following error
    Released object types must be transportable.
    While the releasing the method its showing the following message
    Object type components have higher release level than oject type.
    If any one knows how to resolve this issue please help in this topic
    Thanku.
Regards,
K.S.L.Neelima.

Hi Neelima,
As the error message shows: Released object types must be transportable
This means you have saved the object type also as local object under $tmp. You should not do this. Create the object type under any dev package and then try releasing it. This will work for sure.

Problem regarding the creation of sales order using bapi.

Hai all,
I am creating sales order using bapi but i am, get following error messages :
TYPE ID NUMBER MESSAGE
E VP 112 Please enter sold-to party or ship-to party
E V4 219 Sales document was not changed
I have entered all the parameters.
my program is as follows :
*& Report ZSD_SALES_ORDER
REPORT ZSD_SALES_ORDER.
 Tables
*table definitions
TABLES:vbak, "Sales Document: Header Data
 knvv, "Customer Master Sales Data
 mara, "General Material Data
 t001l, "Plants/Branches
 mvke, "Sales Data for Material
 vbap, "Sales Document: Item Data
 konv. "Conditions (Transaction Data)
 Types
*type for upload data
TYPES :BEGIN OF ty_upload,
 matnr(20) TYPE c, " Old material number
 quantity(20) TYPE c, " Cumulative order quantity in sales units
VALUE TYPE BAPIKWERT1,
 value(20) TYPE c, " Condition value
 value TYPE konv-kwert, " Condition value
END OF ty_upload.
*type for final output table
TYPES :BEGIN OF ty_main,
 bismt TYPE mara-bismt, "Old material number
 matnr TYPE vbap-matnr, "Material Number
 kunnr TYPE vbak-kunnr, "customer number
 auart TYPE vbak-auart, "Sales Document Type
 vkorg TYPE vbak-vkorg, "Sales Organization
 vtweg TYPE vbak-vtweg, "Distribution Channel
 spart TYPE vbak-spart, "Division
 vbeln TYPE vbak-vbeln, "Sales document
 werks TYPE marc-werks, " Plant
 lgort TYPE mard-lgort, "Storage Location
 posnr TYPE vbap-posnr, "Sales Document Item
 parvw TYPE vbpa-parvw, "Partner function
 kwmeng TYPE vbap-kwmeng, "Cumulative order quantity in sales units
 kschl TYPE konv-kschl, "Condition type
 kwert TYPE konv-kwert, "Condition value
KWERT TYPE BAPIKWERT1,
 kwert(20) TYPE c, "Condition value
 waers TYPE konv-waers, "Currency
 END OF ty_main.
*type for old material number
TYPES: BEGIN OF ty_matnr,
 matnr TYPE mara-matnr,
 bismt TYPE mara-bismt,
 END OF ty_matnr.
*type for order number
TYPES :BEGIN OF ty_output,
 vbeln TYPE vbak-vbeln, "Sales Document
 END OF ty_output.
 Constants Begin with C_ *
CONSTANTS:
c_zpmu(4) TYPE c VALUE 'ZPMU',
c_zpmm(4) TYPE c VALUE 'ZPMM'.
DATA: c_ch(1) TYPE c VALUE 'X'.
 Data Begin with W_ *
*global data for validations
DATA: w_count TYPE i,
 w_vkorg TYPE vbak-vkorg,
 w_vtweg TYPE vbak-vtweg,
 w_spart TYPE vbak-spart,
 w_werks TYPE t001l-werks,
 w_check TYPE c,
 w_itemno TYPE posnr_va,
 W_COND TYPE C.
 w_cond(3) TYPE c.
 Internal tables Begin with IT_ *
*internal table definitions
DATA : it_upload TYPE STANDARD TABLE OF ty_upload ,
 wa_upload TYPE ty_upload.
DATA : it_main TYPE STANDARD TABLE OF ty_main,
 wa_main TYPE ty_main.
DATA: it_matnr TYPE STANDARD TABLE OF ty_matnr,
 wa_matnr TYPE ty_matnr.
DATA : it_output TYPE STANDARD TABLE OF ty_output.
Internal table for BAPI.
DATA: it_bapisdhd1 TYPE STANDARD TABLE OF bapisdhd1, "Sales and Distribution Document Header
 wa_bapisdhd1 TYPE bapisdhd1.
DATA: it_bapisditm TYPE STANDARD TABLE OF bapisditm , "Sales and Distribution Document Item
 wa_bapisditm TYPE bapisditm.
DATA: it_bapiparnr TYPE STANDARD TABLE OF bapiparnr, "SD Document Partner: WWW
 wa_bapiparnr TYPE bapiparnr.
DATA: it_bapischdl TYPE STANDARD TABLE OF bapischdl, "Schedule Lines
 wa_bapischdl TYPE bapischdl.
DATA: it_bapicond TYPE STANDARD TABLE OF bapicond, "Communication Fields for Maintaining Conditions in the Order
 wa_bapicond TYPE bapicond.
DATA: it_bapiret2 TYPE STANDARD TABLE OF bapiret2, "Return Parameter
 wa_bapiret2 TYPE bapiret2.
 Parameters Begin with PR_ *
*selection screen definition
SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME .
PARAMETERS: pr_vkorg TYPE vbak-vkorg OBLIGATORY,
 pr_vtweg TYPE vbak-vtweg OBLIGATORY,
 pr_spart TYPE vbak-spart OBLIGATORY,
 pr_kunnr TYPE kna1-kunnr OBLIGATORY,
 pr_werks TYPE marc-werks OBLIGATORY,
 pr_lgort TYPE mard-lgort OBLIGATORY.
PARAMETERS: pr_auart TYPE vbak-auart OBLIGATORY,
 PR_AUGRU TYPE VBAK-AUGRU OBLIGATORY.
 pr_augru TYPE vbak-augru.
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN BEGIN OF BLOCK blk2 WITH FRAME.
PARAMETERS : pr_file TYPE ibipparms-path OBLIGATORY.
SELECTION-SCREEN END OF BLOCK blk2.
 At selection-screen *
AT SELECTION-SCREEN.
PERFORM f006_validate_vkorg.
PERFORM f007_validate_vtweg.
PERFORM f008_validate_spart.
PERFORM f009_validate_kunnr.
PERFORM f010_validate_werks.
PERFORM f011_validate_lgort.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR pr_file.
*for f4 help----
PERFORM f003_f4_help.
 S T A R T O F S E L E C T I O N *
START-OF-SELECTION.
*for material ,quantity and value upload
PERFORM f001_upload_file.
*get data
PERFORM f003_get_data.
*for check the data
PERFORM f002_check_data .
PERFORM f004_process.
*for posting
PERFORM f005_posting.
END-OF-SELECTION.
 E N D O F S E L E C T I O N *
*& Form f001_upload_file
 upload file
FORM f001_upload_file .
DATA : lw_fname TYPE string.
CLEAR lw_fname.
lw_fname = pr_file.
REFRESH it_upload.
CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 filename = lw_fname
 filetype = 'ASC'
 has_field_separator = c_ch
 TABLES
 data_tab = it_upload
 EXCEPTIONS
 file_open_error = 1
 file_read_error = 2
 no_batch = 3
 gui_refuse_filetransfer = 4
 invalid_type = 5
 no_authority = 6
 unknown_error = 7
 bad_data_format = 8
 header_not_allowed = 9
 separator_not_allowed = 10
 header_too_long = 11
 unknown_dp_error = 12
 access_denied = 13
 dp_out_of_memory = 14
 disk_full = 15
 dp_timeout = 16
 OTHERS = 17.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT it_upload INTO wa_upload.
 wa_upload-value = ( wa_upload-value ) / 10.
 MODIFY it_upload FROM wa_upload.
ENDLOOP.
ENDFORM. "F001_UPLOAD_FILE
*& Form f003_f4_help
 f4 help
FORM f003_f4_help .
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 program_name = syst-cprog
 dynpro_number = syst-dynnr
 field_name = ' '
 IMPORTING
 file_name = pr_file.
ENDFORM. " f003_f4_help
*& Form check_data
 text
FORM f002_check_data .
DATA: lw_lines TYPE i.
DESCRIBE TABLE it_main LINES lw_lines.
IF lw_lines LE 0.
 RETURN.
ENDIF.
SELECT a~matnr
 a~bismt FROM mara AS a INNER JOIN mvke AS b
 ON amatnr = bmatnr
 INTO CORRESPONDING FIELDS OF TABLE it_matnr
 FOR ALL ENTRIES IN it_main
 WHERE a~bismt = it_main-bismt.
IF sy-subrc = 0.
 LOOP AT it_main INTO wa_main.
 CLEAR : wa_matnr.
 READ TABLE it_matnr INTO wa_matnr WITH KEY bismt = wa_main-bismt.
 IF sy-subrc = 0.
 MOVE: wa_matnr-matnr TO wa_main-matnr.
 ENDIF.
 MODIFY it_main FROM wa_main TRANSPORTING matnr WHERE bismt = wa_main-bismt.
 ENDLOOP.
ELSE.
 MESSAGE e000(zmsd) WITH text-001.
ENDIF.
ENDFORM. "CHECK_DATA
*& Form F009_validate_vkorg
 text
FORM f006_validate_vkorg .
CLEAR w_vkorg.
SELECT SINGLE vkorg
 INTO w_vkorg FROM tvko
 WHERE vkorg EQ pr_vkorg.
IF sy-subrc <> 0.
 MESSAGE e000(zmsd) WITH text-012 pr_vkorg.
ENDIF.
ENDFORM. " F009_validate_vkorg
*& Form f007_validate_vtweg
 text
FORM f007_validate_vtweg .
CLEAR:w_vtweg.
SELECT SINGLE vtweg
 INTO w_vtweg FROM tvtw
 WHERE vtweg EQ pr_vtweg.
IF sy-subrc <> 0.
 MESSAGE e089(zmsd).
ENDIF.
ENDFORM. " f007_validate_vtweg
*& Form f008_validate_spart
 text
FORM f008_validate_spart .
CLEAR:w_spart.
SELECT SINGLE spart
 INTO w_spart FROM tspa
 WHERE spart EQ pr_spart.
IF sy-subrc <> 0.
 MESSAGE e087(zmsd).
ENDIF.
ENDFORM. " f008_validate_spart
*& Form F010_validate_kunnr
 text
FORM f009_validate_kunnr .
DATA: l_kunnr TYPE kunnr.
CLEAR: w_vkorg, w_vtweg,w_spart.
SELECT SINGLE kunnr FROM knvv
 INTO l_kunnr
 WHERE kunnr = pr_kunnr
 AND vkorg = pr_vkorg
 AND vtweg = pr_vtweg
 AND spart = pr_spart.
IF sy-subrc <> 0.
 MESSAGE e000(zmsd) WITH text-010 pr_kunnr text-011 pr_vkorg .
ENDIF.
ENDFORM. " F010_validate_kunnr
*& Form f010_validate_werks
 text
FORM f010_validate_werks .
CLEAR:w_werks.
SELECT SINGLE werks
 INTO w_werks FROM t001w
 WHERE werks EQ pr_werks.
IF sy-subrc <> 0.
 MESSAGE e088(zmsd).
ENDIF.
ENDFORM. " f010_validate_werks
*& Form F011_validate_lgort
 text
FORM f011_validate_lgort .
CLEAR:w_werks .
SELECT SINGLE werks FROM t001l
 INTO w_werks
 WHERE werks = pr_werks
 AND lgort = pr_lgort.
IF sy-subrc <> 0.
 MESSAGE e000(zmsd) WITH text-007 pr_lgort text-008 pr_werks .
ENDIF.
ENDFORM. " F011_validate_lgort
*& Form f003_get_data
 text
FORM f003_get_data .
CLEAR wa_main.
REFRESH it_main.
LOOP AT it_upload INTO wa_upload.
 CLEAR : wa_main.
 MOVE: wa_upload-matnr TO wa_main-bismt,
 wa_upload-quantity TO wa_main-kwmeng,
 wa_upload-value TO wa_main-kwert,
 pr_vkorg TO wa_main-vkorg,
 pr_vtweg TO wa_main-vtweg,
 pr_spart TO wa_main-spart,
 pr_kunnr TO wa_main-kunnr,
 pr_werks TO wa_main-werks,
 pr_lgort TO wa_main-lgort.
 APPEND wa_main TO it_main.
ENDLOOP.
ENDFORM. " f003_get_data
*& Form f004_process
 text
FORM f004_process .
CLEAR w_check.
LOOP AT it_main INTO wa_main.
 IF wa_main-matnr = ''.
 WRITE:/ text-006,
 wa_main-bismt.
 w_check = 1.
 ENDIF.
 IF wa_main-kwmeng = 0.
 WRITE:/ text-005,
 wa_main-bismt.
 w_check = 1.
 ENDIF.
 IF pr_auart <> 'ZM01'.
 IF wa_main-kwert IS INITIAL.
 WRITE:/ text-004,
 wa_main-bismt.
 w_check = 1.
 ENDIF.
 ENDIF.
ENDLOOP.
ENDFORM. " f004_process
*& Form f005_posting
 text
FORM f005_posting .
CLEAR: w_itemno,
 w_cond.
w_itemno = 10.
w_cond = 1.
IF w_check = '' OR w_check = 1.
wa_bapisdhd1-doc_type = pr_auart.
wa_bapisdhd1-ord_reason = pr_augru.
LOOP AT it_main INTO wa_main.
 IF w_cond = 1.
 CLEAR: it_bapiret2,
 it_bapisditm,
 it_bapiparnr,
 it_bapischdl,
 it_bapicond.
 REFRESH:it_bapiret2,
 it_bapisditm,
 it_bapiparnr,
 it_bapischdl,
 it_bapicond.
 MOVE: wa_main-vkorg TO wa_bapisdhd1-sales_org,
 wa_main-vtweg TO wa_bapisdhd1-distr_chan,
 wa_main-spart TO wa_bapisdhd1-division.
 wa_bapisdhd1-wbs_eleM = 'Y561.1'.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
 EXPORTING
 INPUT = pr_kunnr
 IMPORTING
 OUTPUT = pr_kunnr.
 wa_bapisdhd1-PURCH_NO_S = pr_kunnr.
 wa_bapisdhd1-PURCH_NO_C = pr_kunnr.
 ENDIF.
 MOVE: w_itemno TO wa_bapisditm-itm_number,
 wa_main-matnr TO wa_bapisditm-material,
 wa_main-BISMT TO wa_bapisditm-material,
 wa_main-werks TO wa_bapisditm-plant,
 wa_main-lgort TO wa_bapisditm-store_loc.
 wa_bapisditm-target_qty = '10'.
 wa_bapisditm-PURCH_NO_S = pr_kunnr.
 wa_bapisditm-PURCH_NO_C = pr_kunnr.
 APPEND wa_bapisditm TO it_bapisditm.
 IF w_cond = 1.
 wa_bapiparnr-partn_numb = pr_kunnr.
 wa_bapiparnr-itm_number = 10.
 wa_bapiparnr-partn_role = 'SP'.
 APPEND wa_bapiparnr TO it_bapiparnr.
 wa_bapiparnr-partn_role = 'AG'.
 APPEND wa_bapiparnr TO it_bapiparnr.
 CLEAR wa_bapiparnr-partn_role.
 wa_bapiparnr-partn_numb = pr_kunnr.
 wa_bapiparnr-partn_role = 'RE'.
 APPEND wa_bapiparnr TO it_bapiparnr.
 CLEAR wa_bapiparnr-partn_role.
 wa_bapiparnr-partn_numb = pr_kunnr.
 wa_bapiparnr-partn_role = 'RG'.
 APPEND wa_bapiparnr TO it_bapiparnr.
 CLEAR wa_bapiparnr-partn_role.
 wa_bapiparnr-partn_numb = pr_kunnr.
 wa_bapiparnr-partn_role = 'WE'.
 APPEND wa_bapiparnr TO it_bapiparnr.
 ENDIF.
 wa_bapischdl-itm_number = w_itemno.
 wa_bapischdl-req_qty = wa_main-kwmeng.
 wa_bapischdl-PURCH_NO_S = pr_kunnr.
 APPEND wa_bapischdl TO it_bapischdl.
 wa_bapicond-itm_number = w_itemno.
 wa_bapicond-cond_type = 'ZECL'.
 IF ( wa_bapisdhd1-doc_type = 'ZPMU' ) OR ( wa_bapisdhd1-doc_type = 'ZPMM' ).
 wa_bapicond-cond_type = 'ZVAL'.
 ELSE.
 wa_bapicond-cond_type = 'ZMRP'. "+PK12122006
 ENDIF.
 wa_bapicond-cond_value = wa_main-kwert.
 APPEND wa_bapicond TO it_bapicond.
 w_itemno = w_itemno + 10.
 w_cond = w_cond + 1.
ENDLOOP.
data : SALESDOCUMENTIN like BAPIVBELN-VBELN.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
 EXPORTING
 order_header_in = wa_bapisdhd1
 IMPORTING
 salesdocument = SALESDOCUMENTIN
 TABLES
 return = it_bapiret2
 order_items_in = it_bapisditm
 order_partners = it_bapiparnr
 order_schedules_in = it_bapischdl
 order_conditions_in = it_bapicond.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = c_ch.
ENDIF.
LOOP AT it_bapiret2 INTO wa_bapiret2.
 DATA : w_err(100) TYPE c,
 w_matnr TYPE matnr.
 IF wa_bapiret2-type = 'E' AND wa_bapiret2-id = 'V1' AND wa_bapiret2-number = 392.
 UNPACK wa_bapiret2-message_v1 TO w_matnr.
 READ TABLE it_matnr INTO wa_matnr WITH KEY matnr = w_matnr.
 IF sy-subrc EQ 0.
 CONCATENATE text-013 wa_matnr-bismt INTO w_err SEPARATED BY space.
 MESSAGE w_err TYPE 'S'.
 ENDIF.
 ENDIF.
 IF WA_BAPIRET2-TYPE = 'S'. " Comment
 WRITE: 40 TEXT-009, WA_BAPIRET2-MESSAGE_V2+0(10).
 ENDIF.
ENDLOOP.
ENDFORM. " f005_posting
I have given all the necessary parameters. it is telling that error is in parameter
sales_header_in.
I have checked it.
i have assigned purch_no_s and purch_no_c of the structure BAPISDHD1(ORDER_HEADER_IN)
in the bapi with customer number.
and also i have assigned the partnumber of the structure BAPIPARNR ORDER_PARTNERS
in the bapi with customer number.
but still , it is diplaying the error message, please enter the sold to or ship to party number.
how to resolve this error.
this is urgent requirement.
points will be awarded.
thanking u in advance,
a.srinivas.

Hi,
Did u have a look at the standard programs which make use of BAPI_SALESORDER_CREATEFROMDAT1
Heres a list...
LWSSOU08
MV45WF0S
MWWMJF21_BAPI_SALESORDER_CREAT
RBUS2032
Regards,
Tanveer.
Please mark helpful answers

Problem in PO creation using BAPI_PO_CREATE1

Hi Experts,
I am creating the PO by using the BAPI_PO_CREATE1.
I am giving the net price for the material in POITEM-NET_PRICE and also 'X' in POITEMX-NET_PRICE.
For some material, BAPI is working fine and for some material BAPI is giving the error like 'Net price must be greater than zero'.
When i tried to create the PO manually for material for which the BAPI is giving the error, the PO was created successfully.
I am working on R/3 Release 4.6C.
Anybody have the suggestion how to resolve this problem?
Thanks in Advance,
Abhishek Ingole

Abhishek,
It's not your BAPI. That is how your customizing settings are deffined for the PO creation.
"If you want to create a purchase order without a value, you must set the
IR indicator to " ". "
contact your functional person to check the settings and find out if you need to skip the records with 0 net price.......
Also you should get this error when you create a PO online. Please try it again with 0 net price.
Thanks,
Alchemist.

Problem with BAPI (Flight) Tutorial

Hi,
Im new in developeing with Web Dynpro for Java.
I did every steps of this tutorial (Adaptive RFC tutorial - with the BAP_Flight_Getlist) exactly:
http://help.sap.com/saphelp_webas630/helpdata/DE/b2/326b09e58bcf499f73b5cc278808f4/content.htm
But i can not deploy the application - Error: deployment aborted.
05.04.2008 11:00:23 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[022]Deployment aborted
Settings
SDM host : dmhpnb34
SDM port : 50018
URL to deploy : file:/C:/DOKUME1/ADMINI1/LOKALE~1/Temp/temp29689Flights.ear
Result
=> deployment aborted : file:/C:/DOKUME1/ADMINI1/LOKALE~1/Temp/temp29689Flights.earAborted: development component 'Flights'/'local'/'LOKAL'/'0.2008.04.05.11.00.19'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application local/Flights.. Reason: Clusterwide exception: Failed to deploy application local/Flights. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/Flights. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
My SLD is working, also my JCOS, so there should not be the problem.
Are there more good small tutorials (like this flight tutorial) with Web Dynpro and BAPI ?!

thx for the advise. I developed the tuturial application again and can now run it. But if i click on search button with the entered values Departure City: Frankfurt and Arrival City: New York
i get no values in the table (i checked in the ERP System if the flights with this directions exists - its there):
Custom Controller Code:
// This file has been generated partially by the Web Dynpro Code Generator.
// MODIFY CODE ONLY IN SECTIONS ENCLOSED BY @@begin AND @@end.
// ALL OTHER CHANGES WILL BE LOST IF THE FILE IS REGENERATED.
package mypackages;
// IMPORTANT NOTE:
// ALL IMPORT STATEMENTS MUST BE PLACED IN THE FOLLOWING SECTION ENCLOSED
// BY @@begin imports AND @@end. FURTHERMORE, THIS SECTION MUST ALWAYS CONTAIN
// AT LEAST ONE IMPORT STATEMENT (E.G. THAT FOR IPrivateFlightsController).
// OTHERWISE, USING THE ECLIPSE FUNCTION "Organize Imports" FOLLOWED BY
// A WEB DYNPRO CODE GENERATION (E.G. PROJECT BUILD) WILL RESULT IN THE LOSS
// OF IMPORT STATEMENTS.
//@@begin imports
import mypackages.model.Bapi_Flight_Getlist_Input;
import mypackages.model.Bapisfldst;
import mypackages.model.FlightModel;
import mypackages.wdp.IPrivateFlightsController;
import com.sap.mw.jco.JCO;
import com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory;
import com.sap.tc.webdynpro.progmodel.model.api.WDModelScopeType;
//@@end
//@@begin documentation
//@@end
public class FlightsController
Logging location.
private static final com.sap.tc.logging.Location logger =
 com.sap.tc.logging.Location.getLocation(FlightsController.class);
static
 //@@begin id
 String id = "$Id$";
 //@@end
 com.sap.tc.logging.Location.getLocation("ID.com.sap.tc.webdynpro").infoT(id);
Private access to the generated Web Dynpro counterpart
for this controller class. 
Use <code>wdThis</code> to gain typed access to the context,
to trigger navigation via outbound plugs, to get and enable/disable
actions, fire declared events, and access used controllers and/or
component usages.
@see mypackages.wdp.IPrivateFlightsController for more details
private final IPrivateFlightsController wdThis;
Root node of this controller's context. 
Provides typed access not only to the elements of the root node
but also to all nodes in the context (methods nodeXYZ())
and their currently selected element (methods currentXYZElement()).
It also facilitates the creation of new elements for all nodes
(methods createXYZElement()). 
@see mypackages.wdp.IPrivateFlightsController.IContextNode for more details.
private final IPrivateFlightsController.IContextNode wdContext;
A shortcut for <code>wdThis.wdGetAPI()</code>. 
Represents the generic API of the generic Web Dynpro counterpart
for this controller. 
private final com.sap.tc.webdynpro.progmodel.api.IWDController wdControllerAPI;
A shortcut for <code>wdThis.wdGetAPI().getComponent()</code>. 
Represents the generic API of the Web Dynpro component this controller
belongs to. Can be used to access the message manager, the window manager,
to add/remove event handlers and so on. 
private final com.sap.tc.webdynpro.progmodel.api.IWDComponent wdComponentAPI;
public FlightsController(IPrivateFlightsController wdThis)
 this.wdThis = wdThis;
 this.wdContext = wdThis.wdGetContext();
 this.wdControllerAPI = wdThis.wdGetAPI();
 this.wdComponentAPI = wdThis.wdGetAPI().getComponent();
//@@begin javadoc:wdDoInit()
/** Hook method called to initialize controller. */
//@@end
public void wdDoInit()
 //@@begin wdDoInit()
 Bapi_Flight_Getlist_Input input = new Bapi_Flight_Getlist_Input();
 wdContext.nodeBapi_Flight_Getlist_Input().bind(input);
 Bapisfldst bapisfldstFrom = new Bapisfldst();
 input.setDestination_From(bapisfldstFrom);
 Bapisfldst bapisfldstTo = new Bapisfldst();
 input.setDestination_To(bapisfldstTo);
 // Creates an instance of a client to the remote SAP system
 client = JCO.createClient("800", //SAP logon client number
 "Andreas", //SAP logon user
 "*****", //SAP logon password
 "DE", //SAP logon language
 "dmsaperp", //Host name of application server
 "00"); //SAP system number
 // Creates the model instance
 model = (FlightModel)WDModelFactory.getModelInstance( FlightModel.class, WDModelScopeType.APPLICATION_SCOPE);
 // Assigns the client to the model
 model.setJcoClient(client);
 //@@end
//@@begin javadoc:wdDoExit()
/** Hook method called to clean up controller. */
//@@end
public void wdDoExit()
 //@@begin wdDoExit()
 //@@end
//@@begin javadoc:getFlights()
/** Declared method. */
//@@end
public void getFlights( )
 //@@begin getFlights()
 //@@end
The following code section can be used for any Java code that is
not to be visible to other controllers/views or that contains constructs
currently not supported directly by Web Dynpro (such as inner classes or
member variables etc.). 
Note: The content of this section is in no way managed/controlled
by the Web Dynpro Designtime or the Web Dynpro Runtime.
//@@begin others
JCO.Client client;
 FlightModel model;
//@@end
content of obsolete user coding area(s) -
//@@begin obsolete:getFlights()^
// client.connect();
// try {
// // Calls remote Function Module BAPI_FLIGHT_GETLIST
// wdContext.currentBapi_Flight_Getlist_InputElement().modelObject().execute();
// catch (Exception ex) {
// ex.printStackTrace();
// finally {
// client.disconnect();
// // Invalidates the output context node
// wdContext.nodeOutput().invalidate();
//@@end

BAPI_ROUTING_CREATE problem in component creation for phantom materials

Hi,
I am using the BAPI "BAPI_ROUTING_CREATE" to create a Routing. It works fine creating the operations, Component allocations, InspectionChar creation and updating the Header data Information.
The Problem i am facing is with the allocation of components with Phantom assembly. Can any one help me in passing the Parameters to the BAPI to allocate the components with the Phantom assembly.
i am getting error message
"cpccdt-206 The component to be assigned has not been completely specified "
Thanks
Pravin

I i'm having exactly the same problem.
"cpccdt-206 The component to be assigned has not been completely specified "
In my case this message occurs with normal material and not Phantom materials.
Do you have any solution already?
Thanks,
Joao
Message was edited by:
João Costa TMG

Problem in BAPI creation

Similar Messages

Maybe you are looking for