BAPI's in the same LUW

Hi experts,
I'm developing a FM, that will do the folowing SD process:
- create Sales Order
- outbound delivery
- Goods Issue
- Create the Billing document.
I'm using BAPI's for all.
My question is:
I want to make the commit work, only in the last of the process, after create the billing doc.
But, if I don't make the commit work after each bapi calling, the next bapi does not work.
There is some way to do this without make a commit ?
Alexandre Nogueira

I wonder if it is possible.
I had similar problem in earlier project. We sued BAPIs for this and here we had to use COMMIt in order to execute next BAPI.
If in the flow, any BAPI fails, you can revert back earlier documents by deleting from db.
Instead of going with this option, we created a custom program which will show status for each Entry. If it is failed at any stage, it will display as red entry and user can view the log for error message. They can correct these entries and repost. So it will continue the process and once it is completed then the entry will have green status.

Similar Messages

Looking for a BAPI that does the same as /$SYNC

Dear Experts,
Could someone tell me which BAPI resets all buffers, I need one just like running /$SYNC. Thanks in advance.
PS: I use a system for test purpose, not a real one in a company.

Thanks for your answer Markus. I would like to call the t-code $SYNC out of the SAP GUI, because I am using a webservice to measure the memory used in the buffers, which gives me the same as the transaction ST02 (and I want to avoid the SAP GUI effect on memory usage by using ST02 and $SYNC, for the ST02 I have a BAPI, but not for the T-Code).Then I need to reset the buffers to know how much memory is used by some of my webservices.
Do you know a way to use this t-code $SYNC out of the SAP GUI?
PS: I use a system for testing purposes, not a real one in a company. And it's on Unix.
Edited by: raesna1 on Dec 14, 2010 6:12 PM

Two bapi calls in the same session using PI

Hi,
I have a file to RFC scenario wherein I need to call a BAPI (L_TO_CANCEL) and then again, I need to call another bapi called
"BAPI_TRANSACTION_COMMIT" in the same session. My question is, if I use RFC adapter, do I have to call the commit bapi again?
If yes, is there anyway I can do that ?
I believe that will be the case only if I use a proxy. Is that correct ?
The requirement is to call these two BAPIs and finally include a success or error message in the response.
Thanks.

Inside the BPM you do not have a specific exception message. You can do an exception handling based on the exception, but the excpetion itself is not a real message.
If you want a real message, you could create an ABAP proxy, which has a message like this:
root
- part1
       - rfc response
   - part2
        - error text
then you can split this inside BPM and send a the response or the error.
Of course there are other possible solutions.

How ca we create an INVOICE using a BAPI and triggring the same IDoc

Hi Gurus,
I have a senario where in I need to create an Invoice from a remote using BAPI and then the INVOICE IDOC has to be triggered for external purpose.
How can be this achived??
Help me as early as possible.
Thanks in Advance...
Suma

Hi,
Are you looking for BAPI BAPI_ACC_INVOICE_RECEIPT_POST?
Hope this helps (please reward me if it does).
Regards, Joerg

In BAPI's why the structures are used in table parameters?

Hello sir,
what is BAPI sir? In BAPI's why the structures are used in table parameters? table parameters they are using structures but not using any customized tables ?
regards
rachu.

Hello Rachu
BAPIs provide RFC-enabled interfaces to SAP business objects (e.g. like customer, sales order, purchase order, etc.).
A BAPI does basically the same like you would need to do calling the corresponding transaction (e.g. BAPI_SALESORDER_CREATE -> VA01).
Since they are RFC-enabled they can be called from external systems.
BAPIs represent an external interface for the outside world. Very often you will find within the BAPI that there is a mapping done to the (SAP-)internal structures at the beginning of the coding and vice versa at the end of the coding. Thus, you will (almost) never find any DB table name used as type of a BAPI TABLES parameter.
Regards
Uwe

BAPI to get the Sales order line item details

Hi,
My program gets Sale sorder and item as the input and I need to fetch all the item (Given item) details for this Sales Order from VBAP. Is there any BAPI to get the item details?

Hi,
This is a sample code of BAPI.Try to map it to your requirement.This is not related to vendor.This is related to sales order.
Constants
CONSTANTS: c_contract LIKE vbak-vbeln VALUE '0020000720',
c_item LIKE vbap-posnr VALUE '000010'.
Structures
Structure to hold BAPI Header
DATA: st_bapisdhd1 LIKE bapisdhd1.
Internal Tables
Sales Order Create BAPI Return Messages
DATA: tbl_return TYPE STANDARD TABLE OF bapiret2
WITH HEADER LINE.
Sales Order BAPI Line Item
DATA: tbl_bapisditm TYPE STANDARD TABLE OF bapisditm
WITH HEADER LINE.
Sales Order BAPI Line Item
DATA: tbl_bapisditmx TYPE STANDARD TABLE OF bapisditmx
WITH HEADER LINE.
Sales Order BAPI Pricing Conditions
DATA: tbl_bapicond TYPE STANDARD TABLE OF bapicond
WITH HEADER LINE.
Sales Order BAPI Partner Functions
DATA: tbl_bapiparnr TYPE STANDARD TABLE OF bapiparnr
WITH HEADER LINE.
Sales Order BAPI Schedule Lines
DATA: tbl_bapischdl TYPE STANDARD TABLE OF bapischdl
WITH HEADER LINE.
Sales Order BAPI Schedule Lines
DATA: tbl_bapischdlx TYPE STANDARD TABLE OF bapischdlx
WITH HEADER LINE.
Sales Order BAPI Pricing Conditions
DATA: tbl_bapicondx TYPE STANDARD TABLE OF bapicondx
WITH HEADER LINE.
Customer Enhancement for VBAK, VBAP, VBEP
DATA: tbl_bapiparex TYPE STANDARD TABLE OF bapiparex
WITH HEADER LINE.
Table to hold BAPI Detail Conditions
DATA: tbl_bapisdcond TYPE STANDARD TABLE OF bapisdcond
WITH HEADER LINE.
Table to hold Return Messages from Sales Order Change BAPI
DATA: tbl_return_chg TYPE STANDARD TABLE OF bapiret2
WITH HEADER LINE.
Variables
DATA: g_vbeln_created LIKE vbak-vbeln,
g_valid_contract TYPE c,
g_cont_price_date TYPE d.
Start of Selection
START-OF-SELECTION.
PERFORM validate_contract.
PERFORM create_sales_ord.
PERFORM update_sales_ord.
End of Selection
END-OF-SELECTION.
PERFORM write_output_report.
Subroutines
*& Form create_sales_ord
Create the Sales Order
FORM create_sales_ord .
PERFORM populate_bapi_tables.
PERFORM call_create_sales_ord_bapi.
ENDFORM. " create_sales_ord
*& Form populate_bapi_tables
Fill up the BAPI Tables
FORM populate_bapi_tables .
PERFORM populate_bapi_header.
PERFORM build_bapi_partners.
PERFORM build_bapi_items.
PERFORM build_bapi_sched_lines.
ENDFORM. " populate_bapi_tables
*& Form populate_bapi_header
Build BAPI Header Details
FORM populate_bapi_header .
CLEAR st_bapisdhd1.
st_bapisdhd1-doc_type = 'ZOC'. "Order type
st_bapisdhd1-sales_org = '026'. "Sales Org
st_bapisdhd1-distr_chan = '00'. "Dist Channel
st_bapisdhd1-division = '00'. "Division
st_bapisdhd1-purch_no_c = 'Cust Po No'. "Cust PO No
st_bapisdhd1-name = 'Orderer'. "Name of Orderer
st_bapisdhd1-ord_reason = ''. "Order Reason
st_bapisdhd1-sales_off = '3001'. "Sales Office
st_bapisdhd1-sales_grp = '301'. "Market Area
IF g_valid_contract = 'X'.
st_bapisdhd1-price_date = g_cont_price_date.
ENDIF.
ENDFORM. " populate_bapi_header
*& Form build_bapi_partners
Build BAPI Partner Functions
FORM build_bapi_partners .
CLEAR tbl_bapiparnr.
tbl_bapiparnr-partn_role = 'AG'.
tbl_bapiparnr-partn_numb = '0000100750'.
APPEND tbl_bapiparnr.
CLEAR tbl_bapiparnr.
tbl_bapiparnr-partn_role = 'WE'.
tbl_bapiparnr-partn_numb = '0000504472'.
APPEND tbl_bapiparnr.
ENDFORM. " build_bapi_partners
*& Form build_bapi_items
Build The BAPI Line Items
FORM build_bapi_items .
DATA: l_matnr LIKE mara-matnr.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = '10000072'
IMPORTING
output = l_matnr.
CLEAR tbl_bapisditm.
tbl_bapisditm-itm_number = c_item.
IF g_valid_contract = 'X'.
tbl_bapisditm-ref_doc = c_contract.
tbl_bapisditm-ref_doc_it = c_item.
tbl_bapisditm-ref_doc_ca = 'G'. "Contract
ENDIF.
tbl_bapisditm-material = l_matnr.
tbl_bapisditm-plant = '3012'.
tbl_bapisditm-target_qty = '5.000'.
tbl_bapisditm-target_qu = 'M3'.
tbl_bapisditm-item_categ = 'ZZOC'.
tbl_bapisditm-sales_dist = '301'.
tbl_bapisditm-dlv_prio = '02'.
tbl_bapisditm-prc_group5 = '080'.
tbl_bapisditm-cust_mat35 = 'kdmat'.
tbl_bapisditm-route = 'TESYS'.
tbl_bapisditm-usage_ind = 'CIV'.
APPEND tbl_bapisditm.
CLEAR tbl_bapisditmx.
tbl_bapisditmx-itm_number = c_item.
tbl_bapisditmx-ref_doc = 'X'.
tbl_bapisditmx-ref_doc_it = 'X'.
tbl_bapisditmx-ref_doc_ca = 'X'.
tbl_bapisditmx-material = 'X'.
tbl_bapisditmx-updateflag = 'I'.
tbl_bapisditmx-plant = 'X'.
tbl_bapisditmx-target_qty = 'X'.
tbl_bapisditmx-target_qu = 'X'.
tbl_bapisditmx-item_categ = 'X'.
tbl_bapisditmx-sales_dist = 'X'.
tbl_bapisditmx-dlv_prio = 'X'.
tbl_bapisditmx-prc_group5 = 'X'.
tbl_bapisditmx-cust_mat35 = 'X'.
tbl_bapisditmx-usage_ind = 'X'.
tbl_bapisditmx-route = 'X'.
APPEND tbl_bapisditmx.
ENDFORM. " build_bapi_items
*& Form build_bapi_sched_lines
Build the BAPI Schedule Lines
FORM build_bapi_sched_lines .
CLEAR tbl_bapischdl.
tbl_bapischdl-itm_number = c_item.
tbl_bapischdl-req_qty = '1'.
tbl_bapischdl-req_date = sy-datum.
APPEND tbl_bapischdl.
ENDFORM. " build_bapi_sched_lines
*& Form build_bapi_conditions
Pull the BAPI Pricing Conditions from the Contract
FORM build_bapi_conditions .
LOOP AT tbl_bapisdcond.
CLEAR tbl_bapicond.
MOVE-CORRESPONDING tbl_bapisdcond TO tbl_bapicond.
APPEND tbl_bapicond.
CLEAR tbl_bapicondx.
tbl_bapicondx-itm_number = tbl_bapicond-itm_number.
tbl_bapicondx-cond_st_no = tbl_bapicond-cond_st_no.
tbl_bapicondx-cond_count = tbl_bapicond-cond_count.
tbl_bapicondx-cond_type = tbl_bapicond-cond_type.
tbl_bapicondx-updateflag = 'I'.
tbl_bapicondx-cond_value = 'X'.
tbl_bapicondx-currency = 'X'.
tbl_bapicondx-cond_unit = 'X'.
tbl_bapicondx-cond_p_unt = 'X'.
tbl_bapicondx-varcond = tbl_bapicond-varcond.
APPEND tbl_bapicondx.
ENDLOOP.
ENDFORM. " build_bapi_conditions
*& Form call_create_sales_ord_bapi
Call the Sales Order Create BAPI
FORM call_create_sales_ord_bapi .
CLEAR g_vbeln_created.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
order_header_in = st_bapisdhd1
IMPORTING
salesdocument = g_vbeln_created
TABLES
return = tbl_return
order_items_in = tbl_bapisditm
order_items_inx = tbl_bapisditmx
order_partners = tbl_bapiparnr
order_schedules_in = tbl_bapischdl.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
ENDFORM. " call_create_sales_ord_bapi
*& Form update_sales_ord
Update the newly created Sales Order with the Pricing Conditions
from the Contract
FORM update_sales_ord .
CHECK g_valid_contract EQ 'X'.
PERFORM get_contract_details.
PERFORM build_bapi_conditions.
PERFORM call_change_sales_ord_bapi.
ENDFORM. " update_sales_ord
*& Form get_contract_details
Get Contract Details
FORM get_contract_details .
Need to manually get the relevant Pricing Conditions as the BAPI
BAPISDORDER_GETDETAILEDLIST causes problems when we call the BAPI
BAPI_SALESORDER_CREATEFROMDAT2 and BAPI_SALESORDER_CHANGE (I think
this is due to the fact that these BAPIs belong to the same Function
Group and there must be some common structures that are not cleared
causing us all sorts of grief when we try and call the next BAPI)
DATA: tbl_konv TYPE STANDARD TABLE OF konv WITH HEADER LINE.
DATA: tbl_komv TYPE STANDARD TABLE OF komv WITH HEADER LINE.
DATA: tbl_vbak TYPE STANDARD TABLE OF vbak WITH HEADER LINE.
Pricing Condition Master
DATA: BEGIN OF tbl_t685a OCCURS 0,
kschl LIKE t685a-kschl,
kaend_wrt LIKE t685a-kaend_wrt,
END OF tbl_t685a.
SELECT *
INTO TABLE tbl_vbak
FROM vbak
WHERE vbeln = c_contract.
READ TABLE tbl_vbak INDEX 1.
SELECT *
INTO TABLE tbl_konv
FROM konv
WHERE knumv = tbl_vbak-knumv AND
kposn = c_item.
CHECK sy-subrc EQ 0.
We now need to make sure we only bring across the Condition Types that
are EDITABLE. If we bring across non editable conditions (such as
'ZPR1') the Change Sales Order BAPI will fail
SELECT kschl kaend_wrt
INTO TABLE tbl_t685a
FROM t685a
FOR ALL ENTRIES IN tbl_konv
WHERE kappl EQ 'V' AND "Sales
kschl EQ tbl_konv-kschl AND
kaend_wrt EQ 'X' AND "Value is Editable
kmanu NE 'D'. "Process manually
Prepare for Binary Search
SORT tbl_t685a BY kschl.
LOOP AT tbl_konv.
READ TABLE tbl_t685a WITH KEY kschl = tbl_konv-kschl BINARY SEARCH.
IF sy-subrc EQ 0.
MOVE-CORRESPONDING tbl_konv TO tbl_komv.
APPEND tbl_komv.
ENDIF.
ENDLOOP.
CHECK NOT tbl_komv[] IS INITIAL.
Map KOMV into the more BAPI friendly BAPISDCOND structure
CALL FUNCTION 'MAP_INT_TO_EXT_STRUCTURE'
TABLES
fxvbak = tbl_vbak
fxkomv = tbl_komv
fxbapikomv = tbl_bapisdcond
EXCEPTIONS
entry_missing = 1
OTHERS = 2.
ENDFORM. " get_contract_details
*& Form call_change_sales_ord_bapi
Call the Change Sales Order BAPI
FORM call_change_sales_ord_bapi .
DATA: st_head_chg LIKE bapisdh1x,
st_logic_switch TYPE bapisdls.
CHECK NOT g_vbeln_created IS INITIAL.
CHECK g_valid_contract EQ 'X'.
st_head_chg-updateflag = 'U'.
st_logic_switch-cond_handl = 'X'.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
salesdocument = g_vbeln_created
order_header_inx = st_head_chg
logic_switch = st_logic_switch
TABLES
return = tbl_return_chg
conditions_in = tbl_bapicond
conditions_inx = tbl_bapicondx.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
ENDFORM. " call_change_sales_ord_bapi
*& Form write_output_report
Produce Output Report
FORM write_output_report .
IF NOT g_vbeln_created IS INITIAL.
WRITE:/ 'Success! Sales Order', g_vbeln_created, 'was created!'.
ELSE.
WRITE:/ 'Failure! Sales Order was not created!'.
ENDIF.
SKIP.
WRITE:/ 'Sales Order Create Log'.
LOOP AT tbl_return.
WRITE:/ tbl_return-type, tbl_return-id, tbl_return-number,
tbl_return-message.
ENDLOOP.
SKIP.
WRITE:/ 'Sales Order Change Log'.
LOOP AT tbl_return_chg.
WRITE:/ tbl_return_chg-type, tbl_return_chg-id,
tbl_return_chg-number, tbl_return_chg-message.
ENDLOOP.
ENDFORM. " write_output_report
*& Form validate_contract
Make sure that the Contract is Valid
FORM validate_contract .
DATA: l_gueen LIKE vbak-gueen,
l_prsdt LIKE vbkd-prsdt.
SELECT SINGLE vbakgueen vbkdprsdt
INTO (l_gueen, l_prsdt)
FROM vbak
INNER JOIN vbkd
ON vbakvbeln = vbkdvbeln
WHERE vbak~vbeln = c_contract AND
vbkd~posnr = '000000'.
IF sy-datum LE l_gueen.
Contract is valid! Set Order Price Date
g_valid_contract = 'X'.
g_cont_price_date = l_prsdt.
ENDIF.
ENDFORM. " validate_contract
Regards
Rajesh Kumar

FM or BAPI to update the database table /TDAG/CPT_DEC_IN

Hi All,
I need to update a few entries in the database table /TDAG/CPT_DEC_IN (CP: Declarable Substances, Independent attributes). This table contains data for the EHS ( Environment, Health and Safety) Module in SAP.
Instead of doing a direct database update, I needed a FM or a BAPI to update the same.
Any pointers towards this will be really useful.
Thanks and Regards,
Arti Dohare

Hi Raymond,
Thanks for the reply. it seems I was using the wrong BAPI then.
I actually created the network using the BAPI "BAPI_BUS2002_CREATE".
This BAPI does not have the field call "Resp. cost cntr" in its input parameters and so I could not pass it there. Now I am trying to find if there is any standard FM or BAPI to maintain this field in the networks.
I request you to please suggest some FM or BAPI if you know.
Thanks and Regards.
Piyush R Sakharkar.

Not to upload the same file more than once from legacy thru BAPI

i have a BAPI program for uploading datas to ME21N transaction code.the values are getting stored in structure table only
to upload the values under one header, i have declared one constant serial number, in which that is the main identification to upload the various line items in one header.
if i uploaded the data once again , the data must not be uploaded, even if a different user tries to upload. The serial number will be same for all the items and also the supplying plant also will be same for all line items.how will i identify or store the serial number and plant , in such a way that the same plant for this combination must not be uploaded again. i have created a ztable and stored the serial num and plant.if this two fields are getting repeated for the same plant then the action must not occur else if for a diff plant the bapi program has to create a PO.
can anybody give me a solution for this. how to make this simpler and identify the already uploaded data.

hi
when u r about to upload query ur main table ekko or ekpo if the entries already exist.
if yes then issue an error message.
Regards
Sajid

Copy standard bapi to Zbapi in the same standard package

Dear SAP,
I wanted to copy a standard bapi into Zbapi. As soon as i do this it is asking for access key.
Is it ok to use the access key and create??
Is there any exit to do this ?
Please help me in this regard.
The Bapi name /AFS/BAPI_SALESORD_CREATEFDATA
from this Bapi, i want to create the ZBAPI.
Regards,
Arati

If you put it in the same function group as the original, when new function modules are added to that function group, your BAPI will be affected - possibly disappear (depending on settings). it will certainly be an upgrade issue.
If you put it in a SAP package, you are violating the principle of separating custom developments from SAP standard, but it's unlikely to cause issues.
However, copying a BAPI (indeed any cloning of SAP standard code) is a bad idea. The reason is that the copy won't benefit from any notes or upgrades. If there's an error in the standard fixed by note application, you won't get it applied in the copy. Your copy will gradually become out of date. At some point it will probably break, and then you'll have to reclone the original, which can be quite difficult if it has changed radically.
You should first try to find user exits (CMOD, BADI, explicit enhancement points), and implicit enhancement points, and finally direct modification of the original bapi.
I repeat, cloning a SAP standard object is 99.9999% of the time the worst things to do. Far worse than a customer modification. Ignorant project managers, team leads etc. prefer clones because they don't need an object key. Don't be stupid. Do the right thing.

Multiple Input Ports on BAPI to submit at the same time

Hi
I have looked at previous threads and still not getting this right. When I click the submit button I need it to all go to the BAPI at the same time.
I'm using BAPI SalesorderCreatefromdat2, I need to use at least three input ports.
I have done the following.
-dragged the bapi on the page
-selected the ports required, flipped a port of required
-the for ports I have created 1 form (Order Headr I n Port), 2 tables (Order Itmes In port, Order Partners Port).
-the have connected the form and tables to the bapi, so have three different lines.
-For each one the eventname is *SubmitAll
-Then there is one button,on the action tab I selected custom action,the name is SUBMITALL, Apply To is Self
Is the above correct??
Please let me know, thanks in advance

Hi Basheer
Thank you for your reply.
I have changed the buttons to Action Type "System Action", the field System Action to "Submit Form", the Apply To is "Self"
I however get the error "Please enter sold to party or ship to party"
Can you please help me. I have changed my BAPI to use SalesorderCreatefromdat1 like yours.
I'm using the following input ports and fields
-Order Header in form, using fields DISTR_CHAN, DIVISON, DOC_TYPE, SALES_ORG
-Order Partners Table in table, using fields PARTN_NUM and PARTN_ROLE
-Order Itmes Table in Table, using fields MATERIAL and TARGET_QTY.
Is this correct? Thank you for the response.

Why BDC when we can do the same with Bapi's

Hiii
Plz tell me why BDC when we can do the same with Bapi...
plz list out the differences clearly
Thanks & Regards
krishna

If the same functionality can be achieved by BAPI then we generally go for BAPI instead of BDC. The main reason is that the screen no can change in the next version and in that case the BDC code will not work. But if no BAPI is available then we go for BDC.
Sometimes we need to handle a large amount of data in BDC/BAPI in which it is not preferable to use 'CALL TRANSACTION' command. If the corresponding BAPI internally use 'CALL TRANSACTION' command. Then instead of that BAPI we create a BDC with SESSION METHOD.
Ex: IDOC_INPUT_ORDERS internally use CALL TRANSACTION. So if we need to use a large amount of data we create a BDC with session method instead of using IDOC_INPUT_ORDERS.

RFC or Bapi RFC ? to import RFC Adaptive Model - Is the same one or other?

Hi:
I want to know if is exactly the same to import a RFC not a (BAPI marked as RFC) to use the model, since I'm getting this error:
[Info]: Creating Model: PepueModel
[Info]: Creating Model Class: Z_Psim_Ngc_Pep_Ue_Input
[Info]: Creating Model Class: Z_Psim_Ngc_Pep_Ue_Output
[Error]: RFC Import Failed. The import has been terminated.
[Fatal]: com.sap.mw.jco.JCO$Exception: The function module "DD_DOMA_GET" not released for 'remote' calls.
[Fatal]: com.sap.ide.metamodel.importers.rfcmodel.RFCImportFailedException: RFC Import failed. Cause: class com.sap.mw.jco.JCO$Exception:The function module "DD_DOMA_GET" not released for 'remote' calls.
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: The function module "DD_DOMA_GET" not released for 'remote' calls.
 at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeExecute(Native Method)
 at com.sap.mw.jco.rfc.MiddlewareRFC$Client.execute(MiddlewareRFC.java:1221)
 at com.sap.mw.jco.JCO$Client.execute(JCO.java:3691)
 at com.sap.mw.jco.JCO$Client.execute(JCO.java:3136)
 at com.sap.mdi.ddtypes.DDFactory.execute(DDFactory.java:173)
 at com.sap.mdi.ddtypes.DDFactory.execute(DDFactory.java:164)
 at com.sap.mdi.ddtypes.DDDomain.<init>(DDDomain.java:45)
 at com.sap.mdi.ddtypes.DDDataelement.<init>(DDDataelement.java:59)
 at com.sap.mdi.ddtypes.DDFactory.analyseJCOReturn(DDFactory.java:451)
 at com.sap.mdi.ddtypes.DDFactory.getDDObject(DDFactory.java:434)
 at com.sap.mdi.ddtypes.DDFactory.getDDObject(DDFactory.java:372)
 at com.sap.mdi.ddtypes.DDFactory.getDDObjectWithSubtree(DDFactory.java:262)
 at com.sap.mdi.RfmParameter.getDDObject(RfmParameter.java:602)
 at com.sap.dictionary.types.mdi2metamodel.R3ToMetamodelDictionaryConverterWithNestedStructures.getDdicObject(R3ToMetamodelDictionaryConverterWithNestedStructures.java:206)
 at com.sap.ide.metamodel.importers.rfcmodel.DynamicRFCModelImporter.ImportRFC(DynamicRFCModelImporter.java:341)
 at com.sap.ide.metamodel.importers.rfcmodel.DynamicRFCModelImporter.doImport(DynamicRFCModelImporter.java:196)
 at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelWizard$3.run(ModelWizard.java:706)
 at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
The tutorial:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/11/e2bc3d9ecc6b3be10000000a114084/frameset.htm">click here</a>
says "not-released function modules with a yellow icon."
My RFC (NOT BAPI MARKED AS RFC) is display with a yellow icon.
Searching the error "DD_DOMA_GET" not released for 'remote' calls I found the SAP note: 717836, it says The function module DD_DOMA_GET should be changed to remote-enabled. Where Should I find this function? I guess that is at the R3 System, what should I do to make it remote-enabled?. The other note I found was the SAP note 672745. But I really don't know it those notes apply to my problem.
What is the meaning of: not released? what should be done to make it RELEASE?.
Who made it told me that can't make me a BAPI to bring me the data, he only can do a RFC to get the list I need. The RFC (NOT BAPI MARKED AS RFC) was tranported and can be executed without any problem inside the R3 4.6
The RFC has a parameter, but I think that at import time it doesn't care.
Thanks for the time and interest on this thread.

Rodrigo:
The yellow or green icon it doesn't have to be if its a RFC or BAPI, it have to be with the release state of the function (BAPI or RFC, in this case seems to be the same).
This is the documentation abut it (it's at my original post too) see: http://help.sap.com/saphelp_nw04/helpdata/en/11/e2bc3d9ecc6b3be10000000a114084/frameset.htm
Hope it helps you

Simultaneous background jobs using the same BAPI issue

I scheduled 2 simultaneous background jobs on a custom program using the same BAPI (closing PM orders).
Run 1 to CLSD orders created on year 2001
Run 2 to CLSD orders created on year 2000
What happened was while run 1 was still active, run 2 encountered a dump and was cancelled.
Upon checking in ST22, dump was generated in CO_ZV_CONSISTENCY_CHECK.
Also, Run 2's dump happened when it encountered a data inconsistency for an order number being processed for Run 1.
Since the BAPI is being accessed at the same time by the two jobs, Is it possible that the commit work on run 1 could affect the processing for the Run 2, hence the data inconsistency?
Is this a buffer issue?
Additionally, no dump is encountered when Run 1 or Run 2 is run by itself.
I also encountered this issue before for creating Project and WBS using BAPI, but the solution we came up with was not to do parallel runs to avoid the error as this was a one time upload only.

If the second job is dependent on the 1st job, then use following logic which will let you know the status of 1st job. Once 1st job is completed, call JOB_OPEN of 2nd job.
ENDLESS loop till 1st job is completed
DO.
CALL FUNCTION 'BP_JOB_READ'
 EXPORTING
 job_read_jobcount = w_jobcount
 job_read_jobname = w_jobname
 job_read_opcode = '20'
 IMPORTING
 job_read_jobhead = wa_jobhead
 TABLES
 job_read_steplist = i_jobsteplist
 EXCEPTIONS
 invalid_opcode = 1
 job_doesnt_exist = 2
 job_doesnt_have_steps = 3
 OTHERS = 4.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
To Display the status text as per the status type
CASE wa_jobhead-status.
 WHEN 'S'. WRITE: / text-006. "'Scheduled'.
 WHEN 'R'. WRITE: / text-007. "'Released'.
 WHEN 'F'. WRITE: / text-008. "'Completed'.
 WHEN 'A'. WRITE: / text-009. "'Cancelled'.
 WHEN OTHERS.
ENDCASE.
IF wa_jobhead-status = 'F'.
exit.
ENDIF.
ENDDO.
PERFORM OPEN_2nd_JOb.

In LSMW using BAPI Scenario, how to assign the same file to HEADER and ITEM

Hi,
i got a problem when we are in ASSIGN FILES step how to assign the same file to both HEADER and ITEM Structures?

Hi,
When defining the file in specify files step check the option 'Data for Multiple Source Structures'.
Hope it helps.
Thanks,
Mahesh

Use same LUW / create session

Hi,
I would like to use the BAPI BAPI_BUS2172_CREATE to create a new cProjects Proj.definition. This BAPI requires the BAPI BAPI_CPROJECTS_COMMIT_WORK to be called afterwards in order to acutally create the database entries. Unfortunately it doesn't work because the second BAPI seems to be called from within a different LUW (Logical unit of work). Is there any way to call these two BAPIs "together" so that they use the same connection or LUW in the backendsystem?
Many thanks & regards,
Nils

Hello Nils,
I think it has something to do with the RFC itself. When you call a BAPI in VC then you get a session id, or something like that. When the BAPI ends the session becomes invalid and therefore the next BAPI becomes another session id.
But to be honest I don't understand that much about RFC, session ids etc...
So I use this workaround: it works fine: and ...
never change a running system!
Regards, Michael

BAPI's in the same LUW

Similar Messages

Maybe you are looking for