-
Hi SamT 
No there no way to identify them together because the outcome of SAP is identified with only my name/or one's of my team an the date.
- I receive the prices via email (many emails to be precise) to be uploaded for the next month one week before month end in the request form that you know, I do a first check to get read of the very gross errors (typos for example)
- I transfer the content of the request in a template that can be processed by the MUT.
- I upload everything via MUT.
- I have then a windows of one week to check for errors in SAP.
- I get out of SAP an extract of all the prices upload for a given date (all those for next month usually)
- I check the extract or errors.
My (yours too) tool is meant:
- to check errors in the request sheet2 (even after the upload , that doesn't matter because prices are for the next month) that way I can understand whether the error comes from a wrong request or from the faulty upload tool.
- to check out if what requested is actually what we have in the system (by comparing the two sheets)
- to Spot not Requested Records
You have noticed that the tool gives the message NOT Requested when in the SAP extract you have a record that wasn't in the request, that is because in SAP there are some prices records (funny ones) created when someone tries to place an order for a piece that doesn't have a prices record yet.
Last edited by isasa74; 10-31-2015 at 02:57 PM.
Reason: typos
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules