RFC+BAPI+TABLE HELP

Hi all.
Im install SAP NetWeaver Sneak preview ABAP edition.
Me application writen i VB 6 connect ok.
BAPI,TABLE- object connect ok.
If retrieving data command BAPI getdetail+show app closed=crash,TABLE search ok,if TABLE show data or TABLE detail data,main app writen error - No search table-table not found ......
Please help

Armin,
First of all than you for your reaction. I couldn't answer earlier because I was too busy to catch up with project deadlines.
I checked the mapping between the custom controller and the view controller is done. It should be OK since I can display the bapi returned table in a Table widget.
But I still don't know how to access this returned table from the wdDoInit() method of the view controller.
My context is as following:
Bapi_Currency_Getlist_Input
-- Curreny_List
-- Currency
I can get a reference to currentBapi_Currency_Getlist_Input, next I can get a reference to currentCurrency_ListElement. But as from this point, I can't get a List or any other container with the currency values. (The bapi I call is bapi_currency_getlist and I try to create a value help with curency values)

Similar Messages

Passing values to RFC/BAPI Table

Hi,
I am having a very strange problem. While passing the values to RFC/BAPI table using add method the values are not passed to backend SAP. Below is the code which I am using just to pass some data in RFC/BAPI table.
The same code was working few days back. Is there any configuration in JCO or any other problems other than the code?
Your l help is greatly appreciated.
public void executeZtest_Function_Input( )
// //@@begin executeZtest_Function_Input()
// //$$begin Service Controller(943377124)
 IWDMessageManager manager = wdComponentAPI.getMessageManager();
 try{
Ztest_Function_Input input = new Ztest_Function_Input();
 for (int i=0; i<5;i++){
 Zhr_Ear_Cclist cc =new Zhr_Ear_Cclist();
 cc.setFi_User("[email protected]");
 input.addIcc_List(cc);
 wdContext.nodeZtest_Function_Input().bind(input);
 wdContext.currentZtest_Function_InputElement().modelObject().execute();
 wdContext.nodeOutput().invalidate();
 } catch(WDDynamicRFCExecuteException ce) {
 manager.reportException(ce.getMessage(), false);
 //$$end
 //@@end

Hi Raksh,
 I also got the same problem. Please check the following ways then you will solve problem.
1. First check the appropriate BAPI in SAP GUI Software. You have to determine where is the problem?. Is it in Dynpro or BAPI itself?.
2. Suppose the BAPI structure change you will wont't run. If BAPI strusture change you have to reimport BAPI.
3. Please check the JCo connectio using test Button. Then redeploy your project.
4. Rebuild your project then redeploy.
Check the above ways you may get answer.
Kind Regards,
S.Saravanan

ALE/IDOC and RFC/BAPI Integration Scenarios with SAP DS for ESA v3

Hi,
we are planning two PoCs of Integration Plattforms. One of our major requirement set is SAP Integration into our existing SOA.
Because we also have R/3 4.7 Systems in production, we are planning to test ALE/IDOC and RFC/BAPI Integration scenarios with these Integration Plattforms.
My question is:
We are looking for are smart solution to get a SAP Test Environment, where we can test ALE/IDOC und RFC/BAPI Integration scenarios.
It is possible to do this with SAP DS for ESA v3 or shall we better use IDES for that purpose?
Best regards,
Steven

Hi Abhishek,
This is our scenario. We are doing an integration of SAP HR r/3 system with the CRM system. We need housing information details of the employees which we have in custom infotype 9310 in SAP HR system and we need those details in the CRM system. So am planning out for an ALE/IDOC approach for the integration and gonna maintain the 9310 details in a custom table. In the CRM system, we gonna build a BOL layer for accessing the 9310 details. Also i'm preparing a HLD for this process. I wanna read and go through few same HLD's before i submit my proposal to my client. Please suggest me and help me out.
Thanks in advance.
Regards,
Arunmozhi.

How to use field symbols while creating a new RFC Bapi

Hi all,
I have written a RFC Bapi in the traditional way.
I need to replace all with field symbols (import. export. tables and source code).
What is the syntax ?
Any sample codng will be more helpful.
Regards
Senthil

Please search for available information on "field symbols" before posting
Thread locked
Thomas

How to passing lowercase values to RFC/BAPI using webdynpro for JAVA

Hi Exerts,
When we sending values to RFC/BAPI through webdynpro (JAVA), the values are sent in capital (uppercase) letters to ECC.
So if we fill xxxx, it is send like XXXX. Why? and how to avoid this?
Thanks in advance,
Joeri

Hi,
There could be two possibility if you are storing this value in ABAP table.
1. You are entering value in UPPERCASE in your webdynpro application.
2. The data stored in ABAP table, converts value in small to upper case.
1. Can you tell me how you are passing this value, is user entering value in some input field which is binded to some context and this value are you passing to RFC/BAPI...???
Or else before passing value to RFC/BAPI you can use toLowerCase string function and the npass this value to RFC/BAPI
e.g String name = wdContext().currentContextelement().getName().toLowercase();
Now pass this name to RFC/BAPI is should go as lowercase only..
This is from webdynpro java side..
2. If you are storing this value in ABAP table, check the domain/type of variable in ABAP table for which you are storing the value. Ask ABAPper, so that this value are stored in small case letter.
There is one tick in domain which you need to remove so that it stores in lower case. I dont have exact information but you can consult this with ABAPer.
Hope this information helps guy ..!!!!
Regards,
Jigar

QM - RFC/BAPI required

Dear team,
Is there any built in RFC/BAPI in R/3 to update UDCODE and Inspection lot fields in QALS and QAVE tables(QM related).
PRUEFLOS from QALS and dataelement:: QPLOS
VBEWERTUNG from QAVE and data element : QBEWERTUNG
Thanks.
-Drumi

Hey Did you check this one.
As per your requirement hope this can be used. BAPI_INSPLOT_SETUSAGEDECISION
You can also check the following Bussiness Objects
BUS2045
BUS204501
BUS204502
BUS204503
Hope this helps,
Bhargav.

RFCs, BAPI, USEREXIT

Hallo Friends,
Can someone provide me with example code(s) that use the following?
User exit
RFCs
BAPI
Please make explainatory comments to key command lines !
I would appreciate if the following information could be provided too:
Aim of project
Project description
Description of what the above (User exit, Rfcs, Bapi) does in the code.
Purpose of use
etc etc
Why do I need these Infos?
I need it to prepare myself for a coming interview.
Please reply to my e-mail:
[email protected]
Thanks for the reply and good points will be awarded.
Blacky.

Hi
what is BAPI?
BAPI stands for Business API(Application Program Interface).
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.
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
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
RFC
RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
and you will be passing an Import parameter DESTINATION to it.
Other code and usage will be similar to any fun module;
Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
Refer this link:
http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm
User exits
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
The naming standard of function modules for functionmodule exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
To find a Exit.
Goto Transaction -- Find The Package
SMOD >f4>Use the Package here to Find the Exits In the Package.
Else if you Want to search by Application Area wise ,
There is one more tab to find the Exits in the Respective Application Area.
Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
Now Run ur Transaction to Check if it Triggers.
Thats it..
Suppose you need to find out all the user exits related to a tcode.
1. Execute the Tcode.
2. Open the SAP program.
3. Get the Development Class.
4. Execute Tcode SE84.
5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
6. Enter the Development class and execute.
Check out this thread..
The specified item was not found.
1. Type the transaction : system->status-> <PROG. NAME>
2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
3. Open CMOD utilities->SAP enhancements
EDIT->All selections
4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
5. The displayed list contains the enhancements names for the transaction You were looking for.
6. Create a project in CMOD and the code in default include->activate.
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these links
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.planetsap.com/userexit_main_page.htm
User-Exits
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/ab038.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.sap-basis-abap.com/sapab013.htm
http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
These links will help you to learn more on user exits.
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.allsaplinks.com/user_exit.html
www.sap-img.com/abap/what-is-user-exits.htm
Also please check these threads for more details about user exits.
Re: Screen exit
user exit and customer exit
user exit
1. Document on UserExits in FI/CO
http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
2. Finding User Exits...
http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
3. List of all User Exits...
http://www.planetsap.com/userexit_main_page.htm
Reward points if useful
Regards
Anji

BAPI please help!

Hi experts!
Im new to BAPI, can someone help me to make a code? Right now, im using
BAPI_SALESDOCU_CREATEDAT2 and i dont know were to start..Please provide sample
code for this BAPI. One thing, this is with reference to quotation (VA23). Thank you very much! Reward points will be given to deserved reply.
Regards,
Mackoy

BAPIs:
- are designed as the methods of business objects in the business object repository (accessable using transaction BAPI or SWO1)
- have non-technical parameter names (the technical field names in SAP are mapped)
- have a fixed interface and functionality across all SAP releases (this is probably the key point as it means you can develop integrations with them which do not need to be changed when you upgrade)
Generally, if you are trying to find a function for a particular requirement you should look for a BAPI first, then for a RFC function which has a released status (check the function attributes in SE37), and then just a normal RFC last.
The benefit of an RFC function with released status means that it also has a fixed interface which will not change with new SAP releases
RFC-
http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
BAPI-
Business application Prograaming Interface is nothing but the Method of a Business object.
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 these threads
What is the difference between RFC and BAPI?.
whats difference between rfc and bapi?
difference between rfc & bapi
difference between RFC and BAPi
Difference between BAPI and RFC?
Regards
Sudheer
Priyanka Neelam
Posts: 1,266
Questions: 0
Registered: 11/13/06
Forum points: 1,854
Re: difference bet rfc and bapi
Posted: Jul 26, 2007 7:13 AM in response to: m.kanny d Reply
Hi,
RFC is a fun module similar to other fun modulkes with special Parameter as DESTINATIOn and in the attributes you have to make it as RFC ebnables
where as BAPI is the API of the BUSINESS OBJECT which you see in SWo1 Tcode
RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
and you will be passing an Import parameter DESTINATION to it.
Other code and usage will be similar to any fun module;
Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
Refer this link:
http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm
check out the following link it might help you
http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf
BAPI stands for Business API(Application Program Interface).
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.
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
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

Issue with Create BAPI - Please help

I need to do a Create BAPI the structure is as follows:
-Orders
 -Operations_create (Afvgd - BAPI table structure)
On a click of a InsertOperation button, I should be able to insert the line Items to the Operations_create node and then set them finally to the Model node. Then do the order create(Insert BAPI as a whole).
The problem is there is an already existing element (framework created). So if I do the following code in onActionInsertOperation. I am getting an extra duplicate record.
Is there a easy fix to this . I am not sure Supplyfunction will help here. If so, How?
Or Can I tweak the code here?
Thank you ... Any help is appreciated
View Controller:
onActionInsertOperation(){
 IOperations_CreateElement oprEle = wdContext.createOperations_CreateElement();
 oprEle .setGLAccount(wdContext.currentOperations_CreateElement().getGLAccount());
 oprEle .setVendorNo(wdContext.currentOperations_CreateElement().getVendorNo());
 wdContext.nodeOperations_Create().addElement(oprEle);
onActionCreateOrder(){
 wdThis.wdGetVmrsCustController().callBapi_CreateOrder();
 wdThis.wdGetVmrsCustController().callBapi_Commit();
Custom Controller:
callBapi_CreateOrder(){
 for(int i=0;i<wdContext.nodeOperations_Create().size();i++) {
 Afvgd item = new Afvgd();
 item.setGLAccount(wdThis.wdGetContext().nodeOperations_Create().getOperations_CreateElementAt(i).getGLAccount());
 item.setVendor(wdThis.wdGetContext().nodeOperations_Create().getOperations_CreateElementAt(i).getVendorNo());
 inputCreateOrder.addOperations(item) ;
 // Executing the Model
 // Invalidating ...

Hello Vivek,
If the node Operations_create is a Value Node then you may bind the oprEle element to
the nodeOperations_Create() instead of adding it to the Node.
onActionInsertOperation()
 IOperations_CreateElement oprEle =
 wdContext.createOperations_CreateElement();
 oprEle .setGLAccount
 (wdContext.currentOperations_CreateElement().getGLAccount());
 oprEle .setVendorNo
 (wdContext.currentOperations_CreateElement().getVendorNo());
 wdContext.nodeOperations_Create().bind(oprEle);
Also, you may change the cardinality of the Operations_Create node to 0:1 or 0:N (from 1:N).
By doing this, you can prevent automatic generation and addition of an element by the WDF.
Bala

Scenario File to RFC (BAPI): BAPI not executed successful

Hi Dear Friends!
At execution of asynchronous Scenario File to RFC (BAPI BAPI_ACC_DOCUMENT_POST)
I have the following error in RWB Communication Channel (RFC receiver):
- Error: 2007-07-25 11:08:25 EEST: Message processed for interface BAPI_ACC_DOCUMENT_POST:
com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message
to remote system:com.sap.aii.af.rfc.core.client.RfcClientBapiException:
BAPI not executed successful
Simultaniously Test Configuration was executed successfully. And mapping is good.
But I don't any message in target system in sxmb_moni (formed by BAPI).
In XI system I see in sxmb_moni:
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface mi_sender*</Trace>
<Trace level="1" type="T">select interface namespace urn:file:to:bapi</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
Please help me understand my error.
With the best regards,
Natalia Maslova

Hi, Dear Friends! Thanks for support!
My settings of
Connection between systems:
DX7 01 (client 001) - XI Integration Server and DE2 13 (client 200) - target system.
Phisically both systems are in one server: 10.20.30.24 (srv24)
Business system DE2_200 has Communication Channel: cc_bapi_r, its settings (in Integration Builder Configuration):
Adapter Type: RFC
Receiver
Transport Protocol: RFC
Message Protocol: RFC (RFC XML)
Adapter Engine: Integration Server
RFC Client Parameter:
RFC Server Type: SAP System
Application Server: 10.20.30.24
System Number: 13
Authentication Mode: Use Logon Data for SAP System
Logon User: n_maslova
Logon Password: *******=*******
Logon Language: EN
Logon Client: 200
Maximum Connections: 1
x Advanced Mode
x Send 'Confirm Transaction'
x Commit Handling for Single BAPI Calls
x BAPI Advances Mode
Successful RETURN-TYPE Values: 0
As I understand these settings are the settings of RFC-destination for target system DE2 13 (200) from XI (DX7 01 001).
In SLD, Business system DE2_200 is defined as:
Integration:
Role: Application System
Related Integration Server: DX7_001
Technical System: DE2 on srv24
Client: 200 of DE2
Logical System Name: DE1CLNT200
In target system DE2 13 (200) with the help of transaction sm59 I created
RFC-destination DX7_001 of type H:
Technical setting parameters:
Target Host: 10.20.30.24
Prefix Path: /sap/xi/engine/?type=entry
Service Number: 8001
Registration and Safe:
SSL: Non active.
SSL: client certificate: DFAULT SSL-client
Enter to system:
Language: EN
Client: 001
User: PIAPPLUSER
Status PW: saved
Password: ********
After that in this system DE2 13 (200) with the help of transaction sxmb_adm I set in Integration Engine -> Configuration -> Configurate Integration Engine
(Change Global Configuration Data):
Role of Business System: Application System
Related Integr. Server: dest://DX7_001
Best regards,
Natalia

Diff... between ALE, IDOC, RFC, BAPI, BADI --- Not clear and clarify

Hi All
    I am learning XI and the difference between " ALE, IDOC, RFC, BAPI, BADI "
    Not clear and when to use what and how in point of XI ?
   Pl..clarify me
Adv..thanks and points
--- Rakesh Behera

Hi
This will expalin you every thing ...pl..go through
The interface concept of the classic R/3 is based on two different strategies: Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
I hope this will help you to understand the difference bet..those
regards
--- prasad

Documentation on Function Modules,RFC,BAPI

hi friends,
I have to give training in these 3 topics(function module,RFC,BAPI) .can u please help me with the documentation part .
thanku

hi,
give your mail id, such i can forward documents to that.
regards,
Pavan

Is there a common RFC/BAPI so that using it I can create multi report in EP

Hi,
I am new to EP ..
I have to generate some 25 reports of R3 systems which shoudl be exposed to EP. After going thru the docs on EP..
It says that for every reports I need to create either an RFC or a BAPI. But It is a tedious job to create RFC functions for every report. Since these report is already there(Written) in the R3 System. I hate to convert these again as an RFC for every report.
Is there a common RFC /BAPI where I need to pass required parameters and the transaction code for a specific report instead of creating a new RFC for every reports. so that that specific RFC will do the job for me.
Is there a better/intelligent way to accomplish this task.
Please do not say use SAP trasnational iViews ... As this expose the SAP GUI directly to the user..thru this one can trigger new transactions ... Correct me if I am wrong.
thanks
Pkiran

thanks mario,
very helpful answer
pkiran

About bapi with help of example

about bapi with help of example plz dont give links.

With the correct customizing (order types, etc...) the following BAPI will create a PM order for you.
Naturally the master data is also required to be created in SAP (Technical objects, Work places, etc...)
*& Report Z_BAPI_ALM_ORDER_MAINTAIN_TEST *
REPORT z_bapi_alm_order_maintain_test.
TABLES: mara,
 resb. "anyagfoglalások táblája
DATA: it_methods LIKE STANDARD TABLE OF bapi_alm_order_method,
 wa_methods LIKE LINE OF it_methods.
DATA: it_header LIKE STANDARD TABLE OF bapi_alm_order_headers_i,
 wa_header LIKE LINE OF it_header.
DATA: it_operation LIKE STANDARD TABLE OF bapi_alm_order_operation,
 wa_operation LIKE LINE OF it_operation.
DATA: it_component LIKE STANDARD TABLE OF bapi_alm_order_component,
 wa_component LIKE LINE OF it_component.
DATA: it_component_up LIKE
 STANDARD TABLE OF bapi_alm_order_component_up,
 wa_component_up LIKE LINE OF it_component_up.
DATA: et_numbers LIKE STANDARD TABLE OF bapi_alm_numbers,
 wa_numbers LIKE LINE OF et_numbers.
DATA: et_extension_in LIKE STANDARD TABLE OF bapiparex,
 wa_extension_in LIKE LINE OF et_extension_in.
DATA: et_return LIKE STANDARD TABLE OF bapiret2,
 wa_return LIKE LINE OF et_return.
DATA: it_resb LIKE STANDARD TABLE OF resb,
 wa_resb LIKE LINE OF it_resb.
DATA: lv_commit TYPE i.
PARAMETERS: p_test AS CHECKBOX DEFAULT 'X'.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS: p_create RADIOBUTTON GROUP rg1 DEFAULT 'X'.
SELECTION-SCREEN COMMENT 4(30) text-rcr.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS: p_change RADIOBUTTON GROUP rg1.
SELECTION-SCREEN COMMENT 4(30) text-rch.
PARAMETERS: p_aufnr LIKE aufk-aufnr MEMORY ID anr.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN SKIP.
PARAMETERS: p_compon AS CHECKBOX DEFAULT 'X'.
PARAMETERS: p_partn AS CHECKBOX DEFAULT 'X'.
START-OF-SELECTION.
IF p_aufnr IS INITIAL.
 MOVE '007321002921' TO p_aufnr.
ENDIF.
PERFORM it_methods_fill.
PERFORM it_header_fill.
PERFORM it_operation_fill.
IF p_compon = 'X'.
 PERFORM it_component_fill.
ENDIF.
REFRESH et_numbers.
break zaladev.
CALL FUNCTION 'Z_BAPI_ALM_ORDER_MAINTAIN'
 TABLES
 it_methods = it_methods
 it_header = it_header
* IT_HEADER_UP =
* IT_HEADER_SRV =
* IT_HEADER_SRV_UP =
* IT_USERSTATUS =
* IT_PARTNER =
* IT_PARTNER_UP =
 it_operation = it_operation
* IT_OPERATION_UP =
* IT_RELATION =
* IT_RELATION_UP =
 it_component = it_component
 it_component_up = it_component_up
* IT_TEXT = it_text
* IT_TEXT_LINES =
 extension_in = et_extension_in
 et_return = et_return
 et_numbers = et_numbers.
CLEAR lv_commit.
LOOP AT et_return INTO wa_return.
 IF wa_return-type = 'S' AND NOT wa_return-message_v2 IS INITIAL.
 IF p_test IS INITIAL.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
 lv_commit = 1.
 ENDIF.
 EXIT.
 ENDIF.
ENDLOOP.
IF lv_commit IS INITIAL.
 CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
ENDIF.
break zaladev.
*& Form it_methods_fill
* text
* --> p1 text
* <-- p2 text
FORM it_methods_fill.
IF p_create = 'X'. "LÉTREHOZÁS
 MOVE '1' TO wa_methods-refnumber.
 MOVE 'HEADER' TO wa_methods-objecttype.
 MOVE 'CREATE' TO wa_methods-method.
 MOVE '%00000000001' TO wa_methods-objectkey.
 APPEND wa_methods TO it_methods.
 MOVE '1' TO wa_methods-refnumber.
 MOVE 'OPERATION' TO wa_methods-objecttype.
 MOVE 'CREATE' TO wa_methods-method.
 MOVE '%000000000010010' TO wa_methods-objectkey.
 APPEND wa_methods TO it_methods.
 MOVE '2' TO wa_methods-refnumber.
 MOVE 'OPERATION' TO wa_methods-objecttype.
 MOVE 'CREATE' TO wa_methods-method.
 MOVE '%000000000010020' TO wa_methods-objectkey.
 APPEND wa_methods TO it_methods.
 MOVE '3' TO wa_methods-refnumber.
 MOVE 'OPERATION' TO wa_methods-objecttype.
 MOVE 'CREATE' TO wa_methods-method.
 MOVE '%0000000000100200010' TO wa_methods-objectkey.
 APPEND wa_methods TO it_methods.
 MOVE '4' TO wa_methods-refnumber.
 MOVE 'OPERATION' TO wa_methods-objecttype.
 MOVE 'CREATE' TO wa_methods-method.
 MOVE '%0000000000100200020' TO wa_methods-objectkey.
 APPEND wa_methods TO it_methods.
 IF p_compon = 'X'.
 MOVE 1 TO wa_methods-refnumber.
 MOVE 'COMPONENT' TO wa_methods-objecttype.
 MOVE 'CREATE' TO wa_methods-method.
 MOVE '%00000000001' TO wa_methods-objectkey.
 APPEND wa_methods TO it_methods.
 MOVE 2 TO wa_methods-refnumber.
 MOVE 'COMPONENT' TO wa_methods-objecttype.
 MOVE 'CREATE' TO wa_methods-method.
 MOVE '%00000000001' TO wa_methods-objectkey.
 APPEND wa_methods TO it_methods.
 ENDIF.
 MOVE '1' TO wa_methods-refnumber.
 MOVE '' TO wa_methods-objecttype.
 MOVE 'SAVE' TO wa_methods-method.
 MOVE '%00000000001' TO wa_methods-objectkey.
 APPEND wa_methods TO it_methods.
ELSE. "MÓDOSÍTÁS
 MOVE '1' TO wa_methods-refnumber.
 MOVE 'HEADER' TO wa_methods-objecttype.
 MOVE 'CHANGE' TO wa_methods-method.
 MOVE p_aufnr TO wa_methods-objectkey.
 APPEND wa_methods TO it_methods.
 IF p_compon = 'X'.
 MOVE 1 TO wa_methods-refnumber.
 MOVE 'COMPONENT' TO wa_methods-objecttype.
 MOVE 'CHANGE' TO wa_methods-method.
 MOVE p_aufnr TO wa_methods-objectkey.
 APPEND wa_methods TO it_methods.
 MOVE 2 TO wa_methods-refnumber.
 MOVE 'COMPONENT' TO wa_methods-objecttype.
 MOVE 'CHANGE' TO wa_methods-method.
 MOVE p_aufnr TO wa_methods-objectkey.
 APPEND wa_methods TO it_methods.
 MOVE 3 TO wa_methods-refnumber.
 MOVE 'COMPONENT' TO wa_methods-objecttype.
 MOVE 'DELETE' TO wa_methods-method.
 MOVE p_aufnr TO wa_methods-objectkey.
 APPEND wa_methods TO it_methods.
 ENDIF.
 MOVE '1' TO wa_methods-refnumber.
 MOVE '' TO wa_methods-objecttype.
 MOVE 'SAVE' TO wa_methods-method.
 MOVE p_aufnr TO wa_methods-objectkey.
 APPEND wa_methods TO it_methods.
ENDIF.
ENDFORM. " it_methods_fill
*& Form it_header_fill
* text
* --> p1 text
* <-- p2 text
FORM it_header_fill .
IF p_create = 'X'. "LÉTREHOZÁS
 MOVE '%00000000001' TO wa_header-orderid.
 MOVE 'D210' TO wa_header-order_type. "rendelésfajta
 MOVE '2000' TO wa_header-planplant. "tervező gyár
 MOVE '19' TO wa_header-mn_wk_ctr. "fel.munkahely
 MOVE '2000' TO wa_header-plant. "fel.munkahely gyára
 MOVE 'CUV-SZV-CSUR-ATEM-I...' TO wa_header-funct_loc. "műsz.hely
 MOVE '' TO wa_header-equipment. "berendezés
 MOVE '' TO wa_header-material. "anyagszám
* MOVE '' TO wa_header-LOC_WK_CTR. "fel.munkahely
* MOVE '' TO wa_header-LOC_COMP_CODE. "vállalat
* MOVE sy-datum TO wa_header-START_DATE. "kezdés dátuma
* MOVE sy-datum TO wa_header-FINISH_DATE. "befejezés dátuma
* MOVE '' TO wa_header-BASICSTART. "kezdés időpontja
* MOVE '' TO wa_header-BASIC_FIN. "befejezés időpontja
 MOVE 'Teszt szöveg 1' TO wa_header-short_text. "szöveg
 APPEND wa_header TO it_header.
ELSE. "MÓDOSÍTÁS
 MOVE p_aufnr TO wa_header-orderid.
 MOVE 'CUV-SZV-CSUR-ATEM-II..' TO wa_header-funct_loc. "műsz.hely
 MOVE 'Teszt szöveg módosítva 2' TO wa_header-short_text. "szöveg
 APPEND wa_header TO it_header.
ENDIF.
ENDFORM. " it_header_fill
*& Form it_operation_fill
* text
* --> p1 text
* <-- p2 text
FORM it_operation_fill .
IF p_create = 'X'. "LÉTREHOZÁS
 MOVE 10 TO wa_operation-activity. "művelet
 MOVE '' TO wa_operation-sub_activity. "al-művelet
 MOVE 'PM01' TO wa_operation-control_key. "vezérlő kulcs
* MOVE '19' TO wa_operation-WORK_CNTR. "munkahely
* MOVE '2000' TO wa_operation-PLANT. "gyár
 MOVE '' TO wa_operation-standard_text_key. "mintakulcs
 MOVE 'Művelet leírása 1.sor' TO wa_operation-description."leírás
 MOVE '' TO wa_operation-vendor_no. "szállító
* MOVE 3 TO wa_operation-quantity. "mennyiség
* MOVE 'KG' TO wa_operation-base_uom. "menny.egys.
* MOVE 500 TO wa_operation-PRICE. "ár
* MOVE 1 TO wa_operation-PRICE_UNIT. "áregység
* MOVE 'HUF' TO wa_operation-CURRENCY. "pénznem
* MOVE '' TO wa_operation-PERS_NO. "törzsszám
 MOVE 10 TO wa_operation-work_activity. "művelet munkája
* MOVE 'KG' TO wa_operation-UN_WORK. "művelet munkája
 MOVE 2 TO wa_operation-number_of_capacities. "szüks. kapacitás
 APPEND wa_operation TO it_operation.
 MOVE 20 TO wa_operation-activity. "művelet
 MOVE '' TO wa_operation-sub_activity. "al-művelet
 MOVE 'PM01' TO wa_operation-control_key. "vezérlő kulcs
* MOVE '19' TO wa_operation-WORK_CNTR. "munkahely
* MOVE '2000' TO wa_operation-PLANT. "gyár
 MOVE '' TO wa_operation-standard_text_key. "mintakulcs
 MOVE 'Művelet leírása 2.sor' TO wa_operation-description."leírás
 MOVE '' TO wa_operation-vendor_no. "szállító
* MOVE 5 TO wa_operation-quantity. "mennyiség
* MOVE 'KG' TO wa_operation-base_uom. "menny.egys.
* MOVE 500 TO wa_operation-PRICE. "ár
* MOVE 1 TO wa_operation-PRICE_UNIT. "áregység
* MOVE 'HUF' TO wa_operation-CURRENCY. "pénznem
* MOVE '' TO wa_operation-PERS_NO. "törzsszám
 MOVE 5 TO wa_operation-work_activity. "művelet munkája
* MOVE 'KG' TO wa_operation-UN_WORK. "művelet munkája
 MOVE 1 TO wa_operation-number_of_capacities. "szüks. kapacitás
 APPEND wa_operation TO it_operation.
 MOVE 20 TO wa_operation-activity. "művelet
 MOVE 10 TO wa_operation-sub_activity. "al-művelet
 MOVE 'PM01' TO wa_operation-control_key. "vezérlő kulcs
* MOVE '19' TO wa_operation-WORK_CNTR. "munkahely
* MOVE '2000' TO wa_operation-PLANT. "gyár
 MOVE '' TO wa_operation-standard_text_key. "mintakulcs
 MOVE 'Alművelet leírása 2/1.sor' TO wa_operation-description."leírás
 MOVE '' TO wa_operation-vendor_no. "szállító
* MOVE 5 TO wa_operation-quantity. "mennyiség
 MOVE 'KG' TO wa_operation-base_uom. "menny.egys.
* MOVE 500 TO wa_operation-PRICE. "ár
* MOVE 1 TO wa_operation-PRICE_UNIT. "áregység
* MOVE 'HUF' TO wa_operation-CURRENCY. "pénznem
* MOVE '' TO wa_operation-PERS_NO. "törzsszám
 MOVE 2 TO wa_operation-work_activity. "művelet munkája
* MOVE 'KG' TO wa_operation-UN_WORK. "művelet munkája
 MOVE 1 TO wa_operation-number_of_capacities. "szüks. kapacitás
 APPEND wa_operation TO it_operation.
 MOVE 20 TO wa_operation-activity. "művelet
 MOVE 20 TO wa_operation-sub_activity. "al-művelet
 MOVE 'PM01' TO wa_operation-control_key. "vezérlő kulcs
* MOVE '19' TO wa_operation-WORK_CNTR. "munkahely
* MOVE '2000' TO wa_operation-PLANT. "gyár
 MOVE '11' TO wa_operation-standard_text_key. "mintakulcs
 MOVE 'Alművelet leírása 2/2.sor' TO wa_operation-description."leírás
 MOVE '' TO wa_operation-vendor_no. "szállító
 MOVE 5 TO wa_operation-quantity. "mennyiség
 MOVE 'KG' TO wa_operation-base_uom. "menny.egys.
* MOVE 500 TO wa_operation-PRICE. "ár
* MOVE 1 TO wa_operation-PRICE_UNIT. "áregység
* MOVE 'HUF' TO wa_operation-CURRENCY. "pénznem
* MOVE '' TO wa_operation-PERS_NO. "törzsszám
 MOVE 3 TO wa_operation-work_activity. "művelet munkája
* MOVE 'KG' TO wa_operation-UN_WORK. "művelet munkája
 MOVE 1 TO wa_operation-number_of_capacities. "szüks. kapacitás
 APPEND wa_operation TO it_operation.
ELSE. "MÓDOSÍTÁS
ENDIF.
ENDFORM. " it_operation_fill
*& Form it_component_fill
* text
* --> p1 text
* <-- p2 text
FORM it_component_fill.
IF p_create = 'X'. "LÉTREHOZÁS
 MOVE '0010' TO wa_component-item_number.
 MOVE '000000023336110300' TO wa_component-material. "cikkszám
 MOVE '2000' TO wa_component-plant. "gyár
 MOVE '0001' TO wa_component-stge_loc. "raktár
 MOVE 1 TO wa_component-requirement_quantity. "felh.m.
 MOVE '0020' TO wa_component-activity. "művelet
 APPEND wa_component TO it_component.
 MOVE '0020' TO wa_component-item_number.
 MOVE '000000095000001900' TO wa_component-material. "cikkszám
 MOVE '2000' TO wa_component-plant. "gyár
 MOVE '' TO wa_component-stge_loc. "raktár
 MOVE 2 TO wa_component-requirement_quantity. "felh.m.
 MOVE '0020' TO wa_component-activity. "művelet
 MOVE 'N' TO wa_component-item_cat. "tételtípus
 MOVE '0000000014' TO wa_component-vendor_no. "szállító
 APPEND wa_component TO it_component.
ELSE. "MÓDOSÍTÁS
 SELECT * FROM resb
 INTO TABLE it_resb
 WHERE aufnr EQ p_aufnr.
 IF sy-subrc = 0.
 READ TABLE it_resb INTO wa_resb
 WITH KEY aufnr = p_aufnr.
 MOVE wa_resb-rsnum TO wa_component-reserv_no.
 ELSE.
 CLEAR wa_component-reserv_no.
 ENDIF.
 MOVE '0010' TO wa_component-item_number.
 MOVE '0001' TO wa_component-res_item.
* MOVE '000000023336110400' TO wa_component-material. "cikkszám
* MOVE '2000' TO wa_component-plant. "gyár
* MOVE '0001' TO wa_component-stge_loc. "raktár
 MOVE 6 TO wa_component-requirement_quantity. "felh.m.
 MOVE '0020' TO wa_component-activity. "művelet
 APPEND wa_component TO it_component.
 MOVE 'X' TO wa_component_up-requirement_quantity.
 MOVE 'X' TO wa_component_up-activity.
 APPEND wa_component_up TO it_component_up.
 MOVE '0020' TO wa_component-item_number.
 MOVE '0002' TO wa_component-res_item.
* MOVE '000000095000001800' TO wa_component-material. "cikkszám
* MOVE '2000' TO wa_component-plant. "gyár
* MOVE '0001' TO wa_component-stge_loc. "raktár
 MOVE 6 TO wa_component-requirement_quantity. "felh.m.
 MOVE '0010' TO wa_component-activity. "művelet
 APPEND wa_component TO it_component.
* MOVE 'X' TO wa_component_up-material.
 MOVE 'X' TO wa_component_up-requirement_quantity.
 MOVE 'X' TO wa_component_up-activity.
 APPEND wa_component_up TO it_component_up.
 MOVE '0030' TO wa_component-item_number.
 MOVE '000000023336110400' TO wa_component-material. "cikkszám
 MOVE '2000' TO wa_component-plant. "gyár
 MOVE '0001' TO wa_component-stge_loc. "raktár
 MOVE 7 TO wa_component-requirement_quantity. "felh.m.
 MOVE '0020' TO wa_component-activity. "művelet
 APPEND wa_component TO it_component.
ENDIF.
ENDFORM. " it_component_fill

Alternative UI Output formats for BAPI table

Hi Experts,
Can I display the output of a BAPI table in any other format apart from a table.
Regards
Abdullah

Abdullah,
In web dynpro you cannot have tables with scrollbar. A workaround for that may be a use of ScrollContainer UI element with fixed height and display all table rows via setting visibleRowsCount=-1.but problem here is , table headers will be scrolled as well. So it is better not to have them like that.
I would suggest take use of existing table UI element and dont alter its functionality.
Regarding incorporating the application using web dynpro I guess that you must be knowing(not sure but think that you need to get rid of COM DCOM).
hope it helps
regards,

RFC+BAPI+TABLE HELP

Similar Messages

Maybe you are looking for