Purchase Order Release/Create |
Purchase Order Release/Create integration is triggered when a Card is Released to External Supplier in ULtriva
 Note |
|---|
Please make sure the Purchase Order Release Event Rule for Integration is Enabled |
| Note |
|---|
If the Release should wait then please Enable Release Waiting For Purchase Order Flag is set for this Item |
Ultriva PO Release:
Ultriva:
Updates all the related fields required to create the PO.
These fields are identified in the column below
ERP:
ERP Connector must consume this data and send the Purchase Order Results back to Ultriva
ERP Connector must update the PO related and the Status fields
Release Card action would generate the P.O. Release operation in the ERP System. UEK application supports following types of P.O.
- Blanket P.O.: PO number is constant for an Item or group of Items. Every transaction creates new PO Release/Release Line to existing PO. P.O. number is stored in Item 2 Supplier Master Table. UEK gets newly created PO line number and saves it in CardCycle table to be used in PO Receive transaction.
- Standard P.O.: Every transaction creates new PO. PO number and PO line number are saved in CardCycle table after each transaction.
Purchase Order Release/Create SQL Table DefinitionThe following table defines the fields in Purchase Order SQL Table.
Processing Logic
ERP Connector must query this table periodically by running a SELECT Query with WHERE Clause ((ERP_STATUS IS NULL OR ERP_STATUS = '') AND UEK_STATUS = 'created')
If one or more records returned by above query then Connector does following: Update the record with the ERP_STATUS = 'Processing' and ERP_LAST_UPDATE_DATE = current time Then sends the data to ERP System
Once ERP Creates a Standard Purchase Order or Blanket Release then connector must populate the required ERP Fields back to this table and Update the ERP_STATUS = 'processed' and ERP_LAST_UPDATE_DATE = CurrrentTime where clause should be GID column of this record
If the transaction failed in the ERP system, then the connector must update the record with the ERP_STATUS = 'FAILED' AND ERP_LAST_UPDATE_DATE = Current time.
If any additional error details to be passed back to ultriva then Connector should Insert those details into the UEK_INTERFACE_ERRORS table with ROW_ID is set to the GID of this staging record.
PO Release/Create Data (outbound from Ultriva) UEK2ERPPOData
Field Name | Data Type | Length | Required | Populated By | Description |
|---|---|---|---|---|---|
GID | VARCHAR | 32 | Y | Ultriva | Unique Identifier. |
PREPARER_NAME | VARCHAR | 64 | N | Ultriva | Item Buyer Name |
ITEM_NUM | VARCHAR | 32 | Y | Ultriva | Item Code/Number for this transaction |
QUANTITY | INTEGER | N/A | Y | Ultriva | Qty released |
UNIT_PRICE | NUMBER | N/A | N | ERP | Unit Price to be passed to Ultriva for this Purchase Order |
UNIT_OF_MEASURE | VARCHAR | 16 | N | Ultriva | Unit of Measure defined in Ultriva for this Item Number |
DESTINATION_ORGANIZATIOM_CODE | VARCHAR | 32 | Y | Ultriva | Plant Or Workcenter Code where this Card Released |
DESTINATION_SUBINVENTORY | VARCHAR | 32 | N | Ultriva | SubInventory Code (as custom field) defined in Ultriva Item |
DELIVER_TO_LOCATION_CODE | VARCHAR | 32 | N | Ultriva | Location Code defined in the Item Master |
DELIVER_TO_REQUESTOR_NAME | VARCHAR | 64 | N | Ultriva | Item's Co-ordinator (buyer) Name |
NEED_BY_DATE | DATETIME | N/A | Y | Ultriva | Required Receive Date |
ORG_ID | INTEGER | N/A | N | Ultriva | Organization ID set as custom configuration field in Business Unit |
VENDOR_CODE | VARCHAR | 32 | Y | Ultriva | Vendor Code - the supplier who is receiving this order |
VENDOR_SITE_CODE | VARCHAR | 32 | N | Ultriva | Vendor Site Code - A Custom field set in the Supplier |
BUYER_CODE | VARCHAR | 32 | N | Ultriva | Buyer user code set in the buyer user record |
ERP_PO_NUMBER | VARCHAR | 32 | N | Ultriva/ERP | Blanket Purchase Order number set in the Item 2 Supplier relation ship |
ERP_PO_LINE_NUMBER | INTEGER | N/A | N | Ultriva/ERP | Blanket Purchase Order Line number set in the Item 2 Supplier relation ship |
ERP_PO_RELEASE_NUM | VARCHAR | N/A | N | ERP | The P.O. Release No if any. |
ERP_PO_RELEASE_LINE_NUM | VARCHAR | 32 | N | ERP | The Release Line No if any. |
ERP_STATUS | VARCHAR | 32 | Y | ERP | Status of Transcation ERP Should Set to Processed or Failed. |
ERP_LAST_UPDATE_DATE | DATETIME | N/A | Y | ERP | Record Updated Time |
KANBAN_CARD_NO | VARCHAR | 32 | N | Ultriva | Kanban Card ID from Ultriva |
BPFL_VERSION | INTEGER | N/A | Y | Ultriva | Card Version No. Ultriva Internal Value |
CYCLE_NO | INTEGER | N/A | Y | Ultriva | Card Cycle No. |
CYCLE_ID | VARCHAR | 32 | Y | Ultriva | Unique Cycle ID |
UEK_STATUS | VARCHAR | 32 | Y | Ultriva | Status of Transcation. Ultriva will set it to Created. |
UEK_LAST_UPDATE_DATE | DATETIME | N/A | Y | Ultriva | Record Added/Updated Time |
PO_STRATEGY | VARCHAR | 8 | Y | Ultriva | Ultriva Internal Value |
PO_TRANSACTION_ID | VARCHAR | 32 | Y | Ultriva | Ultriva Internal Value |
FLAGS | INTEGER | N/A | N | Ultriva | Internal Ultriva Item Flags value |
ReleaseID | Varchar | 32 | N | Ultriva | Barcode ID for the Card with Cycle and Checksum |
ParentBusinessCode | Varchar | 128 | N | Ultriva | Parent Business Unit code. In case if the card is released for workcenter then this field will contain the Parent Business Unit Code |
ParentBusinessName | Varchar | 128 | N | Ultriva | Parent Business Unit Name. In case if the card is released for workcenter then this field will contain the Parent Business Unit Name |
ParentConcentratorName | Varchar | 128 | N | Ultriva | Parent Business Unit Concentrator Name. In case if the card is released for workcenter then this field will contain the Parent Business Unit Concentrator Name |
CARD_LOCATION | Varchar | 64 | N | Ultriva | Current Storage Location Code of the Card |