RFC Interface Generation

Under 4.6C, in SE37 you could generate RFC interface code (.c and .h files) for a function by going to the menu bar: Utilities / RFC Interface / Generate
Under 4.7, there is no RFC Interface option under Utilities. Any idea if this has been moved elsewhere, or if it is gone altogether?

Hi Lisa,
Look at oss note 551830. It tells you the replacement.

Similar Messages

Generating RFC Interface skeleton code

hi
In SAP R346C the menu for generating Rfc skelecton code was present in the utilities menu.
I am not able to locate it in sapr347. Can somebody point it to me.

Hi,
this is OSS-Nr. 551830:
Symptom
There is no code generator for RFC interfaces in transaction SE37, menu option Utilities -> RFC interface -> Generate.
Other terms
RFC stub, C programming
Reason and Prerequisites
Since functions were changed in the Web Application Server, the generation function is no longer provided.
Solution
Instead of directly using the RFC library, you can use the Java Connector (JCo) or the .NET Connector.
As of Version 6.20, you can also use our SOAP implementation for calls to SAP.
You can download both connectors from SAPnet. Here you will also find information on the release as well as use of SOAP implementation. This information is available on http://service.sap.com/connectors.
sorry ...
Viktor

EDI to RFC interface

Hi,
I'm about to implement Spec2000 to RFC interface. since XI does not support EDI (no EDI adaptors available) i'll have choose one out of two options:
1. manipulate EDI as it was regular text file.
2. use 3rd party tool as an adaptor.
i belies my first option is complicated and clearly has great risk, so i'm looking for as much leads as i can get.
Tnx in advance
Uri

>
uri karagila wrote:
> Hi,
>
> I'm about to implement Spec2000 to RFC interface. since XI does not support EDI (no EDI adaptors available) i'll have choose one out of two options:
>
> 1. manipulate EDI as it was regular text file.
> 2. use 3rd party tool as an adaptor.
>
> i belies my first option is complicated and clearly has great risk, so i'm looking for as much leads as i can get.
>
> Tnx in advance
>
> Uri
Option 1 - I guess that is not a good idea considering the complexity in EDI messages. But then it denpends how many interfaces you have. If there are very less say under 10 interfaces using the EDI spec. then it is still worth investing time and money on coming up with the manipulation but else.... its a night mare.
Option 2 - There are various third party adapter available ex. seeburger, iway etc which you can make use. Only thing is it comes with a cost but life becomes much easier.

NWDS import RFC interface for the structure issue??

Hi Gurus,
I'm working on the SAP NetWeaver BPM with NWDS 7.3 SP12 rite now and got confused about the RFC interface structure stuff.
I have a mapping activity defined in the process and the receiver interface needs a RFC. So I go to "Process Modeling" -> "Services Interfaces", right click and choose "Import RFC",type the correct RFC/BAPI name connecting with the SAP ECC system. The issue is that when I finished importing the RFC, went to the "Data Types", the RFC interface namespace shows out but the structure shows seperately with individual segment, so the whole nested RFC interface structure messed up in parallel which is incorrect for the data object and output mapping for later process activities.
Anyone has ran into such kind of issue or experience the same, any solution or suggestion?
Thanks in advance,
Rajesh

William,
Another two questions relates to NWDS BPM development:
1. Sometimes after I import the service interface into NWDS, the structure displays differently from it defines in ESR, I mean the fields sequence. I dont know why
2. Refer to your screenshot,
Assume the occurence of node HEADER and item is (0..1), when I want to map a blank constant to them to generate the target structure, the editor not allows and display error which is very different with ESR mapping tool, could you please help to advise? Tons of thanks!
Thanks a lot in advance,
Rajesh

Rfc interface generator

Hallo Gurus,
as far as you know is the "RFC Interface Generator" still active?
It should be under:
Tools --> ABAP Workbench ---> Development --> Function library
and then utilities -> RFC generate
I am working on a SAP ECC 6.0.
I need it to generate the code to call an RFC from an external program...
Thank you very much indeed!

se37 > <fm_name>
goto > furture options> generate RFC include
generate RFC/ update include

Performance Tuning in HTTP - RFC Interface

Hi,
I'm currently working on a HTTP --> RFC scenario and facing slow performance issues. When I test this interface with a transaction having 1 line item, the response from RFC is instantaneous. However, when there are about 400 line items, the average response time from RFC is about 8-9 seconds. When this interface goes live, there will be transactions with > 1000 line items. I'm really worried about the performance going down, as performance is a major criteria for deploying this interface.
Could you suggest any steps to improve the performance/reduce the response time?
Thanks,
Guru

Guru,
Disable all the Fields in the RFC which you are not using / populating.
One of my colleagues faced a similar problem and when they disabled the fields which were not being used when triggering the RFC call, the perfromance improved drastically.
Also, turn off logging of Synch Messages as this also can cause perfromance issues.
SXMB_ADM --> Integration Engine Configuration --> LOGGING_SYNC should be set to 0
Regards
Bhavesh

Virtual Interface generation bug in NetWeaver ?

I use the Web Service generation wizard to generate a virtual interface which exposes methods in an EJB. As one of the parameters I pass a simple java bean, lets say:
public class StatusCode
private String name;
private boolean buggy;
public String getName() {...}
public void setName(String newName){...}
public boolean isBuggy() {...}
public void setBuggy(boolean trueOrFalse){...}
When I look at the virtual interface generated, especially at the Types tab, my boolean attribute is not included.
If I change the getter to "getBuggy()", the attribute is included in the VI. The only problem is that the typical Java Bean framework, say from sun or ibm, always map 'boolean' getters to 'isSomething()' and not 'getSomething()'.
Is this a bug with NW? Is there a fix or workaround for this ?
My version of NW:
Version: 2.0.7
Build id: 200407270250
Thanks in advance,
Mark
I posted this question also in the NW development forum, but so far no replies.

I try to login by use:
username : Administrator
password : <master password> (at least 1 number)
I try to login many times but it always fails.
(I am very sure about my password since i also try to reinstall many times - 10th. both J2EE 1.4 and Java EE 5)
Ivaylo Ivanov, do you sure that you test with this new edition. (Not the previous edition)
I see the other persons get the result like me:
Telnet Administration
SAP J2EE Engine v7.100
User name: Administrator
Password:
The user account is either expired, or not valid yet.
Login failed. Reason: The user account is either expired, or not valid yet.
Connection to host lost.
if my login is not correct, it will tell the other messags.
Telnet Administration
SAP J2EE Engine v7.100
User name: f
Password:
Cannot authenticate the user.
Login failed. Reason: Cannot authenticate the user.

Virtual Interface generation bug with NetWeaver ?

I use the Web Service generation wizard to generate a virtual interface which exposes methods in an EJB. As one of the parameters I pass a simple java bean, lets say:
public class StatusCode
    private String name;
    private boolean buggy;
    public String getName() {...}
    public void setName(String newName){...}
    public boolean isBuggy() {...}
    public void setBuggy(boolean trueOrFalse){...}
When I look at the virtual interface generated, especially at the Types tab, my boolean attribute is not included.
If I change the getter to "getBuggy()", the attribute is included in the VI. The only problem is that the typical Java Bean framework, say from sun or ibm, always map 'boolean' getters to 'isSomething()' and not 'getSomething()'.
Is this a bug with NW? Is there a fix or workaround for this ?
My version of NW:
Version: 2.0.7
Build id: 200407270250
Thanks in advance,
Mark
(If this is not the right forum, could someone suggest where I can post this question?)

Hi. As of Netweaver 2004s, the virtual interface piece has be absorbed into the creation of the web service definition, so there is no need to create it as well.   When you are getting the 403, how are you trying to run this, using the Web Service Homepage? If so, you will need to configure what j2e engine that you want to use to use. You can do this in WSADMIN under the Administration settings.   Check that this is set. YOu must know the URL of your j2e engine.
Regards,
Rich Heilman

Proxy to FILE/RFC Interface

Hi Experts,
Recently your ECC is upgrade, My Scenario is PROXY - > PI -> FILE/RFC, There are 2 issues for the same interface.
Getting CCMS Alerts as below. When I check in SMQ2, i dont see any messages are stucked in the queue, but we are receiving this alerts frequently from after upgrade.
Issue 1:-
ALERT for MIP \ Transactional RFC and Queued RFC \ Int. Server Outbound Messages (XBQO*) \ Blocked queues: Client 001 at 20140801 101549 ( Time in UTC ) RED CCMS alert for monitored object Blocked queues: Client 001 Alert Text:Blocked inbound queue: Client 001 Q name XBQO0___XI_SERIALIZE0068 status RETRY dest CHGVA-SAP-MIP_MIP_14 System:MIP
Segment:SAP_CCMS_CHGVA-SAP-MIP_MIP_14
MTE:MIP\Transactional RFC and Queued RFC\Int. Server Outbound Messages (XBQO*)\Blocked queues: Client 001
Client:000
User:SAPSYS
Severity: 50
Issue 2:-
The messages is getting successful in message monitoring when going into details Audit log is showing the below error. Once is successfully delivered the message the message Id is trying to deliver the same message ID and getting the below error.
This is also comming after upgrade.
Putting message into receive queue failed, due to: com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID e4196a30-56ac-59f1-a2e0-0050569a0002(INBOUND) already exists in database: com.sap.sql.DuplicateKeyException: Violation of PRIMARY KEY constraint 'PK__XI_AF_MS__99C1915D08BFA0D4'. Cannot insert duplicate key in object 'SAPMIPDB.XI_AF_MSG'..
Can any one help me out from this both issues.
Thanks in Advance for your responces
G V Anil

Hi Sarojkanta,
Its a Production issue, The messages comming form ECC as a scheduled background job.
We upgraded our ECC system to 6.0 EHP6 from EHP5 and now all asynchronous. Sender PROXY Interfaces hits PI and go immediately into RETRY status and the messages are getting successful to teh receiver. but its trying second time with the same Message ID and then we are facing this issue as show in the above screen shot.
When checked in MONI for this interface all the messages are showing as below.
Call Adapter is getting failed and trying second time.
Thanks
G V Anil

HTTP to RFC Interface Determination problem

Hi experts,
I am doing HTTP <-> RFC scenario mentioned in blog
/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
almost everthing is done; but while configuring the interface determination, i am not able to see the inbound interface.
your valuable help would be appreciated
Regards
Sumit Bhutani

Hi Bhavesh,
Thanks for your quick response; this problem has been resolved, but while testing my scenario using RWB i am getting this error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to read payload from the message object</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Please suggest on this
Thanks
Sumit

RFC interface failed without mapping

HELLO ALL,
I was working on SOAP to RFC scenario having a simple message mapping in it. The interface was working perfectly fine.
Later on I got a requirement to remove the mapping from my interface.
I was able to run the interface after the changes but It doesnt return any value, which usually happens when we pass wrong parameters to the RFC for which RFC doesnt find any entry.
I tested the RFC with the same test data using se37 and it returned me the records.
Any clue, why the RFC doesnt understand the input values when we dont have a mapping ? Does the message mapping convert/format the input data ?
I will appreciate for your inputs.
Thanks to all.
PEERU

Thanks both, for your replies.
As per my understanding mapping is optional in XI.
I am using the RFC request and response structure for the SOAP end. I just created a message interface for the SOAP sender, based on the RFC request and response structures.
Correct me if in the case of RFC, SAP makes mapping a mandatory object. I dint find any document which says that mapping is always needed for RFC receiver interface.
Thank You.
PEERU

RFC Proxy generation - redistribution of runtime jars

Hello
I've generated java proxies for some RFC function modules with the help of the NetWeaver Developer Studio and they seem to work OK.
I used the following libraries for the generation:
From plugins\com.sap.ide.jcb.core\lib\
aii_proxy_rt.jar
aii_util_misc.jar
SAPmdi.jar
From plugins\com.sap.mw.jco\lib\
sapjco.jar
I know that redistribution of SAP JCO is forbidden.
What about the other jars? Is it permissible to redistribute them?
Are all the jars required for the generated proxy runtime?
Thanks
Dror

Hi chandu,
Try these links. This may help you.
http://help.sap.com/saphelp_nw04/helpdata/en/2b/f49b21674e8c44940bb3beafd83d5c/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/02/265c3cf311070ae10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/85/78af1bf407434796aaf8dbd6d4e7b7/content.htm
Thanks and Regards
Vishal Kumar

ALE interface generation from BAPI_POEC_CREATE

Hi,
I want to generate an ALE interface from BAPI_POEC_CREATE (object type BUS2201).
FUNCTION BAPI_POEC_CREATE.
*"*"Lokale Schnittstelle:
*" IMPORTING
*"     VALUE(I_PO_HEADER) LIKE BAPI_PO_HEADER_C STRUCTURE
*"        BAPI_PO_HEADER_C
*"     VALUE(I_PO_HEADER_CUST) LIKE BAPI_PO_HEADER_CUST_C STRUCTURE
*"        BAPI_PO_HEADER_CUST_C OPTIONAL
*"     VALUE(I_TESTRUN) TYPE BBPS_BAPI2091-TESTRUN DEFAULT SPACE
*" EXPORTING
*"     VALUE(E_PO_HEADER) TYPE BAPI_PO_HEADER_D
*"     VALUE(E_PO_HEADER_CUST) TYPE BAPI_PO_HEADER_CUST_D
*" TABLES
*"      I_PO_ITEMS STRUCTURE BAPI_PO_ITEM_C OPTIONAL
*"      I_PO_ITEMS_CUST STRUCTURE BAPI_PO_ITEM_CUST_C OPTIONAL
*"      I_PO_ACCASS STRUCTURE BAPI_ACC_C OPTIONAL
*"      I_PO_ACCASS_CUST STRUCTURE BAPI_ACC_CUST_C OPTIONAL
*"      I_PO_PARTNER STRUCTURE BAPI_BUP_C OPTIONAL
*"      I_PO_TEXT STRUCTURE BAPI_TEXT_I OPTIONAL
*"      I_PO_ATTACH STRUCTURE BAPI_ATT_C OPTIONAL
*"      I_PO_ORGDATA STRUCTURE BAPI_ORG_C OPTIONAL
*"      I_PO_LIMIT STRUCTURE BAPI_LIMIT_C OPTIONAL
*"      I_PO_SDLN STRUCTURE BAPI_SDLN_C OPTIONAL
*"      E_PO_ITEMS STRUCTURE BAPI_PO_ITEM_D OPTIONAL
*"      E_PO_ITEMS_CUST STRUCTURE BAPI_PO_ITEM_CUST_D OPTIONAL
*"      E_PO_ACCASS STRUCTURE BAPI_ACC_D OPTIONAL
*"      E_PO_ACCASS_CUST STRUCTURE BAPI_ACC_CUST_D OPTIONAL
*"      E_PO_PARTNER STRUCTURE BAPI_BUP_D OPTIONAL
*"      E_PO_ORGDATA STRUCTURE BAPI_ORG_D OPTIONAL
*"      E_PO_LIMIT STRUCTURE BAPI_LIMIT_D OPTIONAL
*"      E_PO_SDLN STRUCTURE BAPI_SDLN_D OPTIONAL
*"      E_PO_TEXT STRUCTURE BAPI_TEXT_I OPTIONAL
*"      E_PO_STATUS STRUCTURE BAPI_BBP_STATUS OPTIONAL
*"      E_PO_ATTACH STRUCTURE BAPI_ATT_D OPTIONAL
*"      RETURN STRUCTURE BAPIRET2 OPTIONAL
1) I encoutered a first problem : as you can see, these are two parameters with the same type BAPI_TEXT_I. So it gives an error message during generation in BDBG. I can bypass this error by deleting the second parameter (E_PO_TEXT) in debug. But I don't like this method of course...
2) I have a second problem : the three parameters I_PO_HEADER_CUST, I_PO_ITEMS_CUST, I_PO_ACCASS_CUST are not taken in account in the generated FM (ZIDOC_INPUT_ZPURCHASEORDEREC_C), even if corresponding EDI segments are generated. I needed to add them manually (at the end of the following code) :
FUNCTION zidoc_input_zpurchaseorderec_c.
*"*"Interface locale :
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWF_PARAM-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWF_PARAM-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
* this function module is generated                                   *
*          never change it manually, please!        10.06.2008         *
DATA:
      z1zpurchaseorderec_create LIKE z1zpurchaseorderec_create,
      z1bp_po_header_c LIKE z1bp_po_header_c,
      z1bp_po_item_c LIKE z1bp_po_item_c,
      z1bp_acc_c LIKE z1bp_acc_c,
      z1bp_bup_c LIKE z1bp_bup_c,
      z1bp_bup_c1 LIKE z1bp_bup_c1,
      z1bp_bup_c2 LIKE z1bp_bup_c2,
      z1bp_text_i LIKE z1bp_text_i,
      z1bp_att_c LIKE z1bp_att_c,
      z1bp_org_c LIKE z1bp_org_c,
      z1bp_limit_c LIKE z1bp_limit_c,
      z1bp_po_item_d LIKE z1bp_po_item_d,
      z1bp_po_item_d1 LIKE z1bp_po_item_d1,
      z1bp_acc_d LIKE z1bp_acc_d,
      z1bp_bup_d LIKE z1bp_bup_d,
      z1bp_bup_d1 LIKE z1bp_bup_d1,
      z1bp_bup_d2 LIKE z1bp_bup_d2,
      z1bp_org_d LIKE z1bp_org_d,
      z1bp_limit_d LIKE z1bp_limit_d,
      z1bp_bbp_status LIKE z1bp_bbp_status,
      z1bp_att_d LIKE z1bp_att_d,
* go through all IDocs                                                 *
LOOP AT idoc_contrl.
*   select segments belonging to one IDoc                              *
    REFRESH t_edidd.
    LOOP AT idoc_data WHERE docnum = idoc_contrl-docnum.
      APPEND idoc_data TO t_edidd.
    ENDLOOP.
*   through all segments of this IDoc                                  *
    CLEAR error_flag.
    REFRESH bapi_retn_info.
    CATCH SYSTEM-EXCEPTIONS conversion_errors = 1.
      LOOP AT t_edidd INTO idoc_data.
        CASE idoc_data-segnam.
          WHEN 'Z1ZPURCHASEORDEREC_CREATE'.
            z1zpurchaseorderec_create = idoc_data-sdata.
            MOVE z1zpurchaseorderec_create-i_testrun
              TO i_testrun.
          WHEN 'Z1BP_PO_HEADER_C'.
            z1bp_po_header_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_po_header_c
               TO i_po_header.                              "#EC ENHOK
            IF z1bp_po_header_c-doc_date
               IS INITIAL.
              CLEAR i_po_header-doc_date.
            ENDIF.
            IF z1bp_po_header_c-pcdat_to
               IS INITIAL.
              CLEAR i_po_header-pcdat_to.
            ENDIF.
            IF z1bp_po_header_c-vper_start
               IS INITIAL.
              CLEAR i_po_header-vper_start.
            ENDIF.
            IF z1bp_po_header_c-vper_end
               IS INITIAL.
              CLEAR i_po_header-vper_end.
            ENDIF.
          WHEN 'Z1BP_PO_ITEM_C'.
            z1bp_po_item_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_po_item_c
               TO i_po_items.                               "#EC ENHOK
            IF z1bp_po_item_c-deliv_date
               IS INITIAL.
              CLEAR i_po_items-deliv_date.
            ENDIF.
            APPEND i_po_items.
          WHEN 'Z1BP_ACC_C'.
            z1bp_acc_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_acc_c
               TO i_po_accass.                              "#EC ENHOK
            APPEND i_po_accass.
          WHEN 'Z1BP_BUP_C'.
            z1bp_bup_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bup_c
               TO i_po_partner.                             "#EC ENHOK
            READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
                         segnam = 'Z1BP_BUP_C1'.
            IF sy-subrc <> 0.
              APPEND i_po_partner.
            ENDIF.
          WHEN 'Z1BP_BUP_C1'.
            z1bp_bup_c1 = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bup_c1
               TO i_po_partner.                             "#EC ENHOK
            READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
                         segnam = 'Z1BP_BUP_C2'.
            IF sy-subrc <> 0.
              APPEND i_po_partner.
            ENDIF.
          WHEN 'Z1BP_BUP_C2'.
            z1bp_bup_c2 = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bup_c2
               TO i_po_partner.                             "#EC ENHOK
            APPEND i_po_partner.
          WHEN 'Z1BP_TEXT_I'.
            z1bp_text_i = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_text_i
               TO e_po_text.                                "#EC ENHOK
            APPEND e_po_text.
          WHEN 'Z1BP_ATT_C'.
            z1bp_att_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_att_c
               TO i_po_attach.                              "#EC ENHOK
            APPEND i_po_attach.
          WHEN 'Z1BP_ORG_C'.
            z1bp_org_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_org_c
               TO i_po_orgdata.                             "#EC ENHOK
            APPEND i_po_orgdata.
          WHEN 'Z1BP_LIMIT_C'.
            z1bp_limit_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_limit_c
               TO i_po_limit.                               "#EC ENHOK
            APPEND i_po_limit.
          WHEN 'Z1BP_PO_ITEM_D'.
            z1bp_po_item_d = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_po_item_d
               TO e_po_items.                               "#EC ENHOK
            IF z1bp_po_item_d-deliv_date
               IS INITIAL.
              CLEAR e_po_items-deliv_date.
            ENDIF.
            READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
                         segnam = 'Z1BP_PO_ITEM_D1'.
            IF sy-subrc <> 0.
              APPEND e_po_items.
            ENDIF.
          WHEN 'Z1BP_PO_ITEM_D1'.
            z1bp_po_item_d1 = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_po_item_d1
               TO e_po_items.                               "#EC ENHOK
            APPEND e_po_items.
          WHEN 'Z1BP_ACC_D'.
            z1bp_acc_d = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_acc_d
               TO e_po_accass.                              "#EC ENHOK
            APPEND e_po_accass.
          WHEN 'Z1BP_BUP_D'.
            z1bp_bup_d = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bup_d
               TO e_po_partner.                             "#EC ENHOK
            READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
                         segnam = 'Z1BP_BUP_D1'.
            IF sy-subrc <> 0.
              APPEND e_po_partner.
            ENDIF.
          WHEN 'Z1BP_BUP_D1'.
            z1bp_bup_d1 = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bup_d1
               TO e_po_partner.                             "#EC ENHOK
            READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
                         segnam = 'Z1BP_BUP_D2'.
            IF sy-subrc <> 0.
              APPEND e_po_partner.
            ENDIF.
          WHEN 'Z1BP_BUP_D2'.
            z1bp_bup_d2 = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bup_d2
               TO e_po_partner.                             "#EC ENHOK
            APPEND e_po_partner.
          WHEN 'Z1BP_ORG_D'.
            z1bp_org_d = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_org_d
               TO e_po_orgdata.                             "#EC ENHOK
            APPEND e_po_orgdata.
          WHEN 'Z1BP_LIMIT_D'.
            z1bp_limit_d = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_limit_d
               TO e_po_limit.                               "#EC ENHOK
            APPEND e_po_limit.
          WHEN 'Z1BP_BBP_STATUS'.
            z1bp_bbp_status = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bbp_status
               TO e_po_status.                              "#EC ENHOK
            APPEND e_po_status.
          WHEN 'Z1BP_ATT_D'.
            z1bp_att_d = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_att_d
               TO e_po_attach.                              "#EC ENHOK
            APPEND e_po_attach.
*** JSE 12/06/08 segments "forgotten" by BDBG
          WHEN 'Z1BP_PO_HEADER_CUST_C'.
            z1bp_po_header_cust_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_po_header_cust_c
              TO i_po_header_cust_c.
          WHEN 'Z1BP_PO_ITEM_CUST_C'.
            z1bp_po_item_cust_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_po_item_cust_c
               TO s_po_items_cust.                          "#EC ENHOK
            APPEND s_po_items_cust TO i_po_items_cust.
          WHEN 'Z1BP_ACC_CUST_C'.
            z1bp_acc_cust_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_acc_cust_c
               TO s_po_accass_cust.                         "#EC ENHOK
            APPEND s_po_accass_cust TO i_po_accass_cust.
*** JSE 12/06/08
        ENDCASE.
      ENDLOOP.
    ENDCATCH.
As for first point, I don't like this method, because it modifies a generated FM. Is there a way to force generation of this 3 parameters by BDBG ?
3) Considering the risk of overwriting modications in the generated FM, I have these questions : when are regenerated interfaces created by BDBG ? Are they regenerated always manually ? Or are they regenerated during transport for example ?
Thanks a lot for your help.
Julien.

Hi,
Pls see this very useful thread:
Re: 'BAPI_POEC_CREATE' function doesn't work with extended classic scenario
BR,
Disha.
Do reward points for useful answers.

Pro: SOAP to RFC, WSDL generation

Hi Frnd,
I am getting problem in the WSDL Generation from the ID,
When i generated it first time i was getting the following in the Soap:address
<soap:address location="http://vessxip01:8001/XISOAPAdapter/MessageServlet?channel=:BS_PWS:CC_PWS_WeighVoidData_SOAPsend&version=3.0;Sender.Service=BS_PWS;Interface=+urn%3Aveoliaes%3APWSTransaction%3ASAPR3toPWS%5EMIout_WeighVoidData" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
But When i am generation it again i am getting the following for the same tag, SOAP:Address
<soap:address location="http://vessxip01:8001/XISOAPAdapter/MessageServlet?channel:BS_PWS:CC_PWS_WeighVoidData_SOAPsend&version=3.0;Sender.Service=BS_PWS;Interface=urn%3Aveoliaes%3APWSTransaction%3ASAPR3toPWS%5EMIout_WeighVoidData" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
When we look concentrate i found " + " sign is missing in the next generation.
Please tell me what is the meaning of "+" sign, and why it is not comming in the regeneration of the WSDL.
Where as first one is working fine and the second one is not working.
Thanks,
Raj.

http://vessxip01:8001/XISOAPAdapter/MessageServlet?channel:BS_PWS:CC_PWS_WeighVoidData_SOAPsend&version=3.0;Sender.Service=BS_PWS;Interface=urn%3Aveoliaes%3APWSTransaction%3ASAPR3toPWS%5EMIout_WeighVoidData
The WSDL format that you are using is configured to hit the Integration Engine....hence the port number that you use should be that of the Integration Engine......
Now from where will i get this information:
1) Open SAP GUI --- tcode /nSXMB_ADM ---> Integration Engine Configuration ..... you will see the port here.... so if it is 8001 you need to use 8001 in the above URL.....
2) RWB --> Component Monitoring --> Integration Engine --> Test Message .....you can again see the port over here....
If i am not wrong 5XX00 is supposed to be used (mandatory) from PI7.1 onwards.....
Please tell me what is the meaning of "+" sign, and why it is not comming in the regeneration of the WSDL.
absolutely no idea :(.........but never saw a wsdl format with "+" sign in it.....
please correct me for any incorrect information given by me
Regards,
Abhishek.

Receiver RFC - Interface Objects

Hi every one,
I have a scenario, SOAP (SYNC)- XI - RFC (SYNC), MY question is do we need to create and interface objects for the receiver. Or can I use the RFC as the interface object.
Technical explanation would really help me.
Please clear.
Thanks,
-Naveen.

Hi Naveen,
<i>>>>>>do we need to create and interface objects for the receiver. Or can I use the RFC as the interface object.</i>
As RFC itself is a interface you need not create a seperate interface for an RFC.
In message mapping you will need to create two message mapping.
One SOAP_Req to RFC_Req
two RFC_Res to SOAP_Res.
When you will try to implement Interface Mapping, the source interface would be the imported 'External defination' of WSDL and the receiver would be the RFC. In the lower section of the same screen click 'Response' tab and add RFC_Res to SOAP_Res as mapping prog and under 'Request' tab add SOAP_Req to RFC_Req.
Let me know if you further assistance.
regards,
Ashish

RFC Interface Generation

Similar Messages

Maybe you are looking for