Logical port could not be determined

I try to send a WS RM Message from XI server to ABAP system. I get error :" Error while determining the logical port"
Please suggest where is entry for logical port?

create an entry for logical port in tcode IDX1
Reward points, if helpful,
Sandeep Kaushik

Similar Messages

Customer/vendor could not be determined for intermediate document

does any one know how to solve this problem, i got this error for an inbound idoc 820 (remmitance advice).

Hi rob,
Message no. FD017
This is the following message:
Customer/vendor could not be determined for intermediate document 0000000000047039
Message no. FD017
Diagnosis
Several procedures are defined for determining the partner (customer or vendor):
1. The customer/vendor can send his/her account number (the account
   number in our system) in the address segment.
2. The customer/vendor can send his/her account number (our number at
   the customer or vendor) in the address segment.
3. Only the name in the address segment clearly identifies the
   customer/vendor. In this case you can create an allocation within
   intermediate document customizing (IDoc base -> Control -> Forward
   inbound).
4. The customer/vendor is determined using his/her bank details (only
   for the "INVOIC01" intermediate document type).
5. The customer/vendor is taken from the control record of the
   intermediate document.
For 1.-3.: One of the address segments with the partner functions
           "II", "RS", "SU", 'SE' ("INV_ID01"), or "RS" or
           "LF" ("INVOIC01") is used for determining the
           customer/vendor.
Procedure
Create the customer or vendor within Financial Accounting or maintain his/her bank details.
Create customer         - Proceed
Customer bank details   - Proceed
Create vendor           - Proceed
Vendor bank details     - Proceed
If the customer/vendor can only be determined using his/her name, create a record within intermediate document customizing with
logical address = name, application = "FI" or "MM" and physical target in the SAP system = customer number/vendor number.
Proceed

IDoc type could not be determined for the IDoc in F110

Dear All,
The below mentioned error is encountered by us in F110.We have check all the setiing and not able to find the solution for this error.
Now our heads has gone for a toss....can anyone kindly suggest what and where we have missed out.
The system is not creating the IDOC file.....
IDoc type could not be determined for the IDoc
Message no. B1090
Diagnosis
The IDoc passed to the ALE layer could not be processed. The specifications passed in the control record were not correct.
The basic IDoc type (field EDIDC-IDOCTP on the outbound side or EDI_DC-IDOCTYP on the inbound side)has not been specified for this IDoc.
The attempt to read the basic IDoc type from table EDIDO also failed. No table entry was found for IDoc type from field DOCTYP.
Procedure
Possible error sources:
- The calling program did not provide values for the fields specified above correctly. Make a note of the transaction in which this error occurred and consult your ALE administrator.
- The IDoc type is not known in your system and must be maintained.
Kindly do the needful.
Regards

If you want to create IDocs from the proposal run, outbound parameters (we20) with the 'Test' flag are required in addition.
see OSS note 504230 : Message EUPEXR forms the logical unit around the individual payment messages (PAYEXT IDocs). The E1IDRD1 segments contain the IDoc numbers of the payment messages in field DOCNUM. Segment E1IDRS1 contains check sums (total of all amounts, account numbers, bank numbers, number of payment messages). This information is provided for the EDI subsystem. Set up EUPEXR In Transaction WE20 for the partner profile for the house bank, create the outbound parameters for message type EUPEXR with IDoc type IDCREF01. If you want to create IDocs from the proposal run, outbound parameters with the 'Test' flag are required in addition.

Business Place for document could not be determined

Hi,
When I am posting Remittance challan I am getting this following error,
"Business Place for document could not be determined".
Could any body please help me to solve this problem.
I maintained the following settings in system
1. T-Code: J_1IEWTNUMGR
UN04 SC04 194C 02
2. T-Code: J_1IEWTNUM
02 02
3. T-Code: J_1IEWTNO
Maintained Number ranges
I posted vendor document and I gave Business place and Section code also. Even After all the settings I am getting this problem. Please let me know is there any steps I missed are any thing I have to maintain in system.
Best Regards
Raj

Hi Pavan,
Thanks for you replay. I checked in table, data available in the table J_1IEWTNUMGR against Company code, Business place and Off Key.
One more question is whether we need to give Business place or Section code while creating TDS challan using J1INCHLN. It will appear like "Business Place/Section Code" in the screen. If I select from drop down It is taking Section code. Is it possible to change the logic from Section code to Business place.
Thanks & Regards
Raju.

Additional account assignments could not be determined in inbound idoc

Hi Gurus,
Iam getting the error for inter company billiing idoc .
Direction         2     Inbox
Current status    51 --> Application document not posted
Basic type        INVOIC01
Extension         ZINVOIC2
Message type      INVOIC
Partner No.       I0107IC
Partn.Type        LI
Port              P12INTERCP
Error is : Item: 002 - additional account assignments could not be determined
                Message no. FD171
Please let me know where we can assign the additional account assignment for intercompany billing .
Thanks in advance
RameshG

Check Note 137686 - ALE_INVOIC01: Internal allocatn Customizing in FI
thanks
G. Lakshmipathi

Exchange 2010 - The certificate status could not be determined because the revocation check failed.

I have tried everything I have found online to get my DigiCert to work.
I have exported the cert and imported it into my child domains and they look perfect.
It is just my parent domain having issues.
netsh winhttp show proxy
does show my correct proxy server for http and https and port 8080
I have tried name, FQDN and IP address.
In the Bypass-list I have tried none, *.domain.com, and a list of all domains and child domains in my forest.
I have flushed the cache
certutil -urlcache crl delete
certutil -urlcache ocsp delete
and rebooted the Exchange 2010 (Windows 2008 R2) server
No matter what, I still see in my Server Configuration for the parent domain's DigiCert cert the message
The certificate status could not be determined because the revocation check failed.
with a red X on the left hand icon. Again, Child domains all say "The certificate is valid for Exchange Server usage."
Note: In spite of having the red X, I was able to assign via EMS the services.
Webmail works fine. Outlook Anywhere fails... I suspect it is due to my red X problem.
Suggestions?
Thanks in Advance
Jim.
Jim.

I have contacted DigiCert and they said the cert is working per their utility, hence the problem is outside the scope of their support.
I have followed, several times, http://support.microsoft.com/kb/979694
http://www.digicert.com/help/ reports all is well.
The DigiCertUtil.exe reports all is well and happy.
I have run
netsh winhttp set proxy proxy-server="http=myproxy:8080;https=myproxy:8080" bypass-list="*.mydomain.com"
Current WinHTTP proxy settings:
Proxy Server(s) : http=myproxy:8080;https=myproxy:8080
Bypass List : *.mydomain.com
I have flushed the cache using the commands
certutil -urlcache crl delete
certutil -urlcache ocsp delete
I still see in my Server Configuration for the parent domain's DigiCert cert the message
"The certificate status could not be determined because the revocation check failed."
with a red X on the left hand certificate icon.
To verify the cert via command line:
certutil -verify -urlfetch c:\mail_domain_com.cer
LoadCert(Cert) returned ASN1 bad tag value met. 0x8009310b (ASN: 267)
CertUtil: -verify command FAILED: 0x8009310b (ASN: 267)
CertUtil: ASN1 bad tag value met.
I suspect this is why I cannot get Outlook Anywhere to connect.
Child domains show a happy certificate icon. Parent domain does not.
Still scratching my head.
Thanks all!
Jim.

Port could not be created in SAP r/3

HI sap gurus...
 I am trying to do this scenario..IDOC-XI-JDBC In this ....from SAP R/3
SAP R3 SAP NW XI
1. Define Logical system - BD54 1. Define Logical system - BD54
MATLO
GR3 MATLOGR3
MATLOGXI
MATLOGXI
2. Assign logical System to Client 2. Assign logical System to Client - SCC4
Here assign both the logical system Here assign both the logical system
are assigned to client 800 are assigned to client 100
MATLOGR3 MATLOGR3
MATLOGXI MATLOGXI
3. Create RFC destination of type 3 for SAP XI system using transaction SM59:
RFC Destination : MATLOGXI RFC Destination : MATLOGR3
Connection Type : 3 Connection Type : 3
Target Host : ECCSERVER Target Host : ECCSERVER
System Number :01 System Number : 00

up to this successful...
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
|
.-> "ALE configuration for pushing idocs from SAP to XI"
I am following this blog....
here while creating the partner profile .. i am getting an error
like this
under port tabular column
i am getting an error that
Log for Partner Profile Generation
Partner
System MATLOGR3 System MATLOGR3 as a partner type already exists
System MATLOGXI System MATLOGXI as a partner type already exists
Port
System MATLOGR3 Port could not be created
RFC destination MATLOGR3 not specified for system MATLOGR3
 Enter the RFC destination and restart the generation 
Inb. Parameters
System MATLOGR3 Inbound parameters for message type MATMAS already exist

Hi
1. Go through these documents for the settings that need to be done.
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.do
2. Check out whether you assigned logical systems to your clients.Next check the ports(for inbound and outbound) also in we20.And also go through the link below.
http://www.sappoint.com/abap/ale.pdf
3. Might be you have not created the RFC destination from your target system.
say for eg if u have two systems sys1 and sys2.
you need to create RFC destination for sys2 from sys1 and viceversa before generating Partner Profile

Shopping cart error--Tax code could not be determined

We are using classic extended scenario.
When i am trying to create a shopping cart i am getting two error messages " tax code could not be determined" and Not possible to calculate tax.
have checked in the SPRO in EBP System->
Tax calculation->Determine system for tax calculation which is set to R/3.
SPRO->Tax calculation->Enter tax code -V0 -zero rate
 V1-VAT 17.5
 V3-Non recoverable.
SPRO->Determine tax code for country/product category->Domestic -GB -P146-V0
SPRO->Determine tax code for country/product category->International -GB -P146-V1.
I have checked the transaction FXTP in R/3-
Procedure attache to this is TAXGB.
Could you please suggest me how to eliminate the error.
Points will be rewarded.
Edited by: imam uddin on Jul 18, 2008 2:48 PM

Hi
It's recommended to have the same Tax related configuration data replicated in SRM system from R/3 as well.
I don't recommeded you to go with Hard-coding of tax codes.
We have faced similar issues with Delivery address and we have to solve it using our custom logic inside the BBP_DOC_CHANGE_BADI and BBP_CREATE_PO_BACK BADIs.
Anyways, send the detailed business requirements to my mail which are already having with you. )
I will definitely help you out.
Please refer to following threads as well.
sales tax gurus
How to display country related tax codes in SRM
e-Invoice tax calculation.
Tax code T1 does not exist for jurisdiction code error in shopping basket
Drill down facility not working for Tax codes ....Urgent!!!!!
Tax Issue
Tax Calculation
Tax setting in Extended Classic Scenario
Withholding Tax in SRM5.0
IDOCS for Tax Information
Taxes in Bid Invitation
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

10.5 server: could not reliably determine the server´s fully qualified doma

I bought mac 10.5 server unlimited clientes, yesterday I tried to install the software 3 times and never worked (from basic to advanced apple preconfigurations). I had the carrier support yesterday to verify that it is not a problem of the link.
the server has static IP, manually asigned.
server admin: computer name www.MMM.com, local hostname: www, network interface: ethernet (0), ipv4, add 201.122.etc.etc) dns name: dsl-201-122-63.etc !here LEOPARD is taking the address from the DSLÑ provider,!!!!! and I dont know how to change, but the address is entered manually in the network preferences!!!!!.
I go to admin server: server name: www.MMM.com, services: DNS and WEB : ON
DNS: Zones; www.MMM.com, type: primary
Homepage: Service: www.MMM:com:80
(also, I tri8ed with A redord www, type machine, value: 201.122.etc.etc)
WEB: enabled domain name www.MMM.com address (any or 201.122.etc.etc), port 80,webserver
alias: MMM.com, web services enabled: all.
also enabled default address any, port 80
stop, and start web service.
error log:
httpd: aprsockaddr_infoget() failed afor www.MMM.com
httpd: could not reliably determine the server´s fully qualified domain name, using 127.0.0.1 for server name..
any idea about how to correct that? I tried also the new installation, formating the disk, and the server software is not configurating the server correctly)the easy and advances installation are not working correctly).
thanks a lot
Alberto

ok,
I formated the MAC server for 4th time, installed again the server software, then I went for the Basic configuration. then entered the adress manually, then you have to delete the DNS entry (set it in blank), then in the next window enter the NS (which is the server name). then continue the installation.
after starting the web service is running and it is resolving address.then you can upgrade to the advanced configuration and install the other services.
in that order the www is resolving the address.

Port could not be created

Hi gurus,
While creating ALE partner profiles from R/3 , I am getting the following error.
Port could not be created
RFC destination SRMCLNT100 not specified for system SRMCLNT100
Enter the RFC destination and restart the generation
I have created the RFC destination from R/3 as wellas from SRMclinet 100 and could be able to remote logon to the respective systems. I am able to create partner profiles from SRMclient 100 but I could not do it from R/3.
Pl give your advice.
SS

Hello,
We defining ALE Distribution models, we add message types between 2 logical systems.
When generating the partner profile from this view, the system tries to use an RFC destination with exactly the same name as the logical system.
In your case, it does not find the RFC destination SRMCLNT100 in R/3.
A workaround is to maintain the partner profiles manually :
WE20 to maintain partner profile
WE21 to maintain ports
Rgds
Christophe

ALE-Port could not be created

HI,
Could someone tell me why and how to fix my issue,
when i generating partner profile (ALE process) there is a error :
"Port could not be created
RFC destination D010500 not specified for system D010500
Enter the RFC destination and restart the generation "
Thanks & Regards,
Saiful arif

Hi
Follow the given sequence for ALE settings :
Steps to be done:
Steps for XI
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the R3 system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto IDX1.
Create a new port.
Give the port name.
Give the client number for the R3 system.
Select the created Rfc Destination.
Step 3)
Goto IDX2
Create a new Meta data.
Give the Idoc type.
Select the created port.
Steps for R3.
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the XI system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto WE21.
Create a port under transactional RFC.(R3->XI)
Designate the RFC destination created in prev step.
Step 3)
Goto SALE.
Basic settings->Logical Systems->Define logical system.
Create two logical systems(one for XI and the other for R3)
Basic settings->Logical Systems->Assign logical system.
Assign the R3 logical system to respective client.
Step 4)
Goto WE20.
Partner type LS.
Create two partner profile(one for XI the other for R3).
Give the outbound or inbound message type based on the direction..
hope this helps you out :
Regard's
Chetan Ahuja

Getting an error "Customer could not be determined" for IDOCs in SCM 7.0

Hi Friends,
I am executing the report RSMIPROACT in ECC 6.0 system to publish Demand and Stocks into the SCM 7.0 system.
The IDOC is processed without any errors in ECC 6.0 . However, in the SCM 7.0 system , the IDOC fails with the error.
I have noticed that 2 things .
1. E1ADRE1 field is NOT being sent by the ECC system .
2. I get the same error even if I manually add this field and add value 300 or 301 for the qualifier field.
Has anybody faced this problem before ?
I look forward to replies.
Detailed error is given below.
Regards,
Ranjini.
Customer could not be determined
Message no. /SAPAPO/EDI010
Diagnosis
The system must determine the customer number from the IDoc data in order to update stock and sales figures for customers. It uses the additional section E1ADRE1 with the qualifier '300' or '301' in the vendor address section to do this. The customer number stored here should have a valid customer number in the APO System.
The section was not available in the processed IDoc.
System Response
The system cancels processing.
Procedure
Configure the EDI convertor in such a way that the corresponding section has a value.

Hi Ranjini,
Please look into the following
1) Customer master data is fully maintained
2) Customer number ranges are fully defined in customisation
3) Customer address details are maintained
4) Is there any special characters used while defining customer data or customer
number like $, #,[ etc.,?
5) Customer int models are active in SCM side prior to IDOC processing (including
customer, demand, stocks etc)
Please confirm your findings
Regards
R. Senthil Mareeswaran.

Error "codepage could not be determined for the receiver-system"

Hi,
we use the idoc-adapter to send message from mySAP ERP to PI.
All worked fine.
So, this morning I have changed the datatype of the messageId from "char" to "int" in mySAP ERP in the customizing menue (install param). So, no message received in SAP PI.
When I start transction "we05" in mySAPERP" I get the following error:
"codepage could not be determined for the receiver-system" status 02.
I have changed the datatyp to "char" but the same probleme
Can anybody help me please?
Regards
Stefan

This error shouldn't occur unless there is some modification at the OS level codepages.
Please check the entried in the RFC destination for connecting to the XI system. Unicode settings.
Regards,
Prateek

Error message while CREATING PO - PGrp could not be determined

Hi all,,.
We are on SRm 7. ECS.
The issue we are facing is:
WHen I click on CREATE PURCAHSE ORDER trasnaction,I get this message "Purcahsing group could not be determined;Inform system administrator".
Edited by: nmsrm1234 on Nov 10, 2011 2:09 AM

Hello,
The error is coming because to create PO directly you have to be a Purchaser,you need to belong to a purchasing group in SRM.In PPOMA_BBP Assign your user id below a purchasing group directly or right click the present position and go to 'Assignment-->Purchaser Assignment', select a purchasing group and save.
Then Try creating now a purchaser order directly .
Regards,
Neelima

Report RSMIPROACT gives Customer could not be determined for IDOCs

Hi Friends,
I am executing the report RSMIPROACT in ECC 6.0 system to publish Demand and Stocks into the SCM 7.0 system.
The IDOC is processed without any errors in ECC 6.0 . However, in the SCM 7.0 system , the IDOC fails with the error.
I have noticed that 2 things .
1. E1ADRE1 field is NOT being sent by the ECC system .
2. I get the same error even if I manually add this field and add value 300 or 301 for the qualifier field.
Has anybody faced this problem before ?
I look forward to replies.
Detailed error is given below.
Regards,
Ranjini.
Customer could not be determined
Message no. /SAPAPO/EDI010
Diagnosis
The system must determine the customer number from the IDoc data in order to update stock and sales figures for customers. It uses the additional section E1ADRE1 with the qualifier '300' or '301' in the vendor address section to do this. The customer number stored here should have a valid customer number in the APO System.
The section was not available in the processed IDoc.
System Response
The system cancels processing.
Procedure
Configure the EDI convertor in such a way that the corresponding section has a value.

Hi,
i'm facing the same problem. Could you solve it?
Regards

Logical port could not be determined

Similar Messages

Maybe you are looking for