SES Creator Assignment and Notification Based on PO Creation Scenario

[Adel_Rihan]

Hello SAP Community,

I have received a requirement from the customer to control the SES (Service Entry Sheet) creator and send notifications based on how the PO (Purchase Order) is created. The key point is that this should be achieved entirely through MM configuration, with minimum ABAP developments. However, if there is no standard way to achieve this, I would appreciate suggestions on possible workarounds.

Here are the requirements:

1. PO Created with Reference to PR (Purchase Requisition)

   • The PR creator should be nominated as the SES creator.
   • The PR creator should receive a notification when the PO is created.
   • Another notification should be sent when the delivery date is reached.
   • Only the PR creator should be allowed to create the SES.

2. PO Created Without PR

   • A field should be available to nominate the SES creator.
   • The recipient field, for example, should have a search help (F4) with a list of users.
   • The entered name in the recipient field should be assigned as the SES creator.
   • The SES creator should receive notifications when the PO is created and when the delivery date is reached.

3. PO Created Without PR and Without Recipient Name

   • The system should allow any user with the appropriate role to create the SES.

4. PO Created with PR and Recipient Name

   • Both the PR creator and the recipient should be allowed to create the SES.

Looking forward to your insights. Thanks in advance!

[jagdeepsingh83 · Accepted solution]

First of all, I like the way you have detailed your requirements --It seems it will be a mix of configuration and development -Check my responses next to your requirements 

1. PO Created with Reference to PR (Purchase Requisition)

   • The PR creator should be nominated as the SES creator.---Make use of the requisitioner field as the mandatory field (via config) and make the drop-down help of UserID F4 help and validation that the user id is valid on the PR--as when you PO get created this field will flow to PO-- you can also write ABAP code where PR creator is requisitioner ID --however --user should have the ability to replace with other valid user ID 
   • The PR creator should receive a notification when the PO is created.--> This will be ABAP development --implementation of BADI 
   • Another notification should be sent when the delivery date is reached.-->This will be a program that can scheduled in the background as a job that runs daily say 7:00 am to send --you can copy existing program ME2N and send output to Requisitioner field of PO as it will be copied from PR to PO --so need to go back to PR table
   • Only the PR creator should be allowed to create the SES.--This will be a BADI --not standard

2. PO Created Without PR

   • A field should be available to nominate the SES creator.---Point 1--Requisitioner field 
   • The recipient field, for example, should have a search help (F4) with a list of users.--Point 1--Drop-down F4 help to requisitioner  field --allow you select different user --
   • The entered name in the recipient field should be assigned as the SES creator.--This now known you do not additional field as SES creator as you using the standard requisitioner field available.
   • The SES creator should receive notifications when the PO is created and when the delivery date is reached.

3. PO Created Without PR and Without Recipient Name

   • The system should allow any user with the appropriate role to create the SES.--This is enhancement and BADI for SES creation validation against the requisitioner field.

4. PO Created with PR and Recipient Name

   • Both the PR creator and the recipient should be allowed to create the SES.--this is again the enhancement in SES transaction --BADI implementation or User Exit.