Symptom
- In app Mass Changes to Purchase Scheduling Agreement when selecting multiple SAs by item and click on Mass Edit, when clicking on Value Help of Delivery address, the system does not recognize an address even if they are maintained at company code level, plant level, shipping point level.
- No manual maintenance possible either.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Access app Mass Changes to Purchase Scheduling Agreements.
- Select multiple Scheduling Agreements and click on Scheduling Agreement Items.
- Click on Mass Edit button.
- Search for Delivery address on item fields.
- Click on Value Help and see no proposed addresses by the system.
- Try to manual maintain Delivery address and system pops out message "Invalid entry".
Cause
Popup reads exclusively from table BUT052 (BP Relationship: Addresses):
- A BP relationship must exist in BUT050.
- That relationship must have an address record in BUT052.
Resolution
To maintain the required entries in BUT052 (Business Partner Relationship Address), please refer to KBA 3467309 - BP contact person is created with data in BUT051 but when synched with customers it updates BUT052 and follow the steps below:
- Open the Maintain Business Partner Master Data app.
- Open the relevant Business Partner.
- Create or maintain a Contact Person relationship for the Business Partner.
- Open the Contact Person relationship.
- Navigate to the Address Data section.
- Select Assign Company Address.
- Choose the required company address and save the relationship.
- Save the Business Partner changes.
- Retest the scenario in Mass Changes to Purchase Scheduling Agreements (F2668) and check whether the Delivery Address value help returns entries.
See Also
KBA 3467309 - BP contact person is created with data in BUT051 but when synced with customers it updates BUT052
Keywords
contact relationship, but051, bur001, but052, synchronize, migration, fiori , KBA , MM-FIO-PUR-SQ-SCH-CL , Fiori UI for Manage Scheduling Agreements (Public Cloud) , Problem
SAP Knowledge Base Article - Public