Symptom
When replicating Business Partner identification data using the SOAP service without providing the Validity Period element, the system raises the following error: Error 742(R1): 'Enter a Valid To date.'
Environment
SAP S/4HANA Cloud Public Edition
Cause
- The error occurs because of how the system processes existing Business Partner identification records depending on the Complete Transmission Indicator (CTI).Identification records are stored in the table, where the Valid From date is part of the record's primary key.
- The system behaves differently depending on whether CTI is set to false or true.
Scenario 1: CTI = false
- When CTI is set to false, the system does not delete existing identification records. Instead, it attempts to update the existing records while retaining the Valid From date stored in the database.
- If the incoming payload does not contain the Validity Period element, the Valid To date remains empty. Since the existing record has a Valid From date but no Valid To date, the system raises error 742(R1).
Scenario 2: CTI = true
- When CTI is set to true, the system deletes the existing identification records and inserts the incoming records as new entries.
- If the incoming payload does not contain the Validity Period element, both the Valid From and Valid To dates remain empty. In the described scenario, this does not trigger error 742(R1).
Resolution
When sending Business Partner identification data with CTI set to false, always provide both StartDate and End Date in the Validity Period element for every Identification node.Ensure that the dates are valid for the identification record being replicated.
Sample XML Payload
<Identification actionCode="04">
<PartyIdentifierTypeCode>BUP005</PartyIdentifierTypeCode>
<BusinessPartnerID>7282404000</BusinessPartnerID>
<ValidityPeriod>
<StartDate>2026-09-07</StartDate>
<EndDate>2026-10-31</EndDate>
</ValidityPeriod>
</Identification>
See Also
Keywords
effective dating, end dating, open-ended period, date interval closure, temporal validity check, primary key with date, upsert behavior, delta load, full load replace, payload omission, required end date, record lifecycle, time-sliced records, versioned identifiers, overlapping period handling , KBA , LO-MD-BP-WS , Web Service for Business Partner , Problem
SAP Knowledge Base Article - Public