If you are using the built-in SAP workflow inbox of the SAP EDI process, whoever accepts the idoc from an errored status into SAP as a booked order can make corrections without having to modify EDI or Idoc data; just the resulting order reflects the change. As Denise says, managing the order date is the job of customer service, therefore they should also know that if you are modifying an order, e.g. quantity, you should speak with the customer to ensure that they are agreeing to the change, and they are making the same change in their system (so that your invoice does not get rejected for failing to match the order, and because by shipping against the order you have accepted the order and its terms as sent).
If the correction needed is to an order already booked into SAP, and was not the type of error that would cause the Idoc to go to the workflow inbox, then customer service can modify it in SAP which does have appropriate change logging. I guess I don't understand the question because - No, Customer Service should not have to modify EDI raw data or external Idoc data, and rarely internal Idoc data (e.g. the error had to do with cross reference or conversion tables required to process the data into SAP and not actually the EDI order data as sent by the customer). - Yes Customer Service should be able to process failed transactions into SAP from the workflow inbox (without requiring a custom transaction) - Yes Idoc data can be edited without use of a custom transaction when required to allow the document to successfully process through the workflow process. - Only under rare circumstances should you have to change data outside of SAP and process it back in (and this would be beyond the scope of Customer service personnel). E.g. A trading partner will not send you a document again once you have received and acknowledged it; they figure it is up to you to handle it. With customer service getting approval as to the changes required, technical staff can correct the order and send it back in (process a modified copy of the EDI data, or correct a copy of the Idoc file). Appropriate followup should be had with the Trading Partner to correct the issue for future transmissions as this can not be a normal mode of doing business. Ken ----- Original Message ----- From: Denise Tate To: [email protected] Sent: Thursday, December 14, 2006 3:36 PM Subject: RE: [EDI-L] Letting Customer Service Modify Data - SAP or EDI? - Opinions Please Allowing Customer Service to modify the data after it is in SAP is basically their job. If a customer ordered incorrect case qty, the order will have to be modified before shipping, whenever it is done. I am opposed to altering the raw data as it came in. I agree it is a contract. As long as you have audit records showing you processed the data into your SAP application, if it bombs after it is processed is another departments responsibility. When I first jumped into EDI, I was told EDI just "processes" or "passes" the data, EDI doesn't alter the data. I have held to that premise of not altering the data and it has helped me over the years protect my job. By the time the order is ready to ship and invoice, hopefully, Customer Service will have corrected the issues via contact with the customer. Just my 2 cents. Denise -----Original Message----- From: Travis Truax [mailto:[EMAIL PROTECTED] Sent: Thursday, December 14, 2006 1:44 PM To: 'phoenixedi'; [email protected] Subject: RE: [EDI-L] Letting Customer Service Modify Data - SAP or EDI? - Opinions Please Are you sure your customers wil allow it? As Chris mentioned - it is a contract. If we changed our customers' quantities, when we went to invoice them - they would reject the "incorrect" quantity (even though it is closer to correct than what they sent.) Same goes for item codes. It doesn't matter if what they ordered doesn't exist- they aren't going to pay for some line item that is not on the PO... Travis- -----Original Message----- From: phoenixedi [mailto: [EMAIL PROTECTED] <mailto:phoenixedi%40yahoo.com> com] Sent: Thursday, December 14, 2006 12:05 PM To: [EMAIL PROTECTED] <mailto:EDI-L%40yahoogroups.com> com Subject: [EDI-L] Letting Customer Service Modify Data - SAP or EDI? - Opinions Please We run SAP and TLE, and we currently do not allow our customer service reps to modify any IDOC or EDI data. Our Director of Customer Service wants them to be able to edit any "failed" data that comes in. For example, if a customer orders an item in a wrong quantity (they order 11 when it has to be 12), the order will fail in SAP and the CSR's will see it on a custom SAP transaction. They want to be able to fix the data and then reprocess it. My suggestion is to do it in SAP with a custom transaction, but I wanted to cover all options. I don't think modifying the data outside of SAP and processing it back in is a good solution, but I'm open to what other people are doing. Thanks. ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix. Yahoo! Groups Links [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
