A Time Receipt is a summary of many objects
- The Time Receipt itself
- Time Receipt Scrap information
- Issue Document
- Receipt Document
In the background
- Post Calculation
- Additional Warehouse transaction
- Quality Control Order
- Close Document request
It is possible to create a time receipt with automatic backflushing process.
It is possible to create a time receipt with all information about Issue and Receipt documents.
Example
Create Time Receipt for work order 1314, Line 10, Routing Position 10 and PersonnelId 14 for 2 Pcs from 8 to current time
(Assembly: If Stock and Production unit not the same or Consume Unit is defined: See "Confirm Units"
With Scrap Definition
With Issue Document
With Reciept Document
[
{"DocEntry":1314,"LineNumber":10,"LineNumber2":10,"PersonnelId":"14","QuantityGoodRUoM":2,"FromTime":"8:00",
"TimeReceiptScrap":
[
{"ScrapId":"DontCheckQty","Quantity":3,"UDF1":"test"},
{"ScrapId":"Scrap-001","Quantity":3,"UDF1":"test"}
],
"Issue":{"Lines":[{"ItemCode":"RM","WhsCode":"01","Quantity":1,"BaseLineNumber2":10}]},
"Receipt":{"Lines":[{"ItemCode":"FP","WhsCode":"01","Quantity":2}]}
}
]
Result
{
"value": 1, // 1 = ok, otherwise the error message
"SystemNumber": [
2581 // the created Time Receipt number, can be a list of Numbers
]
}
All properties are available from TimeReceipt, TimeReceiptScrap, Issue and ReceiptDocument
In Receipt and Issue document you don't need to define BaseDocentry/BaseLineNumber, only LineNumber2 for BoM Position.
The System does not check, if the defined Material is OK. If wrong Material is defined, the system books the wrong Material.
The System books Items only for not closed Positions. If position is closed or position number is wrong, the system ignore the Information without error message.
In routing position > extended > Confirm Unit you can define a Confirm unit and a Conversion Factor.
If you want to work with the confirm unit, you must define the quantity in field QuantityGoodRUoM
You can read the UoM in WorkorderRouting/RUoM
If you want to create a receipt for the assembly in same time you must calculate the quantity in Warehouse Unit from the Assembly
Formula is
Receipt Quantity = QuantityGoodRUoM * WorkorderRouting/RUoMFactor : WorkorderPos/UoMConsumptionFactor
|
Additional Properties are Available
Field
|
Type
|
Description
|
DocEntry
|
Edm.Integer
|
Work order DocEntry
|
LineNumber
|
Edm.Integer
|
Work order Position
|
LineNumber2
|
Edm.Integer
|
Work order Routing Position (internal Number)
|
LineNumber3
|
Edm.Integer
|
Optional Position Parallel Resource
|
PersonnelId
|
Edm.String
|
PersonnelId
|
TimeType
|
Edm.String
|
Optional The Time Type
|
ResourceId
|
Edm.String
|
Optional The ResourceId, if not Standard ResourceId
|
QuantityGood
|
Edm.Decimal
|
Optional Quantity in Unit of Assembly
|
QuantityGoodRUoM
|
Edm.Decimal
|
Quantity in Unit of Measurement from Routing Position
|
QuanittyScrap
|
Edm.Decimal
|
Optional Quantity Scrap
|
QuantityScrapRUoM
|
Edm.Decimal
|
Optional Quantity Scrap in Unit of measurement from Routing position. Don't define this, if scrap information defined
|
ExternalCosts
|
Edm.Decimal
|
Price
|
Remarks
|
Edm.String
|
a Remark
|
CostElementId
|
Edm.String
|
Optional Cost Element Id
|
CostCenter
|
Edm.String
|
Optional Cost Center
|
DocDate
|
Edm.Date
|
Define the document (Validation) Date
In Beas Userinterface the DocDate and StartDate is always the same
In BSL you must define the DocDate separatly
|
StartDate
|
Edm.Date
|
Start date
Information: StartDateTime is not allowed. Use Start Date and Start Time
Note: if StarDate not today, you must define the DocDate and the Date in Receipt and Issue Document too (Beas 2020.02.01)
[{
"DocEntry": 6001745,
"LineNumber": "10",
"LineNumber2": "10",
"PersonnelId": "1",
"QuantityGood": 1,
"DocDate": "2020/02/28",
"StartDate": "2020/02/28",
"EndDate": "2020/02/28",
"Duration": "75",
"ResourceId":"R-01-1T.STD.08H",
"QuantityScrap":0,
"Remarks": "2554_20_10_4",
"CloseEntry": false, /* Note: if you set this to true: See CloseEntry */
"ManualBooking": true,
"Issue":{"Date":"2020/02/28", "Lines":
[{"ItemCode":"RM","WhsCode":"01","Quantity":1,"BaseLineNumber2":10,"CloseEntry": false}]},
"Receipt":{"Date":"2020/02/28", "Lines":
[{"ItemCode":"FP001","WhsCode":"01","Quantity":1,"CloseEntry": false}]}
}]
|
|
StartTime
|
Edm.String
|
Start time
|
EndDate
|
Edm.Date
|
Optional End Date. If current Date, you don't need to define this
|
EndTime
|
Edm.String
|
Optional End Time. If current Time, you don't need to define this
|
FromTimeReceiptRunning
|
Edm.Integer
|
Get all information from the TimeReceiptRunning with defined System Number. In this case you don't need to define StartDate or StartTime
The TimeReceiptRunning Entry will be deleted
|
CloseEntry
|
Edm.Boolean
|
if defined as "true", the system will close the routing position
if this the last routing position, the system will related to close the work order position and com
if you want to close the position with receipt assembly, the system will close the receipt position too
You don't need to send the close information to the receipt document
TimeReceipt {
"CloseEntry":true, /* Last entry. We will close time receipt and work order position */
"Receipt":{
"Lines":[{
"ItemCode":"FP",
"WhsCode":"01",
"Quantity":2
}]
}
}
|
|
ManualBooking
|
Edm.Boolean
|
Define, if the system create the issue and receipt document automatically, related to the configuration settings or if you define the material self in this post command
"ManualBooking":true
You define the materual for issue in .. "issue":{IssueWo} and "receipt":{receiptWo}
Example:
{"DocEntry":1314,"LineNumber":10,"LineNumber2":10,"PersonnelId":"14","QuantityGood":2,"FromTime":"8:00",
"Issue":{"Lines":[{"ItemCode":"RM","WhsCode":"01","BaseLineNumber2":10}]},
"Receipt":{"Lines":[{"ItemCode":"FP","WhsCode":"01","Quantity":2}]}
}
With the PreAssign object you can read the material, which you need for this time receipt
"ManualBooking":false
The system check configuration wizzard settings and related to this setting the system create the issue / receipt document automatically.
Note: if the assembly is booked on a bin managed warehouse, then this produce an error or an open document
|
|
TimeReceiptRunningId
|
Edm.Integer
|
The System Number of linked TimeReceiptRunning Object. Define this, if you don't use "FromTimeReceiptRunning", but it's linked to the item.
Needed for calculate Duration
The system will delete the entry after saving
|
TimeReceiptScrap
|
Edm.Array
|
Define Json Array with Scrap Information
[
{
"ScrapId":edm.String,
"Quantity":edm.Decimal,
"UDF1"..."UDF4":edm.String,
"ScrapReason":edm.String,
"Percent":edm.Decimal
}
]
Quantity in UoM of Routing Position
The system calculate automatically the Scrap Quantity
|
Duration
|
Edm.Integer
|
Duration in Minute
If not defined, the system calculate this autoamtically
|
Barcode
|
Edm.String
|
Optional: Define Document by Routing Barcode
(Not compatible, if you work with parallel Resource)
|
CalculateDuration
|
Edm.Bolean
|
Define, if the system must calculate the duration.
You don't need to set this. If Duration is not defined, the system calculate this always. But it's possible to disable the automatic calculation
|
Issue
|
Edm.Json
|
Define the Issue document for all material positions
Don't define DocEntry or LineNumber. Only LineNumber2 for Bill of Material positions must be defined.
More see Issue Document
Example:
"Issue":{"Lines":[{"ItemCode":"RM","WhsCode":"01","Quantity":1,"Number2":10}]}
|
Receipt
|
Edm.Json
|
Define the receipt document
Don't define DocEntry or LineNumber.
More see Receipt Document
Example:
"Receipt":{"Lines":[{"ItemCode":"FP","WhsCode":"01","Quantity":2}]}
|
LogInfo
|
Edm.String
|
Information about the Time Calculation.
The function TimeReceipt.TimeCalculation return this information.
You must define this, if time Calculation not inside this process
|
LogInfoHtml
|
Edm.String
|
Infomation about the Time Calculation in HTML Format
|
UDF1...UDF15
|
Edm.String
|
UDF 1-15 Beas2020.08
|
|
