Table of Contents

Search

  1. Preface
  2. Part 1: Getting Started with PowerExchange for SAP NetWeaver
  3. Part 2: Data Integration Using PowerExchange for SAP Dynamic ABAP Table Extractor
  4. Part 3: Data Integration Using ABAP
  5. Part 4: IDoc Integration Using ALE
  6. Part 5: Data Integration Using BAPI/RFC Functions
  7. Part 6: Data Migration
  8. Part 7: Business Content Integration
  9. Part 8: SAP BW Data Extraction
  10. Part 9: Loading Data to SAP BI
  11. Appendix A: Data Type Reference
  12. Appendix B: Code Pages and Unicode Support
  13. Appendix C: Glossary

PowerExchange for SAP NetWeaver User Guide for PowerCenter

PowerExchange for SAP NetWeaver User Guide for PowerCenter

Troubleshooting Business Content Integration

Troubleshooting Business Content Integration

I cannot connect to SAP to create a processing mapping with my user name.
You may not have configured your user name as a logical system user name in SAP.
I cannot see the DataSource for which I want to create a processing mapping.
You may not have activated the DataSource within SAP. Activate the DataSource within SAP.
Not all the fields in the DataSource are visible when I create a processing mapping.
Some fields in the DataSource may be hidden. Use transaction RSA6 in SAP to clear the hidden fields.
How can I verify if the listener workflow received all the data that was sent by SAP?
The PowerCenter Integration Service prints a message in the session log that specifies the number of records that was sent by SAP and the number of records that was received by the listener workflow. Review the session log to see if the number of records match.
The update did not return the data I expected. How can I make sure everything is working properly?
There may be problems within SAP or the DataSource may have hidden fields. Use transaction RSA3 in SAP to test the extraction within SAP using the same data selection criteria as the delta update. You can then compare the results with the results from the delta update.
The BCI listener workflow fails when I configure the BCI listener mapping for delta extraction and the delta extraction does not have any row.
The connection parameters or user names that you defined in the relational connections for the send request workflow and the listener workflow may be different. Ensure that the connection parameters and user names in all the relational connections match.
The session failed with a timestamp error.
The request file is older than the latest processing mapping for that DataSource. Deploy the request file for the latest processing mapping created for the DataSource.

0 COMMENTS

We’d like to hear from you!