Logical System field in BD10/BD14 need as a Mandatory Field

Hi All,
Good Day,
We have Logical System field in BD10 or BD14 etc.. TCodes and I would like to make this field as a Mandatory field. The reason for this is, while sending the Materials using BD10, and If I haven't enter any value for this field, IDOCs are getting generated and sending to all the logical systems say Dev, Quality and Production too. I want to avoid this.
So Is there anyway where we can make the filed "Logical System" as a mandatory field.
Thanks in Advance.
Param.

HI Param,
try BAPI_IDOC_INPUT1and check it in WE57 tcode.
hope this helps
regards
Aakash Banga

Similar Messages

Problem in populating data to Logical System field

Hi All,
I am extracting GR data through Generic extraction. I am created a view using four tables MSEG, EKBE, EKKO and T001. I have a field LOGSY (Logical System). This field is in EKKO table. My problem is LOGSY field have no any data. I have to write a routine to populate data to this field. Can anybody plz tell me the code?
Edited by: Kasi Viswanath Aurangabad on Jun 18, 2008 7:50 AM

Hello,
the code is:
SELECT SINGLE logsys
FROM T000
INTO your_variable
WHERE mandt = sy-mandt.
Assign points if useful,
Best Regards,
Maciej

How many logical systems do I need?

Hi,
If I want to send an IDOC from SAP through the business connector to 10 different parties, what is the cleanest way to do so?
Do I have to create for each party a logical system in SAP? And do I have to maintain then for each an RFC destination to the business connector? Can multiple logical systems use the same rfc destination?
Advantage would be that you see in SAP to who the idocs were send, if you only see that one was send to the business connector and it's send from there to 10 parties you have less control ?
thx for helping,
jeroen

Jeroen,
It depends on the type of document in SAP, and partner type.
You only need logical systems if the other end is a different system from each other.
If your IDoc are KU or LI then you can use the SAP number instead of the logical system.
This means you need more routing rules inside SAP BC. 10 partners is not large. If you have 10000 partners, you have a lot of work. You can always use wildcards in the routing rule (depending on where the messages are going).
Regards,
Simon

Logical system name in SRM system

We are into SRM version 5.(SRM server 5.5) with the backend system as SAP ECC 6.0 .
The logical system is defined as '0000000050' for backend SAP system . All the systems like CRM and BW uses this as the logical system name for backend system . Recently SRM is implemented in our organization and we have no other choice and have to use the logical system name as '0000000050'
When product categories are assigned in the org attributes , the system stores the back end system as 50 and this is the issue. SAP support mentions that this is issue with logical system naming convention and that need to be fixed . But they fail to understand that the same name works fine in all other systems and also in SRM system except product categories .
Is there any OSS note for this fix. I would like to hear your experiences in this scenario.
Thanks
Mani

Hi Mani,
Logical System names are system specific, hence you have a different name in SRM system which will represent your backend system and this is not at all an issue. As suggested by SAP; '0000000050' is not the best name as per best practices.
You should have a name which should be of the pattern: <SID>CLNT<Client Number>.
Now here is the solution/work around. But be very careful and try this in sandbox system before being carried out in Dev/QA/PRD systems. Please make sure no other users are performing any activity while these tasks are being carried out.
In addition, please read through the ["Set up and system copy of SRM server 5.5";|https://websmp204.sap-ag.de/~sapidb/011000358700000310782007E/SRM50_SetupTranspCopy.pdf] guide before you carry out this activity:
The below activities are to be carried out only in SRM system
I assume SRM & Backend are separate instances
1. Create a new logical system name for the backend system in SRM system as per the standard suggested above.
2. Then use the transaction BDLS, to convert the old logical system name to new logical system name in all the tables.
3. Now, the step 2 ensure the logical system name is converted appropriately in all tables except SRM Org Structure related table.
4. Use the report RHOMATTRIBUTES_REPLACE, for replacing all the old logical system value with new logical system value. Please note while providing the inputs in the screen, there will be a Checkbox field called "Sub-String", you must check this one for all attributes you enter in the report. Then when you execute the report, a list will be display, here you have to select all the rows and click the first button on the toolbar. Only then the attributes will be updated.
Please let me know, if further inputs are required.
Regards, Kathirvel

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

How to get the current logical system?

Dear Abapers:
I can't find the logical system value from the table SYST, pls tell me how to get the current logical system name, Thanks!

Hi,
Check with the table T000, the Logical system field name is LOGSYS.
Regards
Thiru

Business System and Logical system

Hi Experts,
in SAP if we want to exchange the Data between the systems we use Logical Syestem. Why we need Logical systems basically? and Why need Business system in XI?
Thanks,
Manoj.

hi manoj,
check this link.
http://help.sap.com/saphelp_nw04s/helpdata/en/42/c817d9d2296bb2e10000000a1553f6/frameset.htm
regards
srinivas

Logical System not appearing in SLD

Hello Friends,
Logical System of SAP R/3 system is not appearing in SLD. The logical system is available in backend ABAP System. I have even run the RZ70 data collection programs as well. However, I am not able to populate the logical system names in SLD.
I have put the same logical system names in the client tab of the technical system but in vain. The logical system field is non-editable and I believe it is always non-editable unless some technical system is not assigned to it.
The logical system name is also not available in ID (if it is not in SLD then it won't be in ID as well).
[The SLDCHECK is throwing exception 4. what to do for this? May be the data is not transfered because of this? Even though I have maintained proper password in SLDAPICUST!!!]
Request your kind adivse on what can be done. Where can I lookout for possible errors.
Thanks & Regards,
Anand Patil

Hi
On SLD - > Technical System -> Client -> Logical System Name , generally It is Editable entity .
If in Your Case , You can not change it, chech with ut basis Guy , for roles and authorisation against your Username ,
Check the Same SLD Roles with some PI Service User.
Regards
Prabhat Sharma.

Logical system name

Hi,
I have done the system copy from production system to quality system yesterday.After that i am unable to change the logical system name in Quality syste in scc4.The logical system field disabled.Why?
Regards,
Mani

Hi,
What we do after system copy is run BDLS in target system & this changes logical system name.
Check below link for more details
Re: about assigning logical system name to client
Thanks
Sushil

Logical System name in BBP_DET_TAX_CODE

I am having a problem updating the logical system name in the configuration for BBP_DET_TAX_CODE. The menu path is SRM Server -> Cross-Application Basic Settings -> Tax Calculation -> Determine Tax Code for Country/Product Category. When I try to add new entries to the table, the logical system name field is grayed out so that I cannot enter any value.
The entries in the table have the logical system name. Example:
I Domestic US CAP035 DRACLNT220 I0
I Domestic US CAP036 DRACLNT220 I0
I tried using the Edit -> Change Field Contents -> Source system name, but this didn't change any values. We are running SRM Server 5.5 with support pack level 14 in classic mode. Any help would be appreciated.
Thanks,
Scott Andrew

Hi
Yes, logical system field is greyed out. Once you enter the product category (category ID), it will automatically pick the relevant backend logical system.
R/Reddy.

Logical systems for ALE

HI all,
I'm configuring for an IDoc to be generated and downloaded to a file via a file port.
This IDoc is of message type PAYEXT.
The file is to be sent ot the bank via the meansa of third party software.
Do I have to create logical systems for these? Or only the outbound logical system?
Do I also need to set up the distribution model , and if so, how far do i need to set it up?
Points wil be awarded. Thanks!

Hi
Use BD64 Tcode to setup distribution Model
Define the 2 logical systems.
see the flow:
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Reward points if useful
Regards
Anji

Unable to convert the sender service ABC_Service to an ALE logical system

Hi,
I have a JMS (Party) --> PI --> IDOC scenario.
Party: ABC_Party
Service: ABC_Service
I am getting the error Unable to convert the sender service ABC_Service to an ALE logical system when I test the scenario using RWB -> Component Monitoring -> Integration Engine -> Test Message.
I have already done the below settings:
1) Defined Header Mapping in Receiver Agreement for IDOC (Sender Party, Sender Service and even Receiver Service are specified)
2) Business Component (ABC_Service) -> Adapter Specific Identifiers -> mentioned details for SAP (IDOC) system.
The scenario works perfectly fine for a party-less communication JMS -> PI -> IDOC
Have already seen:
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system
Thank you,
Pankaj.

You need to create party if its a B2B scenario
Under Identifiers
under agency select any standard agency , scheme name will automatical;ly get populated and name you can give manually as sender name
Please refer this for more details
http://help.sap.com/saphelp_nwpi71/helpdata/en/b9/64663c7a6c2545ae292fb26d8c33c4/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/81/104bb1fbab254c8644877c7f856bbf/content.htm
Re: Party Configuration
In case of cross company process it is required
Regards
Ninad
Edited by: Ninad Sane on Nov 18, 2010 11:17 AM

Unable to convert the sender service to an ALE logical system... Urgent..!!

Hi,
Im DOing File to Idoc scenario.
Firstly i check LS name exist or not in BS.. then i found its not maintained.
I edited the BS and provided the required LS name.
and the same has been tested in ID
Business System -> Service -> Adapter Specific Identifiers .
Now i got logical system name in "Adapter Specific Identifiers".
Pressed Apply, save and activate the changes.
But still it is showing the same error.
1. Any idea what might have gone wrong??
2. I need to maintain the
   LS name of R/3 in XI system? and
   LS name of XI in R/3 system?
    Is it necessary?
Waiting for your answers.
Regards
Seema.
Edited by: reddy seema on Dec 27, 2007 1:37 AM

Hi Reddy,
        just mention the logical system name in the Sender Business system or Service ( click on sender business service> Service(menu)> Adapter Specific Identifiers--> specify the logical system name which you configured in R/3 WE20 ..) in R/3 side WE20 you need to configure the Inbound parameters of your Idoc ..
Here sender business system and Reciver Business system logical system names are different.. for checking just go to Services and check the adapater specific identifiers..--> then you   can find the name of logical system.. like that you need to check for both systems.. and both should be different..
try with this option..
Regards
@jay

Hi how to create logical systems.

Hi,
how to create logical systems. Do we need to create logical system name for creating RFC destinations? plz help me out.
thanks
dhanush.

Hi,
transaction:
SALE -> Basic Settings -> Logical Systems -> Define Logical System
No, you don't need to create Logical Systems to define RFC destinations.
Regards,
Jakub

Is Logical System required for Solution Manager to work?

Hi all
We will be upgrading to SAP ERP in the near future and will have to use Solution Manager.
We only have one company code and no business areas in our configuration. So that, we do not need ALE, consequently, we have not defined/used a logical system.
Do we now need to define a logical system and assign our client to it, in order to use Solution Manager?
tia
Manuel

Hi Manuel,
in logical components the term "Logical System" is used to discribe the combination of system and client in an ABAP system. This does not mean you have to define logical systems in ALE customizing. That is not required as far as I know.
Regards
Andreas

Logical System field in BD10/BD14 need as a Mandatory Field

Similar Messages

Maybe you are looking for