AddPurchaseOrder - method

Input

Input is .xml file with following marks.

Element

Item description

Obligation

<PurchaseOrderHeader>

 

 

+<PurchaseOrderYear>

Purchase order year

yes

+<PurchaseOrderBook>

Purchase order book

yes

+<SupplierID>

Supplier ID

yes

+<CustomerID>

Customer ID

no

+<Status>

Status

no

+<Document>

Document

no

+<OrderDate>

Order date

no

+<CostUnitID>

Cost unit ID

no

+<CostCenterID>

Cost center ID

no

+<ClerkID>

Clerk ID

no

+<WorkOrderID>

Work order ID

no

+<AnalyticID>

Analytic ID

no

+<AnalyticAN1ID>

Analytic AN1 ID

no

+<AnalyticAN2ID>

Analytic AN2 ID

no

+<AnalyticAN3ID>

Analytic AN3 ID

no

+<ForeseenDeliveryDate>

Foreseen delivery date

no

+<SentDocument>

Sent document

no

+<PickedNote>

Picked note

no

+<CanceledDate>

Canceled date

no

+<CanceledNote>

Canceled note

no

+<CurrencyID>

Currency ID

no

+<RebatePercentage>

Rebate percentage

no

+<NoteHeader>

Note header

no

+<NoteFooter>

Note footer

no

+<Note>

Note

no

+<ClerkIDSupplier>

Clerk ID supplier

no

+<SearchKeySeqence>

Search key seqence

no

+<PriceListID>

Price list ID

no

+<WHType2ID>

WH type2 ID

no

+<WarehouseID>

Warehouse ID

no

+<LanguageID>

Language ID

no

+<EstimatedpayDate>

Estimatedpay date

no

+<DeliveryType>

Delivery type

no

+<ParityCode>

Parity code

no

+<SignedPRACDate>

Signed PRAC date

no

+<AnnexID>

DocumentID of annex attached to purchase order

no

+<DiscountGroupID>

Discount group ID

no

+<FolderID>

ID of folder with document related to purchase order

no

+<ApprovedDate>

Approved date

no

+<ApprovedNote>

Approved note

no

+<ApprovedDeliveryDate>

Approved delivery date

no

+<PurchaseOrderLines>

 

 

++<PurchaseOrderLine>

 

 

+++<LineSEQNumber>

Line SEQ number

yes

+++<ItemID>

Item ID, bar code or alternate code in accordance with ItemIDtype

yes

+++<ItemIDType>

Determines what is entered in ItemID and OrderQuantity
​Possible values are ID for Item ID, BC for bare code, AC for alternate code

yes

+++<OrderedQuantity>

Ordered quantity in original or alternate unit of measure in accordance with ItemIDtype

yes

+++<Price>

Price

no

+++<QuantitySupplier>

Quantity supplier

no

+++<UnitOfMeasureSupplier>

Unit of measure supplier

no

+++<PriceSupplier>

Price supplier

no

+++<DiscountPercentage>

Discount percentage

no

+++<ForeseenDeliveryDate>

Foreseen delivery date

no

+++<CostCenterID>

Cost center ID

no

+++<CostUnitID>

Cost unit ID

no

+++<ClerkID>

Clerk ID

no

+++<WorkOrderID>

Work order ID

no

+++<AnalyticID>

Analytic ID

no

+++<Note>

Note

no

+++<Description>

Description

no

+++<ItemTitle1>

Item title1

no

+++<ItemTitle2>

Item title2

no

+++<UnitOfMeasure>

Unit of measure

no

+++<DimensionQuantity>

Dimension quantity

no

+++<DimensionLenght>

Dimension lenght

no

+++<DimensionWidth>

Dimension width

no

+++<DimensionHeight>

Dimension height

no

+++<DiscountPercentage2>

Discount percentage2

no

+++<DiscountPercentage3>

Discount percentage3

no

+++<DiscountPercentage4>

Discount percentage4

no

+++<DiscountPercentage5>

Discount percentage5

no

+++<QuantityForTesting>

Quantity for testing

no

+++<NumberOfPackages>

Number of packages

no

+++<Series>

Series

no

+++<EstimatedSupplyDate>

Estimated supply date

no

 

Output

The output is a .xml file in which it is stated, if the method is successful or not.

In case of succeful addition of purchase order returns in XML purchase order number. Example:

<?xml version="1.0" encoding="utf-8"?>
<CreateResult xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <Keys>
    <Key>
      <Name>Leto</Name>
      <Value>2017</Value>
    </Key>
    <Key>
      <Name>SifraKnjigeNarocila</Name>
      <Value>PR</Value>
    </Key>
    <Key>
      <Name>StevilkaNarocila</Name>
      <Value>92</Value>
    </Key>
  </Keys>
  <ResultCode>Created</ResultCode>
  <Errors />
</CreateResult>

 

 

Natisni