OCI Catalog for Vendor problem : Logical system for catalog not maintained

We have set up an OCI catalog with on of our vendors. This works fine untill we transfer shopping basket data from Vendor sysem into our SRM-system (SRM5.0). Then data is not being transfered and Vendor Webshop screen remains 'open'.
in SLG1 i have found an error "Logical system for catalog not maintained. Inform system administrator'
Anyone an idea what the cause of this error can be or what we need to check ?
Thanks in advance

Hi,
I have not seen that error before. However, I think it may have to do with the LOGICAL_SYSTEM OCI field. Can you check if your punch-out catalog vendor is populating that field? Also, check if you have the correct BP# populated in the catalog configuration and the LOGICAL SYSTEM Field on the define External Webservices is blank.
SG

Similar Messages

  • Error:No Logical system for FI is maintained.

    Hi,
    we are working on SRM 4.0 and i got the below error messages while trying to create the shopping cart from catalog in quality system.
    1. No Logical system for FI is maintained.inform system admin.
    2. Enter company code.
    3. Partner00000123458 not found.
    we have checked org structure in production and quality system,but there is no problem with production. problem with quality system only. even both systems are having same structure.
    can you please advise  where we need to check the settings pertaining to logical system in SRM side.
    Regards,
    SIS

    Hi
    1.Kindly make ensure that all SPRO settings with quality logical system ( ECC as well as SRM) .
    2. check org attribure value  logical sytem too

  • ALE logical systems for business service or process

    Hi,
    I am trying to send an IDOC into my R/3 system. It is the same IDOC type that I have sucessfully sent out to parties. All the config is in place for communicating with the system, because I have sent others IDOCs in the past. However, they always were sent from another R/3 business system. They processed sucessfully.
    I am now trying to sending IDOC's from a BPM,as well as, from a business service. They are under the "With Party" section of the directory. These obviously do not have logical systems, so when I try to send the IDOC I get
    "Unable to convert the sender service Purchase_Orders to an ALE logical system", where purchase_Orders being the name of the business serice.
    How can I handle this problem?
    Should I hard code values somewhere?
    Which ones?
    I have read the other posts for the error above, but my situation seems to be different.
    Help!
    Chris

    Hi,
    To solve your problem, here my solution:
    1/ In your Business Process of your ID (configurator), go to menu "Service > Adapter-specific identifier" and in the part "IDoc Adapter", write your Logical System.
    2/ Create this Logical System on your target system (R/3).
    WARNING: XI allows you to used a Logical System for only one service (Business Process). Thus, if you are several interfaces, you must used different Logical Systems.
    Mickael.

  • Wrong logical system for partner profile

    Dear gurus,
    we have been sending ORDERS Idocs for some time now, using to a logical system called MSC_MM_PRD, a RFC connection called MSC_MM_PRD and a port for Idoc processing called A000000003.
    Now, we would like to send ORDERS Idocs to another logical system. We created that new logical system called MES001, a RFC connection (MES) and a Port for IDoc processing using that RFC destination (A00000004).
    After that we maintained a partner profile for the new logical system MES001 with outbound parameters for ORDERS Idocs. So far, so good.
    But then, I had to create a new message type for purchase orders to use that new connection (called ZEDI) and I guess that is where I made a mistake: I copied the existing message type for the old ALE connection and changed some parameters (like name etc.).
    Now, when I create a new purchase order and add a message of the new type and save the order, I get an error message:
    EDI: Partner profile outbound process code not available
    Message no. E0335
    Diagnosis
    An outbound partner profile could not be found with the following key:
    /MSC_MM_PRD/LS//EF/ZEDI//
    [u2026]
    Procedure
    Please check the outbound partner profiles for the assignment of the process code:
    As you can see, SAP tries to find an outbound partner profile using the old logical system (MSC_MM_PRD) and the new message type (ZEDI) as a key and obviously fails.
    Can anyone please tell me why SAP uses the old logical system and how I can change that?
    Cheers
    Alicia

    Hi,
    problem was, that we had not created a proper distribution model for the message type (BD64). After we did that, it worked fine.
    Cheers
    Alicia

  • Cost center integration with HR - logical system for CRT inconsistent

    Hi there,
    we are distributing Cost centers from our SAP ERP system to another SAP HR system via ALE [COSMAS01 basic type].
    The cost center created in target system contains information about source system logical system name - table CSKS, field LOGSYSTEM.
    This is causing problems in Travel Managment in SAP HR system, where we get the error: Logical system for CTR inconsistent.
    Cost centers created/changed in HR system does not contain any value in CSKS-LOGSYSTEM field and work fine.
    Any ideas how to solve this issue?
    For now to fix the issue, user needs to do a phony change in SAP HR system to get rid of original LOGSYSTEM value.
    I am thinking about removing field E1CSKSM-LOGSYSTEM from COSMAS IDoc but I gues there must be simpler soloution.
    Thanks for your advices,
    Igor

    Igor :
    I think this has something to do with matching logical system with controlling area in TKA01. Another option for cc's logical system to have no values when outbound ALE is to config V_TKA01_ALE (so it will be transported to the system that has cc ALE to other systems) to have field 'ALE Distribution Method' blank (No distribution to other system).
    This way, when SAP is creating outbound idoc for COSMAS, field CSKS-logicalsystem will not be populated (logic is in SAP 'MASTERIDOC_CREATE_COSMAS' , around line 86).
    Rgds.

  • Error KC041: Logical system for BPR

    Dear all,
    I am having a problem when costing a specific sales order. Can anyone tell me what this means and how we can solve this. I am a newb so please try to be clear. The following error appears:
    "Planning overhead credits not allowed for BPR PD-BDT"
    Message number: KC041
    Diagnosis
    You are not in the logical system where the transaction data for BPR PD-BDT is managed.
    System response
    Activity planning overhead credits is not allowed.
    Procedure
    Activity planning overhead credits can only be carried out in logical system LSP02200_S

    You are not in the logical system where the transaction data for BPR PD-BDT is managed.

  • Logical System for Financial Accounting FI lacking; information systems

    Hello,
    we`ve got a problem with the creation of a SC. After the selection of a product (doesn`t matter if it`s a "free text", good or service), we got always the following Error:
    "Logical System for Financial Accounting FI lacking; information systems"
    I`ve already checked the attribute "ACS" in PPOMA_BBP and the RFC-Connections. Have anybody an idea, what i can do else or where i can get further information about this error (like System Log,...)?
    Regards Jochen

    Hi Jochen,
    Kindly check the following SPRO settings in your system
    1. SPROSRM ServerTech Basic settings--Define backend system for Prod category. (Ensure that your category which you are using in your SC is defined here with source/target system)
    2. SPROSRM ServerCross App Basic Settings--Define Objects in backend systems. (Ensure that Purch grp, prod category, source system, and PO details are maintained here)
    3. SPROSRM ServerCross App Basic Settings--Define G/L account for prod category. (Ensure that your Prod category, Source system, Acct assgnmt categry and G/L account are maintained)
    Pl check the above and revert back.
    Regards,
    Nikhil

  • Auto creation of notification for vendor problems

    Hi, pls advise how to generate notificatin for vendor problems during goods receipt. can it be possible to generate automatically when there is problem for the vendor for the goods which are subjected to GR. Pls advise.

    Hi Yadav,
    pls advise how to generate notificatin for vendor problems during goods receipt.
    While doing GR( which is stores activity) why you want to generate Notification, once GR is made the inspection lot is generated, then while doing RR if some thing is not as per specs then you can raise notification automatically.
    can it be possible to generate automatically when there is problem for the vendor for the goods which are subjected to GR. Pls advise.
    You will be able to generate auto  notification only after you do GR, while doing RR. This authorization you can given to stores but  again unless you inspect the material how you will know that there is problem in material and you need to raise notification.
    for auto notification while RR, you have to assign notification type Q2/ N2 at that inspection type at customizing.
    Also you should tick 'Defect recording' tab in  control indicator of  MIC's, this will  automatically  pop up the Window for  defect recording and  thereby notification.
    Best Regards,
    Shekhar

  • Logical System for RFC-Business system?

    Hi,
    I want use RFC adapter for my scenario like File to RFC.
    The query is like, is there any importance to use Logical system for my Business System which is using for my RFC Adapter in my communication channel.
    Regards
    Gopi

    logical system name is relevant only for Idocs, but it is always a good idea to maintain the technical and business systems with all the information you can provide.
    you can check the logical system names of ABAP application servers at bd54 tx code.
    Regards,
    Henrique.

  • Logical system for client 001 for SAP NETWEAVER ABAP TRIAL VERSION for BI

    Hi,
    I have installed SAP NETWEAVER ABAP TRIAL VERSION for BI. In that I have to create logical system for client 001. I have taken a list of available clients from the abap R3 side. Here is a list of it.
    Clients View
    Cl. Name City Crcy
    000 SAP AG Konzern Walldorf EUR
    001 Auslieferungsmandant R11 Kundstadt USD
    066 Test EarlyWatch Profiles Walldorf EUR
    I cannot get inside the BW side for it asks me to create a logical system for client 001. What to do?
    Kindly help me.
    Kannan

    hi,
    ? First log on to SAP R/3 server connections Go to SCC4 in R/3 & in Scc4 BW server. A screen opens in that logical name of the system would be opened in both (R/3 & BW).
    ? Take notepad in it save .R/3 & BW logical names go to R/3 & click SM59 to create R/3 connections click then a screen opens gives BW logical name in RFC Destination option & give connection. type 3 & give some description & then press enter.
    ? You will get another screen under it then at target host gives BW server name we will get it from BW logon change ID, IP address option & give the system no. The system no go to logon pad just drag it then you will see the name.
    ? Then click on log on securities go to log on give BW server details like No, client user Password. Then save it then click test connection tab if there are errors then it gives yellow color if they are no error the whole thing come as white.
    ? Then click on the Remote Logon then we go to BW server give RFC – SM59 & click create. Then give the server name which is at the bottom right corner give it then give the no, name, password in logon Security save it & test connection & then remote logon.
    ? R/3 - B W - R/3
    ? Logical connection source system connection is used to transfer the data from R/3 to BW. Go to BW system& click RSA1 go to source system option go to top to the source systems right click on it. Then click create then a screens opens then.
    ? PC ?Flat file , DB ? Database
    ? Select the option manual then a screen appears RFC Destination, Logical source name then click OK then it goes to opens other screen save it test connection then remote login then it go back to the then a screen opens then click only activate.
    ? BW ? RS1 ? SOURCE SYSTEM ? CREATE MANUAL AUTOMATIC CELL
    ? R/3 ? Test connections login ? back ? replicate method ? active data R/3 Source system you will able to.
    hope it helps u
    Ramesh

  • How to create Logical System for ALE?

    Hi All,
       I'm an abaper and want to create Logical System For ALE. When i tried to make it using Tcode: SALE, msg appears that "Caution: The table is cross-client", when clik on continue button it shows "You are not allowed to change cross-client customizing".  Help with proper documentation.
    Thanks in Advance.

    Hi,
    what you did is correct but you don't have the authorization for cross-clients in your sever.First take the authorization for cross-clients then follw the steps
    Here i am giving link go through that and do practice,
    http://www.****************/Tutorials/ALE/MaterialMaster/Distribute1.htm
    http://www.****************/Tutorials/ALE/ALEMainPage.htm
    Reward if it useful
    lakshmi.

  • From R/3 to CRM create one logical system for CRM client 300.

    Suppose i create one logical system for CRM in R/3 TO CRM scenario for client 300.another user wants to work on jdbc to CRM client 300 for this he wants to create another logical system for client 300 it is not possible,so,it is ok if he assign same logical system when he was working for CRM client 300 when he wants to create business system for CRM in JDBC to CRM.

    Hi,
    Business Systems are te logical system name for a CLient in the SAP.
    These can be reused again for different configuration scnario that you must have created for different interface.
    All you need to do is assing the Business system to your configuration scenario and Communication channel to the same.
    Regards
    Vijaya

  • Create a client and logical system for BW

    Hi all,
    Can anyone show me how to create a BW client?
         create a BW client and logical system for BW client.
         create sourcesystems for the other clients in BW.
    I have follow some documents
    B84: BI Connectivity
    B03: General Settings BI Integration
    But it's not working the data can't flow to BW server.

    hi,
    check out the following thread's. it will guide you
    Connection steps for SAP BW and R/3
    Info required  while  creating source system
    R/3 Source system creation error in BW 7.0
    regards
    harikrishna N

  • Internal order - Error - Different logical system for order

    Hello all,
    I try to send IDoc (INTERNAL_ORDER) from system A to system B.
    I have done:
    - BD64 / WE20 / WE21
    But after having customizing I have got following error:
    Different logical system for order xxxxxx
    Message no. 2075ALE001
    Diagnosis
    Internal order xxxxxxx already exists in system B. Its master system B is different from the master system A of the new internal order to be distributed with the same order number xxxxxxx.
    System Response
    Internal order xxxxxxx with master system A cannot be distributed in system B.
    Procedure
    Check customizing for ALE for internal orders.
    How to solve this?
    My aim is to maintain internal order master data in test system.
    Thanks for your help.
    David

    I have found something.
    If I change in table AUFK, logical from empty to A (master) and I run IDOC then IDOC has been correctly integrated.
    Then: how to define "master"?

  • Define one logical system for PI or multiple LS for 3rd-party system?

    Hi gurus,
    We are using IDOC2SOAP and SOAP2IDOC scenario in PI7.11. My question is regarding the logical system(or partner profile) on R3 side. We have two 3rd party system:A and B, so we have two choices.
    1. define one single logical system for PI integration server;
    2. define two logical systems for A and B.
    For choice 1, it seems we can only use one business sytem or business component (business service in 7.0) as the two 3rd party system, especially for SOAP2IDOC scenario.
    For choice 2, it seems we have no restrictions.
    Is it correct?Any help will be appreciated.

    technically you can use both options.
    The question is - do you want all the IDOCs in your R3 system to appear as though they were sent from the PI?
    What if a lot of 3rd party systems were sending the same IDOC (for example - ORDERS) and you want to investigate only those who were sent from system A?
    I like it configured that every system will be identified by a name I give it.
    I just use the IDOC communication channel checkbox of "Take Sender from Payload"
    or use a different service in the IBC that has a different logical system configured in its Adapter specific identifiers.
    Hope it helps,
    Imanuel Rahamim.

Maybe you are looking for