NCR Data Load |
This interface is used to create a NCR for the Items received by the Plant and identified as having Non Conformity.
The following table defines the fields in NCR Data Load file. The fields marked as bold are required. Required fields must always have non-empty data.
Field Name | Data Type | Length | Required | Nullable | Description |
---|---|---|---|---|---|
QUALITYNUMBER | STRING | 32 | Y | N | Unique Number for the NCR |
EBJ_BUSCODE | STRING | 32 | Y | N | Business Unit Code. This must match with the code in Ultriva. |
EBJ_ITEMNO | STRING | 32 | N | Y | Item Number for which the NCR is created. |
SUPPLIERCODE | STRING | 32 | Y | N | Supplier Code- Supplier of the Item |
ORDERNUM | STRING | 64 | N | Y | Purchase Order Number |
ORDERLINENUM | INT | N/A | N | N | Purchase Order Line Number |
ORDERRELEASENUM | STRING | 32 | N | Y | Purchase Order Blanket Release Number if any |
ORDERRELEASELINENUM | STRING | 32 | N | Y | Purchase Order Blanket Release Line Number |
LOTNUM | STRING | 64 | N | Y | Supplier Lot Number |
QTYRECEIVED | FLOAT | N/A | N | Y | Total Quantity Received |
QTYREJECTED | FLOAT | N/A | N | Y | Total Quantity Rejected |
LIABILITYASSIGNMENT | STRING | 64 | N | Y | Assignment of Liability for this NCR – One of the entries in the Master Code. If not present then the given code will be added to the Master code |
STARTDATE | DATETIME | N/A | Y | N | NCR Start Date |
DISPOSITIONREVIEWSTARTDATE | DATETIME | N/A | N | Y | Date on which the Disposition Review Started |
DISPOSITIONCODE | STRING | 32 | Y | N | Disposition Code – Entry in the Master Code. If not present then the given code will be added to the Master code |
DISPOSITIONFINALIZEDTIME | DATETIME | N/A | N | Y | Date on which the Disposition Finalized |
RMANUMBER | STRING | 64 | N | Y | RMA Details for the NCR |
PROCESSNCCODE | STRING | 32 | Y | N | Process NC Code – Entry in the Master Code. If not present then the given code will be added to the Master code |
CHARACTERISTICNO | STRING | 64 | N | Y | Characteristic Number for the NCR |
PRODUCTREQMT | STRING | 64 | N | Y | Product Requirement for the NCR |
SERIALNO | STRING | 64 | N | Y | Serial No |
REVISION | STRING | 64 | N | Y | Revision |
ROOTCAUSECODE | STRING | 32 | Y | N | Root Cause Code - Entry in the Master Code. If not present then the given code will be added to the Master code |
SUPPLIERRESPONSEACCEPTABLE | INT | N/A | N | Y | Accepting Supplier Response |
SUPPLIERRESPONSEVERIFIEDBY | STRING | 32 | N | Y | Supplier Response Verified By |
SUPPLIERRESPONSEVERIFIEDTIME | DATETIME | N/A | N | Y | Date on which the Supplier Response was verified |
SUPPLIERNOTES | STRING | 64 | N | Y | Supplier Notes for the NCR |
DEBIT MEMO | STRING | 64 | N | Y | Debit Memo for the NCR |
COMPLETIONDATE | DATETIME | N/A | N | Y | NCR Completion Date |
This interface uses following fields as uniqueness constraint.
Field Name | Mandatory Field |
---|---|
QUALITYNUMBER | Yes |
EBJ_BUSCODE | Yes |
If a record already exists with PROCESSED status for a given QUALITYNUMBER then this RECORD is marked as DUPLICATE
Given EBJ_BUSCODE must exist in the system.
Batch Job Processor validates each record for the following:
Given EBJ_ITEMNO must exist in the given Business Unit context.
Given SUPPLIERCODE must be an approved Supplier for the Item Number provided in the system.
Given ORDERNUM must be a valid Order Number.
Given QTYRECEIVED and QTYREJECTED must be valid values
The Batch Job Processor creates a Non Conformity Report for the given order details.
The Kanban cards related to the given ORDERNUM and ORDERLINENUM are first fetched and marked for Non Conformity.
The Non Conformity Type will be “Product” as the NCR is raised for the Item No provided.
The Non Conformity Origin will be “Incoming Inspection”.
All the Codes (Disposition Code, Process NC Code, RootCause Code) if not available in the Master Code will be generated and then added to the NCR.
Disposition details are added to the NCR.
Supplier Notes is appended to the NCR.
The Completion Date sent should be greater than the Start Date. If it is not sent correctly it will check for the Disposition Finalized Time and if that is greater than Start Date then that will be used as Completion Date else it will populate the System date as the Completion Date.
Then finally the NCR is also closed in the process.
The Batch Job Processor will mark incoming records with specific error messages during processing.
The following table shows the error messages and their meaning:
![]() |
---|
In the following table the placeholders are encoded with curly braces. |
Error Message | Meaning |
---|---|
Given Supplier Code {0} not found in the associated suppliers | Given supplier is not an approved supplier in Ultriva. |
Given Item No {0} not found in the associated suppliers | Given item code is not found in the given business unit code. |
Given PO# {0}, PO Line# {1} is not found in the system | Given OrderNum is not available in the system for the Business unit provided. |
Invalid Quantity Received {0} | Invalid Quantity Received {0} |
Invalid Quantity Rejected {0} | Invalid Quantity Rejected {0} |