IDL Multiphase Projects
Introduction
The multiphase project is used to manage a project, its related phases and task and to populate the related sales invoices.
Input file definition
| Field name | Type | Nullable | Description | Accepted values | Comment |
| Organization | String(40) | No | Indicates the organization to be used when processing documents. | Organization search key | |
| Search Key | String(40) | No | Search key identifying the project. | ||
| Name | String(60) | No | Name of the Project | ||
| Project Type | String(60) | Yes | Existing Project type. | Project type name | |
| Project Status | String(60) | No | Status of the project | {Open, Order, Order closed} | |
| Processed | Boolean | No | {'TRUE', 'FALSE'} | ||
| Start Date | Date | Yes | |||
| Date Finish | Date | Yes | The real end date is used to indicate when the project is expected to be completed or has been completed. | ||
| Date Contract | Date | Yes | The planned end date is used to determine when the document becomes effective. This is usually the contract date. The planned end date is used in reports and report parameters. | ||
| Responsible | String(60) | Yes | Person in charge of the Project | Business Partner name with Employee flag true. | |
| Business Partner | String(60) | Yes | Business Partner name. | ||
| BP Location | String(60) | Yes | Business Partner location | BP Location name | Only if Business Partner is provided |
| User / Contact | String(60) | Yes | Contact user of the Business Partner | User name related to the Business Partner | Only if Business Partner is provided |
| Payment Method | String(60) | Yes | Payment Method name | ||
| Payment Term | String(60) | Yes | Payment Term name | ||
| Commitment | Boolean | Yes | Commitment indicates if the document is legally binding. | {'TRUE', 'FALSE'} | |
| Commit Ceiling | Boolean | Yes | The commitment amount and quantity is the maximum amount and quantity to be charged. Ignored, if the amount or quantity is zero. | {'TRUE', 'FALSE'} | |
| Committed Amount | Quantity | Yes | The commitment amount is independent from the planned amount. You would use the planned amount for your realistic estimation, which might be higher or lower than the commitment amount. | ||
| Committed Quantity | Quantity | Yes | The commitment quantity is independent from the planned quantity. You would use the planned quantity for your realistic estimation, which might be higher or lower than the commitment quantity. | ||
| Serv Revenue | Quantity | Yes | Revenue services | ||
| ExpExpenses | Quantity | Yes | Planned Expenses | ||
| ServSerCost | Quantity | Yes | Expected cost of services provided. | ||
| ServOutCost | Quantity | Yes | Expected cost of services outsourced. | ||
| ServCost | Quantity | Yes | Expected total cost of services provided. | When is left blank is defaulted to the sum of ServSerCost and ServOutCost | |
| ExpReinvoicing | Quantity | Yes | Reinvoicing Expenses | ||
| ServMargin | Quantity | Yes | Expected service margin. | ||
| ExpMargin | Quantity | Yes | Expected margin for expenses. | ||
| Sales Representative | String(60) | Yes | User name | ||
| Warehouse | String(60) | Yes | Warehouse name | ||
| Price List | String(60) | Yes | Price List name | ||
| PO Reference | String(20) | Yes | Order Reference | ||
| Summary | Boolean | Yes | {'TRUE', 'FALSE'} | Default value is False | |
| Description | String(255) | Yes |