Goto TCODE: SCDO with this object name: EINKBELEG. One example of how print-relevant PO document changes been triggeredįirst, look up why the output for PO 5504023487 at PO messages was triggered at 02-14-2019 22:06:03.Ĭheck the PO header/item changes at the triggered time inside ME23N, which change document object is EINKBELEG.
Obviously, new PO creation, PO display/print preview shouldn’t trigger printout. The first thing is the mode of Print Operation of PO: new PO creation, PO changes or PO display/preview will function differently.And field XBEST is the indicator of whether active this field for printout.īesides, there’re several aspects that determine whether to trigger PO printout (include email been send out). accordingly, as well as address table ADRC.
T166C is the key table to control print-relevant PO changes, it’s been used to check changes at field level include header level/item level/schedule line item level against table EKKO/EKPO/EKET, etc. SAP Standard: Fields Relevant to Printouts of Changes (TCODE: OMFS)Ĭustomized settings of Fields Relevant to Printouts of Changes are stored at the T166C table. SAP System already provides an excellent solution with transaction OMFS, where you can maintain a combination of table name and table fields along with control flags to control whether PO printout should be triggered or not.īut customer demand never stops: what if some organization wants to get email notifications for specific changes while other organizations don’t? This article will try to introduce the mechanism of print-relevant PO document changes and some tips when extending it to the organization level. It would be great if anybody can give me a basic logic for matching my requirements.After Purchase Order been created at the system, the relevant users should get notice email if any important fields been changed like net price, delivery address, items, etc. I had already referred the post #109383 which is similar to my requirement but there are some differences. However, again same rule applied that the supplier with N POs will receive N emails as explained in Point 1. The JDE system probably will retrieve all the suppliers of the selected POs and perform the batch job email sending. However, is there any possibility to have batch POs selection and email sending feature? Example, the end user will select a list of all the POs of the day and then send them all in one time. Lastly, above scenario is on one-by-one basis, which mean the PO is being sent one by one for each supplier. Also, the archived PO should be named with its PO number for easy reference.Ĥ. Also, the POs that being emailed should be archived at somewhere, such as either at our local shared directory or public shared + secured directory because the end user might need to track and retrieve/refer to it in future, such as when the supplier claims that they did not received email + PO from us. Perhaps there is a searchable report for them to retrieve the history of the email + PO being sent.ģ. Whenever there is a PO emailed to the supplier, JDE will need to keep track of the email sent such as when, who and how many times it has been sent. Best if there is any feature to know that the recipient has received or read the email sent by us.Ģ. The email probably can be differentiated by the PO number at the email subject and attachment(.pdf) name. If there supplier is having 5 different POs, JDE will send 5 different emails and each is having different PO being attached. Once the PO is validated and approved, the end user will have the feature (eg: button) to email the PO to the relevant supplier. Please check it out and let me know whether it is possible in JDE or Do we need to use any other third party tools to do the trick?ġ. I have the following requirement from my user.
0 kommentar(er)
