Proxy Communication Error SLD_NO_OWN_BS

While setting up proxy communication between PI/PO and SAP backend, after a new PI/PO 7.4 single stack server installation, I came across error “SLD_NO_OWN_BS”. Full Error in PI Message Log: “SOAP: Call failed: com.sap.aii.af.sdk.xi.srt.BubbleException: System Error Received. HTTP Status Code = 200: However System Error received in payload ErrorCode = SLD_NO_OWN_BS ErrorCategory = XIServer Parameter1

How to Transport LSMW Objects?

Lets look how to transport LSMW Objects between clients. LSMW (Legacy System Migration Workbench) is a tool that supports legacy system data migration to SAP systems. Legacy data can be imported, transformed and saved to SAP via iDocs, BAPIs, Batch Data Input (BDC) or as Direct Input. This article discuss ways you can transport LSMW

Create LSMW with BDC Recording Example

LSMW which stands for Legacy System Migration Workbench supports conversion of legacy system data in a orderly and convenient way. Tool allows you to import converted legacy data to SAP. There are several ways you can import legacy data to SAP using LSMW. Below are few common methods used to migrate legacy data to SAP

XML Transformation Example with XSLT_TOOL

With ever changing world of integration one language that has stood the test of time is XML. Due to capabilities of XML and large number of system integration requirments, its impertinent for technical consultants to understand the XML transformation capabilities in SAP.  SAP transformations are used to filter and recognize XML data. SAP transformations can

Find SAP Query Detail from Program Name

SAP queries automatically creates a ABAP program when they are saved and generated. These auto generated programs starts with AQ. If you come across a report transaction with a long program name similar to AQ====****====**** this could be a program generated by a SAP query. Name should be in the following format: First 2 letters of report