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
When handling SAP query you may come across error user groups similar to SYST****XX. If you are unable to view these user groups or quarries belong to these user groups follow below steps. 1. Go to SQ03 settings and allow display of system objects. 2. Go to SQ01 select standard query areas to view the
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
After a upgrade, sometime SAP query programs assigned to transaction codes terminates with runtime errors. Few errors I have come across are, Error when importing object FIELDCAT. The generated program does not exists. The generated program mismatches the query definition. Short dump of the type IMPORT_ALIGNMENT_MISMATCH in program SAPLAQRUNT. Some of the errors like missing program names
Error “function group contains errors” could be due to inconsistencies in the function group. If you come across this error when trying to execute a function module follow the below steps to rectify the issue. To fix the issue you simply have to repair the function group. Go to se37 and select Utilities and repair
At runtime of ALV report short dumps can occur if the ALV is not consistently build. You can find the consistency of the ALV using ALV consistency check. This will show the status of ALV attributes like field catalog, Layout, filter, variant etc. As a example below ALV gives a runtime error when exporting to
I came across this error when working with file to iDoc interface. Check the below settings if the error occurs. 1. Maintian Communication Channel Configuration. In your receiver iDoc communication channel maintain the correct RFC destination and port. 2. Connection settings in SM59 Check if the connection is working without errors. 3. Port Settings
I came across the error “Receiver Service Cannot be Converted into an ALE Logical System” when I was working on a File to iDoc interface. This error can occur for iDoc sender of receiver if the business system is not configured properly. You have to check the settings shown below if the error occurs.. 1.