Ip address of localhost could not be determine

hi am running installer in oracle linux 6 to install oracle database 11g and am geting this error
Cause - The localhost is not mapped to a valid IP address in Hosts file (Eg. /etc/hosts in Unix).
Action - Assign a valid IP address for the localhost or set it to loopback IP address (127.0.0.1 in IPv4 or ::1 in IPv6).
Summary  - tshifhiwa-pc: tshifhiwa-pc

hosts is 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
and etc/resolve.conf is empty
and ifconfig is
eth0 Link encap:Ethernet HWaddr D4:85:64:14:8B:57
inet addr:192.168.5.12 Bcast:192.168.5.255 Mask:255.255.255.0
inet6 addr: fe80::d685:64ff:fe14:8b57/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2654 errors:0 dropped:0 overruns:0 frame:0
TX packets:2899 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1884955 (1.7 MiB) TX bytes:715663 (698.8 KiB)
Interrupt:28
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1308 (1.2 KiB) TX bytes:1308 (1.2 KiB)

Similar Messages

  • 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.

  • 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

  • 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

  • Error during SC creation - Jurisdiction code could not be determined

    Hi All,
    For testing purpose , I have set up one user id. While creating SC with that ID, I  am getting one error, it says "Jurisdiction code could not be determined ".
    Plant , company code everything enetred in the SC is perfect.
    On another hand, I can create SC with my id without any error..
    Attibutes are identical of both the  user ids.
    Can someone help me to know the reason for this particular case
    Regards,
    Sheetal

    Hi
    Jurisdiction code is determined based on Ship to Address data of the shopping cart and the country code. Pl check if the ship to address in the shopping cart is correct. It might be missing mandatory informations like Postal code, city, District.
    Regards,
    Sanjeev

  • Error "Jurisdiction code could not be determined" in so create bapi

    I am using the bapi "SO_NEW_DOCUMENT_ATT_SEND_API1" for creating the sales order,
    it gives the error "Jurisdiction code could not be determined" Sometimes there are two juridiction code maintained in the system .
    1) During the ship to party address change at sales order , city , country and postal code fields determine the Juridiction codes. Sometimes there are two juridiction code maintained in the system for one city and in such cases BAPI fails to create an order.
    2)When the ship to party is foreign country then we do not need Juridiction code in sales order. In such cases also the BAPI fails to create sales orders and writes an error log , saying juridition code could not be determined.
    Proposed Soltuion.
    We have to modify the BAPI to force the values of ship to address as it is from the text file without exiting the sales order creation.
    Thank You,
    Ganesh

    hi ,
      u need to give the right postal address. If it is then it won't give the warning message.
    Regards,
    Rose.

  • 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.

  • Unable to create shopping cart - Jurisdiction code could not be determined

    Hi,
    I've found several threads here asking about tax jurisdiction code but none of them seem to solve my problem.
    When we create shopping carts for our north american back end R/3 system we cannot save them because of an error with the jurisdiction code "Jurisdiction code could not be determined ".  Our ship-to address is correctly maintained with the city, country, post code, etc.  I have tried maintaining the jurisdiction code on our organisational business partner but this makes no difference.  For info, we use Taxware to create the jurisdiction code in the back end.
    We looked at applying oss note 436760 but apparently this note is only valid for SAP Basis Component 4.6 and 6.1 but we are on 7.00.  Do you think it is necessary for us to implement a BADI?
    Thanks in advance for any help.
    Roo

    Hi All,
    Please see my answer to similar concern raised in the thread:
    [BAdI BBP_CATALOG_TRANSFER - Material Group Mapping issue;
    Your question is that initially it was working with Jurisdiction code and now not? Why?
    Because, the backend system is either connected to the third party Tax engine such as Taxware, and doing so, some of the addresses (Country, Region, City and Pin Code combination) may have more than one Jurisdiction code, in such cases, SRM gets confused of which code to select, and hence the error.
    Use the BAdI and get going!
    Thanks for reading!
    Ashok Kawa

  • 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
    <b>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.</b>
    Anyways, send the detailed business requirements to my mail which are already having with you.        )
    I will definitely help you out.
    <u>Please refer to following threads as well.</u>
    <b>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.

  • 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

  • Withholding tax -number could not be determined for numbering group ID0017

    While positing the FB60 transaction with withholding tax for country Indonesia, the below error is coming:
    A number could not be determined for numbering group ID0017
    Message no. 7Q630
    "The system could not determine a certificate number for the numbering
    group.
    Withholding tax types exist that are relevant to numbering. The system
    cannot determine a certificate number because the Customizing settings
    are incomplete.
    Sysem Response
    Payment cannot be made.
    Procedure
    Check the number ranges in the numbering group."
    Already seen the wothholding tax number range and it is coorec. Please advise how to resolve.

    Dear,
    Please check whether you have assigned the number range to the number group in the below setting
    Spro
    Financial Account Global Setting> Withholding Tax>  Extended Withholding Tax> Posting> India> Remittance Challan>     Assign Number Range to Number Groups

  • Customer/vendor could not be determined for IDOC

    Hi all,
    Am trying to post incoming payments through EDI ..
    IDOC Information
    IDOC type: PEXR2002
    Message type: REMADV
    Function Module: IDOC_INPUT_REMADV
    Process code: REMA
    Am getting these 2 errors :
    Customer/vendor could not be determined for intermediate document
    Company code could not be determined for intermediate document
    Has anyone encountered this problem, if yes can anyone suggest the solutions, any help regarding this is highly appreciated.
    Thanks.

    Hi,
    Currently I am facing with the same type error when trying to post incoming payments through EDI.
    IDOC Information
    IDOC type: PEXR2002
    Message type: REMADV
    Function Module: IDOC_INPUT_REMADV
    Process code: REMA
    I am getting the below error:
    1. Company code could not be determined for intermediate document
    I have maintained record records for partner type and partner number in OBCA.
    Please advice what are the other configuration changes do I need to maintain.
    Your assistance would be highly appreciated.
    Thanks.
    Edited by: Victor Collins on Feb 27, 2009 9:31 PM

  • Company code could not be determined for IDoc #.......

    I was trying to generate an IDoc manually by using the tcode WE19. I have manually keyed the data in to the respective segments for the basic type PEXR2002 and message type REMADV. After this while processing, the IDoc is getting generated, but not posted OK. I am getting the following two error messages 51 stating:
    'Company code could not be determined for the IDoc #....'
    'Customer/vendor could not be determined for the IDoc #.'
    Can any one give some inputs on this issue?
    Shaji
    Message was edited by: Shaji Thomas

    Hi Shaji,
    You may look at the OSS note 316811.
    Thanks
    Vinod

Maybe you are looking for