P Card Test
P Card Test
(Doc ID
2713492.1)
Here are example steps to create a P-CARD - This has to be done in Financials:
Setup P-Card having Company Pay Option in fusion expense (Doc ID 2532513.1)
STEP 1: Create a SQL*Loader program that uses the flat file provided by the card issuer
containing the credit card transaction details you want to transfer into the
AP_EXPENSE_FEED_LINES_ALL table.
STEP 7: Select the Procurement Card check box to indicate that the supplier site is P-Card
enabled.
STEP 9: After that upload the data through the SQL Loader Program, then run the
"Procurement Card Transaction Validation Program" Request.
Navigation: Payable Super User--> View--> Request
STEP 10: Run the other Requests:
Navigation: Payable Super User--> View--> Request "Create Procurement Card Issuer
Invoice"
"Payables Open Interface Import with source"
Source Parameter as "PCARD"
How to import Contract Terms and Conditions using FBDI Import Management?
Currently Import Management (standard uploading functionality) does not support import
contract terms and conditions, (the clauses to a contract). Users can import clauses, values
sets, and manual user variables from external sources into the Contract Terms Library by
importing the data from an XML file.
Office Documentation:
https://docs.oracle.com/en/cloud/saas/sales/22b/fascc/how-you-import-clauses-into-the-
contract-terms-library.html
What are the steps to migrate all the contract clauses from one environment to
another.
SOLUTION
The only way to import clauses is through XML, but I am giving you some information
that can ease your work:
1. Steps on how to generate an XML file for existing clauses, to then use for the import:
1. Run the following SQL script against the DB to export the Clause information
SELECT DISPLAY_NAME,
ARTICLE_INTENT,
A.ARTICLE_LANGUAGE,
ARTICLE_TYPE,
ARTICLE_STATUS,
ORG_ID,
ARTICLE_DESCRIPTION,
ADDITIONAL_INSTRUCTIONS,
PROVISION_YN,
GLOBAL_YN,
LOCK_TEXT,
INSERT_BY_REFERENCE,
REFERENCE_SOURCE,
REFERENCE_TEXT,
DEFAULT_SECTION,
ARTICLE_TEXT,
START_DATE,
END_DATE,
AV.ATTRIBUTE_CATEGORY,
AV.ATTRIBUTE1,
AV.ATTRIBUTE2,
AV.ATTRIBUTE3,
AV.ATTRIBUTE4,
AV.ATTRIBUTE5,
AV.ATTRIBUTE6,
AV.ATTRIBUTE7,
AV.ATTRIBUTE8,
AV.ATTRIBUTE9,
AV.ATTRIBUTE10,
AV.ATTRIBUTE11,
AV.ATTRIBUTE12,
AV.ATTRIBUTE13,
AV.ATTRIBUTE14,
AV.ATTRIBUTE15,
ARTICLE_TYPE,
ARTICLE_DESCRIPTION,
END_DATE,
INSERT_BY_REFERENCE,
ADDITIONAL_INSTRUCTIONS,
ARTICLE_NUMBER,
PROVISION_YN,
START_DATE,
ARTICLE_TITLE,
ARTICLE_TEXT
FROM OKC_ARTICLES_ALL A, OKC_ARTICLE_VERSIONS AV
WHERE A.ARTICLE_ID = AV.ARTICLE_ID
2. You use the information generated in point 1 and follow the steps in the
documentation to create your XML:
Understanding Fusion Enterprise Contracts Data Import (Doc ID 2151576.1) - here you
can find a sample
Spend Classification
Use “Start Spend Classification scheduled process to begin the process of classifying spend data
When to Use
Use this process periodically when you want to classify the different types of spend
transactions. Submit the scheduled process to classify spend data, without having to
navigate to the spend classification work area.
Role:
Procurement Data Analyst
(ORA_POI_PROCUREMENT_DATA_ANALYST_ABSTRACT)
Privilege:
POI_ADMINISTER_SPEND_CLASSIFICATION_PRIV
POI_MANAGE_SPEND_CLASSIFICATION_BATCH_PRIV
POI_SPEND_CLASSIFICATION_WORKAREA_PRIV
Import po’s
Use the Import Orders scheduled process to import purchase orders
Privileges Required
Verify that you have the following role or privilege:
Role:
ORA_PO_PROCUREMENT_INTEGRATION_SPECIALIST_JOB
Privilege:
PO_IMPORT_PURCHASE_ORDER_PRIV