Replies to This Discussion

Permalink Reply by Miriam Moore on May 19, 2010 at 2:01pm

Yes! We have had this exact experience, though we send our emails to ourselves and then forward the email to the vendor. We've gone through phases where some PDFs are not attached. I'll have to do some research as it hasn't happened in a while. What versions are you on? We are on PS 8.8 and PeopleTools 8.46. I'll post more later.

Follow up question: the reason we send the emails to ourselves and then forward them is that we have firewalls around PeopleSoft and have problems sending files from PS to outside the firewall. What is your setup?

Permalink Reply by Miriam Moore on May 20, 2010 at 1:19pm

Cynthia -

I looked back on our case and found what resolved it for us. This is the solution we got from PS Development. When we did this setup the problem was resolved. Hope this is helpful for you.

For every business unit taken for dispatch processing, the file directory server will be assigned based on the SETID for that BU.Please ask the customer to check the following setup values for the BU’s used.

Go to the navigation PeopleTools>Utilities à Administration>TableSet Control.
Enter the BU name as the setcontrolvalue (eg. IDRBS, ORRBS etc). Find the Record Group ID “FS_34” in the table. Note the SETID in the row.
Go to the navigation Setup Financials/Supply chain>Common Definitions> File Locations and Images>File Locations. Enter the SETID noted in the above step. If you get any values, then check whether you have a valid file location setup for the file extensions “EMA” and “TMP”(Ensure that is a fully shared path). This path is very much needed to store the output file temporarily before attaching to your email.
In case, if the file location is not setup for that SETID, then create a File location for that SETID and enter the file location for the file extensions “EMA” and “TMP”.

Let me know if you have any questions.
Miriam

Permalink Reply by Cynthia Trevino on May 24, 2010 at 11:22am

Thanks Miriam. These settings are there and we still experience the problem intermittently. We are now thinking it is a hardware issue with the server. We are going to make a couple of changes and see if the problem goes away. Thanks for the input!

Miriam Moore said:

Cynthia -

I looked back on our case and found what resolved it for us. This is the solution we got from PS Development. When we did this setup the problem was resolved. Hope this is helpful for you.

For every business unit taken for dispatch processing, the file directory server will be assigned based on the SETID for that BU.Please ask the customer to check the following setup values for the BU’s used.

Go to the navigation PeopleTools>Utilities à Administration>TableSet Control.
Enter the BU name as the setcontrolvalue (eg. IDRBS, ORRBS etc). Find the Record Group ID “FS_34” in the table. Note the SETID in the row.
Go to the navigation Setup Financials/Supply chain>Common Definitions> File Locations and Images>File Locations. Enter the SETID noted in the above step. If you get any values, then check whether you have a valid file location setup for the file extensions “EMA” and “TMP”(Ensure that is a fully shared path). This path is very much needed to store the output file temporarily before attaching to your email.
In case, if the file location is not setup for that SETID, then create a File location for that SETID and enter the file location for the file extensions “EMA” and “TMP”.

Let me know if you have any questions.
Miriam

Permalink Reply by Sean Read on May 21, 2011 at 10:26am

One additional piece of configuration necessary to make this work is to tell Purchasing what file extension (and thereby what file location) is to be used for pdf's of PO's.  (despite the name, this does NOT control what file extension is actually used on the printed copy.  Navigate Set Up FSCM->Product Related->Procurement Options->Purchasing->Dispatch PO Configuration and on the "Email FIle Extension" field,  choose the EMA or TMP that you set up earlier.  We have both EMA and TMP set up and on the page where you set the actual paths, we have both the File Directory and File Directory (server) set to the same location.

Without both these, it puts the file in the local directory of wherever it's running, and since this is a two-step process (POPO005.SQR creates the attachment, followed by PO_PO_EMAIL app engine to send the email) those two "local" locations may well be different.  We found that without this config, it worked fine in our lower environments, but in Prod, with a more complex appserver config & failover servers, those two locations weren't the same, sometimes not even on the same machine.