WIPTJR: WIP Job Receipts
The WIP Job Receipts business object lets you process receipts against Work in Progress jobs for stocked items.
Properties
| Syspro Module | Work in Progress |
| Class | Transaction |
| Methods | Post |
| Functional Area | WIP Primary Posting |
| Initial version released | Syspro 6.1 |
Functionality
The facility to kit issue material and labor is unavailable.
Input XML
The .XML and .XSD input files indicate the parameters schema and an instance of an XML document for this business object.
WIPTJR.XML
Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2022 SYSPRO Ltd.-->
<!--
Sample XML for the Job Receipt Posting Business Object
-->
<PostJobReceipts xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xsd:noNamespaceSchemaLocation="WIPTJR.XSD">
<Parameters>
<ValidateOnly>N</ValidateOnly>
<ApplyIfEntireDocumentValid>N</ApplyIfEntireDocumentValid>
<IgnoreWarnings>Y</IgnoreWarnings>
<TransactionDate>2007-08-08</TransactionDate>
<SetJobToCompleteIfCoProductsComplete>Y</SetJobToCompleteIfCoProductsComplete>
<IncludeDimensionAnalysis>N</IncludeDimensionAnalysis>
</Parameters>
</PostJobReceipts>
Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2022 SYSPRO Ltd.-->
<!--
Schema for the parameters for the Job Receipt Posting Business Object
-->
<xsd:schema elementFormDefault="qualified" attributeFormDefault="unqualified" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="PostJobReceipts">
<xsd:annotation>
<xsd:documentation>This is the root element.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:all>
<xsd:element name="Parameters" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This contains parameters.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:all>
<xsd:element name="ValidateOnly" default="N" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element indicates which processing phases are to be performed. If set to 'Y' all items are validated and an XML string is returned with the result of the validation. No updating will take place. If set to 'N', each item is validated and updating is performed based on setting of the element 'ApplyIfEntireDocumentValid'. Default is 'N'. Valid values are 'N' and '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 name="ApplyIfEntireDocumentValid" default="N" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element indicates whether to process entire document only if all items are valid. If set to 'N', each item node is validated and rejected if in error or processed if correct. This is the fastest option. If set to 'Y', all items are validated and only processed if entire document is valid. Default is 'N'. Valid values are 'Y' and '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 name="IgnoreWarnings" default="N" minOccurs="0">
<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="N"/>
<xsd:enumeration value="Y"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TransactionDate" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Date transaction raised. If not supplied, then the system run date is used.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:date"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SetJobToCompleteIfCoProductsComplete" default="Y" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element indicates if the notional job should be set to complete after all the co-products have been receipted and completed. Possible values: Y (set notional job to complete after all co-products complete) or N (status of the notional job will not be changed). 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 name="IncludeDimensionAnalysis" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This option determines whether or not to use GL dimension analysis. If set to 'Y' then GL dimension analysis will be used. The default is 'N'.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</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.
WIPTJRDOC.XML
Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2025 SYSPRO Ltd. -->
<!--
Sample XML for the Job Receipt Posting Business Object
-->
<PostJobReceipts xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xsd:noNamespaceSchemaLocation="WIPTJRDOC.XSD">
<Item>
<Journal>12</Journal>
<Job>00000154</Job>
<CoProductLine />
<UnitOfMeasure>S</UnitOfMeasure>
<Quantity>1.0</Quantity>
<InspectionFlag>N</InspectionFlag>
<CostBasis>C</CostBasis>
<ReceiptCost>441.73</ReceiptCost>
<UseSingleTypeABCElements>N</UseSingleTypeABCElements>
<MaterialDistributionValue />
<LaborDistributionValue />
<JobComplete>Y</JobComplete>
<CoProductComplete>Y</CoProductComplete>
<Reference />
<Notation />
<IncreaseSalesOrderQuantity>N</IncreaseSalesOrderQuantity>
<SalesOrderComplete>N</SalesOrderComplete>
<Lot />
<LotConcession>Sww3</LotConcession>
<LotExpiryDate>2008-01-01</LotExpiryDate>
<LotUseByDate></LotUseByDate>
<LotSellByDate></LotSellByDate>
<LotInternalExpiryDate></LotInternalExpiryDate>
<LotManufactureDate></LotManufactureDate>
<LotDispatchDate></LotDispatchDate>
<LotBestBeforeDate></LotBestBeforeDate>
<BinLocation>A1</BinLocation>
<BinOnHold />
<BinOnHoldReason />
<BinUpdateWhDefault />
<FifoBucket />
<Serials>
<SerialNumber>8875</SerialNumber>
<SerialQuantity>12</SerialQuantity>
<SerialExpiryDate>2011-12-30</SerialExpiryDate>
<SerialLocation />
<SerialFifoBucket />
</Serials>
<WipInspectionReference />
<WipInspectionNarration />
<HierarchyJob>
<Head />
<Section1 />
<Section2 />
<Section3 />
<Section4 />
<CostOfSalesAmount />
</HierarchyJob>
<AddReference />
<MaterialReference />
<QuantityFromStock />
<CustomForm>
<CustomItem>
<CustomColumn>AlpColumn</CustomColumn>
<CustomValue>Alpha value</CustomValue>
</CustomItem>
<CustomItem>
<CustomColumn>NumCol</CustomColumn>
<CustomValue>100.00</CustomValue>
</CustomItem>
<CustomItem>
<CustomColumn>DatCol</CustomColumn>
<CustomValue>2022-01-01</CustomValue>
</CustomItem>
</CustomForm>
<InspectionLevel>GII</InspectionLevel>
<Lpn>
<LpnDetails>
<CreateNewLpn>Y</CreateNewLpn>
<LicensePlateNumber />
<Container>Pallet</Container>
<NumberOfContainers>2</NumberOfContainers>
<ContainerQuantity>6.000</ContainerQuantity>
</LpnDetails>
<LpnDetails>
<CreateNewLpn>Y</CreateNewLpn>
<LicensePlateNumber>12323322145</LicensePlateNumber>
<Container>BOX</Container>
<NumberOfContainers>1</NumberOfContainers>
<ContainerQuantity>3.000</ContainerQuantity>
</LpnDetails>
</Lpn>
<eSignature>{12345678-1234-1234-1234-123456789012}</eSignature>
</Item>
</PostJobReceipts>Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2025 SYSPRO Ltd. -->
<!--
Schema for the Job Receipt Posting Business Object
-->
<xsd:schema elementFormDefault="qualified" attributeFormDefault="unqualified" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="PostJobReceipts">
<xsd:annotation>
<xsd:documentation>This is the root element.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:choice maxOccurs="unbounded">
<xsd:element name="Item" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>This is the top element for all data required for the transaction.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:sequence>
<xsd:element name="Journal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This is the journal number to which the transaction journal entries generated will be added. It must be valid for the current posting period and warehouse and may not have been printed already. If not supplied a new journal will be created.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Job">
<xsd:annotation>
<xsd:documentation>This element is mandatory and must contain a valid job against which the receipt is to be made</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CoProductLine" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This indicates the co-product line number to be receipted for a notional job. This element will be ignored if the job is not a notional 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="LedgerCode" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Ledger code against which the merchandise amount of the received items is to be distributed. This element is ignored if the inventory setup option 'Request ledger codes for inventory transactions' is switched off or the option to 'Request ledger code for receipts' is switched off. If the ledger code is not returned then the WIP control account defined against the job 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="PasswordForLedgerCode" minOccurs="0">
<xsd:annotation>
<xsd:documentation>If a ledger code is returned and it requires a password, this element must contain the relevant password for the specified ledger code.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="UnitOfMeasure" default="S">
<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 name="Quantity" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Quantity to receive in against the job or co-product. If not returned or returned as zero then the quantity to receive is calculated as the difference between the quantity to manufacture and the quantity received in against the job or co-product.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="InspectionFlag" default="N" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element specifies whether you are receipting a job into inspection or directly into stock. This element is only valid when the item is lot traceable and has been setup to either receipt the quantity into inspection or stock. Possible values are 'N' or 'Y'. 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 name="CostBasis" default="C" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element specifies which cost basis to use, for the job receipt, to reduce the value of work in progress. If standard costing is in use then and the last cost is not required then this element is ignored as the cost used is always the current cost.
Valid values are:
C - Current warehouse cost
W - Outstanding work in progress value
A - Actual costs
E - Expected cost
M - Manual unit cost entered against the receipt cost element</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="C" />
<xsd:enumeration value="W" />
<xsd:enumeration value="A" />
<xsd:enumeration value="E" />
<xsd:enumeration value="M" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ReceiptCost" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element contains the unit cost required if the cost basis is defined as Manual (M). It must be positive and in the stocking unit of measure.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="UseSingleTypeABCElements" default="N" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element is only required if ABC costing is in use. If not supplied and ABC costing is required, it defaults to 'N'. Valid values are 'N' and '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 name="MaterialDistributionValue" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Element contains the value of material to reduce the material costs against the job. If not returned or returned as spaces then the system defaults to the amount calculated from the proportion of expected material costs of the job. The sum of this plust the labor distribution value must together equal the total cost of the receipt.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LaborDistributionValue" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Element contains the value of labor to reduce the labor costs against the job. If not returned or returned as spaces then the system defaults to the amount calculated from the proportion of expected labor costs of the job. The sum of this plus the material distribution value must together equal the total cost of the receipt.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="JobComplete" default=" " minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element contains the flag indicating whether the job should be flagged as complete or not. Please note that this element does not apply to notional jobs. Enter Y to set the job to be complete. Enter N to set the job to be not complete. Enter Spaces if you want the completion status to be determined by the program (i.e. the quantity already manufactured for the job is added to the quantity being received in. A comparison is made to the original quantity that was required to be manufactured. If the result is equal to (or greater than) the original quantity to be manufactured, then the job is set to complete. If it is less than the original quantity to be manufactured, then the job is set to be not complete.)</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value=" " />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CoProductComplete" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This indicates whether the co-product should be flagged as complete or not. Enter Y to set the co-product to be complete. Enter N to set the co-product to be not complete. Enter Spaces if you want the completion status to be determined by the program (i.e. the quantity already manufactured for the co-product is added to the quantity being received in. A comparison is made to the original quantity that was required to be manufactured. If the result is equal to (or greater than) the original quantity to be manufactured, then the co-product is set to complete. If it is less than the original quantity to be manufactured, then the co-product is set to be not complete.)</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Reference" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element can contain a source reference for the receipt transaction. This reference is printed on the journal report and is stored on the movement 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="Notation" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element can contain a notation which is printed on the journal report after the transaction details.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="IncreaseSalesOrderQuantity" default="N" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element is optional. If the Job is linked to a Sales Order and the receipt quantity is greater than the quantity on back order against the sales order, the order quantity will be increased to the receipt quantity, if this element 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:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SalesOrderComplete" default="N" minOccurs="0">
<xsd:annotation>
<xsd:documentation>If receipting in a quantity for a job that is attached to a sales order and the quantity being received in does not satisfy the sales order's back order quantity then this element can be set to 'Y' to set the sales order to be complete (i.e. reduce the sales order quantity to equal the quantity shipped).</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="Lot" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The following only applies if the stock item being received in is lot traceable and lot traceability is in use. The entry is mandatory if processing a positive receipt and the lot numbering method is manual and the option to use the job number as the lot has not been set. If a negative receipt is being processed, the lot must be entered.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LotConcession" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This indicates the lot concession number. If the element 'IgnoreWarnings' is set to 'N' in the parameters, a warning will be given if it is blank.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LotExpiryDate" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element contains the expiry date for the lot being receipted in. If it is not returned, the lot expiry date is calculated based on the shelf life defined against the stock item. This date can be returned as zero which indicates no expiry.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:date" />
</xsd:simpleType>
</xsd:element>
<xsd:element name="LotUseByDate" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This indicates the recommended date the Lot should be used by. Format CCYY-MM-DD.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string" />
</xsd:simpleType>
</xsd:element>
<xsd:element name="LotSellByDate" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This indicates the date by when the Lot should be sold. Format CCYY-MM-DD.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string" />
</xsd:simpleType>
</xsd:element>
<xsd:element name="LotInternalExpiryDate" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This indicates the an internal expiry date. Format CCYY-MM-DD.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string" />
</xsd:simpleType>
</xsd:element>
<xsd:element name="LotManufactureDate" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This indicates the date the Lot was manufactured. Format CCYY-MM-DD.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string" />
</xsd:simpleType>
</xsd:element>
<xsd:element name="LotDispatchDate" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This indicates the date the Lot was or will be dispatched by. Format CCYY-MM-DD.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string" />
</xsd:simpleType>
</xsd:element>
<xsd:element name="LotBestBeforeDate" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This indicates the date the Lot is best before. Format CCYY-MM-DD.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string" />
</xsd:simpleType>
</xsd:element>
<xsd:element name="BinLocation" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element contains the bin location of the stock being received. It is ignored if multiple bins are not in use. If not returned on a positive receipt then the default bin defined against the stock warehouse record 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="BinOnHold" minOccurs="0">
<xsd:annotation>
<xsd:documentation>If the work in progress option to place multiple bins on hold when receipting a job is set to 'Prompt operator', this element can contain 'Y' or 'N'. It is ignored in all other cases.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BinOnHoldReason" minOccurs="0">
<xsd:annotation>
<xsd:documentation>If the bin being receipted in is to be placed on hold (element BinOnHold = 'Y') then a reason can be entered and this is stored against the bin record.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BinUpdateWhDefault" default="N" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Enter 'Y' against this element if you wish the default bin held against the stock warehouse to be changed to the bin in the 'BinLocation' element.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
<xsd:enumeration value="" />
<xsd:enumeration value="N" />
<xsd:enumeration value="Y" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FifoBucket" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element is optional. If FIFO is installed and processing a negative receipt, a specific FIFO bucket may be specified for updating. If a FIFO bucket is supplied when processing a positive receipt, it will be 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="Serials" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>A set of serial numbers and relevant information must be supplied if stock item specified is serialized.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:all minOccurs="0">
<xsd:element name="SerialNumber">
<xsd:annotation>
<xsd:documentation>Serial number being received into stock. The format is either alphanumeric or numeric depending on the serial numbering method used.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element ref="SerialQuantity" />
<xsd:element ref="SerialExpiryDate" minOccurs="0" />
<xsd:element ref="SerialLocation" minOccurs="0" />
<xsd:element name="SerialFifoBucket" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The FIFO/actual costing bucket which the quantity must be issued from, this must be supplied when doing a negative receipt.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:element name="SerialRange" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>The contents of this node is used to specify a prefix and suffix or starting serial number for a range of new serial numbers to be generated. It is only valid when processing receipts for manual serialized stock items. It has two formats, depending on the serial key type. If serial numbers are alphanumeric, a prefix and a suffix need to be supplied. If serial numbers are numeric, a starting serial number is required.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:all minOccurs="0">
<xsd:element name="SerialPrefix" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element specifies the prefix to be used when generating a range of alphanumeric serial numbers. Prefix + suffix cannot exceed the size of the serial number key. Mandatory for alphanumeric serial numbers.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SerialSuffix" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element specifies the suffix to be used when generating a range of alphanumeric serial numbers. The suffix element must be numeric. Prefix + suffix cannot exceed the size of the serial number key. Mandatory for alphanumeric serial numbers.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="StartSerialNumber" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element specifies the starting serial number when generating a range of numeric serial numbers. Mandatory for numeric serial numbers.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SerialQuantity" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element is mandatory and specifies the quantity to receive for the specified serial number. If within the 'Serials' group and manual serial, it can only be 1 or -1. If within the 'SerialRange' or 'SerialAllocation' group, it is the total quantity to be received for the specified range.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SerialExpiryDate" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element contains the expiry date of a new serial number or range of serial numbers being received into stock.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:date" />
</xsd:simpleType>
</xsd:element>
<xsd:element name="SerialLocation" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element contains the location of the serial number or range of serial numbers being received when processing a positive receipt.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:element name="SerialAllocation" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>This element is used to specify a range of serial numbers to be processed. It is only valid when processing negative receipts for manual serialized stock items.</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="false">
<xsd:all minOccurs="0">
<xsd:element name="FromSerialNumber">
<xsd:annotation>
<xsd:documentation>This element specifies the starting serial number to be allocated when processing negative receipts.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ToSerialNumber" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element specifies the ending serial number to be allocated when processing negative receipts. If this element is not supplied, serial numbers will be allocated starting at the FromSerialNumber until the specified quantity has been allocated.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SerialQuantity">
<xsd:annotation>
<xsd:documentation>This element is mandatory and specifies the quantity to receive for the specified serial number. If within the 'Serials' group and manual serial, it can only be 1 or -1. If within the 'SerialRange' or 'SerialAllocation' group, it is the total quantity to be received for the specified range.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:element name="WipInspectionReference" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This indicates the WIP inspection reference that will be created when the job is receipted into WIP inspection. This element is only applicable when WIP inspection is in use and the job is for a lot traceable or inspectable item. This element will be ignored when you have selected auto-numbering for the WIP inspection reference. The format is either alphanumeric or numeric depending on the key configuration option for WIP inspection reference 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="WipInspectionNarration" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This indicates the narration for the WIP inspection reference that will be created when the job is receipted into WIP inspection.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="HierarchyJob" minOccurs="0">
<xsd:complexType mixed="false">
<xsd:all>
<xsd:element name="Head" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Head is part of a unique key to identify a hierarchy. Only applicable when projects and contracts is installed and the job is a hierarchical 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="Section1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Section1 is part of a unique key to identify a hierarchy. Only applicable when projects and contracts is installed and the job is a hierarchical 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="Section2" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Section2 is part of a unique key to identify a hierarchy. Only applicable when projects and contracts is installed and the job is a hierarchical 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="Section3" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Section3 is part of a unique key to identify a hierarchy. Only applicable when projects and contracts is installed and the job is a hierarchical 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="Section4" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Section4 is part of a unique key to identify a hierarchy. Only applicable when projects and contracts is installed and the job is a hierarchical 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="CostOfSalesAmount" minOccurs="0">
<xsd:annotation>
<xsd:documentation>You use the cost of sales amount field to assign the outstanding cost of sales amount to specified hierarchies. The cost of sales amount includes the combined labor and material values. Only applicable when projects and contracts is installed and the job is a hierarchical job.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:element name="AddReference" minOccurs="0">
<xsd:annotation>
<xsd:documentation>You can use the additional reference field for your own use to hold any extra information required.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MaterialReference" minOccurs="0">
<xsd:annotation>
<xsd:documentation>You can use the material additional reference field for your own use to hold any extra information required. The field is stored on the job detail posting 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="QuantityFromStock" minOccurs="0">
<xsd:annotation>
<xsd:documentation>When processing a negative receipt for a job attached to a sales order then enter a quantity here to take from the stock back to the job. The difference between this quantity and the receipt quantity will be taken from the sales order. It is important to note that a quantity can only be taken from stock if part of the quantity manufactured was receipted into stock.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CustomForm">
<xsd:annotation>
<xsd:documentation>This is the top element for the set of custom form columns and values to be posted with the transaction. It only applies when receipting a sub job as this then issues material to the master job - this is the transaction where the custom form fields will be posted to.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CustomItem" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>This element contains a custom form column and value.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CustomColumn" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This element specifies the custom form column.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CustomValue" minOccurs="0" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="InspectionLevel" type="xsd:string" default="GII" minOccurs="0">
<xsd:annotation>
<xsd:documentation>This indicates the Inspection Level that must be used against the Quality Management inspection. Only relevant on a reversal of a receipt quantity which results in the quantity counted being equal to the quantity receipted in inspection and the Sample basis is 'Sample quantity'. Format is 4 alphanumeric characters. The default is 'GII'.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Lpn">
<xsd:annotation>
<xsd:documentation>This a root element for License plate number details. This node and all its elements are ignored if License Plate Numbering is not in use.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="LpnDetails">
<xsd:annotation>
<xsd:documentation>This element is used to specify the License plate number receipt details.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CreateNewLpn" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Specify whether to create a new license plate number. Valid values are 'Y' - Yes and 'N' - No. Default is 'Y'.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="LicensePlateNumber" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The License plate number to receipt into.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Container" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Container to be used for LPN receipt.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="NumberOfContainers" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The number of containers to be used.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ContainerQuantity" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The quantity for the container.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="eSignature" minOccurs="0">
<xsd:annotation>
<xsd:documentation>If required, this element must contain a GUID, for the eSignature system to accept the transaction as having been authenticated. The GUID format is in the format {36303032-3330-3031-3038-323434363433}, where the numbers can be replaced with any character. It is up to the developer to have requested a password to protect the transaction. An example is that a GUID associated with the act of entering a valid password could be obtained and presented.</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:choice>
</xsd:complexType>
</xsd:element>
<xsd:element name="SerialExpiryDate">
<xsd:annotation>
<xsd:documentation>This element contains the expiry date of a new serial number or range of serial numbers being received into stock.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:date" />
</xsd:simpleType>
</xsd:element>
<xsd:element name="SerialLocation">
<xsd:annotation>
<xsd:documentation>This element contains the location of the serial number or range of serial numbers being received when processing a positive receipt.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SerialQuantity">
<xsd:annotation>
<xsd:documentation>This element is mandatory and specifies the quantity to receive for the specified serial number. If within the 'Serials' group and manual serial, it can only be 1. If within the 'SerialRange' or 'SerialAllocation' group, it is the total quantity to be received for the specified range.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="preserve" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:schema>-
A transaction cannot be processed if the entered job is on hold (Syspro menu | Work in Progress | Setup | Jobs | Edit pulldown | Hold).
-
An error will be returned if the operator is denied access to the job classification against the job (Setup | Security | Operators | Security | Job Classification).
-
A transaction cannot be processed if the entered job has not been confirmed.
-
A transaction cannot be posted if the stock code against the job is on full or partial hold (Syspro menu | Inventory | Setup | Stock Codes | Edit pulldown | On Hold Status).
-
An error will be returned if the operator is denied access to the warehouse against the job (Setup | Security | Operators | Security | Warehouses).
-
A job cannot be receipted into inspection if the operator is denied access to the security activity: WIP Inspection functions (Setup | Security | Operators | Security | Activities).
-
If the entered job is complete and the parameter IgnoreWarnings is set to N, a warning message will be returned.
-
If the entered job is complete, an error message will be returned if the operator is denied access to the security activity: WIP Posting to a completed job (Setup | Security | Operators | Security | Activities).
-
When flagging a job as complete, if there are outstanding material and/or labor allocations against the entered job and the parameter IgnoreWarnings is set to N, a warning message will be returned.
-
If there are outstanding material and/or labor allocations against the entered job, an error message will be returned if the operator is denied access to the security activity: WIP Complete job if outst. P/O's, materials or operations (Setup | Security | Operators | Security | Activities).
-
If the new unit cost exceeds the acceptable cost variance percentage defined in Inventory Setup (Setup | Distribution Setup | Inventory | General tab) and the parameter IgnoreWarnings is set to N, a warning message will be returned.
-
If the new unit cost exceeds the acceptable cost variance percentage defined in Inventory Setup, an error message will be returned if the the operator is denied access to the security activity: Inventory Override on inventory cost variance (Setup | Security | Operators | Security | Activities).
-
A transaction cannot be posted if multiple bins are installed (Setup | Distribution Setup | Inventory | General tab), the entered bin location is on hold (Syspro menu | Inventory | Inventory Query | Query pulldown | Multiple Bins | Edit pulldown | Hold) and the parameter IgnoreWarnings is set to N.
-
A negative receipt cannot cause stock to go negative in a bin or warehouse if negative stock is not allowed (Setup | Distribution Setup | Inventory | General tab).
-
A negative receipt cannot cause stock to go negative in a FIFO bucket, a lot or against an ECC controlled item.
-
When processing a negative receipt and the job is linked to a sales order, an error will be returned if the supplied quantity exceeds the ship quantity against the sales order line.
-
When processing a negative receipt, an error will be returned if the supplied quantity exceeds the quantity manufactured against the job.
-
When processing a negative receipt against a job in inspection, the inspection reference cannot be reduced by more than the quantity manufactured minus the quantity already accepted, scrapped and reworked.
-
When processing a negative receipt against a job in inspection, an error will be returned if the supplied quantity will cause the warehouse's quantity in inspection to go negative.
-
A transaction for a traceable item cannot be posted if the entered lot has been archived.
-
If the stock code is traceable and the lot number should equal the job number (Setup | Lot Traceability Setup | General tab), an error will be returned if the job and lot key types are not the same (Setup | Company Setup | Key Types tab).
-
A transaction for a traceable item cannot be posted if the entered lot is on hold (Syspro menu | Inventory | Inventory Query | Query pulldown | Lots | Edit pulldown | Change).
-
An error will be returned if the serial tracking method against the stock code is manual (Syspro menu | Inventory | Setup | Stock Codes | Tracking tab) and the supplied quantity contains decimals.
-
The number of decimals entered against the quantity cannot exceed the maximum number of decimals defined against the stock code (Syspro menu | Inventory | Setup | Stock Codes | General tab).
-
A warning message will be returned if the stock code's cost is zero, the costing method is standard (Setup | Distribution Setup | Inventory | General tab) and the parameter IgnoreWarnings is set to N.
-
An error will be returned if the CostBasis is defined as W and the Work in Progress value against the job is not greater than zero.
-
A warning message will be returned if the receipt quantity exceeds the quantity outstanding against the job (quantity to manufacture less quantity manufactured) and the parameter IgnoreWarnings is set to N.
-
If the parameter IgnoreWarnings is set to N, warnings will be returned if the job is linked to a sales order and the sales order:
- Has been cancelled
- Is complete
- Is in a status of 0 (Order in process)
- Is in a status of 4 (Warehouse) and maintenance of a sales orders after a delivery note has been printed is not permitted (Setup | Distribution Setup | Sales Orders | Printing tab)
- Line is part of a kit
The sales order will not be updated under these circumstances.
-
If the parameter IgnoreWarnings is set to N, a warning will be returned if the job is linked to a sales order and the warehouse against the job does not match the warehouse against the sales order line. The sales order will not be updated under this condition.
-
If the parameter IgnoreWarnings is set to N, a warning will be returned if the job is linked to a sales order and the sales order is in a status of 4 (Warehouse). The sales order will still be updated under this condition.
-
An error will be returned if the job is linked to a sales order, the sales order is a scheduled order and the stock has not yet been allocated.
-
If multiple bins are installed (Setup | Distribution Setup | Inventory | General tab) and the job is linked to a sales order, the sales order will not be updated if:
- The Work in Progress Setup option: Place multiple bins on hold when receipting a job is set to automatic (Setup | Manufacturing Setup | Work in Progress | General 2 tab)
- The entered bin location is on hold (Syspro menu | Inventory | Inventory Query | Query pulldown | Multiple Bins | Edit pulldown | Hold)
- The element BinOnHold is set to Y
-
The LedgerCode element is ignored unless ledger codes are requested for inventory transactions (Setup | Distribution Setup | Inventory | Options tab) and a ledger code is requested for receipts (Setup | Distribution Setup | Inventory | Options | Define Options pushbutton).
-
If an entry is not supplied against the LedgerCode element or it has been ignored, the WIP ledger code defined against the job 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, the entry will be validated.
In addition, an error message will be returned if the ledger code is on hold. If a ledger code has been supplied against the LedgerCode element and a password has been defined against the ledger code, which does not match the password entered against the element PasswordForLedgerCode (Syspro menu | General Ledger | Setup | General Ledger Codes) an error message will be returned.
-
Warning messages will be returned if a ledger code has been supplied against the LedgerCode element and 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 job is a sub job, errors will be returned if the master job is not on file, is not confirmed or is on hold. A warning will be returned if the master job is complete and the parameter IgnoreWarnings is set to N. If the entered job is complete, an error message will be returned if the operator is denied access to the security activity: WIP Posting to a completed job (Setup | Security | Operators | Security | Activities).
-
An error will be returned if the job is a sub job and a corresponding allocation for the stock code cannot be located against the master job.
-
If the stock code against a sub job is an ECC controlled item (Syspro menu | Inventory | Setup | Stock Codes | Tracking tab), it cannot be issued to the master job if an Engineering Change Order is currently in progress for the item and material allocations have been prevented for all stock codes on the ECO.
-
Refer to WIPTJR.XSD and WIPTJR.XML for the parameters schema and an instance of an XML document for this business object.
-
Refer to WIPTJRDOC.XML and WIPTJRDOC.XSD 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.
WIPTJROUT.XML
Copy
<?xml version="1.0" encoding="Windows-1252"?>
<!-- Copyright 1994-2022 SYSPRO Ltd.-->
<!--
Sample XML for the Job Receipt Posting Business Object
-->
<postjobreceipts Language="05" CssStyle="" DecFormat="1" DateFormat="01" Role="01" Version="6.0.000">
<Item>
<Job>00000107</Job>
<Lot>LOT00107</Lot>
</Item>
<Journals>
<Key>
<JnlYear>2006</JnlYear>
<JnlMonth>12</JnlMonth>
<Journal>00098</Journal>
<EntryNumber>00001</EntryNumber>
<Warehouse>SA</Warehouse>
<GlJournal>
<GlYear>2009</GlYear>
<GlPeriod>02</GlPeriod>
<GlJournal>00311</GlJournal>
</GlJournal>
</Key>
</Journals>
<StatusOfItems>
<ItemsProcessed>1</ItemsProcessed>
<ItemsInvalid>0</ItemsInvalid>
</StatusOfItems>
</postjobreceipts>
Refer to WIPTJROUT.XML for a sample of the XML returned by this business object.
Prerequisites
The Inventory and Work in Progress modules 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.