264889
264889 AA-7R69FU POC - POD delete functionality
Copyright OBS Logistics © 2009
The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied
FUNCTIONAL OVERVIEW
Client Requirement
Now user can not amend on a POC-POD record once posted successfully in SAP. This has been noticed that some times POC-POD done via system mistakenly or any other reason but physically material is either still needs to be collected or delivered. In this scenario user is unable to amend any thing on collection / delivery information (e.g. Actual Date-time, Actual quantity etc);
We were raising an EARS call before in order to delete the POC-POD manually by MTS Support Team and now it seems we must have this functionality available with in the MTS. Not all but few users will be having an access to delete the POC – POD record. Currently we require this for selected users only; for IT Super User only.;
21-04-09 (AK) : We do not need message transaction between MTS and SAP on POC-POD deletion. Aramco will delete the POC - POD manually in SAP and then inform us to delete the POC - POD from MTS.;
21-04-09 (AK) : User should be able to resend the POC-POD with the correct information once deleted from MTS.;
30-04-09 (AK) : Aramco first delete the POC - POD from SAP and then Exel delete from MTS so there will be no conflict in SAP.
Solution
The delete POC/POD function will be accessible from the TRIPDTL screen (see functional description for example) If the user has the correct privileges (i.e. IT Super User) a button will be visible and enabled call “Delete POC/POD”. Clicking this will display a new canvas showing the following record details:
•Actual Dispatched Quantity •Actual Delivered Quantity •Actual Arrival Date/time •Actual Depart Date/time •POC Flag •POD Flag •Badge Number (POD Name) •A non-conformance button •The comments field on the SCH_HAULAGE_ACTIVITY table will be used to hold any comments.
The record will be able to be resent (if Aramco have not removed the original the entry will fail MTS unable to verify records have been deleted from SAP.).
Scope
This change will be applied to system version 10.4.7 on SARTST and once approved SARPRD
SET-UP
Pre-requisites
None
Menu Structure
Unchanged
Data
A new function ‘”DELETE_POC_POD” will be created. This function will be controlled by adding entry in table ADM_FN_ACCESS only giving access to group_name IT SUPERUSERS and ADMIN.
FUNCTIONAL DESCRIPTION
Existing Functionality
Using an existing booking reference: “20012089700010500” as an example we are going to delete the successful POC. (at Collection Point PK)
From here the user selects the button “View Trip”
This will display the trip
Now go to record in question (booking_ref 20012089700010500)
If the user right-mouse clicks on a field it brings up a sub-menu. The menu item ‘Show Detail’ is not in use by Aramco, therefore this will be adapted to handle Delete POC/POD functionality and be renamed Delete POC/POD. This will only be accessible to Super Users.
New Functionality
Delete functionality will only be accessible to limited users.
If a user has permission to delete POC/POD a canvas will display allowing users to amend the record and save, this will mark the current record as “DELETED” and create another replacement POC/POD.
When the record has been saved, the result will be able to be viewed in the INT_ERR screen
When POC/POD the outbound message will be updated with username and time of deletion e.g.. “POC/POD Deleted by ABDULQADIRA on 22/06/2009 09:00:00 by delete function in TRIPDTL”
When POC/POD the acknowledgment record message will be updated with username and time of deletion e.g.. “POC/POD Deleted by ABDULQADIRA on 22/06/2009 09:00:00 by delete function in TRIPDTL” PLUS the Status Message will be set to “POC/D Deleted.”
All changes will be written to the TRIP audit table and ADM_LOG to enable monitoring.
Functionality not in scope for this change.
•Revenue Accounting Module:No change •Exports for POC/POD(e.g. SAR POC POD Validation, SAR POC POD Acknowledgement Exceptions):No change. •If Aramco/SAP have not removed the original the entry, and second POC/POD sent the record will fail within SAP, this is not within scope as MTS is unable to verify records have been deleted from SAP.
References
| EST-264889 | Est-265889 RIO AA-FR69FU POC-POD delete functionality v1.0.doc | 1.0 | 11/05/08 |
Document History
| 0.1 | 11/06/09 | Draft | Initial version | CBW |
| 1.0 | 15/06/09 | Issue | Reviewed and Issued | MJC |
| 2.0 | 23/06/09 | Issue | Issued | C2W |
| 2.1 | 30/06/09 | Draft | Revised after correspondence from AK | C2W |
| 3.0 | 01/07/09 | Issue | Reviewed and Issued | MJC |
Authorised By
| Matt Crisford | Development Manager | |
| Suk Sandhu | TMSCC MTS Product Manager |
