Logical port entry in SRT_CFG_DEF_ASGN table

Hello,
I am trying to consume a web service thru client proxy. After Service pack upgrade, the default logical port info though present, is not being passed on to the web service proxy.
In debug mode, I found that the table SRT_CFG_DEF_ASGN has no entries in the Quality system where testing is being done. How can I maintain the same?. Also, the program SRT_ADMIN_CHECK threw errors saying
bgRFC destination is not operational
bgRFC supervisor destination is not registered
Service destination in client XXX is not configured
Service destination in client 500 Unregistered etc.
Please help.
Thanks
Jay

Hi Jay,
You must configure the client :
- WAS6.40 7.0 SPS14 or higher via SOAMANAGER.
http://help.sap.com/saphelp_nw70/helpdata/en/47/3431de6c720aa7e10000000a114a6b/frameset.htm
- Lower than WAS6.40 7.0 SPS14 via LPCONFIG.
http://help.sap.com/saphelp_nw70/helpdata/en/47/3431de6c720aa7e10000000a114a6b/content.htm
Regards,
Eduardo.

Similar Messages

Preserving SOA Logical Ports and Trust Relationships during DB Refresh

Hi,
I have been searching for this for a while and have not had any luck so far. I thought maybe the vast experience in this community might be able to help me.
I am trying to preserve the SOA Logical Ports and the SMT1 Trust relationships of the target server during DB Refresh. Is there a list of tables that we could export (Much like exporting/transporting RFC Destination)?
Regards
Shantanu

Hi
Check the here under tables if they fits to your needs
Regards
SRT_LP                       Logical Ports
SRT_LP_FEAT            Logical Port Feature
SRT_LP_OP_FEAT     Logical Port Feature (Operation-Dependent)
SRT_LP_SXI_ADDR   Logical Ports: XI Addressing
RSECACTB                 Table for ABAP Access Authorization for Secure Memory
RSECTAB                    Secure Memory: Memory for Encrypted Data
RFCTRUST                 List of existing trusting systems
RFCSYSACL               List of permitted trusted systems for the current system

Logical system entry for table entry

Hi,
After system copy from one system name to another , I am facing some inconsistenices in various tables.
The table entry can be seen in se16.But when I try to select entries from the same table using SELECT statement, table are not getting populated.
I ran the BDLS also . How do I check the logical system entried for table where I have inconsistent entries?
Thanks,
Chitta

Hello Chitta,
But when I try to select entries from the same table using SELECT statement, table are not getting populated.
what are you trying to populate?
If your question is, its not showing anything... what error message you're getting? are you trying to run in the DB level?
If you're getting error, that this object doesn't exist in the database then you might not be logging with correct user. its an SAP table, then its owner is the SAP schema user. If you login with the schema user, it should show in a normal select statement. But if you login with <sid>adm then you have to give the correct schema id before tablename.
select * from <SchemaID>.<tablename>
SchemaID may be sapr3, sapsr3, or sap<SID> depending on your release.
Regards,
Debasis.

IDOC Error - Entry in outbound table not found - Status 37

Hello,
we try to generate the IDOC in a Test Tool WE19. I always get the same error "Entry in outbound table not found" - Status 37. I tried already many config changes (Partner, Ports, Distribution Modell...).
The thing is that the IDOC should be sent on external system (non-SAP System) but also the IDOC should be write to file. The external system should later on catch the IDOC and process the data.
I suppose the problem is the fact that we send it to external non-SAP System. I add as Port Data and the source where the IDOC shoud be generated. The Partner that I choose is logical system. However I dont specify the RFC Connection because the file should only be saved and not send directly on the external system. Is it possible or maybe I need to specify the IP-Adress of the external system?
When it works I need to generate the IDOC as service management IW32. I try it with TA IORD. I get the message "rejected". Probably because of the error in the test tool WE19.
I am already fighting on it for many hours...
Thank you in advance
Michael

Hi
In we 19
Receiver
Port: A port created in R/3 referencing RFC dest pointing to XI.
Partner no: LS of XI (CLNT100)
Partner Type: LS
Sender
Partner no: LS of R/3 (RD1CLNT500)
Partner Type: LS
Message Type is DESADV
Basic DELVRY05
and i am sending blank idoc for testing.
Regards
Monika

Logical port error when accessing e-recruiting web pages

Hi,
We are trying to set up our e-recruiting 3.0 and web dispatcher systems. We were receiving an error in our e-recruiting system in transaction SM20 that states Logon Failed (Reason=34, Type=H). The user is SAPSYS for client 000. The system was attempting to log on to our web dispatcher system. SAP suggested creating an entry in SM30, table VUSREXTID, mapping the External ID to our web dispatcher system. This entry helped in that we are not receiving the above error message anymore. However, when we attempt to access the web pages we are receiving the error Name of logical port &lp_name& is invalid. Prior to adding this entry we were able to access the logon page by entering the following url using an external alias (ex. https://recruiting.mphi.org/internal). Recruiting.mphi.org is our web dispatcher system. We do not want our e-recruiting system to be accessible from the outside. We want everything to go through our web dispatcher. Has anyone had a similar issue setting these up?
Thanks!
Heather

Hello Heather,
I am no specialist in network infrastructure but i remember a customer setting up a web dispüatcher szenario. I also encountered this &lp_name& error from time to time during my work.
The error points towards damaged urls and the customer also encountered such problems when setting up the web dispatcher landscape. Sometimes the last parameter of the URL was ignored or lost. Sometimes the web dispatcher transformed the URL including the parameters. But as parameters are case sensitive transforming them to upper/lower result in errors as the system no longer recognizes them.
Perhaps you can check the URL with which the web dispatcher is calling the sap server to find out if it does any funny things w/ the links.
Best Regards
Roman Weise

Calling external Web Service: PI is looking for a logical port and proxy.

Hi,
My scenario is ECC Proxy -> PI -> External Webservice (WS adapter).
the Web service adapter fails with the error message:
<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">WS_ADAPTER_SYS_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>System error while calling Web service adapter: Error when initializing SOAP client application: 'error_text'</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
When I debug the message processing, it is looking for a port in table SSRVRTCONFIG, finds it(entry created automatically when WS adapter and the corresponding receiver agreement is activated in ID.
Then the program looks for an entry in "SRT_CFG_CLI_ASGN" for a proxy and logical port combination and errors out.
to be able to call an external web service, do we need a proxy to be created? I tried to create but the proxy creation fails because the external WSDL has some unsupported tags.
Also do we need to do any other configuration in SOAMANAGER? I am assuming not because the Web service is external.
Any help would be appreciated.
Thanks
Vijay

I already checked that note and made sure that the points mentioned are met. I have a trace set up on the target system and would know if the call reaches them and then fails in authorization. Right now the call doesnt even reach the target system and also from debugging I know that the program is looking for a proxy and then fails.

Error while creating logical port for Reporting

Hi,
In one of the training materials for Duet Enterprise, i saw the steps for creating logical port for the consumer proxy /IWTNG/CO_PXY_RECORDS_REPOSITO.
When i am trying to create the logical port, i am getting an error saying,
" SRT Framework exception: Error in WSDL access: Exception occurred in communication framework:Error in HTTP Framework:500 Native SSL error
https://<server:port>/_vti_bin/OBAFileReceiver.asmx?wsdl "
I would like to know is it really necessary to create this logical port for "Reporting Scenario" and is it not created automaticallly using the Installation Wizard??
And in case it has to be created, how to resolve this SRT framework exception?
~ Ramanath.

Hi,
the consumer proxy /IWTNG/CO_PXY_RECORDS_REPOSITO was used in Duet Enterprise SP01. Now with SP02 the consume proxy /IWTNG/CO_OBAFILE_RECEIVER_SOA is created.
However, the SSL error that you are getting looks a little strange (it does not mean that there is an error, but it is worth checking):
So can you go to SOAMANAGER -> Service Administration -> Single Service Configuration. In here select "Consumer Proxy" from the "Search by", Search Pattern "/IWTNG/CO_OBAFILE_RECEIVER_SOA" and Field: Both.
You should find one entry. Select it and click "Apply Selection".
Now go to the Configurations tab. Here you should see one Logical Port with name "LOGICALPORTFORREPORTING" with Creation Type "Manually Created". In fact this logical port was created by the Wizard.
Click on Display and scroll down again. Now in the "Additional Information" tab there is a string after HTTP Destination, e.g. 0050568E3F5A1ED096F22339C44BAF83.
Copy this value and go to your SAP GUI -> Transaction SM59.
Here click on Find/Search and search for this HTTP Destination. You should find one Type G RFC Destination that has the target host of your SharePoint server and the path prefix /_vti_bin/OBAFileReceiver.asmx.
Now you can test the service. Just click on Connection Test. The result should be a HTTP Response: 200.
If not, then something went wrong with the automatic configuration and we should take another look at it (for example maybe the SSL certificate from SharePoint that was imported by the Wizard is not valid)
Regards,
Holger.
PS. Don't use the "Ping Web Service" test from SOAMANGER -- unfortunately this is not working consistently.

Logical system not defined in table SMOF_ERPSH!

Hello,
In the inbound queue of CRM, the queues are in 'SYSFAIL' status. The error message is ' logical system not defined in table SMOF_ERPSH!' .
the table has an entry for relevant ERP system.
I dont know where else to check.
I have checked the logical destinations on CRM and it is defined correctly.
can anyone help me here.
Regards,
Pratima

Hi Pratima,
I am also facing the same issue. I checked all the entries and Entries are there in the respective tables but still the same issue.
But if I delete the queue, the changes are replicated for that time but after some time again the queues are getting blocked with the same issue.
Pratima, can you please tell you whether your issue got fixed on this.
Thanks,
Sharath.

Logical port for client proxy

Hi,
when consuming a webservice i have to create a logical port and this port will be used when i create an instance of the proxy class e.g.
DATA: lo_proxy TYPE REF TO /ipro/co_bbp_cms_ibf_metadata.
CREATE OBJECT lo_proxy EXPORTING logical_port_name = 'E6S_300'.
The question is how could i know how the customer will name the logical port?
Is there a way to get a list of logial ports for a give proxy class?
Regards,
Christoph

the following table holds all the logical port for a given proxy class
SRT_LP
Regards
Raja

Read logical port for the proxy

HI ,
There is method or FM that can bring all the logical port that available for proxy class,
logical port that defined on SOAMANAGER or LPCONFIG .
Regards
Joy

Try this way
    call function 'RFC_READ_TABLE'
         destination                rfc_sys
         exporting
              query_table          = 'SRT_LP' " Table for Logical Ports
         tables
              options              = options1
              fields               = nametab1
              data                 = i_srt_lp[]. " Output table contains call values for proxy class after fm call
a®

Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING

hello colleagues,
In the phase Connect Diagnostics dont show the Agent available in SLD, but when go to SLD i have the agents,
Error,
Connect Diagnostics Agent
The table does not contain any data
Agent availables in all SLD
SOAP:1.007 SRT: Unupported xstream found: ("HTTP Code 401 : Unauthorized")
Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING
Thanks

OK, then pls follow below steps;
- Go to step 'Create Users' in solman_setup System Preparation scenario and make sure the user SM_INTERN_WS has a green status. Use the 'Test Login' button to make sure the user is not locked and has correct credentials maintained in solman_setup
- Immediately after checking the user status, navigate to Configure Connectivity->Enable Web Services and execute again the 'Create Logical Ports' automatic activity, in order to propagate the correct credentials to the Logical Port definitions.
- If the above operation is not successful, repeat the two steps above, providing a different user Id in 'Create Users' step, eg SM_INTERN_W1. This will prevent situations where the user gets locked by Logical Ports using an obsolete password.
Let me know the results.
Regards,
Vivek

Getting idoc error - Entry in outbound table not found- in outbound scenari

hi,
while generating idoc for outbound idoc to file scenario - i am getting error
"Entry in outbound table not found" (29 - error in ALE service)
Diagnosis
No partner profile (outbound parameter) could be found using the following key:
/C100/KU//WP_EAN////
This refers to the key fields in table EDP13:
RCVPRN Partner number
RCVPRT Partner type
RCVPFC Partner function
MESTYP Logical message
MESTYP Message code
but already entry has been maintained in partner profiles for the corresponding message.
same setup is working for other message types. pls let me know what might be the problem

Hi,
Check whether partner name is correct or not in WE20/outbound parameters undoer Logical System.
Regards,
Sreenivas.

Short dumop in J2I5 (provide duplicate entry in Standard table)

Hello Expert ,
                          We have a problem in T.Code J2I5 ( Excise Register Extraction) input entry is lelect Excise group 20 . and a date   from 04.08.09 onwards. and select the register RG23D . it shows the run time error ( Eg The ABAP/4 Open SQL array insert results in duplicate database record ) . but in the standard Tcode is there possible to provide duplicate entry in Standard table
Thaks & regards
Aditya Kr Tripathi

Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB
Date and Time          29.01.2010 10:57:09
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
problem occurs in this code :
   assign I_RG23D_TAB-I_RG23D_TYP to <x_rg23dtyp> casting.
   <x_extrctdata> = <x_rg23dtyp>.
    class CL_ABAP_CONTAINER_UTILITIES definition load.
    call method CL_ABAP_CONTAINER_UTILITIES=>FILL_CONTAINER_C
      EXPORTING
        IM_VALUE               = i_rg23d_tab-i_rg23d_typ
      IMPORTING
        EX_CONTAINER           = i_report_tab-extrctdata
      EXCEPTIONS
        ILLEGAL_PARAMETER_TYPE = 1
        others                 = 2.
   I_REPORT_TAB-EXTRCTDATA = I_RG23D_TAB-I_RG23D_TYP.
    COMPUTE I_REPORT_TAB-EXTRCTLNGT = STRLEN( I_REPORT_TAB-EXTRCTDATA ).
    APPEND I_REPORT_TAB.
ENDLOOP.
IF M_EXTRACTED = 'X'.
    LOOP AT I_RG23D_KEY.
      DELETE
      FROM J_2IEXTRCT
      WHERE BUDAT    = I_RG23D_KEY-BUDAT
      AND   SERIALNO = I_RG23D_KEY-SERIALNO
      AND   REGISTER = I_RG23D_KEY-REGISTER
      AND   EXGRP    = I_RG23D_KEY-EXGRP.
    ENDLOOP.
ENDIF.
Control table check here for data Extraction
INSERT J_2IEXTRCT FROM TABLE I_REPORT_TAB.
If the insertion of the extract table is successfull then the table
for Extraction is Inserted
IF SY-SUBRC EQ 0.
    PERFORM FILL_EXTDT USING C_RG23D M_EXTRACTED.
ENDIF.
ENDFORM.                                                    " RG23D
*&      Form RG23CPART1
Purpose : RG23C Part I extraction logic
FORM RG23CPART1.
DATA: $PART1      TYPE PART1_TYP,
        $LINCNT     LIKE SY-LINCT,
        M_EXTRACTED VALUE '',
        $RC         LIKE SY-SUBRC.
*********************************************************************************************8

Entry in outbound table not found

i am using we19 trying to do standard outbound processing for idoc mbgmcr02
i use receiver Port internal and partner abc01
         sender Port -
and partner abc02
in we20 is set up partner
abc01   type ls   in outbound parameter area i see mbgmcr
now in 19 when is use as receiver partner abc01 i get the following error
entry in outbound table not found
/abc01/ls//mbgmcr   message no 400   id E0
can anyone direct me to what i am doing wrong?????????????????/

Hi Janice,
See these..
http://help.sap.com/saphelp_erp2005vp/helpdata/en/71/9bbdde2f66454bb9771170369bae81/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/2d/f371e4d24a11d289810000e8216438/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b80c243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/f0/08ef0d06b111d286e2080009b98822/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
cheers,
Prashanth

Entry in outbound table not found E0 400

Hi all,
    Can anyone please help me with the below error which i am facing in ALE IDOCS.
status 29: Entry in outbound table not found E0 400
I am unable to see my port name in the created IDOC and the basic type is incorrectly called.
may I know what settings need to be verified.
Thanks in advance.

SAP checks the IDoc control record for outbound IDoc against EDP13 (outbound partner profile table). EDP13 is updated when you create outbound partner profile parameter in WE20
Check if you have created the partner profile outbound parameter in WE20 correctly to match your outbound IDoc control record.
SAP checks partner number, port, partner function of the receiver along with message type, message code and message function. They all should match between WE20 outbound partner profile parameter for your message type and the IDoc control record (EDIDC) segment.
This is the SAP code that throws the error message you mentioned
read table q_edidc index 1.
select single * from edp13
                  where rcvprn eq q_edidc-rcvprn
                  and   rcvprt eq q_edidc-rcvprt
                  and   rcvpfc eq q_edidc-rcvpfc
                  and   mestyp eq q_edidc-mestyp
                  and   mescod eq q_edidc-mescod
                  and   mesfct eq q_edidc-mesfct
                  and   test   eq q_edidc-test.
if sy-subrc ne 0.
    concatenate q_edidc-rcvprn '/' q_edidc-rcvprt '/' q_edidc-rcvpfc '/'
                q_edidc-mestyp '/' q_edidc-mescod '/' q_edidc-mesfct '/'
                q_edidc-test into text.
    condense text no-gaps.
    message a400(E0) with text(50).
endif.

Logical port entry in SRT_CFG_DEF_ASGN table

Similar Messages

Maybe you are looking for