Most Common Questions For View PDF/Communicate Purchase Order/Agreement to Supplier (Doc ID 1392241.1)

Last updated on AUGUST 12, 2022

Applies to:

Oracle Fusion Purchasing - Version 11.1.11.1.0 and later
Oracle Fusion Purchasing Cloud Service - Version 11.1.11.1.0 and later
Information in this document applies to any platform.

Purpose

View PDF refers to the action where you can view the PDF of a document from UI pages like Manage Order, View Agreement, and View Change Order.

Communicate Documents is used to communicate purchase orders or agreements to suppliers. This can be done through one of these options - submitting a document with valid communicate parameters for approval, Communicate Purchasing Documents ESS UI or by selecting the communicate control action from the manage and view document pages.

Issues in these flows usually arise either when the PDF of the document could not be generated or the communication is not set up properly. The e-mail communication to the Supplier will happen in the language defaulted from the following sources in the following order:

1. Supplier Site
2. Procurement Configuration for the Procurement BU
3. Base language of the application instance

There are 2 components in the pdf that gets translated to the language defaulted.

1. Purchase Order Data
For the Purchase Order Data to appear in the defaulted language on the pdf, the instance should have that defaulted language as one of the installed languages, so that there will be data available in the database tables in that language.

2. Labels in the RTF Template
For the Labels in the RTF Template to get translated to the defaulted language, the translations should be uploaded to the BI Publisher against the RTF Template in that locale.

    Make sure to upload the xlf file to the right language locale. (e.g. Swedish   locale, if you picked Swedish as the langauge on the Supplier Site Address.

    In the translation xlf file, have the source language as the default locale on the setup(e.g; English - "en-US") and the target-language as the language for which you are uploading the translations.

The Source and Target tags in the xlf file should have the values in the languages as mentioned above.
    e.g;
     <source>Phone</source>
   <target>Telefon</target>