Message type: E = Error
Message class: PG - Error Messages for Master Data Programs
Message number: 269
Message text: Record is not saved. Identical record already exists
You are creating an Additional Actions (0302) record. An identical
record (action type, action reason) already exists for this date.
This record will not be stored in the Additional Actions infotype
(0302).
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
PG269
- Record is not saved. Identical record already exists ?The SAP error message PG269, which states "Record is not saved. Identical record already exists," typically occurs when you are trying to create or save a record in the system that is considered a duplicate of an existing record. This is a common validation check in SAP to maintain data integrity and prevent duplicate entries.
Cause: Duplicate Entry: The most common cause is that the record you are trying to save has the same key fields as an existing record in the database. This could be due to: Attempting to create a new entry with the same unique identifier (e.g., material number, vendor number, etc.). Data being imported or uploaded that contains duplicates. Configuration Settings: Certain configurations in the SAP system may enforce strict checks for duplicates based on specific fields. Data Migration Issues: If data is being migrated from another system, it may inadvertently contain duplicates.
Solution: Check Existing Records: Before creating a new record, check the
Get instant SAP help. Sign up for our Free Essentials Plan.
PG268
This record can only be maintained using the Actions infotype (0000)
What causes this issue? An 'Actions' record (0000) exists for this 'Additional Actions' record (0302). You must therefore maintai...
PG267
Info group could not be updated
What causes this issue? An error has occurred while updating the info group.System Response The system issues an error message and will not allow yo...
PG270
Correct Action function can only be used for entry and leaving actions
What causes this issue? The <LS>Change Entry/Leaving Date</> function (transaction PA41) may only be used for entry and leaving actions. ...
PG271
Wage type &1 is not permitted on &3 for infotype "&4"
What causes this issue? There is no entry for &V1& wage type on &V3& under the current <DS:DE.MOLGA>Country Grouping</> (...
Click on this link to search all SAP messages.