Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: WRF_AT - Messages for Allocation Table RTFASH
Message number: 201
Message text: Goods receipt date is not valid. Check this in the site delivery phase
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
WRF_AT201
- Goods receipt date is not valid. Check this in the site delivery phase ?Certainly! Here's a detailed explanation for the SAP error message WRF_AT201: Goods receipt date is not valid. Check this in the site delivery phase:
Error Message:
WRF_AT201 - Goods receipt date is not valid. Check this in the site delivery phase
Cause:
This error typically occurs during the Goods Receipt (GR) process in SAP, especially in scenarios involving project systems, plant maintenance, or delivery processing where the system validates the goods receipt date against certain business rules or master data settings.
The main reasons for this error are:
Goods Receipt Date Outside Allowed Posting Period:
- The GR date entered is outside the open posting periods defined in the system for the relevant plant or company code.
Goods Receipt Date Not Matching Delivery or Project Dates:
- The GR date does not align with the delivery schedule or project phase dates (e.g., site delivery phase).
- In project-related deliveries, the GR date must fall within the project or site delivery phase dates.
Incorrect or Missing Date Configuration:
- The site delivery phase or project system phase dates are not maintained or incorrectly maintained.
- The system checks the GR date against these phases and throws an error if the date is invalid.
Custom Validation or User Exit:
- There might be custom validations or user exits implemented that enforce stricter date checks during the goods receipt.
Solution:
To resolve the error, follow these steps:
Check Posting Periods:
- Verify that the goods receipt date falls within an open posting period.
- Use transaction MMPV or OB52 to check and open the relevant posting periods if necessary.
Verify Site Delivery Phase Dates:
- Check the site delivery phase or project phase dates in the relevant project system or delivery document.
- Ensure that the GR date is within the allowed date range.
- Use transactions like CJ20N (Project Builder) to check project phases and their dates.
Adjust Goods Receipt Date:
- If the GR date is incorrect, adjust it to a valid date within the allowed range.
Check Custom Validations:
- Review any custom user exits or BAdIs that might be validating the GR date.
- Examples include user exits in MM or project system modules.
- Coordinate with your ABAP team if custom code adjustments are needed.
Reprocess the Goods Receipt:
- After correcting the date or configuration, retry the goods receipt posting.
Related Information:
Transactions:
Modules Involved:
Notes and Documentation:
Aspect | Details |
---|---|
Cause | GR date outside allowed posting period or site delivery/project phase date range. |
Solution | Verify and correct posting periods, project phase dates, and GR date; check custom code. |
Key Transactions | MIGO, CJ20N, OB52, MMPV |
Modules | MM, PS, SD |
If you provide more context (e.g., module, transaction, or scenario), I can help tailor the solution further.
Get instant SAP help. Sign up for our Free Essentials Plan.
WRF_AT200
Select an item in the Allocation Instruction list
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
WRF_AT199
System error; plausibility errors still exist before alloc. table posting
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
WRF_AT899
Quantities are too large (quantity field overflow)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
WRF_AT_GENERAL001
Delivery date (seasonal scheduling) for dist. center &1 shifted to &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.