Which is NOT a required piece of information when importing contract header Information from a source file?

When importing contract data using the "Revenue Management Source Document" FBDI template, the system requires a unique identifier for each source document. The template provides five fields for this purpose: SourceDocumentUniqueId1 through SourceDocumentUniqueId5. While at least one of these fields must be populated to ensure the document is unique within the source system, the Source Document Unique Identifier Number 1 field itself is not mandatory. You could populate SourceDocumentUniqueId2 instead, as long as the overall combination is unique.

A. The Date of Source Document is required to establish the contract's timing and is a mandatory field (SOURCEDOCUMENTDATE).

B. The Source Document Type code is required to classify the transaction (e.g., sales order, invoice) and is a mandatory field (SOURCEDOCUMENTTYPECODE).

C. The Record Type is a mandatory technical field (RECORDTYPECODE) used by the import process to distinguish header, line, and other record types.

D. The Source System is required to identify the origin of the data and is a mandatory field (SOURCESYSTEMCODE).

E. The Currency code is essential for any financial transaction and is a mandatory field (CURRENCYCODE).

Oracle Help Center

File-Based Data Import (FBDI) for Oracle Financials Cloud

24B

Document: Revenue Management Source Document Import. The associated FBDI template (VrmSourceDoc.xlsm) and control file definitions show that SOURCEDOCUNIQUEIDENTIFIER1 is a nullable column in the VRMSOURCEDOCSINTERFACE table.

Oracle Enterprise Repository for Oracle Fusion Cloud Applications

Database Table: VRMSOURCEDOCSINTERFACE. The table definition explicitly lists SOURCEDOCUNIQUEIDENTIFIER1 as nullable

whereas fields like SOURCESYSTEMCODE

SOURCEDOCUMENTDATE

and CURRENCYCODE are defined as NOT NULL.