Order Acknowledgment |
The following table(s) illustrate(s) the data mapping between Ultriva and Oracle.
RECORD_ACCEPTANCE Using PO_CHANGE API
ULTRIVA | ORACLE | Oracle Documentation | Ultriva Notes |
---|---|---|---|
GID | NA | NA | NA |
PREPARER_NAME | NA | NA | NA |
ITEM_NUM | NA | NA | NA |
QUANTITY | NA | NA | NA |
UNIT_PRICE | NA | NA | NA |
UNIT_OF_MEASURE | NA | NA | NA |
DESTINATION_ORGANIZATION_CODE | NA | NA | NA |
DESTINATION_SUBINVENTORY | NA | NA | NA |
DELIVER_TO_LOCATION_CODE | NA | NA | NA |
DELIVER_TO_REQUESTOR_NAME | NA | NA | NA |
NEED_BY_DATE | NA | NA | NA |
ORG_ID | NA | NA | NA |
VENDOR_CODE | NA | NA | NA |
VENDOR_SITE_CODE | NA | NA | NA |
BUYER_CODE | NA | NA | NA |
ERP_PO_NUMBER | PO_NUM | Purchase order number | NA |
ERP_PO_LINE_NUMBER | NA | NA | NA |
ERP_PO_RELEASE_NUM | RELEASE_NUM | Required if the purchase order is a release. The pass-in value must be a number. | NA |
ERP_PO_RELEASE_LINE_NUM | NA | NA | NA |
ERP_STATUS | NA | NA | NA |
ERP_LAST_UPDATE_DATE | NA | NA | NA |
KANBAN_CARD_NO | NA | NA | NA |
BPFL_VERSION | NA | NA | NA |
CYCLE_NO | NA | NA | NA |
CYCLE_ID | NA | NA | NA |
UEK_STATUS | NA | NA | NA |
UEK_LAST_UPDATE_DATE | NA | NA | NA |
PO_STRATEGY | NA | NA | NA |
PO_TRANSACTION_ID | NA | NA | NA |
FLAGS | NA | NA | NA |
CATEGORY | NA | NA | NA |
RELEASEID | NA | NA | NA |
ParentBusinessCode | NA | NA | NA |
ParentBusinessName | NA | NA | NA |
ParentConcentratorName | NA | NA | NA |
CARD_LOCATION | NA | NA | NA |
NA | REVISION_NUM | Which revision of the purchase order/release is being acted upon. | Before calling the API, lookup the PO and get the version number |
''NEW' | ACTION | Indicates the action to take. The value must be NEW. | NA |
NA | ACTION_DATE | Indicates the date of follow-up action. Default value is SYSDATE | NA |
NA | EMPLOYEE_ID | The fnd_global.user_id of the buyer. | NA |
''Y' | ACCEPTED_FLAG | Indicate if purchase is accepted. Must be ’Y’ or ’N’ | NA |
''Accepted All Terms' | ACCEPTANCE_ LOOKUP_CODE | Type of acceptance, its value must be corresponding to the LOOKUP_CODE in PO_ LOOKUP_CODES table with LOOKUP_TYPE of "CCEPTANCE TYPE. The possible values are: Accepted Terms, Accepted All Terms, On Schedule, Unacceptable Changes, and REJECTED. | NA |
NA | NOTE | NA | NA |
1 | VERSION | Version of the API | NA |
NA | NA | NA | NA |