> ## Documentation Index > Fetch the complete documentation index at: https://developers.cmicglobal.com/llms.txt > Use this file to discover all available pages before exploring further. # Create a PCI Header > ## Overview This endpoint allows for the viewing and creation of Potential Change Items header information, such as Company, Project, Scope of Work, PCI dates and more. Potential Change Items can be used to enter change requests for ongoing projects. PCIs are items that are expected to result in additional work or cost, beyond what was stated in the original submittal. These items can be made internally or externally and can be linked to requests for quotation (RFQ) and other related objects. To create PCI details, please refer to “_Create a PCI Detail_” documentation. ## UI Navigation - Enterprise > Change Management > Change Orders > Enter PCI - CMiC Field > Budget & Cost Management > Potential Change Items ## Reference Article - [Change Management - Enter PCI](https://docs.cmicglobal.com/portal/Content/E_Reference_Material/CM_-_Change_Management/Reference/Change_Orders/EnterPCI.htm) - [CMiC Field - Potential Change Items](https://docs.cmicglobal.com/portal/Content/E_Reference_Material/CMiC_Field/Reference/Budget___Cost_Management/PCIs/Potential_Change_Items.htm?Highlight=enter%20pci) ## Commonly Used Body Parameters | CMiC UI Fieldname | Name | Description | Type | Data Length | Example | Required | | --- | --- | --- | --- | --- | --- | --- | | Company Code | CmmCompCode | Company Code associated with the PCI’s project | string | 8 | “ZZ” | Yes | | Job Code | CmmJobCode | Job Code associated with the PCI’s Project | string | 10 | “23-410” | Yes | | PCI Type | CmmTypeCode | Enter/select the PCI’s type code. Must be a valid CmiC PCI type. | string | 4 | “EXT” | Yes | | PCI Code | CmmCode | PCI number identifying PCI | string | 11 | “EXT-23005” | Yes | | PCI Description | CmmName | PCI name or description | string | 200 | “Excavation Scope Change” | Yes | | PCI Date | CmmRefDate | This date is used as the reference date for the PCI in other screens, such as the Post Change Orders screen. | datetime | | “2016-05-03” | Yes | | Pre-post Status Code | CmmPrepostStatCode | Status code before posting. Must be a valid PCI status code in CMiC. | string | 10 | “APPROVED” | Yes | | Projected Amount Calc Method | CmmCalcProjAmtMethod | Flag to indicate the calculation method for projected amount when a change order is posted, and Update Projected Amount is checked. (A)dd Change Budget Amount or (R )ecalculate Projected Amount | string | 1 | “A” | Yes | | VUuid | CmmVUuid | Unique Row ID. When creating a new change item, this field should be included in the body of the request but left empty. Including this parameter allows you to preview the posting after submission. | string | 64 | “C6007D3BB3742CACE0530100007F8D31” | No | ## Other (Optional) Body Parameters | CMiC UI Fieldname | Name | Description | Type | Data Length | Example | | --- | --- | --- | --- | --- | --- | | Action Code | CmmActionCode | This is the Action Code Created by the system. Action items are used to schedule and coordinate phone calls, delivery dates, meetings and other action types relevant to the Opportunity Management module. The Action Code is used to identify the action item type. Click [here](https://support.cmicglobal.com/s/article/Action-Item-Codes) to learn more about Action Item Codes. | string | 1 | | | Allowance | CmmAllowance | Allowance Type (I)n Scope, (O)ut of Scope, (N)either. Default is N. | string | 1 | “T” | | Approved Flag | CmmAprvFlag | Idicate weather this PCI is Approved or not. Related to PCI Status Code. Y or N | string | 1 | “Y” / “N” | | Auto Calculate Markups | CmmAutoCalcMarkupFlag | Automatically generate markup lines once the PCI record has been saved. Y or N | string | 1 | “Y” / “N” | | Batch Number | CmmBchNum | Batch number associated with PCI posting | integer | 11 | “755568” | | Bid Item | CmmBiditemFlag | Flag to indicate that it is an automatic change order created by the bid item. (Y)es, (N)o, or null | string | 1 | “null” / “Y” / “N” | | Bill Method Code | CmmBillMethCode | Valid values are (D)Details or (S)Summary. If left as null, it will default to D. | string | 1 | “D” | | Change Issued Date | CmmChgSentToOwnerDate | Enter the dates the change order was issued. | datetime | | “2019-02-28” | | Change Signed Date | CmmChgSignedByOwnerDate | Enter the dates the change order was signed. | datetime | | “2019-02-28” | | PCI Class Code | CmmClassCode | PCI Class associated with the PCI type. (E )xternal, (I)nternal, (T)ransfer, (O)riginal Budget Change | string | 1 | “E” | | Classifier 1 | CmmClvValueCode1 | Classifier Value 1 | string | 16 | | | Classifier 2 | CmmClvValueCode2 | Classifier Value 2 | string | 16 | | | Classifier 3 | CmmClvValueCode3 | Classifier Value 3 | string | 16 | | | Classifier 4 | CmmClvValueCode4 | Classifier Value 4 | string | 16 | | | Classifier 5 | CmmClvValueCode5 | Classifier Value 5 | string | 16 | | | Classifier 6 | CmmClvValueCode6 | Classifier Value 6 | string | 16 | | | Control Job Code | CmmCtrlJobCode | Controlling Job Code for PCIs linked to subjobs. If the Project is associated with a controlling Job, this field should be set as “ALL” | string | 10 | “ALL” | | Cycle Number | CmmCycleNum | For reallocation PCIs only: Reallocation Cycle Number | integer | 4 | “1” | | Due to owner Date | CmmDueToOwnerDate | For reference purposes only, to indicate when this change is due to the owner. | datetime | | “2016-04-26” | | End Date | CmmEffectiveEndDate | Change Order End Date | datetime | | “2018-09-11” | | Start Date | CmmEffectiveStartDate | Change Order Start Date | datetime | | “2018-09-10” | | Global Update Date | CmmGlobalUpdateDate | Timestamp of “global” PCI update, including e.g. PCI header/details, RFQ, Notes, Attachments. | datetime | | “2024-05-29T06:15:09-04:00” | | Impact Days | CmmImpactDays | Enter number of days of impacted by change. These will print on the Change Order and calculate new finish date. | integer | 4 | “10” | | Create Date | CmmIuCreateDate | Date the record was created | datetime | | “2018-09-10T13:44:36-04:00” | | Update Date | CmmIuUpdateDate | Date the record was last updated | datetime | | “2018-09-10T13:44:36-04:00” | | Lump Sum Flag | CmmLumpsumFlag | Y = Lump Sum PCI, N= Regular PCI | string | 1 | “Y” / “N” | | Original PCI Code | CmmOrigCmmCode | Reallocation PCI only: Original PCI code being adjusted (re-allocation) | string | 11 | “EXT-001” | | Original Owner Allowance Amount | CmmOrigOwnerAllowanceAmt | Applicable only In Scope, Out of Scope Allowance Type PCI. Written only at posting time. For Out of Scope is normally 0 | number | 18 | “0” | | Owner Allowance Amount | CmmOwnerAllowanceAmt | Applicable only In Scope, Out of Scope Allowance Type PCI. For Out of Scope is normally 0 | number | 18 | “100” | | PCI Owner Change Order | CmmOwnerChgCode | Enter the Owner Change Order number associated with the Change Order. The Owner Change Order number is a reference field that will appear on Job Billing AIA style report. | string | 20 | “OCO-002” | | Pending Flag | CmmPendFlag | Pending Type associated with the PCI status code. Available options are: (A)pproved, (C )ancelled, (N) Pre-Pending, (P)ending, (R )ejected. For more details on PCI Pending Types, please refence the following article: [PCI Status Codes](https://docs.cmicglobal.com/portal/Content/E_Reference_Material/CM_-_Change_Management/Reference/Local_Tables/PCI_Status_Codes.htm?Highlight=pci%20status%20code) | string | 1 | “Y” / “N” | | Post Vendor Contracts with PCI | CmmPostContrFlag | Insert (Y), if the Subcontract associated to this PCI should be posted at the same time as the PCI; otherwise, the related Subcontract is posted separately (N). | string | 1 | “Y” / “N” | | Post Date | CmmPostDate | Date PCI was posted | datetime | | “2016-02-02” | | PCI Posted Status | CmmPostingFlag | System generated value to indicate the status of the PCI, if it its posted or unposted | string | 12 | “POSTED” | | Proposal Issued | CmmPropIssuedToOwnerDate | Date when Proposal was issued to Owner | datetime | | “2019-02-20 | | Proposal Signed | CmmPropSignedByOwnerDate | Date when the Proposal was signed by Owner | datetime | | “2019-02-20” | | Reason | CmmReasonText | Select Reason for PCI. Must be a valid reason in CMiC. For more details please see the following article: [Maintain Reason LOV](https://docs.cmicglobal.com/portal/Content/E_Reference_Material/JC_-_Job_Costing/Reference/Setup/Maintain_Reason_LOV_Screen.htm?Highlight=maintain%20reason). This can be a required field based on Company Control settings. | string | 200 | “Reason A” | | PCI Scope | CmmScopeDesc | Description of scope, in regard to the change. | string | 4000 | “Test” | | Source Type | CmmSourceText | If the PCI was created from another object in CMiC Field, enter/select the type of the source. These codes can be created by checking the ‘[Maintain Source Type LOV](https://docs.cmicglobal.com/portal/Content/E_Reference_Material/JC_-_Job_Costing/Reference/Setup/Maintain_Source_LOV_Screen.htm?Highlight=maintain%20source)’ box in the Maintenance section of the Project Roles screen (standard Treeview path: CMiC Field > Security > Project Roles). | string | 200 | “Source1” | | Source | CmmSrcId | This field displays the object from which the PCI is created, if crated from a PM object like RFIs for example. See more details on the following article: [Linking/Creating a PCI to Objects](https://docs.cmicglobal.com/portal/Content/E_Reference_Material/CMiC_Field/Reference/Budget___Cost_Management/PCIs/Linking_Creating_a_PCI_to.htm?Highlight=create%20pci) | string | 30 | “DOCPKG-003” | | System Status Code | CmmStatCode | determine the current status of the subcontract. (Pending, In-Progress etc.) | string | 1 | “Pending” | | Status Code Last Update Date | CmmStatCodeUpdateDate | Date the PCI Status Code was last updated | datetime | | “2016-07-08T09:50:06-04:00” | | Update % Complete | CmmUpdPcComplFlag | Y/N. Defaults to Y if left null | string | 1 | “Y” / “N” | | Update Projected Amount during Posting | CmmUpdProjAmtFlag | Select (Y) if the default for Change Orders is to update the job projected amount each time a Change Order is posted.

If Change Orders are already included in the amounts for your projection forecasts, then this value should be (N). | string | 1 | “Y” / “N” | | Entered By | CmmUser | Username that created the PCI record | string | 30 | “SMUSER6” | | Workflow Status | CmmWorkflowStatus | A workflow status field is displayed on the Subcontract Screen. The possible values (set by workflow) are:

Un-submitted, Pending, Rejected, Approved (Submitted)

Note: If Workflow is being used for subcontracts and subcontract change orders, additional workflow columns are available to be used in the SC and SCCO logs but they must be incorporated during the workflow design process. If these columns have not been built into the workflow design, they will not be populated during workflow and can be removed from logs. | | | “Un-submitted” / “Pending” / “Approved” / “Rejected” / “null” | ## OpenAPI ````json POST /cm-rest-api/rest/1/cmmast { "openapi": "3.0.0", "info": { "title": "API Catalog", "description": "", "version": "1.0.0" }, "servers": [ { "url": "https://mobtest.cmiccloudr12.com/cmictestrti", "description": "CMIC API Server" } ], "security": [ { "cmicBasicAuth": [] } ], "tags": [ { "name": "Highlights" }, { "name": "Asset Management | Equipment" }, { "name": "Asset Management | Fixed Assets" }, { "name": "Asset Management | Purchase Order" }, { "name": "Asset Management | Inventory" }, { "name": "Asset Management | Requisition" }, { "name": "Asset Management | Purchase Change Order" }, { "name": "Bim Model" }, { "name": "Bim Model Revision" }, { "name": "Bim Tag Model" }, { "name": "Bim Tags" }, { "name": "Bim FileUpload Jersey" }, { "name": "Core System | Business Partners" }, { "name": "Core System | Business Partner Addresses" }, { "name": "Core System | Bank" }, { "name": "Core System | Currency" }, { "name": "Core System | Exchange Rates" }, { "name": "Core System | Global Table Text Codes" }, { "name": "Core System | Global Table Regions" }, { "name": "Core System | Terms" }, { "name": "Core System | System Contact" }, { "name": "Core System | Weight Measures" }, { "name": "Core System | Field User Defined Classifiers" }, { "name": "Core System | User Defined Classifiers by Object" }, { "name": "Core System | User Extension Definitions by Object" }, { "name": "Core System | User Extention Field Data Value" }, { "name": "Core System | User Extension Values by Object" }, { "name": "Core System | User System Role" }, { "name": "Core System | User Project Role" }, { "name": "Core System | Documents by Object" }, { "name": "Core System | Audit Status Log by Object" }, { "name": "Core System | Licensed Users" }, { "name": "Core System | Company Access" }, { "name": "Core System | Copy User Settings" }, { "name": "Core System | User Maintenance" }, { "name": "Core System | User Roles" }, { "name": "Core System | Security Groups" }, { "name": "Core System | Job/Project Security" }, { "name": "Core System | Weight Measure with Conversions Code" }, { "name": "Core System | Weight Measure Conversions Code" }, { "name": "Core System | User-defined-fields" }, { "name": "Core System | User-extension" }, { "name": "ECM and Workflow | Image Manager" }, { "name": "Financials | General Ledger" }, { "name": "Financials | Accounts Payable" }, { "name": "Financials | Accounts Receivable" }, { "name": "Preventative Maintenance | Issue Work Orders" }, { "name": "Preventative Maintenance | Issue Work Items" }, { "name": "Preventative Maintenance | Issue Work Budgets" }, { "name": "Preventative Maintenance | Issue Priorities" }, { "name": "Preventative Maintenance | Issue Status" }, { "name": "Preventative Maintenance | Issue Types" }, { "name": "Preventative Maintenance | Accumulative Equipment" }, { "name": "Preventative Maintenance | Work Orders" }, { "name": "Preventative Maintenance | Work Items" }, { "name": "Preventative Maintenance | Work Budgets" }, { "name": "Preventative Maintenance | Priorities" }, { "name": "Preventative Maintenance | Tasks" }, { "name": "HCM | UKG Pay Deductions" }, { "name": "HCM | UKG Pay Earnings" }, { "name": "HCM | UKG Pay Headers" }, { "name": "HCM | UKG Pay Taxes" }, { "name": "HCM | Payroll Geographical States" }, { "name": "HCM | Payroll Trades" }, { "name": "HCM | Payroll Union" }, { "name": "HCM | Payroll Pay Runs" }, { "name": "HCM | Payroll Pay Groups" }, { "name": "HCM | Payroll Tax" }, { "name": "HCM | Payroll Worker Compensation" }, { "name": "HCM | Payroll Work Locations" }, { "name": "HCM | Payroll Trade Pay Rates" }, { "name": "HCM | Payroll Union Pay Rates" }, { "name": "HCM | Payroll Job Pay Rates" }, { "name": "HCM | Payroll Master Benefits" }, { "name": "HCM | Payroll Master Deductions" }, { "name": "HCM | Payroll Ben/Ded/Leave Base Codes" }, { "name": "HCM | Payroll Ben/Ded Plans" }, { "name": "HCM | Payroll Ben/Ded Plan Options" }, { "name": "HCM | Payroll Company Benefits" }, { "name": "HCM | Payroll Company Deductions" }, { "name": "HCM | Payroll Vertex Geographic Locations" }, { "name": "HCM | Payroll Checks" }, { "name": "HCM | Payroll Timesheets" }, { "name": "HCM | Employee" }, { "name": "HCM | Employee (Minimum payload)" }, { "name": "HCM | Employee History" }, { "name": "HCM | Tax Exemptions" }, { "name": "HCM | Employee Tax Overrides" }, { "name": "HCM | Employee Pay Splits" }, { "name": "HCM | Employee Benefits" }, { "name": "HCM | Employee Clock In and Out" }, { "name": "HCM | Employee Deductions" }, { "name": "HCM | Employee Leaves" }, { "name": "HCM | Employee Leave History" }, { "name": "HCM | Employee Hour Types" }, { "name": "HCM | Employee Pay History" }, { "name": "HCM | Employee Work Statuses" }, { "name": "HCM | Employee Security Group" }, { "name": "HCM | Crewtime Crew" }, { "name": "HCM | Crewtime Employee Timesheet" }, { "name": "HCM | Crewtime Equipment Timesheet" }, { "name": "HCM | Crew Maintenance Activity Assignment" }, { "name": "HCM | Crew Maintenance Member Assignment" }, { "name": "HCM | Crew Maintenance Member Trade and Union Assignment" }, { "name": "HCM | Crew Maintenance Equipment Assignment" }, { "name": "HCM | Crew Maintenance Equipment Detail Assignment" }, { "name": "HCM | HR Requisitions" }, { "name": "HCM | HR Relations" }, { "name": "HCM | HR Employee Skills" }, { "name": "HCM | HR Incident" }, { "name": "HCM | HR Employee Relatives / Dependents" }, { "name": "HCM | HR Employee Positions" }, { "name": "HCM | HR Applicants" }, { "name": "HCM | HR Applications" }, { "name": "HCM | Vertex Location City" }, { "name": "HCM | HR Application History" }, { "name": "HCM | HR Dependent Benefits" }, { "name": "HCM | HR Dependent Deductions" }, { "name": "HCM | HR Employee Elected Plans" }, { "name": "HCM | HR Employee Training Certifications" }, { "name": "HCM | HR Trainings" }, { "name": "HCM | E-Timesheets" }, { "name": "HCM | System Contacts" }, { "name": "HCM | System User Payroll Security Group" }, { "name": "HCM | Payroll Timesheet Posting" }, { "name": "HCM | CrewTimesheet Posting" }, { "name": "HCM | HR Positions Master" }, { "name": "HCM | Payroll Pay Periods" }, { "name": "HCM | Payroll Rate Codes" }, { "name": "HCM | Payroll Overhead Codes and Rates" }, { "name": "HCM | Payroll Assigned Overhead to Jobs" }, { "name": "Materials Management | Material Sale Orders" }, { "name": "Materials Management | Material Sale Orders Details" }, { "name": "Materials Management | Truck Rate Detail" }, { "name": "Opportunity Management | Competitors" }, { "name": "Opportunity Management | Opportunities" }, { "name": "Opportunity Management | Revenue Details" }, { "name": "Opportunity Management | Opportunity History" }, { "name": "Opportunity Management | Organization" }, { "name": "Project Controls | Job Billing" }, { "name": "Project Controls | Job Cost" }, { "name": "Project Controls | PCI Details" }, { "name": "Project Controls | Unposted PCI Details" }, { "name": "Project Controls | PCI Headers" }, { "name": "Project Controls | Owner Change Orders" }, { "name": "Project Controls | CM Statuses" }, { "name": "Project Controls | CM Types" }, { "name": "Project Controls | CM Vendor Details" }, { "name": "Project Controls | Post PCI" }, { "name": "Project Management | Uploading Documents" }, { "name": "Project Management | Downloading Documents" }, { "name": "Project Management | Foreign Bid Item Imports" }, { "name": "Project Management | Communications" }, { "name": "Project Management | Daily Journals" }, { "name": "Project Management | Communications Types" }, { "name": "Project Management | Daily Journal Daily Work Plans" }, { "name": "Project Management | Daily Journal Field Forces" }, { "name": "Project Management | Daily Journal Labour" }, { "name": "Project Management | Daily Journal Materials" }, { "name": "Project Management | Daily Journal Owner Equipment" }, { "name": "Project Management | Daily Journal Quality Control" }, { "name": "Project Management | Daily Journal Tasks" }, { "name": "Project Management | Daily Journal Trade Equipment" }, { "name": "Project Management | Daily Journal Transactions" }, { "name": "Project Management | Daily Journal User Defined Data" }, { "name": "Project Management | Daily Journal Visitors" }, { "name": "Project Management | Daily Journal Bill Details" }, { "name": "Project Management | Field Work Directives" }, { "name": "Project Management | Contract Types" }, { "name": "Project Management | Company Contacts" }, { "name": "Project Management | Distribution BCC" }, { "name": "Project Management | Distribution CC" }, { "name": "Project Management | Field Work Directive Statuses" }, { "name": "Project Management | Issues" }, { "name": "Project Management | Key Players" }, { "name": "Project Management | Meetings" }, { "name": "Project Management | Meeting Attendees" }, { "name": "Project Management | Meeting Item Statuses" }, { "name": "Project Management | Meeting Tracks" }, { "name": "Project Management | Notes" }, { "name": "Project Management | Projects" }, { "name": "Project Management | Project Items" }, { "name": "Project Management | Project Item Phase Segment Sums" }, { "name": "Project Management | Project Partners" }, { "name": "Project Management | Notices" }, { "name": "Project Management | Notice Statuses" }, { "name": "Project Management | Owner JS Query" }, { "name": "Project Management | PCI Real Locations" }, { "name": "Project Management | Project Contacts" }, { "name": "Project Management | RFIs (Requests for Information)" }, { "name": "Project Management | RFI Statuses" }, { "name": "Project Management | Submittal Packages" }, { "name": "Project Management | Submittal Package Details" }, { "name": "Project Management | Submittal Package Status" }, { "name": "Project Management | Submittals" }, { "name": "Project Management | Submittal Status" }, { "name": "Project Management | Transmittals" }, { "name": "Project Management | Subcontract Headers" }, { "name": "Project Management | Subcontract Schedules" }, { "name": "Project Management | Subcontract Sechedule Phase Segment Sums" }, { "name": "Project Management | User Roles" }, { "name": "Project Management | Punchlists" }, { "name": "Project Management | Punchlist Details" }, { "name": "Project Management | Punchlist Statuses" }, { "name": "Project Management | Meeting Items" }, { "name": "Project Management | Self Perform Vendor" }, { "name": "Project Management | Submittal Types" }, { "name": "Project Management | Assign contact and partner to project" }, { "name": "Project Management | Subcontract Prequal" }, { "name": "Project Management | Bid Item Package" } ], "paths": { "/cm-rest-api/rest/1/cmmast": { "post": { "tags": [ "Project Controls | PCI Headers" ], "summary": "Create a PCI Header", "description": "## Overview\n\nThis endpoint allows for the viewing and creation of Potential Change Items header information, such as Company, Project, Scope of Work, PCI dates and more.\n\nPotential Change Items can be used to enter change requests for ongoing projects. PCIs are items that are expected to result in additional work or cost, beyond what was stated in the original submittal. These items can be made internally or externally and can be linked to requests for quotation (RFQ) and other related objects.\n\nTo create PCI details, please refer to “_Create a PCI Detail_” documentation.\n\n## UI Navigation\n\n- Enterprise > Change Management > Change Orders > Enter PCI\n- CMiC Field > Budget & Cost Management > Potential Change Items\n\n## Reference Article\n\n- [Change Management - Enter PCI](https://docs.cmicglobal.com/portal/Content/E_Reference_Material/CM_-_Change_Management/Reference/Change_Orders/EnterPCI.htm)\n- [CMiC Field - Potential Change Items](https://docs.cmicglobal.com/portal/Content/E_Reference_Material/CMiC_Field/Reference/Budget___Cost_Management/PCIs/Potential_Change_Items.htm?Highlight=enter%20pci)\n\n## Commonly Used Body Parameters\n\n| CMiC UI Fieldname | Name | Description | Type | Data Length | Example | Required |\n| --- | --- | --- | --- | --- | --- | --- |\n| Company Code | CmmCompCode | Company Code associated with the PCI’s project | string | 8 | “ZZ” | Yes |\n| Job Code | CmmJobCode | Job Code associated with the PCI’s Project | string | 10 | “23-410” | Yes |\n| PCI Type | CmmTypeCode | Enter/select the PCI’s type code. Must be a valid CmiC PCI type. | string | 4 | “EXT” | Yes |\n| PCI Code | CmmCode | PCI number identifying PCI | string | 11 | “EXT-23005” | Yes |\n| PCI Description | CmmName | PCI name or description | string | 200 | “Excavation Scope Change” | Yes |\n| PCI Date | CmmRefDate | This date is used as the reference date for the PCI in other screens, such as the Post Change Orders screen. | datetime | | “2016-05-03” | Yes |\n| Pre-post Status Code | CmmPrepostStatCode | Status code before posting. Must be a valid PCI status code in CMiC. | string | 10 | “APPROVED” | Yes |\n| Projected Amount Calc Method | CmmCalcProjAmtMethod | Flag to indicate the calculation method for projected amount when a change order is posted, and Update Projected Amount is checked. (A)dd Change Budget Amount or (R )ecalculate Projected Amount | string | 1 | “A” | Yes |\n| VUuid | CmmVUuid | Unique Row ID. When creating a new change item, this field should be included in the body of the request but left empty. Including this parameter allows you to preview the posting after submission. | string | 64 | “C6007D3BB3742CACE0530100007F8D31” | No |\n\n## Other (Optional) Body Parameters\n\n| CMiC UI Fieldname | Name | Description | Type | Data Length | Example |\n| --- | --- | --- | --- | --- | --- |\n| Action Code | CmmActionCode | This is the Action Code Created by the system. Action items are used to schedule and coordinate phone calls, delivery dates, meetings and other action types relevant to the Opportunity Management module. The Action Code is used to identify the action item type. Click [here](https://support.cmicglobal.com/s/article/Action-Item-Codes) to learn more about Action Item Codes. | string | 1 | |\n| Allowance | CmmAllowance | Allowance Type (I)n Scope, (O)ut of Scope, (N)either. Default is N. | string | 1 | “T” |\n| Approved Flag | CmmAprvFlag | Idicate weather this PCI is Approved or not. Related to PCI Status Code. Y or N | string | 1 | “Y” / “N” |\n| Auto Calculate Markups | CmmAutoCalcMarkupFlag | Automatically generate markup lines once the PCI record has been saved. Y or N | string | 1 | “Y” / “N” |\n| Batch Number | CmmBchNum | Batch number associated with PCI posting | integer | 11 | “755568” |\n| Bid Item | CmmBiditemFlag | Flag to indicate that it is an automatic change order created by the bid item. (Y)es, (N)o, or null | string | 1 | “null” / “Y” / “N” |\n| Bill Method Code | CmmBillMethCode | Valid values are (D)Details or (S)Summary. If left as null, it will default to D. | string | 1 | “D” |\n| Change Issued Date | CmmChgSentToOwnerDate | Enter the dates the change order was issued. | datetime | | “2019-02-28” |\n| Change Signed Date | CmmChgSignedByOwnerDate | Enter the dates the change order was signed. | datetime | | “2019-02-28” |\n| PCI Class Code | CmmClassCode | PCI Class associated with the PCI type. (E )xternal, (I)nternal, (T)ransfer, (O)riginal Budget Change | string | 1 | “E” |\n| Classifier 1 | CmmClvValueCode1 | Classifier Value 1 | string | 16 | |\n| Classifier 2 | CmmClvValueCode2 | Classifier Value 2 | string | 16 | |\n| Classifier 3 | CmmClvValueCode3 | Classifier Value 3 | string | 16 | |\n| Classifier 4 | CmmClvValueCode4 | Classifier Value 4 | string | 16 | |\n| Classifier 5 | CmmClvValueCode5 | Classifier Value 5 | string | 16 | |\n| Classifier 6 | CmmClvValueCode6 | Classifier Value 6 | string | 16 | |\n| Control Job Code | CmmCtrlJobCode | Controlling Job Code for PCIs linked to subjobs. If the Project is associated with a controlling Job, this field should be set as “ALL” | string | 10 | “ALL” |\n| Cycle Number | CmmCycleNum | For reallocation PCIs only: Reallocation Cycle Number | integer | 4 | “1” |\n| Due to owner Date | CmmDueToOwnerDate | For reference purposes only, to indicate when this change is due to the owner. | datetime | | “2016-04-26” |\n| End Date | CmmEffectiveEndDate | Change Order End Date | datetime | | “2018-09-11” |\n| Start Date | CmmEffectiveStartDate | Change Order Start Date | datetime | | “2018-09-10” |\n| Global Update Date | CmmGlobalUpdateDate | Timestamp of “global” PCI update, including e.g. PCI header/details, RFQ, Notes, Attachments. | datetime | | “2024-05-29T06:15:09-04:00” |\n| Impact Days | CmmImpactDays | Enter number of days of impacted by change. These will print on the Change Order and calculate new finish date. | integer | 4 | “10” |\n| Create Date | CmmIuCreateDate | Date the record was created | datetime | | “2018-09-10T13:44:36-04:00” |\n| Update Date | CmmIuUpdateDate | Date the record was last updated | datetime | | “2018-09-10T13:44:36-04:00” |\n| Lump Sum Flag | CmmLumpsumFlag | Y = Lump Sum PCI, N= Regular PCI | string | 1 | “Y” / “N” |\n| Original PCI Code | CmmOrigCmmCode | Reallocation PCI only: Original PCI code being adjusted (re-allocation) | string | 11 | “EXT-001” |\n| Original Owner Allowance Amount | CmmOrigOwnerAllowanceAmt | Applicable only In Scope, Out of Scope Allowance Type PCI. Written only at posting time. For Out of Scope is normally 0 | number | 18 | “0” |\n| Owner Allowance Amount | CmmOwnerAllowanceAmt | Applicable only In Scope, Out of Scope Allowance Type PCI. For Out of Scope is normally 0 | number | 18 | “100” |\n| PCI Owner Change Order | CmmOwnerChgCode | Enter the Owner Change Order number associated with the Change Order. The Owner Change Order number is a reference field that will appear on Job Billing AIA style report. | string | 20 | “OCO-002” |\n| Pending Flag | CmmPendFlag | Pending Type associated with the PCI status code. Available options are: (A)pproved, (C )ancelled, (N) Pre-Pending, (P)ending, (R )ejected. For more details on PCI Pending Types, please refence the following article: [PCI Status Codes](https://docs.cmicglobal.com/portal/Content/E_Reference_Material/CM_-_Change_Management/Reference/Local_Tables/PCI_Status_Codes.htm?Highlight=pci%20status%20code) | string | 1 | “Y” / “N” |\n| Post Vendor Contracts with PCI | CmmPostContrFlag | Insert (Y), if the Subcontract associated to this PCI should be posted at the same time as the PCI; otherwise, the related Subcontract is posted separately (N). | string | 1 | “Y” / “N” |\n| Post Date | CmmPostDate | Date PCI was posted | datetime | | “2016-02-02” |\n| PCI Posted Status | CmmPostingFlag | System generated value to indicate the status of the PCI, if it its posted or unposted | string | 12 | “POSTED” |\n| Proposal Issued | CmmPropIssuedToOwnerDate | Date when Proposal was issued to Owner | datetime | | “2019-02-20 |\n| Proposal Signed | CmmPropSignedByOwnerDate | Date when the Proposal was signed by Owner | datetime | | “2019-02-20” |\n| Reason | CmmReasonText | Select Reason for PCI. Must be a valid reason in CMiC. For more details please see the following article: [Maintain Reason LOV](https://docs.cmicglobal.com/portal/Content/E_Reference_Material/JC_-_Job_Costing/Reference/Setup/Maintain_Reason_LOV_Screen.htm?Highlight=maintain%20reason). This can be a required field based on Company Control settings. | string | 200 | “Reason A” |\n| PCI Scope | CmmScopeDesc | Description of scope, in regard to the change. | string | 4000 | “Test” |\n| Source Type | CmmSourceText | If the PCI was created from another object in CMiC Field, enter/select the type of the source. These codes can be created by checking the ‘[Maintain Source Type LOV](https://docs.cmicglobal.com/portal/Content/E_Reference_Material/JC_-_Job_Costing/Reference/Setup/Maintain_Source_LOV_Screen.htm?Highlight=maintain%20source)’ box in the Maintenance section of the Project Roles screen (standard Treeview path: CMiC Field > Security > Project Roles). | string | 200 | “Source1” |\n| Source | CmmSrcId | This field displays the object from which the PCI is created, if crated from a PM object like RFIs for example. See more details on the following article: [Linking/Creating a PCI to Objects](https://docs.cmicglobal.com/portal/Content/E_Reference_Material/CMiC_Field/Reference/Budget___Cost_Management/PCIs/Linking_Creating_a_PCI_to.htm?Highlight=create%20pci) | string | 30 | “DOCPKG-003” |\n| System Status Code | CmmStatCode | determine the current status of the subcontract. (Pending, In-Progress etc.) | string | 1 | “Pending” |\n| Status Code Last Update Date | CmmStatCodeUpdateDate | Date the PCI Status Code was last updated | datetime | | “2016-07-08T09:50:06-04:00” |\n| Update % Complete | CmmUpdPcComplFlag | Y/N. Defaults to Y if left null | string | 1 | “Y” / “N” |\n| Update Projected Amount during Posting | CmmUpdProjAmtFlag | Select (Y) if the default for Change Orders is to update the job projected amount each time a Change Order is posted.

If Change Orders are already included in the amounts for your projection forecasts, then this value should be (N). | string | 1 | “Y” / “N” |\n| Entered By | CmmUser | Username that created the PCI record | string | 30 | “SMUSER6” |\n| Workflow Status | CmmWorkflowStatus | A workflow status field is displayed on the Subcontract Screen. The possible values (set by workflow) are:

Un-submitted, Pending, Rejected, Approved (Submitted)

Note: If Workflow is being used for subcontracts and subcontract change orders, additional workflow columns are available to be used in the SC and SCCO logs but they must be incorporated during the workflow design process. If these columns have not been built into the workflow design, they will not be populated during workflow and can be removed from logs. | | | “Un-submitted” / “Pending” / “Approved” / “Rejected” / “null” |", "requestBody": { "content": { "application/json": { "schema": { "type": "object", "example": { "CmmCompCode": "001", "CmmJobCode": "14001", "CmmTypeCode": "EXT", "CmmCode": "EXT0123", "CmmName": "L's PCI", "CmmRefDate": "2023-11-11", "CmmPrepostStatCode": "PENDING", "CmmCalcProjAmtMethod": "A", "CmmVUuid": "E" } } } } }, "parameters": [ { "name": "Content-Type", "in": "header", "schema": { "type": "string" }, "example": "application/vnd.oracle.adf.resourceItem+json" } ], "responses": { "201": { "description": "Created", "headers": { "Content-Type": { "schema": { "type": "string", "example": "application/vnd.oracle.adf.resourceitem+json" } } }, "content": { "application/json": { "schema": { "type": "object" }, "example": { "CmmActionCode": null, "CmmAllowance": null, "CmmAprvFlag": null, "CmmAutoCalcMarkupFlag": null, "CmmBchNum": null, "CmmBiditemFlag": null, "CmmBillCatCode": null, "CmmBillCode": null, "CmmBillMethCode": null, "CmmBillName": null, "CmmBillPhsCode": null, "CmmBillRevisAmt": null, "CmmCalcProjAmtMethod": "A", "CmmChgSentToOwnerDate": null, "CmmChgSignedByOwnerDate": null, "CmmClassCode": null, "CmmClvValueCode1": null, "CmmClvValueCode2": null, "CmmClvValueCode3": null, "CmmClvValueCode4": null, "CmmClvValueCode5": null, "CmmClvValueCode6": null, "CmmCode": "EXT0123", "CmmCompCode": "001", "CmmCtrlJobCode": null, "CmmCycleNum": null, "CmmDueToOwnerDate": null, "CmmEffectiveEndDate": null, "CmmEffectiveStartDate": null, "CmmFundsourceCode": null, "CmmGlobalUpdateDate": null, "CmmImpactDays": null, "CmmInvCode": null, "CmmIuCreateDate": null, "CmmIuUpdateDate": null, "CmmJobCode": "14001", "CmmLumpsumFlag": null, "CmmName": "L's PCI", "CmmOrigCmmCode": null, "CmmOrigOwnerAllowanceAmt": null, "CmmOwnerAllowanceAmt": null, "CmmOwnerChgCode": null, "CmmPendFlag": null, "CmmPmFlag": null, "CmmPmObjectCode": null, "CmmPostContrFlag": null, "CmmPostDate": null, "CmmPostDateDummy": null, "CmmPostingFlag": null, "CmmPrepostStatCode": "PENDING", "CmmPropIssuedToOwnerDate": null, "CmmPropSignedByOwnerDate": null, "CmmReasonText": null, "CmmRefCmmCode": null, "CmmRefDate": "2023-11-11", "CmmRfqDueDate": null, "CmmRfqLimitAmt": null, "CmmRfqProceedFlag": null, "CmmScopeDesc": null, "CmmSourceText": null, "CmmSrcId": null, "CmmStatCode": null, "CmmStatCodeUpdateDate": null, "CmmTypeCode": "EXT", "CmmUpdPcComplFlag": null, "CmmUpdProjAmtFlag": null, "CmmUser": null, "CmmVUuid": "F396762021727DDEE05316821FACD0CF", "CmmWorkflowStatus": null, "links": [ { "rel": "self", "href": "http://mobtest.cmiccloudr12.com:80/cmictestrti/cm-rest-api/rest/1/cmmast/F396762021727DDEE05316821FACD0CF", "name": "cmmast", "kind": "item" }, { "rel": "canonical", "href": "http://mobtest.cmiccloudr12.com:80/cmictestrti/cm-rest-api/rest/1/cmmast/F396762021727DDEE05316821FACD0CF", "name": "cmmast", "kind": "item" } ] } } } } } } } }, "components": { "securitySchemes": { "cmicBasicAuth": { "type": "http", "scheme": "basic", "description": "Basic authentication" } } } } ````