Explanation: | The Integration Service received an RFC call from SAP for a function that is not registered to the Integration Service. |
User Response: | Use the RFC Destination created for the Integration Service in SAP to send outbound IDocs only. |
Explanation: | The 6.x IDoc_Prepare AEP transformation contains an invalid value for the IDocParamType property. |
User Response: | Edit the transformation and select either ControlRecord or SegmentRecord for this property. |
Explanation: | The Integration Service failed to retrieve the IDoc metadata for a 6.x IDoc mapping. |
User Response: | Verify that the Informatica transports were correctly installed or upgraded. Verify that the saprfc.ini file is configured. Also, verify that the RFC Destination created in the SAP system for the Integration Service is valid. |
Explanation: | The 6.x IDoc_Writer AEP transformation contains a list of values for the IDocTypeList property that are not separated with the correct delimiter. |
User Response: | Edit the transformation and use a semicolon (;) to separate the list of IDoc types. |
Explanation: | The number of IDoc types listed in the IDocTypeList property does not match the number specified in the NumberOfIDocTypes property for the 6.x IDoc_Writer AEP transformation. |
User Response: | Edit the transformation so that the value for the NumberOfIDocTypes property matches the number of IDoc types listed in the IDocTypeList property. |
Explanation: | The Integration Service failed to retrieve the metadata for the IDoc_Writer AEP transformation in a 6.x inbound IDoc mapping. |
User Response: | Verify that the Informatica transports were correctly installed or upgraded. Verify that the saprfc.ini file is configured. Also, verify that the RFC Destination created in the SAP system for the Integration Service is valid. |
Explanation: | The 6.x IDoc_Writer AEP transformation received data for an IDoc type that is not included in the IDocTypeList property. |
User Response: | Edit the transformation so that the IDocTypeList property includes all IDoc types the transformation will receive. |
Explanation: | The 6.x IDoc_Writer AEP transformation received data for an IDoc type that is not included in the IDocTypeList property. |
User Response: | Edit the transformation so that the IDocTypeList property includes all IDoc types the transformation will receive. |
Explanation: | The Integration Service failed to parse the IDoc control record data received by the 6.x IDoc_Writer AEP transformation. |
User Response: | Correct the source data so that it contains valid control record data. |
Explanation: | The 6.x IDoc_Writer AEP transformation received data for an invalid segment for the IDoc type. |
User Response: | Correct the source data so that it contains only valid segment data as defined by the metadata for the IDoc type. |
Explanation: | The 6.x IDoc_Writer AEP transformation received a null value for the control record. |
User Response: | Correct the source data so that the IDoc control record data does not contain null values. |
Explanation: | The 6.x IDoc_Writer AEP transformation received a null value for the segment record. |
User Response: | Correct the source data so that the IDoc segment record data does not contain null values. |
Explanation: | There is not enough memory on the node where the Integration Service process runs to perform the desired operation. |
User Response: | Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. |
Explanation: | There is not enough memory on the node where the Integration Service process runs to perform the desired operation. |
User Response: | Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. |
Explanation: | There is not enough memory on the node where the Integration Service process runs to perform the desired operation. |
User Response: | Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. |
Explanation: | There is not enough memory on the node where the Integration Service process runs to perform the desired operation. |
User Response: | Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. |
Explanation: | The SAPALEIDoc target definition received several data segments but no control record segment (EDIDC) for the specified IDoc type. Each IDoc must contain one control record segment followed by one or more data segments. This error might occur if the transformation preceding the SAPALEIDoc target definition is not an SAP/ALE IDoc Prepare transformation and if it passes invalid IDoc data. |
User Response: | Verify that valid IDoc data is passed to the SAPALEIDoc target definition. |
Explanation: | The SAPALEIDoc target definition received several data segments but no control record segment (EDIDC) for an IDoc type. Each IDoc must contain one control record segment followed by one or more data segments. This error might occur if the transformation preceding the SAPALEIDoc target definition is not an SAP/ALE IDoc Prepare transformation and if it passes invalid data. |
User Response: | Verify that valid IDoc data is passed to the SAPALEIDoc target definition. |
Explanation: | The number of control record segments that the SAPALEIDoc target definition received does not match the total number of IDocs received. Each IDoc must contain one control record segment followed by one or more data segments. This error might occur if the transformation preceding the SAPALEIDoc target definition is not an SAP/ALE IDoc Prepare transformation and if it passes invalid data. |
User Response: | Verify that valid IDoc data is passed to the SAPALEIDoc target definition. |
Explanation: | The SAPALEIDoc target definition received a control record segment but no data segments for the specified IDoc type. Each IDoc must contain one control record segment followed by one or more data segments. This error might occur if the transformation preceding the SAPALEIDoc target definition is not an SAP/ALE IDoc Prepare transformation and if it passes invalid data. |
User Response: | Verify that valid IDoc data is passed to the SAPALEIDoc target definition. |
Explanation: | There is not enough memory on the node where the Integration Service process runs to perform the desired operation. |
User Response: | Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. |
Explanation: | The Idle Time session property specified for the SAPALEIDoc source definition contains an invalid value. |
User Response: | In the session properties, edit the Idle Time value so that it is greater than or equal to -1. |
Explanation: | The Packet Count session property specified for the SAPALEIDoc source definition contains an invalid value. |
User Response: | In the session properties, edit the Packet Count value so that it is greater than or equal to -1. |
Explanation: | The Real-time Flush Latency session property specified for the SAPALEIDoc source definition contains an invalid value. |
User Response: | In the session properties, edit the Real-time Flush Latency value so that it is greater than or equal to 0. |
Explanation: | The Reader Time Limit session property specified for the SAPALEIDoc source definition contains an invalid value. |
User Response: | In the session properties, edit the Reader Time Limit value so that it is greater than or equal to 0. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Integration Service cannot initialize the session. The session properties for the Source Qualifier instance might be invalid. |
User Response: | Check the additional error message for more information. |
Explanation: | In the session properties, an invalid application connection type was selected for the SAPALEIDoc source definition. An SAPALEIDoc source definition must use an SAP_ALE_IDoc_Reader application connection. |
User Response: | In the session properties, select an SAP_ALE_IDoc_Reader application connection for the SAPALEIDoc source definition. |
Explanation: | In the 6.x IDoc_Interpreter EP transformation, the TypeOfEP property is not set to IDocInterpreter. |
User Response: | Edit the transformation so that the TypeOfEP property is equal to IDocInterpreter. |
Explanation: | The Integration Service encountered an error while reading IDocs from the SAP system. |
User Response: | See the additional error messages for more information. |
Explanation: | The RFC Destination created in the SAP system for the Integration Service may be invalid. |
User Response: | Verify that the RFC Destination is valid. |
Explanation: | The SAPALEIDoc source definition contains more than one input group. |
User Response: | Recreate the SAPALEIDoc source definition. |
Explanation: | The SAPALEIDoc source definition may contain incorrect port names. |
User Response: | Recreate the SAPALEIDoc source definition. |
Explanation: | The 6.x IDoc_Writer AEP transformation received data for an IDoc type that is not included in the IDocTypeList property. |
User Response: | Edit the transformation so that the IDocTypeList property includes all IDoc types the transformation will receive. |
Explanation: | The Integration Service could not initialize the writer properties for the specified target. The session failed. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service could not find a value for the specified connection property. |
User Response: | Check the additional error message for more information. |
Explanation: | Internal error. The PowerCenter repository contains inconsistencies. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Integration Service could not configure recovery for the session. |
User Response: | Check the additional error message for more information. |
Explanation: | This is a warning message. The data for the segment exceeds the maximum length. The data was truncated. |
User Response: | Check the data for the segment specified in the message. Correct the length of the data for the next session run. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The recovery cache folder in the session properties is invalid. |
User Response: | In the session properties, specify a recovery cache folder. |
Explanation: | The Integration Service could not configure recovery for the session. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service failed to cache the SAP IDoc. The Integration Service might have written only part of the IDoc to the recovery cache before the session failed. |
User Response: | Check the additional error message for more information. |
Explanation: | This is an informational message. The Integration Service truncated the last IDoc in the cache. |
User Response: | None. |
Explanation: | The Integration Service could not truncate the last IDoc in the cache. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service could not cache an IDoc. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service could not commit IDocs to the target when it reached the session condition(s) you specified in the session properties. The session failed. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service could not flush the cache. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service could not read the cached IDoc. The cache might contain inconsistencies. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service could not commit IDocs to the target at the end of the Real-time Flush Latency interval. The session failed. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service could not read the message from the recovery cache. |
User Response: | Check the additional error message for more information. |
Explanation: | The metadata file used to create the SAP/ALE IDoc Interpreter transformation may be invalid. |
User Response: | Recreate the SAP/ALE IDoc Interpreter transformation. |
Explanation: | There is not enough memory on the node where the Integration Service process runs to process the IDoc data in the SAP/ALE IDoc Interpreter transformation. |
User Response: | Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. |
Explanation: | There is not enough memory on the node where the Integration Service process runs to process the IDoc data in the SAP/ALE IDoc Interpreter transformation. |
User Response: | Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. |
Explanation: | There is not enough memory on the node where the Integration Service process runs to process the IDoc data in the SAP/ALE IDoc Interpreter transformation. |
User Response: | Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. |
Explanation: | There is not enough memory on the node where the Integration Service process runs to process the IDoc data in the SAP/ALE IDoc Interpreter transformation. |
User Response: | Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. |
Explanation: | There is not enough memory on the node where the Integration Service process runs to process the IDoc data in the SAP/ALE IDoc Interpreter transformation. |
User Response: | Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. |
Explanation: | You configured the session to validate inbound IDocs before writing them to the SAP system. The Integration Service determined that a value for the mandatory segment in the IDoc is missing. |
User Response: | Verify that the SAP/ALE IDoc Prepare transformation for the inbound IDoc contains values for the mandatory segment. |
Explanation: | You configured the session to validate inbound IDocs before writing them to the SAP system. The Integration Service determined that the segment contains more than the allowed number of records. |
User Response: | Correct the source data so that the number of records for the segment do not exceed the maximum number allowed. |
Explanation: | You configured the session to validate inbound IDocs before writing them to the SAP system. The Integration Service determined that the segment contains less than the minimum number of records allowed. |
User Response: | Correct the source data so that the number of records for the segment meet the minimum number of records allowed. |
Explanation: | Data for the primary or foreign key fields is missing. |
User Response: | Make sure the data contains primary and foreign keys. |
Explanation: | Data for the connected fields in the named segment is missing. |
User Response: | Make sure the data exists for the connected fields in the named segment. |
Explanation: | The SAP/ALE IDoc Prepare transformation received data that is larger than the precision for the row. |
User Response: | Correct the source data so that the value matches the precision for the row. |
Explanation: | The SAP/ALE IDoc Prepare transformation received orphan rows. The session fails if the Orphan Row Handling session property is set to Error and the error count has exceeded the error threshold. |
User Response: | Verify that all child rows have parent rows. |
Explanation: | The SAP/ALE IDoc Prepare transformation received duplicate rows. |
User Response: | Eliminate the duplicate rows in the data. |
Explanation: | The SAP/ALE IDoc Prepare transformation received orphan rows. The session fails if the Orphan Row Handling session property is set to Error and the error count has exceeded the error threshold. |
User Response: | Verify that all child rows have parent rows. |
Explanation: | The SAP/ALE IDoc Prepare transformation received duplicate rows. |
User Response: | Eliminate the duplicate rows in the data. |
Explanation: | The SAP/ALE IDoc Interpreter transformation received IDoc data that is less than the fixed length of 1,063 characters for each segment. |
User Response: | Correct the source data so that it equals 1,063 characters for each segment. |
Explanation: | One or more input groups in the SAP/ALE IDoc Prepare transformation are not connected. |
User Response: | Make sure that all input groups are connected. |
Explanation: | There is not enough disk space to perform the desired operation. |
User Response: | Check the disk for free space. |
Explanation: | The session is configured to validate outbound IDocs and write invalid IDocs to a relational or flat file target. The Integration Service determined that a value for the mandatory segment in the IDoc is missing. |
User Response: | Correct the source data so that the mandatory segment contains values. |
Explanation: | The session is configured to validate outbound IDocs and write invalid IDocs to a relational or flat file target. The Integration Service determined that the segment contains more than the allowed number of records. |
User Response: | Correct the source data so that the number of records for the segment do not exceed the maximum number allowed. |
Explanation: | The session is configured to validate outbound IDocs and write invalid IDocs to a relational or flat file target. The Integration Service determined that the segment contains less than the minimum number of records allowed. |
User Response: | Correct the source data so that the number of records for the segment meet the minimum number of records allowed. |
Explanation: | The outbound IDoc session contains an SAP/ALE IDoc Interpreter transformation created in version 7.x. The Extended Syntax Check session property is selected. However, the Integration Service cannot validate outbound IDocs for an SAP/ALE IDoc Interpreter transformation created in earlier versions because the transformation does not contain an Error Output port. |
User Response: | Recreate the SAP/ALE IDoc Interpreter transformation. |
Explanation: | The cache directory specified for the SAP/ALE IDoc Prepare transformation does not exist. |
User Response: | In the session properties, enter a valid directory for the Cache Directory property. |
Explanation: | The cache size specified for the SAP/ALE IDoc Prepare transformation is inadequate. |
User Response: | In the session properties, increase the cache size. |
Explanation: | The source in the inbound IDoc mapping does not contain valid data for the IDoc control record. |
User Response: | Verify that the source data contains valid control record data. |
Explanation: | The SAP/ALE IDoc Interpreter transformation received orphan rows. The session fails if the Orphan Row Handling session property is set to Error and the error count has exceeded the error threshold. |
User Response: | Verify that all child rows have parent rows. |
Explanation: | The SAP/ALE IDoc Interpreter transformation received an orphan row. The session fails if the Orphan Row Handling session property is set to Error and the error count has exceeded the error threshold. |
User Response: | Verify that all child rows have parent rows. |
Explanation: | The SAP/ALE IDoc Interpreter transformation received duplicate rows. The transformation uses the segment number as the primary key to detect duplicate rows. The segment number is part of the header data for each segment data row that the transformation receives for the IDoc message. |
User Response: | Verify that each segment in the IDoc message has a unique segment number. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The SAP_ALE_IDoc_Writer application connection object contains invalid values for one or more connection parameters. |
User Response: | Enter correct values for the connection parameters in the SAP_ALE_IDoc_Writer application connection object. |