Symptom
The My Purchase Requisitions - New app(F1639A) is the successor of the apps Create Purchase Requisition(F1643) and My Purchase Requisitions(F1639) apps. As of the SAP S/4HANA Cloud 2308 update these apps were deprecated .
Environment
SAP S/4HANA Cloud Public Edition
Resolution
The following points should be considered for the new App:
- As soon as the end user launches “Create Purchase Requisition” app, new header draft will be created. It will shown in the “My Purchase Requisitions – New” app
Even if user does not add items, header draft with 0 items will be shown. This header draft should not be used in the new app - If there are any drafts created in the old “My Purchase Requisitions” app, then those drafts will be shown in the “My Purchase Requisitions – New” app These drafts should not be used in the new app
- Draft created in old Create PR / My PR app should not be edited in the My PR – New app and vice versa, If the end user tries to add a new item in the new app, for the draft created in the old app, a continuous busy indicator will be shown
- As and when a user works on a Draft document, it appears on the top of the list in the landing page (descending order of last modified). Be watchful about which Header draft radio button is selected / Mini cart is populated before Create Item is clicked
- The User defaults facet seen in the landing page is the mini version of the full-fledged application “Default Settings for Users – Purchase Requisition”.
See Also
- Refer to the following link for additional information.
- Please check out the below blog to know more about the new app.
Link - The app Create Purchase Requisition(F1643) will be deprecated as of release 2308CL.
Refer link - The app My Purchase Requisitions(F1639) will be deprecated as of release 2308CL.
Refer link
Keywords
F1643, F1643A, F1639 , KBA , MM-FIO-PUR-REQ-SSP , Fiori UI for Self Service Procurement , How To
Product
SAP S/4HANA Cloud Public Edition all versions