Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Connection could not be established between PowerCenter and SAP. |
User Response: | Contact the SAP administrator. Also see the RFC trace file or SAP system log for more details. |
Explanation: | Internal Error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | There was a problem with the RFC communication with SAP. |
User Response: | Get the detailed message from the session log. See the RFC trace file, SAP system log, and SAP documentation for more details. contact Informatica Global Customer Support for further assistance. |
Explanation: | You generated the ABAP program for a mapping on one SAP system, but you ran the session with the mapping on another SAP system. |
User Response: | Regenerate the ABAP program for the mapping against the source system and run the session on the same SAP system. |
Explanation: | SAP could not parse a filter expression. |
User Response: | If you entered a filter override in the session properties, verify the syntax. If you entered a filter override in the mapping properties, open the mapping in the Designer and validate the filter. |
Explanation: | The SAP system is down. |
User Response: | Contact the SAP system administrator. |
Explanation: | You may not have permission to release the background job. |
User Response: | Verify with the SAP administrator that you have proper permissions. You must have authorization on S_DATASET, S_PROGRAM, and S_BTCH_JOB objects. |
Explanation: | The connection to the SAP system is broken. |
User Response: | Check with the SAP system administrator or contact Informatica Global Customer Support. |
Explanation: | The Integration Service could not open the staging file. |
User Response: | Verify the path to the file. |
Explanation: | You accessed the staging file through NFS mount, and the Integration Service user may not have write permission on the staging file or directory. |
User Response: | Get write permissions from the system administrator for the Integration Service user. |
Explanation: | You generated an ABAP program for this mapping, but you did not install it on the SAP system. |
User Response: | Open the Generate and Install dialog box in the Mapping Designer and install the ABAP program for the mapping. |
Explanation: | Insufficient heap memory allocation. |
User Response: | Reduce the number of processes running, or increase the virtual memory on the Integration Service host. |
Explanation: | You might have transported the ABAP program to a system that contains different hierarchy and/or master table information. |
User Response: | Verify the SAP source matches the definition in the repository. |
Explanation: | RFC error. |
User Response: | Contact the SAP administrator. |
Explanation: | The leaf nodes of the hierarchy are empty. There are no key values. |
User Response: | Verify the hierarchy from which you are trying to extract. |
Explanation: | Internal SAP error. |
User Response: | Contact the SAP administrator. |
Explanation: | SAP could not import hierarchy information from PowerCenter, possibly because the SAP administrator did not run the transport program, YPMPARSQ. |
User Response: | Have the SAP administrator run the program YPMPARSQ from the ZERP development class. |
Explanation: | Either the SAP system failed or the program to extract from a hierarchy failed. |
User Response: | Check with the SAP administrator. |
Explanation: | You saved the repository with the mapping open after you installed the ABAP program on the application server. |
User Response: | In the Designer, open the mapping and save the repository. Then install the ABAP program. |
Explanation: | You saved the repository with the mapping open after you installed the ABAP program on the application server. |
User Response: | In the Designer, open the mapping and save the repository. Then install the ABAP program. |
Explanation: | The SAP codepage and the SAP reader codepage are incompatible. |
User Response: | Ensure that the SAP reader code page is compatible with the SAP code page. |
Explanation: | The pmlocale.bin file is missing or does not have the code page ID you selected in the database connection. |
User Response: | Verify the existence of the pmlocale.bin file and the code page information. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The SAP code page is not compatible with the code page you selected in the database connection. |
User Response: | Select a code page that is compatible with the Integration Service and the SAP system. |
Explanation: | The Integration Service could not verify the version of the transport files. |
User Response: | Verify that the SAP system is running and the transports are activated. Contact Informatica Global Customer Support. |
Explanation: | The PowerCenter Client or Integration Service cannot communicate with the SAP system. |
User Response: | See the additional error message for more information. Also see the SAP trace file for more information. |
Explanation: | The PowerCenter Client or Integration Service cannot communicate with the SAP system. |
User Response: | See the additional error message for more information. Also see the SAP trace file for more information. |
Explanation: | The PowerCenter Client or Integration Service cannot communicate with the SAP system. |
User Response: | See the additional error message for more information. Also see the SAP trace file for more information. |
Explanation: | The PowerCenter Client or Integration Service cannot communicate with the SAP system. |
User Response: | See the additional error message for more information. Also see the SAP trace file for more information. |
Explanation: | The PowerCenter Client or Integration Service cannot communicate with the SAP system. |
User Response: | See the additional error message for more information. Also see the SAP trace file for more information. |
Explanation: | The PowerCenter Client or Integration Service cannot communicate with the SAP system. |
User Response: | See the additional error message for more information. Also see the SAP trace file for more information. |
Explanation: | The PowerCenter Client or Integration Service cannot communicate with the SAP system. |
User Response: | See the additional error message for more information. Also see the SAP trace file for more information. |
Explanation: | The PowerCenter Client or Integration Service cannot communicate with the SAP system. |
User Response: | See the additional error message for more information. Also see the SAP trace file for more information. |
Explanation: | You generated a program for a mapping that has an SAP table reader source of type hierarchy. |
User Response: | You do not need to generate a program if the mapping has an SAP table reader source that is of type hierarchy. |
Explanation: | You entered a query containing characters that are not valid in the source database connection code page. |
User Response: | Change the query to contain characters in the source database connection code page. |
Explanation: | You entered a filter condition containing characters that are not valid with the source database connection code page. |
User Response: | Change the filter condition to contain characters included in the source database connection code page. |
Explanation: | You entered a join condition and/or a source filter condition that contain characters that are not valid in the source database connection code page. |
User Response: | Change either the join, filter, or both conditions to contain characters in the source database connection code page. |
Explanation: | You defined a partition key for a port in the Application Source Qualifier that you deleted. |
User Response: | Edit the session to remove the partition key from the Application Source Qualifier. Then save the new partition information in the session and run again. |
Explanation: | You entered a wrong syntax for the filter expression. |
User Response: | Enter the filter expression using the proper syntax. |
Explanation: | You provided an invalid value for the filter expression in the SAP table reader of the source qualifier. |
User Response: | Specify a valid reserved word in the filter expression. |
Explanation: | You specified multiple field level filters in the filter expression. |
User Response: | Specify a single field level filter in the filter expression. |
Explanation: | You specified a table level filter within a field level filter, in the filter expression. |
User Response: | Delete the table level filter in the field level filter expression. |
Explanation: | The SAP system is Unicode data-enabled, but the Integration Service is running in ASCII data movement mode. |
User Response: | Change the data movement mode of the Integration Service to Unicode. |
Explanation: | The Integration Service could not connect to the remote SFTP server. The user name or password might be invalid. |
User Response: | See the additional error message for more information. |