WIPTJB: WIP Job Creation and Maintenance
The WIP Job Creation and Maintenance business object lets you add, update or delete jobs.
Detailed Description
Jobs can be created for stocked or non-stocked items. When creating a job for a stocked item, the labor and material allocations from the Bill of Materials can be attached to the job or they can be assigned manually. If allocations are being attached to the job, sub jobs can be created for all components in the structure against which it is indicated that a sub job must be raised.
Properties
| Syspro Module | Work in Progress |
| Class | Transaction |
| Methods | Post |
| Functional Area | WIP Primary Posting |
| Initial version released | Syspro 6.1 |
Functionality
1. Triggers and Event Management events are excluded.
2. The trial load facility is unavailable.
3. This business object does not currently support user-defined hierarchies when capturing hierarchical jobs.
Input XML
The .XML and .XSD input files indicate the parameters schema and an instance of an XML document for this business object.
WIPTJB.XML
Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2014 SYSPRO Ltd.-->
<!--
Sample XML for the WIP Job Header Maintenance Posting Business Object
-->
<PostJob xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xsd:noNamespaceSchemaLocation="WIPTJB.XSD">
<Parameters>
<ActionType>A</ActionType>
<ValidateOnly>N</ValidateOnly>
<ApplyIfEntireDocumentValid>N</ApplyIfEntireDocumentValid>
<IgnoreWarnings>N</IgnoreWarnings>
<Snapshot>N</Snapshot>
<TriggerAps>Y</TriggerAps>
<UseParentWhRoute>N</UseParentWhRoute>
<UseParentCompWh>N</UseParentCompWh>
<StatusInProcess>N</StatusInProcess>
</Parameters>
</PostJob>
Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2014 SYSPRO Ltd.-->
<!--
Schema for the parameters for the WIP Job Header Maintenance Posting Business Object
-->
<xsd:schema elementFormDefault="qualified" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="ActionType" default="A">
<xsd:annotation>
<xsd:documentation>Specifies whether to add update copy or delete jobs (A - add, C - update, P - copy, D - delete). Only live jobs can be added and you cannot do a copy when in snapshot.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="A"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="P"/>
<xsd:enumeration value="D"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="IgnoreWarnings">
<xsd:annotation>
<xsd:documentation>Specifies if warnings are to be ignored (Y - if the warnings are to be ignored, N - warnings will be returned as errors in the XML returned, W - warnings will be returned as warnings in the XML returned.)</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="N"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Parameters">
<xsd:annotation>
<xsd:documentation>This element contains the optional parameter elements.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="ActionType" minOccurs="0"/>
<xsd:element ref="ValidateOnly" minOccurs="0"/>
<xsd:element name="ApplyIfEntireDocumentValid" default="N" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Specifies whether the entire document must be validated first before applying the function (N - apply function for each valid item, Y - all items must be valid before function is applied). If not supplied it defaults to 'Y'.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element ref="IgnoreWarnings" minOccurs="0"/>
<xsd:element ref="Snapshot" minOccurs="0"/>
<xsd:element name="TriggerAps" default="Y" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Specifies whether APS must be triggered (Y - APS will be triggered, N - APS will not be triggered) </xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="N"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="UseParentWhRoute" default="N" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This specifies whether or not to use the route, defined against the warehouse control information, when creating a job. It ignores this parameter if alternate routes are not used. (Y - Yes, N - No) The default is No</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="UseParentCompWh" default="N" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This specifies whether or not to use the component warehouse, defined against the parent's warehouse control information, when creating a job. (Y - Yes, N - No) The default is No</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="StatusInProcess" default="N" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This parameter alllows you to add a job based on a sales order when the sales order is in process. When this parameter is 'Y' then the sales order in process status is ignored. (Y - Yes, N - No). The default is No.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="PostJob">
<xsd:annotation>
<xsd:documentation>This is the root element</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element ref="Parameters"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Snapshot" default="N">
<xsd:annotation>
<xsd:documentation>Specifies whether maintaining a live, suggested or snapshot job (N - live, Y - snapshot, S- suggested) </xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TriggerAps" default="Y">
<xsd:annotation>
<xsd:documentation>Specifies APS will be triggered or not. (Y - Trigger APS, N - will not trigger APS).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="N"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ValidateOnly" default="N">
<xsd:annotation>
<xsd:documentation>Specifies whether to only validate the contents of the document. (N - validate and apply function, Y - only validate the document).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="Y"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:schema>
The DOC.XML and DOC.XSD files indicate the schema and an instance of an XML document for this business object.
WIPTJBDOC.XML
Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2025 SYSPRO Ltd. -->
<!--
Sample XML for the WIP Job Header Maintenance Posting Business Object
-->
<PostJob xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xsd:noNamespaceSchemaLocation="WIPTJBDOC.XSD">
<Item>
<Job />
<JobDescription>Add Job using COM object</JobDescription>
<JobClassification />
<WipBranch />
<Priority>50</Priority>
<StockCode>B100</StockCode>
<Version />
<Release />
<Warehouse>FG</Warehouse>
<UnitOfMeasure>S</UnitOfMeasure>
<QtyToMake>10</QtyToMake>
<GrossQuantityFlag>N</GrossQuantityFlag>
<Customer>000001</Customer>
<CustomerName />
<JobTenderDate>2006-05-27</JobTenderDate>
<DateCalcMethod>S</DateCalcMethod>
<IncludeOvertimePct>N</IncludeOvertimePct>
<SetMethodToManual>N</SetMethodToManual>
<JobStartDate>2006-10-30</JobStartDate>
<JobDeliveryDate>2006-10-30</JobDeliveryDate>
<SeqCheckReq>N</SeqCheckReq>
<ConfirmedFlag>N</ConfirmedFlag>
<HoldFlag>N</HoldFlag>
<Route>0</Route>
<RoutePassword />
<WipCtlGlCode />
<NonStocked>N</NonStocked>
<StockDescription />
<ExpLabour />
<ExpMaterial />
<SellingPrice />
<AddLabPct />
<AddMatPct />
<ProfitPct />
<TraceableType>N</TraceableType>
<HierarchyFlag>N</HierarchyFlag>
<HierarchyContract />
<HierarchyCode />
<SalesOrder />
<SalesOrderLine />
<IncludeAllocations>Y</IncludeAllocations>
<ComponentWarehouse />
<SubJobOptions>
<CreateSubJobs>Y</CreateSubJobs>
<SubJobPrefix />
<SubJobSuffix />
<UseGlForAllJobs>N</UseGlForAllJobs>
</SubJobOptions>
<CheckLeadTime>Y</CheckLeadTime>
<ReCalculateJobDates>Y</ReCalculateJobDates>
<ChangeSalesOrderWarehouse />
<CopyMaterial>N</CopyMaterial>
<CopyLabor>N</CopyLabor>
<CopyNonStkFlag>Y</CopyNonStkFlag>
<CopyStockCode />
<CopyVer />
<CopyRel />
<CopyNonRoute>0</CopyNonRoute>
<CopyFromJob>
<ArchivedJob>N</ArchivedJob>
<ArchiveNumber />
<FromJob>30</FromJob>
<PlannedOrBuilt>P</PlannedOrBuilt>
<IncludeMaterialAllocs>N</IncludeMaterialAllocs>
<IncludeLaborAllocs>N</IncludeLaborAllocs>
<IncludeNotepad>N</IncludeNotepad>
<IncludeCustomForms>N</IncludeCustomForms>
<IncludeNarrations>N</IncludeNarrations>
<IncludeMultimedia>N</IncludeMultimedia>
</CopyFromJob>
<CoProducts>
<CoProduct>
<CoProductLine>1</CoProductLine>
<UnitOfMeasure>S</UnitOfMeasure>
<QtyToMake />
<QtyPerNotional />
<ExcludeCoProduct>N</ExcludeCoProduct>
</CoProduct>
</CoProducts>
<AutomaticallyReserveAllocs>Y</AutomaticallyReserveAllocs>
<MaintenanceJob />
<EquipmentCode />
<MaintenanceServiceType />
<LinkCapex />
<eSignature>{36303032-3330-3031-3038-323434363433}</eSignature>
</Item>
</PostJob>Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2025 SYSPRO Ltd. -->
<!--
Schema for the WIP Job Header Maintenance Posting Business Object
-->
<xsd:schema elementFormDefault="qualified" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="AddLabPct">
<xsd:annotation>
<xsd:documentation>Additional charge percentage for labor to be used in part billings as a means of increasing the value of un-billed labor entries held against the job.This is ignored if the item to make is stocked.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AddMatPct">
<xsd:annotation>
<xsd:documentation>Additional charge percentage for material to be used in part billings as a means of increasing the value of un-billed material entries held against the job. This is ignored if the item to make is stocked.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element default="N" name="ChangeSalesOrderWarehouse">
<xsd:annotation>
<xsd:documentation>Set this flag to change the sales order warehouse if changing the warehouse (Warehouse) against a job that is attached to a sales order.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element default="N" name="CheckLeadTime">
<xsd:annotation>
<xsd:documentation>Flag indicating whether to calculate a start date based on the delivery date entered and the lead time against the stock code to see whether the job can be done. Ignored if not adding a new job or the date calculation method (DateCalcMethod) is not set to 'S' or 'M'</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ComponentWarehouse">
<xsd:annotation>
<xsd:documentation>Enter a specific warehouse that must be used when issuing all material to the job. Otherwise the warehouse to use held against each component (specified at the Warehouse to use field of the Stock Codes Setup program) is used when allocating material to the job. This is ignored if not adding a job or allocations are not included.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ConfirmedFlag">
<xsd:annotation>
<xsd:documentation>Flag indicates whether or not the job is confirmed. If adding or copying a job and this is not returned then the WIP setup option 'Jobs confirmed by default' will be used.
Material and labor postings cannot be made to an unconfirmed job. Furthermore unconfirmed jobs can be excluded from requirements planning.
A job can be confirmed at any time but jobs cannot be 'unconfirmed' if the job has been started (i.e. issues of labor hours or materials have been made).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="N" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Customer" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Customer to be used to create a sales order if a part billing is required. The format is alphanumeric or numeric depending on a configuration option within SYSPRO.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CustomerName">
<xsd:annotation>
<xsd:documentation>Customer name. This is overwritten by the customer's name held on file.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DateCalcMethod">
<xsd:annotation>
<xsd:documentation>This flag indicates the calculation method to be applied when calculating the job's start/delivery date based on attached labor allocations.
D - Delivery date based on the start date using forward infinite scheduling.
S - Start date based on the delivery date using backward infinite scheduling.
M - Do not calculate start or delivery date.
F - Delivery date based on the start date using forward finite scheduling. This option is available if the WIP installation option "Load Levelling Required" is set to 'Y' and allocations are attached to the job. If not then it is changed to date method 'D'.
To calculate the delivery date from the start date the program processes each operation attached to the finished part and assumes the queue date of the first operation to be the start date of the job.
The finish date of the first operation is calculated by adding the queue and elapsed time of that operation. The start date of the next operation is the finish date of the previous operation, plus movement time plus one day. The delivery date of the job is the finish date of the last operation plus movement time.
The reverse is true if calculating the start date.
If creating sub jobs (CreateSubJob = 'Y') or job is linked to a sales order then the date calculation method is set to 'S'. This element can be supplied when doing a job copy.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="D" />
<xsd:enumeration value="S" />
<xsd:enumeration value="M" />
<xsd:enumeration value="F" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ExpLabour">
<xsd:annotation>
<xsd:documentation>Expected unit labor cost of the item to make. This is ignored if the item to make is stocked.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ExpMaterial">
<xsd:annotation>
<xsd:documentation>Expected unit material cost of the item to make. This is ignored if the item to make is stocked.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="HierarchyCode">
<xsd:annotation>
<xsd:documentation>If the job is hierarchical (HierarchyFlag = 'Y') then a hierarchy library code can be entered here to create the job's hierarchy of heads and sections. Ignored if not adding a job.
At the time of creating a job you can assign a hierarchy of heads and sections. A head is the top level section for a job. An unlimited number of heads can be assigned. To each head, an unlimited number of sections can be attached and, again, an unlimited number of sections can be attached to each section. The process can continue through four levels of sections.
Currently user defined hierarchy is not supported by this object.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="HierarchyContract">
<xsd:annotation>
<xsd:documentation>If the job is hierarchical (HierarchyFlag = 'Y') and the job is attached to a contract then the contract must be entered here. Ignored if not adding a job.
Any number of jobs can be annotated to form part of an overall contract. Transactions cannot be made to the contract; only to a constituent job.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element default="N" name="HierarchyFlag">
<xsd:annotation>
<xsd:documentation>Flag to indicate whether the job being added is hierarchical. Ignored if not adding a job, if projects and contracts is not installed or the item to make is a notional part or multi-grade coproduct part</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element default="N" name="HoldFlag">
<xsd:annotation>
<xsd:documentation>Flag indicates whether a job is on hold. Set to 'Y' to suspend processing for the job.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="IncludeAllocations">
<xsd:annotation>
<xsd:documentation>Flag to indicate whether to include allocations when adding a job. This flag is ignored if creating a non-stocked item or Bill of Materials is not installed and is set to 'N'.
If set to 'Y' material and labor allocations are added against the job based on the structure and routings defined in the bill of materials for this parent on this route.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="N" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element default="N" name="IncludeOvertimePct">
<xsd:annotation>
<xsd:documentation>Include overtime percentage in forward finite date calculation (DateMethod = 'F'). The overtime percentage is held against the work centers and is used when calculating capacity available on a given day and when calculating the capacity required by the operation for the day.
If not returned then will use the WIP setup option 'Apply overtime percentage to forward finite calculation by default '. This element can be supplied when doing a job copy.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Item">
<xsd:annotation>
<xsd:documentation>This element contains information to maintain a job.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" ref="Job" />
<xsd:element minOccurs="0" ref="JobDescription" />
<xsd:element minOccurs="0" ref="JobClassification" />
<xsd:element minOccurs="0" name="WipBranch" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The WIP branch to assign to this job. If WIP is integrated to G/L by WIP branch, then the ledger code defined for this WIP Branch will be used for the job.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="Priority" />
<xsd:element minOccurs="0" ref="StockCode" />
<xsd:element minOccurs="0" ref="Version" />
<xsd:element minOccurs="0" ref="Release" />
<xsd:element minOccurs="0" ref="Warehouse" />
<xsd:element minOccurs="0" default="S" name="UnitOfMeasure">
<xsd:annotation>
<xsd:documentation>Select 'S' for stocking uom, 'A' for alternate uom, 'O' for other uom or 'M' for manufacturing uom. Quantities and times entered will be according to the unit of measure selected.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="S" />
<xsd:enumeration value="A" />
<xsd:enumeration value="O" />
<xsd:enumeration value="M" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" ref="QtyToMake" />
<xsd:element minOccurs="0" default="N" name="GrossQuantityFlag">
<xsd:annotation>
<xsd:documentation>This flag indicates that the quantity entered will be the actual gross quantity so the net quantity will be calculated after applying prgressive scrap. Ignored if the item to make is a notional part or a multi-grade co-product part.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:pattern value="N" />
<xsd:pattern value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" ref="Customer" />
<xsd:element minOccurs="0" ref="CustomerName" />
<xsd:element minOccurs="0" ref="JobTenderDate" />
<xsd:element ref="DateCalcMethod" />
<xsd:element minOccurs="0" ref="IncludeOvertimePct" />
<xsd:element minOccurs="0" ref="SetMethodToManual" />
<xsd:element minOccurs="0" ref="JobStartDate" />
<xsd:element minOccurs="0" ref="JobDeliveryDate" />
<xsd:element minOccurs="0" ref="SeqCheckReq" />
<xsd:element minOccurs="0" ref="ConfirmedFlag" />
<xsd:element minOccurs="0" ref="HoldFlag" />
<xsd:element minOccurs="0" ref="Route" />
<xsd:element minOccurs="0" ref="RoutePassword" />
<xsd:element minOccurs="0" ref="WipCtlGlCode" />
<xsd:element minOccurs="0" ref="NonStocked" />
<xsd:element minOccurs="0" ref="StockDescription" />
<xsd:element minOccurs="0" ref="ExpLabour" />
<xsd:element minOccurs="0" ref="ExpMaterial" />
<xsd:element minOccurs="0" ref="SellingPrice" />
<xsd:element minOccurs="0" ref="AddLabPct" />
<xsd:element minOccurs="0" ref="AddMatPct" />
<xsd:element minOccurs="0" ref="ProfitPct" />
<xsd:element minOccurs="0" ref="TraceableType" />
<xsd:element minOccurs="0" ref="HierarchyFlag" />
<xsd:element minOccurs="0" ref="HierarchyContract" />
<xsd:element minOccurs="0" ref="HierarchyCode" />
<xsd:element minOccurs="0" ref="SalesOrder" />
<xsd:element minOccurs="0" ref="SalesOrderLine" />
<xsd:element minOccurs="0" ref="IncludeAllocations" />
<xsd:element minOccurs="0" ref="ComponentWarehouse" />
<xsd:element minOccurs="0" ref="SubJobOptions" />
<xsd:element minOccurs="0" ref="CheckLeadTime" />
<xsd:element minOccurs="0" ref="ReCalculateJobDates" />
<xsd:element minOccurs="0" ref="ChangeSalesOrderWarehouse" />
<xsd:element minOccurs="0" default="N" name="CopyMaterial">
<xsd:annotation>
<xsd:documentation>This flag can only be used when adding non-stocked jobs (the job cannot be hierarchical). It allows you to copy material allocations from the specified stocked item in the CopyStockCode tag. The flag can be either Y or N.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="N" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" default="N" name="CopyLabor">
<xsd:annotation>
<xsd:documentation>This flag can only be used when adding non-stocked jobs (the job cannot be hierarchical). It allows you to copy labor allocations from the specified stocked item in the CopyStockCode tag. The flag can be either Y or N.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="N" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" default="N" name="CopyNonStkFlag">
<xsd:annotation>
<xsd:documentation>This flag indicates that material and labor will be copied from an estimate. The flag can be either Y or N. The default is N</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="CopyStockCode">
<xsd:annotation>
<xsd:documentation>This item specifies the stock code from which you want to copy material and labor allocations for a non-stocked job.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="CopyVer">
<xsd:annotation>
<xsd:documentation>This item specifies the revision number for a ECC stock code.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" maxOccurs="3" name="CopyRel">
<xsd:annotation>
<xsd:documentation>This item specifies the release number for a ECC stock code.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="CopyNonRoute">
<xsd:annotation>
<xsd:documentation>This element indicates the estimate route to copy from. If no route is supplied, the field will default to route 0.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="CopyFromJob">
<xsd:annotation>
<xsd:documentation>This element contains information to copy a job</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:all>
<xsd:element minOccurs="0" default="N" name="ArchivedJob">
<xsd:annotation>
<xsd:documentation>This element indicates whether an archived job is to be copied. Set to Y to copy archived job. The default is N.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="ArchiveNumber">
<xsd:annotation>
<xsd:documentation>This element indicates the archive number of the job to be copied. If this element is not supplied or returned as spaces when copying an archived job the job number will be used to pick up the archive number.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FromJob">
<xsd:annotation>
<xsd:documentation>This element indicates the job to be copied. This is mandatory. The format is alphanumeric or numeric depending on the configuration option within SYSPRO.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" default="P" name="PlannedOrBuilt">
<xsd:annotation>
<xsd:documentation>This element indicates if the values used when copying the job should be as planned, that is using the figures entered when the job was created or as built, that is using the figures that were issued. The as built option (B) is only applicable if a job is complete and you are not using progressive scrap.
Possible values are P - planned or B - built. The default is P.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="P" />
<xsd:enumeration value="B" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" default="N" name="IncludeMaterialAllocs">
<xsd:annotation>
<xsd:documentation>This element indicates whether material allocations are to be copied. Set to Y to copy material allocations. The default is N.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:pattern value="N" />
<xsd:pattern value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" default="N" name="IncludeLaborAllocs">
<xsd:annotation>
<xsd:documentation>This element indicates whether labor allocations are to be copied. Set to Y to copy labor allocations. When progressive scrap is set on and you are copying a job which calculates progressive scrap from gross to net then you must include labor allocations. The default is N.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" default="N" name="IncludeNotepad">
<xsd:annotation>
<xsd:documentation>This element indicates whether notepad is to be copied. Set to Y to copy notepad. The default is N.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" default="N" name="IncludeCustomForms">
<xsd:annotation>
<xsd:documentation>This element indicates whether custom forms are to be copied. Set to Y to copy custom forms. The default is N.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" default="N" name="IncludeNarrations">
<xsd:annotation>
<xsd:documentation>This element indicates whether narrations are to be copied. Set to Y to copy narrations. The default is N.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" default="N" name="IncludeMultimedia">
<xsd:annotation>
<xsd:documentation>This element indicates whether multimedia is to be copied. Set to Y to copy multimedia. The default is N.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="CoProducts">
<xsd:annotation>
<xsd:documentation>This element contains information for individual co-products. This element is only applicable for co-products which will be or have been created via a notional part. The co-product types which apply here are concurrent, sequential and proportional.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="CoProduct">
<xsd:annotation>
<xsd:documentation>This element contains co-product information</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:all>
<xsd:element name="CoProductLine">
<xsd:annotation>
<xsd:documentation>This element indicates the co-product line number of the co-product you wish to update. This is mandatory.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element default="S" name="UnitOfMeasure">
<xsd:annotation>
<xsd:documentation>Select 'S' for stocking uom, 'A' for alternate uom, 'O' for other uom or 'M' for manufacturing uom. Quantities and times entered will be according to the unit of measure selected.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="S" />
<xsd:enumeration value="A" />
<xsd:enumeration value="O" />
<xsd:enumeration value="M" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" ref="QtyToMake" />
<xsd:element minOccurs="0" name="QtyPerNotional">
<xsd:annotation>
<xsd:documentation>The quantity required per notional part quantity can be adjusted here. This element is only applicable for proportional type co-products. When the quantity required per notional part is supplied for proportional co-products a check is done to make sure the proportion of quantity percentage has not exceeded 100% for the co-products. If the proportion of quantity percentage has exceeded 100% an error will be output. The proportion of quantity percentage can however be less than 100%.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" default="N" name="ExcludeCoProduct">
<xsd:annotation>
<xsd:documentation>This element indicates whether you want to exclude a co-product from manufacture. When adding a job this element is only available for optional co-products. When maintaining a job and the job is in an unconfirmed stated then this element is available for all co-products. At least one co-product must be included. Possible values for this element are 'N' - do not exclude co-product and 'Y' - exclude co-product. The default is N - do not exclude co-product.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
<xsd:enumeration value=" " />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" default="Y" name="AutomaticallyReserveAllocs">
<xsd:annotation>
<xsd:documentation>Flag to indicate whether to automatically reserve stock for allocations. If the flag is set to 'Y' then stock will be reserved for the quantity required of each allocation where stock is available. If this flag is set to 'N' then reserving will not take place. If a confirmed job is unconfirmed then irrespective of this flag the reserved stock for allocations will be released. This flag is ignored when reserving stock for allocations is switched off in the WIP Setup program. This flag is valid when adding and updating a job. The default is 'Y'</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="N" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="MaintenanceJob">
<xsd:annotation>
<xsd:documentation>This indicates if the job is a maintenance job when Enterprise Asset Management is in use. Possible values: Y (Yes) or N (No). The default is 'N'.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="EquipmentCode" type="xsd:string">
<xsd:annotation>
<xsd:documentation>This is the Equipment code to use to retrieve the EAM structure when Enterprise Asset Management is in use and the Job is a maintenance job. The format is alphanumeric 30 characters.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="MaintenanceServiceType" type="xsd:string">
<xsd:annotation>
<xsd:documentation>This is the Maintenance service type to use to retrieve the EAM structure when Enterprise Asset Management is in use and the Job is a maintenance job. The format is alphanumeric 30 characters.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="LinkCapex">
<xsd:annotation>
<xsd:documentation>This indicates that the job is linked to an asset and the asset is a capex item. Possible values: Y (Yes) or N (No). The default is the setting saved against the Equipment code, but can select to still not link the job.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="eSignature">
<xsd:annotation>
<xsd:documentation>GUID for eSignatures</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Job">
<xsd:annotation>
<xsd:documentation>Job specifies the job being maintained. This is mandatory if changing or deleting a job or adding/copying and the job numbering method is manual.
If deleting a job then this is the only element required. The format is alphanumeric or numeric depending on the configuration option within SYSPRO.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="JobClassification">
<xsd:annotation>
<xsd:documentation>Job classification for the job. If not supplied when adding a job then this defaults to the job classification held against the stock code if stocked or the job classification against the operator. If job numbering method is by job class then this is used to generate the job on an add.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="JobDeliveryDate">
<xsd:annotation>
<xsd:documentation>Date on which the job is due for completion. If adding/copying a job and this is not returned the date defaults to today.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string" />
</xsd:simpleType>
</xsd:element>
<xsd:element name="JobDescription">
<xsd:annotation>
<xsd:documentation>This is the description to appear against the job. If not defined when adding/copying a job for a stocked item then the stock description is used.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="JobStartDate">
<xsd:annotation>
<xsd:documentation>Date on which the job is to start. If adding/copying a job and this is not returned the date defaults to today.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string" />
</xsd:simpleType>
</xsd:element>
<xsd:element name="JobTenderDate">
<xsd:annotation>
<xsd:documentation>Tender date required. This date is only used for documentation purposes. If adding a job and this is not returned the date defaults to today.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string" />
</xsd:simpleType>
</xsd:element>
<xsd:element default="N" name="NonStocked">
<xsd:annotation>
<xsd:documentation>When adding a job this flag indicates whether the item to make is non-stocked. If the warehouse to use is set to '**' then this flag is set to 'Y'.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PostJob">
<xsd:annotation>
<xsd:documentation>This is the root element.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" ref="Item" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Priority">
<xsd:annotation>
<xsd:documentation>Priority of the job (1-99). 1 indicates the lowest priority and 99 indicates the highest priority.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ProfitPct">
<xsd:annotation>
<xsd:documentation>Additional percentage profit charge to be used in part billings as a means of increasing the value to be invoiced.This is ignored if the item to make is stocked.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="QtyToMake">
<xsd:annotation>
<xsd:documentation>Quantity required to make. If adding this is zero then the quantity to make is calculated based on the manufacturing basis defined against the stock code. This cannot be changed against a hierarchical job. Quantity required to make within the co-product node allows you to individually add co-product quantities. The highest calculated notional part quantity will be used as the notional part quantity and is calculated as follows: (co-product quantity / co-product quantity per = notional part quantity). The default notional part quantity will be the qtytomake supplied or calculated for the notional part within the item node. If not all co-products are individually changed and the default notional part quantity is still the highest notional part quantity then it will be used as the notional part quantity. Co-products which are not individually changed will be driven by the notional part quantity. This element is only applicable when the WIP setup option 'Quantity capture co-product jobs' is a 'C' - Co-product. This element is not applicable for proportional co-products.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string" />
</xsd:simpleType>
</xsd:element>
<xsd:element default="N" name="ReCalculateJobDates">
<xsd:annotation>
<xsd:documentation>Set this flag to force recalculation of start and delivery dates when updating a job. This flag is ignored and date recalculation automatically takes place if one of the following has been changed; quantity (QtyToMake), date calculation method (DateCalcMethod), start date (JobStartDate) or delivery date (JobDeliveryDate). The date recalculation is also automatic when dealing with a notional part job and you are changing the quantity against co-products or you are excluding co-products. If the date method is manual then this flag is not ignored unless you are dealing with a notional part job and the co-product quantities change or you are excluding co-products.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Release">
<xsd:annotation>
<xsd:documentation>Release indicates the ECC release number of the component part. Ignored if not an ECC controlled item, or if ECC controlled at a stocking/revision level. When adding and this is not supplied then defaults to the current release number for the stock code. This cannot be changed. The format is alphanumeric or numeric depending on the configuration option within Bill of Materials setup.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Route">
<xsd:annotation>
<xsd:documentation>Bill of materials route from which to create the job allocatons. This is only required when adding a job and 'Bill of Materials' is installed and the BOM setup option 'Alternate routings required' is set. This can also be used when copying material and labor allocations for a non-stocked job and specifies the route from which you want to copy. If not supplied then defaults to the standard route (0).</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="RoutePassword">
<xsd:annotation>
<xsd:documentation>The password associated with the Bill of Material route. This element can be supplied when copying a job.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SalesOrder">
<xsd:annotation>
<xsd:documentation>Sales order for which the job is to be added. Ignored if not adding a job or sales orders is not installed or the sales order line os not returned.The format is alphanumeric or numeric depending on the sales order key type option within SYSPRO.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SalesOrderLine" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Sales order line for which the job is to be added. Ignored if not adding a job or sales orders is not installed or the sales order is not returned. If valid then the information for creating the job (stock code, warehouse, quantity etc.) is all obtained from the sales order line.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="SellingPrice">
<xsd:annotation>
<xsd:documentation>Unit selling price to be used in part billings to determine the value of the sales order.This is ignored if the item to make is stocked. When changing a job if the job is for a capex item then this is also ignored. The format is 10.5 positive numeric.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SeqCheckReq">
<xsd:annotation>
<xsd:documentation>Flag indicates whether or not sequence checking is required on operations when posting labor (i.e. an operation number cannot be posted to if work has not already commenced on the previous operation. If adding a job and this is not returned then will use the WIP setup option 'Sequence checking required by default'</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="N" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element default="N" name="SetMethodToManual">
<xsd:annotation>
<xsd:documentation>This option will fix the calculated dates by setting the calculation method to manual (DateMethod = 'M'). This element can be supplied when doing a job copy.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="StockCode">
<xsd:annotation>
<xsd:documentation>Stock code of the finished item that is required to be made. This is mandatory when adding unless created from a sales order (see SalesOrder).
When changing a job this can only be changed if maintaining a non-stocked live job and the job is not for a capex item. The format is alphanumeric or numeric depending on the configuration option within SYSPRO.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="StockDescription">
<xsd:annotation>
<xsd:documentation>Description of the item to make. If a job for a stocked item is being processed then the description held against the item is used.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SubJobOptions">
<xsd:annotation>
<xsd:documentation>Options required when creating sub jobs for attached components.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" ref="CreateSubJobs" />
<xsd:element minOccurs="0" ref="SubJobPrefix" />
<xsd:element minOccurs="0" ref="SubJobSuffix" />
<xsd:element minOccurs="0" ref="UseGlForAllJobs" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element default="N" name="CreateSubJobs">
<xsd:annotation>
<xsd:documentation>Flag to indicate whether or not to create the required sub jobs for all components in a structure against which you indicated that a sub job must be raised (within the Bill of Materials Structures and Routings program). This will create, in effect, a bill of jobs for all relevant components down the BOM chain.
Ignored if not adding a new job and if not including allocations (IncludeAllocations = 'N')</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SubJobPrefix">
<xsd:annotation>
<xsd:documentation>If creating sub jobs for components (CreateSubJobs = 'Y') and job numbering is set to Manual. This prefix is strung together with the sub job suffix (SubJobSuffix) to create the job for each sub job.The format is alphanumeric or numeric depending on the job key type option within SYSPRO.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SubJobSuffix">
<xsd:annotation>
<xsd:documentation>If creating sub jobs for components (CreateSubJobs = 'Y') and job numbering is set to Manual. This suffix is strung together with the sub job prefix (SubJobPrefix) to create the job for each sub job.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element default="N" name="UseGlForAllJobs">
<xsd:annotation>
<xsd:documentation>Set this flag to 'Y' to use the work in progress control account against the parent job for all sub jobs when creating sub jobs for components (CreateSubJobs = 'Y')</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element default="N" name="TraceableType">
<xsd:annotation>
<xsd:documentation>Flag to indicate whether a non-stocked item to make is traceable. Ignored if not adding a job, if lot traceability is not installed or the item to make is stocked.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
<xsd:enumeration value="" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Version">
<xsd:annotation>
<xsd:documentation>Version indicates the ECC version number of the stock code to make. Ignore if not an ECC controlled item, or if ECC controlled at a stocking level. When adding and this is not supplied then defaults to the current version number for the stock code. This cannot be changed. The format is alphanumeric or numeric depending on the configuration option within Bill of Materials setup.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Warehouse">
<xsd:annotation>
<xsd:documentation>This is the warehouse to use for the finished stock code. When adding and this is not supplied then the finished stock code's warehouse to use is applied. If the non-stocked flag is set then this is ignored.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="WipCtlGlCode">
<xsd:annotation>
<xsd:documentation>Work in progress control account to which the value of work in progress is to be posted. When adding a job and this is blank then uses the account defined against the stock code, if that is blank then the account defined in GL integration is used. This cannot be changed once the job has been confirmed and transactions have been posted to the job or the job is for a capex item.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="eSignature">
<xsd:annotation>
<xsd:documentation>GUID for eSignatures</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:schema>-
When adding a job and specifying a Route, if there is a password defined against the route (Syspro menu | Bill of Materials | Setup | Routings), the entry against the element RoutePassword must match the defined password.
-
When adding a job and specifying a Route, the route must be flagged as being available for jobs (Syspro menu | Bill of Materials | Setup | Routings).
-
If Lot Traceability is installed, the Lot Traceability Setup option: Parent traceable if component traceable (Setup | Lot Traceability Setup | General tab) is selected and the parent part against the job is not traceable, an error will be returned if the component stock code is traceable (Syspro menu | Inventory | Setup | Stock Codes | Tracking tab).
-
When adding a job for a back ordered sales order, an error will be returned if the operator is denied access to the branch against the sales order (Setup | Security | Operators | Security | A/R Branches).
-
When adding a job for a back ordered sales order, if a salesperson code (with access control applied) has been defined against the operator (Setup | Security | Operators | Security | Salesperson), an error will be returned if the salesperson defined against the operator does not match the salesperson defined against the sales order.
-
When adding a job for a back ordered sales order, the sales order cannot be a hierarchical order, a credit note or a debit note.
-
When adding a job for a back ordered sales order, the sales order must be in a status of 1 (Open order), 2 (Open backorder), 3 (Released backorder), 4 (Warehouse) or 8 (Released for invoice), if the type of order is a counter sale.
-
When adding a job for a back ordered sales order, the sales order line must be a merchandise line (i.e. stocked or non-stocked) and there must be a quantity on back order.
-
A job cannot be added for an ECC controlled item (Syspro menu | Inventory | Setup | Stock Codes | Tracking tab) if an Engineering Change Order is currently in progress for the item and new jobs have been prevented for all stock codes on the ECO.
-
When adding a job, if an entry is not made against the element Warehouse, the warehouse to use entered against the stock code will be used (Syspro menu | Inventory | Setup | Stock Codes | Descriptive tab). If this is blank, the default warehouse against the operator will be used (Setup | Security | Operators | Defaults tab). If this is also blank, the default warehouse defined against the company will be used (Setup | Company Setup | General tab). If the job is being created from a back ordered sales order, the warehouse against the sales order line will be used.
-
An error will be returned if the operator is denied access to either the ComponentWarehouse or Warehouse (Setup | Security | Operators | Security | Warehouses).
-
When adding a job, an entry must exist against the element JobClassification if the Work in Progress Setup option: Job classification required is selected (Setup | Manufacturing Setup | Work in Progress | Job Creation tab). If an entry is not made against this element, the job classification entered against the stock code will be used (Syspro menu | Inventory | Setup | Stock Codes | Production tab). If this is blank, the default job classification against the operator will be used (Setup | Security | Operators | Defaults tab).
-
An error will be returned when adding a job if the operator is denied access to the JobClassification (Setup | Security | Operators | Security | Job Classification).
-
An error will be returned when changing or deleting an existing job if the operator is denied access to the job classification against the job (Setup | Security | Operators | Security | Job Classification).
-
A job cannot be added or deleted if the stock code is on hold (Syspro menu | Inventory | Setup | Stock Codes | Edit pulldown | On Hold Status).
-
An error will be returned if the customer against the job is on hold (Syspro menu | Accounts Receivable | Setup | Customers | Options tab) and the parameter IgnoreWarnings is set to N.
-
An error will be returned if the customer against the job is not on the list of customers that may be accessed by the operator or the salesperson attached to the customer is not the specific salesperson to which the operator is allowed access (Setup | Security | Operators | e.net | Customers).
-
If an existing job is on hold (Syspro menu | Work in Progress | Setup | Jobs | Edit pulldown | Hold), the job cannot be deleted and can only be changed if the element HoldFlag is set to N.
-
A completed job cannot be changed.
-
When adding a job, the stock code's part category can only be made in, subcontracted or bought out (Syspro menu | Inventory | Setup | Stock Codes | Descriptive tab).
-
When adding a job, an error will be returned if the stock code's part category is bought out (Syspro menu | Inventory | Setup | Stock Codes | Descriptive tab) and the parameter IgnoreWarnings is set to N.
-
The element JobStartDate will be ignored if the DateCalcMethod is S.
-
The element JobDeliveryDate will be ignored if the DateCalcMethod is D or F. In addition, if an entry is not supplied against this element and a job is being created for a back ordered sales order, the order's ship date will be used as the basis to calculate the job delivery date.
-
When changing a job, if the Warehouse is changed against a sub job and the parameter IgnoreWarnings is set to N, an error will be returned.
-
When changing a job, the QtyToMake cannot be changed to less than the quantity that has already been manufactured for the job.
-
When changing a job, if the QtyToMake is changed against a master job and the parameter IgnoreWarnings is set to N, an error will be returned, as this will have an affect on all the attached sub jobs, which will have to be corrected manually.
-
When changing a job, if the QtyToMake is changed against a sub job and the parameter IgnoreWarnings is set to N, an error will be returned, as this will have an affect on the master job, which will have to be corrected manually.
-
When changing a job, if the QtyToMake is changed and at least one of the factory documents has been printed, an error will be returned if the parameter IgnoreWarnings is set to N.
-
When adding a job, if an entry is not made against the element QtyToMake and a job is being added for a stocked item, the quantity to make will be calculated according to the batching rule defined against the stock code. If a job is being created for a non-stocked item and the quantity to make is not supplied, the quantity will default to 1. If a job is being created for a back ordered sales order, the quantity on back order against the sales order line will be used.
-
A sub job cannot be deleted without first being detached from the master job.
-
A master job that has active sub jobs cannot be deleted without first detaching the sub jobs.
-
A job cannot be deleted if the WIP value against the job is not zero for the current period, previous period 1 or previous period 2.
-
A job cannot be deleted if there have been material or labor issues to the job for the current period, previous period 1 or previous period 2.
-
A job that is attached to a sales order cannot be deleted if the parameter IgnoreWarnings is set to N.
-
If Inventory is integrated to General Ledger in detail or summary (Setup | General Ledger Integration | General Ledger tab) and a ledger code is entered against the element WipCtlGlCode, the entry will be validated. In addition, error messages will be returned if the ledger code is not a control account or an asset type account and the parameter IgnoreWarnings is set to N(Syspro menu | General Ledger | Setup | General Ledger Codes).
-
If Inventory is integrated to General Ledger by report, in detail or in summary (Setup | General Ledger Integration | General Ledger tab) and a ledger code is not entered against the element WipCtlGlCode, the system will attempt to locate the appropriate entry. If a WIP ledger control account has been defined against the stock code, this account will be used.
If this is not defined, the WIP control account defined in General Ledger Integration (Setup | General Ledger Integration | W.I.P. tab) will be used. If Inventory is integrated to General Ledger in detail or in summary and an appropriate entry cannot be located, an error message will be returned.
In addition, error messages will be returned if the ledger code is not a control account or an asset type account and the parameter IgnoreWarnings is set to N (Syspro menu | General Ledger | Setup | General Ledger Codes).
-
If the element UseGlForAllJob is set to N, and a WIP ledger control account has been defined against the stock code, this account will be used for all sub jobs. If this is not defined, the WipCtlGlCode against the master job will be used.
-
Refer to WIPTJB.XSD and WIPTJB.XML for the parameters schema and an instance of an XML document for this business object.
-
Refer to WIPTJBDOC.XSD and WIPTJBDOC.XML for the schema and an instance of an XML document for this business object.
Output XML
The OUT.XML indicates a sample of the XML returned by this business object.
WIPTJBOUT.XML
Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2014 SYSPRO Ltd.-->
<!--
Sample XML for the WIP Job Header Maintenance Posting Business Object
-->
<postjob Language='05' CssStyle='' DecFormat='1' DateFormat='01' Role='01' Version='6.0.001'>
<Item>
<Job>00000122</Job>
<ItemNumber>1</ItemNumber>
<SubJobs>
<Job>00000123</Job>
<SubJobs>
<Job>00000124</Job>
<SubJobs>
<Job>00000125</Job>
</SubJobs>
</SubJobs>
</SubJobs>
</Item>
<StatusOfItems>
<ItemsProcessed>1</ItemsProcessed>
<ItemsInvalid>0</ItemsInvalid>
</StatusOfItems>
</postjob>
Refer to WIPTJBOUT.XML for a sample of the XML returned by this business object.
Prerequisites
The Work in Progress module must be installed to run this business object.
The WIP Primary Posting functional area must be licensed.
Limitations
No limitations apply to this business object.
Copyright © 2026 Syspro PTY Ltd.